High-security E-currency IDs for E-commerce transactions

• US 20020032649A1
• Filed: 04/11/2001
• Published: 03/14/2002
• Est. Priority Date: 04/13/2000
• Status: Abandoned Application

• Current Assignee: Selvarajan, Balamurugan
• Original Assignee: Selvarajan, Balamurugan
• Inventors: Selvarajan, Balamurugan
• Application Number:
  US09/833,468
• Publication Number:
  US 20020032649A1
• Time in Patent Office: Days
• US Class Current: 705/40
• CPC Class Codes: G06Q 20/06 Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
• 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/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]

Abstract

E-currency ID provides a highly secure, single-usage ‘virtual card’ that can be used for purchase on the Internet, while maintaining user privacy, security and control. Anytime the user needs to use a credit card on the Internet, they can use a unique e-currency ID instead. No actual card information is transmitted to the vendor and the e-currency ID cannot be reused, thus providing security against misuse of information even if the vendor'"'"'s security system is breached. The user can optionally setup for notification and confirmation, wherein all request from vendors for payment authorization are sent to the user (notification) and are only authorized after user approval (confirmation). The invention also provides capability for setting up recurring payments using e-currency Ids.

Claims

1. A method for making payments on the Internet, comprising:

a user obtaining a unique ID from a Service Provider when said user wants to make a payment on the Internet;

said user communicating said ID to a vendor in place of a credit card; and

said vendor completing or rejecting the transaction by communicating with said Service Provider.

2. The method of claim 1, the method further comprising said user registering with said Service Provider and obtaining a Client from said service Provider all prior to the step of a user obtaining a unique ID.

3. The method of claim 1, wherein before the step of completing the transaction, said method further comprising:

said Service Provider validating said unique ID and account balances of said user and completing said payment only if said unique ID is valid and has not expired and said user balances are adequate; and

said Service Provider sending acceptance to the vendor.

4. The method of claim 1, wherein before the step of rejecting the transaction, the method further comprising said Service Provider validating said unique ID and account balances of said user and sending a rejection to said vendor if said user balances are inadequate or said unique ID is invalid or has expired.

5. The method of claim 1, wherein said ID has a preset timeout, wherein after said preset timeout expires, said ID will not be approved by said Service Provider, and once used, said ID will not be approved again by said Service Provider.

6. The method of claim 2, wherein said Service Provider Client has at least one mode of operation selected from the group consisting of a notification mode, a confirmation mode, a card reader mode and a recurring payment mode.

7. The method of claim 6, further comprising operating said Client in said notification mode, wherein anytime a vendor requests validation of an ID, said Service Provider notifies said user.

8. The method of claim 6, further comprising operating said Service Provider client in said confirmation mode, wherein anytime said vendor requests validation of a ID generated by said user, a confirmation is requested from said user, wherein only after said user authorizes the transaction does said Service Provider provide approval for said transaction.

9. The method of claim 6, further comprising operating said Client in said card reader mode, wherein said Client works only after said user inserts a service card into a special reader attached to a PC.

10. The method of claim 6, further comprising operating said VCSP client in said recurring payment mode, wherein recurring payment information needed to complete a recurring transaction is stored at said Service Provider, wherein a request from said vendor that provides a previously used ID acts as a trigger for said recurring transaction.

11. The method of claim 2, wherein said Client has the capability to record payment details into desktop or web-based personal finance tools.

12. The method of claim 2, wherein said Client is a separate application interacting with a browser.

13. The method of claim 2, wherein said Client comprises code running on a browser.

14. The method of claim 2, wherein said Client is entirely web based.

15. The method of claim 1, wherein said Service Provider includes a server that stores user settings.

16. A method for completing a secure e-commerce transaction between a customer and a vendor, both connected to a network, while protecting information even if vendor'"'"'s security is breached and providing end-to-end user control, comprising:

obtaining a single use ID from a Service Provider (SP) when a customer is ready to place an order;

transmitting said ID to a vendor in place of credit card information or bank account information of said customer;

sending information from said SP to said customer system when said vendor requests payment and taking user confirmation; and

sending acceptance/rejection to said vendor from said SP after validating customer balances.