Patent Grant
7529706
The invention relates in general to effecting online financial transactions between individuals or between individuals and entities such as banks, merchants and other companies. More particularly, the invention relates to batch processing international money exchanges in an online context.
The present invention relates generally to online financial transactions, and more particularly to systems and methods for effecting person-to-person online financial transactions.
As more and more individuals become connected to the Internet, the number of e-commerce transaction grows proportionately. Currently, typical e-commerce transactions require individuals to submit confidential information such as credit card information or other bank account information over the Internet to effect a transfer of funds. For example, each time an individual purchases a product from a different merchant over the Internet, the individual must typically submit confidential credit card information to the merchant to complete the purchase transaction. The more an individual transmits such confidential information over the Internet the more opportunity there is for that information to be compromised.
Additionally, it is often difficult for individuals to effect monetary transactions without ultimately having a check sent from the payor to the payee; credit card transactions are not widely available for individuals. For example, in the context of an auction where one individual wins a bid to purchase an item from another individual, the purchaser must usually send a check to the seller. Such transactions are generally undesirable as postage is necessary to send the check, and processing of the check is required. This generally results in an undesirable increase in the amount of time and effort required to complete the transaction.
Accordingly, it is desirable to provide systems and methods for effecting online financial transaction between individuals or between individuals and merchants without the need for sending and cashing checks or transmitting confidential information.
The present invention provides systems and methods for effecting online financial transactions between individuals or between individuals and entities such as banks, merchants and other companies. The present invention is particularly useful for performing international money exchanges. In one embodiment, a method includes receiving a plurality of monetary exchange requests to exchange a first currency for a second currency, and monitoring the amount of the first currency that has been requested to be exchanged pursuant to the plurality of monetary exchange requests. The method further includes processing the plurality of monetary exchange requests when the amount of first currency requested to be exchanged reaches a predetermined level.
Other aspects, features, and techniques of the invention will be apparent to one skilled in the relevant art in view of the following detailed description of the invention
In one embodiment, a user may access a fund exchange server to establish an online account, which may then be used to transfer funds to and from other online accounts. An online account is generally a stored value account representing funds held in an account for the user at an affiliated financial institution. Each account, whether an individual account or a corporate account, may have one or more sub-accounts associated therewith. To fund an online account, funds may be transferred to an online account from, for example, a credit card account, direct demand account (DDA), or other financial account or from another online account. To withdraw funds, funds may be transferred to a credit card account or other bank account. In one embodiment, any user may initiate a send money transaction or a request payment transaction with any other entity provided that entity is able to receive an electronic message. For example, in one embodiment the receiving entity needs an ID or an e-mail address for an e-mail account to which an electronic message may be sent. It should be appreciated that the electronic message may be an e-mail message, instant message or other electronic message.
A user (e.g., an entity such as an individual or corporation) that desires to send money to another entity may do so by accessing an existing online account associated with the user and initiating a “send money” transaction. The user sending money (i.e., payor) enters an amount of funds to be transferred and contact information such as a user ID or an e-mail address of the recipient of the funds (i.e., payee). The payee may be an individual or other entity such as a corporation. The system sends an electronic message to the payee, for example, using an e-mail address if provided, indicating that the amount of funds has been “received” on the payee's behalf. In one embodiment, to effect transfer of the funds, the payee must access the system, for example, by selecting a URL or other link provided in the electronic message, and direct the received funds to an online account. An existing online account may be identified by the payee by providing information such as an account number and/or other identifying information, such as a password. If the payee does not have an existing online account, the payee may sign up for an account and provide credit card information or information for a checking account or other bank account sufficient to effect electronic transfer of funds. Thereafter, the received funds may be directed to the newly activated online account. At any point up to the time the received funds are deposited in the payee's online account, the payor can cancel the transaction according to one embodiment. In another embodiment, or in addition to one or more of the preceding embodiments, a user may withdraw any or all of the balance in their online account(s) at any time by transferring funds to a credit card account or other bank account.
A request money or request payment transaction (e.g., sending a bill) may also be initiated by a user (e.g., individual or corporation) that desires to receive payment from another entity. The user may enter an amount of funds owed and contact information such as an e-mail address for the recipient of the payment request (payor). In the case of multiple payors, an amount and contact information (e.g., user IDs and/or an e-mail address) may be necessary for each payor. The recipient of such a transaction request (payor) may be an individual or another entity such as a merchant corporation. The system may then send a payment request to the payor via an electronic message, for example via e-mail to a provided address, and the payor may respond by selecting a URL or other link provided in the electronic message. If the payor accepts the payment request, the payor may identify an online account from which to transfer funds to the payee (initiator of the payment request). If the payor does not have an online account established, the payor may be required to sign up for an online account and provide credit card information, or information for a checking account, or other bank account sufficient to effect electronic transfer of funds, to fund the online account. Thereafter, the amount of funds may be transferred to the payee and the system sends an e-mail notification or other electronic message to the payee indicating that the funds have been “received” on the payee's behalf. To complete the transaction, the payee may be required to direct the received funds to an online account, for example, by providing an online account number and/or other identifying information such as a password. In one embodiment, the payor may cancel the transaction at any time until the payee directs the received funds to an online account.
Another aspect of the invention involves effecting online transactions in an international context. In one embodiment, users are able to access one or more fund exchange servers to establish online accounts, which may then be used to transfer funds to and from other users' online accounts.
Another aspect of the invention relates to effecting monetary exchanges of currency of different countries. In one embodiment, monetary exchanges are carried out using one or more fund exchange servers before transferring funds between online accounts from difference countries.
Another aspect of the invention is to perform batch-process international money exchanges, which in one embodiment leads to more favorable currency exchange rates. In the embodiment, a currency accumulator may used to keep track of currency exchange requests. In another embodiment, each currency processed by the accumulator may be assigned a “bucket,” which is a symbolic representation of a database entry for the monetary amount which has been requested to be exchanged for a given currency. In another embodiment, or in addition to the previous embodiment, when the contents of a particular currency's “bucket” reaches a given level (e.g., predetermined minimum and/or maximum), the monetary amount in the bucket may be exchanged for an equivalent amount of a second currency (e.g., U.S. dollars).
In yet another embodiment of the accumulator, or in addition to the previous embodiments, the accumulator may further include a business rules engine which is usable to cause a bucket for a given currency to be emptied upon the occurrence of some event or condition. For example, a given currency's bucket may be emptied by the accumulator when the exchange rates for that currency (against the USD, for example) change. Moreover, the business rules engine may cause a currency's bucket to be emptied if trading in the particular currency is halted.
Reference to the remaining portions of the specification, including the drawings and claims, will realize other features and advantages of the present invention. Further features and advantages of the present invention, as well as the structure and operation of various embodiments of the present invention, are described in detail below with respect to the accompanying drawings. In the drawings, like reference numbers indicate identical or functionally similar elements.
Several elements in the system shown in
According to one embodiment as will be described in more detail below, fund exchange server 20 and any related components are operator configurable using an application including computer code-run using a central processing unit such as an Intel Pentium processor or the like. Computer code for operating and configuring fund exchange server 20 as described herein is preferably stored on a hard disk, but the entire program code, or portions thereof, may also be stored in any other memory device such as a ROM or RAM, or provided on any media capable of storing program code, such as a compact disk medium, a floppy disk, or the like. Additionally, the entire program code, or portions thereof may be downloaded from a software source to fund exchange server 20 over the Internet as is well known, or transmitted over any other conventional network connection as is well known, e.g., extranet, VPN, LAN, etc., using any communication medium and protocol as are well known. Additionally, portions of the program code may be downloaded or provided to client device 30 and executed on client device 30.
In general, a user accesses and queries fund exchange server 20, servers 501 to 50N, and other servers through a client device 30 to view and download content such as news stories, advertising content, search query results including links to various websites and so on. Such content can also include other media objects such as video and audio clips, URL links, graphic and text objects such as icons and hyperlinks, forms, pages and the like. Additionally, such content is typically presented to the user as a web page formatted according to downloaded JavaScript code and HTML code and data as is well known. In general, any Standard Generalized Markup Language (SGML) may also be used. Users are able to communicably access fund exchange server 20, e.g., over the Internet 40, using a client device 30 and conduct transactions, open online accounts and monitor online account activity as will be described herein.
A user may access fund exchange server 20 by selecting or entering the URL identifying the fund exchange server 20. One example of such a fund exchange server 20 is located at the URL https://paydirect.yahoo.com. When accessed, fund exchange server 20 preferably provides the user with one or more web pages including options for opening online accounts, accessing existing online accounts, initiating transactions, responding to transaction requests, etc. If the user has already established an online account, they may access an account page by providing an account number and security information such as a password and/or a security key. The account page may include various status information of pending and past transactions, account balance(s), user preferences, etc., as well as options for initiating various financial transactions. If the user does not have an established account, the user can select to open an account. The user can open an account by providing information such as an e-mail address, a password, mailing address and/or other information as may be necessary.
In general, an “online account” is an online stored value account representing an amount of funds held on the users behalf at an affiliate bank or other financial institution. A database 22 is provided for storing account information and data as is well known. To fund an account, the user must provide credit card information, e.g., credit card number, expiration date, etc, sufficient to effect a transfer of funds from a credit card account to the financial institution holding the user's actual funded account. An ATM check card (e.g., including a Visa logo) may also be used for transfer of funds to and from a checking account. ACH transfers may also be used to transfer funds to and from the affiliate financial institution as are well known. As shown in
According to one embodiment, various online financial transactions may be initiated using an established online account, including a “send money” transaction, a “request money” transaction and a “move money” transaction. In a “send money” transaction, one is able to send funds to an entity such as another individual or a merchant, in a “request money” transaction, one is able to receive payment from another entity or entities, and in a “move money” transaction, one is able to transfer funds to and from a credit card account, ATM check card account, checking account, brokerage account, any other financial account, or another online account associated with the user.
After the amount and identification information has been entered and submitted, e.g., by selecting continue button 260, at block 110 the system processes the information and sends an electronic message (e.g., e-mail notification or IM) to the recipient (payee) using the contact information provided by the payor. The electronic message may include a link (e.g., URL link or other selectable link) to a web page located on the fund exchange server 20. In one embodiment, the electronic message only alerts the payee that funds are ready to be transferred to the payee. However, the electronic message can include various other information such as the sender's name, the amount of funds ready for transfer, etc.
Upon selecting the link, a communication session may be established between the payee (i.e., using client device 30) and the fund exchange server 20. The payee is provided with a web page or other online document that allows the payee to accept or reject the “send money” transaction. For example, in one embodiment, a form is provided with various fields and selection buttons. If the identity confirmation feature was selected by the payor, the payee may also be presented with the identity confirmation query and a field for entering a response to the query. The payee must identify an account into which the funds are to be transferred, e.g., by providing an account number and password. If the payee does not have an account established, an account can be opened as described above. After all appropriate information has been entered and submitted by the payee, the system processes the received information at block 120. If the payee rejected the transaction, at block 125 the payor is notified of the rejection, e.g., by an e-mail notification message or by updating the payor's account page, and the transaction is canceled. If the payee has accepted the transaction, the system determines whether identity confirmation is active for the current transaction at block step 130. If the identity confirmation feature was not selected by the payor, at block 135 the funds may be transferred from the payor's account to the account identified by the payee. If, however, the identity confirmation feature was selected, the payor may be notified at block 140 that the payee has responded to the identity confirmation query, which in one embodiment is done using an electronic message. The response may also be included in an electronic message along with a URL link to the system. However, the response may alternatively be posted to the payor's account page for review the next time the payor logs into the system.
If the payor is satisfied with the information provided in the identity confirmation response, the payor may respond to the system with a decision. For example, the payor may select an accept button or a reject button. At block 150, the system receives and processes the payor's decision. If the payor rejected the identity confirmation response, the transaction may be canceled at block 155. If the payor accepted the response, at block 160 the funds may be transferred from the payor's account to the account identified by the payee. The payor may also be able to cancel the transaction at any time until the funds are transferred to the payee's account.
After the amount and identification information has been entered and submitted, e.g., by selecting continue button 460, at block 310, the system may then process the information and send an electronic message (e.g., e-mail notification or IM) to the recipient (payor) using the contact information provided by the payee. The electronic message typically includes a link (e.g., URL link or other selectable link) to a web page located on the fund exchange server 20. In one embodiment, the electronic message only alerts the recipient that a payment request (e.g., invoice or bill) has been received. It should be appreciated that the electronic message may also include various other information, such as the sender's name, the amount of funds desired to be transferred, etc.
Upon selecting the link, a communication session is established between the payor (i.e., using client device 30) and the fund exchange server 20. The payor may then be provided with a web page or other document that allows the payor to accept or reject the “request money” transaction. For example, in one embodiment, a form is provided with various fields and selection buttons. The payor may be required to identify an account from which the funds are to be transferred, e.g., by providing an account number and password. If the payor does not have an account established, an account can be opened and funded as described above. If the payor accepts the transaction, they may then be provided with the ability to select the identity confirmation feature. If the identity confirmation feature is selected, the payor may be required to enter a query. After all appropriate information has been entered and submitted by the payor, the system processes the received information at step 320. If the payor rejected the transaction, at block 325 the payee is notified of the rejection, e.g., by an electronic message or by updating the payee's account page. If the payor has accepted the transaction, at block 330 the system may notify the payee, e.g., by sending an electronic to the payee indicating that the transaction has been accepted by the payor. In one embodiment, the payor may select to accept the transaction in part, in which case the payor must enter the partial payment amount. The partial payment amount may also be communicated to the payee, either in an electronic message indicating acceptance or by posting to the payee's account page. If the payor has selected the optional identity confirmation feature, the query is also communicated to the payee, either in an electronic message indicating acceptance or by posting to the payee's account page. The electronic message may also include a link to a web page located on the find exchange server 20.
Upon selecting the link, a communication session is established between the payee (e.g., using client device 30) and the fund exchange server 20. In one embodiment, the payee is provided with a web page that allows the payee to direct the “received” funds to an online account. For example, the payee may be provided with an account page for an account associated with the payee. Alternately, or in addition, a form is provided with various fields and selection buttons. If the identity confirmation feature was selected by the payor, the payee is also presented with the identity confirmation query and a field for entering a response to the query. The payee may be required to identify an account into which the funds are to be transferred, e.g., by designating the account associated with the active account page, or by providing an account number and password for another account associated with the payee. If desired, the payee may open another account as described above.
After all appropriate information has been entered and submitted by the payee, the system processes the received information at block 340. The payee may also be provided with an option to cancel the transaction at this point. At block 350, the system determines whether identity confirmation is active for the current transaction. If the identity confirmation feature was not selected by the payor, at block 355 the funds may be transferred from the payor's account to the account identified by the payee. If the identity confirmation feature was selected, the payor may be notified (which in one embodiment is done via an electronic message) that the payee has responded to the identity confirmation query. This response may be included in an electronic message along with a URL, link to the system. However, the response may also be posted to the payor's account page for review the next time the payor logs in to the system.
If the payor is satisfied with the information provided in the identity confirmation response, the payor may respond to the system with a decision. For example, the payor may select an accept button or a reject button. At block 370, the system receives and processes the payor's decision. If the payor rejected the identity confirmation response, the transaction may then be canceled at block 375. If the payor accepted the response, at block 380 the funds are transferred from the payor's account to the account identified by the payee. The payor may also be able to cancel the transaction at any time until the funds are transferred to the payee's account.
In one embodiment, a multiple payor bill may be submitted as part of a “request money” transaction.
In a “move money” transaction, funds may be transferred to and from an online account. According to one embodiment, funds may be withdrawn from an online account to a credit card account, an ATM check card account, checking account or other financial account. According to another embodiment, funds may be transferred to an online account from a credit card account, an ATM check card account, checking account or other financial account. The financial institution server 50 effects the transfer of the actual funds with the appropriate account server, e.g., credit card server, ACH network server, bank server, etc. In another embodiment, funds may be transferred between online accounts associated with the user. For example, the user may have two or more separate online accounts or one or more online sub-accounts may be tied to a master online account. For sub-accounts, actual funds are debited or credited to an account at the financial institution associated only with the master account, such that when an online transaction involving a sub-account is completed actual funds may only be withdrawn from, or added to, the master account. Funds may be moved between the master account and a sub-account by the entity controlling the master account. Sub-accounts are useful for many applications, including, for example, allowing parents (controlling master account) to provide a monthly allowance to a child (sub-account) away at college or providing a limited spending account (sub-account) for an employee in charge of buying office supplies for a company (controlling master account).
To effect transfer between online accounts and between an online account and a credit card account, ATM check card account, checking account or other financial account, the user is preferably provided with a form with fields for entering the amount desired to be transferred, the account into which funds are to be transferred and the account from which funds are to be transferred.
According to one embodiment, multiple affiliate banks are provided for conducting settlements, e.g., ACH settlements with other banks, check card transactions, transactions with credit card companies, etc. Referring to
According to yet another embodiment, a transaction limit is placed on an online account until it has been established that the user is able to receive mail at a billing address, e.g., for a credit card or ATM check card. In this embodiment, the user is limited to sending or receiving no more than a certain amount (e.g., $200) until the user has verified that they are able to receive U.S. mail at the billing address. When the user signs up or registers with the system, a letter may be sent to the billing address. In one embodiment, the letter includes a code, such as an alphanumeric code. After the letter and code have been received, the user can verify/confirm the physical billing address by entering the code when logging in to the system. Once the physical address has been confirmed, the transaction limit may be raised. In one embodiment, the transaction limit is automatically raised, for example, to the lesser of $1000/month or the credit card limit, if credit card information was entered. Alternatively, the transaction limit may be set by the user, within a specified maximum set by the system. It will also be appreciated that any transaction limit determining scheme may be used.
Continuing to refer to
Referring now to
Two aspects of the invention include a security system and a transactional system. To this end,
The transactional system 1020, in the embodiment of
The pricing engine 1030 may be used to determine the fee that will be imposed for a given transaction. In one embodiment, the fee may be based on one or more factors, such as the origination and/or destination country involved in the transaction, the individual requesting the transaction, the amount of the transaction, programs related to the transaction and/or promotional/incentive-based factors. For example, repeat or referred customers may receive reduced transaction fees, or given one or more free transactions as part of a promotion.
Referring now to
In one embodiment, the accumulator 1205 may interact with one or more monetary exchange instances (e.g., instances 15, 815, etc.), a system for performing foreign currency exchanges (e.g., HSBC's eTreasury system), and a customer service interface for managing the accumulator 1205. In addition, the accumulator 1205 may include one or more of the following components:
It should of course be understood that one or more of the aforementioned components may be merged together (e.g., one database for all data stored).
The business rules engine may be used to govern the behavior of the accumulator 1205. In one embodiment, each currency is assigned a “bucket,” which is a symbolic representation of a database entry for the monetary amount which has been requested to be exchanged for a given currency. In another embodiment, or in addition to the previous embodiment, when the contents of a particular currency's “bucket” reaches a given level (e.g., predetermined minimum and/or maximum), the monetary amount in the bucket may be exchanged for an equivalent amount of a second currency (e.g., U.S. dollars). In one embodiment, this is done using the eTreasury system.
The eTreasury system may also specify minimum and maximum trading amounts. If the predetermined minimum and/or maximum for a currency's bucket is outside the range specified by the eTreasury system, the predetermined limits may be reduced to match the eTreasury values.
In yet another embodiment, or in addition to the previous embodiments, the business rules engine may cause a bucket for a given currency to be emptied when the exchange rates for that currency (against the USD, for example) change. Moreover, the business rules engine may cause a currency's bucket to be emptied if trading in the particular currency is halted.
In another embodiment, or in addition to the previous embodiments, a notional “end of day” time may be established at which point all currency buckets will be processed. Moreover, currency buckets may be cleared via a manual command. At the “end of day” time, there will likely be an overall profit amount. This profit amount represents the difference between the amount of currency received from each monetary exchange instance and the amount of currency that was traded via the eTreasury system. In one embodiment, this profit may be split amongst each of the monetary exchange instances involved and a message sent to each instance reporting that instance's share of the profit.
Another aspect of the business rules engine relates to a notional start of each trading day. At this point in time, currency exchange rates may be received from the eTreasury system, to which a loading may be added to produce profit margins for the exchange system. Loadings can be applied to the buy and sell rates for each currency pair asymmetrically (that is, the same loading need not be applied to both the buy and sell rates). The loadings can be applied to any currency pair which can be traded via the accumulator system, not just to the rates of a given currency against the US dollar. Some of the possible types of loading include a percentage offset from the current value or a fixed number of points away from the given rate.
Continuing to refer to
Thereafter, any transactional costs are determined and applied at block 1340 of
As mentioned above,
At this point, the process 1330 continues to block decision block 1430 where a determination is made as to whether the time period of the transaction makes the transactional risk high. If so, the time period for the exchange to take place is set to every day, or alternatively to every Y hours (1435). If, on the other hand, the time period of the transaction does not make it a high risk transaction, process 1330 may simply set the time period for the exchange to take place to be every Z days (1440).
Thereafter, process 1330 continues to block 1445 of
At this point in process 1330, the aforementioned determinations are used to determine and tabulate the transactional tolerance limits at block 1460. In some cases, there may be a desire to manually override these determined limits. Accordingly, process 1330 provides for the entry of such manual limits at block 1470.
Referring now to
While the preceding description has been directed to particular embodiments, it is understood that those skilled in the art may conceive modifications and/or variations to the specific embodiments described herein. Any such modifications or variations which fall within the purview of this description are intended to be included herein as well. It is understood that the description herein is intended to be illustrative only and is not intended to limit the scope of the invention.
This application is related to and claims priority from U.S. provisional patent Application No. 60/588,182, filed on Jul. 14, 2004. This application is also related to U.S. patent application Ser. No. 09/639,014, filed on Aug. 15, 2000, entitled “Systems and Methods for Implementing Person-to-Person Money Exchange”, U.S. application Ser. No. 10/990,774, filed Nov. 16, 2004, entitled “Systems and Methods for Implementing Account to Account Money Exchanges”, U.S. application Ser. No. 10/990,775, filed Nov. 16, 2004, entitled “Systems and Methods for Implementing Person-to-Person International Exchanges”, and U.S. application Ser. No. 11/112,316, filed Apr. 21, 2005, entitled, “Traffic Messaging System” which are all hereby incorporated herein by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5406584 | Erisman | Apr 1995 | A |
| 5757917 | Rose et al. | May 1998 | A |
| 5825003 | Jennings et al. | Oct 1998 | A |
| 5826241 | Stein et al. | Oct 1998 | A |
| 5903878 | Talati et al. | May 1999 | A |
| 6032136 | Brake, Jr. et al. | Feb 2000 | A |
| 6039250 | Ito et al. | Mar 2000 | A |
| 6044360 | Picciallo | Mar 2000 | A |
| 6070150 | Remington et al. | May 2000 | A |
| 6263447 | French et al. | Jul 2001 | B1 |
| 6318282 | Tsai | Nov 2001 | B1 |
| 6554184 | Amos | Apr 2003 | B1 |
| 6898575 | Mull | May 2005 | B2 |
| 7031939 | Gallagher et al. | Apr 2006 | B1 |
| 20010034676 | Vasic | Oct 2001 | A1 |
| 20020016769 | Barbara et al. | Feb 2002 | A1 |
| 20020022966 | Horgan | Feb 2002 | A1 |
| 20020029190 | Gutierrez-Sheris | Mar 2002 | A1 |
| 20030140004 | O'Leary et al. | Jul 2003 | A1 |
| 20040111370 | Saylors et al. | Jun 2004 | A1 |
| 20040236646 | Wu et al. | Nov 2004 | A1 |
| 20060015452 | Kulasooriya et al. | Jan 2006 | A1 |
| 20060015453 | Kulasooriya et al. | Jan 2006 | A1 |
| Number | Date | Country |
|---|---|---|
| 2002-140645 | May 2002 | JP |
| WO-0016227 | Mar 2000 | WO |
| WO-0028461 | May 2000 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20060015437 A1 | Jan 2006 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60588182 | Jul 2004 | US |
