GB2506421A

GB2506421A - Electronic receipt

Info

Publication number: GB2506421A
Application number: GB1217423.1A
Authority: GB
Inventors: Enrique Garrido; Darren Leigh Shaw; Andrew Graham Hodges
Original assignee: MIURA SYSTEMS Ltd
Current assignee: MIURA SYSTEMS Ltd
Priority date: 2012-09-28
Filing date: 2012-09-28
Publication date: 2014-04-02
Also published as: GB201217423D0

Abstract

System and method for issuing an electronic receipt comprises a terminal configured to acquire details of a transaction, an electronic receipt generator arranged to generate electronic receipt data of the transaction, a machine-readable image generator arranged to generate a machine-readable image representing the electronic receipt data and a display unit arranged to display the machine readable image to an external device to obtain the electronic receipt data based on the machine-readable image. A server may also be provided to store the electronic receipt and transmit the electronic receipt to a user when data representing the machine-readable image is received from the user. The electronic receipt and machine readable image may be generated at the terminal or a server. The receipt may be authenticated. The machine readable image may be a barcode, two dimensional barcode, QR code, matrix code or the like which is scanned or captured by the users mobile device, such as a mobile phone, smartphone or PDA. The machine readable image may contain the electronic receipt data or a link to the electronic receipt data. The user is able to obtain an electronic copy of a receipt instead of a paper receipt.

Description

ELECTRONIC RECEIPT

Field of the Invention

The present invention reiates to a system and method for providing electronic reoeipts and in particular for providing eleotronic receipts of transactions at a point of sale terminal.

Background of the Invention

Within the Card payment technology sector there is a requirement to solve a challenge whereby the cardholder may require some form of real time card payment confirmation from the merchant for the goods or services purchase without requiring a Point of Sale acceptance device to have a physical receipt printer.

One way of doing this is to capture cardholder personal information such as personal e-mail address or mobile telephone number allowing for the receipt details to be provided. These details are entered into the merchant's payment system and then stored by the merchant or his solution provider so that they can deliver the receipt electronically (e.g. as a SMS message or e-mail) However, this creates data security concerns as it requires the cardholder to share personal information. The cardholder may also be unwilling to share personal information with merchants (both individuals and organisations) Therefore these is required a method and system for the cardholder to be provided with a payment receipt for his or her future records without compromising security and anonymity.

In addition to the above security concerns, printing of receipts is a time consuming and costly exercise both to the merchant and environment. Therefore, there is required a method and system for a customer to receive an anonymous and paperless confirmation of their purchases.

Summary of the Invention

Against this background and in accordance with a first aspect there is provided a system for issuing an electronic receipt comprising: a terminal configured to acquire details of a transaction; an electronic receipt generator arranged to generate electronic receipt data of the transaction; a machine-readable image generator arranged to generate a machine-readable image representing the electronic receipt data; and a display unit arranged to display the machine-readable image to an external device to obtain the electronic receipt data based on the machine-readable image. Therefore, an electronic receipt can be issued without requiring personal or contact information from a customer. The transaction may be a retail transaction, for example. The terminal may be located within a retail outlet such as a shop or restaurant.

Additional examples include kiosks or unattended payment points such as pay-at-pump terminals at fuel stations. The terminal may be an automated teller machine, for example.

The external device may be a mobile terminal, for example.

The terminal may be configured to receive details of the transaction from an external source of from a transaction carried out by or within the terminal itself.

The terminal may be configured to acquire details of a completed transaction, a transaction in progress or one or more historic transactions. The electronic receipt data may include one or more transactions. Therefore, the electronic receipt data may also include a list of transactions, account details, account balance details or a statement of account, for example.

Preferably, the system may further comprise a server comprising an electronic storage configured to store the electronic receipt data. Therefore, the electronic receipt can be saved for later validation. In this case, the mobile terminal may present the machine-readable image back to the terminal or other device for reading the electronic receipt data and to validate or authenticate it. The server may be the same or different entity that processed the transaction.

