Data carrier, reader device, system and method for generating digital transaction receipts

Abstract

The invention relates to a data carrier (100). The data carrier (100) comprises a data memory (110), a data carrier processor (120), a contactless and / or a contact-based data carrier interface (130), and an application (111) stored in the data memory (110). The data carrier processor (120) is configured to execute the application (111). The application (111) comprises a data element (112) which contains personal contact data of an owner of the data carrier (100). The data carrier processor (120) is configured to carry out a transaction process with a reader device (200) at the request of the reader device. The application (111) is configured to read the personal contact data of the owner of the data carrier (100) from the data element (112) and to make said data available to the reader device (200) such that the personal contact data can be used by the reader device (200) to create and send a digital transaction receipt via the transaction process. The invention further relates to a reader device (200), to a system (300) having a data carrier (100) and a reader device (200), and to a corresponding method (400).

Description

[0001] Data carrier, reading device, system and method for generating digital transaction documents

[0002] The present invention relates to a data carrier, a reading device, a system and a method for automatically sending digital transaction documents for transactions, in particular payment card transactions.

[0003] Due in part to ongoing efforts to protect the environment and due to increasing digitalization, there are efforts in all areas of life to reduce unnecessary paper consumption.

[0004] Particularly in payment transactions (for example, in retail), some countries have legal obligations to issue a receipt for corresponding payment transactions at the point of sale (POS). These receipts are usually printed on paper and, in most cases, simply discarded afterward. This unnecessary paper consumption incurs costs and is also detrimental to the environment.

[0005] Therefore, various initiatives to provide payment receipts digitally have been underway for some time. These initiatives include, for example, a payment terminal (POS terminal) prompting the buyer to enter their email address, after which the receipt is sent to that email address instead of being printed. Another option is dedicated software applications, such as those on smartphones, as part of customer loyalty programs or other mobile apps. With such solutions, a corresponding identifier (such as a QR code) can be scanned or entered by the customer at the point of sale, after which the payment receipt is made available for retrieval in the corresponding application (or in a user account assigned to the user).

[0006] However, such solutions are often cumbersome and not truly user-friendly, as they require, for example, entering an email address or using additional applications on a payment card or mobile phone, and rely on centralized databases with all the associated data privacy concerns and costs. Furthermore, current POS and POI implementations cannot securely transmit private data between the card and the terminal.

[0007] Accordingly, the object of the present invention is to provide a device and a method that enable a simple and secure way to provide digital transaction receipts.

[0008] This problem is solved by the subject matter of the independent claims. Exemplary embodiments are described in the dependent claims and the following description. Further features of the invention are shown in the figures and the description of the figures.

[0009] This document discloses a data carrier and a reader configured to generate a digital transaction document, a system comprising the data carrier and the reader, and a method for generating a digital transaction document. All features described with respect to one of these aspects are also valid for the other aspects and vice versa.

[0010] According to a first aspect, a data carrier is disclosed. The data carrier comprises a data storage device, a data carrier processor, a contactless and / or contact-based data carrier interface, and an application stored in the data storage device. The data carrier processor is configured to execute the application. The application includes a data element containing the personal contact information of the data carrier's owner. The data carrier processor is configured to perform a transaction operation with a reader while the data carrier is in a communication connection with the reader via the data carrier interface.The application is configured to read the personal contact details of the data carrier owner from the data element and make them available to the reader, so that the personal contact details can be used by the reader to create and send a digital transaction receipt about the transaction.

[0011] The data carrier can be any type of data carrier used to carry out transactions, in particular, for example, a card-shaped data carrier in the form of a smart card, such as a payment card like a credit or debit card. However, the data carrier can also be, for example, an identity document or any other data carrier that enables any type of transaction, or even a virtual card, as described below. In the following, the data carrier is primarily described using the example of a payment card in the form of a smart card. It should be noted, however, that this disclosure is not limited to such payment cards. The application can be part of a transaction application or can be a standalone application that serves (either exclusively or in conjunction with other conceivable functions) to provide personal contact information.

[0012] A contact-based data carrier interface could be, for example, the contact area of ​​a card chip. A contactless data carrier interface could be, for example, a contactless NFC interface.

