Payment processing method and device, equipment and medium

Abstract

The embodiment of the invention discloses a payment processing method and device, equipment and a medium. The scheme comprises the steps of obtaining a payment processing request; the payment processing request is triggered by a first device of a payer and a second device of a payee based on a near field communication mode; before a transaction resource corresponding to the payment processing request is transferred to a collection account of the payee, sending a first payment result page to a first device of the payer; the first payment result page is used for representing that a communication step based on near field communication is completed in an online transaction process; after the transaction resource is transferred to a collection account of the payee, sending a second payment result page to a first device of the payer; the second payment result page is used for indicating that the resource transfer step is completed.

Description

[0001] This application is a divisional application of "A payment processing method, device, equipment and medium (application date: September 9, 2024, application number: 202411260271.0)". Technical Field

[0002] The present application relates to the field of computer technology, and in particular to a payment processing method, device, equipment and medium. Background Art

[0003] With the development of computer technology, more and more services can be realized through near-field communication, such as mobile payment, access control and access management, data transmission and information exchange, etc. In recent years, near-field communication technology has been widely used in payment services due to its low cost and convenience, such as swiping NFC cards to take public transportation.

[0004] Therefore, how to improve the user payment experience in the near-field communication payment scenario is a technical problem that needs to be solved urgently. Summary of the invention

[0005] The embodiments of this specification provide a payment processing method, apparatus, device and medium to solve the problem of poor user payment experience in existing payment processing methods.

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

[0007] The embodiment of this specification provides a payment processing method, including:

[0008] Obtaining a payment processing request; the payment processing request is triggered by a first device of a payer and a second device of a payee based on near field communication;

[0009] Before the transaction resources corresponding to the payment processing request are transferred to the payment receiving account of the payee, a first payment result page is sent to the first device of the payee; the first payment result page is used to indicate that the communication step based on near field communication in the online transaction process has been completed;

[0010] After the transaction resources are transferred to the payment account of the payee, a second payment result page is sent to the first device of the payee; the second payment result page is used to indicate that the resource transfer step has been completed.

[0011] The embodiment of this specification provides a payment processing method, including:

[0012] The first device obtains the tag information of the near field communication of the second device by means of near field communication; the tag information is used to trigger the generation of a payment processing request;

[0013] Obtaining a first payment result page sent by the server; the first payment result page is sent by the server before the transaction resources corresponding to the payment processing request are transferred to the payment receiving account of the payee; the first payment result page is used to indicate that the communication step based on near field communication in the online transaction process has been completed;

[0014] Obtain a second payment result page sent by the server; the second payment result page is sent by the server after the transaction resources are transferred to the payment account of the payee.

[0015] The embodiment of this specification provides a payment processing device, including:

[0016] A payment processing request acquisition module, used to acquire a payment processing request; the payment processing request is triggered by a first device of a payer and a second device of a payee based on near field communication;

[0017] A first payment result page sending module, used for sending a first payment result page to a first device of the payer before the transaction resources corresponding to the payment processing request are transferred to the payment receiving account of the payee; the first payment result page is used to indicate that the communication step based on near field communication in the online transaction process has been completed;

[0018] The second payment result page sending module is used to send the second payment result page to the first device of the payer after the transaction resources are transferred to the payment account of the payee; the second payment result page is used to indicate that the resource transfer step has been completed.

[0019] The embodiment of this specification provides a payment processing device, including:

[0020] A tag information acquisition module, used to acquire the tag information of the near field communication of the second device by means of near field communication; the tag information is used to trigger the generation of a payment processing request;

[0021] a first payment result page acquisition module, used to acquire a first payment result page sent by the server; the first payment result page is sent by the server before the transaction resources corresponding to the payment processing request are transferred to the payment account of the payee; the first payment result page is used to indicate that the communication step based on near field communication in the online transaction process has been completed;

[0022] The second payment result page acquisition module is used to acquire the second payment result page sent by the server; the second payment result page is sent by the server after the transaction resources are transferred to the payment account of the payee.

[0023] The embodiment of the present specification provides a processor; and,

[0024] a memory communicatively connected to the at least one processor; wherein,

[0025] The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so as to enable the at least one processor to implement a payment processing method.

[0026] An embodiment of the present specification provides a computer-readable medium on which computer-readable instructions are stored. The computer-readable instructions can be executed by a processor to implement a payment processing method.

[0027] At least one embodiment in the present specification can achieve the following beneficial effects: by obtaining a payment processing request triggered by a near-field communication method, before the transaction resources corresponding to the payment processing request are transferred to the payee's payment account, a first payment result page can be sent to the payee's first device for display, so that the user can obtain the payment information and determine that the communication steps of the near-field communication have been completed; and then after the transaction resources are transferred to the payee's payment account, a second payment result page is sent to the payee's first device so that the user can determine that the payment service is also completed, so that the user can obtain the payment information more quickly without having to stay in the near-field communication stage for too long, thereby improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0029] Figure 1 It is a schematic diagram of an application scenario of a payment processing method provided in an embodiment of this specification;

[0030] Figure 2 It is a flowchart of a payment processing method provided in an embodiment of this specification;

[0031] Figure 3 is a schematic diagram of a first payment result page provided in an embodiment of this specification;

[0032] Figure 4 is a schematic diagram of a second payment result page provided in an embodiment of this specification;

[0033] Figure 5is a schematic diagram of multiple pages of prompt information displayed in a first device provided by an embodiment of this specification;

[0034] Figure 6 It is a flowchart of a payment service processing method provided in an embodiment of this specification;

[0035] Figure 7 It is a swim lane diagram of a payment processing method provided in an embodiment of this specification;

[0036] Figure 8 This specification provides an embodiment corresponding to Figure 2 A schematic diagram of the structure of a payment processing device;

[0037] Fig. 9 This specification provides an embodiment corresponding to Figure 6 A schematic diagram of the structure of a payment processing device;

[0038] Fig.10 It is a structural diagram of a payment processing device provided in an embodiment of this specification. DETAILED DESCRIPTION

[0039] In order to make the purpose, technical solutions and advantages of one or more embodiments of this specification clearer, the technical solutions of one or more embodiments of this specification will be clearly and completely described below in combination with the specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of one or more embodiments of this specification.

[0040] Near Field Communication (NFC) is a technology that allows two electronic devices to wirelessly transmit data within a distance of a few centimeters. This short-range wireless connection is mainly used in scenarios such as mobile payment information sharing and simplified device pairing. In a payment scenario based on near-field communication, users can use NFC-enabled devices to make contactless payments. During the payment process, the user's device communicates wirelessly with the merchant terminal via NFC to achieve fast payment. For example, in a bus scenario, the user terminal can be read as an NFC tag by the gate on the bus to complete the payment; or when taking the subway, the user uses the user terminal to touch the gate on the subway, and the user terminal can be read as an NFC tag or card by the gate on the subway to complete the payment.

[0041] In actual applications, users can use a mobile terminal with NFC card reading function to read the payment information in the merchant device with NFC tag through close contact or contactless methods such as tapping, and complete payment based on the payment information.

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

[0043] Figure 1 Schematic diagram of an application scenario of a payment processing method provided in an embodiment of this specification. Figure 1 As shown, the solution may include a first device 1, a server 2 and a second device 3. The first device 1 may be a user terminal device with a function of reading an NFC tag, for example, a mobile user terminal device such as a mobile phone, a tablet, a smart watch, a wearable smart device and a laptop computer. The second device 3 may be a device associated with an NFC tag, and may also be called an NFC device, such as a POS machine, a cash register terminal, etc. The second device 3 may have an NFC tag built in, or the NFC tag may be set separately from the second device. In actual applications, the first device 1 may trigger the generation of a payment request and send it to the server 2 by sticking or touching the second device 3. The server 2 may send the first payment result page to the first device 1 before completing the transaction; after completing the transaction, the second payment result page may be sent to the first device 1.

[0044] Next, a payment processing method provided in the embodiment of the specification will be described in detail with reference to the accompanying drawings. Figure 2 A schematic diagram of a payment processing method provided in an embodiment of this specification. From a program perspective, the execution subject of the process can be a program installed on an application server or an application client.

[0045] like Figure 2 As shown, the process may include the following steps:

[0046] Step 202: Obtain a payment processing request.

[0047] The payment request may be triggered by the payer's first device and the payee's second device based on face-to-face payment. For example, it may be a payment processing request triggered by scanning a code, such as the first device scanning the payment code displayed by the second device, or the first device displaying the payment code and being scanned by the second device. As an implementation method, the payment processing request may be triggered by the payer's first device and the payee's second device based on near field communication. For example, the first device may act as an NFC card reader to read the NFC tag information in the second device to trigger the payment processing request. In another example, the first device may act as an NFC tag or card, and the second device may act as an NFC card reader to read the NFC tag information in the first device.

