Member payment method and device, equipment and medium

Abstract

The embodiment of the invention discloses a member payment method and device, equipment and a medium. The scheme can comprise the following steps: a user terminal sends a near field communication trigger signal; acquiring a member payment link provided by a near field communication device responding to the near field communication trigger signal; the member payment link comprises fixed information and a dynamic token; determining that a target application in the user terminal is in a starting state based on an application identifier contained in the fixed information; sending confirmation information containing the dynamic token to a server based on the started target application; the server is used for determining user information and a payment voucher of the user terminal based on the dynamic token and sending the user information and the payment voucher to merchant equipment associated with the near field communication equipment; and obtaining payment result information fed back by the server.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular, to a membership payment method, device, equipment and medium. Background Art

[0002] With the rapid development of the Internet economy, users' consumption behaviors have gradually shifted from single transactions to continuous service relationships. Against this background, the membership mechanism, as a core user operation model, has significantly improved user stickiness and the efficiency of commercial value conversion through differentiated services and rights incentives. More and more merchants use the membership mechanism to provide services to users.

[0003] Currently, in the consumption scenario, a common way to use membership is that the merchant scans the membership code provided by the user through a terminal such as a mobile phone, or the merchant asks for information such as the user's mobile phone number and membership number. The merchant first completes the user's membership login on the merchant device such as the cash register, and then the merchant settles the goods purchased by the user. During the settlement process, the user also needs to provide a payment code through a terminal such as a mobile phone to complete the settlement. The entire process requires multiple operations by the merchant or the user, and the operation is relatively cumbersome.

[0004] Therefore, a more convenient membership payment method is needed. Summary of the Invention

[0005] Embodiments of this specification provide a membership payment method, device, equipment and medium to solve the problem of cumbersome operations in the existing membership payment method.

[0006] To solve the above technical problems, the embodiments of this specification are implemented as follows: A membership payment method provided by an embodiment of this specification, which is applied to a user terminal, includes: Sending a near-field communication trigger signal; Obtaining a membership payment link provided by a near-field communication device in response to the near-field communication trigger signal; the membership payment link includes fixed information and a dynamic token; Based on the application identifier included in the fixed information, determining that the target application in the user terminal is in a startup state; Sending confirmation information including the dynamic token to the server based on the started target application; the server is used to determine the user information and payment voucher of the user terminal based on the dynamic token and send them to the merchant device associated with the near-field communication device; the merchant device is used to execute the membership processing process based on the user information and send a payment request to the server based on the payment voucher; the payment voucher is used to represent the user account information of the user terminal; Obtain the payment result information fed back by the server; the payment result information is generated by the server based on the payment request sent by the merchant device.

[0007] A membership payment method provided by an embodiment of this specification, which is applied to a near-field communication device, includes: Obtain the near-field communication trigger signal sent by the user terminal; In response to the near-field communication trigger signal, send a membership payment link to the user terminal; the membership payment link includes fixed information and a dynamic token; the user terminal is used to execute the above method based on the membership payment link.

[0008] A membership payment device provided by an embodiment of this specification includes: A trigger signal sending module, configured to send a near-field communication trigger signal; A link obtaining module, configured to obtain the membership payment link provided by the near-field communication device in response to the near-field communication trigger signal; the membership payment link includes fixed information and a dynamic token; An application startup module, configured to determine that the target application in the user terminal is in a startup state based on the application identifier included in the fixed information; An information sending module, configured to send confirmation information including the dynamic token to the server based on the started target application; the server is used to determine the user information and payment voucher of the user terminal based on the dynamic token and send them to the merchant device associated with the near-field communication device; the merchant device is used to execute the membership processing process based on the user information and send a payment request to the server based on the payment voucher; the payment voucher is used to represent the user account information of the user terminal; A result obtaining module, configured to obtain the payment result information fed back by the server; the payment result information is generated by the server based on the payment request sent by the merchant device.

[0009] A membership payment device provided by an embodiment of this specification includes: A trigger signal obtaining module, configured to obtain the near-field communication trigger signal sent by the user terminal; A link sending module, configured to send a membership payment link to the user terminal in response to the near-field communication trigger signal; the membership payment link includes fixed information and a dynamic token; the user terminal is used to execute the above method based on the membership payment link.

[0010] A membership payment device provided by an embodiment of this specification includes: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the above-mentioned membership payment method.

[0011] A computer-readable medium provided by an embodiment of this specification, on which computer-readable instructions are stored, and the computer-readable instructions can be executed by a processor to implement the above-mentioned membership payment method.

[0012] At least one embodiment of this specification can achieve the following beneficial effects: The user terminal can obtain a membership payment link from a near-field communication device associated with the merchant device through near-field communication. The membership payment link includes fixed information and a dynamic token. The user terminal can start a target application in the user terminal based on the application identifier included in the fixed information, and can also send the dynamic token to the server based on the target application. After obtaining the dynamic token sent by the user terminal, the server can determine the user information and payment voucher of the user terminal and send them directly or indirectly to the merchant device associated with the near-field communication device. The merchant device can execute a membership processing process based on the user information, and can also send a payment request to the server based on the payment voucher to complete the payment process. The user terminal can also obtain transaction result information generated by the server for processing the payment request sent by the merchant device.

[0013] In the embodiment of this specification, the user terminal can obtain link information for membership payment through near-field communication. Based on the access of the user terminal, the server can send user information and payment vouchers to the merchant device. The merchant device can execute a membership processing process based on the user information, and can also request the server to process the payment service based on the payment voucher. Throughout the process, one interaction between the user terminal and the near-field communication device can trigger two service processes of membership login and payment, thereby simplifying the operations of both the user and the merchant.

[0014] For example, for the user, the user only needs to touch the user terminal and the near-field communication device once to use the membership rights for payment, without the user having to perform a membership login operation first and then a payment operation. For the merchant, the merchant does not need to manually enter the user's membership information, such as the mobile phone number, and then manually perform payment operations such as scanning the code.

[0015] On the other hand, in the embodiment of this specification, the server queries the user information and payment voucher of the user terminal based on the dynamic token sent by the user terminal. Among them, the user terminal sending the dynamic token to the server can indicate that the user agrees to perform membership payment. That is to say, based on the user's confirmation, the server queries the relevant information of the user terminal, which can improve the security of user information. It can also reduce invalid queries and save computing resources. Description of the Drawings

[0016] To more clearly illustrate the technical solutions in the embodiments of this specification or the prior art, the following will briefly introduce the accompanying drawings required for the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only some embodiments described in this application. For those of ordinary skill in the art, without creative efforts, other accompanying drawings can also be obtained based on these drawings.

[0017] Figure 1 Schematic diagram of an application scenario of a membership payment method provided by an embodiment of this specification; Figure 2 Schematic flow chart of a membership payment method provided by an embodiment of this specification; Figure 3 Schematic flow chart of a membership payment method provided by an embodiment of this specification; Figure 4 Swimlane diagram of a membership payment method provided by an embodiment of this specification; Figure 5 Corresponding to the Figure 2 Schematic structural diagram of a membership payment device; Figure 6 Corresponding to the Figure 3 Schematic structural diagram of a membership payment device; Figure 7 Schematic structural diagram of a membership payment device provided by an embodiment of this specification. Specific implementation manners

[0018] To make the objectives, technical solutions, and advantages of one or more embodiments of this specification clearer, the following will clearly and completely describe the technical solutions of one or more embodiments of this specification in conjunction with the specific embodiments and the corresponding accompanying drawings of this specification. Obviously, the described embodiments are only some of the embodiments of this specification, rather than all embodiments. Based on the embodiments in this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope protected by one or more embodiments of this specification.

[0019] The terms used in one or more embodiments of this application are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this application. The singular forms "a", "the", and "said" used in one or more embodiments of this application and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used in one or more embodiments of this application refers to and includes any or all possible combinations of one or more related listed items.

[0020] It should be understood that although the terms first, second, etc. may be used in one or more embodiments of the present application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of one or more embodiments of the present application, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "when" or "while" or "in response to a determination".

[0021] In order to clearly illustrate the implementation manners of the embodiments of this specification, the following explains some terms.

[0022] Near Field Communication (NFC) is a short-range wireless communication technology that allows devices to exchange data when they are very close (usually within 4 centimeters). NFC technology is based on Radio Frequency Identification (RFID) technology and can provide various functions such as data transmission, communication, and near-field payment.

[0023] NFC technology mainly includes three communication modes: Reader / Writer Mode, Card Emulation Mode, and Peer-to-Peer Mode.

[0024] Reader / Writer Mode is a working mode. In this mode, an NFC device can read or write information to an NFC tag or a device containing an NFC tag. For example, in a payment scenario, a mobile phone can be in the Reader / Writer Mode to obtain payment information on the payment device side for payment. A device in this mode can be called a reader device.