Advantageously, the server may further comprise a receiver configured to receive from a sender, data represented by the machine-readable image; and a transmitter configured to transmit to the sender the electronic receipt data in response to the received data. Rather than encoding the electronic receipt data, the machine-readable image may contain other data. On receipt of this other data the server may respond by sending the electronic receipt data.

This improves security as the EQS terminal or merchant does not generate the electronic receipt, which may instead originate within a more secure environment.

Preferably, the server may further comprise an authenticator configured to respond to an authentioation request to authenticate the electronic receipt data. Where the electronic receipt data is generated locally, i.e. within the P05 terminal, then external validation or authentication may be reguired. This can be provided by an external server and so security doesn't rely solely on the merchant equipment. Similar authentication may be achieved should the customer present the machine-readable image (or another representation of the electronio receipt) to the merchant or other party.

Optionally, the machine-readable image may be selected from the group consisting of: barcode (e.g. one-dimensional); two-dimensional barcode; Quick Response Oode (TM); QR code; and matrix barcode. Other graphical or character representations of data may be used and captured by the mobile terminal.

Optionally, the machine-readable image may contain the electronic receipt data. The machine-readable image may encode the electronic receipt data. In other words, these data may be acquired directly from the P05 terminal and so doesn't rely on a data or network connection at the mobile terminal. The P05 terminal may generate the data or download it remotely.

Optionally, the machine-readable image may contain a network link to the electronic receipt data. This link may be a URL or other address or pointer encoded within the machine-readable image, for example. Once followed by the mobile terminal, the electronic receipt data may be acquired across a network.

Preferably, the display unit and terminal may be the same device. This may be a card reader terminal, for

example.

Optionally, the electronic receipt generator may be remote from the terminal and connectable to the terminal over a network.

Preferably, the terminal may be a point of sale, POS, terminal.

Optionally, the transaction may be completed by any of: a credit card; a debit card; cash; Europay (TM) Mastercard (TM) VISA (TM), EM\, chip; ccntactless payment; mobile

telephone; or near field communication, NFO. Other

transaction types may be used.

According to a second aspect, there is provided a method for operating on a mobile terminal for obtaining an electronic receipt comprising the steps of: acquiring a machine-readable image, the machine-readable image representing data associated with a transaction, and obtaining an electronic receipt of the transaction from the machine-readable image. This method may be implemented as an application executed on the mobile terminal such as a cell phone, for example. The electronic receipt of the transaction may be stored locally on the external device or sent to another location. Preferences may be set on the mobile device to send the electronic receipt by email or SMS, for example.

Optionally, obtaining the electronic receipt from the machine-readable image may further comprise the step of decoding electronic receipt data from the machine-readable image. In this case, the machine-readable image contains the electronic receipt data and so the mobile terminal doesn't reguire an active data connection. The machine-readable image may contain data from more than one transaction.

Optionally, obtaining the electronic receipt from the machine-readable image may further comprise the step of decoding a network link from the machine-readable image and following the network link tc remotely stored electronic receipt data. In this case, the machine-readable image doesn't necessarily contain the electronic receipt data (although it could as well) and so the mobile terminal can validate or authenticate the data remotely.

Advantageously, the method may further comprise the step of authenticating the electronic receipt. This may be achieved within the mobile terminal so that it can trust the merchant, POS terminal or automated teller machine (ATM) displaying the machine-readable image.

Optionally, the step of authentication may further comprise the step of obtaining authentication information from a server. This may be achieved across a network.

Authentication may also come from a card issuer (of the card used to make the transaction) or other entity.

According to a third aspect there is provided a method for issuing an electronic receipt comprising the steps of: generating electronic receipt data of a transaction; acquire a machine-readable image representing the electronic receipt data; and displaying the machine-readable image to an external device for the external device to obtain the electronic receipt data based on the machine-readable image.

This method may take place within a retail environment, preferably using a POS terminal or within an ATM. The external device may be a mobile terminal that can capture the machine-readable image and extract data contained within.