[0048] As an implementation method, the first device may be a user terminal device with a function of reading NFC tags, such as a mobile phone, a tablet, a smart watch, a wearable smart device, a laptop computer, etc. The second device may be a device associated with an NFC tag, such as a POS machine, a cash register terminal, or a cash register device associated with a cash register system.

[0049] In the embodiments of this specification, near field communication may include NFC communication, Bluetooth communication, or WIFI communication, etc., which can realize short-distance communication. The payment processing request may be sent by the payee to the server. For example, after the payee obtains identification information containing user account information in the first device through near field communication, such as a string representing user account information, specifically information representing the payment code of the first device, the payment processing request may be generated based on the identification information and the order information determined by the payee. Among them, the order information may be order information generated based on information such as commodity price and commodity type.

[0050] In actual applications, the payment processing request may also be sent by the payer to the server. For example, the payer may obtain transaction information through near field communication. The transaction information may include the account identification information of the payee and the pending transaction information determined by the payee, such as the amount to be paid, etc. The payment processing request is generated based on the acquired transaction information and the identification information of the payee's user account. The payment processing request may include the identification information of the payer's account, the identification information of the payee's account, and the order information of the goods to be paid.

[0051] Step 204: before the transaction resources corresponding to the payment processing request are transferred to the payment account of the payee, a first payment result page is sent to the first device of the payee.

[0052] In the embodiments of this specification, the first payment result page is used to indicate that the communication steps based on near-field communication in the online transaction process have been completed. The first payment result page can display the result information of the near-field communication. The first payment result page can be generated when the payment processing flow is triggered by the first device or the second device, and the payment processing flow has been started, but all steps have not been completed. It can be used to prompt the user that the communication steps of near-field communication between the first device and the second device have been completed, and the first device and the second device can be moved away; it can also display payment result information to the user. The payment result displayed here can be an estimated payment result, such as a result indicating a successful payment, so that the user can move the first device and the second device away after seeing it, without having to keep the first device and the second device close for a long time.

[0053] Step 206: After the transaction resources are transferred to the payee's payment account, a second payment result page is sent to the payee's first device.

[0054] In the embodiments of this specification, the second payment result page is used to indicate that the resource transfer step has been completed. The second payment result page may be a page generated based on the payment processing result after the server completes the payment processing process based on the payment processing request and obtains the payment processing result. The second payment result page may also represent the final result page displayed after the near-field communication payment is completed. The transaction resources may be provided by the payer or by other service providers that can provide resources. In actual applications, the user can determine that the payment to the payee has been completed by viewing the second payment result page displayed on the first device.

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

[0056] Figure 2 The method in the embodiment of the present invention can obtain a payment processing request triggered by a near-field communication method, and before the transaction resources corresponding to the payment processing request are transferred to the payment account of the payee, a first payment result page can be sent to the first device of the payee for display, so that the user can determine through the first device that the communication steps of the near-field communication have been completed; and then after the transaction resources are transferred to the payment account of the payee, a second payment result page is sent to the first device of the payee so that the user can determine that the payment service is also completed, so that the user can obtain the payment information more quickly without staying in the near-field communication stage for too long, thereby improving the user experience.

[0057] based on Figure 2 The method of this specification also provides some specific implementation schemes of the method, which are described below. As an implementation mode, optionally, the payment processing request in the embodiment of this specification includes the order information to be processed; the method may also include:

[0058] Determine the order amount information in the order information to be processed;

[0059] A first payment result page including the order amount information is generated.

[0060] In the embodiment of this specification, after the server obtains the payment processing request, it can generate a first payment result page according to the order information to be processed contained in the payment processing request. The first payment result page can include order amount information in the order information.

[0061] The order information may include order amount information; it may also include product information, unit price information of each product, discount information given by the payee, etc. If the payee gives a discount, the order amount information may be the amount after the discount; if the payee does not give a discount, the order amount information may be the original amount. For example, if Mall A has a 10 yuan discount for purchases over 100 yuan today, and User A's purchase price in Mall A is 120 yuan, then the order amount information in the order information may be 110 yuan; if Mall A does not have a discount today, the order amount information in the order information may be 120 yuan.

[0062] In the embodiments of this specification, the payment processing request may include information such as the payee account identification information and the payee account identification information. The first payment result page may also display payment result information, such as payment success, payment failure, and other result information; it may also display payee information, such as the payee name, and other information. If an abnormality occurs in the process of the server obtaining the payment processing request, such as failure to successfully obtain or identify the payment processing request due to network abnormality or server abnormality, the first payment result page may also be a page for displaying payment failure, and specifically may display failure reason information, such as poor network signal, server abnormality, and other information.

[0063] Figure 3 This is a schematic diagram of a first payment result page provided in an embodiment of this specification. Figure 3 As shown, the page 300 may include payment result information 302, transaction amount information 304, and identification information 306 of the transaction party, such as a user name in small letters of AAA, where the user name may be the real name of the payer or payee, or the nickname information of the payer or payee in the payment application, or the trademark name of the payee account, etc. The payment application may be an application that provides an online resource transaction environment for the payer and payee.

[0064] like Figure 3 As shown, the page may also include a control 308 for closing the page, such as a "Done" control. After the user clicks the control, the page may be closed or redirected to other pages, such as the home page of the first device, the home page of the payment APP, etc. It is understandable that if the payment result information is a failure, the payment result information 302 may be displayed as a payment failure, and the reason for the payment failure may be displayed on the current page, such as network disconnection, server abnormality, etc.; or a prompt message may be displayed on the upper layer of the current page, such as "Transaction abnormality, please touch via NFC to complete the payment". Figure 3 For illustrative purposes only, the first payment result page may also display information such as payment date, which is not specifically limited here.

[0065] As an implementation mode in the embodiments of this specification, optionally, the method may further include:

[0066] Processing the payment processing request according to a preset payment processing flow, sending the transaction resources corresponding to the payment processing request to the payment receiving account of the payee, and obtaining payment result information;

[0067] Based on the payment result information, the second payment result page is generated; the second payment result page includes information on the actual payment amount of the payer.

[0068] The preset payment processing flow in the embodiments of this specification may represent a flow for processing a payment processing request, which may specifically be a processing flow in which a server reads the information carried in the payment processing request, deducts transaction resources from the account providing the resources, and transfers the deducted transaction resources to the account of the payee. In actual applications, a request for deducting resources from the payee's account may also be sent to other servers for managing the payee's account, and the server deducts the resources from the payee's account. The server or another server may also add the corresponding resources to the payee's account. Other servers or another server may provide the transfer result for the resources to the server for processing the payment processing request, and generate a second payment result page.

[0069] The account providing resources can be the payer's account or other accounts that can provide resources. For example, transaction resources can be deducted from other accounts that provide services to the payer. Other resource providers can first advance payment for the payer user and transfer the deducted transaction resources to the payee's account and other processing procedures.

[0070] The actual payment amount indicates the amount that the payer actually needs to pay, which can be equal to the order amount. If the payer can enjoy certain discounts, the actual payment amount can be the amount after enjoying the discount. The actual payment amount can be less than or equal to the order amount. The order amount can be the amount corresponding to the transaction order, or it can be expressed as the amount that the payee needs to collect. It is understandable that if there are discount resources that can be written off, the discount resources can be written off during the user's payment process to reduce the user's actual payment amount, but the amount received by the payee can still be the order amount.

[0071] Figure 4 This is a schematic diagram of a second payment result page provided in an embodiment of this specification. Figure 4As shown, the second payment result page 400 may include payment result information 402 and payment amount information 404; it may also include a transaction user name 410, such as Xiao A, payment amount information 406, such as RMB 100.00, and payment method information 408, such as XX bank card (0000), where 0000 may be the last four digits of the bank card number; it may also include reward information 412 of the payment application, which may be points information or red envelope information. The reward information 412 may include a control for jumping to a page displaying the reward information after clicking the reward information 412, such as a card package interface for displaying coupons, a points page for displaying points information, etc.

[0072] like Figure 4 As shown, the page may also include a control 414 for closing the page, such as a "Done" control. After the user clicks the control, the page can be closed or jumped to other pages, such as the home page of the first device, the home page of the payment APP, and the like. Figure 4 This is for illustrative purposes only. Some of the information, such as reward information, may not be displayed. Other information, such as the name of the payee, the written-off resource information, etc., may also be displayed. No specific limitation is made here.

