Patent Grant
10402795
The present invention relates to computer systems for money transfers. More particularly, the present invention relates to systems and methods for prefunding money transfer send transactions and transaction fees.
A number of businesses offer money transfer and other services through a network of agents. A customer that desires to use these services to transfer money to a third party can take the money to an agent of the money transfer service. The agent accepts the money, obtains necessary information such as the customer's identity and the identity of the receiver, and initiates a transaction. The money is then made available to the receiver by another agent.
When a customer is ready to send the transaction, the agent collects fees to cover processing costs for the money transfer service, and provides a source of revenue for the money transfer service. A customer who makes frequent money transfers may be subjected to a transaction fee each time a money transfer transaction is generated and sent. In addition, the customer may provide cash, money order, or other immediate or near-immediate form of payment to the agent, and agent is responsible for the receipt and processing of the payment. This carrying and exchange of immediate or near-immediate forms of currency for each transaction can be inconvenient.
An approach to processing money transfers that both reduces the instances that currency is carried and exchanged and reduces fees for repeat customers would also be useful.
In one aspect, the present disclosure relates to a system for sending money transfer transactions. The system includes a computer configured to facilitate prefunding a number of money transfer transaction fees. Each prefunded money transfer transaction fee is usable to pay for a transaction fee associated with a future money transfer send transaction. The computer is further configured to charge an amount for each prefunded money transfer transaction fee based on the number of money transfer transaction fees prefunded. A server connected to the computer is configured to store information related to the prefunded money transfer transaction fees.
In another aspect, the present disclosure relates to a method for operating a computer system for sending money transfers. The method includes receiving a request on a computer to prefund a number of money transfer transaction fees that are each usable to pay for a transaction fee associated with a future money transfer send transaction. An amount is charged for each prefunded money transfer transaction fee based on the number of money transfer transaction fees prefunded The method further includes receiving funds to pay for the prefunded money transfer transaction fees, and storing information related to the prefunded money transfer transaction fees on a server.
In a further aspect, the present disclosure relates to a method for operating a computer system for sending money transfers. The method includes receiving a request on a computer to prefund either (a) a number of money transfer transaction fees each usable to pay for a transaction fee associated with a future money transfer send transaction or (b) a number of future money transfer send transactions and associated money transfer transaction fees. Additionally, the method includes charging an amount for each prefunded money transfer transaction fee that is based on (a) the number of money transfer transaction fees prefunded and (b) whether future money transfer send transactions are being prefunded. The method further includes receiving funds to pay for the prefunded money transfer transaction fees and any prefunded future money transfer send transactions, and storing information related to the prefunded money transfer transaction fees and any prefunded future money transfer send transactions on a server.
While multiple embodiments are disclosed, still other embodiments of the present invention will become apparent to those skilled in the art from the following detailed description, which shows and describes illustrative embodiments of the invention. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not restrictive.
The send location 14 may be a facility that is approved by a financial services organization to send purchase requests for money transfers to the server 20. The send location 14 may be a store or dedicated location that provides redemption services for money transfers. Alternatively, the send location 14 may access a computer remotely, such as via a telephone call or the internet. The send computer 12 is operated by an agent at the approved send location 14. The send computer 12 may include software that facilitates entry of information to request sending the money transfer for subsequent transmission to the server 20 for approval. The agent at the send location 14 may also review purchaser identification and accept funds from the sender of the money transfer. In some embodiments, the agent accepts funds on behalf of the financial services organization. The send location 14 may also include a telephone (not shown) or other voice communications device to contact the financial services organization if questions arise during the money transfer request process. While a single send location 14 is shown in
In alternative embodiments, the send computer 12 may be any computer configured to provide information to the server 20 via a secure internet or server connection. For example, the send computer 12 may be a home computer, kiosk, or other interactive device. The send computer 12 may include a web browser or other application that provides a user interface to enter information to send a money transfer. The web browser may allow for entry of sender identification information and sender account information, the latter of which authorizes withdrawal of funds from an account with a financial institution to fund the money transfer. As another example, the send computer 12 may be configured to receive money transfer send information from the sender via telephone or interactive voice recognition systems. As a further example, a telephone at the send location 14 may be used to contact a call center (not shown) to initiate a send request to the server 20.
The receive location 18 may be an institution that is approved by the financial services organization to receive money transfers for the benefit of a receiver associated with the institution and issue funds to the money transfer receivers. As discussed above, the receive location 18 may be institutions such as a correctional facility, custodial care facility, a court, or a school. The receive computer 16 at the receive location 18 may be operated by an approved employee of the institution using the receiver interface 24. The receive computer 18 may include software that facilitates retrieval of information about money transfers sent to the institution for the benefit of receivers associated with the institution. The employee operating the receive computer 16 at the receive location 18 may also, in some cases, review the information associated with the money transfer, such as the amount and purpose of the money transfer funds. If approved, the employee issues funds to the money transfer receiver's account at the institution. The receive location 18 may also include a telephone or other voice communications device to contact the financial services organization if questions arise during the money transfer receipt process. While a single receive location 18 is shown in
The server 20 may be housed and/or operated by or on behalf of the financial services organization that, among other functions, approves and coordinates send transactions of money transfers at the send location 14 and receive transactions of money transfers at the receive location 18. The server 20 facilitates approval of send requests from the send location 14 and receive requests from the receive location 18. In some embodiments, the server 20 is configured to process send and receive requests automatically. In other embodiments, the server 20 provides information to a user at the financial services organization for review and approval. For example, the server 20 may be connected to a computer 26 that provides an interface to a user at the financial services organization to review and approve or deny money transfer send or receive transactions. In some embodiments, the server 20 provides compliance functions for money transfer transaction. The server 20 includes storage capabilities to store information from money transfer send transactions for later retrieval during the money transfer receive approval process. In addition, the server 20 may store other information such as, for example, past customer money transfer send/receive activity, customer account information, and computer identification and log-in information for the send computer 12 and receive computer 16.
As will be described in more detail herein, the system 10 facilitates allowing a customer to prefund money transfer transaction fees to be applied to money transfers purchased at a later time. The system 10 may also be configured to allow the customer to prefund future money transfers as well as the transaction fees, to be sent at a future date. In some embodiments, the number of transaction fees prefunded and/or whether future money transfers are funded establishes the amount charged for each prefunded transaction fee. For example, the per transaction fee amount may be reduced for each transaction fee or each group of transaction fees prefunded.
By allowing the customer to prefund a number of transaction fees and/or money transfers, the financial services organization is able to establish a recurring relationship with the customer in one visit to the send location. In addition, the customer is able to set up multiple transactions without having to carry cash, money orders, or other forms of immediate or near-immediate currency to the send location each time a money transfer is sent. This provides convenience for both the customer and agent when the prefunded future money transfer and transaction fees are redeemed. In addition, prefunded transactions and fees increase safety for the customer and agent, since it reduces the number of instances that the customer brings funds to the send location.
In step 52, the send computer 12 charges an amount for each prefunded money transfer transaction fee based on the number of money transfer transaction fees prefunded. For example, in some embodiments, the amount charged for the each prefunded transaction fee may be reduced by a percentage of the full price transaction fee. The percentage reduction in the amount charged for each prefunded transaction fee may increase with increasing number of transaction fees prefunded. For example, the percentage reduction in the amount charged for each prefunded transaction fee may be linearly related to the number of transaction fees prefunded. As another example, the percentage reduction may be calculated based on an incremental number of transaction fees prefunded (i.e., larger discount for each group of transaction fees prefunded). In some embodiments, the send computer 12 may be programmed with a maximum or cap percentage reduction such that, when the cap percentage reduction is reached, prefunding of additional transaction fees does not result in an increased percentage reduction in the amount charged for each prefunded transaction fee.
In one exemplary implementation, the send computer 12 is configured to reduce the charge for each prefunded money transfer transaction fee by 1% for each transaction fee prefunded. As another example, the send computer 12 may be configured to increase the per prefunded transaction fee discount with each group of transaction fees prefunded (e.g., for each group of six). The percentage may be capped at a discount maximum, as discussed above. The discount percentage increase may be linear (i.e., same percentage increase with each group of transaction fees prefunded) or may escalate with increasing numbers of groups of transaction fees funded. In the latter case, one exemplary implementation may provide a 2% discount for six prefunded transaction fees, a 5% discount for twelve prefunded transaction fees, and a 15% discount for twenty-four prefunded transaction fees. These discounts and prefunded transaction fee group numbers are merely exemplary, and any combination of prefunded transaction fee group numbers and associated discounts are possible.
When the percentage reduction for each prefunded transaction fee has been calculated based on the number of transaction fees prefunded, then, in step 54, funds to pay for the prefunded money transfer transaction fees are received by the financial services organization. For example, if the customer is working with an agent at a send location 14, the customer provides funds (e.g., cash, money order, etc.) in the calculated amount to the agent. As another example, if the customer is using a self-service send computer 12 (e.g., kiosk, personal computer, etc.), the customer may pay for the prefunded transaction fees via electronic means, such as with a credit card or via direct withdrawal from a bank account.
In some embodiments, prefunding money transfer transaction fees may lock in or secure a foreign exchange rate for future money transfers. When the customer requests to prefund transaction fees, the customer may also be prompted to provide the destination country of the future money transfer associated with the prefunded transaction fees. The send computer 12 may be configured to determine the exchange rate between the country from which the customer is sending, and the country of the recipient of the future money transfer. Then, the send computer 12 locks in the exchange rate when the prefunding of the transaction fees has been completed. In some embodiments, the exchange rate is locked in when the funds to cover the prefunded money transfer fees are received.
The send computer 12 may also be configured to assign an expiration date to the prefunded transaction fees. In some embodiments, the locked in exchange rate associated with each prefunded transaction fee lapses after the expiration date. In some embodiments, for a prefunded transaction fee that has passed the expiration date, the exchange rate applied is the exchange rate on the day that the money transfer associated with the prefunded transaction fee is sent. The expiration date may also affect other aspects of the prefunded transaction fees, such as the amount of the discount applied to each prefunded transaction fee.
In step 56, information related to the prefunded money transfer transaction fees is stored, for example in server 20. The information related to the prefunded transaction fees may include, for example, the amount prefunded for each transaction fee and a confirmation number for each prefunded transaction fee or each group of transaction fees. The information may also include locked exchange rate and expiration date information for each prefunded transaction fee. In various embodiments, during the process of funding the transaction fees, the send computer 12 may be configured to prompt the customer for information associated with the prefunded transaction fees. For example, the send computer 12 may prompt the customer to provide identification information about the customer (e.g., name, photograph, government issued identification information, etc.) to allow the system 10 to associate the prefunded transaction fees with the customer for ease of retrieval upon use with a future money transfer transaction. The information about the customer may be stored with the transaction confirmation number in the server 20. The information associated with the prefunded transaction fees stored in the server 20 may also include information about the future money transfers associated with the prefunded transaction fees, such as the send amount, send date, and recipient identification information.
When the customer wishes to send a money transfer, the customer may go to a send location 14. The send location 14 may be the same or a different send location 14 as the send location 14 at which the transaction fees were prefunded. The customer provides information related to the money transfer (e.g., money transfer recipient, money transfer amount, etc.), and the transaction fees for the money transfer are calculated. The customer may then provide a confirmation number or other identifying information associated with the prefunded transaction fees stored in the server 20. The send computer 12 then retrieves information about the transaction fees prefunded by the customer, and applies the prefunded transaction fees to the money transfer transaction. The prefunded transaction fee used on the money transfer transaction is then marked as being used on the server 20.
In some cases, it may be useful or convenient to also fund money transfers in advance of the actual send date.
In step 62, the amount for each prefunded money transfer transaction fee is reduced by an amount that is based on the number of transaction fees prefunded. Step 62 is substantially similar to step 52 discussed above. For example, in some embodiments, the amount charged for the each prefunded transaction fee may be reduced by a percentage of the full price transaction fee. The percentage reduction in the amount charged for each prefunded transaction fee may increase with increasing number of transaction fees prefunded. For example, the percentage reduction in the amount charged for each prefunded transaction fee may be linearly related to the number of transaction fees prefunded. As another example, the percentage reduction may be calculated based on an incremental number of transaction fees prefunded.
In decision step 64, the send computer 12 prompts the customer to decide whether to prefund one or more money transfer send transactions. If the customer does not request to fund any money transfer send transactions, then, in step 68, the customer provides funds to pay for the prefunded money transfer transaction fees, similar to step 54 in
On the other hand, if in decision step 64 the customer decides to fund one or more money transfer transactions, then, in step 66, the amount charged for each prefunded transaction fee is further discounted by a prefunded money transfer discount. The prefunded money transfer discount may be a flat percentage that is added on to the discount applied above in step 62. For example, in one implementation, the prefunded money transfer discount is 5%. In other embodiments, the prefunded money transfer discount may be a function of the number of money transfers prefunded. The combined discounts applied for the prefunding of money transfers and transaction fees may be capped at a maximum discount, as discussed above.
After the discounts for prefunding money transfers and transaction fees is calculated, then, in step 68, funds to pay for the prefunded money transfer transaction fees are received by the financial services organization. For example, if the customer is working with an agent at a send location 14, the customer provides funds (e.g., cash, money order, etc.) in the calculated amount to the agent. As another example, if the customer is using a self-service send computer 12 (e.g., kiosk, personal computer, etc.), the customer may pay for the prefunded transaction fees via electronic means, such as with a credit card or via direct withdrawal from a bank account.
In step 70, information related to the prefunded money transfers and transaction fees is stored, for example in server 20. The information related to the prefunded money transfers may include, for example, the amount prefunded for each money transfer and a confirmation number for each money transfer or each group of money transfers. The information may also include locked exchange rate and expiration date information for each prefunded transaction fee. The information may further include customer identification information, the send dates of the prefunded money transfers, and recipient identification information.
When the customer wishes to send a prefunded money transfer, the customer may go to a send location 14. The send location 14 may be the same or a different send location 14 as the send location 14 at which the transaction fees were prefunded. The customer provides information to retrieve the prefunded money transfer (e.g., confirmation number, customer identification, send amount, recipient information, etc.) The send computer 12 then retrieves information about the money transfers prefunded by the customer, applies the prefunded transaction fees associated with the money transfer transaction, and sends the money transfer.
The prefunding of money transfers may be useful and convenient to a customer who frequently sends money transfers, particularly to the same recipient. For example, if a customer uses money transfer services to pay a recurring bill, the customer can prefund money transfers to cover multiple future bills in a single visit to a send location 14. In some embodiments, an account number the customer uses in association with the payee of the bill may be attached to the prefunded money transfer. Thus, when the bill comes due, the customer may go to the send location and approve sending of the prefunded money transfer to the payee. Alternatively, the send computer 12 may be configured to send a prefunded money transfer automatically on or before the due date of the bill.
Various modifications and additions can be made to the exemplary embodiments discussed without departing from the scope of the present invention. For example, while the embodiments described above refer to particular features, the scope of this invention also includes embodiments having different combinations of features and embodiments that do not include all of the above described features.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5326960 | Tannenbaum | Jul 1994 | A |
| 5432326 | Noblett, Jr. et al. | Jun 1995 | A |
| 5434929 | Beernink et al. | Jul 1995 | A |
| 5604802 | Holloway | Feb 1997 | A |
| 5864483 | Brichta | Jan 1999 | A |
| 5920848 | Schutzer et al. | Jul 1999 | A |
| 5949044 | Walker et al. | Sep 1999 | A |
| 5974146 | Randle et al. | Oct 1999 | A |
| 6010067 | Elbaum | Jan 2000 | A |
| 6018718 | Walker et al. | Jan 2000 | A |
| 6039250 | Ito et al. | Mar 2000 | A |
| 6073090 | Fortune et al. | Jun 2000 | A |
| 6139177 | Venkatraman et al. | Oct 2000 | A |
| 6205433 | Boesch et al. | Mar 2001 | B1 |
| 6292786 | Deaton et al. | Sep 2001 | B1 |
| 6370514 | Messner | Apr 2002 | B1 |
| 6554184 | Amos | Apr 2003 | B1 |
| 6661466 | Kou | Dec 2003 | B1 |
| 6687679 | Van Luchene et al. | Feb 2004 | B1 |
| 6915271 | Meyer et al. | Jul 2005 | B1 |
| 6938013 | Gutierrez Sheris | Aug 2005 | B1 |
| 6999943 | Johnson et al. | Feb 2006 | B1 |
| 7050983 | Kawai | May 2006 | B2 |
| 7083087 | Gangi | Aug 2006 | B1 |
| 7213744 | Michelsen et al. | May 2007 | B2 |
| 7258268 | Steiger, Jr. | Aug 2007 | B2 |
| 7356505 | March | Apr 2008 | B2 |
| 7386518 | Cordery et al. | Jun 2008 | B2 |
| 7389256 | Adams et al. | Jun 2008 | B1 |
| 7406445 | Silverbrook et al. | Jul 2008 | B1 |
| 7490062 | Hansmann et al. | Feb 2009 | B2 |
| 7568615 | Corona et al. | Aug 2009 | B2 |
| 7647244 | Platner et al. | Jan 2010 | B2 |
| 7660734 | Neal et al. | Feb 2010 | B1 |
| 7668612 | Okkonen | Feb 2010 | B1 |
| 7693789 | Degen et al. | Apr 2010 | B2 |
| 7742942 | Nicholson | Jun 2010 | B2 |
| 7761344 | Smith | Jul 2010 | B2 |
| 7761367 | Scalora et al. | Jul 2010 | B1 |
| 7797192 | Mitchell et al. | Sep 2010 | B2 |
| 7810067 | Kaelicke et al. | Oct 2010 | B2 |
| 7810721 | Powell et al. | Oct 2010 | B2 |
| 7925513 | Chao et al. | Apr 2011 | B2 |
| 8019679 | Bennett | Sep 2011 | B2 |
| 8082210 | Hansen et al. | Dec 2011 | B2 |
| 8090594 | Grant et al. | Jan 2012 | B2 |
| 8108977 | Miller | Feb 2012 | B1 |
| 8566237 | Forzley | Oct 2013 | B2 |
| 8571980 | Greenwood | Oct 2013 | B1 |
| 8589918 | Csapuntzakis et al. | Nov 2013 | B1 |
| 8646685 | Bishop et al. | Feb 2014 | B2 |
| 8657688 | Zouiten et al. | Feb 2014 | B1 |
| 8688570 | Jones et al. | Apr 2014 | B2 |
| 8788278 | Scribner et al. | Jul 2014 | B2 |
| 8851366 | Modi | Oct 2014 | B2 |
| 9076134 | Grovit et al. | Jul 2015 | B2 |
| 9092763 | Meszaros | Jul 2015 | B2 |
| 20010014868 | Herz et al. | Aug 2001 | A1 |
| 20010029467 | Yagihashi et al. | Oct 2001 | A1 |
| 20010039535 | Tsiounis et al. | Nov 2001 | A1 |
| 20020002505 | Kojima | Jan 2002 | A1 |
| 20020052778 | Murphy et al. | May 2002 | A1 |
| 20020055907 | Pater et al. | May 2002 | A1 |
| 20020062249 | Iannacci | May 2002 | A1 |
| 20020091603 | Steiger et al. | Jul 2002 | A1 |
| 20020111908 | Milberger et al. | Aug 2002 | A1 |
| 20020143566 | Diveley | Oct 2002 | A1 |
| 20020152177 | Wolf | Oct 2002 | A1 |
| 20020179401 | Knox et al. | Dec 2002 | A1 |
| 20030080185 | Werther | May 2003 | A1 |
| 20030083891 | Lang et al. | May 2003 | A1 |
| 20030110072 | Delurgio et al. | Jun 2003 | A1 |
| 20030120590 | Ieshima et al. | Jun 2003 | A1 |
| 20030130883 | Schroeder et al. | Jul 2003 | A1 |
| 20030130948 | Algiene et al. | Jul 2003 | A1 |
| 20030182228 | Wolf | Sep 2003 | A1 |
| 20030208384 | Nelson et al. | Nov 2003 | A1 |
| 20030208440 | Harada et al. | Nov 2003 | A1 |
| 20030220830 | Myr | Nov 2003 | A1 |
| 20040030647 | Hansen et al. | Feb 2004 | A1 |
| 20040107146 | Alfano | Jun 2004 | A1 |
| 20040143496 | Saenz | Jul 2004 | A1 |
| 20040167815 | DeLaHunt | Aug 2004 | A1 |
| 20040172358 | Lent et al. | Sep 2004 | A1 |
| 20040199462 | Starrs | Oct 2004 | A1 |
| 20040205023 | Hafer et al. | Oct 2004 | A1 |
| 20040230527 | Hansen et al. | Nov 2004 | A1 |
| 20040241627 | Delfing | Dec 2004 | A1 |
| 20050131816 | Britto et al. | Jun 2005 | A1 |
| 20050177496 | Blagg et al. | Aug 2005 | A1 |
| 20050209961 | Michelsen et al. | Sep 2005 | A1 |
| 20050246268 | Foran et al. | Nov 2005 | A1 |
| 20060047672 | Habon et al. | Mar 2006 | A1 |
| 20060074627 | Moore et al. | Apr 2006 | A1 |
| 20060136907 | Bennett et al. | Jun 2006 | A1 |
| 20060191994 | Steiger | Aug 2006 | A1 |
| 20060242154 | Rawat et al. | Oct 2006 | A1 |
| 20060253321 | Heywood | Nov 2006 | A1 |
| 20060261150 | Seifert et al. | Nov 2006 | A1 |
| 20060287953 | Chauhan | Dec 2006 | A1 |
| 20070033112 | Nagle, Jr. | Feb 2007 | A1 |
| 20070073617 | Tolbert et al. | Mar 2007 | A1 |
| 20070088010 | Huebler et al. | Apr 2007 | A1 |
| 20070088610 | Chen | Apr 2007 | A1 |
| 20070108271 | Degen et al. | May 2007 | A1 |
| 20070121843 | Atazky et al. | May 2007 | A1 |
| 20070203821 | DuFour | Aug 2007 | A1 |
| 20070221728 | Ferro et al. | Sep 2007 | A1 |
| 20070233615 | Tumminaro | Oct 2007 | A1 |
| 20070255662 | Tumminaro | Nov 2007 | A1 |
| 20070294116 | Stephens et al. | Dec 2007 | A1 |
| 20080033870 | Gutierrez-Sheris | Feb 2008 | A9 |
| 20080046381 | Naccache | Feb 2008 | A1 |
| 20080109279 | Csoka | May 2008 | A1 |
| 20080140568 | Henry | Jun 2008 | A1 |
| 20080147506 | Ling | Jun 2008 | A1 |
| 20080154719 | Gounares et al. | Jun 2008 | A1 |
| 20080249908 | Lorberg et al. | Oct 2008 | A1 |
| 20080275771 | Levine | Nov 2008 | A1 |
| 20080301040 | Knudson et al. | Dec 2008 | A1 |
| 20090006205 | Bixler et al. | Jan 2009 | A1 |
| 20090006233 | Chemtob | Jan 2009 | A1 |
| 20090006549 | Singh et al. | Jan 2009 | A1 |
| 20090037311 | Omar | Feb 2009 | A1 |
| 20090048980 | Hubsher | Feb 2009 | A1 |
| 20090063261 | Scribner et al. | Mar 2009 | A1 |
| 20090063331 | Rodin | Mar 2009 | A1 |
| 20090067331 | Watsen et al. | Mar 2009 | A1 |
| 20090089172 | Quinlan et al. | Apr 2009 | A1 |
| 20090089869 | Varghese | Apr 2009 | A1 |
| 20090100168 | Harris | Apr 2009 | A1 |
| 20090106149 | Bennett et al. | Apr 2009 | A1 |
| 20090157520 | Algiene et al. | Jun 2009 | A1 |
| 20100100426 | Sander et al. | Apr 2010 | A1 |
| 20100100477 | Giammanco | Apr 2010 | A1 |
| 20100114774 | Linaman et al. | May 2010 | A1 |
| 20100153225 | Ferro et al. | Jun 2010 | A1 |
| 20100161485 | Bulawa et al. | Jun 2010 | A1 |
| 20100235283 | Gerson | Sep 2010 | A1 |
| 20100293113 | Munzer et al. | Nov 2010 | A1 |
| 20100299761 | Shapiro | Nov 2010 | A1 |
| 20110137796 | Tullis | Jun 2011 | A1 |
| 20110213653 | Mesaros | Sep 2011 | A1 |
| 20110246328 | Dunwoody et al. | Oct 2011 | A1 |
| 20110282790 | Bennett et al. | Nov 2011 | A1 |
| 20110313920 | Trickel | Dec 2011 | A1 |
| 20120010993 | Ferrara et al. | Jan 2012 | A1 |
| 20120016795 | Hill et al. | Jan 2012 | A1 |
| 20120030098 | Bulawa et al. | Feb 2012 | A1 |
| 20120036071 | Fulton et al. | Feb 2012 | A1 |
| 20120209769 | Rolfs | Aug 2012 | A1 |
| 20120245987 | Isaacson et al. | Sep 2012 | A1 |
| 20120303524 | Bertram et al. | Nov 2012 | A1 |
| 20130060690 | Oskolkov et al. | Mar 2013 | A1 |
| 20130132067 | Gelbman | May 2013 | A1 |
| 20130151418 | Licciardello et al. | Jun 2013 | A1 |
| 20130191194 | Shreibati et al. | Jul 2013 | A1 |
| 20130282561 | Runkle et al. | Oct 2013 | A1 |
| 20130325720 | Bennett et al. | Dec 2013 | A1 |
| 20140095384 | Basha | Apr 2014 | A1 |
| 20140207664 | Sander et al. | Jul 2014 | A1 |
| 20140213345 | Zouiten et al. | Jul 2014 | A1 |
| 20140244414 | Runkle et al. | Aug 2014 | A1 |
| 20140250014 | Runkle et al. | Sep 2014 | A1 |
| 20140278900 | Scribner et al. | Sep 2014 | A1 |
| 20140279228 | Fry et al. | Sep 2014 | A1 |
| 20150039499 | Christopherson et al. | Feb 2015 | A1 |
| 20150149355 | Arnthong et al. | May 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 1866861 | Dec 2007 | EP |
| WO9116691 | Oct 1991 | WO |
| WO0146778 | Jun 2001 | WO |
| WO2009052365 | Apr 2009 | WO |
| Entry |
|---|
| Elham Ramezani, Mobile Payment, Jun. 2008, E-Business Technology, web, 1-18 (Year: 2008). |
| Banorte Selects Moneygram for US Transfers—Mexico, Apr. 17, 2002, Business News Americas—Latin America's Business Information Leader, 1 page. |
| Information on MoneyGram.com 2003-2006, archived web pages printed from www.archive.org, date is in the URL in YYYYMMDD format. |
| International Search Report and Written Opinion issued in PCT/US2008/080292, dated Jan. 20, 2009 , 14 pages. |
| International Search Report and Written Opinion issued in PCT/US2012/022491, dated Jul. 5, 2012, 10 pages. |
| International Search Report and Written Opinion issued in PCT/US2012/038607, dated Nov. 13, 2012, 20 pages. |
| MoneyGram Adds 1,500 Bancomer Locations in Mexico, Apr. 17, 2001, 2 pages. |
| MoneyGram Corporate—How to transfer money, MoneyGram.International, webpages from http://www.moneygram.com/MGICorp/ConsumerProducts . . . , 5 Pages; May 30, 2007. |
| Press release from Norkom Technologies, “Wall Street's Back Office Launches Market-Leading AML software from Norkom,” Feb. 15, 2007, 2 pp., http://www.norkom.com. |
| International Search Report and Written Opinion issued in PCT/US2013/037595, dated Jul. 30, 2013, 11 pages. |
| Listingbook, LLC v. Market Leader, Inc., F.Supp.3d (2015), Westlaw 2015 WL 7176455, 12 pages. |
| “Money Transmitter Services”, snapshot taken Oct. 2011, http://web.archive.org/web/20111 0121 00544/http://www.dfs.ny.gov/consumer/usingamoneytrans.htm, 2 pages. |
| Dr. Manuel Orozco. “The Remittance Marketplace: Prices, Policy and Financial Institutions.” Pew Hispanic Center, Jun. 2004, 45 pages. |
| “Authoring Techniques for Device Independence W3C Woking Group Note”, Feb. 18, 2004, 57 pages. |
| Lorna Priest, “Keyboard Installation and Use”, Feb. 2009, available at https://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=keyboardinstallationanduse (Year: 2009), 12 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20130179334 A1 | Jul 2013 | US |
