WO2020238231A1 - 一种转账请求的处理方法、装置及设备 - Google Patents

一种转账请求的处理方法、装置及设备 Download PDF

Info

Publication number
WO2020238231A1
WO2020238231A1 PCT/CN2020/070892 CN2020070892W WO2020238231A1 WO 2020238231 A1 WO2020238231 A1 WO 2020238231A1 CN 2020070892 W CN2020070892 W CN 2020070892W WO 2020238231 A1 WO2020238231 A1 WO 2020238231A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
payee
transfer
user
account
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2020/070892
Other languages
English (en)
French (fr)
Inventor
夏云
代尊富
杨凡
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Advanced New Technologies Co Ltd
Original Assignee
Advanced New Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Advanced New Technologies Co Ltd filed Critical Advanced New Technologies Co Ltd
Priority to US16/877,235 priority Critical patent/US20200410474A1/en
Publication of WO2020238231A1 publication Critical patent/WO2020238231A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/326—Payment applications installed on the mobile devices
    • G06Q20/3263—Payment applications installed on the mobile devices characterised by activation or deactivation of payment capabilities
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/108—Remote banking, e.g. home banking
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/325—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks
    • G06Q20/3255—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks using mobile network messaging services for payment, e.g. SMS
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4014—Identity check for transactions
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/12—Accounting
    • G06Q40/125—Finance or payroll

