CN112308543A

CN112308543A - Data transfer method, device and equipment and computer storage medium

Info

Publication number: CN112308543A
Application number: CN201910672891.8A
Authority: CN
Inventors: 王倩玉; 李哲敏; 揭靓; 刘斌; 王健; 姚兵; 陈增雄; 吴嘉骏; 史卉萍; 江磊; 秦泗明; 王冲; 蒋有为
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-07-24
Filing date: 2019-07-24
Publication date: 2021-02-02

Abstract

The application discloses a data transfer method, a data transfer device, data transfer equipment and a computer storage medium, relates to the technical field of computers, and is used for providing a more convenient and faster transfer mode and improving the protection degree of personal information privacy of a user. The method comprises the following steps: sending a first transfer request to a background server of a transfer platform in response to a transfer operation instruction for transferring account data input by a transfer user, wherein the first transfer request carries a collection identifier of a collection user; responding to a transfer confirmation prompt message returned by the background server, and prompting a transfer user to perform transfer confirmation according to the transfer confirmation prompt message; and responding to the transfer confirmation operation instruction of the transfer user, and sending a transfer confirmation request for transferring the account data to the background server, so that the background server requests the trusted transfer mechanism to initiate the transfer of the account data to the collection mechanism where the collection user is located after receiving the transfer confirmation request.

Description

Data transfer method, device and equipment and computer storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a data transfer method, apparatus, and device, and a computer storage medium.

Background

With the development of electronic informatization, online transaction modes are more and more common, and the online transaction modes enable users to carry out transfer transaction without going out, so that the online transaction mode is more convenient and faster.

At present, when online account transfer is carried out, account transfer in the same institution can be generally realized through account transfer identification, while account transfer in a cross institution generally needs to fill in detail detailed information of a money receiving user, for example, information such as a money receiving institution where the money receiving user is located, a bank account number and a name of a receiver needs to be provided, and the account transfer can be initiated after all information is submitted. In addition, many users pay great attention to security of personal information privacy at present, and the above transfer mode needs to disclose more personal privacy and is also very disadvantageous to protection of personal information privacy.

Disclosure of Invention

The embodiment of the application provides a data transfer method, a data transfer device, data transfer equipment and a computer storage medium, which are used for simplifying a transfer mode and improving the safety of personal information.

In one aspect, a data transfer method is provided, the method including:

sending a first transfer request to a background server of a transfer platform in response to a transfer operation instruction for transferring account data input by a transfer user, wherein the first transfer request carries a collection identifier of a collection user;

responding to a transfer confirmation prompt message returned by the background server, and prompting a transfer user to perform transfer confirmation according to the transfer confirmation prompt message, wherein the transfer confirmation prompt message is generated when the background server sends a verification request to a trusted transfer mechanism based on the collection identifier and determines that the collection identifier passes verification based on a verification response message returned by the trusted transfer mechanism, and the verification request is used for requesting verification of the validity of the collection identifier;

and responding to the transfer confirmation operation instruction of the transfer user, and sending a transfer confirmation request for transferring the account data to the background server, so that the background server requests the trusted transfer mechanism to initiate the transfer of the account data to the collection mechanism where the collection user is located after receiving the transfer confirmation request.

In one aspect, a data transfer method is provided, the method including:

responding to a first transfer request sent by a terminal, and sending a verification request to a trusted transfer mechanism based on a collection identifier carried by the first transfer request;

sending a transfer confirmation prompt message to the terminal when the verification of the collection identification is determined to pass according to a verification response message returned by the credible transfer mechanism;

and responding to a confirmed account transfer request for transferring account data sent by the terminal, and initiating a second account transfer request to the credible account transfer mechanism, wherein the second account transfer request carries the collection identifier, so that the credible account transfer mechanism initiates the transfer of the account data to the collection mechanism where the collection user is located according to the collection identifier.

In one aspect, a data transfer apparatus is provided, the apparatus comprising:

the account transfer platform comprises a first sending unit, a second sending unit and a control unit, wherein the first sending unit is used for responding to an account transfer operation instruction for transferring account data input by an account transfer user and sending a first transfer request to a background server of the account transfer platform, and the first transfer request carries a collection identifier of a collection user;

the transfer prompting unit is used for responding to a transfer confirmation prompting message returned by the background server and prompting a transfer user to perform transfer confirmation according to the transfer confirmation prompting message, wherein the transfer confirmation prompting message is generated when the background server sends a verification request to a trusted transfer mechanism based on the collection identifier and determines that the collection identifier passes verification based on a verification response message returned by the trusted transfer mechanism, and the verification request is used for requesting verification of the validity of the collection identifier;

the first sending unit is further configured to send a transfer confirmation request for transferring account data to the background server in response to the transfer confirmation operation instruction of the transfer user, so that the background server receives the transfer confirmation request and requests the trusted account transfer mechanism to initiate transfer of the account data to the collection mechanism where the collection user is located.

Optionally, the first sending unit is configured to:

and responding to a transfer operation instruction input by a transfer user in a transfer page of a transfer platform, and sending a first transfer request to a background server of the transfer platform, wherein the first transfer request carries a collection identifier of a collection user input by the transfer user on the transfer page.

Optionally, the transfer prompting unit is configured to:

verifying the collection identification according to the transfer confirmation prompt message;

when the collection identification passes the verification, switching to a transfer confirmation page from the transfer page;

and monitoring whether the transfer user inputs the confirmed transfer operation instruction through the confirmed transfer page.

Optionally, the apparatus further includes a first output unit, configured to:

responding to a verification failure prompt message returned by the background server, and outputting prompt information according to the verification failure prompt message to prompt that the payment receiving identification fails to be verified; the verification failure prompt message is generated when the background server determines that the collection identification verification is not passed based on a verification response message returned by the trusted transfer agency.

Optionally, the device further comprises a page display unit and a cash register selection unit;

the first sending unit is also used for responding to a list display operation instruction input by a transfer user on the transfer page and sending a list acquisition request to the background server; the list display operation instruction is used for displaying a selectable cashier mechanism list;

the page display unit is used for displaying a gathering mechanism list display page according to a list acquisition response message returned by the background server, wherein the gathering mechanisms in the gathering mechanism list carried in the list acquisition response message are all mechanisms which can perform transfer confirmed by the background server;

the collection mechanism selecting unit is used for responding to a selection operation instruction input by a transfer user on the collection mechanism list display page and selecting the collection mechanism selected by the selection operation instruction;

the first sending unit is configured to generate the first transfer request according to the collection identifier and the collection mechanism identifier in response to the transfer operation instruction, and send the first transfer request to the background server.

Optionally, the verification of the payment receiving identifier includes:

registering the association information of the collection identification and at least one collection mechanism in the trusted transfer mechanism; alternatively, the first and second electrodes may be,

and the trusted transfer mechanism registers the related information of the collection mechanism corresponding to the collection identification and the collection mechanism identification.

Optionally, the apparatus further comprises a second output unit;

the first sending unit is further configured to send a first registration request to the background server in response to a registration operation instruction for registering collection information input by a user, where the first registration request carries collection information to be registered, and the collection information includes a collection identifier and account information associated with the collection identifier;

the second output unit is used for outputting a registration result according to a second registration response message returned by the background server; the second registration response message carries a registration result carried in a first registration response message returned to the background server by the trusted account transfer mechanism, and the first registration response message is returned to the background server by the trusted account transfer mechanism after the background server sends a second registration request to the trusted account transfer mechanism based on the collection information; the registration result is used to indicate whether the registration was successful.

In one aspect, a data transfer apparatus is provided, the apparatus comprising:

the second sending unit is used for responding to the first transfer request sent by the terminal and sending a verification request to the trusted transfer mechanism based on the collection identifier carried by the first transfer request;

the second sending unit is further used for sending a transfer confirmation prompt message to the terminal when the collection identification is confirmed to pass the verification according to the verification response message returned by the trusted transfer agency;

and the transfer initiating unit is used for responding to a transfer confirmation request for transferring the account data sent by the terminal and initiating a second transfer request to the credible transfer mechanism, wherein the second transfer request carries the collection identification, so that the credible transfer mechanism initiates the transfer of the account data to the collection mechanism where the collection user is located according to the collection identification.

Optionally, the transfer initiating unit is configured to:

generating a payment request according to the transfer confirmation request, and sending the payment request to the terminal, wherein the payment request is used for requesting a transfer user to pay the amount corresponding to the account data to be transferred;

and when the payment is determined to be successful according to the payment response message returned by the terminal, generating the second transfer request, and sending the second transfer request to the trusted transfer agency.

Optionally, the second sending unit is further configured to:

