Resource Transfer Processing Method, Apparatus, Storage Medium, and Electronic Device
By using sound wave assisted communication during the scanning code payment process, transaction requests and data are sent to the backend server on the sound wave, the transaction failure problem caused by network jitter is solved, and payment success rate and user satisfaction are improved.
Patent Information
- Application Number
- CN202011248231.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-11-10
- Publication Date
- 2025-07-18
- Estimated Expiration
- 2040-11-10
AI Technical Summary
During the payment process of scanning the code, the transaction cannot be completed smoothly due to network jitter, especially when the terminal equipment of both buyers and sellers are abnormal, the existing technology is difficult to effectively solve, affecting the payment success rate and user satisfaction.
By sending transaction-related requests and data on sound waves, and transmitting transaction requests and data to the backend server using sound wave auxiliary communication method, realizing resource transfer.
It effectively reduces the phenomenon of unable to successfully complete resource transfer due to poor network environment, and improves the success rate and user satisfaction of the transaction process.
Smart Images

Figure CN114462996B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and more particularly, to a resource transfer processing method, apparatus, storage medium, and electronic device. Background Art
[0002] With the improvement of the data processing capabilities of electronic devices and the rapid development of communication technologies, it has become increasingly common for different users to conduct transactions through electronic devices. For example, when purchasing goods, users can use terminal devices to scan a code for payment to complete the transaction. During the code-scanning payment process, the terminal devices of both the buyer user and the seller user need to interact transaction information with the background server through a communication network. Frequently, due to reasons such as unstable communication networks, the code-scanning payment process between the buyer and the seller cannot be successfully completed.
[0003] Currently, during the code-scanning payment process, if the network of the buyer user's terminal device jitters and the payment code cannot be obtained and displayed, it often affects the buyer user from successfully completing the payment. At this time, although the payment can be completed relying on the pre-prepared offline payment code, however, for the security of the transaction, the payment code of the buyer user usually has a time limit. If the offline payment code has expired, the code-scanning payment process cannot be completed. Similarly, if the network of the seller user's terminal device jitters, the code-scanning payment process cannot be completed either. Summary of the Invention
[0004] To solve the technical problems existing in the related art, embodiments of this application provide a resource transfer processing method, apparatus, storage medium, and electronic device, which can effectively reduce the phenomenon that resource transfer cannot be successfully completed due to a poor network environment.
[0005] To achieve the above object, the technical solution of the embodiments of this application is implemented as follows:
[0006] In a first aspect, an embodiment of this application provides a resource transfer processing method, which is executed by a first transaction application and includes:
[0007] During the process of resource transfer, load the transaction-related request to be sent to the background server on a sound wave and send it to a second transaction application, so that the second transaction application sends the transaction-related request to the background server;
[0008] Receive the transaction-related data sent by the second transaction application through the sound wave, and complete the resource transfer according to the transaction-related data; the transaction-related data is generated by the background server based on the received transaction-related request.
[0009] In a second aspect, an embodiment of this application provides a resource transfer processing method, which is executed by a second transaction application and includes:
[0010] During the process of resource transfer, receive the transaction-related request sent by the first trading application through sound waves, and send the transaction-related request to the background server, so that the background server generates transaction-related data based on the received transaction-related request;
[0011] Receive the transaction-related data returned by the background server, and load the transaction-related data on the sound wave and send it to the first trading application, so that the first trading application completes the resource transfer according to the transaction-related data.
[0012] Thirdly, an embodiment of the present application provides a resource transfer processing device, which is applied to the first trading application and includes:
[0013] A request sending unit, configured to load the transaction-related request to be sent to the background server on the sound wave and send it to the second trading application during the process of resource transfer, so that the second trading application sends the transaction-related request to the background server;
[0014] A data receiving unit, configured to receive the transaction-related data sent by the second trading application through the sound wave, and complete the resource transfer according to the transaction-related data; the transaction-related data is generated by the background server based on the received transaction-related request.
[0015] In an optional embodiment, the request sending unit is specifically configured to:
[0016] If network abnormality is detected, load the transaction-related request on the sound wave and send it to the second trading application; or,
[0017] Send the transaction-related request to the background server, and load the transaction-related request on the sound wave and send it to the second trading application.
[0018] In an optional embodiment, the request sending unit is specifically configured to:
[0019] Send a network test request to the background server at intervals of a set duration. If no response message is received from the background server within a preset duration after sending the network test request, it is confirmed that network abnormality is detected; or,
[0020] Send the transaction-related request to the background server. If no transaction-related data is received from the background server within a preset duration, it is confirmed that network abnormality is detected.
[0021] Fourthly, an embodiment of the present application provides a resource transfer processing device, which is applied to the second trading application and includes:
[0022] A request receiving unit, configured to receive a transaction-related request sent by a first transaction application via sound waves during the process of resource transfer, and send the transaction-related request to a background server, so that the background server generates transaction-related data based on the received transaction-related request;
[0023] A data sending unit, configured to receive the transaction-related data returned by the background server, and load the transaction-related data on sound waves and send it to the first transaction application, so that the first transaction application completes resource transfer according to the transaction-related data.
[0024] In an optional embodiment, the first transaction application is a transaction application associated with a resource receiving account, and the second transaction application is a transaction application associated with a resource payment account; or, the first transaction application is a transaction application associated with a resource payment account, and the second transaction application is a transaction application within the sound wave sending range of the first transaction application; the request receiving unit is specifically configured to:
[0025] Receive a resource transfer request sent by the first transaction application via a third sound wave, and send the resource transfer request to the background server according to the address information of the background server in the third sound wave; the resource transfer request carries the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer;
[0026] The data sending unit is specifically configured to:
[0027] Receive the resource transfer result data returned by the background server, and load the resource transfer result data on a fourth sound wave and send it to the first transaction application; the resource transfer result data is generated by the background server based on the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer in the received resource transfer request.
[0028] In a fifth aspect, an embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, it implements the resource transfer processing method in the first aspect.
[0029] In a sixth aspect, an embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, it implements the resource transfer processing method in the second aspect.
[0030] In a seventh aspect, an embodiment of the present application further provides an electronic device, including a memory and a processor. A computer program that can run on the processor is stored on the memory. When the computer program is executed by the processor, the processor implements the resource transfer processing method of the first aspect.
[0031] In an eighth aspect, an embodiment of the present application further provides an electronic device, including a memory and a processor. A computer program that can run on the processor is stored on the memory. When the computer program is executed by the processor, the processor implements the resource transfer processing method of the second aspect.
[0032] In the resource transfer processing method, device, storage medium, and electronic device according to the embodiments of the present application, during the process of resource transfer, a transaction-related request that needs to be sent to the background server is loaded on a sound wave and sent to a second transaction application, so that the second transaction application sends the transaction-related request to the background server, and receives the transaction-related data sent by the second transaction application through the sound wave, and completes the resource transfer according to the transaction-related data. By completing the resource transfer through the method of assisted communication by sound wave, the phenomenon that the resource transfer cannot be successfully completed due to a poor network environment can be effectively reduced, and the success rate of the resource transfer process can be improved. BRIEF DESCRIPTION OF THE DRAWINGS
[0033] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the following drawings are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.
[0034] Figure 1 It is a schematic diagram of an application scenario of a resource transfer processing method provided by an embodiment of the present application;
[0035] Figure 2 It is an interaction diagram of a resource transfer processing method provided by an embodiment of the present application;
[0036] Figure 3 It is an interaction diagram of another resource transfer processing method provided by an embodiment of the present application;
[0037] Figure 4 It is an interaction diagram of another resource transfer processing method provided by an embodiment of the present application;
[0038] Figure 5 It is an interaction diagram of another resource transfer processing method provided by an embodiment of the present application;
[0039] Figure 6 It is a schematic diagram of the system architecture of a code scanning payment system provided by an embodiment of the present application;
[0040] Figure 7 A schematic diagram of a payment interface provided by an embodiment of the present application;
[0041] Figure 8 Another schematic diagram of a payment interface provided by an embodiment of the present application;
[0042] Figure 9 Another schematic diagram of a payment interface provided by an embodiment of the present application;
[0043] Figure 10 Another schematic diagram of a payment interface provided by an embodiment of the present application;
[0044] Figure 11 A schematic flowchart of a resource transfer processing method provided by an embodiment of the present application;
[0045] Figure 12 Another schematic flowchart of a resource transfer processing method provided by an embodiment of the present application;
[0046] Figure 13 A structural block diagram of a resource transfer processing device provided by an embodiment of the present application;
[0047] Figure 14 Another structural block diagram of a resource transfer processing device provided by an embodiment of the present application;
[0048] Figure 15 A schematic diagram of the structure of an electronic device provided by an embodiment of the present application;
[0049] Figure 16 Another schematic diagram of the structure of an electronic device provided by an embodiment of the present application. Detailed implementation manners
[0050] In order to make the objectives, technical solutions, and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without making creative efforts shall fall within the protection scope of the present application.
[0051] It should be noted that the terms "including" and "having" and their variants involved in the documents of the present application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device including a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products, or devices.
[0052] The following explains some terms in the embodiments of the present application to facilitate the understanding of those skilled in the art.
[0053] (1) Payment code: In the process of conducting transactions or resource transfers through mobile payment, the relevant information of the transaction can be carried and displayed in a readable graphic identifier, which can be referred to as a payment code. For example, the account information of the resource payment account or the resource receiving account can be written into their respective corresponding payment codes. The payment code can be a barcode or a two-dimensional code. Among them, the two-dimensional code uses certain specific geometric figures to distribute black and white patterns in a two-dimensional plane direction according to a certain rule to record alphanumeric information. In the code compilation, the concept of the "0" and "1" bit stream that constitutes the internal logic basis of the computer is utilized, and several geometric figures corresponding to binary are used to represent alphanumeric information. Scanning the payment code through an image acquisition component or an optoelectronic scanning component can automatically identify the information in the payment code.
[0054] (2) Acoustic wave communication: A short-distance communication method that transmits data through high-frequency acoustic waves of about 20KHz. Acoustic wave communication utilizes the sending end to play acoustic waves containing data information, and the receiving end collects the acoustic waves and analyzes the transmitted data information for communication. For example, the sending end can represent 0 and 1 respectively by sending one of two adjacent frequencies. The sending end sends the acoustic wave obtained by encoding the data information through FFT (Fast Fourier Transform), and the receiving end analyzes the received acoustic wave through FFT to obtain the data information in the acoustic wave.
[0055] The term "exemplary" used hereinafter means "serving as an example, embodiment, or illustration". Any embodiment described as "exemplary" does not have to be construed as superior to or better than other embodiments.
[0056] The terms "first" and "second" in the text are only used for descriptive purposes and cannot be construed as explicitly or implicitly indicating relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first" and "second" may explicitly or implicitly include one or more of such features. In the description of the embodiments of the present application, unless otherwise specified, the meaning of "a plurality" is two or more.
[0057] To better understand the technical solutions provided by the embodiments of the present application, the following briefly introduces the application scenarios applicable to the technical solutions provided by the embodiments of the present application. It should be noted that the application scenarios introduced below are only used to illustrate the embodiments of the present application and are not limiting. In specific implementations, the technical solutions provided by the embodiments of the present application can be flexibly applied according to actual needs.
[0058] Figure 1 shows an application scenario of the resource transfer processing method provided by the embodiments of the present application. Refer to Figure 1 As shown, in this application scenario, it includes a first terminal device 100, a second terminal device 200, a first back-end server 300, and a second back-end server 400. The first terminal device 100 and the first back-end server 300, and the second terminal device 200 and the second back-end server 400 can be communicatively connected through a communication network 500 to transmit data. The communication network can be a wired network or a wireless network. For example, the first terminal device 100 and the first back-end server 300 can transmit data through a cellular data network or a WiFi wireless network; the second terminal device 200 and the second back-end server 400 can also transmit data through a cellular data network or a WiFi wireless network. The first terminal device 100 and the second terminal device 200 can transmit data through sound waves.
[0059] Among them, the first terminal device 100 can be a mobile terminal such as a mobile phone, a personal digital assistant (PDA), a tablet computer, a smart wearable device (such as a smart watch and a smart helmet), etc. The second terminal device 200 can be a scanning machine terminal, or a mobile terminal such as a mobile phone, a personal digital assistant, a tablet computer, a smart wearable device, etc. The first back-end server 300 and the second back-end server 400 can be a single server, or a server cluster or a cloud computing center composed of several servers, or a virtualization platform, or a personal computer, a mainframe computer, or a computer cluster, etc.
[0060] In the application scenario provided by the embodiments of the present application, a first transaction application is installed on the first terminal device 100. The first back-end server 300 can be a server that provides back-end support for the first transaction application. The number of first terminal devices 100 connected to the first back-end server 300 can be one or more. A second transaction application is installed on the second terminal device 200. The second back-end server 400 can be a server that provides back-end support for the second transaction application. The number of second terminal devices 200 connected to the second back-end server 400 can be one or more.
[0061] For example, the first terminal device 100 may be a mobile phone, on which a first transaction application is installed. The first backend server 300 is used to provide payment and collection services for the first transaction application. After the first user logs in to the first transaction application using the first account, during the process of making a payment using the first transaction application, the first account can be understood as a resource payment account. The first terminal device 100 displays a payment code of the resource payment account obtained from the first backend server 300 to complete the payment. The second terminal device 200 may be a scanning machine terminal with an optoelectronic scanning component. A second transaction application with a collection function is installed on the scanning machine terminal for resource reception. The second backend server 400 is used to provide collection and accounting services for the second transaction application. The second transaction application is bound to the second account of the second user. During the process of realizing collection using the second transaction application, the optoelectronic scanning component of the scanning machine terminal scans the payment code of the resource payment account, obtains the account information of the resource payment account, and sends a payment request to the second backend server 400 to complete the collection. The above transaction process of making a payment and receiving a payment and the interaction process of each device during this process will be described in detail below.
[0062] In the embodiments of the present application, both the first terminal device and the second terminal device are equipped with acoustic wave communication components. The acoustic wave communication components may include an acoustic wave transmitting component and an acoustic wave receiving component. In a resource transfer scenario, acoustic wave communication can be used to assist in resource transfer. Among them, the resource transfer may specifically be a code scanning payment process. The embodiments of the present application will be described by taking the code scanning payment as an example.
[0063] Currently, during the code scanning payment process, if the terminal device of the buyer user experiences network jitter and cannot obtain and display the payment code, it often affects the buyer user from successfully completing the payment. At this time, although the payment can be completed by relying on the pre-prepared offline payment code, however, for the security of the transaction, the payment code of the buyer user usually has a time limit. If the offline payment code has expired, the code scanning payment process cannot be completed. Similarly, if the terminal device of the seller user experiences network jitter, the code scanning payment process cannot be completed either.
[0064] To solve the technical problems existing in the related art, the embodiments of the present application provide a resource transfer processing method, device, storage medium, and electronic device. During the process of resource transfer, a transaction-related request to be sent to the backend server is loaded on an acoustic wave and sent to the second transaction application, so that the second transaction application sends the transaction-related request to the backend server. By receiving the transaction-related data sent by the second transaction application through the acoustic wave and completing the resource transfer according to the transaction-related data. Completing the resource transfer through the acoustic wave-assisted communication method can effectively reduce the occurrence of the phenomenon that the resource transfer cannot be successfully completed due to a poor network environment, improve the success rate of the resource transfer process, and enhance the overall payment satisfaction.
[0065] In an embodiment of the present application, the code scanning payment is implemented through the interaction process among the first terminal device, the second terminal device, the first background server, and the second background server. In this embodiment, the first transaction application installed on the first terminal device is a transaction application associated with the resource payment account, and the second transaction application installed on the second terminal device is a transaction application associated with the resource receiving account. Among them, the first terminal device may be a mobile terminal such as a mobile phone of the buyer user, and the second terminal device may be a code scanning machine terminal of the seller user or a device such as a mobile phone. This interaction process may be as follows Figure 2 shown and includes the following steps:
[0066] Step S201, the second terminal device receives the transaction amount input by the seller user and enters the code scanning state.
[0067] Among them, the seller user may also be referred to as a merchant. The merchant opens the second transaction application on the second terminal device, and this second transaction application is associated or bound to the merchant's resource receiving account. If the second terminal device is a code scanning machine terminal, the second transaction application can be understood as a software system installed on the code scanning machine terminal that can realize the collection function through code scanning. The merchant inputs the transaction amount for code scanning payment, which can also be referred to as the collection amount here. The second terminal device receives the collection amount input by the merchant, starts the image acquisition component or the optoelectronic scanning component, and enters the code scanning state.
[0068] Step S202, the second terminal device starts the sound wave receiving function.
[0069] The second transaction application on the second terminal device may start the sound wave receiving function while entering the code scanning state, or may start the sound wave receiving function after a preset time interval from the moment of entering the code scanning state.
[0070] Specifically, the second transaction application starts the sound wave receiving function by opening the sound wave receiving component. Among them, the sound wave receiving component may be, but is not limited to, a microphone.
[0071] Step S203, the first terminal device receives the payment code generation operation input by the buyer user.
[0072] Specifically, the buyer user opens the first transaction application on the first terminal device, logs in to the first transaction application through the resource payment account, and after entering the payment interface as shown in Figure 7 , can click the button for generating the payment code to trigger the payment code generation operation.
[0073] Step S204, the first terminal device sends a payment code acquisition request to the first background server.
[0074] The first transaction application on the first terminal device receives a payment code generation operation input by the buyer user and sends a payment code acquisition request to the first background server through the communication network. Among them, the account information of the resource payment account is carried in the payment code acquisition request. The account information of the resource payment account can be the account number or other account identification information that uniquely identifies the account.
[0075] For the security of the transaction, the first terminal device can encrypt the payment code acquisition request once and then send it to the first background server. The encryption method for the single encryption is the encryption method agreed upon by the first transaction application and the first background server that provides services for it. After receiving the payment code acquisition request sent by the first terminal device, the first background server can decrypt it according to the single encryption method to obtain the account information of the resource payment account therein.
[0076] Step S205: If the first terminal device does not receive the payment code data within the preset first time period, it loads the payment code acquisition request and the address information of the first background server on the first sound wave.
[0077] Specifically, as Figure 8 shown, if the first transaction application on the first terminal device does not receive the payment code data returned by the first background server within the preset first time period and the waiting state is always displayed on the payment interface, it is considered that the network is abnormal. The first transaction application loads the payment code acquisition request and the address information of the first background server on the first sound wave. Among them, the address information of the first background server can be the IP address of the first background server.
[0078] Optionally, the first transaction application can encrypt the once-encrypted payment code acquisition request and the address information of the first background server a second time, and then load them on the first sound wave through sound wave encoding. The encryption method for the second encryption is the encryption method agreed upon by the first transaction application and the second transaction application.
[0079] Step S206: The first terminal device sends the first sound wave to the second terminal device.
[0080] When starting the first transaction application on the first terminal device, if the user authorizes the first transaction application to use the sound wave emission component of the first terminal device, the first transaction application can start the sound wave emission component through the hardware call interface in the operating system and send the first sound wave to the second terminal device through the sound wave emission component. Among them, the sound wave emission component can be, but is not limited to, a speaker.
[0081] In some embodiments, before the first terminal device sends the first sound wave to the second terminal device, it may not perform the above-mentioned step S204, and monitor whether the network is abnormal in the following manner: The first terminal device may send a network test request to the first background server at intervals of a set duration. After receiving the network test request sent by the first terminal device, the first background server returns a response message to the first terminal device. If the first terminal device does not receive the response message returned by the first background server within a preset first duration after sending the network test request, it is confirmed that the network is abnormal. The first terminal device loads the payment code acquisition request and the address information of the first background server on the first sound wave, and sends the first sound wave to the second terminal device.
[0082] Step S207, the second terminal device acquires the address information of the first background server and the payment code acquisition request in the received first sound wave.
[0083] Optionally, when the second transaction application on the second terminal device receives the first sound wave sent by the first terminal device, it can decrypt the data carried by the first sound wave according to the encryption method of secondary encryption to obtain the address information of the first background server and the payment code acquisition request. However, the second transaction application cannot decrypt the payment code acquisition request, so it cannot obtain the account information of the resource payment account in the payment code acquisition request, which can prevent the leakage of the account information of the resource payment account.
[0084] Step S208, the second terminal device sends a payment code acquisition request to the first background server.
[0085] The second transaction application on the second terminal device determines the background server according to the acquired address information of the first background server. After determining that the background server that needs to send the payment code acquisition request is the first background server, it sends the payment code acquisition request to the first background server through the communication network. The communication network can be a cellular data network or a WiFi wireless network.
[0086] Step S209, the first background server generates payment code data.
[0087] The first background server receives the payment code acquisition request sent by the second terminal device, decrypts it according to the encryption method of primary encryption to obtain the account information of the resource payment account therein, generates the payment code data corresponding to the resource payment account according to the account information of the resource payment account, and encrypts the payment code data by using the encryption method of primary encryption.
[0088] Step S210, the first background server sends the payment code data to the second terminal device.
[0089] The first back-end server returns the encrypted payment code data to the second transaction application of the second terminal device.
[0090] Step S211, the second terminal device loads the received payment code data onto the second sound wave.
[0091] The second transaction application on the second terminal device receives the payment code data returned by the back-end server, encodes the received payment code data by sound wave and loads it onto the second sound wave.
[0092] Step S212, the second terminal device sends the second sound wave to the first terminal device.
[0093] The second transaction application can send the second sound wave to the first terminal device through the sound wave transmitting component of the second terminal device.
[0094] Step S213, the first terminal device displays the payment code according to the payment code data in the received second sound wave.
[0095] The first transaction application on the first terminal device decodes the second sound wave received by the sound wave receiving component of the first terminal device to obtain the payment code data in the second sound wave, decrypts the payment code data according to the encryption method of one-time encryption, and displays the payment code generated according to the payment code data in the payment interface, as Figure 9 shown. This payment code can be understood as a payment code, which can be a two-dimensional code or other computer-readable codes, and contains the account information of the resource payment account.
[0096] Step S214, the second terminal device generates a payment request according to the scanned payment code.
[0097] The second terminal device scans the payment code displayed on the first terminal device through the image acquisition component or the optoelectronic scanning component. The second transaction application identifies the scanned payment code, obtains the account information of the resource payment account therein, and generates a payment request according to the account information of the resource payment account, the account information of the resource receiving account and the transaction information of this resource transfer. The payment request can also be called a resource transfer request. Among them, the account information of the resource payment account is obtained from the scanned payment code, and the resource receiving account is the account associated with the second transaction application, so the second transaction application can obtain its account information; the transaction information of this resource transfer includes the transaction code used to uniquely identify this transaction and the transaction amount input by the seller user in step S201. The payment request generated by the second transaction application adopts the first specified format agreed upon by the second transaction application and the second back-end server.
[0098] Step S215, the second terminal device sends the payment request to the second back-end server.
[0099] Step S216: The second back-end server generates a deduction request according to the received payment request.
[0100] The second back-end server is a server that provides services for the second trading application. The second back-end server first verifies the received payment request sent by the second terminal device. If the received payment request conforms to the agreed first specified format, the verification passes. The second back-end server generates a deduction request based on the account information of the resource payment account and the transaction amount in the payment request. The deduction request adopts the second specified format agreed upon by the first back-end server and the second back-end server.
[0101] Step S217: The second back-end server sends the deduction request to the first back-end server.
[0102] Step S218: The first back-end server makes a deduction according to the deduction request.
[0103] Specifically, after receiving the deduction request sent by the second back-end server, the first back-end server verifies the deduction request. If the received deduction request conforms to the agreed second specified format, the verification passes. The first back-end server deducts the amount corresponding to the transaction from the resource payment account according to the account information of the resource payment account in the deduction request.
[0104] In some embodiments, the first back-end server also verifies the deduction request according to other conditions in addition to the predetermined format. The present application does not specifically limit the specific verification method.
[0105] Step S219: If the first back-end server determines that the deduction is successful, it generates a payment result notification and a deduction result notification.
[0106] Specifically, if it is determined that the deduction is successful, the first back-end server generates resource transfer result data, which includes a payment result notification and a deduction result notification. Among them, the payment result notification is used to be provided to the second terminal device of the second trading application associated with the resource receiving account, and the deduction result notification is used to be provided to the first terminal device of the first trading application associated with the resource payment account.
[0107] Step S220: The first back-end server sends the payment result notification to the second back-end server.
[0108] For the payment result notification, the first back-end server first provides it to the second back-end server. The second back-end server adds the amount corresponding to the transaction to the resource receiving account according to the payment result notification and sends the payment result notification to the second terminal device.
[0109] Step S221: The second back-end server sends the payment result notification to the second terminal device.
[0110] Optionally, the second terminal device may display the payment result according to the received payment result notification.
[0111] Step S222, the first back-end server sends a deduction result notification to the first terminal device.
[0112] Optionally, the first terminal device may display the deduction result according to the received deduction result notification. For Figure 10 example, it may display the information indicating successful deduction and the deduction amount.
[0113] In the above embodiments, during the code scanning payment process, if the terminal device experiences network jitter, the transaction process can be completed through the acoustic wave assisted communication method, which can effectively reduce the occurrence of the phenomenon that the transaction cannot be successfully completed due to a poor network environment, improve the success rate of the transaction process, and enhance the user's satisfaction with code scanning payment.
[0114] In another embodiment of the present application, the code scanning payment process is implemented through the interaction process between the first terminal device, the second terminal device, the first back-end server, and the second back-end server. In this embodiment, the first transaction application installed on the first terminal device is a transaction application associated with the resource receiving account, and the second transaction application installed on the second terminal device is a transaction application associated with the resource payment account. The interaction process may be as Figure 3 shown and includes the following steps:
[0115] Step S301, the first terminal device receives the transaction amount input by the seller user and enters the code scanning state.
[0116] Step S302, the first terminal device activates the acoustic wave receiving function.
[0117] Step S303, the second terminal device receives the payment code generation operation input by the buyer user.
[0118] Specifically, the buyer user opens the second transaction application on the second terminal device, logs in to the second transaction application through the resource payment account, and may click the button to generate the payment code to trigger the payment code generation operation.
[0119] Step S304, the second terminal device sends a payment code acquisition request to the second back-end server.
[0120] The second transaction application on the second terminal device receives the payment code generation operation input by the buyer user and sends a payment code acquisition request to the second back-end server. Among them, the payment code acquisition request carries the account information of the resource payment account. The account information of the resource payment account may be the account number or other account identification information that uniquely identifies the account.
[0121] Step S305: The second back-end server generates payment code data according to the received payment code acquisition request.
[0122] Among them, the payment code data is generated by the back-end server based on the account information of the resource payment account in the received payment code acquisition request.
[0123] Step S306: The second back-end server sends the payment code data to the second terminal device.
[0124] Specifically, in the embodiment of the present application, the second back-end server sends the generated payment code data to the second transaction application.
[0125] Step S307: The second terminal device displays the payment code according to the received payment code data.
[0126] Step S308: The first terminal device generates a payment request according to the scanned payment code.
[0127] The first terminal device generates a resource transfer request according to the scanned payment code. The resource transfer request carries the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer. In this embodiment, the resource transfer request is a payment request.
[0128] Specifically, the first terminal device scans the payment code displayed on the second terminal device through an image acquisition component or an optoelectronic scanning component. The first transaction application identifies the scanned payment code, obtains the account information of the resource payment account therein, and generates a payment request according to the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer. Among them, the account information of the resource payment account is obtained from the scanned payment code, and the resource receiving account is the account associated with the first transaction application. Therefore, the first transaction application can obtain its account information; the transaction information of this resource transfer includes a transaction code for uniquely identifying this transaction and the transaction amount input by the seller user in step S301. The payment request generated by the first transaction application adopts a third specified format agreed upon by the first transaction application and the first back-end server.
[0129] For the security of the transaction, the first transaction application can encrypt the payment request once and then send it to the first back-end server. The encryption method for the once encryption is the encryption method agreed upon by the first transaction application and the first back-end server that provides services for it. The first back-end server can decrypt the payment request sent by the first transaction application according to the encryption method for the once encryption to obtain the transaction information therein.
[0130] Step S309: The first terminal device sends the payment request to the first back-end server.
[0131] Step S310, if the first terminal device determines that it has not received a payment result notification for more than a preset second duration, it will load the payment request generated based on the scanned payment code and the address information of the first backend server on the third sound wave.
[0132] In some embodiments, if the first terminal device determines that it has not received a payment result notification for more than a preset second time threshold, it determines that a network anomaly is detected. If a network anomaly is detected, the first terminal device will load the payment request generated based on the scanned payment code and the address information of the first backend server on the third sound wave and send it to the second transaction application.
[0133] Specifically, if the first transaction application on the first terminal device has not received a payment result notification returned by the first backend server for more than a preset second duration and the waiting state is continuously displayed on the payment collection interface, it is considered that there is a network anomaly. The first transaction application will load the payment request generated based on the scanned payment code and the address information of the first backend server on the third sound wave. Among them, the address information of the first backend server may be the IP address of the first backend server.
[0134] Optionally, the first transaction application may perform secondary encryption on the once-encrypted payment request and the address information of the first backend server, and then load it on the third sound wave through sound wave encoding. The encryption method for secondary encryption is the encryption method agreed upon by the first transaction application and the second transaction application.
[0135] Step S311, the first terminal device sends the third sound wave to the second terminal device.
[0136] When starting the first transaction application on the first terminal device, if the merchant authorizes the first transaction application to use the sound wave emission component of the first terminal device, the first transaction application may start the sound wave emission component through the hardware call interface in the operating system and send the first sound wave to the second terminal device through the sound wave emission component. Among them, the sound wave emission component may be, but is not limited to, a speaker.
[0137] In some embodiments, before the first terminal device sends the first sound wave to the second terminal device, it may not perform the above-mentioned step S309 and monitor whether there is a network anomaly in the following manner: The first terminal device may send a network test request to the first backend server at intervals of a set duration. After receiving the network test request sent by the first terminal device, the first backend server returns a response message to the first terminal device. If the first terminal device does not receive the response message returned by the first backend server within a preset second duration after sending the network test request, it confirms that a network anomaly is detected. The first terminal device will load the payment request generated based on the scanned payment code and the address information of the first backend server on the third sound wave and send the third sound wave to the second terminal device.
[0138] Step S312: The second terminal device obtains the payment request and the address information of the first back-end server from the received third sound wave.
[0139] Optionally, when the second transaction application on the second terminal device receives the third sound wave sent by the first terminal device, it can decrypt the data carried by the third sound wave according to the encryption method of secondary encryption to obtain the address information of the first back-end server and the payment request. However, the second transaction application cannot decrypt the payment request, so it cannot obtain the transaction information in the payment request.
[0140] Step S313: The second terminal device sends the payment request according to the address information of the first back-end server.
[0141] The second transaction application on the second terminal device determines the back-end server according to the obtained address information of the first back-end server. After determining that the back-end server that needs to send the payment request is the first back-end server, it sends the payment request to the first back-end server.
[0142] Step S314: The first back-end server generates a deduction request according to the received payment request.
[0143] The first back-end server is the server that provides services for the first transaction application. The first back-end server first verifies the received payment request. If the received payment request conforms to the agreed third specified format, the verification passes. The first back-end server generates a deduction request according to the account information of the resource payment account and the transaction amount in the payment request. The deduction request adopts the fourth specified format agreed upon by the first back-end server and the second back-end server.
[0144] Step S315: The first back-end server sends the deduction request to the second back-end server.
[0145] Step S316: The second back-end server makes a deduction according to the deduction request.
[0146] Specifically, after the second back-end server receives the deduction request sent by the first back-end server, it verifies the deduction request. If the received deduction request conforms to the agreed fourth specified format, the verification passes. The second back-end server deducts the amount corresponding to the transaction from the resource payment account according to the account information of the resource payment account in the deduction request. In some embodiments, the second back-end server also verifies the deduction request according to other conditions in addition to the predetermined format. This application does not make specific limitations on the specific verification method.
[0147] Step S317: If the second back-end server determines that the deduction is successful, it generates a payment result notification and a deduction result notification.
[0148] Specifically, if it is determined that the deduction is successful, the second back-end server generates resource transfer result data, which includes a payment result notification and a deduction result notification. Among them, the payment result notification is used to be provided to the first terminal device installed with the first transaction application associated with the resource receiving account, and the deduction result notification is used to be provided to the second terminal device installed with the second transaction application associated with the resource payment account.
[0149] Step S318, the second back-end server sends the payment result notification to the first back-end server.
[0150] Regarding the payment result notification, the second back-end server first provides it to the first back-end server. The first back-end server adds the amount corresponding to the transaction to the resource receiving account according to the payment result notification, and sends the payment result notification to the first terminal device.
[0151] Step S319, the first back-end server sends the payment result notification to the second terminal device.
[0152] Step S320, the second terminal device loads the received payment result notification on the fourth sound wave.
[0153] Specifically, the second terminal device loads the received payment result notification on the fourth sound wave to generate payment result notification sound wave information.
[0154] Step S321, the second terminal device sends the fourth sound wave to the first terminal device.
[0155] Specifically, the second terminal device sends the payment result notification sound wave information through the fourth sound wave.
[0156] Step S322, the first terminal device obtains the payment result notification from the received fourth sound wave.
[0157] Optionally, the first terminal device can also display the payment result according to the received payment result notification.
[0158] Step S323, the second back-end server sends the deduction result notification to the second terminal device.
[0159] Optionally, the second terminal device can display the deduction result according to the received deduction result notification. The deduction result notification can simultaneously display the notification of successful deduction and the deduction amount.
[0160] In the above embodiment, during the code scanning payment process, if the terminal device of the seller user has network jitter, the transaction process can be completed through the way of acoustic wave assisted communication, which can effectively reduce the phenomenon that the transaction cannot be successfully completed due to poor network environment, improve the success rate of the transaction process, and enhance the user's satisfaction with the code scanning payment.
[0161] In an embodiment of the present application, the code scanning payment is implemented through the interaction process among the first terminal device, the second terminal device, the first background server, and the second background server. In this embodiment, the first transaction application installed on the first terminal device is the transaction application associated with the resource payment account, and the second transaction application installed on the second terminal device is the transaction application associated with the resource receiving account. The interaction process may be as follows Figure 4 shown, including the following steps:
[0162] Step S401, the second terminal device receives the transaction amount input by the seller user and enters the code scanning state.
[0163] Step S402, the second terminal device activates the sound wave receiving function.
[0164] Step S403, the first terminal device receives the payment code generation operation input by the buyer user.
[0165] Step S404, the first terminal device sends a payment code acquisition request to the first background server.
[0166] Step S405, the first terminal device loads the payment code acquisition request and the address information of the first background server on the first sound wave.
[0167] Specifically, after the first terminal device sends the payment code acquisition request to the first background server, without making any judgment, it directly loads the payment code acquisition request and the address information of the first background server on the first sound wave.
[0168] Step S406, the first terminal device sends the first sound wave to the second terminal device.
[0169] Step S407, the second terminal device acquires the address information of the first background server and the payment code acquisition request in the received first sound wave.
[0170] Step S408, the second terminal device sends a payment code acquisition request to the first background server.
[0171] Step S409, the first background server generates payment code data according to the first received payment code acquisition request.
[0172] Specifically, the first background server generates payment code data, which is generated by the first background server based on the account information of the resource payment account in the first received payment code acquisition request. The received payment code acquisition request may be generated based on the payment code acquisition request in step S404, or may be generated based on the payment code acquisition request in step S408. In Figure 4 the shown step S409, it is assumed that the first background server receives the payment code acquisition request sent by the second terminal device in step S408.
[0173] Step S410, the first backend server sends payment code data to the second terminal device.
[0174] Step S411, the second terminal device loads the received payment code data onto the second sound wave.
[0175] Step S412, the second terminal device sends the second sound wave to the first terminal device.
[0176] Step S413, the first terminal device displays the payment code according to the payment code data in the received second sound wave.
[0177] In some other embodiments, the first backend server may generate payment code data for the received payment code acquisition request and send it to the corresponding terminal device. For example, the first backend server receives the payment code acquisition request sent by the first terminal device in step S404, generates payment code data and sends it to the first terminal device. The first backend server also receives the payment code acquisition request sent by the second terminal device in step S408, generates payment code data and sends it to the second terminal device. The second terminal device then sends the payment code data to the first terminal device through sound waves. The first terminal device can display the payment code according to the payment code data received any time, and this transaction can be completed.
[0178] Step S414, the second terminal device generates a payment request according to the scanned payment code.
[0179] Step S415, the second terminal device sends the payment request to the second backend server.
[0180] Step S416, the second backend server generates a deduction request according to the received payment request.
[0181] Step S417, the second backend server sends the deduction request to the first backend server.
[0182] Step S418, the first backend server makes a deduction according to the deduction request.
[0183] Step S419, if the first backend server determines that the deduction is successful, it generates a payment result notification and a deduction result notification.
[0184] Step S420, the first backend server sends the payment result notification to the second backend server.
[0185] Step S421, the second backend server sends the payment result notification to the second terminal device.
[0186] Step S422, the first backend server sends the deduction result notification to the first terminal device.
[0187] The interaction process between the first backend server and the second backend server in steps S416 to S422 can be referred to Figure 2 the execution of steps S216 to S222 in
[0188] In the above-mentioned embodiment during the QR code payment process, the terminal device of the buyer user can simultaneously use the traditional data network method and the acoustic wave-assisted communication method to complete the transaction process, which can effectively reduce the occurrence of the phenomenon that the transaction cannot be successfully completed due to a poor network environment, improve the success rate of the transaction process, and enhance the user's satisfaction with QR code payment.
[0189] In an embodiment of the present application, the QR code payment process is implemented through the interaction process between the first terminal device, the second terminal device, the first backend server, and the second backend server. In this embodiment, the first transaction application installed on the first terminal device is the transaction application associated with the resource receiving account, and the second transaction application installed on the second terminal device is the transaction application associated with the resource payment account. This interaction process can be as Figure 5 shown and includes the following steps:
[0190] Step S501, the first terminal device receives the transaction amount input by the seller user and enters the QR code scanning state.
[0191] Among them, the seller user can also be referred to as a merchant. The merchant inputs the transaction amount for QR code payment, which can also be referred to as the received amount here. The second terminal device receives the received amount input by the merchant, activates the image acquisition component or the optoelectronic scanning component, and enters the QR code scanning state.
[0192] Step S502, the first terminal device activates the acoustic wave receiving function.
[0193] Specifically, the first terminal device can activate the acoustic wave receiving function simultaneously when entering the QR code scanning state, or can activate the acoustic wave receiving function after a preset time interval from the moment of entering the QR code scanning state.
[0194] Step S503, the second terminal device receives the payment code generation operation input by the buyer user.
[0195] Specifically, the buyer user opens the second transaction application on the second terminal device, logs in to the second transaction application through the resource payment account, and can click the button for generating the payment code to trigger the payment code generation operation.
[0196] Step S504, the second terminal device sends a payment code acquisition request to the second backend server.
[0197] Among them, the payment code acquisition request carries the account information of the resource payment account.
[0198] Step S505: The second back-end server generates payment code data according to the received payment code acquisition request.
[0199] Among them, the payment code data is generated by the back-end server based on the account information of the resource payment account in the received payment code acquisition request.
[0200] Step S506: The second back-end server sends the payment code data to the second terminal device.
[0201] Specifically, in the embodiment of the present application, the second back-end server sends the generated payment code data to the second transaction application. In this embodiment, the second transaction application is the transaction application associated with the resource payment account.
[0202] Step S507: The second terminal device displays the payment code according to the received payment code data.
[0203] Step S508: The first terminal device generates a payment request according to the scanned payment code.
[0204] In order to complete the scan code payment according to the payment code displayed by the second terminal device, the first terminal device scans the displayed payment code and generates a resource transfer request according to the scanned payment code. The resource transfer request carries the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer. The transaction information of this resource transfer includes identification information for uniquely identifying this resource transfer. In this embodiment, the resource transfer request is a payment request.
[0205] Step S509: The first terminal device sends the payment request to the first back-end server.
[0206] Step S510: The first terminal device loads the payment request generated according to the scanned payment code and the address information of the first back-end server on the third sound wave.
[0207] Step S511: The first terminal device sends the third sound wave to the second terminal device.
[0208] Specifically, in this embodiment, the first terminal device does not judge whether the network is abnormal, but directly loads the payment request generated according to the scanned payment code and the address information of the first back-end server on the third sound wave and sends it to the second terminal device.
[0209] Step S512: The second terminal device obtains the payment request and the address information of the first back-end server from the received third sound wave.
[0210] Specifically, the second terminal device receives the third sound wave and obtains the third sound wave information in the third sound wave, thereby obtaining the payment request and the address information of the first back-end server in the third sound wave.
[0211] Step S513, the second terminal device sends a payment request to the first back-end server according to the address information of the first back-end server.
[0212] Step S514, the first back-end server generates a deduction request according to the received payment request first.
[0213] Assume that the first back-end server can receive the payment request sent by the first terminal device in step S509 and can also receive the payment request sent by the second terminal device in step S513. These two payment requests have the same resource transfer identification information. The first back-end server generates a deduction request according to the received payment request first.
[0214] Specifically, in order to avoid duplicate deductions, when receiving a payment request, the first back-end server can judge whether it has ever received the resource transfer request according to the identification information of this resource transfer in the payment request. If it has ever received it, the payment request is ignored. If not, it means that this is the first time to receive this payment request, and then it deducts money from the resource payment account according to this resource transfer request. Assume that the first back-end server first receives the payment request sent by the second terminal device in step S513, and the first back-end server generates a deduction request according to this payment request.
[0215] Step S515, the first back-end server sends a deduction request to the second back-end server.
[0216] Step S516, the second back-end server makes a deduction according to the deduction request.
[0217] Step S517, if the second back-end server judges that the deduction is successful, it generates a payment result notification and a deduction result notification.
[0218] Step S518, the second back-end server sends a payment result notification to the first back-end server.
[0219] Step S519, the first back-end server sends a payment result notification to the second terminal device.
[0220] Step S520, the second terminal device loads the received payment result notification on the fourth sound wave.
[0221] Step S521, the second terminal device sends the fourth sound wave to the first terminal device.
[0222] Step S522, the first terminal device obtains the payment result notification from the received fourth sound wave.
[0223] Specifically, the second terminal device sends a fourth sound wave to the first terminal device, and the first terminal device obtains a payment result notification from the received fourth sound wave.
[0224] Step S523, the second back-end server sends a deduction result notification to the second terminal device.
[0225] The interaction process between devices in steps S515 to S522 can be referred to Figure 3 the execution of steps S315 to S323 in, which will not be elaborated here.
[0226] In the above-mentioned embodiment during the code scanning payment process, the terminal device of the seller user can simultaneously use the traditional data network method and the sound wave assisted communication method to complete the transaction process, which can effectively reduce the occurrence of the phenomenon that the transaction cannot be successfully completed due to a poor network environment, improve the success rate of the transaction process, and enhance the user's satisfaction with the code scanning payment.
[0227] The embodiments of the present application may further include the following several implementation manners:
[0228] In another embodiment, the first terminal device may be a mobile terminal such as the mobile phone of the seller user, the first transaction application may be a transaction application associated with the resource receiving account corresponding to the seller user, and the second terminal device may be a mobile terminal such as the mobile phone of the buyer user. The second transaction application may be a transaction application associated with the resource payment account corresponding to the buyer user. The buyer user can use the second transaction application to scan the payment code of the resource receiving account displayed by the first transaction application, thereby realizing code scanning payment. The specific process is as follows:
[0229] The first transaction application receives the input payment code generation operation of the seller user. The payment code can be a collection code, and a payment code acquisition request is generated. The payment code acquisition request includes the account information of the resource receiving account. If the first transaction application detects that the network of the first terminal device is abnormal, it can load the payment code acquisition request and the address information of the first background server on the first sound wave and send it to the second transaction application. The second transaction application obtains the address information of the first background server and the payment code acquisition request in the received first sound wave, and sends the payment code acquisition request to the first background server through the second terminal device. The first background server generates payment code data according to the account information of the resource receiving account in the payment code acquisition request sent by the second terminal device, and sends it to the second transaction application. The second transaction application loads the received payment code data on the second sound wave and sends it to the first transaction application. The first transaction application displays the payment code, that is, the collection code, according to the payment code data in the received second sound wave. The buyer user uses the second transaction application to scan the collection code, obtains the account information of the resource receiving account, and displays the payment page, receives the transaction amount input by the buyer user through the payment page, and generates a resource transfer request. The resource transfer request includes the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer. The second transaction application sends the resource transfer request to the second background server through the second terminal device. The second background server deducts the money from the resource payment account according to the received resource transfer request, and sends a payment result notification to the first background server. The payment result notification carries the account information of the resource receiving account. The first background server adds the corresponding amount of money to the resource receiving account according to the received payment result notification. After the second background server completes the deduction, it sends a deduction result notification to the second transaction application, and the second transaction application can display the deduction result. After the first background server completes the collection, it sends a payment result notification to the first transaction application, and the first transaction application can display the payment result.
[0230] In another embodiment, the first terminal device can be a mobile terminal such as the mobile phone of the seller user. The first transaction application can be the transaction application associated with the resource receiving account corresponding to the seller user. The second terminal device can be a mobile terminal such as the mobile phone of the buyer user. The second transaction application can be the transaction application associated with the resource payment account corresponding to the buyer user. The buyer user can use the second transaction application to scan the collection code of the resource receiving account displayed by the first transaction application, so as to realize code scanning payment. The specific process is as follows:
[0231] The first transaction application receives an input payment code generation operation from the seller user. The payment code can be a collection code, and a payment code acquisition request is generated. The payment code acquisition request includes the account information of the resource receiving account. The first transaction application sends the payment code acquisition request to the first back-end server. At the same time, the payment code acquisition request and the address information of the first back-end server can be loaded on the first sound wave and sent to the second transaction application. The second transaction application obtains the address information of the first back-end server and the payment code acquisition request in the received first sound wave, and sends the payment code acquisition request to the first back-end server through the second terminal device. The first back-end server generates payment code data according to the first received payment code acquisition request. For example, if the first back-end server first receives the payment code acquisition request sent by the second terminal device, the first back-end server generates payment code data according to the account information of the resource receiving account in the payment code acquisition request sent by the second terminal device, and sends it to the second transaction application. The second transaction application loads the received payment code data on the second sound wave and sends it to the first transaction application. The first transaction application displays the payment code, that is, the collection code, according to the payment code data in the received second sound wave. The buyer user uses the second transaction application to scan the collection code, obtains the account information of the resource receiving account, and displays the payment page, receives the transaction amount input by the buyer user through the payment page, and generates a resource transfer request. The resource transfer request includes the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer. The second transaction application sends the resource transfer request to the second back-end server through the second terminal device. The second back-end server deducts the money from the resource payment account according to the received resource transfer request, and sends a payment result notification to the first back-end server. The payment result notification carries the account information of the resource receiving account. The first back-end server adds the corresponding amount of money to the resource receiving account according to the received payment result notification. After the second back-end server completes the deduction, it sends a deduction result notification to the second transaction application, and the second transaction application can display the deduction result. After the first back-end server completes the collection, it sends a payment result notification to the first transaction application, and the first transaction application can display the payment result.
[0232] In another embodiment, the first terminal device can be a mobile terminal such as the seller user's mobile phone. The first transaction application can be a transaction application associated with the resource receiving account corresponding to the seller user. The second terminal device can be a mobile terminal such as the buyer user's mobile phone. The second transaction application can be a transaction application associated with the resource payment account corresponding to the buyer user. The buyer user can use the second transaction application to scan the collection code of the resource receiving account displayed by the first transaction application, so as to realize scan code payment. The specific process is as follows:
[0233] The first transaction application receives an input payment code generation operation from the seller user. The payment code can be a collection code, and a payment code acquisition request is generated. The payment code acquisition request includes the account information of the resource receiving account. The first transaction application sends the payment code acquisition request to the first back-end server. The first back-end server generates payment code data based on the account information of the resource receiving account in the payment code acquisition request sent by the second terminal device, and sends it to the first transaction application. The first transaction application displays the payment code, that is, the collection code, according to the received payment code data. The buyer user uses the second transaction application to scan the collection code, obtains the account information of the resource receiving account, and displays a payment page, receives the transaction amount input by the buyer user through the payment page, and generates a resource transfer request. If the second transaction application detects that the network of the second terminal device is abnormal, it can load the resource transfer request and the address information of the second back-end server on the third sound wave and send it to the first transaction application. The resource transfer request contains the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer. The first transaction application sends the resource transfer request to the second back-end server through the first terminal device according to the address information of the second back-end server. The second back-end server deducts the money from the resource payment account according to the received resource transfer request, and sends a payment result notification to the first back-end server. The payment result notification carries the account information of the resource receiving account. The first back-end server adds the corresponding amount of money to the resource receiving account according to the received payment result notification. After the second back-end server completes the deduction, it sends a deduction result notification to the first transaction application. The first transaction application loads the received deduction result notification on the fourth sound wave and sends it to the second transaction application. The second transaction application can display the deduction result. After the first back-end server completes the collection, it sends a payment result notification to the first transaction application. The first transaction application can display the payment result.
[0234] In another embodiment, the first terminal device can be a mobile terminal such as the seller user's mobile phone. The first transaction application can be a transaction application associated with the resource receiving account corresponding to the seller user. The second terminal device can be a mobile terminal such as the buyer user's mobile phone. The second transaction application can be a transaction application associated with the resource payment account corresponding to the buyer user. The buyer user can use the second transaction application to scan the collection code of the resource receiving account displayed by the first transaction application, so as to realize scan code payment. The specific process is as follows:
[0235] The first transaction application receives an input payment code generation operation from the seller user. The payment code can be a collection code, and a payment code acquisition request is generated. The payment code acquisition request includes the account information of the resource receiving account. The first transaction application sends the payment code acquisition request to the first background server. The first background server generates payment code data based on the account information of the resource receiving account in the payment code acquisition request sent by the second terminal device and sends it to the first transaction application. The first transaction application displays the payment code, that is, the collection code, according to the received payment code data. The buyer user uses the second transaction application to scan the collection code, obtains the account information of the resource receiving account, and displays a payment page, receives the transaction amount input by the buyer user through the payment page, and generates a resource transfer request. The second transaction application sends the resource transfer request to the second background server through the second terminal device. At the same time, the second transaction application can load the resource transfer request and the address information of the second background server on the third sound wave and send it to the first transaction application. The resource transfer request contains the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer. The transaction information of this resource transfer includes identification information for uniquely identifying this resource transfer. The first transaction application sends the resource transfer request to the second background server through the first terminal device according to the address information of the second background server. The second background server deducts funds from the resource payment account according to the first received resource transfer request. Specifically, to avoid duplicate deductions, when the second background server receives a resource transfer request, it can judge whether it has ever received this resource transfer request according to the identification information of this resource transfer in the resource transfer request. If it has ever received it, it ignores this resource transfer request. If it has not received it, it means that it is the first time to receive this resource transfer request, and then it deducts funds from the resource payment account according to this resource transfer request. Assume that the second background server first receives the resource transfer request sent by the first terminal device. The second background server deducts funds from the resource payment account according to this resource transfer request and sends a payment result notification to the first background server. The payment result notification carries the account information of the resource receiving account. The first background server adds the corresponding amount of money to the resource receiving account according to the received payment result notification. After the second background server completes the deduction, it sends a deduction result notification to the first transaction application. The first transaction application loads the received deduction result notification on the fourth sound wave and sends it to the second transaction application. The second transaction application can display the deduction result. After the first background server completes the collection, it sends a payment result notification to the first transaction application. The first transaction application can display the payment result.
[0236] In another embodiment, the first terminal device may be a mobile terminal such as the mobile phone of the buyer user. The first transaction application may be a transaction application associated with the resource payment account corresponding to the buyer user. The second terminal device may be a mobile terminal such as a mobile phone on which the second transaction application is installed and running. The second transaction application may be a transaction application within the sound wave sending range of the first terminal device corresponding to the first transaction application. The second transaction application and the first transaction application are the same application. For example, when the buyer user purchases goods, the first transaction application can be used to scan the collection code pre-printed by the seller on a piece of paper, thereby realizing code scanning payment. The specific process is as follows:
[0237] The first transaction application starts the image acquisition component to scan the collection code pre-printed by the seller on a piece of paper, obtains the account information of the resource receiving account, and displays the payment page. It receives the transaction amount input by the buyer user through the payment page and generates a resource transfer request. The resource transfer request includes the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer. If the first transaction application detects that the network of the first terminal device is abnormal, it can load the resource transfer request and the address information of the first background server on the third sound wave and send the third sound wave through the sound wave transmitting component of the first terminal device. At this time, if the second terminal device is within the sound wave sending range of the first terminal device and is using the second transaction application, the second transaction application can receive the third sound wave sent by the first terminal device. The second transaction application can send the resource transfer request to the first background server through the second terminal device according to the address information of the first background server in the third sound wave. The first background server deducts money from the resource payment account according to the received resource transfer request and sends a deduction result notification to the second transaction application. The second transaction application loads the received deduction result notification on the fourth sound wave and sends it to the first transaction application. The first transaction application can display the deduction result, thereby completing the transaction process. The interaction process between the first background server and the background server corresponding to the seller user is the same as that in the above embodiments and will not be elaborated here.
[0238] In some embodiments, the system architecture diagram of the code scanning payment system may be as Figure 6 shown. Figure 6 The user's mobile phone in can be understood as the first terminal device, the user's mobile phone client can be understood as the first transaction application, the code scanning machine terminal can be understood as the second terminal device, and the code scanning machine terminal software can be understood as the second transaction application. Both the user's mobile phone and the code scanning machine terminal may include a user-level software layer, a sound wave communication software layer, and a sound wave communication hardware layer.
[0239] For a user's mobile phone, the user-level software layer includes the user mobile phone client, i.e., the first transaction application with payment collection and payment functions. The acoustic wave communication software layer includes a network quality monitoring module, an acoustic wave communication control module, a data encryption and decryption module, and an acoustic wave encoding and decoding module. The acoustic wave communication hardware layer includes an acoustic wave transmitting component and an acoustic wave receiving component. The network quality monitoring module is used to monitor whether the network of the user's mobile phone is unobstructed. If the network is unobstructed, the acoustic wave communication control module can enable acoustic wave communication, encrypt the network request data through the data encryption and decryption module to ensure data security, encode the data into an acoustic wave signal through the acoustic wave encoding and decoding module, and finally send the acoustic wave signal through the acoustic wave transmitting component.
[0240] For the scanning machine terminal, the user-level software layer includes the scanning machine terminal software, i.e., the second transaction application with payment collection functions. The acoustic wave communication software layer includes a network quality monitoring module, an acoustic wave communication control module, a data encryption and decryption module, and an acoustic wave encoding and decoding module. The acoustic wave communication hardware layer includes an acoustic wave transmitting component and an acoustic wave receiving component. When the scanning machine terminal software is waiting for scanning, the acoustic wave communication control module will start the acoustic wave receiving component to receive the acoustic wave signal from the user mobile phone client, decode it through the acoustic wave encoding and decoding module and decrypt it through the data encryption and decryption module to obtain the network request data, and send the network request data to the background server through the cellular data network or WiFi wireless network.
[0241] Although the embodiments of the present application provide the operation steps of the method as shown in the above embodiments or drawings, based on routine or non-creative labor, more or fewer operation steps may be included in the method. In the steps where there is no necessary causal relationship logically, the execution order of these steps is not limited to the execution order provided by the embodiments of the present application. When the method is actually processed or executed by the device, it can be executed in the method order shown in the embodiments or drawings or executed in parallel.
[0242] Based on the same inventive concept as the above embodiments, the embodiments of the present application provide a resource transfer processing method, which can be executed by the first transaction application. Figure 11 The flowchart of the resource transfer processing method is shown, as Figure 11 shown, the method may include the following steps:
[0243] Step S1101, during the process of resource transfer, load the transaction-related request to be sent to the background server on the acoustic wave and send it to the second transaction application, so that the second transaction application sends the transaction-related request to the background server.
[0244] In an alternative embodiment, after detecting a network anomaly, the first transaction application may load a transaction-related request onto a sound wave and send it to the second transaction application. Exemplarily, the first transaction application may send a network test request to the background server at regular intervals. If no response message is received from the background server within a preset duration after sending the network test request, it is confirmed that a network anomaly has been detected; alternatively, the first transaction application may send a transaction-related request to the background server. If no transaction-related data is received from the background server within the preset duration, it is confirmed that a network anomaly has been detected.
[0245] In another alternative embodiment, while sending a transaction-related request to the background server, the first transaction application may load the transaction-related request onto a sound wave and send it to the second transaction application.
[0246] Step S1102: Receive the transaction-related data sent by the second transaction application via a sound wave, and complete the resource transfer based on the transaction-related data.
[0247] Among them, the transaction-related data is generated by the background server based on the received transaction-related request.
[0248] And Figure 11 Corresponding to the resource transfer processing method shown, an embodiment of the present application further provides a resource transfer processing method, which can be executed by the second transaction application. Figure 12 The flowchart of this resource transfer processing method is shown. As Figure 12 shown, this method may include the following steps:
[0249] Step S1201: During the process of resource transfer, receive the transaction-related request sent by the first transaction application via a sound wave, and send the transaction-related request to the background server, so that the background server generates transaction-related data based on the received transaction-related request.
[0250] Step S1202: Receive the transaction-related data returned by the background server, and load the transaction-related data onto a sound wave and send it to the first transaction application, so that the first transaction application completes the resource transfer based on the transaction-related data.
[0251] In an alternative embodiment, the first transaction application is a transaction application associated with a resource payment account, and the second transaction application is a transaction application associated with a resource receiving account; the transaction-related request during the resource transfer process may be a payment code acquisition request, and the transaction-related data may be payment code data. Loading the transaction-related request that needs to be sent to the background server onto a sound wave and sending it to the second transaction application may include:
[0252] Load the payment code acquisition request onto the first sound wave and send it to the terminal device where the second transaction application is located, so that the second transaction application can obtain the payment code acquisition request from the first sound wave received by the terminal device, and send the payment code acquisition request to the background server according to the address information of the background server in the first sound wave; the payment code acquisition request carries the account information of the resource payment account;
[0253] Receive the transaction-related data sent by the second transaction application through the sound wave, including:
[0254] Receive the payment code data sent by the second transaction application through the second sound wave; the payment code data is generated by the background server based on the account information of the resource payment account in the received payment code acquisition request and sent to the second transaction application.
[0255] Correspondingly, receive the transaction-related request sent by the first transaction application through the sound wave and send the transaction-related request to the background server, including:
[0256] Receive the payment code acquisition request sent by the first transaction application through the first sound wave and send the payment code acquisition request to the background server according to the address information of the background server in the first sound wave; the payment code acquisition request carries the account information of the resource payment account;
[0257] Receive the transaction-related data returned by the background server and load the transaction-related data onto the sound wave and send it to the first transaction application, including:
[0258] Receive the payment code data returned by the background server and load the payment code data onto the second sound wave and send it to the first transaction application; the payment code data is generated by the background server based on the account information of the resource payment account in the received payment code acquisition request.
[0259] In another optional embodiment, the first transaction application is a transaction application associated with the resource receiving account, and the second transaction application is a transaction application associated with the resource payment account; or, the first transaction application is a transaction application associated with the resource payment account, and the second transaction application is a transaction application within the sound wave sending range of the first transaction application; the transaction-related request during the resource transfer process may be a resource transfer request, and the transaction-related data may be resource transfer result data. Loading the transaction-related request to be sent to the background server onto the sound wave and sending it to the second transaction application includes:
[0260] Load the resource transfer request onto the third sound wave and send it to the terminal device where the second trading application is located, so that the second trading application obtains the resource transfer request from the third sound wave received by the terminal device, and sends the resource transfer request to the background server according to the address information of the background server in the third sound wave; the resource transfer request carries the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer.
[0261] Receive the transaction-related data sent by the second trading application through the sound wave, including:
[0262] Receive the resource transfer result data sent by the second trading application through the fourth sound wave; the resource transfer result data is generated by the background server based on the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer in the received resource transfer request.
[0263] Correspondingly, receive the transaction-related request sent by the first trading application through the sound wave and send the transaction-related request to the background server, including:
[0264] Receive the resource transfer request sent by the first trading application through the third sound wave and send the resource transfer request to the background server according to the address information of the background server in the third sound wave; the resource transfer request carries the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer.
[0265] Receive the transaction-related data returned by the background server and load the transaction-related data onto the sound wave and send it to the first trading application, including:
[0266] Receive the resource transfer result data returned by the background server and load the resource transfer result data onto the fourth sound wave and send it to the first trading application; the resource transfer result data is generated by the background server based on the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer in the received resource transfer request.
[0267] Based on the same inventive concept, an embodiment of the present application further provides a resource transfer processing device, which can be arranged in the first terminal device. Since this device is the device corresponding to the resource transfer processing method applied to the first trading application in the embodiment of the present application, and the principle of this device to solve problems is similar to that of this method, the implementation of this device can refer to the implementation process of the above method embodiment, and the repeated parts will not be described again.
[0268] Figure 13 The structural schematic diagram of a resource transfer processing device provided by an embodiment of the present application is shown. This resource transfer processing device is applied to the first trading application, such as Figure 13As shown in the figure, it includes: a request sending unit 1301 and a data receiving unit 1302; among them,
[0269] The request sending unit 1301 is configured to, during the process of resource transfer, load a transaction-related request to be sent to the background server on a sound wave and send it to the second transaction application, so that the second transaction application sends the transaction-related request to the background server;
[0270] The data receiving unit 1302 is configured to receive transaction-related data sent by the second transaction application through a sound wave, and complete resource transfer according to the transaction-related data; the transaction-related data is generated by the background server based on the received transaction-related request.
[0271] In an optional embodiment, the first transaction application is a transaction application associated with a resource payment account, and the second transaction application is a transaction application associated with a resource receiving account; the request sending unit 1301 is specifically configured to: load a payment code acquisition request on a first sound wave and send it to the terminal device where the second transaction application is located, so that the second transaction application obtains the payment code acquisition request from the first sound wave received by the terminal device, and sends the payment code acquisition request to the background server according to the address information of the background server in the first sound wave; the payment code acquisition request carries the account information of the resource payment account.
[0272] The data receiving unit 1302 is specifically configured to:
[0273] Receive payment code data sent by the second transaction application through a second sound wave; the payment code data is generated by the background server based on the account information of the resource payment account in the received payment code acquisition request and sent to the second transaction application.
[0274] In an optional embodiment, the first transaction application is a transaction application associated with a resource receiving account, and the second transaction application is a transaction application associated with a resource payment account; or, the first transaction application is a transaction application associated with a resource payment account, and the second transaction application is a transaction application within the sound wave sending range of the first transaction application; the request sending unit 1301 is specifically configured to:
[0275] Load a resource transfer request on a third sound wave and send it to the terminal device where the second transaction application is located, so that the second transaction application obtains the resource transfer request from the third sound wave received by the terminal device, and sends the resource transfer request to the background server according to the address information of the background server in the third sound wave; the resource transfer request carries the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer.
[0276] The data receiving unit 1302 is specifically configured to:
[0277] Receive the resource transfer result data sent by the second trading application via the fourth sound wave; the resource transfer result data is generated by the background server based on the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer in the received resource transfer request.
[0278] In an alternative embodiment, the request sending unit 1301 is specifically configured to:
[0279] If a network anomaly is detected, load the transaction-related request on a sound wave and send it to the second trading application; or,
[0280] Send the transaction-related request to the background server and load the transaction-related request on a sound wave and send it to the second trading application.
[0281] In an alternative embodiment, the request sending unit 1301 is specifically configured to:
[0282] Send a network test request to the background server at intervals of a set duration. If no response message is received from the background server within a preset duration after sending the network test request, it is confirmed that a network anomaly is detected; or,
[0283] Send the transaction-related request to the background server. If no transaction-related data is received from the background server within the preset duration, it is confirmed that a network anomaly is detected.
[0284] Based on the same inventive concept, another resource transfer processing device is further provided in an embodiment of the present application. This resource transfer processing device is disposed in the second terminal device. Since this device is the device corresponding to the resource transfer processing method applied to the second trading application in the embodiment of the present application, and the principle of this device for solving problems is similar to that of this method, the implementation of this device can refer to the implementation process of the embodiment of the above method, and the repeated parts will not be described again.
[0285] Figure 14 Shows a schematic structural diagram of another resource transfer processing device provided in an embodiment of the present application. This resource transfer processing device is applied to the second trading application, as Figure 14 shown, and includes: a request receiving unit 1401 and a data sending unit 1402; wherein,
[0286] The request receiving unit 1401 is configured to receive the transaction-related request sent by the first trading application via a sound wave during the process of resource transfer, and send the transaction-related request to the background server, so that the background server generates transaction-related data based on the received transaction-related request;
[0287] A data sending unit 1402, configured to receive transaction-related data returned by a background server, and load the transaction-related data on a sound wave to send to a first transaction application, so that the first transaction application completes resource transfer according to the transaction-related data.
[0288] In an alternative embodiment, the first transaction application is a transaction application associated with a resource payment account, and the second transaction application is a transaction application associated with a resource receiving account; the request receiving unit 1401 is specifically configured to:
[0289] Receive a payment code acquisition request sent by the first transaction application through a first sound wave, and send the payment code acquisition request to the background server according to the address information of the background server in the first sound wave; the payment code acquisition request carries account information of the resource payment account.
[0290] The data sending unit 1402 is specifically configured to:
[0291] Receive payment code data returned by the background server, and load the payment code data on a second sound wave to send to the first transaction application; the payment code data is generated by the background server based on the account information of the resource payment account in the received payment code acquisition request.
[0292] In an alternative embodiment, the first transaction application is a transaction application associated with a resource receiving account, and the second transaction application is a transaction application associated with a resource payment account; or, the first transaction application is a transaction application associated with a resource payment account, and the second transaction application is a transaction application within the sound wave sending range of the first transaction application; the request receiving unit 1401 is specifically configured to:
[0293] Receive a resource transfer request sent by the first transaction application through a third sound wave, and send the resource transfer request to the background server according to the address information of the background server in the third sound wave; the resource transfer request carries the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer.
[0294] The data sending unit 1402 is specifically configured to:
[0295] Receive resource transfer result data returned by the background server, and load the resource transfer result data on a fourth sound wave to send to the first transaction application; the resource transfer result data is generated by the background server based on the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer in the received resource transfer request.
[0296] Based on the same inventive concept, an electronic device is further provided in an embodiment of the present application. In an embodiment, the electronic device may be a terminal device associated with a resource receiving account, such as Figure 1The second terminal device 200 shown. In this embodiment, the structure of the electronic device may be as Figure 15 shown, including a memory 1501, a communication module 1503, an acoustic wave receiving component 1505, an acoustic wave transmitting component 1506, and one or more processors 1502.
[0297] The memory 1501 is used to store computer programs executed by the processor 1502. The memory 1501 may mainly include a program storage area and a data storage area. Among them, the program storage area may store an operating system, programs required to run game functions, etc.; the data storage area may store various game information and operation instruction sets, etc.
[0298] The memory 1501 may be a volatile memory, such as a random-access memory (RAM); the memory 1501 may also be a non-volatile memory, such as a read-only memory, a flash memory, a hard disk drive (HDD), or a solid-state drive (SSD); the memory 1501 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this. The memory 1501 may be a combination of the above memories.
[0299] The processor 1502 may include one or more central processing units (CPUs) or be a digital processing unit, etc. The processor 1502 is used to implement the above resource transfer processing method when calling the computer program stored in the memory 1501.
[0300] The communication module 1503 is used to communicate with other terminal devices or a background server.
[0301] In the embodiments of the present application, the specific connection medium between the above memory 1501, communication module 1503, acoustic wave receiving component 1505, acoustic wave transmitting component 1506, and processor 1502 is not limited. In the embodiments of the present disclosure Figure 15 it is shown that the memory 1501 and the processor 1502 are connected through a bus 1504, and the bus 1504 is shown as a thick line in Figure 15 The connection manners between other components are only for illustrative purposes and are not to be construed as limiting. The bus 1504 may be divided into an address bus, a data bus, a control bus, etc. For the sake of convenience of representation, Figure 15 only one thick line is shown in
[0302] A computer storage medium is stored in the memory 1501. Computer-executable instructions are stored in the computer storage medium, and the computer-executable instructions are used to implement the resource transfer processing method of the embodiments of the present application. The processor 1502 is used to execute the above-mentioned resource transfer processing method.
[0303] The acoustic wave receiving component 1505 and the acoustic wave transmitting component 1506 can provide an audio interface between the user and the second terminal device 200. The acoustic wave receiving component 1505 is used to receive acoustic wave data sent by other terminal devices and transmit the acoustic wave data to the processor 1502 for decoding. The acoustic wave transmitting component 1506 can send the acoustic wave data to be sent to other terminal devices, such as Figure 1 the first terminal device 100 in
[0304] In another embodiment, the electronic device may be a payment terminal device associated with a resource receiving account, such as Figure 1 the first terminal device 100 shown. In this embodiment, the structure of the electronic device may be as shown in Figure 16 and includes components such as a communication component 210, a memory 220, a display unit 230, a camera 240, a sensor 250, an audio circuit 260, a Bluetooth module 270, a processor 280, etc.
[0305] The communication component 210 is used to communicate with the server. In some embodiments, it may include a WiFi (Wireless Fidelity) module. The WiFi module belongs to short-range wireless transmission technology, and the electronic device can help the user send and receive information through the WiFi module.
[0306] The memory 220 can be used to store software programs and data. The processor 280 executes various functions and data processing of the first terminal device 100 by running the software programs or data stored in the memory 220. The memory 220 may include a high-speed random access memory and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices. The memory 220 stores an operating system that enables the first terminal device 100 to operate. In the present application, the memory 220 can store the operating system and various application programs, and can also store the code for implementing the resource transfer processing method of the embodiments of the present application.
[0307] The display unit 230 can also be used to display information input by the user or information provided to the user, as well as the graphical user interface (GUI) of various menus of the first terminal device 100. Specifically, the display unit 230 may include a display screen 232 disposed on the front of the first terminal device 100. Among them, the display screen 232 may be configured in the form of a liquid crystal display, a light-emitting diode, etc. The display unit 230 can be used to display the payment interface and the like in the embodiments of the present application.
[0308] The display unit 230 can also be used to receive input numerical or character information, and generate signal inputs related to the user settings and function controls of the first terminal device 100. Specifically, the display unit 230 may include a touch screen 231 disposed on the front of the first terminal device 100, which can collect touch operations of the user thereon or nearby, such as clicking buttons, dragging scroll boxes, etc.
[0309] Among them, the touch screen 231 can cover the display screen 232, or the touch screen 231 and the display screen 232 can be integrated to implement the input and output functions of the first terminal device 100. After integration, it can be simply called a touch display screen. In the present application, the display unit 230 can display application programs and corresponding operation steps.
[0310] The camera 240 can be used to capture static images, and the user can send the images captured by the camera 240 to the background server or other game users through the cloud game client. The camera 240 can be one or multiple. An object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then transmits the electrical signal to the processor 280 to convert it into a digital image signal.
[0311] The terminal device may further include at least one sensor 250, such as an acceleration sensor 251, a distance sensor 252, a fingerprint sensor 253, a temperature sensor 254. The terminal device may also be configured with other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, a light sensor, a motion sensor, etc.
[0312] The audio circuit 260, the sound wave receiving component 261, and the sound wave transmitting component 262 can provide an audio interface between the user and the first terminal device 100. The first terminal device 100 can also be configured with volume buttons for adjusting the volume of the sound signal. The audio circuit 260 can convert the sound wave data received by the sound wave receiving component 261 into an electrical signal and send it to the processor 280 for decoding processing. On the other hand, the audio circuit 260 can also convert the received electrical signal into sound wave information, transmit it to the sound wave transmitting component 262, and then the sound wave transmitting component 262 outputs the sound wave information to other terminal devices, such as the second terminal device 200.
[0313] The Bluetooth module 270 is used to interact with other Bluetooth devices having Bluetooth modules through the Bluetooth protocol. For example, the terminal device can establish a Bluetooth connection with a wearable electronic device that also has a Bluetooth module through the Bluetooth module 270 to perform data interaction.
[0314] The processor 280 is the control center of the terminal device, connecting various parts of the entire terminal using various interfaces and lines. By running or executing software programs stored in the memory 220 and calling data stored in the memory 220, it executes various functions of the terminal device and processes data. In some embodiments, the processor 280 may include one or more processing units; the processor 280 can also integrate an application processor and a baseband processor, where the application processor mainly processes the operating system, user interface, and application programs, etc., and the baseband processor mainly processes wireless communication. It can be understood that the above baseband processor may not be integrated into the processor 280. In this application, the processor 280 can run the operating system, application programs, user interface display, and touch response, as well as the resource transfer processing method of the embodiments of this application. In addition, the processor 280 is coupled to the display unit 230.
[0315] The embodiments of this application also provide a computer storage medium, in which computer-executable instructions are stored, and the computer-executable instructions are used to implement the resource transfer processing method of any embodiment of this application.
[0316] In some possible implementation manners, each aspect of the resource transfer processing method provided in this application can also be implemented in the form of a program product, which includes program code. When the program product runs on a computer device, the program code is used to cause the computer device to execute the steps of the resource transfer processing method described above in this specification according to various exemplary embodiments of this application. For example, the computer device can execute the resource transfer processing method flow of steps S1101 - S1102 as shown in Figure 11 ; or, it can execute the resource transfer processing method flow of steps S1201 - S1202 as shown in Figure 12 .
[0317] Those of ordinary skill in the art can understand that all or part of the steps of implementing the above method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps including those of the above method embodiments; and the aforementioned storage medium includes: various media that can store program codes, such as removable storage devices, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs.
[0318] As described above, the above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the present application.
Claims
1. A resource transfer processing method, characterized in that, Executed by a first transaction application, the method includes: During the process of resource transfer, loading a transaction-related request to be sent to a background server onto a sound wave and sending it to a second transaction application, so that the second transaction application sends the transaction-related request to the background server; Receiving transaction-related data sent by the second transaction application through a sound wave, and completing resource transfer according to the transaction-related data; the transaction-related data is generated by the background server based on the received transaction-related request; When the first transaction application is a transaction application associated with a resource payment account and the second transaction application is a transaction application associated with a resource receiving account, the loading the transaction-related request to be sent to the background server onto a sound wave and sending it to the second transaction application includes: Loading a payment code acquisition request onto a first sound wave and sending it to the terminal device where the second transaction application is located, so that the second transaction application obtains the payment code acquisition request from the first sound wave received by the terminal device, and sends the payment code acquisition request to the background server according to the address information of the background server in the first sound wave; the payment code acquisition request carries the account information of the resource payment account; The receiving the transaction-related data sent by the second transaction application through a sound wave includes: Receiving payment code data sent by the second transaction application through a second sound wave; the payment code data is generated by the background server based on the account information of the resource payment account in the received payment code acquisition request and sent to the second transaction application.
2. The method according to claim 1, wherein The loading the transaction-related request to be sent to the background server onto a sound wave and sending it to the second transaction application includes: If network anomaly is detected, loading the transaction-related request onto a sound wave and sending it to the second transaction application; or, Sending a transaction-related request to the background server, and loading the transaction-related request onto a sound wave and sending it to the second transaction application.
3. The method according to claim 2, wherein The detecting network anomaly includes: Sending a network test request to the background server at every set time interval, and if no response message returned by the background server is received within a preset time after sending the network test request, confirming that network anomaly is detected; or, Sending a transaction-related request to the background server, and if no transaction-related data returned by the background server is received within a preset time, confirming that network anomaly is detected.
4. The method according to any one of claims 1 to 3, characterized in that When the first transaction application is a transaction application associated with a resource receiving account and the second transaction application is a transaction application associated with a resource payment account, or when the first transaction application is a transaction application associated with a resource payment account and the second transaction application is a transaction application within the sound wave sending range of the first transaction application, the loading the transaction-related request to be sent to the background server onto a sound wave and sending it to the second transaction application includes: Load the resource transfer request onto the third sound wave and send it to the terminal device where the second trading application is located, so that the second trading application obtains the resource transfer request from the third sound wave received by the terminal device, and sends the resource transfer request to the background server according to the address information of the background server in the third sound wave; the resource transfer request carries the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer. Receiving the transaction-related data sent by the second trading application through sound waves, including: Receiving the resource transfer result data sent by the second trading application through the fourth sound wave; the resource transfer result data is generated by the background server based on the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer in the received resource transfer request.
5. A resource transfer processing method, characterized in that, Executed by the second trading application, the method includes: During the process of resource transfer, receive the transaction-related request sent by the first trading application through sound waves, and send the transaction-related request to the background server, so that the background server generates transaction-related data based on the received transaction-related request. Receive the transaction-related data returned by the background server, and load the transaction-related data onto the sound wave and send it to the first trading application, so that the first trading application completes the resource transfer according to the transaction-related data. When the first trading application is the trading application associated with the resource payment account and the second trading application is the trading application associated with the resource receiving account, the receiving the transaction-related request sent by the first trading application through sound waves and sending the transaction-related request to the background server includes: Receive the payment code acquisition request sent by the first trading application through the first sound wave, and send the payment code acquisition request to the background server according to the address information of the background server in the first sound wave; the payment code acquisition request carries the account information of the resource payment account. The receiving the transaction-related data returned by the background server and loading the transaction-related data onto the sound wave and sending it to the first trading application includes: Receive the payment code data returned by the background server, and load the payment code data onto the second sound wave and send it to the first trading application; the payment code data is generated by the background server based on the account information of the resource payment account in the received payment code acquisition request.
6. The method according to claim 5, wherein When the first trading application is the trading application associated with the resource receiving account and the second trading application is the trading application associated with the resource payment account, or when the first trading application is the trading application associated with the resource payment account and the second trading application is the trading application within the sound wave sending range of the first trading application, the receiving the transaction-related request sent by the first trading application through sound waves and sending the transaction-related request to the background server includes: Receive the resource transfer request sent by the first trading application via the third sound wave, and send the resource transfer request to the background server according to the address information of the background server in the third sound wave; the resource transfer request carries the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer. Receiving the transaction-related data returned by the background server and sending the transaction-related data loaded on the sound wave to the first trading application includes: Receive the resource transfer result data returned by the background server, and send the resource transfer result data loaded on the fourth sound wave to the first trading application; the resource transfer result data is generated by the background server based on the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer in the received resource transfer request.
7. A resource transfer processing device, characterized in that, Applied to the first trading application, the device includes: A request sending unit, configured to load a transaction-related request to be sent to the background server on a sound wave and send it to the second trading application during the process of resource transfer, so that the second trading application sends the transaction-related request to the background server; A data receiving unit, configured to receive the transaction-related data sent by the second trading application via the sound wave, and complete the resource transfer according to the transaction-related data; the transaction-related data is generated by the background server based on the received transaction-related request; When the first trading application is a trading application associated with the resource payment account and the second trading application is a trading application associated with the resource receiving account, the request sending unit is specifically configured to: Load the payment code acquisition request on the first sound wave and send it to the terminal device where the second trading application is located, so that the second trading application obtains the payment code acquisition request from the first sound wave received by the terminal device, and send the payment code acquisition request to the background server according to the address information of the background server in the first sound wave; the payment code acquisition request carries the account information of the resource payment account; The data receiving unit is specifically configured to: Receive the payment code data sent by the second trading application via the second sound wave; the payment code data is generated by the background server based on the account information of the resource payment account in the received payment code acquisition request and sent to the second trading application.
8. The device according to claim 7, characterized in that, When the first trading application is a trading application associated with the resource receiving account and the second trading application is a trading application associated with the resource payment account, or when the first trading application is a trading application associated with the resource payment account and the second trading application is a trading application within the sound wave sending range of the first trading application, the request sending unit is specifically configured to: Load the resource transfer request onto the third sound wave and send it to the terminal device where the second trading application is located, so that the second trading application can obtain the resource transfer request from the third sound wave received by the terminal device, and send the resource transfer request to the background server according to the address information of the background server in the third sound wave; the resource transfer request carries the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer. The data receiving unit is specifically configured to: Receive the resource transfer result data sent by the second trading application through the fourth sound wave; the resource transfer result data is generated by the background server based on the account information of the resource payment account, the account information of the resource receiving account, and the transaction information of this resource transfer in the received resource transfer request.
9. A resource transfer processing device, characterized in that, Applied to the second trading application, the device includes: A request receiving unit, configured to receive, during the resource transfer process, a transaction-related request sent by the first trading application through a sound wave, and send the transaction-related request to the background server, so that the background server generates transaction-related data based on the received transaction-related request. A data sending unit, configured to receive the transaction-related data returned by the background server, and load the transaction-related data onto a sound wave and send it to the first trading application, so that the first trading application completes the resource transfer according to the transaction-related data. When the first trading application is the trading application associated with the resource payment account and the second trading application is the trading application associated with the resource receiving account, the request receiving unit is specifically configured to: Receive the payment code acquisition request sent by the first trading application through the first sound wave, and send the payment code acquisition request to the background server according to the address information of the background server in the first sound wave; the payment code acquisition request carries the account information of the resource payment account. The data sending unit is specifically configured to: Receive the payment code data returned by the background server, and load the payment code data onto the second sound wave and send it to the first trading application; the payment code data is generated by the background server based on the account information of the resource payment account in the received payment code acquisition request.
10. A computer-readable storage medium storing a computer program therein, characterized in that: When the computer program is executed by a processor, it implements the method described in any one of claims 1 to 4 or the method described in any one of claims 5 to 6.
11. An electronic device, characterized in that, It includes a memory and a processor, and a computer program that can run on the processor is stored on the memory. When the computer program is executed by the processor, it implements the method described in any one of claims 1 to 4 or the method described in any one of claims 5 to 6.
Citation Information
Patent Citations
Two-dimensional code acoustic wave payment device and payment system thereof, and payment method thereof
CN109064162A