Data transfer method, apparatus, device, and storage medium

Abstract

Embodiments of the present application disclose a data transfer method, device and equipment, and a storage medium. The method comprises: obtaining a data transfer value generated by a first client in response to a data transfer operation to a second client, and a data remaining value of an account of the first client before responding to the data transfer operation; if the data transfer value is not greater than the data remaining value, generating first prompt information for prompting a user that the data transfer is successful and sending the first prompt information to the first client, sending a data transfer request to a second server, instructing the second server to transfer the data transfer value from an account with a first data transfer identifier to an account with a second data transfer identifier, and sending second prompt information to the first client when a data transfer success result fed back by the second server is obtained. The above method avoids the problem that a user needs to wait for a long time for a data transfer result during a data transfer process.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more specifically, to a data transfer method, apparatus, device, and storage medium. Background Technology

[0002] With the development of mobile terminal technology, people are becoming increasingly reliant on terminal devices such as smartphones, tablets, and laptops. Currently, users typically need to use client applications installed on these devices for transportation, shopping, and item redemption, all of which require data transfer via these clients, such as the withdrawal and transfer of amounts, usage frequency, redemption limits, or points.

[0003] Currently, for data transfer operations, to obtain the final data transfer result, the data transfer needs to be performed by the server corresponding to the data recipient or a dedicated server for performing data transfer. After obtaining the transfer result, it is returned to the server corresponding to the client. The final transfer result is then returned to the client by the server corresponding to the client. This process takes too long, causing users to wait too long to obtain the final data transfer result, thus causing inconvenience to customers. Summary of the Invention

[0004] In view of this, embodiments of this application propose a data transfer method, apparatus, device, and storage medium that can be implemented in...

[0005] In a first aspect, embodiments of this application provide a data transfer method applied to a first server. The method includes: obtaining a data transfer value generated by a first client in response to a data transfer operation to a second client, and the remaining data value of the first client's account before responding to the data transfer operation; if the data transfer value is not greater than the remaining data value, generating a first prompt message and sending the first prompt message to the first client, the first prompt message being used to indicate to the user that the data transfer was successful; sending a data transfer request to the second server, instructing the second server to transfer the data transfer value from the account containing a first data transfer identifier to the account containing a second data transfer identifier, the data transfer request carrying the first data transfer identifier, the second data transfer identifier, and the data transfer value, the first data transfer identifier corresponding to the first client, the second data transfer identifier corresponding to the second client, and at least one of the accounts containing the first data transfer identifier and the account containing the second data transfer identifier having an account type different from the account type of the first client's account; if a data transfer success result is received from the second server based on the data transfer request, sending a second prompt message to the first client, the second prompt message including the data transfer success result.

[0006] Secondly, embodiments of this application provide a data transfer method applied to a first client. The method includes: in response to a data transfer operation to a second client, sending identification information of the first client to a first server, so that the first server obtains the remaining data value of the first client's account before responding to the data transfer operation based on the identification information of the first client; sending a data transfer request including a data transfer value to a second server, the data transfer value being obtained based on the data transfer operation initiated to the second client; receiving a first prompt message generated by the first server when the data transfer value is not greater than the remaining data value, the first prompt message being used to prompt the user that the data transfer was successful; receiving a second prompt message fed back by the first server, the second prompt message being generated by the first server when receiving a data transfer success result fed back by the second server based on the data transfer request, or when the first server receives a data transfer failure result fed back by the second server based on the data transfer request, and the first server transfers the data transfer value from the remaining data value of the first client's account to the account where the second data transfer identifier of the second client is located.

[0007] Thirdly, embodiments of this application provide a data transfer device applied to a first server. The device includes a data acquisition module, a prompt message generation module, a request sending module, and a prompt message sending module. The first data acquisition module is used to acquire the data transfer value generated by the first client in response to a data transfer operation to a second client, and the remaining data value of the first client's account before responding to the data transfer operation. The prompt message generation module is used to generate a first prompt message if the data transfer value is not greater than the remaining data value, and to send the first prompt message to the first client, the first prompt message indicating successful data transfer. The request sending module is used to send a data transfer request to the second server, instructing the second server to transfer the data transfer value from the account containing a first data transfer identifier to the account containing a second data transfer identifier. The data transfer request carries a first data transfer identifier of the first client, a second data transfer identifier of the second client, and the data transfer value. At least one of the first and second data transfer identifiers corresponds to a bank code. The prompt message sending module is used to send a second prompt message to the first client if a successful data transfer result is received from the second server based on the data transfer request, the second prompt message including the successful data transfer result.

[0008] In one possible implementation, the data acquisition module is further configured to respond to a second data transfer identification code acquisition request sent by the first client, generate a first data transfer identification code and feed it back to the first client; and acquire the data transfer value fed back by the second client after scanning the first data transfer identification code displayed by the first client.

[0009] In one possible implementation, the data acquisition module is further configured to acquire the data transfer value input by the user based on the data transfer interface received by the first client, wherein the data transfer interface is generated by the first client scanning the second data transfer identification code corresponding to the second client in response to the user-triggered scanning operation.

[0010] In one possible implementation, if the account containing the first data transfer identifier is not the account of the first client, and the account type of the account containing the second data transfer identifier is the same as the account type of the first client's account, the device further includes a data transfer module, configured to transfer the data transfer value from the remaining data value of the first client's account to the account containing the second data transfer identifier of the second client, and generate a data transfer success result, when the second server receives a data transfer failure result indicating that the data transfer value was transferred from the account containing the first data transfer identifier to the account containing the second data transfer identifier based on the data transfer request.

[0011] In one possible implementation, the prompt message sending module is further configured to obtain the account type of the account that transferred the data transfer value in the account corresponding to the first client, and send a second prompt message to the first client including the data transfer success result and the account type.

[0012] In one possible implementation, if the first data transfer identifier corresponds to data transfer discount information, the obtained data transfer success result includes the data transfer discount information and the actual data transfer value obtained by processing the data transfer value based on the data transfer discount information.

[0013] Fourthly, this application provides a data transfer device applied to a first client. The device includes: an identification information sending module, a first prompt information receiving module, and a second prompt information receiving module. The identification information sending module is used to send identification information of the first client to a first server in response to a data transfer operation to a second client. This allows the first server to obtain the remaining data value of the first client's account before responding to the data transfer operation based on the identification information of the first client, and to send a data transfer request including a data transfer value to the second server. The data transfer value is obtained based on the data transfer operation initiated to the second client. The first prompt information receiving module is used to receive a first prompt information generated by the first server when the data transfer value is not greater than the remaining data value. The first prompt information is used to indicate to the user that the data transfer was successful. The second prompt information receiving module is used to receive a second prompt information fed back by the first server. The second prompt information is generated by the first server when it receives a successful data transfer result from the second server based on the data transfer request, or when it receives a failed data transfer result from the second server based on the data transfer request, and the first server transfers the data transfer value from the remaining data value of the first client's account to the account containing the second data transfer identifier of the second client.

[0014] In one optional implementation, the identification information sending module is further configured to, in response to a data transfer request, collect the user's identity authentication information, send the identity authentication information and the identification information of the first client to a first server, so that the server authenticates the identity authentication information, and, upon successful authentication, obtains the remaining data value of the first client's account before responding to the data transfer operation based on the identification information of the first client.

[0015] In one possible implementation, the data transfer device further includes a data transfer value acquisition module, which is used to scan the second data transfer identification code corresponding to the second client to generate a data transfer interface in response to a user-triggered scanning operation; receive the data transfer value input by the user based on the data transfer interface; and send the data transfer value to the first server.

[0016] In one possible implementation, the data transfer device further includes an identification code display module, which is used to display a first data transfer identification code fed back by the first server when the identity authentication information is successfully authenticated, so that the second client can feed back a data transfer value to the first server after scanning the first data transfer identification code.

[0017] In one possible implementation, the data transfer device further includes a prompt information display module, configured to, if the current display interface of the terminal where the first client is located is a first designated interface, jump to display a second designated interface, wherein the first designated interface displays a first prompt information and the second designated interface displays a second prompt information; if the current display interface of the terminal where the first client is located is not the first designated interface, display a notification or pop-up window on the current display interface, wherein the notification or pop-up window is used to indicate that the first client has received the second prompt information.