Optionally, the acquired machine-readable image is received from an external server. There are several ways in which the machine-readable image may be received. It may be generated at the point of use as and when required. This means that an active data connection to a network is not required. However, security may be improved by receiving the machine-readable image or data necessary to generate it from an external source.

Preferably, the method may further comprise the step of authenticating the received machine-readable image.

Optionally, the acquired machine-readable image may be locally generated.

Preferably, the external device may be a mobile terminal. Other preferably portable devices may be used.

Optionally, the method may further comprise the steps of: receiving from the external device, data represented by the machine-readable image; and transmitting to the sender the electronic receipt data in response to the received data.

Optionally, the machine-readable image may contain the electronic receipt data.

Optionally, the machine-readable image may contain a network link to the electronic receipt data. The machine-readable image may contain both the electronic receipt data and a link (e.g. for verification or additional information) Optionally, the method may further comprise the step of authenticating the electronic receipt data within the external device.

Optionally, the step of authenticating the electronic receipt data may further comprise the steps of: applying a hash function to the electronic receipt data to generate a checksum; and comparing the generated checksum with a received checksum. Additional security may be included such as digital signatures and public and private key encryption,

for example.

The methods described above may be implemented as a computer program comprising program instructions to operate a computer. The computer program may be stored on a computer-readable medium.

It should be noted that any feature described above may be used with any particular aspect or embodiment of the invention.

Brief description of the Figures

The present invention may be put into practice in a number of ways and embodiments will now be desoribed by way of example only and with referenoe to the a000mpanying drawings, in which: FIG. 1 shows a schematic diagram of a system for providing an electronic receipt, given by way of example only; FIG. 2 shows a flow chart of a method for providing an electronic receipt; FIG. 3 shows a flow chart of a method for receiving an electronic receipt; and FIG. 4 shows a flow chart of a method carried out by a server processing transaction data.

It should be noted that the figures are illustrated for simplicity and are not necessarily drawn to scale.

Detailed description of the preferred embodiments

Machine-readable images that represent or encode data such as Quick Response (QR) codes or 2D barcodes may be generated within a Payment Terminal environment and presented on a point of sale (POS) display to provide certifiable' electronic payment transactions receipt data which can be captured anonymously by the cardholder via the use of a mobile QR/barcode reading application. For simplicity, these machine-readable images are described as

QR codes throughout this description.

This allows the customer (cardholder or cash customer, for example) to capture, at the time of purchase, a valid -10 -electronic payment receipt or payment receipt token by the reading the QR/2D bar code on their mobile. This can be used to provide full payment receipt details in real-time or at a later date without sharing personal data with a merchant. The only data shared may be that relating directly to the card payment transaction process.

The electronic payment receipt may be certified or authenticated. In other words, the electronic receipt may include all variable or mandatory transaction data elements specified by a card acquirer and issuing organisations for the receipt to be considered valid. This may include EMV, Magstripe, Contactless & NFC payment transactions as well as cash payments, for example.

To ensure the authenticity of the QR code or 2D barcode, the data used to create the image may be authenticated within the P05 environment. For example authenticity or integrity of the data may be checked by individually hashing (MAC'ing) the QR code data or alternatively ensuring this data is provided within integrity security functions of the payment message delivery system.

The P05 device may only allow authenticated data to be used to create a QR Code or 2D Bar Code for display.

This process will ensure the integrity of the receipt origins and can be further enhanced if either the local mobile application or remote server carries out further verification based upon data hashes, MAC'ing or other authentication.

-11 -Once captured, there are a number of options as to how the receipt can then be presented/delivered electronically to the cardholder. This may be locally through a mobile terminal application (smart phone, tablet or PDA, for example) or on-line via mobile web services or even via SMS.

The customer may also choose locally via the Mobile application where the receipt data should be sent. For example, they could enter into a trusted mobile Application ]0 their personal details so that every-time a payment receipt is captured via that application it will send the receipt data to a default e-mail address or mobile number (for SMS) This ensures that the customer only needs to share this information with a single trusted entity that is providing an authenticated and validated mobile application and service.