[0073] As an implementation mode, optionally, the second payment result page in the implementation mode of this specification may also include at least one of the following: amount payable information, amount reduction or exemption information enjoyed by the user, and payment method information. The payment method may indicate the means used for deduction, or the source of the deducted resources, such as a bank card, a balance deposited by the user in the payment application, a credit card, etc. The amount payable information may indicate the amount that should be paid in the case of a discount. The amount reduction or exemption information enjoyed by the user may indicate the preferential resources that can be written off in the current transaction, such as discount coupons, red envelopes, etc. This information may be displayed in the above Figure 4 The second payment result page is shown.

[0074] In the embodiments of this specification, the transaction resources provided to the payee may be provided by the payer or by other service providers that can provide resources. Optionally, sending the transaction resources corresponding to the payment processing request to the payee's payment account may specifically include:

[0075] deducting the transaction resources corresponding to the payment processing request from the payment account of the payer, and sending the transaction resources to the payment account of the payee;

[0076] Alternatively, the transaction resources corresponding to the payment processing request are deducted from the account of the third-party resource provider, and the transaction resources are sent to the payment account of the payee; the third-party resource provider is a service provider other than the payee and the payee that can provide resources;

[0077] Alternatively, a third amount of resources is deducted from the payment account of the payer, and a fourth amount of resources is deducted from the account of the third-party resource provider; the sum of the third amount and the fourth amount is equal to the amount of transaction resources corresponding to the payment processing request; the third amount of resources and the fourth amount of resources are sent to the payment account of the payee.

[0078] In the embodiments of this specification, sufficient transaction resources can be deducted from the payer's account; sufficient transaction resources can also be deducted from the third-party resource provider's account to fully advance the payer; or part of the transaction resources can be deducted from the payer's account, and the remaining part of the transaction resources can be deducted from the third-party resource provider's account, and the sum of the resources deducted from the two is the sufficient transaction resources, and the third-party resource provider advances part of the resources for the payer to complete the transaction.

[0079] As an implementation method, in order to improve the user experience, a third-party resource provider may advance payment for the user to complete the transaction. Optionally, the sending of the transaction resources corresponding to the payment processing request to the payment recipient's payment account described in the embodiments of this specification may specifically include:

[0080] If the resources of the transaction amount corresponding to the payment processing request cannot be deducted from the payment account of the payer, the resources of the transaction amount are deducted from the account of the third-party resource provider; the third-party resource provider is a service provider other than the payer and the payee that can provide resources;

[0081] The resources of the recipient's receiving account will be increased by the transaction amount.

[0082] Among them, failure to deduct resources corresponding to the transaction amount of the payment processing request from the payment account of the payer may indicate failure to successfully deduct required resources from the payment account of the payer, for example, failure to deduct resources from the payer's account due to insufficient resources in the payer's account, instability of the network or server, etc.

[0083] In actual applications, after receiving the payment processing request, the server can deduct money from the payer's account, or can first determine whether the balance in the payer's account is greater than or equal to the amount of the transaction. If the deduction fails or the balance is determined to be less than the amount of the transaction, it can indicate that the resources corresponding to the transaction amount of the payment processing request have not been deducted from the payer's payment account. The third-party resource provider can be a third party that can provide transaction resources to the payer, specifically the manager of the payment application, or other service providers associated with the payment application.

[0084] In actual applications, after receiving the payment processing request, the server can also directly deduct the corresponding transaction resources from the account of the third-party resource provider, and transfer the transaction resources to the payee's account by means of third-party advance payment. Then, the corresponding resources are deducted from the payer's account and added to the third-party resource provider.

[0085] As an implementation method, it is possible to determine whether to deduct the corresponding resources from the payer's account based on the amount in the payment account. Optionally, the sending of the transaction resources corresponding to the payment processing request to the payee's payment account in the embodiments of this specification may specifically include:

[0086] Determine whether a first quantity of resources in the payment account of the payer is greater than or equal to a second quantity of transaction resources corresponding to the payment processing request, and obtain a determination result;

[0087] If the determination result indicates that the first amount is greater than or equal to the second amount, deducting the second amount of resources from the payment account of the payer;

[0088] If the judgment result indicates that the first amount is less than the second amount, the second amount of resources is deducted from the account of the third-party resource provider; the third-party resource provider is a service provider other than the payer and the payee that can provide resources;

[0089] The second amount of resources is added to the recipient's recipient account.

[0090] In the embodiments of this specification, the transaction resources may represent the resources that the payer should pay to the payee, which may be the order amount. In practical applications, if there is a discount, the second quantity may represent the quantity of resources after the discount, such as the discount provided by the payee, or the discount provided by the payment platform. The payment processing request may include identification information of the payee's account and identification information of the payee's account. The identification information may be identification information generated based on the account information, or may be the user identification or device identification of the payee or payer. The server may determine the payee's account based on the identification information of the payee's account, and deduct the second amount of resources from the payee's account; the payee's account may be determined based on the identification information of the payee's account, and the second amount of resources may be transferred to the payee's account.

[0091] In actual applications, after receiving the payment processing request, the server can directly deduct the corresponding resources from the payment account according to the preset payment processing process without executing the above judgment step. If the deduction fails, the second amount of resources can be deducted from the account of the third-party resource provider. Alternatively, the resources can be deducted from the payment account according to the preset payment processing process. If the amount of the deducted resources is less than the second amount, the remaining resources to be deducted can be deducted from the account of the third-party resource provider.

[0092] As an implementation mode, optionally, the payer account described in the embodiment of this specification may include one or more accounts, and the first quantity represents the quantity of available resources in any available account in the payer account or the total quantity of available resources in each available account in the payer account.

[0093] The payer account may represent an account storing resources payable by the user, and may specifically include a user account that can store available resources allocated to the user in a payment application for processing payment services, a service account associated with the target application that can provide resources to the user, a user's bank card account, an account used for advance consumption by the user, an account used to store acquired preferential resources that can be redeemed, etc.

[0094] The bank card can be the bank card that the user binds and uses in the payment application; the account used for advance consumption can be an account provided by the payment application or a third-party service provider, in which the user can overdraw and has a fixed refund date; the account for preferential resources that can be redeemed can be an account used to store resources such as red envelopes, coupons, and discount coupons that are collected by users or issued by the payment application and can be redeemed by users when making payments.

[0095] In actual applications, if multiple accounts of a user can be used independently, they can also be used in combination. For example, if a priority is set, the second amount of resources can be deducted from the account with the highest priority; if no priority is set, the second amount of resources can be randomly deducted from any account that can complete the payment independently, where the priority can be set by the user or by the server of the payment application. For another example, if the number of available resources in the account with a high priority is less than the second amount, or the number of available resources in each account is less than the second amount, the resources are deducted from the payer's account using a combined payment method, and the second amount of resources are added to the payee's account.

[0096] In actual applications, if the available resources in the payment account used by the user or after the combination of multiple accounts is still less than the second amount of resources, the second amount of resources can be deducted from the account of the third-party resource provider, or the third amount of resources can be deducted from the account of the third-party resource provider, where the third amount can represent the difference between the second amount and the amount of available resources in the payer's account. Specifically, part of the resources required to be paid can be deducted from the payer's account, and the remaining resources required to be paid can be deducted from the account of the third-party resource provider.

[0097] As an implementation method, if the third-party resource provider advances the payment for the user, the user may be notified. Optionally, after deducting the transaction amount of resources from the account of the third-party resource provider in the embodiment of this specification, the following may also be included:

[0098] Sending a prompt message indicating that the bill has not been settled to the first device of the payer.

[0099] In the embodiments of this specification, the prompt information can be used to remind the user that there is a transaction bill that has not been settled; or to remind the user that there is a sum of money that needs to be repaid, etc. It can be sent to the first device in the form of an application notification; it can also be sent to the first device in the form of a text message or instant messaging; or it can be displayed on the first device The bill details page is used to remind the user. The first device can obtain the prompt information sent by the server indicating that the bill has not been settled, and display an information page containing the prompt information.

[0100] Figure 5 A schematic diagram of multiple pages of prompt information displayed in a first device according to an embodiment of this specification. Figure 5 As shown, page 510 may represent a display page containing prompt information, specifically, a bill page opened by a user in a payment application, which may include prompt information 5104 , and the page may be jumped to page 520 by clicking the page jump control 5104 .

[0101] Page 510 may also include a summary area 514 for displaying summary information, which may display the month of the bill viewed by the user, the total amount of resource inflows and outflows in that month, the extent of the expenditure budget, and an analysis control 5102 for analyzing income and expenditure, such as income and expenditure analysis; it may also include a transaction area 516 for displaying transaction status, which may display the trademark of the consumer merchant or icons set by the user, such as A, B, and may also display the transaction type such as catering, the name of the transaction party having a transaction with the user such as Name A, Name B, etc., the transaction time, transaction amount, and current transaction status, etc.; it may also include a search control 512, wherein 512 may be used to search for information such as the name of the transaction user contained in the bill and the date of consumption.

