CN114118995A

CN114118995A - Resource data transfer method and device and electronic equipment

Info

Publication number: CN114118995A
Application number: CN202010886532.5A
Authority: CN
Inventors: 王娇妮
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-08-28
Filing date: 2020-08-28
Publication date: 2022-03-01

Abstract

The application discloses a resource data transfer method, a resource data transfer device and electronic equipment, and relates to the technical field of internet. Wherein, the method comprises the following steps: the method comprises the steps of obtaining transfer party information of resource data, displaying a receiving notice of the resource data, wherein the transfer party information comprises account information of a transfer party account and the quantity of the resource data needing to be transferred from the transfer party account, and the receiving notice is used for prompting the existence of the resource data needing to be received; responding to the sharing operation aiming at the received notification, and sending the received notification to a terminal corresponding to the sharing operation, wherein the terminal is used for acquiring receiver information based on the received notification and sending the receiver information to a server, and the receiver information comprises account information of a receiver account; and receiving transfer success information, wherein the transfer success information is sent by the server after the transfer of the amount of the resource data from the transfer party account to the receiving party account. Therefore, the operation and inconvenience of the transfer party can be reduced, and the probability of providing errors for the account of the receiving party can be reduced.

Description

Resource data transfer method and device and electronic equipment

Technical Field

The present application relates to the field of internet technologies, and in particular, to a method and an apparatus for transferring resource data, and an electronic device.

Background

With the rapid development of internet technology, people have more and more requirements for online resource data transfer, for example, online money transfer, remittance and the like, which brings great convenience to the life of people. However, in some scenarios, the transfer of online resource data is usually handled and controlled by the roll-out party, which is inconvenient.

Disclosure of Invention

The application provides a resource data transfer method, a resource data transfer device and electronic equipment, which can solve the problems.

In one aspect, an embodiment of the present application provides a resource data transfer method, including: acquiring transfer party information of resource data, wherein the transfer party information comprises account information of a transfer account and the quantity of the resource data needing to be transferred from the transfer account; displaying a receiving notice of the resource data, wherein the receiving notice is used for prompting that the resource data with the quantity needing to be received exist; responding to a sharing operation aiming at the receiving notification, and sending the receiving notification to a terminal corresponding to the sharing operation, wherein the terminal is used for acquiring receiver information based on the receiving notification and sending the receiver information to a server, and the receiver information comprises account information of a receiver account; receiving transfer success information, wherein the transfer success information is sent by the server after the transfer of the amount of the resource data from the transfer party account to the receiving party account according to the received transfer party information and the receiving party information.

In another aspect, an embodiment of the present application provides a resource data transfer method, including: receiving a receiving notification sent by a terminal, wherein the receiving notification is used for prompting that resource data needing to be received exist; responding to the confirmation operation aiming at the receiving notification, and acquiring account information of a receiver account, wherein the receiver account is used for receiving the resource data; generating receiver information of the resource data, wherein the receiver information comprises account information of the account of the receiver; and sending the receiver information to a server, wherein the server is used for acquiring transfer party information, the transfer party information comprises account information of a transfer party account and the quantity of the resource data needing to be transferred from the transfer party account, and transferring the quantity of the resource data from the transfer party account to the receiver account according to the transfer party information and the receiver information.

Optionally, before the responding to the selection operation and determining the account information corresponding to the selection operation from the at least one piece of account information as the account information of the account of the receiving party, the resource data transfer method provided in the embodiment of the application further includes: responding to the account information binding operation, and binding the obtained new account information to the terminal; and displaying the new account information.

Optionally, before generating the receiver information of the resource data, the resource data transfer method provided in the embodiment of the present application further includes: displaying a service authorization interface; and responding to the authorization operation detected in the service authorization interface to generate the receiver information of the resource data.

In another aspect, an embodiment of the present application provides a resource data transfer apparatus, including: the device comprises an acquisition module, a display module, a sharing module and a transfer module. The obtaining module is used for obtaining transfer party information of the resource data, and the transfer party information comprises account information of a transfer party account and the quantity of the resource data which need to be transferred from the transfer party account. And the display module is used for displaying a receiving notice of the resource data, and the receiving notice is used for prompting that the resource data needing to be received exist. The sharing module is used for responding to the sharing operation aiming at the receiving notification and sending the receiving notification to a terminal corresponding to the sharing operation, the terminal is used for obtaining receiver information based on the receiving notification and sending the receiver information to a server, and the receiver information comprises account information of a receiver account. The transfer module is configured to receive transfer success information, where the transfer success information is sent by the server after transferring the amount of the resource data from the transfer party account to the receiving party account according to the transfer party information and the receiving party information.

Optionally, in the resource data transfer apparatus provided in this embodiment of the application, the account of the receiving party is an account that is determined by the terminal in response to the confirmation operation for the reception notification from an account corresponding to the bound at least one piece of account information and is used for receiving the resource data.

Optionally, in the device for transferring resource data provided in the embodiment of the present application, the resource data is first type data, and the quantity is a first quantity, the device further includes a generating module, and the generating module is configured to generate a receiving notification of the resource data by, before the display module displays the receiving notification, the following manner: acquiring an identifier of second type data required to be received by the account of the receiver, and taking the acquired identifier as the second type identifier; determining the quantity of second type data required to be received by the account of the receiving party based on the first quantity, the first type identification of the first type data and the second type identification, and taking the determined quantity as a second quantity; and generating the receiving notice according to the first type identification, the first quantity, the second type identification and the second quantity.

Optionally, in the resource data transfer apparatus provided in this embodiment of the present application, the manner of generating, by the generation module, the notification receiving according to the first type identifier, the first number, the second type identifier, and the second number is as follows: generating a display page comprising the first type identifier, the first number, the second type identifier and the second number; determining a page link of the display page as the reception notification.

Optionally, in the resource data transfer device provided in this embodiment of the present application, the server is configured to generate a transfer packet according to the transfer party information and the receiving party information, and forward the transfer packet to the resource transfer processing end; and the resource transfer processing terminal is used for transferring the amount of resource data from the transfer party account to the receiving party account according to the transfer message.

Optionally, the resource data transfer apparatus provided in the embodiment of the present application may further include a verification module. The verification module is used for sending the transfer party information to the server before the display module displays the receiving notice of the resource data, and the server is used for carrying out password verification on the transfer party account according to the transfer party information; and if the password passes the verification, deducting the first amount of the first type data from the transfer-out party account, wherein the resource transfer processing end is used for transferring the second amount of the second type data to the receiving party account.

Optionally, in the resource data transfer apparatus provided in this embodiment of the present application, the verification module may be further configured to, before the display module displays the reception notification of the resource data, obtain a name of the recipient when it is determined that the first number reaches the target number; and sending the name of the receiver to the server, wherein the server is used for acquiring real-name information of the account of the receiver from the information of the receiver, comparing whether the name of the receiver is the same as the real-name information of the account of the receiver, and if so, transferring the first amount of the first type data from the account of the transfer party to the account of the receiver according to the information of the transfer party and the information of the receiver.

Optionally, the transfer party information further includes a service type identifier, and the server is configured to send the transfer party information and the receiver information to the resource transfer processing end according to a manner corresponding to the service type identifier.

Optionally, the server sends the transfer party information and the receiving party information to the resource transfer processing end in a manner corresponding to the service type identifier: identifying the service type identifier; if the service type identification is a target identification, a target service interface is called to process the information of the roll-out party and the information of the receiving party so as to send the information of the roll-out party and the information of the receiving party to a resource transfer processing end corresponding to the target identification.

On the other hand, an embodiment of the present application provides a resource data transfer apparatus, which includes a receiving module, an obtaining module, a generating module, and a transferring module. The receiving module is used for receiving a receiving notification sent by the terminal, wherein the receiving notification is used for prompting that resource data needing to be received exist. The obtaining module is configured to obtain account information of a receiver account in response to the confirmation operation for receiving the notification, where the receiver account is an account for receiving the resource data. The generation module is used for generating receiver information of the resource data, and the receiver information comprises account information of the account of the receiver. The transfer module is used for sending the receiver information to a server, the server is used for obtaining transfer party information, the transfer party information comprises account information of a transfer party account and the quantity of the resource data needing to be transferred from the transfer party account, and the quantity of the resource data is transferred from the transfer party account to the receiver account according to the transfer party information and the receiver information.

In another aspect, an embodiment of the present application provides an electronic device, including: one or more processors; a memory; one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs configured to perform the methods provided by the above-described embodiments.

In another aspect, the present application provides a computer-readable storage medium, on which program code is stored, and the program code can be called by a processor to execute the method provided by the foregoing embodiment.