The QR code or 2D barcode presented on the point of sale display can provide a number of different formatted options including: 1. Encrypted non sensitive card Data elements presented in QR code format which can then be decrypted by the local Mobile Application and presented on the mobile phone display and stored. This can be done by a thick client application on the mobile which can extract the card data elements from the QR code and place them into a pre-oonflgured receipt layout format for display on through the mobile application.

2. Unprotected (Clear) non-sensitive card Data elements presented in QR code format which can then be -12 -presented on the mobile phone display and stored. This can be done by a thick client application on the mobile which can extract the card data elements from the QR code and place them into a pre-configured receipt layout format.

3. Unique URL or Web Link which can be managed by the local mobile application to either pull down securely the card receipt data elements tc present locally on the device as above or alternatively may simply allow the user to view the receipt on-line and choose where to send a copy for their local printing and storage.

4. Unique URL or Web Link -I-Contact Details for the Merchant. The QR code could hold both a unique payment URL and information regarding the merchants such as on-line website, telephone or mobile contact details, and special discount codes etc., which cculd be used by the application to store in the general mobile contacts or in a specific repository for that mobile application.

5. The QR Code or 2D data could also include specific data to generate an FAN barccde on the electronic receipt presented on the Mobile phone display which could be used by the Merchant to verify the receipt and scan into their system in the event of a refund or return of goods process.

Cther barcode formats may be used Including but not limited to Code 128.

The Process Flow for QR Code/2D Barcode Payment Receipt Capture at POS.

The following summarises the high level process that is followed to deliver an anonymous, secure electronic receipt -13 -from the P05 terminal using QR codes or 2D barcodes. Each stage of the process is numbered and reflected on figure 1.

1. Cardholder inserts payment card/Swipes/Taps / Tap mobile phone.

2. The payment transaction is processed by the P05 using payment standard processes.

3. The Authorisation response returned to the P05 includes additional QR Code/ 2D barcode data.

4. The P05 receives the Payment response and processes the payment (Authorised/Deolined eto) 5. The P05 then takes the QR Code/2D Bar Code data received and authenticates to ensure it is valid and from a secure source.

6. The P05 then runs a QR oode/2D bar code generator within its secure environment and creates a QR/2D code image for display on the P0S Display.

7. The P05 displays the QR Code /2D bar Code on the P05 Display.

8. The cardholder launches a mobile application on their Mobile terminal (Tablet/PDA/Smartphone) to read the QR Code/2D barcode.

9. The Mobile Application reads the Code and confirms to the cardholder they have obtained an electronic receipt.

The confirmation can be provided only if the Mobile Application has verified it has either: -14 -a) Captured all of the main data elements to present on a receipt using the Mobile application.

b) Captured a valid URIJ based upon proprietary checks/validation of data which it can use to retrieve the transaction data from a secure server at a later time.

10. Depending on the Mobile application method used to present the receipt the mobile App will:-a) Provide a visual receipt to the cardholder on the mobile display which is then stored locally as well as a copy will be on the originating server where the data was sent.

b) Contact the remote server using the unigue ORb/Data provided and retrieve the receipt data to provide a visual receipt to the cardholder on the mobile display which is then stored locally as well as a copy will be on the originating server.

c) One of the above and will then ask the Cardholder where they want the receipt sending. (If they have default settings then it will automatically send the electronic copy to that setting i.e. default e-mail) e) One of the above but will also provide the cardholder with an option to save additional contact details for the merchant which were contained in the QR Code.

f) One of the above and include Loyalty or Voucher details within the payment receipt presented/stored.

11. Transaction Complete and cardholder has captured a valid payment receipt electrcnically and anonymously without passing personal information to the merchant.

Note: In the event of a refund or return of goods then the cardholder can do the following: -15 -a) Present a copy of the receipt visually to the merchant on the display of their mobile.

b) The Mobile Application displays the original QR Code/2D Barcode for scanning by the retailer equipment to trigger the refund.

c) The original receipt contained an FAN barcode as part of its data and this can be displayed on the mobile and scanned by the merchant using traditional bar code scanning equipment.

