Remote payment method and system

• US 20020152179A1
• Filed: 10/25/2001
• Published: 10/17/2002
• Est. Priority Date: 10/27/2000
• Status: Abandoned Application

• Current Assignee: ICOM Mobile Limited
• Original Assignee: ICOM Mobile Limited
• Inventors: Racov, Achiezer
• Application Number:
  US10/033,154
• Publication Number:
  US 20020152179A1
• Time in Patent Office: Days
• US Class Current: 705/67
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/32 using wireless devices
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/3674 involving authentication

Abstract

A computer-based method and system for effecting a remote payment transaction involving the use of a mobile communications device. Using the described system and the communications device, a customer may electronically purchase goods, services, remit payments, track loyalty bonuses and effect enhanced personal financial account management with less effort, increased convenience and user-authorized security features for account access and manipulation. Using a mobile communications device, the customer instructs the remote payment system to provide funds to a merchant, where the funds are transferred from a customer account to a merchant account. If desired, the system automatically manages the value of these accounts by interacting with external financial accounts, such as bank accounts. The system also monitors transaction frequency and average account value to calculate a bonus to reward the customer'"'"'s loyalty.

Claims

1. A computer-based remote payment transaction system comprising:

a server operated by a service provider, said server including a data memory for storing two or more server accounts, said server accounts including a first party server account and a second party server account, said server configured to;

(a) establish the first party server account using an account registration subsystem;

(b) authenticate an authorized user of the first party server account using an authentication subsystem;

(c) receive an electronic payment instruction via a mobile communications device from the authorized user, said payment instruction requesting that a purchase value be transferred from the first party server account to the second party server account;

(d) notify the authorized user via the mobile communications device that the payment instruction was received;

(e) transfer the requested payment value from the first party server account to the second party server account;

(f) receive an electronic transfer instruction via the mobile communications device from the authorized user, said transfer instruction ordering that a requested value be transferred from an account associated with the first party at a first financial institution to the first party server account;

(g) add the requested value to the first party server account;

(h) instruct the financial institution to transfer funds corresponding to the requested value from the first party financial institution account to an account associated with the service provider at a second financial institution;

(i) update the data memory; and

(j) provide a reward for using the server via a customer loyalty subsystem.

2. The remote payment system of claim 1, wherein the mobile communications device is configured to:

(a) generate a signal for transmitting the electronic payment instruction to the server;

(b) generate a signal for transmitting the electronic transfer instruction to the server;

(c) transmit caller identification information to the server;

(d) display first party server account information; and

(e) receive a signal representing a confirmation receipt for the payment transaction from the server.

3. The remote payment system of claim 2, wherein the first financial institution and the second financial institution are the same financial institution.

4. The remote payment system of claim 1, wherein the server is configured to notify the authorized user that the server received the electronic payment instruction using a secure communications link to the mobile communications device.

5. The remote payment system of claim 1, wherein the mobile communications device comprises a mobile phone or a personal digital assistant.

6. The remote payment system of claim 1, wherein the server authentication subsystem is configured to:

(a) store an authentication credential established by the authorized user, where the authorized user accesses the server to request the payment instruction secured by the authentication credential, wherein the authentication credential is;

(i) in existence at the server prior to the payment request, and

(ii) a unique identifier of the authorized user;

(b) solicit a response associated with the payment transaction via a challenge, where the challenge is transmitted by the server to the authorized user;

(c) accept an answer to the challenge from the authorized user; and

(d) transmit the authorization credential from the server to the mobile communications device following a determination by the server that the answer satisfies the challenge,

wherein the authentication subsystem is operable in a repeatable, on-demand manner by the authorized user using the communications device.

7. The remote payment system of claim 6, wherein the server authentication subsystem is further configured to use the authentication credential to allow the authorized user to proceed with the payment transaction.

8. The remote payment system of claim 6, wherein the server authentication subsystem is further configured to implement a security rules engine for authenticating the payment instruction, wherein if the payment instruction is determined to be non-authentic, the engine requests further information from the authorized user to authenticate the instruction.

