Payment method, device, equipment, and medium based on near field communication

Abstract

The embodiments of the present specification disclose a payment method, device, equipment, and medium based on near field communication, which includes the steps of: a mobile terminal with near field communication function emitting an electromagnetic signal used to trigger an NFC tag, acquiring tag information of the NFC tag responding to the electromagnetic signal, where the tag information includes payment link information; displaying a payment page including user information of a first merchant based on the payment link information, acquiring payment information provided by a second merchant based on the payment page, and sending a payment processing request including the payment information to a server, where the server is used to complete the payment based on the payment processing request.

Description

[Technical Field]

[0001] The present application relates to the field of computers, and more particularly to a payment method, device, apparatus, and medium based on near field communication. [Background technology]

[0002] With the development of computer technology, mobile payment based on payment codes has become increasingly popular and has greatly improved users' payment experience. However, with the development of mobile applications, applications such as games, novels, and short videos occupy longer and longer periods of time on terminal screens. When a user needs to make a payment, he or she needs to log out of the current application, find a payment application with payment function from the application list of the terminal, and then activate the code scanning function in the payment application or open the payment code, which makes the user's operations relatively complicated.

[0003] Therefore, how to simplify users' payment operations and improve user experience is a technical issue that needs to be resolved immediately. Summary of the Invention [Problem to be solved by the invention]

[0004] The embodiments herein provide a payment method, device, equipment, and medium based on near field communication, which solves the problem of complicated user operations present in conventional payment methods.

[0005] In order to solve the above technical problems, the embodiments of the present specification are realized as follows. [Means for solving the problem]

[0006] The embodiments of this specification provide a payment method based on near field communication, which includes the steps of: a mobile terminal with near field communication function emitting an electromagnetic signal used to trigger an NFC tag; acquiring tag information of the NFC tag responding to the electromagnetic signal, where the tag information includes payment link information; displaying a payment page including user information of a first merchant based on the payment link information; acquiring payment information provided by a second merchant based on the payment page; and sending a payment processing request including the payment information to a server, where the server is used to complete the payment based on the payment processing request.

[0007] The embodiments of this specification provide a payment method based on near field communication, which includes the steps of: a mobile terminal with near field communication function emitting an electromagnetic signal used to trigger an NFC tag; acquiring tag information of the NFC tag responding to the electromagnetic signal, where the tag information is used to trigger a payment flow; acquiring transaction identification information based on the tag information, where the transaction identification information is used to represent user payment account information in the mobile terminal; and sending the transaction identification information to a payment instrument associated with the NFC tag, where the payment instrument is used to execute the payment flow according to the transaction identification information.

[0008] The embodiments of this specification provide a payment method based on near field communication, which includes the steps of: a mobile terminal with near field communication function obtaining tag information of an NFC tag associated with a payment device; activating a payment application in the mobile terminal based on the tag information; sending a payment processing request to a server based on the activated payment application, where the server processes payment services based on the payment processing request and feeds back payment result information; and displaying a transaction result page based on the payment result information fed back by the server.

[0009] The embodiments of the present specification provide a payment method based on near field communication, which includes the steps of: a server receiving a payment processing request including payment information sent by a mobile terminal with near field communication function, where the payment information is provided based on a second transaction party displaying a payment page including user information of a first transaction party, where the payment page is generated by the mobile terminal based on tag information in an NFC tag obtained, and the tag information includes payment link information; and completing payment services for the first transaction party and the second transaction party based on the payment processing request.

[0010] The embodiments of the present specification provide a payment method based on near field communication, which includes the steps of: a server acquiring a payment information acquisition request generated based on tag information in an NFC tag acquired by a mobile terminal having near field communication function, the tag information being used to trigger a payment flow; generating transaction identification information based on the payment information acquisition request, the transaction identification information being used to represent user payment account information in the mobile terminal; and sending the transaction identification information to a payment instrument associated with the NFC tag, the payment instrument being used to execute the payment flow according to the transaction identification information.

[0011] The embodiments of this specification provide a payment method based on near field communication, which includes the steps of: a server receiving a payment processing request sent by a mobile terminal, the payment processing request being sent by a payment application launched by the mobile terminal based on tag information in an NFC tag; processing a payment service based on the payment request, generating payment result information; and feeding back the payment result information to the mobile terminal.

[0012] The embodiments of the present specification provide a payment device based on near field communication, which includes: a trigger information sending module, used to emit an electromagnetic signal to trigger an NFC tag; a tag information acquiring module, used to acquire tag information of the NFC tag responding to the electromagnetic signal, where the tag information includes payment link information; a page display module, used to display a payment page including user information of a first merchant based on the payment link information; a payment information acquiring module, used to acquire payment information provided by a second merchant based on the payment page; and a request sending module, used to send a payment processing request including the payment information to a server, where the server completes the payment based on the payment processing request.

[0013] The embodiments of the present specification provide a payment device based on near field communication, which includes: a trigger information sending module used to emit an electromagnetic signal used to trigger an NFC tag; a tag information acquiring module used to acquire tag information of an NFC tag responsive to the electromagnetic signal, where the tag information is used to trigger a payment flow; a transaction identifier acquiring module used to acquire transaction identification information based on the tag information, where the transaction identification information represents user payment account information of the mobile terminal; and a transaction identifier sending module used to send the transaction identification information to a payment instrument associated with the NFC tag, where the payment instrument executes the payment flow according to the transaction identification information.

[0014] The embodiments of the present specification provide a payment device based on near field communication, which includes: a tag information acquisition module used to acquire tag information of an NFC tag associated with a payment device; an application launch module used to launch a payment application in the mobile terminal based on the tag information; a request sending module used to send a payment processing request to a server based on the launched payment application, wherein the server processes the payment service based on the payment processing request and feeds back payment result information; and a page display module used to display a transaction result page based on the payment result information fed back by the server.

[0015] The embodiments of the present specification provide a payment device based on near field communication, which includes: a request acquisition module used to acquire a payment processing request including payment information sent by a mobile terminal with near field communication function, where the payment information is provided based on a second transaction party displaying a payment page including user information of a first transaction party, and the payment page is generated based on tag information in an NFC tag acquired by the mobile terminal, the tag information including 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.

[0016] The embodiments of the present specification provide a payment device based on near field communication, which includes: a request acquisition module used to acquire a payment information acquisition request generated based on tag information in an NFC tag acquired by a mobile terminal with near field communication function, where the tag information is used to trigger a payment flow; an information generation module used to generate transaction identification information used to represent user payment account information in the mobile terminal based on the payment information acquisition request; and a sending module used to send the transaction identification information to a payment device associated with the NFC tag, where the payment device executes the payment flow according to the transaction identification information.

[0017] The embodiments of the present specification provide a payment device based on near field communication, which includes: a request acquisition module used to acquire a payment processing request sent by a mobile terminal, where the payment processing request is sent by a payment application launched by the mobile terminal based on tag information in an NFC tag; a payment processing module used to process a payment service based on the payment request and generate payment result information; and a result sending module used to feed back the payment result information to the mobile terminal.

[0018] The embodiments of the present specification provide a near field communication-based payment device, which includes at least one processor and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, and the instructions, when executed by the at least one processor, cause the at least one processor to realize a near field communication-based payment method.

[0019] The embodiments of the present specification provide a computer-readable medium having computer-readable instructions stored thereon, which, when executed by a processor, can realize a payment method based on near field communication.

[0020] At least one embodiment of the present specification can achieve the following beneficial effects: In an embodiment of the present specification, a mobile terminal can obtain payment link information from an NFC tag through near-field wireless communication, and the mobile terminal can display a payment page based on the information. The user can enter payment information, such as the payment amount, on the payment page to complete the payment. In this way, the user does not need to find a payment application and then perform the corresponding payment operation in the payment application. For example, in a scenario where a payment needs to be made by scanning a payment code, the user does not need to find a payment application and then select a code scanning function in the payment application. In an embodiment of the present specification, the mobile terminal can display a payment page based on the information from the NFC tag, simplifying user operations and improving the user experience.

[0021] In at least one embodiment, the mobile terminal acquires tag information used to trigger a payment flow from the NFC tag via near field communication, acquires transaction identification information, and transmits it to the payment device to make the payment. In this way, the user does not need to find a payment application and perform a corresponding payment operation in the payment application. For example, in a scenario where a payment code needs to be presented and scanned by the payment device to make a payment, the user does not need to find a payment application and select and display the payment code in the payment application. In an embodiment of the present specification, the mobile terminal can transmit transaction identification information for payment to the payment device based on the information in the NFC tag, simplifying user operations and improving the user experience.

[0022] In at least one embodiment, the mobile terminal can obtain tag information from the NFC tag through a near field communication scheme, launch a payment application on the mobile terminal, and initiate a payment processing request to a server, and the server can process the payment service and feed back result information to the mobile terminal. In this way, payment can be triggered through the NFC scheme, and the user does not need to manually find the payment application and then manually launch the payment application to make a payment, which simplifies user operations and improves the user experience.

[0023] In order to more clearly describe the embodiments of this specification or the technical solutions in the prior art, the following briefly introduces drawings that need to be used in the description of the embodiments or the prior art. It is obvious that the drawings in the following description are only some embodiments described in this application, and those skilled in the art can further obtain other drawings based on these drawings without requiring any inventive efforts. [Brief explanation of the drawings]

[0024] [Figure 1] FIG. 1 is a schematic diagram of an application scenario of a payment method based on near field communication in an embodiment of the present specification. [Figure 2] FIG. 1 is a flow diagram of a payment method based on near field communication provided by an embodiment of the present specification. [Figure 3] FIG. 1 is a swimlane diagram of a near field communication-based payment method provided in an embodiment of the present specification. [Figure 4] FIG. 1 is a schematic diagram of an application scenario of a payment method based on near field communication in an embodiment of the present specification. [Figure 5] FIG. 1 is a flow diagram of a payment method based on near field communication provided by an embodiment of the present specification. [Figure 6] FIG. 1 is a swimlane diagram of a near field communication-based payment method provided in an embodiment of the present specification. [Figure 7]FIG. 1 is a flow diagram of a payment method based on near field communication provided in an embodiment of the present specification. [Figure 8] FIG. 1 is a schematic diagram of a payment offer page provided by an embodiment of the present disclosure. [Figure 9] FIG. 1 is a schematic diagram of a payment page provided in an example embodiment of the present specification. [Figure 10] FIG. 10 is a schematic diagram of a transaction results page provided in an example of the present specification. [Figure 11] FIG. 1 is a schematic diagram showing the presentation information provided in the examples of the present specification. [Figure 12] FIG. 1 is a schematic diagram showing the presentation information provided in the examples of the present specification. [Figure 13] FIG. 1 is a schematic diagram showing the presentation information provided in the examples of the present specification. [Figure 14] FIG. 1 is a schematic diagram of a settings page provided in an example of the present specification. [Figure 15] FIG. 1 is a schematic diagram of a payment response page provided in an example of the present specification. [Figure 16] FIG. 1 is a flow diagram of a payment method based on near field communication provided by an embodiment of the present specification. [Figure 17] FIG. 1 is a flow diagram of a payment method based on near field communication provided by an embodiment of the present specification. [Figure 18] FIG. 1 is a flow diagram of a payment method based on near field communication provided by an embodiment of the present specification. [Figure 19] FIG. 3 is a structural schematic diagram of a payment device based on near field communication provided by an embodiment of this specification, corresponding to FIG. 2 . [Figure 20] FIG. 6 is a structural schematic diagram of a payment device based on near field communication provided by an embodiment of this specification, corresponding to FIG. 5 . [Figure 21] FIG. 8 is a structural schematic diagram of a payment device based on near field communication provided by an embodiment of this specification, corresponding to FIG. 7 . [Figure 22]FIG. 17 is a structural schematic diagram of a payment device based on near field communication, which corresponds to FIG. 16 provided by an embodiment of this specification. [Figure 23] FIG. 18 is a structural schematic diagram of a payment device based on near field communication, which corresponds to FIG. 17 provided by an embodiment of this specification. [Figure 24] FIG. 19 is a structural schematic diagram of a payment device based on near field communication provided by an embodiment of the present specification, corresponding to FIG. 18 . [Figure 25] 1 is a structural schematic diagram of a payment device based on near field communication provided by an embodiment of this specification; DETAILED DESCRIPTION OF THE INVENTION

[0025] In order to clarify the objectives, technical solutions, and advantages of one or more embodiments of the present specification, the following clearly and completely describes the technical solutions of one or more embodiments of the present specification with reference to specific embodiments of the present specification and corresponding drawings. It is obvious that the described embodiments are only some of the embodiments of the present specification, and not all of the embodiments. Based on the embodiments of the present specification, all other embodiments obtained by those skilled in the art without requiring inventive efforts fall within the protection scope of one or more embodiments of the present specification.

[0026] Hereinafter, the technical solutions provided by the embodiments of this specification will be described in detail with reference to the drawings.

[0027] In the prior art, when a user purchases a product, the user usually needs to pay by entering a payment code or scanning a merchant's payment code. Typically, the user needs to find a payment application on the terminal and then select the payment code or code scanning function to make the payment. If the user is using other applications on the terminal before making the payment, such as reading e-books and watching videos, the user needs to log out of the current application, then find the payment application, and then find the payment code or code scanning function, which makes the user's operations relatively complicated.