[0102] like Figure 5 As shown, the user can click on the to-be-completed control 5104 in the transaction area 516 to jump to the bill details page 520. The page 520 can represent a display page containing prompt information, and specifically can represent the bill details page opened by the user in the payment application. The bill details page can include a page name 522, which can include prompt information 5202, and the user can jump to page 530 by clicking on the page jump control 5202.

[0103] Page 520 may also include a description area 524 for describing the details of the bill. This area can be used to display information such as the merchant's trademark, merchant name, transaction amount, transaction status, payment instructions, payment time, and product description. The payment instructions can be used to prompt the user why the transaction is not completed "You have used the NFC pay-now-pay-later benefit, please complete the payment in time>", and the bold part here is the page jump control 5202, such as "Please complete the payment in time>", which can be clicked; it may also include a user operation area 526, which can be used for users to select bill categories, add labels, etc., and may also include an auxiliary function area 528, which contains controls that allow users to jump to corresponding function pages, such as contacting the merchant, having questions about the order, and applying for an electronic receipt and other auxiliary function controls.

[0104] like Figure 5 As shown, the user can click the control 5202 in the page 520 to jump to the pending order page 530, which may include the page name 532, which may also serve as a prompt message; it may also include a pending order detail display area 534, which may display information such as the merchant trademark, merchant name, transaction amount, transaction status, payment time, and product description; it may also include a "Pay Now" control 536 so that the user can complete the payment through the control, and the payment may be to deduct the resources corresponding to the transaction amount from the user's account and transfer the deducted resources to the account of the third-party resource provider. Figure 5 This is only for illustrative purposes, and the layout and display content of each page in the figure can be adjusted according to actual needs, and no specific limitation is made here. It is understandable that the user can also be reminded via SMS or other instant messaging methods, and can also enter the page for repayment through other links, which will not be described in detail here.

[0105] In actual applications, users can view prompt information through SMS messages, which may also include link information for entering the repayment page. Users can click on the link information to open the corresponding repayment page. The repayment page may include transaction details, complaint controls provided to users, and payment controls for immediate payment. The interface opened after clicking the link may be page 520 as shown in the figure, or page 530 as shown in the figure, which can be set according to actual needs. Users can also view prompt information through instant messaging. For example, after the user opens the payment application, he can view the message sent by the system in the chat interface of the payment application and click on the link information to open the corresponding repayment page.

[0106] As an implementation method, the user may also proactively return the resources paid by the third-party resource provider. In the embodiment of this specification, after deducting the transaction amount of resources from the account of the third-party resource provider, the following may also be included:

[0107] Acquire a bill settlement request sent by the first device; the bill settlement request is used by the payer to settle the resources provided by the third-party resource provider in response to the payment processing request;

[0108] Based on the bill settlement request, deducting resources of the transaction amount from the payment account of the payer;

[0109] The transaction amount is increased in the account of the third-party resource provider.

[0110] The bill settlement request may be generated based on the settlement operation of the payee. For example, the user finds the order information to be settled, and then actively triggers the repayment, and the first device may send a bill settlement request to the server. In the embodiments of this specification, the bill settlement request may include information about the number of resources that the third-party resource provider has advanced for the user, identification information of the payment account of the payee, etc. The number of resources in the transaction may be the amount of resources advanced for the user by the third-party resource provider at a time, or the total amount of resources advanced for the user by the third-party resource provider.

[0111] As an implementation method, when a user clicks a link in a text message, the repayment page can be displayed through an application such as a browser. After the user clicks the payment control, the user can jump to the corresponding payment application to execute the payment process. As another implementation method, when a user clicks a link in a text message, the payment application can be started, and the repayment page can be displayed in the payment application. After the user clicks the payment control, the payment interface including information such as the payment amount and payment method can be displayed. The payment page can be displayed in the form of a pop-up window. As an implementation method, if the user views the prompt information through the payment application, you can refer to Figure 5 It is understandable that the merchant information can be displayed on the page, but the resources actually deducted will be added to the account of the third-party resource provider.

[0112] Before the server obtains the bill settlement request sent by the first device, the first device can obtain the payee's preset operation on the repayment page displayed in the first device; based on the preset operation, send the bill settlement request to the server so that the server deducts the transaction resources corresponding to the payment processing request from the payee's payment account and adds transaction resources to the account of the third-party resource provider.

[0113] The preset operation may be an operation such as clicking, shaking, or showing a preset gesture. The reminder information may be a reminder information indicating that the bill corresponding to the payment processing request has not been settled. The repayment page may include information on the order amount corresponding to the payment processing, and the order amount may be the amount pre-paid for the user by the third-party resource provider when the user uses the first device to pay. The amount corresponding to the transaction resources may be less than or equal to the order amount. Specifically, after determining that there is a repayment discount, the discount amount may be deducted from the order amount to obtain the amount corresponding to the transaction resources, and the amount corresponding to the transaction resources may be transferred to the account of the third-party resource provider. The amount of transaction resources may be the order amount; specifically, it may be the actual amount paid by the user plus the discount amount of the payment application.

[0114] In actual applications, the server can also trigger the process of active deduction. Specifically, after reaching a preset time, the server can automatically deduct the resources paid by the third-party resource provider from the user's payment account. Optionally, after deducting the resources of the transaction amount from the account of the third-party resource provider in the embodiment of this specification, it can also include:

[0115] After the preset time is reached, the resources of the transaction amount are deducted from the payment account of the payer; the preset time is the time after the resources of the transaction amount are deducted from the account of the third-party resource provider;

[0116] The transaction amount is increased in the account of the third-party resource provider.

[0117] In the embodiments of this specification, resources of the number of transactions can be automatically deducted from the payment account of the payer after a preset time is reached, and added to the account of the third-party resource provider. The preset time can be obtained by adding the preset time to the starting time. The preset time can be 1 year, 5 months, 1 month, etc. The starting time can be the time when the second payment result page is generated, or the completion time of the payment processing request according to the preset payment processing flow, or the time when the resources are deducted from the third-party resource provider. The starting time can be set according to actual needs, and no specific limitation is made here. In actual applications, after the server deducts the resources of the number of transactions in the payer's account, it can send a deduction notification to the first device. The deduction notification can be sent to the first device by instant messaging, text message, in-application notification, etc.

[0118] In actual applications, if the resources in the payment account of the payer are insufficient to deduct the transaction amount after the preset time, a repayment reminder message may be sent to the first device to remind the user to repay. If the user fails to repay within the grace period, the user's credit score may be deducted. The grace period may be one week, three days, or one month after the preset time.

[0119] As an implementation mode, optionally, the method described in the embodiments of this specification may further include:

[0120] Determine whether the order to be paid corresponding to the payment processing request meets the immediate payment condition, and obtain a determination result; the immediate payment condition is used to indicate that the payment result information is obtained before the actual payment is made;

[0121] The sending the first payment result page to the first device may specifically include:

[0122] If the judgment result indicates that the payment processing request satisfies the immediate payment condition, a pre-generated first payment result page is sent to the first device.

[0123] In the embodiment of this specification, if the judgment result indicates that the payment processing request does not meet the immediate payment condition, the generated first payment result page may not be sent to the first device, and the entire payment processing flow may be waited for to be completed before generating a second payment result page and sending it to the first device.

[0124] The immediate payment conditions described in the embodiments of this specification may include at least one of the following:

[0125] The available resources of the payer are greater than or equal to the order amount corresponding to the payment processing request;

[0126] The order amount corresponding to the payment processing request is less than or equal to a preset threshold;

[0127] The transaction party of the payment processing request is a trusted transaction party; the transaction party includes at least one of the payer and the payee.

[0128] In the embodiments of this specification, to determine whether the order to be paid corresponding to the payment processing request meets the immediate payment condition, one of the above conditions may be used for judgment, or a combination of multiple conditions may be used for judgment. For example, if the number of available resources of the payee is greater than or equal to the order amount corresponding to the payment processing request, it may indicate that the immediate payment condition is met; if the number of available resources of the payee is less than the order amount corresponding to the payment processing request, it may indicate that the immediate payment condition is not met. For example, when the payment processing request meets the above three conditions, it indicates that the immediate payment condition is met. The specific content of meeting the immediate payment condition can be set according to actual business needs, and is not limited here.