9. The remote payment system of claim 6, wherein the server is configured to receive input via biometric techniques, said biometric techniques including voice recognition or signature recognition.

10. The remote payment system of claim 1, wherein the server is configured to update a server ledger account to reflect a change in the total funds available in all server accounts affected by the payment transaction.

11. The remote payment system of claim 1, wherein the server customer loyalty subsystem includes a data warehouse that is configured to:

(a) receive account usage information from the data memory, the usage information including average account balance or transaction frequency that is associated with a first party account on the server;

(b) compile and analyze the usage information to calculate a loyalty award;

(c) convert the loyalty award into airtime minutes;

(d) transmit the airtime minutes to a telecommunications account; and

(e) transmit usage information to the authorized user via the mobile communications device.

12. The remote payment system of claim 11, wherein the server receives from the first party a request to transfer the loyalty award to a third party server account from the first party server account, wherein said third party is an authorized user of a third party server account.

13. The remote payment system of claim 11, wherein the telecommunications account is associated with the first party.

14. The remote payment system of claim 11, wherein the telecommunications account is associated with one or more beneficiary parties.

15. The remote payment system of claim 11, wherein the server customer loyalty subsystem is further configured to:

(f) store the loyalty award information within the loyalty data warehouse on the server; and

(g) periodically receive the usage information from the data memory.

16. The remote payment system of claim 1, wherein the payment transaction cannot be repudiated by the first party.

17. The remote payment system of claim 1, wherein the payment transaction cannot be repudiated by the second party.

18. The remote payment system of claim 1, wherein the first party is a customer.

19. The remote payment system of claim 1, wherein the second party is a merchant.

20. A computer-based remote payment transaction system via the Internet comprising:

a server operated by a service provider, said server including a data memory for storing one or more server accounts, said server accounts including a first party server account and a second party server account, said server configured to;

(a) establish the first party server account and the second party server account using an account registration subsystem;

(b) generate a unique reference code for a payment transaction upon a request of a second party, after the second party receives a purchase request from the first party via the Internet;

(c) provide the unique reference code to the second party;

(d) answer an incoming call from the first party to a second party phone number dedicated to the second party;

(e) receive a first party personal identification number linked to the first party server account for authenticating the first party as an authorized user of the first party server account;

(f) receive a transaction amount and the unique reference code from the first party for the payment transaction, wherein the server is configured to automatically match the unique reference code received from the first party to the unique reference code generated upon the request of the second party; and

(g) transfer the payment from the first party server account to the second party server account.

21. A computer-based remote payment transaction method using a server operated by a service provider, said server including a data memory for storing two or more server accounts, said server accounts including a first party server account and a second party server account, comprising the steps of:

(a) establishing the first party server account using an account registration subsystem;

(b) authenticating an authorized user of the first party server account using an authentication subsystem;

(c) receiving an electronic payment instruction via a mobile communications device from the authorized user, said payment instruction including a payment value to be transferred from the first party server account to the second party server account;

(d) notifying the authorized user via the mobile communications device that the payment instruction was received;

(e) transferring the requested payment value from the first party server account to the second party server account;

(f) receiving an electronic transfer instruction via the mobile communications device from the authorized user, said transfer instruction ordering that a requested value be transferred from an account associated with the first party at a first financial institution to the first party server account;

(g) adding the requested value to the first party server account;

(h) instructing the financial institution to transfer funds corresponding to the requested value from the first party financial institution account to an account associated with the service provider a second financial institution;

(i) updating the data memory; and

(j) providing a reward for using the server via a customer loyalty subsystem.

22. The remote payment method of claim 21, wherein the mobile communications device is configured to:

(a) generate a signal for transmitting the electronic payment instruction to the server;

(b) generate a signal for transmitting the electronic transfer instruction to the server;

(c) transmit caller identification information to the server;

