Method of dematerializing a transaction receipt following the implementation of a transaction between a merchant and a user.

Abstract

The present invention relates to a method for dematerializing a transaction receipt following the implementation of a transaction between a merchant and a user. The method is characterized in that it comprises the implementation, by data processing means (31) of a mobile terminal (3) of said user, of the following steps: Receiving a set of data provided by the merchant, containing a link to a web application and initial data representing said transaction; Calling said link so as to implement said web application; Transmitting to a server (2) a request for a dematerialized transaction receipt, generated based on said initial data representing said transaction; Receiving in return by said web application said dematerialized transaction receipt. Fig. 1

Description

Title of the invention: Method for dematerializing a transaction receipt following the implementation of a transaction between a merchant and a user.

[0001] GENERAL TECHNICAL FIELD

[0002] The present invention relates to the field of payment terminals. More specifically, it concerns a method for dematerializing a transaction receipt following the implementation of a transaction between a merchant and a user.

[0003] STATE OF THE ART

[0004] As part of the fight against waste, the end of automatic printing of till receipts and bank card receipts applies in France from August 1, 2023.

[0005] Some merchants have therefore implemented a solution of electronic tickets, for example received by email. The problem is that it is necessary to give the merchant one's address or at least have a customer account with them.

[0006] There is a more universal solution, based on the association of the ticket and the user via a token, called a "CRM token", calculated on the basis of the PAN (Primary Account Number) of the bank card, but it is more complex and requires installing a dedicated application on a smartphone and then scanning a QR code displayed by the till via this application to finally get to the ticket, which puts users off.

[0007] Moreover, it is limited to merchants who have implemented this technology, and often different merchants use different applications (the injection of unique keys per merchant is necessary), which further complicates matters.

[0008] It would be desirable to have a new solution for retrieving an electronic transaction receipt that is completely universal and much simpler to use.

[0009] The present invention improves the situation. PRESENTATION OF THE INVENTION

[0010] The present invention therefore relates, in a first aspect, to a method for dematerializing a transaction receipt following the implementation of a transaction between a merchant and a user, the method being characterized in that it comprises the implementation, by data processing means of a mobile terminal of said user, of the following steps: a. Receipt of a set of data provided by the merchant, containing a link to a web application and initial data representative of said transaction; b. Calling said link so as to implement said web application; c. Transmission of a transaction ticket request to a server dematerialized, generated based on the aforementioned initial data representing the said transaction; d. Receipt in return by said web application of said electronic transaction ticket,

[0011] step (b) comprising reading a user identifier stored in a terminal memory, and step (d) comprising associating said user identifier with said electronic transaction ticket, the method further comprising a step (e) of providing a history of electronic transaction tickets associated with said user identifier, said user identifier being contained in a cookie, step (b) comprising, if the user identifier is not found, the creation of a new user identifier and its storage in said terminal memory by the web application, said web application being of type PWA.

[0012] According to advantageous and non-limiting features:

[0013] Step (b) includes, if the user identifier is not found, a proposal to install said PWA type web application on the user's terminal.

[0014] The server has second data representing said transaction, the dematerialized transaction ticket being generated by data processing means of the server based on the first and second data representing said transaction.

[0015] Said data set is received in step (a) from a merchant point-of-sale terminal through which said transaction was implemented.

[0016] Step (a) includes the transmission to the server of the second data representing said transaction by said merchant point of sale terminal.

[0017] Step (a) is implemented by reading a QR code encapsulating said data set or via a proximity wireless communication.

[0018] Said merchant point of sale terminal includes an electronic payment terminal, said transaction being a payment transaction by bank card via said electronic payment terminal, step (a) comprising the display by the electronic payment terminal of said QR code or the transmission by the electronic payment terminal of said data set to the terminal via said wireless proximity communication.

[0019] According to a second and a third aspect, the invention relates to a computer program product comprising code instructions for executing a process according to the first aspect of dematerializing a transaction receipt following the implementation of a transaction between a merchant and a user; and a computer-readable storage means on which a product is recorded computer program comprising code instructions for the execution of a process according to the first aspect of dematerialization of a transaction ticket following the implementation of a transaction between a merchant and a user. PRESENTATION OF THE FIGURES

[0020] Other features and advantages of the present invention will become apparent from the following description of a preferred embodiment. This description will be given with reference to the accompanying drawings in which:

[0021] [Fig.1] [Fig.1] is a diagram of a system for implementing the method according to the invention;

[0022] [Fig.2] [Fig.2] is a flowchart illustrating the steps of an embodiment of the process according to the invention. DETAILED DESCRIPTION

[0023] Architecture

[0024] With reference to [Fig.1], the present invention relates to a method of dematerializing a transaction ticket following the implementation of a transaction between a merchant and a user.

