Processing payments

By designing a payment terminal that can output multiple communication protocol signals, the problems of payment terminal deployment complexity and Internet connection dependence in the prior art are solved, and the flexibility and reliability of payment without relying on the Internet are realized.

CN110869959BActive Publication Date: 2024-11-29GP NETWORK ASIA PTE LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN201880044621.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2018-07-02
Publication Date
2024-11-29
Estimated Expiration
2038-07-02

AI Technical Summary

Technical Problem

Existing payment terminals require the deployment of multiple types of terminals to support different types of digital payments, and users may not be able to continuously connect to the Internet in some areas, limiting the use of mobile devices in cashless electronic transactions.

Method used

Design a payment terminal that can output signals of two communication protocols (such as NFC and Bluetooth signals), and select a communication method for communication based on the received response, establish a communication channel with external payment devices, ensuring that it does not depend on it. Payment under the Internet.

Benefits of technology

The possibility of payment through mobile devices or payment cards without an Internet connection is realized, simplifying the deployment of merchant terminals, and improving payment flexibility and reliability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN110869959B_ABST
    Figure CN110869959B_ABST
Patent Text Reader

Abstract

A method of operating a payment terminal, the method comprising: receiving an activation input, and in response thereto, outputting a first wireless signal for communicating with a first type of external payment device, and a second wireless signal for communicating with a second type of external payment device. The first wireless signal and the second wireless signal are formatted in a first protocol and a second protocol that are different from each other. The method further comprises: receiving a response to one of the first wireless signal and the second wireless signal, and in response to the response, terminating output of the other of the first wireless signal and the second wireless signal.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The invention belongs to the technical field of payment. Background Art

[0002] Cashless payments are becoming more and more frequently used, mainly due to convenience. Such payments may involve cards or mobile phones. Internet connectivity is a limitation when using mobile phones for cashless electronic transactions.

[0003] Even as the reach of the Internet expands, there is no certainty that users of mobile devices will always be connected to the Internet. Also, for large parts of society in some parts of the world, Internet access may not be affordable. In such cases, completing electronic transactions via mobile phones may not be feasible.

[0004] In addition, merchants may typically have to deploy different types of payment terminals to support different types of digital payments. For example, merchants may have to deploy a certain payment terminal to accept payment using a card. Additionally, merchants may have to deploy another terminal to support payment via mobile phones. Even if such additional terminals are deployed, the terminals may only support mobile phones that use a specific type of communication technology (such as NFC).

[0005] There is a need to improve this situation. Summary of the invention

[0006] In a first aspect, a payment terminal is used to output signals corresponding to two communication protocols or methods so that communication can be performed when a device capable of responding to one of the two protocols or methods is close to the terminal.

[0007] In a second aspect, there is provided a payment terminal capable of communicating using two different communication methods. In use, the payment terminal outputs signals related to the two methods to initiate communication with a payment device such as a mobile phone or a payment card via one of the two methods. When communication is established via one of the two methods, the other method is terminated.

[0008] In a third aspect, a method for operating a payment terminal is provided, the method comprising: receiving an activation input, and in response thereto, outputting a first wireless signal for communicating with a first type of external payment device, and a second wireless signal for communicating with a second type of external payment device, wherein the first wireless signal and the second wireless signal are formatted with respective first and second protocols that are different from each other to receive a response to one of the first wireless signal and the second wireless signal, and in response to the response, terminating the output of the other of the first wireless signal and the second wireless signal.

[0009] The method may further include processing the response to authenticate the external payment device, thereby establishing a communication channel.

[0010] The method may further include processing the response to authenticate the external payment device and performing the terminating step after the processing step.

[0011] The wireless signal may include an NFC signal and a Bluetooth signal.

[0012] The method may further include: processing the response to authenticate the external payment device to establish a communication channel, and receiving data indicating a user from the communication channel; receiving data indicating a transaction amount at an input, and transmitting the data indicating a user and the data indicating a transaction amount to a server.

[0013] The method may further include: processing the response to authenticate the external payment device to establish a communication channel, and receiving data indicating the user and a one-time verification code for identifying the current transaction from the communication channel; receiving data indicating the transaction amount at the input, and transmitting the data indicating the user, the data indicating the one-time verification code, and the data indicating the transaction amount to a server.

[0014] The method may further include outputting a new one-time verification code via the communication channel.

[0015] The method may further include communicating with a server information indicating which of the first wireless signal and the second wireless signal to respond to.

[0016] In a fourth aspect, a payment terminal for wirelessly communicating with an external device is disclosed, the payment terminal having a processing device and a storage device, the storage device storing instructions for controlling the processing device so that the payment terminal outputs a first wireless signal for communicating with a first type of external payment device and a second wireless signal for communicating with a second type of external payment device in response to an activation input, wherein the first wireless signal and the second wireless signal are formatted with respective first and second protocols that are different from each other, and in response to receiving a response to one of the first wireless signal and the second wireless signal, output of the other of the first wireless signal and the second wireless signal is terminated.

[0017] The payment terminal may further include: a keypad for providing an activation signal; a display for displaying information under the control of the processing device; and an output device for communicating with a server.

[0018] The payment terminal may further include: a first wireless device configured to output the first wireless signal under the control of the processing device, and a second wireless device configured to output the second wireless signal under the control of the processing device.

[0019] The payment terminal may further comprise a security device comprising storage means for a security key, the security device being configured to use the key to encrypt or decrypt data for use by the terminal.

[0020] The personal area network device may be configured to output a first wireless signal.

[0021] The near field communication device may be configured to output a second wireless signal.

[0022] In a fifth aspect, a system for processing payments is provided. The system includes a payment terminal, the payment terminal including a first wireless communication module and a second wireless communication module. The first module is capable of initiating and establishing proximity communication using a first communication method that is different from the second communication method. The second module is capable of initiating and establishing proximity communication using the second communication method. The payment terminal is configured to: receive input for initiating a transaction; cause the first module and the second module to attempt to initiate communication using their respective methods. An external entity capable of communicating with it via one of the first method and the second method can be in proximity to the payment terminal such that communication can be initiated between the payment terminal and the external entity depending on which communication module succeeds.

