Transaction aggregation system and method

• US 20020111876A1
• Filed: 05/17/2001
• Published: 08/15/2002
• Est. Priority Date: 02/09/2001
• Status: Abandoned Application

• Current Assignee: Ebizportals Incorporated
• Original Assignee: Ebizportals Incorporated
• Inventors: Narkhede, Atul, Rudraraju, Panduranga R., Shetty, Chandrashekhar, Nirkhe, Madhura, Prateek, Abhinandan
• Application Number:
  US09/861,368
• Publication Number:
  US 20020111876A1
• Time in Patent Office: Days
• US Class Current: 705/26
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0617 Representative agent

Abstract

An aggregation system is configured to execute transactions between a customer and a merchant as transaction messages. The transaction aggregation system includes a user agent, multiple message schemas, a repository for storing the message schemas, and a transaction engine. The user agent converts a transaction request received from the customer into a first-transaction message. The transaction engine then receives and maps the first-transaction message into a second-transaction message using one of the message schemas. The transaction engine then transmits the second-transaction message to the merchant to execute the customer transaction.

Claims

1. A transaction aggregation system configured to execute transactions between a customer and a merchant as transaction messages, comprising:

a user agent configured to convert a transaction request received from said customer into a first-transaction message;

a plurality of message schemas;

a repository configured to store said plurality of message schemas; and

a transaction engine configured to;

receive said first-transaction message from said user agent;

map said first-transaction message into a second-transaction message using one of said message schemas stored in said repository; and

transmit said second-transaction message to said merchant, wherein said merchant executes said customer transaction request.

2. The system of claim 1, wherein said transaction aggregation system further comprises:

a process adapter configured to receive said second-transaction message from said transaction engine and translate said second-transaction message to communicate with a plurality of different merchants; and

a connector module for connecting said customer to said transaction engine.

3. The system of claim 1, wherein said customer transaction request comprises a plurality of transaction requests for a plurality of different merchants.

4. The system of claim 3, wherein said transaction engine processes said plurality of transaction requests according to conditions in a process flow.

5. The system of claim 1, wherein said transaction aggregation system facilitates asynchronous communication between said customer and said merchant.

6. The system of claim 1, wherein said customer can disconnect from said user agent after submitting said transaction request to said user agent using a first customer device and reconnect to said user agent using a second customer device to determine the status of said transaction request.

7. The system of claim 3, wherein said transaction engine queues said plurality of transaction messages to be processed a synchronously.

8. The system of claim 1, wherein said transaction engine maps said first transaction message into said second transaction message using schema based mapping, wherein meta-information contained in said schemas are utilized to transform said first transaction message to said second transaction message.

9. The system of claim 2, wherein said process adapter generates and transmits a transaction request status message to said customer.

10. A method for executing transactions between a customer and a merchant using transactions messages, comprising the steps of:

providing a user agent for converting a transaction request received from said customer into a first-transaction message;

storing a plurality of message schemas in a repository

providing a transaction engine for mapping said first-transaction message into a second-transaction message using one of said message schemas stored in said repository;

transmitting said second-transaction message to said merchant, wherein said merchant executes said customer transaction request.

11. The method of claim 10, comprising the additional steps of:

providing a process adapter for translating said second-transaction message to communicate with a plurality of different merchant devices and transmitting a transaction request status message to said customer.

12. The method of claim 10, comprising the additional step of providing a connector module for connecting said customer to said transaction engine.

13. The method of claim 10, wherein said customer transaction request comprises a plurality of transaction requests for a plurality of different merchants.

14. The method of claim 13, wherein said plurality of transactions requests are processed according to conditions in a process flow.

15. The method of claim 10, wherein said customer can disconnect from said user agent after submitting said transaction request to said user agent using a first customer device and reconnect to said user agent using the same customer device or a second customer device to determine the status of said transaction request.

16. The method of claim 13, wherein said transaction engine queues said plurality of transaction messages to be processed asynchronously.

17. The method of claim 10, wherein said transaction engine maps said first transaction message into said second transaction message using schema based mapping, wherein meta-information contained in said schemas are utilized to transform said first transaction message to said second transaction message.

19. The computer readable storage medium of claim 18, wherein said computer is further instructed to execute a process adapter for translating said second-transaction message to communicate with a plurality of different merchant devices and transmitting a transaction request status message to said customer.

20. The computer readable storage medium of claim 18, wherein said computer is further instructed to execute a connector module for connecting said customer to said transaction engine.

21. The computer readable storage medium of claim 18, wherein said customer transaction request comprises a plurality of transaction requests for a plurality of different merchants.

22. The computer readable storage medium of claim 21, wherein said computer is further instructed to process said plurality of transactions requests according to conditions in a process flow.

23. The computer readable storage medium of claim 18, wherein said customer can disconnect from said user agent after submitting said transaction request to said user agent using a first customer device and reconnect to said user agent using the same customer device or a second customer device to determine the status of said transaction request.

24. The computer readable storage medium of claim 22, wherein said computer is further instructed to execute said transaction engine to queue said plurality of transaction messages to be processed asynchronously.

25. The computer readable storage medium of claim 18, wherein said computer is further instructed to execute said transaction engine to map said first transaction message into said second transaction message using schema based mapping, wherein meta-information contained in said schemas are utilized to transform said first transaction message to said second transaction message.

27. The system of claim 26, wherein said transaction aggregation system further comprises:

a process adapter configured to receive said second-transaction message from said transaction engine and translate said second-transaction message to communicate with a plurality of different merchants; and

a connector module for connecting said customer to said transaction engine.

28. The system of claim 26, wherein said customer transaction request comprises a plurality of transaction requests for a plurality of different merchants.

29. The system of claim 26, wherein said transaction aggregation system facilitates asynchronous communication between said customer and said merchant.

30. The system of claim 26, wherein said customer can disconnect from said user agent after submitting said transaction request to said user agent using a first customer device and reconnect to said user agent using a second customer device to determine the status of said transaction request.

31. The system of claim 28, wherein said transaction engine queues said plurality of transaction messages to be processed asynchronously.

32. The system of claim 26, wherein said transaction engine maps said first transaction message into said second transaction message using schema based mapping, wherein meta-information contained in said schemas are utilized to transform said first transaction message to said second transaction message.

33. The system of claim 27, wherein said process adapter generates and transmits a transaction request status message to said customer.

18. A computer-readable storage medium containing computer executable code for implementing a transaction aggregation application by instructing a computer to operate as follows:

execute a user agent for converting a transaction request received from said customer into a first-transaction message;

execute a repository for storing a plurality of message schemas;

execute a transaction engine for mapping said first-transaction message into a second-transaction message by accessing and using one of said message schemas stored in said repository;

transmitting said second-transaction message to said merchant, wherein said merchant executes said customer transaction request.

26. The transaction aggregation system configured to execute transactions between a customer and a merchant as transaction messages, comprising:

a customer transaction request;

a first transaction message;

a second transaction message;

a user agent configured to convert said customer transaction request into said first transaction message;

a plurality of message schemas;

a process flow;

a repository configured to store said plurality of message schemas and said process flow;

a transaction engine configured to;

receive said first-transaction message from said user agent;

map said first-transaction message into said second-transaction message according to said process flow using one of said message schemas stored in said repository; and

transmit said second-transaction message to said merchant, wherein said merchant executes said customer transaction request.