Payment processing method, apparatus and device, and medium

Abstract

Disclosed in embodiments of the present description are a payment processing method, apparatus and device, and a medium. The solution comprises: acquiring a payment processing request, wherein the payment processing request is triggered by a first device of a payer and a second device of a payee on the basis of near field communication; before a transaction resource corresponding to the payment processing request is transferred to a receiving account of the payee, sending a first payment result page to the first device of the payer, wherein the first payment result page is used for indicating that the near field communication-based communication step in an online transaction process has been completed; and after the transaction resource is transferred to the receiving account of the payee, sending a second payment result page to the first device of the payer, wherein the second payment result page is used for indicating that the resource transfer step has been completed.

Description

Payment processing method, device, equipment and medium

[0001] The present application claims priority to the Chinese patent application No. 202411260271.0, filed on September 9, 2024, and entitled "A payment processing method, device, equipment and medium", the whole content of which is incorporated herein by reference. TECHNICAL FIELD

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

[0003] With the development of computer technology, more and more businesses can be realized through near field communication, such as mobile payment, access control and exit management, data transmission and information exchange, etc. In recent years, near field communication technology has been widely used in payment business due to its low cost and convenient use, such as taking public transportation by NFC card swiping.

[0004] Therefore, how to improve the user payment experience in the near field communication payment mode is a technical problem to be solved. SUMMARY

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

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

[0007] The embodiments of the present specification provide a payment processing method, which includes:

