Payment method, apparatus and device
Patent Information
- Application Number
- MYPI2026001873
- Authority / Receiving Office
- MY · MY
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-10-08
- Filing Date
- 2024-09-30
- Publication Date
- 2025-04-08
AI Technical Summary
In the small merchant scenario, it is difficult for users to use wearable devices (such as smartwatches) that do not have cameras to make QR code-based payments because these devices cannot scan the merchant’s payment code, and small merchants usually do not have a scanning device.
By writing relevant information into the recipient's close-range wireless communication tag, users can read this information through wearable devices, simulate the recipient's scanning code process, and initiate payment requests to the server instead of receiving payment.
It realizes the support of QR code payment based on wearable devices in the small merchant scenario, which reduces hardware requirements and improves the convenience and security of payment. The server can reuse existing processing logic, reducing implementation costs.
Smart Images

Figure PI2026001873_DRAWING_001 
Figure PI2026001873_DRAWING_002 
Figure PI2026001873_DRAWING_003
Abstract
Description
Payment method, device and equipment Technical Field
[0001] This specification relates to the field of electronic payment technology, and in particular to a payment method, device, and equipment. Background Art
[0002] With the development of electronic payment technology and the popularization of smart mobile devices, QR code-based payment has become one of the main means of payment for small payments in people's daily lives, bringing great convenience to both payers and recipients.
[0003] There are currently two main user operation methods for QR code-based payments, taking the user as the payer and the merchant as the payee as an example. The first method is: the user generates and displays the payment code on their terminal (usually a mobile phone), and the merchant uses a barcode scanner or other scanning device to scan the payment code to complete the payment. This method belongs to the payee's main scanning scenario. The second method is: the merchant displays (either electronically or physically) their own payment code, and the user uses the camera of their terminal to scan the payment code to complete the payment. This method belongs to the payee's main scanning scenario.
[0004] With the rise of wearable devices represented by smart watches, more and more users are using smart watches to make payments. Since smart watches are worn on the wrist, users can simply reach out and operate them without having to take their phones out of their pockets or bags, which further enhances convenience.
[0005] Currently, many smartwatches do not have cameras. Therefore, when using such smartwatches to make payments based on QR codes, the second method mentioned above cannot be used because they cannot scan the merchant's payment code. Instead, the first method mentioned above can be used, which is to display the payment code on the smartwatch so that the merchant can scan it. However, in actual applications, many small businesses (such as convenience stores, small vendors, etc.) do not have barcode scanning equipment such as barcode scanners. Therefore, they only print and post their own payment codes for users to scan and pay, and do not support the first method mentioned above. Therefore, in such small business scenarios, users often find it difficult to use wearable devices without cameras, such as these smartwatches, to make payments based on QR codes.
[0006] Based on this, for small business scenarios, there needs to be a solution that is more convenient for users to make payments based on wearable devices and QR codes.
[0007] Summary of the Invention
[0008] One or more embodiments of this specification provide a payment method, apparatus, device, and storage medium to solve the following technical problem: There is a need for a solution that is more convenient for users to make payments based on wearable devices and QR codes.
[0009] To solve the above technical problems, one or more embodiments of this specification are implemented as follows.
[0010] One or more embodiments of the present specification provide a payment method, which is applied to a client of a payment application, and the method includes: receiving a wake-up instruction, wherein the initiation method of the wake-up instruction includes: the mobile device where the client is located reads the short-range wireless communication tag of the payee, obtains the corresponding code value, sends the wake-up instruction to the client and provides the code value; in response to the wake-up instruction, obtains relevant information of the payee according to the code value; based on the relevant information, simulates a predetermined process of scanning and paying when the payee is the code scanning party; by executing the simulated predetermined process, initiates a payment request to the server corresponding to the payee on behalf of the payee to obtain the payment result returned by the server.
[0011] One or more embodiments of the present specification provide a payment device, which is applied to a client of a payment application, and the device includes: an instruction receiving module, which receives a wake-up instruction, wherein the initiation method of the wake-up instruction includes: the mobile device where the client is located reads the short-range wireless communication tag of the payee, obtains the corresponding code value, sends the wake-up instruction to the client and provides the code value; a code value parsing module, which responds to the wake-up instruction and obtains relevant information of the payee according to the code value; a payee code scanning simulation module, which simulates the predetermined process of scanning and paying when the payee is the code scanning party according to the relevant information; and a payment request module, which initiates a payment request to the server corresponding to the payee on behalf of the payee by executing the simulated predetermined process to obtain the payment result returned by the server.
[0012] One or more embodiments of the present specification provide a payment device, which is applied to a client of a payment application, and the device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can: receive a wake-up instruction, wherein the initiation method of the wake-up instruction includes: the mobile device where the client is located reads the short-range wireless communication tag of the payee, obtains the corresponding code value, sends the wake-up instruction to the client and provides the code value; in response to the wake-up instruction, obtains relevant information of the payee according to the code value; based on the relevant information, simulates a predetermined process of scanning and paying when the payee is the code scanner; by executing the simulated predetermined process, initiates a payment request to the server corresponding to the payee on behalf of the payee to obtain the payment result returned by the server.
[0013] One or more embodiments of the present specification provide a non-volatile computer storage medium storing computer-executable instructions, which are applied to a client of a payment application, wherein the computer-executable instructions are configured to: receive a wake-up instruction, wherein the initiation method of the wake-up instruction includes: the mobile device where the client is located reads the short-range wireless communication tag of the payee, obtains a corresponding code value, sends the wake-up instruction to the client and provides the code value; in response to the wake-up instruction, obtains relevant information of the payee according to the code value; based on the relevant information, simulates a predetermined process of scanning and paying when the payee is the code scanner; by executing the simulated predetermined process, initiates a payment request to the server corresponding to the payee on behalf of the payee to obtain the payment result returned by the server.
[0014] At least one of the above-mentioned technical solutions adopted in one or more embodiments of this specification can achieve the following beneficial effects: small merchants can conveniently support wearable device-based payments by setting a short-range wireless communication tag with their own relevant information (for example, identity or payment code value, etc.) written in it. Users can specifically read the short-range wireless communication tag through a wearable device to obtain relevant information of the small merchant. Furthermore, even if the user's wearable device does not have a code scanning function, the small merchant does not have a code scanning machine and does not actually scan the user's code, the user can simulate the interaction process between the small merchant and the server after scanning the code. Therefore, the server can complete the payment processing with reference to the process after the small merchant scans the code. For both the payer and the payee, the hardware requirements are reduced, the convenience is improved, the payment experience is better, and the server can reuse the existing processing logic, with low implementation costs. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0016] FIG1 is a flow chart of a payment method provided in one or more embodiments of this specification;
[0017] FIG2 is a flow chart of a specific implementation scheme of a payment method provided in one or more embodiments of this specification;
[0018] FIG3 is a schematic diagram of an application scenario of the method of FIG1 provided in one or more embodiments of this specification;
[0019] FIG4 is a flowchart of a solution in which a user's client simulates a payee's main scanning scenario to make a payment to a merchant in the scenario of FIG3 , according to one or more embodiments of this specification;
[0020] FIG5 is a flowchart illustrating a solution for controlling the payment amount when the payee's client simulates a main scanning scenario provided by one or more embodiments of this specification;
[0021] FIG6 is a schematic diagram of the structure of a payment device provided by one or more embodiments of this specification;
[0022] FIG7 is a schematic diagram of the structure of a payment device provided in one or more embodiments of this specification. DETAILED DESCRIPTION
[0023] The embodiments of this specification provide a payment method, apparatus, device, and storage medium.
[0024] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.
[0025] From the introduction of background technology, we can know that many small businesses, due to limitations in operating costs or venues, do not have barcode scanning equipment such as barcode scanners, resulting in the inability to support payment scenarios where merchants scan primarily. When users use mobile devices without cameras or cameras that do not support scanning, it is difficult to implement user-directed scanning, thus falling into a dilemma.
[0026] In this regard, the idea of this application is as follows: the essential reason for not supporting merchant main scanning is that merchants cannot obtain the authorization credentials provided by users through payment codes by scanning codes, and thus have no basis to request deductions from the server, while users themselves can obtain their own payment codes conveniently and safely. Therefore, consider letting users simulate the merchant main scanning process on behalf of merchants (the reason for simulating merchant main scanning here is that the merchant main scanning has additional special features compared to user main scanning, which will be explained in detail later). In this process, users need to obtain the relevant information of the merchant to a minimum in order to realize the simulation. Therefore, short-range wireless communication tags are introduced as a channel for obtaining the relevant information, which is low-cost and easy for merchants to deploy. Furthermore, based on the increase in role capabilities brought about by simulation, it can also solve the security problem of the traditional merchant main scanning method, in which users cannot perceive the payment amount in advance when paying, and can also strengthen the mutual trust between the payer and the payee.
[0027] Based on this general idea, the solution of this application will be described in detail below.
[0028] FIG1 is a flow chart of a payment method provided in one or more embodiments of this specification. This method can be applied to a client of a payment application, which is installed on a mobile device. The advantages of this solution are particularly evident for wearable devices, especially those that do not have a camera that supports code scanning. Smart watches are representative of wearable devices. In addition, other wearable devices that support short-range wireless communication (such as smart bracelets) may also use this solution. For ease of description, the following embodiments mainly use smart watches as an example.
[0029] The process in FIG1 includes the following steps S102 to S108 .
[0030] S102: receiving a wake-up instruction, wherein the initiation method of the wake-up instruction includes: the mobile device where the client is located reads the short-range wireless communication tag of the payee, obtains a corresponding code value, sends the wake-up instruction to the client and provides the code value.
[0031] In one or more embodiments of the present specification, the payee (for example, the small merchant mentioned above) is pre-deployed with a short-range wireless communication tag, which contains relevant information of the payee (for example, expressed in a corresponding code value, which may not be plain text, so that the security is better). Based on the relevant information, the identity of the payee can be determined, such as the merchant name or the payment account number, etc. The server of the payment application can transfer the amount paid by the payer to the payee based on the identity.
[0032] The relevant information is, for example, the information contained in the payee's payment code (currently usually a QR code). In order to facilitate different payment methods, the payee can, on the basis of providing a payment code for users to scan and pay, further deploy a short-range wireless communication tag for use by payers who are inconvenient or unable to scan the code. In this case, for example, the proximity of the short-range wireless communication tag also displays: the payee's payment code generated according to the code value, and the payer can flexibly choose the short-range wireless communication tag or payment code for interaction according to the situation of his or her own device. It is possible to write the code value into the short-range wireless communication tag first, or to generate the payment code based on the code value first. The preliminary preparations for these two methods can be carried out independently.
[0033] In one or more embodiments of this specification, since many mobile devices support near field communication (NFC) function and the cost of NFC tags is relatively low, NFC tags can be used as short-range wireless communication tags. In this case, the short-range wireless communication is specifically near field communication.
[0034] In one or more embodiments of this specification, when a payer wants to make a payment, they can hold their smartwatch near the payee's NFC tag. The corresponding NFC module within the smartwatch can then read the code value contained in the NFC tag. A microprocessor or related module within the smartwatch can then invoke the payment application client on the smartwatch and provide the code value read by the NFC module to the payment application client. This process is easy for the payer and, if desired, can even be accomplished without using the smartwatch dial, providing a better user experience.
[0035] S104: In response to the call instruction, obtain relevant information of the payee according to the code value.
[0036] In one or more embodiments of this specification, the code value can be parsed locally on the client, or the client can parse the code value through the server to obtain relevant information about the payee. This helps the client directly understand the current payee and helps improve payment security. Of course, the code value itself can also be used as relevant information about the payee.
[0037] S106: Based on the relevant information, simulate the predetermined process of scanning code to pay when the payee is the code scanning party.
[0038] In one or more embodiments of this specification, simulating the predetermined process of scanning and paying when the payee is the scanner may include: determining that the client replaces the role of the payee in the payee's main scanning scenario, and determining how the predetermined process should be executed in the case of role replacement. It should be noted that, in addition to the role replacement, according to actual needs, the simulated predetermined process and the original predetermined process may have some specific action differences. However, regardless of these differences, the response of the server needs to be affected as little as possible or even not affected. In this way, the modifications required for the implementation of the solution can be mainly carried out on the client side, which is relatively low in cost.
[0039] For ease of understanding, the payee's main scanning scenario and the above-mentioned role replacement are explained. Generally, in this scenario, the payee will generate and display his own payment code, and the payee will scan the payment code to obtain the payee's corresponding credential information, and then initiate a payment request to the server based on the credential information to request that the payee be deducted and the money be transferred to the payee. After the role replacement, there is no need for the payee to initiate a payment request. The payee himself initiates a payment request to the server based on his own credential information and the relevant information of the payee obtained previously (in order to clarify who to pay to) to request that the payee be deducted and the money be transferred to the payee. From the server's perspective, it can still be considered that the payment request is sent by the payee, and there is no need to pay special attention to or even perceive the role replacement. Therefore, after receiving the payment request, the subsequent processing logic of the payee's main scanning scenario can be used.
[0040] It should be noted that after obtaining the relevant information of the payee, the client can also execute the process in the payee main scanning scenario, that is, directly initiate a transfer to the payee through the server to realize the payment. However, this application mainly focuses on simulating the payee main scanning scenario for two main reasons:
[0041] First, simulating the payee's primary scanning scenario is likely to involve one or more additional processing logic for both the payee and the server. Essentially, in this scenario, the server typically provides the payee with additional services, which may be free, paid, or even higher-level paid value-added services (in the case of paid services, a small fee or membership fee will be charged for the corresponding service). These additional services provide the payee with additional conveniences, such as faster response times, higher security, more traffic resources, lower purchase prices, more promotional offers, and more comprehensive accounting services. These conveniences are also achieved through the server's business logic. However, in the payee's primary scanning scenario, these conveniences may not be available to the payee.
[0042] Second, the pre-defined process for the payee-led scanning scenario involves reusable business logic on the server side, resulting in minimal implementation costs. Compared to the processing process in the payee-led scanning scenario, there is little difference in cost or response speed. Furthermore, if the payer does not wish to manually enter the payment amount, the interaction is faster, making it ideal for wearable devices such as smartwatches. In the payer-led scanning scenario, the payer must manually enter the payment amount, which is quite restrictive.
[0043] S108: By executing the predetermined process of the simulation, a payment request is initiated to the server corresponding to the payment direction to obtain the payment result returned by the server.
[0044] In one or more embodiments of the present specification, the client obtains relevant information of the payee based on the payee's short-range wireless communication tag without relying on the mobile device camera. The payer does not need to interact with the server for the time being. The interaction will be simulated by the client, so that from the server's perspective, it seems as if the payee is interacting with the server after scanning the payer's payment code.
[0045] For example, the client can obtain the credential information obtained by the payee when scanning the payment code presented by the payee as the scanner, and then initiate a payment request to the corresponding server on behalf of the payee based on the credential information and related information. The client can generate the payer's own payment code or the information contained in the payment code, which can be used as the credential information by the payee when scanning the payment code presented by the payee as the scanner.
[0046] In addition, the voucher information can also be generated based on the integration of relevant information. In this case, the generated voucher information is different from the traditional voucher information and can more flexibly add product-related extension fields to support optional extension requests (for example, extension requests involving product reservations and / or product customization, etc.). The payer can optionally perform an assignment operation on the product-related extension fields, thereby making the product-related extension fields valid during this payment process.
[0047] In this case, the client receives the payee's assignment of values to the product-related extension fields. Based on the assigned values, the client then sends a payment request to the payee's corresponding server, along with the aforementioned credential information and related information. This allows a single payment to achieve more long-term and diverse results, bringing convenience to the payee.
[0048] For example, a series product reservation field is added. If the product that the payee is currently paying for is one of the products in the series, and subsequent products will be released one after another, the payee can actively operate the series product reservation field when making payment, so as to conveniently make a reservation for the subsequent product while paying, so as not to miss the subsequent products easily. Furthermore, a product attribute customization field may be added to the series product reservation field to pre-select products that meet the customization conditions and may be launched later in the series (it is also possible that the products actually launched later do not meet the customized attributes, and such products will not hit the payee's reservation).
[0049] The simulated process can also include fewer steps. For example, to generate a more concise credential than a payment code, the simulated steps will focus on the subsequent interaction with the server. To ensure that the server can correctly handle this more concise credential, a pre-negotiation can be established with the server. In this case, the server is aware of the client's simulation and can continue the payment process more efficiently.
[0050] To further improve security, the server can also be enabled to clearly perceive the simulation performed by the client, so as to conduct risk control on the client when necessary, or actively interact with the payee to verify and enhance the mutual trust relationship among the three parties.
[0051] Through the method of Figure 1, small merchants can conveniently support wearable device-based payments by setting up short-range wireless communication tags with their own relevant information (such as identity or payment code values, etc.). Users can specifically read the short-range wireless communication tags through wearable devices to obtain relevant information of the small merchant. Furthermore, even if the user's wearable device does not have a code scanning function, the small merchant does not have a code scanning machine and does not actually scan the user's code, the user can simulate the interaction process between the small merchant and the server after scanning the code. Therefore, the server can complete the payment processing with reference to the process after the small merchant scans the code. For both the payer and the payee, the hardware requirements are reduced, the convenience is improved, the payment experience is better, and the server can reuse the existing processing logic, with low implementation costs.
[0052] Based on the method of FIG1 , this specification also provides some specific implementation plans and extension plans of the method, which will be described below.
[0053] In the traditional payee-led scanning scenario, the payer can only passively present the payment code and wait for the payee to scan the code. The payment amount is entered on the payee's machine (automatically entered through product recognition, or manually entered by the payee). The payer cannot perceive the actual payment amount in time when presenting the payment code. Only after waiting for the deduction to be completed can he know from the notification message pushed by the server. Some payers do not care much about such notifications.
[0054] There are many risks in this process: for example, the payment amount may be incorrect due to the payee's incorrect product recognition or manual operation error, especially it may lead to actual overdeduction, and the payer is too passive; for example, after the payment code is generated, it will be briefly exposed in public before being scanned, especially when the payer is careless and the payee is not quick enough to scan the code.
[0055] By adopting the solution provided by this application, where the payee's client simulates the payee's primary scanning scenario, a role replacement is performed. Since the payee does not need to directly display the payment code to the payee, or even display the payment code on the dial, the security of the payment code and the credential information it contains is greatly improved. Moreover, in this simulated scenario, the payee has a higher degree of initiative. Since it is the payee's client that interacts with the server in this case, the payer or client can control the payment amount, thus solving the problem of the payee's inability to promptly perceive the actual payment amount when presenting the payment code in the traditional payee's primary scanning scenario.
[0056] In one or more embodiments of the present specification, taking allowing the payer to control the payment amount as an example, when initiating a payment request to the corresponding server on behalf of the payee by executing a simulated predetermined process, specifically, a payment amount input page can be displayed on the client to receive the payment amount entered by the payer, and the payer can operate on the dial of the smart watch and enter the payment amount in the payment amount input page. The client then initiates a payment request to the corresponding server based on the received payment amount, which is limited by the payment amount (for example, equal to or less than the payment amount).
[0057] It should be noted that the step of entering the payment amount can be decided by the payer whether to execute it. If it is not executed, the payer does not need to operate on the dial, the payment process is simpler and smoother, and the user experience is better.
[0058] According to the above description, one or more embodiments of this specification further provide a flowchart of a specific implementation scheme of a payment method, see FIG2 , which is executed by a client of a payment application on a wearable device of the payer.
[0059] The process in FIG2 includes the following steps S202 to S210 .
[0060] S202: receiving a wake-up instruction, wherein the initiation method of the wake-up instruction includes: the mobile device where the client is located reads the near-field wireless communication tag of the payee, obtains a corresponding code value, sends the wake-up instruction to the client and provides the code value;
[0061] S204: In response to the call instruction, obtain relevant information of the payee according to the code value;
[0062] S206: Displaying a payment amount input page, and receiving the payment amount input by the payer through the payment amount input page.
[0063] S208: Generate your own payment code or the information contained in the payment code according to the payment amount as special voucher information in the simulated payee main scanning scenario.
[0064] Compared with traditional payment codes, the payment code that can be generated or the information contained therein at least additionally indicates the payment amount, so that the payment process is safer and more accurate for the payer.
[0065] S210: Based on the relevant information of the payee and the special credential information, a payment request is initiated on behalf of the payee to the corresponding server to obtain a payment result returned by the server.
[0066] When generating special voucher information, the relevant information of the payee can also be integrated. The voucher information obtained in this way is more integrated, which helps to more reliably link the payer and the payee, and is more specific than traditional information.
[0067] More intuitively, one or more embodiments of this specification also provide a schematic diagram of an application scenario of the method of FIG1 , see FIG3 .
[0068] In the application scenario shown in Figure 3, the user is the payer and the merchant is the payee. The merchant provides its own QR code and a corresponding NFC tag, which can be placed nearby, for example, on a QR code sign without obstructing the code. Users can choose to use a wearable device such as a smartwatch to pay based on the NFC tag rather than the QR code. Other users who do not have such a wearable device can use a smartphone to scan the QR code to pay.
[0069] Furthermore, one or more embodiments of this specification also provide a flow chart of a solution in which the user's client simulates the payee's main scanning scenario to pay the merchant in the scenario of FIG3 , see FIG4 .
[0070] The process in Figure 4 includes the following steps: the user turns on the NFC reading function of the smart watch he is wearing in advance, and the client of the payment application is installed on the smart watch; when the user wants to make a payment for shopping at a merchant, he places the smart watch close to the merchant's NFC tag; the smart watch uses its NFC reading function to read the code value from the merchant's NFC tag; the smart watch wakes up the client of the payment application installed on it and provides the code value to the client; the client requests the server of the payment application to parse the code value; the server parses the code value, obtains the relevant information of the merchant, and returns it to the client; the client generates its own payment code; the client simulates the role of replacing the merchant based on its own payment code and the relevant information of the merchant, and initiates a payment request to the server; the server performs corresponding deduction processing in response to the payment request, and optionally makes payment to the merchant (the payment processing can be delayed, for example, unified payment by day or week, etc.), and returns the payment result.
[0071] Based on this process, users tap their smartwatch against the merchant's NFC tag, activating the payment app client, optionally entering the payment amount, and then conveniently completing the payment through interaction with the server without further reliance on the merchant. Therefore, users' mobile devices without cameras can also pay merchants without barcode scanning equipment, and the payment amount can be customized by the user, making it easy for merchants to support this payment method at a low cost.
[0072] The above mainly enhances security and trust from the perspective of the payer (user). In actual applications, in order to strengthen the trust between the payer and the payee, it is also necessary to consider the risks brought by possible abnormalities of the payer. Based on this consideration, one or more embodiments of this specification also provide a flow chart of the control scheme for the payment amount when the payer's client simulates the payee's main scanning scenario, so as to simultaneously protect the interests of the payer and the payee and strengthen the trust between the two parties. See Figure 5, which can be executed in combination with the process in Figure 1 or Figure 2.
[0073] The process in FIG5 includes the following steps S502 to S510.
[0074] S502: The mobile device where the client is located is close to the near-field wireless communication tag, and reads the amount to be paid written by the payee in the near-field wireless communication tag.
[0075] The amount to be paid can be written immediately or pre-written. For example, the amount corresponding to one or more products can be written, and when reading, the user can select the product or quantity through the client or manual operation. Without requiring the user to perform such additional operations, this latter method is particularly suitable for scenarios where the amount to be paid is fixed, such as selling a single product such as tickets.
[0076] When executing the above-mentioned step of initiating a payment request to the corresponding server, the following steps may be additionally executed.
[0077] S504: Displaying a payment amount related page to receive the payment amount entered or confirmed by the user on the payment amount related page.
[0078] The amount to be paid is the amount agreed upon by the payee, and the payment amount is the amount agreed upon by the payer. This provides both parties with a means to actively control the amount so that they can reach an agreement later.
[0079] S506: Acquire the amount to be paid read by the mobile device.
[0080] S508: Determine whether the received payment amount is not less than the amount to be paid.
[0081] If the two are equal, the two parties have reached an agreement and the payment can continue. If the two are greater, the user may have entered the payment amount incorrectly. In this case, a corresponding prompt can be given to facilitate further verification by the user to avoid loss of benefits.
[0082] S510: If yes, initiate a payment request subject to the amount to be paid to the corresponding server, so that the actual payment amount of the payer one or more times is equal to the amount to be paid.
[0083] If the payment amount received is less than the amount to be paid (which may be due to a user error or a payee error), the payee may lose interest. In this case, the user may be prompted to make corrections before initiating the payment request. Alternatively, an additional payment service may be initiated for the user for the difference between the payment amount and the amount to be paid. After the user confirms (for example, by simply asking the payee for confirmation), the payment is processed. The user has made multiple payments, so that payment services caused by user errors can also be split and processed normally without the need to roll back the service. This helps reduce the risk of misunderstandings and conflicts between the two parties and is more tolerant to possible operational errors on both sides.
[0084] Based on the same idea, one or more embodiments of this specification also provide apparatuses and devices corresponding to the above method, as shown in Figures 6 and 7. The apparatuses and devices can execute the above method and related optional solutions accordingly.
[0085] Figure 6 is a structural diagram of a payment device provided by one or more embodiments of this specification, and the device is applied to the client of the payment application, and the device includes: an instruction receiving module 602, which receives a wake-up instruction, wherein the initiation method of the wake-up instruction includes: the mobile device where the client is located reads the short-range wireless communication tag of the payee, obtains the corresponding code value, sends the wake-up instruction to the client and provides the code value; a code value parsing module 604, responds to the wake-up instruction, obtains the relevant information of the payee according to the code value; the payee scanning simulation module 606, simulates the predetermined process of scanning and paying when the payee is the scanner according to the relevant information; the payment request module 608, by executing the simulated predetermined process, initiates a payment request to the server corresponding to the payee on behalf of the payee, so as to obtain the payment result returned by the server.
[0086] Optionally, the payment request module 608 obtains the credential information that the payee can obtain when scanning the payment code presented by the corresponding payer as the code scanning party; and initiates a payment request to the server corresponding to the payee on behalf of the payee based on the credential information and the relevant information.
[0087] Optionally, the payment request module 608 generates its own payment code or information contained in the payment code as credential information that the payee can obtain when scanning the payment code presented by the corresponding payer as the code scanning party.
[0088] Optionally, the payment request module 608 receives the payer's assignment operation on the product-related extension field; based on the assigned product-related extension field, the credential information and the related information, it initiates a payment request carrying an extension request corresponding to the assignment on behalf of the server corresponding to the payee; wherein, the extension request involves product reservation and / or product customization.
[0089] Optionally, the payment request module 608 displays a payment amount input page to receive the payment amount input by the user; and initiates a payment request limited by the payment amount to the corresponding server based on the received payment amount.
[0090] Optionally, the proximity position of the near-field wireless communication tag further displays: a payment code generated by the payee according to the code value.
[0091] Optionally, the mobile device is a wearable device.
[0092] Optionally, the wearable device includes: a smart watch that does not have a camera that supports code scanning.
[0093] Optionally, the mobile device where the client is located reads the short-range wireless communication tag of the payee, specifically including: the mobile device where the client is located reads the amount to be paid written by the payee in the short-range wireless communication tag this time; the payment request module 608 displays the payment amount related page to receive the payment amount entered or confirmed by the user on the payment amount related page; obtains the amount to be paid read by the mobile device; determines whether the received payment amount is not less than the amount to be paid; if so, initiates a payment request subject to the amount to be paid to the corresponding server, so that the actual payment amount of the user this time is equal to the amount to be paid.
[0094] Optionally, the short-range wireless communication tag is an NFC tag.
[0095] Figure 7 is a structural diagram of a payment device provided by one or more embodiments of this specification, which is applied to a client of a payment application, and the device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can: receive a wake-up instruction, wherein the initiation method of the wake-up instruction includes: the mobile device where the client is located reads the short-range wireless communication tag of the payee, obtains the corresponding code value, sends the wake-up instruction to the client and provides the code value; in response to the wake-up instruction, obtains relevant information of the payee according to the code value; based on the relevant information, simulates a predetermined process of scanning and paying when the payee is the scanner; by executing the simulated predetermined process, initiates a payment request to the server corresponding to the payee on behalf of the payee to obtain the payment result returned by the server.
[0096] Based on the same idea, one or more embodiments of this specification also provide a non-volatile computer storage medium storing computer executable instructions, which is applied to the client of the payment application, and the computer executable instructions are configured to: receive a wake-up instruction, wherein the initiation method of the wake-up instruction includes: the mobile device where the client is located reads the short-range wireless communication tag of the payee, obtains the corresponding code value, sends the wake-up instruction to the client and provides the code value; in response to the wake-up instruction, obtains the relevant information of the payee according to the code value; based on the relevant information, simulates the predetermined process of scanning and paying when the payee is the code scanning party; by executing the simulated predetermined process, initiates a payment request to the server corresponding to the payee on behalf of the payee to obtain the payment result returned by the server.
[0097] In the 1990s, technological improvements could be clearly distinguished as either hardware improvements (for example, improvements to circuit structures like diodes, transistors, and switches) or software improvements (improvements to process flows). However, with the advancement of technology, many process flow improvements today can now be considered direct improvements to hardware circuit structures. Designers almost always create the corresponding hardware circuit structure by programming the improved process flow into the hardware circuit. Therefore, it cannot be said that a process flow improvement cannot be implemented using hardware modules. For example, a programmable logic device (PLD), such as a field programmable gate array (FPGA), is an integrated circuit whose logical function is determined by user programming. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to hire a chip manufacturer to design and manufacture a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly done using "logic compiler" software. This is similar to the software compiler used when developing programs. Before compilation, the original code must also be written in a specific programming language, called a hardware description language (HDL). There is not just one HDL, but many, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art will also understand that by simply programming the method flow in one of these hardware description languages and then programming it into an integrated circuit, a hardware circuit that implements the logic method flow can be easily obtained.
[0098] The controller can be implemented in any suitable manner. For example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also know that in addition to implementing the controller in a purely computer-readable program code format, the controller can be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules that implement the method and structures within the hardware component.
[0099] The systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or entities, or by products having certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
[0100] For the convenience of description, the above devices are described as being divided into various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.
[0101] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0102] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.
[0103] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.
[0104] This specification may be described in the general context of computer-executable instructions, such as program modules, executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media, including storage devices.
[0105] The various embodiments in this specification are described in a progressive manner. Similar portions between the various embodiments can be referenced to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the device, apparatus, and non-volatile computer storage medium embodiments are generally similar to the method embodiments, so their descriptions are relatively simplified. For relevant details, refer to the descriptions of the method embodiments.
[0106] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0107] The foregoing description is merely one or more embodiments of this specification and is not intended to limit this specification. It will be apparent to those skilled in the art that various modifications and variations may be made to one or more embodiments of this specification. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of one or more embodiments of this specification are intended to be within the scope of the claims of this specification.
Claims
1. A payment method, applied to a client of a payment application, comprising: A wake-up instruction is received, wherein the initiation method of the wake-up instruction includes: the mobile device where the client is located reads the short-range wireless communication tag of the payee, obtains a corresponding code value, sends the wake-up instruction to the client and provides the code value; In response to the invoking instruction, obtaining relevant information of the payee according to the code value; According to the relevant information, simulate the predetermined process of scanning code to pay when the payee is the code scanning party; By executing the predetermined process of the simulation, a payment request is initiated on behalf of the server corresponding to the payment direction to obtain the payment result returned by the server.
2. The method according to claim 1, wherein the predetermined process of executing the simulation specifically comprises: Obtaining the voucher information that the payee can obtain when scanning the payment code presented by the corresponding payer as the code scanning party; Initiate a payment request on behalf of the server corresponding to the payment direction according to the credential information and the related information.
3. The method according to claim 2, wherein the obtaining of the credential information that can be obtained when the payee, as the code scanning party, scans the payment code presented by the corresponding payer specifically includes: Generate your own payment code or the information contained in the payment code, which can be used as the credential information that the payee can obtain when scanning the payment code presented by the corresponding payer as the scanner.
4. The method according to claim 2, wherein the initiating a payment request on behalf of the server corresponding to the payment recipient based on the credential information and the related information comprises: Receive the payee's assignment operation on the commodity-related extended fields; Initiate a payment request carrying an extended request corresponding to the assigned value on behalf of the server corresponding to the payment recipient according to the assigned commodity-related extended field, the credential information and the related information; The extension request involves product reservation and / or product customization.
5. The method according to claim 1, wherein the initiating a payment request to the corresponding server comprises: Display the payment amount input page to receive the payment amount entered by the payer; Based on the received payment amount, a payment request limited by the payment amount is initiated to the corresponding server.
6. The method as claimed in claim 1, wherein the proximity position of the near-field wireless communication tag also displays: a payment code generated by the payee according to the code value.
7. The method according to any one of claims 1 to 6, wherein the mobile device is a wearable device.
8. The method of claim 7, wherein the wearable device comprises: Smartwatches that do not have a camera that supports QR code scanning.
9. The method according to claim 7, wherein the mobile device where the client is located reads the near-field wireless communication tag of the payee, specifically comprising: The mobile device where the client is located reads the amount to be paid written by the payee into the near-field wireless communication tag; The initiating a payment request to the corresponding server specifically includes: Displaying a payment amount related page so as to receive the payment amount entered or confirmed by the payer on the payment amount related page; Obtaining the amount to be paid read by the mobile device; Determining whether the received payment amount is not less than the amount to be paid; If so, a payment request subject to the amount to be paid is initiated to the corresponding service end, so that the actual payment amount of the payer one or more times is equal to the amount to be paid.
10. The method according to claim 1, wherein the near field communication tag is an NFC tag.
11. A payment device, applied to a client of a payment application, the device comprising: The instruction receiving module receives a wake-up instruction, wherein the initiation method of the wake-up instruction includes: the mobile device where the client is located reads the short-range wireless communication tag of the payee, obtains a corresponding code value, sends the wake-up instruction to the client and provides the code value; A code value parsing module, in response to the call instruction, obtains relevant information of the payee according to the code value; The payee code scanning simulation module simulates the predetermined process of code scanning payment when the payee is the code scanning party according to the relevant information; The payment request module initiates a payment request to the server corresponding to the payment direction by executing the predetermined process of the simulation, so as to obtain the payment result returned by the server.
12. The device of claim 11, wherein the payment request module is configured to obtain the credential information that can be obtained when the payee, as the code scanning party, scans the payment code presented by the corresponding payer; Initiate a payment request on behalf of the server corresponding to the payment direction according to the credential information and the related information.
13. The device as described in claim 12, wherein the payment request module generates its own payment code or the information contained in the payment code as the credential information that the payee can obtain when scanning the payment code presented by the corresponding payer as the scanner.
14. The device according to claim 12, wherein the payment request module receives a value assignment operation of a payer to an extended field related to a commodity; Initiate a payment request carrying an extended request corresponding to the assigned value on behalf of the server corresponding to the payment recipient according to the assigned commodity-related extended field, the credential information and the related information; in, The extension request relates to product reservation and / or product customization.
15. The device of claim 11, wherein the payment request module displays a payment amount input page to receive the payment amount input by the payer; Based on the received payment amount, a payment request limited by the payment amount is initiated to the corresponding server.
16. The device as claimed in claim 11, wherein the proximity position of the near-field wireless communication tag further displays: a payment code generated by the payee according to the code value.
17. The apparatus according to any one of claims 11 to 16, wherein the mobile device is a wearable device.
18. The apparatus of claim 17, wherein the wearable device comprises: Smartwatches that do not have a camera that supports QR code scanning.
19. The apparatus according to claim 17, wherein the mobile device where the client is located reads the near-field wireless communication tag of the payee, specifically comprising: The mobile device where the client is located reads the amount to be paid written by the payee into the near-field wireless communication tag; The payment request module displays a payment amount related page to receive the payment amount entered or confirmed by the payer on the payment amount related page; Obtaining the amount to be paid read by the mobile device; Determining whether the received payment amount is not less than the amount to be paid; If so, a payment request subject to the amount to be paid is initiated to the corresponding service end, so that the actual payment amount of the payer one or more times is equal to the amount to be paid.
20. The device of claim 11, wherein the near field communication tag is an NFC tag.
21. A payment device, applied to a client of a payment application, the device comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute: A wake-up instruction is received, wherein the initiation method of the wake-up instruction includes: the mobile device where the client is located reads the short-range wireless communication tag of the payee, obtains a corresponding code value, sends the wake-up instruction to the client and provides the code value; In response to the invoking instruction, obtaining relevant information of the payee according to the code value; According to the relevant information, simulate the predetermined process of scanning code to pay when the payee is the code scanning party; By executing the predetermined process of the simulation, a payment request is initiated on behalf of the server corresponding to the payment direction to obtain the payment result returned by the server.