[0023] The first wireless communication module may be a personal area network module. The second wireless communication module may be a near field communication module. The payment terminal may be further configured to terminate attempts to establish a communication channel with any other external entity using the first wireless communication module and the second wireless communication module until the transaction is completed. The external entity may be one of a card and a portable communication device, wherein the payment terminal may be further configured to identify whether the established communication is with one of a near field communication tag of the card, a near field communication module of the portable communication device, or a personal area network module of the portable communication device. The payment terminal may be further configured to communicate to a server whether the established communication is with one of a near field communication tag of the card, a near field communication module of the portable communication device, or a personal area network module of the portable communication device. The external entity may be a portable communication device, wherein the payment terminal may be configured to: before establishing communication with the portable communication device, at least receive data identifying a user attempting to make a payment associated with the transaction; and communicate at least data identifying the user, data identifying the merchant, and data identifying the payment amount to a server to process the transaction, thereby enabling the portable communication device to make a payment without using the Internet. The payment terminal may be further configured to: receive location verification data from the external entity; based on the location verification data, verify whether the payment terminal can be used to accept payment; and reject the transaction if it is confirmed that the payment cannot be accepted, or process the transaction if it is confirmed that the payment can be accepted. The external entity may be a card with which near field communication can be established, and the payment terminal is configured to: read data identifying the user and data to be used as a one-time verification code from the card; write a new one-time verification code into the card; and communicate the data identifying the user and the data to be used as the one-time verification code to a server, wherein the one-time verification code is used to verify whether the one-time verification code is the verification code expected by the card for the current transaction, so as to reject the transaction or continue the transaction. The payment terminal may be further configured to communicate a unique one-time verification code to the server for each transaction, wherein the one-time verification code can be used to verify whether the one-time verification code is the verification code expected by the payment terminal for the current transaction, so as to reject the transaction or continue the transaction. The external entity may be a portable communication device, and the payment terminal may be configured to: receive data identifying a user and data to be used as a one-time verification code from the portable communication device; update a new one-time verification code in the portable communication device; and communicate the data identifying the user and the data to be used as the one-time verification code to a server, wherein the one-time verification code is used to verify whether the one-time verification code is the verification code expected by the portable communication device for the current transaction, so as to reject the transaction or continue the transaction.

[0024] In another aspect, a method for processing a payment is provided. The method includes receiving an input for initiating a transaction at a payment terminal. Thereafter, a first wireless communication module and a second wireless communication module disposed in the payment terminal attempt to establish a communication channel with an external entity. The first wireless communication module is capable of establishing proximity communication using a first communication channel that is different from a second communication channel that the second wireless communication module is capable of establishing. The method further includes: using one of the communication modules to establish a communication channel with the external entity based on which of the first wireless communication module and the second wireless communication module successfully establishes the communication channel with the external entity.

[0025] In yet another aspect, a system for processing payments is provided. The system includes a payment terminal, the payment terminal including a personal area network (PAN) module. The payment terminal is configured to cause the PAN module to propagate an identifier. The system further includes a portable communication device. The device is configured to: receive the identifier propagated by the payment terminal; if the signal strength of the propagated identifier exceeds a first threshold, automatically send a request to establish a communication channel with the PAN module of the payment terminal; and once the communication channel is established, even if the signal strength between the device and the PAN module of the payment terminal drops below the first threshold, continue to maintain communication with the PAN module of the payment terminal until the transaction is completed.

[0026] In still another aspect, a method for processing payment is provided. The method includes: broadcasting an identifier by a personal area network module of a payment terminal; receiving the identifier broadcasted by the payment terminal by a portable communication device; and automatically sending a request to establish a communication channel with the personal area network module of the payment terminal by the portable communication device if the signal strength of the broadcasted identifier exceeds a first threshold. The method further includes: once the communication channel is established, even if the signal strength between the portable communication device and the personal area network module of the payment terminal drops below the first threshold, maintaining the communication between the portable communication device and the personal area network module of the payment terminal until the transaction is completed.

[0027] Also disclosed is a system for processing payments, the system comprising: a payment terminal including a personal area network module, wherein the payment terminal is configured to cause the personal area network module to broadcast an identifier; and a portable communication device, which is configured to: receive the identifier broadcast by the payment terminal; automatically send a request to establish a communication channel with the personal area network module of the payment terminal if the signal strength of the broadcasted identifier exceeds a first threshold; and, once the communication channel is established, continue to maintain communication with the personal area network module of the payment terminal even if the signal strength between the portable communication device and the personal area network module of the payment terminal drops below the first threshold until the transaction is completed.

[0028] The first threshold may be configured such that the portable communication device and the payment terminal are within 20 centimeters of each other to establish a communication channel. The first threshold may be configured such that the portable communication device and the payment terminal are within 10 centimeters of each other to establish a communication channel.

[0029] The first threshold may be configured such that the portable communication device and the payment terminal are within a preconfigured distance of each other to establish a communication channel.

[0030] If the signal strength between the portable communication device and the personal area network module of the payment terminal drops below a second threshold, at least one of the payment terminal or the portable communication device may be configured to terminate the established communication channel.

[0031] The second threshold may be remotely reconfigurable.

[0032] The payment terminal may be configured to: before establishing a communication channel, at least receive data identifying a user attempting to make a payment associated with a transaction; and communicate at least the data identifying the user, the data identifying the merchant, and the data identifying the payment amount to a server to process the transaction, thereby enabling the portable communication device to make payments without using the Internet.

[0033] The payment terminal may be further configured to: receive data corresponding to an account balance of a user using the portable communication device to make payments from a server; and communicate the data corresponding to the account balance to the portable communication device via the communication channel.

[0034] The payment terminal may be further configured to: receive data corresponding to transaction information from a server; and communicate at least a portion of the data corresponding to the transaction information to the portable communication device via the communication channel.

[0035] The payment terminal may be unable to display the user's account balance; and the portable communication device is configured to display the user's account balance after the transaction.

[0036] The identifier may include data identifying compatibility, wherein if the identifier received by the portable communication device includes data identifying compatibility, the portable communication device is configured to automatically request establishment of a communication channel with respect to the payment terminal.

[0037] The payment terminal can be configured to: receive input indicating an amount to be transferred; after receiving the input indicating the amount, receive input for starting to broadcast an identifier; and once a communication channel is established, communicate data corresponding to the amount and a merchant connected to the payment terminal to the portable communication device, wherein the amount and information corresponding to the merchant are displayed on the portable communication device.

[0038] The first threshold may be remotely reconfigurable.

[0039] The personal area network module can be a Bluetooth low energy module or a Bluetooth module.

[0040] A method for processing payment is also disclosed, the method comprising: broadcasting an identifier by a personal area network module of a payment terminal; receiving the identifier broadcast by the payment terminal by a portable communication device; if the signal strength of the broadcast identifier exceeds a first threshold, automatically sending a request by the portable communication device to establish a communication channel with the personal area network module of the payment terminal; and once the communication channel is established, maintaining communication between the portable communication device and the personal area network module of the payment terminal until the transaction is completed, even if the signal strength between the portable communication device and the personal area network module of the payment terminal drops below the first threshold. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In each figure:

[0042] Figure 1 A system 100 for processing payments is shown;

[0043] Figure 2 is a block diagram of a payment terminal 102 of the system 100;