[0018] Fifthly, embodiments of this application provide an electronic device, including a processor and a memory; one or more programs are stored in the memory and configured to be executed by the processor to implement the above-described method.

[0019] Sixthly, embodiments of this application provide a computer-readable storage medium storing program code, wherein the above-described method is executed when the program code is run by a processor.

[0020] In a seventh aspect, embodiments of this application provide a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device retrieves the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the method described above.

[0021] This application provides a data transfer method, apparatus, device, and storage medium. The specific data transfer method is as follows: A data transfer value generated by a first client in response to a data transfer operation to a second client, and the remaining data value of the first client's account before responding to the data transfer operation, are obtained. If the data transfer value is not greater than the remaining data value, a first notification message is generated to indicate successful data transfer and sent to the first client. A data transfer request is sent to a second server, instructing the second server to transfer the data transfer value from the account containing the first data transfer identifier to the account containing the second data transfer identifier. If a successful data transfer result is received from the second server, a second notification message is sent to the first client. This method allows the first server to return a successful data transfer result to the first client as soon as it confirms that the remaining data value of the first client's account is greater than the data transfer value, meaning the first client's account can transfer the data transfer value to the second client. This allows the user to view the result without waiting for the data transfer to complete, effectively saving user waiting time and avoiding the inconvenience caused by prolonged waiting for successful data transfer results. Attached Figure Description

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

[0023] Figure 1 A schematic diagram of the connection of the data transfer system provided in an embodiment of this application is shown; Figure 2 A flowchart illustrating a data transfer method applied to a first server according to an embodiment of this application is shown; Figure 3 A flowchart illustrating a data transfer method applied to a first client according to an embodiment of this application is shown; Figure 4 This illustration shows a timing flow diagram of a data transfer system provided in an embodiment of this application; Figure 5 A flowchart illustrating a data transfer method applied to a data transfer system according to an embodiment of this application is shown. Figure 6 A schematic diagram of the interface of a first client provided in an embodiment of this application is shown; Figure 7 This illustration shows a schematic diagram of a face-scanning payment method for a first client according to an embodiment of this application; Figure 8 A schematic diagram of a payment interface for a first client provided in an embodiment of this application is shown; Figure 9 This illustration shows a schematic diagram of the interface during the payment process of a first client according to an embodiment of this application; Figure 10 This illustration shows a schematic diagram of an interface for displaying first prompt information on a first client, provided in an embodiment of this application. Figure 11 This illustration shows a schematic diagram of an interface for displaying a second prompt message on a first client, according to an embodiment of this application. Figure 12 This paper shows a connection block diagram of a data transfer device applied to a first server according to an embodiment of this application; Figure 13 This paper shows a connection block diagram of a data transfer device applied to a first client according to an embodiment of this application; Figure 14 A structural block diagram of an electronic device for performing the methods of embodiments of this application is shown. Detailed Implementation

[0024] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0025] To facilitate understanding of this solution, a few concepts will be briefly introduced below: Facial recognition is a biometric technology that identifies individuals based on their facial features. It involves using cameras or webcams to capture images or video streams containing faces, automatically detecting and tracking faces in the images, and then identifying the detected faces.

[0026] Facial recognition payment: This is mainly based on facial recognition technology. By obtaining facial information, it identifies the user whose identity is linked to the facial information. Users do not need to input other information, and the payment is completed based on the identified user identity information.

[0027] Data transfer refers to transferring a certain type of data from one client account to another client account. For example, transferring transaction amounts obtained from the clicks and likes of videos and articles published by users of a video playback client or content interaction client to a payment application client or a client with payment application functionality. Another example is transferring transaction amounts obtained from the monetization of rewards (such as gold coins) generated in a game client to a payment application client or a client with payment application functionality. Yet another example is transferring assets from an account associated with one payment application client or a client with payment application functionality to another payment application client or another client with payment application functionality.

[0028] Client-side applications refer to various applications installed on electronic devices, such as payment applications, messaging applications, video playback applications, content interaction platform applications, and game applications.

[0029] Currently, electronic devices (such as mobile phones, laptops, and tablets used for information display and data interaction) are widely available on the market. These devices consist of a display screen and a processor. The display screen shows images and text, and when it's a touchscreen, it also receives user touch input. The processor runs various applications to perform different functions. For example, electronic devices can typically be used for video playback and information interaction through installed clients. Because of their comprehensive functionality, they are widely loved by consumers.

[0030] In certain application use cases, it involves transferring data from a user's application account. For example, in video playback applications or content interaction platform applications, users need to transfer the monetary value earned from clicks and likes on their published videos and articles. Similarly, in game applications, users need to transfer the monetary value earned from in-game rewards (such as in-game currency). For trading clients or applications with trading functions, asset transfers are required when users need to pay for shopping, transportation, or money transfers. In short, all of the above data transfer processes involve transferring data from one client's account to another client.

[0031] The inventors discovered through research that currently, data transfer typically requires the cooperation of multiple servers to complete the transfer operation. However, the data transfer process takes a long time, resulting in a long waiting time for users to receive the final data transfer results, which causes inconvenience to users.

[0032] Based on this, the inventors provide a data transfer method applied to a first server. The method includes: obtaining the data transfer value generated by the first client in response to a data transfer operation to a second client, and the remaining data value of the first client's account before responding to the data transfer operation; if the data transfer value is not greater than the remaining data value, generating a first prompt message and sending the first prompt message to the first client, the first prompt message indicating that the data transfer was successful; sending a data transfer request to the second server, instructing the second server to transfer the data transfer value from the account containing the first data transfer identifier to the account containing the second data transfer identifier, the data transfer request carrying the first data transfer identifier of the first client, the second data transfer identifier of the second client, and the data transfer value, at least one of the first and second data transfer identifiers corresponding to a bank code; if the second server receives a successful data transfer result based on the data transfer request, sending a second prompt message to the first client, the second prompt message including the successful data transfer result. By adopting the above method, after performing a data transfer operation, the first prompt message indicating successful data transfer can be obtained quickly, avoiding the inconvenience caused to users by having to wait for a long time for the second prompt message.

[0033] like Figure 1 As shown in the diagram, this application provides a system architecture diagram of a data transfer system, wherein the data transfer system includes a first server, a second server, a first client, and a second client, wherein the first client and the second client can be installed on the same terminal device or on different terminal devices. Figure 1 A schematic diagram showing the first client and the second client installed on different terminal devices is shown.

[0034] The first client can be an instant messaging client, a payment application client, a video playback client, a content interaction client, or any client with the function of transferring data in its account (such as a client with functions such as transfer or withdrawal). The second client can be a bank client, an instant messaging client, a payment application client, or any client with the function of transferring data to another account (such as a client with payment receiving function). The types of the first client and the second client can be different.

[0035] The terminal device can be any device capable of installing a client, such as a smartphone, tablet, or laptop, or even a desktop computer or television. The terminal device and the server can be connected via a network; that is, the network serves as the medium providing communication links between the terminal device and the first server, and between the first server and the second server. For example, the terminal device can communicate through a client installed on it. The network can include various connection types, such as wired communication links, wireless communication links, etc.

[0036] It should be understood that Figure 1 The number of networks, first servers, and second servers shown is merely illustrative. Depending on implementation needs, there can be any number of networks, first servers, and second servers. For example, the first and second servers could each be server clusters composed of multiple servers.

[0037] In use Figure 1When the data transfer system shown performs a data transfer operation, the first client responds to the data transfer operation to the second client (e.g., by displaying a data transfer identification code on the first client, and then having the second client scan the code to perform the data transfer). The first client then obtains the remaining data value of its account before responding to the data transfer operation and sends it to the first server. The first server receives the data transfer value generated by the first client in response to the data transfer operation to the second client, and obtains the remaining data value of the first client's account (e.g., by receiving the data transfer value sent to the first server by the second client after scanning the data on the first client). The first server also generates a first notification message if the transferred data value is not greater than the remaining data value, and sends this message to the first client. The first notification message indicates successful data transfer, so that the first client displays this message to the user upon receiving it. The first server is also configured to send a data transfer request to the second server. This data transfer request carries a first data transfer identifier of the first client, a second data transfer identifier of the second client, and a data transfer value. At least one of the first and second data transfer identifiers corresponds to a bank code. Upon receiving the data transfer request, the second server, in response to the request, transfers the data transfer value from the account containing the first data transfer identifier to the account containing the second data transfer identifier. Upon successful transfer, the second server sends a successful data transfer result back to the first server. The first server is also configured to send a second notification message to the first client upon receiving the successful data transfer result from the second server. This second notification message includes the successful data transfer result. Upon receiving the second notification message, the first client can display this second notification message to the user.