[0025] In Card Emulation Mode, an NFC device can be emulated as a smart card, allowing it to be used as a payment card, access control card, or other types of cards. The device can interact with existing contactless infrastructures, such as a POS machine or an access control system. For example, using a mobile phone as a bank card for payment in a store; using a mobile phone as an access control card in a company or residential area; using a mobile phone as a transportation card for taking public transportation. A device in this mode can be called a slave device.

[0026] Peer-to-Peer Mode: In this mode, two NFC devices can exchange data with each other. Both devices must be active and capable of sending and receiving data. It is mainly applied to file transfer, social networking, game interaction, etc. For example, quickly pair Bluetooth or Wi-Fi connections via NFC and then transfer files or photos; another example is to exchange business cards, contact information, or social media links by tapping two mobile phones; yet another example is the character exchange or item sharing in multiplayer games, etc.

[0027] NFC tags are small electronic chips that are built-in with antennas and can communicate with NFC-enabled devices (such as smartphones) over a short distance via radio waves. These tags are usually very thin and small and can be embedded in various items, such as posters, business cards, product packaging, devices, etc.

[0028] In practical applications, NFC tags can also be software, such as a device in card emulation mode. When the NFC tag is software, it can be installed in a physical card or a terminal device. It can be implemented as multiple software or software modules (such as those used to provide distributed service authentication services), or it can be implemented as a single software or software module.

[0029] Member payment refers to the way users make payments as members. Specifically, it can mean that users become members of a specific platform or service provider, such as registering as a member for free or paying a fee, and obtain exclusive payment methods or rights and interests, so as to enjoy convenience, security, or additional discounts in transactions.

[0030] The following will, in conjunction with the accompanying drawings, elaborate on the technical solutions provided by each embodiment of this specification.

[0031] Figure 1 It is a schematic diagram of the application scenario of a member payment method provided by an embodiment of this specification. As Figure 1 shown, this solution may include a user terminal 1, a near-field communication device 2, a merchant device 3, and a server 4. Among them, the user terminal 1 can send a near-field communication trigger signal in the NFC near-field communication card reader mode; the near-field communication device 2 may contain an NFC tag or be in card emulation mode. When the user terminal 1 and the near-field communication device 2 are in close proximity, for example, when the user touches the user terminal to the near-field communication device, the near-field communication device 2 can send NFC tag information including a member payment link for triggering member payment to the user terminal 1 in response to the near-field communication trigger signal of the user terminal 1.

[0032] The user terminal 1 can start the target application based on the application identifier in the membership payment link. Using the started payment application, it can send a confirmation message containing the dynamic token in the membership payment link to the server 4. This confirmation message can indicate that the user agrees to make a membership payment. Specifically, it can indicate that the user agrees to log in or register as a merchant member and make a payment using the membership status. After obtaining the dynamic token sent by the user terminal, the server 4 can query the user information and payment vouchers of the user terminal and send the user information and payment vouchers directly or indirectly to the merchant device 3. After obtaining the user information, the merchant device 3 can execute membership processing procedures such as membership login or membership registration for managing membership information. Moreover, the merchant device 3 can also initiate a payment to the server 4 using the obtained payment vouchers, requesting the server 4 to process the transaction that the user terminal needs to pay for.

[0033] In practical applications, the user terminal 1 can be one or more of a smart phone, a laptop computer, a tablet computer, an Internet of Things device, a portable wearable device, or an immersive image display device, etc. Specifically, the Internet of Things device can be one or more of a smart speaker, a smart TV, a smart air conditioner, or a smart vehicle-mounted device, etc. The portable wearable device can be one or more of a smart watch, a smart bracelet, or a head-mounted device, etc. The immersive image display device includes but is not limited to an Augmented Reality (AR) device, a Virtual Reality (VR) device, etc.

[0034] The near-field communication device 2 can be a device with near-field communication function, or can be a device with an NFC tag. It can be an independent electronic device or a component integrated into other devices. For example, it can be an electronic device fixed or removably placed at the cashier desk, or can also be a component located in the self-checkout device or an electronic device connected to the self-checkout device by wired or wireless means, etc.

[0035] The merchant device 3 can be a device capable of processing transactions, or can be a device with a cashier function, such as a cashier desk, a POS machine, a self-checkout device, a smart vending cabinet, etc.

[0036] In practical applications, the near-field communication device 2 and the merchant device 3 can be connected by wired or wireless means, or, a binding relationship or a corresponding relationship can be established between the near-field communication device and the merchant device, etc., all of which can make the near-field communication device 2 associated with the merchant device 3. From a hardware perspective, the near-field communication device 2 and the merchant device 3 can be two independent devices, or can also be an integrated device, which is not specifically limited here. The near-field communication device 2 can be provided to the merchant for use by other service providers other than the merchant, or can also be the merchant's own device, which is not limited here either.

[0037] The server 4 can be an independent physical server, a server cluster or a distributed file system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, Content Delivery Network (CDN), and big data and artificial intelligence platforms.

[0038] Next, a membership payment method provided in the embodiments of the specification will be specifically described with reference to the accompanying drawings.

[0039] Figure 2 It is a schematic flowchart of a membership payment method provided in the embodiments of the present specification. From a program perspective, the execution subject of the process can be a program running on the user terminal. From a hardware perspective, the execution subject of the process can be the user terminal.

[0040] As Figure 2 shown, the process may include the following steps.

[0041] Step 202: Send a near-field communication trigger signal.

[0042] In the embodiments of the present specification, the user terminal can act as a near-field communication card reader device to send a near-field communication trigger signal for triggering near-field communication. Specifically, the near-field communication function of the user terminal can be in an enabled state and in card reader mode, and send an electromagnetic signal for establishing near-field communication. In practical applications, the user terminal can be in a card detection mode, emit a card detection signal, detect whether there is an NFC tag or NFC card nearby, and after determining that there is an NFC tag or NFC card nearby, perform NFC near-field communication with the NFC tag or NFC card to obtain the information in the NFC tag or NFC card. The specific process can refer to the related technology and will not be elaborated here.

[0043] In practical applications, when the user terminal is in an unlocked state, the NFC card reader mode can be started. For example, when payment is required, the user first unlocks the user terminal such as a mobile phone or a smart watch, and the user terminal such as a mobile phone or a smart watch can start the NFC card reader mode and send a near-field communication trigger message. Another example is that before payment is required, the user is using the user terminal such as a mobile phone or a smart watch, and the user terminal can always be in the NFC card reader mode during the user's use process, and send a near-field communication trigger message through a low-power card detection mode or a normal card detection mode. The user can bring the user terminal close to or touch the near-field communication device, and the user terminal can detect the NFC tag or card in the near-field communication device and read the tag information in the near-field communication device through NFC near-field communication.

[0044] In practical applications, the user terminal can also start the NFC card reader mode in a non-unlocked state. For example, the user terminal can start the NFC card reader mode when the screen is on. Or when the user terminal obtains biometric information such as the user's face or iris in the screen-off or locked state, the NFC card reader mode can be started. Or, the user can start the NFC card reader mode of the user terminal by performing some preset operations on the user terminal. For example, pressing the power button, volume button, etc. once or multiple times makes the user terminal enter the NFC card reader mode. Here, the timing and method for the user terminal to start the NFC card reader mode are not specifically limited. As long as it can be started before performing near-field communication with the near-field communication device.

[0045] Step 204: Obtain a membership payment link provided by the near-field communication device in response to the near-field communication trigger signal; the membership payment link includes fixed information and a dynamic token.

[0046] The near-field communication device can be an electronic device with near-field communication capabilities and can have logical processing capabilities. The near-field communication device can be in the NFC card emulation mode or can include an NFC tag so that the near-field communication device can store NFC tag information. If the near-field communication device is within the near-field communication range of the user terminal, the near-field communication device can respond to the near-field communication trigger signal sent by the user terminal and can also send the tag information to the user terminal. The tag information can contain the membership payment link. This link can be link information in formats such as http or https. The membership payment link can include fixed information and a dynamic token. The fixed information can represent information that is included in different membership payment links. The dynamic token can be a token representing the uniqueness of the membership payment link, such as a token token. Different membership payment links can include the same fixed information and different dynamic tokens.

[0047] Step 206: Based on the application identifier included in the fixed information, determine that the target application in the user terminal is in the startup state.

[0048] The target application can be a terminal application with payment functions. For example, it can be a terminal APP application, or it can also be a mini-program application, etc. The application identifier can be identifier information that can uniquely identify the application. For example, it can be the name, abbreviation, or package name of the target application. Different user terminals or user terminals of different systems can determine the corresponding target application based on this application identifier information.

[0049] In practical applications, if the user terminal has not launched the target application before obtaining the membership payment link information, the user terminal can launch the target application after obtaining the membership payment link information. Specifically, the terminal system program of the user terminal can parse the application identifier from the payment link information, launch the target application, and then provide the membership payment link or the dynamic token in the link to the target application. The target application accesses the server based on the membership payment link or the dynamic token. If the user terminal has launched the target application or is using the target application before obtaining the payment link information, the user terminal does not need to launch it again after obtaining the payment link information. The launched target application can access the server based on the membership payment link or the dynamic token.