(d) display first party server account information; and

(e) receive a signal representing a confirmation receipt for the payment transaction from the server.

23. The remote payment method of claim 22, wherein the first financial institution and the second financial institution are the same financial institution.

24. The remote payment method of claim 21, wherein the notifying step further comprises using a secure communications link to the mobile communications device.

25. The remote payment method of claim 21, wherein the mobile communications device comprises a mobile phone or a personal digital assistant.

26. The remote payment method of claim 21, wherein the authenticating step further comprises:

(a) storing an authentication credential established by the authorized user, where the authorized user accesses the server to request the payment instruction secured by the authentication credential, the authentication credential is;

(i) in existence at the server prior to the payment request, and

(ii) a unique identifier for the authorized user;

(b) soliciting a response associated with the payment transaction via a challenge, where the challenge is transmitted by the server to the authorized user;

(c) accepting an answer to the challenge from the authorized user; and

(d) transmitting the authorization credential from the server to the authorized user following a determination by the server that the answer satisfies the challenge,

wherein the authenticating step is operable in a repeatable, on-demand manner by the authorized user using the mobile communications device.

27. The remote payment method of claim 26, wherein the authenticating step further comprises using the authentication credential to allow the authorized user to proceed with the payment transaction.

28. The remote payment method of claim 26, wherein the authenticating step further comprises using a security rules engine for authenticating the payment instruction, wherein if the payment instruction is determined to be non-authentic, the engine requests further information from the authorized user to authenticate the instruction.

29. The remote payment method of claim 26, wherein the server receives input via biometric techniques, said biometric techniques including voice recognition or signature recognition.

30. The remote payment method of claim 26, further comprising updating a server ledger account to reflect a change in the total funds available in all server accounts affected by the payment transaction.

31. The remote payment method of claim 26, wherein the providing a reward step further comprises using a data warehouse for:

(a) receiving account usage information from the data memory, the usage information including average account balance or transaction frequency that is associated with a first party account stored on the server;

(b) compiling and analyzing the usage information to calculate a loyalty award;

(c) converting the loyalty award into minutes;

(d) transmitting the airtime minutes to a telecommunications account; and

(e) transmitting usage information to the authorized user.

32. The remote payment method of claim 31, wherein the server receives from the first party a request to transfer the loyalty award to a third party server account from the first party server account, wherein said third party is an authorized user of a third party server account.

33. The remote payment method of claim 31, wherein the telecommunications account is associated with the first party.

34. The remote payment method of claim 31, wherein the telecommunications account is associated with one or more beneficiary parties.

35. The remote payment method of claim 31, wherein the providing a reward step further comprises:

(f) storing the loyalty award information within the loyalty data warehouse on the server; and

(g) periodically receiving the usage information from the data memory.

36. The remote payment method of claim 21, wherein the payment transaction cannot be repudiated by the first party.

37. The remote payment method of claim 21, wherein the payment transaction cannot be repudiated by the second party.

38. The remote payment method of claim 21, wherein the first party is a customer.

39. The remote payment method of claim 21, wherein the second party is a merchant.

40. A computer-based remote payment transaction method via the Internet using a server operated by a service provider, said server including a data memory for storing one or more server accounts, said server accounts including a first party server account and a second party server account, comprising the steps of:

(a) establishing the first party server account and the second party server account using an account registration subsystem;

(b) generating a unique reference code for the payment transaction upon request of a second party, after the second party receives a purchase request from the first party via the Internet;

(c) providing the unique reference code to the second party;

(d) answering an incoming call from the first party to a second party phone number dedicated to the second party;

(e) receiving a first party personal identification number linked to the first party server account for authenticating the first party as an authorized user of the first party server account;

(f) receiving a transaction amount and the unique reference code from the first party for the payment transaction, wherein the server is configured to automatically match the unique reference code received from the first party to the unique reference code generated upon the request of the second party; and

(g) transferring the payment from the first party server account to the second party server account.