According to the scheme, the terminal of the receiving party can be determined through the sharing operation of the transfer party, the receiving notification of the resource data is sent to the terminal of the receiving party, and then the terminal of the receiving party sends the receiving party information to the server based on the receiving notification, so that the server can transfer the resource data from the account of the transfer party to the account of the receiving party according to the received transfer party information and the receiving party information. Therefore, the inconvenience that the transfer party acquires the account of the receiving party through communication with the receiving party and provides the account of the receiving party manually can be avoided, and the probability of providing errors by the account of the receiving party can be reduced by the receiving party.

These and other aspects of the present application will be more readily apparent from the following description of the embodiments.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 shows a schematic diagram of an application environment suitable for the embodiment of the present application.

Fig. 2 shows a flowchart of a resource data transfer method according to an embodiment of the present application.

Fig. 3 shows a schematic diagram of a generation flow of the reception notification in the embodiment shown in fig. 2.

Fig. 4 shows a schematic view of the substeps of step S223 shown in fig. 3.

Fig. 5 shows a flow of resource transfer processing performed by the server in the embodiment shown in fig. 2.

Fig. 6A is a schematic diagram illustrating a pick interface for a money transfer method provided by an embodiment of the present application.

Fig. 6B is a diagram illustrating a sender information input interface according to an embodiment of the present application.

Fig. 6C is a schematic diagram illustrating a password authentication interface provided in an embodiment of the present application.

Fig. 6D is a schematic diagram illustrating a deduction notification interface provided in an embodiment of the present application.

Fig. 6E is a schematic diagram illustrating a sharing interface provided in the embodiment of the present application.

Fig. 6F is a diagram illustrating a dialog box of the first client according to an embodiment of the present application.

Fig. 6G is a schematic diagram illustrating a display page in a received notification according to an embodiment of the present application.

Fig. 6H is a schematic diagram illustrating a collection account acquisition interface according to an embodiment of the present application.

Fig. 6I is a schematic diagram illustrating a service authorization interface provided by the embodiment of the present application.

Fig. 6J is a schematic diagram illustrating an authentication interface provided in an embodiment of the present application.

FIG. 6K is a diagram illustrating a successful checkout interface provided by an embodiment of the present application.

Fig. 7 shows another flowchart of the resource data transfer method provided in the embodiment of the present application.

Fig. 8 shows another flowchart of the resource data transfer method provided in the embodiment of the present application.

Fig. 9 is a process flow diagram illustrating a money transfer order provided by an embodiment of the present application.

Fig. 10 illustrates a user flow and a funds flow corresponding to the money transfer job of fig. 9 provided by an embodiment of the present application.

FIG. 11 illustrates an order state machine for the money transfer job of FIG. 9 provided by an embodiment of the present application.

Fig. 12 is a flowchart illustrating a resource data transfer method according to an embodiment of the present application.

Fig. 13 shows a sub-step diagram of step S1230 in fig. 12.

FIG. 14 shows another flow diagram of the method of FIG. 12.

Fig. 15 shows a block diagram of a resource data transfer apparatus according to an embodiment of the present application.

Fig. 16 is a block diagram illustrating a resource data transfer apparatus according to an embodiment of the present application.

Fig. 17 is a block diagram of an electronic device according to an embodiment of the present application, configured to execute a resource data transfer method according to an embodiment of the present application.

Fig. 18 is a storage unit according to an embodiment of the present application, configured to store or carry program code for implementing a resource data transfer method according to an embodiment of the present application.

Detailed Description

In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.

At present, the transfer of the on-line resource data is mostly operated and controlled by the transfer party. For example, money transfer operations are typically operated and controlled by the money transfer. In detail, the sender generally needs the receiver to communicate transfer information, and then the sender needs to fill a receiving account, a receiver name, a receiving amount, etc. of the receiver according to the communicated transfer information, and then initiate the remittance. The payee can only wait for the arrival of the fund in the process and further receives the account arrival and contact notice of the payee bank. This approach requires additional communication to obtain payee information and to fill in payee information, which is inconvenient and prone to error by third parties.

In view of the above problems, the inventors have conducted long-term research and provide a method, an apparatus, and an electronic device for transferring resource data, which can obtain information of a receiving party very conveniently and reduce the probability of providing errors by the information of the receiving party. This is described in detail below.

Referring to fig. 1, fig. 1 is a schematic diagram of an application environment suitable for the embodiment of the present application. The server 100 is communicatively connected to the resource transfer processing terminal 200, the first terminal 300, and the second terminal 400 via a network.

Wherein the first terminal 300 may be a terminal of a forwarding party and the second terminal 400 may be a terminal of a receiving party. The first terminal 300 may be installed with a first client 310 and a second client 320, and both the first client 310 and the second client 320 may be applications having a resource data transfer function.

In the embodiment of the present application, the resource data may be an entity resource represented in an electronic data form, and the entity resource may be, for example, money, gold, gifts, equipment, and the like. Resource data may be transferred between accounts of different users in a given amount, for example where the resource data is monetary data, it may be transferred between different bank accounts, financial institution accounts, etc., where the transfer may be by way of payment, remittance, money transfer, etc.

It is worth noting that in the embodiment of the present application, the first client 310 and the second client 320 may be different types of applications. The second client 320 may communicate with the server 100, in other words, the first terminal 300 may log in to the server 100 through the second client 320 and provide the resource data service for the user through cooperation of the second client 320 and the server 100.

In one example, the second client 320 may be a Virtual Bank (VB) client, and correspondingly, the server 100 may be a Virtual Bank server. In another example, the second client 320 may also be another application having a resource data transfer function (e.g., payment, remittance, transfer, etc.), and correspondingly, the server 100 is a server deployed with a server corresponding to the application.

The second terminal 400 may be installed with the first client 410, and the first client 410 and the first client 310 may be the same application, such as instant messaging software W with funds transfer function.

The resource transfer process terminal 200 may be a server of an organization capable of conducting a funds transfer process, such as a server of an agent bank, for example, a Unionpay server. It can be understood that the servers (e.g., the server 100 and the resource transfer processing terminal 200) mentioned in the embodiment of the present application may be independent physical servers, may also be a server cluster or a distributed system formed by a plurality of physical servers, and may also be cloud servers providing basic cloud computing services such as cloud computing, big data, and artificial intelligence platforms. The above-mentioned terminals (e.g., the first terminal 300 and the second terminal 400) may be a smart phone, a tablet Computer, a notebook Computer, a Personal Computer (PC), a portable wearable device, and the like. The embodiments of the present application do not limit this.

Referring to fig. 2, fig. 2 is a flowchart illustrating a resource data transfer method according to an embodiment of the present application, which can be executed by the first terminal 300. The steps of the method are explained below.

S210, transfer party information of the resource data is obtained, wherein the transfer party information comprises account information of a transfer party account and the quantity of the resource data needing to be transferred from the transfer party account.

As described above, the resource data may be an entity resource represented in the form of electronic data, and the present embodiment will be described mainly by taking an example in which the resource data is money data. The transfer party information refers to information of a party needing to transfer the resource data, wherein the transfer party account refers to an account needing to transfer the resource data, and the account information of the transfer party account may include, for example, an account identification of the account, such as an account id (identity). Taking the resource data as currency data as an example, the transferor information may be remitter information, for example, and the transferor account may be a remittance bank account, for example, and correspondingly, the account information of the transferor account may include a bank card number of the remittance bank account. Correspondingly, the amount in the transferor information may be the money transfer amount.

For convenience of description, the amount of resource data that the transfer party account needs to transfer is defined herein as a first amount.

In this embodiment, the roll-out party information may be input by the roll-out party through the first terminal 300, and transmitted to the server 100 by the first terminal 300. The roll-out information indicates what type of resource data the roll-out party wishes to roll out with, and the amount of this type of resource data that the roll-out party wishes to roll out. Wherein the first amount generally corresponds to a type of the resource data. For example, the information of the roll-out party includes the type identifier of the first type data and the corresponding first amount, which indicates that the roll-out party wishes to roll out the first amount of the first type data. It will be appreciated that for a given first amount of data of a first type, the first amount will vary with the type of resource data.

For example, the first type data is resource data corresponding to currency issued in country a, the second type data is resource data corresponding to currency issued in country C, the first type data requiring the transfer of the amount M1 is initially input by the user, and after the amount M1 is input, the second type data is transferred instead, and the amount M1 may be converted into the amount M2 according to the current proportional relationship (e.g., exchange rate, etc.) between the first type data and the second type data. That is, what needs to be transferred from the transfer party account at this time is the amount M2 of the second type of data.

And S230, displaying a receiving notice of the resource data, wherein the receiving notice is used for prompting that the resource data needing to be received exist.

The receiving notification may be image information, text information, or a combination of the image information and the text information for prompting the receiving party that the resource data required to be received exists. In some examples, the receipt notification may include the type identifier of the resource data and the quantity, such that the recipient may view the type and quantity of the resource data that needs to be received based on the receipt notification.