[0038] By adopting the above-mentioned data transfer system, the first server can confirm that the remaining data value of the first client's account is greater than the data transfer value, that is, when the first client's account can transfer the data transfer value to the second client, and then return the result of successful data transfer. There is no need to wait for the data transfer to be successful before returning the result, which effectively saves the time users spend waiting for the data transfer result. Thus, it avoids the inconvenience caused to users by having to wait for a long time for the data transfer result to be successful.

[0039] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0040] Please see Figure 2 , Figure 2 The image shows a data transfer method proposed in an embodiment of this application. This method can be applied to, for example... Figure 1 The first server shown includes the following methods: Step S110: Obtain the data transfer value generated by the first client in response to the data transfer operation to the second client, and the remaining data value of the first client's account before responding to the data transfer operation.

[0041] The data transfer operation can be an operation whereby a user inputs a data transfer value through a data transfer interface; it can also be an operation where a second client scans a first data transfer identification code displayed by a first client to transfer data to the second client; it can also be a user-initiated monetization operation based on clicks or likes initiated by the first client; or it can be a point monetization operation initiated by the first client, or the sale or monetization of game experience points, coins, or virtual items, etc. Correspondingly, the data transfer value can be an amount. The first client can be a payment application client, a video playback client, an information interaction client, or a game client, etc. The first server can be the backend server corresponding to the first client, and the second client can be a payment application client or a client with transfer or transaction functions. The second server refers to the server used to transfer the amount from the first client's account to the second client's account. In this embodiment, the second server can be a server different from the first server.

[0042] As one possible implementation method, the data transfer value generated by the first client in response to the data transfer operation to the second client can be obtained by: generating a first data transfer identification code and feeding it back to the first client in response to the second data transfer identification code acquisition request sent by the first client; and obtaining the data transfer value fed back by the second client after scanning the first data transfer identification code displayed by the first client.

[0043] In this implementation, the second data transfer identification code acquisition request may carry the user identity information of the user to which the first client belongs or the identification information of the first client. When the first server receives the second data transfer identification code acquisition request, it can respond to the request by generating a first data transfer identification code based on the user identity information of the user to which the first client belongs or the identification information of the first client. The first data transfer identification code may be a QR code, barcode, number, or any identification code that can uniquely represent user identity information or the first client. It should be understood that in this implementation, the first data transfer identification code may be one-time use, and the first data transfer identification code generated each time in response to a data transfer operation will be updated.

[0044] The specific method for obtaining the data transfer value fed back by the second client is as follows: After scanning the first data transfer identification code, the second client sends the identification code to the backend server corresponding to the second client, and also sends the data transfer value input by the second client to the backend server corresponding to the second client. It should be understood that if the backend server corresponding to the second client is the first server, then the backend server has completed obtaining the data transfer value upon receiving the data transfer value sent by the second client. If the backend server is different from the first server, the backend server verifies and matches the first data transfer identification code. If the verification and matching are successful, the backend server sends the data transfer value corresponding to the first client to the first server. The first server has completed obtaining the data transfer value upon receiving the data transfer value sent by the backend server of the second client.

[0045] The data transfer value can be pre-entered by the second client before scanning the second data transfer identification code, or it can be entered by the second client after scanning the first data transfer identification code. It should be understood that if the data transfer value is an amount, then the first data transfer identification code displayed by the first client is specifically the payment code corresponding to the first client. If the data transfer value is data such as gold coins, stocks, or experience points, then the first data transfer identification code is an identification code for transferring the aforementioned data to another client (the second client).

[0046] Alternatively, the data transfer value generated by the first client in response to the data transfer operation to the second client can also be obtained by: obtaining the data transfer value input by the user based on the data transfer interface received by the first client, whereby the data transfer interface is generated by the first client scanning the second data transfer identification code corresponding to the second client in response to the user-triggered scanning operation.

[0047] In this implementation, if the data transfer value is an amount, the second data transfer identification code can be the payment code corresponding to the second client; if the data transfer value is data such as gold coins, stocks, or experience points, the first data transfer identification code is the identification code for the second client to receive the data transferred by other clients (such as the first client).

[0048] Another approach is to obtain the data transfer value input by the user based on the data transfer interface received by the first client. The data transfer interface is generated by the data transfer operation triggered by the first client in response to the identification information of the second client selected or input by the user (the identification information can be at least one of bank account, payment application client account, user name, etc.).

[0049] It should also be noted that the remaining data value specifically refers to the data value in the account of the first client before the data transfer value is deducted from the account data in the first client in response to the data transfer operation. In other words, obtaining the remaining data value of the first client's account before responding to the data transfer operation specifically means obtaining the data value in the account of the first client before the remaining data value is deducted from the account in response to the data transfer operation.

[0050] It should be understood that the remaining data value in the first client's account can be stored in the first server or a storage device associated with the server. Accordingly, the first server can obtain the remaining data value of the first client's account in the following ways: When responding to a data transfer operation, the first client can send a data transfer request including its client identifier to the service. Upon receiving the data transfer request, the first server can obtain the remaining data value of the first client's account in response, based on the client identifier in the data transfer request. Alternatively, the remaining data value in the first client's account can also be obtained by the first client and then sent to the server; that is, the first client can respond to a data transfer operation by obtaining the remaining data value of its account before responding to the data transfer operation and sending it to the server.

[0051] Step S120: If the transferred data value is not greater than the remaining data value, generate a first prompt message and send the first prompt message to the first client. The first prompt message is used to notify the user that the data transfer was successful.

[0052] It should be noted that if the transferred data value is not greater than the remaining data value, it means that the remaining data value in the first client's account is sufficient to transfer the transferred data value to the second client. That is, even if the first client is linked to a payment account, and the remaining data value in the payment account is insufficient to transfer the transferred data value to the second client, the transferred data value can still be transferred to the second client using the remaining data value in the first client's account.

[0053] Furthermore, if the account corresponding to the first client used to transfer the data transfer value or the account corresponding to the second client used to receive the data transfer value is a bank account, the specific process of executing the data transfer is usually performed by the UnionPay or NetsUnion server. This process can be time-consuming. The first server generates a first notification message when the transferred data value is no greater than the remaining data value and sends this message to the first client. This allows users to quickly learn the data transfer result without having to wait a long time for the second server to return a successful data transfer result to the first server, and then for the first server to return a notification message including this successful data transfer result to the first client.

[0054] That is, by adopting the above step S120, when the first client receives the first prompt information, the user can exit the data transfer interface to perform other operations or information interactions, which greatly improves the convenience of the user when transferring data.

[0055] Step S130: Send a data transfer request to the second server, instructing the second server to transfer the data transfer value from the account where the first data transfer identifier is located to the account where the second data transfer identifier is located.

[0056] The data transfer request carries a first data transfer identifier, a second data transfer identifier, and a data transfer value. The first data transfer identifier corresponds to the first client, and the second data transfer identifier corresponds to the second client. At least one of the accounts containing the first data transfer identifier and the second data transfer identifier has an account type that is different from the account type of the first client.

[0057] It should be noted that if either the account containing the first data transfer identifier or the account containing the second data transfer identifier has a different account type than the account of the first client, the transfer cannot be executed directly by the first server and must be executed by a separate server, namely the second server.

[0058] For example, if the first data transfer identifier or the second data transfer identifier includes a bank code, then the account used to transfer the data transfer value in the first client or the account used to receive the data transfer value in the second client is a bank account or an online banking account, and the corresponding transfer operation is executed by the bank server.

[0059] The first data transfer identifier is used to identify the account in the first client used for data transfer. The account in the first client used for data transfer can be the account of the first client or the account bound to the first client. Taking data transfer as a transfer or payment as an example, the account bound to the first client can be the bank card account or online banking account bound to the first client.