[0044] FIG. 3A to FIG. 3F is a flow chart of an exemplary method of processing payments by system 100;

[0045] Figure 4A shows the amount entered into the payment terminal 102,

[0046] Figure 4Bshows a user interface of an application of smart phone 104b opened by a user to make a payment;

[0047] Figure 4C A user interface of a smartphone 104b searching for an application for a payment terminal 102 is shown;

[0048] Figure 4D shows the smart phone 104b being paired with the payment terminal 102 via the BLE channel after the smart phone 104b is brought into proximity with the payment terminal 102;

[0049] Figure 4E The user interface of the application of the smart phone 104b is shown, wherein the user is providing input to approve the payment;

[0050] Figure 4F showing a user interface of an application on smartphone 104b showing a transaction being processed;

[0051] Figure 4G The user interface of the application of the smart phone 104b is shown, wherein the transaction information is displayed after a successful transaction;

[0052] Figure 5A A highly schematic diagram of an exemplary transaction grouping is shown;

[0053] Figure 5B Another transaction grouping is shown; and

[0054] Figure 6 A schematic diagram of an embodiment of a payment terminal is shown, illustrating how certain connections to the payment terminal may be performed. DETAILED DESCRIPTION

[0055] In the following description, reference to a phone or smartphone is not intended to be limited to a particular type of portable communication device; these terms are used for convenience and are intended to cover any type of portable communication device.

[0056] A system is disclosed that can process payments without requiring the user making the payment to use the Internet. For example, payments can be made using a card that supports Near Field Communication (NFC) or a smartphone with NFC or Bluetooth Low Energy (BLE) technology.

[0057] Payment is facilitated by a payment terminal deployed at a merchant location. The payment terminal may include a personal area network module (BLE module) and an NFC module. In an embodiment, when initiating a transaction, the payment terminal is configured to attempt to use both BLE and NFC to initiate communication with an external entity given by a consumer / user to make a payment. The external entity may be an NFC-enabled card, or a smartphone with NFC or Bluetooth Low Energy (BLE) technology, in which an application for conducting transactions with the payment terminal is installed.

[0058] In another embodiment, the transaction terminal is configured to try one of BLE and NFC for a period of time, and then if unsuccessful try the other of BLE and NFC, and repeat trying BLE and NFC again and again if necessary.

[0059] In an embodiment, once the payment terminal successfully establishes a communication channel with an external entity via one of BLE and NFC, the payment terminal is configured to disable (attempts to establish communication with any other external entity) the other technology until the initiated transaction is concluded.

[0060] In another embodiment, the payment terminal stops transmitting one of the two outputs once it detects a signal return from the other of the two outputs. This can save battery power in battery-powered terminals.

[0061] In an embodiment, a communication channel with a payment terminal is established via NFC, where the user brings a card or NFC-enabled smartphone near the payment terminal. The payment terminal reads the data from the card / NFC module of the phone and communicates the data to a backend server to process the initiated payment transaction. Note that the merchant is not instructing the payment terminal which communication means to use, but rather the payment terminal automatically decides on its own.

[0062] In an embodiment, a communication channel with a payment terminal is established via BLE, wherein the user brings a BLE-enabled smartphone near the payment terminal. The payment terminal receives data from the phone's BLE module and communicates the data to a backend server to process the initiated payment transaction. Note that even in this case, the merchant is not instructing the payment terminal which communication means to use, but rather the payment terminal automatically decides on its own.

