Payment method and apparatus based on near-field communication, device and medium

Abstract

Embodiments of the present application disclose a payment method and apparatus based on near-field communication, a device, and a medium. A solution comprises: a mobile terminal having near-field communication functionality emitting an electromagnetic signal used for triggering an NFC tag; obtaining tag information of the NFC tag in response to the electromagnetic signal, the tag information comprising payment link information; displaying a payment page including user information of a first transaction party on the basis of the payment link information; obtaining payment information provided by a second transaction party on the basis of the payment page; and sending a payment processing request containing said payment information to a server, the server being used to complete payment on the basis of the payment processing request.

Description

A payment method, device, equipment and medium based on near-field communication Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a payment method, apparatus, device, and medium based on near-field communication. Background Art

[0002] With the development of computer technology, mobile payments based on payment codes are becoming increasingly popular, greatly improving the user payment experience. However, with the growth of mobile applications, games, novels, short videos, and other applications are increasingly occupying terminal screen time. To pay, users must exit the current application, find a payment application with payment functionality from the terminal's application list, and then activate the QR code scanning function or open the payment code in the payment application, which is a complex user operation.

[0003] Therefore, how to simplify users' payment operations and improve user experience is a technical problem that needs to be solved urgently.

[0004] Summary of the Invention

[0005] The embodiments of this specification provide a payment method, apparatus, device, and medium based on near-field communication to solve the problem of complex user operations in existing payment methods.

[0006] To solve the above technical problems, the embodiments of this specification are implemented as follows.

[0007] An embodiment of this specification provides a payment method based on near-field communication, including: a mobile terminal with near-field communication function sends an electromagnetic signal for triggering an NFC tag; obtains tag information of the NFC tag in response to the electromagnetic signal; the tag information includes payment link information; based on the payment link information, displays a payment page including user information of a first transaction party; obtains payment information provided by a second transaction party based on the payment page; and sends a payment processing request including the payment information to a server, wherein the server is configured to complete the payment based on the payment processing request.

[0008] An embodiment of this specification provides a payment method based on near-field communication, comprising: a mobile terminal with near-field communication function sends an electromagnetic signal for triggering an NFC tag; obtaining tag information of the NFC tag that responds to the electromagnetic signal; using the tag information to trigger a payment process; based on the tag information, obtaining transaction identification information for representing user payment account information in the mobile terminal; sending the transaction identification information to a payment device associated with the NFC tag, and the payment device being used to execute the payment process according to the transaction identification information.

[0009] An embodiment of this specification provides a payment method based on near-field communication, including: a mobile terminal with near-field communication function obtains tag information of an NFC tag associated with a payment device; based on the tag information, a payment application in the mobile terminal is started; based on the started payment application, a payment processing request is sent to a server; the server is used to process the payment transaction based on the payment processing request and feedback payment result information; and based on the payment result information feedback by the server, a transaction result page is displayed.

[0010] An embodiment of this specification provides a payment method based on near-field communication, comprising: a server obtaining a payment processing request containing payment information sent by a mobile terminal with near-field communication function; the payment information is provided by the second transaction party based on a payment page displaying user information containing the first transaction party; the payment page is generated by the mobile terminal based on tag information in an obtained NFC tag; the tag information contains payment link information; and based on the payment processing request, completing the payment business for the first transaction party and the second transaction party.

[0011] An embodiment of this specification provides a payment method based on near-field communication, including: a server obtaining a payment information acquisition request generated by a mobile terminal with near-field communication function based on tag information in an acquired NFC tag; the tag information is used to trigger a payment process; based on the payment information acquisition request, transaction identification information is generated for representing user payment account information in the mobile terminal; the transaction identification information is sent to a payment device associated with the NFC tag; and the payment device is used to execute the payment process according to the transaction identification information.

[0012] An embodiment of this specification provides a payment method based on near-field communication, including: a server obtaining a payment processing request sent by a mobile terminal; the payment processing request is sent by a payment application launched by the mobile terminal based on tag information in an NFC tag; processing a payment transaction based on the payment request and generating payment result information; and feeding back the payment result information to the mobile terminal.

[0013] An embodiment of the present specification provides a payment device based on near-field communication, comprising: a trigger information sending module for sending an electromagnetic signal for triggering an NFC tag; a tag information acquisition module for acquiring tag information of the NFC tag in response to the electromagnetic signal; the tag information including payment link information; a page display module for displaying a payment page including user information of a first transaction party based on the payment link information; a payment information acquisition module for acquiring payment information provided by a second transaction party based on the payment page; and a request sending module for sending a payment processing request including the payment information to a server, wherein the server is configured to complete payment based on the payment processing request.

[0014] An embodiment of the present specification provides a payment device based on near-field communication, comprising: a trigger information sending module for sending an electromagnetic signal for triggering an NFC tag; a tag information acquisition module for acquiring tag information of the NFC tag in response to the electromagnetic signal; the tag information is used to trigger a payment process; a transaction identification acquisition module for acquiring, based on the tag information, transaction identification information for representing user payment account information in the mobile terminal; and a transaction identification sending module for sending the transaction identification information to a payment device associated with the NFC tag, wherein the payment device is used to execute a payment process according to the transaction identification information.

[0015] A payment device based on near-field communication provided in an embodiment of this specification includes: a tag information acquisition module for acquiring tag information of an NFC tag associated with a payment device; an application startup module for starting a payment application in the mobile terminal based on the tag information; a request sending module for sending a payment processing request to a server based on the started payment application; the server for processing a payment transaction based on the payment processing request and feeding back payment result information; and a page display module for displaying a transaction result page based on the payment result information fed back by the server.

[0016] A payment device based on near-field communication provided in an embodiment of this specification includes: a request acquisition module, used to obtain a payment processing request containing payment information sent by a mobile terminal with near-field communication function; the payment information is provided by the second transaction party based on a payment page displaying user information containing the first transaction party; the payment page is generated by the mobile terminal based on tag information in an acquired NFC tag; the tag information contains payment link information; and a request processing module, used to complete payment services for the first transaction party and the second transaction party based on the payment processing request.

[0017] An embodiment of the present specification provides a payment device based on near-field communication, comprising: a request acquisition module, configured to acquire a payment information acquisition request generated by a mobile terminal with near-field communication functionality based on tag information in an acquired NFC tag; the tag information is used to trigger a payment process; an information generation module, configured to generate transaction identification information representing user payment account information in the mobile terminal based on the payment information acquisition request; a sending module, configured to send the transaction identification information to a payment device associated with the NFC tag; the payment device being configured to execute a payment process based on the transaction identification information.

[0018] An embodiment of this specification provides a near-field communication-based payment device, comprising: a request acquisition module, configured to acquire a payment processing request sent by a mobile terminal; the payment processing request is sent by a payment application initiated by the mobile terminal based on tag information in an NFC tag; a payment processing module, configured to process a payment transaction based on the payment request and generate payment result information; and a result sending module, configured to feed back the payment result information to the mobile terminal.

[0019] A payment device based on near-field communication is provided in an embodiment of the present specification, comprising: 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 a payment method based on near-field communication.

[0020] An embodiment of this specification provides a computer-readable medium having computer-readable instructions stored thereon. The computer-readable instructions can be executed by a processor to implement a payment method based on near-field communication.

[0021] At least one embodiment of this specification achieves the following beneficial effects: In the embodiments of this specification, a mobile terminal can obtain payment link information from an NFC tag via near-field communication. Based on this information, the mobile terminal can display a payment page, where the user can complete payment by entering payment information such as the payment amount. This eliminates the need for the user to find a payment application and then perform the corresponding payment operation within the payment application. For example, in a scenario where a payment code needs to be scanned, the user does not need to find the payment application and then select the scan code function within the payment application. In the embodiments of this specification, the mobile terminal can display the payment page based on the information in the NFC tag, simplifying user operations and improving the user experience.

[0022] In at least one embodiment, a mobile terminal uses near-field communication to retrieve the tag information from an NFC tag used to trigger the payment process, obtain transaction identification information, and transmit it to a payment device to initiate payment. This eliminates the need for users to find a payment application and then perform the corresponding payment operation within the payment application. For example, in a scenario where a payment code is required to be scanned by a payment device, users no longer need to find the payment application and then select the payment code within the payment application to display it. In the embodiments of this specification, a mobile terminal can transmit transaction identification information used for payment to a payment device based on the information in the NFC tag, simplifying user operations and improving the user experience.

[0023] In at least one embodiment, the mobile terminal can obtain the tag information in the NFC tag through near-field communication, start the payment application in the mobile terminal, and initiate a payment processing request to the server. The server can process the payment service and feedback the result information to the mobile terminal. In this way, payment can be triggered through NFC, and the user does not need to manually find the payment application and then manually start the payment application to make payment, which can simplify user operations and improve user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0025] FIG1 is a schematic diagram of an application scenario of a payment method based on near field communication in an embodiment of this specification;

[0026] FIG2 is a schematic diagram of a process of a payment method based on near field communication provided in an embodiment of this specification;

[0027] FIG3 is a swim-lane diagram of a payment method based on near-field communication provided in an embodiment of this specification;

[0028] FIG4 is a schematic diagram of an application scenario of a payment method based on near field communication in an embodiment of this specification;

[0029] FIG5 is a flow chart of a payment method based on near field communication provided in an embodiment of this specification;

[0030] FIG6 is a swim-lane diagram of a payment method based on near-field communication provided in an embodiment of this specification;

[0031] FIG7 is a flow chart of a payment method based on near field communication provided in an embodiment of this specification;

[0032] FIG8 is a schematic diagram of a payment reminder page provided in an embodiment of this specification;

[0033] FIG9 is a schematic diagram of a payment page provided in an embodiment of this specification;

[0034] FIG10 is a schematic diagram of a transaction result page provided in an embodiment of this specification;

[0035] FIG11 is a schematic diagram of displaying prompt information provided in an embodiment of this specification;

[0036] FIG12 is a schematic diagram of displaying prompt information provided in an embodiment of this specification;

[0037] FIG13 is a schematic diagram of displaying prompt information provided in an embodiment of this specification;

[0038] FIG14 is a schematic diagram of a setting page provided in an embodiment of this specification;

[0039] FIG15 is a schematic diagram of a payment response page provided in an embodiment of this specification;

[0040] FIG16 is a flow chart of a payment method based on near field communication provided in an embodiment of this specification;

[0041] FIG17 is a flow chart of a payment method based on near field communication provided in an embodiment of this specification;

[0042] FIG18 is a flow chart of a payment method based on near field communication provided in an embodiment of this specification;

[0043] FIG19 is a schematic diagram of the structure of a payment device based on near field communication according to an embodiment of this specification, corresponding to FIG2 ;

[0044] FIG20 is a schematic diagram of the structure of a payment device based on near field communication corresponding to FIG5 provided in an embodiment of this specification;

[0045] FIG21 is a schematic diagram of the structure of a payment device based on near field communication provided in an embodiment of this specification, corresponding to FIG7 ;

[0046] FIG22 is a schematic diagram of the structure of a payment device based on near field communication provided in an embodiment of this specification, corresponding to FIG16 ;

[0047] FIG23 is a schematic diagram of the structure of a payment device based on near field communication provided in an embodiment of this specification, corresponding to FIG17 ;

[0048] FIG24 is a schematic diagram of the structure of a payment device based on near field communication provided in an embodiment of this specification, corresponding to FIG18 ;

[0049] FIG25 is a schematic diagram of the structure of a payment device based on near field communication provided in an embodiment of this specification. DETAILED DESCRIPTION

[0050] To make the purpose, technical solutions, and advantages of one or more embodiments of this specification more clear, the technical solutions of one or more embodiments of this specification will be clearly and completely described below in conjunction with the specific embodiments of this specification and the corresponding drawings. Obviously, the embodiments described are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of one or more embodiments of this specification.

[0051] The technical solutions provided by the embodiments of this specification are described in detail below with reference to the accompanying drawings.

[0052] In the prior art, when purchasing goods, users typically need to present a payment code or scan the merchant's payment code to pay. Typically, users must find the payment app on their device and then select the payment code or scan code function to make the payment. If the user is currently using other applications on the device before making a payment, such as reading an e-book or watching a video, they must exit the current application, find the payment app, and then find the payment code or scan code function, making the process more complex.