[0013] To avoid manually entering contact information such as an email address or phone number, or using additional software applications to generate a digital transaction receipt (such as a digital purchase receipt / till receipt in the form of a PDF document or another suitable file format), the data carrier or its data storage contains an additional data element containing the personal contact information. This application, which can be designed as part of a transaction application or as a standalone application, is integrated into the data carrier or its data storage. A transaction application is a software application used by the data carrier's processor to execute the transaction (e.g., a payment) with a corresponding reading device (e.g., a POS terminal). The software application can be executed directly by the data carrier's processor, or in some cases (e.g., with Java solutions) indirectly.through a suitable interpreter, such as a virtual machine. The transaction application preferably operates, particularly with payment cards, according to the EMV standard. This is generally known in the prior art. However, no personal contact details are currently transmitted during a transaction. According to the invention, during a transaction process, such as a payment transaction carried out with the data carrier, the personal contact details are transmitted to the reader. For this purpose, the transaction application can be extended with the functions of the application mentioned here for providing personal data, or a separate application can be provided for this purpose. This transmission can take place before, during, or after the actual transaction process. Furthermore, the personal contact details can either be sent / transmitted directly to the reader by the application, e.g.,as part of the transaction data to be exchanged, or the reading device is granted read access to the corresponding data element or storage.

[0014] The reader can then use this personal contact information to generate a digital transaction receipt containing the essential transaction data and send it to the data carrier owner, for example, via email. This allows for the simpler and automated generation of a digital transaction receipt, eliminating the need for paper receipts. The data carrier owner does not need to manually enter the relevant data during the transaction or use a loyalty app, as described earlier.

[0015] Personal contact details can be stored either during the personalization of the data carrier, for example, when a corresponding payment card is produced, or subsequently by the data carrier owner themselves. For instance, it is conceivable that the owner could add and / or change their personal contact details in a software application associated with the data carrier (such as an online banking app). This could be achieved, for example, by pre-loading the data carrier with the personal contact details using the owner's reading device (e.g., via the NFC interface of a smartphone running the online banking app).Another possibility would be for a software application (such as an online banking app) to first transfer the changed or added personal contact details to a remote server (e.g., via the internet) and assign them to the data carrier. This data would then be transferred to the data carrier by the corresponding reader at the POS the next time the card is used. Alternatively, the cardholder could be offered the option to add and / or change contact details at the POI (Point of Interest), i.e., when a payment card is inserted into the POS terminal, which would then store these details in the data element.

[0016] According to one embodiment, the data carrier is a physical card-shaped data carrier or a virtual representation of a card-shaped data carrier. Such a physical card-shaped data carrier could, for example, be a payment card in the form of a smart card, such as a credit card or a debit card. A virtual representation of such a card-shaped data carrier refers to a digital version of such a physical card-shaped data carrier, as used in digital wallets, for example, in smartphones, smartwatches, or other smartwear devices. It should be noted, however, that the virtual representation of the card-shaped data carrier does not necessarily have to have a physical counterpart. Rather, the data carrier can also be a purely virtual data carrier, for example, a wallet-style credit card or wallet-style debit card.

[0017] In the case of a payment card, the transaction process would be a payment transaction, and the digital transaction receipt would be, for example, a digital receipt in a suitable machine-readable format (for example, without limitation, a PDF file of the receipt). It should be noted, however, that the card-shaped data carrier does not necessarily have to be a payment card, but can be any type of card-shaped data carrier with which any type of transaction can be carried out. An identity card for the digital authentication of a user is mentioned here only as a non-restrictive example. In such a case, the transaction process would be the authentication, and the transaction receipt could, for example, be proof of successful or failed authentication. This is, however, just another example.The terms “transaction process” and “transaction receipt” are to be understood in a comprehensive sense in this context.

[0018] According to another embodiment, the data carrier is a payment card or an identity document.

[0019] A payment card can be, for example, a credit card or a debit card that provides payment transactions using the EMV standard. An identity document can be, for example, a corresponding smart card ID, a national identity card, or any other suitable identity document. According to another embodiment, the personal contact details of the data carrier holder include at least one of the following: an email address, a telephone number, and an identifier.

[0020] An email address or phone number, for example, can be used by the reader to send the digital transaction receipt via a suitable communication server, such as an email server, SMS server, or similar. An identifier could be, for example, an identification number or customer account number, allowing the transaction receipt to be added to the customer account and thus retrieved by the customer (or, more generally, the owner of the data carrier). It is also possible to store the transaction receipt on a suitable online server and send the customer a download link via SMS or email, depending on the type of personal contact information. The transaction receipt itself could optionally be encrypted or password-protected.