In other examples, the receiving notification may include an identity of the transfer-out party in addition to the type identifier and the amount of the resource data, so that the receiving party may also see who the resource data was transferred out based on the receiving notification.

In this embodiment, the reception notification may be generated by the first terminal 300 based on the forwarding party information. Further, the first terminal 300 may execute a trigger operation after receiving the forwarding information, and in response to the trigger operation, the first terminal 300 may transmit trigger information to the server 100, cause the server 100 to generate the reception notification after receiving the trigger information, and return the generated reception notification to the first terminal 300. The triggering operation may be, for example, a confirmation transfer operation performed by the transfer party on the interface of the first terminal 300, or an operation performed by the transfer party on the first terminal 300 to confirm deduction of resource data, which will be described later. The trigger information may include the roll-out information. The present embodiment does not limit this.

And S250, responding to the sharing operation aiming at the receiving notification, and sending the receiving notification to a terminal corresponding to the sharing operation, wherein the terminal is used for acquiring receiver information based on the receiving notification and sending the receiver information to a server, and the receiver information comprises account information of a receiver account.

In this embodiment, the forwarding party may share the receiving notification to the receiving party in a dialog box on the instant messaging software, so that the receiving notification may be sent to a terminal corresponding to the sharing operation. It should be noted that the terminal corresponding to the sharing operation described in S250 may be understood as a terminal of the receiving side, such as the second terminal 400.

In one example, the client for resource data transfer and the client for sharing the reception notification may be the same.

For example, the first client (e.g., 310, 410) may have both the resource data transfer function and the instant messaging function. At this time, the roll-out party may input roll-out party information at the first client 310 and perform a resource data transfer operation, causing the first client 310 to display a reception notification as by S230. Further, the roll-out party may perform a sharing operation on the first client 310 for the received notification, such as selecting a buddy identifier representing the recipient from the buddy list of the first client 310, thereby entering a dialog box with the recipient, and sharing the received notification to the dialog box of the recipient. In this way, a reception notification may be transmitted to the first client 410 of the second terminal 400, and the receiving side may view the reception notification in the dialog box of the transferring-out side.

In another example, the client used for resource data transfer and the client used for sharing the received notification may be different. For example, the second client 320 shown in fig. 1 may be a client for resource data transfer, and the first client 310 may be a client for sharing reception notification.

In detail, the roll-out party may input roll-out party information at the second client 320, perform resource data transfer operation at the second client 320, trigger the second client 320 to display a reception notification according to S230, and may select to share the reception notification through the first client 310, for example, enter a buddy list interface of the first client 310 through a specific sharing interface, the roll-out party may select a buddy identifier corresponding to the receiver from the buddy list of the first client 310, thereby enter a dialog box corresponding to the buddy identifier, and share the reception notification to the dialog box. In this case, the first client 410 of the receiving party may receive the reception notification, and the receiving party may view the reception notification in a dialog box corresponding to the transferring party in the first client 410.

It is understood that the reception notification transmitted to the second terminal 400 can be regarded as a message to the receiving party, and the receiving party can view the reception notification on the second terminal 400. Alternatively, the reception notice may be displayed on the second terminal 400 as a prompt message carrying a page link, for example, "you have an amount of money to be collected", "you have an amount of money transferred from the XX bank", or the like. By operating the prompt information (e.g., clicking, pressing, sliding, etc.), a display page corresponding to the page link may be entered, and various items of information included in the reception notification, such as the type identifier and the amount of the resource data that the receiver needs to receive, may be displayed on the display page.

The receiving side may perform a confirmation operation on the display page, and the performed confirmation operation may be regarded as a confirmation operation for receiving the notification. For example, a confirmation button, such as a virtual button with words "confirm receipt", "confirm receipt", and the like, may be provided on the display page. The recipient can press, click, and slide the confirmation button to effect the confirmation operation. In other words, when the second terminal 400 detects an operation of the confirmation button on the display page, it may be determined that a confirmation operation of the recipient for receiving the notification is detected, thereby entering the recipient account acquisition interface.

In one example, the recipient account acquisition interface may include an input area where the recipient may directly enter account information for the recipient account.

In another example, the receiving-side account obtaining interface may include a selection area, and the selection area may display at least one candidate account information, where the candidate account information may be, for example, the account information bound to the second terminal 400 by the first client 410. The receiving party can select one account from accounts corresponding to the at least one candidate account information displayed in the selection area as the account of the receiving party.

In another example, the receiving-side account obtaining interface may include a selection area and an input area at the same time, and in this case, on the one hand, the receiving side may select an account corresponding to any candidate account information displayed in the selection area as the receiving-side account. On the other hand, the recipient may select to add a new account in the input area, bind the added new account information to the first client 410 of the second terminal 400, and further select an account corresponding to the added new account information as the recipient account.

After obtaining the account information of the recipient account, the second terminal 400 may generate recipient information including the account information of the recipient account. In one embodiment, the second terminal 400 may return the recipient information to the first client 310 of the first terminal 300 through the first client 410. It is worth noting that if the client for resource data transfer is the second client 320, the first client 310 may further transmit the received recipient information back to the second client 320. In this embodiment, the first terminal 300 may transmit the recipient information to the server 100 after obtaining the recipient information. In another embodiment, the receiving notification may carry a communication address (e.g., a link address) of the server 100, and the second terminal 400 may directly send the receiver information to the server 100 according to the receiving notification.

In this embodiment, the receiving party may also refuse to receive the resource data through the second terminal 400, or the receiving party may not confirm the reception notification for a long time, and at this time, the second terminal 400 will not return the receiving party information to the first terminal 300 or the server 100. The long time here may be a time threshold preset by the server 100, for example, 24 hours, 48 hours, and the like. Taking the time length threshold as 24 hours as an example, if the receiving party still does not confirm the receiving notification 24 hours after the receiving notification is sent, the resource data transfer can be cancelled.

When the receiving party confirms the receiving notification within the time threshold range after sending the receiving notification and gives account information of the account of the receiving party, the server 100 may receive the receiving party information (directly sent by the second terminal 400 or sent by the second terminal 400 via the first terminal 300). In other words, in this case, the server 100 may receive the recipient information to perform the subsequent resource data transfer process.

In this case, the server 100 has already obtained information (receiver information and transferor information) necessary for the transfer of the resource data, so that the first amount of resource data in the transferor account can be transferred to the receiver account based on the information.

In this embodiment, the server 100 may generate a transfer message according to the information of the forwarding party and the information of the receiving party, and forward the transfer message to the resource transfer processing terminal 200. The resource transfer processing terminal 200 may obtain the transfer party information and the receiving party information from the transfer message, so that the amount of resource data may be transferred from the transfer party account to the receiving party account according to the transfer party information and the receiving party information.

It can be understood that, in the scenario where the receiver information is returned to the first terminal 300 by the second terminal 400, the sender information and the receiver information may also be directly sent from the first terminal 300 to the resource transfer processing terminal 200, which is not limited in this embodiment.

S270, receiving transfer success information, wherein the transfer success information is sent by the server after the transfer of the amount of the resource data from the transfer party account to the receiving party account according to the received transfer party information and the receiving party information.

In this embodiment, after the server 100 successfully transfers the amount of the resource data from the transfer-out party account to the receiving party account, the transfer success information may be generated and sent to the first terminal 300. The transfer success information here may be a notification that prompts the transfer-out party that the transfer of the resource data was successful. It is understood that the server 100 may also generate a notification for prompting the receiving party that the resource data transfer is successful, and send the notification to the second terminal 400. It is understood that, when the resource data transfer fails, the server 100 may also generate transfer failure information to be respectively transmitted to the first terminal 300 and the second terminal 400.

Through the scheme provided by the embodiment, the transfer party can obtain the information of the receiving party from the terminal of the receiving party only by executing simple sharing operation, so that the inconvenience caused by the fact that the transfer party and the receiving party communicate the information of the receiving party offline is avoided, and the high error rate caused by the fact that the transfer party obtains the information of the receiving party and fills the information in the receiving party can be effectively reduced.

Further, when the account of the receiving party is selected from the accounts bound by the terminal of the receiving party, the probability of error of the information of the receiving party is further reduced because the receiving party does not need to perform manual filling.

In addition, the resource data transfer mode of the receiver information given by the receiver can enable the receiver to know the resource data transfer progress and participate in the resource data transfer process, and user experience is better.

Referring to fig. 2 and 3 together, the method shown in fig. 2 will be further described with reference to fig. 3.