[0063] In the case of BLE, the payment terminal communicates transaction information (such as the amount deducted and the balance in the user's account) (received from the backend server) to the user's smartphone through a communication channel established via BLE. Thus, the user is not only able to make payments without using the Internet or relying on SMS or similar alternatives, but also gets updates about transactions and accounts.

[0064] refer to Figure 1 , a system 100 for processing payments has a payment terminal 102 that can receive payments via external entities such as NFC-enabled cards 104a and portable communication devices 104b. The payment terminal 102 in use communicates with a server 106 via a communication network 108.

[0065] The payment terminal 102 may be, for example, a card reader, a smart phone, a POS system, a tablet, a tablet phone, a computer and a laptop, among other computing devices.

[0066] Reference now Figure 2 , an embodiment of the payment terminal 102 includes a processing module 202, a memory module 204, an input module 206, an output module 208, a WIFI module 210, a communication module 212, a security module 213, a first wireless communication module 214, and a second wireless communication module 216. The memory module 204 is connected to a bus, which connects it to the processor module 202. The processing module 202 is connected to all other modules through the bus 123. The processing module 202 operates under the control of executable instructions stored in the memory module 204 to perform the functions of the payment terminal 102, and usually calls other modules of the device to perform the functions of these modules.

[0067] Reference now Figure 6 , in this embodiment, the input module 206 is connected to a keypad 601 and a stylus 603. The output module 208 is connected to a display screen 605 and a printer 607. The WiFi module is shown as being connected to the server 106 via a wireless link, and the communication module 212 is shown as being connected to the server 106 via a wired link. It will be understood that in use only one of the links to the server 106 may be employed. The first wireless communication module 214 is connected to an NFC antenna, and the second wireless communication module is connected to a Bluetooth antenna 611. In some embodiments, the antennas are integral to the respective wireless communication modules.

[0068] return Figure 2 The processing module 202 is implemented in the form of one or more processors and can be appropriately implemented in hardware, computer executable instructions, firmware, or a combination thereof. The computer executable instruction implementation or firmware implementation of the processing module 202 can include computer executable or machine executable instructions written in any suitable programming language for performing the various functions described.

[0069] In an embodiment, the memory module 204 includes a permanent memory, such as a hard drive, eMMC, SSD or EEPROM. The memory module can be configured to store data and executable program instructions implemented by the processor 202. The memory module 204 can be implemented in the form of a main memory and a secondary memory, wherein the main memory is a hard-wired memory and the secondary memory is a removable memory (such as an SD card). The memory module 204 can store additional data and program instructions that can be loaded and executed on the processor 202, and data generated during the execution of these programs. In addition, the memory module 204 can be a volatile memory (such as a random access memory and / or a disk drive) or a non-volatile memory. The memory module 204 may include a removable memory, such as a compact flash card, a memory stick, a smart media, a multimedia card, a secure digital memory or any other memory storage.

[0070] In the currently described embodiment, input module 206 provides an interface for input devices (such as a keypad, touch screen, mouse, microphone, stylus and other input devices). Output module 208 provides an interface for output devices (such as a display screen, speaker, printer and tactile feedback device, etc.).

[0071] In the presently described embodiment, the input module 206 and the output module 208 are also used to exchange data between the payment terminal 102 and the server 106 , data obtained by the terminal from the NFC-enabled card 104a , the portable communication device 104b .

[0072] In one embodiment, the payment terminal 102 communicates with the server 106 via the communication network 108 using a WIFI module.

[0073] In one embodiment, the payment terminal 102 uses the communication module 212 to communicate with the server 106 via the communication network 108. In one embodiment, the communication module 212 is a GPRS module. In other embodiments, other modules that enable remote communication are used.

[0074] In an embodiment, the communication module 212 includes a modem, a network interface card (such as an Ethernet card), a communication port or a Personal Computer Memory Card International Association (PCMCIA) slot, etc. In one embodiment, the communication module 212 includes a device that supports both wired and wireless protocols. In one embodiment, data in the form of electronic signals is transmitted via the communication module 212. In other embodiments, one or more of electromagnetic signals, optical signals, and other signals are used.

[0075] In an embodiment, the payment terminal uses a digital key to encrypt, decrypt and authenticate data exchanged between the terminal 102 and the external entity 104. In this embodiment, the key is kept in a security module 213. This security module contains all the keys to be used by the device and is a one-time write-only device. The key is written into the security module 213 in a secure environment. The security module 213 is designed so that the key cannot be read directly from the module. When encryption is required, the data is sent to the security module 213, which returns the encrypted data after processing it using the key. The key cannot be accessed directly from the security module 213, thereby ensuring the security of the key. Similarly, in order to decrypt the data, the data is sent to the security module 213, which processes the data using the key to return the decrypted data.

[0076] The security module 213 may be deployed in the form of software, firmware, hardware, or a combination thereof.

[0077] In an embodiment, the first wireless communication module 214 is a personal area network module (hereinafter referred to as a PAN module). In the embodiment currently described, the PAN module is a Bluetooth low energy (BLE) module. In other embodiments, a technology similar to BLE in the current context can be used.

[0078] In an embodiment, the second wireless communication module 216 is a near field communication module (hereinafter referred to as an NFC module). In other embodiments, a technology similar to NFC in the present context may be used.

[0079] Thus, it may be noted that the payment terminal 102 has a first wireless communication module 214 capable of establishing proximity communication with an external entity 104 using a first communication channel or protocol (e.g., BLE) that is different from a second communication channel or protocol (e.g., NFC) that the second wireless communication module 216 is capable of establishing.

[0080] Now we will give some information about Figure 2 and Figure 6 A high level description of an embodiment of a payment terminal in operation.

[0081] Initially, the processor of the processing module 202 is in an idle state, and in this embodiment, the two wireless communication modules 214, 216 are also idle. The terminal is "awakened" by an input from the keypad 601 to its input module 206, which interrupts the idle process of the processing module 202 via the bus 123. The processing module obtains instructions from the memory module 204 via the bus 123 and processes the instructions to provide outputs to the first wireless communication module 214 and the second wireless communication module 216 via the bus 123, and the two wireless communication modules thus start to transmit their respective inquiry signals (i.e., BLE signals and NFC signals, respectively) to find the external device 104. The inquiry signals are sent via the corresponding antennas 609, 611.

[0082] When one of the two antennas 609, 611 receives a response to one of the two inquiry signals, the corresponding wireless communication module calls the processing module 202 through the bus 123, and based on the instructions stored in the memory module 204, the processing module 202 instructs the other corresponding wireless communication module to stop transmitting its inquiry signal. For simplicity, it is assumed that the first wireless communication module (BLE module 214) receives a response, and therefore the second wireless communication module 216 is instructed to enter an idle state.

[0083] Data received from the external device 104 via the antenna 609 is passed along the bus 123 to the security module 213, which decrypts the data using a digital key stored in the security module under the control of the processing module 202, as described elsewhere in this document. This enables the payment terminal to authenticate the external device 104 (e.g., a phone application or a card). Where appropriate, and after authentication is performed, some information is sent to the screen 605 for display, such as instructing the user / merchant to perform an operation such as "enter amount", "enter personal identification number", etc.

[0084] The input module 206 receives responses to any such instructions, for example, input to the keypad 601. This is then processed by the processing module 202, and depending on the results of the processing, more information is displayed on the screen 605 to facilitate further instruction and response rounds, or the transaction information is sufficient to be sent to the server 106.

[0085] When appropriate, the processing module 202 instructs one of the WiFi module 210 and the communication module 212 to interact with the server 106 based on the data received and processed by the terminal 102 .

[0086] In response to the data received from the terminal 102, the server 106 returns the data via one of the WiFi module 210 and the communication module 212. The data is processed by the processing module 202 via the bus 123, and information derived from the data is displayed on the display screen 605 and / or the printer 607 via the output module 208, where appropriate.

[0087] At the end of the transaction, the processing module returns to its idle state.

[0088] At some time during the transaction process, terminal 102 may send data to external device 104, typically such data encrypted by a key stored in security module 213. As described elsewhere, the data sent to the external device may include, for example, a one-time code for security purposes.

[0089] exist FIG. 3A to FIG. 3F In the present invention, tasks performed by a payment terminal 102, an external entity 104 (in some cases, the types of external entities 104a, 104b are referred to as external entities 104 to facilitate easier reading of this document) and a server 106 are discussed.

[0090] At step 302, the payment terminal 102 receives input indicating an amount to be charged. As an example, the merchant uses a physical or numeric keypad disposed in or on the payment terminal 102 to receive input indicating an amount to be charged. As an example, refer to Figure 4A , the Merchant enters the amount Rs.350 that the Merchant intends to receive from the User / Customer.

[0091] At step 304, the payment terminal 102 receives input for initiating a transaction with the external entity 104. As an example, referring again to Figure 4A After entering the amount, the user of the payment terminal 102 presses the return key to provide an immediate input. It can be noted that pressing the return key can be interpreted as a confirmation of the amount discussed in the previous step and the input discussed in the current step.

[0092] At step 306, in response to the initiation input, the payment terminal 102 (e.g., the processing module 202 of the payment terminal 102) causes the first wireless communication module 214 (hereinafter referred to as the BLE module 214, to facilitate easier reading of this document) and the second wireless communication module 216 (hereinafter referred to as the NFC module 216, to facilitate easier reading of this document) to attempt to establish communication with the external entity 104. As an example, both modules 214, 216 may be turned on in response to the initiation input, and thereafter attempt to establish a communication channel. Alternatively, both modules 214, 216 may already be turned on (but in a "sleep" or "power saving" mode), but in this case, begin attempting to initiate and thereby establish a communication channel with the external entity 104.

[0093] At step 308, both the BLE module 214 and the NFC module 216 attempt to establish a communication channel. As an example, in the case of the BLE module 214, the BLE module 214 may begin broadcasting its identifier. On the other hand, in the case of the NFC module 216, the NFC module 216 generates an electromagnetic field. It may be noted that the merchant does not specify which of the modules 214, 216 should be used, but rather the payment terminal 102 is configured to attempt to establish a communication channel using both modules 214, 216, and to establish a communication channel via one of the appropriate modules 214, 216 after authentication when appropriate.

[0094] refer to Figure 3B In step 310 of the embodiment, it can be noted that although it appears as if the external entity 104 is deciding whether the external entity 104 supports NFC or supports BLE, it will be well understood that step 310 is given for the purpose of explanation only. It will be understood that, as previously discussed, the external entity 104 can be an NFC-enabled card 104a (such as a credit card, debit card, purchase card, corporate card, or meal card) or a portable communication device 104b (e.g., a smart phone) having one or more of a BLE function or an NFC function. Later, we will discuss the transaction flow in the case of a portable communication device 104b that supports BLE. Now we discuss the scenario where the external entity 104 is a NFC-enabled card 104a or a NFC-enabled portable communication device 104b. It can be noted that in the case of a portable communication device 104b that has NFC and BLE functions, which of these functions should be used can be defined by the default application settings, user-defined settings in the application, or the availability of a module.

[0095] Referring to step 312, the external entity 104 is brought into close proximity with the payment terminal 102 for detection. As an example, once the merchant has prepared the payment terminal 102 to accept payment, the user / customer may bring the NFC card 104a or NFC device 104b into close proximity with the payment terminal 102 (to the extent required by NFC).

[0096] By way of explanation, in some embodiments, the NFC card / device 104a, 104b carries encrypted data so that only the payment terminal 102 of this embodiment can correctly interact with the NFC card / device of this embodiment. This causes a phenomenon known as "locking" the card / device.

[0097] Referring to step 314, the payment terminal 102 detects and attempts to unlock the external entity by authenticating the external entity 104. Once the authentication is successfully performed, the communication channel is established; that is, transaction data is sent only after the authentication is successful.

[0098] Therefore, after detecting the NFC card 104a or the NFC device 104b, the payment terminal 102 has established a communication channel with the external entity 104 using one of the first wireless communication module 214 and the second wireless communication module 216 based on which of the first wireless communication module 214 and the second wireless communication module 216 successfully initiated a communication channel with the external entity 104. In this case, the payment terminal 102 has established a communication channel with the external entity 104 using the second wireless communication module 216 (NFC module 216). Therefore, the communication channel thus established can be referred to as an NFC channel.

[0099] In this embodiment, upon receiving a response to one of the BLE signal and the NFC signal, the payment terminal 102 terminates any attempt to establish a communication channel with any other external entity using the first wireless communication module 214 and the second wireless communication module 216 until the transaction is completed.

[0100] In another embodiment, when establishing a communication channel, the payment terminal not only receives a response to an output signal from the payment terminal, but also authenticates the external device so that data communication can begin, and the payment terminal terminates further output of other unresponsive communication modules until the current transaction is completed.

[0101] Using the established NFC channel, the payment terminal 102 coordinates with the external entity 104 to unlock the external entity 104. Known (or potentially developed in the future) security techniques deployed at the card / device level and at the payment terminal 102 may be used to unlock the NFC card 104a or NFC device 104b. In the event that the payment terminal 102 fails to unlock, in this embodiment, the transaction is then terminated (transaction end).

[0102] Referring to step 316, once unlocking is successful, the payment terminal 102 reads the user token from the card memory. The user token is data similar to the card number on a credit card that is used to identify the user attempting to make a payment associated with the transaction.

[0103] In one embodiment, in addition to reading the user token, the external entity 104 also stores data used as a one-time verification code. In this embodiment, the payment terminal 102 also reads the stored one-time verification code to improve security.

[0104] The one-time verification code may be understood as data that is unique for each transaction attempted. It may also be noted that, in the case of the NFC card 104a, a new one-time verification code may be written to the card 104a each time the payment terminal 102 reads an existing one-time verification code to process a transaction. It may also be noted that some smartphones may not allow this data to be written to their NFC module, in which case the provision for a one-time verification code implemented in the above example may not be provided.

[0105] As an explanation, refer to Figure 5A , a transaction data packet 500 typically contains a customer token 501, a customer identifier 503, a transaction amount 505, and a merchant ID 507. If a hacker is able to listen to the data while a user is paying or attempting to pay a bill on a terminal, the hacker may be able to pay the same amount multiple times on the same terminal. This is sometimes called a "replay attack." Therefore, it is desirable to distinguish legitimate transactions from replay attacks.

[0106] In this embodiment, there are safety mechanisms in place for detecting "replay attacks". In a replay attack, a hacker listens to data being exchanged between two devices and then replays the data multiple times. In order for the system to detect and flag such attacks, it is necessary to introduce something fresh into the data packets each time. In this embodiment, see Figure 5B This is accomplished by one or both of the following operations: a) maintaining and incrementing a counter on the card after each transaction, and b) sending a timestamp on the payment device as part of the data packet.

