Method for dematerialising a transaction ticket following the execution of a transaction between a merchant and a user

Abstract

The present invention relates to a method for dematerialising a transaction ticket following the execution of a transaction between a merchant and a user, wherein the method is characterised in that it comprises the implementation, by data processing means (31) of a mobile terminal (3) of the user, of the steps of: (a) receiving a data set provided by the merchant, containing a link to a web application and first data representative of the transaction; (b) invoking the link so as to implement the web application; (c) transmitting, to a server (2), a request for a dematerialised transaction ticket, generated according to the first data representative of the transaction; (d) receiving, by the web application, the dematerialised transaction ticket in return.

Description

[0001] Description

[0002] Title of the invention: Method for dematerializing a transaction ticket following the implementation of a transaction between a merchant and a user.

[0003] GENERAL TECHNICAL FIELD

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

[0005] STATE OF THE ART

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

[0007] Some merchants have implemented a solution for electronic tickets, for example, received by email. The problem is that you have to give the merchant your address or at least have a customer account with them.

[0008] 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 then scanning a QR code displayed by the cash register via this application to finally arrive at the ticket, which puts off users.

[0009] Furthermore, 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 things. It would be desirable to have a new solution for retrieving a dematerialized transaction ticket, which is completely universal, and much simpler to use

[0010] The present invention improves the situation.

[0011] PRESENTATION OF THE INVENTION

[0012] The present invention therefore relates, according to a first aspect, to a method for dematerializing a transaction ticket 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 steps of:

[0013] (a) Receipt of a data set provided by the merchant, containing a link to a web application and initial data representative of said transaction;

[0014] (b) Calling said link so as to implement said web application;

[0015] (c) Transmission to a server of a request for a dematerialized transaction ticket, generated based on said first data representative of said transaction;

[0016] (d) Receipt in return by said web application of said dematerialized transaction ticket;

[0017] According to advantageous and non-limiting characteristics:

[0018] Step (b) comprises reading a user identifier stored in a memory of the terminal, and step (d) comprises associating said user identifier with said dematerialized transaction ticket.

[0019] The method comprises a step (e) of providing a history of dematerialized transaction tickets associated with said user identifier.

[0020] Said user identifier is contained in a cookie. Step (b) comprises, 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.

[0021] The said web application is of the PWA type.

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

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

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

[0025] Step (a) comprises transmitting to the server the second data representative of said transaction by said merchant's point-of-sale terminal.

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

[0027] Said merchant point of sale terminal comprises an electronic payment terminal, said transaction being a bank card payment transaction via said electronic payment terminal, step (a) comprising the electronic payment terminal displaying said QR code or the electronic payment terminal transmitting said data set to the terminal via said proximity wireless communication.

[0028] According to a second aspect, the invention relates to a mobile terminal of a user, characterized in that the terminal comprises data processing means configured to, with a view to the dematerialization of 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 first data representative of said transaction;

[0029] - call said link so as to implement said web application;

[0030] - transmit to a server a request for a dematerialized transaction ticket, generated based on said first data representative of said transaction;

[0031] - Receive in return in said web application said dematerialized transaction ticket.

[0032] According to a third aspect, the invention relates to a system for dematerializing a transaction ticket following the implementation of a transaction between a merchant and a user, comprising a server and a point-of-sale terminal of the merchant for the implementation of said transaction, characterized in that:

[0033] - The point of sale terminal comprises data processing means configured to transfer, to a mobile terminal of said user, a set of data provided by the merchant, containing a link to a web application and first data representative of said transaction; with a view to calling said link so as to implement said web application by the mobile terminal;

[0034] - The server comprises data processing means configured to receive from said web application a request for a dematerialized transaction ticket, and to transmit in return to said web application said dematerialized transaction ticket, generated according to the request and second data representative of said transaction.

[0035] According to a fourth and a fifth aspect, the invention relates to a computer program product comprising code instructions for executing a method according to the first aspect of dematerializing a transaction ticket following the implementation of a transaction between a merchant and a user; and a storage means readable by computer equipment on which is recorded a computer program product comprising code instructions for executing a method according to the first aspect of dematerializing a transaction ticket following the implementation of a transaction between a merchant and a user.

[0036] PRESENTATION OF FIGURES