[0025] By "dematerialization," we mean obtaining a digital version of the ticket (called a dematerialized ticket) on the user's mobile terminal 3, as opposed to a paper version. It should be noted that it is entirely possible for the paper ticket to also be printed and given to the user (if requested), but preferably, this method completely replaces the paper ticket.

[0026] The transaction receipt in question can be any receipt whose issuance is relevant following the transaction, generally referred to as a "payment receipt," advantageously a receipt for said transaction. This is typically a cash register receipt or a bank card receipt (in the case where the transaction is a payment by bank card), but it can also be a receipt relating to a failed payment or a cancelled transaction, a credit receipt, or even a receipt constituting a promotional discount, etc.

[0027] Note that the transaction is typically a payment by bank card of the user via an electronic payment terminal 10 (POS) of the merchant (with or without contact on the POS 10), the bank card being potentially dematerialized on the user's mobile terminal 3, but it can very well be a transaction by check or in cash (and then there is no POS 10).

[0028] The present method is implemented by the terminal 3, and involves a server 2 generally remote and connected to the terminal 3, as well as advantageously to a point of sale terminal 1 (POS) of the merchant, by a network 20 such as the internet network.

[0029] Said POS terminal 1, commonly referred to as a cash register, is the equipment that enables the transaction in practice. It comprises data processing means 11, the optional payment terminal 10, and / or interface means 13 (as will be seen, this may be a screen and / or wireless proximity communication means, typically an NFC / RFID reader). Note that in the presence of a payment terminal 10, the data processing means 11 and the interface means 13 of the POS terminal 1 can be used in conjunction with the payment terminal 10 (i.e., the processor, screen, and NFC reader of the payment terminal 10 are used for contactless payments).

[0030] The server 2 also has data processing means 21 (typically a processor) and data storage means 22 (memory, for example a hard disk).

[0031] The mobile terminal 3 is a personal terminal belonging to the user, in particular a smartphone, possibly dematerializing a bank card and capable of being used for carrying out the transaction. It also has data processing means 31 (typically a processor) and data storage means 32 (memory, for example flash), and potentially a camera.

[0032] Method