[0107] Thus, the packet 520 of this embodiment includes not only the customer token 501, customer identifier 503, transaction amount 505 and merchant ID 507, but also the counter number 509 stored on the card / device and the timestamp 511 of the transaction.

[0108] In an embodiment, the data read from the NFC card 104a or the NFC module of the mobile device 104b (or the data communicated via BLE) includes data that enables the payment terminal 102 to identify whether the data it is collecting is from the NFC card 104a or the NFC module of the mobile device 104b (or via the BLE of the mobile device). Therefore, the payment terminal 102 (or the server 106, or both) can identify whether the communication established is with one of the near field communication tag of the card 104a, the near field communication module of the portable communication device 104b, or the personal area network module 214 of the portable communication device 104b. It can be noted that this provision enables the server 106 to establish the data set required to process the transaction. As an example, in the case of the NFC card 104a, a one-time verification code is required, while in the case of the NFC module from the mobile device 104b, a one-time verification code may not be required (due to the constraints discussed above) to process the transaction.

[0109] In an embodiment, the data read from the NFC card / device 104a, 104b or received via BLE includes location verification data. In other words, the payment terminal 102 receives location verification data from the external entity 104. The location verification data is used to verify whether the payment terminal 102 can be used to accept payment.

[0110] In one embodiment, the data is written to an external entity 104 (e.g., card 104a), and the terminal is set to reject cards carrying that code unless it is the case that the terminal is located at the location of concern. In a completely closed corporate payment environment (such as a company cafeteria), the payment device is expected to accept payments only from one (or more) companies, and the billing is completed locally at the payment device level itself. If the device does not find a customer card containing a specific identifier (identifying the company), the transaction is immediately rejected. No server call is required.

[0111] In the event that it is determined that the payment cannot be accepted, the transaction is rejected. On the other hand, if it is verified that the payment can be accepted, the transaction is processed. The verification in question can be performed by the payment terminal 102.