[0037] Other characteristics and advantages of the present invention will appear on reading the following description of a preferred embodiment. This description will be given with reference to the appended drawings in which:

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

[0039] [Fig. 2]Figure 2 is a flowchart illustrating the steps of an embodiment of the method according to the invention.

[0040] DETAILED DESCRIPTION

[0041] Architecture

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

[0043] By "dematerialization" is meant obtaining a digital version of the ticket (called a dematerialized ticket) on a mobile terminal 3 of the user, as opposed to a paper version. Note that it is entirely possible for the paper ticket to be further printed and given to the user (if he requests it), but preferably the present method completely replaces the paper ticket. The transaction ticket in question may be any ticket whose issue is of interest following the transaction, what is generally called a "payment ticket", advantageously a receipt of said transaction. This is typically a sales receipt or a bank card receipt (in the case where the transaction is a payment by bank card), but it may also be a ticket relating to a payment failure or a canceled transaction, a credit ticket, or even a ticket worth a promotional discount, etc.

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

[0045] 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.

[0046] Said POS 1, commonly called cash register, is the equipment enabling said transaction in practice. It comprises data processing means 11, the possible TPE 10 and / or interface means 13 (as will be seen, this may be a screen and / or proximity wireless communication means, typically an NFC / RFID reader). Note that in the presence of a TPE 10, the data processing means 11 and the interface means 13 of the POS 1 may be confused with the TPE 10 (i.e. the processor, the screen of the TPE 10 and its NFC reader are used for contactless payments).

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

[0048] The mobile terminal 3 is a terminal personal to the user, in particular a smartphone, where appropriate dematerializing a bank card and which can be used for implementing the transaction. It also has data processing means 31 (typically a processor) and data storage means 32 (a memory, for example flash), and potentially a camera.

[0049] Process

[0050] With reference to Figure 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 first data representative of said transaction.

[0051] This step can be implemented in a known manner, by reading a QR code or by proximity wireless communication, using the means of the POS 1:

[0052] - According to a first embodiment, a QR code encapsulating said set of data is displayed by the interface 13 of the POS 1 or directly the TPE 10. The user implements step (a) by scanning said QR code with a camera of his terminal 3.

[0053] - According to a second embodiment, said set of data is transmitted to the proximity wireless communication terminal 3. The user implements step (a) by bringing his terminal close to the interface 13. In a particularly preferred embodiment, the user implements the transaction with his terminal 3 on the contactless EFT 10 (via a dematerialized bank card), and step (a) is implemented directly following the transaction, using the same proximity wireless communication, i.e. the user brings his terminal 3 close to pay, the transaction is implemented and he directly receives said set of data containing the link to the web application and the first data representative of said transaction. The present invention will not be limited to any way of implementing step (a).There may also be several ways implemented simultaneously to receive said data set, which is the case in figure 1 (display of the QR code on the screen 13 + NFC communication with the TPE 10).

[0054] 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 reception of said set of data and therefore the dematerialization of the transaction receipt, for example “Please scan the QR code displayed by the cash register to retrieve your dematerialized receipt”.

[0055] Using a web application avoids any OS-specific mobile application and any complex installation, since web applications are supported by all browsers natively without intervention on the terminal 3. In addition, as we will see later, the clever use of a connection witness or "cookie", permitted by any web browser, makes it possible to avoid any use of a CRM tokenization service.

[0056] As such, said link to the web application contained in the data set received in step (a) is defined by a URL (Uniform Resource Locator) address. A call to said link “executes” the application in a browser by accessing the remote web page.

[0057] 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 constraints of the latter. More specifically, the web pages of the application appear to the user on their terminal 3 in the same way as mobile applications, so that the user does not visually notice the difference.

[0058] It is even possible to "install" a PWA web application on terminal 3, installation consisting of creating a shortcut to the URL of the web application (advantageously the said link defined above), an icon then being added to the home screen of terminal 3 in the same way as for any ordinary application. If the user presses this PWA icon, it is in fact the browser which is launched with a call to said URL shortcut.

[0059] Preferably, said link is independent of the transaction and therefore of said first data representative of said transaction. This therefore allows payments of different types (bank card, cash, etc.) at different merchants, in a completely universal manner. It should be remembered that until now the dematerialization mechanism was specific to a bank card and a merchant due to the use of keys to link the user to a PAN.

