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 payment account information to process a payment transaction;
converting, by the mobile computing device, the request for the payment account information 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 account information 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 account information to the merchant system computing device.
2. The computer-implemented method of claim 1 , wherein converting the request for the payment account information to the request readable by the non-secure memory processor comprises:
converting the request for the payment account information to a readable request for a payment processing response by the non-secure memory processor of the mobile computing device.
3. The computer-implemented method of claim 1 , wherein converting, by the mobile computing device, the request for the payment account information to the request readable by the non-secure memory processor comprises converting the request for the payment account information into bytes comprising the request readable by the non-secure memory processor.
4. The computer-implemented method of claim 1 , wherein the response to the request for the payment account information provides a same functionality as a response created by the secure memory processor.
5. The computer-implemented method of claim 1 , wherein the response to the request for the payment account information is indistinguishable from a response created by the secure memory processor.
6. The computer-implemented method of claim 1 , wherein the response to the request for the payment account information comprises a payment account identifier.
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 an account comprising information for at least one of a credit card account, debit account, stored value account, gift card account, and bank account for a user associated with the mobile computing device.
8. The computer-implemented method of claim 6 , 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 6 , wherein the payment account identifier is retrieved from a digital wallet application on the mobile computing device.
10. The computer-implemented method of claim 1 , wherein the request for the payment account information is received using a near field communication (NFC) protocol.
11. The computer-implemented method of claim 6 , 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.
12. The computer-implemented method of claim 6 , 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.
13. 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 account information 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.
14. 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 payment account information to process a payment transaction;
converting, by the mobile computing device, the request for the payment account information 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 account information that is identifiable by the merchant system as a payment response generated by a secure memory processor.
15. The one or more non-transitory computer-readable media of claim 14 , wherein:
the response to the request for the payment account information comprises a payment account identifier; and
the payment account identifier is generated by an account management system and transmitted to the mobile computing device, wherein the account management system maintains an account comprising information for at least one of a credit card account, debit account, stored value account, gift card account, and bank account for a user associated with the mobile computing device.
16. The one or more non-transitory computer-readable media of claim 15 , wherein the operations further comprise communicating, by the mobile computing device, the payment account identifier to the account management system for payment account identifier verification during processing of a payment request.
17. A mobile computing device for processing payment transactions, comprising:
a storage device;
a controller communicatively coupled to the storage device; and
a processor communicatively coupled to the storage device and the controller, the controller of the mobile computing device executing application code instructions that are stored in the storage device to cause the mobile computing device to:
receive a request for payment account information to process a payment transaction from a merchant system computing device; and
convert the request for the payment account information to a request readable by the processor; and
the processor of the mobile computing device executing application code instructions that are stored in the storage device to cause the mobile computing device to:
generate a response to the request for the payment account information that is identifiable as a response created by a secure element processor, the response comprising a payment account identifier.
18. The mobile computing device of claim 17 , wherein the payment account identifier is generated by a non-secure memory processor.
19. The mobile computing device of claim 17 , wherein the storage device comprises a secure memory other than a secure element memory.
20. The mobile computing device of claim 17 , wherein the storage device comprises a combination memory with secure memory and non-secure memory portions.