In some cases, it may be the case that resource data is transferred across regions, for example, when a transferring party performs a resource data transfer operation, it indicates that a receiving party needs to receive data of a second type in addition to a first amount of data of a first type that needs to be transferred. In this case, the first terminal 300 may determine the amount of the second type data that the receiving side needs to receive based on the first amount and the current proportional relationship between the first type data and the second type data, and for convenience of description, the amount of the second type data that the receiving side needs to receive is hereinafter defined as the second amount.

For the case of transferring the resource data across the region, the receiving party can simultaneously check the type identifier and the quantity of the resource data transferred by the transferring party and the type identifier and the quantity of the resource data required to be received by the receiving party. For example, in the above example, the first amount of data of the first type is transferred out, and the second amount of data of the second type is required to be received, the reception notification in S230 may be obtained through the flow shown in fig. 3, in other words, before executing S230, the resource data transfer method provided in this embodiment may further include the flow shown in fig. 3.

S221, acquiring the identifier of the second type data required to be received by the account of the receiver, and taking the acquired identifier as the second type identifier.

In this embodiment, the second type of data that the account of the receiving party needs to receive may be actively specified by the transfer party when the first terminal 300 initiates the resource data transfer, or may be automatically determined based on the resource data transfer mode selected by the transfer party at the first terminal 300. For example, the operations required to transfer resource data across regions are often complex, e.g., cross-border money transfers require the transferee to provide a money transfer routing code (e.g., swiftcode), etc., and the cross-border money transfers take a long time to complete. Thus, in some embodiments, a specialized cross-border money transfer channel is provided to enable rapid cross-border money transfers between designated currencies. For example, the global quick-transfer service provided by the Unionpay can realize remittance through various foreign currencies and collection through RMB. The transferor may choose to transfer the resource data through the cross-border remittance channel at the first terminal 300, and at this time, the first terminal 300 may default that the second type of data that the recipient needs to receive is renminbi.

S222, determining a quantity of a second type of data that needs to be received by the account of the receiving party based on the first quantity, the first type identifier of the first type of data, and the second type identifier, and taking the determined quantity as a second quantity.

In implementation, the first terminal 300 may search for a current proportional relationship between the first type data and the second type data according to the first type identifier and the second type identifier, and in a case that both the first type data and the second type data are currency data, the current proportional relationship may be a current exchange rate. The first terminal 300 may then determine the second number based on the first number and the current proportional relationship.

S223, generating the receiving notification according to the first type identifier, the first quantity, the second type identifier, and the second quantity.

In the implementation process, the image information, the text information or the combination of the image information and the text information including the first type identifier, the first amount, the second type identifier and the second amount may be generated, and the generated information may be used as the reception notification. Thus, by receiving the notification, the receiving party can check that the transferring party account transfers a first amount of the first type data, and can receive a second amount of the second type data.

Illustratively, S223 may be implemented by the flow shown in fig. 4. The detailed description is as follows.

S223-1, generating a display page comprising the first type identification, the first number, the second type identification and the second number.

In the implementation process, according to a given page template, the first type identifier, the first number, the second type identifier, and the second number may be filled in corresponding fields of the page template, and the page template filled with the first type identifier, the first number, the second type identifier, and the second number is the display page described in S213-1.

S223-2, determining the page link of the display page as a reception notification.

In this embodiment, the display page generated in S23-1 has a corresponding page link, and the page link may be directly used as a reception notification. In addition, the page link and given prompt information may also be combined into the reception notification, where the prompt information may be, for example, the above-mentioned information for prompting the receiving party that there is resource data that needs to be received.

In this embodiment, different transfer modes may be provided for the resource data transfer across the region. In the process of performing the trans-regional resource data transfer, the transfer party may first perform a selection operation of a resource data transfer mode, and when the resource data transfer mode selected by the selection operation is a preset mode, may cause the first terminal 300 to perform processing according to the resource data transfer method provided in the embodiment of the present application.

In other words, the selected resource data transfer mode is different, and the resource data transfer process is also different. In detail, in this embodiment, when the first terminal 300 detects the use operation of the cross-region resource data transfer service, a selection interface of the resource data transfer mode may be provided, where the selection interface may display at least one selectable resource data transfer mode, and the transfer party may select one of the resource data transfer modes to be used.

Different resource data transfer manners may correspond to different service type identifiers, and the first terminal 300 or the server 100 may store a correspondence between the resource data transfer manner and the service type identifier. In this way, the first terminal 300 may determine the resource data transfer mode selected by the selection operation according to the selection operation of the transfer party on the selection interface of the resource data transfer mode, and further search for the service type identifier corresponding to the selected resource data transfer mode according to the corresponding relationship.

Alternatively, the service type identifier may be part of the transferor information, in other words, the transferor information may include the service type identifier, and the service type identifier may be transmitted to the server 100 along with the account information of the transferee account and the first amount. The server 100 may send the information of the forwarding party and the information of the receiving party to the resource transfer processing end 200 according to the corresponding manner of the service type identifier.

In an implementation process, the server 100 may generate a first packet according to a packet format corresponding to the transfer packet, where the first packet includes fields used to fill the information of the forwarding party, the information of the receiving party, and the service type identifier, and each field may be empty or a default value. The server 100 may fill the forwarding party information, the receiving party information, and the service type identifier determined through S271 into corresponding fields of the first packet, where the first packet filled with the forwarding party information, the receiving party information, and the service type identifier is the second packet.

After the server 100 generates the second message, the second message may be sent to the resource transfer processing end 200 as a transfer message. The transfer packet carries a service type identifier, the server 100 may determine, based on the service type identifier carried in the transfer packet, to which resource transfer processing terminal 200 the transfer packet is sent, and processes of resource data transfer performed by different resource transfer processing terminals 200 are different.

In other examples, the first terminal 300 may directly generate a transfer message according to the forwarding party information, the receiving party information, and the service type identifier, and send the transfer message to the resource transfer processing terminal 200. The process of generating the transfer message by the first terminal 300 is similar to the process of generating the transfer message by the server 100, and is not described herein again.

In this case, the server 100 sends the information of the forwarding party and the information of the receiving party to the resource processing terminal 200 in a manner corresponding to the service type identifier, which may be implemented by the steps shown in fig. 5.

S501, identifying the service type identification in the transfer message.

S502, if the service type identifier is a target identifier, a target service interface is called to process the information of the forwarding party and the information of the receiving party so as to forward the information of the forwarding party and the information of the receiving party to a resource transfer processing end corresponding to the target identifier.

In this embodiment, if the transfer packet is directly sent from the first terminal 300 to the resource transfer processing terminal 200, the flow shown in fig. 5 may be executed by the first terminal 300.

If the information of the forwarding party and the information of the receiving party are transmitted to the resource transfer processing terminal 200 via the server 100, the service type identifier may be transmitted to the server 100 together with the information of the forwarding party and the information of the receiving party. In this case, the flow shown in fig. 5 may be executed by the server 100. In detail, the server 100 may store service type identifiers corresponding to different resource data transfer manners, where the service type identifier corresponding to the resource data transfer method provided in this embodiment may be Tag1, and the service type identifier corresponding to another resource data transfer manner may be, for example, Tag2, and certainly, in the case that there are more resource data transfer manners, more service type identifiers may also be stored.

The Tag1 can be regarded as the target identifier in S272-2. In the implementation process, the server 100 may read the service type identifier in the transfer message, compare the read service type identifier with the stored Tag1, and if the two identifiers are the same, indicate that the transfer party wishes to transfer the resource data in the resource data transfer mode corresponding to the Tag1, so that the target service interface may be invoked to process the transfer message according to the processing logic corresponding to the target identifier Tag 1.

The target service interface can be, for example, a global speed transfer service interface of the Unionpay, and can realize quick remittance from various foreign currencies to the Renminbi without providing a remittance routing number of a receiver account and the like. In this example, the transfer message may be sent to the union pay server by calling the target service interface, and correspondingly, the union pay server may obtain the information of the forwarding party and the information of the receiving party in the transfer message, and perform subsequent resource data transfer processing according to the obtained information of the forwarding party and the information of the receiving party. For the calling of the target service interface, the receiver information required by the transregional resource data transfer is simplified, the remittance routing number of the account of the receiver does not need to be provided, and on the basis, the receiver can select one account bound by the second terminal to receive the resource data, so that the information required to be filled in and the errors caused by information filling in the transregional resource data transfer process are greatly reduced.

Optionally, when the service type identifier corresponding to the selecting operation is Tag2, the processing may be performed according to a resource data transfer manner corresponding to Tag 2.

Referring to fig. 6A, taking cross-regional resource data transfer as an example of cross-border remittance, a remittance method selection interface 601 (which can be understood as the selection interface of the resource data transfer method described above) is shown, in which two remittance methods of "bank card number remittance" and "remittance to W client friend" are shown.

