US 7,617,157 B2Grant
Method for receiving electronically transferred funds using an automated teller machine
Issue Date:2009-11-10
•39 Claims
•4 Drawing Sheets
Abstract
A method for performing a money transfer receive transaction involving a desired amount of money to be transferred from a sender to a recipient includes receiving transaction identifying information provided by the recipient; comparing the transaction identifying information with transaction data stored on a host computer system; providing a confirmation code, to be issued to the recipient, if the transaction identifying information matches the transaction data stored on the host computer system; storing the confirmation code on the host computer system; receiving at the host computer system input corresponding to the confirmation code from a dispensing terminal in communication with the host computer system; comparing the input to the stored confirmation code; and allowing funds, corresponding to at least a portion of the desired amount of money, to be dispensed by the dispensing terminal if the input matches the stored confirmation code.
Metadata
Assignee
- The Western Union Company
Inventors
- Dean A. Seifert
- Earney E. Stoutenburg
Application Information
Application Number:US 10/037,827
Filing Date:2002-01-03
Priority Date:2002-01-03
Art Unit:3693
Classifications
IPC:
G06Q40/00
Patent Drawings (4 sheets)
Description
Background of the Invention
[0001] 1. Field of the Invention
[0002] The invention relates to a method of performing money transfer receive transactions.
[0003] 2. Background Art
[0004] A money transfer transaction performed with a financial services institution may include a money transfer send transaction, or send transaction, and a money transfer receive transaction, or receive transaction. Under a send transaction, a sender sends or “wires” money to a recipient through the financial services institution. Under a receive transaction, the recipient receives money through the financial services institution. Many such transactions are also facilitated by businesses, organizations or other entities that act as agents of the financial services institution.
[0005] Various methods are known for performing send transactions. One known method, for example, involves a sender completing a transaction form and providing the form to an agent. The transaction form includes such information as the desired amount of money to be sent, sender information, and recipient information. The agent then enters the information from the transaction form into a computer, such as a point of sale terminal, that is in communication with a central data base or host computer of the financial services institution. Alternatively, the agent may communicate the information to a representative of the financial services institution, and the representative may provide additional information to the agent that is added to the transaction form. Next, the agent collects from the sender the desired amount of money to be sent plus any applicable fees and/or taxes.
[0006] Another method of performing a send transaction involves providing a telephone at an agent location with which a sender can access an operator of a financial services institution. The sender then provides information to the operator, such as recipient name, sender name, desired amount of money to be sent, and agent location. Next, the operator transmits a transaction form, which includes the information provided by the sender, to an agent at the agent location via a facsimile transmittal machine. The sender then signs the transaction form. Next, the agent collects from the sender the desired amount of money to be sent plus any applicable fees and/or taxes. The agent then signs the transaction form and transmits the form back to the operator. Next, the operator enters the information from the transaction form into a central data base of the financial services institution.
[0007] Still another method of performing a send transaction includes providing a sender an access card that is used to access a central data base of a financial services institution. The sender provides the access card to an agent, and the agent enters the access card into the terminal so as to retrieve from the data base a list of potential recipient names previously identified by the sender. After the list has been retrieved, the sender selects a desired recipient from the list, and provides a desired amount of money to be sent to the selected recipient. Next, the agent collects from the sender the desired amount of money to be sent plus any applicable fees and/or taxes.
[0008] A prior method of performing a receive transaction involves a sender providing a recipient a money transfer control number (MTCN), which represents a unique key to transaction information or data stored in the data base. The recipient may then enter the MTCN on a form, which is provided to an agent by the recipient. Next, the agent accesses the data base using a terminal, and obtains a receive amount that corresponds to the MTCN. Alternatively, the agent may obtain the receive amount, or other information related to the receive transaction, by entering the recipient's name, sender's name, or sender's telephone number into the terminal.
[0009] The agent may then print a check for the receive amount. Next, the check is provided to the recipient. The recipient then endorses the check and receives cash from the agent. The agent may then use the signed check to obtain reimbursement from the financial services institution.
[0010] If the receive amount exceeds the agent's payout limit, which is the amount the agent is authorized or willing to pay out in cash to the recipient, then the agent may issue multiple checks, such as one check for an amount up to the payout limit, and one or more additional checks for the remainder of the receive amount. The additional check or checks must then be taken elsewhere for encashment.
[0011] Because this method of performing a receive transaction requires the agent to have significant cash on hand, this method is not practical for agents that typically do not have significant cash available. As a result, the number of agent locations available to a recipient is limited.
Summary of the Invention
[0012] A method, according to the invention, for performing a money transfer receive transaction involving a desired amount of money to be transferred from a sender to a recipient includes receiving transaction identifying information provided by the recipient; comparing the transaction identifying information with transaction data stored on a host computer system; providing a confirmation code, to be issued to the recipient, if the transaction identifying information matches the transaction data stored on the host computer system; storing the confirmation code on the host computer system; receiving at the host computer system input corresponding to the confirmation code from a dispensing terminal in communication with the host computer system; comparing the input to the confirmation code stored on the host computer system; and allowing funds, corresponding to at least a portion of the desired amount of money, to be dispensed by the dispensing terminal if the input matches the confirmation code stored on the host computer system.
Brief Description of the Drawings
[0013] FIG. 1 is a schematic diagram of a system according to the invention for performing money transfer transactions; and
[0014] FIG. 2 (2a and 2b) is a flowchart illustrating operation of a method according to the invention for performing money transfer transactions.
Detailed Description of the Preferred Embodiment(s)
[0015] FIG. 1 shows a system 10 according to the invention for performing electronic data transfers to effect money transfer transactions through a financial services institution. Generally, a money transfer transaction according to the invention may be divided into two distinct transactions, a money transfer send transaction, or send transaction, and a money transfer receive transaction, or receive transaction. Under the send transaction, a sender electronically sends or “wires” money to a recipient through the financial services institution. Under the receive transaction, the recipient receives the money through the financial services institution. Money transfer transactions may also be facilitated by an agent that may receive a commission for each transaction. Agent, as used herein, refers to a person that assists in one or more money transfer transactions through the financial services institution, but is not a direct employee of the financial services institution. Furthermore, both the sender and the recipient may be referred to as customers of the financial services institution and/or the agent.
[0016] The system 10 includes one or more send-transaction initiating devices, such as a personal computer 12 and/or an electronic terminal 14, for initiating the send transaction. The send transaction initiating devices 12, 14 may be located in any suitable area, such as an agent location, a sender's home or office, or a public place. The electronic terminal 14 may include a keypad 15, a display device 16 and a card reader 17. A printer 18 may also be provided in communication with the electronic terminal 14 for printing such things as receipts or other printed records. While the electronic terminal 14 may be any suitable electronic device such as an unattended automated teller machine (ATM), in the embodiment shown in FIG. 1 , the electronic terminal 14 is an FDX-400® available from Western Union of Greenwood Village, Colo.
[0017] The send-transaction initiating devices 12, 14 are preferably in communication, either directly or indirectly, with a host computer system 20 of the financial services institution. For example, send-transaction initiating devices 12, 14 may be linked to the host computer system 20 via any suitable communication network such as a local area network, a wide area network, a dial-up network, the Internet, a wireless network or any combination thereof. While the host computer system 20 may include one or more host computers, in the embodiment shown in FIG. 1 , the host computer system 20 includes a money transfer host 21 and a payout account host 22 in communication with the money transfer host 21. Furthermore, the send-transaction initiating devices 12, 14 may be used to provide transaction details to the host computer system 20, as explained below in detail.
[0018] The system 10 also includes one or more receive-transaction initiating devices or terminals, such as electronic terminal 23, a personal computer 24, or cellular telephone 25, that are used to initiate receive transactions, as explained below in greater detail. The electronic terminal 23 may include a keypad 26, a display device 28, a card reader 30 and an image scanner 31. A printer 32 may also be provided in communication with the electronic terminal 23 for printing such things as negotiable instruments, receipts and/or other printed records. While the electronic terminal may be any suitable electronic device, in the embodiment shown in FIG. 1 , the electronic terminal 23 is also an FDX-400®.
[0019] Each receive-transaction initiating terminal 23, 24 and 25 may be linked to the host computer system 20 either directly or indirectly. For example, each receive-transaction initiating terminal 23, 24 and 25 may be linked to the host computer system 20 via any suitable communication network, such as a local area network, wide area network, a dial-up network, the Internet, a wireless network or any combination thereof.
[0020] In addition, the system 10 includes a receive-transaction fulfillment terminal or dispensing terminal, such as an ATM 34, that is used to dispense cash to the recipient. The ATM 34 may include a keypad 35, a display device 36, a card reader 37, a printer 38, a cash accepting device 39, a cash dispensing device 40, and an image scanner 41. The ATM 34 may be linked to the host computer system 20 via any suitable communication network such as a local area network, a wide area network, a dial-up network, the Internet, a wireless network or any combination thereof. Furthermore, such a communication network may be public (e.g, CIRRUS®, PLUS®, MAC®, etc.) or private so as to provide a barrier to entry.
[0021] The ATM 34 is also in communication with an authorization source or host 42 via a debit authorization network, such as MAC® or PLUS®, or via any other suitable communication network, such as a local area network, wide area network, a dial-up network, the Internet, a wireless network or any combination thereof. The authorization host 42 is in communication with the host computer system 20 via any suitable communication network. Alternatively, the authorization host 42 may be part of the host computer system 20.
[0022] FIG. 2 is a flow chart illustrating operation of a method or system, such as the system 10, for performing money transfer transactions according to the invention. As will be appreciated by one of ordinary skill in the art, many of the steps in the flow chart, such as steps performed by the host computer system 20 or other electronic device, represent control logic or instructions that may be effected or implemented by hardware, software, or a combination of hardware and software.
[0023] As mentioned above, each money transfer transaction may be divided into a send transaction and a receive transaction. At step 100, the sender begins the send transaction by providing transaction details to a send-agent, who is an agent that assists in send transactions and may also assist in receive transactions. The transaction details may include, for example, the sender's name and address, recipient name, and/or a desired amount of money to be transferred to the recipient, which may be referred to as principal amount. At step 102, the send-agent enters the transaction details into the electronic terminal 14 using, for example, the keypad 15. At step 103, the electronic terminal 14 transmits the transaction details to the host computer system 20. If the principal amount to be sent is over a certain amount, then the terminal 14 or the host computer system 20 may also request supplemental information from the sender, such as driver's license number, social security number, date of birth, etc. in order to comply with institutional and/or regulatory requirements.
[0024] Next, at step 104, the host computer system 20 determines a collect amount, which represents the principal amount plus any service fee and taxes, if applicable, and returns the collect amount to the electronic terminal 14 for display on display device 16. The host computer system 20 may also return a code, such as a money transfer control number (MTCN), to the electronic terminal 14. The send-agent then collects the collect amount from the sender, as indicated at step 106. At step 107, transaction data, which may include some or all of the transaction details and/or the MTCN, is stored on the host computer system 20. At step 108, the printer 18 may then be used to automatically print a receipt, which may include the MTCN, thereby ending the send transaction.
[0025] Alternatively, the send transaction may be carried out in any suitable manner. For example, instead of using the electronic terminal 14, the send-agent may use a telephone (not shown) to contact an operator or other employee of the financial services institution, and to provide transaction details to the operator. The operator may then communicate with the host computer system 20 to carry out the send transaction. As another example, the sender may utilize the personal computer 12 to access the host computer system 20 over the Internet, and to provide transaction details to the host computer system 20. The sender may then pay the collect amount using a credit card. As another example, the send transaction may be carried out in multiple stages, such as disclosed in co-pending application Ser. No. 09/427,249, which is assigned to the assignee of the present invention and is hereby incorporated by reference in its entirety. Under this approach, send transactions may be “staged” using a computer, telephone, or by other means, and then “fulfilled” at an agent location. As yet another example, the send transaction may be carried out utilizing an ATM, such as disclosed in U.S. Pat. No. 5,650,604, which is hereby incorporated by reference in its entirety. Under any of the above approaches, transaction data, which may include some or all of the transaction details described above and/or an MTCN, may be stored on the host computer system 20.
[0026] At step 110, the receive transaction begins with the sender providing the recipient transaction identifying information, which may include some or all of the transaction details and/or the MTCN. During the receive transaction, the principal amount may be referred to as the receive amount. Next, at step 112, the recipient provides the transaction identifying information to a receive-agent, who is an agent that assists in receive transactions. It is to be understood that the receive-agent may also assist in send transactions. The recipient may also indicate to the receive-agent whether or not he or she desires to receive at least a portion of the receive amount from ATM 34.
[0027] At step 114, the receive-agent enters the transaction identifying information into the electronic terminal 23 using, for example, the keypad 26. The electronic terminal 23 then transmits the transaction identifying information to the host computer system 20, as indicated at step 116. Depending on the dollar value of the receive amount, or other characteristics of the receive transaction, the host computer system 20 may prompt the receive agent via the electronic terminal 23 to obtain identification, such as a driver's license, from the recipient. Next, the host computer system 20 compares the transaction identifying information with the stored transaction data, at step 118. If the transaction identifying information does not match the stored transaction data, then the host computer system 20 may request that the transaction identifying information be re-entered, as indicated at step 120. If, after one or more subsequent attempts, the transaction identifying information still does not match the stored transaction data, then the transaction may be terminated.
[0028] If, on the other hand, the transaction identifying information matches the stored transaction data, the host computer system 20 may then generate, assign, or otherwise provide an identification code and a confirmation code, as indicated at step 122. The identification code and the confirmation code may each be a numeric code that, together, may be used to uniquely identify the money transfer transaction. For example, the identification code and the confirmation code may each be a number. Alternatively, if the ATM 34 or other dispensing terminal is appropriately configured, the identification code and/or the confirmation code may comprise one or more alpha-numeric characters, symbols, sounds and/or images. For example, if the keypad 35 of the ATM 34 has letter characters as well as number characters, the identification code and/or the confirmation code may comprise alpha-numeric characters. As another example, if the ATM 34 or other dispensing terminal includes a scanner, such as image scanner 41, the identification code and/or the confirmation code may comprise one or more images and/or symbols, such as a bar code.
[0029] Next, at step 124, the identification code and confirmation code are transmitted or otherwise provided to the electronic terminal 23. The identification code and the confirmation code are also stored on the host computer system 20 at step 125. At step 126, the identification code and confirmation code are provided to the recipient. For example, the receive-agent may print the identification code and confirmation code on a receipt using the printer 32. At step 128, the host computer system 20 may load payout funds corresponding to some or all of the receive amount in a payout account maintained on the payout account host 22. For example, the money transfer host 21 may communicate with the payout account host 72 so as to load payout funds on the payout account host 22. Alternatively, payout funds corresponding to some or all of the received amount may be stored in a pending state on the host computer system 20. For example, payout funds may be stored in a pending state on a transaction database of the host computer system 20.
[0030] Alternatively, the receive transaction may be initiated in any suitable manner. For example, referring to FIG. 1 , the recipient may use personal computer 24, telephone 25, or other electronic device, such as a personal digital assistant, to communicate with the host computer system 20 and provide the transaction identifying information to the host computer system 20. If the transaction identifying information matches the stored transaction data, then the host computer system 20 may provide the identification code and the confirmation code directly to the recipient, and may also load payout funds into the payout account.
[0031] As another example, the recipient may use telephone 44 to contact an employee of the financial services firm, such as a telephone operator or customer services representative (CSR) 46, so as to provide the transaction identifying information to the CSR 46. Depending on the dollar value of the receive amount, or other characteristics of the receive transaction, the CSR 46 may request that the recipient provide his or her driver's license number. The CSR 46 may then access the host computer system 20 using personal computer 48, for example, so as to compare the transaction identifying information with the stored transaction data. If the transaction identifying information matches the stored transaction data, the host computer system 20 may then generate or assign the identification code and the confirmation code, which are provided to the CSR 46 and stored on the host computer system 20. Furthermore, the host computer system 20 may load payout funds into the payout account or store payout funds in a pending state. Next, the CSR 46 may provide the identification code and confirmation code to the recipient.
[0032] As yet another example, the receive transaction may be initiated by using the ATM 34. Under this approach, the recipient may enter the transaction identifying information into the ATM 34 using the keypad 35. The ATM 34 then transmits the transaction identifying information to the host computer system 20 through the authorization host 42. Next, the host computer system 20 compares the transaction identifying information with the stored transaction data. If the transaction identifying information matches the stored transaction data, then the host computer system 20 may generate or assign the identification code and the confirmation code, which are transmitted or otherwise provided by the host computer system 20 to the ATM 34. The identification code and confirmation code are also stored on the host computer system 20. Furthermore, the host computer system may also load payout funds into the payout account. The ATM 34 then provides the codes to the recipient. For example, the codes may displayed on display device 36 and/or printed on a receipt using printer 38.
[0033] Once the recipient obtains the identification code and the confirmation code, the recipient may use these codes at the ATM 34 to obtain some or all of the receive amount. For example, in response to prompts by the ATM 34, the recipient may enter input corresponding to the identification code and confirmation code into the ATM 34 using keypad 35, at step 130. The recipient may also enter a desired withdrawal amount into the ATM 34 using the keypad 35, as indicated at step 132. The desired withdrawal amount may be a portion or all of the receive amount.
[0034] At step 134, the ATM 34 transmits the input and the desired withdrawal amount to authorization host 42, which transmits the input and the desired withdrawal amount to the host computer system 20. After receiving the input, the host computer system 20 compares the input to the stored identification code and confirmation code, as indicated at step 136. If the input does not match the stored codes, then the host computer system 20 may request that the input be re-entered, as indicated at step 138. If, after one or more subsequent attempts, the input still does not match the stored codes, then the transaction may be terminated.
[0035] If, on the other hand, the input matches the stored codes, then the host computer system 20 authorizes or otherwise allows the ATM 34 to dispense funds corresponding to the desired withdrawal amount to the recipient, at step 140. At step 142, if a payout account is being used, the host computer system 20 may also allow the payout account to exceed the receive amount or go negative by a predetermined, configurable amount, such as $5.00, so as to cover any transaction fee charged by the owner or operator of the ATM 34. After some period of time, such as at the end of each day, the host computer system 20 may then zero out the payout account, as well as any other payout accounts associated with other money transfer transactions, as indicated at step 144. Alternatively, the host computer system 20 may load an additional amount in the payout account, at the time the payout funds are loaded into the payout account or at any other time, so as to cover any transaction fee. For example, the host computer system 20 may automatically calculate a transaction fee at the time of a debit request, and then load the transaction fee into the payout account. Such a transaction fee may be determined, for example, by assuming an even, whole dollar desired withdrawal amount, and attributing any additional requested debit amount to the transaction fee. More specifically, if the ATM 34 transmits a debit request of $301.95, the host computer system 20 may assume that the desired withdrawal amount for the recipient is $300, and that the remaining $1.95 is the transaction fee.
[0036] As yet another alternative, if the payout funds are stored in a payout account or just stored in a pending state on the host computer system 20, the ATM 34 may debit or otherwise deduct a transaction fee, if any, from the payout funds, if authorized to do so by the recipient and/or the host computer system 20. As another alternative, the ATM 34 may request that the recipient enter an amount of money sufficient to cover the transaction fee into the cash accepting device 39.
[0037] Advantageously, if the recipient does not withdraw funds corresponding to the full amount of the payout funds, the host computer system 20 may be configured to allow the recipient to initiate a second or other subsequent withdrawal, using the same identification code and confirmation code, at the ATM 34 or a different ATM. In such a case, the host computer system 20 may include instructions for allowing the payout account to further exceed the amount of the payout funds, or go further negative, to cover any additional transaction fees for the additional dispensing transaction, or the recipient may be responsible for any additional transaction fees.
[0038] Because the method described above includes use of both an identification code and a confirmation code, the method may be used with ATM's that are configured to receive two separate numbers, such as disclosed in U.S. Pat. No. 5,650,604. Alternatively, the method according to the invention may involve generation and use of only one code. For example, the host computer system 20 may generate, assign or otherwise provide only the identification code or the confirmation code, and the recipient may use only the one code to obtain some or all of the receive amount.
[0039] As yet another alternative, the recipient may assign or otherwise provide the identification code, and the host computer system 20 may generate, assign or otherwise provide the confirmation code. For example, if the electronic terminal 23 includes image scanner 31 and the ATM 34, or other receiver transaction initiating device, includes an images scanner, such as image scanner 41, then the recipient may establish the identification code as an anatomical image, such as a finger print, retinal image or facial image. As another example, the recipient may establish the identification code as his or her telephone number, social security number, or any other number or code, such as a code that includes one or more alpha-numeric characters, symbols, sounds and/or images. The host computer system 20 may also use the identification code and/or the receive amount as part of a key or algorithm to generate the confirmation code, or the host computer system 20 may randomly generate the confirmation code. Under this approach, if two recipients utilize the same identification code for two different transactions, the host computer system 20 will generate or assign a different confirmation code for each transaction so that the transactions can be uniquely identified.
[0040] Under the invention, actions by the recipient, not the sender, are preferably what trigger generation or establishment of the identification code and/or confirmation code. Furthermore, the identification code and/or confirmation code are issued directly to the recipient, rather than being issued to the sender. As a result, no matter how the send transaction is carried out, the recipient may cause the receive transaction to be carried out using the ATM 34 or other suitable dispensing terminal.
[0041] While embodiments of the invention have been illustrated and described, it is not intended that these embodiments illustrate and describe all possible forms of the invention. Rather, the words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the invention.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
What is claimed is:
1. A method for performing a money transfer receive transaction involving a desired amount of money to be transferred from a sender to a recipient, the method comprising:
receiving transaction identifying information provided by the recipient, wherein the transaction identifying information is not operable at a dispensing terminal;
comparing the transaction identifying information with transaction data stored on a host computer system;
providing a confirmation code, to be issued to the recipient, if the transaction identifying information matches the transaction data stored on the host computer system;
storing the confirmation code on the host computer system;
receiving at the host computer system input corresponding to the confirmation code from the dispensing terminal in communication with the host computer system;
comparing the input to the confirmation code stored on the host computer system; and
allowing funds, corresponding to at least a portion of the desired amount of money, to be dispensed by the dispensing terminal if the input matches the confirmation code stored on the host computer system.
2. The method of claim 1 wherein the confirmation code includes a number.
3. The method of claim 1 wherein the confirmation code includes a letter.
4. The method of claim 1 wherein the confirmation code includes a symbol.
5. The method of claim 1 wherein the confirmation code includes an image.
6. The method of claim 1 wherein the step of providing a confirmation code includes providing, by the host computer system, the confirmation code to a receive-transaction initiating device in communication with the host computer system.
7. The method of claim 6 wherein the receive-transaction initiating device is a personal computer.
8. The method of claim 6 wherein the receive-transaction initiating device is a telephone.
9. The method of claim 1 wherein the step of providing a confirmation code includes providing, by a telephone operator, the confirmation code to the recipient.
10. The method of claim 1 further comprising:
providing an identification code to the recipient if the transaction identifying information matches the transaction data stored on the host computer system;
storing the identification code on the host computer system;
receiving at the host computer system additional input corresponding to the identification code from the dispensing terminal;
comparing the additional input to the identification code stored on the host computer system; and
wherein the step of allowing funds, corresponding to at least a portion of the desired amount of money, to be dispensed by the dispensing terminal includes allowing the funds to be dispensed if the additional input matches the identification code stored on the host computer system.
11. The method of claim 10 wherein the identification code includes a number.
12. The method of claim 10 wherein the identification code includes a letter.
13. The method of claim 10 wherein the identification code includes a symbol.
14. The method of claim 10 wherein the identification code includes an image.
15. The method of claim 1 further comprising:
receiving an identification code established by the recipient;
storing the identification code on the host computer system;
receiving at the host computer system additional input corresponding to the identification code from the dispensing terminal; and
comparing the additional input to the identification code stored on the host computer system;
wherein the step of all owing funds, corresponding to at least a portion of the desired amount of money, to be dispensed by the dispensing terminal includes allowing the funds to be dispensed if the additional input matches the identification code stored on the host computer system.
16. The method of claim 15 wherein the identification code includes a number.
17. The method of claim 15 wherein the identification code includes a letter.
18. The method of claim 15 wherein the identification code includes a symbol.
19. The method of claim 15 wherein the identification code includes an image.
20. A method for performing a money transfer transaction, the method comprising:
storing transaction data on a host computer system, wherein the transaction data includes a desired amount of money to be electronically transferred from a sender to a recipient;
receiving at the host computer system transact on identifying information from a receive-transaction initiating terminal in communication with the host computer system, wherein the transaction identifying information is provided by the recipient;
comparing the transaction identifying information with the transaction data stored on the host computer system;
providing, by the host computer system, an identification number and a confirmation code to the receive-transaction initiating terminal, for issuance to the recipient, if the transaction identifying information matches the transaction data stored on the host computer system;
storing the identification number and the conformation code on the host computer system;
receiving at the host computer system input corresponding to the identification number and the confirmation code from a dispensing terminal in communication with the host computer system;
comparing the input to the identification number and the confirmation code stored on the host computer system; and
authorizing funds corresponding to at least a portion of the desired amount of money to be dispensed by the dispensing terminal if the input matches the identification number and the confirmation code stored on the host computer system.
21. The method of claim 1 wherein the transaction identifying information includes a first code provided by the sender to the recipient.
22. The method of claim 21 further comprising receiving at the host computer system an identification code provided by the recipient, and generating the confirmation code by the host computer system based on the identification code wherein the identification code is different than the first code.
23. The method of claim 1 further comprising loading, payout funds corresponding to at least a portion of the desired amount of money in a payout account maintained on the host computer system, and allowing the payout account to go negative by an amount to cover a transaction fee associated with use of the dispensing terminal.
24. The method of claim 1 further comprising loading payout funds corresponding to at least a portion of the desired amount of money in a payout account maintained on the host computer system, receiving at the host computer systems a debit request from the dispensing terminal, automatically determining by the host computer system a transaction fee associated with use of the dispensing terminal in response to receiving the debit request, and then loading an additional amount in the payout account to cover the transaction fee.
25. The method of claim 24 wherein the step of automatically determining the transaction fee includes assuming an even, whole dollar first portion of the debit request corresponds to a desired withdrawal amount for the recipient, and attributing a second portion of the debit request to the transaction fee.
26. The method of claim 1 further comprising loading payout funds corresponds to at least a portion of the desired amount of money in a payout account maintained on the host computer system, and allowing the dispensing terminal to debit the payout account to cover a transaction fee associated with use of the dispensing terminal.
27. The method of claim 1 wherein the allowing, step includes allowing funds, corresponding to a first portion of the desired amount of money, to be dispensed by the dispensing terminal if the input matches the confirmation code stored on the host computer system, and wherein the method further comprises receiving at the host computer system additional input corresponding to the confirmation code from an additional dispensing terminal in communication with the host computer system, comparing the additional input to the confirmation code stored on the host computer system, and allowing additional funds, corresponding to a second portion of the desired amount of money, to be dispensed by the additional dispensing terminal if the additional input matches the confirmation code stored on the host computer system.
28. The method of claim 1 further comprising:
receiving at the host computer system an identification code from an electronic terminal that is different from the dispensing terminal, the identification code being an anatomical image of the recipient;
storing the identification code on the host computer system;
receiving at the host computer system additional input corresponding to the identification code from the dispensing terminal;
comparing the additional input to the identification code stored on the host computer system; and
wherein the step of allowing funds, corresponding to at least a portion of the desired amount of money, to be dispensed by the dispensing terminal includes allowing the funds to be dispensed if the additional input matches the identification code stored on the host computer system.
29. The method of claim 1 wherein the dispensing terminal is an unattended automated teller machine.
30. The method of claim 20 wherein the transaction data further includes a first code provided by the sender to the recipient, the first code being different than the confirmation code, and wherein the transaction identifying information includes the first code.
31. The method of claim 30 wherein the dispensing terminal is an unattended automated teller machine.
32. The method of claim 1 wherein the allowing step comprises allowing the funds to be dispensed by the dispensing terminal to the recipient.
33. The method of claim 20 wherein the authorizing step comprises authorizing the funds to be dispensed by the dispensing terminal to the recipient.
34. The method of claim 1 wherein the confirmation code is not provided by the sender.
35. The method of claim 1 wherein receiving transaction identifying information provided by the recipient comprises receiving transaction identifying information, provided by the recipient, from a receive-transaction initiating terminal that is different than the dispensing terminal.
36. The method of claim 20 wherein the identification number and the confirmation code are not provided by the sender.
37. The method of claim 20 wherein the receive-transaction initiating terminal is different than the dispensing terminal.
38. A method for performing a money transfer receive transaction involving a desired amount of money to be transferred from a sender to a recipient, the method comprising:
receiving transaction identifying information provided by the recipient;
comparing the transaction identifying information with transaction data stored on a host computer system;
providing a confirmation code, to be issued to the recipient, if the transaction identifying information matches the transaction data stored on the host computer system;
storing the confirmation code on the host computer system;
loading payout funds into a payout account associated with the confirmation code in response to the transaction identifying information matching the transaction data;
receiving at the host computer system input corresponding to the confirmation code from a dispensing terminal in communication with the host computer system;
comparing the input to the confirmation code stored on the host computer system; and
allowing funds, corresponding to at least a portion of the desired amount of money, to be dispensed by the dispensing terminal from the payout account if the input matches the confirmation code stored on the host computer system.
39. The method of claim 1, wherein the confirmation code is generated by the host.
Patent Citations (129)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4032931(A) | 1977-06-01 | Haker | Applicant |
| US4454414(A) | 1984-06-01 | Benton | Applicant |
| US4523087(A) | 1985-06-01 | Benton | Applicant |
| US4641239(A) | 1987-02-01 | Takesako | Applicant |
| US5021967(A) | 1991-06-01 | Smith | Applicant |
| US5083272(A) | 1992-01-01 | Walker et al. | Applicant |
| US5220501(A) | 1993-06-01 | Lawlor et al. | Applicant |
| US5283829(A) | 1994-02-01 | Anderson | Applicant |
| US5326960(A) | 1994-07-01 | Tannenbaum | Applicant |
| US5350906(A) | 1994-09-01 | Brody et al. | Applicant |
| US5448043(A) | 1995-09-01 | Nakano et al. | Applicant |
| US5461217(A) | 1995-10-01 | Claus | Applicant |
| US5477037(A) | 1995-12-01 | Berger | Applicant |
| US5477038(A) | 1995-12-01 | Levine et al. | Applicant |
| US5570465(A) | 1996-10-01 | Tsakanikas | Applicant |
| US5650604(A) | 1997-07-01 | Marcous | Examiner |
| US5691525(A) | 1997-11-01 | Aoki et al. | Applicant |
| US5717868(A) | 1998-02-01 | James | Applicant |
| US5721768(A) | 1998-02-01 | Stinson et al. | Applicant |
| US5732136(A) | 1998-03-01 | Murphree et al. | Applicant |
| US5745886(A) | 1998-04-01 | Rosen | Applicant |
| US5764888(A) | 1998-06-01 | Bolan et al. | Applicant |
| US5774879(A) | 1998-06-01 | Custy et al. | Applicant |
| US5779379(A) | 1998-07-01 | Mason et al. | Applicant |
| US5787403(A) | 1998-07-01 | Randle | Applicant |
| US5799087(A) | 1998-08-01 | Rosen | Applicant |
| US5826241(A) | 1998-10-01 | Stein et al. | Applicant |
| US5875435(A) | 1999-02-01 | Brown | Applicant |
| US5896298(A) | 1999-04-01 | Richter | Applicant |
| US5897620(A) | 1999-04-01 | Walker et al. | Applicant |
| US5897989(A) | 1999-04-01 | Beecham | Applicant |
| US5898154(A) | 1999-04-01 | Rosen | Applicant |
| US5899982(A) | 1999-05-01 | Randle | Applicant |
| US5902983(A) | 1999-05-01 | Crevelt et al. | Applicant |
| US5903881(A) | 1999-05-01 | Schrader et al. | Applicant |
| US5909673(A) | 1999-06-01 | Gregory | Applicant |
| US5913202(A) | 1999-06-01 | Motoyama | Applicant |
| US5920629(A) | 1999-07-01 | Rosen | Applicant |
| US5920848(A) | 1999-07-01 | Schutzer et al. | Applicant |
| US5936221(A) | 1999-08-01 | Corder et al. | Applicant |
| US5937396(A) | 1999-08-01 | Konya | Applicant |
| US5949044(A) | 1999-09-01 | Walker et al. | Applicant |
| US5952639(A) | 1999-09-01 | Ohki et al. | Applicant |
| US5953703(A) | 1999-09-01 | Takeuchi et al. | Applicant |
| US5953709(A) | 1999-09-01 | Gilbert et al. | Applicant |
| US5953710(A) | 1999-09-01 | Fleming | Applicant |
| US5963647(A) | 1999-10-01 | Downing et al. | Applicant |
| USRE36365(E) | 1999-11-01 | Levine et al. | Applicant |
| US5993047(A) | 1999-11-01 | Novogrod et al. | Applicant |
| US6003763(A) | 1999-12-01 | Gallagher et al. | Applicant |
| US6012048(A) | 2000-01-01 | Gustin et al. | Applicant |
| US6015087(A) | 2000-01-01 | Seifert et al. | Applicant |
| US6027216(A) | 2000-02-01 | Guyton et al. | Applicant |
| US6032137(A) | 2000-02-01 | Ballard | Applicant |
| US6035406(A) | 2000-03-01 | Moussa et al. | Applicant |
| US6039250(A) | 2000-03-01 | Ito et al. | Applicant |
| US6044360(A) | 2000-03-01 | Picciallo | Applicant |
| US6045039(A) | 2000-04-01 | Stinson et al. | Applicant |
| US6064990(A) | 2000-05-01 | Goldsmith | Applicant |
| US6070156(A) | 2000-05-01 | Hartsell, Jr. | Applicant |
| US6088684(A) | 2000-07-01 | Custy et al. | Applicant |
| US6098053(A) | 2000-08-01 | Slater | Applicant |
| US6119106(A) | 2000-09-01 | Mersky et al. | Applicant |
| US6119931(A) | 2000-09-01 | Novogrod | Applicant |
| US6122625(A) | 2000-09-01 | Rosen | Applicant |
| US6145738(A) | 2000-11-01 | Stinson et al. | Applicant |
| US6149056(A) | 2000-11-01 | Stinson et al. | Applicant |
| US6206283(B1) | 2001-03-01 | Bansal et al. | Applicant |
| US6209104(B1) | 2001-03-01 | Jalili | Examiner |
| USRE37122(E) | 2001-04-01 | Levine et al. | Applicant |
| US6223168(B1) | 2001-04-01 | McGurl et al. | Applicant |
| US6250557(B1) | 2001-06-01 | Forslund et al. | Applicant |
| US6275829(B1) | 2001-08-01 | Angiulo et al. | Applicant |
| US6282523(B1) | 2001-08-01 | Tedesco et al. | Applicant |
| US6286756(B1) | 2001-09-01 | Stinson et al. | Applicant |
| US6292789(B1) | 2001-09-01 | Schutzer | Applicant |
| US6314169(B1) | 2001-11-01 | Schelberg, Jr. | Applicant |
| US6324522(B2) | 2001-11-01 | Peterson et al. | Applicant |
| US6332134(B1) | 2001-12-01 | Foster | Applicant |
| US6351739(B1) | 2002-02-01 | Egendorf | Applicant |
| US6367693(B1) | 2002-04-01 | Novogrod | Applicant |
| US6394343(B1) | 2002-05-01 | Berg et al. | Applicant |
| US6415271(B1) | 2002-07-01 | Turk et al. | Applicant |
| US6473500(B1) | 2002-10-01 | Risafi et al. | Examiner |
| US6488203(B1) | 2002-12-01 | Stoutenburg et al. | Examiner |
| US6502747(B1) | 2003-01-01 | Stoutenburg et al. | Applicant |
| US6547132(B1) | 2003-04-01 | Templeton et al. | Applicant |
| US6554184(B1) | 2003-04-01 | Amos | Examiner |
| USRE38255(E) | 2003-09-01 | Levine et al. | Applicant |
| US6736314(B2) | 2004-05-01 | Cooper et al. | Applicant |
| US6761309(B2) | 2004-07-01 | Stoutenburg et al. | Applicant |
| US6814282(B2) | 2004-11-01 | Seifert et al. | Applicant |
| US6908031(B2) | 2005-06-01 | Seifert et al. | Applicant |
| US6994251(B2) | 2006-02-01 | Hansen et al. | Applicant |
| US7070094(B2) | 2006-07-01 | Stoutenburg et al. | Applicant |
| US7104440(B2) | 2006-09-01 | Hansen et al. | Applicant |
| US7229011(B2) | 2007-06-01 | Hansen et al. | Applicant |
| US2001/0037281(A1) | 2001-11-01 | French | Applicant |
| US2001/0042785(A1) | 2001-11-01 | Walker et al. | Examiner |
| US2002/0016763(A1) | 2002-02-01 | March | Applicant |
| US2002/0026373(A1) | 2002-02-01 | Kamath et al. | Applicant |
| US2002/0062285(A1) | 2002-05-01 | Amann et al. | Examiner |
| US2002/0087462(A1) | 2002-07-01 | Seifert | Applicant |
| US2003/0024979(A1) | 2003-02-01 | Hansen et al. | Applicant |
| US2003/0028491(A1) | 2003-02-01 | Cooper | Examiner |
| US2003/0069856(A1) | 2003-04-01 | Seifert et al. | Examiner |
| US2003/0074328(A1) | 2003-04-01 | Schiff et al. | Applicant |
| US2003/0080185(A1) | 2003-05-01 | Werther | Applicant |
| US2003/0083987(A1) | 2003-05-01 | Stoutenburg et al. | Applicant |
| US2003/0126083(A1) | 2003-07-01 | Seifert et al. | Applicant |
| US2003/0149662(A1) | 2003-08-01 | Shore | Examiner |
| US2004/0088248(A1) | 2004-05-01 | Cutler | Applicant |
| US2004/0211831(A1) | 2004-10-01 | Stoutenburg et al. | Applicant |
| US2005/0121513(A1) | 2005-06-01 | Drummond et al. | Applicant |
| US2006/0131387(A1) | 2006-06-01 | Hansen et al. | Applicant |
| US2006/0143118(A1) | 2006-06-01 | Stoutenburg et al. | Applicant |
| US2006/0191999(A1) | 2006-08-01 | Stoutenburg et al. | Applicant |
| US2008/0215487(A1) | 2008-09-01 | Stoutenburg et al. | Applicant |
| EP949596(A2) | 1999-10-01 | Applicant | |
| EP1077436(A2) | 2001-02-01 | Applicant | |
| FR2699358(A1) | 1994-06-01 | Applicant | |
| WO9626508(A) | 1996-08-01 | Applicant | |
| WO9836521(A) | 1998-08-01 | Applicant | |
| WO/22559(A1) | 2000-04-01 | Applicant | |
| WO67177(A2) | 2000-11-01 | Applicant | |
| WO1/04816(A1) | 2001-01-01 | Applicant | |
| WO139093(A) | 2001-05-01 | Applicant | |
| WO1/39093 | 2001-05-01 | Applicant | |
| WO3/060635(A2) | 2003-07-01 | Applicant |
Non-Patent Literature (27)
- Garfinkel, Simson & Spafford, Gene. Web Security Privacy & Commerce. O'Reilly. 2nd Edition. Nov. 1, 2001. pp. 125-129, 554-555 and 621-622.Examiner
- U.S. Appl. No. 10/855,127, filed May 27, 2004, Stoutenburg et al.Applicant
- U.S. Appl. No. 09/427,249, filed Oct. 26, 1999, Applicants: Earney E. Stoutenburg et al., “Method and System for Performing Money Transfer Transactions”.Applicant
- U.S. Appl. No. 09/975,171, filed Oct. 10, 2001, Applicants: Dean A. Seifert et al.,, “Method and System for Performing Money Transfer Transactions”.Applicant
- Disclosure Under 37 CFR § 1.56 dated Sep. 26, 2008, filed for U.S. Appl. No. 10/037,827.Applicant
- Bernstein, Phillip A.; Newcomer, Eric, Principles of Transaction Processing for the Systems Professional, Morgan Kaufmann Publishers, 1997, p. 24.Applicant
- International Search Report for PCT/US2002/039933, mailed Nov. 5, 2004.Applicant
- International Search Report for PCT/US2002/040556, mailed Jul. 15, 2003.Applicant
- International Preliminary Examination Report mailed Aug. 28, 2002 and Search Report mailed May 31, 2001 for PCT/US2000/041572.Applicant
- New commercial services from Western Union allow businesses to directly transfer money internationally; User companies can now send or receive money at their own offices through on-line connection to world's largest international money transfer network, Business Wire, Oct. 16, 1995, p. 1.Applicant
- Western Union Money Transfer, How To Send A Money Transfer 2001-2004.Applicant
- Author Unknown “Online Payment Services” www.auctionbytes.com/cab/pages/payment, compiled Nov. 2002, 3 pages.Applicant
- Author Unknown “PayPal News”, www.andrys.com/paypal.html, published prior to 2003, 3 pages.Applicant
- Author Unknown “PayPal.com Case Study” http://fox.rollins.edu/-slackman/paypal.htm, 2001, 6 pages,Applicant
- Boneh, Dan “Beaming Money by Email is Web's Next killer App”, PR Newswire, Nov. 16, 1999, pp. 1-4.Applicant
- Business Editors And High-Tech Writers “billserv.com Launches bills.com, an Internet Portal for Consumers to Pay Bills Online at No Cost” Business Wire, Feb. 22, 2000, pp. 1-2, New York.Applicant
- Confinity, Inc. “PayPal for the Palm”, www.handheldnew.com/file.asp?ObjectID=5401, published prior to Oct. 2003, 2 pages.Applicant
- Epper Hoffman, Karen “PayPal Still Running Free, but the e-payments company's carefree days may be numbered if regulators decide it's essentially a bank” Bank Technology News, published between 2001-2003, www.banktechnews.com/btn/articles/btnoct01-13.shtml, 3 pages.Applicant
- Latour, Almar “PayPal Electronic Plan May be On the Money in Years to Come”, The Wall Street Journal Interactive Edition, Nov. 15, 1999, downloaded from www.paypayl.com/html/wsj.html, 2 pages.Applicant
- Plotkin, Hal “Beam Me Up Some Cash” Silicon Valley Insider, Sep. 8, 1999, www.halplotkin.com/cnbcs029.htm, 3 pages.Applicant
- Steiner, Ina “PayPal Online Payment Service—Another Way to Pay for Auction items” www.auctionbytes.com, Feb. 20, 2000, 4 pages.Applicant
- Wijnen, Rene “You've Got Money!”, Bank Technology News, Jun. 2000, pp. 1-4, vol. 13, Issue 6, New York.Applicant
- International Search Report WO 2003060633 for PCT/US2002/03993 Mailed Nov. 5, 2004.Applicant
- International Search Report WO 2003060635 for PCT/US02/40556 Mailed Jul. 15, 2003.Applicant
- International Search Report WO 2007061505 for PCT/US2006/037888 Mailed May 22, 2007.Applicant
- Disclosure Under 37 CFR 1.56 dated Dec. 15, 2008, filed for U.S. Appl. No. 10/037,827.Applicant
- Supplementary European Search Report for EP 02 79 2380 dated May 7, 2009 and mailed May 14, 2009.Applicant