[0028] To address the shortcomings of the prior art, the present solution provides the following embodiment. FIG. 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 FIG. 1, the solution may include a mobile terminal 1 with near field communication capabilities, an NFC tag 2 carrying tag information, and a server 3 used for handling payment services. When the mobile terminal 1 approaches the NFC tag 2 and reaches a certain distance, it can trigger the NFC tag and obtain tag information contained in the NFC tag 2. The tag information may include payment link information used to display a payment page, and the mobile terminal 1 can display the payment page based on the obtained tag information. A user can enter information such as the payment amount on the payment page, and the terminal 1 can send a payment request including the payment information to the server 3. The server 3 can process the payment request and complete the payment.

[0029] Next, a payment method based on short-range wireless communication provided by an embodiment of the specification will be specifically described with reference to the drawings.

[0030] 2 is a flow diagram of a payment method based on near field communication provided by an embodiment of this specification. From a program perspective, the execution entity of the flow may be an application server, a program installed in a terminal application, or an application client.

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

[0032] Step 202: A mobile terminal with near field communication capability emits an electromagnetic signal used to trigger an NFC tag.

[0033] NFC (Near Field Communication) is a type of near-field wireless communication technology, and mobile terminals may have NFC near-field wireless communication capabilities. Mobile terminals may include mobile terminals, such as handheld and wearable terminals, such as mobile phones and smart watches. Near-field wireless communication, also known as short-range wireless communication, is a type of short-range high-frequency wireless communication technology that allows contactless point-to-point data transmission and data exchange between electronic devices. In the embodiments of this specification, the NFC tag may be a type of passive electronic tag or electronic chip that, when approached by a mobile device with near-field wireless communication capabilities, generates an induction signal and transmits data to the mobile device. After turning on the near-field wireless communication capability, the mobile device can transmit an electromagnetic signal to activate the NFC tag within a preset distance and transmit data. A specific NFC communication process can refer to conventional NFC communication technologies, and therefore will not be described in detail here.

[0034] Step 204: Obtain tag information of the NFC tag responsive to the electromagnetic signal, where the tag information includes payment link information.

[0035] The tag information to be transmitted may be written in advance in the NFC tag. In the embodiment of the present specification, the tag information may include link information used to make a payment, such as a payment application that needs to be called and payment link information, and the mobile terminal may call and display a payment page according to the acquired tag information.

[0036] Step 206: Based on the payment link information, display a payment page including the user information of the first business partner.

[0037] The first transaction partner can be understood as the party to which the NFC tag belongs. If the NFC tag is a deposit tag, the first transaction partner can represent the depositing party, and if the NFC tag is a withdrawal tag, the first transaction partner can represent the withdrawing party. The tag information in the NFC tag can be generated based on the transaction partner information provided by the first transaction partner. In practical application, payment link information used to call up a payment page according to the NFC communication protocol can be written into the NFC tag.

[0038] Step 208: Obtain the payment information provided by the second business partner based on the payment page.

[0039] The second transaction partner and the first transaction partner may represent the parties in a transaction relationship. As described above, if the NFC tag is a deposit tag, the first transaction partner may represent the depositing party, and the second transaction partner may represent the withdrawing party. If the NFC tag is a withdrawal tag, the first transaction partner may represent the withdrawing party, and the second transaction partner may represent the depositing party. The payment page may include an area for entering or selecting payment information, such as the payment amount and payment method, and the transaction information may be entered according to actual transaction needs. The payment page in the embodiments herein may be the same as or similar to a conventional payment page entered by scanning a payment code, such as a two-dimensional code, with a terminal. The user can provide payment information according to conventional operating methods, which can be more tailored to the user's habits. In actual applications, the layout, format, and content of the payment page may be set according to actual needs, but are not specifically limited herein. For example, in actual applications, the first transaction partner may set the transaction amount information, or the second transaction partner may set the transaction amount according to actual transaction needs. In this way, the payment page may include transaction amount information set by the first or second customer according to the withdrawal amount required, and the second customer may perform an operation indicating confirmation of the transaction information, such as clicking a confirmation control, or if the user does not cancel the payment after a preset period of time, such as a 3-second or 5-second countdown, for example, does not click a cancel control, this may indicate that the second customer has confirmed the information on the payment page, and the terminal may then obtain payment information including the transaction amount information.

[0040] As can be understood, the second transaction partner may perform several substantive operations on the payment page. For example, the second transaction partner may click a control indicating confirmation, enter a payment amount, and select or confirm a payment method, thereby performing a substantive operation on the payment page. The second transaction partner may also perform a non-substantive operation on the payment page. For example, the payment page may display countdown information. Alternatively, the payment page may not display countdown information, but a countdown program may run in the background of the terminal. If the user does not operate the payment page, for example, does not perform a payment cancellation operation, before the countdown ends, this may indicate that the user agrees to the payment or that the user has confirmed the payment information. Here, if the user does not perform a payment cancellation operation, this may indicate that the user has not performed a substantive operation on the payment page, or that the user's operation on the payment page is an inaction type operation. That is, in the embodiments of the present specification, the step of obtaining payment information provided by the second transaction partner on the payment page may include, but is not limited to, a step of obtaining payment information provided by a substantive operation or a non-substantive operation performed by the second transaction partner on the payment page.

[0041] Step 210: Send a payment processing request including the payment information to a server, and the server is used to complete the payment according to the payment processing request.

[0042] The mobile terminal can generate a payment processing request according to the payment information provided by the user and send it to the server, so that the server can process a complete payment service based on the received payment processing request. The payment processing request may include payment information such as merchant information, transaction amount, and transaction method, so that the server can complete payment for both parties in the transaction. In practical application, the payment method or transaction method can include a payment account number provided by a financial institution, such as a bank card account number of a bank, and can also include a payment account number of a third-party payment application, such as a payment account number corresponding to a second merchant in a third-party payment application, and can also include a payment account number of another user associated with the second merchant, such as a family number payment.

[0043] It should be understood that the order of some steps in the method described in one or more embodiments herein may be interchanged according to actual needs, or some steps may be omitted or deleted. For example, to further improve payment efficiency, if the tag information of the NFC tag includes payment information, for example, if the first customer writes 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 flow 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.

[0044] In the method of FIG. 2, the mobile terminal can obtain payment link information from the NFC tag via near field communication. The mobile terminal can display a payment page based on the information, and the user can enter payment information, such as the payment amount, on the payment page to complete the payment. In this way, the user does not need to find a payment application and then perform the corresponding payment operation in the payment application. For example, in a scenario where a payment needs to be made by scanning a payment code, the user does not need to find a payment application and then select a code scanning function in the payment application. In the embodiment of this specification, the mobile terminal can display a payment page based on the information from the NFC tag, simplifying user operations and improving the user experience.

[0045] Common NFC payment solutions in the prior art, such as NFC card reading payment on buses and subways, simulate a mobile terminal such as a mobile phone as an NFC card, and use NFC short-range wireless communication technology to send information on the NFC card to a payment device, such as a bus card reader or a subway ticket gate, and then complete the payment through the payment device. However, the payment device needs to be installed in a specific location, and the cost is relatively high because the payment device is equivalent to an NFC card reader.

[0046] In practical applications, most mobile terminals are equipped with near field communication functions and include near field communication modules. In the embodiments of this specification, the mobile terminal corresponds to an NFC card reader, and the NFC tag may be a passive electronic tag. The payment process can be simplified by utilizing the functions of the mobile terminal itself. The NFC tag has a small volume and can be conveniently placed at the location where payment is required. This eliminates the need to modify or overmodify existing hardware devices, resulting in low costs, a wide range of applications, and a wider range of applications.

[0047] In addition, in the embodiments of this specification, a payment page can be displayed when a mobile terminal approaches an NFC tag carrying payment information through near field communication, and when a user provides payment information on the payment page, the payment page may be the same as the payment page that appears when the user scans a code on the terminal. For the server in the payment request state, the existing processing link can be used to process the payment request, eliminating the need to build a new service processing link, which can reduce the developer's workload and server overhead, thereby accelerating the implementation of NFC communication payment methods.

[0048] Based on the method of FIG. 2, examples of the present specification are described below to further provide some specific implementation solutions of the method.

[0049] In practical application, payment can be made through a payment application having a payment function in a mobile terminal. Optionally, in the embodiments herein, the tag information can include instruction information used to launch the payment application, and display a payment page including user information of the first business partner based on the payment link information. The step of displaying a payment page associated with the first business partner specifically includes: launching the payment application in the mobile terminal based on the instruction information; and displaying the payment page associated with the first business partner based on the launched payment application.

[0050] The payment application may represent a terminal application having a payment function, wherein the mobile terminal may obtain command information used to launch the payment application in the tag information through short-range wireless communication, and then launch the payment application in the terminal, and then display a payment page based on the launched payment application, and the payment page may represent an application page of the payment application.

[0051] The instruction information may include an application identifier of the payment application to be launched, and the terminal can determine the payment application according to the application identifier after reading the instruction information. In practical application, it can further determine whether the payment application exists in the terminal, and if not, generate prompting information indicating payment failure, or generate prompting information to prompt the user to download and install the payment application. If it exists, the payment application can be launched.

[0052] In practical application, the NFC tag information may include information used to represent the processed service. For example, it may include information used to display a payment page, and the mobile terminal can display the payment page according to the tag information. Optionally, in the embodiments herein, the tag information may include request identification information used to request acquisition of payment page information. Displaying the payment page based on the launched payment application specifically includes: generating a payment page information acquisition request according to the request identification information, sending the payment page acquisition request to the server, acquiring payment page information generated by the server based on the payment page acquisition request, the payment page information including user information of the first merchant, and displaying the payment page including user information of the first merchant based on the payment page information.

[0053] The tag information may include information about the first merchant, such as merchant identification information, and may also include token information requesting the server to provide information required for the payment page. The mobile terminal or the launched payment application can send a request to the server to obtain the payment page information. The server can generate the payment page information based on the user information of the first merchant and provide it to the mobile terminal. The mobile terminal can then render and display the payment page based on the obtained payment page information. In practical application, the payment page information may 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 information such as the name, nickname, and account identifier of the first merchant, the mobile terminal can add information about the first merchant to the page template, determine the payment method used by the user logging in to the mobile terminal, and add the payment method information to the page template, thereby generating and displaying the payment page.

[0054] In actual applications, the payment page may include information about the first customer, such as the name of the business, the depositor's nickname, part of the deposit account number, and the depositor's name, and may further include an area used to enter or select the payment amount, and may further include controls used to determine the payment information, such as a commit control and a payment confirmation control.In actual applications, after the user commits the payment information, a payment password input page may be displayed, allowing the user to enter the password and make the payment.

[0055] To ensure the security of the payment, in embodiments of the present specification, the transaction partner can be further verified. Optionally, in embodiments of the present specification, the tag information can include user identification information of the first transaction partner, such as depositor information and business operator information. The method in embodiments of the present specification can further include determining whether the first transaction partner has transaction authorization based on the user identification information and obtaining a determination result. The step of displaying a payment page including the user information of the first transaction partner specifically includes displaying a payment page including the user information of the first transaction partner if the determination result indicates that the first transaction partner has transaction authorization.

[0056] In practical applications, the legitimacy and compliance of trading partners can be verified. A server with verification functionality may store information on authorized trading partners, such as a list of authorized trading partners, and determine whether a first trading partner is an authorized trading partner or whether the first trading partner is on the list of authorized trading partners. If yes, it can be determined that the first trading partner is authorized to trade. Furthermore, a third party can authenticate the trading partner's compliance, etc. The specific authentication method is not specifically limited herein.

[0057] In the prior art, payment codes such as two-dimensional codes are typically placed on checkout counters or attached to locations convenient for users to make payments, and may be carried by the business owner. In embodiments of the present specification, the NFC tag can be attached to an existing payment code stand, for example, attached or placed in a location that does not affect two-dimensional code recognition, such as behind or to the side of a two-dimensional code image, and an independent carrier can be installed to hold the NFC tag. Optionally, in embodiments of the present specification, the NFC tag can be located in a carrier that includes the payment code of the first transaction customer, or in a carrier that does not include the payment code of the first transaction customer. A payment code can be understood as a scannable payment code image in an image format, such as a common two-dimensional code.

[0058] Because the volume of the NFC tag is relatively small, in the embodiments of the present specification, the NFC tag can be placed in any position that is convenient for the user to make a payment. For example, it can be placed on the back of the payment code carrier or on the front side where it does not affect the payment code. When the user brings their mobile terminal close to or near the carrier, the payment flow can be entered and a payment page can be displayed. Furthermore, an NFC payment stand can be installed, which may include an NFC payment identifier. When the user brings their mobile terminal close to or near the payment stand, the payment flow can be entered and a payment page can be displayed.

[0059] In practical applications, before making a payment, a user may use the mobile terminal to process other services, such as watching videos, playing games, reading e-books, reading news articles, or communicating with other users using instant messaging. In embodiments herein, the user can make a payment without having to log out of the current application they are using before making a payment. Optionally, in embodiments herein, upon obtaining tag information from an NFC tag containing payment link information, if the mobile terminal is displaying an application page of a second application, the step of displaying a payment page associated with the first transaction partner may specifically include the step of overlaying and displaying the payment page on top of the application page of the second application.