responding to a first registration request sent by a terminal, and sending a second registration request to the trusted transfer agency based on collection information carried by the first registration request; the collection information comprises a collection identifier and account information associated with the collection identifier;

generating a second registration response message according to the first registration response message returned by the credible transfer mechanism, and sending the second registration response message to the terminal; the first registration response message carries a registration result indicating whether the registration is successful, and the second registration response message carries the registration result carried by the first registration response message.

In one aspect, a computer device is provided, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of the above aspect when executing the program.

In one aspect, a computer-readable storage medium is provided that stores processor-executable instructions for performing the method of the above aspect.

In the embodiment of the application, when account data are transferred, account transfer can be carried out through the collection identification of a collection user, the background server can request the trusted account transfer mechanism to verify the collection identification, and once the verification is passed, the transfer of the account data can be initiated after the account transfer user confirms the account transfer. Therefore, the transfer user can complete the transfer operation through the receiving identification of the receiving user without filling excessive information of the receiving user, the information required by the transfer of the user is reduced, a more convenient and quicker transfer mode is provided for the user, the transfer operation is simplified, the error rate of filling the information of the receiving user is reduced, and the transfer success rate is improved. In addition, the information to be filled in can be only the collection identification, and the collection user only needs to provide the collection identification of the collection user for the transfer user without providing additional personal information, so that the possibility of revealing the personal information is reduced, and the personal information privacy protection degree of the collection user is improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only the embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.

FIG. 1 is a schematic diagram of a transfer page in the prior art;

fig. 2 is a schematic view of an application scenario provided in an embodiment of the present application;

FIG. 3 is a system architecture diagram according to an embodiment of the present application;

FIG. 4 is a schematic flow chart illustrating information related to the registered account of the receiving user according to an embodiment of the application;

FIG. 5 is a schematic diagram of an interface for registering a payee according to an embodiment of the application;

fig. 6 is a schematic flowchart of a data transfer method according to an embodiment of the present application;

FIG. 7 is a schematic diagram of an interface for a transfer user to initiate a transfer according to an embodiment of the application;

FIG. 8 is a schematic diagram of an interface provided by an embodiment of the present application for a user to select a non-default checkout mechanism;

FIG. 9 is a schematic diagram of an interface for prompting an illegal payment identification according to an embodiment of the present application;

FIG. 10 is a schematic illustration of a transfer confirmation page provided by an embodiment of the application;

FIG. 11 is a schematic interface diagram of a payment page provided in an embodiment of the present application;

FIG. 12 is a schematic view of a transfer result display page provided by an embodiment of the present application;

FIG. 13 is a diagram illustrating a history transfer list displayed in a quick transfer function page according to an embodiment of the present application;

fig. 14 is a schematic flow diagram of an actual physical fund flow provided in the embodiment of the present application;

fig. 15 is a schematic flow diagram of a virtual fund flow in a transfer platform according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of a data transfer apparatus according to an embodiment of the present application;

fig. 17 is a schematic structural diagram of another data transfer device according to an embodiment of the present application;

fig. 18 is a schematic structural diagram of a computer device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions in the embodiments of the present application will be described clearly and completely with reference to the accompanying drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application. In the present application, the embodiments and features of the embodiments may be arbitrarily combined with each other without conflict. Also, while a logical order is shown in the flow diagrams, in some cases, the steps shown or described may be performed in an order different than here.

For the convenience of understanding the technical solutions provided by the embodiments of the present application, some key terms used in the embodiments of the present application are explained first:

transfer platform: the transfer platform can be a transfer platform provided by each large banking institution, such as an internet bank, a mobile phone bank or a bank Application (APP), or can also be a transfer platform provided by each large financial institution, or can also be various electronic payment platforms.

Transfer user: refers to a roll-out user, i.e., a user that rolls out account data.

The payee: the user who transfers the account data into the account data transfer system is referred to as a transfer-in user.

A trusted transfer agency: trusted money transfer institutions refer to money transfer systems or platforms provided by institutions with high confidence, such as those provided by government agencies (e.g., financial authorities).

A collection identifier: the identifier that is associated with the collection account and registered by the collection user in the trusted account transfer mechanism may be, for example, a mobile phone number or an email address, and of course, may also be other identifiers, such as a registration number when the user registers, and the like, which is not limited in this embodiment of the application.

In addition, the term "and/or" herein is only one kind of association relationship describing an associated object, and means that there may be three kinds of relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this document generally indicates that the preceding and following related objects are in an "or" relationship unless otherwise specified. Furthermore, references to "first" or "second", etc. herein are only used to distinguish between similar items and not to describe a particular order or sequence.

The transfer operation essentially manifests itself in the accounting process as a transfer of account data between different accounts, i.e., the transfer of account data corresponding to one account to another account, typically occurring during a transaction, e.g., a payment is a data transfer from a buyer's account to a seller's account. When transferring accounts on line, the account transfer in the same institution can be realized through the account transfer identification, and the account transfer of the cross institution generally needs to fill in the detailed information of a payment receiving user in detail. The current cross-institution transfer is usually to transfer to bank cards of other banks through online transfer tools such as internet banks or mobile phone banks of bank institutions, or the cross-institution transfer can also be to transfer to bank cards of various banks through an electronic payment platform, as shown in figure 1, the transfer page diagram is a transfer page diagram of transferring to bank cards of banks through the electronic payment platform, wherein information such as a payee institution where a payee is located, a bank card number and a payee name needs to be provided, the transfer can be initiated after all information is submitted, the information which needs to be provided when the user initiates the cross-institution transfer is complicated, particularly, the bank account card number is usually long, is difficult to remember, is inconvenient to fill, delays time, and is easy to have the problems of wrong filling or failed matching of the payee name, and the transfer fails once the wrong filling is performed, and needs to be refilled again, the operation is more complicated. In addition, many users pay great attention to security of personal information privacy at present, and the above transfer mode needs to disclose more personal privacy and is also very disadvantageous to protection of personal information privacy.

The applicant analyzes the prior art and finds that, in the prior art, when transferring money, all information of a receiving user is provided by the transferring user, so that the problem of redundant information exists, and because the information needs to be filled in to initiate the transferring money, the receiving user needs to provide the information to the transferring user, so that the risk of revealing personal information privacy exists, therefore, if the problems need to be solved, the information of the receiving user needs to be hidden from the transferring user, but in order to distinguish the receiving user, the transferring user needs to be identified through a certain receiving identifier, so that the user only needs to provide the receiving identifier when transferring money, the information of too many receiving users does not need to be provided, and on the other hand, the protection degree of the personal information privacy of the receiving user is correspondingly higher.

In view of the analysis and consideration, the embodiment of the application provides a data transfer method, when account data is transferred, account can be transferred through a collection identifier of a collection user, a background server can request a trusted account transfer mechanism to verify the collection identifier, and once the verification is passed and the account transfer is confirmed by the account transfer user, the transfer of the account data can be initiated. Therefore, the transfer user can complete the transfer operation through the collection identification of the collection user without filling excessive information of the collection user, the information required for the transfer of the user is reduced, a more convenient and quicker transfer mode is provided for the user, meanwhile, the error rate of filling the information of the collection user is reduced, the transfer success rate is improved, and the transfer experience of the user is improved. In addition, the information to be filled in can be only the collection identification, and the collection user only needs to provide the collection identification of the collection user for the transfer user without providing additional personal information, so that the personal information privacy protection degree of the collection user is improved.

In the embodiment of the application, it is considered that one user may set account numbers in a plurality of banking institutions or financial institutions, that is, one collection identifier may be associated with accounts of a plurality of institutions, so that the user may provide a collection identifier and a collection institution identifier, and may set one collection institution as a default collection institution, or of course, the user may select a collection institution from a collection institution list. When the user selects the collection mechanism, in order to avoid that the transfer user directly sees the collection mechanism where the collection user is located, all the collection mechanisms can be displayed in the collection mechanism list, so that the transfer user cannot directly receive the collection mechanism where the transfer user is located, and the personal information of the collection user is protected to a certain extent. In addition, the collection mechanism displayed in the collection mechanism list in the embodiment of the application is a mechanism which can transfer accounts and is confirmed by the background server, and the collection mechanism selected by the account transfer user is a mechanism which can transfer accounts, so that the success rate of account transfer is improved.

In the embodiment of the application, in order to transfer accounts conveniently, a collection user can preset a default collection mechanism, so that the user does not need to select the collection mechanism, the collection mechanism can automatically transfer to the default collection mechanism set by the collection user during subsequent account transfer, the operation of the transfer user is reduced, and the personal information privacy protection degree of the collection user is improved.

