MULTI-TIER TRANSACTION PROCESSING METHOD AND PAYMENT SYSTEM IN M- AND E- COMMERCE

• US 20110035294A1
• Filed: 08/04/2009
• Published: 02/10/2011
• Est. Priority Date: 08/04/2009
• Status: Abandoned Application

• Current Assignee: Authernative
• Original Assignee: Authernative
• Inventors: MIZRAH, LEN L.
• Application Number:
  US12/535,546
• Publication Number:
  US 20110035294A1
• Time in Patent Office: Days
• US Class Current: 705/26.42
• CPC Class Codes: G06F 21/33 using certificates
• CPC Class Codes: G06F 21/645 using a third party
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/389 Keeping log of transactions for guaranteeing non-repudiation of a transaction
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0615 Anonymizing
• CPC Class Codes: G06Q 40/12 Accounting
• CPC Class Codes: G06Q 50/188 Electronic negotiation

Abstract

A server executes a protocol that automates transactions involving a customer and a merchant agreeing to trade money in the customer'"'"'s account for goods or services available from the merchant. The protocol protects personal identifying information of the customer from disclosure to the merchant, and protects all parties from repudiation of the specific transaction. The protocol defines a pre-authenticated form of the specific transaction; obtains authorization from the customer and the merchant to commit on their behalf to the pre-authenticated transaction; and obtains authorization from the bank to commit resources for settlement with the merchant. After obtaining authorizations, a transaction clearance code is generated completing a record of the pre-authenticated transaction for non-repudiation, for proof of a right to receive settlement from the third party and for proof of a right to receive the goods or services from the merchant.

Claims

1. For automated transactions involving a first party and a second party agreeing to trade resources such as money in an account held by a third party on behalf of the first party for goods or services available from the second party, a method protecting personal identifying information of the first party from disclosure to the second party and protecting the specific transaction from repudiation by any party to the transaction, comprising:

executing a protocol using a server for obtaining commitments from the first, second and third parties to a specific transaction having transaction parameters arranged between the first and second parties, the protocol defining a pre-authenticated form of the specific transaction;

obtaining authorization from the first and second parties for the server to commit on behalf of the first and second parties to the specific transaction in the pre-authenticated form; and

obtaining authorization from the third party for the server to commit on behalf of the third party resources for clearance of the specific transaction in the pre-authenticated form;

after obtaining said authorizations from the first, second and third parties, generating at the server a transaction clearance code unique to the specific transaction, delivering the transaction clearance code to the parties of the specific transaction, and storing the transaction clearance code in the record of the specific transaction in the server;

said record of the specific transaction capable of being used for non-repudiation of the specific transaction by the first, second and third parties, and said transaction clearance code usable by the second party to prove a right to receive said allocated resources from the third party and by the first party to prove a right to receive the goods or services subject of the specific transaction from the second party.

2. The method of claim 1, wherein said defining a pre-authenticated form of the specific transaction includes:

exchanging messages on communication channels between the server and terminals of the first party and the second party (i) for authentication of the first party to the server by a user authentication process that identifies the first party and verifies that the first party holds an account with the third party, (ii) for identification and verification of the transaction parameters by receiving an identifier of the second party from the first party, by communicating with the second party for determination of the transaction parameters, and by communicating with the first party for verification of the transaction parameters, and (iii) for authentication of the server to the first party including delivering a transaction parameter determined by the server from the second party.

3. The method of claim 1, wherein said obtaining authorization from the first and second parties for the server to commit on behalf of the first and second parties to the specific transaction in the pre-authenticated form includes:

exchanging messages on communication channels between the server and terminals of the first party and the second party including communicating with the second party for indication of authorized transaction parameters, and by communicating with the first party for verification of the authorized transaction parameters.

4. The method of claim 1, including performing a process at the server to facilitate agreement of the transaction parameters for the specific transaction between the first and second parties.

5. The method of claim 1, wherein at least one of said communication terminals of the parties to the specific transaction comprises a mobile computing device executing a wireless communication protocol.

6. For automated transactions involving a first party and a second party agreeing to trade resources such as money in an account held by a third party on behalf of the first party for goods or services available from the second party, a method protecting personal identifying information of the first party from disclosure to the second party and protecting the specific transaction from repudiation by any party to the transaction, comprising:

executing a protocol using a server for obtaining commitments from the first, second and third parties to a specific transaction having transaction parameters arranged between the first and second parties, the protocol including;

exchanging messages on communication channels between the server and terminals of the first party and the second party (i) for authentication of the first party to the server by a user authentication process that identifies the first party and verifies that the first party holds an account with the third party, (ii) for identification and verification of the transaction parameters by receiving an identifier of the second party from the first party, by communicating with the second party for determination of the transaction parameters, and by communicating with the first party for verification of the transaction parameters, and (iii) for authentication of the server to the first party including delivering a transaction parameter determined by the server from the second party to thereby define a pre-authenticated form of the specific transaction;

storing a definition of the pre-authenticated form of the specific transaction in a record of the specific transaction in the server;

exchanging messages on communication channels between the server and terminals of the first party and the second party to obtain authorization from the first and second parties for the server to commit on behalf of the first and second parties to the specific transaction in the pre-authenticated form;

storing an indication in the record of the specific transaction in the server confirming said pre-authorization;

exchanging messages on communication channels between the server and terminals of the third party to obtain authorization from the third party for the server to commit on behalf of the third party resources for clearance of the specific transaction;

storing an indication in record of the specific transaction in the server confirming said authorization by the third party; and

