Server device for controlling a transaction, first entity and second entity

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.

1 . 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.   
     
     
         2 . The first entity in accordance with  claim 1 , 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. 
     
     
         3 . The first entity in accordance with  claim 1 , 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. 
     
     
         4 . The first entity in accordance with  claim 1 , in which the identification code generator is operative to generate a two-dimensional QR code comprising the transaction information. 
     
     
         5 . 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.   
     
     
         6 . The second entity in accordance with  claim 5 , 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. 
     
     
         7 . The second entity in accordance with  claim 5 , 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. 
     
     
         8 . The second entity in accordance with  claim 6 , 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. 
     
     
         9 . 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.   
     
     
         10 . 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.   
     
     
         11 . 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. 
     
     
         12 . 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.