Processing payment transactions without a secure element
A user conducts a wireless payment transaction with a merchant system by transmitting payment information from a user device to a terminal reader without accessing a secure element resident on the user device. A user taps a user device in a merchant system's terminal reader's radio frequency field. The terminal reader and the user device establish a communication channel and the terminal reader transmits a signal comprising a request for a payment processing response. The signal is received by the user device and converted by a controller to a request understandable by an application host processor. The controller transmits the request to the application host processor, where the request is processed, and a response is transmitted to the controller and then to the terminal reader. The response generated by the application host processor is identifiable by the merchant system as a payment response.
1. A computer-implemented method to process payment transactions without accessing secure memories, comprising: receiving, by a mobile computing device and from a merchant system computing device, a request for a payment processing response; converting, by the mobile computing device, the request for the payment processing response to a request readable by a non-secure memory processor of the mobile computing device; generating, by the non-secure memory processor of the mobile computing device, a response to the request for the payment processing response that is identifiable by the merchant system as a payment response generated by a secure memory processor; and transmitting, by the mobile computing device, the response to the request for the payment processing response to the merchant system computing device.
2. The computer-implemented method of claim 1 , wherein the request for the payment processing response is a request to proceed with a financial payment transaction.
3. The computer-implemented method of claim 1 , wherein the response to the request for the payment processing response includes an indication that the mobile computing device is capable of performing a financial transaction.
4. The computer-implemented method of claim 1 , wherein the request for the payment processing response is a request for payment account information.
5. The computer-implemented method of claim 1 , wherein the response to the request for the payment account information comprises a payment account identifier.
6. The computer-implemented method of claim 5 , wherein the payment account identifier is associated with at least one of a credit card account, a debit account, a stored value account, a gift card account, or a bank account for a user associated with the mobile computing device.
7. The computer-implemented method of claim 6 , wherein the payment account identifier is generated by an account management system and transmitted to the mobile computing device, wherein the account management system maintains information for at least one of the credit card account, the debit account, the stored value account, the gift card account, or the bank account for the user associated with the mobile computing device.
8. The computer-implemented method of claim 5 , wherein the payment account identifier is associated with at least one of a geographic limitation, a time limitation, or a number of use limitation.
9. The computer-implemented method of claim 5 , wherein the payment account identifier is retrieved from a digital wallet application on the mobile computing device.
10. The computer-implemented method of claim 5 , further comprising communicating, by the mobile computing device, the payment account identifier to an account management system for payment account identifier verification during processing of a payment request.
11. The computer-implemented method of claim 5 , wherein the non-secure memory processor resident on the mobile computing device generates the payment account identifier using a scheme that can be replicated by an account management system during processing of a payment request.
12. The computer-implemented method of claim 1 , wherein the response to the request for the payment processing response includes at least one of a proxy account number or a token account number.
13. The computer-implemented method of claim 1 , wherein converting the request for the payment processing response to the request readable by the non-secure memory processor comprises: converting the request for the payment processing response to a readable request for a payment processing response by the non-secure memory processor of the mobile computing device.
14. The computer-implemented method of claim 1 , wherein converting, by the mobile computing device, the request for the payment processing response to the request readable by the non-secure memory processor comprises converting the request for the payment processing response into bytes comprising the request readable by the non-secure memory processor.
15. The computer-implemented method of claim 1 , wherein the request for the payment processing response provides a same functionality as a response created by the secure memory processor.
16. The computer-implemented method of claim 1 , wherein the request for the payment processing response is indistinguishable from a response created by the secure memory processor.
17. The computer-implemented method of claim 1 , wherein the request for the payment processing response is received using a near field communication (NFC) protocol.
18. The computer-implemented method of claim 1 , wherein: generating, by the non-secure memory processor of the mobile computing device, the response to the request for the payment processing response comprises allowing the mobile computing device to process payment transactions using financial account information for any of a plurality of payment providers without transferring control of a secure memory processor from one payment provider to a different payment provider.
19. One or more non-transitory computer-readable media having computer-readable program instructions embodied thereon that when executed by a mobile computing device cause the mobile computing device to perform operations, the operations comprising:
receiving, by a mobile computing device and from a merchant system computing device, a request for a payment processing response; converting, by the mobile computing device, the request for the payment processing response to a request readable by a non-secure memory processor of the mobile computing device; and
generating, by the non-secure memory processor of the mobile computing device, a response to the request for the payment processing response that is identifiable by the merchant system as a payment response generated by a secure memory processor.
20. The one or more non-transitory computer-readable media of claim 19 , wherein: the request for the payment processing response is a request to proceed with a financial payment transaction; and the response to the request for the payment processing response includes an indication that the mobile computing device is capable of performing a financial transaction.
21. The one or more non-transitory computer-readable media of claim 19 , wherein: the request for the payment processing response is a request for payment account information; and the response to the request for the payment account information comprises a payment account identifier.
22. The computer-implemented method of claim 21 , wherein the payment account identifier is generated by an account management system and transmitted to the mobile computing device, wherein the account management system maintains information for at least one of the credit card account, the debit account, the stored value account, the gift card account, or the bank account for the user associated with the mobile computing device.
23. A mobile computing device for processing payment transactions, comprising:
one or more storage devices; a controller communicatively coupled to the one or more storage devices; and a processor communicatively coupled to the one or more storage devices and the controller, the controller of the mobile computing device configured to execute application code instructions that are stored in the one or more storage devices to cause the mobile computing device to:
receive a request for a payment processing process from a merchant system computing device; and convert the request for the payment processing response to a request readable by the processor; and the processor of the mobile computing device configured to execute application code instructions that are stored in the one or more storage devices to cause the mobile computing device to:
generate a response to the request for the payment processing response that is identifiable as a response generated by a secure element processor.
24. The mobile computing device of claim 23 , wherein: the request for the payment processing response is a request to proceed with a financial payment transaction; and the response to the request for the payment processing response includes an indication that the mobile computing device is capable of performing a financial transaction.
25. The mobile computing device of claim 23 , wherein: the request for the payment processing response is a request for payment account information; the response to the request for the payment account information comprises a payment account identifier; and the payment account identifier is generated by the processor.
26. The mobile computing device of claim 23 , wherein the one or more storage devices comprises a secure memory other than a secure element memory.
27. The mobile computing device of claim 23 , wherein the one or more storage devices comprises a combination memory with secure memory and non-secure memory portions.