After introducing the design concept of the embodiment of the present application, some simple descriptions are provided below for application scenarios to which the technical solution of the embodiment of the present application can be applied, and it should be noted that the application scenarios described below are only used for describing the embodiment of the present application and are not limited. In a specific implementation process, the technical scheme provided by the embodiment of the application can be flexibly applied according to actual needs.

Please refer to fig. 2, which is an application scenario to which the technical solution in the embodiment of the present application can be applied, and in the scenario, the application scenario may include a terminal 101, a backend server 102, a trusted transfer agency 103, a collection agency 104, and a terminal 105.

The terminal 101 may be a mobile phone, a Personal Computer (PC), a tablet computer (PAD), a Personal Digital Assistant (PDA), a notebook computer, or an intelligent wearable device (e.g., an intelligent watch and an intelligent bracelet). The application provided by the bank, the financial institution or the payment platform, etc. may be installed in the terminal 101, or a website provided by the bank, the financial institution or the payment platform, etc. may be opened, and the application or the website may implement the function of the method to be executed by the terminal side in the data transfer method provided in the embodiment of the present application, so that a user transferring accounts through the application or the website may initiate a transfer by using the method to be executed by the terminal side in the data transfer method provided in the embodiment of the present application.

The terminal 101 may include one or more processors 1011, memory 1012, an I/O interface 1013 for interacting with the server 102, and a display panel 1014, among other things. The memory 1012 of the terminal 101 may store program instructions of the application or the website (including program instructions of the data transfer method provided by the embodiment of the present application), and when the program instructions are executed by the processor 1011, the program instructions can be used to implement the functions of the application or the website and the data transfer method provided by the embodiment of the present application, and display a corresponding display page on the display panel 1014.

It should be noted that, although only one terminal 101 is shown in fig. 2, in practical applications, there may be many terminals 101 installed with the application or capable of opening the website, and therefore, the terminal 101 may be any one of the terminals 101.

The backend server 102 may be a backend server included as the above-described application or website. Backend server 102 may include one or more processors 1021, memory 1022, an I/O interface 1023 to interact with the terminal, an I/O interface 1024 to interact with a trusted account transfer authority, and so on. The memory 1022 may store program instructions of a method to be executed by the backend server in the data transfer method provided by the embodiment of the present application, and when the program instructions are executed by the processor 1021, the method to be executed by the backend server in the data transfer method provided by the embodiment of the present application may be implemented, so as to help a transfer user initiate transfer. In addition, the background server 102 may also be configured with a database, which may be used to store the identity authentication information of each user and information such as historical transfer orders.

The trusted account transfer 103 may be a trusted account transfer platform provided by a device of a trusted account transfer, such as a relevant institution managing account data transfer in a government institution, and the receiving user may register in the trusted account transfer 103 to associate the receiving identifier with account information that the receiving user wants to receive, so that when the transferring user transfers money to the receiving user, only the receiving identifier of the receiving user needs to be provided, and the transfer request may be sent to the corresponding receiving institution through the trusted account transfer 103, thereby completing the transfer.

Trusted transfer institution 103 may include one or more processors 1031, memory 1032, an I/O interface 1033 to interact with a background server, and an I/O interface 1034 to interact with a checkout institution, among other things. The memory 1032 may store program instructions of the auxiliary transfer function of the trusted transfer mechanism 103, and when the program instructions are executed by the processor 1031, the auxiliary transfer function of the trusted transfer mechanism 103 may be implemented, so as to help a transfer user initiate a transfer to a collection institution. In addition, the trusted account transfer authority 103 may further configure a database, and the database may be used to store information such as an association relationship between the receipt identifier of each receiving user and each account information.

The collection 104 may be any collection device, such as a bank, financial institution, or payment platform. Gathering mechanism 104 may include one or more processors 1041, memory 1042, I/O interface 1043 for interacting with trusted transfer mechanisms, I/O interface 1044 for interacting with terminals, and the like. The memory 1042 may store program instructions of the posting function of the cashing mechanism 104, and when executed by the processor 1041, may implement executing corresponding posting function logic when receiving a transfer request. In addition, trusted account transfer institution 104 may be configured with a database that may be used to store account-related information for users that open accounts at the institution.

It should be noted that the embodiments of the present application are equally applicable to transfers within the same institution, i.e., the collection institution and the backend server 102 may be the same device.

The terminal 105 may be a mobile phone, a PC, a PAD, a PDA) laptop or a terminal device such as a smart wearable device (e.g., a smart watch and a smart bracelet). The application provided by the collection institution 104 or a website provided by the collection institution 104 in the terminal 105 is used for receiving prompt information sent after the collection institution 104 enters the account of the payment receiving user and inquiring whether the account transfer is successfully entered. The terminal 105 may include one or more processors 1051, memory 1052, an I/O interface 1053 to interact with a checkout authority, and a display panel 1054, among other things. Among other things, the memory 1052 of the terminal 105 may store program instructions for an application or website provided by the cash register 104, which when executed by the processor 1051, can be used to implement the functions of the application or website and display the corresponding display page on the display panel 1054.

The devices that need to communicate can be connected through one or more networks for communication, but the devices that need to communicate are not limited to the devices connected in fig. 2, and can communicate through the networks when any device has a communication requirement. The network may be a wired network or a WIreless network, for example, the WIreless network may be a mobile cellular network, or may be a WIreless-Fidelity (WIFI) network, and of course, may also be other possible networks, which is not limited in this embodiment of the present application.

Illustratively, a transfer user can initiate transfer in an application in the terminal 101, wherein a transfer request can carry a collection identifier of the receiving user, the background server 102 can verify the validity of the collection identifier to the trusted transfer mechanism 103 according to the collection identifier in the transfer request, when the collection identifier is verified and the transfer is confirmed by the transfer user, the background server 102 can request the trusted transfer mechanism 103 to initiate transfer to a receiving mechanism 104 where the receiving user is located, the trusted transfer mechanism 103 forwards the transfer request to the receiving mechanism 104, and the receiving mechanism 104 can complete subsequent posting logic based on the transfer request, thereby completing the transfer.

Of course, the method provided in the embodiment of the present application is not limited to be used in the application scenario shown in fig. 2, and may also be used in other possible application scenarios, and the embodiment of the present application is not limited. The functions that can be implemented by each device in the application scenario shown in fig. 2 will be described in the following method embodiments, and will not be described in detail herein.

As shown in fig. 3, the system architecture of the transfer system according to the embodiment of the present application is schematically illustrated, and the transfer system includes a transfer service subsystem, a payment subsystem, and a trusted transfer agency system, where the transfer service subsystem and the payment subsystem may be implemented by the backend server shown in fig. 2, and the trusted transfer agency system may be implemented by the trusted transfer agency shown in fig. 2.

The transfer service subsystem can comprise an inquiry component module, a service processing module, an order processing module, an account processing module and a batch processing module, and the payment subsystem and the trusted transfer agency system can also comprise different functional modules. Each module is used for realizing different functions, and each module can also comprise sub-modules for realizing different sub-functions. The following description is made for each functional module of different systems.

1. Transfer business subsystem

- -query component Module

Identity authentication (KYC) information checking submodule: and checking whether the transfer user has corresponding KYC information, namely confirming whether the transfer user passes identity authentication.

Anti-Money Laundering (Anti-Money Laundering, AML) blacklist check submodule: users who are on the AML blacklist are those who are not allowed to transfer to them, and therefore, after the transfer user initiates the transfer, the receiving user is checked to see if the receiving user is on the AML blacklist.

A gathering list inquiry submodule: for querying the payee list from the payment subsystem for feedback to the terminal.

And the limit inquiry and check submodule: for inquiring the transfer amount of the transfer user from the payment subsystem and checking whether the transfer initiated by the transfer user exceeds the amount.

Balance inquiry checking submodule: the payment subsystem queries the balance of the transfer user and checks whether the balance is sufficient to pay for the transfer initiated by the transfer user.

And (3) handling fee management: for managing the commission required for the transfer initiated by the transfer user.

-a business process module

The order placing submodule of the transfer business order comprises: the method and the device are used for generating the transfer business sheet when transfer business exists, namely when a transfer user initiates transfer.

A bill transfer list query submodule: when the user wants to inquire the historical bill transfer list of the user, the transfer service subsystem can inquire the historical bill transfer list of the user through the sub-module.

A transfer bill detail query submodule: after the user selects a specific transfer form in the historical transfer form list, the account service subsystem can inquire the detail information of the selected transfer form through the sub-module.

A bill transfer state query submodule: when the user wants to inquire the current state of a certain transfer bill, the account business subsystem can inquire the state information of the transfer bill from the payment subsystem through the sub-module. The status is, for example, an unpaid status, a paid status, a status in transfer, and the like.