The "bank card number remittance" is a traditional online remittance method, and the corresponding service type identifier is Tag2, for example. This remittance method requires at least a remittance routing number of a recipient account in addition to recipient information required in the scheme of this embodiment, and after a remittance message (which can be understood as a transfer message) is generated based on remitter information, recipient information, Tag2 and the remittance routing number, the remittance message may be stored in a designated location of an agent bank in a file form based on Tag2, and a server of the agent bank may transfer resource data across areas according to the remittance message in the file form by itself. The server of the proxy line here can be understood as the resource transfer processing terminal 200 described above.

The "remittance to the W client friend" may be a remittance method corresponding to the resource data transfer method provided in this embodiment, and the service type identifier corresponding to the remittance method is Tag1, for example. The remittance mode can generate a receiving notice (which can be understood as a receiving notice) based on remitter information (which can be understood as transfer party information), share the receiving notice to a friend of a W client (for example, a friend of a first client), receive remittance information (excluding a remittance routing number) returned by the W client corresponding to a remitter, generate a remittance message carrying the remitter information, the remitter information and Tag1, and call a global speed transfer service interface of the union bank corresponding to the Tag according to Tag1 to process the remittance message, so as to forward the remittance message to the union bank server. Here, the union pay server can be understood as the resource transfer processing terminal 200 described above.

In this embodiment, after the transfer party selects a certain resource data transfer mode, the first terminal 300 may provide an interface for inputting information of the transfer party. Taking the example of cross-regional resource data transfer as cross-border remittance, the transferor information may be remitter information, and fig. 6B shows an interface 602 for entering remitter information in the cross-border remittance service.

The interface 602 includes a selection entry 602-1 for the type of money to be transferred, and by operating the operation button 602-2 corresponding to the entry 602-1, the area in which the entry 602-1 is located can display the candidate types, and the sender can select one (for example, AAA type) from the displayed candidate types as the type of money to be transferred. The AAA may be considered as the first type of identification in the above embodiments, in other words, the AAA currency may be considered as the first type of data that needs to be transferred from the transfer party account.

The interface 602 may also include a pick area 602-3 for the amount of money to be transferred, where the sender may fill in the amount of money to be transferred at area 602-3, which may be understood to correspond to the type of money selected in the entry 602-1. For example, interface 602 shows that the sender needs to transfer 500 AAA currencies.

Interface 602 may also include a pick portal 602-4 for a money transfer account and a trigger button 602-5 for accessing pick portal 602-4. By operating the trigger button 602-5, candidate account information, such as at least a portion of the bank card number of the first client 310 bound to the first terminal 300, may be displayed in the area of the pick portal 602-4. The sender may select one of the displayed candidate account information (e.g., account information of XX1 account), and the XX1 account corresponding to the selected candidate account information is the money transfer account. The money transfer account herein may be understood to be a transfer party account in the above-described embodiments of the present application.

For example, the area of the pick portal 602-4 may also display the balance of the money transfer account, which may be the amount corresponding to the type of money selected in the pick portal 602-1, e.g., the area of the pick portal 602-4 may display the balance of the AAA currency in the XX1 account as XXXXX.

When the sender performs the confirmation operation on the interface 602, information in each entry and area of the interface 602 may constitute sender information. The confirmation operation here may be, for example, clicking or pressing the area of the interface 602 where the "roll-out" typeface is located.

In the embodiment of the present application, it is considered that the transfer process of the resource data includes two parts, the first part is to deduct a first amount of first type data from the transfer-out party account, and the second part is to transfer a second amount of second type data to the receiving party account. Therefore, the first terminal 300 may perform the first part of the operation when obtaining the forwarding information, and perform the second part of the operation when obtaining the receiving information returned by the second terminal 400, so as to reduce the time consumption of the whole transferring process. Based on this, the resource data transfer method provided in the embodiment of the present application may further include a flow illustrated in fig. 7.

S220-1, sending the transfer party information to a server, wherein the server is used for carrying out password verification on the transfer party account according to the transfer party information.

And S220-2, if the password passes the verification, deducting a first amount of first type data from the transfer-out party account, wherein the resource transfer processing end is used for transferring a second amount of second type data to the receiving party account according to the transfer message.

It is to be understood that the steps shown in fig. 7 may be performed before the flow (S221-S223) shown in fig. 3. In detail, in an implementation process, when the first terminal 300 obtains the information of the roll-out party and detects a confirmation operation on the information of the roll-out party (for example, clicking a word "roll-out" on the interface 702), the information of the roll-out party may be sent to the server 100, the server 100 may identify an account of the roll-out party and send prompt information to the first terminal 300 for prompting to input a payment password of the account of the roll-out party, the first terminal 300 receives the input payment password and sends the input payment password to the server 100, and the server 100 performs the above-mentioned first part of operations when the input payment password is verified, that is, deducts a first amount of first type data from the account of the roll-out party.

Referring to FIG. 6C, a password verification interface 603 for a money transfer account during a money transfer service is shown, taking the resource data transfer as a money transfer as an example. Password verification interface 703 includes a password entry box 603-1 and a virtual key area 603-2 for entering a password. FIG. 6C shows a money transfer job with a money transfer of YYY for the money transfer account XX1 account and a money transfer of AAA for the type of currency required to be transferred by an amount of 500. Then the money transfer account XX1 may be prompted for a payment password. When cryptographically authenticated, an amount of 500 AAA currencies may be deducted from the money transfer account. After deducting the AAA currency of 500, a deduction success notification interface may be displayed, which may be, for example, 604 shown in fig. 6D.

Illustratively, the notification interface 604 may display the type of currency AAA deducted and the amount of currency deducted as 500.00. In addition, the notification interface 604 may also display a share button 604-1 for the sender to perform the sharing operation. The share button here may be a virtual button. The sharing operation for receiving the notification in S250 of the above embodiment may be implemented by clicking, pressing, or sliding the sharing button 604-1, for example.

Taking the second client 320 as the client for transferring the resource data and the first client 310 as the client for sharing the reception notification, when the sender presses the sharing button 604-1, the second client 320 of the first terminal 300 may start the first client 310 and display the friend list of the sender at the first client 310. Such as sharing interface 605 shown in fig. 6E, which illustrates a buddy list of the sender at first client 310 from which the sender may select a recipient's corresponding buddy identifier, such as YYY 1. The first terminal 300 may display a confirmation interface 605-1 on the sharing interface 605 in response to the selection operation of the sender. The sender may operate a confirmation button on the confirmation interface 605-1, for example, an area where the word "send" is located, and when the first terminal 300 detects an operation (for example, a single click, multiple clicks, a press, a long press, etc.) with respect to the confirmation button on the confirmation interface 605-1, a reception notification may be transmitted to a terminal of YYY1, for example, the second terminal 400.

Since the first terminal 300 receives the reception notification from the first client 310, the second terminal 320 receives the reception notification from the first client 410, and the reception notification can be displayed in the dialog 606 of the sender at the first client 410. Referring to fig. 6F, a dialog 606 is shown for the sender at the first client 410. As previously described, the received notification may include the reminder information 706-1, which may be displayed in the dialog box 606, as well as a display page. The operation (click, press, double click, long press, etc.) of the prompt message may cause the second terminal 400 to jump to the display page. The display page may be, for example, 6707 as shown in fig. 6G, in which a first number 500.00, a first type identity AAA, a second number 456.45 and a second type identity BBB are shown. This indicates that the money transfer account transferred an amount of 500.00 AAA currency, while the money transfer account may receive an amount of 456.45 BBB currency.

The payee (i.e., the recipient) may confirm the money to be received on the display page 607. For example, collection of money can be confirmed by operating the confirm button 607-1. In one case, the recipient may return the money to the money transfer account via an immediate return button 607-2. Alternatively, if the recipient does not confirm via the confirm button 607-1 for more than a certain amount of time (e.g., the above-mentioned time threshold) after receiving the receipt notification, the money may be automatically returned to the money transfer account.

When the payee confirms the receipt through the confirmation button 607-1 on the display page 607, the second terminal 400 may acquire the receipt account information of the payee. Referring to FIG. 6H, which illustrates a schematic view of the collection account acquisition interface 608, the collection account acquisition interface 608 may include a first field 608-1 and a second field 608-2. The first region 608-1 shows at least one bank account to which the first client 410 of the second terminal 400 has bound, for example, an a bank savings card with a tail number of XYX1, a B bank savings card with a tail number of XYX2, and a C bank savings card with a tail number of XYX 3. The second field 608-2 shows a new account binding portal through which a new bank account can be bound to the first client 410 of the second terminal 400.

The payee may select one of the first field 608-1 as the receiving account (i.e., the recipient account) or may add a new bank account through an entry in the second field 608-2 and select the new bank account as the receiving account.