[0060] Said first transaction data preferably comprises at least one merchant identifier and one unique transaction identifier, and potentially part of the information constituting the ticket, varying according to the type of ticket to be dematerialized (amount, timestamp, payment information, purchase details, etc.). Preferably, second data representative of the transaction is provided, with the following conditions:

[0061] - The set of first and second data contains all the information of the ticket (i.e. the ticket can be generated entirely from the first and second data);

[0062] - The intersection of the first and second data is non-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.

[0063] It is assumed that the server 2 has said second data representative of said transaction. As such, step (a) may also comprise the reception by the server 2, advantageously also from the POS 1, via the network 20, of said second data representative of said transaction. This transmission follows the payment and is typically concomitant with the display of a QR code or other In a step (b), said link is called by the data processing means 31 of the 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 a manner identical to a normal mobile application if it is a PWA web application.

[0064] Step (b) may differ depending on whether this is the first time the user is implementing this method on this terminal 3.

[0065] Preferably, step (b) comprises in this respect the reading (if it exists) of a user identifier stored in a memory 32 of the terminal 3. It is assumed that if the method has already been implemented, such an identifier exists. If, on the contrary, the user identifier is not found, step (b) advantageously comprises the creation of a new user identifier and its storage in said memory 32 of the terminal 3.

[0066] The said user identifier is very preferably 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 manner completely transparent to the user, and it stores the said user identifier there, for example randomly generated.

[0067] Please note that if the user refuses or deletes their cookies, this is not a problem; the only consequence will be that the next time this process is implemented, the web application will not find a user ID (see below).

[0068] Note that step (b) may include, if the user's identifier 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 using a manifest file. If the user calls the link while a shortcut is already created, this opens it directly.

[0069] Then, the method comprises a step (c) of transmitting to the server 2 a request for a dematerialized transaction ticket, generated according to said first data representative of said transaction. Everything takes place in said web application, which will interact with the server 2, typically by providing it with all or part of the first data representative of said transaction, at least those it needs to make the link with the second data, and those which it would lack to generate the dematerialized ticket. It is assumed that the server 2 is capable of generating the dematerialized ticket according to all the data at its disposal, this is essentially formatting, for example in HTML or PDF.

[0070] Note that step (c) can be performed automatically by the web application as soon as the latter 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 the server 2 is provided by said web application, the user has nothing to do, and the terminal 3 does not need to be preconfigured in any way (the information received in step (a) is sufficient to implement the entire rest of the process).

[0071] In return, said web application receives from the server 2 said dematerialized transaction ticket in a step (d), for display on the terminal 3, and where appropriate local storage on the storage means 32 of the terminal 3. Note that in addition said ticket advantageously remains stored on storage means 22 of the server 2, for subsequent consultation. In this respect, step (d) may comprise the generation by the data processing means 21 of the server 2 as a function of the data of the request and the second data representative of the transaction which it has.

[0072] Preferably, if the user has accepted the cookie, step (d) comprises the association of said user identifier with said dematerialized transaction ticket, on the server 2 and / or the terminal 3.

[0073] This allows easy access to previous dematerialized tickets: the method advantageously comprises a step (e) of providing a history of dematerialized 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 his terminal 3 and generated randomly, no one other than him is able to access his tickets.

[0074] As explained, if the user deletes his cookie after a certain time, he loses his identifier and therefore this history, which means that the old tickets concerned are no longer accessible by anyone, and a new identifier will be created at the next dematerialization.

[0075] Terminal and dematerialization system

[0076] According to a second aspect, the invention relates to the mobile terminal 3 of a user 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.

[0077] The data processing means 31 are configured for, with a view to the dematerialization of a transaction ticket following the implementation of a transaction between a merchant and said user:

[0078] - 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 proximity wireless communication);

[0079] - call said link so as to implement said web application;

[0080] - transmit to a server 2 (to which it is connected via the network 20) ​​a request for a dematerialized transaction ticket, generated based on said first data representative of said transaction;