[0060] In practical application, the payment page can be displayed in a part or the whole area on the application page of the second application.

[0061] Optionally, the method in the embodiments of the present specification may further include: obtaining a logout operation on the payment page of the second transaction destination; and switching to and displaying an application page of the second application based on the logout operation.

[0062] The payment page may include controls used to indicate logging out of the payment page, such as a payment confirmation control and a close control. A user may log out of the payment page by operating on the controls, or by performing a preset operation on the payment page, such as a swipe operation in a preset direction, such as a left swipe, a right swipe, an up swipe, or a down swipe. In the embodiments of the present specification, after logging out of the payment page, the application page displayed on the terminal before making the payment can continue to be displayed, further improving the user experience.

[0063] In some embodiments of the present specification, after a user commits payment information or enters a payment password, a page showing a transaction result may be displayed, where the transaction result page may be superimposed on all or part of the application page of the second application, and may include a control for logging out or closing the page. After logging out or closing the page, the application page of the second application may continue to be displayed.

[0064] In practical application, after obtaining the information representing the transaction result, the mobile terminal can further generate presentation information representing the transaction result, such as a short message and a prompt sound, and can display the presentation information based on the application page of the second application.

[0065] In practical application, when a business operator allows payment using multiple payment applications, the mobile terminal may further display a page for the user to select a payment application after approaching or being close to the NFC tag, so that the user can select a payment application and make a payment. Optionally, in an embodiment of the present specification, the tag information may include first trigger information, which is used to trigger the mobile terminal to determine a terminal application having a payment function on the mobile terminal and generate an application selection page. The method in the embodiment of the present specification may further include: determining a terminal application having a payment function on the mobile terminal in response to the first trigger information; generating an application selection page based on the terminal application having the payment function; and displaying the application selection page.

[0066] The application selection page may include application identifiers, such as icons, of terminal applications having payment functions, and may display the terminal applications after sorting them according to the time they were launched, with terminal applications that the user has used most recently being sorted at the top.

[0067] Optionally, in an embodiment of the present specification, after the step of displaying the application selection page, the method may further include a step of obtaining a target terminal application selected by the second business partner from the application selection page. The step of displaying a payment page including transaction information of the first business partner based on the payment link information may specifically include a step of employing the target terminal application to access the payment link information, and a step of displaying a payment page including transaction information of the first business partner in the target terminal application.

[0068] Similar to the display manner of the payment page or transaction result page, if the mobile terminal is using the second application before acquiring tag information from the NFC tag, the application selection page may be superimposed on all or part of the application page of the second application, and may be used for controlling or presetting the page to log out or close the page, and the application page of the second application may continue to be displayed after logging out or closing the page.

[0069] In practical application, the payment page, transaction result page, and application selection page, as well as the payment flow related pages, may be displayed above the application page of the second application in a semi-transparent or non-transparent manner.

[0070] In practical applications, the mobile terminal may have a near field communication function and may further include components such as a camera used to scan payment codes. In order to avoid user interruptions and minimize resource consumption, the user can simply turn on a code scanning function, for example, enter the code scanning function of a payment application, and scan the payment code with the terminal to make a payment without activating the NFC payment process. Optionally, in the embodiments herein, before the step of acquiring tag information of the NFC tag responsive to the electromagnetic signal, a step of determining whether the mobile terminal has launched a code scanning application program used to scan a payment code image can be included. The step of acquiring tag information of the NFC tag responsive to the electromagnetic signal specifically includes the step of acquiring tag information of the NFC tag responsive to the electromagnetic signal if the code scanning application program has not been launched.

[0071] In practical applications, the mobile terminal launches a code scanning application program used to scan a payment code image; for example, when a user clicks "Scan" or other control for code scanning in the payment application, the camera of the mobile terminal is activated, and may not read the information on the NFC tag, and may not execute a flow that the information on the NFC tag can trigger.

[0072] As can be understood, in the embodiments of the present specification, the method of triggering the payment flow through the near field communication method needs to be based on the user's authorization, for example, the user agrees to turn on the NFC payment method, and user information within the user's authorization range can be obtained and used for payment.

[0073] To more clearly explain the payment method based on near field communication provided in the embodiments of the present specification, Fig. 3 is a swimlane diagram of the payment method based on near field communication provided in the embodiments of the present specification. As shown in Fig. 3, the solution may include an NFC information transmission step and a payment processing step, and specifically, may include steps 302 to 322.

[0074] Step 302: A mobile terminal with a near field communication function transmits an electromagnetic signal to trigger an NFC tag, where the mobile terminal can turn on the NFC function and transmit an electromagnetic signal to trigger an NFC electronic tag or chip within a preset distance to establish near field communication.

[0075] Step 304: When the mobile terminal approaches or is close to the NFC tag, it can establish near field communication with the NFC tag, and the NFC tag can transmit tag information to the mobile terminal.

[0076] Step 306: The mobile terminal can obtain tag information of the NFC tag responsive to the electromagnetic signal, the tag information including payment link information, which may include identification information of the first customer, such as a user ID, and may further include payment link information used to trigger a payment flow, which can launch a payment application in the mobile terminal and display a payment page.

[0077] Step 308: Generate a payment page information acquisition request based on the payment link information and send it to the server. Here, the payment link information may include link information for launching a payment application, and the mobile terminal can launch the corresponding payment application and then send a payment page information acquisition request to the server based on the payment application. The request may include identification information of the first transaction partner, such as business operator identification information, and may also include the terminal identifier of the mobile terminal or the application user identifier of the user who logged in to the payment application on the mobile terminal, so that the server can determine the party to conduct the transaction and generate payment page information.

[0078] Step 310: The server can generate payment page information according to the acquisition request sent by the mobile terminal, and feed it back to the mobile terminal.

[0079] Step 312: The mobile terminal can display a payment page according to the acquired payment page information. The payment page may include an area for the user to enter payment information such as a payment amount and a payment method.

[0080] 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.

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

[0082] Step 318: The server can obtain the payment processing request sent by the mobile terminal, and process the transaction based on the transaction information, such as the transaction amount and both transaction information included in or corresponding to the payment processing request.

[0083] Step 320: The server can further generate a transaction result and feedback it to the mobile terminal.

[0084] Step 322: The mobile terminal can display the transaction result information according to the transaction result fed back by the server.

[0085] In the prior art, a user can enter a payment page by scanning a code on a terminal, but in the embodiment of the present specification, the payment page can be called up by NFC near field communication, which simplifies user operations. Simply put, the NFC tag in the embodiment of the present specification may include information used to conduct a transaction, such as a merchant identifier and a token that triggers a payment flow, which is carried in the payment code in the prior art.

[0086] In conventional payment methods, the mobile terminal may also be scanned, for example, by displaying a payment code on the mobile terminal and scanning it with a payment device to complete the payment. In conventional methods, the user needs to open a payment application, find the payment code, and display the payment code. For example, even if the user is using another application before making a payment, the user needs to log out of the application and then find the payment application to make the payment, which requires a relatively large number of steps for the user. In order to simplify the user's operation steps and improve the user experience, another payment method based on near field wireless communication is also provided in the embodiments of the present specification.

[0087] FIG. 4 is a schematic diagram of an application scenario of a payment method based on near field communication in an embodiment of the present specification. As shown in FIG. 4, the solution may include a mobile terminal 1 with near field communication capabilities, an NFC tag 2 carrying tag information, a payment instrument 3 associated with the NFC tag, and a server 4 used for handling payment services. When the mobile terminal 1 approaches the NFC tag 2 and reaches a certain distance, it can trigger the NFC tag and acquire tag information contained in the NFC tag 2. The tag information may include information used for triggering a payment flow. Based on the acquired tag information, the mobile terminal 1 can send a request for acquiring transaction identification information to the server 4. The server 4 can then feed back transaction identification information representing user payment account information of the mobile terminal 1 to the mobile terminal 1. The mobile terminal 1 can transmit the transaction identification information to the payment instrument 3 via NFC communication, and the server 4 can also transmit the transaction identification information to the payment instrument 3 via network transmission. After obtaining the transaction identification information, the payment instrument 3 can send a payment processing request to the server 4, which can then process the payment service between the mobile terminal user and the user to which the payment instrument belongs. Based on the above scenario, Figure 5 is a flow diagram of a payment method based on near field communication provided by an embodiment of this specification. From a program perspective, the execution entity of the flow may be an application server, a program installed in a terminal application, or an application client.

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

[0089] Step 502: A mobile terminal with near field communication capability emits an electromagnetic signal used to trigger an NFC tag.

[0090] Similar or equivalent to the principles of the above embodiments, the mobile terminal may include mobile terminals such as handheld and wearable terminals, for example, mobile phones and smart watches. Near field communication, also known as short-range wireless communication, is a type of short-range high-frequency wireless communication technology that allows contactless point-to-point data transmission and data exchange between electronic devices. In the embodiments of this specification, the NFC tag may be a type of passive electronic tag or electronic chip that, when approached by a mobile device with near field communication capability, generates an induction signal and transmits data to the mobile device. After turning on the near field communication capability, the mobile device can transmit an electromagnetic signal to activate the NFC tag within a preset distance and transmit data. The specific NFC communication process can refer to conventional NFC communication technologies, and therefore will not be described in detail here.

[0091] Step 504: Obtain tag information of the NFC tag that responds to the electromagnetic signal, and the tag information is used to trigger a payment flow.

[0092] The tag information may include information used to trigger the payment flow, such as information for launching a payment application and carrier information, and the mobile terminal can obtain the information in the NFC tag through short-range communication and trigger the execution of the payment flow.

[0093] Step 506: According to the tag information, obtain transaction identification information used to represent the user payment account information in the mobile terminal.

[0094] The transaction identification information can be used to determine a user payment account in the mobile terminal. If the tag information included in the NFC tag is a payment flow used for withdrawing money, the account can be a withdrawal account; if the tag information included in the NFC tag is a payment flow used for depositing money, the account can be a deposit account, and there are no specific limitations here. In practical application, a user can make a payment by using a terminal application with a payment function in the mobile terminal, and the user payment account can be the user account logged in to the terminal application.

[0095] Step 508: Send the transaction identification information to a payment instrument associated with the NFC tag, and the payment instrument is used to execute a payment flow according to the transaction identification information.

[0096] A payment instrument can be understood as an instrument that can send a transaction request to a server that processes the transaction, and may be equipped with a program or terminal application used to execute the payment flow. In practical applications, the payment instrument can represent another merchant's instrument that transacts with a user of a mobile terminal, and specifically can include a cash register instrument, a self-checkout instrument, etc. The payment instrument may include an NFC tag, or the NFC tag may include an instrument identifier of the payment instrument, so that the payment instrument and the NFC tag have a correspondence relationship. In practical applications, the payment instrument can further send a payment processing request to a server that processes the payment request according to the payment flow, and the server then completes the payment transaction between the two parties.

[0097] In a scenario where money is withdrawn using a mobile device, the mobile terminal can represent the withdrawing device, and the payment device can represent the depositing device. In a scenario where money is deposited using a mobile device, the mobile terminal can represent the depositing device, and the payment device can represent the withdrawing device.

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

[0099] In the method of Figure 5, the mobile terminal obtains tag information used to trigger a payment flow from the NFC tag via near field communication, obtains transaction identification information, and transmits it to the payment device to make a payment. In this way, the user can find a payment application and does not need to perform a corresponding payment operation in the payment application. For example, in a scenario where a payment code needs to be presented and scanned by the payment device to make a payment, the user does not need to find a payment application and select and display the payment code in the payment application. In the embodiment of this specification, the mobile terminal can transmit transaction identification information for payment to the payment device based on the information in the NFC tag, which simplifies user operations and improves the user experience.

[0100] To ensure the security of payment, the mobile terminal can request the server to generate transaction identification information according to actual transaction needs. The transaction identification information in different payment processes may be different. Optionally, in the embodiments of the present specification, the step of obtaining transaction identification information used to represent user payment account information of the mobile terminal based on the tag information specifically includes the steps of sending a payment information obtaining request to a server, the payment information including user identification information of the mobile terminal, and obtaining the transaction identification information generated by the server based on the user identification information.

[0101] Here, the user identification information may be a user ID, a device identifier of a mobile terminal, or identification information that can be used to determine a user payment account, such as a user application identifier in a user's terminal application. The server can determine a user payment account according to the user identification information and generate transaction identification information corresponding to the user payment account, so that the user payment account can be used to process a payment transaction according to the transaction identification information. In practical application, the transaction identification information may be a string such as a withdrawal code number and a transaction order number, and the server can process both sides of the transaction according to the transaction identification information.

[0102] In the embodiment of the present specification, transmitting the transaction identifier to the payment device may be performed by a short-range wireless communication method or a network method. In one embodiment, in the embodiment of the present specification, transmitting the transaction identification information to the payment device specifically includes transmitting the transaction identification information to the payment device by a short-range wireless communication method.