[0050] The target application being in the launched state can be launched in the foreground or background of the user terminal, and no specific limitation is made here.

[0051] Step 208: Send confirmation information containing the dynamic token to the server based on the launched target application.

[0052] Among them, the server can be used to determine the user information and payment voucher of the user terminal based on the dynamic token and send them to the merchant device associated with the near-field communication device. The merchant device is used to execute the membership processing process based on the user information and send a payment request to the server based on the payment voucher. The payment voucher is used to represent the user account information of the user terminal.

[0053] The confirmation information can represent the information that the user agrees to use the membership rights and interests for payment. For example, it can represent that the user agrees to log in to the membership or register as a member and make a payment. The determination information can include the dynamic token included in the membership payment link obtained by the user terminal. The server can preset the execution process that the dynamic token can trigger. In the embodiments of this specification, the membership payment link can trigger two processes: membership login and payment. Specifically, after the server obtains the dynamic token sent by the user terminal, it can query the user information and payment voucher of the user terminal. The user information can be the information used to represent the user identity and can be used to determine the membership rights and interests of the user. The payment voucher can be the information used to represent the user account of the user terminal and can be used to determine the user account for payment.

[0054] In practical applications, in order to distinguish different users, after a user registers on a network platform, the system will automatically assign the user a numerical value of a user identification UID (User Identification), which can represent the user's number, and different users have different UIDs. As an implementation manner, user information can be information related to the user and can identify a unique user. As an implementation manner, user information can include the user's unique identifier in the target application. For example, the user UID of the user in the target application.

[0055] Of course, the user information can also be other information that can identify a unique user or information representing the user's identity. For example, the user's payment account information, the user's email account, the user's identity document number, the user's mobile phone number, etc. The specific content of the user information is not limited here, as long as it can identify a unique user.

[0056] The payment voucher can be information representing the user account of the user terminal and can enable the merchant device to trigger the execution of the transaction process. For example, the payment voucher can be the user's payment account, the payment code information corresponding to the user's payment account, etc. As an implementation manner, the payment voucher can include the payment code number of the user account of the user terminal.

[0057] The payment code data can be the number representing the payment code. When the merchant cannot scan the QR code, the payment can be completed by manually entering this string of numbers. In the common scenario of QR code payment, the merchant scans the payment code shown by the user terminal to obtain the payment code number corresponding to the payment code, and then executes the corresponding payment processing process. The payment code number can correspond to a unique payment account. The payment code number can be a string that conforms to a preset rule. For example, the payment code number can be a pure number, or it can also be a string containing multiple character formats such as numbers, letters, and symbols. For example, a string starting with "28", a string starting with "13", etc. The specific format of the payment code number can be set according to actual needs or the format supported by the target application, and is not specifically limited here.

[0058] The merchant device can represent the device for conducting transactions in the merchant, such as a cashier desk, a POS machine, a self-checkout device, etc.

[0059] The near-field communication device can be a device with near-field communication function associated with the merchant device. It can be used as an auxiliary device to assist the merchant in completing the transaction, and can also be called an auxiliary payment device, an auxiliary transaction device, etc.

[0060] This enables merchants who originally do not support transactions via near-field communication to also have the function of conducting transactions via near-field communication. For the merchant side, there is no need to modify the merchant-side equipment, and the merchant can also have the ability to conduct transactions via near-field communication, with low costs or even no additional costs.

[0061] As an implementation method, the near-field communication device can be associated with the merchant device in a wired or wireless manner. For example, the near-field communication device is connected to the merchant device via a USB data cable or other forms of cables; or the near-field communication device and the merchant device are in the same wired or wireless network.

[0062] As another implementation method, the near-field communication device can establish a binding relationship with the merchant device. For example, a binding relationship between the near-field communication device and the merchant device is established through a mobile terminal such as a mobile phone in an application, applet, or web page for establishing the binding relationship; or if the near-field communication device has an operable interface or screen, the near-field communication device can also access the application, applet, or web page for establishing the binding relationship to establish the binding relationship between the near-field communication device and the merchant device; or if the merchant device has an operable interface or screen, the near-field communication device can also access the application, applet, or web page for establishing the binding relationship to establish the binding relationship between the near-field communication device and the merchant device; or the merchant can apply to use the near-field communication device, and after the merchant's application is approved, the server can record the corresponding relationship between the near-field communication device and the merchant device; or after the near-field communication device is distributed to or provided to the merchant, the installer or other personnel provide information indicating the corresponding relationship between the near-field communication device and the merchant device to the server. Specifically, reference can be made to the introduction of related technologies. There is no limitation on the specific method here, as long as the near-field communication device and the merchant device can have an associated relationship.

[0063] Of course, the near-field communication device can also be a component of the merchant device and be integrated into the merchant device. There is no limitation on the specific distribution form of the device here.

[0064] In practical applications, after the server determines the user information and payment voucher of the user terminal, it can be directly sent to the merchant device, or it can also be sent to the near-field communication device, and then sent to the merchant device by the near-field communication device.

[0065] As an implementation, the membership payment link can be generated by the server and fed back to the near-field communication device. The server can store the corresponding relationship between the membership payment link or the dynamic token and the near-field communication device, and can also store the corresponding relationship between the near-field communication device and the associated merchant device. After the server determines the user information and the payment voucher based on the dynamic token sent by the user terminal, it can also determine the merchant device associated with the near-field communication device using the dynamic token, and then send the user information and the payment voucher to the merchant device.

[0066] As another implementation, the membership payment link can be generated by the server and fed back to the near-field communication device. The server can store the corresponding relationship between the membership payment link or the dynamic token and the near-field communication device. After the server determines the user information and the payment voucher based on the dynamic token sent by the user terminal, it can also determine the near-field communication device using the dynamic token, and then send the user information and the payment voucher to the near-field communication device. The near-field communication device can provide the user information and the payment voucher to the merchant device in a wireless or wired manner.

[0067] The merchant device can execute the relevant processes of membership processing based on the user information. For example, based on the user information, the membership rights and interests of the user at the merchant membership can be determined, such as membership level, preferential amount, discount information, etc. Or, after the user's payment is completed, the user's membership points can be increased, etc.

[0068] The merchant device can also generate a payment request based on the payment voucher and send it to the server. The payment request can include the payment voucher or the identification information capable of representing the payment voucher, so that the server can determine the paying user.

[0069] In actual application, when the server feeds back the user information and the payment voucher, it can also carry the dynamic token. The merchant device can also send a payment request to the server based on the payment voucher and the dynamic token. The payment request can include the payment voucher or the identification information capable of representing the payment voucher, and can also include the dynamic token.

[0070] Or, after the user terminal reads the membership payment link, the near-field communication device can sense that the link is read and can also send the dynamic token to the merchant device; or, after the near-field communication device obtains the user information and the payment voucher fed back by the server, it can provide them to the merchant device together with the dynamic token. In this way, the merchant device can also initiate a payment to the server based on the dynamic token and the payment voucher. The server can determine the transaction between the two parties based on the dynamic token and process it.

[0071] Step 210: Obtain the payment result information fed back by the server; the payment result information is generated by the server based on the payment request sent by the merchant device.

[0072] After the server obtains the payment request sent by the merchant device, it can process the transaction requested by the payment request and generate payment result information. The payment result information can be information indicating payment completion, information indicating payment success, information indicating payment failure, and so on.

[0073] The server can feed back the payment result information to the user terminal. The user terminal can display the payment result information, or play a prompt tone or voice message.

[0074] In practical applications, the server can also feed back the payment result information to the merchant device and / or the near-field communication device. The content or form of the payment result information displayed in the user terminal, the merchant device, and the near-field communication device can be the same or different, which is not specifically limited here.

[0075] It should be understood that the order of some steps of the method described in one or more embodiments of this specification can be mutually exchanged according to actual needs, or some of the steps can also be omitted or deleted.

[0076] Figure 2 In the method, the user terminal can obtain the link information for member payment through near-field communication. Based on the access of the user terminal, the server can send user information and payment vouchers to the merchant device. The merchant device can execute the member processing process based on the user information and can also request the server to process the payment service based on the payment vouchers. Throughout the process, one interaction between the user terminal and the near-field communication device can trigger two service processes of member login and payment, which can simplify the operations of both users and merchants. For example, for users, users only need to touch the user terminal and the near-field communication device once to pay using member rights, without the need for users to first perform a member login operation and then a payment operation. For merchants, merchants do not need to manually enter the user's member information, such as the mobile phone number, and then manually perform payment operations such as scanning codes.