[0060] If the first client corresponds to multiple accounts, that is, if the accounts corresponding to the first client include the account of the first client and the accounts bound to the first client, the first data transfer identifier can be obtained according to the data transfer priority order of the accounts corresponding to the first client. For example, taking a payment application client as the first client, if the payment application client corresponds to three accounts: the account of the payment application client (i.e., the balance account), the first bank account bound to the payment client, and the second bank account bound to the payment client, with the priority order being the first bank account, the balance account, and the second bank account, then when the first server sends a data transfer request to the second server, it can first obtain the identifier information corresponding to the first bank account based on the data transfer priority order of the payment application client.

[0061] The second data transfer identifier can be used to represent the account identifier receiving the data transfer value. The second data transfer identifier can be obtained by the first client when performing the data transfer operation, or by the first server, or by the second server.

[0062] In one possible implementation, the method for obtaining the data transfer value generated by the first client in response to the data transfer operation to the second client is as follows: in response to the second data transfer identification code acquisition request sent by the first client, a first data transfer identification code is generated and fed back to the first client; the data transfer value fed back by the second client after scanning the first client and displaying the first data transfer identification code is obtained.

[0063] In this system, after scanning the data identification code displayed by the first client, the second client can send a first data transfer identification code to either the backend server corresponding to the second client or to the first server. Simultaneously, it can also send a second data transfer identifier corresponding to the second client back to the first server. Therefore, when the first server receives the second data transfer identification code sent by the second client, it can obtain the second data transfer identifier and, upon obtaining the second data transfer identifier, can send a data transfer request including the second data transfer identifier to the second server.

[0064] In another possible implementation, if the acquisition of the data transfer value generated by the first client in response to the data transfer operation to the second client specifically involves: acquiring the data transfer value input by the user based on the data transfer interface received by the first client, where the data transfer interface is generated by the first client scanning the second data transfer identification code corresponding to the second client in response to a user-triggered scanning operation, then the second data transfer identifier is obtained by the first client when scanning the second data transfer identification code corresponding to the second client and sent to the server. Accordingly, the first server can send a data transfer request to the second server including the first data transfer identifier, the second data transfer identifier, and the data transfer value.

[0065] Similarly, if the data transfer interface is generated by a data transfer operation triggered by the first client in response to the user's selection or input of the second client's identification information (which can be at least one of a bank account, payment application client account, username, etc.), then the corresponding second data transfer identifier of the second client can be obtained by the first client based on the selected or input second client's identification information and sent to the server. Correspondingly, the first server can also send a data transfer request to the second server, including the first data transfer identifier, the second data transfer identifier, and the data transfer value.

[0066] Upon receiving a data transfer request, the second server can respond by transferring the data transfer value from the account corresponding to the first data transfer identifier to the account corresponding to the second data transfer identifier.

[0067] It should be understood that if the first data transfer identifier corresponds to data transfer discount information, then when the second server receives the data transfer request, it can respond to the data transfer request by processing the data transfer value based on the data transfer discount information and the actual data transfer value obtained by processing the data transfer value based on the data transfer discount information, and transfer the actual data transfer value from the account corresponding to the first data transfer identifier to the account corresponding to the second data transfer identifier.

[0068] It should be understood that if the data transfer value is specifically the transfer amount, then the data transfer discount information can be a minimum purchase requirement or a discount based on the amount. For example, a discount of 2 yuan off for purchases over 100 yuan, a discount of 40 yuan off for purchases over 300 yuan, or a 10% discount for purchases over 300 yuan, etc.

[0069] When the second server transfers the data transfer value from the account corresponding to the first data transfer identifier to the account corresponding to the second data transfer identifier, if the transfer is successful, the second server can send a message to the first server indicating that the data transfer was successful. Conversely, if the transfer fails, the second server can send a message to the first server indicating that the data transfer failed.

[0070] Step S140: If the data transfer success result is obtained from the second server based on the data transfer request, a second prompt message is sent to the first client, which includes the data transfer success result.

[0071] It should be understood that if the first data transfer identifier corresponds to data transfer discount information, the obtained data transfer success result includes the data transfer discount information and the actual data transfer value obtained by processing the data transfer value based on the data transfer discount information.

[0072] Correspondingly, the second notification will also include the aforementioned data transfer discount information and the actual data transfer value. Users can then obtain this information based on the actual data transfer value and data transfer discount.

[0073] To facilitate users in viewing the type of account in the account corresponding to the first client where data transfer has occurred, the first server is also used to obtain the account type of the account in the account corresponding to the first client that transferred the data transfer value, and send a second prompt message to the first client including the data transfer success result and the account type.

[0074] In another implementation, if the first server receives a data transfer failure result from the second server based on the data transfer request, it can be determined that the amount of data in the account corresponding to the first data transfer identifier is insufficient to pay the data transfer value. Therefore, it is necessary to change the account corresponding to the first client in order to perform the data transfer again.

[0075] In this approach, the first server can change the account used for data transfer corresponding to the first client in one of the following ways: First, it can select the next account adjacent to the account containing the first data transfer identifier, based on the priority of the accounts corresponding to the first client from highest to lowest, and then use the data transfer identifier corresponding to that next account as the new first data transfer identifier. Alternatively, it can use the first client's account as the account used for data transfer and use the data transfer identifier corresponding to that first client's account as the new first data transfer identifier.

[0076] If at least one of the accounts containing the new first data transfer identifier and the second data transfer identifier has an account type different from the account type of the first client, then the first server, upon obtaining the new first data transfer identifier, can return to execute step S130. It should be understood that if the account corresponding to the new first data transfer identifier is the account of the first client, the second server can complete the data transfer and return a successful data transfer result; if the account corresponding to the new first data transfer identifier is an account associated with the first client (bank account or online banking account), the second server may complete the data transfer and return a successful data transfer result, or it may fail to transfer the data and return a failed data transfer result. If a failed data transfer result is returned, the server will again obtain the next account adjacent to the account containing the first data transfer identifier according to the priority of each account corresponding to the first client from high to low, and return to execute step S130 until the account corresponding to the new first data transfer identifier is obtained and is the account of the first client, at which point the data transfer can be completed.

[0077] It should be noted that if the account corresponding to the new first data transfer identifier is the account of the first client, that is, the account corresponding to the new first data transfer identifier is of the same type as the account of the first client, the account corresponding to the second data transfer identifier may be of the same or different type as the account of the first client. If they are different, the same steps as S130 above can be performed to complete the data transfer.

[0078] If the account types of the new first data transfer identifier account and the second data transfer identifier account are the same as the account type of the first client account, the method further includes: transferring the data transfer value from the data remaining value of the first client account to the account of the second data transfer identifier of the second client, and generating a data transfer success result.

[0079] By employing the data transfer method of this application, the first server obtains the data transfer value generated by the first client in response to the data transfer operation to the second client, and the remaining data value of the first client's account before responding to the data transfer operation. If the data transfer value is not greater than the remaining data value, the first server generates a first notification message to inform the user that the data transfer is successful and sends it to the first client. The server then sends a data transfer request to the second server, instructing the second server to transfer the data transfer value from the account containing the first data transfer identifier to the account containing the second data transfer identifier. If the second server returns a successful data transfer result, the server sends a second notification message to the first client. This method allows the user to perform other operations on the client after executing a data transfer operation. This avoids the inconvenience caused by waiting a long time for the second server to return a second notification message after the data transfer is completed.

[0080] Please see Figure 3 Another embodiment of this application provides a data transfer method, which is applied to a first client and includes: Step S210: In response to the data transfer operation to the second client, send the identification information of the first client to the first server, so that the first server can obtain the remaining data value of the first client's account before responding to the data transfer operation based on the identification information of the first client, and send a data transfer request including the data transfer value to the second server.

[0081] The data transfer value is obtained based on the data transfer operation initiated to the second client.

[0082] The data transfer operation to the second client can be a voice operation, a selection operation to choose the second client from the client list corresponding to the first client, or an operation to show the second client a first data transfer identification code so that the second client can scan the first data transfer identification code, or an operation to scan the second client's second data transfer identification code.