[0053] In order to solve the defects in the prior art, the present solution provides the following embodiments: Figure 1 is a schematic diagram of an application scenario of a payment method based on near field communication in an embodiment of this specification. As shown in Figure 1, the solution may include a mobile terminal 1 with near field communication function, an NFC tag 2 carrying tag information, and a server 3 for handling payment services. Among them, when the mobile terminal 1 is close to the NFC tag 2, when it reaches a certain distance, it can trigger the NFC tag and obtain the tag information contained in the NFC tag 2. The tag information may include payment link information for displaying the payment page. The mobile terminal 1 can display the payment page based on the obtained tag information. The user can enter the payment amount and other information on the payment page. The terminal 1 can send a payment request containing the payment information to the server 3, and the server 3 can process the payment request to complete the payment.

[0054] Next, a payment method based on near field communication provided in the embodiments of the specification will be described in detail with reference to the accompanying drawings.

[0055] Figure 2 is a flow chart of a payment method based on near field communication provided in an embodiment of this specification. From a program perspective, the execution subject of the process can be a program or application client installed in an application server or terminal application.

[0056] As shown in FIG. 2 , the process may include the following steps 202 to 210 .

[0057] Step 202: A mobile terminal with a near field communication function sends an electromagnetic signal for triggering an NFC tag.

[0058] NFC (Near Field Communication) is a near field communication technology, and mobile terminals can have NFC near field communication functions. Mobile terminals can include portable, wearable and other movable terminals, such as mobile phones, smart watches, etc. Near field communication, also known as short-range wireless communication, is a short-range high-frequency wireless communication technology that allows contactless point-to-point data transmission and exchange between electronic devices. In the embodiments of this specification, the NFC tag can be a passive electronic tag or electronic chip, which can generate an induction signal with the mobile device and transmit data when a mobile device with near field communication function is close. After turning on the near field communication function, the mobile device can send electromagnetic signals, which can activate NFC tags within a preset distance to perform data transmission. The specific NFC communication process can be referred to the existing NFC communication technology and will not be repeated here.

[0059] Step 204: Acquire tag information of the NFC tag that responds to the electromagnetic signal; the tag information includes payment link information.

[0060] The tag information to be transmitted can be pre-written in the NFC tag. In the embodiment of this specification, the tag information may include link information for payment, for example, it may include the payment application to be invoked and the payment link information. The mobile terminal can invoke and display the payment page based on the acquired tag information.

[0061] Step 206: Based on the payment link information, a payment page including the user information of the first transaction party is displayed.

[0062] The first transaction party can be understood as the party that owns the NFC tag. If the NFC tag is used for receiving payments, the first transaction party can represent the payee; if the NFC tag is used for making payments, the first transaction party can represent the payee. The tag information in the NFC tag can be generated based on the transaction party information provided by the first transaction party. In actual applications, the payment link information used to invoke the payment page can be written into the NFC tag according to the NFC communication protocol.

[0063] Step 208: Obtain payment information provided by the second transaction party based on the payment page.

[0064] The second transaction party and the first transaction party can represent the two parties that have a transaction relationship. For example, if the NFC tag is used as a tag for collecting payment, the first transaction party can represent the payee, and the second transaction party can represent the payee; if the NFC tag is a tag for payment, the first transaction party can represent the payee, and the second transaction party can represent the payee. The payment page may include an area for filling in or selecting payment information such as the payment amount and payment method, and the transaction information can be filled in according to actual transaction needs. The payment page in the embodiment of this description may be the same as or similar to the existing payment page entered by scanning a QR code or other payment code through a terminal. The user can provide payment information according to the existing commonly used operation method, which can be more in line with user habits. In actual applications, the layout, format, content, etc. of the payment page can also be set according to actual needs, and no specific limitation is made here. For example, in actual applications, the first transaction party can set the transaction amount information according to actual transaction needs, or the transaction amount can be set by the second transaction party. In this way, the payment page can include the transaction amount information set by the first transaction party or the second transaction party according to the required payment amount. The second transaction party can perform an operation to confirm the transaction information, such as clicking the OK control or after a preset time period, such as after a 3-second or 5-second countdown, if the user does not cancel the payment, if the cancel control is not clicked, it can indicate that the information in the payment page of the second transaction party has been confirmed, and the terminal can obtain the payment information including the transaction amount information.

[0065] It is understandable that the second transaction party can perform some substantial operations on the payment page, such as clicking a control indicating confirmation, filling in the payment amount, confirming or selecting a payment method, etc. to perform real operations on the payment page; the second transaction party can also perform non-substantial operations on the payment page, for example, the payment page can display countdown information or the payment page does not display countdown information but executes a countdown program in the terminal background. If the user does not operate the payment page before the countdown ends, such as not performing the operation to cancel the payment, it can indicate that the user agrees to make the payment, or it can indicate that the user has confirmed the payment information. Among them, the user’s failure to cancel the payment operation can indicate that the user has not performed a substantial operation for the payment page, or it can indicate that the user has performed an inaction type operation on the payment page. That is to say, in the embodiments of this specification, the above-mentioned acquisition of the payment information provided by the second transaction party based on the payment page can include obtaining the payment information provided by the second transaction party based on the substantial operation or non-substantial operation performed on the payment page, which is not specifically limited here.

[0066] Step 210: Send a payment processing request containing the payment information to a server, and the server is configured to complete the payment based on the payment processing request.

[0067] The mobile terminal can generate a payment processing request based on the payment information provided by the user and send it to the server, so that the server can complete the payment transaction based on the received payment processing request. The payment processing request can include payment information such as the transaction party, transaction amount, and transaction method, so that the server can complete the payment for both parties. In actual applications, the payment method or transaction method can include a payment account provided by a financial institution, such as a bank card account at a bank; a payment account of a third-party payment application, such as the payment account corresponding to the second transaction party in a third-party payment application; and payment accounts of other users associated with the second transaction party, such as family number payment.

[0068] It should be understood that the order of some steps in the methods described in one or more embodiments of this specification can be interchanged according to actual needs, or some steps can be omitted or deleted. For example, to further improve payment efficiency, if the tag information of the NFC tag contains payment information, such as the first transaction party has written information such as the transaction amount or order number into the tag information of the NFC tag according to actual needs, the above steps 206 and 208 can be omitted, and the payment process can be triggered based on the tag information, and a payment request can be sent to the server so that the server can process the payment request and complete the payment.

[0069] In the method shown in Figure 2, the mobile terminal can obtain the payment link information in the NFC tag through near-field communication. Based on this information, the mobile terminal can display a payment page, and the user can complete the payment by entering the payment information such as the payment amount on the payment page. This eliminates the need for the user to find the payment application and then perform the corresponding payment operation in the payment application. For example, in a scenario where a payment code needs to be scanned, the user does not need to find the payment application and then select the scan code function in the payment application. In the embodiments of this specification, the mobile terminal can display the payment page based on the information in the NFC tag, which can simplify user operations and improve the user experience.

[0070] Common NFC payment solutions, such as NFC card payments on buses and subways, simulate mobile devices like phones as NFC cards. Using NFC near-field communication technology, the card information is sent to a payment device, such as a bus card reader or subway gate, which then completes the payment. This requires the installation of payment devices at specific locations, which are equivalent to NFC card readers, resulting in high costs.

[0071] In actual applications, most mobile terminals have near-field communication functions and are equipped with near-field communication modules. In the embodiments of this specification, the mobile terminal is equivalent to an NFC card reader. The NFC tag can be a passive electronic tag, which can simplify the payment process with the help of the functions of the mobile terminal itself. In addition, the NFC tag is small in size and can be conveniently placed at the location where payment is required. There is no need to modify or over-modify existing hardware equipment. It is low in cost and can be applied in a variety of occasions, with a wider range of applications.

[0072] In addition, in the embodiments of this specification, near-field communication is used to enable the mobile terminal to display a payment page when it is close to an NFC tag carrying information used for payment. The user provides payment information on the payment page, and the payment page can be the same as the payment page presented to the user by scanning the code through the terminal. For the server in the payment request, the existing processing link can be used to process the payment request without building a new business processing link, which can also reduce the workload of developers and the server overhead, which is conducive to accelerating the implementation of the NFC communication payment method.

[0073] Based on the method of FIG2 , the examples of this specification also provide some specific implementation plans of the method, which are described below.

[0074] In actual applications, payment can be made through a payment application with a payment function in the mobile terminal. Optionally, the label information in the embodiment of this specification may include instruction information for starting the payment application; the above-mentioned display of the payment page corresponding to the first transaction party based on the payment link information, which includes the user information of the first transaction party, may specifically include: based on the instruction information, starting the payment application in the mobile terminal; based on the started payment application, displaying the payment page corresponding to the first transaction party.

[0075] The payment application can represent a terminal application with a payment function, wherein, after the mobile terminal obtains the instruction information for starting the payment application in the tag information through near-field communication, it can start the payment application in the terminal, and then display the payment page based on the started payment application. The payment page can represent the application page of the payment application.

[0076] The instruction message may include the application identifier of the payment application to be launched. After reading the instruction message, the terminal can determine the payment application based on the application identifier. In actual applications, it can also determine whether the payment application exists in the terminal. If not, a prompt message indicating that payment cannot be made can be generated, or a prompt message prompting the user to download and install the payment application can be generated. If the payment application exists, the payment application can be launched.

[0077] In actual applications, the NFC tag information may include information for indicating the business being processed, for example, information for displaying a payment page, and the mobile terminal may display the payment page based on the tag information. Optionally, in the embodiments of this specification, the tag information may include request identification information for requesting to obtain payment page information; the display of the payment page based on the payment application being started may specifically include: the payment application in the started state generates a payment page information acquisition request based on the request identification information; sends the payment page acquisition request to the server; obtains the payment page information containing the user information of the first transaction party generated by the server based on the payment page acquisition request; and displays the payment page containing the user information of the first transaction party based on the payment page information.

[0078] The tag information may include information about the first transaction party, such as merchant identification information, and may also include token information for requesting the server to provide the information required for the payment page. The mobile terminal or the activated payment application may send a request to the server for obtaining the payment page information. The server may generate the payment page information based on the user information of the first transaction party and feed it back to the mobile terminal. The mobile terminal may render and display the payment page based on the obtained payment page information. In the implementation application, the payment page information may also be generated by the mobile terminal. For example, the mobile terminal may include a page template for the payment page. If the NFC tag information includes the name, nickname, account identification, and other information of the first transaction party, the mobile terminal may add the information of the first transaction party to the page template. It may also determine the payment method used by the user logged in to the mobile terminal, add the payment method information to the page template, and generate and display the payment page.

[0079] In actual applications, the payment page may include information about the first party to the transaction, such as the merchant name, the payee's nickname, partial account information, the payee's name, etc. It may also include an area for entering or selecting the payment amount, and controls such as a submit control and a payment confirmation control for confirming the payment information. In actual applications, after the user submits the payment information, a payment password input page may also be displayed so that the user can enter the password to make the payment.

[0080] To ensure payment security, the transaction parties may also be verified in the embodiments of this specification. Optionally, the tag information in the embodiments of this specification may include user identification information of the first transaction party; for example, payee information, merchant information, etc. The method in the embodiments of this specification may further include: based on the user identification information, determining whether the first transaction party has transaction authority, and obtaining a determination result; and displaying the payment page containing the user information of the first transaction party may specifically include: if the determination result indicates that the first transaction party has transaction authority, displaying the payment page containing the user information of the first transaction party.

[0081] In practical applications, the legality and compliance of transaction parties can be verified. A server with verification capabilities can store information about transaction parties with transaction authority, such as a list of transaction parties with transaction authority. This server can determine whether the first transaction party is a transaction party with transaction authority, or whether the first transaction party is included in the list of transaction parties with transaction authority. If so, it can be determined that the first transaction party has transaction authority. The compliance of the transaction parties can also be verified by a third party. The specific verification method is not specifically limited here.

[0082] In the prior art, payment codes such as QR codes are usually placed at the cash register or pasted in a place convenient for users to pay, or they can be carried by merchants. In the embodiments of this specification, the NFC tag can be carried on an existing payment code card, for example, pasted or placed behind or on the side of the QR code image, etc., which does not affect the recognition of the QR code, and an independent carrier can be set to prevent the NFC tag. Optionally, the NFC tag described in the embodiments of this specification can be located in a carrier containing the payment code of the first transaction party, or can be located in a carrier that does not contain the payment code of the first transaction party. The payment code can be understood as a scannable payment code image in the form of a common QR code or other image.

[0083] Due to the small size of NFC tags, in the embodiments of this specification, NFC tags can be placed in any convenient location for users to pay. For example, they can be placed on the back of the payment code carrier or on the front without affecting the payment code. The user can enter the payment process and display the payment page by bringing the mobile terminal close to or holding it close to the carrier. An NFC payment card can also be set up. The payment card can contain an NFC payment logo. The user can also enter the payment process and display the payment page by bringing the mobile terminal close to or holding it close to the payment card.