[0103] The payment device may have an NFC function, for example, an NFC module, and may receive data transmitted via a short-range wireless communication scheme. The mobile terminal may transmit transaction identification information to the payment device via a short-range wireless communication scheme. Here, the step of transmitting the transaction identification information to the payment device via a short-range wireless communication scheme may specifically include the steps of writing the transaction identification information to the NFC tag and feeding back the transaction identification information to the payment device via the NFC tag via a short-range wireless communication scheme.

[0104] Here, the channel mode of the NFC tag is adopted, and the transaction identification information can be written into the NFC tag and then directly and transparently transmitted to the payment device, and the transaction identification information does not need to be stored in the NFC tag.

[0105] As another embodiment, in the examples of the present specification, the tag information may include a device identifier of the payment device, and the step of sending the transaction identification information to the payment device specifically includes a step of sending a payment request including the device identifier to a server, where the server generates the transaction identification information and is used to send the transaction identification information to the payment device according to the device identifier.

[0106] In the embodiments of the present specification, the server may generate transaction identification information and further transmit the information to the payment device. In practical applications, near-field communication requires a relatively short distance between the mobile terminal and the NFC tag, and data transmission requires a certain time, which may be 1 second, 2 seconds, or 3 seconds. If the time period during which the distance between the mobile terminal and the NFC tag is within a preset range is relatively short, the transaction identification information may not be transmitted via near-field communication. Therefore, to ensure that the transaction is carried out normally, the server may further transmit the transaction identification information to the payment device.

[0107] In practical applications, the above two transmission methods may be implemented in both ways or simultaneously, and the payment device can obtain the transaction identification information through any method. Since the transaction identification information transmitted through the two transmission methods is the same and can be used only once, the entire payment system can ensure idempotence and the normal execution of the transaction. If the payment device does not have the ability to obtain information transmitted through the short-range wireless communication method, the transaction identification information can be sent to the payment device through a service.

[0108] Similar to the above embodiment, in this embodiment, the tag information may include first link information used to launch a payment application on the mobile terminal. The method in this embodiment may further include launching the payment application based on the first link information, and the step of obtaining transaction identification information used to represent user payment account information on the mobile terminal may specifically include obtaining the transaction identification information based on the launched payment application.

[0109] The tag information may include an identifier of a designated payment application, and the mobile terminal can launch the designated payment application after obtaining the tag information and make a payment based on the payment application, where the transaction identification information may be transaction identification information that the payment application sends a request to a server and that the server feeds back to the payment application.

[0110] To improve the user's sense of security regarding payments, embodiments of the present specification may further generate presentation information, which is used to prompt the user to launch a payment application on the mobile terminal and use the payment application to make a payment. Optionally, embodiments of the present specification may further include, after the step of launching the payment application, a step of displaying presentation information, which is used to indicate that the payment application has been launched. Here, the presentation information may specifically include presentation information in the form of vibration, sound, text, image, etc., and may further include an on-page display of the payment application, so that the user can sense that the payment application has been launched.

[0111] In practical application, the presentation information may be displayed on top of or in a partial area of ​​the currently displayed page of the mobile terminal, and the user can further perform a preset operation to close the presentation information, and the terminal can continue to display the currently displayed page.

[0112] In practical application, the payment application may be run in the background of the mobile terminal, and may be invisible to the user, thus reducing the user's interruption, for example, when the user is using another application on the mobile terminal, and thus avoiding interrupting the user's use of the application, thereby reducing the user's interruption.

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

[0114] Here, the transaction result information may be result information obtained by the server processing the payment processing request including the transaction identification information transmitted by the payment device, or may be information indicating the success or failure of the transaction. The process by which the server processes the payment processing request may be the same as a conventional process, and a detailed description thereof will be omitted here.

[0115] Similar to the above embodiment, in a practical application, a user may use the mobile terminal to process other services, such as watching videos, playing games, reading e-books, reading news articles, or communicating with other users using instant messaging, before making a payment. In the embodiment herein, the user can make a payment without having to log out of the current application they are using before making a payment. Optionally, in the embodiment herein, if the mobile terminal is displaying an application page of a second application when acquiring tag information of the NFC tag, the step of displaying a transaction result page may specifically include a step of superimposing and displaying the transaction result page on top of the application page of the second application.

[0116] In practical application, the transaction result page can be displayed in a part or the entire area on the application page of the second application.

[0117] Optionally, the method in the embodiments of the present specification may further include the steps of obtaining a logout operation for the transaction result page, and switching to and displaying an application page of the second application based on the logout operation.

[0118] Similar to the transaction result page in the above embodiment, the transaction result page in this embodiment may include controls used to display a logout page, such as a confirmation control and a close control. A user may log out of the payment page by operating on the controls, or by performing a preset operation on the page, such as a swipe operation in a preset direction, such as a left swipe, a right swipe, an up swipe, or a down swipe. In the embodiment of the present specification, after logging out of the transaction result page, the application page displayed on the terminal before making the payment can continue to be displayed, further improving the user experience.

[0119] In practical application, if the payment device has a code scanning function, it can scan the payment code, such as a withdrawal code, displayed on the mobile terminal. In embodiments of the present specification, the mobile terminal can also display a payment code page based on near-field communication, simplifying the user's operation of opening a payment application and then opening the payment code page. Optionally, the method in embodiments of the present specification may further include generating a payment code image based on the transaction identification information and displaying the payment code image, and the step of transmitting the transaction identification information to the payment device specifically includes transmitting the transaction identification information to the payment device with a code scanning function via the payment code image.

[0120] In the embodiments of the present specification, the payment device may include devices with code scanning capabilities, such as POS machines, code scanning boxes, and code scanning guns. In such embodiments, payment identification information can be obtained according to tag information in an 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 may be simply understood as payment information included in a conventional payment code, such as a withdrawal code digit in a withdrawal code. In the examples of the present specification, the generated payment code image may be the same as or have the same function as the payment code image generated by a withdrawal code control in a mobile terminal, and the payment device can process the payment service according to a conventional payment flow by scanning the code image.

[0121] In the embodiments of the present specification, the payment flow executed by the payment instrument after obtaining transaction identification information may be the same as the traditional payment flow executed after obtaining transaction identification information through code scanning, and the existing flow can be used to perform service processing, eliminating the need to develop a new processing flow, thereby saving resources and reducing the developer's workload.

[0122] To more clearly explain the payment method based on near field communication provided in the embodiments of the present specification, Fig. 6 is a swimlane diagram of the payment method based on near field communication provided in the embodiments of the present specification. As shown in Fig. 6, the method may include an NFC information transmission step and a payment processing step, and specifically, may include steps 602 to 618.

[0123] Step 602: A mobile terminal with a near field communication function transmits an electromagnetic signal to trigger an NFC tag, where the mobile terminal can turn on the NFC function and transmit an electromagnetic signal to trigger an NFC electronic tag or chip within a preset distance to establish near field communication.

[0124] Step 604: When the mobile terminal approaches or is close to the NFC tag, it can establish near field communication with the NFC tag, and the NFC tag can transmit tag information to the mobile terminal. The tag information may include information used to trigger a payment flow. Here, the NFC tag is described as being located in the payment device. In actual application, the NFC tag may be located separately from the payment device, but this is not a specific limitation.

[0125] Step 606: The mobile terminal can obtain tag information of the NFC tag responsive to the electromagnetic signal, which may include identification information of the first transaction partner, such as a user ID, a business identifier, and business authorization information, and may further include information used to activate a payment application on the mobile terminal.

[0126] Step 608: The mobile terminal obtains transaction identification information used to represent the user payment account information of the mobile terminal according to the tag information. The transaction identification information may be generated by the server according to the user information of the mobile terminal and fed back to the mobile terminal.

[0127] Step 610: Send the transaction identification information to the payment instrument. Here, the transaction identifier can be sent to the payment instrument according to one or both of the above two methods. Step 612: The payment instrument can generate a transaction processing request based on the transaction identification information and send it to the server. The transaction processing request may include the payment instrument identifier or the identifier of the user of the payment instrument, and may also include the transaction amount, and may also include information such as a deposit account.

[0128] Step 614: The server can receive the transaction processing request sent by the payment instrument and complete the transaction between the merchants corresponding to the request. Step 616: The server can generate a transaction result and feed it back to the mobile terminal, and then feed it back to the payment instrument. Step 618: The mobile terminal can display transaction result information according to the transaction result fed back by the server. Information representing the transaction result may be displayed on the payment instrument.

[0129] In this embodiment, the tag information may include a payment instrument identifier or an identifier of the business operator to which the payment instrument belongs. The payment instrument may be verified based on the identifier to determine whether the payment instrument has transaction authorization. Only when the payment instrument has transaction authorization can transaction identification information be obtained. The specific verification process may be the same as or similar to the above embodiment, and will not be described in detail here.

[0130] Based on a similar idea, FIG. 7 is a flow diagram of a payment method based on near field communication provided in an embodiment of the present specification. As shown in FIG. 7, the solution may include the following steps 702 to 714:

[0131] Step 702: The mobile terminal obtains tag information of an NFC tag associated with the payment instrument.

[0132] Here, the mobile terminal may be a mobile terminal with near field communication capabilities, and the tag information may include information used to trigger a payment flow. In practical applications, the mobile terminal may approach an NFC tag, for example, a payment device having an NFC tag, and acquire tag information from the NFC tag. The NFC tag may be associated with the payment device, for example, located within the payment device, or may be located separately from the payment device. The payment device may represent a device with payment processing capabilities, such as a POS machine, a container, a cash register system associated with a cash register system, a self-payment device, etc., or another mobile terminal with NFC capabilities, such as a mobile phone or a smart watch. The specific form of the payment device is not specifically limited here, and the payment device may be referred to as an NFC device, a device having an NFC tag, or a device with NFC capabilities.

[0133] In this specification, the mobile terminal may be a card reader, and when the NFC switch is turned on, it may always emit an LPCD signal, or it may be a mixture of LPCD and normal card search. When the mobile terminal approaches an NFC tag, for example, by touching or bumping against a payment device, the tag coil in the NFC tag will affect the amplitude or phase of the LPCD signal of the mobile terminal. The mobile terminal determines that there is a tag nearby according to this effect, and then initiates an inquiry and enters into a dialogue process. Specifically, this may be a command dialogue or a data dialogue, for example, the mobile terminal can obtain information from the NFC tag. For specific NFC, please refer to the related art, and a detailed description will be omitted here.

[0134] Step 704: Based on the tag information, launch a payment application in the mobile terminal.

[0135] The tag information may include information used to launch a payment application. Specifically, it may include an identifier representing the payment application, such as a package name of the payment application, and the mobile terminal can launch the payment application based on the identifier. In practical application, the mobile terminal's OS (Open System) can call the corresponding terminal application app according to the application package name and provide at least some of the information in the acquired tag information, such as at least some of the URL, to the terminal application, thereby allowing the terminal application to execute a corresponding flow. For example, the tag information may also include jump page information, and after the mobile terminal launches the payment application, the payment application can acquire a URL for page jumping and perform the corresponding page jump according to the URL. Furthermore, for example, the tag information may also include a service identifier, such as a payment service. After the payment application is launched on the mobile terminal, the payment application can execute a corresponding processing flow according to the service identifier, such as sending a payment request to a server, triggering a payment processing flow of the server, or obtaining feedback information from the server.

[0136] Step 706: Send a payment processing request to the server based on the activated payment application.

[0137] The mobile terminal can send a payment request to the server based on the activated payment application. It may be understood that the payment application in the mobile terminal sends the payment request to the server. The payment request may include identification information of the payment account in the mobile terminal for payment. If the tag information includes payment information such as the payment amount, the payment request may also include payment information such as the payment amount. If the tag information includes information such as the device identifier of the payment device or the merchant identifier to which the payment device belongs, the payment request may also include this information.

[0138] Step 708: The server processes the payment service according to the payment processing request, and feeds back the payment result information.

[0139] In practical application, the server may process the payment service independently, or may interact with other devices during the process to complete the payment service. The specific process can be referred to in the above embodiment, and detailed description will be omitted here.

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

[0141] The transaction result page may also be referred to as a payment result page, and may be a page used to display transaction result information or payment result information. It can be understood that this embodiment and the above-mentioned embodiment are solutions based on the same technical idea, and some specific embodiments of this embodiment may be the same as those of the above-mentioned embodiment, and detailed descriptions thereof will be omitted here.

[0142] To more clearly explain this example and the payment methods provided in the above examples, some specific embodiments are further provided herein.

[0143] To improve the user experience and make the user aware that it is the response executed by the mobile terminal that is being used, further presentation information may be displayed on the mobile terminal before launching the payment application.

[0144] Optionally, as shown in FIG. 7, step 704 may specifically include step 7042 of displaying a payment submission page based on the tag information, step 7044 of obtaining the user's first preset operation on the payment submission page and generating first confirmation information, and step 7046 of launching a payment application in the mobile terminal based on the first confirmation information.

[0145] Here, the tag information may include link information used to display a payment offer page, and the mobile terminal can display the payment offer page by recognizing the link information. The payment offer page can also be displayed by accessing the link information using the terminal's browser. The payment offer page may include offer information used to offer to make a payment using the payment application. In actual application, the operating system of the mobile terminal may display the payment offer page based on a page identifier or code corresponding to the payment offer page included in the link information, or may send a request used to obtain the payment offer page to the mobile terminal's server, and feedback the payment offer page via the server.

