System and method for providing software-based contactless payment

Abstract

Systems and methods provide software-based contactless payments. According to various embodiments, a system for software-based contactless payment includes a token manager that generates a token and provides the token to a mobile device of a customer for use with a transaction, a communication interface that receives the token in association with a transaction, and a processor that processes the token using to determine whether to authorize the transaction.

1 - 20 . (canceled) 
     
     
         21 . A method for software-based contactless payment, comprising:
 receiving, from a customer mobile device via a communication network, a request for a token for use with a transaction;   generating, using a processor, the token in response to the request;   providing, via the communication network when the customer mobile device is in an online environment, the token to the customer mobile device for use with the transaction, wherein the token is stored within an app processor of the customer mobile device that is connectively coupled to an embedded NFC chip;   receiving, through an authorization network from a merchant system via the customer mobile device embedded NFC chip, the token in association with a transaction and transaction data;   comparing the received token and transaction data to a database of provided tokens, wherein each provided token is associated with one or more parameter requirements including transaction limits, use limits and time limits; and   transmitting, via the authorization network, an authorization response based on the comparison, wherein a transaction is authorized when the received token matches a token in the database and the transaction data complies with the parameter requirement.   
     
     
         22 . The method of  claim 21 , wherein the token comprises randomly-generated alphanumeric characters. 
     
     
         23 . The method of  claim 21 , wherein the token is provided to the customer mobile device in real-time by a real-time data application programming interface for use with the transaction. 
     
     
         24 . The method of  claim 21 , wherein the customer mobile device enables an NFC emulation mode by a card emulation application programming interface. 
     
     
         25 . The method of  claim 21 , further comprising receiving an identifier associated with the mobile device and utilizing the identifier in a transaction authorization determination. 
     
     
         26 . The method of  claim 21 , wherein the token serves as a limited-use credit card number. 
     
     
         27 . The method of  claim 21 , wherein the token is further received through an NFC data exchange format application programming interface configured for reading and writing. 
     
     
         28 . The method of  claim 21 , wherein the token is formattable by the merchant system into a track of data utilized directly by the authorization network. 
     
     
         29 . The method of  claim 21 , wherein the received token is transmitted in response to receiving a personal identification number provided by the customer via the customer mobile device. 
     
     
         30 . The method of  claim 21 , wherein the one or more parameter requirements enables a previous token to be used for a defined period of time to enable a transaction when the customer mobile device lacks a connection to the communication network. 
     
     
         31 . A system for software-based contactless payment, comprising:
 a token manager that:
 generates a token in response to receiving a request for the token via a communication network from a customer mobile device
 transmits the token to the customer mobile device in an online environment for use with a transaction, wherein the token is stored within an app processor of the customer mobile device, the app processor connectively coupled to an embedded NFC; 
 
   a communication interface that receives, through an authorization network from a merchant system via the customer mobile device embedded NFC chip, the token in association with the transaction and transaction data; and   a processor that:
 compares the received token and transaction data to a database of provided tokens, wherein each provided token is associated with one or more parameter requirements including transaction limits, use limits and time limits; and 
 authorizes a transaction when the received token matches a token in the database and the transaction data complies with the parameter requirement, wherein the communication interface transmits the authorization via the authorization network. 
   
     
     
         32 . The system of  claim 31 , wherein the authorization is transmitted to the merchant system. 
     
     
         33 . The system of  claim 31 , wherein the token serves as a limited-use credit card number. 
     
     
         34 . The system of  claim 31 , wherein the token is provided to the customer mobile device in real-time by a real-time data application programming interface for use with the transaction. 
     
     
         35 . The system of  claim 31 , wherein the customer mobile device enables an NFC emulation mode by a card emulation application programming interface. 
     
     
         36 . The system of  claim 31 , wherein the token is formattable by the merchant system into a track of data utilized directly by the authorization network. 
     
     
         37 . The system of  claim 31 , wherein the token is further received through an NFC data exchange format application programming interface configured for reading and writing. 
     
     
         38 . The system of  claim 31 , wherein the one or more parameter requirements enables a previous token to be used for a defined period of time to enable a transaction when the customer mobile device lacks a connection to the communication network. 
     
     
         39 . The system of  claim 31 , wherein the received token is transmitted in response to a receiving personal identification number provided by the customer via the customer mobile device. 
     
     
         40 . The system of  claim 31 , wherein the token manager receives an identifier associated with the customer mobile device from the customer mobile device, and the processor utilizes the identifier in the authorization determination.