METHOD AND SYSTEM FOR AUTHORIZING A FUNDS TRANSFER OR PAYMENT USING A PHONE NUMBER

• US 20070179885A1
• Filed: 01/30/2007
• Published: 08/02/2007
• Est. Priority Date: 01/30/2006
• Status: Abandoned Application

• Current Assignee: CPNI, Inc.
• Original Assignee: CPNI, Inc.
• Inventors: Nayak, Biswajit, Bird, Terrence Patrick, Berhan, Siraj
• Application Number:
  US11/668,665
• Publication Number:
  US 20070179885A1
• Time in Patent Office: Days
• US Class Current: 705/39
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: H04M 2203/105 Financial transactions and auctions, e.g. bidding
• CPC Class Codes: H04M 3/4938 comprising a voice browser which renders and interprets, e.g. VoiceXML

Abstract

A system and method for phone authorized transfers and/or payments are described. The system generates and authorizes instructions for funds transfers and payments between sender and recipient of participating institutions. The participating institutions of the sender and recipient of the funds transfer/payment may be the same or different, and may be located within the same or different countries. The system and method generates and authorizes funds transfer/payment instructions using the phone number of the recipient as identifying information and without providing banking particulars of the recipient. In some embodiments, the system implements an interactive voice response (IVR) application allowing a user to interact with the system using voice prompts responsive to the user'"'"'s spoken response in the telephone receiver or the user input on the keypad of the user'"'"'s touch-tone wired or wireless telephone. In some embodiments, the phone number of either or both of the sender and recipient may be shared among multiple users.

Claims

1. A phone authorized transfer and/or payment system for generating funds transfer instructions between a sender and a recipient, each of the sender and recipient having a phone number registered with the system and stored within a respective customer database, the system comprising:

a first telephone application gateway server comprising a processor operatively connected to a memory, the memory having data and instructions stored thereon to configure the first telephone application gateway server to implement an interactive voice response (IVR) application for interfacing with a sender and to;

request and receive a funds transfer request from the sender via a call received by the IVR application, the funds transfer request comprising at least an amount for transfer (the “

transaction amount”

) and a phone number of the recipient;

determine the sender'"'"'s phone number;

verify the determined sender'"'"'s phone number against registered phone numbers in a first customer database connected to the first telephone application gateway server; and

if the determined sender'"'"'s phone number is verified,

determine a first proxy identifier (ID) associated with at least the determined sender'"'"'s phone number from the first customer database; and

send to a first transaction instruction server managed by a first participating institution a first funds transfer request to transfer funds from an account of the sender at the first participating institution to an outgoing settlement account of the first participating institution, wherein the first funds transfer request includes the first proxy ID as a pointer to the account of the sender from which the funds are to be transferred, the first funds transfer request instructing the first transaction instruction server to generate a first funds transfer instruction.

2. The system of claim 1, wherein the determining of the first proxy ID comprises:

determining a first unique user identifier (ID) corresponding to the sender'"'"'s phone number from a mapping of unique user IDs to phone numbers in the first customer database; and

determining the first proxy ID from the first unique user ID from a mapping of unique user IDs to first proxy IDs in the first customer database.

3. The system of claim 1, wherein the first telephone application gateway server is further configured to:

if the determined sender'"'"'s phone number is not verified, terminate the call.

4. The system of claim 1, wherein the first telephone application gateway server is further configured to:

determine a second proxy identifier (ID) associated with the phone number of the recipient received by the IVR application; and

request the first transaction instruction server to send to a second transaction instruction server managed by a second participating institution a second funds transfer request to transfer funds to an account of the recipient at the second participating institution from an incoming settlement account of the second participating institution, wherein the second funds transfer request includes the second proxy ID as a pointer to the account of the recipient to which the funds are to be transferred, the second funds transfer request instructing the second transaction instruction server to generate a second funds transfer instruction.

5. The system of claim 4, wherein the determining of the second proxy ID comprises:

determining a second unique user identifier (ID) corresponding to the recipient'"'"'s phone number from a mapping of unique user IDs to phone numbers in the first customer database if recipient'"'"'s phone number is stored within the first customer database, or a second customer database associated with and connected to another telephone application gateway server if recipient'"'"'s phone number is not stored within the first customer database; and

determining the second proxy ID from the second unique user ID from a mapping of unique user IDs to second proxy IDs in the first or second customer database.

6. The system of claim 5, wherein the first telephone application gateway server is further configured to:

identify the first and second transaction instruction servers using addressing information associated with the first and second proxy IDs stored in the respective customer databases.