[0084] In actual applications, before making a payment, the user can use the mobile terminal to handle other business, such as watching videos, playing games, reading electronic content, reading news information, communicating with other users using instant messaging, etc. In the embodiment of this specification, the user does not need to exit the current application being used before making a payment, and can also make a payment. Optionally, in the embodiment of this specification, when the tag information of the NFC tag containing the payment link information is obtained, the mobile terminal is displaying the application page of the second application, and the display corresponds to the payment page of the first transaction party, which can specifically include: displaying the payment page superimposed on the upper layer of the application page of the second application.

[0085] In actual application, the payment page may be displayed in a partial area or the entire area of ​​the application page of the second application.

[0086] Optionally, the method in the embodiment of this specification may further include: obtaining an exit operation of the second transaction party on the payment page; and switching to an application page of the second application for display based on the exit operation.

[0087] The payment page may include controls for exiting the payment page, such as a payment confirmation control and a close control. The user can exit the payment page by operating the controls or by performing preset operations on the payment page, such as swiping left, right, up, or down in preset directions. In the embodiments of this specification, after exiting the payment page, the application page displayed on the terminal before payment can continue to be displayed, further improving the user experience.

[0088] In the embodiments of this specification, after the user submits payment information or enters a payment password, a page displaying the transaction results may also be displayed. The transaction results page may be overlaid on top of all or part of the second application's application page. The transaction results page may also include controls for exiting or closing the page. After exiting or closing the page, the second application's application page may continue to be displayed.

[0089] In actual applications, after the mobile terminal obtains the information indicating the transaction result, it can also generate prompt information indicating the transaction result, such as a short message, a prompt tone, etc., and can also display the prompt information based on the application page of the second application.

[0090] In actual applications, when a merchant allows multiple payment applications for payment, a page for the user to select a payment application may be displayed after the mobile terminal is brought close to or in proximity to the NFC tag, and the user may select a payment application to make the payment. Optionally, the tag information described in the embodiments of this specification may include first trigger information, which is used to trigger the mobile terminal to determine a terminal application with a payment function in the mobile terminal and generate an application selection page; the method in the embodiments of this specification may also include: determining a terminal application with a payment function in the mobile terminal in response to the first trigger information; generating an application selection page based on the terminal application with a payment function; and displaying the application selection page.

[0091] The application selection page may include application identifiers of terminal applications with payment functions, such as icons, etc.; the terminal applications may be sorted and displayed in order of their launch time, with the terminal applications most recently used by the user being placed at the front.

[0092] Optionally, after the above-mentioned display of the application selection page in the embodiment of this specification, it may also include: obtaining the target terminal application selected by the second transaction party from the application selection page; displaying the payment page containing the transaction information of the first transaction party based on the payment link information may specifically include: using the target terminal application to access the payment link information; and displaying the payment page containing the transaction information of the first transaction party within the target terminal application.

[0093] Similar to the display of the payment page or transaction results page described above, if the mobile terminal is currently using a second application before acquiring the tag information from the NFC tag, the application selection page can be displayed as an overlay on all or part of the second application's application page. It can also be used to exit or close the page, or to perform a preset operation, so that the second application's application page can continue to be displayed after exiting or closing the page.

[0094] In actual applications, payment process-related pages such as the payment page, transaction result page, and application selection page may be displayed above the application page of the second application in a semi-transparent or non-transparent manner.

[0095] In actual applications, the mobile terminal may have a near-field communication function and may also have components such as a camera for scanning payment codes. In order to avoid disturbing the user and minimize resource consumption, if the user has already turned on the code scanning function, for example, has entered the code scanning function of a payment application and is ready to scan the payment code through the terminal to make a payment, the NFC payment process may not be started. Optionally, in the embodiment of this specification, before the above-mentioned acquisition of the tag information of the NFC tag that responds to the electromagnetic signal, it may include: determining whether the mobile terminal has started the code scanning application for scanning the payment code image; the acquisition of the tag information of the NFC tag that responds to the electromagnetic signal may specifically include: if it is not started, then acquiring the tag information of the NFC tag that responds to the electromagnetic signal.

[0096] In actual applications, if the mobile terminal has started a code scanning application for scanning the payment code image, for example, the user has clicked "Scan" or other controls for scanning codes in the payment application, the camera of the mobile terminal is in the started state, and it is no longer necessary to read the information in the NFC tag or execute the process triggered by the information in the NFC tag.

[0097] It is understandable that the method of triggering the payment process through near-field communication in the embodiments of this specification needs to be based on user authorization. For example, if the user agrees to enable the NFC payment method, user information can be obtained and used for payment within the scope of user authorization.

[0098] To more clearly illustrate a near-field communication-based payment method provided in the embodiments of this specification, Figure 3 is a swim-lane diagram of a near-field communication-based payment method provided in the embodiments of this specification. As shown in Figure 3, the solution may include an NFC information transmission phase and a payment processing phase, specifically, steps 302 through 322.

[0099] Step 302: A mobile terminal with near field communication (NFC) functionality sends an electromagnetic signal to trigger an NFC tag. The mobile terminal may enable the NFC functionality to send an electromagnetic signal to trigger an NFC tag or chip within a preset distance to establish near field communication.

[0100] Step 304: When the mobile terminal approaches or is close to the NFC tag, near field communication can be established with the NFC tag, and the NFC tag can send tag information to the mobile terminal.

[0101] Step 306: The mobile terminal may obtain tag information from the NFC tag that responds to the electromagnetic signal; the tag information may include payment link information. The tag information may include identification information of the first transaction party, such as a user ID, and payment link information for triggering the payment process. This link information may be used to launch a payment application on the mobile terminal and display a payment page.

[0102] Step 308: Based on the payment link information, a payment page information acquisition request is generated and sent to the server. The payment link information may include link information for launching a payment application. The mobile terminal may launch the corresponding payment application and then, based on the payment application, send a payment page information acquisition request to the server. This request may include identification information of the first transaction party, such as merchant identification information, as well as the terminal identification of the mobile terminal or the application user identification of the user logged into the payment application on the mobile terminal, so that the server can identify the two parties to the transaction and generate the payment page information.

[0103] Step 310: Based on the acquisition request sent by the mobile terminal, the server may generate payment page information and feed it back to the mobile terminal.

[0104] Step 312: The mobile terminal may display a payment page based on the acquired payment page information. The payment page may include an area for the user to fill in payment information such as the payment amount and payment method.

[0105] Step 314: The user fills in the payment information on the payment page, and the mobile terminal can obtain the payment information provided by the user.

[0106] Step 316: The mobile terminal may generate a payment processing request based on the payment information provided by the user, and send it to the server, requesting the server to process the transaction.

[0107] Step 318: The server may obtain the payment processing request sent by the mobile terminal, and process the transaction based on the transaction information contained in or corresponding to the payment processing request, such as the information of the transaction parties, the transaction amount, and other transaction information.

[0108] Step 320: The server may also generate a transaction result and feed it back to the mobile terminal.

[0109] Step 322: The mobile terminal may display transaction result information based on the transaction result fed back by the server.

[0110] In the prior art, users can access the payment page by scanning a code at a terminal. In the embodiments of this specification, the payment page can be invoked through NFC short-range communication, which can simplify user operations. Simply put, the NFC tag in the embodiments of this specification can contain the information used for transaction carried in the payment code in the prior art, such as the merchant identification and the token that triggers the payment process.

[0111] In existing payment methods, mobile terminals can also be scanned objects. For example, a payment code can be presented on a mobile terminal and scanned by a payment device to complete the payment. In existing methods, users must open the payment app, find the payment code, and then display the payment code. If the user is currently using another app before making a payment, they must exit that app and then find the payment app to make the payment, requiring a number of steps. To simplify user operations and improve the user experience, the embodiments of this specification also provide an alternative payment method based on near-field communication.

[0112] Figure 4 is a schematic diagram of an application scenario of a payment method based on near-field communication in an embodiment of this specification. As shown in Figure 4, the solution may include a mobile terminal 1 with near-field communication functionality, an NFC tag 2 carrying tag information, a payment device 3 associated with the NFC tag, and a server 4 for handling payment transactions. When the mobile terminal 1 approaches the NFC tag 2 and reaches a certain distance, the NFC tag can be triggered to obtain the tag information contained in the NFC tag 2. The tag information may include information for triggering the payment process. Based on the obtained tag information, the mobile terminal 1 can send a request to obtain transaction identification information to the server 4. The server 4 can feedback transaction identification information representing the user payment account information in the mobile terminal to the mobile terminal 1. The mobile terminal 1 can send the transaction identification information to the payment device 3 via NFC communication. The server 4 can also send the transaction identification information to the payment device 3 via network transmission. After obtaining the transaction identification information, the payment device 3 can send a payment processing request to the server 4. The server 4 can process the payment transaction between the mobile terminal user and the user to whom the payment device belongs. Based on the above scenario diagram, Figure 5 is a flow diagram of a payment method based on near-field communication provided in an embodiment of this specification. From a program perspective, the execution entity of the process can be a program or application client installed in an application server or terminal application.

[0113] As shown in FIG. 5 , the process may include the following steps 502 to 508 .

[0114] Step 502: A mobile terminal with a near field communication function sends an electromagnetic signal for triggering an NFC tag.

[0115] The principles are similar to those of the above-mentioned embodiments, and the mobile terminal may include portable, wearable and other movable terminals, such as mobile phones, smart watches and the like. Near field communication, also known as short-range wireless communication, is a short-range high-frequency wireless communication technology that allows contactless point-to-point data transmission and exchange between electronic devices. In the embodiments of this specification, the NFC tag may be a passive electronic tag or electronic chip, which can generate an induction signal with the mobile device and transmit data when a mobile device with near-field communication function is close. After turning on the near-field communication function, the mobile device can send an electromagnetic signal, which can activate an NFC tag within a preset distance to perform data transmission. The specific NFC communication process can be referred to the existing NFC communication technology and will not be described here.

[0116] Step 504: Acquire tag information of the NFC tag that responds to the electromagnetic signal; the tag information is used to trigger the payment process.

[0117] The tag information may include information for triggering the payment process, such as information for starting the payment application, merchant information, etc. The mobile terminal may obtain the information in the NFC tag through near field communication and trigger the payment process.

[0118] Step 506: Based on the tag information, obtain transaction identification information for representing the user payment account information in the mobile terminal.

[0119] The transaction identification information can be used to identify the user's payment account in the mobile terminal. If the tag information contained in the NFC tag indicates a payment process for making a payment, the account can be the payment account. If the tag information contained in the NFC tag indicates a payment process for receiving a payment, the account can be the receiving account. This is not specifically limited here. In actual applications, users can use a terminal application with payment functionality on the mobile terminal to make payments, and the user's payment account can also be the user account logged into the terminal application.

[0120] Step 508: Send the transaction identification information to the payment device associated with the NFC tag, and the payment device is used to execute the payment process according to the transaction identification information.

[0121] A payment device can be understood as a device capable of sending transaction requests to a server that processes transactions. It may be equipped with a program or terminal application for executing the payment process. In practical applications, a payment device can represent the device of the other party conducting a transaction with the user of a mobile terminal, specifically a cash register, self-service checkout device, etc. The payment device may include an NFC tag, or the NFC tag may include a device identifier for the payment device, establishing a corresponding relationship between the payment device and the NFC tag. In practical applications, the payment device may also send a payment processing request to the server that processes the payment request according to the payment process, so that the server can complete the payment transaction between the two parties.

[0122] In the scenario of paying via a mobile device, the mobile terminal can represent the payee's device, and the payment device can represent the payee's device. In the scenario of receiving money via a mobile device, the mobile terminal can represent the payee's device, and the payment device can represent the payee's device.

[0123] It should be understood that the order of some steps in the methods described in one or more embodiments of this specification can be interchanged according to actual needs, or some steps can be omitted or deleted.

[0124] In the method shown in Figure 5, the mobile terminal uses near-field communication to retrieve the tag information from the NFC tag used to trigger the payment process, obtain the transaction identification information, and transmit it to the payment device to initiate payment. This eliminates the need for the user to find the payment application and then perform the corresponding payment operation within the payment application. For example, in a scenario where a payment code is required to be scanned by the payment device for payment, the user does not need to find the payment application and then select the payment code within the payment application to display it. In the embodiments of this specification, the mobile terminal can transmit the transaction identification information used for payment to the payment device based on the information in the NFC tag, simplifying user operations and improving the user experience.