Transfer list state change submodule: when the state of a certain transfer bill changes, the state of the transfer bill is changed.

Payment order callback submodule: the payment subsystem may invoke this sub-module to notify the transfer service subsystem of the payment result of the transfer user.

The new sub-module of payee information: when the user wants to add new payee information to the payee list, the transfer service subsystem may add new payee information via the sub-module.

Payee list query submodule: when the user transfers money, one payee can be selected from the payee list as a payee, the user can request to display the payee list, and the transfer service subsystem can inquire the payee list of the user through the sub-module and feed back the payee list to the user.

Payee details query submodule: the payee list generally only displays the summary information of the payee, when a user wants to check the detailed information of a certain payee, the payee can be selected, and the transfer service subsystem can inquire the detailed information of the selected payee through the sub-module and feed back the detailed information to the user.

-order processing module

The transfer payment order placing sub-module comprises: and the payment subsystem is used for placing a payment order after the user confirms the transfer so as to initiate the payment of the amount involved in the transfer by the user.

The sub-module for sending the converted bill, the withdrawal order and the cash order: and the system is used for generating the cash-out bill after the user finishes payment. The cashing refers to a process of transferring the amount of money related to the user transfer from the account of the transfer platform to the account of the collection institution.

A payment order refund order generation submodule: and the refund list is generated when the user transfer fails so as to return the amount of money involved in the user transfer to the user.

-an account handling module

When the transfer types are different, different transfer sub-modules can be called to realize transfer logic.

The merchant transfers the sub-module to the user (Business-to-Customer, B2C): for enabling the merchant to transfer funds to the user.

And a quick transfer submodule: the method is used for realizing the function of quick transfer.

The user transfers sub-module to the merchant (Customer-to-Business, C2B): for enabling the transfer of the user to the merchant.

Payment refund submodule: the method is used for refunding to the user or the merchant when the transfer fails.

- -batch processing Module

For processing batches of tasks in a system.

Quick transfer status inquiry retry submodule: after the user initiates the transfer, the user may not correctly receive the feedback of the transfer state, and then the sub-module can inquire the transfer list in the non-feedback state in batch.

The order form inquiry reconciliation submodule of returning tickets: the order of the returned ticket is an order generated when the cash receiving mechanism successfully enters the account, but the account of the actual cash receiving user cannot successfully enter the account, when the order of the returned ticket exists, the transferring mechanism and the cash receiving mechanism need to check the fund flow direction, so that a problem is determined in which link, and therefore batch reconciliation can be carried out through the sub-module and the cash receiving mechanism.

The refund order processing refund submodule: when a refund order appears, the fund needs to be returned to the transfer user in the original way, so that batch refund processing of the refund order can be realized through the submodule.

2. Payment subsystem

KYC information management module: for managing KYC information of each user.

Quota management module: for managing transfer limits for each user.

A balance management module: for managing the account balance of each user.

Payment order placing module: upon receiving a payment order request from the transfer service subsystem, a payment order is generated.

A cashier mechanism list management module: and the collection interface is used for regularly detecting each collection mechanism so as to confirm whether the collection mechanism can accept the transfer or not, and storing the collection mechanism capable of accepting the transfer in the collection mechanism list based on the detection result.

The quick transfer service module comprises: the transfer service subsystem can call the quick transfer service module to initiate quick transfer to the credible transfer mechanism system.

Quick transfer status query module: the transfer service subsystem can call a quick transfer state query module to query the state of quick transfer bills.

A recharge order placing module: when transferring money, the fund of the transfer user is transferred to the account of the transfer platform, and a recharge order can be generated by a recharge order placing module to be used as a fund transfer voucher in the transfer process.

An account balance recharging module: for charging the account registered by the user in the transfer platform.

An account registration module: for registering a new account for the user at the transfer platform.

3. Credible transfer agency system

A collection information registration module: the collection information is the incidence relation between the collection identification of the collection user and the account information, and the user can register the collection information through the collection information registration module.

A collection information modification module: when the payment information sending time of the user can be changed, the user can modify the payment information by using the payment information modifying module.

A collection information inquiry module: when a user initiates transfer, the collection information query module can be used for querying collection information of the collection user, so that the collection identification of the collection user is verified.

A collection information logout module: for logging out the registered receipt information.

A quick transfer interface: after the user confirms the transfer, the transfer service subsystem can call a quick transfer interface of the credible transfer mechanism system through the payment subsystem, and sends a quick transfer request to the credible transfer mechanism system.

Quick transfer inquiry interface: when the initiated quick transfer order needs to be inquired, a quick transfer inquiry interface can be called for inquiry.

Swift account transfer reconciliation interface: when the order of returning tickets needs to be checked, the quick transfer account checking interface can be called to check the account.

To further illustrate the technical solutions provided by the embodiments of the present application, the following detailed description is made with reference to the accompanying drawings and the detailed description. Although the embodiments of the present application provide the method operation steps as shown in the following embodiments or figures, more or less operation steps may be included in the method based on the conventional or non-inventive labor. In steps where no necessary causal relationship exists logically, the order of execution of the steps is not limited to that provided by the embodiments of the present application. The method can be executed in sequence or in parallel according to the method shown in the embodiment or the figure when the method is executed in an actual processing procedure or a device.

In the embodiment of the application, if the money is transferred to the receiving user through the receiving identification, the receiving user needs to associate the receiving identification with the account information which is owned by the receiving user and can accept the transfer in advance, so that the subsequent transfer can be successfully carried out. Therefore, before describing the data transfer method of the embodiment of the present application, a process of registering transfer-related information will be described first. As shown in fig. 4, a flow diagram for registering transfer related information for a receiving user is shown.

Step 401: the terminal sends a first registration request to the background server, and the background server receives the first registration request.

In this embodiment, the payee may register in an application provided by a bank, a financial institution, a payment platform, or the like installed in the terminal, or register in a website provided by the bank, the financial institution, the payment platform, or the like, to send a first registration request to the backend server.

Fig. 5 is a schematic diagram of an interface for registering a payee, taking an application of the payment platform as an example. After entering the application of the payment platform, the payee may enter the home page of the payment platform, which may display the payment-related function options as shown in the top left diagram of fig. 5. Of course, the payment platform home page may be a home page of an application of the payment platform, may not be a home page of an application of the payment platform, and may also be a page that enters the payment platform home page through a certain function option after entering the application of the payment platform.

In the paymate homepage, some functions or services that the paymate can provide, such as the services of "pay" and "jump remittance" shown in fig. 5, may be exhibited. The fast transfer function may be a function of fast transferring money by using a money receiving identifier, and certainly, a name of the function may be set according to an actual situation, which is not limited in the embodiment of the present application, for example, to adapt to a Fast Pay System (FPS) released by a financial administration, and then the name of the function may also be a fast transfer. After the user operates the quick transfer function option, the user can enter a quick transfer function page, and on the page, the user can not only initiate quick transfer, but also receive quick payment. For a user who is a collection user, before the user is required to register information required by fast transfer, the user cannot perform the fast transfer, so that the collection user needs to operate the function option of 'register the fast transfer' in the fast transfer page to enter the fast transfer registration page and fill corresponding information in the page, such as selecting a collection mode and filling a collection identifier, wherein different collection modes can correspond to different types of collection identifiers, for example, the collection mode is that the collection identifier collects money by using a mobile phone number, the collection identifier can be a mobile phone number, or the collection mode is that a collection mailbox address is used for collecting money.

After the user fills necessary information, such as an institution where the account to be associated is located, an account name, account related information and the like, in the quick transfer registration page, and selects to submit, the payment platform application may generate a first registration request based on the user filled information, and send the first registration request to the background server through a communication interface of the terminal.

Step 402: and the background server sends a second registration request to the credible transfer agency, and the credible transfer agency receives the second registration request.

In the embodiment of the application, after the background server receives the first registration request, the validity of the account information background server of the payment platform can be verified, and account information background servers of other institutions cannot verify the validity, so that the background server can generate a second registration request according to the first registration request and send the second registration request to the trusted account transfer institution, the trusted account transfer institution serves as the trusted institution and can be accessed to or store account information of each large bank, financial institution or payment platform, and the like, and the trusted account transfer institution can verify the validity of the account information.

Specifically, the transfer service subsystem may send the first registration request to a collection information registration module of the trusted account transfer institution system through the payment subsystem, so that collection information is registered using the collection information registration module.

Step 403: the trusted transfer authority determines whether the recipient identification can be associated with account information.