[0077] On the other hand, in the embodiments of this specification, the server queries the user information and payment vouchers of the user terminal based on the dynamic token sent by the user terminal. Among them, the user terminal sending the dynamic token to the server can indicate that the user agrees to perform member payment. That is to say, based on the user's confirmation, the server queries the relevant information of the user terminal, which can improve the security of user information. It can also reduce invalid queries and save computing resources.

[0078] Based on Figure 2For the method, the embodiments of this specification also provide some specific implementation solutions of this method, which will be described below.

[0079] In practical applications, when a user makes a payment at a merchant, it is possible that the user has not registered as a merchant member before, or has already registered as a merchant member before. For these different situations, the user terminal can display different page information. As an implementation manner, if the user of the user terminal is not a registered member of the merchant to which the merchant device belongs; the sending of the confirmation information containing the dynamic token to the server based on the started target application may specifically include: Based on the started target application, display a membership registration and payment page; Based on the user's confirmation operation on the membership registration and payment page, generate first confirmation information indicating agreement to register as a member and make a payment to the server; the first confirmation information includes the dynamic token.

[0080] Among them, after the user terminal obtains the membership payment link, it can access the server based on this link. The server can determine the corresponding merchant device or merchant according to the dynamic token. For example, one or more corresponding relationships between merchants, merchant devices, near-field communication devices, membership payment links, or dynamic tokens can be stored in the above server. According to this corresponding relationship, when the user terminal accesses the server based on the membership payment link, the server can determine the merchant corresponding to the membership payment link obtained by the user terminal. Member information of merchant members can be stored in the server or the server of the merchant. After the server obtains the access of the user terminal, it can determine whether the user of the user terminal is a registered member according to the stored member information. If it is not a registered member, that is, the user is a new member who needs to register, the server can feedback the membership registration and payment page to the user terminal.

[0081] Alternatively, the user terminal or the target application in the terminal can also store the merchant members that the user has registered. The user terminal can locally determine whether the user is a registered member. For example, the membership payment link can include a merchant identifier. The user terminal can record the merchant identifier information of each merchant that the user has registered as a member. After the user terminal obtains the membership payment link, it can determine whether the user is a member of the merchant corresponding to this membership payment link according to the merchant identifier in the membership payment link and the merchant members that the user has registered. If the user is not a member of the merchant corresponding to this membership payment link, a registration request can be sent to the server, and the server can feedback the membership registration and payment page to the user terminal.

[0082] In the embodiments of this specification, the membership registration and payment page may be a page for triggering the membership registration and payment process. This page may include a confirmation control, and may also include prompt information for membership registration, or may also include information such as an authorization agreement. The confirmation control may be a control indicating that the user agrees to register as a member and make a payment, such as a control displaying words like "Register as a member and pay". If the user performs an operation on this confirmation control, it may indicate that the user agrees to register as a merchant member and agrees to make a payment as a merchant member.

[0083] In practical applications, the confirmation control may also be a control that allows the user not to perform a substantial operation. For example, a countdown may also be displayed in the display area of the confirmation control or nearby. If the user does not click the cancel control or does not exit the membership registration and payment page within the preset countdown time, it may also indicate that the user agrees to register as a member and make a payment, and the user terminal may also generate a first confirmation information containing a dynamic token.

[0084] If the user is a newly registered member, in addition to the user's unique identifier in the target application that the server provides to the merchant device or the near-field communication device, with the user's authorization and consent, the server may also query the information representing the user's identity provided by the user in the target application and provide it to the merchant device or the near-field communication device. For example, the user's mobile phone number, user nickname, name, identity document number, etc., so that the merchant device or the merchant management system can perform membership management based on the user identity information. The specific method or content of specific membership management can refer to the existing relevant technologies and will not be elaborated here. It can be understood that this information representing the user's identity is compliant and legal information.

[0085] Considering that in practical applications, some users may not want to register as members and only want to make ordinary payments. The above membership registration and payment page may also include a control for only payment, such as a control displaying words like "Direct payment". If the user performs an operation on this control, the user terminal may send a payment confirmation information containing a dynamic token to the server. The server may send the payment voucher of the user terminal queried based on this information to the merchant device or the near-field communication device, without sending the user information of the user terminal; or the server may also send an instruction identifier indicating an ordinary payment to the merchant device or the near-field communication device, so that the merchant device can initiate a payment to the server based on the dynamic token. In this case, the merchant device does not need to perform the membership processing process for the user of this user terminal.

[0086] If the user is already a merchant member, the user terminal can also display a member login and payment page after obtaining the member payment link. Optionally, if the user of the user terminal is a registered member of the merchant to which the merchant device belongs; the sending of the confirmation information containing the dynamic token to the server based on the started target application may specifically include: Based on the started target application, display a member login and payment page; Based on the user's confirmation operation on the member login and payment page, generate second confirmation information indicating agreement to log in as a member and make a payment to the server, and the second confirmation information includes the dynamic token.

[0087] The member login and payment page can be a page for triggering the member login and payment process. This page can include a confirmation control, and can also include prompt information for member login, or can also include information such as a login authorization agreement. The confirmation control can be a control indicating that the user agrees to log in as a member and make a payment, such as a control displayed with words like "Log in as a member and make a payment". If the user performs an operation on this confirmation control, it can indicate that the user agrees to log in as a merchant member and agrees to make a payment as a merchant member.

[0088] In actual application, the confirmation control can also be a control that allows the user not to perform a substantial operation. For example, a countdown word can also be displayed in the confirmation control display area or nearby. If the user does not click the cancel control or does not exit the member login and payment page within the countdown time of the preset duration, it can also indicate that the user agrees to log in as a member and make a payment, and the user terminal can also generate the first confirmation information containing the dynamic token.

[0089] The above-mentioned member registration and payment page and / or member login and payment page can be a page displayed by the user terminal based on the page information fed back by the server after the user terminal accesses the server based on the member payment link; or the member registration and payment page and / or member login and payment page can be a page generated and displayed locally by the user terminal according to a preset page template. The member registration and payment page and / or member login and payment page can also include a cancel control, a page close control, etc. The specific generation process and specific content of the page are not specifically limited here and can be set according to actual needs.

[0090] In practical applications, to further simplify user operations, a user can authorize a terminal application to automatically process some information that requires confirmation. As an implementation manner, a target application can have an extremely fast service processing function. After this function is started, the user terminal may not render and display an intermediate service page, or display the intermediate service page within an extremely short time, and the target application automatically performs a confirmation operation on the intermediate page, without the user having to perform it manually. Optionally, it is determined whether the user terminal has started the extremely fast service processing function; the extremely fast service processing function is a function in which the target application automatically processes an intermediate service page without the user having to manually operate on the intermediate service page. The display of the member login and payment page may specifically include: if the user terminal has not started the extremely fast service processing function, the member login and payment page is displayed.

[0091] In the local target application of the user terminal, it can be recorded whether the user has enabled the extremely fast service processing function, and the above determination step can be executed locally by the user terminal.

[0092] In the case where the user has not started the extremely fast service processing function, the user terminal can display the member login and payment page. After the user performs a confirmation operation on this page, the user terminal can send a second confirmation message containing a dynamic token to the server.

[0093] Optionally, the method in the embodiments of this specification may further include: if the user terminal has started the extremely fast service processing function, the target application automatically generates a third confirmation message containing the dynamic token.

[0094] If the user terminal has started the extremely fast service function, after the user terminal obtains a member payment link, the user terminal may not display the member login and payment page at the front end, or display this page but the target application automatically performs a confirmation operation, without the user having to perform a confirmation operation, and the target application can also send a confirmation message containing a dynamic token to the server.

[0095] If the member login and payment page is generated locally by the user terminal, before or after it is determined that the user is a registered user, if the user has enabled the extremely fast service processing function, the user terminal may not generate the member login and payment page locally and can directly generate a confirmation message containing a dynamic token.

[0096] If the membership login and payment page is generated by the server, the server can generate the page information of the membership login and payment page according to a preset process and feedback it to the user terminal. If the user terminal has enabled the fast business processing function, after obtaining the page information, the user terminal can not render and display the membership login and payment page, but automatically execute the confirmation operation on the page by the target application in the background. The user terminal can also send a second confirmation message containing a dynamic token to the server without displaying the membership login and payment page. Alternatively, after obtaining the page information, the user terminal can render and display the membership login and payment page on the front end. After the membership login and payment page is displayed, the target application automatically executes the confirmation operation and sends a confirmation message containing a dynamic token to the server.

[0097] From the user's perspective, after the user touches the user terminal with the near-field communication device, the membership payment can be completed without any other operations.

[0098] In practical applications, the above fast business processing function can be a service function provided by the target application, or a service provided by the target application for the user on the basis of user authorization when the user meets preset conditions, such as the user having good credit. It can also be a function that does not require the user to manually start.

