WO2021155785A1 - 一种支付方法、终端、服务器及系统 - Google Patents

一种支付方法、终端、服务器及系统 Download PDF

Info

Publication number
WO2021155785A1
WO2021155785A1 PCT/CN2021/074862 CN2021074862W WO2021155785A1 WO 2021155785 A1 WO2021155785 A1 WO 2021155785A1 CN 2021074862 W CN2021074862 W CN 2021074862W WO 2021155785 A1 WO2021155785 A1 WO 2021155785A1
Authority
WO
WIPO (PCT)
Prior art keywords
payment
nfc
payment terminal
terminal
tag
Prior art date
Application number
PCT/CN2021/074862
Other languages
English (en)
French (fr)
Inventor
陈成钱
郭伟
周钰
Original Assignee
中国银联股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中国银联股份有限公司 filed Critical 中国银联股份有限公司
Publication of WO2021155785A1 publication Critical patent/WO2021155785A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327—Short range or proximity payments by means of M-devices
    • G06Q20/3278—RFID or NFC payments by means of M-devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification

Definitions

  • the invention belongs to the field of financial data processing, and specifically relates to a payment method, terminal, server and system.
  • NFC Near Field Communication
  • RFID Radio Frequency Identification, radio frequency identification
  • NFC payment functions For example, relying on UnionPay’s tag payment technology, an NFC tag is embedded in the merchant acceptance label, and the NFC chip of the NFC tag stores the merchant’s information. You can use the cloud QuickPass APP or a designated model of mobile phone to directly touch the tag to initiate the payment. Merchant payment.
  • the main principle is shown in Figure 1, where a mobile phone that supports NFC function turns on the "card reader mode" and transfers a small amount of power by touching the NFC tag on the phone, and then uses a small amount of power to drive the NFC tag circuit and transfer the data stored in the NFC tag. After the information is sent to the mobile phone, the mobile phone wakes up the installed payment application after reading the data stored in the NFC tag, and enters the payment interface to the merchant represented by the NFC tag, enters the amount and password, and completes the payment.
  • the existing solutions cannot avoid the payment security problem when the NFC tag is maliciously covered by criminals using the NFC tag of a non-merchant.
  • the existing solutions cannot avoid the payment security problem when the NFC tag is maliciously covered by criminals using the NFC tag of a non-merchant.
  • the mobile phone will only read the merchant information in one of the NFC tags (which one is selected is not controllable), which will cause payment security problems.
  • the present invention provides the following solutions.
  • a payment method is provided, which is applied to a payment terminal with NFC function.
  • the method includes: when at least two NFC tags are detected, determining a target NFC tag from the at least two NFC tags; The merchant's registration place and obtain the current location of the payment terminal; generate and initiate a payment request, the payment request carries the merchant's registration place of the target NFC tag and the current location of the payment terminal.
  • determining the target NFC tag from the at least two NFC tags further includes: determining the target NFC tag using anti-collision rules based on the radio frequency card protocol, and reading the merchant identification and merchant stored in the target NFC tag Registration.
  • determining the target NFC tag from the at least two NFC tags further includes: reading the merchant identification and the merchant registration place stored in the at least two NFC tags, and listing at least two in the interface of the payment terminal.
  • a merchant identifier of an NFC tag detects touch operations on the interface of the payment terminal, and determines the target NFC tag based on the detected touch operations.
  • a contactless connection is established with each of the at least two NFC tags; after the target NFC tag is determined, the connection with other NFC tags is disconnected.
  • the method further includes: receiving a payment completion message or a payment rejection message, and then disconnecting the contactless connection with the target NFC tag.
  • the payment request further includes a tag conflict identifier, which is used to indicate the conflict of the at least two NFC tags.
  • the method further includes: receiving alarm information, and displaying the alarm information on the interface of the payment terminal, where the alarm information is used to indicate that multiple NFC tags conflict.
  • a payment method is provided, which is applied to a payment server.
  • the method includes: receiving a payment request, the payment request carrying a target NFC tag and the current location of the payment terminal; according to the merchant registration place and the current location of the payment terminal carried by the target NFC tag Make comparisons; pay or refuse to pay based on the results of the comparison.
  • the payment request further includes a tag conflict identification
  • the method further includes: in response to detecting the tag conflict identification, a comparison is made between the merchant registration place carried by the target NFC tag and the current location of the payment terminal.
  • it further includes: if the payment is made according to the comparison result, sending a payment completion message and/or an alarm message to the payment terminal and/or the merchant terminal; if the payment is rejected according to the comparison result, sending the payment terminal Rejection of payment message and/or warning information, which is used to indicate conflicts between multiple NFC tags.
  • a payment method is provided, which is characterized by being applied to a payment system composed of at least one payment terminal with NFC function and a payment server.
  • the method includes: the payment terminal executes the payment method as in the first aspect;
  • the server is used to execute the payment method as in the second aspect.
  • a payment terminal has an NFC module, and further includes: a payment application module configured to: when at least two NFC tags are detected through the NFC module, determine from the at least two NFC tags Target NFC tag; obtain the merchant registration place stored in the target NFC tag through the NFC module, and obtain the current location of the payment terminal; generate and initiate a payment request, the payment request carries the merchant registration place of the target NFC tag and the current location of the payment terminal.
  • a payment application module configured to: when at least two NFC tags are detected through the NFC module, determine from the at least two NFC tags Target NFC tag; obtain the merchant registration place stored in the target NFC tag through the NFC module, and obtain the current location of the payment terminal; generate and initiate a payment request, the payment request carries the merchant registration place of the target NFC tag and the current location of the payment terminal.
  • the NFC module is further used to determine the target NFC tag using the anti-collision rule based on the radio frequency card protocol, and read the merchant identification and merchant registration place stored in the target NFC tag.
  • the payment application module is also used to: read the merchant identification and merchant registration place stored in at least two NFC tags through the NFC module, and list at least two NFC tags in the interface of the payment terminal Merchant identification; detect touch operations on the interface of the payment terminal, and determine the target NFC tag based on the detected touch operations.
  • the NFC module is further configured to: in response to detecting at least two NFC tags, establish a contactless connection with each of the at least two NFC tags; after determining the target NFC tag, disconnect Open the contactless connection with other NFC tags.
  • the payment application module is further used to: receive a payment completion message or a payment rejection message; the NFC module is also used to: after receiving a payment completion message or a payment rejection message, disconnect from the target NFC tag Contactless connection.
  • the payment request further includes a tag conflict identifier, which is used to indicate the conflict of the at least two NFC tags.
  • the payment application module is further configured to: receive alarm information sent by the payment server, and display the alarm information on the interface of the payment terminal, and the alarm information is used to indicate the conflict of at least two NFC tags.
  • a payment server including: a receiving unit for receiving a payment request, the payment request including the target NFC tag and the current location of the payment terminal; The current location of the terminal is compared; the payment unit makes a payment or refuses to pay according to the comparison result.
  • the payment request further includes a tag conflict identifier
  • the comparison unit is further configured to: in response to detecting the tag conflict identifier, compare the merchant registration place carried by the target NFC tag and the current location of the payment terminal.
  • it further includes a sending unit, configured to send a payment completion message and/or an alarm message to the payment terminal and/or the merchant terminal if the payment is made according to the comparison result;
  • a payment rejection message and/or alarm information are sent to the payment terminal, and the alarm information is used to indicate that multiple NFC tags conflict.
  • a payment system which is characterized by comprising: at least one payment terminal with NFC function and a payment server, wherein the payment terminal is used to execute the method as in the first aspect; the payment server is used to execute the method as in the second aspect Methods.
  • a payment terminal including: at least one processor; and a memory connected in communication with the at least one processor; wherein the memory stores instructions executable by at least one processor, and the instructions are Execute, so that at least one processor can execute: when at least two NFC tags are detected, determine the target NFC tag from the at least two NFC tags; obtain the merchant registration place stored in the target NFC tag, and obtain the current payment terminal Location: Generate and initiate a payment request.
  • the payment request carries the merchant registration address of the target NFC tag and the current location of the payment terminal.
  • a payment server including: at least one processor; and a memory connected in communication with the at least one processor; wherein the memory stores instructions executable by at least one processor, and the instructions are executed by the at least one processor. Execute to enable at least one processor to execute: receive a payment request, the payment request carries the target NFC tag and the current location of the payment terminal; compare the merchant's registration place carried by the target NFC tag and the current location of the payment terminal; perform comparison according to the comparison result Pay or refuse to pay.
  • a computer-readable storage medium stores a program.
  • the program is executed by a multi-core processor, the multi-core processor is caused to execute the method of the first aspect or the second aspect.
  • the merchant registration place of the NFC tag and the current location of the payment terminal are added to the payment request generated and initiated by the payment terminal, so that the current location of the payment terminal can be based on The merchant registration place of the NFC tag and the current location of the payment terminal perform secure payment, which improves the security of payment.
  • Figure 1 is a schematic diagram of the principle of payment transactions through NFC tags
  • FIG. 2 is a schematic diagram of a scene of multiple NFC tag conflicts existing in the prior art
  • FIG. 3 is a schematic flowchart of a payment method according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a payment method according to another embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a payment method according to another embodiment of the present invention.
  • Fig. 6 is a schematic flowchart of a payment method according to another embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a payment terminal according to an embodiment of the present invention.
  • Fig. 8 is a schematic structural diagram of a payment server according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a payment terminal according to another embodiment of the present invention.
  • Fig. 10 is a schematic structural diagram of a payment server according to another embodiment of the present invention.
  • the embodiment of the present invention provides a payment method.
  • the inventive concept of the method is first introduced.
  • a payment terminal with NFC function usually realizes transaction payment by approaching and touching the NFC tag.
  • the embodiment of the present invention A payment method is provided, wherein when a payment terminal detects at least two NFC tags, a target NFC tag is determined from the at least two NFC tags; the target NFC tag and the current location of the payment terminal are acquired; wherein the target NFC tag carries merchant registration
  • the payment terminal initiates a payment request to the payment server, and the payment request carries the target NFC tag and the current location of the payment terminal.
  • the payment request can be used to perform security detection, for example, at the merchant registration place of the NFC tag and the current location of the payment terminal
  • security detection for example, at the merchant registration place of the NFC tag and the current location of the payment terminal
  • the transaction is allowed in the case of consistency, and the transaction is rejected when the merchant registration place of the NFC tag is inconsistent with the current location of the payment terminal, which improves the security of payment.
  • FIG. 2 is only an example in which the embodiments of the present invention can be implemented.
  • the scope of application of the embodiments of the present invention is not limited in any way.
  • FIG. 3 is a schematic flowchart of a payment method 300 according to an embodiment of the present application.
  • the method is used to generate a payment request and is applied to a payment terminal with NFC function.
  • the payment terminal may be a smart phone, a tablet computer or other similar NFC
  • a mobile smart terminal with communication function and a payment application that supports NFC payment functions is installed, such as the "Cloud QuickPass" application installed on the payment terminal.
  • the user can set it on the setting interface of the payment terminal to set the "Cloud QuickPass”
  • the application is set as an application for the payment terminal to make NFC payments by default, and the "cloud flash payment” application is set to run automatically when the NFC tag is detected.
  • the payment application may also be an application preset by the mobile phone manufacturer or called the system's own application, which can carry bank cards, bus cards and other card simulation applications that support NFC payment. This application does not specifically limit this.
  • the execution body may be one or more electronic devices; from a program perspective, the execution body may correspondingly be programs carried on these electronic devices.
  • the method 300 may include:
  • Step S301 When at least two NFC tags are detected, determine the target NFC tag from the at least two NFC tags;
  • the NFC tag pre-stores merchant information
  • the merchant information may include information such as ⁇ merchant UID, merchant name, merchant registration place>, and the merchant UID ensures the uniqueness of the NFC tag.
  • the method 300 may further include: in response to detecting at least two NFC tags, establishing a connection with each of the at least two NFC tags.
  • Non-contact connection is used to realize non-contact point-to-point data transmission between the payment device and the NFC tag.
  • the payment terminal After the payment terminal detects at least two NFC tags, it can only read and write to one radio frequency card in the radio frequency field at a time. Therefore, when multiple NFC tags enter the radio frequency field of the payment terminal at the same time, the payment terminal needs Select a unique NFC tag from the detected NFC tags for reading and writing operations.
  • the first solution can be adopted: use the anti-collision rules based on the radio frequency card protocol (ISO14443) to determine the target NFC tag, and read the target NFC tag
  • the merchant ID includes the merchant UID and the merchant name.
  • the anti-collision rules based on the radio frequency card protocol (ISO14443) mainly include: bit-oriented anti-collision mechanism (ISO14443 Type A use), time slot-oriented anti-collision mechanism (ISO14443 Type B use).
  • bit-oriented anti-collision mechanism ISO14443 Type A use
  • time slot-oriented anti-collision mechanism ISO14443 Type B use
  • the second solution in order to make the determined target NFC tag consistent with the actual merchant, the second solution can be adopted: sequentially reading the merchant identification and merchant registration place stored in at least two NFC tags, where the merchant identification can be Including merchant UID and merchant name, and listing at least two NFC tag merchant identifiers in the interface of the payment terminal.
  • the user can be notified to choose. Label"; detects the touch operation on the interface of the payment terminal.
  • the target NFC tag is determined according to the detected touch operation.
  • reading the NFC tag is limited to reading the merchant UID of the NFC tag.
  • the existing Radio frequency card protocol such as independently encapsulating a set of interfaces for the payment terminal to call, so that when the NFC tag interacts with the payment terminal, the payment terminal not only reads the merchant UID of the NFC tag, but also needs to read the merchant name and merchant. Registration location and other information.
  • the user can independently select the target NFC tag after communicating with the merchant, avoiding payment failure, and improving the user experience.
  • the merchant can also be reminded of the current payment risk.
  • the method further includes: after determining the target NFC tag, disconnecting the contactless connection with other NFC tags.
  • the method 300 may include:
  • Step S302 Obtain the merchant registration place stored in the target NFC tag, and obtain the current location of the payment terminal;
  • the merchant UID, merchant name, and merchant registration location stored in the target NFC tag can be obtained through the non-contact connection transmission established between the payment terminal and the target NFC tag; the payment terminal's information can be obtained through the GPS positioning information of the payment terminal. current location.
  • the method 300 may include:
  • Step S303 Generate and initiate a payment request, where the payment request carries the merchant registration place of the target NFC tag and the current location of the payment terminal.
  • the recipient of the above payment request may be a payment server communicatively connected with the payment terminal.
  • the payment request is used to enable the payment server to compare the registered address of the merchant based on the target NFC tag and the current address of the payment terminal, and make a payment or reject the payment according to the comparison result.
  • the merchant registration place stored in the NFC tag should be consistent with the actual location of the NFC tag.
  • the payment server makes the payment; on the contrary, when the registered place of the merchant carried by the target NFC tag is inconsistent with the current location of the payment terminal, the payment server refuses to pay, which ensures the security of the payment.
  • the generated and initiated payment request further includes the payment amount and/or the payment password.
  • the method may further include: before step S303, receiving the input payment amount and/or payment password. It should be understood that in some small-amount payment scenarios, there may be no need to enter a payment password; in some fixed-amount payment scenarios, there may also be no need to enter the payment amount, which is not specifically limited in this application.
  • the generated and initiated payment request further includes a tag conflict identifier, and the tag conflict identifier is used to indicate that the tag conflict of the at least two NFC tags is detected, so that the payment server responds to the detection Label conflict identification for comparison.
  • the tag conflict identifier is carried in the payment request to indicate the NFC tag conflict. Therefore, when the payment server does not detect the tag conflict identifier, it means that there is only one NFC tag in the radio frequency range of the payment terminal. There is no need to perform a comparison operation.
  • it further includes: receiving a payment completion message or a payment rejection message sent by the payment server, and then disconnecting the contactless connection with the target NFC tag to complete a payment.
  • the alarm information is used to indicate that multiple NFC tags conflict .
  • you can attach warning messages such as "There are multiple NFC tags conflict" and "NFC tags may be overwritten" in the payment completion message or the payment rejection message to remind the payer to pay attention to the security of the payment, and to make the payer and the merchant understand the failure of the payment.
  • Reasons so that corrections can be made as soon as possible.
  • the method shown in FIG. 3 above can be applied in a scenario where the payment terminal is in an unlocked state, and can also be applied in a scenario where the payment terminal is in an unlocked state, such as a scenario where the payment terminal is locked or rested.
  • the embodiment of the present application can also save the step of unlocking the payment terminal by the user, further reduce user operations, and realize fast payment.
  • the various aspects of the above-mentioned payment method provided by the embodiments of this application are achieved by adding the merchant's registration place to the NFC tag, and by using the merchant's registration place and the current location of the payment terminal that carry the NFC tag in the payment request generated and initiated by the payment terminal.
  • the payment request can be checked for security, for example, the transaction is allowed when the merchant registration place of the NFC tag is consistent with the current location of the payment terminal, and the transaction is rejected when the merchant registration place of the NFC tag is inconsistent with the current location of the payment terminal. , Improve payment security.
  • FIG. 4 is a flowchart of a payment method 400 according to an embodiment of the present application.
  • the payment method 400 is used to make a payment according to a payment request and is applied to a payment server.
  • the method 400 includes:
  • Step S401 A payment request is received.
  • the payment request carries the target NFC tag and the current location of the payment terminal; where the payment request may be sent by the payment terminal.
  • Step S402 Comparing the current location of the payment terminal with the merchant registration carried by the target NFC tag;
  • Step S403 Make payment or refuse payment according to the comparison result.
  • the merchant registration place stored in the NFC tag should be consistent with the actual location of the NFC tag.
  • the payment server makes the payment; on the contrary, when the registered place of the merchant carried by the target NFC tag is inconsistent with the current location of the payment terminal, the payment server refuses to pay, ensuring payment security.
  • the payment request may also include the payment amount and/or the payment password. Therefore, after receiving the payment request, the payment server performs a transaction according to the payment amount and/or performs verification according to the payment password. It should be understood that in some small-amount payment scenarios, additional verification of the payment password is not required; in some fixed-amount payment scenarios, transactions can also be performed based on the preset payment amount without the need to carry the payment amount in the payment request. This application does not do this. Specific restrictions.
  • the payment request further includes a tag conflict identifier, so that after receiving the payment request, the payment server responds to detecting the tag conflict identifier according to the merchant registration place and the current location of the payment terminal carried by the target NFC tag. comparing.
  • the payment server in order to remind the payer and the merchant that there is a payment risk, if the payment server makes a payment according to the comparison result, after the payment is completed, it sends a payment completion message and/or an alarm to the payment terminal and/or the merchant terminal Messages, such as "NFC tags may be maliciously covered, please check and remove them as soon as possible! in the payment completion message, and other warning information indicating conflicts between multiple NFC tags, so that merchants can get timely and effective reminders of problems, and further improve In order to improve the payment experience and accurately locate the payment risk problem, the payment security is further guaranteed. If the payment server rejects the payment based on the comparison result, it sends a payment rejection message and/or warning information to the payment terminal.
  • the payment server rejects the payment based on the comparison result, it sends a payment rejection message and/or warning information to the payment terminal.
  • the payment rejection message can be accompanied by "multiple NFC tag conflicts", "NFC tag may be overwritten", etc.
  • the warning message indicating the conflict of multiple NFC tags reminds the payer to pay attention to payment safety, and also enables the payer and the merchant to accurately locate the payment risk, so as to make corrections as soon as possible.
  • the embodiment of the present invention also provides a payment method, which is applied to a payment system composed of at least one payment terminal with NFC function and a payment server.
  • the method includes: the payment terminal executes the payment method shown in FIG. 3; the payment server executes The payment method shown in Figure 4.
  • FIG. 5 is a flowchart of a payment method 500 according to an embodiment of the present application, which is applied to a payment system composed of at least one payment terminal with NFC function, a payment server, and a merchant terminal.
  • step S501 the payment terminal touches the NFC tag, and multiple NFC tags are detected; in step S502, the payment terminal establishes a contactless connection with the detected multiple NFC tags; in step S503 , The payment terminal reads the merchant UID, merchant name, and merchant registration location of multiple NFC tags; in step S504, list the detected merchant identities of the multiple NFC tags in the interface of the payment terminal; in step S505, detect the payment terminal The touch operation on the interface of the payment terminal, when the user selects a certain NFC tag merchant logo on the interface of the payment terminal, the NFC tag selected by the user is determined as the target NFC tag according to the detected touch operation.
  • step S506 disconnect the contactless connection between the payment terminal and other NFC tags; in step S507, obtain the current location of the payment terminal, and (optionally) obtain the entered payment amount and/or payment password; In step S508, the payment terminal initiates a payment request to the payment server.
  • the payment request carries the tag conflict identifier, the merchant UID, merchant name and merchant registration place of the target NFC tag, the current location of the payment terminal, and (optionally) the payment amount and/or payment Password and other information; in step S509, the payment server receives the payment request, and compares it based on the merchant registration place of the target NFC tag and the current location of the payment terminal; after step S509, in step S510a, the payment server is consistent with the above comparison In step S511a, after the payment is completed, the payment server sends a transaction completion message to the payment terminal, and can also send alarm information to the payment terminal; after the payment is completed, in step S512, the payment server sends alarm information to the merchant terminal .
  • step S509 in step S510b the payment server rejects the payment if the above comparison is inconsistent; after the payment is rejected, in step S511b, the payment server sends a transaction rejection message to the payment terminal, and can also send an alarm to the payment terminal information.
  • step S511a or step S511b in step S513 after receiving the transaction completion message or transaction rejection message, the payment terminal disconnects the contactless connection with the target NFC tag; (optional) after step S512 in step S514, The merchant terminal performs a self-check after receiving the alarm information.
  • Fig. 6 is a flowchart of a payment method according to another embodiment of the present invention, which is applied to a payment system composed of at least one payment terminal with NFC function, a payment server, and a merchant terminal.
  • step S601 the payment terminal touches the NFC tag, and multiple NFC tags are detected; in step S602, the payment terminal establishes a contactless connection with the detected multiple NFC tags; in step S603 , The payment terminal performs anti-collision processing based on the anti-collision rules of the radio frequency card protocol, selects one of the NFC tags as the target NFC tag, and reads the merchant UID, merchant name, merchant registration location and other information stored in the target NFC tag; in step In S604, disconnect the contactless connection between the payment terminal and other NFC tags; in step S605, obtain the current location of the payment terminal, (optionally) obtain the input payment amount and/or payment password; in step S606 , The payment terminal initiates a payment request to the payment server, the payment request carries the tag conflict identifier, the merchant UID, merchant name and merchant registration place of the target NFC tag, the current location of the payment terminal, (optionally) the payment amount and/or payment password, etc.
  • step S607 the payment server receives the payment request, and compares the merchant's registration place carried by the target NFC tag with the current location of the payment terminal; after step S607, in step S608a, the payment server performs the comparison if the above comparison is consistent Payment; after the payment is completed, in step S609a, the payment server sends a transaction completion message to the payment terminal, and can also send alarm information to the payment terminal; after the payment is completed, in step S610, the payment server sends alarm information to the merchant terminal.
  • step S607 in step S608b the payment server rejects the payment if the above comparison is inconsistent; after the payment is rejected, in step S609b, the payment server sends a transaction rejection message to the payment terminal, and can also send an alarm to the payment terminal information.
  • step S609a or step S609b in step S611, after receiving the transaction completion message or the transaction rejection message, the payment terminal disconnects the contactless connection with the target NFC tag. (Optional)
  • step S612 the merchant terminal performs a self-check after receiving the alarm information.
  • FIG. 7 is a schematic structural diagram of a payment terminal provided by an embodiment of the present invention.
  • the payment terminal 70 has an NFC module 71 and a payment application module 72, wherein the payment application module 72 is configured to: when at least two NFC tags are detected through the NFC module 71, determine the target NFC tag from the at least two NFC tags Obtain the merchant registration place stored in the target NFC tag through the NFC module 71, and obtain the current location of the payment terminal; generate and initiate a payment request, the payment request carries the merchant registration place of the target NFC tag and the current location of the payment terminal.
  • the NFC module 71 is further used to determine the target NFC tag using the anti-collision rule based on the radio frequency card protocol, and read the merchant identification and merchant registration place stored in the target NFC tag.
  • the payment application module 72 is further configured to: read the merchant identification and merchant registration place stored in at least two NFC tags through the NFC module 71, and list at least two NFCs in the interface of the payment terminal The merchant identification of the tag; the touch operation on the interface of the payment terminal is detected, and the target NFC tag is determined according to the detected touch operation.
  • the NFC module 71 is further configured to: in response to detecting at least two NFC tags, establish a contactless connection with each of the at least two NFC tags; after determining the target NFC tag, Disconnect the contactless connection with other NFC tags.
  • the payment application module 72 is also used to: receive a payment completion message or a payment rejection message; the NFC module 71 is also used to: after receiving a payment completion message or a payment rejection message, disconnect the target NFC tag Non-contact connection between.
  • the payment request further includes a tag conflict identifier, which is used to indicate the conflict of the at least two NFC tags.
  • the payment application module 72 is further configured to: receive alarm information and display the alarm information on the interface of the payment terminal.
  • the alarm information is used to indicate a conflict between multiple NFC tags.
  • Fig. 8 is a schematic structural diagram of a payment server provided by an embodiment of the present invention.
  • the payment server 80 includes: a receiving unit 801 for receiving a payment request, which includes the target NFC tag and the current location of the payment terminal; The current location of the payment terminal is compared; the payment unit 803 makes a payment or refuses to pay according to the comparison result.
  • the payment request further includes a tag conflict identifier
  • the comparison unit 802 is further configured to: in response to detecting the tag conflict identifier, compare the merchant registration place carried by the target NFC tag and the current location of the payment terminal.
  • a sending unit is further included, configured to: if the payment is made according to the comparison result, send a payment completion message and/or an alarm message to the payment terminal and/or the merchant terminal; if the payment is refused according to the comparison result, Then, a payment rejection message and/or alarm information are sent to the payment terminal, and the alarm information is used to indicate that multiple NFC tags conflict.
  • the embodiment of the present invention also provides a payment system.
  • the payment system includes: at least one payment terminal with NFC function and a payment server, wherein the payment terminal is used to execute the method shown in FIG. 3; the payment server is used to execute the method shown in FIG.
  • the payment system further includes a merchant terminal.
  • Fig. 9 is a payment terminal according to an embodiment of the present application, which is used to execute the payment method shown in Fig. 3.
  • the device includes: at least one processor; and a memory connected in communication with the at least one processor; There are instructions that can be executed by at least one processor, and the instructions are executed by at least one processor to enable the at least one processor to execute:
  • FIG. 10 is a payment server according to an embodiment of the present application for executing the payment method shown in FIG. 4.
  • the device includes: at least one processor; and a memory connected in communication with the at least one processor; wherein the memory stores There are instructions that can be executed by at least one processor, and the instructions are executed by at least one processor to enable the at least one processor to execute:
  • the payment request is received, and the payment request carries the target NFC tag and the current location of the payment terminal; compares the merchant registration place carried by the target NFC tag and the current location of the payment terminal; pays or declines the payment according to the comparison result.
  • a non-volatile computer storage medium of a payment method is provided, and computer-executable instructions are stored thereon, and the computer-executable instructions are configured to execute the instructions shown in FIG. 3 when run by a processor.
  • the apparatus, equipment, and computer-readable storage medium provided in the embodiments of the present application correspond to the method in a one-to-one manner. Therefore, the apparatus, equipment, and computer-readable storage medium also have beneficial technical effects similar to their corresponding methods.
  • the beneficial technical effects of the method are described in detail, and therefore, the beneficial technical effects of the device, equipment and computer-readable storage medium are not repeated here.
  • the embodiments of the present invention can be provided as a method, a system, or a computer program product. Therefore, the present invention may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • the computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-permanent memory in computer readable media, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer readable media.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash memory
  • Computer-readable media include permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology.
  • the information can be computer-readable instructions, data structures, program modules, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical storage, Magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices.
  • PRAM phase change memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • RAM random access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory or other memory technology
  • CD-ROM

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Finance (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

一种支付方法、终端、服务器及系统，应用于具有NFC功能的支付终端的支付方法包括：当检测到至少两个NFC标签时，从至少两个NFC标签中确定目标NFC标签（S301）；获取目标NFC标签中存储的商户注册地，并获取支付终端的当前位置（S302）；生成并发起支付请求（S303），支付请求携带目标NFC标签的商户注册地和支付终端的当前位置。应用于支付服务器的支付方法包括：接收支付请求，支付请求携带目标NFC标签和支付终端的当前位置（S401）；根据目标NFC标签携带的商户注册地和支付终端的当前位置进行对比（S402）；根据对比结果进行支付或拒绝支付（S403）。利用上述方法，能够提高支付安全性。

Description

一种支付方法、终端、服务器及系统 技术领域
本发明属于金融数据处理领域，具体涉及一种支付方法、终端、服务器及系统。
背景技术
本部分旨在为权利要求书中陈述的本发明的实施方式提供背景或上下文。此处的描述不因为包括在本部分中就承认是现有技术。
近场通信(Near Field Communication，简称NFC)是一种短距高频的无线通信技术，由RFID(Radio Frequency Identification，射频识别)演变而来。NFC允许电子设备之间进行短距离非接触式点对点数据传输。
目前，很多移动终端都支持NFC支付功能。例如，依托银联的标签支付技术，在商户受理标贴中内嵌NFC标签，该NFC标签的NFC芯片中存储了商户信息，使用云闪付APP或者指定型号手机直接碰触标签就可以发起对该商户的付款。主要原理如图1所示，其中，支持NFC功能的手机打开“读卡器模式”，通过手机触碰NFC标签传递少量电能，进而利用少量电能驱动NFC标签电路，并传递NFC标签中存储的数据信息至手机，手机在读取到NFC标签中存储的数据后唤醒安装的支付应用，并且进入向该NFC标签所代表商户的付款界面，输入金额和密码后完成支付。
然而，现有方案无法避免当NFC标签被不法分子使用非本商户的NFC标签恶意覆盖后的支付安全问题。如图2所示，当商户的NFC标签被不法分子使用非本商户的NFC标签覆盖后，顾客使用手机进行NFC支付时，会出现多张NFC标签同在一个手机的工作场内的情况，根据现有的技术方案，手机会 只读取其中一个NFC标签中的商户信息(选中哪个不可控制)，这样会产生支付安全性的问题。
发明内容
针对上述现有技术中存在的问题，提出了一种支付方法、终端、服务器、系统及计算机可读存储介质，利用这种方法、终端、服务器、系统及计算机可读存储介质，能够解决上述问题。
本发明提供了以下方案。
第一方面，提供一种支付方法，应用于具有NFC功能的支付终端，方法包括：当检测到至少两个NFC标签时，从至少两个NFC标签中确定目标NFC标签；获取目标NFC标签中存储的商户注册地，并获取支付终端的当前位置；生成并发起支付请求，支付请求携带目标NFC标签的商户注册地和支付终端的当前位置。
在一种可能的实施方式中，从至少两个NFC标签中确定目标NFC标签，还包括：利用基于射频卡协议的防冲突规则确定目标NFC标签，并读取目标NFC标签存储的商户标识和商户注册地。
在一种可能的实施方式中，从至少两个NFC标签中确定目标NFC标签，还包括：读取至少两个NFC标签存储的商户标识和商户注册地，并在支付终端的界面中列举至少两个NFC标签的商户标识；检测支付终端的界面上的触控操作，根据检测到的触控操作确定目标NFC标签。
在一种可能的实施方式中，响应于检测到至少两个NFC标签，与至少两个NFC标签中的每一者建立非接触式连接；在确定目标NFC标签之后，断开和其他NFC标签之间的非接触式连接。
在一种可能的实施方式中，还包括：接收支付完成消息或拒绝支付消息，之后断开与目标NFC标签之间的非接触式连接。
在一种可能的实施方式中，支付请求还包含标签冲突标识，用于指示所述至少两个NFC标签的冲突。
在一种可能的实施方式中，还包括：接收告警信息，并在支付终端的界面上显示告警信息，告警信息用于指示多个NFC标签冲突。
第二方面，提供一种支付方法，应用于支付服务器，方法包括：接收支付请求，支付请求携带目标NFC标签和支付终端的当前位置；根据目标NFC标签携带的商户注册地和支付终端的当前位置进行对比；根据对比结果进行支付或拒绝支付。
在一种可能的实施方式中，支付请求还包括标签冲突标识，方法还包括：响应于检测到标签冲突标识，根据目标NFC标签携带的商户注册地和支付终端的当前位置进行对比。
在一种可能的实施方式中，还包括：若根据对比结果进行支付，则向支付终端和/或商户终端发送支付完成消息和/或告警消息；若根据对比结果拒绝支付，则向支付终端发送拒绝支付消息和/或告警信息，告警信息用于指示多个NFC标签冲突。
第三方面，提供一种支付方法，其特征在于，应用于由至少一个具有NFC功能的支付终端以及支付服务器组成的支付系统，方法包括：由支付终端执行如第一方面的支付方法；由支付服务器用于执行如第二方面的支付方法。
第四方面，提供一种支付终端，支付终端具有NFC模块，还包括：支付应用模块，被配置为用于：当通过NFC模块检测到至少两个NFC标签时，从至少两个NFC标签中确定目标NFC标签；通过NFC模块获取目标NFC标签中存储的商户注册地，并获取支付终端的当前位置；生成并发起支付请求，支付请求携带目标NFC标签的商户注册地和支付终端的当前位置。
在一种可能的实施方式中，NFC模块还用于：利用基于射频卡协议的防冲突规则确定目标NFC标签，并读取目标NFC标签存储的商户标识和商户注册地。
在一种可能的实施方式中，支付应用模块，还用于：通过NFC模块读取至少两个NFC标签存储的商户标识和商户注册地，并在支付终端的界面中列举至少两个NFC标签的商户标识；检测支付终端的界面上的触控操作，根据检测到的触控操作确定目标NFC标签。
在一种可能的实施方式中，NFC模块还用于：响应于检测到至少两个NFC标签，与至少两个NFC标签中的每一者建立非接触式连接；在确定目标NFC标签之后，断开和其他NFC标签之间的非接触式连接。
在一种可能的实施方式中，支付应用模块还用于：接收支付完成消息或拒绝支付消息；NFC模块还用于：在接收支付完成消息或拒绝支付消息之后，断开与目标NFC标签之间的非接触式连接。
在一种可能的实施方式中，支付请求还包含标签冲突标识，用于指示所述至少两个NFC标签的冲突。
在一种可能的实施方式中，支付应用模块还用于：接收支付服务器发送的告警信息，并在支付终端的界面上显示告警信息，告警信息用于指示至少两个NFC标签的冲突。
第五方面，提供一种支付服务器，包括：接收单元，用于接收支付请求，支付请求包含目标NFC标签和支付终端的当前位置；对比单元，用于根据目标NFC标签携带的商户注册地和支付终端的当前位置进行对比；支付单元，根据对比结果进行支付或拒绝支付。
在一种可能的实施方式中，支付请求还包括标签冲突标识，对比单元还用于：响应于检测到标签冲突标识，根据目标NFC标签携带的商户注册地和支付终端的当前位置进行对比。
在一种可能的实施方式中，还包括发送单元，用于：若根据对比结果进行支付，则向支付终端和/或商户终端发送支付完成消息和/或告警消息；
若根据对比结果拒绝支付，则向支付终端发送拒绝支付消息和/或告警信息，告警信息用于指示多个NFC标签冲突。
第六方面，提供一种支付系统，其特征在于，包括：至少一个具有NFC功能的支付终端以及支付服务器，其中支付终端用于执行如第一方面的方法；支付服务器用于执行如第二方面的方法。
第七方面，提供一种支付终端，包括：至少一个处理器；以及，与至少一个处理器通信连接的存储器；其中，存储器存储有可被至少一个处理器执行的 指令，指令被至少一个处理器执行，以使至少一个处理器能够执行：当检测到至少两个NFC标签时，从至少两个NFC标签中确定目标NFC标签；获取目标NFC标签中存储的商户注册地，并获取支付终端的当前位置；生成并发起支付请求，支付请求携带目标NFC标签的商户注册地和支付终端的当前位置。
第八方面，提供一种支付服务器，包括：至少一个处理器；以及，与至少一个处理器通信连接的存储器；其中，存储器存储有可被至少一个处理器执行的指令，指令被至少一个处理器执行，以使至少一个处理器能够执行：接收支付请求，支付请求携带目标NFC标签和支付终端的当前位置；根据目标NFC标签携带的商户注册地和支付终端的当前位置进行对比；根据对比结果进行支付或拒绝支付。
第九方面，提供一种计算机可读存储介质，计算机可读存储介质存储有程序，当程序被多核处理器执行时，使得多核处理器执行如第一方面或第二方面的方法。
本申请实施例采用的上述至少一个技术方案能够达到以下有益效果：本实施例中，通过在支付终端生成并发起的支付请求中加入NFC标签的商户注册地和支付终端的当前位置，使得能够基于NFC标签的商户注册地和支付终端的当前位置进行安全性支付，提高了支付安全性。
应当理解，上述说明仅是本发明技术方案的概述，以便能够更清楚地了解本发明的技术手段，从而可依照说明书的内容予以实施。为了让本发明的上述和其它目的、特征和优点能够更明显易懂，以下特举例说明本发明的具体实施方式。
附图说明
通过阅读下文的示例性实施例的详细描述，本领域普通技术人员将明白本文所述的优点和益处以及其他优点和益处。附图仅用于示出示例性实施例的目的，而并不认为是对本发明的限制。而且在整个附图中，用相同的标号表示相同的部件。在附图中：
图1为通过NFC标签进行支付交易的原理示意图；
图2为现有技术中存在的多NFC标签冲突的场景示意图；
图3为根据本发明一实施例的支付方法的流程示意图；
图4为根据本发明另一实施例的支付方法的流程示意图；
图5为根据本发明又一实施例的支付方法的流程示意图；
图6为根据本发明又一实施例的支付方法的流程示意图；
图7为根据本发明一实施例的支付终端的结构示意图；
图8为根据本发明一实施例的支付服务器的结构示意图；
图9为根据本发明另一实施例的支付终端的结构示意图；
图10为根据本发明另一实施例的支付服务器的结构示意图。
在附图中，相同或对应的标号表示相同或对应的部分。
具体实施方式
下面将参照附图更详细地描述本公开的示例性实施例。虽然附图中显示了本公开的示例性实施例，然而应当理解，可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本公开，并且能够将本公开的范围完整的传达给本领域的技术人员。
在本发明中，应理解，诸如“包括”或“具有”等术语旨在指示本说明书中所公开的特征、数字、步骤、行为、部件、部分或其组合的存在，并且不旨在排除一个或多个其他特征、数字、步骤、行为、部件、部分或其组合存在的可能性。
另外还需要说明的是，在不冲突的情况下，本发明中的实施例及实施例中的特征可以相互组合。下面将参考附图并结合实施例来详细说明本发明。
本发明实施例提供一种支付方法，下面，首先对所述方法的发明构思进行介绍。
如图2所示，具有NFC功能的支付终端通常通过靠近并触碰NFC标签而实现交易支付，当支付终端的射频覆盖区有多个NFC标签时，为了进一步保障支 付交易安全，本发明实施例提供一种支付方法，其中当支付终端检测到至少两个NFC标签时，从至少两个NFC标签中确定目标NFC标签；获取目标NFC标签和支付终端的当前位置；其中，目标NFC标签携带商户注册地；支付终端向支付服务器发起支付请求，且支付请求携带目标NFC标签和支付终端的当前位置，利用该支付请求能够进行安全性检测，比如，在NFC标签的商户注册地和支付终端的当前位置一致的情况下允许交易，在NFC标签的商户注册地和支付终端的当前位置不一致的情况下拒绝交易，提高了支付安全性。
本领域技术人员可以理解，图2所描述的应用场景仅是本发明的实施方式可以在其中得以实现的一个示例。本发明实施方式的适用范围不受任何限制。在介绍了本发明的基本原理之后，下面具体介绍本发明的各种非限制性实施方式。
图3为根据本申请一实施例的支付方法300的流程示意图，该方法用于生成支付请求，应用于具有NFC功能的支付终端，该支付终端可以是智能手机、平板电脑或其他类似带有NFC通讯功能的可移动的智能终端，并且安装有支持NFC支付功能的支付应用，比如安装于支付终端的“云闪付”应用，用户可以在支付终端的设置界面进行设置，将“云闪付”应用设定为支付终端默认进行NFC支付的应用，并将该“云闪付”应用设定为响应于检测到NFC标签时自动运行。又比如，支付应用也可能为手机制造商预置的应用或者称之为系统自带应用，能够承载银行卡、公交卡等支持NFC支付的卡模拟应用，本申请对此不作具体限制。在图3所示流程中，从设备角度而言，执行主体可以是一个或者多个电子设备；从程序角度而言，执行主体相应地可以是搭载于这些电子设备上的程序。
如图3所示，该方法300可以包括：
步骤S301：当检测到至少两个NFC标签时，从至少两个NFC标签中确定目标NFC标签；
其中，NFC标签中预先存储有商户信息，商户信息可以包括<商户UID，商户名，商户注册地>等信息，其中商户UID确保该NFC标签的唯一性。当具有 NFC功能的支付终端靠近并触碰多张NFC标签时，这些NFC标签进入该支付终端的射频场，支付终端向射频场发出卡呼叫命令，进而射频场内所有的NFC标签由空闲状态(IDLE)转换为准备状态(READY)，支付终端检测到至少两个NFC标签。
在一种可能的实施方式中，为了实现支付终端和NFC标签之间的数据传输，方法300还可以包括：响应于检测到至少两个NFC标签，与至少两个NFC标签中的每一者建立非接触式连接。其中，非接触式连接用于实现支付装置和NFC标签之间进行非接触式的点对点数据传输。
当支付终端检测到至少两个NFC标签之后，在每一时刻只能对射频场中的一张射频卡进行读写操作，因此当多个NFC标签同时进入支付终端的射频场时，支付终端需要从检测到的NFC标签中选出唯一的NFC标签进行读写操作。
在一种可能的实施方式中，为了简便地确定唯一的目标NFC标签，可以采用第一种方案：利用基于射频卡协议(ISO14443)的防冲突规则确定目标NFC标签，并读取目标NFC标签的商户标识和商户注册地，商户标识包括商户UID和商户名。基于射频卡协议(ISO14443)的防冲突规则主要包括：面向位的防冲突机制(ISO14443 Type A使用)、面向时隙的防冲突机制(ISO14443 TypeB使用)。具体实现可参考现有技术，此处不再赘述。
在一种可能的实施方式中，为了使确定的目标NFC标签和实际商户一致，可以采用的第二种方案：依次读取至少两个NFC标签存储的商户标识和商户注册地，其中商户标识可以包括商户UID和商户名，并在支付终端的界面中列举至少两个NFC标签的商户标识，同时可以通知用户进行选择，比如在界面上显示“检测到多张NFC标签冲突，需要选择其中一个NFC标签”；检测支付终端的界面上的触控操作，当用户在支付终端的界面上选中其中一个NFC标签的商户标识时，根据检测到的触控操作确定目标NFC标签。此外，现有的射频卡协议(ISO14443)中，读取NFC标签仅限读取NFC标签的商户UID，为了实现上述读取NFC标签中存储的商户名和商户注册地的操作，需要修改现有的射频卡协议(ISO14443)，比如独立封装一套接口供支付终端调用，从而使NFC标签与支 付终端进行数据交互时，支付终端除了读取NFC标签的商户UID，同时还需要读取商户名、商户注册地等信息。通过采用本实施方式，可以由用户和商户沟通之后自主选择目标NFC标签，避免支付失败的情况，提高了用户体验，此外也可以提醒商户当前的支付风险。
在一种可能的实施方式中，方法还包括：在确定目标NFC标签之后，断开和其他NFC标签之间非接触式连接。
如图3所示，该方法300可以包括：
步骤S302：获取目标NFC标签中存储的商户注册地，并获取支付终端的当前位置；
其中，可以通过支付终端和目标NFC标签之间建立的非接触式连接传输获得获取目标NFC标签中存储的商户UID、商户名和商户注册地等信息；可以通过支付终端的GPS定位信息获取支付终端的当前位置。
如图3所示，该方法300可以包括：
步骤S303：生成并发起支付请求，其中，支付请求携带目标NFC标签的商户注册地和支付终端的当前位置。
其中，上述支付请求的接收方可以是与该支付终端通信连接的支付服务器。该支付请求用于使支付服务器能够基于目标NFC标签的商户注册地址和支付终端的当前地址进行对比，并根据对比结果进行支付或拒绝支付。
具体地，NFC标签中存储的商户注册地应当与该NFC标签的实际所在地应当具有一致性，利用NFC的短距离通信特点，当目标NFC标签携带的商户注册地和支付终端的当前位置一致时，支付服务器进行支付；相反，当目标NFC标签携带的商户注册地和支付终端的当前位置不一致时，支付服务器拒绝支付，保证了支付安全性。
在一种可能的实施方式中，生成并发起的支付请求中还包含支付金额和/或支付密码。方法还可以包括：在步骤S303之前，接收输入的支付金额和/或支付密码。应当理解，在一些小额支付场景中，也可以无需额外输入支付密码；在一些定额支付场景中，也可以无需输入支付金额，本申请对此不作具体限制。
在一种可能的实施方式中，生成并发起的支付请求中还包含标签冲突标识，该标签冲突标识用于指示检测到上述至少两个NFC标签的标签冲突情况，以使支付服务器响应于检测到标签冲突标识进行对比。通过采用本实施方式，利用在支付请求中携带标签冲突标识以指示NFC标签冲突情况，因此当支付服务器未检测到该标签冲突标识时，则该说明支付终端的射频范围内只有一个NFC标签，则无需执行对比操作。
在一种可能的实施方式中，还包括：接收支付服务器发送的支付完成消息或拒绝支付消息，之后断开与目标NFC标签之间的非接触式连接，完成一次支付。
在一种可能的实施方式中，为了提示支付者存在支付风险，还可以包括：接收支付服务器发送的告警信息，并在支付终端的界面上显示告警信息，告警信息用于指示多个NFC标签冲突。比如可以在支付完成消息或拒绝支付消息中附带“存在多张NFC标签冲突”，“NFC标签可能被覆盖”等警告信息，提醒支付者注意支付安全，同时也使支付者和商户了解支付失败的原因，以便于尽快做出修正。
在一种可能的实施方式中，上述图3所示的方法，可以应用在支付终端处于已解锁场景，也可以应用在支付终端处于未解锁的状态，如支付终端锁屏或息屏的场景。当应用在锁屏或息屏场景下时，本申请实施例还能够省去用户解锁支付终端的步骤，进一步减少用户操作，并实现快速支付。
本申请实施例提供的上述支付方法的各个方面，通过在NFC标签中加入商户注册地，且通过在支付终端生成并发起的支付请求中携带NFC标签的商户注册地和支付终端的当前位置，利用该支付请求能够进行安全性检测，比如，在NFC标签的商户注册地和支付终端的当前位置一致的情况下允许交易，在NFC标签的商户注册地和支付终端的当前位置不一致的情况下拒绝交易，提高了支付安全性。
图4为根据本申请一实施例的支付方法400的流程图，该支付方法400用于根据支付请求进行支付，应用于支付服务器。
如图4所示，方法400包括：
步骤S401：接收支付请求，支付请求携带目标NFC标签和支付终端的当前位置；其中，该支付请求的发送发可以是支付终端。
步骤S402：根据目标NFC标签携带的商户注册地和支付终端的当前位置进行对比；
步骤S403：根据对比结果进行支付或拒绝支付。
具体地，NFC标签中存储的商户注册地应当与该NFC标签的实际所在地应当具有一致性，利用NFC的短距离通信特点，当目标NFC标签携带的商户注册地和支付终端的当前位置一致时，支付服务器进行支付；相反，当目标标NFC标签携带的商户注册地和支付终端的当前位置不一致时，支付服务器拒绝支付，保证了支付安全性。
在一种可能的实施方式中，支付请求中还可以包含支付金额和/或支付密码。从而支付服务器在接收到支付请求之后，根据支付金额进行交易，和/或根据支付密码进行验证。应当理解，在一些小额支付场景中，也可以无需额外验证支付密码；在一些定额支付场景中，也可以根据预设支付金额进行交易而无需在支付请求中携带支付金额，本申请对此不作具体限制。
在一种可能的实施方式中，支付请求还包括标签冲突标识，从而支付服务器在接收到支付请求之后，响应于检测到标签冲突标识，根据目标NFC标签携带的商户注册地和支付终端的当前位置进行对比。
在一种可能的实施方式中，为了提示支付者和商户存在支付风险，若支付服务器根据对比结果进行支付，在支付完成之后，则向支付终端和/或商户终端发送支付完成消息和/或告警消息，比如在支付完成消息中附带“NFC标签可能被恶意覆盖了，请尽快检查并除去！”等用于指示多个NFC标签冲突的告警信息，这样商户可以及时得到有效的问题提醒，进一步提升了支付的使用体验，准确的定位支付风险问题，进一步保障了支付安全。若支付服务器根据对比结果拒绝支付，则向支付终端发送拒绝支付消息和/或告警信息，比如可以在拒绝支付消息中附带“存在多张NFC标签冲突”，“NFC标签可能被覆盖”等用于指 示多个NFC标签冲突的警告信息，提醒支付者注意支付安全，同时也使支付者和商户准确定位支付风险，以便于尽快做出修正。
本发明实施例还提供一种支付方法，应用于由至少一个具有NFC功能的支付终端以及支付服务器组成的支付系统，该方法包括：由支付终端执行图3所示的支付方法；由支付服务器执行图4所示的支付方法。
图5是根据本申请一实施方式的支付方法500的流程图，应用于由至少一个具有NFC功能的支付终端、支付服务器以及商户终端组成的支付系统。
如图5所示，在步骤S501中，支付终端触碰NFC标签，检测到多个NFC标签；在步骤S502中，支付终端和检测到的多个NFC标签建立非接触式连接；在步骤S503中，支付终端读取多个NFC标签的商户UID、商户名和商户注册地；在步骤S504中，在支付终端的界面中列举检测到的多个NFC标签的商户标识；在步骤S505中，检测支付终端的界面上的触控操作，当用户在支付终端的界面上选择某个NFC标签的商户标识时，根据检测到的触控操作确定用户选择的NFC标签作为目标NFC标签。在步骤S506中，断开支付终端和其他NFC标签之间的非接触式连接；在步骤S507中，获取支付终端的当前位置，(可选地)获取输入的支付金额和/或支付密码；在步骤S508中，支付终端向支付服务器发起支付请求，支付请求携带标签冲突标识，目标NFC标签的商户UID、商户名和商户注册地，支付终端的当前位置，(可选地)支付金额和/或支付密码等信息；在步骤S509中，支付服务器接收到支付请求，并基于目标NFC标签的商户注册地和支付终端的当前位置进行对比；在步骤S509之后在步骤S510a中，支付服务器在上述对比一致的情况下进行支付；在支付完成之后在步骤S511a中，支付服务器向支付终端发送交易完成消息，还可以向支付终端发送告警信息；在支付完成之后在步骤S512中，支付服务器向商户终端发送告警信息。或者，在步骤S509之后在步骤S510b中，支付服务器在上述对比不一致的情况下则拒绝支付；在拒绝支付之后在步骤S511b中，支付服务器向支付终端发送拒绝交易消息，还可以向支付终端发送告警信息。在步骤S511a或者步骤S511b之后在步骤S513中，支付终端接收到交易完成消息或者拒绝交易消息之后，断开和目 标NFC标签的无接触连接；(可选的)在步骤S512之后在步骤S514中，商户终端在接收到告警信息之后进行自检。
图6是本发明的另一实施方式的支付方法的流程图，应用于由至少一个具有NFC功能的支付终端、支付服务器以及商户终端组成的支付系统。
如图6所示，在步骤S601中，支付终端触碰NFC标签，检测到多个NFC标签；在步骤S602中，支付终端和检测到的多个NFC标签建立非接触式连接；在步骤S603中，支付终端基于射频卡协议的防冲突规则进行防冲突处理，选出其中一个NFC标签作为目标NFC标签，读取该目标NFC标签中存储的商户UID、商户名、商户注册地等信息；在步骤S604中，断开支付终端和其他NFC标签之间的非接触式连接；在步骤S605中，获取支付终端的当前位置，(可选地)获取输入的支付金额和/或支付密码；在步骤S606中，支付终端向支付服务器发起支付请求，支付请求携带标签冲突标识，目标NFC标签的商户UID、商户名和商户注册地，支付终端的当前位置，(可选地)支付金额和/或支付密码等信息。在步骤S607中，支付服务器接收到支付请求，并基于目标NFC标签携带的商户注册地和支付终端的当前位置进行对比；在步骤S607之后在步骤S608a中，支付服务器在上述对比一致的情况下进行支付；在支付完成之后在步骤S609a中，支付服务器向支付终端发送交易完成消息，还可以向支付终端发送告警信息；在支付完成之后在步骤S610中，支付服务器向商户终端发送告警信息。或者，在步骤S607之后在步骤S608b中，支付服务器在上述对比不一致的情况下则拒绝支付；在拒绝支付之后在步骤S609b中，支付服务器向支付终端发送拒绝交易消息，还可以向支付终端发送告警信息。在步骤S609a或者步骤S609b之后在步骤S611中，支付终端接收到交易完成消息或者拒绝交易消息之后，断开和目标NFC标签的无接触连接。(可选的)在步骤S610之后在步骤S612中，商户终端在接收到告警信息之后进行自检。
基于相同的技术构思，本发明实施例还提供一种支付终端。图7为本发明实施例提供的一种支付终端的结构示意图。
支付终端70具有NFC模块71和支付应用模块72，其中，支付应用模块72被配置为用于：当通过NFC模块71检测到至少两个NFC标签时，从至少两个NFC标签中确定目标NFC标签；通过NFC模块71获取目标NFC标签中存储的商户注册地，并获取支付终端的当前位置；生成并发起支付请求，支付请求携带目标NFC标签的商户注册地和支付终端的当前位置。
在一种可能的实施方式中，NFC模块71还用于：利用基于射频卡协议的防冲突规则确定目标NFC标签，并读取目标NFC标签存储的商户标识和商户注册地。
在一种可能的实施方式中，支付应用模块72，还用于：通过NFC模块71读取至少两个NFC标签存储的商户标识和商户注册地，并在支付终端的界面中列举至少两个NFC标签的商户标识；检测支付终端的界面上的触控操作，根据检测到的触控操作确定目标NFC标签。
在一种可能的实施方式中，NFC模块71还用于：响应于检测到至少两个NFC标签，与至少两个NFC标签中的每一者建立非接触式连接；在确定目标NFC标签之后，断开和其他NFC标签之间的非接触式连接。
在一种可能的实施方式中，支付应用模块72还用于：接收支付完成消息或拒绝支付消息；NFC模块71还用于：在接收支付完成消息或拒绝支付消息之后，断开与目标NFC标签之间的非接触式连接。
在一种可能的实施方式中，支付请求还包含标签冲突标识，用于指示所述至少两个NFC标签的冲突。
在一种可能的实施方式中，支付应用模块72还用于：接收告警信息，并在支付终端的界面上显示告警信息，告警信息用于指示多个NFC标签冲突。
基于相同的技术构思，本发明实施例还提供一种支付服务器。图8为本发明实施例提供的一种支付服务器的结构示意图。
如图8所示，支付服务器80包括：接收单元801，用于接收支付请求，支付请求包含目标NFC标签和支付终端的当前位置；对比单元802，用于根据目 标NFC标签携带的商户注册地和支付终端的当前位置进行对比；支付单元803，根据对比结果进行支付或拒绝支付。
在一种可能的实施方式中，支付请求还包括标签冲突标识，对比单元802还用于：响应于检测到标签冲突标识，根据目标NFC标签携带的商户注册地和支付终端的当前位置进行对比。
在一种可能的实施方式中，还包括发送单元，用于：若根据对比结果进行支付，则向支付终端和/或商户终端发送支付完成消息和/或告警消息；若根据对比结果拒绝支付，则向支付终端发送拒绝支付消息和/或告警信息，告警信息用于指示多个NFC标签冲突。
基于相同的技术构思，本发明实施例还提供一种支付系统。
支付系统包括：至少一个具有NFC功能的支付终端以及支付服务器，其中支付终端用于执行如图3所示的方法；支付服务器用于执行如图4所示的方法。
在一种可能的实施方式中，支付系统还包括商户终端。
图9为根据本申请一实施例的支付终端，用于执行图3所示出的支付方法，该装置包括：至少一个处理器；以及，与至少一个处理器通信连接的存储器；其中，存储器存储有可被至少一个处理器执行的指令，指令被至少一个处理器执行，以使至少一个处理器能够执行：
当检测到至少两个NFC标签时，从至少两个NFC标签中确定目标NFC标签；获取目标NFC标签中存储的商户注册地，并获取支付终端的当前位置；生成并发起支付请求，支付请求携带目标NFC标签的商户注册地和支付终端的当前位置。图10为根据本申请一实施例的支付服务器，用于执行图4所示出的支付方法，该装置包括：至少一个处理器；以及，与至少一个处理器通信连接的存储器；其中，存储器存储有可被至少一个处理器执行的指令，指令被至少一个处理器执行，以使至少一个处理器能够执行：
接收支付请求，支付请求携带目标NFC标签和支付终端的当前位置；根据目标NFC标签携带的商户注册地和支付终端的当前位置进行对比；根据对比结果进行支付或拒绝支付。
根据本申请的一些实施例，提供了支付方法的非易失性计算机存储介质，其上存储有计算机可执行指令，该计算机可执行指令设置为在由处理器运行时执行图3所示出的支付方法或者图4所示支付方法。
本申请中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于装置、设备和计算机可读存储介质实施例而言，由于其基本相似于方法实施例，所以其描述进行了简化，相关之处可参见方法实施例的部分说明即可。
本申请实施例提供的装置、设备和计算机可读存储介质与方法是一一对应的，因此，装置、设备和计算机可读存储介质也具有与其对应的方法类似的有益技术效果，由于上面已经对方法的有益技术效果进行了详细说明，因此，这里不再赘述装置、设备和计算机可读存储介质的有益技术效果。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中 的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。此外，尽管在附图中以特定顺序描述了本发明方法的操作，但是，这并非要求或者暗示必须按照该特定顺序来执行这些操作，或是必须执行全部所示的操作才能实现期望的结果。附加地或备选地，可以省略某些步骤，将多个步骤合并为一个步骤执行，和/或将一个步骤分解为多个步骤执行。
虽然已经参考若干具体实施方式描述了本发明的精神和原理，但是应该理解，本发明并不限于所公开的具体实施方式，对各方面的划分也不意味着这些方面中的特征不能组合以进行受益，这种划分仅是为了表述的方便。本发明旨在涵盖所附权利要求的精神和范围内所包括的各种修改和等同布置。

Claims (22)

  1. 一种支付方法，其特征在于，应用于具有NFC功能的支付终端，所述方法包括：
    当检测到至少两个NFC标签时，从所述至少两个NFC标签中确定目标NFC标签；
    获取所述目标NFC标签中存储的商户注册地，并获取支付终端的当前位置；
    生成并发起支付请求，所述支付请求携带所述目标NFC标签的所述商户注册地和所述支付终端的当前位置。
  2. 根据权利要求1所述的方法，其特征在于，从所述至少两个NFC标签中确定目标NFC标签，还包括：
    利用基于射频卡协议的防冲突规则确定所述目标NFC标签，并读取所述目标NFC标签存储的商户标识和所述商户注册地。
  3. 根据权利要求1所述的方法，其特征在于，从所述至少两个NFC标签中确定目标NFC标签，还包括：
    读取所述至少两个NFC标签存储的商户标识和所述商户注册地，并在所述支付终端的界面中列举所述至少两个NFC标签的所述商户标识；
    检测所述支付终端的界面上的触控操作，根据检测到的所述触控操作确定所述目标NFC标签。
  4. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    响应于检测到所述至少两个NFC标签，与所述至少两个NFC标签中的每一者建立非接触式连接；
    在所述确定目标NFC标签之后，断开和其他NFC标签之间的所述非接触式连接。
  5. 根据权利要求4所述的方法，其特征在于，还包括：
    接收支付完成消息或拒绝支付消息，之后断开与所述目标NFC标签之间的非接触式连接。
  6. 根据权利要求1所述的方法，其特征在于，所述支付请求还包含标签冲突标识，用于指示所述至少两个NFC标签的冲突。
  7. 根据权利要求1所述的方法，其特征在于，还包括：
    接收告警信息，并在所述支付终端的界面上显示所述告警信息，所述告警信息用于指示所述至少两个NFC标签的冲突。
  8. 一种支付方法，其特征在于，应用于支付服务器，所述方法包括：
    接收支付请求，所述支付请求携带目标NFC标签和支付终端的当前位置；
    根据所述目标NFC标签携带的商户注册地和所述支付终端的当前位置进行对比；
    根据所述对比结果进行支付或拒绝支付。
  9. 根据权利要求8所述的方法，其特征在于，所述支付请求还包括标签冲突标识，所述方法还包括：
    响应于检测到所述标签冲突标识，根据所述目标NFC标签携带的所述商户注册地和所述支付终端的当前位置进行对比。
  10. 根据权利要求8所述的方法，其特征在于，还包括：
    若根据所述对比结果进行支付，则向所述支付终端和/或商户终端发送支付完成消息和/或告警消息；
    若根据所述对比结果拒绝支付，则向所述支付终端发送拒绝支付消息和/或告警信息，所述告警信息用于指示多个NFC标签冲突。
  11. 一种支付方法，其特征在于，应用于由至少一个具有NFC功能的支付终端以及支付服务器组成的支付系统，所述方法包括：
    由所述支付终端执行如权利要求1-7中任一项所述的支付方法；
    由所述支付服务器用于执行如权利要求8-10中任一项所述的支付方法。
  12. 一种支付终端，其特征在于，所述支付终端具有NFC模块，还包括：
    支付应用模块，被配置为用于：
    当通过NFC模块检测到至少两个NFC标签时，从所述至少两个NFC标签中确定目标NFC标签；
    通过NFC模块获取所述目标NFC标签中存储的商户注册地，并获取支付终端的当前位置；
    生成并发起支付请求，所述支付请求携带所述目标NFC标签的所述商户注册地和所述支付终端的当前位置。
  13. 根据权利要求12所述的支付终端，其特征在于，
    所述NFC模块还用于：
    利用基于射频卡协议的防冲突规则确定所述目标NFC标签，并读取所述目标NFC标签存储的商户标识和所述商户注册地。
  14. 根据权利要求12所述的支付终端，其特征在于，
    所述支付应用模块，还用于：
    通过所述NFC模块读取所述至少两个NFC标签存储的商户标识和所述商户注册地，并在所述支付终端的界面中列举所述至少两个NFC标签的所述商户标识；
    检测所述支付终端的界面上的触控操作，根据检测到的所述触控操作确定所述目标NFC标签。
  15. 根据权利要求12所述的支付终端，其特征在于，
    所述NFC模块还用于：
    响应于检测到所述至少两个NFC标签，与所述至少两个NFC标签中的每一者建立非接触式连接；
    在所述确定目标NFC标签之后，断开和其他NFC标签之间的非接触式连接。
  16. 根据权利要求15所述的支付终端，其特征在于，
    所述支付应用模块还用于：接收支付完成消息或拒绝支付消息；
    所述NFC模块还用于：在接收支付完成消息或拒绝支付消息之后，断开与所述目标NFC标签之间的非接触式连接。
  17. 根据权利要求12所述的支付终端，其特征在于，所述支付请求还包含标签冲突标识用于指示所述至少两个NFC标签的冲突。
  18. 根据权利要求12所述的支付终端，其特征在于，
    所述支付应用模块还用于：
    接收告警信息，并在所述支付终端的界面上显示所述告警信息，所述告警信息用于指示所述至少两个NFC标签的冲突。
  19. 一种支付服务器，其特征在于，包括：
    接收单元，用于接收支付请求，所述支付请求包含目标NFC标签和所述支付终端的当前位置；
    对比单元，用于根据所述目标NFC标签携带的商户注册地和所述支付终端的当前位置进行对比；
    支付单元，根据所述对比结果进行支付或拒绝支付。
  20. 根据权利要求19所述的支付服务器，其特征在于，所述支付请求还包括标签冲突标识，所述对比单元还用于：
    响应于检测到所述标签冲突标识，根据所述目标NFC标签携带的所述商户注册地和所述支付终端的当前位置进行对比。
  21. 根据权利要求19所述的支付服务器，其特征在于，还包括发送单元，用于：
    若根据所述对比结果进行支付，则向所述支付终端和/或商户终端发送支付完成消息和/或告警消息；
    若根据所述对比结果拒绝支付，则向所述支付终端发送拒绝支付消息和/或告警信息，所述告警信息用于指示多个NFC标签冲突。
  22. 一种支付系统，其特征在于，包括：至少一个具有NFC功能的支付终端以及支付服务器，其中所述支付终端用于执行如权利要求1-7中任一项所述的方法；所述支付服务器用于执行如权利要求8-10中任一项所述的方法。
PCT/CN2021/074862 2020-02-03 2021-02-02 一种支付方法、终端、服务器及系统 WO2021155785A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010078735.1A CN111242608B (zh) 2020-02-03 2020-02-03 一种支付方法、终端、服务器及系统
CN202010078735.1 2020-02-03

Publications (1)

Publication Number Publication Date
WO2021155785A1 true WO2021155785A1 (zh) 2021-08-12

Family

ID=70869951

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/074862 WO2021155785A1 (zh) 2020-02-03 2021-02-02 一种支付方法、终端、服务器及系统

Country Status (2)

Country Link
CN (1) CN111242608B (zh)
WO (1) WO2021155785A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111242608B (zh) * 2020-02-03 2024-03-22 中国银联股份有限公司 一种支付方法、终端、服务器及系统

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120068828A1 (en) * 2009-05-29 2012-03-22 Telefonaktieolaget L M Ericsson (Publ) Method, apparatus, and computer program product for detecting risk tags
US20130045686A1 (en) * 2011-08-18 2013-02-21 Kt Corporation System, mobile communication terminal and method for providing information
CN105631662A (zh) * 2015-06-19 2016-06-01 宇龙计算机通信科技(深圳)有限公司 Nfc支付方法、nfc支付系统和移动终端
CN108734462A (zh) * 2018-05-15 2018-11-02 惠龙易通国际物流股份有限公司 一种移动支付方法、装置、系统和存储介质
CN109600714A (zh) * 2018-11-26 2019-04-09 努比亚技术有限公司 一种支付方法、终端及可读存储介质
CN110400138A (zh) * 2019-07-30 2019-11-01 中国工商银行股份有限公司 防盗刷的移动支付方法和装置
CN111242608A (zh) * 2020-02-03 2020-06-05 中国银联股份有限公司 一种支付方法、终端、服务器及系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012143744A1 (en) * 2011-04-20 2012-10-26 Sony Ericsson Mobile Communications Ab Methods, systems and computer program products for registration of and anonymous communications related to tagged objects
US10198604B2 (en) * 2014-02-21 2019-02-05 Sony Mobile Communications Inc. Detection of unauthorized tags
CN105023299A (zh) * 2014-04-28 2015-11-04 戴姆勒大中华区投资有限公司 联网车载支付系统和支付方法
US10373167B2 (en) * 2016-06-30 2019-08-06 Square, Inc. Logical validation of devices against fraud
CN106779677A (zh) * 2016-11-21 2017-05-31 深圳付贝科技有限公司 一种支付方法及其装置、电子设备及支付系统
WO2019000440A1 (zh) * 2017-06-30 2019-01-03 华为技术有限公司 Nfc支付方法及终端
CN109359968A (zh) * 2018-09-28 2019-02-19 中国工商银行股份有限公司 一种支付方法、装置、电子设备及支付标签

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120068828A1 (en) * 2009-05-29 2012-03-22 Telefonaktieolaget L M Ericsson (Publ) Method, apparatus, and computer program product for detecting risk tags
US20130045686A1 (en) * 2011-08-18 2013-02-21 Kt Corporation System, mobile communication terminal and method for providing information
CN105631662A (zh) * 2015-06-19 2016-06-01 宇龙计算机通信科技(深圳)有限公司 Nfc支付方法、nfc支付系统和移动终端
CN108734462A (zh) * 2018-05-15 2018-11-02 惠龙易通国际物流股份有限公司 一种移动支付方法、装置、系统和存储介质
CN109600714A (zh) * 2018-11-26 2019-04-09 努比亚技术有限公司 一种支付方法、终端及可读存储介质
CN110400138A (zh) * 2019-07-30 2019-11-01 中国工商银行股份有限公司 防盗刷的移动支付方法和装置
CN111242608A (zh) * 2020-02-03 2020-06-05 中国银联股份有限公司 一种支付方法、终端、服务器及系统

Also Published As

Publication number Publication date
CN111242608A (zh) 2020-06-05
CN111242608B (zh) 2024-03-22

Similar Documents

Publication Publication Date Title
TWI676107B (zh) 資訊交互方法及裝置
US11068676B2 (en) Service processing method, device and apparatus
WO2017185367A1 (zh) 一种交易应用的选择方法和终端
CN107657448B (zh) 一种账户创建、账户充值、数据同步方法及设备
US11200558B2 (en) Automatic vending
WO2015062412A1 (en) Method, device and system for online payment
JP2023524538A (ja) 近距離無線通信ｎｆｃ通信方法、装置及び電子機器
US20160132918A1 (en) One-tap sign up for merchant loyalty programs
US10810591B2 (en) Virtual reality headset device and payment method
US12050677B2 (en) Medium for temporary account access
WO2021155785A1 (zh) 一种支付方法、终端、服务器及系统
US10542018B1 (en) Security breach notification
US10223687B2 (en) Link of mobile devices to facilitate mobile commerce transactions
WO2015101057A1 (en) Data processing method and related device and system
US10373144B1 (en) Transaction payment processing by multiple data centers
US20220092564A1 (en) Resource configuration methods, apparatuses, and systems
US20190188660A1 (en) Payment apparatus and method for enabling a payment device for remotely accessing a transaction
US20180288575A1 (en) Tracking system
US20210288525A1 (en) Transaction device capable of managing and routing power from an external power source
WO2023050900A1 (zh) 数据处理方法、系统、终端和计算机可读存储介质
US12051068B2 (en) System, method, and computer program product for remote authorization of payment transactions
CN114519580A (zh) 近距离通信的请求支付方法、支付方法、终端及存储介质
KR20200112564A (ko) 동적 nfc 정보와 동적 2차원 바코드 생성 방법
OA16900A (en) Method, device and system for establishing conversation relation.

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21750580

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21750580

Country of ref document: EP

Kind code of ref document: A1