[0083] In one possible implementation, in response to a data transfer operation to a second client, the identification information of the first client is sent to the first server so that the first server can obtain the remaining data value of the first client's account before responding to the data transfer operation based on the identification information of the first client. Specifically, in response to a data transfer request, the user's identity authentication information is collected, and the identity authentication information and the identification information of the first client are sent to the first server so that the server can authenticate the identity authentication information and obtain the remaining data value of the first client's account before responding to the data transfer operation based on the identification information of the first client when the authentication is successful.

[0084] The data transfer request is obtained based on user actions, such as triggering a data transfer control on the first client, or based on voice messages or gestures from the user. The server or its associated storage device may store the remaining data value of the first client's account. This remaining data value represents the transferable data value in the first client's account before responding to the data transfer operation. When the data transfer value is an amount, the specific transferable data value in the account is the transferable amount.

[0085] User authentication information can be biometric information such as facial recognition, voiceprint, and fingerprint, or it can be a verification code composed of subtitles and numbers, or even gesture tracking, etc. The first server can authenticate the received authentication information based on preset authentication information.

[0086] Since the data transfer operations used by the first client to transfer data to the second client are different, the way the data transfer value is obtained is also different. It can be obtained by the first client, or by the first server or the second client, etc. No specific limitation is made here.

[0087] In one possible implementation, the data transfer value can be obtained as follows: in response to a data transfer operation to a second client, the first client sends its identification information to the first server; in response to a user-triggered scanning operation, the first client scans the second data transfer identification code corresponding to the second client to generate a data transfer interface; the first client receives the data transfer value input by the user based on the data transfer interface and sends the data transfer value to the server.

[0088] In this implementation, the aforementioned second data transfer identification code can be an image, QR code, barcode, or string, etc. It should be understood that when the data transfer value specifically refers to the transfer amount, the aforementioned second data transfer identification code is specifically a payment code. When the first client scans the payment code, the first client can send the payment code to the first server, so that the first server can identify the payment code and generate an interface (data transfer interface) for transferring funds to the second client's account and send it back to the first client, so that the first client can jump to and display the interface, so that the user can enter the transfer amount (data transfer value) into the interface. When the first client obtains the data transfer value, it can send the data transfer value to the first server.

[0089] In another possible implementation, the data transfer value can be obtained as follows: in response to the data transfer operation to the second client, the first client sends the identification information of the first client to the first server and then displays the first data transfer identification code fed back by the first server when the identity authentication information is successfully authenticated, so that the second client can feed back the data transfer value to the first server after scanning the first data transfer identification code.

[0090] When the identity authentication information is successfully authenticated, the first server sends a first data transfer identification code to the first terminal. This first data transfer identification code can be an image, a QR code, a barcode, or a string, etc. The specific implementation process of the second client sending the data transfer value back to the review server after scanning the first data transfer identification code can be found in the previous description of step S110, and will not be repeated here.

[0091] Step S220: Receive the first prompt message generated by the first server when the data transfer value is not greater than the remaining data value. The first prompt message is used to prompt the user that the data transfer was successful.

[0092] For a detailed description of the first prompt message, please refer to the previous description of step S120; it will not be repeated here.

[0093] Upon receiving the first notification message, the first client can display it on its interface. This first notification message may specifically include the data transfer value and a notification that the data transfer was successful.

[0094] Step S230: Receive the second prompt information from the first server. The second prompt information is generated by the first server when it receives the data transfer success result from the second server based on the data transfer request, or when the first server receives the data transfer failure result from the second server based on the data transfer request, and the first server transfers the data transfer value from the remaining data value of the first client's account to the account where the second data transfer identifier of the second client is located.

[0095] For a detailed description of the second prompt message, please refer to the previous descriptions of steps S230 and S240; they will not be repeated here.

[0096] It should be noted that when the first client receives the second prompt from the server, it can either display the second prompt directly or display it as a notification or a pop-up.

[0097] To facilitate user understanding of data transfer discount information during the data transfer process, in this embodiment, if the first data transfer identifier corresponds to data transfer discount information, the obtained successful data transfer result includes the data transfer discount information and the actual data transfer value obtained by processing the data transfer value based on the data transfer discount information. That is, the second prompt information may include the data transfer value and the data transfer discount information.

[0098] To help users understand the specific account that is transferring data, in this embodiment, the second prompt information returned by the first server includes the account type, which is the account type of the account that transferred the data transfer value in the account corresponding to the first client.

[0099] In one possible implementation of this application, after the first client receives the second prompt information from the first server, the method further includes: If the current display interface of the terminal where the first client is located is the first designated interface, then the system will jump to display the second designated interface. The first designated interface displays the first prompt message, and the second designated interface displays the second prompt message. If the current display interface of the terminal where the first client is located is not the first designated interface, then a notification or pop-up window will be displayed on the current display interface. The notification or pop-up window is used to indicate that the first client has received the second prompt message.

[0100] It should be understood that if the current display interface of the terminal where the first client is located is not the first designated interface, it indicates that the first client has exited the display interface of the first prompt message after receiving the first prompt message to perform other operations. That is, after receiving the first prompt message, the user can perform other operations, thereby effectively saving the user's waiting time for the data transfer result and improving the user's data transfer experience.

[0101] Specifically, the second notification information mentioned above may include one or more of the following: the actual value of the data transferred, the account type, and the data transfer discount information.

[0102] By adopting the above method, users can be informed that the data transfer has been completed.

[0103] The data transfer method applied to a first client in this application includes: in response to a data transfer operation to a second client, sending identification information of the first client to a first server, so that the first server obtains the remaining data value of the first client's account before responding to the data transfer operation based on the identification information of the first client; sending a data transfer request including a data transfer value to a second server, wherein the data transfer value is received based on the data transfer operation initiated to the second client; receiving a first prompt message generated by the first server when the data transfer value is not greater than the remaining data value, the first prompt message being used to prompt the user that the data transfer was successful; and receiving a second prompt message fed back by the first server, the second prompt message being generated by the first server when receiving a data transfer success result fed back by the second server based on the data transfer request, or when the first server receives a data transfer failure result fed back by the second server based on the data transfer request, and the first server transfers the data transfer value from the remaining data value of the first client's account to the account where the second data transfer identifier of the second client is located. This allows the server to return a successful data transfer result to the first client as soon as it confirms that the remaining data value in the first client's account is greater than the data transfer value, meaning the first client's account can transfer the data transfer value to the second client. This allows the user to view the result without having to wait for the data transfer to be successfully completed before returning the result to the first client. This effectively saves the time users spend waiting for the data transfer result and avoids the inconvenience caused by having to wait for a long time for the data transfer result to be completed.

[0104] Please refer to the following: Figure 4 and Figure 5 This application also provides a data transfer method, which is applied to a data transfer system including a first client, a second client, a first server, and a second server. The method is illustrated using the example of a payment application client as the first client, a merchant POS terminal as the second client, a backend server for the payment application client as the first server, and a UnionPay server as the second server. When a user transfers funds from the payment application client to the merchant POS terminal, the specific transfer method is as follows: Step S310: The payment application client responds to the user's transfer operation by obtaining the user's identity authentication information and sends a transfer request, including the payment application client's identification information and identity authentication information, to the backend server.

[0105] The identity authentication information includes passwords, biometric information (such as face, fingerprint or voiceprint, etc.) or gesture trajectory, etc.

[0106] like Figure 6 As shown, in this embodiment, the user can trigger the facial recognition payment control A in the payment application client to activate the camera of their terminal and capture the user's facial image, as shown below. Figure 7 The system sends a transfer request, including the facial image and the identification information of the payment application client, to the backend server using the facial image shown in Figure B.

[0107] It should be understood that the aforementioned facial recognition operation can be performed not only by the backend server but also by the terminal where the payment application client is located. If it is performed by the terminal where the payment application client is located, the terminal can display the following after the facial recognition is successful: Figure 8 The interface shown in the image sends a transfer request, including the identification information of the payment application client, to the backend server when the user triggers the payment confirmation control C.

[0108] After the payment application client sends the transfer request to the backend server, it can display something like this: Figure 9 The interface shown allows users to wait for the backend server to return a result before exiting the interface. For example, if the payment application client does not receive a payment result from the backend server 15 seconds after sending a transfer request, the user can exit the payment interface using the close control D.