In the embodiment of the application, the purpose of the receiving user is to associate the receiving identifier provided by the receiving user with the account information of the receiving user, so that during subsequent transfer, only the receiving identifier of the receiving user needs to be provided without providing detailed account information, but in order to guarantee the security and the legal rights of each user information, obviously, the receiving identifiers corresponding to different identities cannot be associated with the account information, for example, the mobile phone number of the user a cannot be associated with the account information of the user B, so that the trusted account transfer agency needs to verify the authenticity of the receiving identifier and the account information and also needs to verify whether the receiving identifier and the account information belong to the same user.

Specifically, when the collection identifier and the account information both exist really and belong to the same user, the collection identifier and the account information may be associated, otherwise, if the collection identifier and the account information do not exist really or do not belong to the same user, it is determined that the collection identifier and the account information cannot be associated.

Step 404: and the trusted transfer agency sends the first registration response message to the background server, and the background server receives the first registration response message.

In the embodiment of the application, if the trusted transfer agency determines that the collection identification can be associated with the account information, the collection identification is associated with the account information, namely the quick transfer function information is successfully registered; or if the trusted transfer agency determines that the receiving identification cannot be associated with the account information, determining that the registration of the quick transfer function information fails. The trusted transfer agency can carry the registration result in a first registration response message and send the first registration response message to the background server so as to inform the user.

Step 405: and the background server sends the second registration response message to the terminal, and the terminal receives the second registration response message.

After receiving the first registration response message, the background server may feed back the registration result to the payee. Specifically, the background server may generate a second registration response message based on the registration result carried in the first registration response message, and send the second registration response message to the terminal. After the terminal receives the second registration response message and acquires the registration result, the corresponding registration result may be displayed in the short-cut transfer registration result display page, and as shown in fig. 5, when the registration result is a successful registration, information indicating that the registration is successful may be displayed in the short-cut transfer registration result display page.

After the receiving user is successfully registered, the receiving user can be transferred by using the receiving identification of the receiving user. Please refer to fig. 6, which is a schematic flow chart of a data transfer method provided in an embodiment of the present application, and the method may be applied to the scenario shown in fig. 2, for example, and the flow of the method is described as follows.

Step 601: the terminal sends a KYC information verification request to the background server, and the background server receives the KYC information verification request.

In the embodiment of the application, based on the supervision requirements of related financial departments, identity authentication is generally required for users who transfer accounts online, therefore, when the users enter a quick transfer function page through a transfer platform homepage, a KYC information verification request is sent to a background server, the background server is requested to verify whether the transfer users pass the identity authentication, and whether the transfer users have corresponding KYC information is checked.

Step 602: the background server sends a KYC information verification response message to the terminal, and the terminal receives the KYC information verification response message.

After the background server finishes the check, a KYC information verification response message is sent to the terminal. If KYC information exists, namely the user passes identity authentication, the user can be allowed to transfer accounts, and then KYC information verification response information carries indication information indicating that the identity authentication passes, so that the terminal can directly enter a quick transfer function page from a transfer platform homepage; otherwise, if the identity authentication is not passed by the user, the identity authentication is required to be performed by the user firstly if the identity authentication is not passed by the user, and the KYC information verification response message carries indication information indicating that the identity authentication is not passed, the terminal can jump to an identity authentication page to guide the user to perform the identity authentication, and after the identity authentication is completed, the terminal can jump to a quick transfer function page. The inspection of the KYC information can be completed by combining a KYC information inspection submodule in the transfer service subsystem and a KYC information management module in the payment subsystem, which are shown in fig. 3.

Step 603: and initiating a first transfer request to a background server, and receiving the first transfer request by the background server.

In the embodiment of the application, when a transfer user needs to initiate transfer to a receiving user, the transfer user can perform transfer operation in an application provided by a bank, a financial institution, a payment platform and the like installed in a terminal, or perform transfer operation in a website provided by the bank, the financial institution, the payment platform and the like, so as to send a transfer request to a background server. Subsequently, for convenience of description, institutions such as banks, financial institutions or payment platforms which can initiate account transfer are collectively called as account transfer platforms.

As shown in fig. 7, an interface diagram of the transfer user initiating the transfer is taken as an example when the transfer user has completed the identity authentication. And after the transfer user enters a transfer platform homepage and enters a quick transfer function page, the transfer user selects a transfer function option and can jump to a transfer mode selection page. In the transfer mode selection page, the transfer user can select a corresponding transfer mode, wherein, in order to enable the receiving user to initiate transfer when the quick transfer function is not registered by the receiving user, the transfer user can also initiate transfer, a common transfer mode can be added in the transfer mode selection page, namely, a transfer mode needing to provide detailed account information is required, for example, the transfer mode of 'bank account' shown in fig. 7, the transfer can be carried out by utilizing the bank account information of the receiving user, of course, besides the common transfer mode, the transfer mode can also comprise a plurality of quick transfer modes, for example, the transfer mode of 'mobile phone number' shown in fig. 7, namely, the transfer mode is carried out by utilizing the number, and the transfer mode of 'e-mail address', namely, the transfer mode is carried out by utilizing the e-mail address, and certainly, the transfer can. The user may select a transfer method that the receiving user can receive in the transfer method selection page.

For example, when the user selects to transfer money using a mobile phone number as a collection identifier, the user may enter a transfer information filling page as shown in the lower right diagram of fig. 7. When the mobile phone number is used as the collection identifier, the user usually needs to fill in the mobile phone number of the collection user and the transfer amount, and the user can initiate the transfer. Some items which can be selected to be filled in can be filled in, for example, "collection account" shown in fig. 7, a collection account and an account opened by a collection user at a collection institution, and when the user does not select, the collection account can be a default collection account set by the collection user; or, if the receiving user wants the transferring user to transfer to a specific non-default receiving mechanism, the receiving user can inform the transferring user of the desired receiving account in advance, and the transferring user can select the corresponding receiving account when initiating the transferring. Of course, besides the filling information shown in fig. 7, other information to be filled may also be included, which is not limited in this embodiment of the application.

For another example, when the user selects to transfer money using an email address as a collection identifier, the user may enter a transfer information filling page as shown in the lower left of fig. 7. When the e-mail address is used as the collection identification, the user usually needs to fill in the e-mail address of the collection user and the transfer amount, and the transfer can be initiated. Of course, some selectable fill items may be filled, such as "money receiving account" shown in FIG. 7.

In practical application, the transfer user can add the mobile phone number or the email address of the payee to the payee list in advance, so that the user does not need to manually input the mobile phone number or the email address and can select from the payee list.

Specifically, as shown in fig. 8, an interface schematic diagram of a non-default collection mechanism is selected for a user, when the transfer user needs to select the non-default collection mechanism, the collection account option area in the transfer information filling page may be operated to display a corresponding selectable collection mechanism list, and correspondingly, the terminal device may receive a list display operation instruction of the transfer user, respond to the list display operation instruction, and send a list acquisition request to the background server to acquire the collection mechanism list to be displayed from the background server. When the background server returns the list acquisition response message, as shown in fig. 8, the corresponding collection mechanism list is displayed on the display page based on the collection mechanism list carried by the list acquisition response message, the user can select a collection mechanism from the collection mechanism list, which the collection user can collect, and perform selection operation on the collection mechanism, and correspondingly, the terminal can receive and respond to the selection operation instruction input by the transfer user on the collection mechanism list display page to select the collection mechanism selected by the selection operation instruction.

The collection institutions in the collection institution list carried in the list acquisition response message are all institutions which can transfer accounts and are confirmed by the background server, namely, the transfer accounts can be initiated to the collection institutions at present, and for some collection institutions which cannot initiate the transfer accounts, such as the collection institutions which are being maintained, the collection institutions cannot be included in the collection institution list, so that the transfer success rate of the user is reduced.

Specifically, the collection mechanism list management module in the payment subsystem may detect the transfer function of each collection mechanism, for example, may attempt to initiate transfer to a collection mechanism to detect whether the collection mechanism can receive transfer, and store the collection mechanism capable of transferring money in the collection mechanism list according to the detection result, and when a user requests to obtain the collection mechanism list, the collection list query sub-module of the transfer service subsystem may obtain the collection mechanism list from the payment subsystem and feed back the collection mechanism list to the terminal, so that the collection mechanism list can be displayed in an application page in the terminal.

Certainly, when the user wants to initiate a transfer, the user may enter the quick transfer function page through another entry, for example, a public link entry or an applet entry in an instant messaging application, which is not limited in the embodiment of the present application.