[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 a near field communication mode;

[0009] Before the transaction resource corresponding to the payment processing request is transferred to the payee's payee account, a first payment result page is sent to the first device of the payer; 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;

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

[0011] The embodiments of the present specification provide a payment processing method, which includes:

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

[0013] The first payment result page sent by the server is acquired; the first payment result page is sent by the server before a transaction resource corresponding to the payment processing request is transferred to a payment account of the payee; the first payment result page is used to indicate that a near field communication-based communication step in an online transaction process has been completed;

[0014] The second payment result page sent by the server is acquired; the second payment result page is sent by the server after the transaction resource is transferred to the payment account of the payee.

[0015] The embodiment of the present specification provides a payment processing device, comprising:

[0016] A payment processing request acquisition module is configured 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 is configured to send a first payment result page to the first device of the payer before a transaction resource corresponding to the payment processing request is transferred to a payment account of the payee; the first payment result page is used to indicate that a near field communication-based communication step in an online transaction process has been completed;

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

[0019] The embodiment of the present specification provides a payment processing device, comprising:

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

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

[0022] The second payment result page obtaining module is configured to obtain a second payment result page sent by the server; the second payment result page is sent by the server after the transaction resource is transferred to the payment account of the payee.

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

[0024] The memory is in communication connection with 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 to enable the at least one processor to execute to implement a payment processing method.

[0026] The embodiment of the present specification provides a computer readable medium having computer readable instructions stored thereon, and the computer readable instructions are executable by a processor to implement a payment processing method.

[0027] The at least one embodiment in the present specification can achieve the following beneficial effects: by obtaining a payment processing request triggered based on near field communication, before the transaction resource corresponding to the payment processing request is transferred to the payment account of the payee, a first payment result page can be sent to the first device of the payer to be displayed, so that the user can know the payment information and determine that the communication step of near field communication has been completed; and then after the transaction resource is transferred to the payment account of the payee, a second payment result page is sent to the first device of the payer, so that the user determines that the payment service is also completed, so that the user can know the payment information more quickly, without staying in the near field communication stage for too long time, and the user experience is improved. BRIEF DESCRIPTION OF DRAWINGS

[0028] In order to more clearly illustrate the technical solutions in the embodiments of the present specification or the prior art, the following will briefly introduce the drawings needed to be used in the embodiment or prior art description. Obviously, the drawings in the following description are only some embodiments described in the present application, and those skilled in the art can also obtain other drawings according to these drawings without creative labor.

[0029] Fig. 1 is a schematic diagram of an application scenario of a payment processing method provided by the embodiment of the present specification;

[0030] Fig. 2 is a flowchart of a payment processing method provided by the embodiment of the present specification;

[0031] Fig. 3 is a schematic diagram of a first payment result page provided by the embodiment of the present specification;

[0032] Fig. 4 is a schematic diagram of a second payment result page provided by the embodiment of the present specification;

[0033] FIG. 5 is a multi-page schematic diagram of displaying prompt information in a first device according to an embodiment of the present specification;

[0034] FIG. 6 is a flowchart of a payment service processing method according to an embodiment of the present specification;

[0035] FIG. 7 is a swim lane diagram of a payment processing method according to an embodiment of the present specification;

[0036] FIG. 8 is a structural schematic diagram of a payment processing apparatus corresponding to FIG. 2 according to an embodiment of the present specification;

[0037] FIG. 9 is a structural schematic diagram of a payment processing apparatus corresponding to FIG. 6 according to an embodiment of the present specification;

[0038] FIG. 10 is a structural schematic diagram of a payment processing device according to an embodiment of the present specification. DETAILED DESCRIPTION

[0039] In order to make the purpose, technical solutions and advantages of one or more embodiments of the present specification clearer, the technical solutions of one or more embodiments of the present specification will be described clearly and completely below in conjunction with specific embodiments of the present specification and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present specification, rather than all the embodiments. Based on the embodiments in the present specification, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of one or more embodiments of the present specification.

[0040] Near Field Communication (NFC) is a technology that allows two electronic devices to perform wireless data transmission within a distance of a few centimeters. This short-range wireless connection is mainly used in scenarios such as mobile payment information sharing and simplifying device pairing. In the NFC payment scenario, a user can use a device supporting NFC function to make contactless payment. During the payment process, the user's device performs wireless communication with the merchant terminal through NFC, realizing fast payment. For example, in the public transportation scenario, the user terminal can be read by the gate machine on the bus as an NFC tag to complete payment; or when taking the subway, the user uses the user terminal to touch the gate machine on the subway, and the user terminal can be read by the gate machine on the subway as an NFC tag or card to complete payment.

[0041] In actual application, a user can use a mobile terminal with NFC card reading function to read payment information in a merchant device storing an NFC tag through close-range contact or contactless methods such as touch-to-touch, and complete payment based on the payment information.

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

[0043] FIG. 1 is a schematic diagram of an application scenario of a payment processing method provided in an embodiment of the present specification. As shown in FIG. 1, the scheme can include a first device 1, a server 2, and a second device 3. The first device 1 can be a user terminal device with the function of reading an NFC tag, such as a mobile phone, a tablet, a smart watch, a wearable smart device, a laptop, and the like. The second device 3 can be a device associated with an NFC tag, also referred to as an NFC device, such as a POS machine, a cash register terminal, and the like. The NFC tag can be built-in in the second device 3, or the NFC tag can be separately provided from the second device. In actual application, the first device 1 can be in a manner of being pasted or touched with the second device 3 to trigger the generation of a payment request and send the payment request to the server 2. The server 2 can send a first payment result page to the first device 1 before completing the transaction. After completing the transaction, the server 2 can send a second payment result page to the first device 1.

[0044] Next, a payment processing method provided by an embodiment of the present specification will be described in detail with reference to the drawings. FIG. 2 is a flowchart of a payment processing method provided by an embodiment of the present specification. From the program perspective, the execution subject of the flowchart can be a program or an application client loaded on an application server.

[0045] As shown in FIG. 2, the flowchart can include the following steps:

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

[0047] The payment request can be triggered by the first device of the payer and the second device of the payee in a face-to-face payment manner, for example, the payment processing request can be triggered in a scanning code manner, such as the first device scanning the payment code displayed by the second device, or the second device scanning the payment code displayed by the first device. As an implementation manner, the payment processing request can be triggered by the first device of the payer and the second device of the payee in a near field communication manner. For example, the first device can read the NFC tag information in the second device as an NFC card reader to trigger the payment processing request. For another example, the first device can be an NFC tag or a card, and the second device can be an NFC card reader to read the NFC tag information in the first device.

[0048] As an implementation manner, the first device can be a user terminal device with the function of reading an NFC tag, such as a mobile phone, a tablet, a smart watch, a wearable smart device, a laptop, and the like. The second device can 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, and the like.

[0049] The near field communication in the embodiments of the present specification can include NFC communication mode, Bluetooth communication mode, or WIFI communication mode, and the like, which can realize near field communication. The payment processing request can be sent by the payee to the server, such as the payee obtaining the identification information containing the user account information in the first device through the near field communication mode, such as a string representing the user account information, and specifically can be information representing the payment code of the first device. Then, the payment processing request can be generated based on the identification information and the order information determined by the payee. The order information can be generated based on the information such as the price of the goods and the type of the goods.

[0050] In actual application, the payment processing request can also be sent by the payer to the server, such as the payer obtaining the transaction information through the near field communication mode. The transaction information can contain the account identification information of the payee, and can also contain the transaction information determined by the payee, such as the amount of money to be paid, and the like. The payment processing request can be generated based on the obtained transaction information and the identification information of the user account of the payer. The payment processing request can include the identification information of the payer account, the identification information of the payee account, and the order information of the goods to be paid, and the like.

[0051] Step 204: sending a first payment result page to the first device of the payer before the transaction resource corresponding to the payment processing request is transferred to the payment account of the payee.

[0052] The first payment result page in the embodiments of the present specification is used to indicate that the communication step based on the near field communication in the online transaction process has 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, the payment processing flow has been started, but not all steps have been completed. It can be used to prompt the user that the communication step of the near field communication between the first device and the second device has been completed, and the first device and the second device can be far away from each other. It can also show the payment result information to the user. The payment result displayed here can be a predicted payment result, such as a result indicating that the payment is successful, so that the user can see it and move the first device and the second device away without keeping the first device and the second device close for a long time.

[0053] Step 206: sending a second payment result page to the first device of the payer after the transaction resource is transferred to the payment account of the payee.

[0054] The second payment result page in the embodiments of the present specification is used to indicate that the resource transfer step has been completed. The second payment result page can be a page generated based on a payment processing result obtained by the server after completing the payment processing procedure based on the payment processing request. The second payment result page can also indicate a final result page displayed after completing the near field communication payment. The transaction resource can be provided by the payer or can be provided by other service parties capable of providing 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 method described in one or more embodiments of the present specification can be exchanged according to actual needs, or some steps can be omitted or deleted.

[0056] The method in FIG. 2 can send the first payment result page to the first device of the payer for display before the transaction resource corresponding to the payment processing request triggered in the near field communication-based manner is transferred to the payee account of the payee, so that the user can determine that the near field communication step has been completed through the first device; and then send the second payment result page to the first device of the payer after the transaction resource is transferred to the payee account of the payee, so that the user can determine that the payment service is also completed, so that the user can quickly obtain the payment information without staying in the near field communication stage for too long time, and the user experience is improved.

[0057] Based on the method in FIG. 2, the embodiments of the present specification further provide some specific implementation schemes of the method, which are described below. As an implementation manner, optionally, the payment processing request in the embodiments of the present specification contains order information to be processed; the method can further include:

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

[0059] generating a first payment result page containing the order amount information.

[0060] After the server in the embodiments of the present specification obtains the payment processing request, the first payment result page can be generated according to the order information to be processed contained in the payment processing request, and the first payment result page can contain the order amount information in the order information.

[0061] The order information can include order amount information, and can also include commodity information, unit price information of each commodity, discount information provided by the payee, and the like. If the payee provides a discount, the order amount information can be the amount of money after the discount; if the payee does not provide a discount, the order amount information can be the original amount of money. For example, if A market has a full 100 yuan discount of 10 yuan today, and the user A purchases goods at A market at a price of 120 yuan, then the order amount information in the order information can be 110 yuan; if A market does not have a discount today, the order amount information in the order information can be 120 yuan.

[0062] In the payment processing request in the embodiments of the present specification, the account identification information of the payee and the account identification information of the payer can be included. The first payment result page can also display payment result information, such as payment success, payment failure, and the like; and can also display payee information, such as the name of the payee and the like. If the server fails to obtain the payment processing request due to network anomalies or server anomalies, the first payment result page can also be a page for displaying payment failure, and can display failure reason information, such as poor network signal, server anomaly, and the like.

[0063] FIG. 3 is a schematic diagram of a first payment result page provided by an embodiment of the present specification. As shown in FIG. 3, the page 300 can include payment result information 302, and can also include transaction amount information 304, and can also include identification information 306 of the transaction party, such as the user name of AAA, wherein the user name can be the real name of the payer or the payee, can also be the nickname information of the payer or the payee in the payment application, or can also be the trademark name of the payee account, and the like. The payment application can be an application program that provides an online resource transaction environment for the payer and the payee.

[0064] As shown in FIG. 3, the page can also include a control 308 for closing the page, such as a “finish” control. After the user clicks the control, the page can be closed, or can jump to other pages, such as the main page of the first device, the home page of the payment APP, and the like. It can be understood that if the payment result information is a failure, the payment result information 302 can be displayed as the word “payment failure”, and the reason for the payment failure can be displayed on the current page, such as network disconnection, server anomaly, and the like; or a prompt information can be displayed on the upper layer of the current page, such as “transaction anomaly, please touch the NFC to complete the payment”. FIG. 3 is only illustrative, and the first payment result page can also display payment date information, which is not limited herein.

[0065] In an embodiment, the method can further include:

[0066] The payment processing request is processed according to a preset payment processing procedure, a transaction resource corresponding to the payment processing request is sent to a payment account of the payee, and payment result information is obtained.

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

[0068] The preset payment processing procedure in the embodiments of the present specification can represent a procedure for processing a payment processing request, and specifically can be a procedure in which a server reads information carried in a payment processing request, deducts a transaction resource from an account providing the resource, and transfers the deducted transaction resource to a payee account. In actual applications, a request for deducting a resource in a payer account can also be sent to another server for managing the payer account, and the server can deduct the resource in the payer account. The server or another server can also add the corresponding resource to the account of the payee. The other server or another server can provide a transfer result of the resource to the server for processing the payment processing request, and generate the second payment result page.

[0069] The account providing the resource can be a payer account or another account capable of providing the resource. For example, a transaction resource can be deducted from another account providing services for the payer, the other resource provider can first pay for the payer user, the deducted transaction resource can be transferred to the payee account, and the like.

[0070] The actual payment amount represents the amount actually required to be paid by the payer, and can be equal to the order amount. If the payer can enjoy certain preferential treatment, the actual payment amount can be the amount after enjoying the preferential treatment, and 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 can represent the amount to be collected by the payee. It can be understood that if there is a deductible preferential resource, the preferential resource can be deducted during the payment process of the user to reduce the actual payment amount of the user, but the amount received by the payee can still be the order amount.

[0071] FIG. 4 is a schematic diagram of a second payment result page according to an embodiment of the present specification. As shown in FIG. 4, the second payment result page 400 can include payment result information 402 and payment amount information 404, and also include transaction user name 410, such as Xia A, payment amount information 406, such as 100.00 yuan, payment method information 408, such as XX bank card (0000), wherein 0000 can be the last four digits of the card number of the bank card, and also can include reward information 412 of the payment application. The reward information can be integral information or red envelope information. The reward information 412 can include a control for jumping to a page for displaying the reward information, such as a card package interface for displaying a coupon or an integral page for displaying integral information, etc.

[0072] As shown in FIG. 4, the page can also include a control 414 for closing the page, such as a “complete” control. After the user clicks the control, the page can be closed or can jump to other pages, such as the home page of the first device, the home page of the payment APP, etc. FIG. 4 is only illustrative. Some information, such as reward information, can not be displayed, and other information, such as the name of the payee, the resource information for verification, etc. can be displayed. Herein, no specific limitation is made.

[0073] As an implementation form, optionally, the second payment result page according to an embodiment of the present specification can also include at least one of the following: the amount of money to be paid, the amount of money enjoyed by the user for reduction and exemption, and the payment method information. The payment method can represent the way for deduction or the source of the deducted resource, such as a bank card, a balance stored in the payment application, a credit card, etc. The amount of money to be paid can represent the amount of money to be paid under the condition of a discount. The amount of money enjoyed by the user for reduction and exemption can represent the discount resource, such as a discount coupon, a red envelope, etc. that can be verified in the current transaction. These information can be displayed in the second payment result page shown in FIG. 4.

[0074] The transaction resource provided to the payee in the embodiment of the present specification can be provided by the payer or other service provider capable of providing resources. Optionally, the above-mentioned sending the transaction resource corresponding to the payment processing request to the payment account of the payee can specifically include the following steps:

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

[0076] or, deducting the transaction resource corresponding to the payment processing request from the account of a third resource provider and sending the transaction resource to the payment account of the payee; the third resource provider is a service provider capable of providing resources other than the payer and the payee;

[0077] or, deducting a third amount of resources from the payment account of the payer, and deducting a fourth amount of resources from the account of the third resource provider; the sum of the third amount and the fourth amount equals the amount of transaction resources corresponding to the payment processing request; sending the third amount of resources and the fourth amount of resources to the payment account of the payee.

[0078] In the embodiments of the present application, the full amount of transaction resources can be deducted from the account of the payer, or the full amount of transaction resources can be deducted from the account of the third resource provider to fully pay for the payer, or part of the transaction resources can be deducted from the account of the payer and the remaining part of the transaction resources can be deducted from the account of the third resource provider, the sum of the resources deducted from the two accounts equals the full amount of transaction resources, and the third resource provider pays for part of the resources of the payer to complete the transaction.

[0079] As an implementation form, to improve the user experience, the third resource provider can be used to pay for the user to complete the transaction. Optionally, the sending of the transaction resources corresponding to the payment processing request to the payment account of the payee can specifically include:

[0080] If the transaction amount of resources corresponding to the payment processing request cannot be deducted from the payment account of the payer, the transaction amount of resources is deducted from the account of the third resource provider; the third resource provider is a service provider capable of providing resources other than the payer and the payee.

[0081] The transaction amount of resources is added to the payment account of the payee.

[0082] The transaction amount of resources corresponding to the payment processing request cannot be deducted from the payment account of the payer, which means that the required resources cannot be successfully deducted from the payment account of the payer. For example, the resources in the payment account are insufficient, the network or server is unstable, or the like.

[0083] In actual application, after the server obtains the payment processing request, the payment account of the payer can be deducted, or it can be determined whether the balance in the payment account of the payer is greater than or equal to the amount of the transaction. If the deduction is not successful or it is determined that the balance is less than the amount of the transaction, it means that the transaction amount of resources corresponding to the payment processing request cannot be deducted from the payment account of the payer. The third resource provider can be a third party capable of providing transaction resources for the payer, which can be a management party of a payment application or other service providers associated with the payment application.

[0084] In actual application, after obtaining the payment processing request, the server can also directly deduct the corresponding transaction resource from the account of the third resource provider, adopt the third-party financing mode, and transfer the transaction resource to the account of the payee. Then, the corresponding resource is deducted from the account of the payer and added to the third resource provider.

[0085] As an implementation manner, whether the corresponding resource is deducted from the account of the payer can be determined according to the amount in the account of the payer. Optionally, the method for sending the transaction resource corresponding to the payment processing request to the account of the payee can specifically include the following steps.

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

[0087] if the determination result indicates that the first quantity is greater than or equal to the second quantity, the second quantity of the resource is deducted from the account of the payer;

[0088] if the determination result indicates that the first quantity is less than the second quantity, the second quantity of the resource is deducted from the account of the third party resource provider; the third resource provider is a service provider capable of providing resources other than the payer and the payee;

[0089] adding the second quantity of the resource to the account of the payee.

[0090] In the embodiments of the present specification, the transaction resource can represent the resource that the payer should pay to the payee, and can be the order amount. In actual application, if there is a discount, the second quantity can represent the quantity of the resource after the discount, such as the discount or discount provided by the payee, or the discount or discount provided by the payment platform. The payment processing request can include identification information of the account of the payee and identification information of the account of the payer. The identification information can be identification information generated based on the account information, or a user identifier or a device identifier of the payee or the payer, and the server can determine the account of the payee according to the identification information of the account of the payer, and deduct the second quantity of the resource from the account of the payer; and can determine the account of the payee according to the identification information of the account of the payee, and transfer the second quantity of the resource to the account of the payee.

[0091] In actual application, after obtaining the payment processing request, the server can directly deduct the corresponding resource from the account of the payer according to the preset payment processing procedure, without performing the above-mentioned determination step. If the deduction fails, the second quantity of the resource can be deducted from the account of the third resource provider. The resource can also be deducted from the account of the payer according to the preset payment processing procedure, and if the quantity of the deducted resource is less than the second quantity, the remaining resource to be deducted can be deducted from the account of the third resource provider.

[0092] As an implementation form, the payer account can include one or more accounts, and the first amount can represent an amount of available resources in any of the accounts or a total amount of available resources in each of the accounts.

[0093] The payer account can represent an account storing resources payable by the user, and can specifically include a user account in a payment application for processing payment services, and can also include a service account associated with a target application and providing resources to the user, and can also include a bank card account of the user, an account for the user to consume in advance, and an account for storing obtained discount resources that can be cancelled.

[0094] The bank card can be a bank card bound by the user in the payment application; the account for consumption in advance can be an account provided by the payment application or a third party service provider and used by the user to overdraw, and has a fixed refund date; and the account for discount resources that can be cancelled can be an account for storing resources such as red packets, coupons and discount coupons that can be cancelled when the user pays.

[0095] In actual application, if multiple accounts of the user can be used independently or in combination, the second amount of resources can be deducted from the account with the highest priority, or can be randomly deducted from any account that can independently complete the payment, and the priority can be set by the user or the server of the payment application. For example, if the amount of available resources in the account with the highest priority is less than the second amount, or the amount of available resources in each account is less than the second amount, the resources in the payer account are deducted in a combined payment manner, and the second amount of resources is added to the payee account.

[0096] In actual application, if the amount of available resources in the payer account used by the user or 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 resource provider, or the third amount of resources can be deducted from the account of the third resource provider, and the third amount can represent the difference between the second amount and the amount of available resources in the payer account. Specifically, part of the required payment resources can be deducted from the payer account, and the remaining required payment resources can be deducted from the account of the third resource provider.

[0097] As an implementation form, if the third resource provider advances the resources for the user, the user can be notified. Optionally, after the transaction amount of resources is deducted from the account of the third resource provider, the method can further include:

[0098] sending prompt information indicating that the bill is not settled to the first device of the payee.

[0099] The prompt information in the embodiments of the present specification can be used to prompt the user that the payment of a transaction bill has not been completed, or to prompt the user that there is a payment to be repaid, etc. The prompt information can be sent to the first device in the form of an application notification, or can be sent to the first device in the form of a short message or instant messaging, or can be displayed on the first device in the form of a bill detail page to prompt the user. The first device can obtain the prompt information indicating that the bill is not settled sent by the server, and display an information page containing the prompt information.

[0100] FIG. 5 is a multi-page schematic diagram of displaying prompt information in the first device according to an embodiment of the present specification. As shown in FIG. 5, page 510 can represent a display page containing prompt information, and specifically can represent a bill page opened by the user in the payment application. The page can include prompt information 5104, and the user can jump to page 520 by clicking page jump control 5104.

[0101] The page 510 can further include a summary area 514 for displaying summary information. The summary area can display the month of the bill viewed by the user, the total amount of resource inflow and outflow of the month, the degree of expenditure budget, and analysis control 5102 for analyzing income and expenditure, etc. The page can further include a transaction area 516 for displaying transaction information. The transaction area can display the trademark of the consumption merchant or the icon set by the user, such as A and B, and can also display the transaction type, such as catering, the name of the transaction party, such as name A and name B, the transaction time, the transaction amount, and the current transaction state, etc. The page can further include a search control 512, which can be used to search the name of the transaction user, the consumption date, etc. in the bill.

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

[0103] The page 520 can also include a description area 524 for describing the details of the bill, which can be used to display information such as merchant trademarks, merchant names, transaction amounts, transaction statuses, payment instructions, payment times, and product descriptions. The payment instruction can be used to prompt the user that the transaction is not completed, and the reason is "You have used the NFC first-use-after-payment benefit, please complete the payment as soon as possible >". The bold part is a page jump control 5202, such as "please complete the payment as soon as possible >", which can be clicked. The user operation area 526 can be included, which can be used for user selection of bill classification, addition of labels, and other operations. The auxiliary function area 528 can also be included, which contains controls that enable the user to jump to the corresponding function page, such as contacting the merchant, having questions about the order, and applying for an electronic receipt.

[0104] As shown in FIG. 5, the user can click the control 5202 in the page 520 to jump to the order to be completed page 530, which can include a page name 532, which can also be used as a prompt message. The details display area 534 of the order to be completed can also be included, which can display information such as merchant trademarks, merchant names, transaction amounts, transaction statuses, payment times, and product descriptions. The "immediate payment" control 536 can also be included to enable the user to complete payment through the control. The payment can be to deduct the transaction amount of resources from the user's account and transfer the deducted resources to the account of the third resource provider. FIG. 5 is only illustrative, and the layout and display content of each page in the figure can be adjusted according to actual needs, which is not limited specifically here. It can be understood that the user can also be reminded through a short message 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 application, the user can view the prompt message through a short message, and the short message can also contain link information for entering the repayment page. The user can click the link information to open the corresponding repayment page. The repayment page can include transaction detail information and can also include an appeal control provided for the user and other information. The payment control for immediate payment can also be included. The interface opened after clicking the link can be the 520 page as shown in the figure, or the 530 page as shown in the figure, which can be set according to actual needs. The user can also view the prompt message through instant messaging, such as opening the payment application and viewing the message sent by the system in the chat interface of the payment application. Clicking the link information can open the corresponding repayment page.

[0106] As an implementation manner, the user can also actively return the resources paid by the third resource provider. After the above-mentioned deduction of the transaction amount of resources from the account of the third resource provider in the embodiment of the present specification, the following can also be included:

[0107] obtaining a bill settlement request sent by the first device; the bill settlement request is used for the payor to settle the third resource provider for the resource provided by the payment processing request;

[0108] deducting the transaction amount of resources from the payment account of the payor based on the bill settlement request;

[0109] increasing the transaction amount of resources in the account of the third resource provider.

[0110] The bill settlement request can be generated based on the settlement operation of the payor. For example, the user finds the order information to be settled, and then actively triggers the repayment. The first device can send the bill settlement request to the server. In the bill settlement request in the embodiment of the present specification, the information of the transaction amount of resources paid by the third resource provider for the user, the identification information of the payment account of the payor, etc. can be included. The transaction amount of resources can be the resource quota paid by the third resource provider for the user once, or the total resource quota paid by the third resource provider for the user.

[0111] As an implementation manner, the user clicks the link in the short message, and the repayment page can be displayed through the browser application. After the user clicks the payment control, the payment process can be executed in the corresponding payment application. As another implementation manner, the user clicks the link in the short message, and the payment application can be started. The repayment page is displayed in the payment application. After the user clicks the payment control, the payment interface including the payment amount and the payment method, etc. can be displayed. The payment page can be displayed in the form of a pop-up window. As an implementation manner, if the user views the prompt information through the payment application, the repayment can be completed by referring to the operation mode in FIG. 5. It can be understood that the merchant information can be displayed in the page, but the actually deducted resources will be increased to the account of the third resource provider.

[0112] Before the server obtains the bill settlement request sent by the first device, the first device can obtain the preset operation of the payor on the repayment page displayed in the first device. Based on the preset operation, the bill settlement request is sent to the server, so that the server deducts the transaction resource corresponding to the payment processing request from the payment account of the payor, and increases the transaction resource in the account of the third resource provider.

[0113] The preset operation can be clicking, shaking, or showing a preset gesture. The reminder information can be reminder information indicating that the bill corresponding to the payment processing request is not settled. The repayment page can include information of an order amount corresponding to the payment processing, and the order amount can be an amount that the third resource provider pre-pays for the user when the user uses the first device to pay. The amount corresponding to the transaction resource can be less than or equal to the order amount, and specifically, after it is determined that there is a repayment discount, the amount corresponding to the transaction resource can be obtained by deducting the discount amount from the order amount, and the amount corresponding to the transaction resource can be transferred to the account of the third resource provider. The amount of the transaction resource can be the order amount, and specifically, the amount of the transaction resource can be the actual payment amount of the user plus the discount amount of the payment application.

[0114] In actual application, the server can also trigger the process of active deduction. Specifically, after the preset time is reached, the server can automatically deduct the resources pre-paid by the third resource provider from the payment account of the user. Optionally, after the transaction amount of resources is deducted from the account of the third resource provider in the embodiments of the present specification, the following steps can also be included:

[0115] deducting the transaction amount of resources from the payment account of the payment party after the preset time is reached, the preset time being a time after the transaction amount of resources is deducted from the account of the third resource provider;

[0116] increasing the transaction amount of resources in the account of the third resource provider.

[0117] In the embodiments of the present specification, the transaction amount of resources can be automatically deducted from the payment account of the payment party after a preset time period is reached, and added to the account of the third resource provider. The preset time can be obtained by adding the preset time period to the starting time. The preset time period 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 completing the payment processing request according to the preset payment processing process, or the time when the resources are deducted from the third resource provider, and the starting time can be set according to actual needs, which is not limited here. In actual application, after the server deducts the transaction amount of resources from the payment account of the payment party, a deduction notice can be sent to the first device. The deduction notice can be sent to the first device in the form of instant messaging, short message, in-application notification, etc.

[0118] In actual application, if the resources in the payment account of the payment party are insufficient to deduct the transaction amount of resources after the preset time, a repayment reminder information can also be sent to the first device to remind the user to repay, and if the user does not complete the repayment within the grace period, the credit score of the user can be deducted. The grace period can be one week, three days, or one month, etc. after the preset time.

[0119] As an implementation form, optionally, the method in the embodiments of the present specification can further include:

[0120] determining whether the to-be-paid order corresponding to the payment processing request satisfies an immediate payment condition to obtain a determination result; the immediate payment condition is used to indicate that the payment result information is enjoyed first and then the actual payment is performed;

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

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

[0123] In the embodiments of the present specification, if the determination result indicates that the payment processing request does not satisfy the immediate payment condition, the generated first payment result page can not be sent to the first device, and the second payment result page can be generated and sent to the first device after the entire payment processing flow is completed.

[0124] The immediate payment condition in the embodiments of the present specification can include at least one of the following:

[0125] The available resource amount of the payer is 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 the present specification, whether the to-be-paid order corresponding to the payment processing request satisfies the immediate payment condition can be determined by using one of the above conditions, or can be determined by using multiple conditions in combination. For example, if the available resource amount of the payer is greater than or equal to the order amount corresponding to the payment processing request, it can be indicated that the immediate payment condition is satisfied, and if the available resource amount of the payer is less than the order amount corresponding to the payment processing request, it can be indicated that the immediate payment condition is not satisfied. For another example, when the payment processing request satisfies the above three conditions, it indicates that the immediate payment condition is satisfied. The specific content of the immediate payment condition can be set according to actual business requirements, which is not limited herein.

[0129] The number of available resources of the payer can be determined first to see whether it is greater than or equal to the order amount corresponding to the payment processing request. After it is determined that the number of available resources of the payer is greater than or equal to the order amount corresponding to the payment processing request, it is determined 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 determined whether the transaction party of the payment processing request is a trusted transaction party. The determination order of the three determination conditions can be adjusted, or the determination can be performed in parallel. It can be understood that the determination of whether the payment processing request satisfies the instant payment condition can be performed according to only one of the determination conditions. The determination of whether the payment processing request satisfies the instant payment condition can be performed according to only two of the determination conditions. The two conditions can be determined in parallel or in series, and the determination order of the two conditions can be exchanged. In actual applications, the number of determination conditions and the determination execution order can be determined based on actual needs, which are not limited here.

[0130] In actual applications, the determination of whether the payment processing request satisfies the instant payment condition can also be performed based on other factors. As an implementation manner, it is further determined in the embodiments of the present specification whether the current second device or the payee account satisfies a preset condition. Specifically, the first number of times that the second device does not receive the paid resources in the case that the third resource provider pays for the user can be obtained. It is determined whether the first number of times is less than or equal to a first preset number of times. If the first number of times is less than or equal to the first preset number of times, it indicates that the preset condition is satisfied, and the first payment result page can be sent to the first device of the payer. If the first number of times is greater than the first preset number of times, it indicates that the preset condition is not satisfied, and the first payment result page is not sent to the first device of the payer. The second number of times that the payee account does not receive the paid resources in the case that the third resource provider pays for the user can also be obtained. It is determined whether the second number of times is less than or equal to a second preset number of times. If the second number of times is less than or equal to the second preset number of times, it indicates that the preset condition is satisfied, and the first payment result page can be sent to the first device of the payer. If the second number of times is greater than the second preset number of times, it indicates that the preset condition is not satisfied, and the first payment result page is not sent to the first device of the payer.

[0131] In actual applications, the determination can be performed according to actual needs by selecting one or more of the above manners, and can also be performed in a preset order, such as parallel determination, serial determination according to the execution order, or determination according to only one of the determination manners. It can be understood that in the parallel determination manner mentioned above, if one of the determination conditions is not satisfied, the remaining determination conditions being executed can be paused. The specific determination process is not limited here.

[0132] As an implementation manner, the method in the embodiments of the present specification can further include the following steps.

[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 through near field communication;

[0134] generating transaction identification information representing a transaction account of the payor based on the payment trigger request;

[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 to-be-paid commodity information;

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

[0137] obtaining a payment processing request sent by the payee.

[0138] In the embodiments of the present specification, the tag information can be a string in accordance with a preset rule, for example, it can be a link, such as a URL link. The tag information can include identification information of the second device, order identification information, etc. The specific content of the tag information is not limited here. The payment trigger request can be generated by the first device based on part or all of the information in the tag information obtained from the second device after the first device is close to or close to the second device.

[0139] In actual application, the tag information can include identification information for starting a payment application, such as an application identification of the payment application. The first device can start the payment application according to the tag information after obtaining the tag information, and can trigger the payment process based on the started payment application. The server can be a server capable of processing related businesses of the payment application.

[0140] The transaction identification information can be identification information representing the payor account information, which can be a string of characters. Specifically, it can be a string of characters that can be recognized by a server for processing payment business, or a string of characters that meets the payment rules of the payment application. For example, it can be a string starting with 28, or a string starting with 25, 30, etc. The length of the string can be 16 to 24 characters, or other lengths according to requirements. The specific form of the string is not limited here. In actual application, the transaction identification information can be a string representing the payor code.

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

[0142] In actual application, the second device connected to the cash register device can also receive the commodity information obtained by the cashier based on the scanning of the commodity 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 to-be-paid commodity and the to-be-paid amount of the to-be-paid information through the second device or the cash register system connected to the second device, 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 to-be-paid order information; the user can use the first device to paste 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 to-be-paid order satisfies the instant payment condition based on the information related to the transaction order included in the payment trigger request. If the instant payment condition is satisfied, the instant payment identifier 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 instant payment identifier based on the transaction identification information and send it to the server.

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

[0144] In actual application, the payment processing request can also be sent by the first device to the server. Specifically, the first device obtains the 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 can include order information and identification information of the payee account.

[0145] As an implementation, the server can determine whether the first payment result page can be sent to the first device by judging whether the immediate payment identifier exists in the received payment processing request. Optionally, the embodiments of the present specification can further include:

[0146] determining whether the payment processing request contains the identifier 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 can specifically include:

[0148] If the payment processing request contains the identifier information indicating that the to-be-paid order corresponding to the payment processing request satisfies the immediate payment condition, the first payment result page is sent to the first device of the payer.

[0149] In the embodiments of the present specification, the payment processing request can be generated based on the transaction identifier information. If the transaction identifier information contains the immediate payment identifier indicating that the to-be-paid order satisfies the immediate payment condition, the payment processing request can also contain the immediate payment identifier. Whether the immediate payment condition is satisfied can be determined according to the identifier information. If the payment processing request does not contain the identifier information indicating that the to-be-paid order corresponding to the payment processing request satisfies the immediate payment condition, the first payment result page can not be sent to the first device of the payer. After the preset payment processing procedure is completed, the second payment result page is sent.

[0150] As an implementation, the payment processing request can also be sent by the payer. Optionally, the payment processing request can be obtained in the embodiments of the present specification, which can specifically include:

[0151] The payment processing request sent by the first device is obtained.

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

[0153] The first device obtains the tag information in the communication tag of the second device through near field communication. The tag information contains the transaction identifier information of the payee;

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

[0155] The transaction identifier information of the payee in the embodiments of the present specification can represent the identifier information of the payee's payment account, can be string information representing the payee's payment code, and can further include transaction amount information, information of goods purchased by the user, and the like. The identifier information of the payer can be the identifier information of the payer's payment account or the user UID information of the payer. The payment processing request can include order information, payee account information, and payer account information, and the like.

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

[0157] The server can determine whether the payment order corresponding to the payment processing request satisfies the instant payment condition after receiving the payment processing request. If the instant payment condition is satisfied, the first payment result page can be sent to the first device. If the instant payment condition is not satisfied, the first payment result page can not be sent to the first device. The second payment result page can be sent to the first device after the payment processing flow is completed.

[0158] Based on the same idea, the present specification also provides a method with the first device as the execution subject. FIG. 6 is a flowchart of a payment service processing method according to an embodiment of the present specification. From the program perspective, the execution subject of the flow can be a program or an application client loaded on the first device. From the hardware perspective, the execution subject of the flow can be the first device. Specifically, the first device can 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 the near field communication label information of the second device through near field communication.

[0160] The tag information in the embodiments of the present specification is used to trigger the generation of a payment processing request. The near field communication mode can be Bluetooth communication, NFC communication, WIFI communication, and other near field communication modes. The tag information can be a string that meets a preset rule, for example, it can be a link, for example, a URL link. The tag information can include identification information of the second device, order identification information, and token information generated according to the tag information, and the like. The specific content of the tag information is not limited here. The payment processing request can include the tag information obtained from the second device and the payer information stored in the first device; the payer information can include the account number of the payer, the payer account, and the payer ID, and the like.

[0161] The first device can generate a payment trigger request based on the tag information and send the payment trigger request to the server. The server generates transaction identification information of the payer based on the payment trigger request and sends the transaction identification information to the second device. The second device generates a payment processing request based on the transaction identification information and sends the payment processing request to the server. The server determines whether the to-be-paid order corresponding to the payment processing request meets the instant payment condition. If the to-be-paid order meets the instant payment condition, the server generates a first payment result page and sends the first payment result page to the first device. After the to-be-paid order is completed based on the preset payment processing process, the server generates a second payment result page and sends the second payment result page to the first device.

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

[0163] The first payment result page in the embodiments of the present specification is sent by the server before the transaction resource corresponding to the payment processing request is transferred to the payment account of the payee. The first payment result page is used to indicate that the near field communication step in the online transaction process has been completed. The first payment result information can indicate that the near field communication between the first device and the second device has been completed, and the payer can take the first device away from the second device. The transaction resource can be the amount of money that the payer should pay. The first payment result page can also display the amount of money that the payer should pay. The amount of money that the payer should pay can be the amount of money after the merchant performs a discount.

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

[0165] The second payment result page in the embodiments of the present specification is sent by the server after the transaction resource is transferred to the payment account of the payee. If the resource received by the payee is paid by the payer, the second payment result page can display the actual payment amount of the payer; the actual payment amount of the payer can be the actual payment amount of the payer. If the resource received by the payee is paid by the third resource provider, the third payment result page can display the payment amount of the third resource provider, and the payment amount of the third resource provider can be the quantity corresponding to the amount to be paid by the payer. The third resource provider can be a service provider capable of providing resources other than the payer and the payee, such as a payment application, other service providers cooperating or associated with the payment application.

[0166] Optionally, in the embodiments of the present specification, if the transaction resource is a resource provided by a third resource provider; the third resource provider is a service provider capable of providing resources other than the payer and the payee; the method can further comprise:

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

[0168] Displaying an information page containing the prompt information.

[0169] Optionally, in the embodiments of the present specification, if the transaction resource is a resource provided by a third resource provider; the third resource provider is a service provider capable of providing resources other than the payer and the payee;

[0170] The method can further comprise:

[0171] Obtaining a preset operation of the payer on a repayment page displayed in the first device; the repayment page contains information of the order amount corresponding to the payment processing;

[0172] Based on the preset operation, sending a bill settlement request to the server to deduct the transaction resource from the payment account of the payer and increase the transaction resource in the account of the third resource provider.

[0173] Optionally, in the embodiments of the present specification, the repayment page can be displayed by the first device based on a preset operation of the payer on a page containing prompt information displayed in the first device; the prompt information is prompt information indicating that the bill corresponding to the payment processing request is not settled.

[0174] The same concepts or features as in the above embodiments exist in the present embodiments, and the description of the above embodiments can be referred to, which will not be repeated here.

[0175] In order to more clearly illustrate the payment processing method provided in the embodiments of the present specification, FIG. 7 is a swim lane diagram of a payment processing method provided in the embodiments of the present specification. As shown in FIG. 7, the scheme can include a communication stage, a first payment result page generation stage, and a second payment result page generation stage, and specifically can include:

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

[0177] Among them, the second device contains an NFC tag, or the second device is connected to the NFC tag through a wired or wireless manner.

[0178] Step 704: Based on the tag information, a payment trigger request is generated.

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

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

[0181] If the instant payment condition is met, step 712 can be performed: based on the payment trigger request, transaction identification information containing an instant payment identifier is generated; if the instant payment condition is not met, step 710 can be performed: based on the payment trigger request, transaction identification information not containing an instant payment identifier is generated. Among them, the transaction identification information can be used to represent the transaction identification information of the transaction account of the payer. In actual application, if the instant payment condition is not met, transaction identification information containing an identifier representing that the instant payment condition is not met is also generated.

[0182] Step 714: The transaction identification information is sent to the second device of the payee.

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

[0184] In actual application, the payment processing request can also be generated by the cash register system associated with the second device or sent to the server.

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

[0186] Step 720: Determine whether the payment processing request contains an instant payment identifier.

[0187] If the payment processing request contains an instant payment identifier, step 722 can be performed: a first payment result page is sent to the first device of the payer. So that the first device performs step 724: the first device acquires the first payment result page sent by the server.

[0188] When executing steps 720 and / or 722, the server can execute the resource transfer process synchronously or asynchronously. Specifically, step 726 can be executed: 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 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, step 730 can be executed: deduct the second quantity of resources from the payer's payment account. If the first quantity of resources in the payer's payment account is less than the second quantity of transaction resources corresponding to the payment processing request, step 728 can be executed: deduct the second quantity of resources from the account of the third resource provider.

[0190] In the embodiments described in this specification, the second amount of resources deducted from the payer's payment account can be the user's actual payment amount plus the discount granted by the payment application. The deducted second amount of resources can be added to the payee's receiving account. In practical applications, if the payment processing request does not contain an immediate payment identifier, the relevant steps for resource transfer can still be performed, such as step 726 or step 730.

[0191] Step 732: The server sends the 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 that the resources were provided by the third-party resource provider, and may also include a prompt message reminding the user to repay.

[0193] Step 734: The first device obtains the sent second payment result page. In practical applications, the server may send page information to the first device for generating and displaying the page. The first device then displays the corresponding page based on the obtained page information, such as the first payment result page, the second payment result page, a prompt page, etc. Concepts or features present in this embodiment that are identical to those in the above embodiments can be referred to the descriptions of the above embodiments, and will not be repeated here. It should be understood that the order of some steps in the methods described in the embodiments of this specification can be interchanged according to actual needs, or some steps can be omitted or deleted. For example, it is not necessary to determine whether the order or request meets the immediate payment conditions; after obtaining the request, the server sends the first payment result page back to the first device, and steps 708, 720, etc., can be omitted. Alternatively, it is not necessary to determine the payer's account balance; resources can be provided by a third-party resource provider or deducted from the payer's account, and step 726 can be omitted.

[0194] It can be understood that if the information acquired or used by the server in each embodiment of the present specification contains information that needs to be authorized by the user, the information is acquired or used under the authorization of the user, for example, the user is provided with an authorization agreement before or during the use of the payment application, and the user selects to agree to the authorization agreement.

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

[0196] Based on the same idea, the present specification also provides a device corresponding to the above method. FIG. 8 is a structural schematic diagram of a payment processing device corresponding to FIG. 2 provided by an embodiment of the present specification. As shown in FIG. 8, the device can include:

[0197] The payment processing request acquisition module 802 is configured 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 a near field communication mode;

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

[0199] The second payment result page sending module 806 is configured to send a second payment result page to the first device of the payer after the transaction resource is 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 the device of FIG. 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 configured to: determine 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 can include: a payment processing request processing unit configured to process the payment processing request according to a preset payment processing procedure, send a transaction resource corresponding to the payment processing request to a payment account of the payee, and obtain payment result information; and a second payment result page generation unit configured to generate the second payment result page based on the payment result information; the second payment result page includes information of a real payment amount of the payer.

[0202] Optionally, the second payment result page further comprises at least one of the following: the amount of money to be paid, the amount of money to be reduced, and the payment method.

[0203] Optionally, the payment processing request processing unit is specifically configured to: if the transaction amount of resources corresponding to the payment processing request cannot be deducted from the payment account of the payer, deduct the transaction amount of resources from an account of a third resource provider; the third resource provider is a service provider capable of providing resources other than the payer and the payee; and increase the transaction amount of resources in the payment account of the payee.

[0204] Optionally, the payment processing request processing unit is specifically configured to: determine whether 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, to obtain a determination result; if the determination result indicates that the first amount is greater than or equal to the second amount, deduct the second amount of resources from the payment account of the payer; if the determination result indicates that the first amount is less than the second amount, deduct the second amount of resources from an account of a third resource provider; the third resource provider is a service provider capable of providing resources other than the payer and the payee; and increase the second amount of resources in the payment account of the payee.

[0205] Optionally, the payment account comprises one or more accounts, and the first amount represents the amount of resources available in any available account of the payment account or the total amount of resources available in each available account of the payment account.

[0206] Optionally, the second payment result page generation module further comprises a prompt information sending unit, which is specifically configured to: send 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 further comprises a payment account resource deduction unit, which is specifically configured to: obtain a bill settlement request sent by the first device; the bill settlement request is used for the payer to settle resources provided by the third resource provider for the payment processing request; based on the bill settlement request, deduct the transaction amount of resources from the payment account of the payer; and increase the transaction amount of resources in the account of the third resource provider.

[0208] Optionally, the second payment result page generation module is specifically configured to: after a preset time is reached, deduct the transaction amount of resources from the payment account of the payer; the preset time is a time after the transaction amount of resources is deducted from the account of the third resource provider; and increase the transaction amount of resources in the account of the third resource provider.

[0209] Optionally, the apparatus can further include a pay-on-condition judging module, which can be specifically configured to judge whether the to-be-paid order corresponding to the payment processing request satisfies a pay-on-condition, and obtain a judging result; the pay-on-condition is used to indicate that the payment result information is enjoyed first and then the actual payment is performed.

[0210] The sending of the first payment result page to the first device of the payer can specifically include: if the judging result indicates that the payment processing request satisfies the pay-on-condition, sending the pre-generated first payment result page to the first device of the payer.

[0211] Optionally, the pay-on-condition includes at least one of the following: the available resource quantity 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; and the transaction party includes at least one of the payer and the payee.

[0212] Optionally, the apparatus can further include a transaction identifier sending module, which can be specifically configured to: obtain the 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 through the near field communication mode; generate transaction identifier information used to represent the transaction account of the payer based on the payment trigger request; and send the transaction identifier information to the payee, so that the payee generates the payment processing request based on the transaction identifier information and the to-be-paid commodity information.

[0213] Optionally, the transaction identifier information includes identifier information used to represent that the to-be-paid order corresponding to the payment processing request satisfies the pay-on-condition.

[0214] Optionally, the apparatus can further include a pay-on-condition identifier judging module, which can be specifically configured to judge whether the payment processing request includes the identifier information used to represent that the to-be-paid order corresponding to the payment processing request satisfies the pay-on-condition.

[0215] The sending of the first payment result page to the first device of the payer can specifically include: if the payment processing request includes the identifier information used to represent that the to-be-paid order corresponding to the payment processing request satisfies the pay-on-condition, sending the first payment result page to the first device of the payer.

[0216] Based on the same idea, the present specification also provides an apparatus corresponding to the above method. FIG. 9 is a structural schematic diagram of a payment processing apparatus corresponding to FIG. 6 according to an embodiment of the present specification. As shown in FIG. 9, the apparatus can include:

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

[0218] The first payment result page acquisition module 904 is configured to acquire a first payment result page sent by the server; the first payment result page is sent by the server before a transaction resource corresponding to the payment processing request is transferred to a payment account of the payee; and 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 configured to acquire a second payment result page sent by the server; the second payment result page is sent by the server after the transaction resource is transferred to the payment account of the payee.

[0220] Based on the apparatus in FIG. 9, the embodiments of the present specification further provide some specific implementation solutions of the method, which are described as follows. Optionally, if the transaction resource is a resource provided by a third resource provider; the third resource provider is a service provider capable of providing resources other than the payer and the payee; the apparatus can further include an information page display module, which is specifically configured to acquire prompt information sent by the server and indicating that a bill is not settled; and display an information page containing the prompt information.

[0221] Optionally, if the transaction resource is a resource provided by a third resource provider; the third resource provider is a service provider capable of providing resources other than the payer and the payee; the apparatus can further include a payer repayment module, which is specifically configured to acquire a preset operation of the payer on a repayment page displayed in the first device; the repayment page contains information of an order amount corresponding to the payment processing; and based on the preset operation, send a bill settlement request to the server, so as to deduct the transaction resource corresponding to the payment processing from a payment account of the payer and increase the transaction resource in an account of the third 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; and the reminder information is reminder information indicating that a bill corresponding to the payment processing request is not settled.

[0223] Based on the same idea, the embodiments of the present specification also provide a device corresponding to the above method. FIG. 10 is a structural schematic diagram of a payment processing device provided by an embodiment of the present specification. As shown in FIG. 10, the device 1000 can include at least one processor 1010, and a memory 1030 in communication connection with 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 to enable the at least one processor 1010 to implement the above payment processing method.

[0224] Based on the same idea, the embodiments of the present specification also provide a computer readable medium corresponding to the above method. The computer readable medium stores computer readable instructions executable by a processor to implement the above payment processing method.

[0225] Each of the embodiments in the present specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other. Each of the embodiments focuses on the difference from other embodiments. In particular, for the device shown in FIG. 10, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the part of the method embodiment.

[0226] In the 1990s, it was quite obvious to distinguish whether an improvement in a technology was in hardware (e.g., improvement in circuit structures of diodes, transistors, switches, etc.) or in software (improvement in method flow). However, as technology has evolved, many improvements in method flow today can be considered as direct improvements in hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structures by programming the improved method flow into hardware circuits. Therefore, it cannot be said that an improvement in a method flow cannot be implemented by hardware entity modules. For example, a programmable logic device (PLD) (e.g., a field programmable gate array (FPGA)) is an integrated circuit whose logic function is determined by user programming of the device. A digital system is "integrated" on a PLD by the designer programming it, rather than by asking a chip manufacturer to design and fabricate a custom integrated circuit chip. Moreover, instead of manually fabricating integrated circuit chips, this programming is now mostly implemented by "logic compiler" software, which is similar to software compilers used in program development, and the original code to be compiled is written in a specific programming language, which is called a hardware description language (HDL), and there are many such languages, 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., and the most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should be aware that, as long as the method flow is logically programmed in the above-mentioned hardware description languages and programmed into an integrated circuit, a hardware circuit implementing the logical method flow can be easily obtained.

[0227] The controller can be implemented in any suitable way, for example, the controller can take the form of a microprocessor or processor and a computer readable medium storing computer readable program code, such as software or firmware, executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller and an embedded microcontroller, examples of which include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also know that, in addition to being implemented in pure computer readable program code, the controller can also be implemented to perform the same functions in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers and embedded microcontrollers, etc. by logically programming the method steps. Therefore, such a controller can be considered as a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can even be considered as both a software module implementing a method and a structure within a hardware component.

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

[0229] For the sake of description, the above apparatuses are described in functional division and are described respectively. Of course, the functions of the units can be implemented in the same or multiple software and / or hardware in the implementation of the present application.

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

[0231] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks or in conjunction with the flowcharts described above.

[0232] These computer program instructions can also be stored in a computer- readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the function specified in the flowchart block or blocks or in conjunction with the flowcharts described above.

[0233] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks or in conjunction with the flowcharts described above.

[0234] In one typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory. The memory can include non-persistent memory, random access memory (RAM), and / or non-volatile memory such as read-only memory (ROM) or flash memory, among others, in a computer-readable medium. The memory is an example of computer-readable media.

[0235] Computer-readable media includes permanent and non-permanent, movable and non-movable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible to a computing device. According to the definition herein, computer-readable media does not include transitory media such as modulated data signals and carriers.

[0236] It should also be noted that the terms "comprising", "comprising" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or apparatus that includes a list of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or apparatus. Without more limitations, the element defined by the statement "comprising a" does not exclude the presence of additional identical elements in the process, method, article or apparatus that includes the element.

[0237] Those skilled in the art will appreciate that embodiments of the present application can be provided as a method, system or computer program product. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Moreover, the present application can 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.

[0238] The present application can be described in the general context of computer-executable instructions, such as program modules, executed by computers. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The present application can 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 can be located in both local and remote computer storage media including storage devices.

[0239] The above merely provides an example of the present application, but is not intended to limit the present application. Any modification, equivalent replacement, improvement, etc. within the spirit and principle of the present application should be included in the scope of claims of the present application.

Claims

A payment processing method, comprising: 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; sending a first payment result page to the first device of the payer before a transaction resource corresponding to the payment processing request is transferred to a payee 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; sending a second payment result page to the first device of the payer after the transaction resource is transferred to the payee account of the payee; the second payment result page is used to indicate that the resource transfer step has been completed. The method of claim 1, wherein the payment processing request includes order information to be processed. The method further comprises: determining order amount information in the order information to be processed; generating a first payment result page containing the order amount information. The method according to claim 1, further comprising: processing the payment processing request according to a preset payment processing procedure, sending the transaction resource corresponding to the payment processing request to the payee account of the payee, and obtaining payment result information; generating the second payment result page based on the payment result information; the second payment result page includes information of the actual payment amount of the payer. The second payment result page according to claim 3 further includes at least one of the following: information of the amount to be paid, information of the discount amount enjoyed by the user, and information of the payment method. The method according to claim 3, wherein the sending of the transaction resource corresponding to the payment processing request to the payee account of the payee comprises: if the transaction quantity of resources corresponding to the payment processing request cannot be deducted from the payment account of the payer, then the transaction quantity of resources is deducted from an account of a third resource provider; the third resource provider is a service provider capable of providing resources other than the payer and the payee; increasing the transaction quantity of resources in the payee account. The method according to claim 3, wherein the sending of the transaction resource corresponding to the payment processing request to the payee account of the payee comprises: judging whether a first quantity of resources in the payment account of the payer is greater than or equal to a second quantity of resources corresponding to the payment processing request, to obtain a judgment result; if the first quantity is greater than or equal to the second quantity, then the second quantity of resources is deducted from the payment account of the payer; if the first quantity is less than the second quantity, then the second quantity of resources is deducted from an account of a third party resource provider; the third resource provider is a service provider capable of providing resources other than the payer and the payee; increasing the second quantity of resources in the payee account. The method according to claim 5 or 6, wherein the payment account of the payer includes one or more accounts, and the first quantity represents the quantity of available resources in any available account of the payment account of the payer or the total quantity of available resources in each available account of the payment account of the payer. The method of claim 5, wherein after deducting the transaction amount of resources from the account of the third resource provider, the method further comprises: sending prompt information indicating that the bill is not settled to the first device of the payer. The method of claim 5, wherein after deducting the transaction amount of resources from the account of the third resource provider, the method further comprises: obtaining a bill settlement request sent by the first device; the bill settlement request is used for the payer to settle the resources provided by the third resource provider for the payment processing request; deducting the transaction amount of resources from the payment account of the payer based on the bill settlement request; adding the transaction amount of resources to the account of the third resource provider. The method of claim 5, wherein after deducting the transaction amount of resources from the account of the third resource provider, the method further comprises: deducting the transaction amount of resources from the payment account of the payer after a preset time is reached; the preset time is a time after deducting the transaction amount of resources from the account of the third resource provider; adding the transaction amount of resources to the account of the third resource provider. The method of claim 1, wherein the method further comprises: determining whether the order to be paid corresponding to the payment processing request satisfies a pay-first condition to obtain a determination result; the pay-first condition is used to indicate that the payment result information is enjoyed first and then actual payment is made; the sending of the first payment result page to the first device of the payer specifically comprises: if the determination result indicates that the payment processing request satisfies the pay-first condition, a pre-generated first payment result page is sent to the first device of the payer. The method of claim 11, wherein the pay-first condition comprises at least one of the following: an available resource amount of the payer is greater than or equal to an 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 value; a transaction party of the payment processing request is a trusted transaction party; the transaction party comprises at least one of the payer and the payee. The method of claim 1, wherein the method further comprises: 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 through near field communication; generating transaction identification information used to indicate a transaction account of the payer based on the payment trigger request; sending the transaction identification information to the payee so that the payee generates a payment processing request based on the transaction identification information and commodity information to be paid; the obtaining of the payment processing request specifically comprises: obtaining the payment processing request sent by the payee. The method of claim 13, wherein the transaction identification information comprises identification information indicating that an order to be paid corresponding to the payment processing request satisfies a pay-first condition. The method of claim 14, wherein the method further comprises: determining whether the payment processing request contains identification information indicating that the order corresponding to the payment processing request satisfies the instant payment condition; the first payment result page is sent to the first device of the payer, specifically comprising: If the payment processing request contains identification information indicating that the order corresponding to the payment processing request satisfies the instant payment condition, the first payment result page is sent to the first device of the payer. A payment processing method comprises: 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; The first payment result page sent by the server is obtained; The first payment result page is sent by the server before the transaction resource corresponding to the payment processing request is transferred to the payment account of the payee; The first payment result page is used to indicate that the near field communication step in the online transaction process has been completed; The second payment result page sent by the server is obtained; The second payment result page is sent by the server after the transaction resource is transferred to the payment account of the payee. The method of claim 16, if the transaction resource is a resource provided by a third resource provider. The third resource provider is a service provider capable of providing resources other than the payer and the payee; The method further comprises: Obtaining prompt information sent by the server indicating that the bill is not settled; Display the information page containing the prompt information. The method of claim 16, if the transaction resource is a resource provided by a third resource provider. The third resource provider is a service provider capable of providing resources other than the payer and the payee; The method further comprises: Obtaining the preset operation of the payer on the repayment page displayed in the first device; The repayment page contains information of the order amount corresponding to the payment processing; Based on the preset operation, a bill settlement request is sent to the server to deduct the transaction resource from the payment account of the payer and increase the transaction resource in the account of the third resource provider. According to claim 18, the repayment page is displayed by the first device based on the preset operation of the payer on the page containing the prompt information displayed in the first device; The prompt information is a prompt information indicating that the bill corresponding to the payment processing request is not settled. A payment processing device comprises: A payment processing request acquisition module 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; The first payment result page sending module is used to send the first payment result page to the first device of the payer before the transaction resource corresponding to the payment processing request is transferred to the payment account of the payee; The first payment result page is used to indicate that the near field communication step in the online transaction process has been completed; 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 resource is 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. A payment processing device comprises: The tag information acquisition module is configured to acquire, by means of near field communication, tag information of the second device in near field communication. The tag information is used to trigger generation of a payment processing request. The first payment result page acquisition module is configured to acquire a first payment result page sent by a server; the first payment result page is sent by the server before a transaction resource corresponding to the payment processing request is transferred to a payment account of the payee; and the first payment result page is used to indicate that a near field communication step in an online transaction process has been completed. The second payment result page acquisition module is configured to acquire a second payment result page sent by the server; the second payment result page is sent by the server after the transaction resource is transferred to the payment account of the payee. A payment processing device comprises: at least one processor; and a memory connected to the at least one processor in communication; 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 of any one of claims 1 to 19. A computer readable medium having stored thereon computer readable instructions executable by a processor to implement the payment processing method of any one of claims 1 to 19.

Images