[0109] Step S320: The backend server responds to the transfer request by authenticating the identity information, and after successful authentication, sends a payment identification code to the payment application client, and obtains the remaining amount in the payment application client's account before responding to the transfer request based on the identification information.

[0110] Step S330: When the payment application client receives the payment identification code, it displays the payment identification code.

[0111] Step S340: The merchant's POS terminal scans the payment code displayed on the payment application client to send a payment order, including the account corresponding to the POS terminal and the payment amount, to the backend server.

[0112] The payment amount can be the amount pre-entered before the merchant's POS terminal scans the payment code displayed in the payment application client, or the amount entered in the payment interface generated after the merchant's POS terminal scans the payment code displayed in the payment application client. It can be set according to actual needs.

[0113] Step S350: After receiving a payment order, if the backend server determines that the payment amount in the payment order is not greater than the remaining amount in the payment application client's account, it generates a first prompt message and sends it back to the payment application client.

[0114] The first notification message is used to inform the user that the payment was successful.

[0115] like Figure 10 As shown, if the payment amount is 30 yuan and the remaining balance in the payment application client's account is no less than 30 yuan, a first notification message including the payment success result and the payment amount can be generated. After receiving the first notification message, the user can trigger... Figure 10 The interface shown includes a close / exit control for performing other operations.

[0116] Step S360: The backend server sends a payment request to the UnionPay server based on the payment order and the payment account corresponding to the payment application client.

[0117] The payment request includes a first data transfer identifier for identifying the account used for payment corresponding to the payment application client, a second data transfer identifier for the account corresponding to the second client, and the payment amount.

[0118] Step S370: When UnionPay server receives a payment request, it transfers the payment amount from the account containing the first data transfer identifier to the account containing the second data transfer identifier in response to the payment request, and returns the payment result to the backend server.

[0119] Specifically, if the UnionPay server successfully transfers the payment amount, it will report the payment success result to the platform server; if the UnionPay server fails to transfer the payment amount, it will report the payment failure result to the platform server.

[0120] If the first data transfer identifier or the second data transfer identifier corresponds to payment discount information, the above steps may specifically be as follows: When the UnionPay server receives a payment request, it responds to the payment request by calculating the actual payment amount based on the payment discount information, and then transfers the actual payment amount from the account where the first data transfer identifier is located to the account where the second data transfer identifier is located.

[0121] Step S380: If the platform server receives a payment success result from the UnionPay server, it sends a second notification message to the payment application client.

[0122] The second notification includes the payment success result. It should be understood that if the first or second data transfer identifier corresponds to payment discount information, the transfer success result may also include the actual payment amount and payment discount information. For an example, please refer to [link to example]. Figure 11 As shown, if the payment amount is 30 yuan (the original price is 30 yuan) and the payment discount information is a discount of 2 yuan for purchases over 10 yuan, then a second prompt information including the actual payment amount, payment discount information and the original price can be generated.

[0123] In addition, to make it easier for users to view the payment account corresponding to the payment application client, the second prompt message may also include the specific payment account.

[0124] If the platform server receives a payment failure result from the UnionPay server, it can select the payment account corresponding to the payment application client again. If at least one of the selected payment accounts or the account corresponding to the merchant POS terminal has an account type different from the payment client's account type, the platform server will send a payment request to the UnionPay server based on the payment order and the selected payment account corresponding to the payment application client again, and execute steps S360 to S370.

[0125] If the selected payment account and the account corresponding to the merchant POS terminal are of the same type as the payment client's account, that is, if the selected payment account is the payment client's account, then the payment amount will be transferred from the remaining amount in the payment client's account to the account corresponding to the merchant POS terminal, and a payment success result will be generated.

[0126] Please see Figure 12 This application provides a data transfer device 400, which is applied to, for example... Figure 1 The first server shown, device 400, includes a data acquisition module 410, a prompt message generation module 420, a request sending module 430, and a prompt message sending module 440.

[0127] The data acquisition module 410 is used to acquire the data transfer value generated by the first client in response to the data transfer operation to the second client, and the remaining data value of the first client's account before responding to the data transfer operation; the prompt message generation module 420 is used to generate a first prompt message and send it to the first client if the data transfer value is not greater than the remaining data value, and the first prompt message is used to prompt the user that the data transfer is successful; the request sending module 430 is used to send a data transfer request to the second server, instructing the second server to transfer the data transfer value from the account where the first data transfer identifier is located to the account where the second data transfer identifier is located, the data transfer request carries the first data transfer identifier and the data transfer value, the first data transfer identifier corresponds to the first client, the second data transfer identifier corresponds to the second client, and at least one of the accounts where the first data transfer identifier is located and the second data transfer identifier is located has an account type that is different from the account type of the first client's account; the prompt message sending module 440 is used to send a second prompt message to the first client if the data transfer success result is received from the second server based on the data transfer request, the second prompt message includes the data transfer success result.

[0128] In one possible implementation, the data acquisition module 410 is further configured to respond to a second data transfer identification code acquisition request sent by the first client, generate a first data transfer identification code and feed it back to the first client; and acquire the data transfer value fed back by the second client after scanning the first data transfer identification code displayed by the first client.

[0129] In another possible implementation, the data acquisition module 410 is further configured to acquire the data transfer value input by the user based on the data transfer interface received by the first client. The data transfer interface is generated by the first client scanning the second data transfer identification code corresponding to the second client in response to the user-triggered scanning operation.

[0130] In one possible implementation, if the account containing the first data transfer identifier is not the account of the first client, and the account type of the account containing the second data transfer identifier is the same as the account type of the first client's account, the device 400 further includes a data transfer module, which is used to transfer the data transfer value from the remaining data value of the first client's account to the account containing the second data transfer identifier of the second client and generate a data transfer success result when the second server receives a data transfer failure result indicating that the data transfer value was transferred from the account containing the first data transfer identifier to the account containing the second data transfer identifier based on a data transfer request.

[0131] In one possible implementation, the prompt message sending module 440 is further configured to obtain the account type of the account in the account corresponding to the first client that transferred the data transfer value, and send a second prompt message to the first client including the data transfer success result and the account type.

[0132] In one possible implementation, if the first data transfer identifier corresponds to data transfer discount information, the obtained data transfer success result includes the data transfer discount information and the actual data transfer value obtained by processing the data transfer value based on the data transfer discount information.

[0133] Please see Figure 13 This application embodiment also provides an application for, for example Figure 1 The data transfer device 500 shown for the first client includes: an identification information sending module 510, a first prompt information receiving module 520, and a second prompt information receiving module 530.

[0134] The identification information sending module 510 is used to send the identification information of the first client to the first server in response to the data transfer operation to the second client, so that the first server can obtain the remaining data value of the first client's account before responding to the data transfer operation based on the identification information of the first client, and send a data transfer request including the data transfer value to the second server. The data transfer value is obtained based on the data transfer operation initiated to the second client. The first prompt information receiving module 520 is used to receive the first prompt information generated by the first server when the data transfer value is not greater than the remaining data value. The first prompt information is used to prompt the user that the data transfer is successful. The second prompt information receiving module 530 is used to receive the second prompt information fed back by the first server. The second prompt information is generated by the first server when it receives the data transfer success result fed back by the second server based on the data transfer request, or when the first server receives the data transfer failure result fed back by the second server based on the data transfer request, and the first server transfers the data transfer value from the remaining data value of the first client's account to the account where the second data transfer identifier of the second client is located.

[0135] In one possible implementation, the identification information sending module 510 is further configured to, in response to a data transfer request, collect the user's identity authentication information, and send the identity authentication information and the identification information of the first client to the first server, so that the server can authenticate the identity authentication information, and obtain the remaining data value of the first client's account before responding to the data transfer operation based on the identification information of the first client when the authentication is successful.

[0136] In one possible implementation, the data transfer device 500 further includes a data transfer value acquisition module, which is used to scan the second data transfer identification code corresponding to the second client to generate a data transfer interface in response to a user-triggered scanning operation; receive the data transfer value input by the user based on the data transfer interface; and send the data transfer value to the first server.

[0137] In one possible implementation, the data transfer device 500 further includes an identification code display module, which is used to display a first data transfer identification code fed back by the first server when the identity authentication information is successfully authenticated, so that the second client can feed back the data transfer value to the first server after scanning the first data transfer identification code.