As shown in figure 1 (step 3) payments may be authorised by a payment gateway or acquirer. In addition to payment or other transaction data, the QR code data are also returned securely in an authorisation response via this channel.

At step 6, the card or mobile payments processed through a POS device and QR or 2D barcodes are displayed on the device display at the end of a transaction to allow a cardholder to capture electronic receipt data without requiring the transfer of personal details to the merchant.

At step 9, the QR or 2D barcodes are generated within the secure environment of the point of sale device using data supplied via the payment response and the data authenticated or verified using security features of the P05 prior to generating the data in QR oode format for display.

At step 8, the cardholder completes payment transaction using card or mobile device in the usual manner. This may take the form of an FMV chip, magnetic stripe, contactless -16 -payment or near field communication, for example. The cardholder then scans the POS display to read the QR code using a reader application on the mobile phone which accesses an onboard camera. The readout application confirms when successfully read and a cardholder may provide details of the card payment receipt electronically. The payment receipt can be generated off-line in real time (visually) for the cardholder or unique data captured from the QR code can be used to pull down the electronic receipt details securely from a remote server.

At step 10, the mobile application can use the unique data captured from the QR code to link to a remote server to download or provide a viewable payment receipt. This may include loyalty or discount details and/or a standard barcode. This allows the card or account holder to capture a receipt even when off-line or in the absence of a reliable data connection and pick up the data when the mobile application has access to a data connection.

At step 11, the payment receipt can be shown locally on the mobile device and include any loyalty or voucher data retrieved from the QR code or added by the remote server.

Alternatively, the application may simply link to the remote server and show an on-line copy of the receipt.

The application on the mobile terminal can be used to manage the cardholder's preferred settings so that when a receipt is captured it may be automatically c-mailed to a default or configurable e-mail account of their choice.

Figure 2 shows a flowchart of a method 100 used to provide an electronic receipt of a transaction. At step -17 - 110, a transaction is initiated. This may occur within a retail environment between a merchant and a customer, for example. Completion of the transaction takes place at step 120. This may be achieved by the customer paying for goods and services. For example, this may be achieved by handing over cash or using a credit cr debit card. Alternatively, non-contact payment techniques may be used. Authentication and validation of such a completed transaction may take place in the usual way.

At step 130 electronic receipt data are generated.

This may be done by the financial transaction processing system or a separate electronic receipt generator.

Electronic receipt data may be generated locally or at a separate server connected over a network. The network may be the internet, for example. The electronic receipt data may contain specific items including but not limited to the transaction amount, the merchant's identity, the goods or services provided, the time and date of the transaction and any other information.

At step 140, a machine-readable image that represents data (such as a QR code, for example) is acquired.

Acquiring this QR code may be achieved locally from a QR code generator or remotely. Where the QR code is acquired from a remote location separate to the merchant's system, then authentication may take place at step 150 (i.e. within the terminal) . Local generation may not require authentication.

The QR code is then displayed to the customer who may then capture this with a mobile terminal such as their cell phone or camera phone, for example.

-18 -Figure 3 shows a flowchart of a method 200 carried out on the mobile terminal of the customer. This methcd 200 may take the form of a mobile application (running on a suitable mobile operating system), which is initiated or started at step 210. Capturing the QR code occurs at step 220. The data contained within the QR code may be extracted at step 230. The data may include electronic receipt data itself or a link to such data that may be downloaded by following this link. Additional information may be included to aid authentication.

At step 240, authentication of the extracted data may take place. Different types of authentication may occur.

For example, a hash algorithm may be applied to some or all of the extracted data to obtain a checksum or validation code. This checksum or validation code may be compared with a received checksum or validation code obtained across a network, preferably from the transaction processing server or electronic receipt data generating server. A match of the checksums indicates that the extracted data is authentic and has not been tampered with.

At step 250, the electrcnic receipt data is stored.

This may be stored locally on the mobile terminal or sent elsewhere, perhaps by electronic mail or other communication means.

