FR3156958A1 - Transaction process with multimedia data display - Google Patents

Abstract

The invention relates to a transaction method, comprising the following steps: during a payment transaction between a customer and a merchant (ML1), establishing a communication link between a payment terminal (TP1) of the merchant and a mobile terminal (MT1) of the customer; acquiring by the payment terminal (TP1) a payment device identifier (CI1); transmitting transaction data to a server (PSRV); transmitting by the server to the customer's terminal an access link (PNLK) to an application (WP); upon activation of the access link, transmitting by the mobile terminal to the server an access request to the application containing the access link and the payment device identifier; upon receipt of the access request, generating and transmitting by the server a progressive web application to the mobile terminal; and receiving and executing the application by the mobile terminal. Figure 2

Description

Transaction process with multimedia data display

The present invention relates to payment transactions carried out using a mobile terminal such as a smartphone at merchants, for example in a shopping center or a city district.

State of the art

Payment cards, such as bank cards, have long been widely used for purchasing goods and/or services. In a typical payment card transaction, the merchant totals the purchase amount at the point of sale checkout, and the customer inserts their payment card into a card reader at the checkout to initiate the transaction. Additional customer confirmation, such as a PIN, may be required to complete the transaction. This information is typically entered by the customer using a keypad located on the merchant's checkout. Payment transaction information, including the transaction amount and the bank card identification information (or PAN - "Primary Account Number"), is transmitted from the payment terminal to a transaction server associated with the merchant (an entity that processes and settles the merchant's bank with the merchant's bank), and then is routed from the transaction server to the customer's or card issuer's bank via the card issuer's payment network (e.g., VISA™, MASTERCARD™, etc.). If the transaction is authorized, an authorization code is then sent by the card issuer to the merchant's transaction server, which sends the authorization code to the payment terminal. The customer can then receive the purchased goods or services.

Mobile payments are increasingly used by many consumers as an alternative to traditional payment methods (cash, checks, payment cards, etc.). Mobile payments allow consumers to use their mobile phones to pay for goods or services. For this purpose, bank card information is stored in an e-wallet application that is executed by the mobile phone during a payment transaction initiated with a payment terminal.

Mobile payments offer several advantages over payment cards.

In this context, it is desirable for a merchant to be able to extend its relationship with its customer beyond the payment transaction, while limiting the customer's involvement as much as possible. Thus, extending this relationship may simply consist of sending the customer a digital receipt relating to the transaction, a discount coupon to be used in a future transaction, a message or advertising content, or a message allowing the customer to sign up for a loyalty program. It may also be desirable to be able to send a message or advertising content to a customer only if one or more conditions are met. Such conditions may, for example, depend on time, a geographical location, a transaction amount, or the items or services purchased.

Summary

Embodiments relate to a transaction method, comprising steps consisting of: during a payment transaction by a customer at a merchant, establishing a communication link between a payment terminal of the merchant and a mobile terminal of the customer; acquiring by the payment terminal of the merchant, a payment device identifier of the customer; transmitting to a server, data relating to the transaction and comprising the acquired payment device identifier; storing by the server the data relating to the transaction in a database; transmitting by the server to the payment terminal an access link to a progressive web application; transmitting the access link and the payment device identifier, by the payment terminal to the mobile terminal, via the communication link; upon activation of the access link, transmitting by the mobile terminal to the server, a request for access to the progressive web application containing the access link and the payment device identifier; upon receipt of the request for access to the progressive web application, generating by the server, a progressive web application; transmitting the progressive web application generated, by the server to the mobile terminal; and receive and execute the progressive web application by the mobile terminal.

By using the progressive web application (PWA) mechanism, it is possible to display a personalized web page on the mobile terminal of the identified customer during a transaction at a merchant, without requiring any specific intervention from the customer, other than the use of the mobile terminal during the transaction and the activation of a link on the mobile terminal by the customer. Thus, it is not necessary to provide a specific display means or a document printout to provide the customer with information, for example, relating to the transaction. The payment device used during the transaction may be a smartphone with an electronic wallet application storing a bank card identifier.

According to one embodiment, the progressive web application received by the mobile terminal is configured to perform at least one of the following operations: display a receipt relating to the payment transaction, display an advertising message, display a discount coupon linked to the payment transaction, display data attached to a purchase, display a web page for registering for a loyalty program, display a web page containing a customer account statement relating to a loyalty program, and display a discount coupon.

Thus, the information transmitted to the customer can be very varied. It can notably allow the customer to join a loyalty program, and therefore to obtain information about the customer.

According to one embodiment, the payment device identifier is determined by the payment terminal by applying a cryptographic function to a bank card number stored and transmitted by the customer's mobile terminal to the payment terminal.