7. The system of claim 5, wherein the mapping of unique user IDs to phone numbers and the mapping of unique user IDs to proxy IDs are provided by a common mapping in the respective customer databases.

8. The system of claim 7, wherein the first and second customer databases each comprise mappings of phone numbers to unique user ID to proxy IDs for registered users.

9. The system of claim 8, wherein the first and second customer databases further comprise a mapping of proxy IDs to an address of the associated transaction instruction server.

10. The system of claim 5, further comprising:

the first transaction instruction server, the first transaction instruction server comprising a processor operatively connected to a memory, the memory having data and instructions stored thereon to configure the first transaction instruction server to;

receive the first funds transfer request from the telephone application gateway server;

determine an account number of the sender from the first proxy ID in the first funds transfer request using a mapping of proxy IDs to account numbers in a database associated with the first transaction instruction server;

generate the first funds transfer instruction to transfer an amount from the account number of the sender to the outgoing settlement account of the first participating instruction; and

post the first funds transfer instruction to a first electronic settlement system of the first participating institution.

11. The system of claim 10, further comprising:

the second transaction instruction server, the second transaction instruction server comprising a processor operatively connected to a memory, the memory having data and instructions stored thereon to configure the second transaction instruction server to;

receive the second funds transfer request from the first transaction instruction server;

determine an account number of the sender from the second proxy ID in the second transfer request using a mapping of proxy IDs to account numbers in a database associated with the first or second transaction instruction server;

generate the second funds transfer instruction to transfer an amount to the account number of the recipient from the incoming settlement account of the second participating instruction; and

post the second funds transfer instruction to a second electronic settlement system of the second participating institution.

12. The system of claim 11, further comprising:

a first electronic settlement system of the first participating instruction, a second electronic settlement system of the second participating instruction, and a communications network connecting the first electronic settlement system and second electronic settlement system;

the first electronic settlement system being configured to transfer funds from the account number of the sender to the outgoing settlement account of the first participating institution in accordance with posted first funds transfer instruction;

the second electronic settlement system being configured to transfer funds to the account number of the recipient from the incoming settlement account of the second participating institution in accordance with posted second funds transfer instructions;

the first and second electronic settlement systems being configured to transfer funds between the outgoing settlement account and the incoming settlement account of each of the first and second participating institutions.

13. The system of claim 4, wherein the first and second participating institutions are the same or different, the first and second transaction instruction servers of the first and second participating institutions being the same or different, respectively.

14. The system of claim 1, wherein the IVR application implemented by the first telephone application gateway server is further configured to request and receive from the sender a currency for transfer if the currency of the sender'"'"'s account and recipient account are different.

15. The system of claim 1, wherein the IVR application implemented by the first telephone application gateway server is further configured to request and receive from the sender a personal user identifier, and wherein the first telephone application gateway server is further configured to:

verify if the personal user identifier received by the IVR application matches a personal user identifier stored in the first customer database; and

if the personal user identifier matches, determine the first proxy ID.

16. The system of claim 15, wherein the first telephone application gateway server is further configured to:

if the personal user identifier does not match, repeat the requesting and receiving of the personal user identifier until the personal user identifier matches or until a pre-determined number of failures to match has occurred.

17. The system of claim 15, wherein the first unique user ID is determined using the determined phone number and the verified personal user identifier using a mapping of unique user IDs to phone numbers and personal user identifiers.

18. The system of claim 4, further comprising:

a plurality of telephone application gateway servers; and

a routing system connected to the first telephone application gateway server and the plurality of telephone application gateway servers, the routing system comprising a central repository containing mappings of phone numbers to respective telephone application gateway server addresses for all users registered with the system;

wherein the first telephone application gateway server is further configured to;

if the recipient'"'"'s phone number is not stored within the first customer database, request from the routing system the address of the telephone application gateway server associated with the recipient'"'"'s phone number; and

wherein the routing system is configured to provide the address of the telephone application gateway server associated with the recipient'"'"'s phone number in response to a request from the first telephone application gateway server.

19. The system of claim 18, wherein the first telephone application gateway server is further configured to:

if the recipient'"'"'s phone number is not stored within the first customer database, request from the telephone application gateway server associated with the recipient'"'"'s phone number the second proxy ID associated with the recipient'"'"'s phone number.

20. The system of claim 18, wherein the central repository is a global repository containing mappings of domestic and international phone numbers to the respective telephone application gateway server addresses.

21. The system of claim 5, wherein the first telephone application gateway server is further configured to:

determine if the recipient'"'"'s phone number is associated with more than one unique user ID in the first or second customer database;

