# US 7,610,222 B2 · Method for providing a money transfer service through a payment enabler system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 7,610,222 B2
- Document ID: US7610222B2
- Status: Granted
- Kind: B2
- Application number: 11/928,315
- Filed: 2007-10-30
- Published: 2008-04-24
- Granted: 2009-10-27
- Earliest claimed: 2000-07-11
- Assignees: First Data Corporation
- Inventors: Cheryl L. Neofytides; Aamer Ali Baig
- Web page: https://patentgrep.com/patent/US7610222B2

## CPC

- G06Q 30/06: Buying, selling or leasing transactions
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 20/04: Payment circuits
- G06Q 20/10: specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q 20/102: {Bill distribution or payments}
- G06Q 20/1085: {involving automatic teller machines [ATMs]}
- G06Q 20/40: Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q 30/0609: {Qualifying participants for shopping transactions (payment transaction verification G06Q20/401)}
- G06Q 30/0613: {using intermediate agents}
- G06Q 30/0615: {Anonymizing}
- G06Q 30/0619: {Neutral agent}
- G06Q 40/04: Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
- 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

## Abstract

A method for processing person-to-person payments and money requests using a computer network. A payment enabler linked to the Internet enables an individual to register for an account through which the individual can make payments to other individuals, request money from other individuals, and access other functionality to facilitate the management of the individual's financial transactions. At the time an individual authorizes a payment to another person or directs the payment enabler to request money from another person, the person to whom the payment or money request is directed may, but need not, have already registered for an account with the payment enabler. To communicate with individuals, the payment enabler may use both Web pages and e-mail. An intermediary typically operates the payment enabler and acts as a conduit for the money transfer from one individual (the payor) to another individual (the payee). This enables the payor to pay through a variety of different payment methods and the payee to receive payment through a variety of different methods. Individuals may make payments from and receive money transfers into a stored value account. In addition to initiating immediate money transfer and request money transactions, an individual may use the payment enabler to schedule future or recurring transactions. Address book functionality may provide users the ability to retain information on counter parties. The address book may be integrated into the money transfer and money request interfaces to allow an individual to quickly select the counter party for a transaction.

## Claims

### Claim 1

A computer implemented method for providing a money transfer service between a first party and a second party through a payment enabler system, comprising:
maintaining, on a memory storage device at the payment enabler system, a database of registered users that have registered with the payment enabler system, the registered users database comprising a plurality of records that include an email address and other account information including a default payment method and a default money receiving method;
maintaining, on a memory storage device at the payment enabler system, an address book database for storing address book records on behalf of a first party comprising names associated with second parties with whom the first party may initiate a money transfer, each address book record including a name and an associated email address provided by the first party;
in response to selection by the first party of an entry in the address book database of a particular second party for purposes of initiating a money transfer with the selected second party, retrieving, via a processing unit, the email address associated with the selected second party from the first party's associated address book records in the address book database; accessing the registered users database and determining whether the retrieved email address associated with the selected particular second party has a record in the registered users database;
in response to a determination that the second party has no entry in the registered users database, sending, via a processing unit, the second party a registration invitation email utilizing the retrieved email address to notify the second party that a transaction is pending and instructing the second party to register with the payment enabler system by accessing the payment enabler system;
in response to accessing of the payment enabler system by the second party after the registration invitation email, conducting a user registration process comprising: receiving, via a processing unit, registration information comprising an email address of the registering user, identification information, and a default money transfer method;
in response to receiving registration information from a registering user, creating a database record in the registered users database including the registration information; and completing the transaction between the first party and the second party by the payment enabler transferring money between the first party and the second party utilizing a determined money transfer method.

### Claim 2 (depends on 1)

The method of claim 1, wherein the record in the registered users database includes security information provided by a first party association with a selected second party; and the completing the transaction is carried out in response to registration by the second party and provision of corresponding expected security response information from the second party.

### Claim 3 (depends on 2)

The method of claim 2, wherein the security information provided by the first party is a question and the corresponding expected security response information from the second party comprises an expected answer.