[0138] In one possible implementation, the data transfer device 500 further includes a prompt information display module, configured to, if the current display interface of the terminal where the first client is located is a first designated interface, jump to display a second designated interface, the first designated interface displaying a first prompt information and the second designated interface displaying a second prompt information; if the current display interface of the terminal where the first client is located is not the first designated interface, display a notification or pop-up window on the current display interface, the notification or pop-up window being used to indicate that the first client has received the second prompt information.

[0139] It should be noted that the device embodiments in this application correspond to the aforementioned method embodiments. The specific principles in the device embodiments can be found in the content of the aforementioned method embodiments, and will not be repeated here.

[0140] The following will combine Figure 14 This application provides a description of an electronic device 100.

[0141] Please see Figure 14 Based on the data transfer method provided in the above embodiments, this application also provides another electronic device 100 including a processor 102 capable of executing the aforementioned method. The electronic device 100 may be a server 10 or a terminal device. The terminal device may be a smartphone, tablet computer, computer, or portable computer, etc., which may install a first client and / or a second client.

[0142] The electronic device 100 also includes a memory 104. The memory 104 stores a program that can execute the contents of the foregoing embodiments, and the processor 102 can execute the program stored in the memory 104.

[0143] The processor 102 may include one or more cores for data processing and message matrix units. The processor 102 connects to various parts within the electronic device 100 using various interfaces and lines, and performs various functions and processes data by running or executing instructions, programs, code sets, or instruction sets stored in the memory 104, and by calling data stored in the memory 104. Optionally, the processor 102 may be implemented using at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). The processor 102 may integrate one or more of the following: Central Processing Unit (CPU), Graphics Processing Unit (GPU), and modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the displayed content; and the modem handles wireless communication. It is understood that the modem may also not be integrated into the processor 102 and may be implemented separately using a communication chip.

[0144] The memory 104 may include random access memory (RAM) or read-only memory (ROM). The memory 104 can be used to store instructions, programs, code, code sets, or instruction sets. The memory 104 may include a program storage area and a data storage area. The program storage area may store instructions for implementing an operating system, instructions for implementing at least one function, instructions for implementing the various method embodiments described below, etc. The data storage area may also store data acquired by the electronic device 100 during use.

[0145] The electronic device 100 may also include a network module and a screen. The network module is used to receive and transmit electromagnetic waves, converting electromagnetic waves into electrical signals, thereby enabling communication with communication networks or other devices, such as audio playback devices. The network module may include various existing circuit elements used to perform these functions, such as antennas, radio frequency transceivers, digital signal processors, encryption / decryption chips, SIM cards, memory, etc. The network module can communicate with various networks such as the Internet, corporate intranets, and wireless networks, or communicate with other devices via wireless networks. The aforementioned wireless networks may include cellular telephone networks, wireless local area networks, or metropolitan area networks. The screen can display interface content and facilitate data interaction.

[0146] In some embodiments, the electronic device 100 may further include a peripheral interface 106 and at least one peripheral device. The processor 102, memory 104, and peripheral interface 106 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral interface via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of the following: a radio frequency component 108, a positioning component 112, a camera 114, an audio component 116, a display screen 118, and a power supply 122. Peripheral interface 106 can be used to connect at least one I / O (Input / Output) related peripheral device to processor 102 and memory 104. In some embodiments, processor 102, memory 104 and peripheral interface 106 are integrated on the same chip or circuit board; in some other embodiments, any one or two of processor 102, memory 104 and peripheral interface 106 can be implemented on separate chips or circuit boards, and this application embodiment does not limit this.

[0147] The radio frequency (RF) component 108 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The RF component 108 communicates with communication networks and other communication devices via electromagnetic signals. The RF component 108 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. Optionally, the RF component 108 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc. The RF component 108 can communicate with other terminals via at least one wireless communication protocol. This wireless communication protocol includes, but is not limited to: the World Wide Web, metropolitan area networks, intranets, various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and / or WiFi (Wireless Fidelity) networks. In some embodiments, the RF component 108 may also include circuitry related to NFC (Near Field Communication), which is not limited in this application.

[0148] The positioning component 112 is used to locate the current geographical location of the electronic device 100 in order to enable navigation or LBS (Location Based Service).

[0149] Camera 114 is used to capture images or videos. Optionally, camera 114 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is located on the front panel of the electronic device 100, and the rear-facing camera is located on the back of the electronic device 100. In some embodiments, there are at least two rear-facing cameras, which are any one of a main camera, a depth-sensing camera, a wide-angle camera, and a telephoto camera, to achieve background blurring by fusion of the main camera and the depth-sensing camera, panoramic shooting by fusion of the main camera and the wide-angle camera, VR (Virtual Reality) shooting, or other fusion shooting functions. In some embodiments, camera 114 may also include a flash. The flash can be a single-color temperature flash or a dual-color temperature flash. A dual-color temperature flash refers to a combination of a warm light flash and a cool light flash, which can be used for light compensation at different color temperatures.

[0150] Audio component 116 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, and convert the sound waves into electrical signals that are input to processor 102 for processing, or input to radio frequency component 108 for voice communication. For stereo acquisition or noise reduction purposes, there may be multiple microphones, each located at a different part of electronic device 100. The microphone may also be an array microphone or an omnidirectional microphone. The speaker is used to convert electrical signals from processor 102 or radio frequency component 108 into sound waves. The speaker may be a conventional diaphragm speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can convert electrical signals not only into sound waves that humans can hear, but also into sound waves that humans cannot hear for purposes such as ranging. In some embodiments, audio component 114 may also include a headphone jack.

[0151] Display screen 118 is used to display a UI (User Interface). This UI may include graphics, text, icons, videos, and any combination thereof. When display screen 118 is a touch display screen, it also has the ability to collect touch signals on or above its surface. These touch signals can be input as control signals to processor 102 for processing. In this case, display screen 118 can also be used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard. In some embodiments, there may be one display screen 118, which serves as the front panel of electronic device 100; in other embodiments, there may be at least two display screens, respectively disposed on different surfaces of electronic device 100 or in a folded design; in still other embodiments, display screen 118 may be a flexible display screen, disposed on a curved or folded surface of electronic device 100. Furthermore, display screen 118 may be configured as a non-rectangular irregular shape, i.e., a non-rectangular screen. Display screen 118 may be made of materials such as LCD (Liquid Crystal Display) or OLED (Organic Light-Emitting Diode).

[0152] Power supply 122 is used to supply power to various components in electronic device 100. Power supply 122 can be alternating current, direct current, a disposable battery, or a rechargeable battery. When power supply 122 includes a rechargeable battery, the rechargeable battery can be a wired rechargeable battery or a wireless rechargeable battery. A wired rechargeable battery is a battery that is charged via a wired line, while a wireless rechargeable battery is a battery that is charged via a wireless coil. The rechargeable battery can also be used to support fast charging technology.

[0153] This application also provides a computer-readable storage medium. This computer-readable medium stores program code that can be called by a processor to execute the methods described in the above method embodiments.

[0154] Computer-readable storage media can be electronic storage devices such as flash memory, EEPROM (Electrically Erasable Programmable Read-Only Memory), EPROM, hard disk, or ROM. Optionally, computer-readable storage media includes non-transitory computer-readable storage medium. The computer-readable storage medium has storage space for program code that performs any of the method steps described above. This program code can be read from or written to one or more computer program products. The program code can be compressed, for example, in a suitable form.

[0155] This application also provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods described in the various optional implementations above.

[0156] In summary, this application provides a data transfer method, apparatus, device, and storage medium. The method includes: obtaining a data transfer value generated by a first client in response to a data transfer operation to a second client, and the remaining data value of the first client's account before responding to the data transfer operation; if the data transfer value is not greater than the remaining data value, generating a first prompt message to indicate successful data transfer to the user and sending it to the first client; sending a data transfer request to a second server, instructing the second server to transfer the data transfer value from the account containing the first data transfer identifier to the account containing the second data transfer identifier; and if a successful data transfer result is received from the second server, sending a second prompt message to the first client. This method allows the first server to return a successful data transfer result to the first client as soon as it confirms that the remaining data value of the first client's account is greater than the data transfer value, i.e., the first client's account can transfer the data transfer value to the second client. This allows the user to view the result without waiting for the data transfer to complete, effectively saving the user's waiting time and avoiding the inconvenience caused by prolonged waiting for successful data transfer results.

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