[0021] According to another embodiment, the application is configured to communicate with the reader via a secure channel protocol based on an asymmetric cryptographic method and to transmit personal contact details.

[0022] One such asymmetric cryptographic method could be a Diffie-Hellman key exchange, such as the "Blinded Diffie-Hellman" method, which is already included in the latest EMV specifications and thus enables the secure exchange of data, such as personal data, over an otherwise potentially insecure channel. The cryptographic method secures the communication link itself. However, other cryptographic methods for securing the communication link are also conceivable. Such asymmetric cryptographic methods are generally known and are therefore not explained in detail here. Cryptographic methods that may only appear in the future, such as post-quantum cryptography (PQC), can also be used in due course.

[0023] Optionally, the cardholder can configure whether an encryption method should be used by default, for example, using a corresponding software application such as an online banking app (in the case of payment cards) or another associated app. If implemented according to a standard, the card reader could also prompt the cardholder to choose whether encryption should occur before transmission. Alternatively, the card issuer can configure these settings on the card itself for the cardholder.

[0024] According to another embodiment, the application is configured to sign the transaction document created by the reader, before the transaction document is sent by the reader, using a private key stored in the data storage.

[0025] By having the application sign the transaction document in this way, manipulation of the transaction document is prevented. For example, the transaction document can first be provided to the application by the reader, which then performs the signing. The signed transaction document is then sent by the reader.

[0026] According to a second aspect, a reader is provided for a data carrier according to one of the embodiments described herein. The reader comprises a reader processor and a contactless and / or contact-based reader interface. The reader processor is configured to establish a communication link with the data carrier interface via the reader interface. The reader processor is configured to receive the data carrier owner's personal contact information from the data carrier via the reader interface. The reader processor is configured to create a digital transaction receipt for a transaction carried out with the data carrier and send it to the data carrier owner using the personal contact information.

[0027] The reader interface is designed to correspond to the data carrier interface. For example, the reader can be a smart card reader, such as a POS terminal in the case of a payment card. At some point after establishing communication with the data carrier, the reader, or rather its reader processor, receives the personal contact details of the data carrier's owner, as described above in relation to the data carrier. Once the transaction is complete, the reader generates a corresponding transaction receipt and sends it to the data carrier's owner. This transmission can be handled, for example, via a communication server, as described below.

[0028] In one embodiment, the reader itself includes a communication server or is connected to an external communication server. The transaction document is sent via the communication server.

[0029] The communication server can be, for example, an email server that can send emails to an email address contained in the personal contact information, or an SMS server, or something similar, as described above. The communication server can also be an external server that is not part of the reader itself, but is only connected to it, or rather to a corresponding data interface (e.g., a packet-based network interface) of the reader. Since readers such as POS terminals already have network or internet access, providing such a communication server within the reader itself is essentially a software-based adaptation of such readers that does not require any hardware changes. With an external server as the communication server, the relevant data only needs to be transmitted to it, for example, via IP, which then processes the data.The transaction receipt is then forwarded, for example, as an email.

[0030] The above explanations regarding the first aspect (data carrier) already encompass all the necessary information for understanding the reading device and will not be repeated here. Reference is made to the corresponding explanations regarding the first aspect.

[0031] According to another embodiment, the reader processor is configured to encrypt the created transaction document with a public key stored in the data storage of the data carrier before the transaction document is sent by the reader.

[0032] Such a public key can be provided to the reader, for example, via the data carrier along with personal contact information, or at another time before the transaction receipt is sent. For instance, the public key could be a PGP public key, which the reader uses to encrypt the transaction receipt before sending it. The owner of the data carrier can then decrypt the received transaction receipt with their private key. This is just one example, however, and other suitable encryption schemes can also be used. This ensures that the transaction receipt cannot be read by unauthorized persons.

[0033] Optionally, the owner of the data carrier can choose whether encryption should take place by default, similar to what was described above regarding the use of asymmetric cryptographic methods. With a corresponding implementation according to a standard, the owner could also be prompted by the reading device to choose whether encryption should take place before transmission.

[0034] According to another embodiment, the reader processor is configured to sign the created transaction document with a private key before sending it.

[0035] The private key can be a private key of the data carrier to which the reader is granted access, or a private key of the reader itself.