In the embodiment of the application, after the user fills necessary transfer information in the transfer information filling page, the 'submit' button can be operated to initiate transfer, the application of the transfer platform can respond to a transfer operation instruction input by the transfer user in the transfer page of the transfer platform to generate a first transfer request, and the first transfer request is sent to the background server through the communication interface of the terminal. For example, when the transfer user only provides the collection identifier and the transfer amount, the generated first transfer request may carry the collection identifier and the transfer amount; or when the transfer user provides the collection identifier, the transfer amount and the collection mechanism identifier, the first transfer request can be generated according to the collection identifier, the transfer amount and the collection mechanism identifier, that is, the first transfer request can be generated to carry the collection identifier, the transfer amount and the collection mechanism identifier. The cashier identification can be the name or number of the cashier.

Step 604: and the background server sends a verification request to the credible transfer mechanism, and the credible transfer mechanism receives the verification request.

In the embodiment of the application, after receiving the first transfer request, the background server may perform a certain check on the information of the receiving user carried in the first transfer request, for example, it may check whether the receiving user is located in an AML blacklist, if the receiving user is located in the AML blacklist, transfer to the receiving user is prohibited, and if the receiving user is not located in the AML blacklist, transfer to the receiving user may be permitted. The AML blacklist check can be realized by an AML blacklist check submodule in the transfer service subsystem.

After confirming that the transfer to the receiving user is allowed, the background server also needs to verify the validity of the receiving identification of the receiving user, for example, if the transferring user provides an unregistered user identification or the user identification is not associated with the account of the receiving institution, the transfer cannot be completed, so the background server can generate a verification request based on the information of the receiving user and send the verification request to the trusted transfer institution to verify the validity of the user identification.

Specifically, after the transfer service subsystem receives the first transfer request, a verification request is sent to the trusted transfer mechanism system through the payment subsystem, so that a collection identifier of a collection user is inquired through a collection information inquiry module of the trusted transfer mechanism system, and the validity of the collection identifier is verified.

Step 605: the trusted account transfer mechanism sends a verification response message to the background server, and the background server receives the verification response message.

In the embodiment of the application, the trusted transfer agency can verify the collection identification so as to check the validity of the collection identification.

The verification of the collection identifier may include:

the method comprises the steps that associated information of a collection identifier and at least one collection mechanism is registered in a trusted transfer mechanism, namely when a transfer user only provides the collection identifier, the transfer is carried to a default account of the collection user associated with the collection identifier, whether the collection information associated with the collection identifier is registered in the trusted transfer mechanism or not is verified, and only the collection information associated with the collection identifier is registered in the trusted transfer mechanism, the collection is legal; alternatively, the first and second electrodes may be,

the method includes that relevant information of a collection mechanism corresponding to a collection identification and a collection mechanism identification is registered in a trusted transfer mechanism, namely when a transfer user only provides the collection identification and the collection mechanism identification, namely the transfer user transfers to an account of a specified collection mechanism, besides verifying whether the collection information relevant to the collection identification is registered in the trusted transfer mechanism or not, whether the relevant information between the collection identification and the account of the specified collection mechanism is included in account information relevant to the collection identification or not needs to be verified, and only when the collection information relevant to the collection identification is registered in the trusted transfer mechanism and the relevant information between the collection identification and the account of the specified collection mechanism exists, the user identification can be identified to be legal. For example, the receiving user a has an account in bank a, and the receiving account a associates its own mobile phone number with the account in bank a, but the transferring user B designates the receiving institution as bank B when transferring to the receiving user a, but the receiving user a has not associated the account in bank B with the mobile phone number, so that even if the transferring user B has established the receiving institution as bank B, the transferring user a cannot successfully transfer the funds to the account in bank B, that is, the transferring information provided by the transferring user B cannot pass the verification.

After the verification is completed, the trusted transfer agency can carry the verification result in a verification response message and send the verification result to the background server. When the verification result indicates that the collection identifier is verified, the verification response message can carry the verification result, and account information associated with the collection identifier can be carried in the verification response message and sent to the background server. For example, when the collection institution is the default collection institution, the account information associated with the collection identification at the default collection institution may be sent to the backend server, or when the collection institution is the designated non-default collection institution, the account information associated with the collection identification at the designated non-default collection institution may be sent to the backend server.

Step 606: and the background server determines whether the payment receiving identification passes the verification according to the verification response message.

In the embodiment of the application, the background server can determine whether the collection identification passes the verification according to the verification result carried in the verification response message.

Step 607: if the determination result in the step 606 is negative, the background server sends a verification failure prompt message to the terminal.

Step 608: and the terminal outputs prompt information according to the verification failure prompt message.

Specifically, when the background server determines that the payment receiving identifier fails to be verified, the background server may send a verification failure prompt message to the terminal, and correspondingly, the terminal may output a prompt message on the display interface according to the verification failure prompt message in response to the verification failure prompt message to prompt that the payment receiving identifier is illegal.

Fig. 9 is a schematic diagram of an interface for prompting collection of illegal identification. In fig. 9, for example, when the transfer user selects to transfer money by using a mobile phone number, when the payment identifier input by the transfer user has not yet registered the quick transfer money, the user may prompt that "the mobile phone number has not yet registered the quick transfer account", and certainly, the prompt content may be set according to a specific situation, which is not limited in the embodiment of the present application.

Step 609: and if the determination result in the step 606 is yes, the background server sends a transfer confirmation prompt message to the terminal.

Specifically, when the background server determines that the receiving identification passes the verification, the transfer to the receiving user is allowed, and then the background server may send a transfer confirmation prompt message to the terminal, where the transfer confirmation prompt message may carry transfer information input by the transfer user, such as the receiving identification and the receiving amount, and may also carry identity information of the receiving user, such as the name of the receiving user, to help the transfer user confirm whether the receiving user is a user who wants to transfer money.

The processes of steps 607 to 608 and the process of step 609 are not all executed, when the determination result of step 606 is yes, the process of step 609 and the subsequent processes are executed, and when the determination result of step 606 is yes, the processes of steps 607 to 608 are executed, so for distinction, the processes of steps 607 to 608 are shown by using dotted lines in fig. 6.

Step 610: and the terminal prompts the transfer user to confirm the transfer according to the transfer confirmation prompt message.

In the embodiment of the application, after the terminal receives the transfer confirmation prompt message, the receiving identification can be verified according to the transfer confirmation prompt message, when the receiving identification is verified to be passed, the transfer page is switched to the transfer confirmation page, and whether a transfer user inputs a transfer confirmation operation instruction through the transfer confirmation page or not is monitored. Wherein, necessary transfer information may be displayed in the transfer confirmation page to prompt the transfer user to confirm the transfer.

As shown in fig. 10, a diagram of a transfer confirmation page. In the transfer confirmation page, a receiving identification and a receiving amount can be displayed, and information of the identity of a receiving user, such as the name of the receiving user, can be identified, so that the transfer user can more clearly confirm whether the receiving user is a user who wants to transfer money, and the probability of transfer errors is reduced.

Step 611: the terminal sends a transfer confirmation request for transferring the account data to the background server, and the background server receives the transfer confirmation request.

When the user confirms that the transfer information, such as the transfer amount and the transfer user name, is correct, the confirmed transfer operation may be performed. As shown in fig. 10, the transfer user may operate a confirmation transfer button in the transfer confirmation page, and accordingly, the terminal may monitor a confirmation transfer operation input by the transfer user through the confirmation transfer page, and notify the transfer platform application of the corresponding confirmation transfer operation indication, and the transfer platform application may generate a confirmation transfer request according to the confirmation transfer operation indication, and send the confirmation transfer request to the background server through the terminal communication interface.

Step 612: the background server sends a payment request to the terminal, and the terminal receives the payment request.

In the embodiment of the application, when the transfer confirmation request of the terminal is received by the background server, the transfer user can know that the transfer user confirms that the transfer is required, and the background server can generate a corresponding payment request to request the transfer user to pay corresponding transfer amount.

Specifically, a transfer confirmation request sent by the terminal can be received by the transfer service subsystem, and a transfer service order placing submodule in the transfer service subsystem generates a transfer service order based on transfer related information of the transfer and stores the transfer service order as a certificate for the user to have the transfer. In addition, a transfer payment order placing sub-module in the transfer business subsystem sends a payment order request to the payment subsystem, the payment order request can carry the order number of the transfer business order, a payment order placing module of the payment subsystem is used for generating a payment order based on the order number of the transfer business order and sending payment order information to the transfer business subsystem, and the transfer business subsystem carries the obtained payment order information in the payment request and sends the payment order information to the terminal.

Step 613: and the terminal displays a payment page according to the payment request.

In the embodiment of the application, after the transfer platform application in the terminal obtains the payment request, the transfer platform application can jump to a payment page to prompt a user to input a payment password.