[0125] To ensure payment security, the mobile terminal may request the server to generate transaction identification information based on actual transaction requirements. The transaction identification information may vary for different payment processes. Optionally, in the embodiments of this specification, obtaining transaction identification information representing the user payment account information in the mobile terminal based on the tag information may include: sending a payment information acquisition request containing the user identification information in the mobile terminal to the server; and obtaining the transaction identification information generated by the server based on the user identification information.

[0126] The user identification information can be a user ID, a mobile terminal device identifier, a user application identifier in a terminal application, or other identification information that can be used to identify the user's payment account. The server can determine the user's payment account based on the user identification information and generate transaction identification information corresponding to the user's payment account so that it can subsequently process payment transactions using the user's payment account based on the transaction identification information. In actual applications, the transaction identification information can also be a string of characters such as a payment code or transaction order number, and the server can process transactions between the two parties based on the transaction identification information.

[0127] In the embodiments of this specification, the transaction identification information may be sent to the payment device via near field communication (NFC) or via a network. As an implementation, the sending of the transaction identification information to the payment device in the embodiments of this specification may specifically include sending the transaction identification information to the payment device via near field communication (NFC).

[0128] The payment device may have NFC functionality, such as an NFC module that can receive data sent via near-field communication. The mobile terminal may transmit transaction identification information to the payment device via near-field communication. Transmitting the transaction identification information to the payment device via near-field communication may specifically include: writing the transaction identification information into the NFC tag; and transmitting the transaction identification information back to the payment device via near-field communication via the NFC tag.

[0129] Here, the channel mode of the NFC tag can be adopted to write the transaction identification information into the NFC tag and then directly transmit it to the payment device. The transaction identification information may not be stored in the NFC tag.

[0130] As another implementation manner, the tag information described in the embodiment of this specification may include the device identification of the payment device; sending the transaction identification information to the payment device may specifically include: sending a payment request including the device identification to a server; the server is used to generate the transaction identification information and send the transaction identification information to the payment device based on the device identification.

[0131] In the embodiments of this specification, the server can generate transaction identification information and send this information to the payment device. In actual applications, near-field communication requires a relatively short distance between the mobile terminal and the NFC tag, and data transmission takes a certain amount of time, which may be 1 second, 2 seconds, 3 seconds, etc. If the distance between the mobile terminal and the NFC tag is within a preset range for a short period of time, the transaction identification information may not be transmitted via near-field communication. To ensure that the transaction can proceed normally, the transaction identification information can also be sent to the payment device through the server.

[0132] In practical applications, both transmission methods can be used simultaneously or simultaneously, allowing the payment device to obtain transaction identification information through either method. Because the transaction identification information transmitted by both transmission methods is identical and can be used only once, the entire payment system is guaranteed to be idempotent, thereby ensuring the normal execution of transactions. If the payment device does not have the ability to obtain information transmitted via near-field communication, the transaction identification information can also be sent to the payment device through the service.

[0133] Similar to the above embodiment, the tag information in this embodiment may include first link information for starting the payment application in the mobile terminal; the method in the embodiment of this specification may also include: starting the payment application based on the first link information; the acquisition of transaction identification information for representing the user payment account information in the mobile terminal may specifically include: acquiring the transaction identification information based on the started payment application.

[0134] The tag information may include the identifier of a designated payment application. After the mobile terminal obtains the tag information, it may launch the designated payment application and make a payment based on the payment application. The transaction identification information may be the transaction identification information that the payment application sends a request to the server and the server feeds back to the payment application.

[0135] To enhance the user's sense of security regarding payment, embodiments of this specification may also generate a prompt message to inform the user that the payment application has been launched on the mobile terminal and that payment is being made using the payment application. Optionally, after launching the payment application, embodiments of this specification may further include: displaying a prompt message indicating that the payment application has been launched. Specifically, the prompt message may include vibration, sound, text, images, or other forms of prompts, and may also include a launch page for the payment application, so that the user can perceive that the payment application has been launched.

[0136] In actual applications, the prompt information can be displayed in the upper layer or partial area of ​​the page currently being displayed on the mobile terminal. The user can also perform a preset operation to close the prompt information, and the terminal can continue to display the currently displayed page.

[0137] In actual applications, the payment application can also be started in the background of the mobile terminal, and the user may not be aware of it, which can reduce disturbance to the user. For example, if the user is using other applications in the mobile terminal, the user's use of the application can be avoided from being interrupted, thereby reducing disturbance to the user.

[0138] In the embodiment of this specification, a transaction result page may also be displayed so that the user can understand the payment status. Optionally, the method in the embodiment of this specification may also include: obtaining transaction result information fed back by the server; and displaying a transaction result page based on the transaction result information.

[0139] The transaction result information may be the result information obtained by the server processing the payment processing request including the transaction identification information sent by the payment device, and may be information indicating a successful transaction or information indicating a failed transaction. The process by which the server processes the payment processing request may be the same as the existing process and will not be described in detail here.

[0140] Similar to the above embodiment, in actual applications, before making a payment, the user can use the mobile terminal to handle other business, such as watching videos, playing games, reading electronic content, reading news information, communicating with other users using instant messaging, etc. In the embodiment of this specification, the user does not need to exit the current application being used before payment to make a payment. Optionally, in the embodiment of this specification, if the tag information of the NFC tag is obtained, the mobile terminal is displaying the application page of the second application, and the display of the transaction result page may specifically include: displaying the transaction result page in an overlay on the application page of the second application.

[0141] In actual applications, the transaction result page may be displayed in a partial area or the entire area of ​​the application page of the second application.

[0142] Optionally, the method in the embodiment of this specification may further include: obtaining an exit operation on the transaction result page; and switching to the application page of the second application for display based on the exit operation.

[0143] Similar to the transaction results page in the above-mentioned embodiment, the transaction results page in this embodiment may include controls for indicating an exit, such as a confirmation control and a close control. The user can exit the payment page by operating these controls, or by performing a preset operation on the page, such as swiping left, right, up, or down in a preset direction. After exiting the transaction results page in the embodiments of this specification, the application page displayed on the terminal before payment can continue to be displayed, further improving the user experience.

[0144] In actual applications, if the payment device has a code scanning function, it can scan the payment code presented by the mobile terminal, such as the payment code. In the embodiments of this specification, the mobile terminal can also display the payment code page based on near-field communication, which can also simplify the user's operation of first opening the payment application and then opening the payment code page. Optionally, the method in the embodiments of this specification can also include: generating a payment code image based on the transaction identification information; displaying the payment code image; and sending the transaction identification information to the payment device, which can specifically include: sending the transaction identification information to the payment device with code scanning function via the payment code image.

[0145] In the embodiments of this specification, the payment device may include a POS machine, a barcode scanning box, a barcode scanning gun, or other devices with a barcode scanning function. In this embodiment, the payment identification information can be obtained based on the tag information in the NFC tag, and then a payment code image can be generated based on the payment identification information. The payment device can scan the payment code image to make a payment. The payment identification information can be simply understood as the information contained in the existing payment code for making a payment, such as the payment code number in the payment code. The payment code image generated in the example of this specification can be the same as or have the same function as the payment code image generated by the payment code control in the mobile terminal. The payment device can process the payment business according to the existing payment process by scanning the code image.

[0146] In the embodiments of this specification, the payment process executed by the payment device after obtaining the transaction identification information can be consistent with the existing payment process executed after obtaining the transaction identification information by scanning a code. The existing process can be used for business processing without building a new processing process, which can save resources and reduce the workload of developers.

[0147] To more clearly illustrate a near-field communication-based payment method provided in the embodiments of this specification, Figure 6 is a swim-lane diagram of a near-field communication-based payment method provided in the embodiments of this specification. As shown in Figure 6, the method may include an NFC information transmission phase and a payment processing phase, specifically including steps 602 to 618.

[0148] Step 602: A mobile terminal with near field communication (NFC) functionality sends an electromagnetic signal to trigger an NFC tag. The mobile terminal may enable the NFC functionality to send an electromagnetic signal to trigger an NFC tag or chip within a preset distance to establish near field communication.

[0149] Step 604: When the mobile terminal approaches or is brought close to the NFC tag, near-field communication (NFC) is established between the mobile terminal and the tag. The NFC tag then transmits tag information to the mobile terminal. This tag information may include information used to trigger the payment process. This example uses the NFC tag located within a payment device. In practice, the NFC tag can also be deployed separately from the payment device, without specific limitation.

[0150] Step 606: The mobile terminal may obtain tag information of the NFC tag that responds to the electromagnetic signal. The tag information may include identification information of the first transaction party, such as user ID, merchant ID, merchant authorization information, etc., and may also include information for launching a payment application in the mobile terminal.

[0151] Step 608: The mobile terminal obtains transaction identification information representing the user payment account information in the mobile terminal based on the tag information. The transaction identification information may be generated by the server based on the user information of the mobile terminal and fed back to the mobile terminal.

[0152] Step 610: Send the transaction identification information to the payment device. The transaction identification information can be sent to the payment device using one or both of the two methods described above. Step 612: The payment device can generate a transaction processing request based on the transaction identification information and send it to the server. The transaction processing request can include the payment device identifier or the identifier of the user identified by the payment device, as well as information such as the transaction amount and the recipient account.

[0153] Step 614: The server receives the transaction processing request sent by the payment device and may complete the transaction between the corresponding parties. Step 616: The server may also generate a transaction result and feedback it to the mobile terminal and the payment device. Step 618: The mobile terminal may display transaction result information based on the transaction result feedback from the server. The payment device may also display information indicating the transaction result.

[0154] In this embodiment, the tag information may also include a payment device identifier or the identifier of the merchant to which the payment device belongs. The payment device may also be verified based on this identifier to determine whether the payment device has transaction authorization. Only if the payment device has transaction authorization can the transaction identification information be obtained. The specific verification process may be the same or similar to that in the above embodiment and will not be further elaborated here.

[0155] Based on the same idea, FIG7 is a flowchart of a payment method based on near field communication provided in an embodiment of this specification. As shown in FIG7 , the solution may include the following steps 702 to 714 .

[0156] Step 702: The mobile terminal obtains tag information of the NFC tag associated with the payment device.

[0157] The mobile terminal may be a mobile terminal with near-field communication capabilities, and the tag information may include information for triggering the payment process. In actual applications, the mobile terminal may be placed in proximity to an NFC tag, such as a payment device with an NFC tag, to obtain the tag information of the NFC tag. The NFC tag may be associated with the payment device, for example, it may be located in the payment device, or the NFC tag may be deployed separately from the payment device. The payment device may represent a device with payment processing capabilities, such as a POS machine, a counter, a cash register system associated with a cash register system, a self-service payment device, etc., or it may be another mobile terminal with NFC capabilities, such as a mobile phone or a smartwatch. The specific form of the payment device is not specifically limited here, and the payment device may also be represented as an NFC device, a device with an NFC tag, or a device with NFC capabilities.

[0158] In this specification, a mobile terminal can be used as a card reader. When the NFC switch is turned on, it will continuously send LPCD signals, or a mixture of LPCD and normal card search. When the mobile terminal is close to the NFC tag, such as by tapping or placing it against a payment device, the tag coil in the NFC tag will affect the LPCD signal of the mobile terminal, either in amplitude or phase. The mobile terminal can determine the presence of a tag based on this effect and then initiate a query, entering into an interaction process. Specifically, this can be a command interaction or data interaction. For example, the mobile terminal can obtain information from the NFC tag. For detailed NFC information, please refer to the relevant technology and will not be detailed here.

[0159] Step 704: Based on the tag information, start the payment application in the mobile terminal.

[0160] The tag information may include information for starting the payment application, specifically, an identifier representing the payment application, such as the package name of the payment application. The mobile terminal can start the payment application based on the identifier. In actual applications, the OS (Opening System) of the mobile terminal can call up the corresponding terminal application app according to the application package name, and can also provide at least part of the information in the obtained tag information, such as at least part of the URL, to the terminal application so that the terminal application executes the corresponding process. For example, the tag information can also include information for jumping to a page. After the mobile terminal starts the payment application, the payment application can obtain the URL for page jumping, and the payment application can make the corresponding page jump according to the URL. For another example, the tag information can also include a service identifier, such as a payment service. After the payment application is started in the mobile terminal, the payment application can execute the corresponding processing flow according to the service identifier, such as sending a payment request to the server, or triggering the server's payment processing flow, or obtaining information fed back by the server, etc.

[0161] Step 706: Based on the activated payment application, a payment processing request is sent to the server.

[0162] The mobile terminal can send a payment request to the server based on the activated payment application. This can also be understood as the payment application in the mobile terminal sending the payment request to the server. The payment request can include the identification information of the payment account used for payment in the mobile terminal. If the tag information includes payment information such as the payment amount, the payment request can also include such payment information. If the tag information includes information such as the device identifier of the payment device or the transaction party identifier of the party to which the payment device belongs, the payment request can also include such information.