[0036] According to a third aspect, a system is disclosed. The system comprises a data carrier according to one of the embodiments described herein and a reading device according to one of the embodiments described herein. The data carrier is configured to establish a communication connection with the reading device via the data carrier interface and the reading device interface. The data carrier processor and the reading device processor are configured together to perform a transaction. The reading device processor is configured to retrieve the personal contact information of the data carrier owner from the data carrier. The reading device processor is configured to create a transaction document for the completed transaction and to send the created transaction document to the data carrier owner using the personal contact information.

[0037] The system aspect and the necessary explanations follow directly from the above explanations regarding the data carrier and the reading device. For details regarding this third aspect (system), reference is therefore made to the explanations concerning the first two aspects. A fourth aspect discloses a method for providing a digital transaction receipt for a transaction carried out with a data carrier to the holder of that data carrier.The process includes establishing a communication link with the data carrier, carrying out a transaction with the data carrier, creating a digital transaction document about the transaction carried out, receiving personal contact details of a data carrier owner from a data element of the data carrier, and sending the created digital transaction document to the data carrier owner using the personal contact details via a communication server.

[0038] The corresponding procedural steps are self-explanatory with regard to the above explanations concerning the data carrier, the reading device, and the system. All explanations made with reference to these device aspects or device claims are directly applicable to the method as well, so the corresponding statements are not repeated here.

[0039] Exemplary embodiments of the invention are explained in more detail below with reference to schematic drawings.

[0040] This shows:

[0041] Fig. 1 shows an exemplary data carrier in the form of a smart card, configured to provide personal contact details to a reader (such as the one shown in Fig. 2) for sending a digital transaction receipt.

[0042] Fig. 2 shows an exemplary system arrangement consisting of a data carrier and an associated reader, using a payment card as the data carrier and a payment terminal (POS terminal) as the reader for the payment card as an example.

[0043] Fig. 3 shows a flowchart of a process for providing a digital transaction receipt for a transaction carried out with a data carrier, for example a payment card, to the holder of the data carrier. In the figures, identical or functionally equivalent elements are labeled with the same reference symbols. The representations in the figures are schematic and not to scale.

[0044] Fig. 1 shows an exemplary data carrier 100. Fig. 2 shows an exemplary arrangement of a system 300 consisting of the data carrier 100 from Fig. 1 and a reading device 200. For clarity, Fig. 2 depicts the data carrier with fewer details. Figs. 1 and 2 are described together below. In the illustrated embodiment, the data carrier 100 is a payment card (e.g., in the form of a smart card), such as a credit or debit card. However, it should be noted that the data carrier 100 does not have to be a dedicated physical data carrier 100 (e.g., in the form of a card), but could also be a virtual card, e.g., readable in a corresponding wallet on a smartphone, smartwatch, or other smartwear device. In the illustrated embodiment, the reading device 200 is a payment terminal (POS terminal) 200, which is used to carry out transaction processes (card transactions), i.e.,especially payment transactions, with which data carrier 100 is configured.

[0045] The data carrier 100, in the illustrated embodiment, comprises a contactless data carrier interface 130 in the form of an NFC interface, which is formed from corresponding coils connected to a card chip or, more generally, a data carrier processor 120, as is known in the prior art. The data carrier 100 also comprises a contact-based data carrier interface 131, which is provided by the corresponding contact surfaces of the card chip, as is also known in the prior art. Although the data carrier 100 is illustrated and described with both a contactless interface 130 and a contact-based interface 131, it should be clear that the data carrier can also comprise only one of these interfaces 130 or 131. The data carrier 100 also has a data storage device 110 in which, among other things, an application 111 is recorded.Application 111 can be a transactional application that enables the data carrier processor 120 to execute a transaction, i.e., in the example shown, in particular to carry out payment transactions, and additionally includes the corresponding functions described for document creation. However, the application can also be a standalone application that serves only for document creation. Application 111 further includes another data element 112, which contains personal contact information, for example, of the owner of the data carrier 100. Such data elements are not used in the prior art. The personal contact information can, for example, include an email address and / or a telephone number and / or another suitable identifier, as described above. It should be noted that the data carrier processor 120 and the data storage device 110 are shown in Fig.1. Elements related to the card chip are shown schematically as boxes. However, the data storage processor 120 and the data storage 110 are usually part of the card chip itself. This is generally known in the prior art and will not be discussed further.

