Remote EMV payment application

Abstract

A system and method for conducting transactions using a remote EMV payment application is disclosed. The system can complete an EMV transaction using an EMV payment application stored in a remote server. The remote EMV payment application can transmit EMV transaction data directly to an issuer system to complete the transaction. The system can receive a transaction request including a payment token and an EMV payment application uniform resource identifier ("URI"). The system can invoke the remote EMV payment application from a payment application server based on the EMV payment application URI, wherein the remote EMV payment application is configured to interact with a merchant system kernel in response to being invoked to process the transaction request, and wherein the remote EMV payment application is configured to transmit a transaction authorization request including the EMV transaction data directly to the issuer system in response to processing the transaction request.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. application serial number 16 / 033,845, filed on July 12, 2018, entitled “REMOTE EMV PAYMENT APPLICATIONS,” which is hereby incorporated by reference in its entirety for all purposes. Technical Field

[0003] The present disclosure relates generally to financial transactions, and more particularly, to a transaction system using a remote EMV payment application. Background Art

[0004] Today, in various situations, credit cards, charge cards, debit cards, and other transaction instruments are generally accepted as a way to make payments to merchants. Payments can be made using the EMV protocol designed to authenticate chip card transactions. For example, an EMV-compliant transaction instrument may include an embedded microprocessor chip configured to store and protect cardholder data using a dynamic authentication function. The embedded microprocessor chip may include a payment application configured to interact with a merchant kernel to exchange data and authorize transactions. At least in part because the payment application is stored in the embedded microprocessor chip of the EMV transaction instrument, the communication protocol between the transaction instrument, the merchant system, and / or the back-end issuer system may be limited. Summary of the invention

[0005] Systems, methods, and articles of manufacture (collectively, "systems") for remote EMV payment applications are disclosed. The system may receive a transaction request, the transaction request including a payment token and an EMV payment application uniform resource identifier ("URI"). The system may invoke a remote EMV payment application from a payment application server based on the EMV payment application URI, wherein the remote EMV payment application is configured to interact with a merchant system kernel to process the transaction request in response to being invoked, wherein the remote EMV payment application is configured to transmit a transaction authorization request containing EMV transaction data directly to an issuer system in response to processing the transaction request. The system may receive a transaction authorization notification from the issuer system, wherein the transaction authorization notification is based on the transaction authorization request generated by the remote EMV payment application.

[0006] In various embodiments, the transaction request may be generated by the merchant application in response to a user device initiating a transaction on the merchant application. The transaction request may also be generated by the merchant point of sale ("PoS") in response to a payment instrument interfacing with the merchant PoS. The payment instrument may include a local EMV payment application, and the merchant PoS may include a merchant PoS kernel. The local EMV payment application is configured to interact with the merchant PoS kernel to initiate the transaction.

[0007] In various embodiments, the system may also transmit a transaction data request (e.g., for a user signature, PIN entry, biometric entry, etc.) in response to the remote EMV payment application determining that additional data is needed to authorize the transaction request. The system may also transmit a transaction authorization request including a payment token to a payment network, wherein the payment network is configured to authorize and / or settle the transaction in response to receiving the transaction authorization request. The remote EMV payment application is configured to process the transaction request by generating a payment cryptogram to be transmitted to the issuer system to authorize the transaction request.

[0008] In various embodiments, the system may receive a transaction request that includes a payment token and an EMV payment application uniform resource identifier (“UR1”). The system may call a remote EMV payment application from a payment application server based on the EMV payment application UR1, wherein the remote EMV payment application is configured to interact with a merchant system kernel in response to being called to process the transaction request. The remote EMV payment application may be configured to transmit EMV transaction data including the payment token to an issuer system in response to processing the transaction request. The system may transmit a transaction authorization request to the issuer system. The issuer system may be configured to combine the EMV transaction data and the transaction authorization request to authorize the transaction. The system may receive a transaction authorization notification based on the interaction of the remote EMV payment application with the merchant system kernel.

[0009] Unless otherwise explicitly stated herein, the above features and elements may be used in various combinations without being exclusive. These features and elements and the operation of the disclosed embodiments will become more apparent from the following description and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The subject matter of the present disclosure is particularly pointed out and distinctly claimed in the concluding portion of the specification. However, a more complete understanding of the disclosure may be gained by reference to the detailed description and claims when considered in conjunction with the accompanying drawings, in which like reference numerals represent like elements.

[0011] Figure 1 is a block diagram illustrating various system components of a system for a remote EMV payment application to complete a transaction from a user device according to various embodiments;

[0012] Figure 2 is a block diagram illustrating various system components of a system for a remote EMV payment application to complete a transaction from a payment instrument according to various embodiments;

[0013] Figure 3 A process flow illustrating a method for conducting an EMV transaction using a remote EMV payment application according to various embodiments;

[0014] Figure 4 A process flow illustrating a method for initiating an EMV transaction using a user device according to various embodiments; and

[0015] Figure 5 A process flow of a method for initiating an EMV transaction using a payment instrument according to various embodiments is shown. DETAILED DESCRIPTION

[0016] Exemplary embodiments are described in detail herein with reference to the accompanying drawings, which illustrate various embodiments by way of illustration. Although these different embodiments are described in sufficient detail to enable those skilled in the art to practice the present disclosure, it should be understood that other embodiments may be implemented and logical and mechanical changes may be made without departing from the spirit and scope of the present disclosure. Therefore, the detailed description herein is for illustration only and not for limitation. For example, the steps set forth in any method or process description may be performed in any order, without being limited to the order described. In addition, any function or step may be outsourced to or performed by one or more third parties. In addition, any function or step may be outsourced to or performed by one or more third parties. The systems, devices, and methods described herein may be modified, added, or omitted without departing from the scope of the present disclosure. For example, the components of the systems and devices may be integrated or separated. In addition, the operations of the systems and devices disclosed herein may be performed by more components, fewer components, or other components, and the methods described may include more steps, fewer steps, or other steps. In addition, the steps may be performed in any suitable order. As used in this document, "each" refers to each member of a set or each member of a subset of a set. Furthermore, any reference to the singular includes plural embodiments and any reference to more than one component may include singular embodiments.Although specific advantages have been enumerated herein, various embodiments may include some, all, or none of the enumerated advantages.

[0017] In various embodiments, systems, methods, and articles of manufacture (collectively, "systems") are disclosed for transactions using remote EMV payment applications. and Compared to a system for conducting EMV transactions using an EMV payment application stored in a server (e.g., a remote server, a cloud-based server, etc.), the system disclosed herein is capable of completing EMV transactions using an EMV payment application stored in a server (e.g., a remote server, a cloud-based server, etc.). In this regard, the system may allow for the use of practical EMV capabilities in different communication protocols including TCP / IP. For example, TCP / IP communications may be conducted between a kernel (e.g., payment software) in a merchant system and a payment application in an issuer server. Thus, by executing a payment application in a remote server, the system may provide a similar level of security found in EMV chip card transactions (e.g., cryptographic verification using cryptographic generated by the payment application and verified by the issuer system) with increased speed and improved efficiency. In addition, the system may also process transactions from a variety of technologies and sources, such as, for example, from in-store payments (e.g., using a contact interface, a contactless interface, a wireless connection, a Bluetooth connection, etc.), remote payments, or payments using mobile devices, credit cards, debit cards, transaction instruments, Internet of Things (IoT) devices, etc.

[0018] The system further improves the functionality of computers and payment networks. For example, by placing the EMV payment application in a server (e.g., payment application server 120) rather than in a microchip on a physical payment instrument (e.g., a credit card, debit card, etc.), the speed and efficiency of processing EMV payment transactions can be increased compared to typical EMV payment transactions. In a typical embedded microchip, the payment application may be limited by low hardware resources (e.g., RAM memory and CPU), while by placing the payment application in a server where more resources may be available, the payment application can be made to perform more complex tasks and operations, thereby allowing complex features such as credit and reward points to be integrated into the payment application. In addition, considering that the physical payment instrument is usually valid for five years, the payment application stored in the embedded microchip may become outdated in terms of payment features and functions, security features and algorithms. In contrast, the payment application stored in the server can be updated frequently as needed without being controlled by the validity period and reissue of the physical payment instrument.

[0019] In various embodiments, a system 100 for a remote EMV payment application is disclosed. The system 100 may include one or more of a user device 105, a merchant checkout system 110, a payment application server 120, and / or an issuer system 130. As further discussed herein, the various components of the system 100 may be interconnected via a network 101 and / or a payment network 107. The system 100 may also contemplate uses associated with network services, utility computing, pervasive and personalized computing, security and identity solutions, autonomous computing, cloud computing, commodity computing, mobile and wireless solutions, open source, biometrics, grid computing, and / or meshed computing.

[0020] In various embodiments, as further discussed herein, the user device 105 may be configured to initiate transactions with the merchant checkout system 110 via the merchant application 115. For example, a transaction account user, holder, beneficiary, etc. (collectively, a "User") may wish to purchase tangible goods or digital goods, services, etc. by browsing the merchant application 115. As further discussed herein, the User may interact with the merchant application 115 via the user device 105 to initiate, authorize, and complete one or more transactions. The user device 105 may include any suitable hardware, software, and / or database components capable of sending, receiving, and storing data. For example, the user device 105 may include a personal computer, a personal digital assistant, a cellular telephone, a smartphone (e.g., etc.), Internet of Things (IoT) devices, self-service terminals, etc. The user device 105 may include an operating system such as, for example, Mobile operating systems, operating system, The user device 105 may include a software component that is installed on the user device 105 and configured to allow the user to access the merchant application 115 through the user device 105. For example, the user device 105 may include a web browser (e.g., MICROSOFT INTERNET GOOGLE etc.), applications, micro-applications or mobile applications, etc.

