[go: up one dir, main page]

WO2016089783A1 - System and method for secure account transfer - Google Patents

System and method for secure account transfer Download PDF

Info

Publication number
WO2016089783A1
WO2016089783A1 PCT/US2015/063028 US2015063028W WO2016089783A1 WO 2016089783 A1 WO2016089783 A1 WO 2016089783A1 US 2015063028 W US2015063028 W US 2015063028W WO 2016089783 A1 WO2016089783 A1 WO 2016089783A1
Authority
WO
WIPO (PCT)
Prior art keywords
payee
payment
account
authentication identifier
bank 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/US2015/063028
Other languages
French (fr)
Inventor
Jian Sun
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.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding 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
Priority claimed from CN201410727542.9A external-priority patent/CN105719183A/en
Application filed by Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to JP2017522509A priority Critical patent/JP2018501541A/en
Priority to SG11201703418PA priority patent/SG11201703418PA/en
Priority to KR1020177014907A priority patent/KR20170085059A/en
Publication of WO2016089783A1 publication Critical patent/WO2016089783A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

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/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems

Definitions

  • This disclosure is generally related to financial transactions. More specifically, this disclosure is related to a system and method for secure transfer of funds based on a third- party entity that authenticates the validity of a payee.
  • Related Art
  • a payer can transfer funds from his bank account to the bank account of a payee by using a variety of computing and mobile devices.
  • multiple payers may wish to transfer funds to a single payee, e.g., multiple families paying tuition to a school, or multiple business owners donating funds to a charity or trust account.
  • certain payee information such as the name and bank account number of the payee, may be publicly disclosed.
  • the public disclosure of some payee information can result in security issues. For example, a hacker may obtain a bank account identifier for a person who has the same name (e.g., same first name and same last name) as the intended payee.
  • a hacker can then publish incorrect information over the internet by replacing the bank account identifier for the intended payee with a different bank account identifier for the person with the same name.
  • a hacker may intercept a packet that contains account information and replace the payee's account identifier with a malicious account identifier.
  • a payee's system may remain unaware of the replaced identifier, and proceed with the indicated funds transfer.
  • funds may be improperly transferred to the bank account of an unauthorized person.
  • current methods for account transfer may not allow a payer to state the dedicated purpose for a transfer of funds, which may also result in improper funds transfer.
  • One embodiment provides a system that facilitates secure transfer of funds.
  • the system generates, by a server, an authentication identifier for a payee of a bank account, wherein the authentication identifier indicates the bank account and a
  • the system receives, from a payer, a message which indicates a first command to transfer a payment amount to the payee, wherein the first command includes the authentication identifier.
  • the system extracts information associated with the payment account and the bank account from the authentication identifier.
  • the system transfers the payment amount to the bank account of the payee based on the extracted information.
  • the system determines the bank account and the corresponding payment account of the payee, and authenticates the bank account and the payment account of the payee.
  • the system transmits one or more messages to a payment system which manages the payment account for the payee, wherein the payment system communicates with a banking system which manages the bank account for the payee.
  • the system transmits a message which indicates a second command to increase funds in the payment account by the payment amount and to freeze the payment account.
  • the system in response to receiving the second message, increases, by a payment system which manages the payment account of the payee, the funds in the payment account by the payment amount.
  • the system also freezes the payment account.
  • the system in response to receiving a confirmation message which indicates a completion of the second command, stores in a database a report which includes the payment amount, the payee, and the authentication identifier.
  • the system performs a search in the database for one or more reports which include the authentication identifier, based on a predetermined date or time period, wherein a report includes a payment amount.
  • the system calculates a total payment amount for the one or more reports.
  • the system generates a batch number for the one or more reports.
  • the system also transmits a message which indicates a third command to transfer the total payment amount from the payment account of the payee to the bank account of the payee, to unfreeze the payment account, and to deduct the total payment amount from the funds of the payment account.
  • the system in response to receiving a confirmation message which indicates a completion of the third command, the system updates in a database a report which includes the total payment amount, the payee, the authentication identifier, and the batch number.
  • the system in response to receiving the third command, the system generates, by a payment system which manages the payment account of the payee, a message which indicates a fourth command to transfer the total payment amount from the payment account to the bank account of the payee.
  • the system unfreezes the payment account.
  • the system deducts the total payment account from the funds of the payment account.
  • the system also transmits a confirmation message to the server which indicates a completion of the third command.
  • the system authenticates, by the payment system, the bank account of the payee.
  • the system generates, by a server, a first authentication identifier for a payee, wherein the first authentication identifier is associated with a payment account of the payee and stored in the server.
  • the system receives, from a payer, a request to transfer a payment amount to the payee, wherein the request includes a second authentication identifier.
  • the server extracts the payment account based on the first authentication identifier. The system transfers the payment amount to the payment account of the payee.
  • the system provides that the payment account of the payee at the third party system is coupled to the bank account of the payee at the bank system.
  • the system generates a first authentication identifier for the payee at the third party system, wherein the first authentication identifier is associated with the bank account of the payee and stored in the third party system.
  • the system receives, from a payer, a request to transfer a payment amount to the payee, wherein the request includes a second authentication identifier.
  • the system extracts the coupled bank account of the payee at the bank system, and transfers the payment amount to the bank account of the payee.
  • FIG. 1A illustrates an exemplary computing system that facilitates secure transfer of funds, in accordance with an embodiment of the present application.
  • FIG. IB illustrates an exemplary computing environment that facilitates secure transfer of funds, in accordance with an embodiment of the present application.
  • FIG. 2 presents a flowchart illustrating a method by a transaction server for securely transferring funds, in accordance with an embodiment of the present application.
  • FIG. 3 presents a flowchart illustrating a method by a transaction server for securely transferring funds, including interaction with a payment system, in accordance with an embodiment of the present application.
  • FIG. 4A presents a flowchart illustrating a method by a transaction server for summarizing and processing a secure transfer of funds, including interaction with a payment system, in accordance with an embodiment of the present application.
  • FIG. 4B presents a flowchart illustrating a method by a payment system for processing a secure transfer of funds, in accordance with an embodiment of the present application.
  • FIG. 5 illustrates an exemplary apparatus that facilitates secure transfer of funds, in accordance with an embodiment of the present application.
  • FIG. 6 illustrates an exemplary computer system that facilitates secure transfer of funds, in accordance with an embodiment of the present application.
  • Embodiments of the present invention solve the problem of improper funds transfer by providing a system which validates the authenticity of a payee, enables freezing of the appropriate payment account, and facilitates automatic funds transfer from the payment account to the corresponding bank account.
  • Improper funds transfer can occur when certain information of a payee is publicly disclosed. For example, if the name and bank account number of a payee are known, a hacker can replace the payee's bank account number with the bank account number for a person with the same name as the payee. In another example, a hacker can intercept a packet that contains a bank account number for the payee and insert in a bank account number for an unauthorized person. Both of these situations may result in improper funds transfer.
  • the present system addresses these security issues by providing a system which acts as a third-party and provides validation of the payee's authenticity.
  • the system generates a unique authentication identifier for the payee and provides the unique identifier to the payer. This allows the payer to transfer funds to the payee based on the unique identifier, without using the name or account number of the payee.
  • the present system may refer to a third-party payment system provided by a third-party payment service provider, such as Alipay or Paypal.
  • the third- party payment system which includes a payment account is coupled to a bank system which includes a bank account of the payee. As a result, the payee does not need to disclose
  • the system also enables a payment system to transfer funds to and freeze the payee's payment account ("payment account transfer"), run a periodic batch report, and automatically transfer all funds associated with the identifier from the payee's payment account to the payee's bank account ("bank account transfer").
  • the system can generate reports detailing the payments made to the payee with respect to both the payment account transfer and the subsequent automatic bank account transfer.
  • the system can set an expiration time for the identifier and prevent the payer from transferring funds if the identifier is expired.
  • the system can also generate a verification code that may only be used for a predetermined number of times, and send the code to the payer.
  • the system can provide the payer with an option to enter a short description or summary of the reason for the fund transfer. The system can subsequently review the entered description and compare it against the generated reports.
  • FIG. 1A illustrates an exemplary computing system that facilitates secure transfer of funds, in accordance with an embodiment of the present application.
  • system 100 can include computing devices 130, 132, and 134, which are associated with users 120, 122, and 124, respectively.
  • Computing devices 130-134 can include, for example, a tablet, a mobile phone, an electronic reader, a laptop computer, a desktop computer, or any other computing device.
  • Computing devices 130-134 can communicate with a transaction server 142 (e.g., a server device which provides authentication services for a financial transaction) and application servers 142 and 144 (e.g., servers or systems which manage payment accounts or bank accounts of a user) via a network 140.
  • a transaction server 142 e.g., a server device which provides authentication services for a financial transaction
  • application servers 142 and 144 e.g., servers or systems which manage payment accounts or bank accounts of a user
  • user 120 interacts with corresponding computing device 130.
  • user 120 may browse to a website for a payment system or a banking system via a web browser running on mobile device 130.
  • User 120 may indicate on device 130 a payment (e.g., a transfer of funds) to a specific payee.
  • the system can provide an authentication identifier to user 120 for use in transferring funds to the payee.
  • the payee may previously provide to the system a list of payers authorized to receive the authentication identifier.
  • the authentication identifier can be, e.g., a digital certificate or a string of numbers of characters.
  • Server 142 can be a third-party which provides authentication services to users who wish to transfer funds to certain payees. Server 142 can extract from the authentication identifier the corresponding payment account and bank account of the payee. Server 142 can then initiate a transfer of the payment to the payee.
  • Server 142 can communicate with application server 144, which can be a system that manages the payment account of the payee ("payment server").
  • Application server 144 can communicate with application server 146, which can be a system that manages the bank account of the payee ("bank server”).
  • server 142 can send a message to payment server 144 to process the payment amount, which can result in payment server 144 increasing the funds of the payment account by the payment amount, and subsequently freezing the payment account, such that no changes may be made to the amount of the funds in the payment account.
  • Payment server 144 can notify server 142 of the increase and freeze, and server 142 can generate a report which indicates the payment amount, the payee, and the authentication identifier.
  • server 142 can search for reports associated with the authentication identifier and generate a batch number for the reports.
  • Server 142 can send a message to payment server 144 to transfer a total payment amount associated with the batch number.
  • Payment server 144 can transfer the funds to bank server 146, which can in turn send a confirmation message of a successful transaction. The confirmation message can also be sent to server 142.
  • Payment server 144 can also decrease the funds of the payment account by the total payment amount, and subsequently unfreeze the payment account.
  • Server 142 can then generate a report which indicates the total payment amount, the payee, the authentication identifier, and the batch number.
  • system 100 depicts a system that facilitates secure funds transfer to a payee based on a third-party which provides a unique identifier for the payee and subsequent validation for the unique identifier.
  • the third party can also generate reports and communicate with systems which manage the payment account and bank account of the payee.
  • FIG. IB illustrates an exemplary computing environment 150 that facilitates secure transfer of funds, in accordance with an embodiment of the present application.
  • Third party system 160 can include a payment account 162 of a payee
  • bank system 170 can include a bank account 172 of the payee.
  • Third party system 160 and bank system 170 can be independent systems, and each of payment account 162 and bank account 172 can be associated with or belong to the respective independent system.
  • Third party system 160 can perform the functionality described in relation to server 142 and payment server 144 of FIG. 1A
  • bank system 170 can perform the functionality described in relation to bank server 146 of FIG. 1A.
  • FIG. 2 presents a flowchart 200 illustrating a method by a transaction server for securely transferring funds, in accordance with an embodiment of the present application.
  • the system determines, by the transaction server, a bank account and a corresponding payment account of a payee (operation 202).
  • the server authenticates the bank account and the payment account of the payee (operation 204).
  • the server generates an authentication identifier for the payee, where the authentication identifier indicates the bank account and the payment account of the payee (operation 206).
  • the authentication identifier is a unique identifier which can be, e.g., a digital certificate or a string of numbers, and can indicate or correspond to the payment account and the bank account.
  • the server receives, from a payer that is a user of a client computing device, a message which indicates a first command to transfer a payment amount to the payee (operation 208).
  • the first command indicates the authentication identifier.
  • the payer in possession of the authentication identifier, can send the identifier and the payment amount in the command to transfer funds to the payee.
  • the server verifies the authentication identifier (decision 210). In some instances, the verification includes checking whether an expiration time for the authentication identifier has been reached. In some instances, the verification includes checking whether the authentication identifier sent by the payer successfully matches the authentication identifier generated for the payee. If the server does not successfully verify the identifier, the operation returns. If the server does successfully verify the identifier, the server extracts information associated with the payment account and the bank account from the authentication identifier (operation 212). For example, the server can extract the account number or other identifier for the payment account and the bank account. Finally, the server transfers the payment amount to the bank account of the payee based on the extracted information (operation 214). Operation 214 can include the operations described below in FIGs. 3, 4A, and 4B.
  • FIG. 3 presents a flowchart 300 illustrating a method by a transaction server for securely transferring funds, including interaction with a payment system, in accordance with an embodiment of the present application.
  • the system transmits, by the transaction server, a message which indicates a second command to increase funds in the payment account and to freeze the payment account (operation 302).
  • the system increases, by a payment system which manages the payment account of the payee, the funds in the payment account by the payment amount, and freezes the payment account (operation 304).
  • the server receives from the payment system a confirmation message which indicates a completion of the second command (operation 306).
  • the server stores in a database a report which indicates the payment amount, the payee, and the authentication identifier
  • FIG. 4A presents a flowchart 400 illustrating a method by a transaction server for summarizing and processing a secure transfer of funds, including interaction with a payment system, in accordance with an embodiment of the present application.
  • the server performs a search in a database for one or more reports which include an authentication identifier, based on a predetermined date or time period (operation 402).
  • a report includes a payment amount, and the predetermined date or time period can be, e.g., a 24-hour period for a certain date.
  • the server calculates a total payment amount for the one or more reports based on the payment amount included in each report in the search result (operation 404).
  • the server generates a batch number for the one or more reports (operation 406).
  • the server transmits a message which indicates a third command to transfer the total payment amount from the payment account of the payee to the bank account of the payee (operation 408).
  • the third command also includes instructions to unfreeze the payment account and to deduct the total payment amount from the funds of the payment account.
  • the operation then continues as described at Label A of FIG. 4B (e.g., a method performed by the payment system).
  • the server updates in a database a report which includes the total payment amount, the payee, the authentication identifier, and the batch number (operation 410).
  • FIG. 4B presents a flowchart 450 illustrating a method by a payment system for processing a secure transfer of funds, in accordance with an embodiment of the present application.
  • a payment system which manages the payment account of the payee generates a message which indicates a fourth command to transfer the total payment amount from the payment account to the bank account of the payee (operation 452).
  • the payment system authenticates the bank account of the payee (operation 454).
  • the payment system unfreezes the payment account of the payee (operation 456) and deducts the total payment amount from the funds of the payment account (operation 458).
  • the payment system transmits to the server a confirmation message which indicates a completion of the third command (operation 460).
  • FIG. 5 illustrates an exemplary apparatus 500 that facilitates secure transfer of funds, in accordance with an embodiment of the present application.
  • Apparatus 500 can comprise a plurality of modules which may communicate with one another via a wired or wireless communication channel.
  • Apparatus 500 may be realized using one or more integrated circuits, and may include fewer or more modules than those shown in FIG. 5.
  • apparatus 500 may be integrated in a computer system, or realized as a separate device which is capable of communicating with other computer systems and/or devices.
  • apparatus 500 can comprise a communication module 502, an authentication identifier- generating module 504, an authentication identifier-processing module 506, a funds-transferring module 508, a reporting module 510, and a payment system-processing module 512.
  • communication module 502 can send and/or receive data packets to/from other network nodes across a computer network, where a data packet can correspond to a first command to transfer a payment amount to a payee.
  • Authentication identifier-generating module 504 can generate an authentication identifier for a payee of a bank account, where the authentication identifier indicates the bank account and a corresponding payment account of the payee.
  • the authentication identifier can be a first authentication identifier associated with the payment account of the payee or associated with the bank account of the payee.
  • authentication identifier-processing module 506 can extract information associated with the payment account and the bank account from the authentication identifier. Funds-transferring module 508 can transfer the payment amount to the bank account of the payee based on the extracted information. In addition, authentication identifier-generating module 504 can determine the bank account and corresponding payment account of the payee. Authentication identifier-processing module 506 can authenticate the bank account and payment account of the payee. Communication module 502 can also receive a request to transfer a payment amount to the payee, where the request includes a second authentication identifier. Authentication identifier-processing module 506 can successfully match the second authentication identifier to the first authentication identifier.
  • Authentication identifier-processing module 506 can extract the payment account based on the first authentication identifier, and extract the coupled bank account of the payee.
  • Communication module 502 can transmit a message which indicates a second command to increase funds in the payment account by the payment amount and to freeze the payment account.
  • Payment system-processing module 512 can increase the funds in the payment account by the payment amount and freeze the payment account.
  • Reporting module 510 can store in a database a report which includes the payment amount, the payee, and the authentication identifier. Reporting module 510 can also perform a search in the database for one or more reports which include the authentication identifier, based on a predetermined date or time period, wherein a report includes a payment amount. Reporting module 510 can calculate a total payment amount for the one or more reports, and generate a batch number for the one or more reports.
  • Communication module 502 can transmit a message which indicates a third command to transfer the total payment amount from the payment account of the payee to the bank account of the payee, to unfreeze the payment account, and to deduct the total payment amount from the funds of the payment account.
  • Payment system-processing module 512 can authenticate the bank account of the payee, unfreeze the payment account, decrease the funds in the payment account by the total payment amount, and transmit a message which indicates a completion of the third command.
  • reporting module 510 can update in a database a report which includes the total payment amount, the payee, the authentication identifier, and the batch number.
  • Communication module 502 can receive a confirmation message which indicates a completion of the third command.
  • FIG. 6 illustrates an exemplary computer system 602 that facilitates control of the display direction of content on a device, in accordance with an embodiment of the present application.
  • Computer system 602 includes a processor 604, a memory 606, and a storage device 608.
  • Memory 606 can include a volatile memory (e.g., RAM) that serves as a managed memory, and can be used to store one or more memory pools.
  • computer system 602 can be coupled to a display device 610, a keyboard 612, and a pointing device 614.
  • Storage device 608 can store an operating system 616, a content-processing system 618, and data 632.
  • Content-processing system 618 can include instructions, which when executed by computer system 602, can cause computer system 602 to perform methods and/or processes described in this disclosure. Specifically, content-processing system 618 may include instructions for sending and/or receiving data packets to/from other network nodes across a computer network, where a data packet can correspond to a first command to transfer a payment amount to a payee (communication module 620). Content-processing system 618 can include instructions for generating an authentication identifier for a payee of a bank account, where the authentication identifier indicates the bank account and a corresponding payment account of the payee (authentication identifier- generating module 622). The authentication identifier can be a first authentication identifier associated with the payment account of the payee or associated with the bank account of the payee.
  • Content-processing system 618 can also include instructions for, in response to successfully verifying the authentication identifier, extracting information associated with the payment account and the bank account from the authentication identifier (authentication identifier-processing module 624).
  • Content-processing system 618 can include instructions for transferring the payment amount to the bank account of the payee based on the extracted information (funds-transferring module 626).
  • Content-processing system 618 can include instructions for determining the bank account and corresponding payment account of the payee (authentication identifier- generating module 622) and for authenticating the bank account and payment account of the payee (authentication identifier-processing module 624).
  • Content- processing system 618 can further include instructions for receiving a request to transfer a payment amount to the payee, where the request includes a second authentication identifier (communication module 620).
  • Content-processing system 618 can include instructions for successfully matching the second authentication identifier to the first authentication identifier (authentication identifier-processing module 624).
  • Content-processing system 618 can also include instructions for extracting the payment account based on the first authentication identifier, and for extracting the coupled bank account of the payee (authentication identifier- processing module 624).
  • Content-processing system 618 can additionally include instructions for transmitting a message which indicates a second command to increase funds in the payment account by the payment amount and to freeze the payment account (communication module 620). Content-processing system 618 can include instructions for increasing the funds in the payment account by the payment amount and freeze the payment account (payment system-processing module 630).
  • Content-processing system 618 can include instructions for storing in a database a report which includes the payment amount, the payee, and the authentication identifier, and for performing a search in the database for one or more reports which include the authentication identifier, based on a predetermined date or time period, where a report includes a payment amount (reporting module 628).
  • Content-processing system 618 can include instructions for calculating a total payment amount for the one or more reports, and for generating a batch number for the one or more reports (reporting module 628).
  • content-processing system 618 can include instructions for transmitting a message which indicates a third command to transfer the total payment amount from the payment account of the payee to the bank account of the payee, to unfreeze the payment account, and to deduct the total payment amount from the funds of the payment account
  • Content-processing system 618 can include instructions for authenticating the bank account of the payee, unfreezing the payment account, decreasing the funds in the payment account by the total payment amount, and transmitting a message which indicates a completion of the third command (payment system-processing module 6300.
  • Content-processing system 618 can include instructions for, in response to receiving a confirmation message which indicates a completion of the third command, updating in a database a report which includes the total payment amount, the payee, the authentication identifier, and the batch number (reporting module 628). Content-processing system 618 can include instructions for receiving a confirmation message which indicates a completion of the third command (communication module 620).
  • Data 632 can include any data that is required as input or that is generated as output by the methods and/or processes described in this disclosure. Specifically, data 632 can store at least: an authentication identifier; information which indicates a payment account and a corresponding bank account; one or more commands; a payment amount; information indicating a payer and a payee; one or more reports that indicate a payment amount, a payee, an
  • the data structures and code described in this detailed description are typically stored on a computer-readable storage medium, which may be any device or medium that can store code and/or data for use by a computer system.
  • the computer-readable storage medium includes, but is not limited to, volatile memory, non-volatile memory, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs), DVDs (digital versatile discs or digital video discs), or other media capable of storing computer-readable media now known or later developed.
  • the methods and processes described in the detailed description section can be embodied as code and/or data, which can be stored in a computer-readable storage medium as described above.
  • a computer system reads and executes the code and/or data stored on the computer-readable storage medium, the computer system performs the methods and processes embodied as data structures and code and stored within the computer-readable storage medium.
  • the methods and processes described above can be included in hardware modules.
  • the hardware modules can include, but are not limited to, application-specific integrated circuit (ASIC) chips, field-programmable gate arrays (FPGAs), and other programmable-logic devices now known or later developed.
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate arrays
  • the hardware modules When the hardware modules are activated, the hardware modules perform the methods and processes included within the hardware modules.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

One embodiment provides a system that facilitates secure transfer of funds. During operation, the system generates, by a server, an authentication identifier for a payee of a bank account, wherein the authentication identifier indicates the bank account and a corresponding payment account of the payee. The system receives, from a payer, a message which indicates a first command to transfer a payment amount to the payee, wherein the first command includes the authentication identifier. In response to successfully verifying the authentication identifier, the system extracts information associated with the payment account and the bank account from the authentication identifier. The system transfers the payment amount to the bank account of the payee based on the extracted information.

Description

SYSTEM AND METHOD FOR SECURE ACCOUNT
TRANSFER
Inventor: Jian Sun BACKGROUND Field
[0001] This disclosure is generally related to financial transactions. More specifically, this disclosure is related to a system and method for secure transfer of funds based on a third- party entity that authenticates the validity of a payee. Related Art
[0002] The progress of technology brings both an increasing convenience and risk to financial transactions. A payer can transfer funds from his bank account to the bank account of a payee by using a variety of computing and mobile devices. In some cases, multiple payers may wish to transfer funds to a single payee, e.g., multiple families paying tuition to a school, or multiple business owners donating funds to a charity or trust account. In these instances, certain payee information, such as the name and bank account number of the payee, may be publicly disclosed. The public disclosure of some payee information can result in security issues. For example, a hacker may obtain a bank account identifier for a person who has the same name (e.g., same first name and same last name) as the intended payee. The hacker can then publish incorrect information over the internet by replacing the bank account identifier for the intended payee with a different bank account identifier for the person with the same name. In another example, a hacker may intercept a packet that contains account information and replace the payee's account identifier with a malicious account identifier. Upon receiving the intercepted packet, a payee's system may remain unaware of the replaced identifier, and proceed with the indicated funds transfer. As a result, in both of these examples, funds may be improperly transferred to the bank account of an unauthorized person. In addition, current methods for account transfer may not allow a payer to state the dedicated purpose for a transfer of funds, which may also result in improper funds transfer. SUMMARY
[0003] One embodiment provides a system that facilitates secure transfer of funds.
During operation, the system generates, by a server, an authentication identifier for a payee of a bank account, wherein the authentication identifier indicates the bank account and a
corresponding payment account of the payee. The system receives, from a payer, a message which indicates a first command to transfer a payment amount to the payee, wherein the first command includes the authentication identifier. In response to successfully verifying the authentication identifier, the system extracts information associated with the payment account and the bank account from the authentication identifier. The system transfers the payment amount to the bank account of the payee based on the extracted information.
[0004] In some embodiments, the system determines the bank account and the corresponding payment account of the payee, and authenticates the bank account and the payment account of the payee.
[0005] In some embodiments, the system transmits one or more messages to a payment system which manages the payment account for the payee, wherein the payment system communicates with a banking system which manages the bank account for the payee.
[0006] In some embodiments, the system transmits a message which indicates a second command to increase funds in the payment account by the payment amount and to freeze the payment account.
[0007] In some embodiments, in response to receiving the second message, the system increases, by a payment system which manages the payment account of the payee, the funds in the payment account by the payment amount. The system also freezes the payment account.
[0008] In some embodiments, in response to receiving a confirmation message which indicates a completion of the second command, the system stores in a database a report which includes the payment amount, the payee, and the authentication identifier.
[0009] In some embodiments, the system performs a search in the database for one or more reports which include the authentication identifier, based on a predetermined date or time period, wherein a report includes a payment amount. The system calculates a total payment amount for the one or more reports. The system generates a batch number for the one or more reports. The system also transmits a message which indicates a third command to transfer the total payment amount from the payment account of the payee to the bank account of the payee, to unfreeze the payment account, and to deduct the total payment amount from the funds of the payment account. [0010] In some embodiments, in response to receiving a confirmation message which indicates a completion of the third command, the system updates in a database a report which includes the total payment amount, the payee, the authentication identifier, and the batch number.
[0011] In some embodiments, in response to receiving the third command, the system generates, by a payment system which manages the payment account of the payee, a message which indicates a fourth command to transfer the total payment amount from the payment account to the bank account of the payee. The system unfreezes the payment account. The system deducts the total payment account from the funds of the payment account. The system also transmits a confirmation message to the server which indicates a completion of the third command.
[0012] In some embodiments, the system authenticates, by the payment system, the bank account of the payee.
[0013] In some embodiments, the system generates, by a server, a first authentication identifier for a payee, wherein the first authentication identifier is associated with a payment account of the payee and stored in the server. The system receives, from a payer, a request to transfer a payment amount to the payee, wherein the request includes a second authentication identifier. Upon successfully matching the second authentication identifier with the first authentication identifier, the server extracts the payment account based on the first authentication identifier. The system transfers the payment amount to the payment account of the payee.
[0014] In some embodiments, the system provides that the payment account of the payee at the third party system is coupled to the bank account of the payee at the bank system. The system generates a first authentication identifier for the payee at the third party system, wherein the first authentication identifier is associated with the bank account of the payee and stored in the third party system. The system receives, from a payer, a request to transfer a payment amount to the payee, wherein the request includes a second authentication identifier. Upon successfully matching the second authentication identifier with the first authentication identifier at the third party system, the system extracts the coupled bank account of the payee at the bank system, and transfers the payment amount to the bank account of the payee.
BRIEF DESCRIPTION OF THE FIGURES
[0015] FIG. 1A illustrates an exemplary computing system that facilitates secure transfer of funds, in accordance with an embodiment of the present application.
[0016] FIG. IB illustrates an exemplary computing environment that facilitates secure transfer of funds, in accordance with an embodiment of the present application. [0017] FIG. 2 presents a flowchart illustrating a method by a transaction server for securely transferring funds, in accordance with an embodiment of the present application.
[0018] FIG. 3 presents a flowchart illustrating a method by a transaction server for securely transferring funds, including interaction with a payment system, in accordance with an embodiment of the present application.
[0019] FIG. 4A presents a flowchart illustrating a method by a transaction server for summarizing and processing a secure transfer of funds, including interaction with a payment system, in accordance with an embodiment of the present application.
[0020] FIG. 4B presents a flowchart illustrating a method by a payment system for processing a secure transfer of funds, in accordance with an embodiment of the present application.
[0021] FIG. 5 illustrates an exemplary apparatus that facilitates secure transfer of funds, in accordance with an embodiment of the present application.
[0022] FIG. 6 illustrates an exemplary computer system that facilitates secure transfer of funds, in accordance with an embodiment of the present application.
[0023] In the figures, like reference numerals refer to the same figure elements.
DETAILED DESCRIPTION
[0024] The following description is presented to enable any person skilled in the art to make and use the embodiments, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present disclosure. Thus, the present invention is not limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.
Overview
[0025] Embodiments of the present invention solve the problem of improper funds transfer by providing a system which validates the authenticity of a payee, enables freezing of the appropriate payment account, and facilitates automatic funds transfer from the payment account to the corresponding bank account. Improper funds transfer can occur when certain information of a payee is publicly disclosed. For example, if the name and bank account number of a payee are known, a hacker can replace the payee's bank account number with the bank account number for a person with the same name as the payee. In another example, a hacker can intercept a packet that contains a bank account number for the payee and insert in a bank account number for an unauthorized person. Both of these situations may result in improper funds transfer.
[0026] The present system addresses these security issues by providing a system which acts as a third-party and provides validation of the payee's authenticity. The system generates a unique authentication identifier for the payee and provides the unique identifier to the payer. This allows the payer to transfer funds to the payee based on the unique identifier, without using the name or account number of the payee. The present system may refer to a third-party payment system provided by a third-party payment service provider, such as Alipay or Paypal. The third- party payment system which includes a payment account is coupled to a bank system which includes a bank account of the payee. As a result, the payee does not need to disclose
information (such as the payee's name and bank account number) which may be used to facilitate improper funds transfer. The system also enables a payment system to transfer funds to and freeze the payee's payment account ("payment account transfer"), run a periodic batch report, and automatically transfer all funds associated with the identifier from the payee's payment account to the payee's bank account ("bank account transfer"). The system can generate reports detailing the payments made to the payee with respect to both the payment account transfer and the subsequent automatic bank account transfer. These features aid in preventing improper funds transfer.
[0027] In some embodiments, the system can set an expiration time for the identifier and prevent the payer from transferring funds if the identifier is expired. The system can also generate a verification code that may only be used for a predetermined number of times, and send the code to the payer. In addition, the system can provide the payer with an option to enter a short description or summary of the reason for the fund transfer. The system can subsequently review the entered description and compare it against the generated reports.
[0028] FIG. 1A illustrates an exemplary computing system that facilitates secure transfer of funds, in accordance with an embodiment of the present application. In this example, system 100 can include computing devices 130, 132, and 134, which are associated with users 120, 122, and 124, respectively. Computing devices 130-134 can include, for example, a tablet, a mobile phone, an electronic reader, a laptop computer, a desktop computer, or any other computing device. Computing devices 130-134 can communicate with a transaction server 142 (e.g., a server device which provides authentication services for a financial transaction) and application servers 142 and 144 (e.g., servers or systems which manage payment accounts or bank accounts of a user) via a network 140.
[0029] During operation, user 120 interacts with corresponding computing device 130. For example, user 120 may browse to a website for a payment system or a banking system via a web browser running on mobile device 130. User 120 may indicate on device 130 a payment (e.g., a transfer of funds) to a specific payee. Based on the user information for user 120, the system can provide an authentication identifier to user 120 for use in transferring funds to the payee. In some embodiments, the payee may previously provide to the system a list of payers authorized to receive the authentication identifier. The authentication identifier can be, e.g., a digital certificate or a string of numbers of characters. The user then sends the authentication identifier and the payment amount to transaction server 142, which validates the authentication identifier. Server 142 can be a third-party which provides authentication services to users who wish to transfer funds to certain payees. Server 142 can extract from the authentication identifier the corresponding payment account and bank account of the payee. Server 142 can then initiate a transfer of the payment to the payee.
[0030] Server 142 can communicate with application server 144, which can be a system that manages the payment account of the payee ("payment server"). Application server 144 can communicate with application server 146, which can be a system that manages the bank account of the payee ("bank server"). For example, server 142 can send a message to payment server 144 to process the payment amount, which can result in payment server 144 increasing the funds of the payment account by the payment amount, and subsequently freezing the payment account, such that no changes may be made to the amount of the funds in the payment account. Payment server 144 can notify server 142 of the increase and freeze, and server 142 can generate a report which indicates the payment amount, the payee, and the authentication identifier.
[0031] At a later time (e.g., at midnight each day when server 142 is set to run its daily batch report), server 142 can search for reports associated with the authentication identifier and generate a batch number for the reports. Server 142 can send a message to payment server 144 to transfer a total payment amount associated with the batch number. Payment server 144 can transfer the funds to bank server 146, which can in turn send a confirmation message of a successful transaction. The confirmation message can also be sent to server 142. Payment server 144 can also decrease the funds of the payment account by the total payment amount, and subsequently unfreeze the payment account. Server 142 can then generate a report which indicates the total payment amount, the payee, the authentication identifier, and the batch number.
[0032] Thus, system 100 depicts a system that facilitates secure funds transfer to a payee based on a third-party which provides a unique identifier for the payee and subsequent validation for the unique identifier. The third party can also generate reports and communicate with systems which manage the payment account and bank account of the payee. [0033] FIG. IB illustrates an exemplary computing environment 150 that facilitates secure transfer of funds, in accordance with an embodiment of the present application.
Environment 150 can include user 120, a third party system 160, and a bank system 170. Third party system 160 can include a payment account 162 of a payee, and bank system 170 can include a bank account 172 of the payee. Third party system 160 and bank system 170 can be independent systems, and each of payment account 162 and bank account 172 can be associated with or belong to the respective independent system. Third party system 160 can perform the functionality described in relation to server 142 and payment server 144 of FIG. 1A, and bank system 170 can perform the functionality described in relation to bank server 146 of FIG. 1A.
General Method for Securely Transferring Funds
[0034] FIG. 2 presents a flowchart 200 illustrating a method by a transaction server for securely transferring funds, in accordance with an embodiment of the present application.
During operation, the system determines, by the transaction server, a bank account and a corresponding payment account of a payee (operation 202). The server authenticates the bank account and the payment account of the payee (operation 204). The server generates an authentication identifier for the payee, where the authentication identifier indicates the bank account and the payment account of the payee (operation 206). The authentication identifier is a unique identifier which can be, e.g., a digital certificate or a string of numbers, and can indicate or correspond to the payment account and the bank account. Subsequently, the server receives, from a payer that is a user of a client computing device, a message which indicates a first command to transfer a payment amount to the payee (operation 208). The first command indicates the authentication identifier. As described above in relation to FIG. 1, the payer, in possession of the authentication identifier, can send the identifier and the payment amount in the command to transfer funds to the payee.
[0035] The server verifies the authentication identifier (decision 210). In some instances, the verification includes checking whether an expiration time for the authentication identifier has been reached. In some instances, the verification includes checking whether the authentication identifier sent by the payer successfully matches the authentication identifier generated for the payee. If the server does not successfully verify the identifier, the operation returns. If the server does successfully verify the identifier, the server extracts information associated with the payment account and the bank account from the authentication identifier (operation 212). For example, the server can extract the account number or other identifier for the payment account and the bank account. Finally, the server transfers the payment amount to the bank account of the payee based on the extracted information (operation 214). Operation 214 can include the operations described below in FIGs. 3, 4A, and 4B.
Server Communication with Payment System to Transfer Funds
[0036] FIG. 3 presents a flowchart 300 illustrating a method by a transaction server for securely transferring funds, including interaction with a payment system, in accordance with an embodiment of the present application. During operation, the system transmits, by the transaction server, a message which indicates a second command to increase funds in the payment account and to freeze the payment account (operation 302). The system increases, by a payment system which manages the payment account of the payee, the funds in the payment account by the payment amount, and freezes the payment account (operation 304).
Subsequently, the server receives from the payment system a confirmation message which indicates a completion of the second command (operation 306). The server stores in a database a report which indicates the payment amount, the payee, and the authentication identifier
(operation 308).
[0037] FIG. 4A presents a flowchart 400 illustrating a method by a transaction server for summarizing and processing a secure transfer of funds, including interaction with a payment system, in accordance with an embodiment of the present application. During operation, the server performs a search in a database for one or more reports which include an authentication identifier, based on a predetermined date or time period (operation 402). A report includes a payment amount, and the predetermined date or time period can be, e.g., a 24-hour period for a certain date. The server calculates a total payment amount for the one or more reports based on the payment amount included in each report in the search result (operation 404). The server generates a batch number for the one or more reports (operation 406). The server transmits a message which indicates a third command to transfer the total payment amount from the payment account of the payee to the bank account of the payee (operation 408). The third command also includes instructions to unfreeze the payment account and to deduct the total payment amount from the funds of the payment account. The operation then continues as described at Label A of FIG. 4B (e.g., a method performed by the payment system). In response to receiving a confirmation message which indicates a completion of the third command, the server updates in a database a report which includes the total payment amount, the payee, the authentication identifier, and the batch number (operation 410).
[0038] FIG. 4B presents a flowchart 450 illustrating a method by a payment system for processing a secure transfer of funds, in accordance with an embodiment of the present application. In response to receiving the third command, a payment system which manages the payment account of the payee generates a message which indicates a fourth command to transfer the total payment amount from the payment account to the bank account of the payee (operation 452). The payment system authenticates the bank account of the payee (operation 454). Upon authenticating the bank account of the payee, the payment system unfreezes the payment account of the payee (operation 456) and deducts the total payment amount from the funds of the payment account (operation 458). Finally, the payment system transmits to the server a confirmation message which indicates a completion of the third command (operation 460).
Exemplary Apparatus and Computer System
[0039] FIG. 5 illustrates an exemplary apparatus 500 that facilitates secure transfer of funds, in accordance with an embodiment of the present application. Apparatus 500 can comprise a plurality of modules which may communicate with one another via a wired or wireless communication channel. Apparatus 500 may be realized using one or more integrated circuits, and may include fewer or more modules than those shown in FIG. 5. Further, apparatus 500 may be integrated in a computer system, or realized as a separate device which is capable of communicating with other computer systems and/or devices. Specifically, apparatus 500 can comprise a communication module 502, an authentication identifier- generating module 504, an authentication identifier-processing module 506, a funds-transferring module 508, a reporting module 510, and a payment system-processing module 512.
[0040] In some embodiments, communication module 502 can send and/or receive data packets to/from other network nodes across a computer network, where a data packet can correspond to a first command to transfer a payment amount to a payee. Authentication identifier-generating module 504 can generate an authentication identifier for a payee of a bank account, where the authentication identifier indicates the bank account and a corresponding payment account of the payee. The authentication identifier can be a first authentication identifier associated with the payment account of the payee or associated with the bank account of the payee.
[0041] In response to successfully verifying the authentication identifier, authentication identifier-processing module 506 can extract information associated with the payment account and the bank account from the authentication identifier. Funds-transferring module 508 can transfer the payment amount to the bank account of the payee based on the extracted information. In addition, authentication identifier-generating module 504 can determine the bank account and corresponding payment account of the payee. Authentication identifier-processing module 506 can authenticate the bank account and payment account of the payee. Communication module 502 can also receive a request to transfer a payment amount to the payee, where the request includes a second authentication identifier. Authentication identifier-processing module 506 can successfully match the second authentication identifier to the first authentication identifier.
Authentication identifier-processing module 506 can extract the payment account based on the first authentication identifier, and extract the coupled bank account of the payee.
[0042] Communication module 502 can transmit a message which indicates a second command to increase funds in the payment account by the payment amount and to freeze the payment account. Payment system-processing module 512 can increase the funds in the payment account by the payment amount and freeze the payment account.
[0043] Reporting module 510 can store in a database a report which includes the payment amount, the payee, and the authentication identifier. Reporting module 510 can also perform a search in the database for one or more reports which include the authentication identifier, based on a predetermined date or time period, wherein a report includes a payment amount. Reporting module 510 can calculate a total payment amount for the one or more reports, and generate a batch number for the one or more reports.
[0044] Communication module 502 can transmit a message which indicates a third command to transfer the total payment amount from the payment account of the payee to the bank account of the payee, to unfreeze the payment account, and to deduct the total payment amount from the funds of the payment account. Payment system-processing module 512 can authenticate the bank account of the payee, unfreeze the payment account, decrease the funds in the payment account by the total payment amount, and transmit a message which indicates a completion of the third command. In response to receiving a confirmation message which indicates a completion of the third command, reporting module 510 can update in a database a report which includes the total payment amount, the payee, the authentication identifier, and the batch number. Communication module 502 can receive a confirmation message which indicates a completion of the third command.
[0045] FIG. 6 illustrates an exemplary computer system 602 that facilitates control of the display direction of content on a device, in accordance with an embodiment of the present application. Computer system 602 includes a processor 604, a memory 606, and a storage device 608. Memory 606 can include a volatile memory (e.g., RAM) that serves as a managed memory, and can be used to store one or more memory pools. Furthermore, computer system 602 can be coupled to a display device 610, a keyboard 612, and a pointing device 614. Storage device 608 can store an operating system 616, a content-processing system 618, and data 632.
[0046] Content-processing system 618 can include instructions, which when executed by computer system 602, can cause computer system 602 to perform methods and/or processes described in this disclosure. Specifically, content-processing system 618 may include instructions for sending and/or receiving data packets to/from other network nodes across a computer network, where a data packet can correspond to a first command to transfer a payment amount to a payee (communication module 620). Content-processing system 618 can include instructions for generating an authentication identifier for a payee of a bank account, where the authentication identifier indicates the bank account and a corresponding payment account of the payee (authentication identifier- generating module 622). The authentication identifier can be a first authentication identifier associated with the payment account of the payee or associated with the bank account of the payee.
[0047] Content-processing system 618 can also include instructions for, in response to successfully verifying the authentication identifier, extracting information associated with the payment account and the bank account from the authentication identifier (authentication identifier-processing module 624). Content-processing system 618 can include instructions for transferring the payment amount to the bank account of the payee based on the extracted information (funds-transferring module 626). Content-processing system 618 can include instructions for determining the bank account and corresponding payment account of the payee (authentication identifier- generating module 622) and for authenticating the bank account and payment account of the payee (authentication identifier-processing module 624). Content- processing system 618 can further include instructions for receiving a request to transfer a payment amount to the payee, where the request includes a second authentication identifier (communication module 620). Content-processing system 618 can include instructions for successfully matching the second authentication identifier to the first authentication identifier (authentication identifier-processing module 624). Content-processing system 618 can also include instructions for extracting the payment account based on the first authentication identifier, and for extracting the coupled bank account of the payee (authentication identifier- processing module 624).
[0048] Content-processing system 618 can additionally include instructions for transmitting a message which indicates a second command to increase funds in the payment account by the payment amount and to freeze the payment account (communication module 620). Content-processing system 618 can include instructions for increasing the funds in the payment account by the payment amount and freeze the payment account (payment system-processing module 630).
[0049] Content-processing system 618 can include instructions for storing in a database a report which includes the payment amount, the payee, and the authentication identifier, and for performing a search in the database for one or more reports which include the authentication identifier, based on a predetermined date or time period, where a report includes a payment amount (reporting module 628). Content-processing system 618 can include instructions for calculating a total payment amount for the one or more reports, and for generating a batch number for the one or more reports (reporting module 628).
[0050] Additionally, content-processing system 618 can include instructions for transmitting a message which indicates a third command to transfer the total payment amount from the payment account of the payee to the bank account of the payee, to unfreeze the payment account, and to deduct the total payment amount from the funds of the payment account
(communication module 620). Content-processing system 618 can include instructions for authenticating the bank account of the payee, unfreezing the payment account, decreasing the funds in the payment account by the total payment amount, and transmitting a message which indicates a completion of the third command (payment system-processing module 6300.
Content-processing system 618 can include instructions for, in response to receiving a confirmation message which indicates a completion of the third command, updating in a database a report which includes the total payment amount, the payee, the authentication identifier, and the batch number (reporting module 628). Content-processing system 618 can include instructions for receiving a confirmation message which indicates a completion of the third command (communication module 620).
[0051] Data 632 can include any data that is required as input or that is generated as output by the methods and/or processes described in this disclosure. Specifically, data 632 can store at least: an authentication identifier; information which indicates a payment account and a corresponding bank account; one or more commands; a payment amount; information indicating a payer and a payee; one or more reports that indicate a payment amount, a payee, an
authentication identifier, and a total payment amount; a total payment amount; information to communicate with a system which manages a payment account and/or a bank account of a payee; and a database that stores one or more reports.
[0052] The data structures and code described in this detailed description are typically stored on a computer-readable storage medium, which may be any device or medium that can store code and/or data for use by a computer system. The computer-readable storage medium includes, but is not limited to, volatile memory, non-volatile memory, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs), DVDs (digital versatile discs or digital video discs), or other media capable of storing computer-readable media now known or later developed.
[0053] The methods and processes described in the detailed description section can be embodied as code and/or data, which can be stored in a computer-readable storage medium as described above. When a computer system reads and executes the code and/or data stored on the computer-readable storage medium, the computer system performs the methods and processes embodied as data structures and code and stored within the computer-readable storage medium.
[0054] Furthermore, the methods and processes described above can be included in hardware modules. For example, the hardware modules can include, but are not limited to, application-specific integrated circuit (ASIC) chips, field-programmable gate arrays (FPGAs), and other programmable-logic devices now known or later developed. When the hardware modules are activated, the hardware modules perform the methods and processes included within the hardware modules.
[0055] The foregoing descriptions of embodiments of the present invention have been presented for purposes of illustration and description only. They are not intended to be exhaustive or to limit the present invention to the forms disclosed. Accordingly, many modifications and variations will be apparent to practitioners skilled in the art. Additionally, the above disclosure is not intended to limit the present invention. The scope of the present invention is defined by the appended claims.

Claims

What Is Claimed Is:
1. A computer system for securely transferring funds to a payee, the system comprising:
a processor; and
a memory coupled to the processor and storing instructions, which when executed by the processor cause the processor to perform a method, the method comprising:
generating, by a server, an authentication identifier for a payee of a bank account, wherein the authentication identifier indicates the bank account and a corresponding payment account of the payee;
receiving, from a payer, a message which indicates a first command to transfer a payment amount to the payee, wherein the first command includes the authentication identifier;
in response to successfully verifying the authentication identifier, extracting information associated with the payment account and the bank account from the authentication identifier; and
transferring the payment amount to the bank account of the payee based on the extracted information.
2. The computer system of claim 1, wherein generating the authentication identifier comprises:
determining the bank account and the corresponding payment account of the payee; and authenticating the bank account and the payment account of the payee.
3. The computer system of claim 1, wherein transferring the payment amount to the bank account of the payee further comprises:
transmitting one or more messages to a payment system which manages the payment account for the payee, wherein the payment system communicates with a banking system which manages the bank account for the payee.
4. The computer system of claim 1, wherein transferring the payment amount to the bank account of the payee further comprises:
transmitting a message which indicates a second command to increase funds in the payment account by the payment amount and to freeze the payment account.
5. The computer system of claim 4, wherein in response to receiving the second message, the method further comprises:
increasing, by a payment system which manages the payment account of the payee, the funds in the payment account by the payment amount; and
freezing the payment account.
6. The computer system of claim 4, wherein the method further comprises:
in response to receiving a confirmation message which indicates a completion of the second command, storing in a database a report which includes the payment amount, the payee, and the authentication identifier.
7. The computer system of claim 1, wherein transferring the payment amount to the bank account of the payee further comprises:
performing a search in the database for one or more reports which include the
authentication identifier, based on a predetermined date or time period, wherein a report includes a payment amount;
calculating a total payment amount for the one or more reports;
generating a batch number for the one or more reports; and
transmitting a message which indicates a third command to transfer the total payment amount from the payment account of the payee to the bank account of the payee, to unfreeze the payment account, and to deduct the total payment amount from the funds of the payment account.
8. The computer system of claim 7, wherein the method further comprises:
in response to receiving a confirmation message which indicates a completion of the third command, updating in a database a report which includes the total payment amount, the payee, the authentication identifier, and the batch number.
9. The computer system of claim 7, wherein in response to receiving the third command, the method further comprises:
generating, by a payment system which manages the payment account of the payee, a message which indicates a fourth command to transfer the total payment amount from the payment account to the bank account of the payee;
unfreezing the payment account;
deducting the total payment account from the funds of the payment account; and transmitting a confirmation message to the server which indicates a completion of the third command.
10. The computer system of claim 7, wherein generating the fourth command further comprises:
authenticating, by the payment system, the bank account of the payee.
11. A computer-implemented method for securely transferring funds to a payee, the method comprising:
generating, by a server, an authentication identifier for a payee of a bank account, wherein the authentication identifier indicates the bank account and a corresponding payment account of the payee;
receiving, from a payer, a message which indicates a first command to transfer a payment amount to the payee, wherein the first command includes the authentication identifier;
in response to successfully verifying the authentication identifier, extracting information associated with the payment account and the bank account from the authentication identifier; and transferring the payment amount to the bank account of the payee based on the extracted information.
12. The method of claim 11, wherein generating the authentication identifier comprises:
determining the bank account and the corresponding payment account of the payee; and authenticating the bank account and the payment account of the payee.
13. The method of claim 11, wherein transferring the payment amount to the bank account of the payee further comprises:
transmitting one or more messages to a payment system which manages the payment account for the payee, wherein the payment system communicates with a banking system which manages the bank account for the payee.
14. The method of claim 11, wherein transferring the payment amount to the bank account of the payee further comprises:
transmitting a message which indicates a second command to increase funds in the payment account by the payment amount and to freeze the payment account.
15. The method of claim 14, wherein in response to receiving the second message, the method further comprises:
increasing, by a payment system which manages the payment account of the payee, the funds in the payment account by the payment amount; and
freezing the payment account.
16. The method of claim 14, further comprising:
in response to receiving a confirmation message which indicates a completion of the second command, storing in a database a report which includes the payment amount, the payee, and the authentication identifier.
17. The method of claim 11, wherein transferring the payment amount to the bank account of the payee further comprises:
performing a search in the database for one or more reports which include the
authentication identifier, based on a predetermined date or time period, wherein a report includes a payment amount;
calculating a total payment amount for the one or more reports;
generating a batch number for the one or more reports; and
transmitting a message which indicates a third command to transfer the total payment amount from the payment account of the payee to the bank account of the payee, to unfreeze the payment account, and to deduct the total payment amount from the funds of the payment account.
18. The method of claim 17, further comprising:
in response to receiving a confirmation message which indicates a completion of the third command, updating in a database a report which includes the total payment amount, the payee, the authentication identifier, and the batch number.
19. The method of claim 17, wherein in response to receiving the third command, the method further comprises:
generating, by a payment system which manages the payment account of the payee, a message which indicates a fourth command to transfer the total payment amount from the payment account to the bank account of the payee;
unfreezing the payment account;
deducting the total payment account from the funds of the payment account; and transmitting a confirmation message to the server which indicates a completion of the third command.
20. The method of claim 17, wherein generating the fourth command further comprises:
authenticating, by the payment system, the bank account of the payee.
21. A computer system for securely transferring funds to a payee, the system comprising:
a processor; and
a memory coupled to the processor and storing instructions, which when executed by the processor cause the processor to perform a method, the method comprising:
generating, by a server, a first authentication identifier for a payee, wherein the first authentication identifier is associated with a payment account of the payee and stored in the server;
receiving, from a payer, a request to transfer a payment amount to the payee, wherein the request includes a second authentication identifier;
upon successfully matching the second authentication identifier with the first authentication identifier, by the server, extracting the payment account based on the first authentication identifier; and
transferring the payment amount to the payment account of the payee.
22. A computer system for securely transferring funds to a payee having a bank account at a bank system and a payment account at a third party system, the computer system comprising:
a processor; and
a memory coupled to the processor and storing instructions, which when executed by the processor cause the processor to perform a method, the method comprising:
providing that the payment account of the payee at the third party system is coupled to the bank account of the payee at the bank system;
generating a first authentication identifier for the payee at the third party system, wherein the first authentication identifier is associated with the bank account of the payee and stored in the third party system;
receiving from a payer, a request to transfer a payment amount to the payee, wherein the request includes a second authentication identifier; upon successfully matching the second authentication identifier with the first authentication identifier at the third party system, extracting the coupled bank account of the payee at the bank system; and
transferring the payment amount to the bank account of the payee.
PCT/US2015/063028 2014-12-03 2015-11-30 System and method for secure account transfer Ceased WO2016089783A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2017522509A JP2018501541A (en) 2014-12-03 2015-11-30 System and method for secure direct debit
SG11201703418PA SG11201703418PA (en) 2014-12-03 2015-11-30 System and method for secure account transfer
KR1020177014907A KR20170085059A (en) 2014-12-03 2015-11-30 System and method for secure account transfer

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201410727542.9 2014-12-03
CN201410727542.9A CN105719183A (en) 2014-12-03 2014-12-03 Directional transfer method and apparatus
US14/952,373 2015-11-25
US14/952,373 US10755345B2 (en) 2014-12-03 2015-11-25 System and method for secure account transfer

Publications (1)

Publication Number Publication Date
WO2016089783A1 true WO2016089783A1 (en) 2016-06-09

Family

ID=56092297

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/063028 Ceased WO2016089783A1 (en) 2014-12-03 2015-11-30 System and method for secure account transfer

Country Status (1)

Country Link
WO (1) WO2016089783A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109767334A (en) * 2018-12-14 2019-05-17 深圳壹账通智能科技有限公司 Fund application processing method, device, computer equipment and storage medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040139008A1 (en) * 2003-01-10 2004-07-15 First Data Corporation Payment system clearing for transactions
US20080097805A1 (en) * 2006-10-23 2008-04-24 Wells R Scott Transaction processing method
US7734527B2 (en) * 2000-08-29 2010-06-08 Uzo Chijioke Chukwuemeka Method and apparatus for making secure electronic payments
US20110184840A1 (en) * 2010-01-27 2011-07-28 Ebay Inc. Systems and methods for facilitating account verification over a network
US20140310171A1 (en) * 2013-04-12 2014-10-16 Bank Of America Corporation Certified person-to-person payment system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7734527B2 (en) * 2000-08-29 2010-06-08 Uzo Chijioke Chukwuemeka Method and apparatus for making secure electronic payments
US20040139008A1 (en) * 2003-01-10 2004-07-15 First Data Corporation Payment system clearing for transactions
US20080097805A1 (en) * 2006-10-23 2008-04-24 Wells R Scott Transaction processing method
US20110184840A1 (en) * 2010-01-27 2011-07-28 Ebay Inc. Systems and methods for facilitating account verification over a network
US20140310171A1 (en) * 2013-04-12 2014-10-16 Bank Of America Corporation Certified person-to-person payment system

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109767334A (en) * 2018-12-14 2019-05-17 深圳壹账通智能科技有限公司 Fund application processing method, device, computer equipment and storage medium

Similar Documents

Publication Publication Date Title
US12244729B2 (en) Systems and methods for creating a universal record
US10755345B2 (en) System and method for secure account transfer
US11210661B2 (en) Method for providing payment gateway service using UTXO-based protocol and server using same
US11392940B2 (en) Multi-approval system using M of N keys to perform an action at a customer device
US11080713B2 (en) System and method for authenticating a transaction
EP3665857B1 (en) Blockchain architecture with record security
AU2017206119B2 (en) Systems and methods for device push provisioning
US8285640B2 (en) System and methods for facilitating fund transfers over a network
US12301580B2 (en) Efficient and secure authentication system
US20180330342A1 (en) Digital asset account management
CN116802661A (en) Token-based out-of-chain interaction authorization
CN111819555A (en) Secure remote token issuance with online authentication
US20240297790A1 (en) Efficient token provisioning system and method
CN113196704A (en) Techniques for securely performing offline authentication
US20250307804A1 (en) Delegated certificate authority system and method
US20200372494A1 (en) Transferring Funds Between Wallet Client Accounts
US20230316275A1 (en) Systems and methods for token-based device binding during merchant checkout
US20140258120A1 (en) Systems and methods for debit card account confirmation
US12309139B2 (en) Passcode authentication using a wallet card
WO2016089783A1 (en) System and method for secure account transfer
US20250111369A1 (en) Systems and methods for account mapping and personal account number linking
CN121444386A (en) On-chain processing of off-chain interactions

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: 15865997

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017522509

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 11201703418P

Country of ref document: SG

ENP Entry into the national phase

Ref document number: 20177014907

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15865997

Country of ref document: EP

Kind code of ref document: A1