Electronic transaction system

• US 20060271499A1
• Filed: 06/28/2004
• Published: 11/30/2006
• Est. Priority Date: 06/27/2003
• Status: Active Grant

• Current Assignee: Tafmo Australia Pty Limited (Block, Inc. (f/k/a Square, Inc.))
• Original Assignee: Tafmo Australia Pty Limited (Block, Inc. (f/k/a Square, Inc.))
• Inventors: Course, Philip
• Granted Patent: US 9,177,304 B2
• Time in Patent Office: Days
• US Class Current: 705/67
• CPC Class Codes: G06Q 20/123 Shopping for digital content
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: H04L 2463/102 applying security measure for e-commerce data processing systems or methods, specially adapted for e-commerce G06Q30/00
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources

Abstract

An electronic transaction system comprising a host server, at least one transaction device; at least one service provider system; and a content management system. When a transaction device issues a client request to the host server for one or more of the electronic goods and/or services, the host server operates to generate a client response in reply to the client request. In generating the client response a service request may be issued to the at least one service provider system. Also includes a matrix recording a set of permissions and/or constraints applicable to the electronic transaction system. The content management system references the matrix in determining the content to be provided to each transaction device to ensure that the set of permissions and/or constraints are complied with. Each transaction device further receives a set of unique identifiers from the host server, each identifier representing a component of the content.

Claims

1. An electronic transaction system comprising:

a host server;

at least one transaction device;

at least one service provider system; and

a content management system,

where the content management system provides content in the form of details of electronic goods and/or services able to be transacted by the electronic transaction system to the at least one transaction device and where, upon the at least one transaction device issuing a client request to the host server for one or more of the electronic goods and/or services detailed, the host server operates to generate a client response in reply to the client request and in generating the client response, where necessary, issuing a service request to the at least one service provider system and receiving a service response from the at least one service provider.

2. An electronic transaction system according to claim 1, further comprising a matrix recording a set of permissions and/or constraints applicable to the electronic transaction system, and where the content management system references the matrix in determining the content to be provided to each transaction device of the at least one transaction device to ensure that the set of permissions and/or constraints are complied with.

3. An electronic transaction system according to claim 2, where the matrix includes at least one of the following dimensions:

a transaction device dimension;

an electronic good or service dimension; and

a merchant dimension,

each dimension operable to record information in respect of the transaction device, electronic good or service or merchant, as appropriate, that may affect the content to be provided by the content management system

4. An electronic transaction system according to claim 2, where the host server determines whether the client request complies with the set of permissions and/or constraints recorded in the matrix and references the matrix in generating a client response to ensure that the set of permissions and/or constraints are complied with.

5. An electronic transaction system according to claim 1, where each transaction device of the at least one transaction device receives a set of unique identifiers from the host server, each unique identifier representing a component of the content, the transaction device operable to check the set of unique identifiers against content already provided and request content having unique identifiers not already provided from the content management system.

6. An electronic transaction system according to claim 5, where the transaction device is further operable to discard components of the content having a unique identifier not included in the set of unique identifiers received from the host server.

7. An electronic transaction system according to claim 5, where the unique identifier consists of a file name and at least one of the following:

a version number;

an error check value.

8. An electronic transaction system according to claim 1, where, upon creation of content using the content management system, the content management system operates to provide the content to each transaction device of the at least one transaction device.

9. An electronic transaction system according to claim 5, where the content includes, in respect of each electronic service and/or good able to be transacted;

at least one of the following;

a description;

a graphic to represent the electronic service or good;

details of acceptable payment methods;

details of acceptable validation or data entry mechanisms; and

/or

details of any document to be provided when the service response confirms a service request was successful.

10. An electronic transaction system according to claim 5, where the content includes at least one of the following:

a menu structure for navigating the electronic services and goods able to be transacted; and

details of any security mechanisms implemented to control access to any restricted portions of the menu structure;

11. An electronic transaction system according to claim 5, where each transaction device of the at least one transaction device receives a scheduled time for transmission of content from the content management system, each transaction device operable to request the set of unique identifiers from the host server on the scheduled time.

12. An electronic transaction system according to claim 1, where the host server operates to generate a client response in reply to the client request by reference to a process model, the process model conceptually comprising a series of steps and links, the arrangement of one or more links in respect of a first step representing a second step to process on the first step resolving to a predetermined result in a set of predetermined results.

13. An electronic transaction system according to claim 12, where the set of predetermined results are a set of Boolean values and a fail result.

14. An electronic transaction system according to claim 1, comprising at least one channel grouping, each channel grouping associated with at least one transaction device, where content provided to each transaction device of a channel grouping is the same as content provided to each other transaction device in the same channel grouping.

15. An electronic transaction system according to claim 1, comprising at least one relationship, each relationship recording details for facilitating communication between the host server and either a transaction device or a service provider system, using their respective native languages and communication protocols.

16. An electronic transaction system according to claim 1, further comprising an electronic inventory, the electronic inventory operable to provide an electronic good to the host server on request.

