CN111242608A - Payment method, terminal, server and system - Google Patents

Payment method, terminal, server and system Download PDF

Info

Publication number
CN111242608A
CN111242608A CN202010078735.1A CN202010078735A CN111242608A CN 111242608 A CN111242608 A CN 111242608A CN 202010078735 A CN202010078735 A CN 202010078735A CN 111242608 A CN111242608 A CN 111242608A
Authority
CN
China
Prior art keywords
payment
nfc
terminal
payment terminal
merchant
Prior art date
Legal status (The legal status 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 status listed.)
Granted
Application number
CN202010078735.1A
Other languages
Chinese (zh)
Other versions
CN111242608B (en
Inventor
陈成钱
郭伟
周钰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Unionpay Co Ltd
Original Assignee
China Unionpay Co Ltd
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 China Unionpay Co Ltd filed Critical China Unionpay Co Ltd
Priority to CN202010078735.1A priority Critical patent/CN111242608B/en
Publication of CN111242608A publication Critical patent/CN111242608A/en
Priority to PCT/CN2021/074862 priority patent/WO2021155785A1/en
Application granted granted Critical
Publication of CN111242608B publication Critical patent/CN111242608B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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

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

The invention provides a payment method, a terminal, a server and a system, and the payment method applied to a payment terminal with an NFC function comprises the following steps: when the at least two NFC tags are detected, determining a target NFC tag from the at least two NFC tags; acquiring a merchant registration place stored in a target NFC label, and acquiring the current position of a payment terminal; and generating and initiating a payment request, wherein the payment request carries the current positions of the merchant registration place and the payment terminal of the target NFC label. The payment method applied to the payment server comprises the following steps: receiving a payment request, wherein the payment request carries a target NFC label and the current position of a payment terminal; comparing the current positions of the merchant registration place and the payment terminal carried by the target NFC label; and carrying out payment or refusing payment according to the comparison result. By the method, the payment safety can be improved.

Description

Payment method, terminal, server and system
Technical Field
The invention belongs to the field of financial data processing, and particularly relates to a payment method, a terminal, a server and a system.
Background
This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.
Near Field Communication (NFC) is a short-range high-Frequency wireless Communication technology, and evolved from Radio Frequency Identification (RFID). NFC allows short-range contactless point-to-point data transfer between electronic devices.
Currently, many mobile terminals support NFC payment functionality. For example, by means of a label payment technology of the UnionPay, an NFC label is embedded in a merchant acceptance label, merchant information is stored in an NFC chip of the NFC label, and payment for a merchant can be initiated by directly touching the label by using a cloud flash payment APP or a mobile phone with a specified model. The main principle is as shown in fig. 1, wherein a "card reader mode" is opened by a mobile phone supporting an NFC function, a small amount of electric energy is transferred by touching an NFC tag with the mobile phone, then an NFC tag circuit is driven by the small amount of electric energy, and data information stored in the NFC tag is transferred to the mobile phone, the mobile phone wakes up an installed payment application after reading data stored in the NFC tag, and enters a payment interface of a merchant represented by the NFC tag, and payment is completed after inputting amount and a password.
However, the existing scheme cannot avoid the payment security problem after the NFC tag is maliciously covered by a lawless person using the NFC tag of a non-local merchant. As shown in fig. 2, when the NFC tag of the merchant is covered by the NFC tag of the non-local merchant used by a lawbreaker, and a customer uses a mobile phone to perform NFC payment, a situation that a plurality of NFC tags are in the same mobile phone workplace may occur, and according to the existing technical solution, the mobile phone may only read merchant information (which is selected to be uncontrollable) in one of the NFC tags, which may cause a problem of payment security.
Disclosure of Invention
In view of the above-mentioned problems in the prior art, a payment method, a terminal, a server, a system, and a computer-readable storage medium are provided, by which the above-mentioned problems can be solved.
The present invention provides the following.
In a first aspect, a payment method is provided, which is applied to a payment terminal with an NFC function, and the method includes: when the at least two NFC tags are detected, determining a target NFC tag from the at least two NFC tags; acquiring a merchant registration place stored in a target NFC label, and acquiring the current position of a payment terminal; and generating and initiating a payment request, wherein the payment request carries the current positions of the merchant registration place and the payment terminal of the target NFC label.
In one possible embodiment, determining the target NFC tag from at least two NFC tags further comprises: and determining a target NFC label by using an anti-collision rule based on a radio frequency card protocol, and reading a merchant identifier and a merchant registration place stored in the target NFC label.
In one possible embodiment, determining the target NFC tag from at least two NFC tags further comprises: reading merchant identifications stored in at least two NFC labels and a merchant registration place, and enumerating the merchant identifications of the at least two NFC labels in an interface of the payment terminal; and detecting touch operation on an interface of the payment terminal, and determining the target NFC label according to the detected touch operation.
In one possible embodiment, in response to detecting the at least two NFC tags, establishing a contactless connection with each of the at least two NFC tags; after the target NFC tag is determined, the non-contact connection with other NFC tags is disconnected.
In one possible embodiment, the method further comprises: and receiving a payment completion message or a payment refusal message, and then disconnecting the non-contact connection with the target NFC tag.
In a possible embodiment, the payment request further comprises a tag collision identifier for indicating a collision of the at least two NFC tags.
In one possible embodiment, the method further comprises: and receiving alarm information, and displaying the alarm information on an interface of the payment terminal, wherein the alarm information is used for indicating the conflict of the plurality of NFC labels.
In a second aspect, a payment method is provided, which is applied to a payment server, and includes: receiving a payment request, wherein the payment request carries a target NFC label and the current position of a payment terminal; comparing the current positions of the merchant registration place and the payment terminal carried by the target NFC label; and carrying out payment or refusing payment according to the comparison result.
In one possible embodiment, the payment request further includes a tag conflict identifier, and the method further includes: and responding to the detection of the label conflict identification, and comparing the current positions of the merchant registration place and the payment terminal carried by the target NFC label.
In one possible embodiment, the method further comprises: if the payment is carried out according to the comparison result, sending a payment completion message and/or an alarm message to the payment terminal and/or the merchant terminal; and if the payment is rejected according to the comparison result, sending a payment rejection message and/or alarm information to the payment terminal, wherein the alarm information is used for indicating the conflict of the plurality of NFC labels.
In a third aspect, a payment method is provided, which is applied to a payment system composed of at least one payment terminal with an NFC function and a payment server, and includes: performing, by a payment terminal, a payment method as in the first aspect; used by a payment server for performing a payment method as in the second aspect.
In a fourth aspect, a payment terminal is provided, which has an NFC module, and further includes: a payment application module configured to: determining a target NFC tag from the at least two NFC tags when the at least two NFC tags are detected by the NFC module; acquiring a merchant registration place stored in a target NFC label through an NFC module, and acquiring the current position of a payment terminal; and generating and initiating a payment request, wherein the payment request carries the current positions of the merchant registration place and the payment terminal of the target NFC label.
In one possible implementation, the NFC module is further configured to: and determining a target NFC label by using an anti-collision rule based on a radio frequency card protocol, and reading a merchant identifier and a merchant registration place stored in the target NFC label.
In one possible implementation, the payment application module is further configured to: reading merchant identifications and merchant registration places stored by at least two NFC labels through an NFC module, and enumerating the merchant identifications of the at least two NFC labels in an interface of a payment terminal; and detecting touch operation on an interface of the payment terminal, and determining the target NFC label according to the detected touch operation.
In one possible implementation, the NFC module is further configured to: in response to detecting the at least two NFC tags, establishing a contactless connection with each of the at least two NFC tags; after the target NFC tag is determined, the non-contact connection with other NFC tags is disconnected.
In one possible implementation, the payment application module is further configured to: receiving a payment completion message or a payment refusal message; the NFC module is further configured to: after receiving the payment completion message or the payment denial message, the contactless connection with the target NFC tag is disconnected.
In a possible embodiment, the payment request further comprises a tag collision identifier for indicating a collision of the at least two NFC tags.
In one possible implementation, the payment application module is further configured to: and receiving alarm information sent by the payment server, and displaying the alarm information on an interface of the payment terminal, wherein the alarm information is used for indicating the conflict of at least two NFC labels.
In a fifth aspect, a payment server is provided, comprising: the payment terminal comprises a receiving unit, a payment processing unit and a payment processing unit, wherein the receiving unit is used for receiving a payment request which comprises a target NFC label and the current position of the payment terminal; the comparison unit is used for comparing the merchant registration place carried by the target NFC label with the current position of the payment terminal; and the payment unit is used for paying or refusing payment according to the comparison result.
In a possible embodiment, the payment request further includes a tag conflict identifier, and the comparing unit is further configured to: and responding to the detection of the label conflict identification, and comparing the current positions of the merchant registration place and the payment terminal carried by the target NFC label.
In a possible implementation, the method further includes a sending unit, configured to: if the payment is carried out according to the comparison result, sending a payment completion message and/or an alarm message to the payment terminal and/or the merchant terminal;
and if the payment is rejected according to the comparison result, sending a payment rejection message and/or alarm information to the payment terminal, wherein the alarm information is used for indicating the conflict of the plurality of NFC labels.
In a sixth aspect, a payment system is provided, which includes: at least one NFC-enabled payment terminal and a payment server, wherein the payment terminal is configured to perform the method according to the first aspect; the payment server is adapted to perform the method of the second aspect.
In a seventh aspect, a payment terminal is provided, comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform: when the at least two NFC tags are detected, determining a target NFC tag from the at least two NFC tags; acquiring a merchant registration place stored in a target NFC label, and acquiring the current position of a payment terminal; and generating and initiating a payment request, wherein the payment request carries the current positions of the merchant registration place and the payment terminal of the target NFC label.
In an eighth aspect, there is provided a payment server comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform: receiving a payment request, wherein the payment request carries a target NFC label and the current position of a payment terminal; comparing the current positions of the merchant registration place and the payment terminal carried by the target NFC label; and carrying out payment or refusing payment according to the comparison result.
In a ninth aspect, there is provided a computer readable storage medium storing a program which, when executed by a multi-core processor, causes the multi-core processor to perform the method of the first or second aspect.
The embodiment of the application adopts at least one technical scheme which can achieve the following beneficial effects: in the embodiment, the merchant registration place of the NFC tag and the current position of the payment terminal are added in the payment request generated and initiated by the payment terminal, so that the security payment can be carried out based on the merchant registration place of the NFC tag and the current position of the payment terminal, and the payment security is improved.
It should be understood that the above description is only an overview of the technical solutions of the present invention, so as to clearly understand the technical means of the present invention, and thus can be implemented according to the content of the description. In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in detail below.
Drawings
The advantages and benefits described herein, as well as other advantages and benefits, will be apparent to those of ordinary skill in the art upon reading the following detailed description of the exemplary embodiments. The drawings are only for purposes of illustrating exemplary embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like elements throughout. In the drawings:
FIG. 1 is a schematic diagram of a payment transaction performed via an NFC tag;
fig. 2 is a schematic diagram illustrating a scenario of multiple NFC tag collision in the prior art;
FIG. 3 is a schematic flow chart of a payment method according to an embodiment of the present invention;
FIG. 4 is a schematic flow chart of a payment method according to another embodiment of the present invention;
FIG. 5 is a schematic flow chart diagram of a payment method according to yet another embodiment of the present invention;
FIG. 6 is a schematic flow diagram of a payment method according to yet another embodiment of the 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 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.
In the drawings, the same or corresponding reference numerals indicate the same or corresponding parts.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
In the present invention, it is to be understood that terms such as "including" or "having," or the like, are intended to indicate the presence of the disclosed features, numbers, steps, behaviors, components, parts, or combinations thereof, and are not intended to preclude the possibility of the presence of one or more other features, numbers, steps, behaviors, components, parts, or combinations thereof.
It should be noted that the embodiments and features of the embodiments may be combined with each other without conflict. The present invention will be described in detail below with reference to the embodiments with reference to the attached drawings.
The embodiment of the invention provides a payment method, and the inventive concept of the method is introduced firstly.
As shown in fig. 2, a payment terminal with an NFC function generally implements transaction payment by approaching and touching an NFC tag, and when there are multiple NFC tags in a radio frequency coverage area of the payment terminal, in order to further secure payment transaction security, an embodiment of the present invention provides a payment method, where when the payment terminal detects at least two NFC tags, a target NFC tag is determined from the at least two NFC tags; acquiring current positions of a target NFC label and a payment terminal; the target NFC label carries a merchant registration place; the payment terminal initiates a payment request to the payment server, the payment request carries the target NFC label and the current position of the payment terminal, and security detection can be performed by using the payment request, for example, transaction is allowed under the condition that a merchant registration place of the NFC label is consistent with the current position of the payment terminal, and transaction is refused under the condition that the merchant registration place of the NFC label is inconsistent with the current position of the payment terminal, so that the payment security is improved.
Those skilled in the art will appreciate that the application scenario depicted in FIG. 2 is merely one example in which embodiments of the present invention may be implemented. The scope of applicability of the embodiments of the present invention is not limited in any way. Having described the general principles of the invention, various non-limiting embodiments of the invention are described in detail below.
Fig. 3 is a flowchart of a payment method 300 according to an embodiment of the present application, which is used for generating a payment request and applying the payment request to a payment terminal having an NFC function, where the payment terminal may be a smart phone, a tablet computer, or another similar mobile smart terminal having an NFC communication function, and a payment application supporting the NFC payment function is installed, such as a "cloud flash payment" application installed on the payment terminal, and a user may set the "cloud flash payment" application as an application that the payment terminal defaults to perform NFC payment, and set the "cloud flash payment" application to automatically run in response to detecting an NFC tag. For another example, the payment application may also be an application preset by a mobile phone manufacturer or referred to as a system-owned application, and can carry card simulation applications supporting NFC payment, such as a bank card and a bus card, which is not particularly limited in this application. In the flow shown in fig. 3, from the device perspective, the execution subject may be one or more electronic devices; from the program perspective, the execution main body may accordingly be a program loaded on these electronic devices.
As shown in fig. 3, the method 300 may include:
step S301: when the at least two NFC tags are detected, determining a target NFC tag from the at least two NFC tags;
the NFC tag is stored with merchant information in advance, the merchant information may include information such as < merchant UID, merchant name, merchant registration place >, and the like, wherein the merchant UID ensures the uniqueness of the NFC tag. When a payment terminal with an NFC function is close to and touches a plurality of NFC labels, the NFC labels enter a radio frequency field of the payment terminal, the payment terminal sends a card calling command to the radio frequency field, all the NFC labels in the radio frequency field are converted into a READY state (READY) from an IDLE state (IDLE), and the payment terminal detects at least two NFC labels.
In one possible implementation, to implement data transmission between the payment terminal and the NFC tag, the method 300 may further include: in response to detecting the at least two NFC tags, a contactless connection is established with each of the at least two NFC tags. The non-contact connection is used for realizing non-contact point-to-point data transmission between the payment device and the NFC tag.
After the payment terminal detects at least two NFC tags, only one radio frequency card in the radio frequency field can be read and written at each moment, so that when a plurality of NFC tags enter the radio frequency field of the payment terminal at the same time, the payment terminal needs to select the only NFC tag from the detected NFC tags for reading and writing.
In one possible embodiment, in order to easily determine the unique target NFC tag, a first scheme may be adopted: and determining a target NFC label by using anti-collision rules based on a radio frequency card protocol (ISO14443), and reading a merchant identifier and a merchant registration place of the target NFC label, wherein the merchant identifier comprises a merchant UID and a merchant name. Anti-collision rules based on the radio frequency card protocol (ISO14443) mainly include: a bit-oriented anti-collision mechanism (used by ISO14443 Type a), a slot-oriented anti-collision mechanism (used by ISO14443 Type b). The specific implementation can refer to the prior art, and is not described herein in detail.
In a possible implementation, in order to make the determined target NFC tag consistent with the actual merchant, a second scheme may be adopted: sequentially reading merchant identifications and merchant registration places stored in at least two NFC tags, wherein the merchant identifications can include a merchant UID and a merchant name, enumerating the merchant identifications of the at least two NFC tags in an interface of a payment terminal, and simultaneously informing a user to select, for example, displaying that 'a plurality of NFC tags are detected to conflict, and one of the NFC tags needs to be selected' on the interface; and detecting touch operation on an interface of the payment terminal, and when a user selects a merchant identifier of one of the NFC tags on the interface of the payment terminal, determining a target NFC tag according to the detected touch operation. In addition, in the existing radio frequency card protocol (ISO14443), the reading of the NFC tag is limited to only reading the merchant UID of the NFC tag, and in order to implement the above operation of reading the merchant name and the merchant registration location stored in the NFC tag, the existing radio frequency card protocol (ISO14443) needs to be modified, for example, a set of interfaces is independently packaged for being called by the payment terminal, so that when the NFC tag and the payment terminal perform data interaction, the payment terminal needs to read the merchant UID of the NFC tag, and also needs to read information such as the merchant name and the merchant registration location. By adopting the embodiment, the target NFC label can be selected independently after the user communicates with the merchant, the condition of payment failure is avoided, the user experience is improved, and in addition, the current payment risk of the merchant can be reminded.
In one possible embodiment, the method further comprises: after the target NFC tag is determined, the non-contact connection with other NFC tags is disconnected.
As shown in fig. 3, the method 300 may include:
step S302: acquiring a merchant registration place stored in a target NFC label, and acquiring the current position of a payment terminal;
the information such as the merchant UID, the merchant name and the merchant registration place stored in the target NFC label can be acquired through the non-contact connection transmission established between the payment terminal and the target NFC label; the current position of the payment terminal can be obtained through the GPS positioning information of the payment terminal.
As shown in fig. 3, the method 300 may include:
step S303: and generating and initiating a payment request, wherein the payment request carries the current positions of the merchant registration place and the payment terminal of the target NFC label.
The receiver of the payment request may be a payment server in communication connection with the payment terminal. The payment request is used for enabling the payment server to compare the merchant registration address of the target NFC label with the current address of the payment terminal, and to pay or reject payment according to the comparison result.
Specifically, a merchant registration place stored in the NFC tag should have consistency with an actual location of the NFC tag, and the payment server performs payment when the merchant registration place carried by the target NFC tag is consistent with the current location of the payment terminal by using the short-range communication characteristic of NFC; on the contrary, when the merchant registration place carried by the target NFC label is inconsistent with the current position of the payment terminal, the payment server refuses payment, and the payment security is ensured.
In one possible embodiment, the generated and initiated payment request further includes a payment amount and/or a payment password. The method may further comprise: before step S303, the input payment amount and/or payment password is received. It should be understood that in some micropayment scenarios, additional input of a payment password may not be required; in some quota payment scenarios, the payment amount may not need to be input, and this application does not specifically limit this.
In a possible implementation manner, the generated and initiated payment request further includes a tag collision identifier, where the tag collision identifier is used to indicate that tag collision situations of the at least two NFC tags are detected, so that the payment server compares the tag collision identifiers in response to the detection of the tag collision identifiers. By adopting the embodiment, the tag conflict identifier carried in the payment request is utilized to indicate the NFC tag conflict condition, so that when the payment server does not detect the tag conflict identifier, only one NFC tag exists in the radio frequency range of the payment terminal, and the comparison operation is not required to be executed.
In one possible embodiment, the method further comprises: and receiving a payment completion message or a payment refusing message sent by the payment server, and then disconnecting the non-contact connection with the target NFC tag to complete one-time payment.
In a possible implementation, in order to prompt the payer to have a payment risk, the method may further include: and receiving alarm information sent by the payment server, and displaying the alarm information on an interface of the payment terminal, wherein the alarm information is used for indicating the conflict of the plurality of NFC labels. For example, warning information such as "there are multiple NFC tag conflicts", "NFC tag may be covered" and the like may be attached to the payment completion message or the payment denial message to remind the payer of paying safety, and at the same time, the payer and the merchant know the reason of payment failure, so as to make a correction as soon as possible.
In a possible implementation manner, the method shown in fig. 3 may be applied to a scenario where the payment terminal is unlocked, or may be applied to a scenario where the payment terminal is not unlocked, such as a scenario where the payment terminal locks a screen or turns off a screen. When the method and the device are applied to a screen locking or screen turning scene, the step of unlocking the payment terminal by a user can be omitted, user operation is further reduced, and quick payment is achieved.
In various aspects of the payment method provided by the embodiment of the application, the merchant registration place is added to the NFC tag, and the merchant registration place of the NFC tag and the current location of the payment terminal are carried in the payment request generated and initiated by the payment terminal, so that security detection can be performed by using the payment request, for example, a transaction is allowed when the merchant registration place of the NFC tag and the current location of the payment terminal are consistent, and the transaction is rejected when the merchant registration place of the NFC tag and the current location of the payment terminal are inconsistent, thereby improving payment security.
Fig. 4 is a flowchart of a payment method 400 according to an embodiment of the present application, where the payment method 400 is used for making a payment according to a payment request, and is applied to a payment server.
As shown in fig. 4, the method 400 includes:
step S401: receiving a payment request, wherein the payment request carries a target NFC label and the current position of a payment terminal; wherein the sending of the payment request may be a payment terminal.
Step S402: comparing the current positions of the merchant registration place and the payment terminal carried by the target NFC label;
step S403: and carrying out payment or refusing payment according to the comparison result.
Specifically, a merchant registration place stored in the NFC tag should have consistency with an actual location of the NFC tag, and the payment server performs payment when the merchant registration place carried by the target NFC tag is consistent with the current location of the payment terminal by using the short-range communication characteristic of NFC; on the contrary, when the merchant registration place carried by the target object NFC label is inconsistent with the current position of the payment terminal, the payment server refuses payment, and the payment security is ensured.
In a possible implementation, the payment request may further include a payment amount and/or a payment password. The payment server thus performs a transaction according to the payment amount and/or performs an authentication according to the payment password after receiving the payment request. It should be understood that in some micropayment scenarios, additional verification of the payment password may not be required; in some quota payment scenarios, the transaction can also be performed according to the preset payment amount without carrying the payment amount in the payment request, which is not specifically limited in the present application.
In a possible implementation manner, the payment request further includes a tag collision identifier, so that after receiving the payment request, the payment server responds to the detection of the tag collision identifier and compares the merchant registration place carried by the target NFC tag with the current location of the payment terminal.
In a possible implementation manner, in order to prompt the payer and the merchant to have payment risk, if the payment server performs payment according to the comparison result, after the payment is completed, a payment completion message and/or an alarm message is sent to the payment terminal and/or the merchant terminal, for example, the payment completion message is accompanied by "the NFC tag may be maliciously covered, please check and remove! ' the like is used for indicating the alarm information of a plurality of NFC label conflicts, so that the merchant can be timely reminded of effective problems, the use experience of payment is further improved, the payment risk problem is accurately positioned, and the payment safety is further guaranteed. If the payment server refuses payment according to the comparison result, sending a payment refusing message and/or alarm information to the payment terminal, for example, warning information such as 'conflict of multiple NFC tags exists', 'the NFC tags may be covered' and the like for indicating the conflict of the multiple NFC tags can be attached to the payment refusing message, so that the payer is reminded to pay safely, and meanwhile, the payer and the merchant can accurately position payment risks so as to make corrections as soon as possible.
The embodiment of the invention also provides a payment method, which is applied to a payment system consisting of at least one payment terminal with the NFC function and a payment server, and the method comprises the following steps: executing the payment method shown in fig. 3 by the payment terminal; the payment method shown in fig. 4 is performed by the payment server.
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 NFC-enabled payment terminal, a payment server, and a merchant terminal.
As shown in fig. 5, in step S501, the payment terminal touches the NFC tag, and detects a plurality of NFC tags; in step S502, the payment terminal establishes a contactless connection with the detected plurality of NFC tags; in step S503, the payment terminal reads the merchant UID, merchant name and merchant registration location of the plurality of NFC tags; in step S504, enumerating merchant identifiers of the detected plurality of NFC tags in an interface of the payment terminal; in step S505, a touch operation on the interface of the payment terminal is detected, and when the user selects a merchant identifier of a certain NFC tag on the interface of the payment terminal, the NFC tag selected by the user is determined as a target NFC tag according to the detected touch operation. In step S506, disconnecting the contactless connection between the payment terminal and the other NFC tag; in step S507, acquiring a current location of the payment terminal, and (optionally) acquiring an input payment amount and/or a payment password; in step S508, the payment terminal issues a payment request to the payment server, where the payment request carries the tag conflict identifier, the merchant UID, the merchant name, and the merchant registration location of the target NFC tag, and (optionally) information such as the payment amount and/or the payment password; in step S509, the payment server receives the payment request, and compares the merchant registration location based on the target NFC tag with the current location of the payment terminal; after step S509, in step S510a, the payment server makes a payment in the case where the above comparison is consistent; after the payment is completed, in step S511a, the payment server sends a transaction completion message to the payment terminal, and may also send alarm information to the payment terminal; after the payment is completed, the payment server transmits alarm information to the merchant terminal in step S512. Alternatively, after step S509, in step S510b, the payment server refuses payment if the comparison is inconsistent; after rejecting the payment, the payment server transmits a rejection transaction message to the payment terminal and may also transmit alarm information to the payment terminal in step S511 b. After step S511a or step S511b in step S513, after the payment terminal receives the transaction completion message or the transaction rejection message, the contactless connection with the target NFC tag is disconnected; (optional) after step S512, in step S514, the merchant terminal performs self-check after receiving the warning 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 including at least one NFC-enabled payment terminal, a payment server, and a merchant terminal.
As shown in fig. 6, in step S601, the payment terminal touches the NFC tag, and detects a plurality of NFC tags; in step S602, the payment terminal establishes a contactless connection with the detected plurality of NFC tags; in step S603, the payment terminal performs anti-collision processing based on an anti-collision rule of a radio frequency card protocol, selects one of the NFC tags as a target NFC tag, and reads information such as a merchant UID, a merchant name, a merchant registration place, and the like stored in the target NFC tag; in step S604, disconnecting the contactless connection between the payment terminal and the other NFC tag; in step S605, acquiring a current location of the payment terminal, and (optionally) acquiring an input payment amount and/or a payment password; in step S606, the payment terminal issues a payment request to the payment server, where the payment request carries information such as the tag conflict identifier, the merchant UID, the merchant name, and the merchant registration location of the target NFC tag, and (optionally) the payment amount and/or the payment password. In step S607, the payment server receives the payment request, and compares the current location of the payment terminal with the merchant registration location carried by the target NFC tag; after step S607, in step S608a, the payment server makes a payment in the case where the above comparison is consistent; after the payment is completed, in step S609a, the payment server sends a transaction completion message to the payment terminal, and may also send an alarm message to the payment terminal; after the payment is completed, the payment server transmits alarm information to the merchant terminal in step S610. Alternatively, after step S607, in step S608b, the payment server refuses payment in case the comparison is not consistent; after rejecting the payment, the payment server transmits a rejection transaction message to the payment terminal and may also transmit alarm information to the payment terminal in step S609 b. After step S609a or step S609b in step S611, the payment terminal disconnects the contactless connection with the target NFC tag after receiving the transaction completion message or the transaction rejection message. (optional) after step S610, in step S612, the merchant terminal performs self-check after receiving the warning information.
Based on the same technical concept, the embodiment of the invention also provides a payment terminal. Fig. 7 is a schematic structural diagram of a payment terminal according to 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 for: determining a target NFC tag from the at least two NFC tags when the at least two NFC tags are detected by the NFC module 71; acquiring a merchant registration place stored in the target NFC label through the NFC module 71, and acquiring the current position of the payment terminal; and generating and initiating a payment request, wherein the payment request carries the current positions of the merchant registration place and the payment terminal of the target NFC label.
In a possible implementation, the NFC module 71 is further configured to: and determining a target NFC label by using an anti-collision rule based on a radio frequency card protocol, and reading a merchant identifier and a merchant registration place stored in the target NFC label.
In one possible implementation, the payment application module 72 is further configured to: reading merchant identifications and merchant registration places stored by at least two NFC labels through the NFC module 71, and enumerating the merchant identifications of the at least two NFC labels in an interface of the payment terminal; and detecting touch operation on an interface of the payment terminal, and determining the target NFC label according to the detected touch operation.
In a possible implementation, the NFC module 71 is further configured to: in response to detecting the at least two NFC tags, establishing a contactless connection with each of the at least two NFC tags; after the target NFC tag is determined, the non-contact connection with other NFC tags is disconnected.
In one possible implementation, the payment application module 72 is further configured to: receiving a payment completion message or a payment refusal message; the NFC module 71 is further configured to: after receiving the payment completion message or the payment denial message, the contactless connection with the target NFC tag is disconnected.
In a possible embodiment, the payment request further comprises a tag collision identifier for indicating a collision of the at least two NFC tags.
In one possible implementation, the payment application module 72 is further configured to: and receiving alarm information, and displaying the alarm information on an interface of the payment terminal, wherein the alarm information is used for indicating the conflict of the plurality of NFC labels.
Based on the same technical concept, the embodiment of the invention also provides a payment server. Fig. 8 is a schematic structural diagram of a payment server according to an embodiment of the present invention.
As shown in fig. 8, the payment server 80 includes: a receiving unit 801, configured to receive a payment request, where the payment request includes a target NFC tag and a current location of a payment terminal; a comparison unit 802, configured to compare the current location of the payment terminal with a merchant registration location carried by the target NFC tag; and a payment unit 803 for making payment or rejecting payment according to the comparison result.
In a possible implementation, the payment request further includes a tag conflict identifier, and the comparing unit 802 is further configured to: and responding to the detection of the label conflict identification, and comparing the current positions of the merchant registration place and the payment terminal carried by the target NFC label.
In a possible implementation, the method further includes a sending unit, configured to: if the payment is carried out according to the comparison result, sending a payment completion message and/or an alarm message to the payment terminal and/or the merchant terminal; and if the payment is rejected according to the comparison result, sending a payment rejection message and/or alarm information to the payment terminal, wherein the alarm information is used for indicating the conflict of the plurality of NFC labels.
Based on the same technical concept, the embodiment of the invention also provides a payment system.
The payment system comprises: at least one payment terminal with NFC functionality and a payment server, wherein the payment terminal is configured to perform the method as shown in fig. 3; the payment server is used to perform the method as shown in fig. 4.
In one possible embodiment, the payment system further comprises a merchant terminal.
Fig. 9 is a payment terminal according to an embodiment of the present application, configured to execute the payment method shown in fig. 3, where the apparatus includes: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform:
when the at least two NFC tags are detected, determining a target NFC tag from the at least two NFC tags; acquiring a merchant registration place stored in a target NFC label, and acquiring the current position of a payment terminal; and generating and initiating a payment request, wherein the payment request carries the current positions of the merchant registration place and the payment terminal of the target NFC label. Fig. 10 is a payment server for executing the payment method shown in fig. 4 according to an embodiment of the present application, where the apparatus includes: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform:
receiving a payment request, wherein the payment request carries a target NFC label and the current position of a payment terminal; comparing the current positions of the merchant registration place and the payment terminal carried by the target NFC label; and carrying out payment or refusing payment according to the comparison result.
According to some embodiments of the present application, there is provided a non-transitory computer storage medium of a payment method having stored thereon computer-executable instructions configured to, when executed by a processor, perform the payment method illustrated in fig. 3 or the payment method illustrated in fig. 4.
The embodiments in the present application are described in a progressive manner, and the same and similar parts among the embodiments can be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus, device, and computer-readable storage medium embodiments, the description is simplified because they are substantially similar to the method embodiments, and reference may be made to some descriptions of the method embodiments for their relevance.
The apparatus, the device, and the computer-readable storage medium provided in the embodiment of the present application correspond to the method one to one, and therefore, the apparatus, the device, and the computer-readable storage medium also have advantageous technical effects similar to those of the corresponding method.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, 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 a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. Moreover, while the operations of the method of the invention are depicted in the drawings in a particular order, this does not require or imply that the operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.
While the spirit and principles of the invention have been described with reference to several particular embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, nor is the division of aspects, which is for convenience only as the features in such aspects may not be combined to benefit. The invention is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims (22)

1. A payment method, applied to a payment terminal with NFC function, the method comprising:
when at least two NFC tags are detected, determining a target NFC tag from the at least two NFC tags;
acquiring a merchant registration place stored in the target NFC label, and acquiring the current position of a payment terminal;
and generating and initiating a payment request, wherein the payment request carries the merchant registration place of the target NFC label and the current position of the payment terminal.
2. The method of claim 1, wherein determining a target NFC tag from the at least two NFC tags further comprises:
and determining the target NFC label by using an anti-collision rule based on a radio frequency card protocol, and reading a merchant identifier and a merchant registration place stored in the target NFC label.
3. The method of claim 1, wherein determining a target NFC tag from the at least two NFC tags further comprises:
reading merchant identifications and merchant registration places stored by the at least two NFC labels, and enumerating the merchant identifications of the at least two NFC labels in an interface of the payment terminal;
and detecting touch operation on an interface of the payment terminal, and determining the target NFC label according to the detected touch operation.
4. The method of claim 1, further comprising:
in response to detecting the at least two NFC tags, establishing a contactless connection with each of the at least two NFC tags;
after the target NFC tag is determined, the non-contact connection with other NFC tags is disconnected.
5. The method of claim 4, further comprising:
and receiving a payment completion message or a payment refusal message, and then disconnecting the non-contact connection with the target NFC tag.
6. The method of claim 1, wherein the payment request further comprises a tag collision flag indicating a collision of the at least two NFC tags.
7. The method of claim 1, further comprising:
and receiving alarm information, and displaying the alarm information on an interface of the payment terminal, wherein the alarm information is used for indicating the conflict of the at least two NFC labels.
8. A payment method applied to a payment server, the method comprising:
receiving a payment request, wherein the payment request carries a target NFC label and the current position of a payment terminal;
comparing the merchant registration place carried by the target NFC label with the current position of the payment terminal;
and paying or refusing to pay according to the comparison result.
9. The method of claim 8, wherein the payment request further includes a tag conflict identification, the method further comprising:
and responding to the detection of the label conflict identification, and comparing the merchant registration place carried by the target NFC label with the current position of the payment terminal.
10. The method of claim 8, further comprising:
if the payment is carried out according to the comparison result, sending a payment completion message and/or an alarm message to the payment terminal and/or the merchant terminal;
and if the payment is rejected according to the comparison result, sending a payment rejection message and/or alarm information to the payment terminal, wherein the alarm information is used for indicating the conflict of the plurality of NFC labels.
11. A payment method applied to a payment system composed of at least one NFC-enabled payment terminal and a payment server, the method comprising:
performing, by the payment terminal, the payment method of any one of claims 1-7;
used by the payment server for performing the payment method of any one of claims 8-10.
12. A payment terminal, characterized in that the payment terminal has an NFC module, further comprising:
a payment application module configured to:
when at least two NFC tags are detected through the NFC module, determining a target NFC tag from the at least two NFC tags;
acquiring a merchant registration place stored in the target NFC label through an NFC module, and acquiring the current position of a payment terminal;
and generating and initiating a payment request, wherein the payment request carries the merchant registration place of the target NFC label and the current position of the payment terminal.
13. The payment terminal of claim 12,
the NFC module is further configured to:
and determining the target NFC label by using an anti-collision rule based on a radio frequency card protocol, and reading a merchant identifier and a merchant registration place stored in the target NFC label.
14. The payment terminal of claim 12,
the payment application module is further configured to:
reading merchant identifications and merchant registration places stored by the at least two NFC tags through the NFC module, and enumerating the merchant identifications of the at least two NFC tags in an interface of the payment terminal;
and detecting touch operation on an interface of the payment terminal, and determining the target NFC label according to the detected touch operation.
15. The payment terminal of claim 12,
the NFC module is further configured to:
in response to detecting the at least two NFC tags, establishing a contactless connection with each of the at least two NFC tags;
after the target NFC tag is determined, the non-contact connection with other NFC tags is disconnected.
16. The payment terminal of claim 15,
the payment application module is further to: receiving a payment completion message or a payment refusal message;
the NFC module is further configured to: disconnecting the contactless connection with the target NFC tag after receiving the payment completion message or the payment denial message.
17. The payment terminal of claim 12, wherein the payment request further comprises a tag collision identifier for indicating a collision of the at least two NFC tags.
18. The payment terminal of claim 12,
the payment application module is further to:
and receiving alarm information, and displaying the alarm information on an interface of the payment terminal, wherein the alarm information is used for indicating the conflict of the at least two NFC labels.
19. A payment server, comprising:
a receiving unit, configured to receive a payment request, where the payment request includes a target NFC tag and a current location of the payment terminal;
the comparison unit is used for comparing the merchant registration place carried by the target NFC label with the current position of the payment terminal;
and the payment unit is used for paying or refusing payment according to the comparison result.
20. The payment server of claim 19, wherein the payment request further comprises a tag conflict identifier, and wherein the comparing unit is further configured to:
and responding to the detection of the label conflict identification, and comparing the merchant registration place carried by the target NFC label with the current position of the payment terminal.
21. The payment server of claim 19, further comprising a sending unit configured to:
if the payment is carried out according to the comparison result, sending a payment completion message and/or an alarm message to the payment terminal and/or the merchant terminal;
and if the payment is rejected according to the comparison result, sending a payment rejection message and/or alarm information to the payment terminal, wherein the alarm information is used for indicating the conflict of the plurality of NFC labels.
22. A payment system, comprising: at least one NFC-enabled payment terminal and a payment server, wherein the payment terminal is configured to perform the method of any one of claims 1-7; the payment server is configured to perform the method of any one of claims 8-10.
CN202010078735.1A 2020-02-03 2020-02-03 Payment method, terminal, server and system Active CN111242608B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202010078735.1A CN111242608B (en) 2020-02-03 2020-02-03 Payment method, terminal, server and system
PCT/CN2021/074862 WO2021155785A1 (en) 2020-02-03 2021-02-02 Payment method, terminal, server and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010078735.1A CN111242608B (en) 2020-02-03 2020-02-03 Payment method, terminal, server and system

Publications (2)

Publication Number Publication Date
CN111242608A true CN111242608A (en) 2020-06-05
CN111242608B CN111242608B (en) 2024-03-22

Family

ID=70869951

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010078735.1A Active CN111242608B (en) 2020-02-03 2020-02-03 Payment method, terminal, server and system

Country Status (2)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021155785A1 (en) * 2020-02-03 2021-08-12 中国银联股份有限公司 Payment method, terminal, server and system

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120268239A1 (en) * 2011-04-20 2012-10-25 Peter Ljung Methods, systems and computer program products for registration of and anonymous communications related to tagged objects
CN105023299A (en) * 2014-04-28 2015-11-04 戴姆勒大中华区投资有限公司 Networking vehicle mounted payment system and networking vehicle mounted payment method
US20160092705A1 (en) * 2014-02-21 2016-03-31 Sony Corporation Detection of unauthorized tags
CN106779677A (en) * 2016-11-21 2017-05-31 深圳付贝科技有限公司 A kind of method of payment and its device, electronic equipment and payment system
US20180005243A1 (en) * 2016-06-30 2018-01-04 Square, Inc. Logical Validation of Devices Against Fraud
CN108701303A (en) * 2017-06-30 2018-10-23 华为技术有限公司 NFC payment and terminal
CN108734462A (en) * 2018-05-15 2018-11-02 惠龙易通国际物流股份有限公司 A kind of method of mobile payment, device, system and storage medium
CN109359968A (en) * 2018-09-28 2019-02-19 中国工商银行股份有限公司 A kind of method of payment, device, electronic equipment and payment label

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2435949A4 (en) * 2009-05-29 2014-04-30 Ericsson Telefon Ab L M Apparatus, method and computer program product for detecting risk tags
KR20130020060A (en) * 2011-08-18 2013-02-27 주식회사 케이티 System, mobile communication terminal and method for providing information
CN105631662A (en) * 2015-06-19 2016-06-01 宇龙计算机通信科技(深圳)有限公司 NFC payment method, NFC payment system and mobile terminal
CN109600714A (en) * 2018-11-26 2019-04-09 努比亚技术有限公司 A kind of method of payment, terminal and readable storage medium storing program for executing
CN110400138A (en) * 2019-07-30 2019-11-01 中国工商银行股份有限公司 The method of mobile payment and device of illegal
CN111242608B (en) * 2020-02-03 2024-03-22 中国银联股份有限公司 Payment method, terminal, server and system

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120268239A1 (en) * 2011-04-20 2012-10-25 Peter Ljung Methods, systems and computer program products for registration of and anonymous communications related to tagged objects
US20160092705A1 (en) * 2014-02-21 2016-03-31 Sony Corporation Detection of unauthorized tags
CN106030606A (en) * 2014-02-21 2016-10-12 索尼公司 Detection of unauthorized tags
CN105023299A (en) * 2014-04-28 2015-11-04 戴姆勒大中华区投资有限公司 Networking vehicle mounted payment system and networking vehicle mounted payment method
US20180005243A1 (en) * 2016-06-30 2018-01-04 Square, Inc. Logical Validation of Devices Against Fraud
CN106779677A (en) * 2016-11-21 2017-05-31 深圳付贝科技有限公司 A kind of method of payment and its device, electronic equipment and payment system
CN108701303A (en) * 2017-06-30 2018-10-23 华为技术有限公司 NFC payment and terminal
CN108734462A (en) * 2018-05-15 2018-11-02 惠龙易通国际物流股份有限公司 A kind of method of mobile payment, device, system and storage medium
CN109359968A (en) * 2018-09-28 2019-02-19 中国工商银行股份有限公司 A kind of method of payment, device, electronic equipment and payment label

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021155785A1 (en) * 2020-02-03 2021-08-12 中国银联股份有限公司 Payment method, terminal, server and system

Also Published As

Publication number Publication date
WO2021155785A1 (en) 2021-08-12
CN111242608B (en) 2024-03-22

Similar Documents

Publication Publication Date Title
US10776776B2 (en) System and method of loading a transaction card and processing repayment on a mobile device
US11334862B2 (en) Terminal transaction method, and terminal
JP5668051B2 (en) Method for pre-selecting at least one application in a mobile communication device including an NFC system
CN111860020A (en) Service processing method, device and equipment
US20160103716A1 (en) Method for using shared device in apparatus capable of operating two operating systems
JP2023524538A (en) Near Field Communication NFC Communication Method, Apparatus and Electronic Equipment
US20170255925A1 (en) Configuration of a transaction in a proximity circuit
CN111242608B (en) Payment method, terminal, server and system
WO2017033118A1 (en) Method and system for enhancing security of contactless card
CN104657854A (en) Wireless power supply to enable payment transaction
KR20150069237A (en) Payment method and system using dynamic NFC tag
CN110869960A (en) Processing payments
CN110889689A (en) Transaction request processing method and device, electronic equipment and readable storage medium
US10217101B2 (en) Link of mobile devices to facilitate mobile commerce transactions
CN108292393B (en) Payment method and device based on NFC
US20220092564A1 (en) Resource configuration methods, apparatuses, and systems
JP2008197956A (en) Information communication device, method and program
KR20130082643A (en) User device for banking transactions, apparatus for banking transactions, and method for banking transactions thereof
WO2023050900A1 (en) Data processing method and system, and terminal and computer-readable storage medium
KR102638750B1 (en) Operating method of electronic device performing near field communication functions
KR102170817B1 (en) Terminal and service providing device, electronic wallet system comprising the same, control method thereof and computer readable medium having computer program recorded therefor
CN114519580A (en) Payment request method, payment method, terminal and storage medium for near field communication
CN104104646A (en) Security information interaction system, device and method based on security carrier active command
KR20150056753A (en) Method for authenticating payment occurred abroad and systems thereof
KR20150022561A (en) Method for authenticating payment occurred abroad and systems thereof

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant