Payment method, device and storage medium

Abstract

The application discloses a payment method, device and storage medium, and belongs to the field of data processing. The method comprises the following steps: receiving a payment input for a first bill; in response to the payment input, sending, through an operating system of the device, a first payment connection request to a payment device of a payee; and in the case that payment connection information sent by the payment device is received, deducting a payment amount in the first bill from a fund account associated with and authorized by a device account of the payment device. According to the embodiment of the application, the payment process can be simplified, the payment efficiency can be improved, and the cost of collecting the payment device can be reduced.

Description

Technical Field

[0001] This application belongs to the field of data processing, and in particular relates to a payment method, device and storage medium. Background Technology

[0002] With continuous economic progress and development, the payment industry is accelerating its internetization, and users are using more and more ways to pay their bills, such as QR code payment and Near Field Communication (NFC) payment.

[0003] While the aforementioned payment methods can meet users' daily payment needs, the QR code payment process is relatively cumbersome. Users need to open a payment application, select the QR code payment function, scan the merchant's QR code, enter the amount, and verify a password to complete the payment. Furthermore, merchants must bear the additional cost of the acquiring equipment, such as a handheld QR code payment terminal. Similarly, NFC payments require both the receiving and payment devices to have NFC hardware, which also increases the cost of the acquiring equipment. Additionally, some scenarios do not support NFC, which can restrict payment options. Summary of the Invention

[0004] This application provides a payment method, device, and storage medium that can simplify the payment process, improve payment efficiency, and reduce the hardware cost of acquiring devices.

[0005] In a first aspect, embodiments of this application provide a payment method applied to a payment device of a payer, the method comprising:

[0006] Receive payment input for the first invoice;

[0007] In response to a payment input, a first payment connection request is sent to the payee's payment device via the device's operating system;

[0008] Upon receiving payment connection information from the receiving device, the payment amount from the first invoice is deducted from the funds account associated with and authorized by the device account of the paying device.

[0009] Secondly, embodiments of this application provide a payment method applied to a payee's payment device, the method comprising:

[0010] Receive payment connection requests sent by the payer's payment device through the device's operating system;

[0011] Based on the payment connection request, the first push message is displayed, which prompts whether to establish a payment connection with the payment device.

[0012] Once a payment connection is established with the payment device, a collection connection message is sent to the payer through the device's operating system. This message instructs the collection device and the payment device to establish a connection and to deduct the payment amount from the first invoice from the funds account associated with and authorized by the payment device's device account.

[0013] Thirdly, embodiments of this application provide a payment method applied to a payee's payment device, the method comprising:

[0014] Receive payment input for the second bill;

[0015] In response to a payment input, the system of the device sends a second payment connection request to the payer's payment device via the device's operating system. The second payment connection request carries a second invoice, which includes the payment amount. The second payment connection request is used to request the establishment of a payment connection with the payment device and to instruct the payer to deduct the payment amount from a funds account associated with and authorized by the device account of the payment device.

[0016] Fourthly, embodiments of this application provide a payment method applied to a payer's payment device, the method comprising:

[0017] The receiving device receives a second payment connection request sent through its operating system. The second payment connection request carries a second bill, which includes the amount to be received.

[0018] Based on the second payment connection request, a second push message is displayed, which prompts whether to establish a payment connection with the receiving device.

[0019] Upon receiving input confirming the establishment of a payment connection with the receiving device, the amount to be received is deducted from the funds account associated with and authorized by the device account of the paying device, based on the second invoice.

[0020] Fifthly, embodiments of this application provide a payment device, including:

[0021] The receiving module is used to receive payment inputs for the first invoice;

[0022] The sending module is used to send a first payment connection request to the payee's receiving device through the device's operating system in response to a payment input.

[0023] The payment processing module is used to deduct the payment amount from the first bill from the funds account associated with and authorized by the device account of the payment device when it receives the payment connection information sent by the receiving device.

[0024] Sixthly, embodiments of this application provide a payment collection device, including:

[0025] The receiving module is used to receive payment connection requests sent by the payer's payment device through the device's operating system;

[0026] The display module is used to display the first push information based on the payment connection request. The first push information is used to prompt whether to establish a payment connection with the payment device.

[0027] The sending module is used to send payment connection information to the payer through the device's operating system when a payment connection is established with the payment device. The payment connection information is used to instruct the receiving device and the paying device to establish a connection and to instruct the deduction of the payment amount in the first bill from the funds account associated with and authorized by the device account of the paying device.

[0028] Seventhly, embodiments of this application provide a payment collection device, including:

[0029] The receiving module is used to receive payment input for the second bill;

[0030] The sending module, in response to a payment input, sends a second payment connection request to the payer's payment device via the device's operating system. The second payment connection request carries a second invoice, which includes the payment amount. The second payment connection request is used to request the establishment of a payment connection with the payment device and to instruct the payer to deduct the payment amount from a funds account associated with and authorized by the payment device's device account.

[0031] Eighthly, embodiments of this application provide a payment device, comprising:

[0032] The receiving module is used to receive a second payment connection request sent by the receiving device of the payee through the device's operating system. The second payment connection request carries a second bill, which includes the amount to be received.

[0033] The display module is used to display second push information based on the second payment connection request. The second push information is used to prompt whether to establish a payment connection with the receiving device.

[0034] The payment processing module is used to deduct the payment amount from the funds account associated with and authorized by the device account of the payment device, based on a second bill, upon receiving input confirming the establishment of a payment connection with the receiving device.

[0035] Ninthly, embodiments of this application provide a business device, including: a processor and a memory storing computer program instructions; the processor executing the computer program instructions implements the payment method of the first aspect, the second aspect, the third aspect, or the fourth aspect.

[0036] In a tenth aspect, embodiments of this application provide a computer-readable storage medium storing a program or instructions that, when executed by a business device, cause the business device to perform steps of the payment method shown in the first aspect, the second aspect, the third aspect, or the fourth aspect.

[0037] Eleventhly, embodiments of this application provide a computer program product, including a computer program that, when executed by a business device, causes the business device to perform steps of the payment method as shown in the first aspect, the second aspect, the third aspect, or the fourth aspect.

[0038] This application provides a payment method, device, and storage medium. It receives a payment input for a first bill. In response to the payment input, the device's operating system sends a first payment connection request to the payee's receiving device. Upon receiving the receiving device's payment connection information, the payment amount from the first bill is deducted from the funds account associated with and authorized by the payment device's device account. This method does not rely on the hardware limitations of the acquiring device or electronic device, nor on the funds account in the payment application installed on the electronic device. It only requires establishing a payment connection and information transmission channel between the payee and payer through the operating system of the electronic device, realizing the flow of payment bills and establishing a payment relationship between the payee and payer. Then, with the connection established between the payee's receiving device and the payer's payment device, payment can be completed through the funds account corresponding to the device account. The payment method is flexible and simple to operate, simplifying the payment process, improving payment efficiency, and reducing the hardware cost of the acquiring device. Attached Figure Description

[0039] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0040] Figure 1 A schematic diagram illustrating an example application scenario of the payment method provided in this application embodiment;

[0041] Figure 2 A flowchart of an embodiment of the payment method provided in the first aspect of this application;

[0042] Figure 3 A flowchart of another embodiment of the payment method provided in the first aspect of this application;

[0043] Figure 4 A flowchart of yet another embodiment of the payment method provided in the first aspect of this application;

[0044] Figure 5 A flowchart illustrating yet another embodiment of the payment method provided in the first aspect of this application;

[0045] Figure 6 A flowchart of an embodiment of the payment method provided in the second aspect of this application;

[0046] Figure 7 A flowchart of another embodiment of the payment method provided in the second aspect of this application;

[0047] Figure 8 A flowchart of an embodiment of the payment method provided in the third aspect of this application;

[0048] Figure 9 A flowchart of another embodiment of the payment method provided in the third aspect of this application;

[0049] Figure 10 A flowchart of an embodiment of the payment method provided in the fourth aspect of this application;

[0050] Figure 11 A flowchart illustrating an example of a payment process provided in an embodiment of this application;

[0051] Figure 12 A flowchart illustrating another example of the payment process provided in this application embodiment;

[0052] Figure 13 A schematic diagram of the structure of an embodiment of the payment device provided in the fifth aspect of this application;

[0053] Figure 14 A schematic diagram of the structure of an embodiment of the payment collection device provided in the sixth aspect of this application;

[0054] Figure 15 A schematic diagram of the structure of an embodiment of the payment collection device provided in the seventh aspect of this application;

[0055] Figure 16 A schematic diagram of the structure of an embodiment of the payment device provided in the eighth aspect of this application;

[0056] Figure 17 This is a schematic diagram of the structure of an embodiment of the service equipment provided in the ninth aspect of this application. Detailed Implementation

[0057] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0058] With the continuous development of payment technology, QR code payment and NFC payment have penetrated into various fields. QR code payment can include the payer-scan payment mode and the recipient-scan payment mode. The payer-scan payment mode is a payment method where the payer scans the recipient's QR code. The recipient-scan payment mode is a payment method where the payer's payment device displays a payment code, and the recipient scans the payment code displayed on the payment device using an acquiring device such as a handheld QR code payment terminal.

[0059] In scenarios using the active scanning payment mode, the payer's process is cumbersome. They need to launch the payment application, select the QR code payment function within that application, then scan the QR code provided by the payee, enter the payment amount, and verify their account password to complete the payment. In scenarios using the passive scanning payment mode, the payee's payment processing is heavily reliant on hardware. The payee must possess a payment processing device such as a handheld QR code POS terminal, a dedicated QR code POS terminal, or a static QR code display to accept payments. Payment processing devices have high equipment costs, while static QR codes not only require careful storage but also pose a risk of information leakage. Furthermore, the two types of devices are functionally incompatible, preventing merchants from flexibly switching payment methods.

[0060] In NFC payment scenarios, there is also a heavy reliance on hardware. Both the payee's and payer's devices must have NFC hardware to complete the payment, which increases the cost of the acquiring equipment. Furthermore, NFC payments are subject to distance requirements; the payee's and payer's devices must be within 10 centimeters of each other to complete the payment, which can cause inconvenience. Additionally, some third-party payment accounts on the devices do not currently support NFC payments, further limiting payment options and reducing efficiency.

[0061] To address the aforementioned problems, this application provides a payment method, device, and storage medium that are not dependent on the hardware limitations of acquiring devices and electronic devices, nor are they limited to the funds account in the payment application installed on the electronic device. It only requires establishing a payment connection and information transmission channel between the payee and payer through the operating system of the electronic device, enabling the flow of payment bills and establishing a payment relationship between the payee and payer. Then, with the payee's acquiring device and the payer's payment device connected, payment can be completed through the funds account corresponding to the device account. This payment method is flexible, simple to operate, simplifies the payment process, improves payment efficiency, and reduces the hardware cost of acquiring devices.

[0062] The payment method in this application embodiment is applicable to any scenario where payment is made via electronic devices. This payment method may involve the payer's electronic device (hereinafter referred to as the payment device), the payee's electronic device (hereinafter referred to as the payee device), the payment institution system, the business system, and the account management system. The following is in conjunction with... Figure 1 The payment architecture in the embodiments of this application will be described in detail.

[0063] Figure 1 This is a schematic diagram illustrating an example of the application scenario of the payment method provided in this application embodiment.

[0064] like Figure 1 As shown, the architecture of this payment method may include a payment device 11, a receiving device 12, a business system 13, and an account management system 14.

[0065] Payment device 11 is a terminal device used by the payer to make payments, specifically including mobile phones, tablets, smart wearable devices, etc., without limiting the specific type of payment device 11. Payment device 11 may have a payment application installed. The payment application can be used for payments and provides payment services. The payment service is authorized to bind at least one fund account of the payer to complete the payment through the fund account. The fund account in this embodiment includes, but is not limited to, at least one of the following: a bank account, a third-party payment account, and a mobile wallet account. Payment device 11 has a display function. In scenarios where the payer initiates payment (i.e., the payee passively receives payment), it can display information requiring the payer's confirmation or authorization, such as a first bill and a first prompt message, to facilitate payment. Conversely, in scenarios where the payer passively pays (i.e., the payee initiates payment), it can display a second push message and a second bill. Payment device 11 can establish a payment connection and information transmission channel with receiving device 12 through its operating system to realize the flow of payment bills, thereby establishing a payment relationship between the payee and the payer. Then, when payment device 11 and receiving device 12 are connected, payment can be completed through at least one fund account in payment device 11. To enable payment via the operating system and the payment application within the device, the payment device 11 can interact with the account management system 14. The account management system 14 associates and authorizes the application account of the payment application with the device account of the payment device 11. Furthermore, since the payment application provides payment services and authorizes binding at least one fund account of the payer, the device account, fund account, and application account of the payment device can be associated and authorized, thereby enabling the mutual transfer of information between the device account, fund account, and application account, and establishing a unique mapping relationship for the payer. Additionally, to ensure the security of the payment process, the payment device 11 can communicate with the business system 14 to ensure the payment security of the payer in this embodiment through the clearing subsystem and risk control subsystem within the business system 14.

[0066] The receiving device 12 is a terminal device used by the payee to interact with the paying device 11 during the payment process. Specifically, it may include mobile phones, tablets, smart wearable devices, etc., and the specific type of receiving device 12 is not limited here. The receiving device 12 may have a payment application installed. The payment application can be used for receiving payments and provides payment services. The payment service is authorized to be bound to at least one of the payee's funds accounts so that the payment amount from the payment bill can be added to the funds account. Here, the payee's payment application can be the same as the payer's payment application, or they can be different payment applications; the specific type of payment application is not limited here. The receiving device 12 has a display function. In the scenario where the payer initiates payment (i.e., the payee passively receives payment), it can display information requiring the payee's confirmation or authorization, such as the first push notification, the first bill, and at least one payment method, thereby completing the payment. Conversely, in the scenario where the payer passively pays (i.e., the payee initiates payment), it can display a second bill and a second prompt message. The receiving device 12 can establish a payment connection with the paying device 11. Through the operating system within the device, a payment connection and information transmission channel are established between the payee and the payer, enabling the flow of payment bills and establishing a payment relationship between them. Then, with the receiving device 12 connected to the paying device 11, payment can be completed through at least one fund account within the receiving device 12. To ensure the security of the payment process, the receiving device 12 can communicate with the business system 13. The clearing subsystem and risk control subsystem within the business system 13 ensure the payment security of the payer and the completion of the payment process in this embodiment. Furthermore, to enable payment through the device's operating system and the payment application within the device, the receiving device 12 can interact with the account management system 14. The account management system 14 associates and authorizes the application account of the payment application with the device account of the receiving device 12. Further, since the payment application provides payment services and authorizes binding at least one fund account of the payee, the device account, fund account, and application account of the receiving device can be associated and authorized, thereby enabling the mutual transfer of information between the device account, fund account, and application account and establishing a unique mapping relationship for the payer.

[0067] It should be noted that the operating system of the device involved in this application embodiment is used to transmit payment connection requests (such as a first payment connection request or a second payment connection request) to the payment application in the receiving device and the payment device. The operating systems of the two devices, namely the receiving device and the payment device, can be the same or different.

[0068] Business system 13 can communicate with the payment application in the payment device and the payment application in the collection device, respectively, to provide the transmission of payment resources for payment and collection services, and can also be used for payment risk control and clearing. Business system 13 may include multiple subsystems, for example, business system 13 may include payment application subsystem 131, risk control subsystem 132, and clearing subsystem 133, etc. Business system 13 may include one or more servers or other business devices. Different servers or other business devices in business system 13 can perform the same functions in business system 13, or they can perform different functions in business system 13. When business system 13 includes multiple servers or other business devices, some servers or other business devices may belong to payment application subsystem 131, some servers or other business devices may belong to risk control subsystem 132, and some servers or other business devices may belong to clearing subsystem 133.

[0069] The account management system 14 is a system for managing accounts such as device accounts, fund accounts, and application accounts. The account management system 14 can interact with the business system 13 to complete tasks such as deducting funds from payment accounts and receiving funds from collection accounts. The account management system 14 may include one or more servers or other business devices. Different servers or other business devices in the account management system 14 can perform the same functions or different functions within the account management system 14; this is not limited here.

[0070] It should be noted that, in order to implement the payment method provided in this application embodiment, the process of linking and establishing a unique customer mapping relationship between the device account, fund account, and application account of the associated and authorized payment device is described in detail above.

[0071] Users (including payees and payers) can initiate account linking through the payment application on the business device (including receiving and paying devices) or through the device's operating system settings. Regardless of the method, users must first complete real-name authentication (in China, this refers to user real-name authentication based on their ID card number). Then, the user authorizes the push of their identity information to the device account or the payment application's application account, thus completing the account linking and establishing a unique customer mapping relationship. At this point, the user still needs to bind their funds account in the application account to fully execute the payment method provided in this application embodiment, ensuring the source and destination of funds are clear. The binding process is similar to the currently common application account card binding process, where the application account and the funds account ensure the establishment of a unique customer mapping relationship, thereby indirectly achieving account linking and establishing a unique customer mapping relationship between the device account and the funds account.

[0072] The payment method provided in this application, which involves the establishment of payment connection relationships and related protocols, operates on existing protocols for file transfer or hardware connection between business devices. It does not adjust the verification and signature methods or communication methods, but only adds protocol content for establishing payment connection relationships. These protocols include active, passive, and bidirectional modes, as detailed below.

[0073] The active payment initiation protocol in the active mode supports scenarios where the payer initiates a payment. The payment application on the payer's payment device must load the protocol according to the payment method provided in this application embodiment, and the payer must have completed the connection between the application account and device account of the payment application on the payment device. The protocol specifies the conditions that the discoverable device account of the receiving device must meet, as well as information such as the payee's identity, payment amount, payment application on the payment device, payment account, payment verification, and whether the payment application is restricted in the payment relationship. For security reasons, the device account of the receiving device generally needs to meet the requirement that the receiving device has activated the payment method provided in this application embodiment, but it does not restrict whether the connection between the application account and device account in the payment application has been completed. If the payee has not completed the connection between the application account and device account, the payment can only be completed after the payee completes the account connection.

[0074] The active payment initiation protocol in the active mode supports scenarios where the payee initiates a payment collection. The payment application on the payee's receiving device must load the protocol according to the payment method provided in this application embodiment, and the payee must have completed the connection between the application account and device account of the payment application on the receiving device. The protocol specifies the conditions that the transaction account of the payment device can be discovered, as well as information such as the payer's identity, the amount received, the payment application on the receiving device, the receiving account, and whether the payment app is restricted in the payment relationship. For security and payment experience considerations, the device account of the payment device generally needs to meet the requirement that the payment device has activated the payment method provided in this application embodiment and has completed the connection between the application account and device account in the receiving application. If the payer has not completed the connection between the application account and device account, the receiving device can only discover the payment device after the payer completes the account connection.

[0075] The passive payment initiation protocol in passive mode is used to support scenarios where the payee initiates payment collection. The payment application in the payer's payment device needs to load the protocol according to the payment method provided in this application embodiment, and the payer has completed the connection between the application account of the payment application in the payment device and the device account. The protocol content stipulates the payee's identity, the amount to be received, the payment application in the payee's device, the payee's account, whether the payment application in the payment device is limited, the application account of the payment application in the payment device, the payer's resource account, payment password verification information, etc. in the payment relationship.

[0076] The passive payment initiation protocol in passive mode is used to support scenarios where the payer initiates payment. The payment application in the payee's receiving device must load the protocol according to the payment method provided in this application embodiment, and the receiving device account must have activated the payment method provided in this application embodiment. However, it does not restrict whether the payee has completed the connection between the application account of the payment application in the receiving device and the device account. If the payee has not completed the connection between the application account of the payment application in the receiving device and the device account, the payment can only be completed after the payee completes the account connection. The protocol content stipulates the payer's identity, payment amount, payment application in the receiving device, payer's resource account, payment verification, whether the payment application in the receiving device is limited, and the application account and receiving account of the payment application in the receiving device.

[0077] The bidirectional mode supports scenarios where both the payer and payee simultaneously initiate payments. Both the receiving and paying devices have their payment applications loaded with the payment method protocol provided in this application embodiment, and both parties have completed the connection between the application accounts and device accounts of the payment applications on both devices. The protocol stipulates that the information used by the payer to initiate a payment relationship includes the payee's identity, payment amount, payment application on the paying device, the payer's resource account, payment verification, and whether the payment application on the receiving device is restricted. Similarly, the information used by the payee to initiate a payment relationship includes the payer's identity, payment amount, payment application on the receiving device, the payee's resource account, and whether the payment application on the paying device is restricted. As long as the payment amount matches the payment amount, both the receiving and paying devices meet the restriction requirements, and the payee's identity matches the device account corresponding to the payment application on the receiving device, and the payer's identity matches the device account corresponding to the payment application on the paying device, the payment relationship can be established.

[0078] Based on the above appendix Figure 1 The payment architecture provided in the embodiments of this application is shown below, and the payment method provided in the embodiments of this application will be described in detail.

[0079] Figure 2 A flowchart of an embodiment of the payment method provided in the first aspect of this application.

[0080] like Figure 2 As shown, this application provides a payment method for the first aspect, which can be applied to a payment device, i.e., the payment method can be executed by the payment device. Its application scenario is a scenario where the payer initiates the payment, and the payee passively receives the payment. Based on this, the payment method may include:

[0081] Step 210: Receive payment input for the first bill; Step 220: In response to the payment input, send a first payment connection request to the payee's receiving device through the device's operating system; Step 230: Upon receiving the receiving connection information sent by the receiving device, deduct the payment amount from the first bill from the funds account associated with and authorized by the payment device's device account.

[0082] The steps described above are explained in detail below.

[0083] First, before performing step 210, the payer in this application embodiment needs to complete real-name authentication in the payment device, that is, set up a device account for the payment device, and associate and authorize the device account of the payment device with at least one fund account of the payer according to the identity information of the payer, so as to realize the connection between the device account and the fund account and establish a unique customer mapping relationship in order to complete the payment by the payer.

[0084] Based on this, regarding step 210, the steps of receiving payment input can be illustrated in different scenarios in this application embodiment.

[0085] In one possible embodiment, the payment device may include at least one payment application, which includes a payment interface that may include a first bill and a payment control corresponding to the first bill, and may determine the user's input of touching the payment control as a payment input for the first bill.

[0086] In another possible embodiment, the user's input of pressing a preset touch payment button on the payment device, swiping a preset gesture on the touch screen of the payment device, or clicking a preset position on the touch screen of the payment device can be identified as the payment input for the first bill.

[0087] Regarding step 220, in one possible embodiment, step 220 may specifically include:

[0088] In response to a payment input, a first payment connection request is sent to the payee's payment device via the device's operating system, according to the operating system's preset data transmission protocol.

[0089] To enrich payment scenarios, the information carried in the first payment connection request can be different, which will be explained below.

[0090] In some instances, the first payment connection request can carry the payment amount from the first invoice. This first payment connection request can be used to request a connection with the payee's receiving device to establish a payment relationship between the payee and payer. It can also be used to display the first invoice and its payment amount to the payee so that the payee can confirm the accuracy of the payment amount. Thus, if the payee allows the connection to be established—that is, if the payer receives the receiving connection information sent by the payee's receiving device—the deduction can be executed without the payer and payee repeatedly confirming the first invoice and its payment amount. This simplifies the payment process and improves payment efficiency.

[0091] In other examples, the first payment connection request is only used to request a connection with the payee's receiving device to establish a payment relationship between the payee and the payer. Then, if the payee allows the connection to be established, i.e., the payer receives the receiving connection information sent by the payee's receiving device, the payer is prompted to enter the payment amount and select the funds account associated with and authorized by the device account of the paying device, thereby completing the deduction.

[0092] It should be noted that the embodiments of this application do not limit the specific function of the first payment connection request, and the function of the first payment connection request can be adjusted according to the actual situation.

[0093] Regarding step 230, to ensure the security of the payer's funds, upon receiving the payment connection information sent by the receiving device, the payment device can determine whether to deduct the payment directly based on the payment amount. Therefore, step 230 may specifically include:

[0094] Upon receiving payment connection information from the receiving device, it determines whether the payment amount meets the preset payment conditions. The preset payment conditions are determined by the preset payment permissions of the funds account associated with and authorized by the device account of the paying device.

[0095] In this way, if the payment amount meets the preset payment conditions, the payment amount in the first bill is deducted from the funds account associated with and authorized by the device account of the paying device; conversely, if the payment amount does not meet the preset payment conditions, the payment password verification information of the funds account is obtained; if it is determined that the entered payment password verification information matches the preset payment password verification information, the payment amount in the first bill is deducted from the funds account associated with and authorized by the device account of the paying device. That is, at the time of payment, the payment password of the payer's funds account is verified, thereby preventing the payer's financial loss.

[0096] Therefore, the payment connection and information transmission channel between the payee and the payer can be established through the operating system in the electronic device, realizing the flow of payment bills and thus establishing a payment relationship between the payee and the payer. Then, with the payee's receiving device and the payer's payment device connected, the payment can be completed through the fund account corresponding to the device account. The payment method is flexible and the operation is simple, which can simplify the payment process, improve payment efficiency and reduce the hardware cost of the acquiring device.

[0097] based on Figure 2 In some embodiments, the payment device may further include a payment application that provides payment services and is linked to the payer's funds account. In this embodiment, the payer can associate and authorize the payment application with the funds account linked to the payment service provided by the payment application, based on the connection between the device account and the funds account and the establishment of a unique customer mapping relationship. This enables the payer to use the funds account in the corresponding payment application to make payments.

[0098] Figure 3 A flowchart of another embodiment of the payment method provided in the first aspect of this application. Figure 3 and Figure 2 The difference is that, Figure 3 The payment method shown may also include step 240, that is, before step 210, step 240 may include:

[0099] Based on the payer's input, associate and authorize the device account, funds account, and application account of the payment application for the payment device.

[0100] Based on step 240, to ensure the security of the payer's funds, upon receiving the payment connection information sent by the receiving device, the paying device can determine whether to deduct the payment directly based on the payment amount. Thus, if the first payment connection request carries a first invoice, and the first invoice includes the payment amount, step 230 can specifically include:

[0101] Upon receiving payment connection information from the payment device, it determines whether the payment amount meets the preset payment conditions, which are determined by the preset payment permissions of the payment application.

[0102] If the payment amount meets the preset payment conditions, the payment amount in the first bill will be deducted from the funds account associated with and authorized by the device account of the payment device;

[0103] If the payment amount does not meet the preset payment conditions, obtain the payment password verification information of the funds account; if it is determined that the entered payment password verification information matches the preset payment password verification information, deduct the payment amount from the first bill from the funds account associated with and authorized by the device account of the payment device.

[0104] Here, in this embodiment of the application, the device account, funds account, and application account of the payment device can be associated and authorized before the payment device sends the first payment connection request to the receiving device, or the device account, funds account, and application account of the payment application can be associated and authorized before the step of deducting the payment amount in the first bill from the funds account associated and authorized with the device account of the payment device. The order in which the device account, funds account, and application account of the payment application are associated and authorized is not limited here, and can be selected according to the actual situation.

[0105] It should be noted that this is different from the above. Figure 2 The difference in step 230 shown is that, because a payment application is added, its preset payment conditions can be determined based on the preset payment permissions of the payment application.

[0106] Based on the above Figure 2 In some embodiments, the steps shown allow the payment device to determine the receiving device with which it intends to establish a payment connection, using information such as geographic location, Bluetooth signal, acoustic signal, and operating system. To accurately distinguish the receiving device among multiple geographically associated devices, embodiments of this application can further determine its identity based on geographic location and the mapping relationship between the three: device account, funds account, and application account. Figure 4 A flowchart of yet another embodiment of the payment method provided in the first aspect of this application. Figure 4 and Figure 2 and Figure 3 The difference is that, Figure 4 The payment method shown may also include step 250, which is before step 210 (or before step 210 and after step 240), and step 250 may include:

[0107] Based on the geographical location of the payment device, display information about the user device associated with that location; based on the information about the user device, determine the receiving device.

[0108] In this way, user devices can be initially screened based on the geographical location of the payment device. Then, further, the steps mentioned above for determining the receiving device based on the user device information can specifically include:

[0109] Based on information about the user's device, devices that have been associated with and authorized device accounts, funds accounts, and application accounts for payment applications are identified as receiving devices.

[0110] In addition to identifying the payment device by geographical location, you can also identify it by directly touching the device for connection. The specific steps are as follows:

[0111] Detects whether there is contact with the user's device;

[0112] If contact with a user device is detected, the user device that has contacted the payment device is identified as the receiving device.

[0113] This can further improve the accuracy of identifying the receiving device, thereby reducing the likelihood of sending payment connection requests to devices that are not receiving devices, and further improving payment security.

[0114] Furthermore, the range of geographical location in this embodiment can be set independently; that is, the geographical location can be the payer's real-time geographical location or a geographical location set by the payer, and is not limited here. Specifically, when the geographical location is a geographical location set by the payer, information about the user device associated with the set geographical location can be displayed to enable remote payment via the Internet.

[0115] Thus, in conjunction with the above, the payment method provided in this application embodiment, under the premise of completing the connection between the device account, application account, and fund account and establishing a unique customer mapping relationship, can realize the flow of bills by completing hardware connection between devices or pushing information between devices through the payment device and the operating system of the device when the geographical distance between the payee and the payer is relatively close, thereby establishing a payment relationship between the payee and the payer, and then completing the payment through the fund account corresponding to the device account. At the same time, it also supports the payee and the payer to complete the payment through the Internet when the geographical distance between the payee and the payer is far.

[0116] Based on the above Figure 2 In some embodiments, the steps shown, besides indicating that the payment device has successfully established a connection with the receiving device by receiving connection information sent by the receiving device, can also provide a scenario where the payment device has not established a connection with the receiving device. Based on this, Figure 5 A flowchart of yet another embodiment of the payment method provided in the first aspect of this application. Figure 5 and Figure 2 , Figure 3 and Figure 4 The difference is that, Figure 5The payment method shown may also include step 260, that is, after step 220, step 260 may include:

[0117] If no payment connection information is received from the payment device, a first prompt message is displayed. The first prompt message is used to prompt the payer to confirm the first target information, and if the first target information is confirmed to meet the preset conditions, the payment should be entered again.

[0118] The first target information includes at least one of the following: device information of the receiving device, and the bill content of the first bill, which includes the payment amount.

[0119] This system prompts the payee to adjust the first target information so that the payment process can be re-executed if the payment device fails to establish a connection with the receiving device. In addition, it should be noted that, in order to improve payment efficiency, a time threshold can be set to remind the payee whether a connection has been established with the receiving device. That is, if the payee does not receive a connection information from the receiving device within a preset time, it is determined that the payment device has failed to establish a connection with the receiving device; conversely, if the payee receives a connection information from the receiving device within a preset time, it is determined that the payment device has successfully established a connection with the receiving device.

[0120] Based on the same inventive concept, the second aspect of this application provides a payment method that can be applied to a payment receiving device, that is, the payment method can be executed by the payment receiving device. Figure 6 A flowchart of an embodiment of the payment method provided in the second aspect of this application.

[0121] like Figure 6 As shown, its application scenario is a situation where the payer initiates the payment and the payee passively receives the payment. Based on this, the payment method can include:

[0122] Step 610: Receive a payment connection request sent by the payer's payment device through the device's operating system; Step 620: Based on the payment connection request, display first push information, which prompts whether to establish a payment connection with the payment device; Step 630: If it is determined that a payment connection has been established with the payment device, send collection connection information to the payer through the device's operating system. The collection connection information instructs the collection device and the payment device to establish a connection and instructs the deduction of the payment amount from the first bill from the funds account associated with and authorized by the payment device's device account.

[0123] The steps described above are explained in detail below.

[0124] First, before executing step 610, similar to the principle of the payer's payment device, the payee in this application embodiment needs to complete real-name authentication in the payment device, that is, set up the device account of the payment device, and associate and authorize the device account of the payment device with at least one fund account of the payee according to the identity information of the payee, so as to realize the connection between the device account and the fund account and establish a unique customer mapping relationship, so as to complete the payee's collection.

[0125] Regarding step 620, this application embodiment provides examples of displaying the content of the first push information in different scenarios corresponding to step 210.

[0126] In one possible embodiment, the receiving device may include at least one payment application. When the payment application in the receiving device and the payment application in the paying device are the same payment application, when the paying device receives payment input from a user touching the payment control, a first push notification can be displayed through the application communication interface of the receiving device that has the same payment application. Alternatively, the device's operating system can prompt the payee and payer to establish a payment connection with the paying device using a specific payment application via system prompts.

[0127] In another possible embodiment, the receiving device can push a first push message to the payee via the device's operating system in the form of a system prompt.

[0128] In step 530, this embodiment of the application can determine the establishment of a payment connection between the receiving device and the paying device through the process of the payee confirming the payment method. Specifically, before step 530, the payment method may also include:

[0129] Display at least one payment method;

[0130] Upon receiving input selecting a target payment method among at least one payment method, a payment connection is established with the payment device.

[0131] It should be noted that the payment method here can be the default, in which case the payee does not need to make a selection. Based on this, the payee's confirmation process of the first push message can be used as the basis for determining whether a payment connection has been established between the receiving device and the paying device. For example, the first recommendation message includes two options: allow connection and disallow connection. Thus, if the receiving device receives the input to allow connection, it sends the payment connection information to the payer through its operating system; conversely, if the receiving device does not receive the input to allow connection, it does not perform any action. Of course, to facilitate the payer's understanding of the payee's status as soon as possible, the receiving device may send a message to the payer indicating that a payment connection will not be established if it does not receive the input to allow connection.

[0132] Based on the above process, in some embodiments, the payment receiving device includes a payment application that provides a payment receiving service. The payment receiving service is linked to the payee's funds account so that the payment amount deducted by the payer can be added to the payee's funds account. In this embodiment, the payee can associate and authorize the payment application with the payee's funds account linked to the payment service provided by the payment application, based on the connection between the device account and the funds account and the establishment of a unique customer mapping relationship. This enables the payee to use the funds account in the corresponding payment application to receive payments.

[0133] Based on this Figure 7 A flowchart of another embodiment of the payment method provided in the second aspect of this application. Figure 7 and Figure 6 The difference is that, Figure 7 The payment method shown may also include step 640, that is, after step 630, step 640 may include:

[0134] When the application account of the payment application is associated with and authorized with the device account of the receiving device, the payment amount deducted from the payer's funds account will be transferred to the payee's funds account.

[0135] It should be noted that the embodiments of this application are not limited to the case where the payment amount deducted from the payer's funds account is transferred to the payee's funds account. In some examples, the payee can automatically bind the payee's account within a preset association period after the payment amount is transferred from the payer's funds account to the payee's funds account. If, within the preset association period, the device account of the payee's payment device, the payee's funds account, and the application account of the payment application are associated and authorized based on the payee's input, the payment amount will be transferred to the payee's funds account. Conversely, if the preset association period is exceeded—that is, if it is determined that the device account of the payee's payment device, the payee's funds account, and the application account of the payment application are not associated and authorized within the preset association period—the payment amount will be returned to the payer's funds account, thereby ensuring the payer's fund security.

[0136] In summary, in scenarios where the payer initiates payment and the payee passively receives payment, the payer's electronic payment device receives the payment input for the first bill. Responding to this input, the device's operating system sends a first payment connection request to the payee's receiving device. Upon receiving the receiving device's connection information, the device deducts the payment amount from the first bill from the funds account associated with and authorized by the payer's device account. This approach is independent of the hardware limitations of the acquiring device and electronic devices, and does not rely on the funds account within the payment application installed on the electronic device. It only requires establishing a payment connection and information transmission channel between the payee and payer through the electronic device's operating system, thus enabling the flow of the payment bill and establishing a payment relationship between them. Once the payee's receiving device and the payer's payment device are connected, payment can be completed using the funds account corresponding to the device account, or the device account, the payment application's application account, and the funds account. This flexible and simple payment method simplifies the payment process, improves efficiency, and reduces the hardware costs of the acquiring device.

[0137] Furthermore, based on the aforementioned scenario where the payer initiates payment and the payee passively receives payment, this application embodiment also provides a payment method in the scenario where the payer passively pays, i.e., the payee initiates payment, specifically in conjunction with... Figure 8 and Figure 10 Please provide a detailed explanation.

[0138] Figure 8 A flowchart of an embodiment of the payment method provided in the third aspect of this application.

[0139] like Figure 8 As shown, this application provides a payment method for a third aspect, which can be applied to a payment receiving device. That is, the payment method can be executed by the payment receiving device, and its application scenario is a scenario where the payer passively pays, i.e., the payee initiates the payment. Based on this, the payment method may include:

[0140] Step 810: Receive payment input for the second bill; Step 820: In response to the payment input, send a second payment connection request to the payer's payment device through the device's operating system. The second payment connection request carries the second bill, which includes the payment amount. The second payment connection request is used to request the establishment of a payment connection with the payment device and to instruct the payer to deduct the payment amount from a funds account associated with and authorized by the payment device's device account.

[0141] The steps described above are explained in detail below.

[0142] First, before executing step 810, the payee in this application embodiment needs to complete real-name authentication in the payment device, that is, set up the device account of the payment device, and associate and authorize the device account of the payment device with at least one fund account of the payee according to the identity information of the payee, so as to realize the connection between the device account and the fund account and establish a unique customer mapping relationship, so as to complete the payment collection by the payee.

[0143] Regarding step 810, this application embodiment can provide examples of the steps for receiving payment input in different scenarios.

[0144] In one possible embodiment, the payment device may include at least one payment application, which includes a payment interface that may include a second bill and a corresponding payment control for the second bill, and may determine the user's touch input of the payment control as the payment input for the second bill.

[0145] In another possible embodiment, the user's input of pressing the preset touch payment button on the payment device, swiping the preset gesture on the touch screen of the payment device, or clicking the preset position on the touch screen of the payment device can be identified as the payment input for the second bill.

[0146] Regarding step 820, in one possible embodiment, step 820 may specifically include:

[0147] In response to a payment input, a second payment connection request is sent to the payer's payment device via the device's operating system, according to the operating system's preset data transmission protocol.

[0148] Here, in order to enrich the payment scenarios, the information carried in the second payment connection request can be different, which will be explained below.

[0149] In some instances, the second payment connection request can carry the payment amount from the second invoice. This second payment connection request can be used to request a connection with the payer's payment device to establish a payment relationship between the payer and payee. It can also be used to display the second invoice and the payment amount in it to the payer so that the payer can confirm the accuracy of the payment amount. Thus, once the payer allows the connection to be established (i.e., once the payer confirms that the payment device and the payee's device have established a payment connection), the payment is completed without the need for repeated confirmation of the payment amounts from the second invoice and the payee. This simplifies the payment process and improves payment efficiency.

[0150] In other examples, the second payment connection request is only used to request a connection with the payer's receiving device to establish a payment relationship between the payer and payee. Then, if the payer allows the connection to be established, the payer is prompted to enter the payment amount to complete the deduction.

[0151] It should be noted that the embodiments of this application do not limit the specific function of the second payment connection request, and the function of the second payment connection request can be adjusted according to the actual situation.

[0152] Based on the above steps, in some embodiments, the receiving device may further include a payment application that provides payment services and is linked to the payee's funds account. In this way, the payee in this embodiment can associate and authorize the payment application with the payee's funds account linked to the payment service provided by the payment application, based on the connection between the device account and the funds account and the establishment of a unique customer mapping relationship. This enables the payee to use the funds account in the corresponding payment application to receive payments.

[0153] Based on this Figure 9 A flowchart of another embodiment of the payment method provided in the third aspect of this application. Figure 9 and Figure 8 The difference is that, Figure 8 The payment method shown may also include step 840, such as Figure 8 As shown, prior to step 810, if the receiving device includes a payment application that provides a payment service and is linked to the payee's funds account, step 830 may include:

[0154] When the payer deducts the payment amount from the funds account associated with and authorized by the payment device's device account, within a preset association period, the device account of the receiving device, the funds account of the receiving device, and the application account of the payment application are associated and authorized based on the input of the receiving party.

[0155] Conversely, if the payer deducts the amount received from the funds account associated with and authorized by the device account of the payment device, within a preset association period, the device account of the unassociated and unauthorized payment device, the payee's funds account, and the application account of the payment application will be identified, and the amount received will be returned to the payer's funds account.

[0156] Therefore, this embodiment is not limited to the order in which the payee associates and authorizes the device account of the receiving device, the payee's funds account, and the application account of the payment application. Instead, the receiving device may associate and authorize its device account, the payee's funds account, and the payment application's application account after the payment amount deducted from the payer's funds account has been transferred to the payee's funds account, in order to transfer the payment amount to the payee's funds account. Alternatively, when a payment connection is established with the paying device, the order in which the payee associates and authorizes the device account of the receiving device, the payee's funds account, and the payment application's application account may be chosen to facilitate subsequent payment collection.

[0157] Furthermore, based on the above steps, in some embodiments, besides the case where the collecting device receives payment connection information sent by the paying device, indicating that the collecting device has successfully established a connection with the paying device, a case where the collecting device has not established a connection with the paying device can also be provided. Therefore, after step 810, the payment method may further include:

[0158] If no payment connection information is received from the payment device, a second prompt message is displayed. The second prompt message is used to prompt the payee to confirm the second target information, and if the second target information is confirmed to meet the preset conditions, the payee should re-enter the payment information.

[0159] The second target information includes at least one of the following: device information of the payment device, bill content of the second bill, and the bill content includes the amount received.

[0160] This prompts the payee to adjust the second target information so that the payment process can be re-executed if the payment device fails to establish a connection with the receiving device.

[0161] It should be noted that, in order to improve payment efficiency, a time threshold can be set to remind the payee whether a connection has been established with the receiving device. That is, if the payee does not receive a payment connection information from the payment device within a preset time, it is determined that the payment device has not successfully established a connection with the receiving device; conversely, if the payee receives a payment connection information from the payment device within a preset time, it is determined that the payment device has successfully established a connection with the receiving device.

[0162] It should be noted that, in the embodiments of this application, the method for determining the payment device of the payer can also refer to... Figure 4 Step 250, as shown, involves displaying information about the user device associated with the geographical location of the receiving device; and determining the payment device based on the information of the user device.

[0163] In this way, user devices can be initially screened based on the geographical location of the receiving device. Then, further, the steps mentioned above for determining the payment device based on the user device information can specifically include:

[0164] Based on information about the user's device, devices that have been associated with and authorized device accounts, funds accounts, and application accounts for payment applications are identified as payment devices.

[0165] In addition to identifying the payment device by geographical location, you can also identify it by directly touching the device for connection. The specific steps are as follows:

[0166] Detects whether there is contact with the user's device;

[0167] If contact with a user device is detected, the user device that has contacted the receiving device is identified as the payment device.

[0168] This can further improve the accuracy of identifying the payment device, thereby reducing the likelihood of sending payment connection requests to devices that are not payment devices, and further enhancing payment security. Based on the same inventive concept, a fourth aspect of this application provides a payment method that can be applied to a payment device, i.e., the payment method can be executed by the payment device. Figure 10 A flowchart of an embodiment of the payment method provided in the fourth aspect of this application.

[0169] like Figure 10 As shown, its application scenario is a passive payment by the payer, i.e., a payment initiated by the payee. Based on this, the payment method can include:

[0170] Step 1010: Receive a second payment connection request sent by the receiving device through its operating system. The second payment connection request carries a second invoice, which includes the amount to be received. Step 1020: Based on the second payment connection request, display a second push notification to indicate whether to establish a payment connection with the receiving device. Step 1030: Upon receiving input confirming the establishment of a payment connection with the receiving device, deduct the amount to be received from the funds account associated with and authorized by the payment device's device account, based on the second invoice.

[0171] The steps described above are explained in detail below.

[0172] First, before performing step 1010, the payer in this application embodiment needs to complete real-name authentication in the payment device, that is, set up a device account for the payment device, and associate and authorize the device account of the payment device with at least one fund account of the payer according to the identity information of the payer, so as to realize the connection between the device account and the fund account and establish a unique customer mapping relationship in order to complete the payment by the payer.

[0173] Regarding step 1030, this embodiment of the application can establish a payment connection between the payment device and the receiving device by having the payer input payment password verification information of the payer's funds account. Specifically, before step 1030, the payment method may include:

[0174] Once the payment password verification information of the funds account is obtained, a payment connection is established with the receiving device.

[0175] It should be noted that the payment password verification information here can include character information manually entered by the user, or facial information, fingerprint information, or voiceprint information of the payer.

[0176] Therefore, to ensure the safety of the payer's funds, upon receiving input confirming the establishment of a payment connection with the receiving device, the payment device can determine whether to deduct the payment directly based on the payment amount. Accordingly, step 1030 may specifically include:

[0177] Upon receiving input confirming the establishment of a payment connection with the receiving device, it determines whether the payment amount meets the preset payment conditions, which are determined by the preset payment permissions of the funds account associated with and authorized by the device account of the paying device.

[0178] In this way, if the received amount meets the preset payment conditions, the amount in the second invoice is deducted from the funds account associated with and authorized by the payment device's device account. Conversely, if the received amount does not meet the preset payment conditions, the payment password verification information of the funds account is obtained. If the entered payment password verification information matches the preset payment password verification information, the amount in the second invoice is deducted from the funds account associated with and authorized by the payment device's device account. In other words, the payment password of the payer's funds account is verified at the time of payment, thereby preventing financial loss for the payer.

[0179] In summary, this method does not rely on the hardware limitations of acquiring devices or electronic devices, nor on the funds account in the payment application installed on the electronic device. It only requires establishing a payment connection and information transmission channel between the payee and the payer through the operating system of the electronic device, realizing the flow of payment bills and thus establishing a payment relationship between the payee and the payer. Then, with the payee's acquiring device and the payer's payment device connected, the payment can be completed through the funds account corresponding to the device account, or the device account, the application account of the payment application, and the funds account. The payment method is flexible and simple to operate, which can simplify the payment process, improve payment efficiency, and reduce the hardware cost of acquiring devices.

[0180] To facilitate understanding of the payment method in the embodiments of this application, the following example illustrates the payment process between the payment device, the receiving device, the business system, and the account management system, using the scenario where the payer initiates the payment and the payee passively receives the payment.

[0181] In execution such Figure 11 He Ru Figure 12 Before illustrating the process, it should be noted that the payment method provided in this application embodiment solves the payment problem between the payee and the payer. It is hardware-independent, enables cross-application payments, and can be initiated by either the payer or the payee. The payee and payer execute the payment method provided in this application embodiment through devices (i.e., the receiving device and the paying device) or the payment application used for payment. In executing... Figure 11 He Ru Figure 12 Before the process shown, the payer and payee need to complete real-name authentication of the device account, set up and authorize the binding authentication between the device account and the application account of the payment application, and associate and bind the authentication between the application account of the payment application and the funds account, so as to realize the account connection of the device account, application account and funds account and establish a unique customer mapping relationship.

[0182] Based on this Figure 11 A flowchart illustrating an example of a payment process provided in an embodiment of this application.

[0183] like Figure 11 As shown, the payment method may include steps 1111 to 1118.

[0184] Step 1111: The payment device receives the payment input from the payer for the first bill in the payment application on the payment device, which is considered as initiating the establishment of a payment connection relationship.

[0185] Step 1112: The payment application in the payment device sends a first payment connection request to the payment application in the payee's receiving device through the device's operating system to request the establishment of a payment connection relationship.

[0186] Step 1113: The payment application in the receiving device prompts the recipient to collect payment.

[0187] In step 1114, the receiving device can select a payment method while confirming payment, or use the default payment method. Confirmation of payment by the payee is considered agreement to establish a payment connection. Conversely, if the payee refuses payment, the device's operating system sends a message to the paying device prompting the payee to confirm the contents of the first invoice with the paying party, so that payment can be re-initiated after verification.

[0188] Step 1115: The payment application in the receiving device returns the payment connection information to the device's operating system, and then sends the payment connection information to the payment device through the device's operating system.

[0189] Step 1116: Upon receiving the payment connection information from the receiving device, the payment device determines that the operating systems of the two devices have completed the establishment of a payment connection. Simultaneously, the operating system of the device notifies the payment application in the payment device to initiate a payment. Then, the payment application in the payment device sends a payment request to the account management system. The payment request includes the application account of the payment application and the funds account associated with and authorized by the application account.

[0190] Step 1117: The account management system performs security verification based on the application account of the payment application making the payment in the payment request and the fund account associated with and authorized by the application account. If the security verification is successful, a deduction request is sent to the business system. The deduction request includes the application account of the payment application making the payment, the fund account associated with and authorized by the application account, and instructions to allow the deduction.

[0191] Step 1118: Based on the deduction request, the business system deducts the payment amount from the first bill from the funds account associated with and authorized by the application account of the payment application in the payment device, and adds the deducted payment amount to the funds account authorized and bound to the payee's device account with the payment device in order to complete the payment.

[0192] The specific details of steps 1111 to 1118 above can be found in the relevant content of the above embodiments, and will not be repeated here.

[0193] Similarly, to facilitate understanding of the payment method in the embodiments of this application, the following example illustrates the payment process between the payment device, the receiving device, the business system, and the account management system, using the scenario of passive payment by the payer, i.e., payment initiated by the payee.

[0194] Figure 12 A flowchart illustrating another example of a payment process provided in an embodiment of this application.

[0195] like Figure 12 As shown, the payment method may include steps 1211 to 1217.

[0196] Step 1211: The receiving device receives the receiving party's payment input for the second bill in the payment application on the receiving device, which is considered as initiating the establishment of a payment connection relationship.

[0197] Step 1212: The payment application in the receiving device sends a second payment connection request to the payment application in the payer's payment device through the device's operating system to request the establishment of a payment connection relationship.

[0198] Step 1213: The payment application in the payment device prompts the payer to make payment.

[0199] In step 1214, the payment device may, upon confirming payment, default to agreeing to establish a payment connection and forwarding the payment to the payment application within the payment device. Conversely, if the payer refuses to accept payment, the device's operating system sends a message to the payment device prompting the payee to confirm the contents of the second invoice with the payer, so that payment can be re-initiated after confirmation.

[0200] Step 1215: The payment application in the payment device returns connection confirmation information to the device's operating system, and sends connection confirmation information to the receiving device through the device's operating system.

[0201] Step 1216: The operating system of the device notifies the payment application in the payment device to initiate a payment. Then, the payment application in the payment device sends a payment request to the account management system. The payment request includes the application account of the payment application and the funds account associated with and authorized by the application account.

[0202] Step 1217: The account management system performs security verification based on the application account of the payment application making the payment in the payment request and the fund account associated with and authorized by the application account. If the security verification is successful, a deduction request is sent to the business system. The deduction request includes the application account of the payment application making the payment, the fund account associated with and authorized by the application account, and instructions to allow the deduction.

[0203] Step 1218: Based on the deduction request, the business system deducts the payment amount from the first bill from the funds account associated with and authorized by the application account of the payment application in the payment device, and adds the deducted payment amount to the funds account authorized and bound to the payee's device account with the payment device in order to complete the payment.

[0204] The specific details of steps 1211 to 1217 above can be found in the relevant content of the above embodiments, and will not be repeated here.

[0205] In summary, the embodiments of this application provide a payment method, device, and storage medium. The method receives a payment input for a first bill. In response to the payment input, the operating system of the device sends a first payment connection request to the payee's receiving device. Upon receiving the receiving connection information from the receiving device, the payment amount in the first bill is deducted from the funds account associated with and authorized by the device account of the paying device. This approach does not rely on the hardware limitations of the acquiring device or electronic device, nor does it restrict the funds account in the payment application installed on the electronic device. It only requires establishing a payment connection and information transmission channel between the payee and the payer through the operating system of the electronic device, thus realizing the flow of payment bills and establishing a payment relationship between the payee and the payer. Then, with the connection established between the payee's receiving device and the payer's paying device, payment can be completed through the funds account corresponding to the device account. The payment method is flexible and simple to operate, simplifying the payment process, improving payment efficiency, and reducing the hardware cost of the acquiring device.

[0206] Based on the same inventive concept, the fifth aspect of this application provides a payment device for the payer. Figure 13 A schematic diagram of an embodiment of the payment device provided in the fifth aspect of this application.

[0207] like Figure 13 As shown, payment device 1300 can be used for, for example Figure 1 The payment device 11 and payment device 1300 shown may specifically include:

[0208] The receiving module 1301 is used to receive payment input for the first bill;

[0209] The sending module 1302 is used to send a first payment connection request to the payee's receiving device through the device's operating system in response to a payment input;

[0210] The payment processing module 1303 is used to deduct the payment amount from the first bill from the funds account associated with and authorized by the device account of the payment device when it receives the payment connection information sent by the receiving device.

[0211] The payment device 1300 provided in the embodiments of this application will be described in detail below.

[0212] In one or more possible embodiments, the payment device 1300 provided in this application may further include a first association module, used to associate and authorize the device account of the payment device with at least one fund account of the payer based on the identity information of the payer.

[0213] In another or more possible embodiments, the payment device 1300 provided in this application embodiment may further include a second association module, used to associate and authorize the device account, fund account and application account of the payment device and the payment application based on the input of the payer, when the payment device includes a payment application, the payment application provides payment services and the payment service is bound to the payer's funds account.

[0214] In another possible embodiment, the payment processing module 1303 may be specifically used to determine whether the payment amount meets the preset payment conditions when the first payment connection request carries the first bill, the first bill includes the payment amount, and the payment connection information sent by the payment receiving device is received; the preset payment conditions are determined by the preset payment permissions of the payment application.

[0215] If the payment amount meets the preset payment conditions, the payment amount in the first bill will be deducted from the funds account associated with and authorized by the device account of the payment device;

[0216] If the payment amount does not meet the preset payment conditions, obtain the payment password verification information of the funds account; if it is determined that the entered payment password verification information matches the preset payment password verification information, deduct the payment amount from the first bill from the funds account associated with and authorized by the device account of the payment device.

[0217] In another or more possible embodiments, the payment device 1300 provided in this application may further include a first display module and a first determination module; wherein,

[0218] The first display module is used to display information about the user device associated with the geographical location of the payment device.

[0219] The first determination module is used to determine the receiving device based on the user's device information.

[0220] In another or more possible embodiments, the payment device 1300 provided in this application may further include a detection module and a second determination module; wherein,

[0221] The detection module is used to detect whether there is contact with the user's equipment;

[0222] The second determining module is used to determine, upon detecting contact with the user device, that the user device that is in contact with the payment device is the receiving device.

[0223] It should be noted that the device account, funds account, and application account of the payment device are interconnected, and the device account of the payment device authorizes the funds account of the payment device.

[0224] In another or more possible embodiments, the sending module 1302 may specifically be used to send a first payment connection request to the payee's receiving device through the device's operating system in response to a payment input, according to the operating system's preset data transmission protocol.

[0225] In another or more possible embodiments, the payment device 1300 provided in this application embodiment may further include a second display module, which is used to display a first prompt message when no payment connection information is received from the receiving device. The first prompt message is used to prompt the payer to confirm the first target information and, if the first target information is confirmed to meet the preset conditions, to re-enter the payment information.

[0226] The first target information includes at least one of the following: device information of the receiving device, and the bill content of the first bill, which includes the payment amount.

[0227] Based on the same inventive concept, the sixth aspect of this application provides a payment receiving device for the payee. Figure 14 A schematic diagram of an embodiment of the payment collection device provided in the sixth aspect of this application.

[0228] like Figure 14 As shown, the payment collection device 1400 can be used as follows: Figure 1 The payment collection device 12 and payment collection device 1400 shown may specifically include:

[0229] The receiving module 1401 is used to receive a payment connection request sent by the payer's payment device through the device's operating system;

[0230] Display module 1402 is used to display first push information based on payment connection request. The first push information is used to prompt whether to establish a payment connection with payment device.

[0231] The sending module 1403 is used to send payment connection information to the payer through the operating system of the device when it is determined that a payment connection has been established with the payment device. The payment connection information is used to instruct the receiving device and the paying device to establish a connection and to instruct the deduction of the payment amount in the first bill from the funds account associated with and authorized by the device account of the paying device.

[0232] The following is a detailed description of the payment device 1400 provided in the embodiments of this application.

[0233] In one or more possible embodiments, the payment device 1400 provided in this application embodiment may further include a payment processing module, used to transfer the payment amount deducted from the payer's funds account to the payee's funds account when the payment device includes a payment application, the payment application provides a payment service, the payment service is bound to the payee's funds account, and the application account of the payment application is associated with and authorized to the device account of the payment device.

[0234] Based on the same inventive concept, the seventh aspect of this application provides a payment receiving device for the payee. Figure 15 A schematic diagram of an embodiment of the payment collection device provided in the seventh aspect of this application.

[0235] like Figure 15 As shown, the 1500 payment device can provide, for example... Figure 1 The payment collection device 12 shown, and the payment collection device 1500 specifically may include:

[0236] The receiving module 1501 is used to receive payment input for the second bill;

[0237] The sending module 1502 is configured to, in response to a payment input, send a second payment connection request to the payer's payment device via the device's operating system. The second payment connection request carries a second invoice, which includes the payment amount. The second payment connection request is used to request the establishment of a payment connection with the payment device and to instruct the payer to deduct the payment amount from a funds account associated with and authorized by the payment device's device account.

[0238] The following is a detailed description of the payment device 1500 provided in the embodiments of this application.

[0239] In one or more possible embodiments, the payment receiving device 1500 provided in this application embodiment may further include a second association module, which is used to associate and authorize the device account of the payment receiving device, the payment receiving account of the payee, and the application account of the payment application within a preset association period, based on the input of the payee, when the payment receiving device includes a payment application, the payment application provides a payment receiving service, the payment receiving service is bound to the payee's funds account, and the payer deducts the payment amount from the funds account associated with and authorized by the device account of the payment device.

[0240] In another or more possible embodiments, the payment receiving device 1500 provided in this application embodiment may further include a processing module, which is used to determine, within a preset association period, the device account of the payment receiving device that is not associated and authorized, the payment receiving device's fund account, and the payment application's application account when the payer deducts the payment amount from the fund account associated with and authorized by the payment device's device account, and then returns the payment amount to the payer's fund account.

[0241] In another or more possible embodiments, the payment receiving device 1500 provided in this application embodiment may further include a first display module, used to display a second prompt message when no payment connection information is received from the payment device. The second prompt message is used to prompt the payee to confirm the second target information, and to re-enter the payment information when the second target information is confirmed to meet the preset conditions.

[0242] The second target information includes at least one of the following: device information of the payment device, bill content of the second bill, and the bill content includes the amount received.

[0243] In another or more possible embodiments, the payment device 1500 provided in this application may further include a second display module and a first determination module; wherein,

[0244] The second display module is used to display information about the user device associated with the geographical location of the receiving device.

[0245] The first determination module is used to determine the payment device based on the information of the user device.

[0246] In another or more possible embodiments, the payment receiving device 1500 provided in this application may further include a detection module and a second determination module; wherein,

[0247] The detection module is used to detect whether there is contact with the user's equipment;

[0248] The second determining module is used to determine, upon detecting contact with the user device, that the user device that is in contact with the receiving device is the payment device.

[0249] Based on the same inventive concept, the eighth aspect of this application provides a payment device for the payer. Figure 16 A schematic diagram of an embodiment of the payment device provided in the eighth aspect of this application.

[0250] like Figure 16 As shown, payment device 1600 can be used for, for example Figure 1 The payment device 11 shown, and the payment device 1600 specifically may include:

[0251] The receiving module 1601 is used to receive a second payment connection request sent by the receiving device of the payee through the device's operating system. The second payment connection request carries a second bill, which includes the amount to be received.

[0252] Display module 1602 is used to display second push information based on the second payment connection request. The second push information is used to prompt whether to establish a payment connection with the receiving device.

[0253] The payment processing module 1603 is used to deduct the payment amount from the funds account associated with and authorized by the device account of the payment device based on a second bill, upon receiving input confirming the establishment of a payment connection with the receiving device.

[0254] The payment device 1600 provided in the embodiments of this application will be described in detail below.

[0255] In one or more possible embodiments, the payment device 1600 provided in this application may further include a determining module, used to determine to establish a payment connection with the receiving device when the payment password verification information of the funds account is obtained.

[0256] A ninth aspect of this application also provides a service device, which may include, for example, Figure 1 The payment and collection devices are shown. Figure 17 This is a schematic diagram of the structure of an embodiment of the service equipment provided in the ninth aspect of this application. Figure 17 As shown, the service device 1700 includes an input device 1701, an input interface 1702, a processor 1703, a memory 1704, an output interface 1705, and an output device 1706.

[0257] Input interface 1702, processor 1703, memory 1704, and output interface 1705 are interconnected via bus 1710. Input device 1701 and output device 1706 are connected to bus 1710 via input interface 1702 and output interface 1705, respectively, and thus connected to other components of service device 1700. Specifically, input device 1701 receives input information from the outside and transmits the input information to processor 1703 via input interface 1702; processor 1703 processes the input information based on computer-executable instructions stored in memory 1704 to generate output information, temporarily or permanently stores the output information in memory 1704, and then transmits the output information to output device 1706 via output interface 1705; output device 1706 outputs the output information to the outside of service device 1700 for user use.

[0258] In one embodiment, Figure 17 The business device 1700 shown can be implemented as a payment device, which may include: a memory configured to store a program; and a processor configured to run the program stored in the memory to execute the payment method described in the above embodiments.

[0259] In one embodiment, the memory can also be used to store file content and in conjunction with the above. Figures 1 to 10 The calculation results for each step in the payment process are described.

[0260] According to embodiments of this application, the processes described in the above-described flowcharts can be implemented as a computer-readable storage medium. For example, embodiments of this application include a computer-readable storage medium that stores a program or instructions on the medium, which, when executed by a service device, causes the service device to perform the steps of the above-described method.

[0261] According to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network, and / or installed from a removable storage medium.

[0262] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions that, when run on a computer, cause the computer to perform the methods described in the various embodiments above. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives), etc.

[0263] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0264] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

[0265] It should be clarified that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. For the device embodiments, equipment embodiments, and computer-readable storage medium embodiments, the relevant parts can be referred to the description section of the method embodiments. This application is not limited to the specific steps and structures described above and shown in the figures. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application. Furthermore, for the sake of brevity, detailed descriptions of known methods and techniques are omitted here.

[0266] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable payment device to produce a machine such that these instructions, executed via the processor of the computer or other programmable payment device, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0267] Those skilled in the art will understand that the above embodiments are exemplary and not restrictive. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Based on a study of the drawings, specification, and claims, those skilled in the art should be able to understand and implement other variations of the disclosed embodiments. In the claims, the term "comprising" does not exclude other means or steps; the quantifier "a" does not exclude a plurality; the terms "first" and "second" are used to identify names and not to indicate any particular order. No reference numerals in the claims should be construed as limiting the scope of protection. The functionality of multiple parts appearing in the claims can be implemented by a single hardware or software module. The appearance of certain technical features in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects.

Claims

1. A payment method, characterized in that, A payment device applied to a payer, the payment device of the payer being connected with a payment device of a payee, the method comprising: receiving a payment input for a first bill, the payment device comprising a payment application, the payment application providing a payment service, the payment service binding a fund account of the payer; in response to the payment input, associating and authorizing a device account of the payment device, the fund account and an application account of the payment application, and sending, through an operating system of the payment device, a first payment connection request to the payment device of the payee according to a preset data transmission protocol of the operating system of the payment device, the first payment connection request carrying the first bill, the first bill comprising a payment amount, the first payment connection request being used to request a connection with the payment device of the payee to establish a payment relationship between the payee and the payer; in a case where the payment device sends payment connection information, determining whether the payment amount meets a preset payment condition, the preset payment condition being determined by a preset payment permission of the payment application; in a case where the payment amount meets the preset payment condition, deducting the payment amount in the first bill from the fund account associated with and authorized by the device account of the payment device.

2. The method of claim 1, wherein, Before the first payment connection request is sent to the payment device of the payee, the method further comprises: associating and authorizing the device account of the payment device with at least one fund account of the payer according to the identity information of the payer.

3. The method of claim 1, wherein, The method further comprises: in a case where the payment amount does not meet the preset payment condition, obtaining payment password verification information of the fund account; in a case where it is determined that the input payment password verification information matches preset payment password verification information, deducting the payment amount in the first bill from the fund account associated with and authorized by the device account of the payment device.

4. The method of claim 1, wherein, Before the payment input for the first bill is received, the method further comprises: displaying information of a user device associated with a geographic location of the payment device according to the geographic location of the payment device; determining the payment device according to the information of the user device.

5. The method of claim 1, wherein, Before the payment input for the first bill is received, the method further comprises: detecting whether a user device is in contact with the payment device; in a case where it is detected that the user device is in contact with the payment device, determining that the user device in contact with the payment device is the payment device.

6. The method according to claim 4 or 5, characterized in that, The device account, the fund account and the application account of the payment application of the payment device are associated with each other, and the device account of the payment device authorizes the fund account of the payment device.

7. The method of claim 1, wherein, The method further comprises: in a case where the payment connection information of the payment device is not received, displaying first prompt information, the first prompt information being used to prompt the payer to confirm first target information, and in a case where it is confirmed that the first target information meets a preset condition, re-performing the payment input; The first target information includes at least one of the following: device information of the collection device, and bill content of the first bill, the bill content including the payment amount.

8. A payment method, characterized by, The method applied to a collection device of a collection party, the collection device of the collection party being connected with a payment device of a payment party, and the method comprising: receiving, by the collection device, a first payment connection request sent by an operating system of the payment device according to a preset data transmission protocol of the operating system of the payment device, the collection device including a payment application, the payment application providing a collection service, the collection service being bound to a fund account of the collection party, the first payment connection request carrying a first bill, the first bill including a payment amount, the first payment connection request being used to request a connection with the collection device of the collection party to establish a payment relationship between the collection party and the payment party; based on the payment connection request, displaying first push information, the first push information being used to prompt whether to establish a payment connection with the payment device; in a case where it is determined to establish a payment connection with the payment device, sending, by the collection device, collection connection information to the payment party according to a preset data transmission protocol of an operating system of the collection device, the collection connection information being used to instruct the collection device and the payment device to establish a connection and instruct the payment amount in the first bill to be deducted from a fund account associated with and authorized by a device account of the payment device; in a case where an application account of the payment application is associated with and authorized by the device account of the collection device, transferring the payment amount deducted from the fund account of the payment party to the fund account of the collection party.

9. A payment method, characterized by The method applied to a collection device of a collection party, the collection device of the collection party being connected with a payment device of a payment party, and the method comprising: receiving a collection input of a second bill; in response to the collection input, sending, by the collection device, a second payment connection request to the payment device of the payment party according to a preset data transmission protocol of an operating system of the collection device, the second payment connection request carrying the second bill, the second bill including a collection amount, the second payment connection request being used to request a payment connection with the payment device and instruct the payment party to deduct the collection amount from a fund account associated with and authorized by a device account of the payment device; the collection device including a payment application, the payment application providing a collection service, the collection service being bound to a fund account of the collection party; the method further comprising: in a case where the payment party deducts the collection amount from the fund account associated with and authorized by the device account of the payment device, associating and authorizing, within a preset association time length, a device account of the collection device, the fund account of the collection party, and an application account of the payment application according to an input of the collection party to transfer the collection amount to the fund account of the collection party.

10. The method of claim 9, wherein, The method further comprises: In a case where the payment amount is deducted from a fund account associated with and authorized by a device account of the payment device, within the preset association time length, it is determined that the device account of the payment device, the fund account of the payee and the application account of the payment application are not associated and authorized, and the payment amount is returned to the fund account of the payer.

11. The method of claim 9, wherein, After the second payment connection request is sent to the payment device of the payer, the method further comprises: In a case where the payment connection information sent by the payment device is not received, second prompt information is displayed, the second prompt information is used to prompt the payee to confirm second target information, and in a case where it is confirmed that the second target information meets a preset condition, the payment input is re-performed; The second target information comprises at least one of the following: device information of the payment device, and bill content of the second bill, the bill content comprising the payment amount.

12. The method of claim 9, wherein, Before the payment input for the second bill is received, the method further comprises: According to the geographical position of the payment device, information of a user device associated with the geographical position is displayed; According to the information of the user device, the payment device is determined.

13. The method of claim 9, wherein, Before the payment input for the second bill is received, the method further comprises: Detecting whether a user device is touched; In a case where it is detected that the user device is touched, the user device touched with the payment device is determined as the payment device.

14. A payment method, characterized by The method applied to a payment device of a payer, the payment device of the payer being connected with a payment device of a payee, the method comprising: Receiving a second payment connection request sent by a payment device of a payee through an operating system of the payment device according to a preset data transmission protocol of the operating system of the payment device, the second payment connection request carrying a second bill, the second bill comprising a payment amount, the payment device comprising a payment application, the payment application providing a payment service, the payment service being bound to a fund account of the payer; Associating and authorizing a device account of the payment device, the fund account and an application account of the payment application; Based on the second payment connection request, second push information is displayed, the second push information being used to prompt whether to establish a payment connection with the payment device; In a case where an input of establishing a payment connection with the payment device is received, it is determined whether the payment amount meets a preset payment condition, the preset payment condition being determined by a preset payment permission of the payment application; in a case where the payment amount meets the preset payment condition, the payment amount is deducted from a fund account associated with and authorized by a device account of the payment device based on the second bill.

15. The method of claim 14, wherein, Before the payment amount is deducted from the fund account associated with and authorized by the device account of the payment device based on the second bill in a case where the input of establishing a payment connection with the payment device is received, the method further comprises: In a case where the payment password verification information of the fund account is obtained, it is determined that a payment connection is established with the payment device.

16. A payment device, characterized by The payment device is connected with a payment device of a payee, comprising: a receiving module configured to receive a payment input for a first bill, the payment device comprising a payment application, the payment application providing a payment service, the payment service binding a fund account of the payer; a sending module configured to, in response to the payment input, associate and authorize a device account of the payment device, the fund account and an application account of the payment application, and send, according to a preset data transmission protocol of an operating system of the payment device, a first payment connection request to a payment device of a payee through the operating system of the payment device, the first payment connection request carrying the first bill, the first bill comprising a payment amount, the first payment connection request being used to request a connection with the payment device of the payee to establish a payment relationship between the payee and the payer; a payment processing module configured to, in a case where the payment device receives payment connection information sent by the payment device, determine whether the payment amount meets a preset payment condition, the preset payment condition being determined by a preset payment permission of the payment application; and in a case where the payment amount meets the preset payment condition, deduct the payment amount in the first bill from the fund account associated with and authorized by the device account of the payment device.

17. A cash receiving apparatus characterized by comprising: The payment device is connected with a payment device of a payee, comprising: a receiving module configured to receive a payment input for a first bill, the payment device comprising a payment application, the payment application providing a payment service, the payment service binding a fund account of the payer; a sending module configured to, in response to the payment input, associate and authorize a device account of the payment device, the fund account and an application account of the payment application, and send, according to a preset data transmission protocol of an operating system of the payment device, a first payment connection request to a payment device of a payee through the operating system of the payment device, the first payment connection request carrying the first bill, the first bill comprising a payment amount, the first payment connection request being used to request a connection with the payment device of the payee to establish a payment relationship between the payee and the payer; a payment processing module configured to, in a case where the payment device receives payment connection information sent by the payment device, determine whether the payment amount meets a preset payment condition, the preset payment condition being determined by a preset payment permission of the payment application; and in a case where the payment amount meets the preset payment condition, deduct the payment amount in the first bill from the fund account associated with and authorized by the device account of the payment device. The payment device is connected with a payment device of a payee, comprising:

18. A cash receiving apparatus characterized by comprising: a receiving module configured to receive a payment input for a first bill, the payment device comprising a payment application, the payment application providing a payment service, the payment service binding a fund account of the payer; a sending module configured to, in response to the payment input, associate and authorize a device account of the payment device, the fund account and an application account of the payment application, and send, according to a preset data transmission protocol of an operating system of the payment device, a first payment connection request to a payment device of a payee through the operating system of the payment device, the first payment connection request carrying the first bill, the first bill comprising a payment amount, the first payment connection request being used to request a connection with the payment device of the payee to establish a payment relationship between the payee and the payer; a payment processing module configured to, in a case where the payment device receives payment connection information sent by the payment device, determine whether the payment amount meets a preset payment condition, the preset payment condition being determined by a preset payment permission of the payment application; and in a case where the payment amount meets the preset payment condition, deduct the payment amount in the first bill from the fund account associated with and authorized by the device account of the payment device. The payment device is connected with a payment device of a payee, comprising: a receiving module configured to receive a payment input for a first bill, the payment device comprising a payment application, the payment application providing a payment service, the payment service binding a fund account of the payer; a sending module configured to, in response to the payment input, associate and authorize a device account of the payment device, the fund account and an application account of the payment application, and send, according to a preset data transmission protocol of an operating system of the payment device, a first payment connection request to a payment device of a payee through the operating system of the payment device, the first payment connection request carrying the first bill, the first bill comprising a payment amount, the first payment connection request being used to request a connection with the payment device of the payee to establish a payment relationship between the payee and the payer; a payment processing module configured to, in a case where the payment device receives payment connection information sent by the payment device, determine whether the payment amount meets a preset payment condition, the preset payment condition being determined by a preset payment permission of the payment application; and in a case where the payment amount meets the preset payment condition, deduct the payment amount in the first bill from the fund account associated with and authorized by the device account of the payment device. The sending module is configured to, in response to the collection input, send, according to a preset data transmission protocol of an operating system of the collection device, a second payment connection request to a payment device of a payer through the operating system of the collection device, the second payment connection request carrying the second bill including the collection amount, the second payment connection request being used to request to establish a payment connection with the payment device and instruct the payer to deduct the collection amount from a fund account associated with and authorized by a device account of the payment device; and the collection device includes a payment application, and the payment application provides a collection service, and the collection service binds a fund account of a payer corresponding to the collection device. The association module is configured to, in a case where the payer deducts the collection amount from the fund account associated with and authorized by the device account of the payment device, associate and authorize, according to an input of the payer, the device account of the collection device, the fund account of the payer, and an application account of the payment application within a preset association time length, so as to transfer the collection amount to the fund account of the payer.

19. A payment device, characterized by The payment device is connected with a collection device of a payer, and the payment device includes: The receiving module is configured to receive a second payment connection request sent by a collection device of a payer according to a preset data transmission protocol of an operating system of the collection device through the operating system of the collection device, the second payment connection request carrying a second bill including a collection amount, the payment device including a payment application, the payment application providing a payment service, and the payment service binding a fund account of the payer. The association module is configured to associate and authorize the device account of the payment device, the fund account, and an application account of the payment application. The display module is configured to display second push information based on the second payment connection request, the second push information being used to prompt whether to establish a payment connection with the collection device. The payment processing module is configured to, in a case where an input of determining to establish a payment connection with the collection device is received, determine whether the collection amount meets a preset payment condition, the preset payment condition being determined by a preset payment permission of the payment application; and in a case where the collection amount meets the preset payment condition, deduct the collection amount from the fund account associated with and authorized by the device account of the payment device based on the second bill.

20. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer program instructions, and the computer program instructions are executed by the processor to implement the payment method in any one of claims 1 to 15.

Images