[0146] In the embodiments of the present specification, the tag information acquired by the mobile terminal may include information used to launch a payment application, and may also include information used to display a page or to request a payment service feedback page from a server.

[0147] In one embodiment, the tag information may include identification information used to launch the payment application, such as an application package name, and may also include link information used to display the page, such as URL information. After obtaining the application identifier, the mobile terminal system can pull up or launch the corresponding payment application in the mobile terminal, and then provide the payment application with link information used to display the page, and the payment application can then display the page based on the link information.

[0148] In another embodiment, the tag information may include link information, such as a URL, which may include identification information of a payment application, such as an application package name. The link information URL may further include information used to display a page, such as information used to display a payment offer page. The mobile terminal can pull up or launch the payment application based on this link information, open the corresponding page, and display the page. The step of displaying a payment offer page based on the tag information specifically includes the step of displaying a payment offer page based on the link information.

[0149] If the mobile terminal is an iOS system, it can pull up the corresponding payment application based on the link information in the tag information, and then display a prompt page suggesting the user make a payment using the payment application. If the mobile terminal is an Android system, it can launch the corresponding payment application based on the application package name in the tag information, and then send the link information included in the tag information to the payment application for displaying the page. The payment application can generate a display page locally based on the link information, or generate the display page based on a server. In practical application, the specific format of the tag information can be set according to the operating system used by the mobile terminal, so that the mobile terminal can accurately recognize the tag information. For example, a universal tag information format can be set so that different operating systems can accurately recognize the tag information.

[0150] The first preset operation may be a click operation, a swipe operation, or an operation of tilting, flipping, or shaking the mobile terminal, and may also be a non-substantial operation. For example, the payment prompting page may include a control used to cancel a payment. If the user does not operate the control within a preset period, the user may indicate that he or she agrees to make a payment using the payment application. That is, after the preset period, the mobile terminal may generate first confirmation information. Here, the operation method is not specifically limited. The first confirmation information may indicate that the user agrees to make a payment using the payment application. After the user agrees, the terminal may launch the payment application.

[0151] 8 is a schematic diagram of a payment presentation page provided by an embodiment of the present specification. As shown in FIG. 8, the payment presentation page 800 may include presentation information 802 used to present a request to make a payment by employing payment application a. It may also include a confirmation control 804. If the user clicks the confirmation control 804, it can indicate that the user agrees to make a payment by employing payment application a, and the terminal can launch the payment application a.

[0152] If payment application a is not installed on the mobile terminal, or is installed but not registered or used by the user, the user can click the confirmation control 802 to jump to a download page used to download the payment application a client, or a page to register and use payment application a, so that after the user registers payment application a, they can make payments using payment application a.

[0153] Optionally, the payment prompt page may further include a download control 806 used to download the client of the payment application A. If the user clicks on the download control 806, the mobile terminal can jump to and display a download page used to download the client of the payment application A. In practical application, the mobile terminal can further determine whether the payment application A is installed on the mobile terminal, and if it is installed, the payment prompt page may not display the download control 806.

[0154] The payment offer page may further include offer information suggesting that the user make a payment using the NFC method. The payment offer page may occupy the entire area of ​​the display page of the terminal, or may be located in a partial area of ​​the display page of the terminal, such as the bottom, top, or middle, or may be displayed in a folded state. Figure 8 is merely an example, and the specific format of the payment offer page is not limited herein.

[0155] Thus, in the above step 2, the step of launching the payment application in the mobile terminal may specifically be a step of allowing the mobile terminal to launch the payment application if the user clicks on a confirmation control on the payment offer page. As can be understood, in actual application, the payment offer page may not be displayed, for example, if the payment security requirements are met or the user approves.

[0156] To improve user experience, in the payment method provided in the embodiment of the present specification, the mobile terminal can further display a page for the user to confirm payment information, so that the user can clearly know the payment status. Optionally, as shown in FIG. 7 , the embodiment of the present specification can further include, before displaying the transaction result page, step 712 of displaying a payment page including payment information, and step 714 of obtaining second confirmation information generated based on the user's second preset operation on the payment page.

[0157] Here, the payment information may be information related to payment, such as transaction amount information, customer information, transaction method, or payment method. The second preset operation may include a substantial operation performed on the payment page, such as clicking and swiping a control on the page, flipping and tilting the mobile terminal, etc., or may include a non-substantial operation performed on the payment page, such as not clicking a control on the payment page representing payment cancellation within a preset period.

[0158] The payment information may be included in the NFC tag. For example, a business may set the amount information required for payment by the payment device. For example, a cashier may set the amount at a POS machine or a checkout counter, or calculate the amount using a preset amount calculation program. For example, in an automatic payment device or a vending machine, a computer program can determine the amount required for the transaction and set the amount information in the NFC tag. The tag information acquired by the mobile terminal may include the payment information, or the payment information may be set by the user of the mobile terminal. The tag information may include a page identifier of a 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 an existing client program of the payment application in the terminal.

[0159] FIG. 9 is a schematic diagram of a payment page provided in an embodiment of the present specification. As shown in FIG. 9, the payment page may include an area 902 used to display payment information. Specifically, it may display payment amount information, as well as information such as the payment method, the customer, and the transaction time. The payment page may also include an operation control 904. When the user clicks on the control, the user agrees to make the payment, and the mobile terminal may generate confirmation information. In practical applications, the operation control may be a control used to confirm the payment or a control used to cancel the payment. For example, if the user does not click on the control representing payment cancellation within a preset period, it may indicate that the user agrees to make the payment. The mobile terminal may also generate confirmation information and perform subsequent processing. As shown in FIG. 9, the payment page may also include descriptive information 906 about NFC payment, which is useful for users to understand the benefits and usage of NFC payment.

[0160] 9 is merely an example, and in actual applications, the specific display content and style of the payment page can be set according to actual needs, but are not specifically limited here. If the user approves or meets security requirements, the payment page may not be displayed.

[0161] The second confirmation information may indicate that the user has confirmed the payment information and agreed to make the payment. In one embodiment, the second information may be used to trigger the sending of a payment processing request, and the step of sending the payment processing request to the server specifically includes the step of sending the payment processing request to the server based on the second confirmation information.

[0162] In an embodiment of the present specification, the server can generate transaction identification information used to represent user payment account information in the mobile terminal based on the payment processing request, and can further send the transaction identification information to the payment equipment, so that the payment equipment executes a payment flow based on the transaction identification information and completes the payment.

[0163] In one embodiment, as shown in FIG. 7, the above step 708 specifically includes step 7082, in which the server generates transaction identification information used to represent the user payment account information in the above mobile terminal based on the payment processing request; step 7084, in which the server sends the transaction identification information to the payment instrument; and step 7086, in which the payment instrument executes the payment flow based on the acquired transaction identification information.

[0164] In practical applications, the server may further perform step 7088 of generating payment result information based on the processing information generated when the payment instrument executes the payment flow.

[0165] In another embodiment, the server may send the transaction identification information to the mobile terminal, which may then send it to the payment device, or the mobile terminal may execute the payment process based on the transaction identification information, for example, without initiating a payment request to the server and having the payment device obtain the transaction identification information. For specific processes, please refer to the content of the above embodiment, and detailed descriptions will be omitted here.

[0166] Here, the transaction identification information may be a single character string. Specifically, it may be a character string that can be recognized by a server used to process the payment service and that conforms to the payment rules of the payment application. For example, it may be a character string starting with 28, 25, or 30. The length of the character string may be 16 to 24 bits, or may be any length that meets the needs. Therefore, the specific format of the character string is not specifically limited here. For related content of the transaction identification information, please refer to the related descriptions in the above embodiments.

[0167] The payment instrument may be an instrument associated with a server used to process payment services, and may transmit a payment request including transaction identification information to the server, and the server may process the payment request, and after processing is complete, may transmit information indicating payment completion directly or indirectly to the mobile terminal, and payment result information may be displayed on the mobile terminal.

[0168] In this specification, the term "server" may refer to a server corresponding to a payment application or may include a cash register system with cash register functions, such as a system associated with cash register counters, cash register devices, and self-payment devices installed in places such as supermarkets and shopping centers. In practical 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 depositing funds, the user payment account can represent a withdrawal account, and if the cash register system is used for withdrawing funds, the user payment account can represent a deposit account. The cash register system may also correspond to a transaction account. The cash register system can generate a transaction request based on the acquired user payment account and the transaction account corresponding to the cash register system and send it to the server, and the server can process the transaction request. For example, appropriate resources can be deducted from the user payment account and added to the transaction account corresponding to the cash register system. After the processing is completed, the server can feed back payment result information to the server. For specific transaction processing flows, please refer to the related art. The cash register system may process transactions according to conventional processing flows, and these will not be described in detail here.

[0169] In practical application, an NFC device server may be installed to manage the payment device, and the transaction identification information may be transmitted from the server to the NFC device server, and then transmitted from the NFC device server to the payment device. The NFC device server may be the same server as the server described above, and is not specifically limited herein.

[0170] In an embodiment of the present disclosure, a payment flow can be executed based on a payment instrument. In one embodiment, after launching a payment application, the mobile terminal can send a payment processing request to a server based on the launched payment application. The server can process the payment processing request, generate transaction identification information, and send it to the payment instrument. Second confirmation information generated based on the payment page can be a trigger signal that triggers the payment instrument to execute the payment flow based on the transaction identification information. Optionally, the present disclosure may further include, after launching the payment application on the mobile terminal, displaying a payment page including payment information, and acquiring second confirmation information generated based on a second preset operation of the user on the payment page, whereby the server sends a payment flow trigger instruction to the payment instrument after the second confirmation information, and the payment instrument can execute the payment flow based on the acquired transaction identification information based on the payment flow trigger instruction.

[0171] Here, after obtaining the second confirmation information, the mobile terminal can send corresponding information indicating that the user confirms the payment to the server, and the server can further send a payment flow triggering command to the payment instrument, and after obtaining the payment flow triggering command, the payment instrument can execute the payment flow based on the obtained transaction identification information.

[0172] In the embodiments of the present specification, after initiating a payment processing request, the mobile terminal can send the payment processing request to a server. The server can generate and send transaction identification information to the payment device. When the terminal displays the payment page, the server can generate and send the transaction identification information to the payment device, so that the payment device can obtain the transaction identification information before the user performs a preset operation on the payment page. The payment device can temporarily store the transaction identification information, and after the user performs a preset operation on the payment page, the payment device can execute the payment flow based on the obtained transaction identification information, so that there is no need to wait for the server to send the transaction identification information, and payment efficiency can also be improved.

[0173] Optionally, in an embodiment of the present specification, before displaying a payment page including payment information, the method may further include a step of determining whether a user of the mobile terminal meets preset payment conditions based on account information of the payment application in the mobile terminal, the preset payment conditions representing conditions under which fast payment can be made, and the step of displaying a payment page including payment information specifically may include a step of displaying a payment page including payment information if the user does not meet the preset payment conditions.

[0174] Here, fast payment can refer to a payment method that requires relatively few user operation steps, or a payment method that does not require the user to perform any operations. As described in the above embodiment, the mobile terminal can complete the payment through the NFC function and display the transaction result page, so that the user does not need to perform any cumbersome operations during the entire payment process.

[0175] If the user does not meet the preset payment conditions, i.e., cannot make a fast payment, a payment page can be displayed to the user, allowing the user to confirm the payment information. If the user meets the preset payment conditions, a transaction result page can be displayed. That is, the mobile terminal does not need to display the payment page before displaying the transaction result page.

[0176] In an embodiment of the present specification, it can be determined whether a user meets preset payment conditions according to user characteristics, where optionally, the preset payment conditions include at least one of: authorization to use an instant payment function; the user being a high-activity user of the payment application; and authorization to use a password-free payment function.

[0177] Here, the instant payment function can refer to a confirmation-free payment function. For example, pages such as the payment page and / or payment presentation page introduced above may not be displayed before the transaction result page, and this is a kind of extremely quick payment method that eliminates or reduces the user's related operations for payment confirmation. In practical application, a user can turn on the instant payment function in the relevant setting page of the payment application. If a user authorizes the use of the instant payment function, the user can determine that the user meets the preset payment conditions, and when making a payment via NFC, the user may not need to display the payment page, or may directly display the transaction result page without displaying the payment presentation page.

[0178] A highly active user may refer to a user whose level of activity in using the payment application is above a preset threshold. In practical applications, the level of activity of a user may be calculated based on factors such as the length of time and frequency with which the user logs in to the payment application. The level of activity of a user may also be determined based on how often the user uses the payment application to perform code scan withdrawals or output withdrawal codes. For highly active users, a fast payment processing flow may be provided, for example, without displaying a payment page.

[0179] In practical applications, for a highly active user, the instant payment function in the user's payment application may be turned on by default, and a corresponding payment flow may be provided to the user based on the status of the instant payment function. The password-free payment function may refer to the function of making payments without requiring password entry, and payments may be made by using biometric features such as fingerprints, faces, voiceprints, and irises as authentication information.