Claims

1. A data transfer method, characterized in that, Applied to a first server, the method includes: Obtain the data transfer value generated by the first client in response to the data transfer operation to the second client, and the remaining data value of the first client's account before responding to the data transfer operation; If the transferred data value is not greater than the remaining data value, a first prompt message is generated and fed back to the first client. The first prompt message is used to prompt the user that the data transfer was successful. A data transfer request is sent to a second server, instructing the second server to transfer the data transfer value from the account where the first data transfer identifier is located to the account where the second data transfer identifier is located. The data transfer request carries the first data transfer identifier, the second data transfer identifier, and the data transfer value. The first data transfer identifier corresponds to the first client, and the second data transfer identifier corresponds to the second client. At least one of the accounts where the first data transfer identifier is located and the account where the second data transfer identifier is located has an account type that is different from the account type of the first client. If the second server receives a successful data transfer result based on the data transfer request, a second notification message is sent to the first client, the second notification message including the successful data transfer result.

2. The data transfer method according to claim 1, characterized in that, Obtain the data transfer value generated by the first client in response to the data transfer operation to the second client, including: In response to the second data transfer identification code acquisition request sent by the first client, a first data transfer identification code is generated and fed back to the first client; Obtain the data transfer value returned by the second client after scanning the first client and displaying the first data transfer identification code.

3. The data transfer method according to claim 1, characterized in that, Obtain the data transfer value generated by the first client in response to the data transfer operation to the second client, including: The first client receives the data transfer value input by the user based on the data transfer interface, which is generated by the first client scanning the second data transfer identification code corresponding to the second client in response to the user-triggered scanning operation.

4. The data transfer method according to claim 1, characterized in that, If the account containing the first data transfer identifier is not the account of the first client, and the account type of the account containing the second data transfer identifier is the same as the account type of the first client, the method further includes: If the second server receives a data transfer failure result when it attempts to transfer the data transfer value from the account containing the first data transfer identifier to the account containing the second data transfer identifier based on the data transfer request, the data transfer value is transferred from the remaining data value of the first client's account to the account containing the second data transfer identifier of the second client, and a data transfer success result is generated.

5. The data transfer method according to claim 1, characterized in that, Sending the second notification message to the first client includes: Obtain the account type of the account that transferred the data transfer value in the account corresponding to the first client, and send a second prompt message to the first client including the data transfer success result and the account type.

6. The data transfer method according to claim 1, characterized in that, If the first data transfer identifier corresponds to data transfer discount information, the obtained data transfer success result includes the data transfer discount information and the actual data transfer value obtained by processing the data transfer value based on the data transfer discount information.

7. A data transfer method, applied to a first client, characterized in that, The method includes: In response to a data transfer operation to a second client, the system sends identification information of the first client to a first server, enabling the first server to obtain the remaining data value of the first client's account before responding to the data transfer operation based on the identification information of the first client. The system then sends a data transfer request, including a data transfer value, to the second server, the data transfer value being obtained based on the data transfer operation initiated to the second client. The data transfer request instructs the second server to transfer the data transfer value from the account containing the first data transfer identifier to the account containing the second data transfer identifier. The data transfer request carries the first data transfer identifier, the second data transfer identifier, and the data transfer value. The first data transfer identifier corresponds to the first client, and the second data transfer identifier corresponds to the second client. At least one of the accounts containing the first and second data transfer identifiers has an account type different from the account type of the first client's account. The system receives a first prompt message generated by the first server when the data transfer value is not greater than the remaining data value. The first prompt message is used to notify the user that the data transfer was successful. The system receives a second notification message from the first server, which includes a data transfer success result. The data transfer success result is either provided by the second server based on the data transfer request or generated by the first server. When the first server receives a data transfer failure result from the second server based on the data transfer request, if it determines that the account containing the first data transfer identifier is not the account of the first client, and the account type of the account containing the second data transfer identifier is the same as the account type of the first client, then the first server transfers the data transfer value from the remaining data value of the first client's account to the account containing the second data transfer identifier of the second client, and generates a data transfer success result.

8. The data transfer method according to claim 7, characterized in that, In response to a data transfer operation to a second client, the system sends identification information of the first client to a first server, enabling the first server to obtain the remaining data value of the first client's account before responding to the data transfer operation based on the identification information of the first client, including: In response to a data transfer request, the system collects the user's identity authentication information and sends the identity authentication information and the identification information of the first client to the first server, so that the server can authenticate the identity authentication information and, upon successful authentication, obtain the remaining data value of the first client's account before responding to the data transfer operation based on the identification information of the first client.

9. The data transfer method according to claim 7, characterized in that, After sending the identification information of the first client to the first server in response to the data transfer operation to the second client, the method further includes: In response to a user-triggered QR code scanning operation, the second data transfer identification code corresponding to the second client is scanned to generate a data transfer interface; Receive the data transfer value input by the user based on the data transfer interface, and send the data transfer value to the first server.

10. The method according to claim 8, characterized in that, After sending the identification information of the first client to the first server in response to the data transfer operation to the second client, the method further includes: The system displays the first data transfer identification code returned by the first server when the identity authentication information is successfully authenticated, so that the second client can return the data transfer value to the first server after scanning the first data transfer identification code.

11. The data transfer method according to claim 7, characterized in that, After receiving the second prompt information from the first server, the method further includes: If the current display interface of the terminal where the first client is located is the first specified interface, then jump to display the second specified interface. The first specified interface displays the first prompt information, and the second specified interface displays the second prompt information. If the current display interface of the terminal where the first client is located is not the first designated interface, a notification or pop-up window is displayed on the current display interface. The notification or pop-up window is used to indicate that the first client has received the second prompt information.

12. A data transfer device, characterized in that, Applied to a first server, the device includes: The data acquisition module is used to acquire the data transfer value generated by the first client in response to the data transfer operation to the second client, and the remaining data value of the first client's account before responding to the data transfer operation; The prompt message generation module is used to generate a first prompt message if the data transfer value is not greater than the remaining data value, and to send the first prompt message to the first client. The first prompt message is used to prompt the user that the data transfer was successful. The request sending module is used to send a data transfer request to the second server, instructing the second server to transfer the data transfer value from the account where the first data transfer identifier is located to the account where the second data transfer identifier is located. The data transfer request carries the first data transfer identifier, the second data transfer identifier, and the data transfer value. The first data transfer identifier corresponds to the first client, and the second data transfer identifier corresponds to the second client. At least one of the accounts where the first data transfer identifier is located and the account where the second data transfer identifier is located has an account type that is different from the account type of the first client's account. The notification message sending module is used to send a second notification message to the first client when the second server receives a successful data transfer result based on the data transfer request. The second notification message includes the successful data transfer result.

13. A data transfer device, characterized in that, Applied to a first client, the device includes: The identification information sending module is used to send the identification information of the first client to the first server in response to a data transfer operation to the second client, so that the first server can obtain the remaining data value of the first client's account before responding to the data transfer operation based on the identification information of the first client, and send a data transfer request including a data transfer value to the second server, wherein the data transfer value is obtained based on the data transfer operation initiated to the second client; The first prompt information receiving module is used to receive the first prompt information generated by the first server when the data transfer value is not greater than the remaining data value. The first prompt information is used to prompt the user that the data transfer was successful. The second prompt information receiving module is used to receive the second prompt information fed back by the first server. The second prompt information is generated by the first server when it receives the data transfer success result fed back by the second server based on the data transfer request, or when the first server receives the data transfer failure result fed back by the second server based on the data transfer request, and the first server transfers the data transfer value from the data remaining value of the first client's account to the account where the second data transfer identifier of the second client is located.

14. An electronic device, characterized in that, It includes a processor and a memory; one or more programs are stored in the memory and configured to be executed by the processor to implement the method of any one of claims 1-6 or 7-11.

15. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores program code, wherein the program code, when executed by a processor, performs the method according to any one of claims 1-6 or 7-11.

16. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method described in any one of claims 1-6 or 7-11.

Images