[0021] The user device 105 may be in electronic and / or operative communication with a merchant application 115. The merchant application 115 may include software, mobile applications, web interfaces, etc. accessible from the user device 105. The merchant application 115 may allow a user to interact with one or more merchants through the user device 105 to browse and purchase tangible goods, digital goods, services, etc. from one or more merchants. In various embodiments, the merchant application 115 may be in electronic and / or operative communication with a merchant checkout system 110 through the network 101. In various embodiments, the merchant application 115 may be hosted on the merchant checkout system 110 and accessible through the user device 105. In this regard, the user device 105 may also be in electronic communication with the merchant checkout system 110 through the network 101. According to various embodiments, the user device 105 and / or the merchant application 115 may be configured to communicate with the merchant checkout system 110 through the user device 105 using TCP / IP, Bluetooth, and / or any other suitable communication protocol.

[0022] In various embodiments, the user device 105 may also be authenticated by the payment application server 120 before completing a transaction in the system 100. For example, the user device 105 may be authenticated using a one-time password, multi-factor authentication, and / or using any other suitable type of authentication.

[0023] Network 101 may include any suitable type of network capable of communicating between one or more of user device 105, merchant application 115, merchant checkout system 110, and / or payment application server 120. As used herein, the term "network" may include any cloud, cloud computing system, or electronic communication system or method incorporating hardware and / or software components. Communications between the parties may be accomplished via any suitable communication channel, such as, for example, a telephone network, an extranet, an intranet, the Internet, a point of interaction device (point of sale device), a personal digital assistant (e.g., ), cellular phones, self-service terminals, etc.), online communications, satellite communications, offline communications, wireless communications, transponder communications, local area networks (LANs), wide area networks (WANs), virtual private networks (VPNs), networking devices or linking devices, keyboards, mice, and / or any suitable communication or data input modality. In addition, although the system is frequently described herein as being implemented using the TCP / IP communication protocol, the system may also use IPX, IP-6, The network may be implemented using OSI, any tunneling protocol (e.g., IPsec, SSH, etc.), or any number of existing or future protocols. If the network is of a public network nature, such as the Internet, it may be advantageous to assume that the network is insecure and vulnerable to eavesdroppers. Those skilled in the art are generally aware of the specific information related to the protocols, standards, and application software used in conjunction with the Internet, and therefore, this article does not need to elaborate on this specific information.

[0024] The various system components may be coupled to the network independently, individually or collectively as appropriate via data links, including, for example, a connection to an Internet Service Provider (ISP) via a local loop, such as typically with a standard modem, cable modem, Dish ISDN, digital subscriber line (DSL) or various wireless communication methods are used in combination. It is noted that the network can be implemented as other types of networks, such as interactive television (ITV) networks. In addition, the system contemplates the use, sale or distribution of any goods, services or information through any network with similar functions as described herein.

[0025] "Cloud" or "cloud computing" includes a model for convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be quickly provisioned and released with minimal management effort or service provider interaction. Cloud computing can include location-independent computing, whereby shared servers provide resources, software, and data to computers and other devices on demand. For more information on cloud computing, see the National Institute of Standards and Technology (NIST) definition of cloud computing.

[0026] In various embodiments, the merchant checkout system 110 may be configured to conduct transactions with users through the merchant application 115. The merchant checkout system 110 may include any suitable combination of hardware, software, and / or database components. For example, the merchant checkout system 110 may include one or more network environments, servers, computer-based systems, processors, databases, etc. In various embodiments, the merchant checkout system 110 may be computer-based and may include a processor, a tangible non-transitory computer-readable memory and / or a network interface, and other suitable system software and hardware components. As described herein, the instructions stored on the tangible non-transitory memory may enable the merchant checkout system 110 to perform various functions. In various embodiments, the merchant checkout system 110 may communicate electronically and / or logically with the user device 105, the merchant application 115, and / or the payment application server 120 through the network 101. According to various embodiments, the merchant checkout system 110 may be configured to communicate with the user device 105, the merchant application 115, and / or the payment application server 120 using TCP / IP, Bluetooth, and / or any other suitable communication protocol. Merchant checkout system 110 may also be in electronic communication with payment network 107 and / or issuer system 130 .

[0027] In various embodiments, the merchant checkout system 110 may include various components configured to facilitate transactions with users. For example, the merchant checkout system 110 may include any suitable number of back-end systems to provide item inventory, transaction processing, item shipping and / or delivery, etc. In various embodiments, the merchant checkout system 110 may include a merchant system kernel 117. The merchant system kernel 117 may include any combination of hardware and / or software. For example, the merchant system kernel 117 may include an EMV kernel. The merchant system kernel 117 may include a function set that provides processing logic and data required to perform EMV transactions. In this regard, as further discussed herein, the merchant system kernel 117 may be configured to interact with the EMV payment application 125 during a transaction. The merchant system kernel 117 may be called by the merchant checkout system 110 in response to the merchant checkout system 110 receiving a transaction request. The merchant system kernel 117 may be configured to perform data exchange (e.g., to complete a transaction) with the EMV payment application 125 through the payment application server 120. In this regard, according to various embodiments, one instance of the merchant system kernel 117 may be launched for each transaction completed in the system 100 .

[0028] In various embodiments, the payment application server 120 can be configured to store, maintain and execute one or more EMV payment applications 125. The payment application server 120 may include one or more of hardware, software and / or database components. For example, the payment application server 120 may include one or more network environments, servers, computer-based systems, processors, databases, etc. In various embodiments, the payment application server 120 may be computer-based and may include a processor, a tangible non-transitory computer-readable memory and / or a network interface, and other suitable system software and hardware components. As described herein, instructions stored on the tangible non-transitory memory may enable the payment application server 120 to perform various functions. The payment application server 120 may communicate electronically and / or logically with the user device 105, the issuer system 130 and / or the merchant checkout system 110 through the network 101.