In this way, the customer can be identified while respecting the confidentiality of their bank card identification information.

According to one embodiment, the method further comprises steps consisting of: storing by the mobile terminal the access link and the payment device identifier received; upon a second activation of the access link, transmitting by the mobile terminal to the server, the request for access to the progressive web application containing the access link and the payment device identifier; and following the transmission of the access request, transmitting by the server to the mobile terminal a modified progressive web application.

Thus, the access mechanism to a progressive web application allows a direct communication link to be established between the customer and the merchant, the initiative of the communication being left to the customer, while the object of the communication is controlled by the merchant.

According to one embodiment, the communication between a merchant's payment terminal and the customer's mobile terminal is of the near-field type.

Embodiments may also relate to a transaction system between a merchant and a customer, the system comprising: a server, a payment terminal installed at the merchant, and communicating with the server, and a mobile terminal of the customer, which can be put into communication with the payment terminal, the system being configured to implement the method defined previously.

Brief description of the figures

The present invention will be better understood with the aid of the following description of exemplary embodiments with reference to the appended figures, in which identical reference signs correspond to structurally and/or functionally identical or similar elements.

FIG. 1 Figure 1 schematically represents a customer journey tracking system, according to one embodiment,

FIG. 2 Figure 2 represents steps of a transaction method between a customer and a merchant, according to one embodiment.

Detailed description

Figure 1 represents a transaction system comprising equipment installed in a store ML1, a transaction server TSRV and a customer tracking management server. The equipment of the store ML1 comprises a payment terminal TP1 and a cash management computer MS1 connected to the payment terminal TP1. Furthermore, the terminal TP1 communicates with the transaction server TSRV, via a MW data transmission network, for example the Internet network.

According to one embodiment, the computer MS1 communicates with the management server PSRV via a data transmission network, for example the MW network. Note that the computer MS1 can be omitted, the payment terminal TP1 grouping together the necessary functionalities of the computer MS1 and being able to communicate directly with the PSRV server.

A customer wishing to make a purchase in the ML1 store has a mobile terminal MT1, for example a smartphone type terminal including an electronic wallet application storing the identification data of one or more bank cards, and an NFC near field communication interface. The TP1 payment terminal also has such a near field communication interface.

Figure 2 represents steps S1 to S15 of a transaction method between a customer and the merchant ML1, according to one embodiment. In step S1, the customer makes a purchase from the merchant ML1. For this purpose, the merchant selects the item(s) chosen by the customer on the computer MS1 or scans the labels of the chosen items. The computer MS1 calculates a transaction amount PX based on the selected items. This selection triggers step S2; the transaction amount PX is transmitted by the computer MS1 to the terminal TP1. In step S3, the terminal TP1 receives the amount PX and displays it on its DSP display screen. The transaction amount PX can also be entered directly using the keyboard of the terminal TP1.

In step S4, the customer presents his mobile terminal MT1 to the terminal TP1. During this presentation, a contactless communication, for example of the near field NFC type ("Near Field Communication"), is established between the mobile terminal MT1 and the terminal TP1. The mobile terminal MT1 then transmits to the payment terminal TP1 identification data PN1 and authentication data for a payment device. This data includes in particular a bank card number PAN ("Primary Account Number"). Thus, the customer may also be required to enter a secret code linked to the payment device to be authenticated. In step S5, the terminal TP1 can generate a cryptographic token CI1 from the identification data PN1 received. The token CI1 is obtained for example using a cryptographic function, such as a hash function. In step S6, the token CI1 (or the identification data PN1) is transmitted to the computer MS1. In addition, the TP1 terminal executes the transaction with the TSRV transaction server by generating and transmitting to it a cryptographic data containing the transaction data such as the PN1 bank card number received, the secret code entered by the user, the amount of the transaction, and the recipient of the payment. The CI1 token makes it possible to identify the payment device and therefore the customer, without having knowledge of the PN1 identifier of the payment device. Note that the CI1 token can be generated not by the TP1 terminal, but by the MS1 computer.