In the embodiment of the present application, in order to ensure that the account information of the account of the recipient sent by the second terminal 400 based on the reception notification is accurate, the transfer party information may include the name of the recipient input by the transfer party, and the recipient information sent by the second terminal 400 may include real name information of the account of the recipient in addition to the account information of the account of the recipient. Based on this, before executing S230, the resource data transfer method provided in the embodiment of the present application may further include the steps illustrated in fig. 8.

S224, if the first quantity reaches the target quantity, the name of the receiver is obtained.

And S225, sending the name of the receiver to a server, wherein the server is used for acquiring the real-name information of the account of the receiver from the information of the receiver, comparing whether the name of the receiver is the same as the real-name information of the account of the receiver, and if so, transferring a first amount of first type data from the account of the transfer party to the account of the receiver according to the information of the transfer party and the information of the receiver.

In implementation, the target amount may be a threshold set for the amount of resource data that needs to be rolled out (i.e., the first amount), which may vary according to the type of the resource data. The first terminal 300 may determine the corresponding target number based on the first type identifier in the roll-out party information after obtaining the roll-out party information, further compare the first number in the roll-out party information with the target number, and if it is determined that the first number reaches the target number, may prompt the roll-out party to input a name of a receiving party. After obtaining the name of the recipient, the first terminal 300 may transmit the name of the recipient to the server 100.

In this embodiment, the receiver information sent by the second terminal 400 based on the reception notification may include real name information of the receiver account in addition to the account information of the receiver account.

Referring again to the example shown in fig. 6H, assuming that the payee selects an a bank deposit card with a tail number of XYX1 as the receiving account in this example, the second terminal 400 needs to transmit account information of the receiving account and real name information to the server 100. Before sending, the second terminal 400 may obtain service authorization of the payee to allow the second terminal 400 to send the bank card number and the real name information of the bank deposit card a as the payee account to the server 100.

Referring to fig. 6I, a service authorization interface 609 is illustratively shown which may display in an area 609-1 information that the second terminal 400 needs to obtain and send to the first terminal 300 and a consent button 609-2 that the payee (recipient) may operate to grant service authorization. Further, to ensure information security, the identity of the payee may be verified to ensure that the service authorization operation was performed by the payee himself.

For example, as shown in the authentication interface 610 of fig. 6J, the payee may input a payment password corresponding to the payee account on the authentication interface 610, thereby implementing authentication.

When the second terminal 400 detects an operation of agreeing to the service authorization and the identity verification of the payee is passed, account information and real-name information of the payee account may be acquired, and receiver information may be generated, where the receiver information carries the account information and the real-name information of the payee account.

After the server 100 receives the recipient information, the real name information in the recipient information may be first compared with the name input by the roll-out party. If the two are different, the obtained information of the receiving party is wrong, and error prompt information can be output. If the two are the same, indicating that the obtained recipient information is substantially correct, a first amount of the first type of data may be transferred from the transferor account to the recipient account based on the received transferor information and recipient information as described above.

In an embodiment of the present application, an interactive process of resource data transfer performed by the server 100, the resource transfer processing terminal 200, the first terminal 300, and the second terminal 400 may be as follows:

s001, the first terminal 300 determines a resource data transfer manner in response to the trigger operation for resource data transfer, and determines a service type identifier corresponding to the resource data transfer manner.

S002, the first terminal 300 receives the transfer party information input by the transfer party, where the transfer party information includes the service type identifier, the account information of the transfer party account, the first type identifier and the first amount of the first type data that needs to be transferred from the transfer party account, and the second type identifier and the second amount of the second type data that needs to be received by the receiving party account.

S003, if the first number reaches the target number, the first terminal 300 prompts to input the name of the receiving party, and adds the name of the receiving party to the information of the forwarding party.

S004, the first terminal 300 transmits the transferee information to the server 100.

And S005, the server 100 receives the transfer party information and outputs prompting information n1 aiming at the transfer party account, wherein the prompting information n1 is used for prompting the input of the payment password of the transfer party account.

S006, the first terminal 300 receives and displays the prompt information n1, and transmits the payment password to the server 100 upon receiving the payment password input based on the prompt information n 1.

S007, the server 100 performs password authentication on the roll-out party account according to the payment password, and if the password authentication passes, deducts a first amount of first type data from the roll-out party account, generates a display page including a first type identifier, the first amount, a second type identifier, and a second amount, and sends a page link of the display page as a receiving notification to the first terminal 300.

S008, the first terminal 300 displays the reception notification, and shares the reception notification to the second terminal 400 corresponding to the sharing operation when the sharing operation for the reception notification is detected.

S009, the second terminal 400 displays the reception notification, and displays the display page in response to a trigger operation for the reception notification.

And S010, the second terminal 400 responds to the confirmation receiving operation executed on the display page, and displays a receiving party account acquisition interface, wherein at least one account information bound by the second terminal 400 is displayed on the receiving party account acquisition interface.

S011, in response to the selecting operation, the second terminal 400 determines one of the accounts corresponding to the selecting operation as a recipient account for receiving the resource data from the account corresponding to the at least one account information.

S012, the second terminal 400 generates recipient information including account information of a recipient account and real name information of the recipient, and displays a service authorization interface including at least a part of the recipient information.

S013, the second terminal 400 responds to the authorization confirmation operation on the service authorization interface, and sends the information about the receiving party to the server 100.

S014, the server 100 generates a first packet according to a given format, fills the first packet with the receiver information, the transfer-out information, and the service type identifier to obtain a second packet, and determines the second packet as a transfer packet.

And S015, the server 100 performs anti-fraud scanning based on the transfer message, identifies the service type identifier after the anti-fraud scanning is passed, calls the target service interface to process the transfer message if the service type identifier is the target identifier, and sends the transfer message to the resource transfer processing terminal 200 corresponding to the service type identifier.

S016 is that the resource transfer processing terminal 200 checks whether the account of the receiving party exists according to the forwarding party information and the receiving party information in the transfer message.

S017, if the account of the receiving party does not exist, the resource transfer processing end 200 notifies the server 100 to return the first type data with the first amount deducted to the account of the receiving party.

Correspondingly, the server 100 generates first transfer failure information and second transfer failure information, wherein the first transfer failure information is used for prompting the transfer failure of the resource data of the transfer party, and the second transfer failure information is used for prompting the transfer failure of the resource data of the receiving party. The server 100 transmits the first transfer failure information to the first terminal 300 and transmits the second transfer failure information to the second terminal 400.

S018, if the account of the receiving party exists, the resource transfer processing terminal 200 transfers a second amount of the second type data to the account of the receiving party, and notifies the server 100 that the transfer of the resource data is successful.

S019, the server 100 generates first transfer success information and second transfer success information, where the first transfer success information is used to prompt that the transfer of the resource data of the transfer party is successful, and the second transfer success information is used to prompt that the transfer of the resource data of the receiving party is successful.

S020, the server 100 sends the first transfer success information to the first terminal 300, and sends the second transfer success information to the second terminal 400.

Referring again to FIG. 9, where the resource data transfer is a money transfer, an overview of the flow of money transfers is shown. The sender application (e.g., the second client 320) of the first terminal 300 may obtain the inputted sender information and transmit the sender information to the server 100, and the server 100 may deduct money according to the sender information (e.g., fig. 6C-6D), and after deducting money, generate a receipt notification according to the sender information, and transmit the receipt notification to the second terminal 400. The second terminal 400 transmits payee information, which may include the bound card account number of the first client 410 of the second terminal 400, to the server 100 based on the receipt notification. The server 100 may assemble a remittance message according to the remitter information, the recipient information, and a service type identifier determined based on a resource data transfer manner selected by the remitter. The money transfer message may then be fraud-resistant scanned, which may be performed by the server 100. After fraud-resistant scanning, the money transfer message may be channel routed for funds.

In the money channel routing phase, the server 100 may determine the resource transfer processing end 200 for receiving the money transfer message according to the service type identifier in the money transfer message. Based on the difference of the service type identifiers in the remittance message, the remittance message can be sent to a unionpay server, or sent to a corresponding agent server through common cross-border remittance routing and remittance routing matching, and then the agent server transfers the money to a payee. The proxy server here may be determined by the money receiving money type selected by the sender. For example, if the sender selects AAA currency, the sender may send the AAA currency to the AAA proxy server; if the sender selects BBB currency, the sender can send the BBB currency to the BBB proxy server; the sender selects CCC currency, and may send it to the CCC proxy server.

In this embodiment, the resource transfer processing terminal 200 may verify the account of the receiving party, for example, determine whether the account of the receiving party really exists, if so, the account of the receiving party may successfully receive the money, and the second terminal 400 may display a successful money receiving interface, such as 611 shown in fig. 6K.