[0129] It is possible to first determine whether the available resources of the payee are greater than or equal to the order amount corresponding to the payment processing request. After determining that the available resources of the payee are greater than or equal to the order amount corresponding to the payment processing request, it is possible to determine whether the order amount corresponding to the payment processing request is less than or equal to the preset threshold. If the order amount corresponding to the payment processing request is less than or equal to the preset threshold, it is possible to determine whether the transaction party of the payment processing request is a trusted transaction party. The judgment order of the three judgment conditions can be adjusted, or the judgment can be executed in parallel. It is understandable that it is also possible to determine whether the payment processing request meets the immediate payment condition based on only one of the judgment conditions. It is also possible to determine whether the payment processing request meets the immediate payment condition based on only two of the judgment conditions. The two conditions can be judged in parallel or in series, and the judgment order of the serial judgment can be interchanged. In actual applications, the number of judgment conditions and the execution order of the judgment can be determined based on actual needs, and no specific limitation is made here.

[0130] In actual applications, it is also possible to determine whether the payment processing request meets the immediate payment condition based on other factors. As a method, in the embodiments of this specification, it is also possible to determine whether the current second device or the payment account meets the preset condition. Specifically, it can be to obtain the first number of times when the third-party resource provider advances the payment for the user and the second device does not receive the advanced resources; to determine whether the first number is less than or equal to the first preset number. If the first number is less than or equal to the first preset number, it can be indicated that the preset condition is met and the first payment result page can be sent to the first device of the payer; if the first number is greater than the first preset number, it can be indicated that the preset condition is not met and the first payment result page is not sent to the first device of the payer. It can also be to obtain the second number of times when the third-party resource provider advances the payment for the user and the payee account does not receive the advanced resources; to determine whether the second number is less than or equal to the second preset number. If the second number is less than or equal to the second preset number, it can be indicated that the preset condition is met and the first payment result page can be sent to the first device of the payer; if the second number is greater than the second preset number, it can be indicated that the preset condition is not met and the first payment result page is not sent to the first device of the payer.

[0131] In practical applications, one or more of the above methods can be selected for judgment according to actual needs, and judgment can also be made in a preset order, such as parallel judgment, serial judgment according to the execution order, or only according to one of the judgment methods. It is understandable that in the above-mentioned parallel judgment method, if one of the judgment conditions is not met, the remaining judgment conditions being executed can be suspended. The specific judgment process is not specifically limited here.

[0132] As an implementation mode, optionally, the method described in the embodiments of this specification may further include:

[0133] Obtaining a payment trigger request sent by the first device; the payment trigger request is generated by the first device based on tag information in a communication tag of the second device obtained by near field communication;

[0134] Based on the payment trigger request, generating transaction identification information for representing the transaction account of the payer;

[0135] Sending the transaction identification information to the payee so that the payee generates a payment processing request based on the transaction identification information and the commodity information to be paid;

[0136] The obtaining of the payment processing request may specifically include:

[0137] Obtain the payment processing request sent by the payee.

[0138] In the embodiments of this specification, the tag information may be a string that complies with preset rules, for example, it may be a link, such as a URL link. The tag information may include identification information representing the second device, order identification information, etc., and the content of the specific tag information is not specifically limited here. The payment trigger request may be generated by the first device based on part or all of the tag information obtained from the second device after the user brings the first device close to the second device or brings the first device close to the second device.

[0139] In actual applications, the tag information may include identification information for starting the payment application, such as an application identification of the payment application. After the first device obtains the tag information, it may start the payment application according to the tag information, and may trigger the payment process based on the started payment application. The server may be a server capable of processing services related to the payment application.

[0140] The transaction identification information may be identification information indicating the payee's account information, and may be a string of characters, specifically a string recognizable by a server for processing payment services, or a string that complies with the payment rules of a payment application, such as a string beginning with 28, or a string beginning with 25, 30, etc. The length of the string may be 16 to 24 characters, or other lengths that meet the requirements, and the specific form of the string is not specifically limited here. In actual applications, the transaction identification information may be a string of characters indicating the payee's payment code.

[0141] The payment trigger request may include identification information of the payer, such as the device identification of the first device and the user identification of the payer, and may also include information of the payee, such as the user identification information of the payee, the account identification information of the payee, etc. After obtaining the trigger request, the server may generate transaction identification information corresponding to the payee according to the identification information of the payee included in the request, and send it to the payee. The cash register device of the payee may generate a payment processing request according to the transaction identification information and the information of the goods to be paid, and send the payment processing request to the server.

[0142] In actual applications, the second device connected to the cash register device can also receive the commodity information obtained by the cashier based on the commodity scanned by the cash register device. The second device can generate a payment processing request based on the commodity information and the transaction identification information, and send the payment processing request to the server. For example, the payee can determine the commodity to be paid and the amount to be paid through the second device or the cash register system connected to the second device, and wait for the payment information, which can be obtained by scanning the code image of the commodity; the second device can generate the tag information of the NFC tag based on the order information to be paid; the user can use the first device to stick the second device to obtain the tag information of the NFC tag, and send a payment trigger request to the server. After receiving the payment trigger request sent by the first device, the server can determine whether the order to be paid meets the immediate payment condition based on the information related to the transaction order contained in the payment trigger request. If the immediate payment condition is met, the immediate payment identification can be included in the transaction identification information and sent to the second device or the cash register system connected to the second device; the second device or the cash register system connected to the second device can generate a payment processing request containing the immediate payment identification based on the transaction identification information and send it to the server.

[0143] As an implementation method, the transaction identification information may include identification information indicating whether the order to be paid corresponding to the payment processing request satisfies the immediate payment condition; if the payment processing request satisfies the immediate payment condition, the transaction identification information may include identification information indicating that the immediate payment condition is satisfied, which can also be called the immediate payment identification. The immediate payment identification can be used to identify that the transaction currently being processed can be paid immediately, and the first payment result page can be sent to the first device before completing the entire payment processing process.

[0144] In actual applications, the payment processing request may also be sent from the first device to the server. Specifically, the first device obtains tag information from the communication tag of the second device through near field communication, generates a payment processing request based on the tag information, and sends it to the server. The tag information may include order information and identification information of the payee's account.

[0145] As an implementation method, the server can determine whether to send the first payment result page to the first device by determining whether there is an immediate payment identifier in the received payment processing request. Optionally, the embodiment of this specification may also include:

[0146] Determining whether the payment processing request contains identification information indicating that the to-be-paid order corresponding to the payment processing request satisfies the immediate payment condition;

[0147] The sending of the first payment result page to the first device of the payer may specifically include:

[0148] If the payment processing request includes identification information indicating that the order to be paid corresponding to the payment processing request meets the immediate payment condition, a first payment result page is sent to the first device of the payer.

[0149] In the embodiments of this specification, the payment processing request may be generated based on the transaction identification information. If the transaction identification information includes an immediate payment identification indicating that the order to be paid meets the immediate payment condition, the payment processing request may also include the immediate payment identification. Whether the immediate payment condition is met can be determined based on the identification information. If the payment processing request does not include identification information indicating that the order to be paid corresponding to the payment processing request meets the immediate payment condition, the first payment result page may not be sent to the first device of the payer, and the second payment result page may be sent after the preset payment processing process is completed.

[0150] As an implementation method, it may also be a payment processing request sent by the payer. Optionally, obtaining the payment processing request in the embodiments of this specification may specifically include:

[0151] Obtain a payment processing request sent by the first device.

[0152] The payment processing request is generated by the first device according to the following steps:

[0153] The first device obtains tag information in the communication tag of the second device by means of near field communication; the tag information includes transaction identification information of the payee;

[0154] The payment processing request is generated based on the identification information of the payee and the transaction identification information of the payee.

[0155] In the embodiments of this specification, the transaction identification information of the payee may represent the identification information of the payee's payment account, may be a string of information representing the payee's payment code, may include transaction amount information, may include information about the goods purchased by the user, etc. The identification information of the payee may be the identification information of the payee's payment account, or may be the payee's user UID information. The payment processing request may include order information, payee account information, payee account information, etc.

[0156] In actual applications, after the cashier completes the confirmation of the product information through the cash register system, the cash register system or the second device connected to the cash register system can send a payment trigger request to the server based on the identification information of the payee and the product order information. The server generates tag information based on the payment trigger request and sends it to the second device. The first device obtains the tag information from the second device through near-field communication, generates a payment processing request based on the tag information, and sends it to the server. The tag information can include order-related information such as the order number, and can also include relevant information of the payee, such as the transaction identification information representing the payee, the string information representing the payee's payment code, etc. The payment processing request can include information on both parties to the transaction, order information to be processed, etc.

[0157] After receiving the payment processing request, the server can determine whether the payment order corresponding to the payment processing request satisfies the immediate payment condition. If the immediate payment condition is met, the server can send the first payment result page to the first device. If the immediate payment condition is not met, the server may not send the first payment result page to the first device, and may send the second payment result page to the first device after the payment processing process is completed.