if the recipient'"'"'s phone number is associated with more than one unique user ID in the first or second customer database, provide a list of shared user names to the sender;

receive an input from the sender selecting the recipient from the list of shared user names; and

determine the second unique user ID from the mapping of unique user IDs to phone numbers in the first or second customer database in accordance with the input from the sender.

22. The system of claim 21, wherein the first telephone application gateway server is further configured to associate the input from the sender selecting the recipient from the list of shared user names with the respective second unique user ID.

23. The system of claim 21, wherein the first telephone application gateway server is further configured to:

if the recipient'"'"'s phone number is not associated with more than one unique user ID, determine the second unique user ID corresponding to the recipient'"'"'s phone number from a mapping of unique user IDs to phone numbers in the first or second customer database without providing a list of shared user names or requesting an input from the sender.

24. A method for generating funds transfer instructions between a sender and a recipient in a phone authorized transfer and/or payment system, each of the sender and recipient having a phone number registered with the system and stored within a respective customer database, the method comprising the steps of:

receiving an identifier associated with the sender;

receiving from the sender a funds transfer request on a first server, the funds transfer request comprising at least an amount for transfer (the “

transaction amount”

) and a phone number as identifying information of a recipient to which the funds are to be transferred;

determining a first proxy identifier (ID) associated with the identifier of the sender;

sending to a first transaction instruction server instructions to generate funds transfer instructions associated with the first proxy ID; and

generating first funds transfer instructions on the first transaction instruction server, the first funds transfer instructions including the first proxy ID as a pointer to an account of the sender at a first participating institution from which the funds are to be transferred.

25. The method of claim 24, further comprising, after the step of receiving the funds transfer request, the step of:

determining a first unique user identifier (ID) corresponding to the identifier of the sender, wherein the step of determining the first proxy ID comprises determining the first proxy ID from a mapping of unique user IDs to proxy IDs.

26. The method of claim 25, wherein the first unique user ID is determined from the phone number of the sender and a personal user identifier provided with the funds transfer request.

27. The method of claim 24, further comprising the step of determining an address of the first transaction instruction server from a mapping of proxy IDs to server addresses.

28. The method of claim 24, wherein the step of generating the first funds transfer instructions comprises:

generating first funds transfer instructions to transfer funds from the account of the sender at the first participating to an outgoing settlement account of the first participating institution.

29. The method of claim 24, further comprising the steps of:

determining a second proxy identifier (ID) associated with the recipient'"'"'s phone number;

sending to a second transaction instruction server instructions to generate second funds transfer instructions associated with the second proxy ID; and

generating second funds transfer instructions on the second transaction instruction server, the second funds transfer instructions including the second proxy ID as a pointer to an account of the recipient at a second participating institution to which the funds are to be transferred.

30. The method of claim 29, further comprising the step of:

determining a second unique user identifier (ID) corresponding to the recipient'"'"'s phone number from a mapping of unique user IDs to registered phone numbers, wherein the step of determining the second proxy ID comprises determining the second proxy ID from a mapping of unique user IDs to second proxy IDs.

31. The method of claim 29, further comprising the step of determining an address of the second transaction instruction server from a mapping of proxy IDs to server addresses.

32. The method of claim 29, wherein the step of generating the second funds transfer instructions comprises:

generating second funds transfer instructions to transfer funds to the account of the recipient at the second participating institution from an incoming settlement account of the second participating institution.

33. The method of claim 29, wherein the first and second participating institutions are the same or different, the first and second transaction instruction servers of the first and second participating institutions being the same or different, respectively.

34. The method of claim 24, wherein the identifier of the sender is a phone number of the sender registered with the system, the method further comprising the step of determining the phone number of the sender, the first unique user ID being determined from a mapping of unique user IDs to registered phone numbers.

35. The method of claim 24, wherein the method is implemented via a graphical user interface on a display of a computing device.

36. The method of claim 24, wherein the method is implemented by an interactive voice response (IVR) application of a telephone application gateway server.

37. The method of claim 29, further comprising the steps of:

determining if the recipient'"'"'s phone number is associated with more than one unique user ID;

if the recipient'"'"'s phone number is associated with more than one unique user ID, providing a list of shared user names to the sender;

receiving an input from the sender selecting the recipient from the list of shared user names; and

determining the second unique user ID from the mapping of unique user IDs to phone in accordance with the input from the caller.

38. The method of claim 37, further comprising the steps of:

if the recipient'"'"'s phone number is not associated with more than one unique user ID, determining the second unique user ID corresponding to the recipient'"'"'s phone number from a mapping of unique user IDs to phone numbers in the first or second customer database without providing a list of shared user names or requesting an input from the caller.

39. A system for generating funds transfer instructions between a sender and a recipient, each of the sender and recipient having a phone number registered with the system and stored within a respective customer database, the system comprising:

a first server having a processor operatively connected to a memory, the memory having data and instructions to configure the server to;

receive an identifier from a sender;

receive from the sender a funds transfer request, the funds transfer request comprising at least an amount for transfer (the “

transaction amount”

) and a phone number as identifying information of a recipient to which the funds are to be transferred;

determine a first proxy identifier (ID) associated with the identifier of the sender; and

send to a first transaction instruction server instructions to generate funds transfer instructions associated with the first proxy ID,

wherein the first transaction instruction server generates first funds transfer instructions, the first funds transfer instructions including the first proxy ID as a pointer to an account of the sender at a first participating institution from which the funds are to be transferred.

40. The system of claim 39, wherein the first server is configured to determine a first unique user identifier (ID) corresponding to the identifier of the sender, wherein the step of determining the first proxy ID comprises determining the first proxy ID from a mapping of unique user IDs to proxy IDs.

41. The system of claim 40, wherein the first server is configured to determine the first unique user ID from the phone number of the sender and a personal user identifier provided with the funds transfer request.

42. The system of claim 39, wherein the first server is further configured to determine an address of the first transaction instruction server from a mapping of proxy IDs to server addresses.

43. The system of claim 39, wherein the first transaction instruction server generating the first funds transfer instructions comprises:

generating first funds transfer instructions to transfer funds from the account of the sender at the first participating to an outgoing settlement account of the first participating institution.

44. The system of claim 39, wherein the first server is further configured to:

determine a second proxy identifier (ID) associated with the recipient'"'"'s phone number; and

send to a second transaction instruction server via the first transaction instruction server instructions to generate second funds transfer instructions associated with the second proxy ID,

wherein the second transaction instruction server generates second funds transfer instructions, the second funds transfer instructions including the second proxy ID as a pointer to an account of the recipient at a second participating institution to which the funds are to be transferred.

45. The system of claim 44, wherein the first server is further configured to determine a second unique user identifier (ID) corresponding to the recipient'"'"'s phone number from a mapping of unique user IDs to registered phone numbers, wherein the step of determining the second proxy ID comprises determining the second proxy ID from a mapping of unique user IDs to second proxy IDs.

46. The system of claim 44, wherein the first server is further configured to determine an address of the second transaction instruction server from a mapping of proxy IDs to server addresses.

47. The system of claim 44, wherein the second transaction instruction server generating second funds transfer instructions comprises:

generating second funds transfer instructions to transfer funds to the account of the recipient at the second participating institution from an incoming settlement account of the second participating institution.

48. The system of claim 44, further comprising:

the first transaction instruction server, the first transaction instruction server comprising a processor operatively connected to a memory, the memory having data and instructions stored thereon to configure the first transaction instruction server to;

receive the first funds transfer request from the first server;

determine an account number of the sender from the first proxy ID in the first funds transfer request using a mapping of proxy IDs to account numbers in a database associated with the first transaction instruction server;

generate the first funds transfer instruction to transfer an amount from the account number of the sender to the outgoing settlement account of the first participating institution; and

post the first funds transfer instruction to a first electronic settlement system of the first participating institution.

49. The system of claim 48, further comprising:

the second transaction instruction server, the second transaction instruction server comprising a processor operatively connected to a memory, the memory having data and instructions stored thereon to configure the second transaction instruction server to;

receive the second funds transfer request from the first transaction instruction server;

determine an account number of the recipient from the second proxy ID in the second transfer request using a mapping of proxy IDs to account numbers in a database associated with the second transaction instruction server;

generate the second funds transfer instruction to transfer an amount to the account number of the recipient from the incoming settlement account of the second participating institution; and

post the second funds transfer instruction to a second electronic settlement system of the second participating institution.

50. The system of claim 49, further comprising:

the first electronic settlement system of the first participating institution, the second electronic settlement system of the second participating institution, and a communications network connecting the first electronic settlement system and second electronic settlement system;

the first electronic settlement system being configured to transfer funds from the account number of the sender to the outgoing settlement account of the first participating institution in accordance with the posted first funds transfer instruction;

the second electronic settlement system being configured to transfer funds to the account number of the recipient from the incoming settlement account of the second participating institution in accordance with the posted second funds transfer instruction; and

