TRANSACTION METHOD AND APPARATUS

• US 20010014878A1
• Filed: 11/09/1998
• Published: 08/16/2001
• Est. Priority Date: 11/09/1998
• Status: Abandoned Application

• Current Assignee: AT&T Corporation (AT&T, Inc.)
• Original Assignee: AT&T Corporation (AT&T, Inc.)
• Inventors: MITRA, NILOTPAL, RONEN, YZHAK
• Application Number:
  US09/188,595
• Publication Number:
  US 20010014878A1
• Time in Patent Office: Days
• US Class Current: 705/39
• 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/385 using an alias or single-use codes
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]

Abstract

The invention provides a transaction system in a data network that permits transactions among a buyer, a seller, and a billing device to occur independently. The transaction system may include authorizing tokens, seller cookies and purchase tokens to provide security, efficiency as well as independent operation. The purchase token is issued by the billing device to the buyer for transactions with sellers. The seller may issue a seller cookie to the buyer so that future transactions between the buyer and the seller may occur without interacting with the billing device. The billing device may issue an authorizing token to approve a buyer purchase order and to assure the seller that the buyer account is sufficient to cover prospective purchases. The authorizing token permits the seller to send an invoice to the billing device without being tied to specific transactions with the buyer. The billing device bills the buyer based on agreements between the buyer and the billing device which is independent of buyer-seller transactions. Thus, the transactions between the buyer and the seller, the seller and the billing device, and the billing device and the buyer may all occur at times that are independent of each other.

Claims

1. A payment method for transactions conducted over a data network between a buyer and a seller, comprising:

receiving via the data network a request related to the transactions, the request being directed to a payer different from the buyer; and

paying the seller at a payment time independent of a number of the transactions based on a buyer account.

2. The method of

claim 1

, wherein the payer authorizes a payment commitment between the buyer and the seller by issuing an authorizing token to the seller.

3. The method of

claim 2

, wherein the request is one of an invoice from the seller for the transactions, or an approval request for a purchase order from either the buyer or the seller, the method further comprising:

retrieving a buyer identification from the request based on either a purchase token or the authorizing token; and

retrieving the buyer account based on the buyer identification.

4. The method of

claim 3

, wherein if the request is an invoice, the paying step comprises one of:

paying the invoice if that the buyer account is sufficient to pay the invoice;

indicating to the seller a later payment time if the buyer account is insufficient to pay the invoice when received but sufficient to pay the invoice a later time;

or

indicating to the seller that the buyer account is unable to pay the invoice.

5. The method of

claim 3

, wherein the request is the approval request for a purchase order, the method further comprising:

sending the authorizing token to the seller that approves the purchase order if the buyer account is sufficient to pay for the purchase order;

sending the authorizing token that approves the purchase order for a delayed payment time if the buyer account is insufficient to pay for the purchase order when received but sufficient to pay for the purchase order at a later time;

or

sending a disapproval message to either the buyer or the seller indicating that the buyer account is unable to pay for the purchase order.

6. The method of

claim 3

, wherein the purchase token and the authorizing token includes information that at least one of:

identifies the payer; and

identifies the buyer.

7. The method of

claim 6

, wherein the information identifying the buyer is encrypted so that the buyer may be anonymous to the seller.

8. The method of

claim 6

, wherein the authorizing token further includes information that identifies the seller.

9. The method of

claim 1

, wherein the request is an application for a subscription from the buyer for a billing service offered by a billing device, the method further comprising:

recording buyer information in the request;

establishing a buyer profile based on information in the request and/or additional information received from the buyer;

establishing the buyer account; and

establishing accounts for specific sellers as instructed by the buyer.

10. The method of

claim 9

, further comprising:

generating a purchase token for the buyer; and

sending the purchase token to the buyer.

11. The method of

claim 1

, further comprising:

receiving a cancellation request from the buyer to cancel the subscription to the billing service;

sending a cancellation message to the seller if the seller has an unexpired authorizing token for the buyer;

receiving a final invoice from the seller;

paying the final invoice if the buyer account has sufficient funds to pay; and

billing the buyer for an unpaid amount.

12. The method of

claim 1