[0099] In practical applications, the target application can also provide the fast business processing function for all application users. The step of determining whether the user terminal has started the fast business processing function can also not be executed. After the user terminal obtains the membership payment link, the target application in the startup state can automatically send a confirmation message containing a dynamic token to the server.

[0100] Considering that it also takes some time for the user terminal or the server to execute the business process, in order to improve the user experience, when the user terminal obtains the membership payment link and starts the target application, a page indicating that the target application is starting can also be displayed, or a page indicating that the membership is logging in or registering can be displayed during the process of logging in or registering for the membership. Or when the server obtains the payment request sent by the merchant device and processes the transaction, the user terminal can also display a page indicating that the transaction is being processed, and so on.

[0101] Based on the same idea, the embodiments of this specification also provide a method with the near-field communication device as the execution subject. Figure 3 It is a schematic flowchart of a membership payment method provided in the embodiments of this specification. From a program perspective, the execution subject of the process can be a program installed on the near-field communication device. From a hardware perspective, the execution subject of the process can be the near-field communication device. As Figure 3 shown, the process can include the following steps.

[0102] Step 302: Obtain the near field communication trigger signal sent by the user terminal.

[0103] Step 304: In response to the near field communication trigger signal, send a membership payment link to the user terminal.

[0104] Wherein, the membership payment link includes fixed information and a dynamic token; the user terminal is used to execute the membership payment method introduced above based on the membership payment link.

[0105] Wherein, the technical content of features such as the user terminal, near field communication device, membership payment link, etc. can be referred to the foregoing embodiments and will not be elaborated here.

[0106] In practical applications, in order to prevent the user terminal from accidentally touching the near field communication device and accidentally logging in to the membership, and also for payment security, the membership payment link sent by the near field communication device in the embodiments of this specification to the user terminal can be a membership payment link determined by the near field communication device after the merchant device triggers the execution of the membership login process. Optionally, before obtaining the near field communication trigger signal sent by the user terminal, it may further include: obtaining a membership login instruction sent by a merchant device associated with the near field communication device; based on the membership login instruction, determining the membership payment link.

[0107] In practical applications, merchant operators such as cashiers can perform operations on the merchant device. When the user needs to settle the bill, the cashier can perform the membership login operation on the merchant device, such as clicking a button, control, etc. indicating the trigger of the membership login process. Or, when the merchant device is a self-checkout device, the user can perform the membership login operation on the merchant device. The membership login instruction can be generated by the merchant device based on a preset operation performed by the settlement personnel on the merchant device.

[0108] The near field communication device can be associated with the merchant device. For example, the near field communication is associated with the merchant device through at least one of a network and a data cable; or, the corresponding relationship between the near field communication device and is stored in the server.

[0109] The merchant device can send the membership login instruction to the near field communication device through a network or a data cable. Or, the merchant device can send the membership login instruction to the server, and the server sends the membership login instruction to the near field communication device.

[0110] After the near field communication device obtains the membership login instruction, it can place the membership payment link in the NFC tag, or set the NFC tag or the membership payment link in the NFC tag to an available state, so that the near field communication device can send the membership payment link to the user terminal in response to the near field communication trigger signal of the user terminal.

[0111] It can be understood that in practical applications, the near-field communication device may not obtain the membership login instruction sent by the merchant device. The tag information of the near-field communication device can be obtained by the user terminal at any time without the merchant device sending a trigger instruction. Here, no specific limitation is imposed on whether the merchant device needs to send a membership login instruction.

[0112] The membership payment link can be requested by the near-field communication device from the server, or it can also be a membership payment link pre-stored locally in the near-field communication device.

[0113] As an implementation manner, determining the membership payment link based on the membership login instruction may specifically include: sending a link information acquisition request to the server based on the membership login instruction; and acquiring the membership payment link fed back by the server.

[0114] The near-field communication device can interact with the server. Specifically, the near-field communication device may have an application program or an application terminal. The near-field communication device can access the server according to a preset access path and send a link information acquisition request to the server. This request may include the identification information of the near-field communication device and may also include service identification information for instructing the server to feed back the membership payment link, so that after the server receives this request, it can determine to execute the process of generating the membership payment link and feed back the membership payment link to the near-field communication device.

[0115] To ensure the uniqueness of the membership payment link, a dynamic token can also be generated based on the identification information of the near-field communication device. For example, a dynamic token can be generated based on the device number of the near-field communication device, or a dynamic token can also be generated based on the device number and the timestamp.

[0116] To improve the efficiency of membership payment, the near-field communication device can locally store the fixed information included in the membership payment link. The server can generate a dynamic token, and then the near-field communication device can locally assemble to obtain the membership payment link. This can reduce the amount of data transmission between the server and the near-field communication device, improve the data transmission efficiency, improve the stability of data transmission, and is also beneficial to improving the user experience. Optionally, acquiring the membership payment link fed back by the server may specifically include: acquiring the dynamic token fed back by the server; and assembling the dynamic token with the fixed information stored locally in the near-field communication device to obtain the membership payment link.

[0117] After the near-field communication device acquires the dynamic token fed back by the server, it can splice the fixed information stored locally and the acquired dynamic token together according to a preset rule to obtain the membership payment link. For example, the near-field communication device may locally have a link template, or a link template containing fixed information, and the dynamic token can be placed into the link template to obtain the membership payment link.

[0118] In the embodiments of this specification, in order to improve the processing efficiency, one or more backup membership payment links can also be pre-stored locally in the near-field communication device. The backup membership payment link can be a membership payment link that already exists locally in the near-field communication device before the merchant device issues a membership login instruction. Optionally, several backup membership payment links can be stored locally in the near-field communication device; determining the membership payment link based on the membership login instruction specifically includes sending the membership payment link to the user terminal, and specifically can include: selecting a membership payment link from several backup membership payment links stored locally.

[0119] As an implementation manner, the near-field communication device can have a logic program for generating membership payment links locally. When the near-field communication device is idle or the number of backup membership payment links is less than or equal to a preset number, the near-field communication device can generate one or more backup membership payment links locally.

[0120] To ensure the uniqueness of the transaction, the membership payment link can be a link that can only be used once. After the near-field communication device provides the membership payment link to the user terminal, the near-field communication device can delete the membership payment link or mark it as an invalid state.

[0121] As another implementation manner, the backup membership payment links stored locally in the near-field communication device can be provided by the server. Optionally, before obtaining the near-field communication trigger signal sent by the user terminal, it can also include: obtaining the several backup membership payment links sent by the server; saving the several backup membership payment links to the local storage space of the near-field communication device.

[0122] In practical applications, the near-field communication device can request the server to send backup membership payment links, or the server can actively push backup membership payment links to the near-field communication device.

[0123] For example, when the number of available backup membership payment links locally in the near-field communication device is less than or equal to the preset number, the near-field communication device can send a link acquisition request to the server. The request can also include the quantity information of the membership payment links to be acquired. The server can feedback the corresponding number of membership payment links to the near-field communication device based on this request and save them locally in the near-field communication device as backup membership payment links. If a user terminal establishes near-field communication with the near-field communication device, the near-field communication device can provide the membership payment link stored locally to the user terminal.

[0124] For another example, the server can record the number of membership payment links that have been sent to the near field communication device, and can also record the number of payment requests sent by the merchant device associated with the near field communication device that have been obtained. Furthermore, the server can determine whether the number of available backup membership payment links on the near field communication device is less than or equal to a preset number. If it is less than or equal to the preset number, the server can actively push a certain number of membership payment links to the near field communication device.

[0125] For another example, after the near field communication device sends a membership payment link to the user terminal, it can request the server or generate a new membership payment link based on a local logic program as a backup membership payment link for subsequent use.

[0126] The near field communication device can have a storage module, and fixed information can be stored locally in the near field communication device. For example, the local storage space of the near field communication device can be a memory space, a cache space, or can also be a trusted execution environment (TEE), etc. There is no specific limitation on the storage space here.

[0127] Similar to the above embodiments, the obtaining of the several backup membership payment links sent by the server specifically may include: the several backup dynamic tokens sent by the server.

[0128] The near field communication device can assemble each backup dynamic token based on the fixed information or link template already available locally to obtain a backup membership payment link.

[0129] For example, after the near field communication device obtains a near field communication trigger signal sent by the user terminal, it can select a dynamic token from the backup dynamic tokens and splice the dynamic token according to the fixed information or link template already available to obtain a membership payment link that can be sent to the user terminal. For another example, after the near field communication device obtains several backup dynamic tokens, it can splice each dynamic token using the fixed information or link template already available, or the near field communication device can execute the splicing process in an idle state to obtain each backup membership payment link. There is no limitation on the generation timing of the membership payment link here.

[0130] In the embodiments of this specification, the merchant device can reuse the existing membership management link and payment link. The user information and payment vouchers of the user terminal queried by the server can be provided to the merchant device so that the merchant device can perform a membership processing process based on the user information and send a payment request to the server based on the payment voucher.