[0180] In one embodiment, if the mobile terminal is an iOS system, the mobile terminal can approach an NFC tag and display a payment prompt page after acquiring tag information. The payment prompt page may be displayed in the form of a Clips card. If the payment prompt page includes a control used to confirm the launch of a payment application, the user can operate the control. As shown in FIG. 8, when the user clicks the "Open" control, the user can indicate their consent to use the payment application to make a payment, and the mobile terminal can launch the payment application. The mobile terminal can send a payment processing request to the server based on the launched payment application, and the server can process the payment service and return result information, and the mobile terminal can display a transaction result page. In practical applications, when the user operates the payment prompt page, the mobile terminal can collect the user's biometric information as payment verification information. If the information indicating the confirmation committed by the user based on the payment prompt page indicates that the user has confirmed the payment information, the payment page does not need to be displayed. Of course, the payment page can be displayed according to actual needs.

[0181] In one embodiment, if the mobile terminal is an Android system, after approaching an NFC tag and acquiring tag information, if a payment application is installed on the mobile terminal, the mobile terminal can launch the payment application and display a payment page. After the user confirms the information on the payment page, the mobile terminal can display a transaction result page. If the user has enabled the instant payment function, the payment page does not need to be displayed after the payment application is launched. Instead, the transaction result page can be displayed after the mobile terminal acquires payment result information. From the user's perspective, after the user uses the mobile terminal to bring it close to an NFC tag or a payment device, the mobile terminal can launch the payment application and display a payment page. To improve the user experience, after launching the payment application, a payment response page indicating that payment is in progress can be displayed, and then a transaction result page can be displayed. If the user has not activated the instant payment function, the payment application can be launched, and then the payment page can be displayed. Similarly, the payment response page can be displayed before or after displaying the payment page, and then the transaction result page can be displayed.

[0182] To improve the user experience, optionally, the method in the embodiments herein may further include a step of displaying presentation information used to suggest the user to set up the instant payment feature.

[0183] Specifically, the presented information may be information suggesting that the user turn on the instant payment function, or information suggesting that the user turn off the instant payment function. The presented information may be displayed after launching the payment application, or may be displayed on a payment-related page displayed in the payment flow, such as the payment page or the transaction result page, or may be displayed independently. For example, after launching the payment application, a page including presented information used to suggest that the user turn on the instant payment function may be displayed before the payment page is displayed. For another example, after displaying the payment page, a page including presented information used to suggest that the user turn on the instant payment function may be displayed. For another example, after displaying the transaction result page, a page including presented information used to suggest that the user turn on the instant payment function may be displayed. Here, the manner of displaying the presented information is not specifically limited.

[0184] In order to avoid excessively disturbing the user, the method in the embodiment of the present specification may further include a step of determining whether the number of times that the presentation information used to suggest that the user set up the instant payment function has been displayed within a preset period is less than or equal to a preset number, and if the number of times that the information has been displayed is less than or equal to the preset number, displaying the presentation information used to suggest that the user set up the instant payment function.

[0185] The preset 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 within one day, or it can be displayed for the first transaction within one day and once every four transactions thereafter, or it can be displayed eight times within one week, for example.

[0186] Optionally, the method in the embodiment herein may further include determining whether a user account of the payment application in the mobile terminal has an instant payment function enabled. The step of displaying presentation information used to suggest that a user set the instant payment function specifically includes displaying first presentation information used to suggest that a user turn on the instant payment function if the user account has not turned on the instant payment function.

[0187] In an embodiment of the present specification, if the user has not turned on the instant payment function, the mobile terminal may display first prompting information suggesting that the user turn on the instant payment function. Here, if the user has turned on the instant payment function, the first prompting information suggesting that the user turn on the instant payment function does not need to be displayed, thereby reducing disturbance to the user.

[0188] To further improve the user experience, optionally, the method may further include, before the step of displaying first presentation information used to suggest that the user turn on the instant payment function, determining whether the user account is a high-activity user account. The step of displaying first presentation information used to suggest that the user turn on the instant payment function specifically includes, if the user account is a high-activity user account, displaying first presentation information used to suggest that the user turn on the instant payment function.

[0189] A high-activity user account may represent a user account with a high level of activity. In an embodiment of the present specification, a first offering information used to suggest that a user turn on the instant payment function may be displayed for a high-activity user account, thereby increasing the probability that the first offering information is provided to a user who has an actual need for the function.

[0190] Optionally, the step of displaying presentation information used to suggest that the user set the instant payment function may further include, specifically, if the user account has the instant payment function turned on, displaying second presentation information used to suggest that the user turn off the instant payment function.

[0191] In the embodiments of the present specification, if the user has turned on the instant payment function, the mobile terminal may display second prompting information used to prompt the user to turn off the instant payment function, whereas if the user has not turned on the instant payment function, the mobile terminal may not display the second prompting information.

[0192] In practical applications, before displaying the second display information, it can further determine whether the user account is a high-activity user account, and if the user account is not a high-activity user account, the second display information can be displayed, thereby avoiding disturbance to the user.

[0193] In one embodiment, in the example of this specification, presentation information used to prompt the user to set up the instant payment function can be displayed in or on top of the transaction result page.

[0194] 10 is a schematic diagram of a transaction result page provided in an embodiment of the present specification. As shown in FIG. 10, the transaction result page may include payment result information 1002, such as payment success and payment failure, payment information 1004, such as payment amount, payment method, merchant, and campaign information, and a control 1006 for closing the transaction result page, such as a "Done" control. In actual applications, the specific content and format of the transaction result page can be set according to actual needs, and are not specifically limited herein.

[0195] 11 is a schematic diagram showing the display of suggested information provided in an embodiment of the present specification. As shown in FIG. 11, suggested information 1102 used to prompt the user to set up the instant payment function may be displayed on top of the transaction result page in the form of a pop-up window. The specific content of the suggested information can be set according to actual needs. For example, the suggested information may further include route information used to set up the instant payment function.

[0196] 11, the page containing the presented information may further include an operation control 1104 used to set the instant payment function. The control may be used to turn the instant payment function on or off, or to jump to a setting page used to set the instant payment function. The page may further include a control used to close the page.

[0197] 12 is a schematic diagram showing the display of presentation information provided in an embodiment of the present specification. As shown in FIG. 12, presentation information 1202 used to present the setting of the immediate payment function is displayed on a transaction result page. The page may further include operation controls 1204 used to set the immediate payment function. The presentation information may or may not overlap the display area of ​​the operation controls.

[0198] In actual applications, for each initiated transaction request, the presented information may be displayed in any of the following formats: a transaction result page format or a format displayed on top of the payment page format. For example, when a user clicks the close control in the pop-up window shown in Figure 11, a transaction result page with the presented information displayed can be displayed, as shown in Figure 12. In actual applications, the names, shapes, and layouts of the presented information and operation controls can be configured according to actual needs.

[0199] 13 is a schematic diagram showing the display of presentation information provided in an embodiment of the present specification. As shown in FIG. 13, presentation information 1302 used to prompt the user to set up the instant payment function is displayed on a transaction result page. The page may further include operation controls 1304 used to set up the instant payment function.

[0200] In practical application, the prompt information may be displayed in different ways for different users, for example, for a user who has not enabled the instant payment function, the prompt information may be displayed in the way shown in Figure 11, and for a user who has enabled the instant payment function, the prompt information may be displayed in the way shown in Figure 13.

[0201] If the user performs an operation on an operation control on the page displaying the presentation information, the mobile terminal can further display a setting page used to set up the instant payment function.

[0202] FIG. 14 is a schematic diagram of a setting page provided in an embodiment of the present specification. As shown in FIG. 14, the page may include introductory information 1402 related to the instant payment function, which may be in the form of text, video, audio, etc. For example, before-on or after-on video presentation information may be included, whereby if the user has enabled the instant payment function, a control 1404 on the setting page can be used to disable the function. If the user has not enabled the function, a control 1404 on the setting page can be used to enable the function. In actual application, after the user has completed the settings for the instant payment function, the terminal may further display a transaction result page.

[0203] Considering that the terminal or server may take some time to execute the payment flow, in order to improve the user experience, the embodiment of the present specification may optionally further include a step of displaying a payment response page before displaying the transaction result page, wherein the payment response page includes presentation information indicating that payment is in progress.

[0204] 15 is a schematic diagram of a payment response page provided in an embodiment of the present specification. As shown in FIG. 15, the payment response page may include presentation information 1502 indicating that payment is in progress, and may further include information 1504 of the near field communication method used, such as the phrase "NFC," and may further include related description information of near field communication payment, such as the phrase "touch to pay," as shown in FIG. 15.

[0205] As can be understood, the schematic diagrams provided in this specification are merely illustrative, and in actual applications, the display content and style of various pages can be set according to actual needs.

[0206] After launching the payment application, the mobile terminal may display a payment response page, and after the server completes processing the payment flow, the mobile terminal may display a transaction result page.

[0207] In one embodiment, after a user uses a mobile terminal with an instant payment feature enabled to bring the mobile terminal close to a payment device having an NFC tag, a payment response page may be displayed on the mobile terminal.

[0208] In the embodiments of the present specification, the payment offer page, payment page, or transaction result page may be displayed when the mobile terminal is unlocked or not. For example, when the mobile terminal is in a screen-locked state, the payment offer page may be displayed after acquiring tag information from an NFC tag. When a user operates the payment offer page, the camera of the mobile terminal collects biometric images of the user's face, iris, fingerprint, etc., and unlocks the mobile terminal, which may then display the transaction result page in the unlocked state. In practical applications, the user may unlock the mobile terminal and then bring the mobile terminal close to the NFC tag to acquire tag information. For example, when the distance between the mobile terminal and the NFC tag meets a certain condition, for example, when the mobile terminal approaches the NFC tag, the mobile terminal or the payment device associated with the NFC tag may emit prompting information, such as audio prompting information, text prompting information, or animation prompting information, to prompt the user to unlock the mobile terminal. To simplify user operations, when the mobile terminal is not unlocked, an application may be launched in the background and the payment offer page, payment page, or transaction result page may be displayed. Based on a similar concept, an embodiment of this specification further provides a payment method based on short-range wireless communication, which is executed by a server, and Fig. 16 is a flow diagram of the payment method based on short-range wireless communication provided by the embodiment of this specification. From the perspective of a program, the execution entity of the flow may be a program installed on a server or an application client.

[0209] As shown in FIG. 16, the flow may include step 1602, in which a server acquires a payment processing request including payment information sent by a mobile terminal having a near field communication function, where the payment information is provided based on the second business partner displaying a payment page including user information of the first business partner, where the payment page is generated by the mobile terminal based on tag information in the acquired NFC tag, where the tag information includes payment link information; and step 1604, in which a server completes payment services for the first business partner and the second business partner based on the payment processing request.

[0210] The server may be a server with payment processing capabilities, and may determine the transaction account or account number of the first transaction partner according to the user information of the first transaction partner, such as a business identifier and a user identifier. Furthermore, the server may determine the transaction amount and the transaction account or account number of the second transaction partner according to the transaction information provided by the second transaction partner, and complete the transaction processing for the transaction amount. The server in this embodiment may correspond to the server in the method described in FIG. 2 above. For similar or identical parts, please refer to the introduction of the above embodiment, and detailed descriptions will be omitted here.

[0211] 17 is a flow diagram of a payment method based on near field communication provided by an embodiment of the present specification. From a program perspective, the execution entity of the flow may be a program installed on a server or an application client.

[0212] As shown in FIG. 17, the flow includes step 1702, in which a server acquires a payment information acquisition request generated based on tag information in an NFC tag acquired by a mobile terminal having a near field communication function, where the tag information is used to trigger a payment flow; step 1704, in which a server generates transaction identification information based on the payment information acquisition request, where the transaction identification information is used to represent user payment account information in the mobile terminal; and step 1706, in which the server sends the transaction identification information to a payment instrument associated with the NFC tag, where the payment instrument is used to execute a payment flow according to the transaction identification information.

[0213] Here, the server may correspond to the server in the method described in Figure 5. For specific details, please refer to the details of the above embodiment, and a detailed description will be omitted here. The server in this embodiment may be the same server as the server in Figure 2 or Figure 16, and is not specifically limited here.

[0214] 18 is a flow diagram of a payment method based on near field communication provided by an embodiment of the present specification. From a program perspective, the execution entity of the flow may be a program installed on a server or an application client.

[0215] As shown in FIG. 18, the flow may include step 1802 in which a server obtains a payment processing request sent by a mobile terminal, where the payment processing request is sent by a payment application launched by the mobile terminal based on tag information in an NFC tag; step 1804 in which a server processes a payment service based on the payment request and generates payment result information; and step 1806 in which the server feeds back the payment result information to the mobile terminal.

[0216] Optionally, the step of processing the payment service based on the payment request may specifically include the steps of generating transaction identification information used to represent user payment account information in the mobile terminal based on the payment processing request, and sending the transaction identification information to a payment device, whereby the payment device executes a payment flow based on the transaction identification information.

[0217] Optionally, the method may further include sending a payment flow trigger instruction to the payment instrument, whereby the payment instrument can execute a payment flow based on the obtained transaction identification information based on the payment flow trigger instruction.

[0218] For the specific implementation process, please refer to the content in the above embodiments, and it will not be described in detail here.

