Alias management and value transfer claim processing

• US 10,417,619 B2
• Filed: 11/19/2012
• Issued: 09/17/2019
• Est. Priority Date: 04/19/2010
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Raj, Thanigaivel Ashwin, Fuentes, Jacob Saul, Tullis, John, Shastry, Vishwanath
• Primary Examiner(s): Niquette, Robert R
• Application Number:
  US13/681,220
• Publication Number:
  US 20130179335A1
• Time in Patent Office: 2,493 Days
• Field of Search: None
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

An alias management and value transfer claim processing system is disclosed. A sending entity initiates value transfer identifying a recipient entity using an alias that is unregistered with the system. The value transfer is authorized, but not settled until the recipient entity registers with the system and claims the value transfer. The registered alias can be used for subsequent value transfers.

Claims

1. A method for transferring value from a sending entity to a recipient entity, the method comprising:

receiving, by a sending entity issuer computer, a first message from a server computer of a payment processing network, the first message instructing the sending entity issuer computer to reserve an amount of funds for a recipient entity identified by a recipient entity alias, wherein the amount of funds corresponds to a transfer amount indicated by a request to transfer value, the request including the recipient entity alias and a sending entity identifier of a sending entity, wherein the first message is received by the sending entity issuer computer based on a determination that the recipient entity alias is not registered with the payment processing network, wherein a registration request message is sent by the server computer of the payment processing network to the recipient entity associated with the recipient entity alias based on the determination, and wherein the registration request message includes a request for the recipient entity to register with the payment processing network;

responsive to the first message received from the server computer, determining, as a function of a number of transactions and amounts of the number of transactions from the sending entity or to the recipient entity within a given time period, a transaction velocity;

determining, by the sending entity issuer computer, if the transaction velocity exceeds a velocity threshold;

responsive to determining that the transaction velocity exceeds a velocity threshold, declining the request;

responsive to determining that the transaction velocity does not exceed a velocity threshold, reserving, by the sending entity issuer computer, the amount of funds corresponding to the transfer amount, the amount of funds being reserved in a source account of the sending entity identified by the sending entity identifier;

determining, based on a second message received from the server computer of the payment processing network, whether the server computer received a response, from the recipient entity, to the registration request message for registration of the recipient entity with the payment processing network;

upon determining that the server computer did not receive the response to the registration request message, removing a reservation of the reserved amount of funds in the source account;

upon determining that the server computer received the response to the registration request, debiting, by the sending entity issuer computer, the reserved amount of funds; and

sending a confirmation message to the server computer, the confirmation message indicating that the reserved amount of funds have been debited.

2. The method of claim 1 wherein the recipient entity is not registered with the payment processing network when the recipient entity alias is not stored in association with the recipient entity by the server computer of the payment processing network.

3. The method of claim 1 wherein the recipient entity alias corresponds to contact information for the recipient entity, and wherein the contact information includes an email address associated with the recipient entity or a phone number associated with the recipient entity.

4. The method of claim 1 wherein the reservation corresponding to the reserved amount of funds is removed upon determining that the server computer does not receive, from the recipient entity, the response to the registration request message within a pre-determined amount of time.

5. The method of claim 1 wherein the second message is a debit message that received from the server computer of the payment processing network in response to the server computer receiving, from the recipient entity, the response to the registration request message.

6. A system comprising:

one or more processors; and

one or more memory devices coupled to the one or more processors, the one or more memory devices comprising instructions executable by the one or more processors to perform a method comprising;

receiving a first message from a server computer of a payment processing network, the first message instructing a sending entity issuer computer to reserve an amount of funds for a recipient entity identified by a recipient entity alias, wherein the amount of funds corresponds to a transfer amount indicated by a request to transfer value, and the request including the recipient entity alias and a sending entity identifier of a sending entity, wherein the first message is received by the sending entity issuer computer based on a determination that the recipient entity alias is not registered with the payment processing network, wherein a registration request message is sent by the server computer of the payment processing network to the recipient entity associated with the recipient entity alias based on the determination, and wherein the registration request message includes a request for the recipient entity to register with the payment processing network;

responsive to the first message received from the server computer, determining, as a function of a number of transactions and amounts of the number of transactions from the sending entity or to the recipient entity within a given time period, a transaction velocity;

determining if the transaction velocity exceeds a velocity threshold;

responsive to determining that the transaction velocity exceeds a velocity threshold, declining the request;

responsive to determining that the transaction velocity does not exceed a velocity threshold, reserving the amount of funds corresponding to the transfer amount, the amount of funds being reserved in a source account of the sending entity identified by the sending entity identifier;

determining, based on a second message received from the server computer of the payment processing network, whether the server computer received a response, from the recipient entity, to the registration request message for registration of the recipient entity with the payment processing network;

upon determining that the server computer did not receive the response to the registration request message, removing a reservation of the reserved amount of funds in the source account; and

upon determining that the server computer received the response to the registration request, debiting the reserved amount of funds and sending a confirmation message to the server computer.

7. The system of claim 6 wherein the source account of the sending entity is managed by the sending entity issuer computer.

8. The system of claim 6 wherein the determination that the recipient entity alias is not registered with the payment processing network is based on determining that the recipient entity alias is not stored in association with the recipient entity by the server computer of the payment processing network.

9. The system of claim 6 wherein the reservation corresponding to the reserved amount of funds is removed upon determining that the server computer of the payment processing network does not receive, from the recipient entity, the response to the registration request message within a pre-determined amount of time.

10. The system of claim 6 wherein the second message is a debit message that received from the server computer of the payment processing network in response to the server computer receiving, from the recipient entity, the response to the registration request message.

11. A system comprising:

a sending entity issuer computer configured to;

receive a first message from a server computer of a payment processing network, the first message instructing the sending entity issuer computer to reserve an amount of funds for a recipient entity identified by a recipient entity alias, wherein the amount of funds corresponds to a transfer amount indicating by a request to transfer value, the request including the recipient entity alias and a sending entity identifier of a sending entity, wherein the first message is received by the sending entity issuer computer based on a determination that the recipient entity alias is not registered with the payment processing network and based on a determination that the server computer has received, from the sending entity, an approval message indicating approval to transfer the amount of funds to the recipient entity;

responsive to the first message received from the server computer, determine, as a function of a number of transactions and amounts of the number of transactions from the sending entity or to the recipient entity within a given time period, a transaction velocity;

determine if the transaction velocity exceeds a velocity threshold;

responsive to determining that the transaction velocity exceeds a velocity threshold, decline the request;

responsive to determining that the transaction velocity does not exceed a velocity threshold, reserve the amount of funds corresponding to the transfer amount;

receive a debit message from the server computer, the debit message instructing the sending entity issuer computer to debit the reserved amount of funds;

in response to the debit message, debit the reserved amount of funds; and

send a confirmation message to the server computer, the confirmation message indicating that the reserved amount of funds has been debited; and

a client computer associated with the sending entity, the client computer configured to;

send, to the server computer of the payment processing network, the request to transfer value the amount of funds to the recipient entity;

receive a second message indicating that the recipient entity is not registered with the payment processing network; and

in response to receiving the second message indicating that the recipient entity is not registered with the payment processing network, send, to the server computer of the payment processing network, the approval message indicating approval to transfer the amount of funds to the recipient entity.