### Claim 4 (depends on 2)

The method of claim 2, wherein the user registration process further comprises:
receiving the security information provided by the first party; in further response to accessing the payment enabler system by the second party, providing a question corresponding to the security information to the registering user;
comparing a received response from the registering user to the corresponding expected security response information; and
completing the transaction only if the received response matches the expected security response information.

### Claim 5 (depends on 1)

The method of claim 1, wherein the transaction comprises a payment from the first party to the second party.

### Claim 6 (depends on 1)

The method of claim 1, wherein the transaction comprises a request for a payment from the second party to the first party.

### Claim 7 (depends on 1)

The method of claim 1, further comprising: in response to determination that a second party already has an entry in the registered users database, completing the transaction between the first party and the second party.

### Claim 8

The method of 1, wherein the registration invitation email sent to the second party by the payment enabler system includes a link that directs the second party to a registration web page associated with the payment enabler system.

### Claim 9 (depends on 1)

The method of claim 1, wherein the transaction is a payment from the first party to the second party, and wherein in further response to a determination that a second party has no entry in the registered users database, obtaining authenticating information from the first party prior to sending the registration invitation email, and storing the authenticating information in the registered users database in anticipation of registration by the second party.

### Claim 10 (depends on 9)

The method of claim 9, wherein the authenticating information comprises a question to be asked of the registering user and an expected answer.

### Claim 11 (depends on 1)

The method of claim 1, wherein the user registration process comprises: allowing the registering user to select a default payment method from a plurality of payment methods, and a default money receiving method from a plurality of money receiving methods.

### Claim 12 (depends on 1)

The method of claim 1, wherein the user registration process further comprises: sending a registering user a confirmation email including a deep link operative for activating an account of the registering user with the payment enabler system.

### Claim 13 (depends on 1)

The method of claim 1, wherein the determined money transfer method comprises the default method for either making payment or receiving money.

### Claim 14 (depends on 1)

The method of claim 1, wherein the determined money transfer method comprises a selected alternate payment method instead of a default payment method.

### Claim 15 (depends on 1)

The method of claim 1, wherein the determined money transfer method comprises a selected alternate money receiving method instead of a default money receiving method.

### Claim 16 (depends on 1)

The method of claim 1, further comprising: storing additional information associated with a money transfer, the additional information including transaction type information and status information.

### Claim 17 (depends on 16)

The method of claim 16, wherein the transaction type information is selected from the following: send, request, refund.

### Claim 18 (depends on 16)

The method of claim 16, wherein the status information is selected from the group: fulfilled, canceled, pending.

### Claim 19 (depends on 16)

The method of claim 16, further comprising: providing an account history display including information corresponding to money transfers between a first party and a plurality of second parties, the account history display comprising, for each money transfer transaction, one or more of the following information items: a name, a reference number associated with the payment enabler system, an email address, an amount, a date, a transaction description, and the additional information.

### Claim 20 (depends on 1)

The method of claim 1, further comprising: providing an address book display for a party to select one or more particular second parties, the address book display comprising, for an address book record in the address book database, one or more of the following information items: a selection box for selection, a name, all email address, and a number of transactions associated with the particular party.

### Claim 21 (depends on 1)

The method of claim 1, wherein the money transfer method comprises: steps a first money transfer from a payor to an intermediary and a second money transfer from the intermediary to a payee.

### Claim 22 (depends on 21)

The method of claim 21, wherein the first money transfer is selected from the group: receiving deposit of an amount of cash by the payor via a payment processor, debiting a credit card of the payor, debiting a bank account of the payor, debiting a stored value account of the payor, and receiving a paper check from the payor.

### Claim 23 (depends on 21)

The method of claim 21, wherein the second money transfer is selected from the group: debiting a bank account of the intermediary to fund dispensing of cash to the payee through an automated teller machine, dispensing cash to the payee by a payment processor, crediting a credit card of the payee, crediting a bank account of the payee, crediting a stored value card of the payee, and sending a paper check to the payee.