Figure 4 shows a flowchart of a method 300 occurring within an electronic receipt issuing server. This server may be remote from both the point of sale device and customer, or maybe within the same organisation or device.

The server may also be located within the transaction -19 -processing terminal. The method 300 starts with a completed transaction being received at step 310. In some implementations, the server generates the QR code at 320.

In other implementations the QR code is generated by an external server or device. Again, the QR code may contain the electronic receipt data cr a link to such data.

At step 330 the QR code may be transmitted to the point of sale terminal (or other terminal) which then displays the QR code to the mobile terminal of the customer.

At step 340, the electrcnic receipt data may be stored together with any other information, including any necessary authentication information. Storage of the electronic receipt data may take place at any point in the method. At some later time, the server may receive an authentication reguest for a particular electronic receipt at step 350.

Once received, then authentication information may be sent to allow the mobile terminal or merchant to authenticate the data. At step 360, a checksum resulting from a hash function is transmitted.

Example payment related data elements include: Merchant Details (Can be ATM Location etc) Name/Address/Contact Details/web Address etc. Transaction Type: Sale/Refund/Cash withdrawl/Statement CardScheme: Visa, MasterCard, Amex, Discover etc. Card Number (PAN) : This is the cardholder number but masked with Asterix -* tc keep sensitive (Leaving First 6 and last 4 digits of the PAN) Card Number Expiry Date.

Cardholder Issue/Start Date.

Cardholder Name.

-20 -FF1 No: Electronic Funds Transfer No -Used as ID on many systems to Track Transaction.

Transaction ID: Unique Transaction or Receipt Identifier.