[0131] As an implementation, the near field communication device can be used as an auxiliary device of the merchant device. The server can send user information and payment vouchers to the near field communication device, which are then provided to the merchant device. Optionally, the method in the embodiments of this specification may further include: obtaining the user information and payment vouchers of the user terminal fed back by the server; sending the user information and payment vouchers to the merchant device associated with the near field communication device.

[0132] In practical applications, the server that processes the payment request sent by the merchant device and the server that provides user information and payment vouchers may be different servers. In the embodiments of this specification, the near field communication device has the ability to access the server that provides user information and payment vouchers. If the merchant device cannot access the server that provides user information and payment vouchers according to the existing link, the near field communication device can also act as an intermediate device to obtain the user information and payment vouchers, so that the merchant device can also execute the membership and payment processes according to the existing link.

[0133] If the merchant device can access the server that provides user information and payment vouchers, the server may have the corresponding relationship between the merchant device and the near field communication device, and may also have the corresponding information between the near field communication device and the membership payment link or dynamic token. After the user terminal sends the confirmation information containing the dynamic token to the server, the server can determine the merchant device corresponding to the dynamic token according to the corresponding relationship, and the server can send the determined user information and payment vouchers to the merchant device. In this way, the merchant device can also obtain the user information and payment vouchers.

[0134] To ensure the correctness of the transaction, in the embodiments of this specification, the server can feed back user information and payment vouchers based on the inquiry of the near field communication device. Optionally, after sending the membership payment link to the user terminal in response to the near field communication trigger signal, it may further include: sending a transaction party information query request containing the dynamic token to the server based on the dynamic token.

[0135] Among them, the transaction party information query request may be a request for the server to query the user-related information of the user terminal that sends the same dynamic token. In practical applications, after the near field communication device senses that the membership payment link is read, it can poll the user information and payment vouchers from the server according to the dynamic token in the membership payment link.

[0136] Before the server obtains a transaction party information query request sent by a near-field communication device, if it has not obtained a confirmation message sent by the user terminal that is consistent with the dynamic token included in the request, the server may not process the transaction party information query request sent by the near-field communication device this time, or suspend the transaction party information query request or mark it as a pending state. If the server subsequently obtains a confirmation message sent by the user terminal that is consistent with the dynamic token included in the request, the server may query the user information and payment vouchers of the user terminal according to the confirmation message, and then feedback the user information and payment vouchers to the near-field communication device that sent the transaction party information query request including the dynamic token or the merchant device associated with the near-field communication device.

[0137] In the embodiments of this specification, the server executes the process of querying user information and payment vouchers after obtaining the confirmation message provided by the user terminal; before obtaining the confirmation message provided by the user terminal, the server may not execute the process of querying user information and payment vouchers. Even after obtaining the transaction party information query request sent by the near-field communication device, the server may not execute the process of querying user information and payment vouchers, but wait until obtaining the confirmation message provided by the user terminal and then execute it. And after obtaining the transaction party information query request sent by the near-field communication device, the server feeds back the queried user information and payment vouchers. This can ensure information security and avoid invalid queries.

[0138] To more clearly illustrate the membership payment method provided in the embodiments of this specification, Figure 4 The following is a swimlane diagram of a membership payment method provided in the embodiments of this specification. As Figure 4 shown, the solution may include the following steps.

[0139] Step 402: The merchant device obtains the membership login trigger operation performed by the cashier.

[0140] The merchant device may be a device with operation components such as an operation screen and a keyboard. When the user arrives at the cashier desk for settlement, the cashier may ask the user whether they are a member or whether they will pay through membership. After the user determines to use the membership, the cashier may operate the merchant device, such as clicking the "member" button, etc., a control that can trigger the membership login and payment process. The merchant device may obtain the membership login trigger operation performed by the cashier.

[0141] In practical applications, if the merchant device is a self-service settlement device, the person who performs the membership login trigger operation may also be the user who is consuming. Here, the specific execution subject of the trigger operation is not limited.

[0142] Step 404: Send a membership login instruction to the near-field communication device.

[0143] Based on the member login trigger operation performed by the cashier, the merchant device can also send an instruction to the near-field communication device so that the near-field communication device can request a member payment link from the server.

[0144] Step 406: The near-field communication device sends a link acquisition request to the server.

[0145] Among them, after the near-field communication device obtains the instruction sent by the merchant device, it can request a member payment link from the server.

[0146] The link acquisition request may include device identification information of the near-field communication device and / or the merchant device, such as device ID, etc. The server can generate a member payment link based on the device identification information and feedback it to the near-field communication device.

[0147] Step 408: The server feeds back the member payment link to the near-field communication device.

[0148] In practical applications, one or more backup member payment link information can also be pre-stored in the near-field communication device, and the steps shown in the above steps 402 to 408 may not be executed. For example, when the near-field communication device is idle or the number of pre-stored backup member payment link information is less than or equal to the preset number, the near-field communication device can actively send a link acquisition request to the server, or the server can actively push the link to the near-field communication device.

[0149] The member payment link may include fixed information and a dynamic token. To improve data transmission efficiency, the server can feedback the dynamic token without feedbacking the entire member payment link to the near-field communication device. The near-field communication device can assemble the member payment link based on the obtained dynamic token and the fixed information or link template stored locally.

[0150] The near-field communication device may include an NFC tag, and the near-field communication device can save the member payment link to the NFC tag so that when a user terminal approaches or touches the near-field communication device later, the user terminal can obtain the member payment link through near-field communication.

[0151] The server can also record which member payment links have been sent to which near-field communication devices, can also record the corresponding relationship between the near-field communication device and the merchant device, and can also record the merchant account information corresponding to the merchant device, etc.

[0152] After sending the member payment link to the near-field communication device, the server can also record the corresponding relationship between the member payment link and the near-field communication device, or record the corresponding relationship between the dynamic token and the near-field communication device that receives the dynamic token.

[0153] In practical applications, users can establish an NFC near-field communication connection between user terminals such as mobile phones and smart watches and near-field communication devices. For example, the user touches or brings the mobile phone close to the near-field communication device. The user terminal acting as an NFC card reader can execute step 410: send a near-field communication trigger signal.

[0154] As an implementation, when the user terminal is in the unlocked state, it can be in the NFC card reader mode, emit an NFC electromagnetic signal, and retrieve nearby NFC tags.

[0155] Near-field communication devices within the near-field communication range of the user terminal can respond to the electromagnetic signal and feedback tag information to the user terminal. Specifically, the near-field communication device can execute step 412: send a membership payment link to the user terminal.

[0156] The membership payment link can be included in the tag information of the NFC tag or the simulated tag of the near-field communication device. The near-field communication device can feedback the membership payment link to the user terminal via near-field communication in response to the near-field communication trigger signal sent by the user terminal. For the specific information transmission process, reference can be made to existing related technologies and will not be elaborated here.

[0157] After the near-field communication device determines the membership payment link to be sent to the user terminal, or during the process of presenting the membership payment link to the user terminal, or after the transmission ends, or after the near-field communication device senses that the link has been read, the near-field communication device can also request user-related information from the server in a polling manner. Specifically, the near-field communication device can execute step 414: poll user information based on a dynamic token.

[0158] The near-field communication device can, based on the dynamic token in the membership payment link, inquire about user-related information of the user who received the membership payment link or the dynamic token from the server at a preset time frequency until it obtains the user-related information feedback from the server.

[0159] In practical applications, the user terminal can be equipped with terminal applications with payment functions or membership management functions, such as terminal application programs APPs, mini-programs, etc. The membership payment link can contain the application identifier of the terminal application for processing payment services. The user terminal can execute step 416: start the payment application based on the application identifier.

[0160] Among them, the terminal system of the user terminal can start the payment application in the user terminal based on the application identifier included in the membership payment link. This payment application can be a payment application that the user has registered and used. On the basis of user authorization, the user terminal can automatically evoke this payment application based on the application identifier. In practical applications, the payment application can be started in the background or in the foreground, and no specific limitation is made here.

[0161] The user terminal system may also provide a membership payment link or a dynamic token in the link to the launched payment application. The payment application may access the server based on the link or the dynamic token. The server may, according to the dynamic token, determine that the user terminal is a user terminal that has established near-field communication with a near-field communication device, and may determine that the user terminal is a user terminal that conducts transactions with a near-field communication device or a merchant device. The user of the user terminal and the merchant of the merchant device are the two parties to the same transaction.

[0162] After the user terminal accesses the server, it may also display a membership payment inquiry page, which may be a page for asking whether the user logs in as a member or uses membership payment. The page may include a confirmation control. After the user operates on the control, it may indicate that the user agrees to log in as a member and pay using membership rights. Alternatively, if the user has not yet registered as a merchant member, the membership payment inquiry page may be a page for asking whether the user registers as a merchant member or whether to make a payment. The page may include a control for registering as a member, or a control for registering as a member and making a payment. After the user operates on the control, it may indicate that the user agrees to register as the merchant member or agrees to pay using membership rights. If the user performs a confirmation operation based on the membership payment inquiry page, the user terminal may execute step 418: send a confirmation message to the server based on the launched payment application.