, further comprising:

receiving a cancellation from the seller to cancel a purchased subscription or a purchased item; and

updating the buyer account to reflect the cancellation.

13. A billing device that pays for transactions conducted over a data network between a buyer and a seller, comprising:

a database; and

a controller coupled to the database, the controller receiving via the data network a request related to the transactions, the request being directed to a payer different from the buyer, and paying the seller at a payment time independent of a number of the transactions based on a buyer account stored in the database.

21. The device of

claim 13

, wherein the request is an application for a subscription from the buyer for a billing service offered by the billing device, the controller recording buyer information in the request, establishing a buyer profile based on information in the request and/or additional information received from the buyer, establishing a buyer account, and establishing up accounts for specific sellers as instructed by the buyer.

22. The device of

claim 21

, wherein the controller generates a purchase token for the buyer, and sends the purchase token to the buyer.

23. The device of

claim 21

, wherein the controller receives a cancellation request from the buyer to cancel the subscription to the billing service, sends a cancellation message to the seller if the seller has an unexpired authorizing token for the buyer, receives a final invoice from the seller, pays the final invoice if the buyer account has sufficient funds to pay, and bills the buyer for an unpaid amount.

24. The device of

claim 13

, wherein the controller receives a cancellation from the seller to cancel a purchased subscription or a purchased item, and updates a buyer account to reflect the cancellation.

14. The device of

claim 14

, wherein the controller authorizes a payment commitment between the buyer and the seller by issuing an authorizing token to the seller.

15. The device of

claim 15

, wherein the request is one of an invoice from the seller for the transactions, or an approval request for a purchase order from either the buyer or the seller, the controller retrieving a buyer identification from the request based on either a purchase token or the authorizing token, and retrieving the buyer account based on the buyer identification.

18. The device of

claim 15

, wherein the purchase token and the authorizing token includes information that at least one of:

identifies the payer; and

identifies the buyer.

19. The device of

claim 18

, wherein the information identifying the buyer is encrypted so that the buyer may be anonymous to the seller.

20. The device of

claim 15

, wherein the authorizing token further includes information that identifies the seller.

16. The device of

claim 16

, wherein if the request is an invoice, the controller pays the invoice if that the buyer account is sufficient to pay the invoice, indicates to the seller a later payment time if the buyer account is insufficient to pay the invoice when received but sufficient to pay the invoice a later time, or indicates to the seller that the buyer account is unable to pay the invoice.

17. The device of

claim 16

, wherein the request is the approval request for a purchase order, the controller sending the authorizing token to the seller that approves the purchase order if the buyer account is sufficient to pay for the purchase order, sending the authorizing token that approves the purchase order for a delayed payment time if the buyer account is insufficient to pay for the purchase order when received but sufficient to pay for the purchase order at a later time, or sending a disapproval message to either the buyer or the seller indicating that the buyer account is unable to pay for the purchase order.

25. A method for billing a payer for a plurality of transactions conducted between a buyer and a seller over a data network, comprising:

receiving approval for a first number of purchase orders from the payer different from the buyer;

conducting a second number of the transactions over the data network with the buyer; and

billing the payer for the transactions a third number of times, wherein the first, second and third numbers are independent of each other.

26. The method of

claim 25

, further comprising:

receiving a purchase request as one of the transactions from the buyer via the data network, the purchase request not including a cookie;

verifying and signing the purchase request;

returning the purchase request to the buyer, the buyer sending the purchase request as the purchase order to the payer for approval; and

filling the purchase order based on an authorizing token received from the payer, the authorizing token being the approval from the payer.

27. The method of

claim 26

, further comprising:

receiving additional information that indicates payment for the purchase order may be made either immediately or delayed by a specified date.

28. The method of

claim 25

, further comprising:

receiving a purchase request as one of the transactions from the buyer via the data network, the purchase request including a purchase token;

verifying the purchase request;

converting the purchase request into the purchase order by signing the purchase request;

forwarding the purchase order to the payer for approval based on the purchase token; and

filling the purchase order based on an authorizing token received from the payer, the authorizing token being the approval from the payer.

29. The method of

claim 28

, wherein the purchase token includes at least one of:

a payer identification; and

a buyer identification;

the buyer identification being one of plain text or encrypted text, the encrypted text maintaining the anonymity of the buyer with respect to the seller.

30. The method of

claim 25

, further comprising:

receiving a transaction request from the buyer via the data network, the transaction request being a transaction of the transactions, the transaction request including a seller cookie;

verifying the transaction request;

retrieving a buyer account;

performing the transaction based on a status of a buyer account without interaction with the payer.

31. The method of

claim 25

, further comprising:

establishing a buyer account based on buyer instructions;

acquiring approval for parameter values in the buyer account from the payer; and

updating the buyer account based on the first number of transactions without interaction with the payer.

32. The method of

claim 25

, wherein the parameter values of the buyer account include at least one of:

a periodic payment amount;

an account balance;

an uncommitted amount;

a credit limit;

a credit remaining amount; and

a credit rating.

33. The method of

claim 25

, further comprising:

generating an invoice independent of the first number of purchase orders and the second number of the transactions; and

sending the invoice as a bill to the payer.

34. The method of

claim 25

, further comprising:

receiving a cancel message from the payer;

generating an invoice for all outstanding charges for the buyer relating to the payer; and

sending the invoice to the payer for a final payment.

35. The method of

claim 25

, further comprising:

receiving a cancel request from the buyer;

generating an end notice to the payer, the end notice including any outstanding charges for the buyer related to the payer; and

sending the end notice to the payer.

36. A seller device that billing a buyer for a plurality of transactions conducted with a seller over a data network, comprising:

a database; and

a controller coupled to the database, the controller receiving approval for a first number of purchase orders from a payer different from the buyer, conducting a second number of the transactions over the data network with the buyer, and billing the payer for the transactions a third number of times, wherein the first, second and third numbers are independent of each other.

37. The device of

claim 36

, wherein the controller receives a purchase request as one of the transactions from the buyer via the data network, the purchase request not including a cookie, verifies and signs the purchase request, returns the purchase request to the buyer, the buyer sending the purchase request as the purchase order to the payer for approval, and fills the purchase order based on an authorizing token received from the payer, the authorizing token being the approval from the payer.

38. The device of

claim 37

, wherein the controller receives additional information that indicates payment for the purchase order may be made either immediately or delayed by a specified date.

39. The device of

claim 36

, wherein the controller receives a purchase request as one of the transactions from the buyer via the data network, the purchase request including a purchase token, verifies the purchase request, converts the purchase request into the purchase order by signing the purchase request, forwards the purchase order to the payer for approval based on the purchase token, and fills the purchase order based on an authorizing token received from the payer, the authorizing token being the approval from the payer.

40. The device of

claim 39

, wherein the purchase token includes at least one of:

a payer identification; and

a buyer identification;

the buyer identification being one of plain text or encrypted text, the encrypted text maintaining the anonymity of the buyer with respect to the seller.

41. The device of

claim 36

, wherein the controller receives a transaction request from the buyer via the data network, the transaction request being a transaction of the transactions, the transaction request including a seller cookie, verifies the transaction request, retrieves a buyer account, performs the transaction based on a status of a buyer account without interaction with the payer.

42. The device of

claim 36

, wherein the controller establishes a buyer account in the database based on buyer instructions, acquires approval for parameter values in the buyer account from the payer, and updates the buyer account based on the first number of transactions without interaction with the payer.

43. The device of

claim 36

, wherein the parameter values of the buyer account include at least one of:

a periodic payment amount;

an account balance;

an uncommitted amount;

a credit limit;

a credit remaining amount; and

a credit rating.

44. The device of

claim 36

, wherein the controller generates an invoice independent of the first number of purchase orders and the second number of the transactions, and sends the invoice as a bill to the payer.

45. The device of

claim 36

, wherein the controller receives a cancel message from the payer, generates an invoice for all outstanding charges for the buyer relating to the payer, and sends the invoice to the payer for a final payment.

46. The device of

claim 36

, wherein the controller receives a cancel request from the buyer, generates an end notice to the payer, the end notice including any outstanding charges for the buyer related to the payer, and sends the end notice to the payer.