Server Device for Controlling a Transaction, First Entity and Second Entity

• US 20110137797A1
• Filed: 11/30/2010
• Published: 06/09/2011
• Est. Priority Date: 05/30/2008
• Status: Active Grant

• Current Assignee: Mrqr10 GmbH & Company KG (net group Beteiligungsgesellschaft mbH)
• Original Assignee: Mrqr10 GmbH & Company KG (net group Beteiligungsgesellschaft mbH)
• Inventors: Hirasawa, Shinji, Stals, Luc, Palzer, Martin, Geldermann, Martin
• Granted Patent: US 8,332,323 B2
• Time in Patent Office: Days
• US Class Current: 705/44
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• 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/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3265 characterised by personalisation for use
• CPC Class Codes: G06Q 20/3276 using a pictured code, e.g. barcode or QR-code, being read by the M-device
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists

Abstract

Server device for performing a transaction in a system having a first entity, such as a POS, a second entity, such as a user having a mobile phone with a digital camera, and a remote server. The first entity generates a code having a transaction information and sends a first message to a server. The second entity, such as a buyer of a product or a user of a service captures the code and transmits a second message to the server having information on the transaction extracted from the code. The transaction is only authorized, when the server has determined that the first message and the second message match with each other. The transaction can be a payment transfer, a grant of an access to a service or a grant of an access to an internet portal.

Claims

1. A server device for controlling a transaction between the first entity and the second entity, comprising:

a receiver for receiving a first message from the first entity, the first message comprising first information related to the transaction, and a second message from the second entity, the second message comprising second information related to the transaction;

a matcher for checking whether the first information in the first message and the second information in the second message comprise a predetermined relation to each other; and

an output interface for authorizing the transaction, when the first information and the second information comprise a predetermined relation and for rejecting the transaction, when the first information and the second information do not comprise the predetermined relation to each other.

2. The server device in accordance with claim 1, in which the matcher is adapted to check whether the time difference between a reception or generation of the first message and the second message or a time difference between a generation of an identification code in the first entity and a transmission or reception of the first message or the second message is greater than the predetermined amount of time or not, and

in which the output interface is operative to reject a transaction, when the predetermined amount of time is exceeded.

3. The server device in accordance with claim 1, in which each of the first message and the second message comprises a time stamp indicating a generation or a transmission time, and

in which the matcher is operative to perform a check based on the time stamps of the first message and the second message.

4. The server device in accordance with claim 1, in which the transaction information comprises a transaction ID uniquely referencing a transaction record comprising further information on the transaction, and

in which the matcher is operative to determine whether a message from the first entity and the message from the second entity comprising matching transaction IDs have been received by the receiver.

5. The server device in accordance with claim 1, in which the transaction is a payment transaction or a cash redraw transaction, and the output interface is operative to initiate the communication to a payment or a cash providing institute only when the transaction has been authorized.

6. The server device in accordance with claim 1, in which the transaction is an access to a data service of the first entity, and in which the output interface is operative to only authorize the transaction by sending an authorization message to the first entity.

7. A first entity for performing a transaction with a second entity under control of a server device, comprising:

a transaction information generator for generating an information on the transaction;

an identification code generator for generating and outputting an identification code, the identification code comprising the information on the transaction;

a message transmitter for transmitting a message to the server, the message comprising the information on the transaction; and

a confirmation receiver for receiving, from the server, an authorization indication.

8. The first entity in accordance with claim 7, in which the transaction information generator is operative to newly create a unique transaction identification in response to a triggering message for triggering a new transaction, the triggering message being received from the second entity.

9. The first entity in accordance with claim 7, in which the transaction comprises an action to be performed by the first entity, and in which the confirmation receiver is operative to allowing the transaction, when the authorization indication is received and for not allowing the transaction, when the authorization indication is not received.

10. The first entity in accordance with claim 7, in which the identification code generator is operative to generate a two-dimensional QR code comprising the transaction information.

11. A second entity for performing a transaction with a first entity under control of a server device, comprising:

an identification code receiver for receiving an identification code generated and output by the first entity, the identification code comprising encoded information on the transaction;

an information provider for providing the information on the transaction comprised in the identification code;

a message transmitter for transmitting a message to the server, the message comprising the information on the transaction; and

a confirmation receiver for receiving, from the server, a confirmation message indicating that the message comprises a predetermined relation to a different message received, by the server, from the first entity.

12. The second entity in accordance with claim 11, in which the message transmitter is operative to retrieve an address of the server from the identification code or to use a fixedly set server address, the fixedly set server address being comprised in a software application residing in an electronic device being the second entity.

13. The second entity in accordance with claim 11, which comprises a mobile electronic device comprising the identification code receiver, the message transmitter and the confirmation receiver, the mobile electronic device being operative to require a user authorization before the message transmitter is activated to transmit the message.

14. The second entity in accordance with claim 12, where the message transmitter is operative to add a unique user ID to the second message such as a mobile service device number of a cellular telephone system.

15. A method, performed in a server device, for controlling a transaction between the first entity and the second entity, comprising:

receiving a first message from the first entity, the first message comprising first information related to the transaction, and a second message from the second entity, the second message comprising second information related to the transaction;

checking whether the first information in the first message and the second information in the second message comprise a predetermined relation to each other; and

authorizing the transaction, when the first information and the second information comprise a predetermined relation and for rejecting the transaction, when the first information and the second information do not comprise the predetermined relation to each other.

16. A method, performed in a first entity, for performing a transaction with a second entity under control of a server device, comprising:

generating an information on the transaction;

generating and outputting an identification code, the identification code comprising the information on the transaction;

transmitting a message to the server, the message comprising the information on the transaction; and

receiving, from the server, an authorization indication.

17. A method, performed in a second entity, for performing a transaction with a first entity under control of a server device, comprising:

receiving an identification code generated and output by the first entity, the identification code comprising encoded information on the transaction;

providing the information on the transaction comprised in the identification code;

transmitting a message to the server, the message comprising the information on the transaction; and

receiving, from the server, a confirmation message indicating that the message comprises a predetermined relation to a different message received, by the server, from the first entity.

18. A computer program for performing, when running on a computer, a method, performed in a server device, for controlling a transaction between the first entity and the second entity, comprising:

receiving a first message from the first entity, the first message comprising first information related to the transaction, and a second message from the second entity, the second message comprising second information related to the transaction;

checking whether the first information in the first message and the second information in the second message comprise a predetermined relation to each other; and

authorizing the transaction, when the first information and the second information comprise a predetermined relation and for rejecting the transaction, when the first information and the second information do not comprise the predetermined relation to each other.

19. A computer program for performing, when running on a computer, a method, performed in a first entity, for performing a transaction with a second entity under control of a server device, comprising:

generating an information on the transaction;

generating and outputting an identification code, the identification code comprising the information on the transaction;

transmitting a message to the server, the message comprising the information on the transaction; and

receiving, from the server, an authorization indication.

20. A computer program for performing, when running on a computer, a method, performed in a second entity, for performing a transaction with a first entity under control of a server device, comprising:

receiving an identification code generated and output by the first entity, the identification code comprising encoded information on the transaction;

providing the information on the transaction included in the identification code;

transmitting a message to the server, the message comprising the information on the transaction; and

receiving, from the server, a confirmation message indicating that the message comprises a predetermined relation to a different message received, by the server, from the first entity.