[0158] Based on the same idea, this specification also provides a method in which the first device is the execution subject. Figure 6 A flow chart of a method for processing a payment service provided in an embodiment of this specification. From a program perspective, the execution subject of the process may be a program or application client installed on a first device. From a hardware perspective, the execution subject of the process may be a first device. Specifically, it may be a mobile terminal such as a mobile phone, a phone watch, a wearable smart device, and a tablet computer.

[0159] Step 602: The first device obtains near field communication tag information of the second device through near field communication.

[0160] In the embodiments of this specification, tag information is used to trigger the generation of a payment processing request. The method of near field communication may be a short-distance communication method such as Bluetooth communication, NFC communication, and WIFI communication. The tag information may be a string that conforms to preset rules, for example, it may be a link, such as a URL link. The tag information may include identification information representing the second device, order identification information, and may also include token information generated according to the tag information, etc. The content of the specific tag information is not specifically limited here. The payment processing request may include tag information obtained from the second device and payer information stored in the first device; the payer information may include information such as the payer's account number, payer account, and payer ID.

[0161] Among them, the first device can generate a payment trigger request based on the tag information and send it to the server. The server can generate the transaction identification information of the payer based on the payment trigger request and send it to the second device. The second device can generate a payment processing request based on the transaction identification information and send it to the server. The server determines whether the order to be paid corresponding to the payment processing request meets the immediate payment condition. If so, it can generate a first payment result page and send it to the first device; then, after completing the order to be paid based on the preset payment processing process, it can generate a second payment result page and send it to the first device.

[0162] Step 604: Obtain the first payment result page sent by the server.

[0163] In the embodiment of this specification, the first payment result page is sent by the server before the transaction resources corresponding to the payment processing request are transferred to the payment account of the payee; the first payment result page is used to indicate that the communication step based on near-field communication in the online transaction process has been completed. The first payment result information can indicate that the short-range communication between the first device and the second device has been completed, and the payee can take the first device away from the second device. The transaction resource can be the amount that the payee should pay. The first payment result page can also display the amount payable by the payee, which can be the amount after the merchant has made a discount.

[0164] Step 606: Obtain the second payment result page sent by the server.

[0165] In the embodiment of this specification, the second payment result page is sent by the server after the transaction resources are transferred to the payment account of the payee. If the resources received by the payee are paid by the payer, the second payment result page can display the amount actually paid by the payer; the actual payment amount of the payer can be the amount actually paid by the payer. If the resources received by the payee are paid by a third-party resource provider, the third payment result page can display the amount paid by the third-party resource provider, and the amount paid by the third-party resource provider can be the amount corresponding to the amount payable by the payer. The third-party resource provider can be a service provider that can provide resources other than the payer and the payee, such as a payment application, or other service providers that have a cooperative or affiliated relationship with the payment application.

[0166] Optionally, in the embodiment of this specification, if the transaction resource is a resource provided by a third-party resource provider; the third-party resource provider is a service provider other than the payer and the payee that can provide resources; the method may further include:

[0167] Obtaining prompt information sent by the server indicating that the bill has not been settled;

[0168] An information page containing the prompt information is displayed.

[0169] Optionally, in the embodiments of this specification, if the transaction resources are resources provided by a third-party resource provider; the third-party resource provider is a service provider other than the payer and the payee that can provide resources;

[0170] The method may further comprise:

[0171] Acquire a preset operation of the payer on the repayment page displayed on the first device; the repayment page includes information on the order amount corresponding to the payment process;

[0172] Based on the preset operation, a bill settlement request is sent to the server so that the server deducts the transaction resources corresponding to the payment processing from the payment account of the payer and adds the transaction resources to the account of the third-party resource provider.

[0173] Optionally, the repayment page described in the embodiment of this specification may be displayed by the first device based on a preset operation of the payer on a page containing reminder information displayed in the first device; the reminder information is a reminder information indicating that the bill corresponding to the payment processing request has not been settled.

[0174] For the same concepts or features in this embodiment as those in the above embodiments, reference can be made to the descriptions of the above embodiments, which will not be repeated here.

[0175] In order to more clearly illustrate a payment processing method provided in the embodiments of this specification, Figure 7 A swim lane diagram of a payment processing method provided in an embodiment of this specification. Figure 7 As shown, the solution may include a communication phase, a first payment result page generation phase, and a second payment result page generation phase, which may specifically include:

[0176] Step 702: The first device obtains the near field communication tag information of the second device.

[0177] The second device includes an NFC tag, or the second device and the NFC tag are connected via a wired or wireless method.

[0178] Step 704: Generate a payment trigger request based on the tag information.

[0179] Step 706: The server obtains the payment trigger request sent by the first device.

[0180] Step 708: Determine whether the order to be paid corresponding to the payment trigger request meets the immediate payment condition;

[0181] If the immediate payment condition is met, step 712 may be executed: based on the payment trigger request, transaction identification information containing the immediate payment identifier may be generated; if the immediate payment condition is not met, step 710 may be executed: based on the payment trigger request, transaction identification information without the immediate payment identifier may be generated. The transaction identification information may be used to indicate the transaction identification information of the transaction account of the payer. In actual applications, if the immediate payment condition is not met, transaction identification information containing identification information indicating that the immediate payment condition is not met may also be generated.

[0182] Step 714: Send the transaction identification information to the payee's second device.

[0183] Step 716: The second device generates a payment processing request according to the transaction identification information and the information of the commodity to be paid.

[0184] In actual applications, the cash register system associated with the second device may also generate or send a payment processing request to the server.

[0185] Step 718: The server obtains the payment processing request sent by the payee.

[0186] Step 720: Determine whether the payment processing request contains an immediate payment flag.

[0187] If the payment processing request contains an immediate payment identifier, step 722 may be executed: sending a first payment result page to the first device of the payer, so that the first device executes step 724: the first device obtains the first payment result page sent by the server.

[0188] When executing steps 720 and / or 722, the server may execute the resource transfer process synchronously or asynchronously, and specifically may execute step 726: the server determines whether the first quantity of resources in the payer's payment account is greater than or equal to the second quantity of transaction resources corresponding to the payment processing request.

[0189] If the first amount of resources in the payment account of the payer is greater than or equal to the second amount of transaction resources corresponding to the payment processing request, step 730 may be executed: the second amount of resources may be deducted from the payment account of the payer. If the first amount of resources in the payment account of the payer is less than the second amount of transaction resources corresponding to the payment processing request, step 728 may be executed: the second amount of resources may be deducted from the account of the third-party resource provider.

[0190] In the embodiment of this specification, the second amount of resources deducted from the payment account of the payer can be the actual amount paid by the user plus the preferential amount given by the payment application. The deducted second amount of resources can be added to the payment account of the payee. In actual application, if the payment processing request does not contain the immediate payment mark, the relevant steps of resource transfer can also be executed, and step 726 or step 730 can be executed.

[0191] Step 732: The server sends a second payment result page to the payer's first device.

[0192] If resources are deducted from a third-party resource provider, the second payment result page may also include information indicating the resources provided by the third-party resource provider, and may also include prompt information prompting the user to repay.

[0193] Step 734: The first device obtains the sent second payment result page. In actual applications, the server may send to the first device page information for generating a display page, and the first device may display the corresponding page based on the obtained page information, such as the first payment result page, the second payment result page, the prompt page, etc. The same concepts or features as those in the above embodiments in this embodiment can refer to the description of the above embodiments, which will not be repeated. It should be understood that the order of some steps in the method described in the embodiments of this specification can be exchanged with each other according to actual needs, or some steps can be omitted or deleted. For example, it is not necessary to judge whether the order or request meets the immediate payment condition. After obtaining the request, the server feeds back the first payment result page to the first device, and the above steps 708, 720 and other steps can be omitted; for example, it is also possible not to judge the account balance of the payee, and the third resource party can be used to provide resources or deduct resources from the payee's account, and the above step 726 can be omitted.

[0194] It will be understood that if the information obtained or used by the server in each embodiment of this specification contains information that requires user authorization for use, this information is obtained or used with the user's authorization, for example, the authorization agreement is provided to the user before or during the user's use of the payment application, and the user chooses to agree to the authorization agreement.

[0195] Through the above method, when the current transaction can be paid immediately, the first payment result page can be displayed to the user first, so that the user can know in advance whether the transaction is successful or failed, reducing the time the user waits for the payment result and improving the user's payment experience.

[0196] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method. Figure 8 The embodiments of this specification provide corresponding to Figure 2 A schematic diagram of the structure of a payment processing device. Figure 8 As shown, the device may include:

[0197] The payment processing request acquisition module 802 is used to acquire a payment processing request; the payment processing request is triggered by the first device of the payer and the second device of the payee based on near field communication;

[0198] The first payment result page sending module 804 is used to send the first payment result page to the first device of the payer before the transaction resources corresponding to the payment processing request are transferred to the payment receiving account of the payee; the first payment result page is used to indicate that the communication step based on the near field communication in the online transaction process has been completed;

