Remote transaction system, method and point-of-sale terminal
Through the remote transaction processing system and methods, the user equipment's data storage and routing data transmission POS configuration is used to solve the problem of insufficient security of the online card payment system, and secure remote card-free transactions are realized, reducing fraud risks and economic losses. .
Patent Information
- Application Number
- CN202011235492.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2015-03-03
- Filing Date
- 2015-03-24
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2035-03-24
AI Technical Summary
The existing online card payment system has insufficient security, and users need to manually enter card information, which is prone to stolen or forged, resulting in economic losses for merchants and consumers. The existing POS terminals are not suitable for remote card-free transactions.
Provide a remote transaction processing system and method, search the corresponding user equipment profile and merchant POS configuration profile through the data repository of the user equipment, and use the routing data to transmit the POS configuration, so that the user equipment acts as a POS terminal to realize secure remote transactions. .
It improves transaction security, reduces the risk of fraud, and avoids the process of users entering card information manually. It is suitable for remote card-free transactions, reducing economic losses to merchants and consumers.
Smart Images

Figure CN112308555B_ABST
Abstract
Description
[0001] This application is a divisional application of the Chinese invention patent application with application number 201580022312.5 and invention name “Remote transaction system, method and point-of-sale terminal”, whose international application date is March 24, 2015 and entered the Chinese national phase on November 2, 2016. Technical Field
[0002] The present invention relates to a system, method and point of sale (PoS) terminal particularly suitable for use in transactions where the buyer is remote from the merchant. Background Art
[0003] Online stores and merchants often accept credit and debit cards as a form of payment. One problem with online card payments is that the user must manually enter the card information into fields on the online store's website or a page associated therewith.
[0004] Online card payments as described above are so-called "card-not-present" transactions because the merchant cannot verify the presence of the physical card at the time of the transaction. Card-not-present transactions can be easily forged and the risk to the merchant is high. Therefore, the associated transaction fees are high.
[0005] For example, there is no guarantee that the user is entering his / her own card information, i.e., the card information could be stolen or otherwise forged and could result in financial loss to the merchant and / or consumer. Information sent to the website could be misused for fraudulent transactions by anyone with access to the information or by a "middleman" who could detect the information from the communication between the user and the website. There are several ways this can be accomplished.
[0006] Various mechanisms for protecting card-not-present transactions have been proposed. Typically, these do not significantly increase security, or require extensive modifications to existing infrastructure and online websites due to incompatibility with existing systems. Typical point-of-sale (PoS) terminals are not suitable for card-not-present transactions by end users in their homes or other locations because each POS terminal is configured for a specific merchant. When a buyer pays in-store, the PoS terminal remits the funds to a pre-configured bank account. It is impractical to expect each consumer to have a POS terminal for each online merchant he or she may wish to use so that the funds are remitted to the bank account of the appropriate merchant. Summary of the invention
[0007] According to one aspect of the present invention, there is provided a remote transaction processing system comprising a first data repository, the first data repository comprising a user device profile of a user device, the user device profile comprising routing data for routing communications to the user device; wherein, upon receiving a payment request designated for a user device for conducting transactions with a merchant, the remote transaction processing system is arranged to retrieve a point of sale (PoS) configuration profile corresponding to the merchant, and retrieve a user device profile corresponding to the designated user device from the first data repository, the remote transaction processing system is arranged to transmit a PoS configuration depending on the PoS configuration profile to the user device based on the routing data, the PoS configuration being executable by the user device to enable the user device to act as a PoS terminal for conducting transactions with the merchant.
[0008] Preferably, the user device profile comprises a public key of a cryptographic key pair of the user device, the remote transaction processing system being arranged to encrypt the transmitted PoS configuration using the public key.
[0009] Preferably, the routing data comprises a plurality of routes for communicating with a user device, the remote transaction processing system being arranged to determine a route from the plurality of routes for communicating with the user device.
[0010] The routes in the routing data may be ordered, the remote transaction processing system being arranged to identify a route to a user device based on the ordering.
[0011] Preferably, the routes include routes for communicating with user equipment via different channels.
[0012] The channel may be selected from the group consisting of: SMS, instant messaging, a communication to a predetermined address on a data communications network, or a data call over a communications network.
[0013] The system may further comprise a second data repository comprising a point of sale (PoS) configuration profile for each of a plurality of merchants, the remote transaction processing system being arranged to retrieve the PoS configuration profile for a merchant from the second data repository.
[0014] The second data store may include a PoS certificate associated with a respective merchant, the PoS certificate including a PoS configuration profile of the merchant.
[0015] The first data repository may include a user device certificate associated with a respective user device, the user device certificate including a public key of the user device.
[0016] The first data repository and the second data repository may be the same data repository.
[0017] The first data store may include a user device profile for each user device of the plurality of user devices.
[0018] The first data repository may be remote from the user device.
[0019] The first data repository may be local to the user device such that the user device profile may be retrieved from the user device.
[0020] The system may include a merchant website including a payment user interface arranged to receive from a user an identifier specifying a user device profile to be used for payment, the remote transaction processing system being arranged to retrieve the user device profile based on the identifier.
[0021] The system may include a payment processing system arranged to receive a payment request for each of a plurality of merchants.
[0022] The payment processing system may be arranged to receive a PoS configuration profile from a merchant upon receiving a payment request.
[0023] The system may comprise a user device comprising a PoS terminal application and a payment card reader, the user device being arranged to receive a PoS configuration for conducting a transaction with a merchant, to configure the PoS terminal application according to the PoS configuration, and to read a payment card via the payment card reader to pay for the transaction via the PoS terminal application.
[0024] The user equipment may comprise a secure element executing the PoS terminal application, the secure element being selected from the group consisting of: a SIM, a UICC or an ESE (Embedded Secure Element), a Trusted Execution Environment (TEE) or a Secure Environment.
[0025] The secure element may be inserted into, embedded in or built into the user device.
[0026] According to another aspect of the present invention, there is provided a remote transaction processing method, comprising: receiving a payment request designated for a user device for conducting a transaction with a merchant; retrieving a point of sale (PoS) configuration profile corresponding to the merchant; retrieving a user device profile corresponding to the designated user device, the user device profile comprising routing data for routing communications to the user device; and transmitting a PoS configuration depending on the PoS configuration profile to the user device according to the routing data, wherein the PoS configuration is executable by the user device to enable the user device to act as a PoS terminal for conducting a transaction with the merchant.
[0027] The method may also include associating a cryptographic certificate with the user device profile, the certificate including a public key of a public and private key pair; encrypting at least some aspects of the PoS configuration using the public key; and decrypting the encrypted PoS configuration using the private key at the user device.
[0028] The method may further comprise storing the cryptographic certificate in a data repository, the step of retrieving the user device profile comprising retrieving the certificate.
[0029] The step of receiving the payment request may include receiving information about the transaction, and the step of transmitting the PoS configuration may include generating the PoS configuration based on the information about the transaction and the PoS configuration profile.
[0030] The step of generating the PoS configuration may include signing the PoS configuration using a private key of a private / public cryptographic key pair.
[0031] The method may also include performing the following steps at the user device: performing a card payment transaction at the user device by the PoS terminal; signing the payment transaction data at the PoS terminal; encrypting the signed payment transaction data at the POS terminal; sending the encrypted and signed payment transaction data to the payment service host by the PoS terminal; and deleting the payment information from the PoS terminal memory by the PoS terminal. In one or more embodiments, a method for protecting all communications from and to a remotely configurable point of sale (PoS) terminal system is provided. The method includes: a PoS terminal cryptographic key, and a merchant payment system host encrypting payment information based on a transaction input using the PoS terminal cryptographic key. The method also includes: signing the generated payment information with a private key, and sending the signed payment information. The merchant or the merchant's payment service provider configures the POS terminal using the merchant's own PoS terminal profile based on the instructions transmitted in the payment information.
[0032] In one or more embodiments, a method for remotely configuring a point of sale (PoS) terminal is provided. The method includes receiving signed payment information at the PoS terminal. The method also includes verifying the payment information using a public key certificate at the PoS terminal.
[0033] In one or more embodiments, a method for remotely configuring a point of sale (PoS) terminal is provided. The method includes: receiving a transaction input at a merchant device. The method also includes: generating payment information based on the transaction input at the merchant device, and signing the generated payment information using a private key. The method also includes: sending the signed payment information and a public key certificate signed by a certification authority to the PoS terminal. The method includes: verifying the public key certificate using the public key certificate of the certification authority at the PoS terminal, and verifying the payment information using the public key certificate signed by the certification authority at the PoS terminal. The method also includes: when the payment information is verified at the PoS terminal, configuring a terminal profile of the PoS terminal at the PoS terminal according to instructions received in the payment information.
[0034] The payment information and the first public key certificate are then sent using the second public key certificate of one of the PoS terminal and the acquiring bank. BRIEF DESCRIPTION OF THE DRAWINGS
[0035] Embodiments of the present invention will now be described by way of example only with reference to the accompanying drawings, in which:
[0036] Figure 1 is a schematic diagram of a remote transaction processing system according to an embodiment of the present invention;
[0037] Figure 2 yes Figure 1 Schematic diagrams of various aspects of the system in operation;
[0038] Figure 3 is a diagram of a transaction flow in which a merchant sends payment information to a mobile user device executing a PoS application (thereby becoming a PoS terminal);
[0039] Figure 4 is a schematic diagram showing the security clearance issuance and configuration of a temporary PoS terminal profile without using an acquiring bank;
[0040] Figure 5 illustrates transaction messages with an online consumer who uses a separate terminal to make purchases and a mobile device to make payments; and
[0041] Figure 6 Transaction messages with online consumers using mobile devices to make purchases and payments are shown. DETAILED DESCRIPTION
[0042] Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to like elements throughout.
[0043] Figure 1 is a schematic diagram of a remote transaction processing system according to an embodiment of the present invention.
[0044] The remote transaction processing system 10 includes a first data repository 20 .
[0045] The first data store 20 comprises a user equipment profile for each user equipment of the plurality of user equipment, each user equipment profile comprising routing data for routing communications to the user equipment.
[0046] Upon receiving a payment request specifying a user device 40 for conducting a transaction with a merchant, the remote transaction processing system 10 is arranged to retrieve a PoS configuration profile corresponding to the merchant and retrieve a user device profile corresponding to the specified user device 40 from the first data repository 20. The remote transaction processing system 10 transmits a PoS configuration dependent on the PoS configuration profile to the user device 40 via the data communications network 30 in accordance with the routing data. The PoS configuration is executable by the user device 40 to cause the user device to act as a PoS terminal for conducting a transaction with the merchant.
[0047] Optionally, the remote transaction processing system 10 may include a second data repository. The second data repository includes a point of sale (PoS) configuration profile for each of the plurality of merchants and is accessed by the remote transaction processing system 10 to retrieve the merchant's PoS configuration profile.
[0048] The first data repository and the second data repository may be separate or combined. They may also be distributed or replicated data repositories.
[0049] Preferably, each of the PoS configuration profile and the user device profile is or includes a cryptographic certificate, such as a PKI certificate.Examples of data that may be included in a cryptographic certificate are discussed below.
[0050] Figure 2 yes Figure 1 Schematic diagram of various aspects of the system in operation.
[0051] In the present embodiment, the user device 40 is a smartphone and comprises a processor 41 , a memory 42, a card reader 45 and a display 43. The user device 40 is arranged to communicate with the data communications network 30.
[0052] The user interacts with the website 60 and reaches a stage in an online transaction with a merchant associated with the website where payment is required. In this embodiment, the user accesses the website 60 via a computing device 70 different from the user device 40, but it should be understood that the user can access the website 60 via the user device 40.
[0053] The website 60 presents the user with payment options in a user interface. Instead of entering a credit or debit card, as is usually the case at this stage in the transaction, the user enters an identifier for the user device 40.
[0054] Upon receiving the identifier, the website 60 transmits the identifier and the merchant identifier to the payment processing system 80 .
[0055] The payment processing system 80 accesses the first data store 20 to retrieve the PoS configuration profile corresponding to the merchant identifier and accesses the second data store 30 to retrieve the user device profile corresponding to the identifier.
[0056] The payment processing system then generates a PoS configuration 90 based on the retrieved PoS profile, which the payment processing system transmits to the user device 40 using the routing data in the retrieved user device profile.
[0057] Upon receiving the PoS configuration 90, the processor 41 of the user device 40 executes the PoS terminal application 44 in its memory 42 and applies the PoS configuration to become a PoS terminal for the merchant. The user is prompted to present the payment card to the card reader 45, the data in the presented card is processed by the PoS terminal and transmitted to the payment processing system 100 to complete the transaction. At this stage, the transaction appears to the payment processing system to have been initiated from the merchant's PoS terminal, as if it had been completed entirely in store using the merchant's own PoS terminal.
[0058] The routing data preferably includes a plurality of routes for communicating with the user device 40. The payment processing system 80 is preferably arranged to determine a route for communicating with the user device from the plurality of routes. For example, the routes in the routing data may be ranked (or evaluated when needed for ranking). The payment processing system may be arranged to identify a route to the user device based on the ranking.
[0059] The routing preferably comprises routing for communicating with the user equipment via different channels.For example, the channel may be selected from a set comprising: SMS, instant messaging, communication to a predetermined address on a data communications network or a data call via a communications network.
[0060] For example, a user device profile may specify a Google Messenger address as a preferred route, and a Skype address as a first fallback, and an SMS to a mobile device number as a second fallback. When it is desired to transfer a PoS profile, the payment processing system 80 first attempts to communicate with the device via Google Messenger, and then attempts to communicate with the device via Skype before sending the SMS message. In the case of SMS and other payload-limited communication mechanisms, multiple messages may be used, or the message may include a link or other parameters that direct the user device to retrieve the PoS profile.
[0061] The routing data may include the user device's MSISDN (telephone) number, a pseudonym, a device identifier (eg IMEI), a secure element identifier (eg IMSI), an email address, an internet address, a digital communications network address or a Bluetooth address.
[0062] The PoS configuration profile may be in the form of or include a certificate and may, for example, include one or more of: a cryptographic signature verifying the contents of the certificate; banking and / or payment processing data for the PoS terminal application to remit transaction information such as payment details to the payment processing system 80.
[0063] The PoS configuration may include information to be used by a PoS terminal application on a user device to determine whether successful cardholder authentication is required to conduct a transaction associated with the received payment information.
[0064] The PoS configuration may include information about supported cardholder authentication methods.
[0065] The PoS configuration may include payment information including one or more of date, time, amount, currency, minimum amount, contactless limit, transaction limit, transaction identifier, merchant name, and merchant's country.
[0066] The PoS configuration profile may include one or more of a payment service provider identification (PSPID), a merchant identification (MID) code, and / or a terminal identification (TID) code.
[0067] The user device profile may be in the form of or include a certificate and may include one or more of the following: the public key of the user device's cryptographic key pair, the user device's IMSI, the user device's MSISDN (phone) number, an identifier of the cellular network service provider, an identifier of the secure element, an identifier of the mobile device, allowed currencies, prohibited currencies, maximum purchase value, high value purchases with an indicator of cardholder authentication support, maximum purchase value, minimum purchase value, expiration date, identification of allowed mobile devices, a list of supported card companies, PoS application software version number, financial risk management information.
[0068] Preferably, the user device is a mobile device such as a mobile phone, smartphone, tablet or other computing device. It may be a multi-purpose device (particularly a smartphone with an appropriate application or other hardware / software / firmware for acting as a PoS terminal), or it may be a dedicated device for providing PoS functionality to a user when conducting remote transactions. Preferably, the user device includes a card reader (e.g. a chip and pin, a magnetic stripe and / or a short-range communication (NFC etc.) antenna), a display, a memory, a processor, a processor executable program, a power supply, a radio frequency transmitter, a mobile phone antenna or other network connector and means for user input such as a keyboard, a touch screen, a camera and / or a microphone.
[0069] The cryptographic key pair of the user device may be generated within the user device or may be distributed to the user device. The cryptographic key pair may be stored in the user device during manufacturing.
[0070] The user device may communicate via one or more of a cellular network, Bluetooth or other short-range radio frequency communications, the Internet, a local area network, a wireless local area network, a camera embedded in the mobile device, a cable connected to the device, a microphone, or a memory card.
[0071] The payment processing system 80 is preferably arranged to encrypt the transmitted PoS configuration using a public key from the user device profile.
[0072] Preferred embodiments enable a user device to act as a PoS terminal. In preferred embodiments, secure remote transaction processing is enabled, preferably allowing such a temporary merchant profile to be used for the duration of a particular transaction, where the merchant profile is only temporarily assigned and stored in the user device acting as a PoS terminal. When the temporary merchant profile is activated and in use, the user device implements a PoS terminal that acts as a remote PoS terminal for the merchant, where the amount paid will be credited to the merchant's account as described in the temporary profile. Once the particular transaction is completed, the temporary profile will preferably be deleted, so the terminal cannot be used until it receives a new profile and transaction input.
[0073] As will be appreciated, in a preferred embodiment, the buyer is not required to enter his / her payment card information anywhere and, therefore, the card information cannot be used fraudulently.
[0074] The point of sale application 44 may be implemented as discussed in co-pending U.S. Patent Application No. US 61 / 726,121, the contents of which are incorporated herein by reference in their entirety. The application 44 may be implemented in hardware, firmware, software, or some combination thereof, and may reside in a UICC / SIM card. It may conform to the EMV payment card scheme and use a Public Key Infrastructure (PKI) type of secure certificate-based solution.
[0075] The preferred embodiment enables secure online payments using chip cards or mobile wallets. In a preferred embodiment, the PoS application (which may reside in a secure chip card memory or user device) has a smart card reader or proximity communication functionality, such as a near field communication (NFC) card reader interface and network communication capabilities.
[0076] Preferably, security certificates are used based on a Public Key Infrastructure (PKI).Secure key management chain integrity enables creating and maintaining a high security level within the system.
[0077] Security Management
[0078] There are several schemes to manage security. The first is to use merchants, acquiring banks, certification authorities (“CAs”, such as card schemes), and buyers. The second scheme includes merchants, certification authorities (CAs), and buyers. The third scheme also includes a trusted third party that manages and operates the PoS certificate database.
[0079] The user device optionally generates and / or uses a cryptographic key pair via the PoS application; a secure private key and a corresponding public key. The key pair may be dedicated to the PoS application, or may be shared with other applications running in the same processor and / or secure element.
[0080] The user device preferably stores the private key in a secure tamper-proof memory or a secure element. This method ensures that the private key is absolutely confidential and can never be read from outside the secure element or exposed outside the secure element.
[0081] The user device preferably creates or uses a public key certificate (user device profile certificate), issues it and sends it to the external certificate database host (before the first payment transaction). Figure 1 In an embodiment of this, this is the first data repository (or is in communication with the first data repository), such that the credentials are accessible from the first data repository. Optionally, the credentials may be retrieved directly from the user device if the credentials are not stored in the database.
[0082] As described above, a payment processing system (such as a payment service host) may retrieve the credentials for the user's mobile device from a credentials database using the MSISDN or similar unique device or user identification.
[0083] The payment processing system may optionally verify the retrieved user device credentials to determine that the consumer's mobile device has a compatible PoS application and is allowed to conduct the transaction.
[0084] The payment processing system preferably uses the public key from the certificate to partially or fully encrypt the payment information before sending it to the PoS terminal or gateway host.
[0085] The payment processing system may optionally include return routing information (eg, network IP address, server identifier, domain name) in the transmitted PoS profile in order to receive information regarding transaction information (eg, authorization request and completed transaction).
[0086] Preferably, the PoS application on the user's device is able to verify that the merchant's PoS configuration profile it receives is valid and has not been altered. This can be achieved by using a PKI security solution that inherits trust from a public CA. To this end, the CA's public key certificate is usually distributed to the PoS terminal at the time of manufacture, but this can be done at a later stage.
[0087] In both cases prior to the first step, the buyer has already completed the online purchase so the full payment information is known, and the user has selected the option to pay using a mobile device with secure PoS terminal functionality and entered his / her mobile device number.
[0088] The merchant host provides a means for the buyer to enter his or her phone number or other identification, or it forwards the buyer to a payment page at a payment service host for the same purpose. The user identification code may be stored in a cookie or the like on the buyer's computing device and automatically filled in the relevant fields on the payment page. This allows the buyer to use a "one-click purchase" method without having to enter any credit card information at all.
[0089] 1. The buyer selects a payment method using a remote PoS terminal on their mobile device.
[0090] 2. The merchant forwards the payment information to a payment service host, such as one operated by a payment acquirer or payment service provider (PSP).
[0091] 3. The buyer enters their mobile device number (MSISDN) or similar unique identifier on the page hosted by the payment service.
[0092] 4. The payment service host retrieves the user device profile certificate from the certificate database host corresponding to the input from the buyer.
[0093] 5. If the retrieval is successful, the PSP verifies the certificate and determines if the mobile device is equipped with a compatible version of the PoS terminal.
[0094] 6.PSP signs the payment information.
[0095] 7. The PSP encrypts the payment information using the public key of the PoS terminal.
[0096] 8. If the payment information is valid, the PoS will configure its terminal profile according to the instructions received in the payment information during a transaction.
[0097] 9. The PoS presents payment instructions to the user.
[0098] 10. The user can accept the payment or reject it.
[0099] 11. If accepted, payment will be processed according to the relevant method.
[0100] 12. When the payment processing is complete, the PoS terminal will automatically delete its profile and cannot be used again until it receives new payment information.
[0101] Go to Figure 3 and Figure 4 , embodiments of the present invention are shown in transaction flow charts and schematic diagrams. Figure 3 The transaction flow diagram shows a transaction flow in which a merchant sends payment information to a mobile user device executing a PoS application (thus becoming a PoS terminal). Figure 4 The transaction flow diagram of FIG. 1 shows a schematic diagram of the security permission issuance and configuration of a temporary PoS terminal profile without using an acquiring bank. The system includes a merchant device and a certification authority, but does not include an acquiring bank. In an embodiment without an acquiring bank, the following operations may occur:
[0102] 1. The merchant signs the payment information (PI) using its private key.
[0103] 2. The merchant sends the signed PI and the merchant’s public key certificate signed by the CA to the PoS terminal.
[0104] 3. The PoS terminal uses the CA’s public key certificate to verify the merchant’s public key certificate.
[0105] 4. If the merchant’s certificate is valid, the PoS will use it to verify the PI.
[0106] 5. If the PI is valid, the PoS will configure its terminal profile according to the instructions received in the PI during a transaction.
[0107] 6. The PoS presents payment instructions to the user.
[0108] 7. The user can accept the payment or reject it.
[0109] 8. If accepted, payment will be processed according to the relevant method.
[0110] 9. When the payment processing is complete, the PoS terminal will automatically delete its profile and cannot be used again until it receives new payment information.
[0111] There may also be other situations where the same level of security is provided by an unbroken chain of security certificates.
[0112] The selection of these scenarios is invisible to the user. The main difference is in the handling of data traffic to the mobile device, in other words, whether the merchant needs to be able to manage data communications between their system and the various mobile devices, or whether this complexity will be centralized and performed by the acquiring bank.
[0113] Transaction message flow
[0114] Figure 5 Transaction messages are shown with an online consumer who uses a separate terminal to make purchases and a mobile device to make payments. Figure 6 Transaction messages with online consumers using mobile devices to make purchases and payments are shown.
[0115] When ready to pay for a product or service (1), the user can enter his / her mobile device number (2) as the payment card number at the online merchant website. The merchant server will generate payment information with all necessary information about the transaction, including but not limited to: the merchant's PoS terminal profile (such as primary account number and other information), risk management information, payment processing information, information about accepted card types, a list of country codes that allow mobile PoS terminals to perform transactions, a list of country codes that do not allow mobile PoS terminals to perform transactions, the date and time of the purchase, the merchant's name and amount, and the user's mobile device number. The payment invoice will be signed by the merchant's own private key and sent to the acquiring bank (3) which will check the authenticity and integrity of the payment invoice, where the private key is signed by a trusted third party (such as a bank, payment card scheme, certification authority or similar institution). If the payment invoice is valid, the CA will sign the payment invoice using its own private key and send the payment invoice to the secure PoS terminal application (4) at the user's mobile device or in the UICC / SIM card in the mobile device.
[0116] The data transfer function may be performed by a trusted service manager or other trusted third party. The transmission may use any available communication protocol supported by the network and mobile device used and the UICC card that may reside in the mobile device, such as instant messaging, SMS, USSD, TCP / IP or CSD.
[0117] A trusted third party such as a CA or a bank may maintain a database linking account numbers to mobile device numbers.
[0118] The PoS terminal will receive the signed payment invoice and will check the integrity and authenticity of the payment invoice using the public key of the payment card scheme, trusted third party or CA residing in its secure memory.
[0119] The PoS terminal will preferably determine its geographic location using, for example, available network information relating to which country it resides in, and compare the location information to a list of allowed and prohibited country codes. If the PoS terminal's current geographic location is not within an allowed location, or if it is in a prohibited location, the PoS terminal will cancel the transaction, and may notify the user and the bank.
[0120] If the payment information is valid, the PoS terminal will use the information in the payment information to configure itself as if it were a PoS terminal belonging to the merchant.
[0121] The payment information includes the amount to be paid as a fixed amount, which cannot be entered or otherwise modified by the user.
[0122] The user may be notified of pending transactions on the network and asked for permission to proceed with the transaction. The user may cancel or accept the transaction "as is", but the user may not change the amount or any other settings or information associated with the transaction.
[0123] The PoS terminal will display the amount, the name or other identification of the merchant and possibly other transaction related information and ask the user to accept. If the transaction is accepted by the user, the PoS terminal will ask to present the payment card to the card reader. In the case of multiple cards or card readers, the PoS terminal will ask the user to select the card and card reader interface to be used.
[0124] The card reader may be integrated in the PoS terminal / mobile device or it may be an external card reader connected to the PoS terminal / mobile device. The card reader may be contact or contactless.
[0125] Once the payment card communicates with a card reader embedded in or connected to the mobile device (5) to complete the transaction, the user may be asked to provide information known to him / her, such as a secret PIN code (or other authentication such as a signature, picture, voice sample or photo, etc.). The PIN code or other authentication information may be entered, for example, using the mobile device's user interface display, keyboard, camera, voice recognition function, character detection function or motion detection function and fingerprint recognition.
[0126] The transaction between the payment card and the PoS terminal may be, for example, an EMV standard transaction, a contactless payment transaction, a smart card transaction, an embedded payment card transaction, a credit or debit card transaction, a transaction using, for example, an account at a network operator, a prepaid or stored value or a wallet card transaction.
[0127] The payment card may be a physically separate payment card, or it may reside in the same UICC card or in the same mobile device as the PoS terminal. The payment card may reside in a mobile wallet located in a mobile device or a UICC / SIM card. The payment card may reside in the same integrated circuit (IC) as the PoS terminal, or it may be in a separate IC. One or both of these ICs may be embedded in a UICC / SIM card or a mobile device. The IC containing the payment card may be embedded in a mobile device, and the IC containing the PoS terminal may be embedded in a UICC card, or vice versa.
[0128] The UICC card may be a SIM card and / or a secure element.
[0129] If a mobile wallet is used and it contains more than one payment card, the user can select which payment card he / she wants to use.
[0130] The payment transaction will be sent back to the payment acquirer, who will check the validity of the transaction with the card issuer (7-8) and confirm the transaction status to the PoS terminal and the online merchant (9). The online merchant can confirm the transaction status to the consumer (10). If the transaction is successfully completed, the funds will be transferred to the merchant's account.
[0131] If the transaction is not approved, the user can cancel the transaction, or try again using the same or a different payment card or card reader.
[0132] Once a transaction is processed and completed, the merchant-specific configuration and payment information will be permanently deleted.
[0133] The present embodiment enables secure online purchases using an NFC compatible mobile device and a UICC card as a PoS terminal for both the merchant and the buyer.
[0134] The PoS terminal can be any networked PoS terminal.
[0135] The payment service host can also be a software application or hardware implementation in a mobile device or SIM card. In this case, the seller's PoS terminal application in the mobile device or in the SIM card can send its own terminal profile to the buyer's PoS terminal application to carry out a secure financial transaction to be routed from the buyer's account to the seller's account.
[0136] Address Database
[0137] The PoS terminal application, PoS configuration database or PoS terminal public key certificate can maintain a database of one or more street or other physical addresses. The address can be used as a billing and / or delivery address for remote purchase of goods, for example. The address can be combined with information sent to an acquiring bank and / or merchant. The address information can be signed by the PoS terminal using its private key for authentication and encrypted using the public key of the merchant or acquiring bank for security purposes.
[0138] The address database may have fixed addresses that cannot be changed by the user and additional addresses that may be modified by the user.
[0139] An address may be tagged for various purposes, such as "delivery address", "billing address", "home address", "work address", "PoS terminal holder address", etc. If an address is included in the data sent to the acquiring bank and / or merchant, and it is tagged as a "delivery address", the merchant should use that address as the delivery address for the merchandise. If an address is tagged as a "billing address", the merchant should send the invoice associated with the purchase to that address.
[0140] Aspects of the present embodiment may also be implemented as software configured for use with a processor to cause the processor to perform operations, or may be implemented as hardware on one or more connected or unconnected devices.
[0141] While the preferred form and embodiment of the present invention have been shown and described, it will be apparent to those skilled in the art that various changes may be made without departing from the inventive concept described above.
Claims
1. A remote transaction processing system, comprising: a plurality of user devices, each of the plurality of user devices comprising a payment card reader and a secure memory element storing a point of sale (PoS) terminal application; a first data repository comprising a user equipment profile for each user equipment of the plurality of user equipment, each of the user equipment profiles comprising routing data for routing communications to the user equipment; as well as a payment service host including a processor configured to execute computer program code to receive a payment request for each of a plurality of merchants to pay for a transaction initiated at a corresponding merchant site or website, the payment service host being configured to, upon receiving one of the payment requests designating one of the user devices for a corresponding transaction with one of the plurality of merchants, execute program code to retrieve a PoS configuration profile corresponding to the merchant and retrieve from the first data repository a user device profile including routing data corresponding to the designated user device, the payment service host being configured to generate a PoS configuration based on the PoS configuration profile and payment information related to a transaction including an amount, and transmit the generated PoS configuration to the user device using the routing data from the retrieved user device profile, wherein the PoS configuration profile includes instructions for configuring the user device to act as a PoS terminal for the merchant during a one-time transaction for the amount that the user can only accept or cancel, wherein the user device is configured to receive a PoS configuration transmitted from the payment service host for a transaction with a merchant, execute a PoS terminal application in the secure memory element, configure the PoS terminal application according to the received PoS configuration, and communicate with a payment card via the payment card reader to pay for the transaction using the PoS terminal application, thereby acting as a PoS terminal for the merchant on the user device for the transaction with the merchant, The PoS terminal application is configured to delete the PoS configuration from the user device after the transaction so that the user device no longer acts as a PoS terminal for conducting transactions with the merchant.
2. The system according to claim 1, wherein: Each of the user device profiles includes a public key of a cryptographic key pair of a user device, the remote transaction processing system being configured to encrypt the transmitted PoS configuration using the public key.
3. The system according to claim 1, wherein: The routing data includes a plurality of routes for communicating with a user device, and the remote transaction processing system is configured to determine a route for communicating with the user device from among the plurality of routes.
4. The system according to claim 3, wherein: The routes in the routing data are ordered, and the remote transaction processing system is configured to identify a route to a user device based on the ordering.
5. The system according to claim 3, wherein: The routing includes routing to communicate with user equipment through different channels.
6. The system according to claim 5, wherein: The channel is selected from the group consisting of: Short Message Service SMS, Instant Messaging, communications to a predetermined address on a data communications network, and data calls through the communications network.
7. The system of claim 1 , further comprising a second data repository comprising a PoS configuration profile for each of the plurality of merchants, the remote transaction processing system being configured to retrieve the PoS configuration profile for the merchant from the second data repository, in, The second data store includes a PoS certificate associated with a respective merchant, the PoS certificate including a PoS configuration profile of the respective merchant.
8. The system according to claim 1, wherein: The first data storage repository is remote from the user device.
9. The system according to claim 1 further includes a merchant website, the merchant website includes a payment user interface, the payment user interface is configured to receive an identifier of a user device profile specified to be used for payment from a user, and the remote transaction processing system is configured to retrieve the user device profile based on the identifier.
10. The system according to claim 1, wherein: The PoS terminal application on the user device is configured to verify that the PoS configuration profile corresponding to the merchant has not been altered.
11. A remote transaction processing method, comprising: receiving, at a payment service host, from a merchant website of one of a plurality of merchants, a payment request specifying a user device for conducting a transaction with the merchant, the user device comprising a payment card reader and a secure memory element in which a PoS terminal application is executable by the user device; Retrieving, by the payment service host, a point of sale (PoS) configuration profile corresponding to the merchant; retrieving, by the payment service host, a user device profile corresponding to the specified user device from a first data repository storing user device profiles, the user device profile including routing data for routing communications to the user device; generating a PoS configuration based on the PoS configuration profile and payment information related to a transaction including an amount, wherein the PoS configuration profile includes instructions for configuring the user device to act as a PoS terminal for the merchant during a one-time transaction for the amount that the user can only accept or cancel; and transmitting the generated PoS configuration to the user device using routing data from the retrieved user device profile, wherein the user device is configured to receive and use a PoS configuration profile transmitted from the payment service host for transactions with merchants to enable the user device to act as a PoS terminal and accept card payments via the payment card reader, The PoS terminal application is configured to delete the PoS configuration from the user device after the transaction so that the user device no longer acts as a PoS terminal for conducting transactions with the merchant.
12. The method according to claim 11, further comprising: associating a cryptographic certificate with a user device profile, the certificate comprising a public key of a public and private key pair; encrypting at least some aspects of the PoS configuration using the public key; and The encrypted PoS configuration is decrypted at the user device using the private key of the public and private key pair.
13. The method according to claim 12, further comprising: storing the cryptographic credentials in a data repository, Wherein, retrieving the user equipment profile includes retrieving the certificate.
14. The method according to claim 11, wherein: Generating the PoS configuration includes signing the PoS configuration using a private key of a private / public cryptographic key pair.
15. The method according to claim 11, further comprising performing the following operations at the user equipment: Card payment transactions are carried out by PoS terminals at user devices, Sign the payment transaction data at the PoS terminal, Encrypt the signed payment transaction data at the POS terminal, The PoS terminal sends the encrypted and signed payment transaction data to the payment service host, and The payment information is deleted from the PoS terminal memory by the PoS terminal.