[0081] - Receive in return in said web application said dematerialized transaction ticket; It should be noted that it is in practice the reception of said set of data provided by the merchant, containing a link to a web application and first data representative of said transaction which causes the configuration of the terminal 3 to implement the other actions.

[0082] 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 method according to the first aspect.

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

[0084] The POS 1 (or in particular the EPT 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 first data representative of said transaction (for example by displaying a QR code to be scanned by the terminal 3 or by authorizing a proximity wireless communication with the terminal 3); with a view to calling said link so as to implement said web application by the mobile terminal 3.

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

[0086] The server (2) comprises data processing means 21 configured to receive from said web application a request for a dematerialized transaction pay slip, and to transmit in return to said web application said dematerialized transaction slip, generated as a function of the request (which generally contains part of the first data representative of the transaction) and second data representative of said transaction.

[0087] Said dematerialization system advantageously comprises at least one mobile terminal 3 according to the second aspect. Computer program product

[0088] 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 dematerialization of a transaction ticket following the implementation of a transaction between a merchant and a user, as well as storage means readable by computer equipment (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

CLAIMS 1. Method for dematerializing a transaction ticket 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 steps of: (a) Receipt of a data set 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 to a server (2) of a request for a dematerialized transaction ticket, generated based on said first data representative of said transaction; (d) Receipt in return by said web application of said dematerialized transaction ticket.

2. Method according to claim 1, in which step (b) comprises reading a user identifier stored in a memory (32) of the terminal (3), and step (d) comprises associating said user identifier with said dematerialized transaction ticket.

3. Method according to claim 2, in which the method comprises a step (e) of providing a history of dematerialized transaction tickets associated with said user identifier.

4. Method according to one of claims 2 and 3, in which said user identifier is contained in a cookie.

5. Method according to one of claims 2 to 4, in which step (b) comprises, 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.

6. Method according to one of claims 1 and 5, in which said web application is of the PWA type.

7. Method according to claims 5 and 6 in combination, in which step (b) comprises, if the user identifier is not found, a proposal to install said PWA type web application on the user's terminal (1).

8. Method according to one of claims 1 to 7, in which the server (2) has second data representative of said transaction, the dematerialized transaction ticket being generated by data processing means (22) of the server (2) as a function of the first and second data representative of said transaction.

9. Method according to one of claims 1 to 8, wherein said data set is received in step (a) from a point of sale terminal (1) of the merchant by means of which said transaction was implemented.

10. Method according to claims 8 and 9 in combination, wherein step (a) comprises transmitting to the server (2) the second data representative of said transaction by said point of sale terminal (1) of the merchant.

11. Method according to one of claims 1 to 10, in which step (a) is implemented by reading a QR code encapsulating said data set or via proximity wireless communication.

12. The method of claims 9 and 11 in combination, wherein said merchant point-of-sale terminal (1) comprises an electronic payment terminal (10), said transaction being a bank card payment transaction via said electronic payment terminal (10), step (a) comprising the electronic payment terminal (10) displaying said QR code or the electronic payment terminal (10) issuing said data set to the terminal (3) via said proximity wireless communication.

13. Mobile terminal (3) of a user, characterized in that the terminal (3) comprises data processing means (31) configured for, with a view to the dematerialization of 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; - call said link so as to implement said web application; - transmit to a server (2) a request for a dematerialized transaction ticket, generated based on said first data representative of said transaction; - Receive in return in said web application said dematerialized transaction ticket.

14. System for dematerializing a transaction ticket following the implementation of a transaction between a merchant and a user, comprising a server (2) and a point of sale terminal (1) of the merchant for the implementation of said transaction, characterized in that: - The point of sale terminal (1) comprises data processing means (11) configured to transfer, to a mobile terminal (3) of said user, a set of data provided by the merchant, containing a link to a web application and first data representative of said transaction; with a view to calling said link so as to implement said web application by the mobile terminal (3); - The server (2) comprises data processing means (21) configured to receive from said web application a request for a dematerialized transaction ticket, and transmit in return to said web application said dematerialized transaction ticket, generated according to the request and second data representative of said transaction.

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

16. Storage means readable by computer equipment on which is recorded a computer program product comprising code instructions for the execution of a method according to one of claims 1 to 12 for dematerializing a transaction ticket following the implementation of a transaction between a merchant and a user.

Images