[0199] The second payment result page sending module 806 is used to send the second payment result page to the first device of the payer after the transaction resources are transferred to the payment account of the payee; the second payment result page is used to indicate that the resource transfer step has been completed.

[0200] based on Figure 8 The present specification also provides some specific implementation schemes of the method, which are described below. Optionally, the device includes a first payment result page generation module, which can be specifically used to: determine the order amount information in the order information to be processed; and generate a first payment result page containing the order amount information.

[0201] Optionally, the device includes a second payment result page generation module, which may specifically include: a payment processing request processing unit, used to process the payment processing request according to a preset payment processing process, send the transaction resources corresponding to the payment processing request to the payee's payment account, and obtain payment result information; a second payment result page generation unit, used to generate the second payment result page based on the payment result information; the second payment result page includes information on the actual payment amount of the payee.

[0202] Optionally, the second payment result page also includes at least one of the following: information on the amount payable, information on the amount of exemption enjoyed by the user, and information on the payment method.

[0203] Optionally, the payment processing request processing unit can be specifically used to: if the resources of the transaction quantity corresponding to the payment processing request cannot be deducted from the payment account of the payer, then the resources of the transaction quantity will be deducted from the account of a third-party resource provider; the third-party resource provider is a service provider other than the payer and the payee that can provide resources; and the resources of the transaction quantity will be added to the payee's collection account.

[0204] Optionally, the payment processing request processing unit can be specifically used to: determine whether a first quantity of resources in the payer's payment account is greater than or equal to a second quantity of transaction resources corresponding to the payment processing request, and obtain a judgment result; if the judgment result indicates that the first quantity is greater than or equal to the second quantity, deduct the second quantity of resources from the payer's payment account; if the judgment result indicates that the first quantity is less than the second quantity, deduct the second quantity of resources from the account of a third-party resource provider; the third-party resource provider is a service provider other than the payer and the payee that can provide resources; and increase the second quantity of resources in the payee's collection account.

[0205] Optionally, the payer account includes one or more accounts, and the first quantity represents the quantity of available resources in any available account in the payer account or the total quantity of available resources in each available account in the payer account.

[0206] Optionally, the second payment result page generation module also includes a prompt information sending unit, which can be specifically used to: send a prompt information indicating that the bill has not been settled to the first device of the payer.

[0207] Optionally, the second payment result page generation module also includes a payment account resource deduction unit, which can be specifically used to: obtain a bill settlement request sent by the first device; the bill settlement request is used by the payer to settle the resources provided by the third-party resource provider for the payment processing request; based on the bill settlement request, deduct the resources of the transaction quantity from the payer's payment account; and increase the resources of the transaction quantity in the account of the third-party resource provider.

[0208] Optionally, the second payment result page generation module can be specifically used to: deduct the resources of the transaction quantity from the payment account of the payer after a preset time is reached; the preset time is the time after the resources of the transaction quantity are deducted from the account of the third-party resource provider; and add the resources of the transaction quantity to the account of the third-party resource provider.

[0209] Optionally, the device may further include an immediate payment condition judgment module, which may be specifically used to: judge whether the order to be paid corresponding to the payment processing request satisfies the immediate payment condition, and obtain a judgment result; the immediate payment condition is used to indicate that the payment result information is obtained before the actual payment is made.

[0210] The sending of the first payment result page to the first device of the payer specifically includes: if the judgment result indicates that the payment processing request satisfies the immediate payment condition, sending a pre-generated first payment result page to the first device of the payer.

[0211] Optionally, the immediate payment condition includes at least one of the following: the amount of available resources of the payer is greater than or equal to the order amount corresponding to the payment processing request; the order amount corresponding to the payment processing request is less than or equal to a preset threshold; the transaction party of the payment processing request is a trusted transaction party; the transaction parties include at least one of the payer and the payee.

[0212] Optionally, the device may also include a transaction identification sending module, which can be specifically used to: obtain a payment trigger request sent by the first device; the payment trigger request is generated by the first device based on the tag information in the communication tag of the second device via near-field communication; based on the payment trigger request, generate transaction identification information for representing the transaction account of the payer; send the transaction identification information to the payee, so that the payee generates a payment processing request based on the transaction identification information and the commodity information to be paid.

[0213] Optionally, the transaction identification information includes identification information indicating that the order to be paid corresponding to the payment processing request meets the immediate payment condition.

[0214] Optionally, the device may further include an immediate payment identification judgment module, which may be specifically used to: judge whether the payment processing request contains identification information indicating that the order to be paid corresponding to the payment processing request meets the immediate payment condition.

[0215] The sending of the first payment result page to the first device of the payer specifically includes: if the payment processing request contains identification information indicating that the order to be paid corresponding to the payment processing request meets the immediate payment condition, then sending the first payment result page to the first device of the payer.

[0216] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method. Fig. 9 The embodiments of this specification provide corresponding to Figure 6 A schematic diagram of the structure of a payment processing device. Fig. 9 As shown, the device may include:

[0217] The tag information acquisition module 902 is used to acquire the tag information of the near field communication of the second device through the near field communication method; the tag information is used to trigger the generation of the payment processing request;

[0218] The first payment result page acquisition module 904 is used to acquire the first payment result page sent by the server; the first payment result page is sent by the server before the transaction resources corresponding to the payment processing request are transferred to the payment account of the payee; the first payment result page is used to indicate that the communication step based on near field communication in the online transaction process has been completed;

[0219] The second payment result page acquisition module 906 is used to acquire the second payment result page sent by the server; the second payment result page is sent by the server after the transaction resources are transferred to the payment account of the payee.

[0220] based on Fig. 9 The present specification also provides some specific implementation schemes of the method, which are described below. Optionally, if the transaction resource is a resource provided by a third-party resource provider; the third-party resource provider is a service provider that can provide resources other than the payer and the payee; the device may also include an information page display module, which can be specifically used to: obtain the prompt information sent by the server indicating that the bill has not been settled; and display an information page containing the prompt information.

[0221] Optionally, if the transaction resources are resources provided by a third-party resource provider; the third-party resource provider is a service provider other than the payer and the payee that can provide resources; the device may also include a payer repayment module, which can be specifically used to: obtain the payer's preset operation on the repayment page displayed in the first device; the repayment page contains information on the order amount corresponding to the payment processing; based on the preset operation, send a bill settlement request to the server, so that the server deducts the transaction resources corresponding to the payment processing from the payer's payment account, and adds transaction resources to the account of the third-party resource provider.

[0222] Optionally, the repayment page is displayed by the first device based on a preset operation of the payer on a page containing reminder information displayed in the first device; the reminder information is reminder information indicating that the bill corresponding to the payment processing request has not been settled.

[0223] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method. Fig.10 This is a schematic diagram of the structure of a payment processing device provided in an embodiment of this specification. Fig.10 As shown, the device 1000 may include: at least one processor 1010; and a memory 1030 communicatively connected to the at least one processor; wherein the memory 1030 stores instructions 1020 executable by the at least one processor 1010, and the instructions are executed by the at least one processor 1010 so that the at least one processor 1010 can implement the above-mentioned payment processing method.

[0224] Based on the same idea, the embodiment of this specification also provides a computer-readable medium corresponding to the above method. The computer-readable medium stores computer-readable instructions, and the computer-readable instructions can be executed by a processor to implement the above payment processing method.

[0225] Each embodiment in this specification is described in a progressive manner. The same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. Fig.10 As for the device shown, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

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

[0227] In the 1990s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0228] The controller can be implemented in any appropriate manner, for example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.

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

[0230] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0231] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

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

[0233] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0234] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

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

[0236] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

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

[0238] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

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

[0240] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A payment processing method, comprising: Get payment processing request; The payment processing request is triggered by a first device of the payer and a second device of the payee based on near field communication; Before the transaction resources corresponding to the payment processing request are transferred to the payment account of the payee, a first payment result page is sent to the first device of the payee; the first payment result page is used to indicate that the communication step based on near-field communication in the online transaction process has been completed; the first payment result page contains result information indicating payment success or payment failure.

2. The method according to claim 1, further comprising: After the transaction resource is transferred to the payment account of the payee, sending a second payment result page to the first device of the payee; The second payment result page is used to indicate that the resource transfer step has been completed.

3. According to the method of claim 1, the first device is a user terminal device having a function of reading an NFC tag; and the second device is a device associated with the NFC tag.

4. The method according to claim 1, wherein the payment processing request includes order information to be processed; The method further comprises: Determine the order amount information in the order information to be processed; A first payment result page including the order amount information is generated.