[0029] In various embodiments, each EMV payment application 125 may include a software application configured to process, authorize and / or complete transaction requests. Each EMV payment application 125 may be configured to interact with the merchant system kernel 117 to process, authorize and / or complete transaction requests. For example, the EMV payment application 125 may be configured to use asymmetric ciphertext and / or symmetric ciphertext to establish a ciphertext-protected secure channel with the merchant system kernel 117 and / or authenticate the merchant system kernel 117. The EMV payment application 125 may also be configured to perform cardholder verification, process transaction restrictions, perform merchant risk analysis and management, perform card action analysis (e.g., first card action analysis, second card action analysis, etc.), process transaction requests, complete transaction requests, etc. In various embodiments, each EMV payment application 125 is for the issuing institution (e.g., AMERICAN EMV payment application 125 may be specific. In this regard, the EMV payment application 125 invoked during a transaction may be based on the issuing institution of the transaction account used in the transaction. For example, each EMV payment application 125 may correspond to a unique resource identifier (URI) that serves as a unique identifier for each EMV payment application 125. In various embodiments, any portion of the EMV payment application 125 discussed herein may be remote and still operate similarly as disclosed herein. Therefore, some portions of the EMV payment application 125 may still be stored locally in the microchip of the transaction instrument.

[0030] In various embodiments, as further discussed herein, the EMV payment application 125 can communicate directly with the issuer system 130. For example, the EMV payment application 125 can be configured to transmit a transaction authorization request containing EMV transaction data directly to the issuer system 130. As further discussed herein, the EMV payment application 125 can also be configured to generate cryptograms (e.g., payment cryptograms) and transmit the cryptograms directly to the issuer system 130. In this regard, in contrast to typical payment applications embedded in physical payment instruments, the EMV payment application 125 can transmit the EMV transaction data required to complete and authorize a transaction directly to the issuer system 130.

[0031] In various embodiments, the payment network 107 may include or interact with a traditional account payment network to facilitate purchases and payments, authorize transactions, and / or settle transactions. The payment network 107 may include any suitable network capable of communicating between the merchant checkout system 110 and the issuer system 130. For example, the payment network 107 may represent an existing proprietary network that currently accommodates transactions for credit cards, debit cards, and / or other types of transaction accounts or transaction instruments. The payment network 107 may be a closed network that is protected from eavesdroppers. In various embodiments, the payment network 107 may include a network such as the AMERICAN Cartes Bancaires, etc., exemplary transaction networks, private networks (e.g., department store networks), and / or any other payment networks.

[0032] In various embodiments, the issuer system 130 may be configured as a central hub for accessing the various systems, engines, and components of the payment network 107. For example, the issuer system 130 may include a sub-network, a computer-based system, a software component, etc. configured to provide access points to the various systems, engines, and components in the payment network 107. In various embodiments, as further discussed herein, the issuer system 130 may also include a credit authorization system (“CAS”) of a transaction account issuer capable of authorizing transactions. The issuer system 130 may be in operable communication and / or electronic communication with the payment application server 120 and / or the payment network 107. The issuer system 130 may include one or more network environments, servers, computer-based systems, processors, databases, etc. In various embodiments, the issuer system 130 may be computer-based and may include a processor, a tangible non-transitory computer-readable memory and / or a network interface, as well as other suitable system software and hardware components. As described herein, instructions stored on the tangible non-transitory memory may enable the issuer system 130 to perform various functions.

[0033] In various embodiments, the issuer system 130 may include systems and databases related to financial and / or transaction systems and processes, such as, for example, one or more authorization engines, authentication engines and databases, settlement engines and databases, accounts receivable systems and databases, accounts payable systems and databases, etc. For example, the issuer system 130 may be configured to authorize and settle payment transactions; maintain transaction account member databases, accounts receivable databases, accounts payable databases, etc.

[0034] In various embodiments, and with reference to Figure 2 , discloses a system 200 for a remote EMV payment application to authorize a transaction from a payment instrument. Figure 1 , system 200 can be similar to system 100. System 200 can include a payment instrument 240 and / or a merchant point of sale 250.

[0035] In various embodiments, the payment instrument 240 may include any suitable transaction instrument capable of initiating a transaction using a contact interface (e.g., swiping a card, inserting an EMV chip card, etc.) and / or a contactless interface (e.g., NFC-enabled payment, etc.). For example, the payment instrument 240 may include a credit card, a debit card, a multi-transaction account card, a user device, an Internet of Things (IoT) device, etc. The payment instrument 240 may include multiple linked transaction accounts. For more information about payment instruments with multiple linked transaction accounts, see U.S. application No. 15 / 646,928, entitled FUND TRANSFER SERVICE FOR MULTIPLELINKED TRANSACTION ACOUNTS, filed on July 11, 2017, the contents of which are incorporated herein by reference in their entirety.

[0036] The payment instrument 240 may include one or more local EMV payment applications 245 corresponding to each transaction account linked to the payment instrument 240. The local EMV payment application 245 may include a software application and may be similar to the (remote) EMV payment application 125. Each local EMV payment application 245 may be configured to select the (remote) EMV payment application 125 required to complete the transaction based on the transaction account selected for the transaction. For example, and as further discussed herein, the local EMV payment application 245 may be configured to interact with the merchant PoS kernel 257 to process data, prompt the user to select a transaction account for the transaction, determine the (remote) EMV payment application 125 to be selected based on the transaction account, generate a transaction request, etc., the transaction request containing at least a payment token and an EMV payment application URI corresponding to the selected (remote) EMV payment application 125.

[0037] In various embodiments, the merchant point of sale (PoS) 250 may include a PoS terminal configured as an institution for conducting transactions. For example, the merchant PoS 250 may include a cash register, a credit card reader and / or a debit card reader, an EMV card reader, etc. The merchant PoS 250 may also include a near field communication (NFC) terminal. In this regard, the NFC terminal may allow information (e.g., payment information, etc.) to be transferred from an NFC-enabled user device, such as, for example, a mobile device, a transaction tool that supports NFC payment, a watch, etc. As further discussed herein, in response to a user initiating a transaction with the merchant PoS 250, a transaction authorization request may be generated. The merchant PoS 250 may communicate electronically and / or logically with the merchant checkout system 110 via the network 101.

[0038] In various embodiments, the merchant PoS 250 may include a merchant PoS kernel 257. The merchant PoS kernel 257 may be similar to the merchant system kernel 117. The merchant PoS kernel 257 may include any combination of hardware and / or software. For example, the merchant PoS kernel 257 may include an EMV kernel. The merchant PoS kernel 257 may include a functional set of processing logic and data required to conduct an EMV transaction. For example, and as further discussed herein, the merchant PoS kernel 257 may be configured to interact with the local EMV payment application 245 to process data, prompt the user to select a transaction account for the transaction, determine the (remote) EMV payment application 125 to be selected based on the transaction account, generate a transaction request, etc., the transaction request at least includes a payment token and an EMV payment application URI corresponding to the selected (remote) EMV payment application 125.

[0039] Reference now Figure 3-Figure 5The process flows and screen shots described are merely examples and are not intended to limit the scope of the present disclosure. For example, the steps detailed in any method or process description may be performed in any order and are not limited to the order presented. It is understood that the following description not only appropriately refers to Figure 3-Figure 5 The steps and elements described in the Figure 1 and Figure 2 Various system elements described herein. It should be understood that although exemplary embodiments are shown in the figures and described herein, the principles of the present disclosure can be implemented using any number of techniques, whether currently known or unknown. The present disclosure should in no way be limited to the exemplary embodiments and techniques shown in the figures and described below. Unless otherwise specifically stated, the items depicted in the figures are not necessarily drawn to scale.

[0040] In various embodiments, and with particular reference to Figure 3 , a method 301 for conducting an EMV transaction using a remote EMV payment application is disclosed. The method 301 can be capable of initiating, authorizing, and completing an EMV transaction using a remote EMV payment application stored in a server (e.g., as compared to an EMV payment application stored locally in a microchip of a transaction instrument). In various embodiments, a merchant checkout system 110 receives a transaction request (step 302). The merchant checkout system 110 can receive the transaction request from a variety of sources, including transactions initiated from a mobile device, an Internet of Things (IoT) device, a transaction instrument (e.g., a credit card, a debit card, etc.), and the like.

[0041] As an example, and with specific reference to Figure 4 and Figure 1, discloses a method 401 for initiating an EMV transaction using a user device according to various embodiments. A user initiates a transaction on a merchant application 115 through a user device 105 (step 402). For example, a user may browse a merchant application 115 through a user device 105 and may want to purchase goods or services. The user may enter data to initiate a transaction, such as purchase options, payment methods, shipping methods, or delivery methods, etc. The merchant application 115 generates a transaction request based on the user input (step 404). The transaction request may include any suitable data related to the transaction, such as, for example, a payment token, a payment amount, a merchant ID, etc. The payment token may include user identification data such as a transaction account number. The transaction request may include additional transaction identification information, which may be a standardized code or number representing transaction characteristics, such as, for example, a merchant category code, a service organization number, a geographic location code, a product code, etc. In various embodiments, the transaction request may also include an EMV payment application uniform resource identifier (URI). The EMV payment application URI may include a unique identifier corresponding to one or more EMV payment applications 125 stored in a payment application server 120. For example, the EMV payment application URI may include a string that identifies the storage location of the corresponding EMV payment application 125 in the payment application server 120. The merchant application 115 transmits the transaction request to the merchant checkout system 110 via the network 101 (step 406). In various embodiments, the merchant application 115 may be configured to transmit the transaction request using any suitable communication protocol, such as, for example, TCP / IP, Bluetooth, etc. In this regard, the method 401 may transmit transaction data without using the ISO / IEC 7816 and / or ISO / IEC 14443 communication protocols that are typically required in EMV transactions.

[0042] As another example, and with specific reference to Figure 5 and Figure 2, a method 501 for initiating an EMV transaction using a payment instrument according to various embodiments is disclosed. A payment instrument 240 is docked with a merchant point of sale ("PoS") 250 (step 502). For example, a user may wish to purchase goods or services from a merchant at the merchant PoS 250. The user may initiate a transaction using the payment instrument 240 by swiping the payment instrument 240 or inserting the payment instrument 240 into the merchant PoS 250 (e.g., contact transaction), using a contactless interface (e.g., NFC, etc.), etc. The merchant PoS 250 determines whether the payment instrument 240 includes a local EMV payment application 245 (step 504). For example, and according to various embodiments, the payment instrument 240 may include a plurality of linked transaction accounts. The payment instrument 240 may include a local EMV payment application 245 configured to select at least one of the plurality of linked transaction accounts during a transaction.

[0043] The merchant PoS 250 calls the local EMV payment application 245 (step 506). For example, in response to the payment instrument 240 docking with the merchant PoS 250, the local EMV payment application 245 interacts with the merchant PoS kernel 257 (step 508). The local EMV payment application 245 and the merchant PoS kernel 257 can determine one or more payment applications (corresponding to one or more transaction accounts linked to the payment instrument 240) that are supported by both the local EMV payment application 245 and the merchant PoS kernel 257. Based on the called local EMV payment application 245, the merchant PoS 250 can prompt the user to select a transaction account on the payment instrument 240 that the user wishes to use to complete the transaction. The user can interact with the merchant PoS 250 to select a transaction account.

[0044] The merchant PoS 250 generates a transaction request based on the interaction of the local EMV payment application 245 with the merchant PoS kernel 257 (step 510). The transaction request may include any suitable data related to the transaction, such as, for example, a payment token, a payment amount, a merchant ID, etc. The payment token may include user identification data such as a transaction account number. The transaction request may include additional transaction identification information, which may be a standardized code or number representing transaction characteristics, such as, for example, a merchant category code, a service organization number, a geographic location code, a product code, a PoS terminal number, etc. In various embodiments, the transaction request may also include an EMV payment application uniform resource identifier (URI). The EMV payment application URI may include a unique identifier corresponding to one or more EMV payment applications 125 stored in the payment application server 120. For example, the EMV payment application URI may include a string identifying the storage location of the corresponding EMV payment application 125 in the payment application server 120. The merchant PoS 250 transmits the transaction request to the merchant checkout system 110 via the network 101 (step 512). In various embodiments, the merchant PoS 250 may be configured to transmit the transaction request using any suitable communication protocol, such as, for example, TCP / IP, Bluetooth, etc.

[0045] Reference again Figure 3 In response to receiving a transaction request (e.g., from step 406, briefly referenced Figure 4 , or from step 512, briefly refer to Figure 5), the merchant checkout system 110 initiates communication with the payment application server 120 via the network 101 (step 304). For example, the merchant checkout system 110 may establish and initiate communication with the payment application server 120 by transmitting the payment token and the EMV payment application URI to the payment application server 120. The payment application server 120 invokes the EMV payment application 125 based on the EMV payment application URI (step 306). The EMV payment application 125 interacts with the merchant system kernel 117 (step 308) to begin processing the transaction request. The EMV payment application 125 may be configured to establish a ciphertext-protected secure channel with the merchant system kernel 117 and / or authenticate the merchant system kernel 117 using asymmetric ciphertext and / or symmetric ciphertext. For example, and in accordance with various embodiments, in an EMV first generation transaction, the EMV payment application 125 may be configured to perform data authentication of the transaction request. The EMV payment application 125 may also be configured to perform cardholder authentication, process transaction or account restrictions, perform merchant risk analysis and management, perform card action analysis (e.g., first card action analysis, second card action analysis, etc.), process transaction requests (online), complete transaction requests, etc. In various embodiments, the EMV payment application 125 may also be configured to generate EMV data, such as, for example, ciphertext, which may be transmitted to the issuer system 130 and verified by the issuer system 130 to authorize the transaction request.

[0046] In various embodiments, the merchant checkout system 110 transmits a transaction data request (step 310). For example, in response to the EMV payment application 125 determining that additional information is needed to authorize the transaction request, the EMV payment application 125 (and / or the merchant system kernel 117) can generate a transaction data request and instruct the merchant checkout system 110 to transmit the transaction data request. Figure 1 , and according to various embodiments, the merchant checkout system 110 can transmit the transaction data request to the merchant application 115. Figure 2 , and according to various embodiments, the merchant checkout system 110 may transmit the transaction data request to the merchant PoS 250. The transaction data request may include data requesting additional user input, such as, for example, biometric input, user PIN, user signature, etc. In response to receiving the transaction data response, the merchant checkout system 110 (briefly referred to as Figure 1 ) or Merchant PoS 250 (Brief Reference Figure 2 ) can transmit the transaction data response to the merchant checkout system 110 via the network 101.

[0047] In various embodiments, the payment application server 120 transmits a transaction authorization request to the issuer system 130 (step 312). The transaction authorization request may include a payment token and / or any other payment information. In various embodiments, the transaction authorization request may also include a ciphertext and other transaction data generated by the EMV payment application 125. At this point, the payment application server 120 transmits the EMV transaction data required to complete the transaction directly to the issuer system 130 (compared to a typical payment system that embeds the payment application into a physical transaction instrument). The issuer system 130 and / or the payment network 107 may be configured to authorize, verify and / or settle the transaction based on the transaction authorization request. For example, the issuer system 130 may query an account member database and may compare the CSV / CVV code, ARQC, account holder identification information, etc. with the values ​​contained in the transaction authorization request. As another example, the issuer system 130 may be configured to verify the ciphertext generated by the EMV payment application 125. The issuer system 130 may also update the accounts receivable database and the settlement database to reflect the transaction. In response to authorizing, authenticating and / or settling the transaction authorization request, issuer system 130 may transmit a transaction authorization response to payment application server 120 and / or merchant checkout system 110. The transaction authorization response may include data indicating whether the transaction was successfully authorized, authenticated and / or settled.

[0048] The EMV payment application 125 completes the processing of the transaction request with the merchant system kernel 117 (step 314). The merchant checkout system 110 transmits a transaction authorization notification (step 316). For example, the merchant checkout system 110 may transmit the transaction authorization notification to the merchant application 115 (see briefly Figure 1 ) or Merchant PoS 250 (Brief Reference Figure 2 ). The transaction authorization notification may include data indicating whether the transaction request is successfully authorized, whether the funds are successfully transferred, etc.

[0049] Systems, methods, and computer program products are provided. In the detailed description herein, references to "various embodiments," "one embodiment," "an embodiment," "an example embodiment," etc. indicate that the described embodiments may include a particular feature, structure, or characteristic, but each embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, these phrases do not necessarily refer to the same embodiment. In addition, when describing a particular feature, structure, or characteristic associated with one embodiment, it should be considered that whether or not explicitly described, the feature, structure, or characteristic that affects other embodiments is within the knowledge of those skilled in the art. After reading the specification, it will be apparent to those skilled in the relevant art how to implement the disclosure in the alternative embodiments.

[0050] As used herein, "satisfy," "meet," "match," "associated with," or similar phrases may include identical matches, partial matches, meeting specific criteria, matching data subsets, correlation, meeting specific criteria, correspondence, association, algorithmic relationships, etc. Likewise, "authenticate" or similar terms as used herein may include precise authentication, partial authentication, authentication data subsets, correspondence, meeting specific criteria, association, algorithmic relationships, etc.

[0051] Words and phrases similar to "associated with" and / or "related to" may include marking, identifying, associating with, using a lookup table or any other method or system to indicate or create a relationship between elements, such as, for example, (i) a transaction account and (ii) an item (e.g., an offer, reward points, discount) and / or a digital channel. In addition, the association may occur at any point in response to any suitable action, event, or time period. The association may occur at predetermined time intervals, may occur periodically, may occur randomly, may occur once, may occur more than once, or may occur in response to a suitable request or action. Any information may be distributed and / or accessed via a software-activated link, wherein the link may be sent via email, text, post, social network input, and / or any other method known in the art.

[0052] Phrases and terms similar to "account", "account number", "account code" or "consumer account" as used herein may include any device, code (e.g., one or more of an authorization / access code, a personal identification number ("PIN"), an Internet code, other identification codes, etc.), numbers, letters, symbols, digital certificates, smart chips, digital signals, analog signals, biometrics, or other identifiers / markers appropriately configured to allow a customer to access, interact with, or communicate with a system. An account number may optionally be located on or associated with a reward account, a charge account, a credit account, a debit account, a prepaid account, a phone card, an embossed card, a smart card, a magnetic stripe card, a barcode card, a transponder, a radio frequency card, or an associated account.

[0053] The system may include or interface with any of the above accounts, devices and / or transponders and readers (e.g., RFID readers) that communicate RF with transponders (which may include key fobs) or interface with them, or communication between the initiator and the target achieved by near field communication (NFC). Typical devices may include, for example, key rings, tags, cards, mobile phones, watches, or any such devices that can be presented for querying. In addition, the systems, computing units, or devices discussed herein may include "pervasive computing devices," which may include traditional non-computerized devices embedded with computing units. Examples may include watches, Internet-enabled kitchen appliances, restaurant tables embedded with radio frequency readers, wallets or purses with embedded transponders, and the like. In addition, the device or financial transaction tool may have electronic functions and communication functions, which are enabled, for example, by: electronic circuit networks printed or otherwise incorporated on or within transaction tools (and commonly referred to as "smart cards"); key fobs with transponders and RFID readers; and / or near field communication (NFC) technology. For more information on NFC, see the following specifications, all of which are incorporated herein by reference: ISO / IEC 18092 / ECMA-340, Near Field Communication Interface and Protocol-1 (NFCIP-1), available at http: / / www.emvco.com; ISO / IEC 21481 / ECMA-352, Near Field Communication Interface and Protocol-2 (NFCIP-2); and EMV 4.3 or EMV Generation 2.

[0054] Account numbers may be assigned and stored in any form of plastic, electronic, magnetic, radio frequency, wireless, audio and / or optical device capable of transmitting or downloading data from itself to a second device. Although each credit provider has its own numbering system, such as the American Credit Card Number System, ... The 15-digit numbering system used is a standard 15-digit numbering system, but the customer account number can be, for example, a 16-digit account number. Each company's account number conforms to the company's standardized format, so that companies that use the 15-digit format usually use three sets of numbers spaced apart, represented by the number "0000 000000 00000". The first five to seven digits are reserved for processing and identify the issuing bank, account type, etc. In this example, the last (15th) digit is used as a sum check of the 15 digits. The middle eight to eleven digits are used to uniquely identify the customer. For example, a merchant account number can be any number or alphanumeric character that can identify a specific merchant for account acceptance, account reconciliation, declaration, etc.

[0055] In various embodiments, the account number can identify the customer. In addition, in various embodiments, the customer can be identified by various identifiers, for example, these identifiers include email addresses, phone numbers, cookie ids, radio frequency identifiers (RFID), biometrics, etc.

[0056] Phrases and words similar to "financial institution", "transaction account issuer", "issuer system", etc. may include any entity that provides transaction account services. Although often referred to as a "financial institution", a financial institution may refer to any type of bank, lender, or other type of account issuer, such as a credit card company, card guarantee company, or a third-party issuer that contracts with a financial institution. It should also be noted that other participants (such as an intermediary clearinghouse) may be involved in certain stages of the transaction.

[0057] Phrases and words similar to "business" or "merchant" are used interchangeably and refer to any person, entity, distributor system, software and / or hardware that is a provider, agent and / or any other entity in the distribution chain of goods or services. For example, a merchant can be a grocery store, retail store, travel agency, service provider, online merchant, etc.

[0058] The terms "payment vehicle," "transaction account," "financial transaction instrument," "transaction instrument," and / or plural forms of these terms may be used interchangeably throughout to refer to a financial instrument. Phrases and terms similar to "transaction account" may include any account that can be used to facilitate a financial transaction.

[0059] In various embodiments, the system (e.g., user device 105) can be integrated with one or more intelligent digital assistant technologies. For example, exemplary intelligent digital assistant technologies may include ALEXA system developed by GOOGLE and / or similar digital assistant technology. AMAZON ALEXA, GOOGLE and All of them can provide cloud-based voice services, which can provide assistance in tasks, entertainment, general information, etc. AMAZON ECHO AMAZON and AMAZON TV and all ALEXA equipment can access the ALEXA system. ALEXA, GOOGLE and The system can receive voice commands through its voice activation technology and activate other functions, control smart devices and / or collect information. For example, music, email, text messages, calls, answered questions, home improvement information, smart home communication / activation, games, shopping, making to-do lists, setting alarms, streaming podcasts, playing audiobooks, and providing weather, traffic and other real-time information such as news. ALEXA, GOOGLE and The system may allow a user to access information related to eligible accounts linked to an online account on all ALEXA-enabled devices.

[0060] Phrases such as customer, client, user, account holder, account affiliate, card member, etc. shall include any individual, entity, business, government organization, enterprise, software, hardware, machine associated with a transaction account who uses the account to purchase merchant products offered by one or more merchants and / or is legally designated to perform transactions on the account, whether or not a physical card is associated with the account. For example, card members may include transaction account owners, transaction account users, account affiliates, sub-account users, affiliated account users, account beneficiaries, account custodians, and / or any other individual or entity associated or affiliated with a transaction account.

[0061] Any communication, transmission, and / or channel discussed herein may include any system or method for delivering content (e.g., data, information, metadata, etc.) and / or the content itself. The content may be presented in any form or medium, and in various embodiments, the content may be delivered electronically and / or may be capable of being presented electronically. For example, a channel may include a website or device (e.g., Facebook, ), a uniform resource locator ("URL"), a document (e.g., document, document, pdf documents, etc.), “electronic books,” “electronic magazines,” applications or micro-applications (as described herein), SMS or other types of text messages, emails, information, Tweets, MMS, and / or other types of communication technologies. In various embodiments, the channel may be hosted or provided by a data partner. In various embodiments, the distribution channel may include at least one of a merchant website, a social media website, an affiliated or partner website, an external vendor, mobile device communications, a social media network, and / or a location-based service. The distribution channel may include at least one of a merchant website or application; a social media website, application, or platform; an affiliated or partner website and application; an external vendor, and mobile device communications. Examples of social media websites, applications, and platforms may include VKontakte (VK), etc. Examples of affiliated or partner websites include AMERICAN etc. In addition, examples of mobile device communications include text messaging, email, and mobile applications for smartphones.

[0062] In various embodiments, the methods described herein are implemented using various specific machines described herein. As will be immediately appreciated by those skilled in the art, the following specific machines, as well as those developed thereafter, may be used in any suitable combination to implement the methods described herein. Further, it is clear from this disclosure that the methods described herein may result in various transformations of certain items.

[0063] The various system components discussed herein may include one or more of the following: a host server or other computing system including a processor for processing digital data; a memory coupled to the processor for storing the digital data; an input digitizer coupled to the processor for inputting the digital data; an application stored in the memory and accessible by the processor for directing the processor to process the digital data; a display device coupled to the processor and the memory for displaying information obtained from the digital data processed by the processor; and a plurality of databases. The various databases used herein may include: customer data; merchant data; financial institution data; and / or similar data useful for the operation of the system. It will be appreciated by those skilled in the art that a user computer may include an operating system (e.g., OS2, MacOS, etc.) and various general supporting software and drivers typically associated with a computer.

[0064] The present system or any part or function thereof can be implemented using hardware, software or a combination thereof, and can be implemented in one or more computer systems or other processing systems. However, the manipulation performed by the embodiment is usually referred to by terms such as matching or selecting, which are usually related to the intellectual operation performed by a human operator. In any operation described herein, this ability of a human operator is not necessary or desirable in most cases. Instead, the operation can be machine-operated, or any operation can be performed or enhanced by artificial intelligence (AI) or machine learning. Useful machines for implementing various embodiments include general-purpose digital computers or similar devices.

[0065] In fact, and according to various embodiments, embodiments relate to one or more computer systems capable of performing the functions described herein. The computer system includes one or more processors, such as a processor. The processor is connected to a communication infrastructure (e.g., a communication bus, a cross over bar, or a network). Various software embodiments are described from the perspective of this exemplary computer system. After reading this description, it will be clear to those skilled in the relevant art how to implement various embodiments using other computer systems and / or architectures. The computer system may include a display interface that forwards graphics, text, and other data from the communication infrastructure (or from a frame buffer, not shown) to be displayed on a display unit.

[0066] The computer system also includes a main memory, such as, for example, a random access memory (RAM), and may also include a secondary memory or a memory-based (non-rotating) hard drive. The secondary memory may include, for example, a hard drive and / or a removable storage drive, which represents a floppy disk drive, a tape drive, an optical disk drive, etc. The removable storage drive reads from and / or writes to a removable storage unit in a known manner. A removable storage unit represents a floppy disk, a tape, an optical disk, etc. that is read by and written to the removable storage drive. It should be understood that a removable storage unit includes a computer-usable storage medium having computer software and / or data stored therein.

[0067] In various embodiments, auxiliary storage may include other similar devices for enabling computer programs or other instructions to be loaded into a computer system. These devices may include, for example, removable storage units and interfaces. Such examples may include program cartridges and cartridge interfaces (e.g., found in video game devices), removable storage chips (e.g., erasable programmable read-only memory (EPROM) or programmable read-only memory (PROM)) and associated nesting, and other removable storage units and interfaces that enable software and data to be transferred from a removable storage unit to a computer system.

[0068] The computer system may also include a communication interface. The communication interface allows software and data to be transmitted between the computer system and an external device. Examples of communication interfaces may include a modem, a network interface (such as an Ethernet card), a communication port, a PCMCIA slot and a card, etc. The software and data files transmitted by the communication interface exist in the form of signals, which may be electronic, electromagnetic, optical or other signals that can be received by the communication interface. These signals are provided to the communication interface via a communication path (e.g., a channel). The channel carries signals and can be implemented using wires, cables, optical fibers, telephone lines, cellular links, radio frequency (RF) links, wireless and other communication channels.

[0069] The terms "computer program medium" and "computer usable medium" and "computer readable medium" are generally used to refer to media such as removable storage drives and hard disks installed in hard drives. These computer program products provide software to computer systems.

[0070] Computer programs (also referred to as computer control logic) are stored in the main memory and / or the secondary memory. The computer programs may also be received via a communication interface. These computer programs, when executed, enable the computer system to perform the features discussed herein. In particular, the computer programs, when executed, cause the processor to perform the features of the various embodiments. Therefore, these computer programs represent the controller of the computer system.

[0071] In various embodiments, the software can be stored in a computer program product using a removable storage drive, a hard drive, or a communication interface and loaded into a computer system. The control logic (software) causes the processor to perform the functions of the various embodiments described herein when executed by the processor. In various embodiments, hardware components, such as application specific integrated circuits (ASICs). It will be apparent to those skilled in the relevant art to implement a hardware state machine to perform the functions described herein.

[0072] In various embodiments, the server may include an application server (e.g., Postgres Plus Advanced (PPAS), etc.). In various embodiments, the server may include a network server (e.g. IIS, GWS, SUN System network server, or Running on virtual machines).

[0073] Web clients include any device (e.g., a personal computer) that communicates over any network (e.g., such as those discussed herein). These browser applications include Internet browsing software installed within a computing unit or system to conduct online transactions and / or communications. These computing units or systems may take the form of a computer or group of computers, including a laptop, notebook computer, tablet computer, handheld computer, personal digital assistant, set-top box, workstation, computer server, mainframe, minicomputer, PC server, pervasive computer, network computer group, such as a desktop computer, ... and A personal computer, kiosk, terminal, point of sale (PoS) device and / or terminal, television, or any other device capable of receiving data over a network. The web client can run INTERNET Safari or any other of the various software packages that can be used to browse the internet.

[0074] It will be appreciated by those skilled in the art that the web client may or may not be in direct contact with the application server. For example, the web client may access the services of the application server through another server and / or hardware component, which may be directly or indirectly connected to an Internet server. For example, the web client may communicate with the application server through a load balancer. In various embodiments, access is performed through a network or the Internet via a commercially available web browser software package.

[0075] It should be understood by those skilled in the art that a web client includes an operating system (e.g., OS, OS2, OS, OS, MacOS, etc.) and various conventional support software and drivers typically associated with computers. The web client may include any suitable personal computer, network computer, workstation, personal digital assistant, cellular phone, smart phone, minicomputer, mainframe, etc. The web client may be in a home or business environment with access to the network. In various embodiments, access is performed via a commercially available web browser software package over a network or the Internet. The web client may implement security protocols such as Secure Sockets Layer (SSL) and Transport Layer Security (TLS). The web client may implement several application layer protocols, including http, https, ftp, and sftp.

[0076] In various embodiments, the components, modules and / or engines of system 100 may be implemented as mini-applications or micro-apps. Micro-apps are typically deployed in the context of a mobile operating system, such as a mobile operating system including Mobile operating systems, operating system, Operating system, etc. The micro-application can be configured to utilize the resources of the larger operating system and related hardware through a set of predetermined rules, which manage the operation of various operating systems and hardware resources. For example, in the case where the micro-application wants to communicate with a device or network other than a mobile device or a mobile operating system, the micro-application can utilize the communication protocol of the operating system and related device hardware under the predetermined rules of the mobile operating system. In addition, in the case where the micro-application requires input from the user, the micro-application can be configured to request a response from the operating system, which monitors various hardware components and then transmits the detected input from the hardware to the micro-application.

[0077] As used herein, an "identifier" may be any suitable identifier that uniquely identifies an item. For example, an identifier may be a Globally Unique Identifier ("GUID"). A GUID may be an identifier created and / or implemented according to a universally unique identifier standard. In addition, a GUID may be stored as a 128-bit value that may be displayed as 32 hexadecimal digits. An identifier may also include a major number and a minor number. Each of the major number and the minor number may be a 16-bit integer.

[0078] As used herein, "issuing a loan," "borrowing," or "debit" means debiting a stored-value or prepaid card type financial account, or charging a credit or debit card type financial account, as the case may be.

[0079] Any database discussed herein may include a relational database, a hierarchical database, a graph database, a blockchain database, or an object-oriented structured database, and / or any other database configuration. Any database may also include a flat file structure, where data may be stored in a single file in the form of rows and columns without a structure for indexing and structural relationships between records. For example, a flat file structure may include a delimited text file, a comma-separated value (CSV) file, and / or any other suitable flat file structure. Common database products that may be used to implement a database include DB2 (located in Armonk, New York), available from various database products acquired by the company (located in Redwood Shores, California), MICROSOFT or MICROSOFT SQL MySQL AB (Uppsala, Sweden), Apache HBase, MapR-DB, or any other suitable database product. In addition, the database can be organized in any suitable manner, for example, as a data table or a lookup table. Each record can be a single file, a series of files, a series of associated data fields, or any other data structure.

[0080] Any database discussed herein may include a distributed ledger maintained by multiple computing devices (e.g., nodes) through a peer-to-peer network. Each computing device maintains a copy and / or partial copy of the distributed ledger and communicates with one or more other computing devices in the network to verify the distributed ledger and write data to the distributed ledger. The distributed ledger can utilize the features and functions of blockchain technology, including, for example, consensus-based verification, immutability, and encrypted chained data blocks. The blockchain may include a ledger of interconnected blocks containing data. The blockchain may provide enhanced security because each block can save the results of individual transactions and any blockchain executable files. Each block can be linked to the previous block and may include a timestamp. Blocks can be linked because each block can include a hash of a previous block in the blockchain. The linked blocks form a chain, and for a single chain, only one successor block is allowed to link to another predecessor block. Forks are possible, where divergent chains are established from a previously unified blockchain, although typically only one divergent chain is maintained as a consensus chain. In various embodiments, a blockchain may implement smart contracts that execute data workflows in a decentralized manner. The system may also include applications deployed on user devices, such as, for example, computers, tablets, smartphones, Internet of Things devices ("IoT" devices), etc. The application may communicate with the blockchain (e.g., directly or through a blockchain node) to transmit and retrieve data. In various embodiments, a governing body or consortium may control access to data stored on the blockchain. Registration with a governing body may provide for participation in the blockchain network.

[0081] Data delivered via a blockchain-based system may be propagated to connected peers within the blockchain network over a duration that may be determined by the block creation time of the particular blockchain technology implemented. On a network based on On the Fabric 1.0 platform, the duration is driven by the specific consensus algorithm selected and can be executed in seconds. In this regard, the propagation time in the system can be improved compared to existing systems, and the implementation cost and time to market can also be significantly reduced. At least in part due to the immutable nature of the data stored in the blockchain, the security of the system is also improved, reducing the probability of various data inputs and outputs being tampered with. In addition, by encrypting the data before storing it on the blockchain, the system can also improve the security of the data. Therefore, by transmitting, storing, and accessing data using the system described in this article, the security of the data is improved, which reduces the risk of computers or networks being compromised.

[0082] In various embodiments, the blockchain-based system can also reduce database synchronization errors by providing a common data structure, thereby at least partially improving the integrity of stored data. Because each node operates with a complete copy of the stored data, the system also improves reliability and fault tolerance compared to traditional databases (e.g., relational databases, distributed databases, etc.), thereby at least partially reducing downtime due to local network outages and hardware failures. Because each node propagates messages to all connected peers, the system can also improve the reliability of data delivery in a network environment with reliable peers and unreliable peers, and because each block includes a link to the previous block, a node can quickly detect missing blocks and propagate requests for missing blocks to other nodes in the blockchain network.For more information on distributed ledgers that implement features and functionality of blockchains, see the following: U.S. Application No. 15 / 266,350, filed on September 15, 2016, entitled SYSTEMS AND METHODS FOR BLOCKCHAIN ​​BASED PAYMENT NETWORKS; U.S. Application No. 15 / 682,180, filed on August 21, 2017, entitled SYSTEMS AND METHODS FOR DATA FILE TRANSFER BALANCING AND CONTROL ON BLOCKCHAIN; U.S. Application No. 15 / 728,086, filed on October 9, 2017, entitled SYSTEMS AND METHODS FOR LOYALTY POINT DISTRIBUTION; U.S. Application No. 15 / 730,086, filed on October 17, 2017, entitled MESSAGING BALANCING AND CONTROL ON BLOCKCHAIN; U.S. Application No. 15 / 785,843, filed on October 17, 2017, entitled API REQUEST AND RESPONSE BALANCING AND CONTROL ON BLOCKCHAIN; U.S. Application No. 15 / 785,870, filed on October 17, 2017, entitled API REQUEST AND RESPONSE BALANCING AND CONTROL ON BLOCKCHAIN; U.S. Application No. 15 / 824,450, filed on November 28, 2017, entitled SINGLESIGN-ON SOLUTION USING BLOCKCHAIN; U.S. Application No. 15 / 824,513, filed on November 28, 2017, entitled TRANSACTION AUTHORIZATION PROCESS USING BLOCKCHAIN; U.S. Application No. 15 / 824,513, filed on November 28, 2017, entitled TRANSACTION PROCESS USING BLOCKCHAIN ​​TOKEN SMART U.S. Application No. 15 / 943,168, entitled CONTRACTS (Transaction Process Using Blockchain Token Smart Contracts); U.S. Application No. 15 / 943,271, filed on April 2, 2018, entitled FRAUDMANAGEMENT USING A DISTRIBUTED DATABASE (Fraud Management Using a Distributed Database), the contents of which are incorporated by reference in their entirety.

[0083] The association of certain data can be accomplished by any desired data association technique, such as those known or practiced in the art. For example, association can be accomplished manually or automatically. Automatic association techniques can include, for example, database search, database merge, GREP, AGREP, SQL, using key fields in a table to speed up search speed, performing sequential searches in all tables and files, sorting records in a file according to a known order to simplify search, etc. The association step can be accomplished by a database merge function, for example, using a "key field" in a preselected database or data area. It is contemplated that various database adjustment steps are performed to optimize database performance. For example, frequently used files such as indexes can be placed on a separate file system to reduce input / output ("I / O") bottlenecks.

[0084] More specifically, "key fields" partition the database according to the high-level object class defined by the key fields. For example, certain types of data can be designated as key fields in multiple related data tables, and then these data tables can be linked based on the data type in the key fields. The data corresponding to the key fields in each linked data table is preferably the same or belongs to the same type. However, for example, data tables with similar but not identical data in the key fields can also be linked by using AGREP. According to one embodiment, any suitable data storage technology can also be used to store data without a standard format. Any suitable technique may be used to store the data sets, including, for example, using the ISO / IEC 7816-4 file structure to store individual files; implementing a domain whereby a dedicated file is selected that exposes one or more elementary files containing one or more data sets; using data sets stored in individual files utilizing a hierarchical file system; data sets stored as records in a single file (including compressed, SQL accessible, hashed via one or more keys, numeric, alphabetically by first ancestor, etc.); binary large objects (BLOBs); stored as ungrouped data elements encoded using ISO / IEC 7816-6 data elements; stored as ungrouped data elements encoded using ISO / IEC Abstract Syntax Notation (ASN.1) in ISO / IEC 8824 and 8825; and / or other proprietary techniques that may include fractal compression methods, image compression methods, etc.

[0085] In various embodiments, the ability to store various information in different formats benefits from storing the information as a BLOB. Therefore, any binary information can be stored in a storage space associated with a data set. As discussed above, binary information can be stored in association with the system, or outside the system but attached to the system. The BLOB method can use fixed storage allocation, circular queue technology, or best practices for memory management (e.g., least recently used paging memory, etc.) to store data sets as ungrouped data elements in the format of binary blocks via fixed memory offsets. By using the BLOB method, the ability to store various data sets with different formats enables multiple unrelated owners of data sets to store data in a database, or store data in association with a system. For example, a first data set that can be stored can be provided by a first party, a second data set that can be stored can be provided by an unrelated second party, and a third data set that can be stored can be provided by a third party that is unrelated to the first party and the second party. Each of these three exemplary data sets can contain different information stored using different data storage formats and / or technologies. In addition, each data set can contain a subset of data that may also be different from other subsets.

[0086] As described above, in various embodiments, the storage of data may not consider a common format. However, when providing data for manipulating a database or system, a data set (e.g., BLOB) may be annotated in a standard manner. The annotation may include a short header, a trailer, or other suitable indicator associated with each data set, which is configured to convey information for managing various data sets. For example, the annotation may be referred to herein as a "conditional header," "header," "trailer," or "status," and may include an indication of the state of the data set, or may include an identifier associated with a specific publisher or owner of the data. In one example, the first three bytes of each data set BLOB may be configured or configurable to indicate the state of the particular data set: for example, loaded, initialized, ready, blocked, removable, or deleted. Subsequent data bytes may be used to indicate, for example, the identity of a transaction / member account identifier, a user, an issuing agency, etc. Each of these conditional annotations is further discussed herein.

[0087] Dataset annotations can also be used for other types of state information and for various other purposes. For example, dataset annotations can include security information that establishes access levels. For example, access levels can be configured to allow only certain individuals, employee levels, companies, or other entities to access a dataset, or to allow access to specific datasets based on transactions, merchants, issuers, users, etc. In addition, security information can only limit / allow certain actions such as accessing, modifying, and / or deleting a dataset. In one example, a dataset annotation indicates that only the dataset owner or user is allowed to delete the dataset, various identified users can be allowed to access the dataset for reading, and others cannot access the dataset at all. However, other access restriction parameters can also be used that allow various entities to access the dataset with various permission levels (if applicable).

[0088] The data including the header or footer may be received by a separate interactive device configured to add, delete, modify or augment the data in accordance with the header or footer. Thus, in one embodiment, the header or footer is not stored on the transaction device along with the data held by the relevant issuing institution, but instead, appropriate action may be taken by providing the user with an appropriate option of action to be taken on the separate device. The system may contemplate a data storage arrangement in which a header or footer or a history of headers or footers of data is stored on the system, device or transaction instrument in association with appropriate data.

[0089] Those skilled in the art should also understand that for security reasons, any database, system, device, server or other system component may include any combination thereof at a single location or multiple locations, with each database or system including any of a variety of suitable security features, such as firewalls, access codes, encryption, decryption, compression, decompression, etc.

[0090] Encryption can be performed by any technology that is now available or that is likely to become available in the art - for example, Twofish, RSA, El Gamal, Schorr signatures, DSA, PGP, PKI, GPG (GnuPG), HPE format preserving encryption (FPE), voltage, and symmetric and asymmetric cryptographic systems. These systems and methods can also be combined with the SHA family of encryption methods and elliptic curve cryptography (ECC) and other quantum readable encryption algorithms that are being developed.

[0091] The computing unit of the web client may also be equipped with an Internet browser that connects to the Internet or an intranet using standard dial-up, cable, DSL, or any other Internet protocol known in the art. Transactions initiated at the web client may pass through a firewall to prevent unauthorized access by users from other networks. In addition, additional firewalls may be deployed between different components of the CMS to further enhance security.

[0092] A firewall may include any hardware and / or software that is appropriately configured to protect CMS components and / or enterprise computing resources from users of other networks. In addition, a firewall may be configured to limit or restrict access to various systems and components behind the firewall for web clients connected through a network server. Firewalls may exist in different configurations, including stateful inspection, proxy-based, access control lists, and packet filtering. A firewall may be integrated into a network server or any other CMS component, or may also exist as a separate entity. A firewall may implement network address translation ("NAT") and / or network address port translation ("NAPT"). A firewall may adapt to various tunneling protocols to facilitate secure communications, such as those used in virtual private networks. A firewall may implement a demilitarized zone ("DMZ") to facilitate communications with public networks such as the Internet. A firewall may be integrated as software in an Internet server, any other application server component, or may exist in another computing device, or may take the form of an independent hardware component.

[0093] The computer discussed herein may provide a suitable website or other Internet-based graphical user interface that a user may access. In one embodiment, INTERNET INFORMATION (IIS), Trading Server (MTS) and SQL Server with operating system, NT network server software, SQL Server database system and In addition, you can use access or SQL Server, Sybase, Informix MySQL, Interbase and other components are used to provide a database management system compatible with dynamic data objects (Active Data Object, ADO). In one embodiment, the Apache web server is used together with the Linux operating system, the MySQL database, and the Perl, PHP, Ruby and / or Python programming languages.

[0094] Any of the communications, input, storage, databases, or displays discussed herein may be facilitated by a website having web pages. The term "web page" as used herein is not intended to limit the types of documents and applications that may be used to interact with a user. For example, in addition to including standard HTML documents, a typical website may also include various forms, Mini Programs, Active Server Pages (ASP), Common Gateway Interface (CGI), Extensible Markup Language (XML), Dynamic HTML, Cascading Style Sheets (CSS), AJAX (Asynchronous and XML), auxiliary applications, plug-ins, etc. The server may include a web service that receives a request from a web server, the request including a URL and an IP address (e.g., 10.0.0.2). The web server retrieves the appropriate web page and sends the data of the web page or application to the IP address. A web service is an application that is able to interact with other applications through communication means such as the Internet. Web services are typically based on standards or protocols such as XML, SOAP, AJAX, WSDL, and UDDI. Web service methods are well known in the technical field and are described in many standard texts. For example, Representational State Transfer (REST), or RESTful, web services can provide a way to achieve interoperability between applications.

[0095] Middleware can include any hardware and / or software that is appropriately configured to communicate between different computing systems and / or process transactions between different computing systems. Middleware components are commercially available and known in the art. Middleware can be implemented by commercially available hardware and / or software, customized hardware and / or software components, or a combination thereof. Middleware can exist in various configurations and can exist as a stand-alone system, or can be a software component that exists on an Internet server. Middleware can be configured to process transactions between various components of an application server and any number of internal or external systems for any purpose disclosed herein. Ltd. (located in Armonk, New York) MQTM (formerly MQSeries) is an example of a commercially available middleware product. An enterprise service bus ("ESB") application is another example of middleware.

[0096] Practitioners will also appreciate that there are many methods for displaying data in browser-based documents. Data can be presented as standard text or in fixed lists, scrollable lists, drop-down lists, editable text fields, fixed text fields, pop-up windows, etc. Likewise, there are many methods for modifying data in a web page (such as, for example, free text entry) using the keyboard, menu item selections, check boxes, option boxes, etc.

[0097] The system and method may be described in terms of functional block components, screen shots, selectable options, and various processing steps. It should be understood that these functional blocks may be implemented by any number of hardware and / or software components configured to perform the specified functions. For example, the system may employ various integrated circuit components, such as memory elements, processing elements, logic elements, lookup tables, etc., which may perform various functions under the control of one or more microprocessors or other control devices. Likewise, the software elements of the system may be implemented in any programming language or scripting language, such as C, C++, C#, based on lightweight data exchange format for languages ​​(JSON), VBScript, Macromedia Cold Fusion, COBOL, Active Server Pages, Assembly, PERL, PHP, awk, Python, Visual Basic, SQL stored procedures, PL / SQL, any UNIX shell script, and Extensible Markup Language (XML), wherein various algorithms are implemented using any combination of data structures, objects, processes, routines, or other programming elements. In addition, it should be noted that the system may employ any number of conventional techniques for data transmission, signaling, data processing, network control, etc. Further, the system may be used to detect or prevent, for example, Security issues with client-side scripting languages ​​such as VBScript. Cryptography and network security methods are well known in the art and are described in many standard texts.

[0098] In various embodiments, software elements of the system may also use accomplish. Multiple modules can be implemented to handle various core functions. For example, a package management module (such as ) can be implemented as an open source library to help organize third-party Installation and management of programs. It can also implement process managers, such as, for example, Parallel Multithreaded Machine ("PM2"); resource and performance monitoring tools, such as, for example, Node Application Metrics ("appmetrics"); library modules for building user interfaces, such as and / or any other suitable and / or desired modules.

[0099] Those of ordinary skill in the art will appreciate that the system can be specifically embodied as existing systems, additional products, processing equipment for executing upgraded software, independent systems, distributed systems, methods, data processing systems, equipment for data processing, and / or customization of computer program products. Therefore, any part of the system or module can take the following forms: processing equipment for executing code, embodiments based on the Internet, embodiments of complete hardware, or embodiments combining various aspects of the Internet, software, and hardware. In addition, the system can take the form of a computer program product on a computer-readable storage medium, which has a computer-readable program code device specifically implemented in a storage medium. Any suitable computer-readable storage medium can be utilized, including hard disks, CD-ROMs, BLU-RAYs, optical storage devices, magnetic storage devices, etc.

[0100] The systems and methods are described herein with reference to screenshots, block diagrams, and flowchart illustrations of methods, devices (e.g., systems), and computer program products according to various embodiments. It should be understood that each functional block in the block diagrams and flowchart illustrations, and combinations of functional blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by computer program instructions.

[0101] Reference now Figure 3-Figure 5 , the process flows and screen shots described are merely examples and are not intended to limit the scope of the present disclosure. For example, the steps detailed in any method or process description may be performed in any order and are not limited to the order presented.

[0102] These computer program instructions may be loaded onto a general purpose computer, a special purpose computer, or other programmable data processing device to produce a machine, whereby the instructions executed on the computer or other programmable data processing device create means for implementing the functions specified in one or more flowchart blocks. These computer program instructions may also be stored in a computer readable memory, which may direct the computer or other programmable data processing device to operate in a particular manner, whereby the instructions stored in the computer readable memory generate an article of manufacture, which includes instruction means for implementing the functions specified in one or more flowchart blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing device to perform a series of operational steps on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more flowchart blocks.

[0103] Therefore, the functional blocks in the block diagrams and flowchart illustrations support a combination of means for performing the specified functions, a combination of steps for performing the specified functions, and program instruction means for performing the specified functions. It should also be understood that each functional block in the block diagrams and flowchart illustrations, and the combination of functional blocks in the block diagrams and flowchart illustrations can be implemented by a hardware-based special-purpose computer system or an appropriate combination of special-purpose hardware and computer instructions, and the hardware-based special-purpose computer system performs the specified functions or steps. In addition, the diagrams and descriptions of the process flow can refer to the user Web pages, websites, web forms, prompts, etc. Practitioners should understand that the illustrated steps described herein may include any number of configurations, including using Web pages, web forms, pop-ups It should also be understood that the multiple steps shown and described may be combined into a single web page and / or , but has been expanded for simplicity. In other cases, steps shown and described as single process steps may be separated into multiple web pages and / or but have been merged for simplicity.

[0104] The term "non-transitory" should be interpreted as excluding only propagating transitory signals per se from the scope of the claims, without disclaiming rights to all standard computer-readable media that are not merely propagating transitory signals. In other words, the meaning of the terms "non-transitory computer-readable medium" and "non-transitory computer-readable storage medium" should be interpreted as excluding only those types of transitory computer-readable media that were found in ReNuijten to fall outside the scope of patentable subject matter under 35 U.S.C. § 101.

[0105] Phrases and terms similar to "account", "account number", "account code" or "consumer account" as used herein may include any device, code (e.g., one or more of an authorization / access code, a personal identification number ("PIN"), an Internet code, other identification codes, etc.), numbers, letters, symbols, digital certificates, smart chips, digital signals, analog signals, biometrics, or other identifiers / markers appropriately configured to allow a customer to access, interact with, or communicate with a system. An account number may optionally be located on or associated with a reward account, a charge account, a credit account, a debit account, a prepaid account, a phone card, an embossed card, a smart card, a magnetic stripe card, a barcode card, a transponder, a radio frequency card, or an associated account.

[0106] In various embodiments, the account number can identify the customer. In addition, in various embodiments, the customer can be identified by various identifiers, for example, these identifiers include email addresses, phone numbers, cookie ids, radio frequency identifiers (RFID), biometrics, etc.

[0107] Rather than describing only a specific result of processing a transaction using a remote EMV payment application, the present disclosure and claims include specific rules for achieving the result of processing a transaction using a remote EMV payment application, as well as specific rules for presenting information into a specific format that is then used and applied to create the desired result of processing a transaction using a remote EMV payment application, as described in McRO, Inc. v. Bandai Namco Games America Inc. (Fed. Cir., Case No. 15-1080, Sept. 13, 2016). In other words, the result of processing a transaction using a remote EMV payment application can be executed by many different types of rules and rule combinations, and the present disclosure includes various embodiments with specific rules. While the absence of complete preemption may not guarantee that a claim is qualified, the present disclosure does not completely preempt the field of processing transactions using a remote EMV payment application at all. The present disclosure serves to narrow, limit, and constrain the present disclosure so as not to cover the general abstract concept of processing transactions using only a remote EMV payment application. Obviously, there are other systems and methods for processing EMV transactions, so it would be inappropriate to claim that the claimed invention preempts the field or monopolizes the basic tools for processing EMV. In other words, the present disclosure will not prevent others from using remote EMV payment applications to process transactions because other systems already perform functions in a manner different from the claimed invention. In addition, the claimed invention includes such inventive concepts that can be found in unconventional and non-common arrangements of known conventional means, consistent with Bascom v. AT&T Mobility, 2015-1763 (Fed. Cir. 2016). The present disclosure and claims go far beyond any conventionality of any one system in that the interaction and synergy of the systems result in additional functionality that is not provided by any independently operating system. The present disclosure and claims may also include interactions between multiple different systems, so the present disclosure cannot be considered an implementation of a general purpose computer or simply "applied to" an abstract process. The present disclosure and claims may also be directed to improvements to software that have specific implementations of solutions to problems in the software field.

[0108] In various embodiments, the systems and methods may include a graphical user interface for dynamically repositioning / rescaling the obscured text information of an underlying window to make it automatically visible to the user (e.g., via user device 105). By dynamically repositioning the text information based on overlapping conditions, the computer's ability to display information is improved. More specifically, a method for dynamically repositioning text information within a lower window displayed in a graphical user interface may include: displaying a first window containing text information in a first format within a graphical user interface on a computer screen; displaying a second window in the graphical user interface; continuously monitoring the boundary of the first window and the second window to detect an overlap condition in which the second window overlaps the first window so that the text information in the first window is obscured from the user's line of sight; determining that the text information will not be fully visible if the text information is repositioned to an uncovered portion of the first window; calculating a first measurement of the area of ​​the first window and a second measurement of the area of ​​the uncovered portion of the first window; calculating a scaling factor that is proportional to the difference between the first measurement and the second measurement; scaling the text information according to the scaling factor; during the overlap state, automatically repositioning, by a processor, the scaled text information in the second format to the uncovered portion of the first window so that the entire scaled text information can be viewed by the user on the computer screen; when the overlap condition no longer exists, automatically returning, by the processor, the repositioned scaled text information to the first format within the first window.

[0109] In various embodiments, the system may also include isolating and deleting malicious code from electronic messages to prevent damage to a computer or network, such as due to infection by a computer virus. The system may scan electronic communications for malicious computer code and remove the electronic communications before it can initiate malicious behavior. The system operates by physically isolating received electronic communications in a "quarantine" area of ​​computer memory. A quarantine area is a storage area created by a computer operating system that does not allow files stored in the area to act on files outside the area. When a communication containing malicious code is stored in the quarantine area, the data contained in the communication is compared to malicious code indication patterns stored in a signature database. The presence of a specific malicious code indication pattern indicates the nature of the malicious code. The signature database also includes code markers that represent the starting and ending points of the malicious code. The malicious code is then extracted from the communication containing the malicious code. The extraction routine is run by a file parsing component of the processing unit. The file parsing routine performs the following operations: scanning the communication for an identified start malicious code marker; marking each scanned byte between the start marker and the following end malicious code marker; continuing to scan until no other start malicious code marker is found; and creating a new data file by copying all unmarked data bytes sequentially into the new file, which forms a sanitized communication file. The sanitized new communication is transferred to a non-isolated area of ​​computer memory. Subsequently, all data in the isolated area is erased. More specifically, the system includes a method for protecting a computer from electronic communications containing malicious code by the following steps: receiving an electronic communication containing malicious code in a computer having a memory, the memory having a boot area, an isolated area, and a non-isolated area; storing the communication in an isolated area of ​​the computer's memory, wherein the isolated area is isolated from the non-isolated area and the boot area in the computer's memory, wherein the code in the isolated area is blocked from performing write operations to other storage areas; extracting the malicious code from the electronic communication through file parsing to create a sanitized electronic communication, wherein the extraction includes: scanning the communication for an identified starting malicious code marker, marking each scanned byte between the starting marker and a subsequent ending malicious code marker, continuing to scan until no further starting malicious code markers are found, and creating a new data file by copying all unmarked data bytes in sequence into a new file, the new file forming a sanitized communication file; transferring the sanitized electronic communication to the non-isolated area of ​​the memory; and deleting all data remaining in the isolated area.

[0110] The benefits, other advantages, and solutions to problems with respect to specific embodiments have been described herein. However, these benefits, advantages, solutions to problems, and any elements that may make any benefit, advantage, or solution produce or become more apparent should not be interpreted as essential, critical, or necessary features or elements of the present disclosure. Therefore, the scope of the present disclosure is limited only by the appended claims, in which, unless explicitly stated, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". In addition, when a phrase similar to 'at least one of A, B, and C' or 'at least one of A, B, or C' is used in a claim or specification, it is intended that the phrase be interpreted as meaning: A may exist alone in an embodiment, B may exist alone in an embodiment, C may exist alone in an embodiment, or any combination of elements A, B, and C may exist in a single embodiment; for example, A and B, A and C, B and C, or A and B and C. Although the present disclosure includes methods, it is contemplated that it may be implemented as computer program instructions on a tangible computer-readable carrier (such as a magnetic or optical storage or a disk or optical disk). All structural, chemical, and functional equivalents to the elements of the various embodiments described above that are known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims of the present disclosure.

[0111] In addition, the device or method does not have to solve every problem that the present disclosure seeks to solve, and the present disclosure is covered by the present claims. In addition, whether or not the elements, components or method steps of the present disclosure are explicitly described in the claims, it is not intended to contribute these elements, components or method steps to the public. No claim element is intended to quote Section 112(f) of Section 35 of the United States Code unless the element is explicitly described using the term "device for". As used herein, the term "comprises", "comprising" or any other variation thereof is intended to cover non-exclusive inclusion, so that the process, method, article or equipment including the list of elements includes not only those elements, but also other elements that are not explicitly listed or inherent to such a process, method, article or equipment.

Claims

1. A method for initiating an EMV transaction using a payment instrument, comprising: receiving, by a processor, a transaction request from a mobile device, the transaction request comprising a payment token and an EMV payment application uniform resource identifier (URI), wherein the transaction request is generated by a merchant point of sale (PoS) in response to a payment instrument interfacing with the merchant PoS, wherein the payment instrument comprises a local EMV payment application, and the merchant PoS comprises a merchant PoS kernel, wherein the local EMV payment application is configured to interact with the merchant PoS kernel to initiate a transaction, and wherein the payment token and the URI correspond to a remote EMV payment application, the remote EMV payment application being selected by the local EMV payment application during the interaction based on a transaction account selected by a user for the transaction; wherein the EMV payment application URI comprises a character string, the character string identifying a storage location of the remote EMV payment application in a payment application server; providing, by the processor, the EMV payment application URI and the payment token from the transaction request to the payment application server; Based on the EMV payment application URI, the payment application server invokes the remote EMV payment application; wherein the remote EMV payment application is configured to, in response to being called, interact with a merchant system kernel executed by the processor to process the transaction request, and wherein the remote EMV payment application is configured to transmit a transaction authorization request containing EMV transaction data directly to an issuer system in response to processing the transaction request, the EMV transaction data including the payment token; as well as A transaction authorization notification is received, by the processor, from the issuer system, wherein the transaction authorization notification is based on the transaction authorization request generated by the remote EMV payment application.

2. The method according to claim 1, further comprising: A transaction data request is transmitted by the processor in response to the remote EMV payment application determining that additional data is required to authorize the transaction request.

3. The method of claim 1, wherein the remote EMV payment application is configured to process the transaction request by generating a payment cryptogram to be transmitted to the issuer system to authorize the transaction request.

4. A system comprising: a processor configured to execute a merchant system kernel; Merchant Point of Sale PoS, including the merchant PoS kernel; Payment tools, including native EMV payment applications; Payment application servers, including remote EMV payment applications; and Issuing agency system; Wherein, the system is configured to perform the method according to claim 1.

5. The system according to claim 4, further comprising: A transaction data request is transmitted by the processor in response to the remote EMV payment application determining that additional data is required to authorize the transaction request.

6. The system of claim 4, wherein the remote EMV payment application is configured to process the transaction request by generating a payment cryptogram to be transmitted to the issuer system to authorize the transaction request.

7. A method for initiating an EMV transaction using a payment instrument, comprising: receiving, by a processor, a transaction request from a mobile device, the transaction request comprising a payment token and an EMV payment application uniform resource identifier (URI), wherein the transaction request is generated by a merchant point of sale (PoS) in response to a payment instrument interfacing with the merchant PoS, wherein the payment instrument comprises a local EMV payment application, and the merchant PoS comprises a merchant PoS kernel, wherein the local EMV payment application is configured to interact with the merchant PoS kernel to initiate a transaction, and wherein the payment token and the URI correspond to a remote EMV payment application, the remote EMV payment application being selected by the local EMV payment application during the interaction based on a transaction account selected by a user for the transaction; wherein the EMV payment application URI comprises a character string, the character string identifying a storage location of the remote EMV payment application in a payment application server; providing, by the processor, the EMV payment application URI and the payment token from the transaction request to the payment application server; Based on the EMV payment application URI, the payment application server invokes the remote EMV payment application; wherein the remote EMV payment application is configured to interact with a merchant system kernel executed by the processor in response to being called to process the transaction request, wherein the remote EMV payment application is configured to transmit EMV transaction data including the payment token to an issuer system in response to processing the transaction request; and transmitting, by the processor, a transaction authorization request to the issuer system, wherein the issuer system is configured to combine the EMV transaction data and the transaction authorization request to authorize the transaction; and A transaction authorization notification is received by the processor from the issuer system.

8. The method according to claim 7, further comprising: A transaction data request is transmitted by the processor in response to the remote EMV payment application determining that additional data is required to authorize the transaction request.

9. The method of claim 7, wherein the issuer system is configured to settle the transaction in response to authorizing the transaction.

10. A system comprising: a processor configured to execute a merchant system kernel; Merchant Point of Sale PoS, including the merchant PoS kernel; Payment tools, including native EMV payment applications; Payment application servers, including remote EMV payment applications; and Issuing agency system; The system is configured to perform the method according to any one of claims 7-9.

Images