[0163] In practical applications, if the user is already a member of the merchant and the user has authorized the user terminal or the payment application to perform membership login or membership payment operations by itself, the user terminal may not display the membership payment inquiry page either. For example, on the membership login and payment page, the user terminal may automatically generate a confirmation message and send it to the server. For example, after the user terminal accesses the server by carrying a dynamic token based on the launched payment application, the server may feedback the merchant information corresponding to the dynamic token to the user terminal. After the user terminal obtains the merchant information, it may automatically execute the process of confirming membership login and send a confirmation message to the server.

[0164] Alternatively, after the user terminal accesses the server, it may obtain the membership payment inquiry page feedback by the user terminal and may also display the membership payment inquiry page. However, without the user performing a confirmation operation, the page may automatically exit within a short time, and the user terminal may automatically perform a confirmation operation and send a confirmation message to the server.

[0165] After the server obtains the confirmation message sent by the user terminal, it may execute step 420: query user information and generate a payment voucher.

[0166] Step 422: Return the user information and the payment voucher to the near-field communication device.

[0167] Among them, the user information can be user information related to payment or information related to membership registration. For example, user UID, user mobile phone number, user ID number, user address, user email account, and so on.

[0168] The payment voucher can be information that can represent the payment account of the user terminal. For example, it can be information representing the payment code of the user terminal, such as the payment code number.

[0169] In practical applications, the existing processing capabilities of the merchant device can be followed or reused, and the merchant device executes the transaction process. The near-field communication device can also execute step 424: sending the user information and the payment voucher to the merchant device After the merchant device obtains the user information and the payment voucher, it can execute step 426: performing a membership login process based on the user information.

[0170] Among them, the merchant device can query the membership information database based on the user information, determine the rights and interests of the member user, determine the amount to be paid by the user, or the preferential amount enjoyed, or determine the points of the member user, etc., for membership information management.

[0171] The merchant device can also execute step 428: initiating a payment based on the payment voucher.

[0172] Among them, the merchant device can send a payment request to the server. The payment request can include the payment voucher, and can also include the amount information to be paid by the user, or can also include the merchant identification information, or can also include the dynamic token included in the above payment link information, so that the server can determine information such as the two parties to the transaction and the amount to be transacted.

[0173] In practical applications, if operators such as cashiers perform a membership login trigger operation on the merchant device, and the merchant device has obtained the information of the goods to be paid by the user, such as the name, quantity, amount, etc. of the goods, for example, the cashier scans the goods first, and the cash register can summarize the price and other information of the goods. After the operators such as cashiers perform a membership login trigger operation on the merchant device, the merchant device can also send information such as the amount to be paid by the user to the near-field communication device, and the near-field communication device can also include this information in the NFC tag information and provide it to the user terminal. The confirmation information sent by the user terminal to the server can also include information such as the amount to be paid by the user. In this way, the server can also check the order based on the information such as the amount to be paid, and can further ensure the accuracy of the transaction.

[0174] Of course, the product information to be paid by the user can also be obtained by the merchant device after an operator such as a cashier performs a membership login trigger operation on the merchant device. For example, the cashier first clicks the "Member" button on the cash register and then scans the product code or performs other operations. In this way, when the merchant device initiates a payment, it can provide information such as the amount to be paid or the actual amount that the user needs to pay according to the membership rights and interests to the server, and the server processes the transaction. The server can also execute step 430: execute the payment process and process the payment.

[0175] The server can process transactions based on the payment requests sent by the merchant device. For example, it can transfer the resources in the user account corresponding to the user terminal to the merchant account corresponding to the merchant device.

[0176] The server can also generate transaction result information and execute step 432: feedback the transaction result information to the user terminal.

[0177] In practical applications, the server can also feedback the transaction result information to the near-field communication device or the merchant device, which is not specifically limited here.

[0178] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method. Figure 5 For the embodiment of this specification, it provides Figure 2 a schematic structural diagram of a membership payment device. This device can be applied to the user terminal. As Figure 5 shown, this device may include: A trigger signal sending module 502, configured to send a near-field communication trigger signal; A link obtaining module 504, configured to obtain a membership payment link provided by a near-field communication device in response to the near-field communication trigger signal; the membership payment link includes fixed information and a dynamic token; An application start module 506, configured to determine that the target application in the user terminal is in a startup state based on the application identifier included in the fixed information; An information sending module 508, configured to send confirmation information including the dynamic token to the server based on the started target application; the server is configured to determine the user information and payment voucher of the user terminal based on the dynamic token and send them to the merchant device associated with the near-field communication device; the merchant device is configured to execute a membership processing process based on the user information and send a payment request to the server based on the payment voucher; the payment voucher is used to represent the user account information of the user terminal; A result obtaining module 510, configured to obtain the payment result information fed back by the server; the payment result information is generated by the server based on the payment request sent by the merchant device.

[0179] Based on Figure 5 For the device, the embodiments of the present specification also provide some specific implementation solutions, which will be described below.

[0180] Optionally, different member payment links include the same fixed information and different dynamic tokens.

[0181] Optionally, the user information includes the user's unique identifier in the target application; the payment voucher includes the payment code number of the user account of the user terminal.

[0182] Optionally, if the user of the user terminal is not a registered member of the merchant to which the merchant device belongs; the above information sending module can specifically be used for: based on the started target application, displaying a member registration and payment page; based on the user's confirmation operation on the member registration and payment page, generating a first confirmation information indicating agreement to register as a member and make a payment to the server; the first confirmation information includes the dynamic token.

[0183] Optionally, if the user of the user terminal is a registered member of the merchant to which the merchant device belongs; the above information sending module can specifically be used for: based on the started target application, displaying a member login and payment page; based on the user's confirmation operation on the member login and payment page, generating a second confirmation information indicating agreement to log in as a member and make a payment to the server, and the second confirmation information includes the dynamic token.

[0184] Optionally, the device may further include a judgment module. Before displaying the member login and payment page, the judgment module can be used for: judging whether the user terminal has started the fast business processing function; the fast business processing function is a function in which the target application automatically processes the business intermediate page without the user manually operating on the business intermediate page.

[0185] The above display of the member login and payment page may specifically include: if the user terminal has not started the fast business processing function, then display the member login and payment page.

[0186] Optionally, the device can also be used for: if the user terminal has started the fast business processing function, then the target application automatically generates a third confirmation information including the dynamic token.

[0187] Based on the same idea, the embodiments of the present specification also provide a device corresponding to the above method. Figure 6 For the Figure 3 shown in the structural schematic diagram of a member payment device provided by the embodiments of the present specification. This device can be applied to a near-field communication device. As Figure 6 shown, this device may include: A trigger signal acquisition module 602, configured to acquire a near field communication trigger signal sent by a user terminal; A link sending module 604, configured to send a membership payment link to the user terminal in response to the near field communication trigger signal; the membership payment link includes fixed information and a dynamic token; the user terminal is configured to execute the above method based on the membership payment link.

[0188] Optionally, the device may further include an instruction acquisition module. Before acquiring the near field communication trigger signal sent by the user terminal, the instruction acquisition module may be configured to: acquire a membership login instruction sent by a merchant device associated with the near field communication device; and determine a membership payment link based on the membership login instruction.

[0189] Optionally, the device may further include an information acquisition and sending module, which may be configured to: acquire user information and a payment voucher of the user terminal fed back by a server; and send the user information and the payment voucher to a merchant device associated with the near field communication device.

[0190] Optionally, the device may further include a request sending module. After sending the membership payment link to the user terminal in response to the near field communication trigger signal, the request sending module may be configured to: send a transaction party information query request including the dynamic token to the server based on the dynamic token.

[0191] Optionally, determining the membership payment link based on the membership login instruction may specifically include: sending a link information acquisition request to the server based on the membership login instruction; and acquiring the membership payment link fed back by the server.

[0192] Optionally, acquiring the membership payment link fed back by the server may specifically include: acquiring the dynamic token fed back by the server; and assembling the dynamic token with the fixed information locally stored in the near field communication device to obtain the membership payment link.

[0193] Optionally, a plurality of standby membership payment links are locally stored in the near field communication device; determining the membership payment link based on the membership login instruction may specifically include: selecting a membership payment link from the plurality of standby membership payment links locally stored.

[0194] Optionally, the device further includes a storage module. Before acquiring the near field communication trigger signal sent by the user terminal, the storage module may further be configured to: acquire the plurality of standby membership payment links sent by the server; and save the plurality of standby membership payment links to the local storage space of the near field communication device.

[0195] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method.