5. The method according to claim 2, further comprising: Processing the payment processing request according to a preset payment processing flow, sending the transaction resources corresponding to the payment processing request to the payment receiving account of the payee, and obtaining payment result information; Based on the payment result information, the second payment result page is generated; the second payment result page includes information on the actual payment amount of the payer.

6. According to the method of claim 5, the second payment result page also includes at least one of the payable amount information, user's exemption amount information, payment method information, and reward information.

7. The method according to claim 5, wherein sending the transaction resource corresponding to the payment processing request to the payment recipient's payment account specifically comprises: deducting the transaction resources corresponding to the payment processing request from the payment account of the payer, and sending the transaction resources to the payment account of the payee; Alternatively, deducting the transaction resources corresponding to the payment processing request from the account of the third-party resource provider, and sending the transaction resources to the payment account of the payee; The third-party resource provider is a service provider other than the payer and the payee that can provide resources; Alternatively, a third amount of resources is deducted from the payment account of the payer, and a fourth amount of resources is deducted from the account of the third-party resource provider; the sum of the third amount and the fourth amount is equal to the amount of transaction resources corresponding to the payment processing request; the third amount of resources and the fourth amount of resources are sent to the payment account of the payee.

8. The method according to claim 5, wherein sending the transaction resource corresponding to the payment processing request to the payment recipient's payment account specifically comprises: If the resources of the transaction amount corresponding to the payment processing request cannot be deducted from the payment account of the payer, the resources of the transaction amount are deducted from the account of the third-party resource provider; the third-party resource provider is a service provider other than the payer and the payee that can provide resources; The resources of the recipient's receiving account will be increased by the transaction amount.

9. The method according to claim 5, wherein sending the transaction resource corresponding to the payment processing request to the payment recipient's payment account specifically comprises: Determine whether a first quantity of resources in the payment account of the payer is greater than or equal to a second quantity of transaction resources corresponding to the payment processing request, and obtain a determination result; If the determination result indicates that the first amount is greater than or equal to the second amount, deducting the second amount of resources from the payment account of the payer; If the judgment result indicates that the first amount is less than the second amount, deducting the second amount of resources from the account of a third-party resource provider; the third-party resource provider is a service provider other than the payer and the payee that can provide resources; The second amount of resources is added to the recipient's recipient account.

10. The method according to claim 9, wherein the payer account comprises one or more accounts, and the first quantity represents the quantity of available resources in any available account in the payer account or the total quantity of available resources in each available account in the payer account.

11. The method according to claim 8, after deducting the transaction amount of resources from the account of the third-party resource provider, further comprising: Sending a prompt message indicating that the bill has not been settled to the first device of the payer.

12. The method according to claim 8, after deducting the transaction amount of resources from the account of the third-party resource provider, further comprising: Obtaining a bill settlement request sent by the first device; The bill settlement request is used by the payer to settle the resources provided by the third-party resource provider in response to the payment processing request; Based on the bill settlement request, deducting resources of the transaction amount from the payment account of the payer; The transaction amount is increased in the account of the third-party resource provider.

13. The method according to claim 8, after deducting the transaction amount of resources from the account of the third-party resource provider, further comprising: After the preset time is reached, the resources of the transaction amount are deducted from the payment account of the payer; The preset time is the time after the resources of the transaction amount are deducted from the account of the third-party resource provider; The transaction amount is increased in the account of the third-party resource provider.

14. The method according to claim 1, further comprising: Determine whether the order to be paid corresponding to the payment processing request meets the immediate payment condition, and obtain a determination result; The instant payment condition is used to indicate that payment result information is obtained first and then actual payment is made; The sending the first payment result page to the first device of the payer specifically includes: If the judgment result indicates that the payment processing request satisfies the immediate payment condition, a pre-generated first payment result page is sent to the first device of the payer.

15. The method according to claim 14, wherein the immediate payment condition comprises at least one of the following: The available resources of the payer are greater than or equal to the order amount corresponding to the payment processing request; The order amount corresponding to the payment processing request is less than or equal to a preset threshold; The transaction party of the payment processing request is a trusted transaction party; the transaction party includes at least one of the payer and the payee; The number of times that the second device fails to receive the advanced resources is less than or equal to a first preset number of times; The number of times that the payee's account has not received the advanced paid resources is less than or equal to a second preset number of times.

16. The method according to claim 1, further comprising: Obtaining a payment trigger request sent by the first device; The payment trigger request is generated by the first device based on tag information in a communication tag of the second device obtained by near field communication; Based on the payment trigger request, generating transaction identification information for representing the transaction account of the payer; Sending the transaction identification information to the payee, the payee generating a payment processing request based on the transaction identification information and information of the commodity to be paid; The obtaining of the payment processing request specifically includes: Obtain the payment processing request sent by the payee.

17. According to the method of claim 16, the transaction identification information is a character string representing the payment code of the payer; and / or the transaction identification information includes identification information indicating that the order to be paid corresponding to the payment processing request meets the immediate payment condition.

18. The method according to claim 17, further comprising: Determining whether the payment processing request contains identification information indicating that the order to be paid corresponding to the payment processing request meets the immediate payment condition; The sending the first payment result page to the first device of the payer specifically includes: If the payment processing request includes identification information indicating that the order to be paid corresponding to the payment processing request meets the immediate payment condition, a first payment result page is sent to the first device of the payer.

19. The method according to claim 1, wherein obtaining a payment processing request comprises: Obtain a payment processing request sent by the first device; wherein the first device obtains tag information of the second device by means of near field communication; the payment processing request is generated based on identification information of the payer and transaction identification information of the payee; the tag information includes transaction identification information of the payee; the transaction identification information of the payee indicates identification information of the payee's payment account.

20. A payment processing method, comprising: The first device obtains the near field communication tag information of the second device through near field communication; The tag information is used to trigger the generation of a payment processing request; Obtain a first payment result page sent by the server; the first payment result page is sent by the server before the transaction resources corresponding to the payment processing request are transferred to the payment account of the payee; the first payment result page is used to indicate that the communication step based on near-field communication in the online transaction process has been completed; the first payment result page contains result information indicating payment success or payment failure.

21. The method according to claim 20, further comprising: Obtain a second payment result page sent by the server; the second payment result page is sent by the server after the transaction resources are transferred to the payment account of the payee.

22. The method according to claim 20, if the transaction resource is a resource provided by a third-party resource provider; The third-party resource provider is a service provider other than the payer and the payee that can provide resources; The method further comprises: Obtaining prompt information sent by the server indicating that the bill has not been settled; An information page containing the prompt information is displayed.

23. The method according to claim 20, if the transaction resource is a resource provided by a third-party resource provider; The third-party resource provider is a service provider other than the payer and the payee that can provide resources; The method further comprises: Acquire a preset operation of the payer on the repayment page displayed on the first device; the repayment page includes information on the order amount corresponding to the payment process; Based on the preset operation, a bill settlement request is sent to the server so that the server deducts the transaction resources corresponding to the payment processing from the payment account of the payer and adds the transaction resources to the account of the third-party resource provider.

24. According to the method according to claim 23, the repayment page is displayed by the first device based on the preset operation of the payer on the page containing reminder information displayed in the first device; the reminder information is reminder information indicating that the bill corresponding to the payment processing request has not been settled.

25. The method according to claim 20, wherein the tag information includes transaction identification information indicating the payment recipient's payment account; the method further comprises: The first device generates the payment processing request based on the identification information of the payer and the transaction identification information of the payee.

26. A payment processing device, comprising: A payment processing request acquisition module, used to acquire a payment processing request; The payment processing request is triggered by a first device of the payer and a second device of the payee based on near field communication; A first payment result page sending module, used for sending a first payment result page to a first device of the payee before the transaction resources corresponding to the payment processing request are transferred to the payment receiving account of the payee; the first payment result page is used to indicate that the communication step based on near field communication in the online transaction process has been completed; the first payment result page contains result information indicating payment success or payment failure; The second payment result page sending module is used to send the second payment result page to the first device of the payer after the transaction resources are transferred to the payment account of the payee; the second payment result page is used to indicate that the resource transfer step has been completed.

27. A payment processing device, comprising: A tag information acquisition module, used to acquire the tag information of the near field communication of the second device by means of near field communication; The tag information is used to trigger the generation of a payment processing request; a first payment result page acquisition module, used to acquire a first payment result page sent by the server; the first payment result page is sent by the server before the transaction resources corresponding to the payment processing request are transferred to the payment receiving account of the payee; the first payment result page is used to indicate that the communication step based on near field communication in the online transaction process has been completed; the first payment result page contains result information indicating payment success or payment failure; The second payment result page acquisition module is used to acquire the second payment result page sent by the server; the second payment result page is sent by the server after the transaction resources are transferred to the payment account of the payee.

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

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

Images