17. An electronic transaction system according to claim 16, where a request from the host server for an electronic good includes a goods identifier, the electronic inventory operable to provide an electronic good having a corresponding goods identifier in response to the request.

18. An electronic transaction system according to claim 16, where, on return of an electronic good to the electronic inventory, the electronic good is not able to be provided in response to a request from the host server for a predetermined period of time.

19. An electronic transaction system according to claim 16, where the electronic good is a serial number to be provided in redeeming an electronic service able to be transacted.

20. An electronic transaction system according to claim 1, where an asynchronous service request or asynchronous client request includes a correlation key and any response to the asynchronous service request or asynchronous client request, as appropriate, includes the correlation key.

21. An electronic transaction system according to claim 20, where the host server is operable to distinguish between a service response and a client request by reference to the correlation key and/or type.

22. An electronic transaction system according to claim 1, where each service request, service response, client request and client response is communicated via at least one message bus.

23. An electronic transaction system according to claim 22, where at least one message bus uses a publish/subscribe mechanism of communication.

24. An electronic transaction system according to claim 1, where the transaction device includes at least one payment application.

25. An electronic transaction system according to claim 24, further comprising an intermediate router having a dedicated connection to the host server and to a payments host, the intermediate router operable to forward a service request issued by a transaction device to the host server and operable to forward a payment request issued by the payment application of the transaction device to the payments host.

26. An electronic transaction system according to claim 25, where the transaction device issues an authorisation request to the intermediate router for forwarding to the payments host and receives an authorisation reply from the payments host via the intermediate router and where, if so authorised, the transaction system thereafter issues a service request to the transaction to the host server via the intermediate router and, upon receiving a service response indicating that the service request was successful, issuing a payment request to the payments host via the intermediate router.

27. An electronic transaction system according to claim 24, where the transaction device includes removable, writeable media for recording one or more of the following:

a receipt;

an electronic good;

details of the client request;

details of the client response.

28. An electronic transaction system according to claim 1, where the host server operates to confirm the identity and/or capacity of the transaction device that issued the client request and, if the identity of the transaction device can not be confirmed, or the capacity of the transaction device is exceeded, operable to ignore the client request.

29. A host server for use in an electronic transaction system according to claim 1.

30. A transaction device for use in an electronic transaction system according to claim 1.

31. A method of performing an electronic transaction comprising the steps of:

providing content in the form of details of electronic goods and/or services able to be transacted to at least one transaction device;

receiving a client request for one or more of the electronic goods and/or services detailed from a transaction device;

generating a client response in reply to the client request which, where necessary, includes issuing a service request to at least one service provider system and receiving a service response from the at least one service provider.

32. A method of performing an electronic transaction according to claim 31, including the step of referencing a matrix recording a set of permissions and/or constraints to ensure that the content to be provided to each transaction device complies with the recorded set of permissions and/or constraints.

33. A method of performing an electronic transaction according to claim 32, including the steps of determining whether the client request complies with the set of permissions and/or constraints recorded in the matrix and the step of generating a client response includes the sub-step of referencing the matrix to ensure that the set of permissions and/or constraints are complied with.

34. A method of performing an electronic transaction according to claim 31, including the step of sending a set of unique identifiers to each transaction device, each unique identifier representing a component of the content, and the step of transmitting any content having unique identifiers not already provided to the transaction device upon request by the transaction device.

35. A method of performing an electronic transaction according to claim 34, including the step of receiving a request for the set of unique identifiers from each transaction device at each transaction device'"'"'s scheduled time.

36. A method of performing an electronic transaction according to claim 31, where the step of generating a client response includes the substep of executing a process model, the process model conceptually comprising a series of steps and links, the arrangement of one or more links in respect of a first step representing a second step to process on the first step resolving to a predetermined result in a set of predetermined results.

37. A method of performing an electronic transaction according to claim 31, including the step of associating each transaction device with at least one channel grouping, the content provided to each transaction device of a channel grouping being the same as content provided to every other transaction device in the same channel grouping.

38. A method of performing an electronic transaction according to claim 31, including the step of recording details for facilitating communication between the host server and each transaction device and the host server and each service provider system to form a set of relationships and the step of using the appropriate relationship in the set of relationships to facilitate communication between the host server and transaction device or service provider system, as appropriate, in their respective native languages and communication protocols.

39. A method of performing an electronic transaction according to claim 31, including the steps of issuing a request to an electronic inventory for an electronic good and receiving an electronic good from the electronic inventory.

40. A method of performing an electronic transaction according to claim 31, including the step of distinguishing between a service response and a client request by reference to a correlation key in the service response and/or type.

41. A method of performing an electronic transaction according to claim 31, including the step of communicating service requests, service responses, client requests and client responses by way of at least one message bus using a publish/subscribe mechanism of communication.

42. A method of performing an electronic transaction according to claim 31, including the steps of confirming the identity and/or capacity of the transaction device that issued the client request and the step of ignoring the client request if the identity of the transaction device can not be confirmed or the capacity of the transaction device is exceeded.

43-46. -46. (canceled)