[0196] Figure 7 FIG. is a schematic structural diagram of a membership payment device provided by an embodiment of this specification. As Figure 7 shown, the device 700 may include: At least one processor 710; and, A memory 730 communicatively connected to the at least one processor; wherein, The memory 730 stores instructions 720 executable by the at least one processor 710, and the instructions are executed by the at least one processor 710 so that the at least one processor 710 can execute the above at least one membership payment method.

[0197] Based on the same idea, the embodiments of this specification also provide a computer-readable medium corresponding to the above method. A computer-readable instruction is stored on the computer-readable medium, and the computer-readable instruction can be executed by a processor to implement the above membership payment method.

[0198] Each embodiment in this specification is described in a progressive manner. The same or similar parts among the embodiments can be referred to each other, and the key point of each embodiment is to illustrate the differences from other embodiments. In particular, for Figure 7 the device shown, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0199] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. And the collection, use, and processing of relevant data need to comply with relevant laws, regulations, and standards in the relevant regions, and corresponding operation entrances are provided for users to choose to authorize or refuse.

[0200] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) or software improvements (improvements to method flows). However, with the development of technology, many method flow improvements today can be regarded as direct improvements to hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement to a method flow cannot be implemented using a hardware entity module. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logical function is determined by the user programming the device. Designers can program themselves to "integrate" a digital system onto a single PLD, without having to ask a chip manufacturer to design and fabricate a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly implemented using "logic compiler" software, which is similar to the software compilers used in program development and writing. The original code before compilation also has to be written in a specific programming language, which is called a Hardware Description Language (HDL). There is not just one type of HDL, but many, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones currently are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also be aware that by simply performing a little logical programming on the method flow using the above-mentioned several hardware description languages and programming it into an integrated circuit, it is easy to obtain the hardware circuit that implements the logical method flow.

[0201] The controller can be implemented in any suitable manner. For example, the controller can take the form of, for example, a microprocessor or a processor and a computer-readable medium storing computer-readable program code (such as software or firmware) executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of the controller include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in the form of pure computer-readable program code, it is entirely possible to make the controller implement the same function in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be regarded as the structures within the hardware component. Or even, the devices for implementing various functions can be regarded as either software modules for implementing the method or structures within the hardware component.

[0202] The systems, devices, modules, or units illustrated in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0203] For the convenience of description, when describing the above devices, they are described separately as various units according to their functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0204] Those skilled in the art should understand that the embodiments of the present invention can be provided as a method, a system, or a computer program product. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present invention can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memories, CD-ROMs, optical memories, etc.) containing computer-usable program code.

[0205] 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 should be understood that each flow and / or block in the flowchart illustrations and / or block diagrams, and combinations of flows and / or blocks in the flowchart illustrations 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 executed by 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 or blocks. Figure 1 in a flow or flows and / or block or blocks Figure 1 or means for implementing the functions specified in a block or blocks.

[0206] 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 that implement the functions specified in the flowchart flow or flows and / or block or blocks. Figure 1 in a flow or flows and / or block or blocks Figure 1 or means for implementing the functions specified in a block or blocks.

[0207] 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 executed on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and / or block or blocks. Figure 1 in a flow or flows and / or block or blocks Figure 1 or means for implementing the functions specified in a block or blocks.

[0208] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0209] Memory may include non-permanent memory in the form of 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.

[0210] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. 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, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined in this article, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0211] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0212] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, the present application may take 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.

[0213] The present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0214] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, various changes and modifications can be made to the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included within the scope of the claims of the present application.

Claims

1. A member payment method, applied to a user terminal, comprising: Sending a near field communication trigger signal; Acquire a member payment link provided by the near field communication device in response to the near field communication trigger signal; The member payment link includes fixed information and a dynamic token; Based on the application identifier included in the fixed information, determining that the target application in the user terminal is in an activated state; Sending confirmation information including the dynamic token to a server based on the started target application; The server is used to determine the user information and payment credentials of the user terminal based on the dynamic token and send them to the merchant device associated with the near field communication device; the merchant device is used to execute the member processing process based on the user information and send a payment request to the server based on the payment credentials; The payment voucher is used to represent the user account information of the user terminal; Obtain payment result information fed back by the server; the payment result information is generated by the server based on the payment request sent by the merchant device.

2. According to the method of claim 1, different member payment links contain the same fixed information and different dynamic tokens.

3. According to the method of claim 1, the user information includes a unique user identifier of the user in the target application; the payment credential includes a payment code number of a user account of the user terminal.

4. The method according to claim 1, if the user of the user terminal is not a registered member of the merchant to which the merchant device belongs; The starting target application sends confirmation information including the dynamic token to the server, specifically including: Based on the launched target application, displaying a member registration and payment page; Based on the user's confirmation operation on the member registration and payment page, a first confirmation message indicating the user's agreement to register as a member and make payment is generated and sent to the server; the first confirmation message includes the dynamic token.

5. The method according to claim 1, if the user of the user terminal is a registered member of the merchant where the merchant device is located; The starting target application sends confirmation information including the dynamic token to the server, specifically including: Based on the launched target application, displaying a member login and payment page; Based on the user's confirmation operation on the member login and payment page, second confirmation information indicating consent to member login and payment is generated to the server, and the second confirmation information includes the dynamic token.

6. The method according to claim 5, before displaying the member login and payment page, further comprising: Determine whether the user terminal has started the ultra-fast service processing function; the ultra-fast service processing function is a function for the target application to automatically process the service intermediate page without the user having to manually operate the service intermediate page; The member login and payment page is displayed, specifically including: If the user terminal does not start the express business processing function, the member login and payment page will be displayed.

7. The method according to claim 6, further comprising: If the user terminal has activated the ultra-fast service processing function, the target application automatically generates third confirmation information including the dynamic token.

8. A member payment method, applied to a near field communication device, comprising: Obtaining a near field communication trigger signal sent by a user terminal; In response to the near field communication trigger signal, sending a member payment link to the user terminal; The member payment link includes fixed information and a dynamic token; the user terminal is used to execute the method according to claim 1 based on the member payment link.

9. The method according to claim 8, before acquiring the near field communication trigger signal sent by the user terminal, further comprising: Obtaining a member login instruction issued by a merchant device associated with the near field communication device; Based on the member login instruction, a member payment link is determined.

10. The method according to claim 8, further comprising: Obtaining user information and payment credentials of the user terminal fed back by the server; The user information and the payment credentials are sent to a merchant device associated with the near field communication device.

11. The method according to claim 8, after sending a member payment link to the user terminal in response to the near field communication trigger signal, further comprising: Based on the dynamic token, a transaction party information query request including the dynamic token is sent to the server.

12. The method according to claim 9, wherein determining the member payment link based on the member login instruction specifically comprises: Based on the member login instruction, sending a link information acquisition request to the server; Obtain the member payment link fed back by the server.

13. According to the method of claim 12, the step of obtaining the member payment link fed back by the server specifically comprises: Obtaining the dynamic token fed back by the server; The dynamic token is assembled with the fixed information stored locally in the near field communication device to obtain the member payment link.

14. The method according to claim 9, wherein the local storage of the near field communication device has a plurality of backup member payment links; and determining the member payment link based on the member login instruction specifically comprises: A member payment link is selected from several backup member payment links stored locally.

15. The method according to claim 14, before acquiring the near field communication trigger signal sent by the user terminal, further comprising: Obtaining the plurality of backup member payment links sent by the server; The plurality of standby member payment links are stored in a local storage space of the near field communication device.

16. A member payment device, applied to a user terminal, comprising: A trigger signal sending module, used for sending a near field communication trigger signal; A link acquisition module, used to acquire a member payment link provided by the near field communication device in response to the near field communication trigger signal; the member payment link includes fixed information and a dynamic token; An application startup module, configured to determine, based on the application identifier included in the fixed information, that the target application in the user terminal is in a startup state; An information sending module, used for sending confirmation information including the dynamic token to a server based on the started target application; The server is used to determine the user information and payment credentials of the user terminal based on the dynamic token and send them to the merchant device associated with the near field communication device; the merchant device is used to execute the member processing process based on the user information and send a payment request to the server based on the payment credentials; The payment voucher is used to represent the user account information of the user terminal; The result acquisition module is used to acquire the payment result information fed back by the server; the payment result information is generated by the server based on the payment request sent by the merchant device.

17. A member payment device, applied to a near field communication device, comprising: A trigger signal acquisition module, used to acquire a near field communication trigger signal sent by a user terminal; A link sending module, used to send a member payment link to the user terminal in response to the near field communication trigger signal; the member payment link includes fixed information and a dynamic token; the user terminal is used to execute the method of claim 1 based on the member payment link.

18. A member payment device, comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the member payment method according to any one of claims 1 to 15.

19. A computer-readable medium having computer-readable instructions stored thereon, wherein the computer-readable instructions can be executed by a processor to implement the member payment method according to any one of claims 1 to 15.

Images