after obtaining said authorizations from the first, second and third parties, generating at the server a transaction clearance code unique to the specific transaction, delivering the transaction clearance code to the parties of the specific transaction, and storing the transaction clearance code in the record of the specific transaction in the server;

said record of the specific transaction capable of being used for non-repudiation of the specific transaction by the first, second and third parties, and said transaction clearance code usable by the second party to prove a right to receive said allocated resources from the third party and by the first party to prove a right to receive the goods or services subject of the specific transaction from the second party.

7. The method of claim 6, wherein said protocol includes:

receiving a message from the first party including an identifier of the second party and a transaction identifier;

sending a message to the second party including the transaction identifier;

receiving a message from the second party including transaction parameters not received at the server from the first party, and indicating authorization by the second party for the server to commit to the specific transaction having the transaction parameters;

sending a message to the first party including transaction parameters received by the server from the second party, thereby authenticating the server to the first party; and

receiving a message from the first party indicating authorization by the first party for the server to commit to the specific transaction having the transaction parameters, whereby the specific transaction is pre-authenticated and authorized in its pre-authenticated form by the first and second parties.

8. The method of claim 6, wherein said protocol includes:

receiving a message from the first party including an identifier of the second party;

exchanging messages with the second party to verify the identifier of the second party;

receiving a message from the second party including a transaction identifier;

sending a message to the first party including the transaction identifier received by the server from the second party, thereby authenticating the server to the first party;

exchanging messages with the first party to determine transaction parameters, and indicating authorization by the first party for the server to commit to the specific transaction having the transaction parameters;

sending a message to the second party including the determined transaction parameters; and

receiving a message from the second party indicating authorization by the second party for the server to commit to the specific transaction having the transaction parameters, whereby the specific transaction is pre-authenticated and authorized in its pre-authenticated form by the first and second parties.

9. The method of claim 6, including performing a process at the server to facilitate agreement of the transaction parameters for the specific transaction between the first and second parties.

10. The method of claim 6, wherein said protocol includes

receiving a message from the first party including an identifier of the second party and an indication of a merchant type by communication from the first party;

exchanging messages with the second party to verify that the second party qualifies as said merchant type;

receiving a message from the second party including a transaction identifier for the specific transaction;

sending to the first party the transaction identifier;

exchanging messages with the first party to determine a selection of goods or services to produce an order for the second party;

sending the order to the second party; and

receiving a message from the second party indicating authorization by the second party for the server to commit to the specific transaction having transaction parameters satisfying the order, whereby the specific transaction is pre-authenticated and authorized in its pre-authenticated form by the first and second parties.

11. The method of claim 10, wherein said exchanging messages with the first party to determine a selection of goods or services to produce an order for the second party;

includes;

presenting by the server a catalog of goods or services available for purchase from the second party, said catalog being accessible by the first party and including resources usable by the first party for selecting the goods or services for said transaction.

12. The method of claim 6, wherein at least one of said communication terminals of the parties to the specific transaction comprises a mobile computing device executing a wireless communication protocol.

13. A server for automated transactions involving a first party and a second party agreeing to trade resources such as money in an account held by a third party on behalf of the first party for goods or services available from the second party, while protecting personal identifying information of the first party from disclosure to the second party and protecting the specific transaction from repudiation by any party to the transaction, comprising:

a processor, a storage system coupled with the processor, and communication interfaces, and including instructions stored in the storage system and executable by the processor to execute a protocol including;

obtaining commitments from the first, second and third parties to a specific transaction having transaction parameters arranged between the first and second parties, the protocol defining a pre-authenticated form of the specific transaction, obtaining authorization from the first and second parties for the server to commit on behalf of the first and second parties to the specific transaction in the pre-authenticated form, and obtaining authorization from the third party for the server to commit on behalf of the third party resources for clearance of the specific transaction in the pre-authenticated form;

after obtaining said authorizations from the first, second and third parties, generating a transaction clearance code unique to the specific transaction, delivering the transaction clearance code to the parties of the specific transaction, and storing the transaction clearance code in the record of the specific transaction;

said record of the specific transaction capable of being used for non-repudiation of the specific transaction by the first, second and third parties, and said transaction clearance code usable by the second party to prove a right to receive said allocated resources from the third party and by the first party to prove a right to receive the goods or services subject of the specific transaction from the second party.

14. The server of claim 13, wherein said defining a pre-authenticated form of the specific transaction includes:

exchanging messages on communication channels between the server and terminals of the first party and the second party (i) for authentication of the first party to the protocol by a user authentication process that identifies the first party and verifies that the first party holds an account with the third party, (ii) for identification and verification of the transaction parameters by receiving an identifier of the second party from the first party, by communicating with the second party for determination of the transaction parameters, and by communicating with the first party for verification of the transaction parameters, and (iii) for authentication of the server to the first party including delivering a transaction parameter determined by the server from the second party.

15. The server of claim 13, wherein said obtaining authorization from the first and second parties for the server to commit on behalf of the first and second parties to the specific transaction in the pre-authenticated form includes:

exchanging messages on communication channels between the server and terminals of the first party and the second party including communicating with the second party for indication of authorized transaction parameters, and by communicating with the first party for verification of the authorized transaction parameters.

16. The server of claim 13, including instructions executable by the processor to facilitate agreement of the transaction parameters for the specific transaction between the first and second parties.

17. The server of claim 13, wherein at least one of said communication terminals of the parties to the specific transaction comprises a mobile computing device executing a wireless communication protocol.