[0046] The reader 200 (see Fig. 2), as shown, has a contactless reader interface 230 (e.g., an NFC transmitter / receiver module) corresponding to the contactless data carrier interface 130 and a contact-based reader interface 231 (e.g., a smart card read / write head designed to correspond to the card chip or its contact area) corresponding to the contact-based data carrier interface 131. However, the reader can only include one of these interfaces 230, 231. The reader 200 can communicate with the data carrier 100 via one or both of the interface pairs 130, 230 or 131, 231. In particular, for example, in wallet implementations with virtual cards, the contact-based data carrier interface 131 can be omitted. In general, only one interface pair 130, 230 or 131, 231 is required.The reader 200 also includes a reader processor 220 and, in the configuration shown, a software-based communication server 240 (e.g., an email server 240). However, the communication server can also be an external server outside the terminal and, for example, be implemented in a server (typically at the merchant's bank). In such configurations, the terminal can send the transaction confirmation along with the transaction data to the bank (acquirer), where the email / SMS can then be generated and sent. The communication server 240 is shown in Fig. 2 as part of a memory 210 of the reader 200, which is connected to the reader processor 220. It should be noted that this only represents the corresponding software instructions for implementing the communication server 240; its functions are, of course, performed by the reader processor 220.In particular, if the communication server 240 is not implemented by the reader 200 itself, but rather on an external bank server, the transaction document can also be transmitted together with the transaction confirmation via the existing communication interface to the bank's server, whereupon the bank sends the transaction document. Even if the communication server 240 is implemented by the reader 200 itself, it can still use this existing communication interface to send the transaction document, for example, as an email. After being sent by the communication server, the digital transaction document is transmitted, for example, via an internet connection, to a receiving server 250, from which the owner of the data carrier 100 can retrieve the transaction document.

[0047] The data carrier 100 and the reader 200 of Figs. 1 and 2 are each configured to carry out the procedure 400 described below with reference to Fig. 3.

[0048] Method 400 is described below with reference to Fig. 2 and with continued reference to Figs. 1 and 2.

[0049] In a first step 410 of the procedure 400, a communication connection is established between the data carrier 100 and the reader 200. This can be done, for example, by inserting the data carrier 100 into the reader 200 in such a way that the contact-based data carrier interface 131 comes into contact with the contact-based reader interface 231, or by bringing the data carrier 100 close to the reader 200 in such a way that the contactless data carrier interface 130 and the contactless reader interface 230 are within reception range.

[0050] In a next step 420, as usual, a transaction process (i.e., in the case of a payment card, in particular a payment process) is carried out by a transaction application of the data carrier 100, which may be, for example, the application 111 if it is implemented by the transaction application, or which may also be an application of the data carrier 100 different from the application 111.

[0051] In step 430, the reader 200 then creates a digital transaction receipt, e.g., a digital cash register receipt for a payment transaction. Optionally, in step 431, the digital transaction receipt can be signed by the data carrier processor 120 or the reader processor 220 with a private key stored on the data carrier 100 and / or encrypted in an optional step 432 with a corresponding public key stored on the data carrier 100, as described above. In particular, when signing by the reader processor 220, it must be ensured that the private key is not copied, for example, by a corresponding technical configuration of the reader 200 that cannot be changed by the owner of the reader.Signing serves primarily to prevent manipulation of the transaction document, while encryption ensures that only the owner of data carrier 100 can read the digital transaction document. The owner of data carrier 100 can, for example, make a default setting regarding optional steps 431 and 432, which is stored on data carrier 100, or may be prompted by the reader 200 to choose whether to sign or encrypt the current transaction.

[0052] In step 440, the reader 200 also receives the personal contact details of the owner of the data carrier 100. It should be noted that step 440 can take place at any time after the communication connection has been established and before the transaction document is sent in step 450, as described below, and does not necessarily have to occur before the transaction document is created in step 430. In general, any technically feasible sequence of steps 420 to 450 is permissible. The sequence described herein serves only as an example to illustrate the disclosed concept and is in no way restrictive.

[0053] In a final step 450, the generated (and optionally signed and / or encrypted) digital transaction document is then sent in a machine-readable format (e.g., as a PDF file) to the owner of the data carrier 100 via the communication server 240 (e.g., an email server 240), which is implemented by the reading device processor 220, or by a bank server, using the personal contact information. For this purpose, the digital transaction document is transmitted, for example, via an internet connection to a receiving server 250, from which the owner of the data carrier 100 can retrieve the transaction document. If the transaction document has been encrypted, the owner of the data carrier 100 can then decrypt it with a private key.

[0054] It should also be noted that "comprehensive" or "comprising" does not exclude other elements or steps, and "a" or "an" does not exclude a plurality. Furthermore, it should be noted that features or steps described with reference to one of the above embodiments may also be used in combination with other features or steps of other embodiments described above. Reference numerals in the claims are not to be considered as limitations.

[0055] Reference symbol list

[0056] Data carrier

[0057] Data storage

[0058] Application Data Element

[0059] Data storage processor, contactless data storage interface, contact-based data storage interface

[0060] Reader, payment terminal (POS terminal) memory

[0061] Reader processor, contactless reader interface, contact-based reader interface, communication server, email server, receiving server

[0062] system

[0063] Proceedings

[0064] Establishing a communication connection; Executing a transaction; Creating a digital transaction document; Signing the digital transaction document; Encrypting the digital transaction document; Receiving personal contact information; Sending the digital transaction document

Claims

Patent claims 1. Data carrier (100), comprising: a data storage device (110); a data carrier processor (120); a contactless and / or contact-based data carrier interface (130); and an application (111) stored in the data storage device (110); wherein the data carrier processor (120) is configured to execute the application (111); wherein the application (111) comprises a data element (112) containing personal contact information of an owner of the data carrier (100); wherein the data carrier processor (120) is configured to perform a transaction operation with a reader (200) while the data carrier (100) is in a communication connection with the reader (200) via the data carrier interface (130);and wherein the application (111) is configured to read the personal contact details of the owner of the data carrier (100) from the data element (112) and make them available to the reader (200) so that the personal contact details can be used by the reader (200) to create and send a digital transaction receipt about the transaction process.

2. Data carrier (100) according to claim 1, wherein the data carrier (100) is a physical card-shaped data carrier (100) or a virtual representation of a card-shaped data carrier (100).

3. Data carrier (100) according to claim 1 or 2, wherein the data carrier (100) is a payment card or an identity document.

4. Data carrier (100) according to any of the preceding claims, wherein the personal contact details of the owner of the data carrier (100) comprise at least one of the following: an email address; a telephone number; and an identifier.

5. Data carrier (100) according to one of the preceding claims, wherein the application (111) is configured to communicate with the reader (200) via a Secure Channel protocol based on an asymmetric cryptographic method and to transmit the personal contact details.

6. Data carrier (100) according to one of the preceding claims, wherein the application (111) is configured to sign the transaction document created by the reader (200) before the transaction document is sent by the reader (200) using a private key stored in the data storage (110).

7. Reader (200) for a data carrier (100) according to one of the preceding claims, the reader (200) comprising: a reader processor (220); and a contactless and / or a contact-based reader interface (230); wherein the reader processor (220) is configured to establish a communication connection with the data carrier interface (130) via the reader interface (230); wherein the reader processor (220) is configured to receive personal contact details of the owner of the data carrier (100) from the data carrier (100) via the reader interface (230); and wherein the reader processor (220) is configured to create a transaction document for a transaction carried out with the data carrier (100) and to send it to the owner of the data carrier (100) using the personal contact details.

8. Reader (100) according to claim 7, wherein the reader processor (200) is configured to encrypt the created transaction document with a public key stored in the data storage (110) of the data carrier (100) before the transaction document is sent by the reader (200).

9. System (300) comprising: a data carrier (100) according to any one of claims 1 to 7; and a reading device (200) according to claim 7 or 8; 19 wherein the data carrier (100) is configured to establish a communication connection with the reader (200) via the data carrier interface (130) and the reader interface (230); wherein the data carrier processor (120) and the reader processor (220) are configured together to perform a transaction operation; wherein the reader processor (220) is configured to retrieve the personal contact details of the owner of the data carrier (100) from the data carrier (100); wherein the reader processor (220) is configured to create a digital transaction receipt for the completed transaction operation; and wherein the reader processor (220) is configured to send the created transaction receipt to the owner of the data carrier (100) using the personal contact details.

10. Method (400) for providing a digital transaction receipt for a transaction carried out with a data carrier (100) to an owner of the data carrier (100), the method comprising: Establish (410) a communication connection with the data carrier (100); Performing (420) a transaction operation with the data carrier (100); Create (430) a digital transaction receipt for the transaction that has been carried out; Receiving (440) personal contact details of a data carrier owner (100) from a data element (112) of the data carrier (100); and Sending (450) the created digital transaction document to the owner of the data carrier (100) using personal contact details via a communication server (240).

Images