Remote emv payment applications

Abstract

Systems and methods for transactions using remote EMV payment applications are disclosed. The system may enable EMV transactions to be completed using EMV payment applications stored in a remote server. The remote EMV payment application may directly communicate EMV transaction data to the issuer system to complete transactions. The system may receive a transaction request comprising a payment token and an EMV payment application uniform resource identifier (“URI”). The system may invoke from a payment application server a remote EMV payment application based on the EMV payment application URI, wherein in response to being invoked, the remote EMV payment application is configured to interact with a merchant system kernel to process the transaction request, and wherein in response to processing the transaction request the remote EMV payment application is configured to transmit a transaction authorization request comprising EMV transaction data directly to the issuer system.

1 . A method of facilitating a transaction between a mobile device and a processor, comprising:
 receiving, by the processor, a transaction request comprising a payment token and an EMV (“EUROPAY®, MASTERCARD®, and VISA®”) payment application uniform resource identifier (“URI”) from the mobile device, the EMV payment application URI comprising a string of characters identifying a storage location of a remote EMV payment application on a payment application server, and wherein the transaction request is initiated by a user input on, a merchant application;   invoking, by the processor in electronic communication with a payment application server, a remote EMV payment application based on the EMV payment application URI, the EMV payment application URI obtained from the mobile device, by sending the payment token and the EMV payment application URI to the payment application server;   receiving, by the processor, a transaction data request for additional information to authorize the transaction request, in response to a determination by the remote EMV payment application that additional information is required to authorize the transaction request;   transmitting, by the processor, a transaction data request to the mobile device, including a request for additional information;   obtaining, by the processor, a transaction data response from the mobile device; sand   receiving, by the processor, a transaction authorization notice from an issuer system, wherein the transaction authorization notice is based on the transaction authorization request generated by the remote EMV payment application.   
     
     
         2 . The method of  claim 1 , wherein the remote EMV payment application is configured to establish a cryptographically protected channel with a merchant system kernel to process the transaction request. 
     
     
         3 . The method of  claim 1 , wherein the merchant application is executed by a user device and the transaction request is transmitted to the processor from the user device. 
     
     
         4 . The method of  claim 1 , wherein the remote EMV payment application is configured to communicate with an issuer system to process, the transaction. 
     
     
         5 . The method of  claim 1 , wherein the additional information required to authorize the transaction request comprises an indication of a biometric authentication of a user. 
     
     
         6 . The method of  claim 1 , further comprising transmitting, by the processor in electronic communication with a payment network, a transaction authorization request comprising the payment token, wherein in response to receiving the transaction authorization request the payment network is configured to at least one of authorize or settle the transaction. 
     
     
         7 . The method of  claim 1 , wherein the remote EMV payment application is configured to process the transaction request by generating a payment cryptogram transmitted to the issuer system to authorize the transaction request. 
     
     
         8 . A system comprising:
 a computing device comprising a processor and a memory; and   instructions stored on the memory that, in response to execution by the processor, cause the computing device to at least:
 receive a transaction request comprising a payment token and an EMV (“EUROPAY®, MASTERCARD®, and VISA®”) payment application uniform resource identifier (“URI”), the EMV payment application URI comprising a string of characters identifying a storage location of a remote EMV payment application, and wherein the transaction request is initiated by a user input on a merchant application; 
 invoke a remote EMV payment application based on the EMV payment application URI, the EMV payment application URI obtained from a mobile device, by sending the payment token and the EMV payment application URI to a payment application server; 
 receive a transaction data request for additional information to authorize the transaction request, in response to, a determination by the remote EMV payment application that additional information is required to authorize the transaction request 
 transmit a transaction data request to the mobile device, including a request for additional information; 
 obtain a transaction data response from the mobile device; and 
 receive a transaction authorization notice from an issuer system, wherein the transaction authorization notice is based on the transaction authorization request generated by the remote EMV payment application. 
   
     
     
         9 . The system of  claim 8 , wherein the remote EMV payment application is configured to establish a cryptographically protected channel with a kernel to process the transaction request. 
     
     
         10 . The system of  claim 8 , wherein the merchant application is executed by a user device and the transaction request is transmitted to the processor from the user device. 
     
     
         11 . The system of  claim 8 , wherein the remote EMV payment application is configured to communicate with an issuer system to process the transaction. 
     
     
         12 . The system of  claim 8 , wherein the additional information required to authorize the transaction request comprises an indication of a biometric authentication of a user. 
     
     
         13 . The system of  claim 8 , wherein the instructions, when executed by the processor, further cause the computing device to transmit a transaction authorization request comprising the payment token, wherein in response to receiving the transaction authorization request a payment network is configured to at least one of authorize or settle the transaction. 
     
     
         14 . The system of  claim 8 , wherein the remote EMV payment application is configured to process the transaction request by generating a payment cryptogram transmitted to the issuer system to authorize the transaction request. 
     
     
         15 . A non-transitory computer-readable medium comprising instructions that, when executed by a processor of a computing device, cause the computing device to at least:
 receive a transaction request comprising a payment token and an EMV (“EUROPAY®, MASTERCARD®, and VISA®”) payment application uniform resource identifier (“URI”) from a mobile device, the EMV payment application URI comprising a string of characters identifying a storage location of a remote EMV payment application on a payment application server, and wherein the transaction request is initiated by a user input on a merchant application;   invoke a remote EMV payment application based on the EMV payment application URI, the EMV payment application URI obtained from the mobile device, by sending the payment token and the EMV payment application URI to the payment application server;   obtain a transaction data request for additional information to authorize the transaction request, in response to a determination by the remote EMV payment application that additional information is required to authorize the transaction request;   transmit a transaction data request to the mobile device, including a request for additional information;   obtain a transaction data response from the mobile device; and   receive a transaction authorization notice from an issuer system, wherein the transaction authorization notice is based on the transaction authorization request generated by the remote EMV payment application.   
     
     
         16 . The non-transitory computer-readable medium of  claim 15 , wherein the remote EMV payment application s configured to establish a cryptographically protected channel with a merchant system kernel to process the transaction request. 
     
     
         17 . The non-transitory computer-readable medium of  claim 15 , wherein the merchant application is executed by a user device and the transaction request is transmitted to the processor from the user device. 
     
     
         18 . The non-transitory computer-readable medium of  claim 15 , wherein the remote EMV payment application is configured to communicate with an issuer system to process the transaction. 
     
     
         19 . The non-transitory computer-readable medium of  claim 15 , wherein the additional information required to authorize the transaction request comprises an indication of a biometric authentication of a user. 
     
     
         20 . The non-transitory computer-readable medium of  claim 15 , wherein the remote EMV payment application s configured to process the transaction request by generating a payment cryptogram transmitted to the issuer system to authorize the transaction request.