[0163] Step 708: The server processes the payment service based on the payment processing request and feeds back payment result information.

[0164] In actual applications, the server can process payment services independently, or it can interact with other devices to complete payment services during the processing process. The specific processing process can be found in the introduction of the above embodiment and will not be repeated here.

[0165] Step 710: The mobile terminal may display a transaction result page based on the payment result information fed back by the server.

[0166] The transaction result page, which may also be referred to as the payment result page, may be a page used to display transaction result information or payment result information. It is understood that this embodiment and the above embodiment are based on the same technical concept, and some specific implementations of this embodiment may be the same as those in the above embodiment, which will not be repeated here.

[0167] In order to more clearly illustrate this embodiment and the payment method provided in the above embodiments, some specific implementation methods are also provided in this specification.

[0168] In order to improve the user experience and let the user know that the response is executed by the mobile terminal, a prompt message can be displayed in the mobile terminal before starting the payment application.

[0169] Optionally, as shown in Figure 7, step 704 may specifically include: step 7042: displaying a payment prompt page based on the tag information; step 7044: obtaining the user's first preset operation for the payment prompt page and generating a first confirmation message; step 7046: based on the first confirmation information, starting the payment application in the mobile terminal.

[0170] The tag information may include link information for displaying a payment prompt page, and the mobile terminal may display the payment prompt page by identifying the link information. Alternatively, the terminal browser may be used to access the link information to display the payment prompt page. The payment prompt page may include prompt information for using a payment application to make a payment. In actual applications, the mobile terminal's operating system may display the payment prompt page based on the page identifier or code corresponding to the payment prompt page contained in the link information, or may send a request for obtaining the payment prompt page to the mobile terminal's server, with the server then providing a response to the payment prompt page.

[0171] In the embodiments of this specification, the tag information acquired by the mobile terminal may include information for starting a payment application, and may also include information for displaying a page, or information for requesting a payment service feedback page from the server.

[0172] As an implementation method, the tag information may include identification information for starting the payment application, such as the application package name, and may also include link information for displaying the page, such as URL information. After obtaining the application identification, the mobile terminal system may pull up or start the corresponding payment application in the mobile terminal, and then provide the link information for displaying the page to the payment application, and then the payment application may display the page based on the link information.

[0173] As another embodiment, the tag information may include link information, such as a URL. This link information may include identification information of the payment application, such as the application package name. The link information URL may also include information for displaying a page, such as information for displaying a payment prompt page. The mobile terminal may launch or start the payment application based on this link information and open the corresponding page to display the page. Displaying the payment prompt page based on the tag information may specifically include: displaying the payment prompt page based on the link information.

[0174] If the mobile terminal is running iOS, the corresponding payment application can be launched based on the link information in the tag information, and a prompt page can be displayed to prompt the user to use the payment application to make a payment. If the mobile terminal is running Android, the corresponding payment application can be launched based on the application package name in the tag information, and then the link information for displaying the page contained in the tag information can be sent to the payment application. The payment application can generate the display page locally based on the link information or based on the server. In actual applications, the specific format of the tag information can also be set according to the operating system used by the mobile terminal so that the mobile terminal can accurately identify the tag information. For example, a universal tag information format can also be set so that different operating systems can accurately identify it.

[0175] The first preset operation can be a click, a slide, or an operation such as tilting, flipping, or shaking the mobile terminal. The first preset operation can also be a non-essential operation. For example, if the payment prompt page includes a control for canceling payment and the user does not operate the control within a preset time period, it can also indicate that the user agrees to use the payment application for payment. That is, after the preset time period, the mobile terminal can generate a first confirmation message. The operation method is not specifically limited here. The first confirmation message can indicate that the user agrees to use the payment application for payment. After the user agrees, the terminal can launch the payment application.

[0176] Figure 8 is a schematic diagram of a payment prompt page provided in an embodiment of this specification. As shown in Figure 8, payment prompt page 800 may include prompt information 802 prompting payment using payment application A. It may also include a confirmation control 804. If the user clicks confirmation control 804, it indicates that the user agrees to use payment application A for payment, and the terminal may launch payment application A.

[0177] If payment application a is not installed in the mobile terminal or is installed but the user has not registered to use it, the user can click the confirmation control 802 to jump to the download page of the client for downloading payment application a or the page for registering to use payment application a, so that after the user registers payment application a, he can use payment application a to make payments.

[0178] Optionally, the payment prompt page may further include a download control 806 for downloading the client of payment application A. If the user clicks the download control 806, the mobile terminal may jump to display a download page for downloading the client of payment application A. In actual application, the mobile terminal may also determine whether payment application A is already installed on the mobile terminal. If it is already installed, the payment prompt page may not display the download control 806.

[0179] The payment prompt page may also include prompts prompting the user to use NFC to pay. The payment prompt page may occupy the entire area of ​​the terminal display page, may be located in a partial area of ​​the terminal display page, such as the lower, upper, or middle area, or may be folded. Figure 8 is only an illustration, and the specific form of the payment prompt page is not limited here.

[0180] In step 2, the payment application in the mobile terminal can be activated by, for example, clicking a confirmation control on the payment prompt page. It is understood that in actual applications, the payment prompt page may not be displayed, for example, if payment security requirements are met or if the user has authorized the payment.

[0181] To enhance the user experience, the mobile terminal in the payment method provided in the embodiments of this specification may also display a page for the user to confirm payment information, so that the user can clearly understand the payment status. Optionally, as shown in Figure 7, before displaying the transaction results page, the embodiments of this specification may also include: Step 712: Displaying a payment page containing payment information; Step 714: Obtaining second confirmation information generated based on a second preset operation performed by the user on the payment page.

[0182] The payment information may be payment-related information, such as the transaction amount, transaction party information, transaction method, or payment method. The second preset operation may include a substantive operation performed on the payment page, such as clicking or sliding a control on the page, flipping or tilting the mobile terminal, etc., or may include a non-substantive operation performed on the payment page, such as not clicking a control on the payment page indicating payment cancellation within a preset time period.

[0183] Payment information can be included in an NFC tag. For example, a merchant can set the payment amount through a payment device, such as a cashier setting the amount at a POS machine or cash register. Alternatively, the amount can be calculated using a pre-set amount calculation program, such as an automatic payment device or vending machine. The amount required for the transaction can be determined by a computer program and then set in the NFC tag. The tag information obtained by the mobile terminal can include the payment information. Payment information can also be set by the user of the mobile terminal. The tag information can include a page identifier for the payment page. After launching the payment application, the payment application can obtain the payment page from the server based on the page identifier or generate the payment page using the payment application client program already installed in the terminal.

[0184] Figure 9 is a schematic diagram of a payment page provided in an embodiment of this specification. As shown in Figure 9, the payment page may include an area 902 for displaying payment information, which may specifically display payment amount information, and may also display information such as payment method, transaction party, transaction time, etc. The payment page may also include an operation control 904. If the user clicks on the control, it may indicate that the user agrees to make the payment, and the mobile terminal may generate a confirmation message. In actual applications, the operation control may be a control for payment confirmation or a control for canceling the payment. If the user does not click on the control indicating cancellation of payment within a preset time period, it may also indicate that the user agrees to make the payment, and the mobile terminal may also generate a confirmation message for subsequent processes. As shown in Figure 9, the payment page may also include descriptive information 906 for NFC payment, which helps users understand the advantages or usage methods of NFC payment.

[0185] It is understood that FIG9 is only an example. In actual application, the specific display content and style of the payment page can be set according to actual needs, and no specific limitation is made here. The payment page may not be displayed if the user authorizes or meets security requirements.

[0186] The second confirmation information may indicate that the user has confirmed the payment information and agreed to make the payment. As an implementation method, the second information may be used to trigger the sending of a payment processing request. The above-mentioned sending of the payment processing request to the server may specifically include: sending a payment processing request to the server based on the second confirmation information.

[0187] In an embodiment of this specification, the server can generate transaction identification information containing user payment account information in the mobile terminal based on the payment processing request, and can also send the transaction identification information to the payment device so that the payment device executes the payment process based on the transaction identification information to complete the payment.

[0188] As an implementation method, as shown in FIG7 , the above-mentioned step 708 may specifically include: step 7082: the server generates transaction identification information containing user payment account information in the mobile terminal based on the payment processing request; step 7084: sending the transaction identification information to the payment device; step 7086: the payment device executes the payment process based on the acquired transaction identification information.

[0189] In actual applications, the server may further execute step 7088: generating payment result information based on processing information generated by the payment execution process.

[0190] As another implementation, the server may send the transaction identification information to the mobile terminal, which then sends it to the payment device. Alternatively, the mobile terminal may execute the payment process based on the transaction identification information, such as initiating a payment request to the server, without the payment device needing to obtain the transaction identification information. The specific process can be found in the above embodiments and will not be further described here.

[0191] The transaction identification information may be a string of characters, specifically a string recognizable by a server for processing payment services and conforming to the payment rules of a payment application. For example, it may be a string beginning with 28, 25, 30, etc. The length of the string may be 16 to 24 characters, or other lengths as required. The specific form of the string is not specifically limited here. For details on the transaction identification information, please refer to the relevant description in the aforementioned embodiments.

[0192] The payment device can be a device associated with a server used to process payment services. The payment device can send a payment request containing transaction identification information to the server. The server can process the payment request. After the processing is completed, it can directly or indirectly send information indicating the completion of payment to the mobile terminal, and the payment result information can be displayed in the mobile terminal.

[0193] In this specification, the server can be a server corresponding to the payment application, or it can include a cash register system with a cash register function, such as a system associated with cash registers, cash register equipment, self-service payment equipment, and other equipment set up in supermarkets, shopping malls, etc. In actual applications, the cash register system can determine the user payment account used for the transaction based on the transaction identification information. If the cash register system is used for collecting money, the user payment account can represent the payment account. If the cash register system is used for payment, the user payment account can represent the collection account. The cash register system can also correspond to a transaction account. The cash register system can generate a transaction request based on the obtained user payment account and the transaction account corresponding to the cash register system and send it to the server. The server can process the transaction request, for example, it can deduct the corresponding resources from the user payment account and add them to the transaction account corresponding to the cash register system. After the processing is completed, the server can feedback the payment result information to the server. For the specific transaction processing process, please refer to the relevant technology. The cash register system can also process the transaction according to the existing processing process, which will not be described in detail here.

[0194] In practical applications, an NFC device server can also be set up to manage payment devices. The transaction identification information can also be sent from the server to the NFC device server, which then sends it to the payment device. The NFC device server and the above server can also be the same server, which is not specifically limited here.

[0195] In the embodiments of this specification, the payment process can be executed based on the payment device. As an implementation method, after starting the payment application, the mobile terminal can send a payment processing request to the server based on the started payment application. The server can process the payment processing request, generate transaction identification information and send it to the payment device. The second confirmation information generated based on the payment page can also serve as a trigger signal to trigger the payment device to execute the payment process based on the transaction identification information. Optionally, after the payment application in the mobile terminal is started as mentioned above, this specification can also include: displaying a payment page containing payment information; obtaining a second confirmation information generated based on the user's second preset operation on the payment page, so that the server sends a payment process trigger instruction to the payment device after the second confirmation information, and the payment device can execute the payment process based on the payment process trigger instruction and the acquired transaction identification information.

[0196] Among them, after obtaining the second confirmation information, the mobile terminal can send corresponding information indicating that the user confirms the payment to the server. The server can further send a payment process trigger instruction to the payment device. After obtaining the payment process trigger instruction, the payment device can execute the payment process based on the transaction identification information that has been obtained.

[0197] In the embodiments of this specification, after initiating a payment processing request, the mobile terminal can send a payment processing request to a server, which can then generate and send transaction identification information to the payment device. While the terminal is displaying the payment page, the server can generate and send the transaction identification information to the payment device. This allows the payment device to obtain the transaction identification information before the user performs a pre-set operation on the payment page. The payment device can temporarily store the transaction identification information. After the user performs the pre-set operation on the payment page, the payment device can execute the payment process based on the obtained transaction identification information, eliminating the need to wait for the server to send the transaction identification information, thereby improving payment efficiency.

[0198] Optionally, before displaying the payment page containing payment information in the embodiment of this specification, it may also include: judging whether the user of the mobile terminal meets the preset payment conditions based on the account information of the payment application in the mobile terminal; the preset payment conditions indicate the conditions for quick payment; the display of the payment page containing payment information may specifically include: if the user does not meet the preset payment conditions, then displaying the payment page containing payment information.