Taking the example that the second client 320 is a virtual bank, fig. 10 shows the user flow and the fund flow corresponding to fig. 6A to 6K. In the user process, a sender may initiate a remittance deduction through a virtual bank, generate a receiving notification according to sender information, share the receiving notification to a first client, select a binding card as a receiving account at the first client 410 by the receiver, return the receiver information including the receiving account information to the virtual bank, send money according to the sender information and the receiver information by the virtual bank, and directly receive remitted money through the binding card of the receiver.

Here, if the sender remits AAA currency and the receiver receives BBB currency, the fund flow may be that, after the sender formally initiates remittance at the virtual bank client, the virtual bank may deduct AAA currency from the remittance account, the AAA currency may be remitted to the resource transfer processing terminal 200 (e.g., a unionpay server), and the unionpay server may further remit a second amount of BBB currency corresponding to the first amount of AAA currency to the receiver.

Referring to FIG. 11, an order state machine corresponding to the example shown in FIGS. 6A-6K is shown. Both in an initial state before obtaining sender information and initiating a money transfer. After obtaining the sender information and initiating the remittance based on the sender information, the remitter may enter a to-be-paid state, and at this time, the sender may select to pay the money to be transferred through fig. 6C and 6D, thereby entering a paid-up to-be-posted state; the sender may also choose to cancel the money transfer, thereby entering a money transfer cancelled state.

The paid money to be credited state is a state in which the sender has paid money but has not been successfully deducted. And when the money is successfully deducted, entering a state of being checked out and waiting for sharing. In the posted to-be-shared state, the sender can select to share the generated receipt notification to the receiver, thereby entering the shared to-be-received state; the sender may also choose to cancel the remittance, thereby entering an order cancellation refund state. In the shared to-receive state, the sender may also choose to cancel the remittance, thereby entering the order cancellation refund state. It is understood that when the receiver selects a withdrawal item based on the receipt notice or the receiver does not confirm the receipt notice after a timeout, it may cause the remittance cancellation to enter an order cancellation in-refund state. Upon a successful refund, an order cancellation refund state may be entered, at which point the deducted money may be returned to the money transfer account.

In the shared pending funds transfer state, if no cancellation of the money transfer occurs, the in-money transfer state may continue. In the remittance in-remittance state, if the remittance fails, the remittance failed and refunded state can be entered, and the deducted money can be returned to the remittance account; otherwise, a money transfer success status may be entered.

Referring to fig. 12, fig. 12 is a flowchart illustrating a resource data transfer method according to an embodiment of the present application, which can be applied to the second terminal 400 shown in fig. 1. The method may comprise the steps of:

s1210, receiving a receiving notification sent by the terminal, wherein the receiving notification is used for prompting that resource data needing to be received exist.

S1230, in response to the confirmation operation for receiving the notification, acquiring account information of a receiver account, where the receiver account is an account for receiving the resource data.

S1250, generating the receiver information of the resource data, wherein the receiver information comprises account information of the account of the receiver.

S1270, sending the receiver information to a server, wherein the server is used for obtaining transfer party information, the transfer party information comprises account information of a transfer party account and the quantity of the resource data needing to be transferred from the transfer party account, and the quantity of the resource data is transferred from the transfer party account to the receiver account according to the transfer party information and the receiver information.

For the detailed implementation process of S1210-S1270, reference may be made to the related description of the processing flow of the second terminal 400 in the foregoing embodiment, and details are not repeated here.

Alternatively, the step of acquiring the account information of the recipient account in S1230 may be implemented by the steps of fig. 13.

S1231, displaying at least one account information bound by the terminal.

S1232, in response to the selection operation, determining the account information corresponding to the selection operation as the account information of the account of the receiving party from the at least one account information.

Here, the detailed implementation process of S1231 and S1232 may refer to the above detailed process for determining the account of the receiving party by the second terminal, and is not described herein again.

Optionally, the resource data transfer method provided in this embodiment may further include a flow shown in fig. 14.

And S1221, responding to the account information binding operation, and binding the obtained new account information to the second terminal.

S1222, displaying the new account information.

For the detailed implementation process of S1221 and S1222, reference may be made to the content of binding new account information to the second terminal 400 in the foregoing embodiment, and details are not described herein again.

By the method provided by the embodiment, the receiver information can be provided for the transfer party in the money transfer process, and data support is provided for simplifying the operation in the money transfer process and reducing the error probability of the money transfer information.

Referring to fig. 15, a block diagram of a resource data transfer apparatus according to an embodiment of the present application is shown. The apparatus 1500 may include a receiving module 1510, a displaying module 1520, a sharing module 1530, and a transferring module 1540.

The obtaining module 1510 is configured to obtain transfer party information of the resource data, where the transfer party information includes account information of a transfer party account and a quantity of the resource data that needs to be transferred from the transfer party account.

The display module 1520 is configured to display a receiving notification of the resource data, where the receiving notification is used to prompt that the resource data that needs to be received exists.

The sharing module 1530 is configured to respond to a sharing operation for the receiving notification, and send the receiving notification to a terminal corresponding to the sharing operation, where the terminal is configured to obtain receiver information based on the receiving notification and send the receiver information to a server, where the receiver information includes account information of a receiver account.

The transfer module 1540 is configured to receive transfer success information, where the transfer success information is sent by the server after the transfer of the amount of the resource data from the transfer party account to the receiving party account according to the transfer party information and the receiving party information.

Optionally, in the apparatus 1500, the account of the receiving party is an account that is determined by the terminal in response to the confirmation operation for receiving the notification from the account corresponding to the bound at least one account information and is used for receiving the resource data.

Optionally, in the apparatus 1500, the resource data is a first type of data, and the number is a first number, and the apparatus further includes a generating module. The generating module may be configured to generate the reception notification of the resource data before the display module 1520 displays the reception notification by: acquiring an identifier of second type data required to be received by the account of the receiver, and taking the acquired identifier as the second type identifier; determining the quantity of second type data required to be received by the account of the receiving party based on the first quantity, the first type identification of the first type data and the second type identification, and taking the determined quantity as a second quantity; and generating the receiving notice according to the first type identification, the first quantity, the second type identification and the second quantity.

Optionally, in the apparatus 1500, the generating module generates the notification reception manner according to the first type identifier, the first number, the second type identifier, and the second number, and includes: generating a display page comprising the first type identifier, the first number, the second type identifier and the second number; determining a page link of the display page as the reception notification.

Optionally, the server 100 may be configured to generate a transfer packet according to the information of the forwarding party and the information of the receiving party, and forward the transfer packet to the resource transfer processing end. The resource transfer processing terminal 200 may be configured to transfer the amount of resource data from the transfer party account to the receiving party account according to the transfer packet.

Optionally, the apparatus 1500 may further comprise a verification module. The verification module may be configured to send the transfer party information to the server 100 before the display module 1520 displays the receiving notification of the resource data, where the server 100 is configured to perform password verification on the transfer party account according to the transfer party information; and if the password is verified, deducting the first amount of the first type data from the transfer-out party account, wherein the resource transfer processing terminal 200 is specifically configured to transfer the second amount of the second type data to the receiving party account.

Alternatively, the verification module may be further configured to, when it is determined that the first number reaches the target number, acquire the name of the recipient and transmit the name of the recipient to the server 100 before the display module 1520 displays the reception notification of the resource data. The server 100 is configured to obtain real-name information of the account of the receiving party from the information of the receiving party, compare whether the name of the receiving party is the same as the real-name information of the account of the receiving party, and if the name of the receiving party is the same as the real-name information of the account of the receiving party, transfer the first amount of the first type data from the account of the transferring party to the account of the receiving party according to the information of the transferring party and the information of the receiving party.

Optionally, the roll-out party information further includes a service type identifier; the server 100 is configured to send the transfer party information and the receiving party information to the resource transfer processing terminal 200 according to a manner corresponding to the service type identifier.

Optionally, the manner in which the server 100 sends the information of the forwarding party and the information of the receiving party to the resource transfer processing end according to the manner corresponding to the service type identifier may be: identifying a service type identifier in the transfer message; if the service type identifier is a target identifier, calling a target service interface to process the information of the forwarding party and the information of the receiving party so as to forward the information of the forwarding party and the information of the receiving party to a resource transfer processing end corresponding to the target identifier.

Referring to fig. 16, fig. 16 is a block diagram of a resource data transfer apparatus according to an embodiment of the present application. The apparatus 1600 may include a receiving module 1610, an obtaining module 1620, a generating module 1630, and a transferring module 1640.

The receiving module 1610 is configured to receive a reception notification sent by a terminal, where the reception notification is used to prompt that resource data that needs to be received exists.

The obtaining module 1620 is configured to obtain account information of a receiver account in response to the confirmation operation for the receiving notification, where the receiver account is an account for receiving the resource data.

The generating module 1630 is configured to generate recipient information of the resource data, where the recipient information includes account information of the recipient account.