[0112] Alternatively, verification may be performed by server 106 or both.

[0113] In other cases where the payment device is located in general retail, billing occurs at the server 106. The customer identifier is also part of the data packet sent to the server. A rule is set up on the back end that prohibits customers with a specific customer identifier from making payments at a certain location (e.g., a location identified by merchant ID 507, which will be recalled and is also part of the transaction data packet).

[0114] As an example of implementation, a company may have issued NFC cards 104a to its employees for use in food and beverage areas deployed within the employee's campus. In the case of using card 104a to pay at a payment terminal 102 outside the campus, the payment terminal 102 (or server 106) may reject the transaction after reading the location verification data.

[0115] Referring now to step 318, the payment terminal 102 writes the new one-time verification code to the external entity 104. As an example, the new one-time verification code is written to the NFC card 104a. In the case where the NFC module of the mobile device 104b allows such writing, in an embodiment, the new one-time verification code is written to the NFC module of the mobile device 104b even in the case of an NFC-enabled mobile device 104b. The new one-time verification code is used for the next transaction. The new one-time verification code may be a preconfigured increment / decrement compared to the existing one-time verification code. Alternatively, the one-time verification code may be a randomly generated code, which may be based on known logic. In an embodiment, the new one-time verification code is generated by the payment terminal 102. At step 320, the new one-time verification code is recorded in the NFC module of the NFC card 104a or the mobile device 104b (if such provision is provided).

[0116] It should be noted that the one-time verification code adds freshness to the data collected from the external entity 104 for each transaction. As an example, in the case where only the user token is collected (as is the conventional case) (which is also constant), a malicious system with access to the user token may abuse the user token to perform transactions.

[0117] Referring to step 322, the payment terminal 102 bundles a user token, a one-time verification code (if any), a merchant ID, a terminal ID, a one-time verification code of the payment terminal 102, and a source for obtaining user data and transaction information (NFC card / mobile phone or BLE). In an embodiment, the payment terminal 102 may also bundle a new one-time verification code. It may be noted that in addition to the one-time verification code corresponding to the external entity 104, there may also be a one-time verification code for the payment terminal 102. Therefore, in the event of abuse, a malicious system with information about the payment terminal 102 (e.g., a merchant ID or a terminal ID) can still be resisted. In an embodiment, the user may also have to communicate a PIN to the payment terminal 102 to authorize the transaction. In some embodiments, a PIN may be required only for transactions exceeding a certain preconfigured amount.

[0118] Additionally, the payment terminal 102 may bundle authentication and security data with other data to enhance security features.

[0119] Referring to step 324, the payment terminal 102 sends the bundled information to the server 106. The payment terminal 102 may use the WIFI module 2 to send the information to the server 106. Alternatively, the payment terminal 102 may use the GPRS module to send the information to the server 106. Alternatively, the payment terminal may encrypt the bundled information using the security module 213 for security purposes before communicating the bundled information to the server 106.

[0120] Referring to step 326 , the server 106 receives the bundled information from the payment terminal 102 .

[0121] Referring to step 328, the server 106 processes the transaction. Conventional steps involved in processing a transaction are not discussed to avoid diverting attention from steps that may be unconventional. The one-time verification code of the external entity 104 and the one-time verification code of the payment terminal 102 are used to determine whether the payment request should be rejected or further processed. The one-time verification code (corresponding to the payment terminal 102) is used to verify whether the one-time verification code is the verification code expected by the payment terminal 102 for the current transaction, in order to reject the transaction or continue the transaction. Likewise, the one-time verification code (corresponding to the external entity 104) is used to verify whether the one-time verification code is the verification code expected by the external entity 104 for the current transaction, in order to reject the transaction or continue the transaction.

[0122] In an embodiment, the payment terminal 102 may even communicate a new one-time verification code corresponding to the external entity 104 to the server 106 , so that the server 106 knows the one-time verification code expected by the external entity 104 in the next transaction.

[0123] In an embodiment, the new one-time verification code of the external entity 104 or the payment terminal 102 is a known change compared to the previous one-time verification code. Therefore, the server 106 may only need to verify the one-time verification code using the previous verification code to reject or continue the transaction.

[0124] In an embodiment, the server 106 communicates a new one-time verification code to the payment terminal 102 for the next transaction.

[0125] In the event that the one-time verification code from the external entity 104 does not exist (which is expected) or the one-time verification code is wrong, the server 106 can prevent the external entity 104 from conducting transactions until the problem is resolved. The same is true for the payment terminal 102.

[0126] Referring to step 330, the server 106 sends the transaction information to the payment terminal 102. The transaction information may include information corresponding to a successful payment or a payment rejection. The transaction information may also include information corresponding to the amount paid to the merchant account and / or selected information about the user / customer making the payment and other information.

[0127] Referring to step 332, the payment terminal 102 receives transaction information from the server 106. Certain of the received information may be output (e.g., displayed) by the payment terminal 102. In some embodiments, certain transaction information may be prevented from being output by the payment terminal 102, and such information may be output on an external device 104 (e.g., a phone).

[0128] Referring to step 334 , once the transaction is complete, the payment terminal 102 may prepare for the next transaction (eg, starting from 302 ).

[0129] Referring now to box 310, as can be recalled, the description we provided previously considered that a user / customer may be using an NFC card 104a or an NFC-enabled smart phone 104b to make a payment. Now we refer to a scenario where a user is using a portable communication device 104b (e.g., a smart phone) with BLE functionality to make a payment.

[0130] It should be understood that BLE is not essential to the invention and other protocols will also work, such as "normal" Bluetooth or WiFi.

[0131] Now we can also compare with other Figure 1 Reference Figure 3E As previously explained, with reference to step 308, both the NFC module 216 and the BLE module 214 of the payment terminal may be attempting to establish a communication channel. As previously explained, in the case of the BLE module 214, the BLE module 214 may begin broadcasting its identifier. The identifier may include data identifying compatibility.

[0132] As an example, see also Figure 3E and Figure 4B , the user opens the payment application in the portable communication device 104b and activates the "pay now" icon. The application enables the BLE module of the BLE-enabled smart phone 104b to search (reference Figure 4C )Payment terminal 102.

[0133] In embodiments where there are multiple payment terminals, the payment terminals typically radiate signals at the same strength, but of course, it is unlikely that two terminals are equidistant from any particular portable communications device (smartphone). The radiation of a signal indicating that a connection (pair) is ready is sometimes referred to in the art as "advertising" and typically includes transmitting a data packet. The term "pairing" is not intended to be limiting.

[0134] The signal strength received at the portable communication device (smartphone) is measured by the smartphone (e.g., by an application running on the smartphone) and used to determine the location of the smartphone relative to each payment terminal available nearby.