[0199] Among them, quick payment can refer to a payment method with fewer user operation steps, or a payment method that does not require the user to perform any operation. As described in the above embodiment, the mobile terminal can complete the payment through the NFC function and display the transaction result page. The entire payment process does not require the user to perform tedious operations.

[0200] If the user does not meet the preset payment conditions, i.e., cannot make a quick payment, a payment page may be displayed to the user so that the user can confirm the payment information. If the user meets the preset payment conditions, a transaction result page may be displayed. In other words, the mobile terminal may not display the payment page before displaying the transaction result page.

[0201] In the embodiments of this specification, whether a user meets preset payment conditions can be determined based on user characteristics. Optionally, the preset payment conditions include at least one of being authorized to use the express payment function, being a highly active user of the payment application, and being authorized to use the password-free payment function.

[0202] The "Express Pay" feature can represent a confirmation-free payment function. For example, the payment page and / or payment reminder page described above may not be displayed before the transaction result page, eliminating or reducing the need for the user to perform payment confirmation operations. This is an extremely fast payment method. In actual applications, users can enable the Express Pay feature in the relevant settings page of the payment application. If the user has authorized the use of the Express Pay feature and can determine that the user meets the preset payment conditions, when the user makes a payment via NFC, the payment page or the payment reminder page may not be displayed, and the transaction result page may be displayed directly.

[0203] Highly active users can be defined as those whose payment app usage activity is greater than or equal to a preset threshold. In practical applications, user activity can be calculated based on factors such as the duration and frequency of a user's login to the payment app. Alternatively, user activity can be determined based on how often a user scans a payment code or enters a payment code. For highly active users, a faster payment process can be provided, such as by not displaying the payment page.

[0204] In practice, for highly active users, the express payment feature can be enabled by default in their payment app, and corresponding payment processes can be provided to users based on the express payment feature's status. Password-free payment can mean that payment can be made without entering a password, and payment can be made using biometrics such as fingerprint, face, voiceprint, and iris as verification information.

[0205] As an implementation method, if the mobile terminal is an iOS system, the mobile terminal is placed close to the NFC tag, and after obtaining the tag information, a payment prompt page can be displayed. The payment prompt page can be displayed in the form of a Clips card. If the payment prompt page contains a control for indicating confirmation to start the payment application, the user can operate the control. As shown in Figure 8, the user clicks the "Open" control, which indicates that the user agrees to use the payment application for payment, and the mobile terminal can start the payment application. Based on the started payment application, the mobile terminal can send a payment processing request to the server, the server can process the payment service and return result information, and the mobile terminal can display the transaction result page. In actual applications, during the user's operation on the payment prompt page, the mobile terminal can collect the user's biometric information as payment verification information. If the user submits confirmation information based on the payment prompt page, it can also indicate that the user has confirmed the payment information, or the payment page may not be displayed. Of course, the payment page can also be displayed according to actual needs.

[0206] As an implementation method, if the mobile terminal is an Android system, after the mobile terminal is brought close to the NFC tag and the tag information is obtained, if the payment application has been installed in the mobile terminal, the payment application can be started and the payment page can be displayed. After the user confirms the information on the payment page, the transaction result page can be displayed. If the user has enabled the ultra-fast payment function, the payment page can be displayed after the payment application is started, and the transaction result page can be displayed after the mobile terminal obtains the payment result information. From the user's perspective, after the user uses the mobile terminal to bring the mobile terminal close to the NFC tag or payment device, the mobile terminal can start the payment application to display the payment page. In order to improve the user experience, a payment response page indicating that payment is in progress can also be displayed after the payment application is started, and then the transaction result page can be displayed. If the user has not enabled the ultra-fast payment function, the payment page can be displayed after the payment application is started, and then the transaction result page can be displayed. Similarly, the payment response page can be displayed before or after the payment page is displayed, and then the transaction result page can be displayed.

[0207] To improve user experience, the method in the embodiments of this specification may optionally further include: displaying a prompt message for prompting the user to set up the express payment function.

[0208] Specifically, the prompt information can be information prompting the user to turn on the ultra-fast payment function, or it can be information prompting the user to turn off the ultra-fast payment function. The prompt information can be displayed after the payment application is started, and can be displayed on payment-related pages displayed in the payment process, such as the payment page and the transaction result page, or it can be displayed independently. For example, after the payment application is started, before the payment page is displayed, a page including prompt information for prompting the user to set up the ultra-fast payment function can be displayed; for example, after the payment page is displayed, a page including prompt information for prompting the user to set up the ultra-fast payment function can be displayed; for example, after the transaction result page is displayed, a page including prompt information for prompting the user to set up the ultra-fast payment function can be displayed. This does not specifically limit the display method of the prompt information.

[0209] To avoid excessively disturbing the user, the method in the embodiment of this specification may also include: determining whether the number of times the prompt message for prompting the user to set up the ultra-fast payment function has been displayed within a preset time period is less than or equal to the preset number of times; if the number of times it has been displayed is less than or equal to the preset number of times, then displaying the prompt message for prompting the user to set up the ultra-fast payment function.

[0210] The preset time period and the preset number of times can be set according to actual needs. For example, it can be displayed at least once and at most four times in a day; for example, the first transaction of a day can be displayed, and then every four transactions thereafter. For example, it can be displayed eight times in a week, and so on.

[0211] Optionally, the method in the embodiment of this specification may also include: determining whether the user account of the payment application in the mobile terminal has enabled the ultra-fast payment function; the prompt information displayed to prompt the user to set up the ultra-fast payment function may specifically include: if the user account has not enabled the ultra-fast payment function, then displaying the first prompt information to prompt the user to enable the ultra-fast payment function.

[0212] In the embodiments of this specification, if the user has not enabled the express payment function, the mobile terminal may display a first prompt message prompting the user to enable the express payment function. If the user has already enabled the express payment function, the first prompt message prompting the user to enable the express payment function may not be displayed, thereby reducing disturbance to the user.

[0213] In order to further improve the user experience, optionally, before the above-mentioned display of the first prompt information for prompting the user to turn on the ultra-fast payment function, it may also include: determining whether the user account is a highly active user account; the display of the first prompt information for prompting the user to turn on the ultra-fast payment function may specifically include: if the user account is a highly active user account, then displaying the first prompt information for prompting the user to turn on the ultra-fast payment function.

[0214] A highly active user account may represent a user account with high activity. In an embodiment of the present specification, a first prompt message may be displayed for a highly active user account to prompt the user to enable the ultra-fast payment function, so that the first prompt message may be provided to users who have actual needs for the function with a greater probability.

[0215] Optionally, the above-mentioned prompt information displayed to prompt the user to set up the ultra-fast payment function may further include: if the ultra-fast payment function has been turned on in the user account, a second prompt information is displayed to prompt the user to turn off the ultra-fast payment function.

[0216] In the embodiment of this specification, if the user has already enabled the express payment function, the mobile terminal may display a second prompt message for prompting the user to disable the express payment function. If the user has not enabled the express payment function, the mobile terminal may not display the second prompt message.

[0217] In actual applications, before displaying the second prompt information, it is also possible to determine whether the user account is a highly active user account. If the user account is not a highly active user account, the second prompt information can be displayed to avoid disturbing the user.

[0218] As an implementation method, in the embodiments of this specification, a prompt message for prompting the user to set up the express payment function can be displayed on the transaction result page or on the upper layer.

[0219] Figure 10 is a schematic diagram of a transaction results page provided in an embodiment of this specification. As shown in Figure 10 , the transaction results page may include payment result information 1002, such as payment success or payment failure, as well as payment information 1004, such as the payment amount, payment method, transaction party, and discount information. It may also include a control 1006 for closing the transaction results page, such as a "Done" control. In actual applications, the specific content and format of the transaction results page can be customized based on actual needs and are not specifically limited here.

[0220] Figure 11 is a schematic diagram of a prompt message provided in an embodiment of this specification. As shown in Figure 11, prompt message 1102 prompting the user to set up the express payment function can be displayed in a pop-up window above the transaction results page. The specific content of the prompt message can be customized based on actual needs. For example, the prompt message can also include path information for setting up the express payment function.

[0221] As shown in FIG11 , the page containing the prompt information may also include an operation control 1104 for setting the ultra-fast payment function. This control can be used to turn the ultra-fast payment function on or off, or to jump to the settings page for setting the ultra-fast payment function. The page may also include a control for closing the page.

[0222] Figure 12 is a schematic diagram of a prompt message display provided in an embodiment of this specification. As shown in Figure 12, prompt message 1202 prompting the user to set up the express payment function is displayed on the transaction results page. The page may also include an operation control 1204 for setting up the express payment function. The prompt message may or may not overlap with the display area of ​​the operation control.

[0223] In actual applications, for an initiated transaction request, the prompt information may be displayed in either the form of a transaction result page or in an upper layer of the payment page, or both forms may be used. For example, if the user clicks the close control in the pop-up window shown in Figure 11, the transaction result page with the prompt information shown in Figure 12 may be displayed. In actual applications, the specific control names, forms, and layout of the prompt information and operation controls can be set according to actual needs.

[0224] FIG13 is a schematic diagram of a display prompt message provided in an embodiment of this specification. As shown in FIG13 , a prompt message 1302 for prompting a user to set up the express payment function is displayed on the transaction results page. The page may also include an operation control 1304 for setting up the express payment function.

[0225] In actual applications, different prompts can be displayed for different users. For example, for users who have not yet enabled the express payment function, prompts can be displayed in the manner shown in FIG11 , and for users who have enabled the express payment function, prompts can be displayed in the manner shown in FIG13 .

[0226] If the user performs an operation on the operation control in the page displaying the prompt information, the mobile terminal may also display a setting page for setting the express payment function.

[0227] Figure 14 is a schematic diagram of a settings page provided in an embodiment of this specification. As shown in Figure 14, this page may include information 1402 about the Express Pay feature, which may be in the form of text, video, or audio. For example, it may include video demonstrations before and after the feature is enabled. If the user has enabled the Express Pay feature, a control 1404 on the settings page can be used to disable the feature. If the user has not enabled the feature, the control 1404 on the settings page can be used to enable the feature. In actual applications, after the user has completed the settings for the Express Pay feature, the terminal may also display a transaction results page.

[0228] Considering that the terminal or server also takes some time to execute the payment process, in order to improve user experience, optionally, before displaying the transaction result page, the embodiment of this specification may also include: displaying a payment response page; the payment response page includes prompt information indicating that payment is in progress.

[0229] Figure 15 is a schematic diagram of a payment response page provided in an embodiment of this specification. As shown in Figure 15 , the payment response page may include a prompt 1502 indicating that a payment is in progress, information 1504 indicating the near-field communication method being used, such as the word "NFC," and other descriptive information related to near-field communication payment, such as the "tap to pay" message shown in Figure 15 .

[0230] It is understood that the various schematic diagrams provided in this specification are merely examples, and in actual applications, the display content and style of various pages can be set according to actual needs.

[0231] After the mobile terminal starts the payment application, it can display the payment response page. After the server completes the payment process, the mobile terminal can display the transaction result page.

[0232] As an implementation method, after a user uses a mobile terminal with the express payment function enabled to approach a payment device with an NFC tag, a payment response page may be displayed on the mobile terminal.

[0233] In the embodiments of this specification, the payment prompt page, payment page or transaction result page can be displayed when the mobile terminal is unlocked or unlocked. For example, when the mobile terminal is in the lock screen state, after obtaining the tag information of the NFC tag, the payment prompt page can be displayed. When the user operates the payment prompt page, the camera of the mobile terminal can collect the user's face, iris, fingerprint and other biometric images, unlock the mobile terminal, and the mobile terminal can display the transaction result page in the unlocked state. In actual application, the user can also unlock the mobile terminal first, and then move the mobile terminal close to the NFC tag to obtain the tag information. For example, when the distance between the mobile terminal and the NFC tag meets the conditions, such as when the mobile terminal is close to the NFC tag, the mobile terminal or the payment device associated with the NFC tag can issue a prompt information for prompting the user to unlock the mobile terminal, such as a voice prompt information, a text prompt information, an animation prompt information, etc. In order to simplify user operations, the application can also be started in the background in the unlocked state, and the payment prompt page, payment page or transaction result page can be displayed. Based on the same idea, the embodiments of this specification also provide a near-field communication-based payment method with a server as the execution entity. Figure 16 is a flow chart of a near-field communication-based payment method provided in the embodiments of this specification. From a program perspective, the execution entity of the process can be a program or application client installed on the server.