[0033] With reference to [Fig.2], the present method is implemented by the data processing means 31 of the mobile terminal 3, and begins with a step (a) of receiving a set of data provided by the merchant (advantageously from the merchant's POS 1), containing a link to a web application and initial data representative of said transaction.

[0034] This step can be implemented in a known manner, by reading a QR code or by wireless proximity communication, using the means of the POS 1: - According to a first embodiment, a QR code encapsulating said data set is displayed by the interface 13 of the POS 1 or directly the POS 10. The user carries out step (a) by scanning said QR code with a camera of his terminal 3. - According to a second embodiment, said data set is transmitted to terminal 3 via wireless proximity communication. The user performs step (a) by bringing their terminal close to interface 13. In a particularly preferred embodiment, the user performs the transaction with their terminal 3 on the POS terminal 10 using contactless technology (via a digital bank card), and step (a) is performed immediately following the transaction, using the same wireless proximity communication; i.e., the user brings their terminal 3 close to pay, the transaction is performed, and they directly receive said data set containing the link to the web application and the first representative data of said transaction.

[0035] The present invention shall not be limited to any particular way of implementing step (a). Moreover, there may be several ways implemented simultaneously of receiving said data set, as is the case in [Fig. 1] (display of the QR code on the screen 13 + NFC communication with the POS terminal 10).

[0036] Note that step (a) may include a prior invitation to the user by the POS 1 (in the form of a pictogram or a visual and / or audio message) to perform an action to trigger the receipt of said data set and thus the dematerialization of the transaction receipt, for example "Please scan the QR code displayed by the till to retrieve your dematerialized till receipt".

[0037] The use of a web application avoids any OS-specific mobile application and any complex installation, since web applications are natively supported by all browsers without intervention on the terminal 3. Moreover, as will be seen later, the clever use of a connection token or “cookie”, allowed by any web browser, makes it possible to avoid any use of a CRM tokenization service.

[0038] In this respect, the link to the web application contained in the dataset received in step (a) is defined by a URL (Uniform Resource Locator). A call to said link "executes" the application in a browser by accessing the remote web page.

[0039] Preferably, said web application is of the PWA (progressive web app) type. A PWA is a web application that provides a user experience similar to that of a mobile application, without the latter's constraints. More precisely, the application's web pages appear to the user on their terminal 3 in the same way as mobile applications, so that the user cannot visually distinguish between them.

[0040] A PWA web application can even be "installed" on terminal 3, the installation consisting of creating a shortcut to the web application's URL (advantageously the aforementioned link), with an icon then being added to terminal 3's home screen in the same way as for any ordinary application. If the user taps this PWA icon, the browser actually launches, calling the aforementioned URL shortcut.

[0041] Preferably, said link is independent of the transaction and therefore of said initial data representing said transaction. This thus allows for payments of different types (bank card, cash, etc.) at different merchants, in a completely universal manner. It should be recalled that up to this point the mechanism The dematerialization was specific to a bank card and a merchant due to the use of keys to link the user to a PAN.

[0042] Said first transaction data preferably includes at least a merchant identifier and a unique transaction identifier, and potentially some of the information constituting the receipt, varying according to the type of receipt to be digitized (amount, timestamp, payment information, purchase details, etc.). Preferably, second data representing the transaction is provided, with the following conditions: - The first and second data sets contain all the ticket information (i.e., the entire ticket can be generated from the first and second data sets); - The intersection of the first and second data is not empty, i.e. we have common data, for example a unique identifier of the transaction, so as to allow the link between the first and second data.

[0043] It is assumed that server 2 has said second data representing said transaction. Accordingly, step (a) may also include the reception by server 2, advantageously also from POS 1, via network 20, of said second data representing said transaction. This transmission follows the payment and is typically simultaneous with the display of a QR code or other

[0044] In a step (b), said link is called by the data processing means 31 of terminal 3 so as to implement said web application. As explained, in a known manner, calling the link automatically launches the browser and the display of the pages that make up the web application, in the same way as a normal mobile application if it is a PWA web application.

[0045] Step (b) may differ depending on whether this is the first time the user has implemented the present method on this terminal 3.

[0046] Preferably, step (b) includes reading (if it exists) a user identifier stored in a memory location 32 of terminal 3. It is assumed that if the process has already been implemented, such an identifier exists. If, on the other hand, the user identifier is not found, step (b) advantageously includes creating a new user identifier and storing it in said memory location 32 of terminal 3.

[0047] The said user identifier is very preferentially contained in a cookie: if the cookie exists, the browser accesses it during the implementation of the web application, and if it does not exist it creates it, in a totally transparent way for the user, and it stores the said user identifier there, for example randomly generated.

[0048] Note that if the user refuses or deletes their cookies, it is not a problem, the only consequence will be that on the next implementation of this process the web application will not find a user identifier (see below).

[0049] Note that step (b) may include, if the user ID is not found, a proposal to install said PWA-type web application on the user's terminal 1 (i.e., the creation of a shortcut), for example, via a manifest file. If the user calls the link when a shortcut has already been created, it opens directly.

[0050] Next, the process includes a step (c) of transmitting to server 2 a request for a digital transaction ticket, generated based on the aforementioned initial data representing the transaction. This all takes place within the web application, which interacts with server 2, typically by providing it with all or part of the initial data representing the transaction, at least the data it needs to link it to the second data, and any data it lacks to generate the digital ticket. It is assumed that server 2 is capable of generating the digital ticket based on all the data it has available; this essentially involves formatting, for example, in HTML or PDF.

[0051] Note that step (c) can be performed automatically by the web application as soon as it is implemented following step (b), i.e., the ticket is directly requested and retrieved following the user's action in step (a), or it is implemented following a user action in the web application, for example, pressing a "retrieve ticket" button. In all cases, all the information necessary to interact with server 2 is provided by said web application; the user has nothing to do, and terminal 3 does not need to be pre-configured in any way (the information received in step (a) is sufficient to implement the entire rest of the process).

[0052] In return, the web application receives the digital transaction ticket from server 2 in step (d), for display on terminal 3, and, if applicable, local storage on the terminal 3's storage devices 32. It should be noted that the ticket is also advantageously stored on the server 2's storage devices 22 for later consultation. In this respect, step (d) may include the generation, by the server 2's data processing devices 21, of the request data and the second data representing the transaction that it possesses.

[0053] Preferably, if the user has accepted the cookie, step (d) includes associating said user identifier with said electronic transaction ticket, on server 2 and / or terminal 3.

[0054] This allows easy access to previous electronic tickets: the method advantageously includes a step (e) of providing a history of electronic transaction tickets associated with said user identifier, for example by means of a button or a dedicated page in the web application. Since the user identifier is data stored only on their terminal 3 and generated randomly, no one other than the user is able to access their tickets.

[0055] As explained, if the user deletes their cookie after a certain time, they lose their identifier and therefore this history, which means that the old tickets concerned are no longer accessible to anyone, and a new identifier will be created at the next digitization.

[0056] Terminal and dematerialization system

[0057] According to a second aspect, the invention relates to a user's mobile terminal 3 for implementing the method according to the first aspect. The terminal 3 comprises data processing means 31, and generally a memory 32 and possibly a camera.

[0058] The data processing means 31 are configured for the purpose of dematerializing a transaction ticket following the implementation of a transaction between a merchant and said user: - Receive a set of data provided by the merchant, containing a link to a web application and initial data representative of said transaction (for example by scanning a QR code encapsulating said set of data or by accepting a wireless proximity communication); - call said link in order to implement said web application; - transmit to a server 2 (to which it is connected via network 20) ​​a request for a digital transaction ticket, generated based on the aforementioned initial data representing said transaction; - To receive in return in the said web application the said electronic transaction ticket;

[0059] It is noted that in practice it is the receipt of said data set provided by the merchant, containing a link to a web application and initial data representative of said transaction which leads to the configuration of terminal 3 to implement the other actions.

[0060] According to a third aspect, the invention relates to the system for dematerializing a transaction ticket following the implementation of a transaction between a merchant and a user also for the implementation of the process according to the first aspect.

[0061] It includes a server 2 and a merchant point of sale terminal 1 for the implementation of said transaction, the point of sale terminal 1 (POS) typically includes an EFTPOS 10 and / or an interface 13.

[0062] The POS 1 (or in particular the POS 10) is configured to transfer to a mobile terminal 3 of said user (or at least "make available", since it is ultimately up to the user to do what is necessary to enable the transfer), a set of data provided by the merchant, containing a link to a web application and initial data representative of said transaction (for example by displaying a QR code to be scanned by the terminal 3 or by allowing a wireless proximity communication with the terminal 3); with a view to calling said link so as to implement said web application by the mobile terminal 3.

[0063] The POS terminal 1 is also generally configured to transmit to server 2 second data representative of said transaction.

[0064] The server (2) includes data processing means 21 configured to receive from said web application a request for a dematerialized transaction payment ticket, and to transmit back to said web application said dematerialized transaction ticket, generated according to the request (which generally contains part of the first data representing the transaction) and second data representing said transaction.

[0065] Said dematerialization system advantageously includes at least one mobile terminal 3 according to the second aspect.

[0066] Computer program product

[0067] According to a fourth and a fifth aspect, the invention relates to a computer program product comprising code instructions for the execution (on the data processing means 11, 21, 31 of the POS 1, the server 2 and / or the terminal 3) of a method according to the first aspect of dematerializing a transaction ticket following the implementation of a transaction between a merchant and a user, as well as computer-readable storage means (for example the data storage means 12, 22, 33 of the POS 1, the server 2 and / or the terminal 3) on which this computer program product is found.

Claims

Demands

1. A method for dematerializing a transaction receipt following the implementation of a transaction between a merchant and a user, the method being characterized in that it comprises the implementation by data processing means (31) of a mobile terminal (3) of said user of the steps of: a. Receiving a set of data provided by the merchant, containing a link to a web application and initial data representing said transaction; b. Calling said link so as to implement said web application; c. Transmitting to a server (2) a request for a dematerialized transaction receipt, generated according to said initial data representing said transaction; d. Receiving in return by said web application said dematerialized transaction receipt.step (b) comprising reading a user identifier stored in a memory (32) of the terminal (3), and step (d) comprising associating said user identifier with said electronic transaction ticket, the process further comprising a step (e) of providing a history of electronic transaction tickets associated with said user identifier, said user identifier being contained in a cookie, step (b) comprising, if the user identifier is not found, the creation of a new user identifier and its storage in said memory (32) of the terminal (1) by the web application, said web application being of type PWA.

2. A method according to claim 1, wherein step (b) includes, if the user identifier is not found, a proposal to install said PWA-type web application on the user's terminal (1).

3. A method according to claim 1 or 2, wherein the server (2) has second data representing said transaction, the dematerialized transaction ticket being generated by data processing means (22) of the server (2) according to of the first and second representative data of said transaction.

4. A method according to any one of claims 1 to 3, wherein said data set is received at step (a) from a point-of-sale terminal (1) of the merchant through which said transaction was implemented.

5. A method according to claims 3 and 4 in combination, wherein step (a) comprises the transmission to the server (2) of the second data representing said transaction by said point-of-sale terminal (1) of the merchant.

6. A method according to any one of claims 1 to 5, wherein step (a) is implemented by reading a QR code encapsulating said data set or via a proximity wireless communication.

7. A method according to claims 4 and 6 in combination, wherein said point-of-sale terminal (1) of the merchant comprises an electronic payment terminal (10), said transaction being a payment transaction by bank card via said electronic payment terminal (10), step (a) comprising the display by the electronic payment terminal (10) of said QR code or the transmission by the electronic payment terminal (10) of said data set to the terminal (3) via said wireless proximity communication.

8. Product computer program comprising code instructions for the execution of a method according to any one of claims 1 to 7 of dematerializing a transaction ticket following the implementation of a transaction between a merchant and a user, when said program is executed on a computer.

9. Computer-readable storage means on which is recorded a computer program product comprising code instructions for the execution of a method according to any one of claims 1 to 7 of dematerializing a transaction ticket following the implementation of a transaction between a merchant and a user.

Images