the first and second electronic settlement system being configured to transfer funds between the outgoing settlement account and the incoming settlement account of each of the first and second participating institutions.

51. The system of claim 39, further comprising a user terminal for receiving input from the sender, the user terminal having a display having a graphical user interface (GUI) displayed thereon, wherein the user terminal is one of a wireless communication, personal computer or point-of-transfer (POT) terminal.

52. The system of claim 44, wherein the first and second participating institutions are the same or different, the first and second transaction instruction servers of the first and second participating institutions being the same or different, respectively.

53. The system of claim 39, wherein the identifier of the sender is a phone number of the sender registered with the system, the method further comprising the step of determining the phone number of the sender, the first unique user ID being determined from a mapping of unique user IDs to registered phone numbers.

54. A method for registering a user in a phone authorized transfer and/or payment system, the method comprising the steps of:

receiving a request to register the user on a telephone gateway application server for managing the user'"'"'s funds transfer communications, the request including a phone number of the user and a proxy identifier (ID) to an account of the user at a first participating institution from which funds are to be transferred;

generating a unique user identifier (ID) being unique at least within a customer database connected to the telephone gateway application server;

storing a mapping of the phone number of the user to the unique user ID to the proxy ID in the customer database; and

receiving an activation request from the user.

55. The method of claim 54, further comprising, after receiving an activation request from the user:

determining if the phone number of the user is shared with one or more other users; and

if the phone number of the user is shared,

requesting and receiving a personal user identifier from the user,

comparing the personal user identifier received from the user with the personal user identifier of the one or more other users with whom the phone number is shared, and

if the personal user identifier received from the user is not different from the personal user identifier of the one or more other users with whom the phone number is shared, repeating the requesting and receiving of the personal user identifier until the personal user identifier is different from the personal user identifier of the one or more other users with whom the phone number is shared.

56. The method of claim 55, wherein the personal user identifier requested from the user has a different structure than the personal user identifier of the one or more other users with whom the phone number is shared.

57. The method of claim 55, wherein the step of determining if the user'"'"'s phone number is shared comprises:

determining if an active user account is associated with the user'"'"'s phone number in the customer database, wherein the user'"'"'s phone number is shared if the user'"'"'s phone number is associated with a user account in the customer database, and wherein the user'"'"'s phone number is not shared if the user'"'"'s phone number is not associated with a user account in the customer database.

58. The method of claim 54, wherein the activation request includes a temporary personal user identifier provided by the system.

59. The method of claim 58, further comprising, after the step of receiving an activation request:

identifying the phone number from which the activation request was sent using a caller identification process;

comparing the identified phone number with phone numbers of inactivated accounts in the customer database; and

if the identified phone number is a phone number of an inactivated account in the customer database,

comparing the temporary personal user identifier provided in the activation request with the temporary personal user identifier stored in the customer database,

if the temporary personal user identifier provided in the activation request matches, activating the account of the user and propagating the phone number and unique user ID to a routing component of the payment system, and

if the temporary personal user identifier provided in the activation request does not match, repeating the requesting and receiving of the personal user identifier until the personal user identifier matches or until a pre-determined number of failures to match has occurred.

60. The method of claim 59, further comprising, before the step of receiving an activation request and after the step of generating a unique user ID, the step of sending a notification message to the user including the temporary personal user identifier.

61. The method of claim 60, wherein the notification message is a secure communication.

62. The method of claim 54, wherein the activation request includes a country-specific unique identifier provided by the user, the method further comprising:

if the identified phone number is a phone number of an inactivated account in the customer database, before activating the account of the user,

comparing the country-specific unique identifier provided in the activation request with a country-specific unique identifier stored in the customer database,

if the country-specific unique identifier provided in the activation request matches, activating the account of the user, and

if the temporary personal user identifier provided in the activation request does not match, repeating requesting and receiving of the personal user identifier until the personal user identifier matches or until a pre-determined number of failures to match has occurred.

63. A system for registering a user having a shared phone number in a phone authorized transfer system, the system comprising:

a telephone gateway application server for managing the user'"'"'s funds transfer communications, the telephone gateway application server being operatively connected to a customer database, the telephone gateway application server comprising a processor operatively connected to a memory, the memory having data and instructions stored thereon to configure the telephone gateway application server to;

receive a request to register the user, the request including a phone number of the user and a proxy identifier (ID) to an account of the user at a first participating institution from which funds are to be transferred;

generate a unique user identifier (ID) being unique at least within a customer database connected to the telephone gateway application server;

store a mapping of a phone number of the user to the unique user ID to the proxy ID in the customer database; and

receive an activation request from the user.