[0219] In embodiments herein, information transmission between the payment instrument and the mobile terminal server may be transmitted over a network.

[0220] Based on a similar concept, embodiments of the present specification further provide an apparatus corresponding to the above method. Figure 19 is a structural schematic diagram of a payment device based on near field communication, corresponding to Figure 2 provided by embodiments of the present specification. As shown in Figure 19, the device may include: a trigger information sending module 1902 for transmitting an electromagnetic signal for triggering an NFC tag; a tag information acquiring module 1904 for acquiring tag information of the NFC tag responding to the electromagnetic signal, where the tag information includes payment link information; a page display module 1906 for displaying a payment page including user information of a first merchant based on the payment link information; a payment information acquiring module 1908 for acquiring payment information provided by a second merchant based on the payment page; and a request sending module 1910 for sending a payment processing request including the payment information to a server, where the server completes the payment based on the payment processing request.

[0221] Based on a similar idea, the present disclosure further provides an apparatus corresponding to the above method. Figure 20 is a structural schematic diagram of a payment device based on near field communication, corresponding to Figure 5 provided by the present disclosure. As shown in Figure 20, the device may include: a trigger information sending module 2002 for transmitting an electromagnetic signal for triggering an NFC tag; a tag information acquiring module 2004 for acquiring tag information of an NFC tag responsive to the electromagnetic signal, where the tag information is used to trigger a payment flow; a transaction identifier acquiring module 2006 for acquiring transaction identification information representing user payment account information of the mobile terminal based on the tag information; and a transaction identifier sending module 2008 for sending the transaction identification information to a payment instrument associated with the NFC tag, where the payment instrument executes the payment flow according to the transaction identification information.

[0222] 21 is a structural schematic diagram of a payment device based on near field communication provided by an embodiment of the present specification, corresponding to FIG. 7. As shown in FIG. 21, the device may include: a tag information obtaining module 2102 for obtaining tag information of an NFC tag associated with a payment device; an application launching module 2104 for launching a payment application in the mobile terminal according to the tag information; a request sending module 2106 for sending a payment processing request to a server according to the launched payment application, where the server processes the payment service according to the payment processing request and feeds back payment result information; and a page displaying module 2108 for displaying a transaction result page according to the payment result information fed back by the server.

[0223] Fig. 22 is a structural schematic diagram of a payment device based on near field communication provided by an embodiment of the present specification, corresponding to Fig. 16. As shown in Fig. 22, the device may include: a request obtaining module 2202 used to obtain a payment processing request sent by a mobile terminal with near field communication capability, the request obtaining module 2202 including payment information, the payment information being provided based on a second merchant displaying a payment page including user information of a first merchant, the payment page being generated based on tag information in an NFC tag obtained by the mobile terminal, the tag information including payment link information; and a request processing module 2204 used to complete payment services for the first merchant and the second merchant based on the payment processing request.

[0224] Figure 23 is a structural schematic diagram of a payment device based on near field communication, corresponding to Figure 17 provided by an embodiment of the present specification. As shown in Figure 23, the device may include: a request obtaining module 2302, used for obtaining a payment information obtaining request generated based on tag information in an NFC tag obtained by a mobile terminal with near field communication function, where the tag information is used for triggering a payment flow; an information generating module 2304, used for generating transaction identification information based on the payment information obtaining request, where the transaction identification information is used to represent user payment account information of the mobile terminal; and a sending module 2306, used for sending the transaction identification information to a payment device associated with the NFC tag, where the payment device executes the payment flow according to the transaction identification information.

[0225] Figure 24 is a structural schematic diagram of a payment device based on near field communication provided by an embodiment of the present specification, corresponding to Figure 18. As shown in Figure 24, the device may include: a request acquisition module 2402 used to acquire a payment processing request sent by a mobile terminal, where the payment processing request is sent by a payment application launched by the mobile terminal based on tag information in an NFC tag; a payment processing module 2404 used to process a payment service based on the payment request and generate payment result information; and a result sending module 2406 used to feed back the payment result information to the mobile terminal.

[0226] Based on a similar concept, the embodiments of the present specification further provide an apparatus corresponding to the above method.

[0227] 25 is a structural schematic diagram of a payment device based on near field communication provided by an embodiment of the present specification. As shown in FIG. 25, the device 2500 may include at least one processor 2510 and a memory 2530 communicatively connected to the at least one processor, wherein the memory 2530 stores instructions 2520 executable by the at least one processor 2510, which, when executed by the at least one processor 2510, cause the at least one processor 2510 to perform at least one of the payment methods based on near field communication.

[0228] Based on a similar concept, the present disclosure also provides a computer-readable medium corresponding to the above-described method, the computer-readable medium storing computer-readable instructions that, when executed by a processor, can realize at least one of the above-described near field communication-based payment methods.

[0229] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, so that the description of each embodiment focuses on the differences from other embodiments. In particular, since the apparatus and device are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiments.

[0230] In the 1990s, technological improvements could be clearly distinguished between hardware improvements (e.g., improvements to circuit structures such as diodes, transistors, and switches) and software improvements (improvements to method flows). However, with the development of technology, many current method flow improvements can be considered direct improvements to hardware circuit structures. Designers often obtain corresponding hardware circuit structures by programming the improved method flows into hardware circuits. Therefore, it cannot be said that method flow improvements cannot be realized with hardware entity modules. For example, programmable logic devices (PLDs) (e.g., field programmable gate arrays (FPGAs)) are a type of such integrated circuit, whose logic functions are determined by user programming. Designers can independently program and "integrate" a digital system into a PLD, eliminating the need for chip manufacturers to design and manufacture dedicated integrated circuit chips. Now, instead of manually manufacturing integrated circuit chips, most such programming is also achieved using "logic compiler" software. It is similar to a software compiler used in program development and creation; to compile the original code, it must also be written in a specific programming language, called a Hardware Description Language (HDL).Meanwhile, there are not just one but multiple HDLs, 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, and RHDL (Ruby Hardware Description Language), among others. Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. As will be apparent to those skilled in the art, a hardware circuit embodying a method flow can be obtained very easily by simply programming the method flow in a few logic steps using the above hardware description languages ​​and programming the method flow into an integrated circuit.

[0231] The controller may be implemented in any suitable manner. For example, the controller may take the form of a microprocessor, or a processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, an application-specific integrated circuit (ASIC), a programmable logic controller, or an embedded microcontroller. Examples of controllers include, but are not limited to, microcontrollers such as the ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. A memory controller may also be implemented as part of the memory's control logic. Those skilled in the art will recognize that in addition to implementing the controller purely in the form of computer-readable program code, the same functions can be realized in the form of logic gates, switches, an application-specific integrated circuit, a programmable logic controller, an embedded microcontroller, etc., by completely logically programming method steps. Therefore, such a controller may be considered a type of hardware component, and the devices contained therein and used to realize various functions may be considered structures within the hardware component. Furthermore, the devices used to implement various functions can be considered as software modules that implement methods, or as structures within hardware components.

[0232] The systems, devices, modules, or units described in the above embodiments may be specifically implemented by computer chips or entities, or may be implemented by products having certain functions. One 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 any combination of these devices.

[0233] For simplicity, the above description of the device is divided into various functional units. Of course, when implementing this application, the functions of each unit can be realized by the same or multiple pieces of software and / or hardware.

[0234] As will be appreciated by those skilled in the art, embodiments of the present invention may be provided as a method, a system, or a computer program product. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. The present invention may also take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk memory, CD-ROM, optical memory, etc.) containing computer-usable program code thereon.

[0235] The present invention will be described with reference to flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present invention. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and combinations of flows and / or blocks in the flowcharts and / or block diagrams, 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, whereby the instructions executed by the processor of the computer or other programmable data processing device produce an apparatus used to implement the function specified in one or more flows in the flowcharts and / or one or more blocks in the block diagrams.

[0236] These computer program instructions may be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture that includes an instruction apparatus, which implements the functions specified in one or more flows of the flowcharts and / or one or more blocks of the block diagrams.

[0237] These computer program instructions may be loaded into a computer or other programmable data processing device, causing the computer or other programmable device to execute a series of operational steps to generate a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide the steps used to implement the functions specified in one or more flows of the flowcharts and / or one or more blocks of the block diagrams.

[0238] In one typical configuration, a computing device includes one or more processors (CPUs), input / output ports, network ports, and internal memory. The internal memory may include volatile memory, random access memory (RAM), and / or non-volatile internal memory in the form of a computer-readable medium, such as read-only memory (ROM) or flash memory (flash RAM). The internal memory is exemplary of a computer-readable medium.

[0239] Computer-readable media include nonvolatile and volatile, removable and non-removable media, and may implement information storage by any method or technology. Information may be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change internal 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 internal memory technology, optical disk read-only memory (CD-ROM), digital multifunction optical disk (DVD), or other optical storage, magnetic cassette tape, magnetic disk tape storage, or other magnetic storage devices, or any other non-transmission medium that may be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media, such as modulated data signals or carrier waves.

[0240] It should be noted that the terms "comprises," "comprises," or any other variations thereof are intended to cover a non-exclusive inclusion, whereby a process, method, article, or device comprising a set of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent in such process, method, article, or device. Absent more limitations, elements qualified by the sentence "comprises a ..." do not exclude the presence of additional identical elements in the process, method, article, or device that includes the said elements.

[0241] As will be appreciated by those skilled in the art, embodiments of the present application may be provided as a method, a system, or a computer program product. Thus, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. The present application may also take the form of a computer program product embodied on one or more computer-usable storage mediums (including, but not limited to, magnetic disk memory, CD-ROM, optical memory, etc.) that contain computer-usable program code thereon.

[0242] This application may be described in the general context of computer-executable instructions being executed by a computer, for example, program modules. Generally, program modules include routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types. This application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media, including storage devices.

[0243] The above-mentioned are merely examples of the present application and are not intended to limit the present application. Those skilled in the art can make various modifications and variations to the present application. Any modifications, equivalent replacements, and improvements made within the spirit and principles of the present application should 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 having a near field communication function emitting an electromagnetic signal used to trigger an NFC tag; acquiring tag information of an NFC tag responsive to the electromagnetic signal, the tag information including payment link information; displaying a payment page including user information of the first merchant based on the payment link information; obtaining payment information provided by the second merchant based on the payment page; and sending a payment processing request including the payment information to a server, the server being used to complete the payment based on the payment processing request.

2. the tag information includes instruction information used to launch a payment application; The step of displaying a payment page including user information of the first business partner according to the payment link information specifically includes: launching the payment application on the mobile terminal based on the instruction information; and displaying the payment page based on the payment application being launched.

3. The tag information includes request identification information used to request obtaining payment page information, and the step of displaying the payment page according to the activated payment application specifically includes: generating a payment page information acquisition request in response to the request identification information by the payment application in an activated state; sending the payment page get request to the server; acquiring payment page information, which includes user information of the first merchant, generated by the server based on the payment page acquisition request; and displaying a payment page including user information of the first merchant based on the payment page information.

4. The tag information includes user identification information of the first trading partner, and the method includes: The method further includes determining whether the first trading partner has transaction authority based on the user identification information, and obtaining a determination result; The step of displaying a payment page including user information of the first merchant specifically includes:

10. The method of claim 1, further comprising the step of: if the determination indicates that the first merchant is authorized to transact, displaying a payment page including user information of the first merchant.

5. The method of claim 1 , wherein the NFC tag is located in a carrier that includes a payment code of the first transaction partner or is located in a carrier that does not include a payment code of the first transaction partner.

6. When acquiring tag information of an NFC tag including payment link information, if the mobile terminal is displaying an application page of a second application, displaying a payment page associated with a first customer specifically includes: The method of claim 1 , further comprising the step of overlaying the payment page on top of an application page of the second application.

7. The method comprises: receiving a logout operation on the payment page of the second merchant; The method of claim 6 , further comprising: switching to and displaying an application page of the second application based on the logout operation.

8. The tag information includes first trigger information, and the first trigger information is used to trigger the mobile terminal to determine a terminal application having a payment function in the mobile terminal and generate an application selection page, and the method includes: determining a terminal application having a payment function in the mobile terminal in response to the first trigger information; generating an application selection page based on the terminal application having payment functionality; The method of claim 1 , further comprising the step of: displaying the application selection page.

9. After the step of displaying the application selection page, The method further includes obtaining the target terminal application selected by the second trading partner from the application selection page; The step of displaying a payment page including transaction information of the first customer based on the payment link information specifically includes: employing the target terminal application to access the payment link information; and displaying a payment page in the target terminal application including transaction information for the first merchant.

10. before the step of acquiring tag information of an NFC tag responsive to the electromagnetic signal, determining whether the mobile terminal has launched a code scanning application program used to scan a payment code image; The step of acquiring tag information of the NFC tag responsive to the electromagnetic signal specifically includes: The method of claim 1 , further comprising the step of, if not activated, obtaining tag information of an NFC tag responsive to the electromagnetic signal.

11. 10. The method of claim 1, wherein the payment page includes at least one of controls used to confirm payment information, an area used to enter or select a payment amount, and an area used to enter or select a payment method.

12. The method comprises: determining whether the payment application is present on the terminal; If not present, generating a presentation indicating insolvency.