The transfer module 1640 is configured to send the receiver information to a server, where the transferor information includes account information of a transferor account and a quantity of the resource data that needs to be transferred from the transferor account, and transfer the quantity of the resource data from the transferor account to the receiver account according to the transferor information and the receiver information.

It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described apparatuses and modules may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, the coupling or direct coupling or communication connection between the modules shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or modules may be in an electrical, mechanical or other form.

In addition, functional modules in the embodiments of the present application may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode.

Referring to fig. 17, a block diagram of an electronic device according to an embodiment of the present application is shown. The electronic device 1700 may be the server 100, the first terminal 300, or the second terminal 400 shown in fig. 1.

Electronic device 1700 in the present application may include one or more of the following components: a processor 1710, a memory 1720, and one or more programs, wherein the one or more programs may be stored in the memory 1720 and configured to be executed by the one or more processors 1710, the one or more programs configured to perform a method as described in the aforementioned method embodiments.

Processor 1710 may include one or more processing cores. The processor 1710 interfaces various components throughout the electronic device 1700 using various interfaces and circuitry to perform various functions and process data for the electronic device 1700 by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 1720, as well as invoking data stored in the memory 1720. Alternatively, the processor 1710 may be implemented in hardware using at least one of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 1710 may integrate one or more of a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a modem, and the like. Wherein, the CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for rendering and drawing display content; the modem is used to handle wireless communications. It is to be appreciated that the modem can be implemented by a single communication chip without being integrated into the processor 1710.

Memory 1720 may include a Random Access Memory (RAM) or may include a Read-Only Memory (Read-Only Memory). The memory 1720 may be used to store an instruction, a program, code, a set of codes, or a set of instructions. The memory 1720 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for implementing at least one function (e.g., a touch function, a sound playing function, an image playing function, etc.), instructions for implementing various method embodiments, and the like. The storage data area may also store data (e.g., roll-out information, recipient information) created during use by the electronic device 1700, and/or the like.

Referring to fig. 18, a block diagram of a computer-readable storage medium according to an embodiment of the present application is shown. The computer readable medium 1800 has stored therein program code that can be invoked by a processor to perform the methods described in the above-described method embodiments.

The computer-readable storage medium 1800 may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read only memory), an EPROM, a hard disk, or a ROM. Alternatively, the computer-readable storage medium 1800 includes a non-transitory computer-readable storage medium. Computer-readable storage medium 1800 has storage space for program code 1810 for performing any of the method steps described above. The program code can be read from or written to one or more computer program products. Program code 1810 may be compressed, for example, in a suitable form.

Embodiments of the present application also provide a computer program product or a computer program comprising computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the resource data transfer method provided by the above-mentioned embodiment of the present application.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not necessarily depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

1. A method for transferring resource data, comprising:

acquiring transfer party information of resource data, wherein the transfer party information comprises account information of a transfer party account and the quantity of the resource data needing to be transferred from the transfer party account;

displaying a receiving notice of the resource data, wherein the receiving notice is used for prompting that the resource data needing to be received exist;

responding to a sharing operation aiming at the receiving notification, and sending the receiving notification to a terminal corresponding to the sharing operation, wherein the terminal is used for acquiring receiver information based on the receiving notification and sending the receiver information to a server, and the receiver information comprises account information of a receiver account;

receiving transfer success information, wherein the transfer success information is sent by the server after the transfer of the amount of the resource data from the transfer party account to the receiving party account according to the received transfer party information and the receiving party information.

2. The method according to claim 1, wherein the account of the receiving party is an account for receiving the resource data, which is determined by the terminal in response to the confirmation operation for receiving the notification from the account corresponding to the bound at least one account information.

3. The method according to claim 1 or 2, wherein the resource data is a first type of data, the amount is a first amount, and before the displaying the reception notification of the resource data, the method further comprises:

acquiring an identifier of second type data required to be received by the account of the receiver, and taking the acquired identifier as the second type identifier;

determining the quantity of second type data required to be received by the account of the receiving party based on the first quantity, the first type identification of the first type data and the second type identification, and taking the determined quantity as a second quantity;

and generating the receiving notice according to the first type identification, the first quantity, the second type identification and the second quantity.

4. The method of claim 3, wherein generating the reception notification according to the first type identifier, the first number, the second type identifier, and the second number comprises:

generating a display page comprising the first type identifier, the first number, the second type identifier and the second number;

determining a page link of the display page as the reception notification.

5. The method according to claim 3, wherein the server is configured to generate a transfer packet according to the forwarding party information and the receiving party information, and forward the transfer packet to a resource transfer processing end; and the resource transfer processing terminal is used for transferring the quantity of the resource data from the transfer party account to the receiving party account according to the transfer message.

6. The method of claim 5, wherein prior to said displaying a notification of receipt of said resource data, said method further comprises:

sending the transfer party information to the server, wherein the server is used for carrying out password verification on the transfer party account according to the transfer party information;

and if the password passes the verification, deducting the first amount of the first type data from the transfer-out party account, wherein the resource transfer processing end is used for transferring the second amount of the second type data to the receiving party account.

7. The method of claim 3, wherein prior to said displaying a notification of receipt of said resource data, said method further comprises:

if the first quantity reaches the target quantity, acquiring the name of the receiver;

and sending the name of the receiver to the server, wherein the server is used for acquiring real-name information of the account of the receiver from the information of the receiver, comparing whether the name of the receiver is the same as the real-name information of the account of the receiver, and if so, transferring the first amount of the first type data from the account of the transfer party to the account of the receiver according to the information of the transfer party and the information of the receiver.

8. The method according to claim 5, wherein the transfer-out party information further includes a service type identifier, and the server is configured to send the transfer-out party information and the receiving party information to the resource transfer processing terminal in a manner corresponding to the service type identifier.

9. The method according to claim 8, wherein the server sends the forwarding party information and the receiving party information to the resource transfer processing terminal in a manner corresponding to the service type identifier, and the manner is as follows:

and identifying the service type identifier, and if the service type identifier is a target identifier, calling a target service interface to process the information of the roll-out party and the information of the receiving party so as to send the information of the roll-out party and the information of the receiving party to a resource transfer processing end corresponding to the target identifier.

10. A method for transferring resource data, comprising:

receiving a receiving notification sent by a terminal, wherein the receiving notification is used for prompting that resource data needing to be received exist;

responding to the confirmation operation aiming at the receiving notification, and acquiring account information of a receiver account, wherein the receiver account is used for receiving the resource data;

generating receiver information of the resource data, wherein the receiver information comprises account information of the account of the receiver;

and sending the receiver information to a server, wherein the server is used for acquiring transfer party information, the transfer party information comprises account information of a transfer party account and the quantity of the resource data which needs to be transferred from the transfer party account, and transferring the quantity of the resource data from the transfer party account to the receiver account according to the transfer party information and the receiver information.

11. The method of claim 10, wherein obtaining account information for the account of the recipient comprises:

displaying at least one account information bound by the terminal;

and responding to a selection operation, and determining account information corresponding to the selection operation as account information of the account of the receiver from the at least one piece of account information.

12. A resource data transfer apparatus, comprising:

the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring transfer party information of resource data, and the transfer party information comprises account information of a transfer party account and the quantity of the resource data which need to be transferred from the transfer party account;

the display module is used for displaying a receiving notice of the resource data, and the receiving notice is used for prompting that the resource data needing to be received exist;

the sharing module is used for responding to the sharing operation aiming at the receiving notification and sending the receiving notification to a terminal corresponding to the sharing operation, the terminal is used for acquiring receiver information based on the receiving notification and sending the receiver information to a server, and the receiver information comprises account information of a receiver account;

and the transfer module is used for receiving transfer success information, wherein the transfer success information is sent by the server after the transfer of the amount of the resource data from the transfer party account to the receiving party account according to the received transfer party information and the receiving party information.

13. A resource data transfer apparatus, comprising:

the receiving module is used for receiving a receiving notification sent by a terminal, wherein the receiving notification is used for prompting that resource data needing to be received exist;

an obtaining module, configured to obtain account information of a receiver account in response to a confirmation operation for the reception notification, where the receiver account is an account used for receiving the resource data;

the generation module is used for generating receiver information of the resource data, and the receiver information comprises account information of the account of the receiver;

the transfer module is used for sending the receiver information to a server, the server is used for obtaining transfer party information, the transfer party information comprises account information of a transfer party account and the quantity of the resource data which need to be transferred from the transfer party account, and the quantity of the resource data is transferred from the transfer party account to the receiver account according to the transfer party information and the receiver information.

14. An electronic device, comprising:

one or more processors;

a memory;

one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs configured to perform the method of any of claims 1-11.

15. A computer-readable storage medium, characterized in that the computer-readable storage medium stores program code that can be invoked by a processor to perform the method according to any one of claims 1 to 11.