Transaction Decision: Authorised/Declined/Cancelled/Void etc (Note Electronic Receipts cover both successful and declined/failed transactions which mirrors receipts generated in these scenarios for the physical world.

Authorisation Code: Unique Response Code sent by the Card Issuer/Acquirer for that transaction.

Transaot ion Amount.

Product/Goods purchased Details: Simple Summary of

goods purchased under this payment transaction.

Date/Time of Transaction.

P03/Site ID Reference: Details of actual P03 or Site that did transaction/AIM details.

Server TD: Details of person who conducted the transactions.

Cardholder Verification Method (CVM) -Method used to authenticate the cardholder for that transaction i.e. PIN VERIFIED, Signature, None.

Iransaction Certificate (TC) : EMV cryptogram used by issuer to verify transaction.

Bar Code (EAN/Code 128 /Other) : The receipt may generate a standard retail Bar Code which can be used by the Merchant to scan receipt on return i.e. REFUND, to identify transaction automatically.

Loyalty Voucher Detail/Discount: May Contain Unique Numbers or Bard Code (FAN/Code 128 or other) to allow the merchant P05 to automatically read and verify discount or loyalty if the original payment receipt was issued with a future discount or loyalty/reward.

-21 -These may be standard elements or mandated by card schemes but otherwise provide some representative examples of fields included within a payment transaction receipt.

Other data elements may be included.

As will be appreciated by the skilled person, details of the above embodiment may be varied without departing from the scope of the present invention, as defined by the appended claims.

For example, the customer may also pay with cash and still receive the electronic receipt according the methods described.

The described system and method for providing an electronic receipt have used the specific example of a retail transaction occurring in a shop or restaurant with a customer paying for goods or services using any payment means. However, the system and method may be used to provide any type of receipt and especially receipts that may be authenticated or validated at a later time. For example, the system and method may be used to provide an electronic receipt of a transaction at an automated teller machine (ATM), automated banking machine (AEM) or cash machine. In this case the transaction may include a withdrawal of cash, deposit of cash and/or cheques or the querying of a balance

or the provision of a statement of account.

Additional security measures may be in place especially during data transfers.

Many combinations, modifications, or alterations to the features of the above embodiments will be readily apparent -22 -to the skilled person and are intended to form part of the invention. Any of the features described specifically relating to one embodiment or example may be used in any other embodiment by making the appropriate changes.

Claims

-23 -CLAIMS: 1. A system for issuing an eleotronic receipt comprising: a terminal configured to acquire details of a transaction; an electronic receipt generator arranged to generate electronic receipt data of the transaction; a machine-readable image generator arranged to generate a machine-readable image representing the electronic receipt data; and a display unit arranged to display the machine-readable image to an external device to obtain the electronic receipt data based on the machine-readable image.
2. The system of claim 1 further comprising a server comprising: an electronic storage configured to store the electronic receipt data.
3. The system of claim 2, wherein the server further comprises: a receiver configured to receive from a sender, data represented by the machine-readable image; and a transmitter configured to transmit to the sender the electronic receipt data in response to the received data.
4. The system of claim 2 or claim 3, wherein the server further comprises an authenticator configured to respond to an authentication request to authenticate the electronic reoeipt data.
5. The system according to any previous claim, wherein the machine-readable image is selected from the group consisting -24 -of: barcode; two-dimensional barcode; Quick Response Code (TM); QR code; and matrix barcode.
6. The system according to any previous claim, wherein the machine-readable image contains the electronic receipt data.
7. The system according to any previous claim, wherein the machine-readable image contains a network link to the electronic receipt data.
8. The system according to any previous claim, wherein the display unit and terminal are the same device.
9. The system according to any previous claim, wherein the electronic receipt generator is remote from the terminal and connectable to the terminal over a network.
10. The system according to any previous claim, wherein the terminal is a point of sale, P08, terminal.
11. The system according to any previous claim, wherein the transaction is completed by any of: a credit card; a debit card; cash; Europay (TM) Mastercard (TM) VISA (TM) , EMV, chip; contactless payment; mcbile telephone; or near field communication, NFC.
12. A method for operating on a mobile terminal for obtaining an electronic receipt comprising the steps of: acquiring a machine-readable image, the machine-readable image representing data associated with a transaction, and obtaining an electronic receipt of the transaction from the machine-readable image.

-25 -
13. The method of claim 12, wherein obtaining the electronic receipt from the machine-readable image further comprises the step of decoding electronic receipt data from the machine-readable image.
14. The method of claim 12, wherein obtaining the electronic receipt from the machine-readable image further comprises the step of decoding a network link from the machine-readable image and following the network link to remotely stored electronic receipt data.
15. The method according to any of claims 12 to 14 further comprising the step of authenticating the electronic receipt.
16. The method of claim 15, wherein the step of authentication further comprises the step of obtaining authentication information from a server.
17. A method for issuing an electronic receipt comprising the steps of: generating electronic receipt data of a transaction; acquire a machine-readable image representing the electronic receipt data; and displaying the machine-readable image to an external device for the external device to obtain the electronic receipt data based on the machine-readable image.
18. The method of claim 17, wherein the acquired maohine-readable image is received from an external server.

-26 -
19. The method of claim 18 further comprising the step of authenticating the received machine-readable image.
20. The method of claim 17, wherein the acquired machine-readable image is locally generated.
21. The method according to any of claims 17 to 20, wherein the external device is a mobile terminal.
22. The method according to any of claims 17 to 21 further comprising the steps of: receiving from the external device, data represented by the machine-readable image; and transmitting to the sender the electronic receipt data in response to the received data.
23. The method according to any of claims 17 to 22, wherein the machine-readable image ccntains the electronic receipt data.
24. The system according to any of claims 17 to 23, wherein the machine-readable image contains a network link to the electronic receipt data.
25. The method according to any of claims 17 to 24 further comprising the step of authenticating the electronic receipt data within the external device.
26. The method of claim 25, wherein the step of authenticating the electronic receipt data further comprises the steps of: applying a hash function to the electronic receipt data to generate a checksum; and -27 -comparing the generated checksum with a received checksum.
27. A method substantially as described with reference to any of the accompanying drawings.
28. An apparatus substantially as described and shown in any of the accompanying drawings.
29. A computer program comprising program instructions that, when executed on a computer cause the computer to perform the method of any of claims 12 to 27.
30. A computer-readable medium carrying a computer program according to claim 29.
31. A computer programmed to perform the method of any of claims 12 to 27.