In step S7, the computer MS1 receives the token CI1 and transmits it to the PSRV server with an identifier ID1 of the merchant ML1, and the transaction data TT, in a PRQ request for a progressive web application PWA ("Progessive Web Application"). The transmitted transaction data TT may include the date of the transaction, the amount of the transaction PX and the identifier of each item thus purchased with its sale price. Note that the identifier CI1 of the customer transmitted by the terminal TP1 to the PSRV server may be directly the bank card number PN1 of the customer. In step S8, the PSRV server receives the PRQ request, and searches in the CB database, an identifier IDD of a PWA application. The PSRV server then generates a link PLNK to the PWA application. In step S9, the PSRV server transmits the link PLNK to the computer MS1 in response to the PRQ request issued in step S7. In step S10, the computer MS1 transmits the PNLK link to the terminal TP1. In step S11, the terminal TP1 transmits to the customer's terminal MT1, via the NFC link established during payment, the PLNK link with the identifier CI1 of the customer's payment device. Upon receipt of the PLNK link, in step S11, the customer's terminal MT1 generates a cookie storing the identifier CI1 received. The user of the terminal MT1 can be notified that he has received the PLNK link and that he can activate it to access a PWA application. The PWA application can be configured to provide access to and display a web page including the receipt corresponding to the TT transaction data, or web pages containing, for example, multimedia content such as an advertising message, a registration form for a loyalty program, a customer account statement relating to a loyalty program, a discount coupon linked to the payment transaction, or data attached to a purchase such as a warranty certificate or a user manual. The web page displayed upon activation of the PWA application may contain several links providing access to other web pages such as those mentioned above.

In step S12, the user launches the execution of the PWA application by executing the PLNK link, in association with the cookie containing the CI1 identifier of the payment device. The execution of the PLNK link triggers the sending of a web page request to a server, for example the PSRV server. Upon receipt of this request, in step S13, the PSRV server stores in the CB database that the client corresponding to the received CI1 identifier is requesting access to a web page. In step S14, the PSRV server generates the requested web page WP and transmits this page to the MT1 terminal in response to the PNLK request sent in step S12. In step S15, the MT1 terminal displays the received web page.

By using the PWA application mechanism, it is possible to display data directly on the mobile terminal used to carry out a payment transaction. Since the PNLK link is stored in the customer's MT1 mobile terminal, it can be activated multiple times, while the content accessible via this link can be modified. The merchant thus has a communication channel to transmit data such as multimedia data to people who have only visited the merchant's store once to make a purchase. This communication channel is established without any specific action by the store's customers, apart from activating the link received when they wish. Thanks to the CI1 identifier transmitted when the PNLK link is activated, the data transmitted by the PSRV server to the customer can be personalized.

It will be apparent to those skilled in the art that the present invention is susceptible of various alternative embodiments and various applications within the scope of the appended claims.

Claims (6)

1. Transaction method, comprising steps consisting of:
during a payment transaction by a customer at a merchant (ML1), establish a communication link between a payment terminal (TP1) of the merchant and a mobile terminal (MT1) of the customer;
acquire by the merchant's payment terminal (TP1), an identifier (CI1) of the customer's payment device;
transmit to a server (PSRV), data relating to the transaction and including the acquired payment device identifier;
store by the server the data relating to the transaction in a database (CB);
transmit by the server to the payment terminal (TP1) an access link (PNLK) to a progressive web application (WP);
transmit the access link and the payment device identifier (CI1), by the payment terminal to the mobile terminal, via the communication link;
upon activation of the access link, transmitting by the mobile terminal to the server, a request for access to the progressive web application containing the access link and the payment device identifier;
upon receipt of the request to access the progressive web application, generate by the server, a progressive web application;
transmit the progressive web application generated by the server to the mobile terminal; and
receive and run the progressive web application through the mobile terminal. 2. Method according to claim 1, wherein the progressive web application (WP) received by the mobile terminal (MT1) is configured to perform at least one of the following operations:
display a receipt relating to the payment transaction,
display an advertising message,
display a discount coupon linked to the payment transaction,
display data attached to a purchase,
display a loyalty program registration web page,
display a web page containing a customer account statement relating to a loyalty program, and
display a discount coupon. 3. Method according to one of claims 1 and 2, in which the payment device identifier (CI1) is determined by the payment terminal (TP1) by applying a cryptographic function to a bank card number stored and transmitted by the customer's mobile terminal (MT1) to the payment terminal. Method according to one of claims 1 to 3, further comprising steps consisting of:
memorize by the mobile terminal (MT1) the access link and the identifier (CI1) of the payment device received;
upon a second activation of the access link, transmit by the mobile terminal to the server (PSRV), the request for access to the progressive web application containing the access link and the payment device identifier; and
following the transmission of the access request, transmit a modified progressive web application to the mobile terminal by the server. Method according to one of claims 1 to 4, in which the communication between a payment terminal (TP1) of the merchant and the mobile terminal (MT1) of the customer is of the near field type. 6. Transaction system between a merchant and a customer, the system comprising:
a server (PSRV),
a payment terminal (TP1) installed at the merchant's premises and communicating with the server, and
a customer's mobile terminal (MT1), which can be put into communication with the payment terminal,
the system being configured to implement the method according to one of claims 1 to 5.