Specifically, the transfer platform application corresponding to the transfer service subsystem and the payment subsystem is used as a front-end application of the background server, and may substantially include two parts corresponding to the transfer service subsystem and the payment subsystem, respectively, a service front-end module corresponding to the transfer service subsystem, and a payment front-end module corresponding to the payment subsystem, or called a cashier desk. When the transfer platform application acquires the payment request, the service front-end module substantially acquires the payment request, and the service front-end module calls an interface of the payment front-end module based on the payment request to display a payment page in the application.

As shown in fig. 11, is a schematic view of an interface of a payment page. The account data amount to be paid and the password input box can be displayed in the payment interface, and the transfer user needs to input a payment password in the password input box.

Step 614: and the terminal sends a payment response message to the background server, and the background server receives the payment response message.

After the transfer user inputs the payment password, the background server needs to verify the correctness of the payment password, so that the terminal can carry the payment password input by the transfer user in the payment response message and send the payment response message to the background server.

Step 615: and the background server sends a second transfer request to the credible transfer mechanism, and the credible transfer mechanism receives the second transfer request.

In the embodiment of the application, the background server can verify the payment password input by the user and determine whether the account of the transfer user meets the transfer requirement, and when the payment password is correct and the account of the transfer user meets the transfer requirement, a second transfer request can be sent to the credible transfer mechanism. The second transfer request can carry transfer user information, collection user information and other necessary transfer related information, such as transfer amount, transfer order number and the like.

Specifically, after the transfer business subsystem receives the payment response message, the payment response message can be forwarded to the payment subsystem, the payment subsystem can verify whether the account of the transfer user meets the transfer requirement, for example, whether the transfer amount exceeds the transfer limit of the transfer user, whether the account balance of the transfer user is enough to pay the transfer amount, and verify the correctness of the payment password, if the payment password is correct, payment logic is carried out, payment success is fed back to the transfer business subsystem, the transfer business subsystem can generate a second transfer request, and the second transfer request is sent to the credible transfer agency system through the payment subsystem; if the payment password is wrong, the payment subsystem feeds back the password error to the transfer service subsystem, the transfer service subsystem sends indication information indicating the password error to the terminal, and the terminal prompts the user that the password is wrong and guides the user to input the payment password again.

Step 616: the trusted transfer authority sends a third transfer request to the collection authority, and the collection authority receives the third transfer request.

In the embodiment of the application, when the trusted account transfer mechanism receives the second account transfer request, a third account transfer request can be sent to the collection mechanism according to the collection mechanism corresponding to the collection user, so that account data transfer is initiated to the collection mechanism.

Step 617: and the receiving institution feeds back the transfer result to the credible transfer institution.

And after executing the posting logic according to the transfer information carried in the third transfer request, the collection mechanism feeds back the transfer result to the credible transfer mechanism so as to feed back the transfer result to the transfer platform where the transfer user is located through the credible transfer mechanism.

Step 618: and the trusted account transfer mechanism feeds back the account transfer result to the background server.

Step 619: and the background server feeds back the transfer result to the terminal.

In the embodiment of the application, when the terminal acquires the transfer result, the transfer result can be displayed in the transfer result display page. In specific application, the terminal can also prompt the transfer result to the transfer user in other modes, for example, the transfer result can be prompted to the transfer user in public number message or push message and other modes.

As shown in fig. 12, a schematic view of a page is displayed for the transfer result. Fig. 12 is a transfer result display page illustrating transfer success, and in the transfer result display page, the transfer result and the transfer related information, such as the name of the receiving user, the receiving identifier, the number of the transfer order, and the like, may be displayed, and the number of the transfer order may be, for example, a number of a transfer service order or a number of a payment order.

In addition, in order to facilitate the user to store own account transfer records, a function button for making electronic bills can be added in the account transfer result display page, and the account transfer user can make the electronic bills and store the electronic bills locally through the function of making the electronic bills. As shown in fig. 12, after the transfer user operates the "make electronic bill" function button, the transfer platform application responds to the user's operation, and may generate a picture as shown in fig. 12, and the user may save the picture to the local by pressing a long button or other button operations. Of course, the electronic bill is shown in the form of a picture in fig. 12, but in practical applications, the electronic bill may also be stored in other forms, such as a text form, and the like, which is not limited in this application.

In the embodiment of the application, after the transfer is successful, the user may store the collection information of the receiving user who successfully transfers the money to the historical transfer list, as shown in fig. 13, the historical transfer list is displayed in the quick transfer function page, where the transfer record of the latest 6 months is shown in fig. 13 as an example, and of course, in actual application, all the transfer records may be shown or the transfer records in one year and the like may be shown, which is not limited in the embodiment of the application. When the transfer user needs to transfer money to the collection user existing in the transfer record list, the collection user can be directly selected from the historical transfer list, the transfer user does not need to input collection information of the collection user by himself, for example, the transfer user wants to transfer money to lie IV, the transfer user can directly select an option corresponding to the lie IV to initiate the transfer, and the method is more convenient and faster.

Please refer to fig. 14, which is a schematic flow diagram of an actual physical fund flow according to an embodiment of the present application.

Transfer user account: the account is an actual physical fund account used for paying the transfer amount for the transfer user, and the account can be an account opened in the transfer platform by the transfer user or an account of other mechanisms bound in the transfer platform, such as bank cards of all big banks.

Account transfer platform account: and the actual physical fund account is used for the transfer platform to quickly transfer and settle the fund.

The account of the collection institution: the collection institution is used to deposit the actual physical funds account that receives the instant transfer liquidated funds.

The account of the collection user: an actual physical funds account is opened for the recipient user at the receiving institution to receive the instant transfer of funds.

As shown in fig. 14, after the user pays the amount of money related to the transfer, the transfer user account pays the funds required for the transfer to the transfer platform, that is, the funds required for the transfer are transferred from the transfer user account to the transfer platform account first, when the transfer platform initiates a quick transfer to a trusted transfer organ, the transfer funds are transferred to a gathering organ account, and when the gathering organ account executes an account entry logic, the transfer funds are transferred to the gathering user account, so that the transfer is completed.

Please refer to fig. 15, which is a schematic flow diagram of a virtual fund flow in a transfer platform in the embodiment of the present application.

Account transfer user C: and a virtual fund account used for paying change and transferring bill in the transfer platform.

Fast transfer merchant B account: and the transfer platform is used for storing a virtual fund account for the user to pay the amount of the transferred bill.

Fast transfer merchant account C: and the transfer platform is used for storing a virtual fund account of the amount to be presented during transfer settlement.

As shown in fig. 15, after the transfer user pays the amount of money involved in the transfer, the transfer funds are transferred from the account of the transfer user C to the account of the fast transfer merchant B, and when the payment subsystem notifies the transfer service subsystem that the payment is completed, the transfer funds are transferred from the account of the fast transfer merchant B to the account of the fast transfer merchant C. The virtual fund flow is used for helping the transfer platform to manage the flow direction of funds among the modules, but the process only relates to the flow direction of the virtual funds and does not relate to the transfer of actual physical funds.

In summary, when the receiving user registers the quick transfer function, the transfer user can only input the receiving identification such as the mobile phone number or the email address of the receiving user, the background server inquires the name of the receiver and the information such as the receiving organization in the credible transfer organization according to the receiving identification input by the user, the user is helped to directly initiate transfer, and funds are transferred to the account associated with the receiving identification in real time, so that the transfer is easier and more convenient, new opportunities are brought to the retail payment industry, and financial technological innovation is promoted.

Referring to fig. 16, based on the same inventive concept, an embodiment of the present application further provides a data transfer device 160, which may be, for example, a terminal, and the device includes:

the first sending unit 1601 is used for responding to a transfer operation instruction for transferring account data input by a transfer user, and sending a first transfer request to a background server of the transfer platform, wherein the first transfer request carries a collection identifier of a collection user;

a transfer prompting unit 1602, configured to respond to a transfer confirmation prompting message returned by the backend server, and prompt the transfer user to perform transfer confirmation according to the transfer confirmation prompting message, where the transfer confirmation prompting message is generated when the backend server sends a verification request to the trusted transfer authority based on the receiving identifier, and determines that the receiving identifier passes verification based on a verification response message returned by the trusted transfer authority, and the verification request is used to request verification of validity of the receiving identifier;

the first sending unit 1601 is further configured to send, in response to the transfer confirmation operation instruction of the transfer user, a transfer confirmation request for transferring the account data to the backend server, so that after the backend server receives the transfer confirmation request, the trusted transfer authority is requested to initiate transfer of the account data to the collection authority where the collection user is located.

Optionally, the first sending unit 1601 is configured to:

and responding to a transfer operation instruction input by a transfer user in a transfer page of the transfer platform, and sending a first transfer request to a background server of the transfer platform, wherein the first transfer request carries a collection identifier of a collection user input by the transfer user on the transfer page.