[0234] As shown in Figure 16, the process may include the following steps: Step 1602: The server obtains a payment processing request containing payment information sent by a mobile terminal with near-field communication function; the payment information is provided by the second transaction party based on a payment page displaying user information containing the first transaction party; the payment page is generated by the mobile terminal based on the tag information in the obtained NFC tag; the tag information contains payment link information; Step 1604: Based on the payment processing request, the payment service for the first transaction party and the second transaction party is completed.

[0235] The server may be a server with payment processing capabilities. It may determine the transaction account or account number of the first transaction party based on the user information of the first transaction party, such as the merchant ID and user ID. It may also determine the transaction amount and the transaction account or account number of the second transaction party based on the transaction information provided by the second transaction party, and complete transaction processing for the transaction amount. The server in this embodiment may be equivalent to the server in the method described in FIG. 2 . Similar or identical parts can be found in the description of the above embodiment and will not be repeated here.

[0236] Figure 17 is a flow chart of a payment method based on near field communication provided in an embodiment of this specification. From a program perspective, the execution subject of the process can be a program or application client installed on the server.

[0237] As shown in Figure 17, the process may include the following steps: Step 1702: The server obtains a payment information acquisition request generated by a mobile terminal with near-field communication function based on the tag information in the obtained NFC tag; the tag information is used to trigger the payment process; Step 1704: Based on the payment information acquisition request, generate transaction identification information for representing the user payment account information in the mobile terminal; Step 1706: Send the transaction identification information to the payment device associated with the NFC tag; the payment device is used to execute the payment process according to the transaction identification information.

[0238] The server can be equivalent to the server in the method described in Figure 5 above. For detailed description, please refer to the description of the above embodiment and will not be repeated here. The server in this embodiment can also be the same server as the server in Figure 2 or Figure 16 above, which is not specifically limited here.

[0239] Figure 18 is a flow chart of a payment method based on near field communication provided in an embodiment of this specification. From a program perspective, the execution subject of the process can be a program or application client installed on the server.

[0240] As shown in Figure 18, the process may include the following steps: Step 1802: The server obtains a payment processing request sent by the mobile terminal; the payment processing request is sent by the payment application launched by the mobile terminal based on the tag information in the NFC tag; Step 1804: Process the payment service based on the payment request and generate payment result information; Step 1806: Feedback the payment result information to the mobile terminal.

[0241] Optionally, processing the payment service based on the payment request may specifically include: generating transaction identification information containing user payment account information in the mobile terminal based on the payment processing request; sending the transaction identification information to the payment device so that the payment device executes the payment process based on the transaction identification information.

[0242] Optionally, the method may further include: sending a payment process triggering instruction to the payment device, so that the payment device can execute the payment process based on the payment process triggering instruction and the acquired transaction identification information.

[0243] The specific implementation process can be found in the above embodiments and will not be elaborated here.

[0244] In the embodiments of this specification, information transmission between the payment device, the mobile terminal and the server can be transmitted through the network.

[0245] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method. Figure 19 is a structural diagram of a payment device based on near field communication provided in the embodiments of this specification corresponding to Figure 2. As shown in Figure 19, the device may include: a trigger information sending module 1902, which is used to send an electromagnetic signal for triggering an NFC tag; a tag information acquisition module 1904, which is used to obtain tag information of the NFC tag in response to the electromagnetic signal; the tag information includes payment link information; a page display module 1906, which is used to display a payment page containing the user information of the first transaction party based on the payment link information; a payment information acquisition module 1908, which is used to obtain the payment information provided by the second transaction party based on the payment page; a request sending module 1910, which is used to send a payment processing request containing the payment information to a server, and the server is used to complete the payment based on the payment processing request.

[0246] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method. Figure 20 is a structural diagram of a payment device based on near field communication provided in the embodiments of this specification corresponding to Figure 5. As shown in Figure 20, the device may include: a trigger information sending module 2002, which is used to send an electromagnetic signal for triggering an NFC tag; a tag information acquisition module 2004, which is used to obtain tag information of the NFC tag in response to the electromagnetic signal; the tag information is used to trigger the payment process; a transaction identification acquisition module 2006, which is used to obtain transaction identification information for representing the user payment account information in the mobile terminal based on the tag information; a transaction identification sending module 2008, which is used to send the transaction identification information to the payment device associated with the NFC tag, and the payment device is used to execute the payment process according to the transaction identification information.

[0247] FIG21 is a schematic diagram of the structure of a near-field communication-based payment device provided in an embodiment of this specification, corresponding to FIG7 . As shown in FIG21 , the device may include: a tag information acquisition module 2102 for acquiring tag information of an NFC tag associated with a payment device; an application launch module 2104 for launching a payment application on the mobile terminal based on the tag information; a request sending module 2106 for sending a payment processing request to a server based on the launched payment application; the server for processing the payment transaction based on the payment processing request and providing payment result information; and a page display module 2108 for displaying a transaction result page based on the payment result information provided by the server.

[0248] Figure 22 is a schematic diagram of the structure of a near-field communication-based payment device provided in an embodiment of this specification, corresponding to Figure 16. As shown in Figure 22, the device may include: a request acquisition module 2202, configured to acquire a payment processing request including payment information sent by a mobile terminal with near-field communication functionality; the payment information is provided by the second transaction party based on a payment page displaying the user information of the first transaction party; the payment page is generated by the mobile terminal based on tag information from a captured NFC tag; the tag information includes payment link information; and a request processing module 2204, configured to complete payment transactions for the first and second transaction parties based on the payment processing request.

[0249] Figure 23 is a schematic diagram of the structure of a near-field communication-based payment device provided in an embodiment of this specification, corresponding to Figure 17. As shown in Figure 23, the device may include: a request acquisition module 2302, configured to acquire a payment information acquisition request generated by a mobile terminal with near-field communication capabilities based on tag information acquired from an NFC tag; the tag information is used to trigger a payment process; an information generation module 2304, configured to generate transaction identification information representing user payment account information in the mobile terminal based on the payment information acquisition request; and a transmission module 2306, configured to transmit the transaction identification information to a payment device associated with the NFC tag; the payment device is configured to execute a payment process based on the transaction identification information.

[0250] Figure 24 is a schematic diagram of the structure of a near-field communication-based payment device provided in an embodiment of this specification, corresponding to Figure 18. As shown in Figure 24, the device may include: a request acquisition module 2402 for acquiring a payment processing request sent by a mobile terminal; the payment processing request is sent by a payment application activated by the mobile terminal based on tag information in an NFC tag; a payment processing module 2404 for processing a payment transaction based on the payment request and generating payment result information; and a result transmission module 2406 for feeding the payment result information back to the mobile terminal.

[0251] Based on the same idea, the embodiments of this specification also provide devices corresponding to the above methods.

[0252] Figure 25 is a schematic diagram of the structure of a near-field communication (NFC)-based payment device provided in an embodiment of this specification. As shown in Figure 25, device 2500 may include: at least one processor 2510; and memory 2530 communicatively coupled to the at least one processor; the memory 2530 stores instructions 2520 executable by the at least one processor 2510. The instructions are executed by the at least one processor 2510 to enable the at least one processor 2510 to perform at least one of the aforementioned NFC-based payment methods.

[0253] Based on the same idea, the embodiments of this specification also provide a computer-readable medium corresponding to the above method. The computer-readable medium stores computer-readable instructions, which can be executed by a processor to implement at least one of the above-mentioned near-field communication-based payment methods.

[0254] The various embodiments in this specification are described in a progressive manner. Similar portions between the various embodiments can be referenced to each other, and each embodiment focuses on the differences from the other embodiments. In particular, since the apparatus and device are generally similar to the method embodiments, their description is relatively simple, and relevant portions can be referenced to the description of the method embodiments.

[0255] In the 1990s, technological improvements could be clearly distinguished as either hardware improvements (for example, improvements to circuit structures like diodes, transistors, and switches) or software improvements (improvements to process flows). However, with the advancement of technology, many process flow improvements today can now be considered direct improvements to hardware circuit structures. Designers almost always create the corresponding hardware circuit structure by programming the improved process flow into the hardware circuit. Therefore, it cannot be said that a process flow improvement cannot be implemented using hardware modules. For example, a programmable logic device (PLD), such as a field programmable gate array (FPGA), is an integrated circuit whose logical function is determined by user programming. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to hire a chip manufacturer to design and manufacture a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly done using "logic compiler" software. This is similar to the software compiler used when developing programs. Before compilation, the original code must also be written in a specific programming language, called a hardware description language (HDL). There is not just one 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 are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art will also understand that by simply programming the method flow in one of these hardware description languages ​​and then programming it into an integrated circuit, a hardware circuit that implements the logic method flow can be easily obtained.

[0256] The controller can be implemented in any suitable manner. For example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers 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 will also know that in addition to implementing the controller in a purely computer-readable program code format, the controller can be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers 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 considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules that implement the method and structures within the hardware component.

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

[0258] For the convenience of description, the above devices are described as being divided into various units according to their functions. Of course, when implementing this application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0259] It will be understood by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0260] The present invention is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0261] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0262] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0263] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory. Memory may include non-permanent storage in a computer-readable medium, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0264] 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. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (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 herein, computer-readable media does not include transitory media such as modulated data signals and carrier waves.

[0265] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0266] 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. Furthermore, 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 magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0267] 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 communications network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0268] The foregoing is merely an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should all be included within the scope of the claims of the present application.

Claims

1. A payment method based on near field communication, comprising: A mobile terminal with near field communication function sends an electromagnetic signal for triggering the NFC tag; Acquire tag information of an NFC tag that responds to the electromagnetic signal; the tag information includes payment link information; Based on the payment link information, displaying a payment page including user information of the first transaction party; Obtaining payment information provided by the second transaction party based on the payment page; A payment processing request including the payment information is sent to a server, and the server is used to complete the payment based on the payment processing request.

2. The method according to claim 1, wherein the tag information includes instruction information for starting a payment application; The displaying of a payment page including the user information of the first transaction party based on the payment link information specifically includes: Based on the instruction information, starting the payment application in the mobile terminal; Based on the started payment application, the payment page is displayed.

3. The method according to claim 2, wherein the tag information includes request identification information for requesting to obtain payment page information; and displaying the payment page based on the payment application being started specifically comprises: The payment application in the startup state generates a payment page information acquisition request according to the request identification information; Sending the payment page acquisition request to the server; Obtain payment page information including user information of the first transaction party generated by the server based on the payment page acquisition request; Based on the payment page information, a payment page including the user information of the first transaction party is displayed.

4. The method according to claim 1, wherein the tag information includes user identification information of the first transaction party; the method further comprises: Based on the user identification information, determining whether the first transaction party has transaction authority, and obtaining a determination result; The displaying of the payment page including the user information of the first transaction party specifically includes: If the determination result indicates that the first transaction party has transaction authority, a payment page including user information of the first transaction party is displayed.

5. The method according to claim 1, wherein the NFC tag is located in a carrier that contains the payment code of the first transaction party, or is located in a carrier that does not contain the payment code of the first transaction party.

6. The method according to claim 1, if the mobile terminal is displaying an application page of a second application when acquiring the tag information of the NFC tag containing the payment link information, the displaying corresponds to the payment page of the first transaction party, specifically comprising: The payment page is displayed in an overlay on the application page of the second application.

7. The method according to claim 6, further comprising: Obtaining an exit operation of the second transaction party on the payment page; Based on the exit operation, switch to the application page of the second application for display.

8. The method according to claim 1, wherein the tag information includes first trigger information, and the first trigger information is used to trigger the mobile terminal to determine a terminal application with a payment function in the mobile terminal and generate an application selection page; the method further comprises: In response to the first trigger information, determining a terminal application having a payment function in the mobile terminal; Based on the terminal application with payment function, generating an application selection page; The application selection page is displayed.

9. The method according to claim 8, after displaying the application selection page, further comprising: Acquire the target terminal application selected by the second transaction party from the application selection page; The step of displaying a payment page including transaction information of the first transaction party based on the payment link information specifically includes: Using the target terminal application to access the payment link information; A payment page including transaction information of the first transaction party is displayed in the target terminal application.

10. The method according to claim 1, before acquiring the tag information of the NFC tag that responds to the electromagnetic signal, comprises: Determining whether the mobile terminal has started a code scanning application for scanning a payment code image; The acquiring tag information of the NFC tag that responds to the electromagnetic signal specifically includes: If not started, obtaining tag information of the NFC tag that responds to the electromagnetic signal.

11. According to the method of claim 1, the payment page includes at least one of a control for confirming payment information, an area for filling in or selecting a payment amount, and an area for filling in or selecting a payment method.

12. The method according to claim 2, further comprising: Determining whether the payment application exists in the terminal; If it does not exist, a prompt message indicating that payment cannot be made will be generated.