[0135] As the first step of pairing, Figure 3E In step 30, the application scans the vicinity and makes a list of "qualified candidates" with which a connection can be established. The application is configured to ensure that the portable communication device (smartphone) is paired only with the intended payment terminal. For example, the merchant asks the customer to open the application and bring the phone close to payment terminal A to initiate a payment. The application then takes over and determines which payment terminal (out of all eligible payment terminals) is closest to the phone. Since the merchant has asked the customer to bring his phone close to payment terminal A, the application will see that payment terminal A is only a few inches away, while the other terminals are several meters away, and will therefore ask to pair with payment terminal A.

[0136] Signal strength logic (establishing a connection with the nearest available payment terminal) is used only to establish a connection.

[0137] Once the phone is paired with the payment terminal and a connection is thus established, the connection remains active until the application decides to disconnect the connection. Even if the phone is pulled away from the terminal, the connection remains active and the application continues to talk to the terminal to complete the transaction. Once the application determines that the transaction is complete, the application disconnects and releases the terminal.

[0138] The terminal is configured so that it cannot be paired with 2 phones at the same time. Once a phone is paired or connected to the terminal, the communication channel between the phone and the terminal is mutually exclusive. That is, no other phone can pair with the terminal or otherwise communicate with the terminal. The terminal is effectively locked to the phone and can only be unlocked (disconnected from the phone) through the application or by physically resetting the payment terminal.

[0139] In an embodiment, this "lock" is performed by configuring the terminal to stop advertising when pairing occurs. In one example, an application on the smartphone issues an instruction to the terminal to stop advertising; in another example, the terminal is configured to stop advertising without input from the smartphone once pairing has occurred.

[0140] The processor of the payment terminal receives the instruction and processes the instruction responsive to the stored instructions and temporarily disables advertising of its pairing capability and presence.

[0141] In an embodiment, the application of the smart phone 104b looks for compatible payment terminals 102 by looking at data present in the identifier that identifies compatibility. For example, there may be multiple BLE devices or Bluetooth devices that may be advertising, but the application is only interested in identifying payment terminals 102 that can be considered for payment (and therefore considered for sending a pairing request).

[0142] The user has moved the portable communication device near the payment terminal so that the signal strength is above a first threshold, such as Figure 3E As shown in step 31 , the smart phone 104 b sends a request to the payment terminal 102 for pairing.

[0143] In one embodiment, a pairing request is issued only when the signal strength from the payment terminal 102 is above a first threshold.

[0144] In another embodiment, a pairing request is issued once the user activates a "pay now" icon, or similarly instructs the smartphone to begin a transaction.

[0145] In a further embodiment, the application displays, for example on its display screen, an indication of one or more terminals with which it may be paired, and the user selects one of these terminals, said selection causing a pairing request sequence to start.

[0146] As an example, consider a merchant location with multiple compatible payment terminals 102. The application of the smartphone 104b will recognize and list all of these payment terminals 102, but it must decide to which of these payment terminals it must send a pairing request.

[0147] In an embodiment, even if a single payment terminal 102 is identified, a pairing request will not be sent unless the signal strength is above a first threshold. In practice, even if BLE is used as a payment channel, the user experience will be similar to "tap-and-pay". The user brings the smart phone 104b close to the payment terminal 102 (see FIG. 1 ). Figure 4D) The payment terminal 102 causes the signal strength to increase, thereby causing the application to request pairing with the payment terminal 102. Therefore, it should be understood that if the signal strength of the broadcasted identifier exceeds the first threshold, the smart phone 104b automatically sends a request to establish a communication channel with the personal area network module 214 of the payment terminal 102.

[0148] The first threshold is configured so that the portable communication device 104a and the payment terminal 102 are within a preconfigured distance of each other to establish a communication channel. The first threshold may be reconfigured remotely via a software update or may be configured at the payment terminal 102.

[0149] In an embodiment, the first threshold is configured such that the portable communication device 104b and the payment terminal 102 are within approximately 20 centimeters of each other to establish a communication channel.

[0150] In another embodiment, the first threshold is configured such that the portable communication device 104b and the payment terminal 102 are within approximately 10 centimeters of each other to establish a communication channel.

[0151] It should be understood that with the configuration of the first threshold, we can set the approximate distance between the portable communication device 104b and the payment terminal 102 for pairing.

[0152] exist Figure 3E At step 32, the payment terminal 102 receives the pairing request. After receiving the request, the payment terminal 102 coordinates with the smart phone 104b using a well-known protocol to successfully pair or reject the request. In the case of a successful pairing, the payment terminal 102 has established a communication channel (BLE channel) with the external entity 104 using the first wireless communication module 214 (BLE module 214). Therefore, the communication channel thus established can be referred to as a BLE channel.

[0153] Once the communication channel is established (paired), if the signal strength between the smart phone 104b and the personal area network module 214 of the payment terminal 102 drops below the first threshold, the smart phone continues to maintain communication with the personal area network module of the payment terminal 102. In effect, the user brings the smart phone 104b close to the payment terminal 102, thereby pairing the smart phone 104b with the payment terminal 102. Thereafter, the user can withdraw the smart phone 104b, but the communication channel will be maintained, thereby improving the user's experience and making the transaction process more reliable.

[0154] In an embodiment, if the signal strength in the channel between the smart phone 104b and the personal area network module 214 of the payment terminal 102 drops below a second threshold, at least one of the payment terminal 102 or the smart phone 104b is configured to terminate the established communication channel. The second threshold may be controllable. The second threshold may be reconfigured remotely or on the device.

[0155] exist Figure 3E At step 33, the payment terminal 102 sends the transaction information to the smart phone 104b. The information is sent via the BLE channel. Such information may include the amount to be transferred and the merchant information, etc.

[0156] exist Figure 3E Step 34 and Figure 4D and Figure 4E At , the smart phone 104 b receives the transaction information sent by the payment terminal 102 .

[0157] exist Figure 3E Step 35 and Figure 4E At NFC, the user can activate an icon, causing the smartphone 104b to send a payment approval and communicate data to facilitate the transaction. The data communicated (in addition to the relevant data discussed in the context of NFC) may also include real-time data. Real-time data may include data corresponding to time. A one-time verification code may be generated by the smartphone 104b. In embodiments, the user may also have to communicate a PIN to authorize the transaction. In some embodiments, a PIN may be required only for transactions over a certain preconfigured amount.

[0158] exist Figure 3F At step 36 , the payment terminal 102 receives the approval and data and may perform the steps previously discussed in connection with step 322 and subsequent steps, which may be applicable to this transaction mode.