Definitions

  • This application relates to the field of computer technology, in particular to a method, device and equipment for processing transfer requests.
  • the embodiments of the present application provide a method, device, and equipment for processing transfer requests, which can complete the transfer operation of platform users to non-platform users without relying on a third-party platform, and improve user experience.
  • the payee information includes at least identification information indicating the contact information of the payee;
  • the transfer request obtaining module is configured to obtain the transfer request submitted by the first terminal; the account of the initiator of the transfer request is logged on the first terminal.
  • the payee information acquisition module is used to obtain the payee information corresponding to the transfer request; the payee information includes at least identification information indicating the contact information of the payee;
  • the first result judgment module is configured to judge whether the recipient is a registered user of the platform that initiated the transfer request according to the recipient information, and obtain the first judgment result;
  • Receiving reminder information sending module configured to send receipt reminding information based on the identification information when the first judgment result indicates that the payee is an unregistered user, so as to prompt the payee to collect the payment .
  • At least one processor and,
  • a memory communicatively connected with the at least one processor; wherein,
  • the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can:
  • the payee information includes at least identification information indicating the contact information of the payee;
  • the embodiment of this specification uses the contact information as the user's identification information.
  • a collection prompt message is sent to prompt the non-registered user to collect the payment.
  • the embodiments of this specification can complete the operation of transferring funds from platform users to non-platform users without relying on a third-party platform, thereby improving user experience.
  • FIG. 1 is a schematic flowchart of a method for processing a transfer request provided by an embodiment of this specification
  • Figure 2 is a schematic diagram of an interface for sending registration information including identification information to an initiator for determination;
  • FIG. 3 is a schematic flowchart of another method for processing a transfer request provided by an embodiment of this specification.
  • FIG. 4 is a schematic structural diagram of a device for processing a transfer request corresponding to FIG. 1 according to an embodiment of this specification;
  • Fig. 5 is a schematic structural diagram of a processing device corresponding to the transfer request of Fig. 1 provided by an embodiment of the specification.
  • Fig. 1 is a schematic flowchart of a method for processing a transfer request provided by an embodiment of this specification. From a program perspective, the execution body of the process can be a program or an application client loaded on an application server.
  • the process can include the following steps:
  • Step 101 Obtain a transfer request submitted by a first terminal; the account of the initiator of the transfer request is logged on the first terminal.
  • the first terminal logs into the account of the initiator of the transfer request, and the first terminal may be a mobile phone, a tablet computer, a smart watch, or the like.
  • the initiator is a platform user.
  • the initiator logs in to the platform account through the first terminal.
  • the recipient information and transfer amount can be included.
  • the payee information can be the account name of the platform, or identity information such as name and contact information.
  • Step 102 Obtain the payee information corresponding to the transfer request; the payee information includes at least identification information indicating the contact information of the payee.
  • the information of the payee used to indicate the identity information of the payer may be a contact method.
  • the contact method can be any method that can contact the payee, and can be a mobile phone number, an email address, or an account number of another instant messaging APP.
  • the identification information is used to refer to the contact information of the payee.
  • the identification information can be an abbreviation of contact information, or can directly refer to a mobile phone number or an e-mail address, and there is no specific limitation here.
  • the payee information may include other identity information in addition to contact information, such as name, ID card information, or passport information.
  • Step 103 Determine whether the payee is a registered user of the platform that initiated the transfer request according to the payee information, and obtain a first determination result.
  • judging whether the payee is a registered user of the platform based on the payee information can be directly determined by contact information, or combined with other information in the payee information to comprehensively determine whether the payee is registered user.
  • the platform server can store registered user information.
  • the payee is a registered user, it can be determined directly according to the contact information, or it can be determined according to the contact information and other identity information, such as name and contact information. As a whole, the registered users are judged together.
  • Step 104 When the first judgment result indicates that the payee is an unregistered user, send collection prompt information according to the identification information, so as to prompt the payee to collect the payment.
  • the transfer can be made directly. If the payee is a non-registered user of the platform, you can send the payee reminder message to remind the payee to collect the payment. Because the transfer request includes the contact information of the payee, such as a mobile phone number.
  • the server may send payment prompt information to the terminal where the mobile phone number is located.
  • the payment reminder information may include how to register a user on the platform. After the payee has successfully registered, the payee can be successfully collected.
  • the contact information is used as the user's identification information, such as a mobile phone number or an email address.
  • a mobile phone number or an email address is usually printed on a business card.
  • contact information can be obtained directly from the business card and transfer.
  • phone numbers or e-mail addresses are also common ways for people to communicate with each other. Therefore, using the contact information as the user's identification information is an effective method that conforms to the user's daily habits.
  • users can have multiple contact methods in the registration information of the platform, such as mobile phone number and e-mail address. That is, a user can bind both e-mail address and mobile phone number, and it is allowed to bind multiple mobile phone numbers or Multiple email addresses.
  • each contact method can only correspond to one user, that is, there is no situation where two users have the same contact method.
  • the platform server can query users according to the contact information.
  • the method in Figure 1 uses the contact information as the user's identification information, and when the payee is not a registered user of the platform, a collection prompt message is sent to prompt the non-registered user to collect the payment.
  • the embodiments of this specification can not only complete the operation of transferring funds from platform users to non-platform users without relying on third-party platforms.
  • the use of contact information as identification information is simple to operate, and is beneficial to protect user privacy and improve user experience.
  • the server may also identify and confirm the account of the initiator, and verify whether the account of the initiator is in a normal state. If the account of the initiator is frozen, the transfer request will not be executed.
  • the judging whether the payee is a registered user of the platform that initiated the transfer request according to the payee information may specifically include: querying whether the identification information exists in a registered user database.
  • the server can uniformly store the registration information in the registered user database.
  • the registered user database in addition to the registered user database, it can also be other databases, and there is no specific limitation here. Therefore, when determining whether the payee is a platform user, a query can be made in the registered user database, and whether there is identification information corresponding to the contact method, a one-to-one comparison can be used. If the registered user database includes the identification information, it means that the user of the contact method corresponding to the identification information is a registered user of the platform.
  • the contact method is: 2389xxx@xxx.com
  • the registered user database does not include "2389xxx@xxx.com”
  • the registered user database includes "2389xxx@xxx.com”
  • the user can have multiple contact methods in the registration information of the platform, such as mobile phone number and email address. That is, a user can bind both email address and mobile phone number, and binding is allowed Multiple mobile phone numbers or multiple email addresses.
  • each contact method can only correspond to one user, that is, there is no situation where two users have the same contact method.
  • the platform server can query users according to the contact information. For example, the contact information of Zhang San in the registration information on the platform can be: "123xxxx4567, 2389xxx@xxx.com".
  • the contact method Since the contact method is different from the ID number, the ID number of a person is fixed since birth, but the contact method will change over time. For example, the user of the mobile phone number "123xxxx4567" in 2000 was “Zhang San", and the user in 2018 might be "Li Si". Therefore, sometimes, just check whether the contact information in the payee information exists in the registered user database to determine whether the payee is a registered user of the platform, and errors may occur. Therefore, in some implementations of the embodiments of the present specification, in order to improve the accuracy of the judgment of the registered user, in addition to the identification information, other information of the payee, such as the name, may also be included in the query. The name and contact information can be integrated together for comparison.
  • the payee information in the transfer request includes: Zhang San, 130xxxx1234.
  • the name of the account name corresponding to "130xxxx1234" was Li Si.
  • the information of the recipient is inconsistent, so it is impossible to determine that the recipient in the transfer request is a registered user.
  • the sending of payment prompt information according to the identification information may specifically include:
  • the collection prompt information includes at least the identification information
  • the payment prompt information is sent to the terminal corresponding to the mobile phone number, and the payee is prompted to use the mobile phone number as the contact method for user registration.
  • the contact method is a mobile phone number
  • the receipt prompt information needs to be sent to the terminal corresponding to the mobile phone number.
  • the collection prompt information will be transmitted through the communication base station, and finally transmitted to the terminal corresponding to the mobile phone number.
  • the prompt message for prompting collection may be generated according to the transfer request, and may include information about the originator of the transfer and information about the transfer amount.
  • the prompt information for prompting collection may also include: how to register the platform, and the download address or web page registration address of the APP corresponding to the platform. For example, a user with "mobile phone number 130xxxx1234", hello, Zhang San transfers 500 yuan to your account, please log in to the following website to download the XX software, and use '130xxxx1234' as the contact method for user registration". In addition, proceed The way of downloading XX software is not limited to the website, and the QR code of the downloading software can be provided directly.
  • the payment prompt information may further include an authorization code.
  • the authorization code is used by the payee to fill in during registration.
  • the authorization code may be a character string composed of numbers and/or letters, and may also be a barcode or a two-dimensional code and other authorization forms.
  • the payment prompt information may further include a registration time limit.
  • the time limit can be used to limit the time for users to register. It can take the form of "please register users before 20 o'clock on March 15, 2019".
  • the time limit can also limit the effective time range of the authorization code, and it can adopt the form of expression of "the authorization code is valid before 20 o'clock on March 15, 2019". If you register at a time outside the valid time range, you cannot successfully complete the transfer. Failure to successfully complete the transfer can include many situations, one is that the registration cannot be successfully completed; the other is that the registration can be successfully completed, but the payment cannot be successfully collected. In the second case, the initiator needs to resubmit the transfer request.
  • the payee uses the mobile phone number as the contact method for user registration.
  • This limitation is to allow the server to determine whether the newly registered user is the payee corresponding to the contact method. Assuming that the contact method is a mobile phone number, and the contact method filled in by the payee when the user registers is an email address, then the server will not be able to detect the registered user who uses the mobile phone number as the contact method in the registered user database, and the server will recognize the receipt The payer has not registered, which will result in the failure to complete the transfer request.
  • the sending the payment prompt information to the terminal corresponding to the mobile phone number may specifically include:
  • the payment reminder information can be sent to the terminal corresponding to the mobile phone number in the form of SMS, and the user of the mobile phone number finds the SMS received by the terminal to perform the user registered.
  • the user can also be prompted to register by voice.
  • the voice can be sent to the terminal of the mobile phone number in text form, which prompts the user in time and facilitates the user to register.
  • the sending of payment prompt information according to the identification information may specifically include:
  • the collection prompt information includes at least the identification information
  • the payment prompt information is sent to the address corresponding to the e-mail address, prompting the payee to use the e-mail address as the contact method for user registration.
  • an embodiment of sending the collection reminder information using the email address as the contact method is also provided.
  • the difference from using the mobile phone number as the contact method is that the sending path of the collection reminder information is different.
  • the payment reminder information will first be sent to the server address of the xxx mailbox.
  • the account of 1234567@xxx.com has an operation to receive mail, the payment reminder information will be sent to In the email address with 1234567@xxx.com as the account.
  • the collection prompt information before sending the collection prompt information according to the identification information, it may further include:
  • the server in order to provide the initiator with an opportunity to improve the transfer request, the server also sets up a temporary account for storing the transfer amount.
  • the temporary account may be a temporary account created by the server in response to the current transfer request.
  • One transfer request corresponds to a temporary account.
  • the temporary account is cancelled.
  • the temporary account may also be an intermediate transition account, and all transfer requests correspond to the same intermediate transition account. The intermediate transition account always exists and will not be destroyed as the transfer request is completed or not.
  • the server will always check whether there is a new user registration after sending the payment reminder to the payee.
  • registration information is obtained.
  • the registration information can be compared with the payee information, and if they are consistent, it means that the newly created account is the payee. Then transfer the transfer amount in the temporary account to the account of the user corresponding to the payee. What is said here is consistent, as long as the content in the payee information exists in the registration information and is the same.
  • the registration information may include: name and contact information; or name, contact information, and certificate information.
  • the credential information can be an ID card, a passport, a driver’s license, an officer’s card, etc., which are not specifically limited here.
  • the payee information can also include other identity information of the user, such as name, hometown, and ID card information.
  • identity information such as name, hometown, and ID card information.
  • the registration information is compared with the payee information, the name and contact information can be compared at the same time. Only when the name and contact information are the same can it be determined as consistent.
  • the payment method information is: Zhang San, 130xxxx1234, and the registration information of User B is: Zhang San, male, ID number 2201561975xxxx1123, phone number 130xxxx1234. Since the registration information includes "Zhang San, 130xxxx1234", it can be determined that user B is the payee corresponding to the transfer request. At this time, the transfer amount in the temporary account can be transferred to user B's account.
  • the transfer amount transferred to the newly created account of the payee can be frozen for a period of time, which can be 5 hours or 24 hours, and the time can be based on actual needs. Make settings. The payee cannot perform any operations on the transfer amount during this period, and the initiator can choose whether to withdraw the transfer amount according to the request.
  • the transfer service is split into two-stage capital flow processing, and the user registration service is combined to complete the user transfer service.
  • the transfer amount in the temporary account is returned to the originator's account.
  • the server can automatically judge according to the set rules, or it can be judged according to the cooperation of the initiator of the transfer request.
  • the judging whether the registration information is consistent with the payee information may specifically include:
  • the present invention may send registration information to the initiator for determination.
  • the registration information sent to the initiator may include the name and contact information of the registered user, and may also include some credential information.
  • the opinion of the initiator can be solicited in the form of inquiry.
  • Figure 2 is a schematic diagram of an interface for sending registration information including identification information to an initiator for determination. As shown in Figure 2, there is an inquiry interface on the mobile phone.
  • the inquiry interface includes upper and lower parts, the upper part is the inquiry area, and the lower part is the user confirmation area.
  • the query area displays the text "Is the registered user the user you need to transfer?".
  • the confirmation area includes two options: "Yes" and "No".
  • the initiator clicks the confirmation button "Yes”; if the registered user is not the user who needs the transfer, the initiator clicks the deny button "No".
  • the server receives the feedback from the initiator, it first determines whether the feedback from the initiator is confirmed or denied. If it is confirmed, the user corresponding to the registration information in the manual is the payee of the transfer request. If it is denied, then The user corresponding to the registration information in the manual is not the recipient of the transfer request.
  • the server can perform some screening first, filter out some obviously non-compliant registration information, and only transmit the information that meets the preset rules to the sender for confirmation, which can reduce some links and avoid wasting time .
  • the judging whether the registration information is consistent with the payee information may specifically include:
  • the first user identity information includes at least a name
  • the server will preset some matching rules to automatically identify whether the registered information is consistent with the payee information.
  • the contact information of the registration information is consistent with the payee information
  • other identity information of the user can be determined.
  • the payee information may also include name
  • the user's registration information may also include information such as name. Therefore, the name in the payee information can be compared with the name in the registration information. If the two names are the same, it means that the user corresponding to the registration information is the payee. In this way, the user does not need to consider whether the payee is a registered user of the platform.
  • the platform server automatically reminds the user to register, automatically determines the payee user, and automatically completes the transfer, so that the user can transfer money without perception and improve user experience .
  • first user identity information and the second user identity information may also include other information.
  • a name is used as an example to introduce, but it is not limited to this.
  • the collection prompt information after sending the collection prompt information according to the identification information, it may further include:
  • the transfer amount in the temporary account is returned to the originator's account.
  • the payee may not receive the above information, or the payee may not register the user in time for some reasons.
  • the server cannot always wait for the payee to register the user. Therefore, it is necessary to preset a time period during which if the payee successfully registers, the transfer request can be completed; if the payee does not register successfully, the transfer request will be cancelled. Then, the transfer amount in the temporary account is returned to the account of the initiator.
  • the preset time period can start timing when the initiator initiates the transfer request, or it can start timing when the receipt prompt message is sent, as long as the starting time point is uniform.
  • the duration of the preset time period can be set according to the actual situation, and can be set to 12 hours, 24 hours, or 48 hours. In addition, the duration of the preset time period can also be modified according to the time data registered by the user.
  • the preset time period is set too long: assuming that the initial value of the preset time period is 48 hours, if 5 registered users are monitored, the time for successful registration is 1 hour, 3 hours, 10 hours, and 18 hours. And 23 hours. It can be found that the registration time of 5 users is less than 24 hours, so it can be presumed that in most normal situations, the user can successfully complete the registration within 24 hours. Therefore, the preset time period can be changed from 48 hours to 24 hours.
  • the preset time period is set too short: assuming that the initial value of the preset time period is 12 hours, it turns out that 4 of the 5 transfer requests initiated are not completed, and the user registration of the payee in the other transfer request The time is 11 hours, so it can be inferred that this may be related to the preset time period is too short, then the preset period can be delayed from 12 hours to 24 hours, observe the user registration effect, and then perform real-time according to the feedback information obtained Adjustment.
  • the method may further include:
  • the transfer amount is returned to the account of the initiating party.
  • the initiator after initiating the transfer request, the initiator found out that his transfer request was filled in incorrectly. It may be that the transfer amount was filled in incorrectly, or the recipient's information may be filled in incorrectly. In short, in order to ensure that the transfer can follow There can be a remedial measure for the true intention of the initiator. That is, the initiator can make a cancellation request after submitting the transfer request. The ultimate purpose of this cancellation request is to prevent the transfer amount from entering the payee's account.
  • returning the transfer amount to the account of the initiating party may specifically include:
  • the transfer amount is returned to the account of the initiator.
  • the premise of initiating a refund request is that the transfer amount is not in the account of the initiating party. Therefore, there are two situations for the refund request. One situation is that the transfer amount is in the temporary account, and the second situation is that the transfer amount is in the payee's account.
  • the fourth judgment result indicates that the transfer amount is stored in the temporary account, and the initiator can request the transfer amount to be returned to its own account at any time.
  • the time that the transfer amount exists in the temporary account is also subject to certain restrictions.
  • “Within a preset time period, when the payee corresponding to the identification information has not successfully registered, Return the transfer amount in the temporary account to the originator’s account” assuming that this preset time period is 24 hours, that is to say, the transfer amount will exist in the temporary account for a maximum of 24 hours Hours. After 24 hours, the transfer amount will be automatically refunded to the originator's account. Therefore, the "time limit" in this embodiment can be set to 24 hours, and the initiator can cancel the transfer request at any time within 24 hours.
  • the fourth judgment result indicates that the transfer amount is not stored in the temporary account, that is, the transfer amount is stored in an account other than the temporary account, that is, in the payee’s account, for this
  • the initiator can initiate a refund request as long as it is within a preset time period. Assuming that the preset time is 24 hours, no matter what account the transfer amount is in, you can request a refund within 24 hours.
  • the difference from the above method is that in this case, it is necessary to determine the time when the transfer is completed, that is, how long it takes for the transfer amount to be transferred to the recipient's account. Because, within a period of time when the transfer amount is transferred to the recipient's account, the transfer amount is frozen. In other words, although the transfer amount is in the payee's account, the transfer amount is not at the control of the payee. During this time, if a refund request is initiated, the transfer amount can be directly refunded to the account of the initiator. However, after this period of time, the transfer amount will not be refunded to the originator's account.
  • the sum of the first preset time and the transfer completion time may be greater than the "preset time period" in the first case, which is more conducive to the originator to maintain its own rights and interests.
  • the transfer completion time as the time from the initiation of the transfer request to the receiver receiving the transfer amount, which is 5 hours, the first preset time is set to 20 hours, and the total length is 25 hours, which will be higher than the first 24 hours of the "preset time period" for this situation.
  • the sum of the first preset time and the transfer completion time may also be less than or equal to the "preset time period" in the first case, which is more conducive to completing the transfer request as soon as possible. For example, if the transfer completion time is 5 hours, and the first preset time is set to 10 hours, then the total length is 15 hours, which will be less than 24 hours of the "preset time period" in the first case.
  • Fig. 3 is a schematic flowchart of another method for processing a transfer request provided by an embodiment of the specification.
  • the embodiment of this specification includes three sets of devices: 1. User A terminal (or equipment); 2. User B terminal (or equipment); 3. Internet financial service provider C (server).
  • user A is already a registered user of an Internet financial service provider
  • user B is not a registered user of an Internet financial service provider.
  • Step 1 User A opens the user terminal device, selects the transfer service, fills in the amount, and user B's identity identification.
  • the identity is a contact method, and the contact method may include a mobile phone number, an email address, and the like. User A submits a transfer request on his terminal.
  • Step 2 User A's terminal device sends the transfer request to Internet financial service provider C.
  • Step 3 Internet financial service provider C verifies the identity information of user A and user B, creates a transfer business receipt, completes user A's deduction processing, and transfers funds from user A's account to an intermediate transition account.
  • Step 4 Internet financial service provider C informs user B (phone call, text message, email) to receive payment through user B's identity identification.
  • Step 5 User B uses his device and the identification mark to register the user.
  • Step 6 User B terminal sends user registration information to Internet financial service provider C, and user B becomes a registered user of Internet financial service provider C.
  • Step 7 Internet financial service provider C monitors that user B completes user registration, automatically triggers payment processing, transfers funds from the intermediate transition account to user B's account, and completes the transfer business.
  • Step 8 The Internet financial service provider C sends the successful payment information to the terminal of user B.
  • Step 9 Internet financial service provider C sends the successful transfer information to user A's terminal.
  • Step 10 User B receives the transfer success message on his terminal.
  • Step 11 User A receives the transfer success message on his terminal.
  • the contact information is used as the identification information of user B.
  • a collection prompt message is sent to user B's contact information to prompt user B to collect payment.
  • User B performs user registration according to the payment prompt information.
  • the Internet financial service provider C detects that the user B has successfully registered, it transfers the funds from the intermediate transition account to the user B account to complete the transfer business.
  • the embodiments of this specification can not only complete the operation of platform users to transfer funds to non-platform users, but also use contact information as identification information. Compared with bank card transfers, the operation is simple and helps protect users’ Privacy, improve user experience.
  • Fig. 4 is a schematic structural diagram of a device for processing a transfer request corresponding to Fig. 1 provided in an embodiment of this specification. As shown in Figure 4, the device may include:
  • the transfer request obtaining module 401 is configured to obtain a transfer request submitted by a first terminal; the first terminal is logged in with the account of the initiator of the transfer request;
  • the payee information obtaining module 402 is configured to obtain payee information corresponding to the transfer request; the payee information includes at least identification information indicating the contact information of the payee;
  • the first result determination module 403 is configured to determine whether the payee is a registered user of the platform that initiated the transfer request according to the payee information, and obtain the first determination result;
  • the collection prompt information sending module 404 is configured to send collection prompt information according to the identification information when the first judgment result indicates that the payee is an unregistered user, so as to prompt the payee to collect paragraph.
  • the device in FIG. 4 determines the payee information through the transfer request obtaining module 401 and the payee information obtaining module 402, and the first result judgment module 403 determines whether the payee is a registered user according to the payee information; When the first result judgment module 403 judges that the payee is not a registered user of the platform, the collection reminder information sending module 404 sends collection reminder information to prompt the non-registered user to collect money.
  • the embodiments of this specification can complete the operation of transferring funds from platform users to non-platform users without relying on third-party platforms. Moreover, the use of contact information as identification information is simpler than bank card transfer, and is beneficial to protect user privacy and improve user experience.
  • the first result judgment module 403 may be specifically used to query whether the identification information exists in the registered user database.
  • the collection reminder information sending module 404 may specifically include:
  • the first collection prompt information generating unit is configured to generate collection prompt information according to the transfer request; the collection prompt information includes at least the identification information;
  • the first collection prompt information sending unit is configured to send the collection prompt information to the terminal corresponding to the mobile phone number when the contact method is a mobile phone number, and prompt the payee to use the mobile phone number as Contact information for user registration.
  • the collection reminder information sending module 404 may specifically include:
  • the second collection prompt information generating unit is configured to generate collection prompt information according to the transfer request; the collection prompt information includes at least the identification information;
  • the second collection reminder information sending unit is configured to send the collection reminder information to the address corresponding to the email when the contact method is an email address, and prompt the payee to use the email address as Contact information for user registration.
  • the device may further include:
  • a transfer amount determination module configured to determine the transfer amount in the transfer request before sending the collection prompt information according to the identification information
  • the transfer amount deduction module is used to deduct the transfer amount from the account of the initiator
  • the transfer amount storage module is used to store the transfer amount in a temporary account
  • the registration information obtaining module is configured to obtain the registration information including the identification information after the receipt prompt information is sent according to the identification information;
  • the second result judgment module is used to judge whether the registration information is consistent with the payee information, and obtain a second judgment result
  • the transfer amount transfer module is configured to transfer the transfer amount in the temporary account to the payee when the second judgment result indicates that the registration information is consistent with the payee information.
  • the contact information in the registration information of the newly created account of the payee is the same as the contact information corresponding to the identification information.
  • the second result judgment module may specifically include:
  • the first registration information sending unit is configured to send the registration information to the first terminal and prompt the initiator to confirm the registration information
  • a confirmation information acquiring unit configured to acquire confirmation information of the initiator on the registration information sent by the first terminal
  • the first determining unit is configured to determine whether the registration information is consistent with the payee information according to the confirmation information.
  • the second result judgment module may specifically include:
  • the first user identity information obtaining unit obtains the first user identity information included in the payee information; the first user identity information includes at least a name;
  • the second user identity information obtaining unit is configured to obtain the second user identity information contained in the registration information
  • the second judgment unit is configured to judge whether the first user identity information is consistent with the second user identity information.
  • the device may further include:
  • the first transfer amount return module is configured to return the transfer amount in the temporary account to the originator's account when the second judgment result indicates that the registration information is inconsistent with the payee information in.
  • the registration information may include: name and contact information;
  • name Or, name, contact information, and credential information.
  • the device may further include:
  • the third result judgment module is used for judging whether the payee corresponding to the identification information is successfully registered within a preset time period after sending the collection prompt information according to the identification information, and obtain the third judgment result ;
  • the second transfer amount return module is configured to return the transfer amount in the temporary account when the third judgment result indicates that the payee corresponding to the identification information has not successfully registered within the preset time period To the originator’s account.
  • the device may further include:
  • a refund request obtaining module configured to obtain a refund request initiated by the initiator in response to the transfer request after the transfer amount is stored in a temporary account
  • the transfer amount return module is configured to return the transfer amount to the account of the initiator when it is determined that the time limit for initiating the refund request does not exceed the time limit.
  • the first collection reminder information sending unit may specifically include:
  • the first collection prompt information sending subunit sends the collection prompt information to the terminal corresponding to the mobile phone number in the form of a short message
  • the second collection prompt information sending sub-unit sends the collection prompt information to the terminal corresponding to the mobile phone number in the form of voice.
  • the embodiment of this specification also provides a device corresponding to the above method.
  • Fig. 5 is a schematic structural diagram of a processing device corresponding to the transfer request of Fig. 1 provided by an embodiment of the specification. As shown in FIG. 5, the device 500 may include:
  • At least one processor 510 and,
  • a memory 530 communicatively connected with the at least one processor; wherein,
  • the memory 530 stores instructions 520 that can be executed by the at least one processor 510, and the instructions are executed by the at least one processor 510, so that the at least one processor 510 can:
  • the payee information includes at least identification information indicating the contact information of the payee;
  • the device in Figure 5 uses the contact information as the user's identification information.
  • the payee When the payee is not a registered user of the platform, it sends a collection prompt message to prompt the non-registered user to collect the payment.
  • the embodiments of this specification can complete the operation of transferring funds from platform users to non-platform users without relying on third-party platforms.
  • the contact information is used as the identification information, which is simple to operate, which is beneficial to protect the privacy of the user and improve the user experience.
  • a programmable logic device Programmable Logic Device, PLD
  • FPGA Field Programmable Gate Array
  • HDL Hardware Description Language
  • ABEL Advanced Boolean Expression Language
  • AHDL Altera Hardware Description Language
  • HDCal JHDL
  • Lava Lava
  • Lola MyHDL
  • PALASM RHDL
  • VHDL Very-High-Speed Integrated Circuit Hardware Description Language
  • Verilog Verilog
  • the controller can be implemented in any suitable manner.
  • the controller can take the form of, for example, a microprocessor or a processor and a computer-readable medium storing computer-readable program codes (such as software or firmware) executable by the (micro)processor. , Logic gates, switches, application specific integrated circuits (ASICs), programmable logic controllers and embedded microcontrollers.
  • controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicon Labs C8051F320, the memory controller can also be implemented as a part of the memory control logic.
  • controller in addition to implementing the controller in a purely computer-readable program code manner, it is entirely possible to program the method steps to make the controller use logic gates, switches, application specific integrated circuits, programmable logic controllers and embedded The same function can be realized in the form of a microcontroller, etc. Therefore, such a controller can be regarded as a hardware component, and the devices included in it for implementing various functions can also be regarded as a structure within the hardware component. Or even, the device for realizing various functions can be regarded as both a software module for realizing the method and a structure within a hardware component.
  • a typical implementation device is a computer.
  • the computer may be, for example, a personal computer, a laptop computer, a cell phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or Any combination of these devices.
  • the embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.
  • a computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.
  • the computing device includes one or more processors (CPU), input/output interfaces, network interfaces, and memory.
  • processors CPU
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-permanent memory in computer readable media, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer readable media.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash memory
  • Computer-readable media include permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology.
  • the information can be computer-readable instructions, data structures, program modules, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical storage, Magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.
  • program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types.
  • This application can also be practiced in distributed computing environments. In these distributed computing environments, remote processing devices connected through a communication network perform tasks.
  • program modules can be located in local and remote computer storage media including storage devices.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computational Linguistics (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Marketing (AREA)
  • Technology Law (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

一种转账请求的处理方法、装置及设备。方法包括：获取第一终端提交的转账请求；所述第一终端上登录有所述转账请求的发起方的账户（S101）；获取所述转账请求对应的收款方信息；所述收款方信息至少包括表示收款方联系方式的标识信息（S102）；根据所述收款方信息判断所述收款方是否为发起所述转账请求的平台的注册用户，得到第一判断结果（S103）；当所述第一判断结果表示所述收款方为非注册用户时，根据所述标识信息，发送收款提示信息，以便提示所述收款方进行收款（S104）。

Description

一种转账请求的处理方法、装置及设备 技术领域
本申请涉及计算机技术领域，尤其涉及一种转账请求的处理方法、装置及设备。
背景技术
现有技术中，在一些互联网金融平台上，由于受平台的限制，用户在进行转账的时候，如果收款方不是平台的注册用户，那么用户将无法完成平台用户向非平台用户转账的操作，甚至无法通知收款方有一笔转账金额待收取。
发明内容
有鉴于此，本申请实施例提供了一种转账请求的处理方法、装置及设备，能够在不依赖第三方平台的情况下，完成平台用户向非平台用户转账的操作，提高用户体验。
为解决上述技术问题，本说明书实施例是这样实现的：
本说明书实施例提供的一种转账请求的处理方法，包括：
获取第一终端提交的转账请求；所述第一终端上登录有所述转账请求的发起方的账户；
获取所述转账请求对应的收款方信息；所述收款方信息至少包括表示收款方联系方式的标识信息；
根据所述收款方信息判断所述收款方是否为发起所述转账请求的平台的注册用户，得到第一判断结果；
当所述第一判断结果表示所述收款方为非注册用户时，根据所述标识信息，发送收款提示信息，以便提示所述收款方进行收款。
本说明书实施例提供的一种转账请求的处理装置，包括：
转账请求获取模块，用于获取第一终端提交的转账请求；所述第一终端上登录有所述转账请求的发起方的账户。
收款方信息获取模块，用于获取所述转账请求对应的收款方信息；所述收款方信息至少包括表示收款方联系方式的标识信息；
第一结果判断模块，用于根据所述收款方信息判断所述收款方是否为发起所述转账请求的平台的注册用户，得到第一判断结果；
收款提示信息发送模块，用于当所述第一判断结果表示所述收款方为非注册用户时，根据所述标识信息，发送收款提示信息，以便提示所述收款方进行收款。
本说明书实施例提供的一种转账请求的处理设备，包括：
至少一个处理器；以及，
与所述至少一个处理器通信连接的存储器；其中，
所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够：
获取第一终端提交的转账请求；所述第一终端上登录有所述转账请求的发起方的账户；
获取所述转账请求对应的收款方信息；所述收款方信息至少包括表示收款方联系方式的标识信息；
根据所述收款方信息判断所述收款方是否为发起所述转账请求的平台的注册用户，得到第一判断结果；
当所述第一判断结果表示所述收款方为非注册用户时，根据所述标识信息，发送收款提示信息，以便提示所述收款方进行收款。
本说明书实施例采用的上述至少一个技术方案能够达到以下有益效果：
本说明书实施例以联系方式作为用户的标识信息，当收款方不是平台的注册用户时，发送收款提示信息，提示非注册用户进行收款。本说明书实施例能够在不依赖第三方平台的情况下，完成平台用户向非平台用户转账的操作，提高用户体验。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1为本说明书实施例提供的一种转账请求的处理方法的流程示意图；
图2为将包含有标识信息的注册信息发送至发起方进行确定的界面示意图；
图3为本说明书实施例提供的另一种转账请求的处理方法的流程示意图；
图4为本说明书实施例提供的对应于图1的一种转账请求的处理装置的结构示意图；
图5为本说明书实施例提供的对应于图1的一种转账请求的处理设备的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合本申请具体实施例及相应的附图对本申请技术方案进行清楚、完整地描述。显然，所描述的实施例仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
以下结合附图，详细说明本申请各实施例提供的技术方案。
图1为本说明书实施例提供的一种转账请求的处理方法的流程示意图。从程序角度而言，流程的执行主体可以为搭载于应用服务器的程序或应用客户端。
如图1所示，该流程可以包括以下步骤：
步骤101：获取第一终端提交的转账请求；所述第一终端上登录有所述转账请求的发起方的账户。
在本说明书实施例中，第一终端登录有转账请求的发起方的账户，第一终端可以是手机、平板电脑、智能手表等。
在本说明书实施例中，发起方是平台用户，当发起方需要进行转账操作时，通过第一终端登录平台账号。在转账请求中，可以包括收款方信息和转账金额等。收款方信息，可以是平台的账户名，还可以是姓名、联系方式等身份标识信息。第一终端获取发起方的转账请求以后，会将转账请求发送给服务器。
在本说明书实施例中，所述的“第一”和“第二”只是为了区分用户和终端，防止概念混淆，并不具有实际意义。
步骤102：获取所述转账请求对应的收款方信息；所述收款方信息至少包括表示收款方联系方式的标识信息。
在本说明书实施例中，所述收款方信息中用于表征收款方身份信息的可以是联系方式。所述联系方式可以是任意能够联系到收款方的方式，可以是手机号码、电子邮箱或者其它即时通讯APP的账户号。所述标识信息用于指代收款方的联系方式。所述标识 信息，可以是联系方式的缩写，也可以直接指代手机号码或者电子邮箱，这里不做具体的限定。
在本说明书实施例中，所述收款方信息除了联系方式之外，还可以包括其它的身份信息，可以为姓名、身份证信息或者护照信息等。
步骤103：根据所述收款方信息判断所述收款方是否为发起所述转账请求的平台的注册用户，得到第一判断结果。
在本说明书实施例中，根据所述收款方信息判断收款方是否为平台注册用户，可以直接通过联系方式进行判断，也可以结合收款方信息中的其它信息综合判断收款方是否为注册用户。
在本说明书实施例中，平台服务器可以存储注册用户信息，在判断收款方是否为注册用户时，可以根据联系方式直接确定，也可以根据联系方式和其他身份信息一起确定，如姓名和联系方式作为一个整体，一起进行注册用户判定。
步骤104：当所述第一判断结果表示所述收款方为非注册用户时，根据所述标识信息，发送收款提示信息，以便提示所述收款方进行收款。
在本说明书实施例中，如果收款方为平台的注册用户时，则可以直接进行转账。如果收款方为平台的非注册用户时，则可以向收款方发送收款提示信息来提示收款方进行收款。因为，转账请求中包括收款方的联系方式，如手机号码。服务器可以向所述手机号码所在终端发送收款提示信息。所述收款提示信息，可以包括如何在该平台上进行用户注册。收款方注册成功后，就可以成功收款。
在一些金融平台转账方式中，平台用户向非平台用户进行转账时，为了转账成功，往往会借助一些第三方平台协助转账。比较常见的是银行系统，发起方只需要填写收款方的银行账户就可以完成转账。但是，由于银行账户并不是用户间通常来进行沟通的交互信息，而且银行卡号是个人隐私，因此，在一些通讯软件中，在输入银行卡号时，经常被会认为是诈骗信息。所以，在互联网金融服务商平台中，考虑到安全性的问题，不宜采用银行账户作为转账方式。另外，银行卡号由十九位数字组成，不方便记忆，给转账也带来了很大的不便。
在本说明书实施例中，采用联系方式作为用户的标识信息，例如手机号码或者电子邮箱。因为，手机号码和电子邮箱是人与人在进行正常交流时，通常会进行交换的信息。例如，名片上通常都会印有电话号码或电子邮箱等联系方式，在进行转账时，可以直接 从名片上获取上述联系方式，进行转账。而且，电话号码或电子邮箱也是人在相处之间用来进行沟通的常用方式。因此，将联系方式作为用户的标识信息是一个符合用户日常习惯的有效的方法。
另外，用户在平台的注册信息中的联系方式可以有多种，如手机号和电子邮箱，即一个用户既可以绑定电子邮箱，又可以绑定手机号，且允许绑定多个手机号或者多个电子邮箱。但是每个联系方式只能对应一个用户，即不存在两个用户拥有同一个联系方式的情况。基于用户与联系方式一一对应，平台服务器可以实现根据联系方式查询用户。
图1中的方法，通过以联系方式作为用户的标识信息，当收款方不是平台的注册用户时，发送收款提示信息，提示非注册用户进行收款。本说明书实施例在不依赖第三方平台的情况下，不仅能够完成平台用户向非平台用户转账的操作。另外，采用联系方式作为标识信息，操作简单，并且有利于保护用户的隐私，提高用户体验。
基于图1的方法，本说明书实施例还提供了该方法的一些具体实施方式，下面进行说明。
可选的，在获取第一终端提交的转账请求之后，服务器还可以会对发起方的账户进行识别确认，校验发起方的账户是否处于正常状态。如果处于发起方的账户处于冻结状态，则不会执行此转账请求。
可选的，所述根据所述收款方信息判断所述收款方是否为发起所述转账请求的平台的注册用户，具体可以包括：查询注册用户数据库是否存在所述标识信息。
在本说明书实施例中，用户在进行平台注册时，除了需要填写姓名等一些常用信息时，一般都会包括联系方式(如手机号码或者电子邮箱)。服务器可以把这些注册信息统一存储于注册用户数据库中。当然，除了注册用户数据库，还可以是其他数据库，这里不做具体限定。因此，在判断收款方是否为平台用户时，可以在注册用户数据库中进行查询，是否存在联系方式对应的标识信息，可以采用一一对比的方式。如果注册用户数据库中包括所述标识信息，则表示所述标识信息对应的联系方式的用户为平台的注册用户。假设，联系方式为：2389xxx@xxx.com，当查询到注册用户数据库中不包括“2389xxx@xxx.com”，则说明2389xxx@xxx.com对应的收款方为非注册用户。当查询到注册用户数据库中包括“2389xxx@xxx.com”，则说明2389xxx@xxx.com对应的收款方为注册用户。
在本说明书实施例中，用户在平台的注册信息中的联系方式可以有多种，如手机号 和电子邮箱，即一个用户既可以绑定电子邮箱，又可以绑定手机号，且允许绑定多个手机号或者多个电子邮箱。但是每个联系方式只能对应一个用户，即不存在两个用户拥有同一个联系方式的情况。基于用户与联系方式一一对应，平台服务器可以实现根据联系方式查询用户。例如，张三在平台上的注册信息中的联系方式可以是：“123xxxx4567，2389xxx@xxx.com”。
由于联系方式与身份证号码不一样，人自出生以后，身份证号码就是一定的，而联系方式却会随着时间的推移而发生改变。比如，手机号码“123xxxx4567”在2000年的使用者为“张三”，而在2018年的使用者可能为“李四”。因此，有的时候，仅仅查询注册用户数据库是否存在收款方信息中联系方式就来判断收款方是否为平台的注册用户，可能会出现差错。因此，在本说明书实施例的部分实施方式中，为了提高注册用户判断的准确性，在进行查询的时候，除了查询标识信息之后，还可以包括收款方的其他信息，比如姓名。可以综合姓名和联系方式一起来进行比对，只有在姓名和联系方式对应的用户为同一个用户时，才能确定该用户为注册用户。如果姓名和联系方式对应的用户为不同的用户，则不能确定联系方式对应的用户为注册用户。例如，转账请求中的收款方信息包括：张三，130xxxx1234。在注册用户数据库查询过程中，查询到：“130xxxx1234”对应的账户名的姓名为李四，显然，这样收款方的信息不一致，因此不能确定转账请求中的收款方为注册用户。
可选的，所述根据所述标识信息，发送收款提示信息，具体可以包括：
根据所述转账请求生成收款提示信息；所述收款提示信息至少包括所述标识信息；
当所述联系方式为手机号码时，将所述收款提示信息发送至所述手机号码对应的终端，提示所述收款方采用所述手机号码作为联系方式进行用户注册。
在本说明书实施例中，提供了两种不同联系方式发送收款提示信息的方式。当联系方式为手机号码时，需要将收款提示信息发送至手机号码对应的终端。所述收款提示信息会经过通讯基站进行信息的传递，最终传输到所述手机号码对应的终端上。
具体的，所述提示收款提示信息可以根据所述转账请求生成，可以包括转账的发起方信息，转账金额信息。所述提示收款提示信息还可以包括：如何进行平台注册的步骤，以及该平台对应的APP的下载地址或者网页注册地址。例如，“手机号码为130xxxx1234”的用户，你好，张三向你的账号转账500元，请登录以下网址进行XX软件的下载，并以‘130xxxx1234’为联系方式进行用户注册”。另外，进行XX软件的下载的方式不 限定于网址，还可以直接提供下载软件的二维码。
在一些具体的实施方式中，为了提高安全性，所述收款提示信息还可以包括授权码。所述授权码用于收款方在进行注册时进行填写。所述授权码可以是由数字和/或字母组成字符串，还可以是条形码或者二维码等其他授权形式。
在一些具体的实施方式中，为了提高安全性，所述收款提示信息还可以包括注册时间限制。时间限制可以是用来限制用户进行注册的时间，可以采用“请在2019年03月15日20时之前进行用户注册”的表现形式。时间限制还可以是限制授权码的有效时间范围，则可以采用“所述授权码在2019年03月15日20时之前有效”的表现形式。在有效时间范围之外的时间注册则不能成功完成转账。不能成功完成转账可以包括多种情况，一种是不能成功完成注册；另一种是能够成功完成注册，但是不能成功进行收款。在第二种情况下，发起方需要重新提交转账请求。
在本说明书实施例中，限定了所述收款方采用所述手机号码作为联系方式进行用户注册，这样限定是为了能够让服务器确定新注册用户是否为联系方式对应的收款方。假设联系方式为手机号码，而收款方在用户注册的时候填写的联系方式为电子邮箱，那么服务器在注册用户数据库将无法检测到以手机号码为联系方式的注册用户，那么服务器将会认定收款方一直没有进行注册，这样将会导致无法完成该转账请求。
可选的，所述将所述收款提示信息发送至所述手机号码对应的终端，具体可以包括：
将所述收款提示信息以短信的形式发送至所述手机号码对应的终端；
和/或，将所述收款提示信息以语音的形式发送至所述手机号码对应的终端。
在一些具体的实施方式中，当以手机号码为联系方式时，可以以短信的方式将收款提示信息发送至手机号码对应的终端上，手机号码的使用者发现终端收到的短信来进行用户注册。但是，很多时候，用户由于忙碌，无法及时看到终端上的短信。此时，为了提高用户的体验，还可以以语音的方式提示用户进行注册。另一个更好的实施方式是，在语音通知用户进行注册之后，还可以将语音以文字形式再发送至所述手机号码的终端，这样即及时提示了用户，又方便用户进行注册。
可选的，所述根据所述标识信息，发送收款提示信息，具体可以包括：
根据所述转账请求生成收款提示信息；所述收款提示信息至少包括所述标识信息；
当所述联系方式为电子邮箱时，将所述收款提示信息发送至所述电子邮箱对应的地 址，提示所述收款方采用所述电子邮箱作为联系方式进行用户注册。
在本说明书实施例中，还提供了以电子邮箱为联系方式的发送收款提示信息的实施例。与以手机号码为联系方式所不同的是，收款提示信息的发送路径不同。以1234567@xxx.com为例，收款提示信息首先会被发送xxx邮箱的服务器地址中，当1234567@xxx.com的账户有收取邮件的操作时，则会将所述收款提示信息发送至以1234567@xxx.com为账户的电子邮箱中。
可选的，在所述根据所述标识信息，发送收款提示信息之前，还可以包括：
确定所述转账请求中的转账金额；
从所述发起方的账户中扣除所述转账金额；
将所述转账金额存储于临时账户中；
在所述根据所述标识信息，发送收款提示信息之后，还可以包括：
获取包含所述标识信息的注册信息；
判断所述注册信息与所述收款方信息是否一致，得到第二判断结果；
当所述第二判断结果表示所述注册信息与所述收款方信息一致时，将所述临时账户中的所述转账金额转入到所述收款方新建的账户中；所述收款方新建的账户的注册信息中的联系方式与所述标识信息对应的联系方式相同。
在本说明书实施例中，为了给发起方提供一个对转账请求进行改进的机会，服务器还设置了存储转账金额的临时账户。当服务器收到转账请求之后，首先会把转账请求发起方的账户中的金额扣除，然后转移到一个临时账户中。所述临时账户，可以是服务器针对当前的转账请求创建的一个临时账户，一个转账请求对应一个临时账户，转账请求完成，则临时账户注销。所述临时账户，也可以是一个中间过渡账户，所有的转账请求均对应同一个中间过渡账户。中间过渡账户一直存在，不会随着转账请求的完成与否而销毁。
在本说明书实施例中，服务器在向收款方发送了收款提示信息之后，会时刻检测是否有新用户注册。每当有一个新用户注册，就会获取注册信息。当获取到以转账请求中的收款方信息中包括的联系方式进行注册的注册信息时，需要进一步确定是否为所述转账请求对应的收款方。可以将注册信息与收款方信息进行对比，如果一致，则说明新建立的账户即为所述收款方。然后将临时账户中的转账金额转入至所述收款方对应的用户 的账户中。这里所说的一致，只要收款方信息中的内容在所述注册信息中全部存在，且相同即可。
可选的，所述注册信息可以包括：姓名和联系方式；或者，姓名、联系方式和证件信息。所述证件信息可以是身份证、护照、驾照、军官证等等，这里不做具体限定。
在本说明书实施例中，还存在一种场景，假设用户A向手机号码为“135xxxx1234”的用户发起转账。转账平台服务器查询注册用户数据库中不存在以该手机号码进行注册的用户，则向该手机号码“135xxxx1234”发送短信或者语音通知用户注册。用户B收到短信或者语音后，发现自己已经使用电子邮箱或其他联系方式在该转账平台注册，此时，用户B可以登录转账平台，在自己的联系方式中添加该手机号，添加完成后，转账平台根据第二判断结果，得知该手机号码对应的用户已存在(包括已注册)，也可以执行后续转账操作。
在一些具体的实施方式中，为了提高转账的安全性和准确性。在收款方信息中还可以包括用户的其他身份信息，如姓名、籍贯和身份证信息等。而涉及到金融转账的平台在进行用户注册时，往往需要用户进行实名认证或者一些其他的信息。那么，在将注册信息与收款方信息进行对比，可以同时比对姓名和联系方式，只有当姓名和联系方式均相同的时候，才可以认定为一致。例如，收款方式信息为：张三，130xxxx1234，用户B的注册信息为：张三，男，身份证号2201561975xxxx1123，电话号码130xxxx1234。由于注册信息中包括“张三，130xxxx1234”，则可以认定用户B为所述转账请求对应的收款方，此时，就可以将临时账户中的转账金额转入至用户B的账户中。
在一些具体的实施方式中，为了提高转账的安全性，转入至收款方新建的账户的转账金额可以被冻结一段时间，可以是5个小时，也可以是24小时，时间可以根据实际需要进行设置。收款方在这段时间内不能对这笔转账金额进行任何操作，而发起方可以根据请求选择是否撤回该笔转账金额。
本说明书实施例中，将转账服务拆分成两阶段资金流处理，结合用户注册服务，完成用户转账服务。
可选的，当所述第二判断结果表示所述注册信息与所述收款方信息不一致时，将所述临时账户中的所述转账金额退回至所述发起方的账户中。
在上面的实施例中，介绍了注册信息与所述收款方信息一致的情况下，会将转账金额转入至收款方的账户中。还有一种情况是，在注册信息与所述收款方信息不一致时， 则说明收款方没有注册成功，那么转账请求不能完成，因此，需要将临时账户中的转账金额退回到发起方的账户中。
在本说明书实施例中，判断注册信息与收款方信息是否一致，有多种方法，可以是服务器根据设定规则自动判断，也可以根据转账请求的发起方配合一同进行判断。
可选的，所述判断所述注册信息与所述收款方信息是否一致，具体可以包括：
将所述注册信息发送至所述第一终端，提示所述发起方对所述注册信息进行确认；
获取所述第一终端发送的所述发起方对所述注册信息的确认信息；
根据所述确认信息判断所述注册信息与所述收款方信息是否一致。
在一些具体实施方式中，为了提高安全性，本发明可以将注册信息发送至发起方进行确定。发送至发起方的注册信息可以包括注册用户的姓名、联系方式，还可以包括一些证件信息。可以以询问的形式征询发起方的意见。图2为将包含有标识信息的注册信息发送至发起方进行确定的界面示意图。如图2所示，手机上有个询问界面，询问界面包括上下两部分，上部分为询问区域，下部分为用户确认区域。询问区域显示文字“请问该注册用户是否是您需要转账的用户？”。确认区域包括两个选项：“是”和“否”。如果该注册用户是发起方需要转账的用户，则发起方点击确认键“是”；如果该注册用户不是发起方需要转账的用户，则发起方点击否认键“否”。当服务器接收到发起方的反馈后，首先判断发起方的反馈信息是确认还是否认，如果是确认的话，则说明书注册信息对应的用户，即为转账请求的收款方，如果是否认的话，则说明书注册信息对应的用户，不是转账请求的收款方。
在一些具体的实施方式中，服务器可以先进行一些筛选，把一些明显不符合规定的注册信息过滤掉，只把符合预设规则的信息传送给发送方进行确认，可以减少一些环节，避免浪费时间。
可选的，所述判断所述注册信息与所述收款方信息是否一致，具体可以包括：
获取所述收款方信息中包含的第一用户身份信息；所述第一用户身份信息至少包括姓名；
获取所述注册信息中包含的第二用户身份信息；
判断所述第一用户身份信息与所述第二用户身份信息是否一致。
在一些具体的实施方式中，服务器会预设一些匹配规则来自动识别注册信息是 否与收款方信息一致。在注册信息的联系方式与收款方信息一致的前提下，还可以对用户的其他身份信息进行确定。例如，收款方信息除了包括联系方式之外，还可以包括姓名，而用户的注册信息中也会包括姓名等信息。因此，可以将收款方信息中的姓名与注册信息中的姓名进行对比，如果两个姓名相同，则说明所述注册信息对应的用户即为收款方。这种方式，可以让用户不用考虑收款方是否为平台的注册用户，平台服务器自动提醒用户注册，自动进行收款方用户确定，自动完成转账，让用户能够无感知的进行转账，提高用户体验。
此外，第一用户身份信息和第二用户身份信息还可以包括其他信息，这里只是以姓名为例做了介绍，但是并不只限定于此。
在本说明书实施例中，所述的“第一”和“第二”只是为了区分不同的身份信息，防止概念混淆，并不具有实际意义。
可选的，在所述根据所述标识信息，发送收款提示信息之后，还可以包括：
判断在预设时间段内，所述标识信息对应的收款方是否注册成功，得到第三判断结果；
当所述第三判断结果表示在预设时间段内，所述标识信息对应的收款方没有注册成功时，将所述临时账户中的所述转账金额退回至所述发起方的账户中。
在本说明书实施例中，当发送收款提示信息以后，收款方可能没有接收到上述信息，也可能收款方因为某些原因，没有及时进行用户注册。在这种情况下，为了转账的安全性，服务器不可能一直等待收款方进行用户注册。因此，需要预设一个时间段，在此时间段内如果收款方成功注册，则可以完成转账请求；如果收款方没有注册成功，则将取消此转账请求。那么，则将临时账户中的转账金额退回至所述发起方的账户中。
预设时间段可以从发起方发起转账请求开始计时，也可以从收款提示信息发出开始计时，只要保证开始的时间点统一即可。
此外，预设时间段的时长可以根据实际情况进行设置，可以设置为12小时、24小时或者48小时。此外，预设时间段的时长也可以根据用户注册的时间数据进行修改。
一种情况是预设时间段设置的过长：假设预设时间段初始值为48小时，如果监测的5个注册用户，注册成功所用的时间分别为1小时、3小时、10小时、18小时和23小时。可以发现5个用户的注册时间均小于24小时，那么可以推定，在大多数正常情况下，24小时之内，用户就可以成功完成注册。因此，可以将预设时间段从48小时 修改为24小时。
另一种情况是预设时间段设置的过短：假设预设时间段初始值为12小时，结果发现发起的5个转账请求有4个没有完成，另一个转账请求中收款方的用户注册时间为11小时，那么可以推断这可能与预设时间段的太短有关系，那么可以将预设间段由12小时延迟至24小时，观察一下用户注册效果，再根据得到的反馈信息进行实时的调整。
可选的，在将所述转账金额存储于临时账户中之后，所述方法还可以包括：
获取所述发起方针对所述转账请求发起的退款请求；
当确定所述退款请求的发起时间未超过时间限制时，将所述转账金额退回至所述发起方的账户中。
在一些具体的实施方式中，发起方在发起转账请求之后，后发现自己的转账请求填错了，可能是转账金额填写错误，也可能是收款方信息填写错误，总之，为了保证转账能按照发起方的真实意愿进行，可以有一个补救措施。即，发起方在提交转账请求之后，可以进行撤销请求。这个撤销请求的最终目的就是防止转账金额进入到收款方的账户中。
可选的，所述当确定所述退款请求的发起时间未超过时间限制时，将所述转账金额退回到所述发起方的账户中，具体可以包括：
判断所述转账金额是否存储于所述临时账户中，得到第四判断结果；
若所述第四判断结果表示所述转账金额存储于所述临时账户中，将所述临时账户中的所述转账金额退回至所述发起方的账户中。
若所述第四判断结果表示所述转账金额未存储于所述临时账户中，获取所述转账请求的完成时间；
当确定所述完成时间未超过第一预设时间时，将所述转账金额退回到所述发起方的账户中。
在本说明书实施例中，发起退款请求的前提是，转账金额未处于发起方的账户中。因此，针对退款请求有两种情况，一种情况是转账金额在临时账户中，第二种情况是转账金额在收款方的账户中。
针对第一种情况，即所述第四判断结果表示所述转账金额存储于所述临时账户中，发起方可以随时请求将转账金额退回至自己账户中。另外，转账金额在临时账户中 存在的时间也是有一定的限制的，如上述实施例中提及到的，“在预设时间段内，所述标识信息对应的收款方没有注册成功时，将所述临时账户中的所述转账金额退回至所述发起方的账户中”，假设这个预设时间段为24个小时，那么也就是说，转账金额在临时账户中的存在时间最多为24个小时。超过24个小时，转账金额将自动退回至发起方的账户中。因此，本实施例中的“时间限制”可以设置为24小时，只要在24小时之内，发起方可以随时撤销转账请求。
针对第二种情况，即所述第四判断结果表示所述转账金额未存储于所述临时账户中，即转账金额存储于临时账户之外的账户，即在收款方的账户中，针对这种情况，又可以有两种处理办法：
一、和处理转账金额存储于临时账户的情况一样，只要在预设时间段内，发起方都可以发起退款请求。假设这个预设时间为24小时，不管转账金额处于什么账户中，只要在24小时之内都有可以请求退款。
二、与上述方法不同的是，这种情况需要判断转账完成的时间，也就是说，转账金额转入至收款方账户的时间有多久。因为，在转账金额转入至收款方账户的一段时间内，转账金额处于冻结状态。也就是说，虽然转账金额在收款方账户中，但是，这笔转账金额并不受收款方的支配。在这段时间内，发起退款请求，转账金额可以直接退回至发起方的账户的。但是，超过这段时间，转账金额将无法退回至发起方的账户。
第一预设时间与转账完成时间之和，可以大于第一种情况的“预设时间段”，这种情况更有利于发起方维护自己的权益。例如，定义转账完成时间为从发起转账请求至收款方收到转账金额的时间，为5个小时，第一预设时间设置为20个小时，总长则为25个小时，会高于第一种情况的“预设时间段”的24个小时。
第一预设时间与转账完成时间之和，也可以小于或者等于第一种情况的“预设时间段”，这种情况更有利于转账请求尽快的完成。例如，转账完成时间为5个小时，而将第一预设时间设置为10个小时，那么总长为15个小时，那么将小于第一种情况的“预设时间段”的24个小时。
图3为本说明书实施例提供的另一种转账请求的处理方法的流程示意图。如图3所示，本说明书实施例包含三套装置：1.用户A终端(或设备)；2.用户B终端(或设备)；3.互联网金融服务商C(服务器)。其中，用户A已经是互联网金融服务商注册用户，用户B不是互联网金融服务商注册用户。
说明书实施例提供的转账请求的处理方法包括以下步骤：
步骤1：用户A打开用户终端设备，选择转账服务，填写金额，以及用户B身份识别标识，所述身份识别标识为联系方式，所述联系方式可以包括手机号码、电子邮箱地址等。用户A在其终端上提交转账请求。
步骤2：用户A终端设备发送所述转账请求至互联网金融服务商C。
步骤3：互联网金融服务商C校验用户A以及用户B身份信息，创建转账业务单据，并完成用户A扣款处理，将资金从用户A账户转移到中间过渡账户。
步骤4：互联网金融服务商C通过用户B身份识别标识通知(电话、短信、电子邮件)用户B收款。
步骤5：用户B使用其设备和该身份识别标识进行用户注册。
步骤6：用户B终端将用户注册信息发送至互联网金融服务商C，用户B成为互联网金融服务商C注册用户。
步骤7：互联网金融服务商C监测到用户B完成用户注册，自动触发收款处理，将资金从中间过渡户转移到用户B账户，完成转账业务。
步骤8：互联网金融服务商C将收款成功信息发送至用户B的终端。
步骤9：互联网金融服务商C将转账成功信息发送至用户A的终端。
步骤10：用户B在其终端上收到转账成功信息。
步骤11：用户A在其终端上收到转账成功信息。
图3中的方法，采用联系方式作为用户B的标识信息，当用户B不是平台的注册用户时，向用户B的联系方式发送收款提示信息，提示用户B进行收款。用户B根据收款提示信息进行用户注册。互联网金融服务商C检测到用户B注册成功后，将资金从中间过渡户转移到用户B账户，完成转账业务。本说明书实施例在不依赖第三方平台的情况下，不仅能够完成平台用户向非平台用户转账的操作，而且采用联系方式作为标识信息，相对于银行卡转账，操作简单，并且有利于保护用户的隐私，提高用户体验。
基于同样的思路，本说明书实施例还提供了上述方法对应的装置。图4为本说明书实施例提供的对应于图1的一种转账请求的处理装置的结构示意图。如图4所示，该装置可以包括：
转账请求获取模块401，用于获取第一终端提交的转账请求；所述第一终端上登录有所述转账请求的发起方的账户；
收款方信息获取模块402，用于获取所述转账请求对应的收款方信息；所述收款方信息至少包括表示收款方联系方式的标识信息；
第一结果判断模块403，用于根据所述收款方信息判断所述收款方是否为发起所述转账请求的平台的注册用户，得到第一判断结果；
收款提示信息发送模块404，用于当所述第一判断结果表示所述收款方为非注册用户时，根据所述标识信息，发送收款提示信息，以便提示所述收款方进行收款。
图4中的装置，通过转账请求获取模块401和收款方信息获取模块402确定收款方信息，第一结果判断模块403根据所述收款方信息判断所述收款方是否为注册用户；当第一结果判断模块403判断收款方不是平台的注册用户时，收款提示信息发送模块404发送收款提示信息，提示非注册用户进行收款。本说明书实施例在不依赖第三方平台的情况下，能够完成平台用户向非平台用户转账的操作。而且采用联系方式作为标识信息，相对于银行卡转账，操作简单，并且有利于保护用户的隐私，提高用户体验。
可选的，所述第一结果判断模块403，具体可以用于查询注册用户数据库是否存在所述标识信息。
可选的，所述收款提示信息发送模块404，具体可以包括：
第一收款提示信息生成单元，用于根据所述转账请求生成收款提示信息；所述收款提示信息至少包括所述标识信息；
第一收款提示信息发送单元，用于当所述联系方式为手机号码时，将所述收款提示信息发送至所述手机号码对应的终端，提示所述收款方采用所述手机号码作为联系方式进行用户注册。
可选的，所述收款提示信息发送模块404，具体可以包括：
第二收款提示信息生成单元，用于根据所述转账请求生成收款提示信息；所述收款提示信息至少包括所述标识信息；
第二收款提示信息发送单元，用于当所述联系方式为电子邮箱时，将所述收款提示信息发送至所述电子邮箱对应的地址，提示所述收款方采用所述电子邮箱作为联系方式进行用户注册。
可选的，所述装置还可以包括：
转账金额确定模块，用于在所述根据所述标识信息，发送收款提示信息之前，确定所述转账请求中的转账金额；
转账金额扣除模块，用于从所述发起方的账户中扣除所述转账金额；
转账金额存储模块，用于将所述转账金额存储于临时账户中；
注册信息获取模块，用于在所述根据所述标识信息，发送收款提示信息之后，获取包含所述标识信息的注册信息；
第二结果判断模块，用于判断所述注册信息与所述收款方信息是否一致，得到第二判断结果；
转账金额转入模块，用于当所述第二判断结果表示所述注册信息与所述收款方信息一致时，将所述临时账户中的所述转账金额转入到所述收款方新建的账户中；所述收款方新建的账户的注册信息中的联系方式与所述标识信息对应的联系方式相同。
可选的，所述第二结果判断模块，具体可以包括：
第一注册信息发送单元，用于将所述注册信息发送至所述第一终端，提示所述发起方对所述注册信息进行确认；
确认信息获取单元，用于获取所述第一终端发送的所述发起方对所述注册信息的确认信息；
第一判断单元，用于根据所述确认信息判断所述注册信息与所述收款方信息是否一致。
可选的，所述第二结果判断模块，具体可以包括：
第一用户身份信息获取单元，获取所述收款方信息中包含的第一用户身份信息；所述第一用户身份信息至少包括姓名；
第二用户身份信息获取单元，用于获取所述注册信息中包含的第二用户身份信息；
第二判断单元，用于判断所述第一用户身份信息与所述第二用户身份信息是否一致。
可选的，所述装置还可以包括：
第一转账金额退回模块，用于当所述第二判断结果表示所述注册信息与所述收款方信息不一致时，将所述临时账户中的所述转账金额退回至所述发起方的账户中。
可选的，所述注册信息可以包括：姓名和联系方式；
或者，姓名、联系方式和证件信息。
可选的，所述装置还可以包括：
第三结果判断模块，用于在所述根据所述标识信息，发送收款提示信息之后，判断在预设时间段内，所述标识信息对应的收款方是否注册成功，得到第三判断结果；
第二转账金额退回模块，用于当所述第三判断结果表示在预设时间段内，所述标识信息对应的收款方没有注册成功时，将所述临时账户中的所述转账金额退回至所述发起方的账户中。
可选的，所述装置还可以包括：
退款请求获取模块，用于在将所述转账金额存储于临时账户中之后，获取所述发起方针对所述转账请求发起的退款请求；
转账金额退回模块，用于当确定所述退款请求的发起时间未超过时间限制时，将所述转账金额退回至所述发起方的账户中。
可选的，所述第一收款提示信息发送单元，具体可以包括：
第一收款提示信息发送子单元将所述收款提示信息以短信的形式发送至所述手机号码对应的终端；
第二收款提示信息发送子单元，将所述收款提示信息以语音的形式发送至所述手机号码对应的终端。
基于同样的思路，本说明书实施例还提供了上述方法对应的设备。
图5为本说明书实施例提供的对应于图1的一种转账请求的处理设备的结构示意图。如图5所示，设备500可以包括：
至少一个处理器510；以及，
与所述至少一个处理器通信连接的存储器530；其中，
所述存储器530存储有可被所述至少一个处理器510执行的指令520，所述指令被所述至少一个处理器510执行，以使所述至少一个处理器510能够：
获取第一终端提交的转账请求；所述第一终端上登录有所述转账请求的发起方的账户；
获取所述转账请求对应的收款方信息；所述收款方信息至少包括表示收款方联系方式的标识信息；
根据所述收款方信息判断所述收款方是否为发起所述转账请求的平台的注册用户，得到第一判断结果；
当所述第一判断结果表示所述收款方为非注册用户时，根据所述标识信息，发送收款提示信息，以便提示所述收款方进行收款。
图5中的设备，通过以联系方式作为用户的标识信息，当收款方不是平台的注册用户时，发送收款提示信息，提示非注册用户进行收款。本说明书实施例在不依赖第三方平台的情况下，能够完成平台用户向非平台用户转账的操作。而且采用联系方式作为标识信息，操作简单，有利于保护用户的隐私，提高用户体验。
在20世纪90年代，对于一个技术的改进可以很明显地区分是硬件上的改进(例如，对二极管、晶体管、开关等电路结构的改进)还是软件上的改进(对于方法流程的改进)。然而，随着技术的发展，当今的很多方法流程的改进已经可以视为硬件电路结构的直接改进。设计人员几乎都通过将改进的方法流程编程到硬件电路中来得到相应的硬件电路结构。因此，不能说一个方法流程的改进就不能用硬件实体模块来实现。例如，可编程逻辑器件(Programmable Logic Device,PLD)(例如现场可编程门阵列(Field Programmable Gate Array，FPGA))就是这样一种集成电路，其逻辑功能由用户对器件编程来确定。由设计人员自行编程来把一个数字系统“集成”在一片PLD上，而不需要请芯片制造厂商来设计和制作专用的集成电路芯片。而且，如今，取代手工地制作集成电路芯片，这种编程也多半改用“逻辑编译器(logic compiler)”软件来实现，它与程序开发撰写时所用的软件编译器相类似，而要编译之前的原始代码也得用特定的编程语言来撰写，此称之为硬件描述语言(Hardware Description Language，HDL)，而HDL也并非仅有一种，而是有许多种，如ABEL(Advanced Boolean Expression Language)、AHDL(Altera Hardware Description Language)、Confluence、CUPL(Cornell University Programming Language)、HDCal、JHDL(Java Hardware Description Language)、Lava、Lola、MyHDL、PALASM、RHDL(Ruby Hardware Description Language)等，目前最普遍使用的是VHDL(Very-High-Speed Integrated Circuit Hardware Description Language)与Verilog。本领域技术人员也应该清楚，只需要将方法流程用上述几种硬件描述语言 稍作逻辑编程并编程到集成电路中，就可以很容易得到实现该逻辑方法流程的硬件电路。
控制器可以按任何适当的方式实现，例如，控制器可以采取例如微处理器或处理器以及存储可由该(微)处理器执行的计算机可读程序代码(例如软件或固件)的计算机可读介质、逻辑门、开关、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑控制器和嵌入微控制器的形式，控制器的例子包括但不限于以下微控制器：ARC 625D、Atmel AT91SAM、Microchip PIC18F26K20以及Silicone Labs C8051F320，存储器控制器还可以被实现为存储器的控制逻辑的一部分。本领域技术人员也知道，除了以纯计算机可读程序代码方式实现控制器以外，完全可以通过将方法步骤进行逻辑编程来使得控制器以逻辑门、开关、专用集成电路、可编程逻辑控制器和嵌入微控制器等的形式来实现相同功能。因此这种控制器可以被认为是一种硬件部件，而对其内包括的用于实现各种功能的装置也可以视为硬件部件内的结构。或者甚至，可以将用于实现各种功能的装置视为既可以是实现方法的软件模块又可以是硬件部件内的结构。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机。具体的，计算机例如可以为个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任何设备的组合。
为了描述的方便，描述以上装置时以功能分为各种单元分别描述。当然，在实施本申请时可以把各单元的功能在同一个或多个软件和/或硬件中实现。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执 行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本申请可以在由计算机执行的计算机可执行指令的一般上下文中描述，例如程序模块。一般地，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本申请，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
以上所述仅为本申请的实施例而已，并不用于限制本申请。对于本领域技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本申请的权利要求范围之内。

Claims (20)

  1. 一种转账请求的处理方法，包括：
    获取第一终端提交的转账请求；所述第一终端上登录有所述转账请求的发起方的账户；
    获取所述转账请求对应的收款方信息；所述收款方信息至少包括表示收款方联系方式的标识信息；
    根据所述收款方信息判断所述收款方是否为发起所述转账请求的平台的注册用户，得到第一判断结果；
    当所述第一判断结果表示所述收款方为非注册用户时，根据所述标识信息，发送收款提示信息，以便提示所述收款方进行收款。
  2. 如权利要求1所述的方法，所述根据所述收款方信息判断所述收款方是否为发起所述转账请求的平台的注册用户，具体包括：
    查询注册用户数据库是否存在所述标识信息。
  3. 如权利要求1所述的方法，所述根据所述标识信息，发送收款提示信息，具体包括：
    当所述联系方式为手机号码时，将所述收款提示信息发送至所述手机号码对应的终端，提示所述收款方采用所述手机号码作为联系方式进行用户注册。
  4. 如权利要求1所述的方法，所述根据所述标识信息，发送收款提示信息，具体包括：
    当所述联系方式为电子邮箱时，将所述收款提示信息发送至所述电子邮箱对应的地址，提示所述收款方采用所述电子邮箱作为联系方式进行用户注册。
  5. 如权利要求1所述的方法，在所述根据所述标识信息，发送收款提示信息之前，还包括：
    确定所述转账请求中的转账金额；
    从所述发起方的账户中扣除所述转账金额；
    将所述转账金额存储于临时账户中；
    在所述根据所述标识信息，发送收款提示信息之后，还包括：
    获取包含所述标识信息的注册信息；
    判断所述注册信息与所述收款方信息是否一致，得到第二判断结果；
    当所述第二判断结果表示所述注册信息与所述收款方信息一致时，将所述临时账户中的所述转账金额转入到所述收款方新建的账户中；所述收款方新建的账户的注册信息 中的联系方式与所述标识信息对应的联系方式相同。
  6. 如权利要求5所述的方法，所述判断所述注册信息与所述收款方信息是否一致，具体包括：
    将所述注册信息发送至所述第一终端，提示所述发起方对所述注册信息进行确认；
    获取所述第一终端发送的所述发起方对所述注册信息的确认信息；
    根据所述确认信息判断所述注册信息与所述收款方信息是否一致。
  7. 如权利要求5所述的方法，所述判断所述注册信息与所述收款方信息是否一致，具体包括：
    获取所述收款方信息中包含的第一用户身份信息；所述第一用户身份信息至少包括姓名；
    获取所述注册信息中包含的第二用户身份信息；
    判断所述第一用户身份信息与所述第二用户身份信息是否一致。
  8. 如权利要求5所述的方法，所述方法还包括：
    当所述第二判断结果表示所述注册信息与所述收款方信息不一致时，将所述临时账户中的所述转账金额退回至所述发起方的账户中。
  9. 如权利要求5所述的方法，所述注册信息包括：姓名和联系方式；
    或者，姓名、联系方式和证件信息。
  10. 如权利要求4所述的方法，在所述根据所述标识信息，发送收款提示信息之后，还包括：
    判断在预设时间段内，所述标识信息对应的收款方是否注册成功，得到第三判断结果；
    当所述第三判断结果表示在预设时间段内，所述标识信息对应的收款方没有注册成功时，将所述临时账户中的所述转账金额退回至所述发起方的账户中。
  11. 如权利要求5所述的方法，在将所述转账金额存储于临时账户中之后，所述方法还包括：
    获取所述发起方针对所述转账请求发起的退款请求；
    当确定所述退款请求的发起时间未超过时间限制时，将所述转账金额退回至所述发起方的账户中。
  12. 如权利要求3所述的方法，所述将所述收款提示信息发送至所述手机号码对应的终端，具体包括：
    将所述收款提示信息以短信的形式发送至所述手机号码对应的终端；
    和/或，将所述收款提示信息以语音的形式发送至所述手机号码对应的终端。
  13. 一种转账请求的处理装置，包括：
    转账请求获取模块，用于获取第一终端提交的转账请求；所述第一终端上登录有所述转账请求的发起方的账户；
    收款方信息获取模块，用于获取所述转账请求对应的收款方信息；所述收款方信息至少包括表示收款方联系方式的标识信息；
    第一结果判断模块，用于根据所述收款方信息判断所述收款方是否为发起所述转账请求的平台的注册用户，得到第一判断结果；
    收款提示信息发送模块，用于当所述第一判断结果表示所述收款方为非注册用户时，根据所述标识信息，发送收款提示信息，以便提示所述收款方进行收款。
  14. 如权利要求13所述的装置，所述收款提示信息发送模块，具体包括：
    第一收款提示信息生成单元，用于根据所述转账请求生成收款提示信息；所述收款提示信息至少包括所述标识信息；
    第一收款提示信息发送单元，用于当所述联系方式为手机号码时，将所述收款提示信息发送至所述手机号码对应的终端，提示所述收款方采用所述手机号码作为联系方式进行用户注册。
  15. 如权利要求13所述的装置，所述收款提示信息发送模块，具体包括：
    第二收款提示信息生成单元，用于根据所述转账请求生成收款提示信息；所述收款提示信息至少包括所述标识信息；
    第二收款提示信息发送单元，用于当所述联系方式为电子邮箱时，将所述收款提示信息发送至所述电子邮箱对应的地址，提示所述收款方采用所述电子邮箱作为联系方式进行用户注册。
  16. 如权利要求13所述的装置，所述装置还包括：
    转账金额确定模块，用于在所述根据所述标识信息，发送收款提示信息之前，确定所述转账请求中的转账金额；
    转账金额扣除模块，用于从所述发起方的账户中扣除所述转账金额；
    转账金额存储模块，用于将所述转账金额存储于临时账户中；
    注册信息获取模块，用于在所述根据所述标识信息，发送收款提示信息之后，获取包含所述标识信息的注册信息；
    第二结果判断模块，用于判断所述注册信息与所述收款方信息是否一致，得到第二判断结果；
    转账金额转入模块，用于当所述第二判断结果表示所述注册信息与所述收款方信息一致时，将所述临时账户中的所述转账金额转入到所述收款方新建的账户中；所述收款方新建的账户的注册信息中的联系方式与所述标识信息对应的联系方式相同。
  17. 如权利要求16所述的装置，所述第二结果判断模块，具体包括：
    第一注册信息发送单元，用于将所述注册信息发送至所述第一终端，提示所述发起方对所述注册信息进行确认；
    确认信息获取单元，用于获取所述第一终端发送的所述发起方对所述注册信息的确认信息；
    第一判断单元，用于根据所述确认信息判断所述注册信息与所述收款方信息是否一致。
  18. 如权利要求16所述的装置，所述第二结果判断模块，具体包括：
    第一用户身份信息获取单元，获取所述收款方信息中包含的第一用户身份信息；所述第一用户身份信息至少包括姓名；
    第二用户身份信息获取单元，用于获取所述注册信息中包含的第二用户身份信息；
    第二判断单元，用于判断所述第一用户身份信息与所述第二用户身份信息是否一致。
  19. 如权利要求16所述的装置，所述装置还包括：
    退款请求获取模块，用于在将所述转账金额存储于临时账户中之后，获取所述发起方针对所述转账请求发起的退款请求；
    转账金额退回模块，用于当确定所述退款请求的发起时间未超过时间限制时，将所述转账金额退回至所述发起方的账户中。
  20. 一种转账请求的处理设备，包括：
    至少一个处理器；以及，
    与所述至少一个处理器通信连接的存储器；其中，
    所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够：
    获取第一终端提交的转账请求；所述第一终端上登录有所述转账请求的发起方的账户；
    获取所述转账请求对应的收款方信息；所述收款方信息至少包括表示收款方联系方式的标识信息；
    根据所述收款方信息判断所述收款方是否为发起所述转账请求的平台的注册用户，得到第一判断结果；
    当所述第一判断结果表示所述收款方为非注册用户时，根据所述标识信息，发送收款提示信息，以便提示所述收款方进行收款。
PCT/CN2020/070892 2019-05-29 2020-01-08 一种转账请求的处理方法、装置及设备 Ceased WO2020238231A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/877,235 US20200410474A1 (en) 2019-05-29 2020-05-18 Processing account transfer requests

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910455717.8 2019-05-29
CN201910455717.8A CN110264327A (zh) 2019-05-29 2019-05-29 一种转账请求的处理方法、装置及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/877,235 Continuation-In-Part US20200410474A1 (en) 2019-05-29 2020-05-18 Processing account transfer requests

Publications (1)

Publication Number Publication Date
WO2020238231A1 true WO2020238231A1 (zh) 2020-12-03

Family

ID=67915650

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/070892 Ceased WO2020238231A1 (zh) 2019-05-29 2020-01-08 一种转账请求的处理方法、装置及设备

Country Status (3)

Country Link
US (1) US20200410474A1 (zh)
CN (1) CN110264327A (zh)
WO (1) WO2020238231A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113706137A (zh) * 2021-10-21 2021-11-26 国网汇通金财（北京）信息科技有限公司 一种应用于缴费信息的数据处理方法及系统

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110264327A (zh) * 2019-05-29 2019-09-20 阿里巴巴集团控股有限公司 一种转账请求的处理方法、装置及设备
CN114819958A (zh) * 2019-10-31 2022-07-29 支付宝(杭州)信息技术有限公司 基于区块链的交易处理方法、装置及设备
CN111105225A (zh) * 2019-11-29 2020-05-05 中移动金融科技有限公司 一种转账方法、装置、设备及存储介质
CN113256294B (zh) * 2019-12-13 2022-12-16 支付宝(杭州)信息技术有限公司 一种网络支付方法、装置、设备及系统
CN111913920A (zh) * 2020-08-12 2020-11-10 中国工商银行股份有限公司 电子名片生成方法、装置、计算机系统和计算机可读介质
US20220253848A1 (en) * 2020-11-12 2022-08-11 Wells Fargo Bank, N.A. Electronic payment reversion
TWI767580B (zh) * 2021-02-22 2022-06-11 兆豐國際商業銀行股份有限公司 轉帳系統與轉帳方法
CN113052606A (zh) * 2021-03-30 2021-06-29 南京维沃软件技术有限公司 应用的防诈骗方法、装置和电子设备
CN113052587B (zh) * 2021-04-30 2024-10-29 中国银行股份有限公司 基于区块链的转账业务处理方法及装置
CN116308323A (zh) * 2023-03-27 2023-06-23 平安科技（深圳）有限公司 一种移动终端虚拟资源处理方法、装置、设备及存储介质
US20250265577A1 (en) * 2024-02-21 2025-08-21 The Toronto-Dominion Bank System and methods for validating resource transfers in a computer network

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101777166A (zh) * 2010-01-21 2010-07-14 中国光大银行 一种利用手机进行银行转账的方法
CN102930469A (zh) * 2012-11-13 2013-02-13 中国民生银行股份有限公司 转账数据处理方法和装置
US20170053346A1 (en) * 2014-02-14 2017-02-23 Zte Corporation Registration method, device and system for third-party payment platform
CN107169753A (zh) * 2017-03-31 2017-09-15 深圳前海微众银行股份有限公司 转账方法、装置及计算机可读存储介质
CN110264327A (zh) * 2019-05-29 2019-09-20 阿里巴巴集团控股有限公司 一种转账请求的处理方法、装置及设备

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TW201227556A (en) * 2010-12-24 2012-07-01 Chunghwa Telecom Co Ltd Electronic transaction system and payment method using telecommunication phone number as account number
CN104200365A (zh) * 2014-09-03 2014-12-10 高勃 一种电子支票的开票及解付方法
CN108197913B (zh) * 2017-12-18 2021-01-05 深圳前海微众银行股份有限公司 基于区块链的支付方法、系统以及计算机可读存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101777166A (zh) * 2010-01-21 2010-07-14 中国光大银行 一种利用手机进行银行转账的方法
CN102930469A (zh) * 2012-11-13 2013-02-13 中国民生银行股份有限公司 转账数据处理方法和装置
US20170053346A1 (en) * 2014-02-14 2017-02-23 Zte Corporation Registration method, device and system for third-party payment platform
CN107169753A (zh) * 2017-03-31 2017-09-15 深圳前海微众银行股份有限公司 转账方法、装置及计算机可读存储介质
CN110264327A (zh) * 2019-05-29 2019-09-20 阿里巴巴集团控股有限公司 一种转账请求的处理方法、装置及设备

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113706137A (zh) * 2021-10-21 2021-11-26 国网汇通金财（北京）信息科技有限公司 一种应用于缴费信息的数据处理方法及系统
CN113706137B (zh) * 2021-10-21 2022-04-01 国网汇通金财（北京）信息科技有限公司 一种应用于缴费信息的数据处理方法及系统

Also Published As

Publication number Publication date
CN110264327A (zh) 2019-09-20
US20200410474A1 (en) 2020-12-31

Similar Documents

Publication Publication Date Title
WO2020238231A1 (zh) 一种转账请求的处理方法、装置及设备
US11574314B2 (en) Transferring money using interactive interface elements
CN107026815B (zh) 一种支付业务处理方法、支付服务器、相关设备及系统
TWI755677B (zh) 獲取銀行卡簽約要素資訊的方法、系統及設備
CN110009335B (zh) 支付码生成、移动支付方法、装置及设备
US20200043067A1 (en) Resource transmission methods and apparatus
CN107003830A (zh) 安全移动联系系统(smcs)
US20240232856A1 (en) Payment method and apparatus, and device
CN108282471B (zh) 一种电子凭证的传输方法、装置及设备
US11222311B2 (en) System and method for secure data transfer
JP2019536142A (ja) 送金方法およびシステム
WO2019179249A1 (zh) 一种支付方法、装置及电子设备
CN108280648A (zh) 交易处理方法和服务器
CN107220818A (zh) 网上支付方法及装置
HK40014811A (zh) 一种转账请求的处理方法、装置及设备
US12205088B2 (en) Value transfer card management system
US20220294924A1 (en) Entity-based controls for value transfer cards
WO2017124935A1 (zh) 事务处理方法和系统
CN107360575A (zh) 一种手机号码的实名开通方法及装置
WO2024069121A1 (en) Network-agnostic system to facilitate peer-to-peer transfers
CN115243230A (zh) 一种业务执行方法、装置、存储介质及电子设备
CA3047263A1 (en) Value transfer card management system
CA3047266A1 (en) Entity-based controls for value transfer cards
CA3027901A1 (en) System and method for secure data transfer

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20815483

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20815483

Country of ref document: EP

Kind code of ref document: A1