13. The method according to claim 2, further comprising: Determining whether the payment application exists in the terminal; If it does not exist, a prompt message is generated to prompt the user to download and install the payment application.

14. The method according to claim 1, further comprising: The payment password input page is displayed.

15. The method according to claim 1, further comprising: Generate a page or prompt information indicating the transaction results.

16. A payment method based on near field communication, comprising: A mobile terminal with near field communication function sends an electromagnetic signal for triggering the NFC tag; Acquiring tag information of an NFC tag that responds to the electromagnetic signal; The tag information is used to trigger the payment process; Based on the tag information, acquiring transaction identification information for representing the user payment account information in the mobile terminal; The transaction identification information is sent to a payment device associated with the NFC tag, and the payment device is used to execute a payment process according to the transaction identification information.

17. The method according to claim 16, wherein the acquiring, based on the tag information, transaction identification information for representing the user payment account information in the mobile terminal comprises: Sending a payment information acquisition request including the user identification information in the mobile terminal to a server; The transaction identification information generated by the server based on the user identification information is obtained.

18. The method according to claim 16, wherein sending the transaction identification information to a payment device comprises: The transaction identification information is sent to the payment device via near field communication.

19. The method according to claim 18, wherein sending the transaction identification information to the payment device by near field communication comprises: Writing the transaction identification information into the NFC tag; The transaction identification information is fed back to the payment device via the NFC tag in a near field communication manner.

20. The method according to claim 16, wherein the tag information includes a device identification of the payment device; and sending the transaction identification information to the payment device comprises: Sending a payment request including the device identification to a server; The server is used to generate transaction identification information, and send the transaction identification information to the payment device according to the device identification.

21. The method according to claim 16, wherein the tag information includes first link information for starting a payment application in the mobile terminal; the method further comprises: Based on the first link information, starting the payment application; The acquiring of transaction identification information for indicating the user payment account information in the mobile terminal specifically includes: Based on the started payment application, the transaction identification information is obtained.

22. The method according to claim 21, after starting the payment application, further comprising: A prompt message is displayed to indicate that the payment application has been started, wherein the prompt message specifically includes prompt message in at least one form of vibration, sound, text or image.

23. The method according to claim 16, further comprising: Obtaining transaction result information fed back by the server; Based on the transaction result information, a transaction result page is displayed.

24. The method according to claim 23, if the mobile terminal is displaying an application page of a second application when acquiring the tag information of the NFC tag, the displaying of the transaction result page specifically comprises: The transaction result page is displayed as an overlay on the application page of the second application.

25. The method according to claim 24, further comprising: Obtaining an exit operation for the transaction result page; Based on the exit operation, switch to the application page of the second application for display.

26. The method according to claim 21, wherein the tag information includes an identification of the payment application; The starting the payment application based on the first link information specifically includes: Based on the identification of the payment application, the payment application is started.

27. The method according to claim 16, further comprising: Based on the transaction identification information, generating a payment code image; Displaying the payment code image; The sending the transaction identification information to a payment device associated with the NFC tag specifically includes: The transaction identification information is sent to a payment device with a code scanning function through the payment code image.

28. A payment method based on near field communication, comprising: The mobile terminal with near field communication function obtains tag information of the NFC tag associated with the payment device; Based on the tag information, starting a payment application in the mobile terminal; Based on the activated payment application, sending a payment processing request to a server; The server is used to process the payment service based on the payment processing request and feedback the payment result information; Based on the payment result information fed back by the server, a transaction result page is displayed.

29. The method according to claim 28, further comprising: Based on the tag information, displaying a payment prompt page; the payment prompt page includes prompt information for prompting the user to use the payment application to make payment; Obtaining a first preset operation of the user on the payment prompt page, and generating first confirmation information; The starting of the payment application in the mobile terminal specifically includes: Based on the first confirmation information, a payment application in the mobile terminal is started.

30. The method according to claim 28, before displaying the transaction result page, further comprising: Display a payment page containing payment information; Acquire second confirmation information generated based on a second preset operation of the user on the payment page. The sending of the payment processing request to the server specifically includes: Based on the second confirmation information, a payment processing request is sent to the server.

31. According to the method according to claim 28, the server is used to generate transaction identification information containing user payment account information in the mobile terminal based on the payment processing request, and send the transaction identification information to the payment device so that the payment device executes the payment process based on the transaction identification information.

32. The method according to claim 31, after starting the payment application in the mobile terminal, further comprising: Display a payment page containing payment information; Obtain second confirmation information generated based on a second preset operation of the user on the payment page, so that the server sends a payment process trigger instruction to the payment device after the second confirmation information, and the payment device can execute the payment process based on the payment process trigger instruction and the acquired transaction identification information.

33. The method according to claim 30 or 32, before displaying the payment page containing payment information, further comprising: Based on the account information of the payment application in the mobile terminal, determining whether the user of the mobile terminal meets the preset payment conditions; The preset payment conditions represent conditions that enable quick payment; The display of the payment page containing the payment information specifically includes: If the user does not meet the preset payment conditions, a payment page containing payment information is displayed.

34. The method according to claim 33, wherein displaying the transaction result page comprises: If the user meets the preset payment conditions, the transaction result page is displayed.

35. According to the method of claim 33, the preset payment conditions include at least one of being authorized to use the ultra-fast payment function, the user being a high-activity user of the payment application, and being authorized to use the password-free payment function.

36. According to the method of claim 30 or 32, the payment information includes at least one of transaction amount information, transaction party information, and transaction method information.

37. The method of claim 28, further comprising: Displays a prompt message to prompt the user to set up the express payment function.

38. The method of claim 37, further comprising: Determine whether the number of times a prompt message for prompting a user to set up the express payment function has been displayed within a preset time period is less than or equal to a preset number of times; The prompt information displayed to prompt the user to set up the quick payment function specifically includes: If the number of times displayed is less than or equal to the preset number, a prompt message is displayed to prompt the user to set up the fast payment function.

39. The method of claim 37, further comprising: Determine whether the user account of the payment application in the mobile terminal has enabled the express payment function; The prompt information displayed to prompt the user to set up the quick payment function specifically includes: If the ultra-fast payment function is not enabled in the user account, a first prompt message is displayed to prompt the user to enable the ultra-fast payment function.

40. The method according to claim 39, before displaying the first prompt information for prompting the user to enable the ultra-fast payment function, further comprising: Determining whether the user account is a highly active user account; The first prompt information displayed to prompt the user to enable the fast payment function specifically includes: If the user account is a highly active user account, a first prompt message is displayed to prompt the user to enable the ultra-fast payment function.

41. According to the method of claim 39, the displaying of prompt information for prompting the user to set up the ultra-fast payment function specifically includes: If the express payment function has been enabled in the user account, a second prompt message is displayed to prompt the user to disable the express payment function.

42. According to the method of claim 37, the displaying of prompt information for prompting the user to set up the ultra-fast payment function specifically comprises: A prompt message for prompting the user to set up the ultra-fast payment function is displayed in the transaction result page or on the upper layer.

43. According to the method of claim 37, the page where the prompt information is located also includes an operation control for setting a fast payment function.

44. The method of claim 43, further comprising: Based on the user's operation on the operation control, a setting page for setting the ultra-fast payment function is displayed.

45. The method according to claim 28, before displaying the transaction result page, further comprising: A payment response page is displayed; the payment response page includes prompt information indicating that payment is in progress.

46. ​​The method according to claim 28, wherein the tag information includes an application identifier of the payment application; and starting the payment application in the mobile terminal based on the tag information specifically comprises: Based on the application identifier, a payment application in the mobile terminal is started.

47. The method according to claim 29, wherein the tag information includes link information, and the link information includes information for displaying the payment prompt page; and displaying the payment prompt page based on the tag information specifically comprises: Based on the link information, a payment prompt page is displayed.

48. The method according to claim 47, wherein the link information further includes an application identifier of the payment application.

49. A payment method based on near field communication, comprising: The server obtains a payment processing request including payment information sent by a mobile terminal having a near field communication function; The payment information is provided by the second transaction party based on displaying a payment page containing user information of the first transaction party; the payment page is generated by the mobile terminal based on tag information in the acquired NFC tag; the tag information contains payment link information; Based on the payment processing request, the payment service for the first transaction party and the second transaction party is completed.

50. A payment method based on near field communication, comprising: The server obtains a payment information acquisition request generated by a mobile terminal with a near field communication function based on tag information in the obtained NFC tag; The tag information is used to trigger the payment process; Based on the payment information acquisition request, generating transaction identification information for representing the user payment account information in the mobile terminal; The transaction identification information is sent to a payment device associated with the NFC tag; the payment device is used to execute a payment process according to the transaction identification information.

51. A payment method based on near field communication, comprising: The server obtains the payment processing request sent by the mobile terminal; The payment processing request is sent by a payment application started by the mobile terminal based on tag information in the NFC tag; Processing a payment service based on the payment request and generating payment result information; The payment result information is fed back to the mobile terminal.

52. The method according to claim 51, wherein processing a payment service based on the payment request comprises: generating transaction identification information including user payment account information in the mobile terminal based on the payment processing request; The transaction identification information is sent to a payment device so that the payment device performs a payment process based on the transaction identification information.

53. The method of claim 52, further comprising: A payment process triggering instruction is sent to the payment device, so that the payment device can execute the payment process based on the payment process triggering instruction and the acquired transaction identification information.

54. A payment device based on near field communication, comprising: A trigger information sending module, used for sending an electromagnetic signal for triggering an NFC tag; A tag information acquisition module, used to acquire tag information of an NFC tag that responds to the electromagnetic signal; the tag information includes payment link information; A page display module, configured to display a payment page including user information of the first transaction party based on the payment link information; A payment information acquisition module, used to acquire payment information provided by the second transaction party based on the payment page; The request sending module is used to send a payment processing request containing the payment information to a server, and the server is used to complete the payment based on the payment processing request.

55. A payment device based on near field communication, comprising: A trigger information sending module, used for sending an electromagnetic signal for triggering an NFC tag; A tag information acquisition module is used to acquire tag information of an NFC tag that responds to the electromagnetic signal; the tag information is used to Trigger the payment process; A transaction identification acquisition module, used to acquire transaction identification information representing user payment account information in the mobile terminal based on the tag information; The transaction identification sending module is used to send the transaction identification information to a payment device associated with the NFC tag, and the payment device is used to execute a payment process according to the transaction identification information.

56. A payment device based on near field communication, comprising: A tag information acquisition module, used to acquire tag information of an NFC tag associated with a payment device; An application startup module, used to start a payment application in the mobile terminal based on the tag information; A request sending module, used for sending a payment processing request to a server based on the activated payment application; The server is used to process the payment service based on the payment processing request and feedback the payment result information; The page display module is used to display the transaction result page based on the payment result information fed back by the server.

57. A payment device based on near field communication, comprising: A request acquisition module, used to acquire a payment processing request containing payment information sent by a mobile terminal with a near field communication function; The payment information is provided by the second transaction party based on displaying a payment page containing user information of the first transaction party; the payment page is generated by the mobile terminal based on tag information in the acquired NFC tag; the tag information contains payment link information; A request processing module is used to complete the payment service for the first transaction party and the second transaction party based on the payment processing request.

58. A payment device based on near field communication, comprising: A request acquisition module, used to acquire a payment information acquisition request generated by a mobile terminal with a near field communication function based on tag information in an acquired NFC tag; The tag information is used to trigger the payment process; An information generation module, used to generate transaction identification information representing the user payment account information in the mobile terminal based on the payment information acquisition request; The sending module is used to send the transaction identification information to a payment device associated with the NFC tag; the payment device is used to execute a payment process according to the transaction identification information.

59. A payment device based on near field communication, comprising: A request acquisition module, used to acquire a payment processing request sent by a mobile terminal; The payment processing request is sent by a payment application started by the mobile terminal based on tag information in the NFC tag; A payment processing module, used to process payment services based on the payment request and generate payment result information; The result sending module is used to feed back the payment result information to the mobile terminal.

60. A payment device based on near field communication, 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, the instructions being executed by the at least one processor to enable the at least one processor to execute a near-field communication-based payment method as described in any one of claims 1 to 15, any one of claims 16 to 27, any one of claims 28 to 48, or claim 49, or claim 50, or any one of claims 51 to 53.

61. A computer-readable medium having computer-readable instructions stored thereon, which can be executed by a processor to implement the near-field communication-based payment method described in any one of claims 1 to 15, any one of claims 16 to 27, any one of claims 28 to 48, claim 49, claim 50, or any one of claims 51 to 53.

Images