13. The method comprises: determining whether the payment application is present on the terminal; 3. The method of claim 2, further comprising: if not present, generating an offer to the user to download and install the payment application.

14. The method comprises: The method of claim 1 , further comprising the step of displaying a payment password entry page.

15. The method comprises: The method of claim 1 , further comprising generating a page or presentation showing a transaction result.

16. A payment method based on near field communication, comprising: a mobile terminal having a near field communication function emitting an electromagnetic signal used to trigger an NFC tag; acquiring tag information of an NFC tag responsive to the electromagnetic signal, the tag information being used to trigger a payment flow; obtaining transaction identification information based on the tag information, which is used to represent user payment account information in the mobile terminal; and transmitting the transaction identification information to a payment device associated with the NFC tag, the payment device being used to execute a payment flow according to the transaction identification information.

17. The step of obtaining transaction identification information used to represent user payment account information in the mobile terminal based on the tag information specifically includes: sending a payment information acquisition request to a server, the request including user identification information of the mobile terminal; and obtaining the transaction identification information generated by the server based on the user identification information.

18. Specifically, the step of transmitting the transaction identification information to the payment instrument includes:

17. The method of claim 16, comprising transmitting the transaction identification information to the payment instrument via a near field communication method.

19. Specifically, the step of transmitting the transaction identification information to the payment device via a short-range wireless communication method includes: writing the transaction identification information to the NFC tag; and feeding back the transaction identification information to the payment instrument via the NFC tag using near field communication techniques.

20. The tag information includes a device identifier of the payment device, and the step of transmitting the transaction identification information to the payment device specifically includes: sending a payment request to a server including the device identifier; 17. The method of claim 16, further comprising: the server being used to generate transaction identification information and transmitting the transaction identification information to the payment instrument in response to the instrument identifier.

21. The tag information includes first link information used to launch a payment application on the mobile terminal, and the method includes: further comprising launching the payment application based on the first link information; The step of obtaining transaction identification information used to represent user payment account information in the mobile terminal specifically includes:

17. The method of claim 16, comprising obtaining the transaction identification information based on the payment application being launched.

22. After the step of launching the payment application, 22. The method of claim 21, further comprising the step of displaying presentation information used to indicate that the payment application has been launched, the presentation information specifically including presentation information in the form of at least one of vibration, sound, text, or image.

23. The method comprises: acquiring trading result information fed back by the server; The method of claim 16 , further comprising: displaying a trading results page based on the trading results information.

24. When acquiring tag information of an NFC tag, if the mobile terminal is displaying an application page of a second application, the step of displaying a transaction result page specifically includes: The method according to claim 23, further comprising the step of superimposing the transaction results page on an application page of the second application.

25. The method comprises: acquiring a logout operation for the transaction result page; The method of claim 24 , further comprising: switching to and displaying an application page of the second application based on the logout operation.

26. the tag information includes an identifier of the payment application; The step of launching the payment application based on the first link information specifically includes:

22. The method of claim 21, comprising launching the payment application based on the payment application identifier.

27. The method comprises: generating a payment code image based on the transaction identification information; and displaying the payment code image. Specifically, the step of transmitting the transaction identification information to a payment device associated with the NFC tag includes:

17. The method of claim 16, including transmitting the transaction identification information via the payment code image to a payment device having code scanning capabilities.

28. A payment method based on near field communication, comprising: a mobile terminal having near field communication capability obtaining tag information of an NFC tag associated with the payment device; launching a payment application on the mobile terminal based on the tag information; sending a payment processing request to a server based on the activated payment application, the server being used to process payment services based on the payment processing request and feed back payment result information; and displaying a transaction result page based on the payment result information fed back by the server.

29. The method comprises: displaying a payment offer page based on the tag information, the payment offer page including offer information used to offer to make a payment using the payment application; obtaining a first preset operation of the user on the payment submission page and generating first confirmation information; The step of launching a payment application on the mobile terminal specifically includes:

30. The method of claim 28, comprising launching a payment application on the mobile terminal based on the first verification information.

30. Before the step to display the trading results page, displaying a payment page containing payment information; and acquiring second confirmation information generated based on a second preset operation of the user on the payment page; The step of sending the payment processing request to the server specifically includes:

30. The method of claim 28, further comprising transmitting a payment processing request to a server based on the second verification information.

31. 29. The method of claim 28, wherein the server generates transaction identification information used to represent user payment account information in the mobile terminal based on the payment processing request, and transmits the transaction identification information to the payment instrument, whereby the payment instrument executes the payment flow based on the transaction identification information.

32. After the step of launching a payment application on the mobile terminal, displaying a payment page containing payment information; 32. The method of claim 31, further comprising: acquiring second confirmation information generated based on a second preset operation of the user on the payment page, whereby the server sends a payment flow trigger instruction to the payment instrument after the second confirmation information, and the payment instrument can execute a payment flow based on the acquired transaction identification information based on the payment flow trigger instruction.

33. Before the step that displays the payment page containing payment information, The method further includes a step of determining whether a user of the mobile terminal meets preset payment conditions based on account information of the payment application in the mobile terminal, the preset payment conditions representing conditions under which fast payment can be made; The step of displaying a payment page including payment information specifically includes:

33. The method of claim 30 or 32, comprising the step of displaying a payment page containing payment information if the user does not meet preset payment terms.

34. The steps for displaying the transaction result page include:

34. The method of claim 33, including the step of displaying a transaction results page if the user meets preset payment terms.

35. 34. The method of claim 33, wherein the preset payment conditions include at least one of: authorization to use an instant payment feature; the user being a highly active user of the payment application; and authorization to use a password-free payment feature.

36. The method according to claim 30 or 32, wherein the payment information includes at least one of transaction amount information, transaction partner information, and transaction method information.

37. The method comprises:

30. The method of claim 28, further comprising the step of displaying presentation information used to suggest that a user set up the instant payment feature.

38. The method comprises: The method further includes determining whether the number of times that the presentation information used to suggest that the user set up the instant payment function is displayed within a preset period is equal to or less than a preset number of times; The step of displaying the presentation information used to suggest that the user set up the immediate payment function specifically includes:

38. The method of claim 37, including the step of displaying presentation information used to suggest that the user set up the instant pay feature if the number of times displayed is less than or equal to a preset number.

39. The method comprises: determining whether a user account of the payment application on the mobile terminal has an instant payment feature enabled; The step of displaying the presentation information used to suggest that the user set up the immediate payment function specifically includes:

38. The method of claim 37, further comprising the step of: if the user account does not have the instant payment feature enabled, displaying first presentation information used to suggest that the user enable the instant payment feature.

40. before the step of displaying first presentation information used to suggest that the user turn on the instant payment function; determining whether the user account is a high activity user account; The step of displaying first presentation information used to suggest that the user turn on the instant payment function specifically includes:

40. The method of claim 39, including the step of displaying first presentation information used to suggest that the user turn on the instant pay feature if the user account is a high activity user account.

41. The step of displaying the presentation information used to suggest that the user set up the immediate payment function specifically includes:

40. The method of claim 39, further comprising the step of displaying second presentation information used to suggest that the user turn off the instant payment feature if the user account has the instant payment feature turned on.

42. The step of displaying the presentation information used to suggest that the user set up the immediate payment function specifically includes:

38. The method of claim 37, further comprising displaying, within or on the transaction results page, presentation information used to suggest that a user set up an instant payment feature.

43. 38. The method of claim 37, wherein the page on which the presentation information resides further includes operational controls used to set up an instant payment feature.

44. The method comprises:

44. The method of claim 43, further comprising the step of displaying a configuration page used to configure an instant payment feature based on a user's operation of the operational control.

45. Before the step to display the trading results page, 30. The method of claim 28, further comprising the step of displaying a payment response page, the payment response page including presentation information indicating payment is in progress.

46. The tag information includes an application identifier of the payment application, and the step of activating the payment application in the mobile terminal based on the tag information specifically includes:

30. The method of claim 28, comprising launching a payment application on the mobile terminal based on the application identifier.

47. The tag information includes link information, and the link information includes information used to display the payment offer page. The step of displaying the payment offer page based on the tag information specifically includes:

30. The method of claim 29, comprising displaying a payment offer page based on the link information.

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

49. A payment method based on near field communication, comprising: a step in which a server receives a payment processing request including payment information sent by a mobile terminal having a near field communication function, the payment information being provided based on a second transaction party displaying a payment page including user information of a first transaction party, the payment page being generated based on tag information in an NFC tag obtained by the mobile terminal, the tag information including payment link information; completing payment services for the first merchant and the second merchant based on the payment processing request.

50. A payment method based on near field communication, comprising: a step of a server acquiring a payment information acquisition request generated based on tag information in an NFC tag acquired by a mobile terminal having a near field communication function, the tag information being used to trigger a payment flow; generating transaction identification information used to represent user payment account information in the mobile terminal based on the payment information acquisition request; and transmitting the transaction identification information to a payment device associated with the NFC tag, the payment device being used to execute a payment flow according to the transaction identification information.

51. A payment method based on near field communication, comprising: a step in which a server acquires a payment processing request sent by a mobile terminal, the payment processing request being sent by a payment application launched by the mobile terminal based on tag information in an NFC tag; processing a payment service based on the payment request and generating payment result information; and feeding back the payment result information to the mobile terminal.

52. The step of processing the payment service based on the payment request specifically includes: generating transaction identification information used to represent user payment account information in the mobile terminal based on the payment processing request; 52. The method of claim 51, comprising: transmitting the transaction identification information to a payment instrument, whereby the payment instrument executes a payment flow based on the transaction identification information.

53. The method comprises:

53. The method of claim 52, further comprising: sending a payment flow triggering instruction to the payment instrument, whereby the payment instrument can execute a payment flow based on the obtained transaction identification information based on the payment flow triggering instruction.

54. 1. A near field communication based payment device, comprising: a trigger information transmitting module used to transmit an electromagnetic signal used to trigger the NFC tag; a tag information acquisition module used to acquire tag information of the NFC tag responsive to the electromagnetic signal, the tag information including payment link information; a page display module, which is used to display a payment page including user information of the first business partner according to the payment link information; a payment information acquisition module, used for acquiring payment information provided by the second customer according to the payment page; a request sending module adapted to send a payment processing request including the payment information to a server, the server adapted to complete the payment based on the payment processing request.

55. 1. A near field communication based payment device, comprising: a trigger information transmitting module used to transmit an electromagnetic signal used to trigger the NFC tag; a tag information acquisition module used to acquire tag information of the NFC tag responsive to the electromagnetic signal, the tag information being used to trigger a payment flow; a transaction identifier obtaining module, which is used to obtain transaction identification information according to the tag information, which is used to represent user payment account information in the mobile terminal; a transaction identifier transmission module adapted to transmit the transaction identification information to a payment device associated with the NFC tag, the payment device adapted to execute a payment flow in accordance with the transaction identification information.

56. 1. A near field communication based payment device, comprising: a tag information acquisition module adapted to acquire tag information of an NFC tag associated with the payment device; an application launch module used to launch a payment application in the mobile terminal based on the tag information; a request sending module used to send a payment processing request to a server according to the activated payment application, wherein the server processes a payment service according to the payment processing request and feeds back payment result information; a page display module adapted to display a transaction result page according to the payment result information fed back by the server.

57. 1. A near field communication based payment device, comprising: a request acquisition module used to acquire a payment processing request including payment information sent by a mobile terminal having a near field communication function, the payment information being provided based on a second business partner displaying a payment page including user information of a first business partner, the payment page being generated based on tag information in an NFC tag acquired by the mobile terminal, the tag information including payment link information; a request processing module adapted to complete payment services for the first merchant and the second merchant based on the payment processing request.

58. 1. A near field communication based payment device, comprising: a request acquisition module used to acquire a payment information acquisition request generated based on tag information in an NFC tag acquired by a mobile terminal having a short-range wireless communication function, the tag information being used to trigger a payment flow; an information generating module used to generate transaction identification information used to represent user payment account information in the mobile terminal according to the payment information acquisition request; a transmitting module adapted to transmit the transaction identification information to a payment device associated with the NFC tag, the payment device adapted to execute a payment flow in accordance with the transaction identification information.

59. 1. A near field communication based payment device, comprising: a request acquisition module used to acquire a payment processing request sent by a mobile terminal, the payment processing request being sent by a payment application launched by the mobile terminal based on tag information in an NFC tag; a payment processing module used for processing a payment service according to the payment request and generating payment result information; a result sending module used to feed back the payment result information to the mobile terminal.

60. 1. A near field communication based payment device, comprising: at least one processor; a memory communicatively coupled to the at least one processor, wherein:

50. A near field communication based payment device, wherein the memory stores instructions executable by the at least one processor, the instructions, when executed by the at least one processor, causing the at least one processor to perform a near field communication based payment method according to any one of claims 1 to 15, or any one of claims 16 to 27, or any one of claims 28 to 48, or claim 49, or claim 50, or any one of claims 51 to 53.

61. 10. A computer readable medium having stored thereon computer readable instructions which, when executed by a processor, are capable of realizing the near field communication based payment method of any one of claims 1 to 15, or any one of claims 16 to 27, or any one of claims 28 to 48, or claim 49, or claim 50, or any one of claims 51 to 53.

Images