[0159] Now refer specifically to step 332 ( Figure 3D ), 37 and 38( Figure 3F ), the payment terminal 102 receives the transaction information from the server 106. It may be noted that, as previously discussed, the server 106 knows based on the received data that the payment terminal 102 received the data via the BLE channel. Thus, the BLE channel may be used to provide updates corresponding to the transaction to the user. Thus, in addition to the typical data sent by the server 106, the server 106 sends and the payment terminal 102 receives data corresponding to the account balance of the user using the smart phone 104b to make the payment. The payment terminal 102 communicates the data corresponding to the account balance to the smart phone 104b via the BLE channel (refer to Figure 4G). Therefore, users will not only be able to make payments without using the internet, but will also be able to get updates about their transactions without using the internet.

[0160] After completing step 38, the application running on the smart phone 104 sends a command through the communication channel with the payment terminal 102. The command instructs the terminal to start advertising so that further transactions can be conducted with other smart phones. The command is received by the payment terminal and processed by the processing circuit system of the payment terminal according to instructions stored in the memory of the terminal, thereby resuming advertising.

[0161] In one embodiment, terminal 102 is also provided with a physical reset device (e.g., a reset key) so that the merchant can re-enable the advertisement as needed. In another embodiment, the reset can be performed remotely, but in some cases, this may not be as safe as using a physical reset device.

[0162] The reset key, when operated, may cause the payment terminal to reboot into a quiescent state where advertising may commence, or may simply override a "stop advertising" command and send a "resume advertising" command to the processing circuitry.

[0163] In an embodiment, the payment terminal 102 is further configured to receive data corresponding to the transaction information from the server 106 and communicate at least a portion of the data corresponding to the transaction information to the smart phone 104b via the communication channel.

[0164] In an embodiment, the payment terminal 102 cannot display the user's account balance; however, the portable communication device 104b is configured to display the user's account balance after the transaction. The data corresponding to the account balance can be encrypted so that only the user's smart phone 104b can decrypt the data.

[0165] It should be noted that some encryption, decryption, authentication, and security techniques that are typically used at different steps are not discussed in order to avoid unnecessarily obscuring aspects of the embodiments.

[0166] The process described above is described as a series of steps, which is done for illustrative purposes only. Therefore, it is contemplated that some steps can be added, some steps can be omitted, the order of the steps can be rearranged, or some steps can be performed simultaneously.

[0167] The example embodiments described herein may be implemented in an operating environment that includes software installed on a computer, hardware, or a combination of software and hardware.

[0168] Although the embodiments have been described with reference to specific example embodiments, it will be apparent that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the systems and methods described herein. Accordingly, the specification and drawings are to be regarded as illustrative rather than restrictive.

[0169] It should be understood that the present invention has been described by way of example only. Various modifications may be made to the techniques described herein without departing from the spirit and scope of the appended claims. The disclosed techniques include techniques that may be provided in an independent manner or in combination with one another. Therefore, features described with respect to one technique may also be presented in combination with another technique.

Claims

1. A method of operating a payment terminal deployed at a merchant location, the method comprising: receiving an activation input and in response thereto, simultaneously outputting a first wireless signal and a second wireless signal, wherein the first wireless signal is used to communicate with a first type of external payment device and the second wireless signal is used to communicate with a second type of external payment device, wherein the first wireless signal and the second wireless signal are formatted in first and second protocols that are different from each other, receiving a response to either one of the first wireless signal and the second wireless signal, and in response to the response, terminating outputting the other of the first wireless signal and the second wireless signal, wherein the first wireless signal is a Bluetooth signal, and the second wireless signal is an NFC signal, wherein the payment terminal is connected via a wired link to a server for processing initiated transactions, Wherein, upon receiving the response to either the first wireless signal or the second wireless signal, the payment terminal terminates any attempt to establish a communication channel with any other external entity using the first wireless signal or the second wireless signal until the transaction is completed.

2. The method of claim 1, further comprising: The response is processed to authenticate the external payment device, thereby establishing a communication channel.

3. The method of claim 1, further comprising: The response is processed to authenticate the external payment device, and the terminating step is performed after the processing step.

4. The method of claim 1, further comprising: processing the response to authenticate the external payment device to establish a communication channel, and receiving data indicative of a user from the communication channel; Data indicative of a transaction amount is received at an input, and data indicative of a user and data indicative of the transaction amount are transmitted to a server.

5. The method of claim 1, further comprising: Process the response to authenticate the external payment device to establish a communication channel, and receive data indicating the user and a one-time verification code for identifying the current transaction from the communication channel; receive data indicating the transaction amount at the input, and transmit the data indicating the user, the data indicating the one-time verification code, and the data indicating the transaction amount to the server.

6. The method of claim 5, further comprising: A new one-time verification code is outputted through the communication channel.

7. The method of claim 1, further comprising: Information indicating which of the first wireless signal and the second wireless signal to respond to is communicated with a server.

8. A payment terminal deployed at a merchant location for wirelessly communicating with an external device, the payment terminal having a processing device and a storage device, the storage device storing instructions for controlling the processing device so that the payment terminal simultaneously outputs a first wireless signal for communicating with a first type of external payment device and a second wireless signal for communicating with a second type of external payment device in response to an activation input, wherein: The first wireless signal and the second wireless signal are formatted in first and second protocols that are different from each other, and in response to receiving a response to either one of the first wireless signal and the second wireless signal, outputting the other of the first wireless signal and the second wireless signal is terminated, wherein the first wireless signal is a Bluetooth signal, and the second wireless signal is an NFC signal, wherein the payment terminal is connected via a wired link to a server for processing initiated transactions, Wherein, upon receiving the response to either the first wireless signal or the second wireless signal, the payment terminal terminates any attempt to establish a communication channel with any other external entity using the first wireless signal or the second wireless signal until the transaction is completed.

9. The payment terminal of claim 8, further comprising: a keypad for providing an activation signal; a display for displaying information under the control of the processing device; and an output device for communicating with a server.

10. The payment terminal of claim 8, having a first wireless device configured to output the first wireless signal under the control of the processing device, and a second wireless device configured to output the second wireless signal under the control of the processing device.

11. A payment terminal as claimed in claim 8, further having a security device, the security device comprising storage means for a security key, the security device being configured to use the key to encrypt or decrypt data for use by the terminal.

12. The payment terminal of claim 8, comprising a personal area network device configured to output the first wireless signal.

13. The payment terminal of claim 8, comprising a near field communication device configured to output the second wireless signal.

14. A non-transitory storage medium storing instructions, wherein when the instructions are executed by a processor, the processor is caused to perform the method according to any one of claims 1 to 7.

Citation Information

Patent Citations

  • Multi-mode communication system and method between terminal devices

    CN103491655A

  • Mobile payment method and system and related equipment

    CN104636916A