Optionally, the transfer prompting unit 1602 is configured to:

verifying a collection identifier according to the transfer confirmation prompt message;

and monitoring whether the transfer user inputs a transfer confirmation operation instruction through a transfer confirmation page.

Optionally, the apparatus further comprises a first output unit 1603 for:

responding to a verification failure prompt message returned by the background server, and outputting prompt information according to the verification failure prompt message to prompt that the payment receiving identification fails to be verified; the verification failure prompt message is generated when the background server determines that the payment receiving identification fails to be verified based on the verification response message returned by the trusted transfer agency.

Optionally, the apparatus further comprises a page presentation unit 1604 and a cash register selection unit 1605;

the first sending unit 1601 is further configured to send a list acquisition request to a background server in response to a list display operation instruction input by a transfer user on a transfer page; the list display operation instruction is used for displaying a selectable cashier mechanism list;

the page display unit 1604 is configured to display a gathering mechanism list display page according to a list acquisition response message returned by the background server, where the gathering mechanisms in the gathering mechanism list carried in the list acquisition response message are all mechanisms that can perform account transfer after being confirmed by the background server;

a collection mechanism selecting unit 1605 for responding to a selection operation instruction input by the transfer user on the collection mechanism list display page, and selecting the collection mechanism selected by the selection operation instruction;

the first sending unit 1601 is configured to generate a first transfer request according to the collection identifier and the collection mechanism identifier in response to the transfer operation instruction, and send the first transfer request to the background server.

Optionally, the verification of the payment receiving identifier includes:

the method comprises the steps that the information related to a collection identification and at least one collection mechanism is registered in the trusted transfer mechanism; alternatively, the first and second electrodes may be,

the trusted transfer agency registers the related information of the collection agency corresponding to the collection agency identification and the collection agency identification.

Optionally, the apparatus further comprises a second output unit 1606;

the first sending unit 1601 is further configured to send a first registration request to the background server in response to a registration operation instruction for registering the receipt information input by the user, where the first registration request carries the receipt information to be registered, and the receipt information includes a receipt identifier and account information associated with the receipt identifier;

a second output unit 1606, configured to output a registration result according to a second registration response message returned by the backend server; the first registration response message is returned to the background server by the credible transfer mechanism after the background server sends a second registration request to the credible transfer mechanism based on the collection information; the registration result is used to indicate whether the registration was successful.

The apparatus may be configured to execute the methods in the embodiments shown in fig. 4 to fig. 15, and therefore, for functions and the like that can be realized by each functional module of the apparatus, reference may be made to the description of the embodiments shown in fig. 4 to fig. 15, which is not described in detail. Note that the first output unit 1603 to the second output unit 1606 are not necessarily functional units, and are therefore shown by broken lines in fig. 16.

Referring to fig. 17, based on the same inventive concept, an embodiment of the present application further provides a data transfer apparatus 170, which may be, for example, a backend server, and the apparatus includes:

a second sending unit 1701, configured to send, in response to the first transfer request sent by the terminal, a verification request to the trusted account transfer authority based on the collection identifier carried in the first transfer request;

a second sending unit 1701, configured to send a transfer confirmation prompt message to the terminal when it is determined that the payment receiving identifier is verified according to the verification response message returned by the trusted account transfer authority;

the transfer initiating unit 1702 is configured to initiate a second transfer request to the trusted account transfer mechanism in response to a transfer confirmation request sent by the terminal to transfer the account data, where the second transfer request carries a collection identifier, so that the trusted account transfer mechanism initiates transfer of the account data to a collection mechanism where a collection user is located according to the collection identifier.

Optionally, the transfer initiating unit 1702 is specifically configured to:

generating a payment request according to the confirmed account transfer request, and sending the payment request to a terminal, wherein the payment request is used for requesting the account transfer user to pay the amount of money corresponding to the account data to be transferred;

and when the payment is determined to be successful according to the payment response message returned by the terminal, generating a second transfer request, and sending the second transfer request to the trusted transfer agency.

Optionally, the second sending unit 1701 is further configured to:

responding to a first registration request sent by a terminal, and sending a second registration request to a trusted transfer agency based on collection information carried by the first registration request; the collection information comprises a collection identifier and account information related to the collection identifier;

The apparatus may be configured to execute the methods in the embodiments shown in fig. 4 to fig. 15, and therefore, for functions and the like that can be realized by each functional module of the apparatus, reference may be made to the description of the embodiments shown in fig. 4 to fig. 15, which is not described in detail.

Referring to fig. 18, based on the same technical concept, an embodiment of the present application further provides a computer device 180, which may include a memory 1801 and a processor 1802.

The memory 1801 is used for storing computer programs executed by the processor 1802. The memory 1801 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to use of the computer device, and the like. The processor 1802 may be a Central Processing Unit (CPU), a digital processing unit, or the like. The embodiment of the present application does not limit the specific connection medium between the memory 1801 and the processor 1802. In fig. 18, the memory 1801 and the processor 1802 of the embodiment of the present application are connected by a bus 1803, the bus 1803 is represented by a thick line in fig. 18, and the connection manner between other components is merely illustrative and not limited. The bus 1803 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 18, but this does not mean only one bus or one type of bus.

The memory 1801 may be a volatile memory (volatile memory), such as a random-access memory (RAM); the memory 1801 may also be a non-volatile memory (non-volatile memory) such as, but not limited to, a read-only memory (rom), a flash memory (flash memory), a Hard Disk Drive (HDD) or a solid-state drive (SSD), or the memory 1801 may be any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 1801 may be a combination of the above memories.

A processor 1802, configured to execute the method according to the embodiment shown in fig. 4 to fig. 15 when calling the computer program stored in the memory 1801.

In some possible embodiments, various aspects of the methods provided herein may also be implemented in the form of a program product including program code for causing a computer device to perform the steps of the methods according to various exemplary embodiments of the present application described above in this specification when the program product is run on the computer device, for example, the computer device may perform the methods according to the embodiments shown in fig. 4-15.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method of data transfer, the method comprising:

2. The method of claim 1, wherein sending a first transfer request to a back-end server of the transfer platform in response to an indication of a transfer operation to transfer the ledger data input by a transfer user comprises:

3. The method as claimed in claim 2, wherein said prompting a transfer user for transfer confirmation based on said confirmation transfer prompting message comprises:

4. The method of claim 1, wherein after the sending the first transfer request to the back-end server of the transfer platform, the method further comprises:

5. The method of any of claims 1-4, wherein the method further comprises:

responding to a list display operation instruction input by a transfer user on the transfer page, and sending a list acquisition request to the background server; the list display operation instruction is used for displaying a selectable cashier mechanism list;

acquiring a response message according to the list returned by the background server, and displaying a collection mechanism list display page, wherein collection mechanisms in the collection mechanism list carried in the list acquisition response message are all mechanisms which can transfer money and are confirmed by the background server;

responding to a selection operation instruction input by a transfer user on the cash register list display page, and selecting the cash register selected by the selection operation instruction;

sending a first transfer request to a background server of the transfer platform in response to a transfer operation instruction for transferring the account data, which is input by a transfer user, wherein the first transfer request comprises the following steps:

and responding to the transfer operation instruction, generating the first transfer request according to the collection identification and the collection mechanism identification, and sending the first transfer request to the background server.

6. The method of claim 5, wherein the receiving identification is validated, comprising:

7. The method of any of claims 1-4, wherein the method further comprises:

responding to a registration operation instruction of registering collection information input by a user, and sending a first registration request to the background server, wherein the first registration request carries collection information to be registered, and the collection information comprises a collection identifier and account information related to the collection identifier;

outputting a registration result according to a second registration response message returned by the background server; the second registration response message carries a registration result carried in a first registration response message returned to the background server by the trusted account transfer mechanism, and the first registration response message is returned to the background server by the trusted account transfer mechanism after the background server sends a second registration request to the trusted account transfer mechanism based on the collection information; the registration result is used to indicate whether the registration was successful.

8. A method of data transfer, the method comprising:

when the verification of the collection identification is confirmed to pass according to the verification response message returned by the credible transfer mechanism, sending a transfer confirmation prompt message to the terminal;

9. The method of claim 8 wherein initiating a second transfer request to the trusted account transfer authority comprises:

10. The method of claim 8, wherein the method further comprises:

11. A data transfer apparatus, the apparatus comprising:

12. A data transfer apparatus, the apparatus comprising:

13. A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor,

the processor, when executing the program, implements the method of any of claims 1-7 or 8-10.

14. A computer-readable storage medium having stored thereon processor-executable instructions,

the processor-executable instructions, when executed by a processor, are for implementing a method as claimed in any of claims 1 to 7 or 8 to 10.