METHOD FOR DATA TRANSFER TO A MAGNETIC READ HEAD, DELETED DATA PROCESSING METHOD, PAYMENT CONNECTION AND PROGRAM THEREOF OF WHICH

DE602018076249T2Active Publication Date: 2024-11-06BANKS & ACQUIRERS INT HLDG SAS
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
DE602018076249
Authority / Receiving Office
DE · DE
Patent Type
Patents
Current Assignee / Owner
Priority Date
2017-06-13
Filing Date
2018-06-12
Publication Date
2024-11-06
Estimated Expiration
2038-06-12

AI Technical Summary

Technical Problem

Existing payment solutions struggle to efficiently transmit and process secondary data, such as loyalty program information, alongside primary payment data, leading to increased user manipulation and time requirements during transactions, especially when compatibility with traditional payment terminals is limited.

Method used

A method that integrates secondary data into the same data stream as primary payment data, using a magnetic field emulation technique, allowing for simultaneous transmission and processing of both types of data without disrupting conventional payment terminal operations, by inserting secondary data between standardized data sequences and using specific markers for detection and processing.

Benefits of technology

This approach simplifies payment transactions by eliminating the need for additional manipulations, ensuring compatibility with all payment terminals, and enabling secure and efficient validation of payment transactions through cryptographic calculations and loyalty program management, thereby reducing user and merchant time and effort.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader
Need to check novelty before this filing date? Find Prior Art

Description

1. Scope of the invention

[0001] The present invention relates to the field of payment transactions. More particularly, it concerns a method for transmitting secondary data to a magnetic read head of a payment terminal, in addition to primary data relating to a means of payment. The invention also relates to a method for processing the received data, implemented by a payment terminal. 2. Prior Art

[0002] Most payment cards include a magnetic stripe, usually located on the back, which contains data related to the payment card. Such magnetic stripe payment cards include credit cards, debit cards, gift cards, and promotional cards. The payment card data (for example, a bank account number, cardholder's name, expiration date, etc.) is written onto the magnetic stripe by alternating the orientation of magnetic particles embedded in the stripe. This data is typically transmitted to a payment terminal by swiping the card through the terminal's magnetic stripe reader. Such a reader includes at least one magnetic read head and an associated decoding circuit. When the card is swiped through the magnetic stripe reader, the card's magnetic stripe moves past the read head.This moving magnetic stripe, which contains magnetic domains of alternating polarity, generates a magnetic field in the narrow detection aperture of the read head. The read head converts this magnetic field into an equivalent electrical signal. The decoding circuit amplifies and digitizes this electrical signal, allowing the same data sequence to be recreated as that originally recorded on the magnetic stripe. The encoding of a payment card's magnetic stripe is described in the international standards ISO / IEC 7811 and 7813.

[0003] The growing popularity and capabilities of smartphones have prompted manufacturers to offer payment solutions using these communication devices. However, one of the main obstacles to the adoption of these payment solutions has been the lack of a data transfer channel between these communication devices and the payment terminals deployed at points of sale. For example, although many smartphones now incorporate Near Field Communication (NFC) capabilities, particularly to offer users contactless payment solutions, many payment terminals are not yet compatible with this contactless technology.The user then has no other choice but to keep a traditional payment card on them in addition to their smartphone, in order to be sure of being able to carry out a payment transaction in all circumstances.

[0004] Several solutions have been proposed to circumvent these incompatibility issues, with the aim of ensuring maximum compatibility with the range of payment terminals currently deployed worldwide. A recent solution involves equipping the user's mobile communication device (typically their smartphone) with a data transmission device that includes a coil capable of generating a magnetic field similar to that generated by the magnetic stripe of a payment card when it passes through the magnetic stripe reader of an electronic payment terminal. Such a data transmission device, described for example in document WO 2016 / 007475, can be connected to the smartphone's audio jack.Other solutions based on the same general principle, but which do not require connecting an additional device to the smartphone, have also been described: these solutions rely on the use of a coil already present in the smartphone (for example, the coil used for inductive charging of some smartphones) to generate such a fluctuating magnetic field. Thus, it becomes possible to make a contactless payment using a smartphone implementing such technology, provided that the payment terminal used for the transaction is equipped with a magnetic stripe card reader (which is the case for the vast majority of electronic payment terminals). The user simply needs to bring their smartphone close enough to the payment terminal for the reader to detect the fluctuations in the magnetic field emitted by the smartphone (or the device connected to it).From the payment terminal's perspective, everything then proceeds as if a magnetic stripe payment card had been swiped through its magnetic stripe reader. This technique thus creates a contactless data transfer channel between a smartphone and a payment terminal, enabling the transmission of payment card data previously stored on the smartphone, for the purpose of processing a payment transaction. This solution aims to simplify payment transactions for the user: they can be carried out simply and quickly, with a limited number of steps, using a communication terminal they already possess. Document WO2016 / 110591 describes a data transmission technique from a communication terminal to a magnetic stripe reader.

[0005] However, in practice, for an increasing number of payment transactions, users need to provide additional information beyond their payment method details. This is particularly true when a user joins a loyalty program and wishes, for example, to receive an immediate discount on a purchase they are currently making, or to accumulate loyalty points associated with the purchase to later obtain a reward for their loyalty. In this case, the user must provide the merchant with additional information to identify them within the loyalty program. This additional information—or secondary data—is provided, for example, in the form of a barcode to be scanned by the merchant.Such a barcode can be printed on a physical loyalty card (the user must then take the card out of their wallet to present it to the merchant) or displayed on the user's smartphone screen via a dedicated application (the user must then open the application and select the loyalty card to display). Consequently, the advantages offered by the previously described payment solution—which emulates, using an electronic device such as a smartphone, the swiping of a magnetic stripe payment card through a payment terminal reader—are largely negated by the additional steps and time required for transmitting secondary data, which is not directly related to the payment itself.

[0006] There is therefore a need for processes that allow the transmission and processing of secondary data alongside a payment operation, and which do not present at least some of the disadvantages described above. 3. Summary

[0007] The proposed technique does not present these drawbacks of the prior art. More specifically, in one aspect, the proposed technique relates to a data transmission method defined by claim 1.

[0008] Thus, the proposed transmission method leverages the transmission of data representing a payment method (standardized data) to a payment terminal to also transmit secondary data intended, for example, to confirm, enrich, or complete a payment transaction. In this way, the transmission of data relating to the payment method and the transmission of secondary data are no longer separate: this information is transmitted through the same communication channel and in a single sequence, via the generation of a magnetic field capable of being detected by the magnetic read head of a payment terminal. Furthermore, since the secondary data is transmitted between successive transmissions of standardized data, it does not interfere with the normal reception of this standardized data by the payment terminal.The solution is therefore compatible with all types of payment terminals, even those that do not allow the processing of secondary data.

[0009] According to a particular embodiment, said secondary data includes at least one data representative of a bank authentication token.

[0010] Thus, secondary data offers the possibility of validating a payment transaction at a payment terminal by allowing verification of the authenticity of the standardized data representing a means of payment.

[0011] According to yet another particular embodiment, said secondary data includes at least one loyalty program identifier.

[0012] The proposed technique allows for the transmission of data that establishes a user's membership in a loyalty program, simultaneously with the payment information required to finalize a payment transaction. Providing this secondary data to the payment terminal enables it to process the information to enhance the payment transaction (for example, to obtain a discount or to credit loyalty points to a loyalty account). In this way, providing this information to the merchant eliminates the need for additional and time-consuming actions by the user (for example, they do not need to search their wallet for a loyalty card to present to the merchant).

[0013] According to another aspect, the proposed technique also relates to a data processing method defined by claim 4.

[0014] Thus, the presence of secondary data within a data stream received by a payment terminal can be detected, and this secondary data can be retrieved at the same time as normalized data representative of a means of payment, to carry out processing related to or alongside the execution of a payment operation.

[0015] Similarly, it is possible to differentiate the processing to be carried out on secondary data, depending on the type of secondary data retrieved within the data stream received by the payment terminal.

[0016] In addition, the detection of well-identified tags within the data stream received by the payment terminal makes it easier to recover normalized data sequences, but also to recover secondary data included between these sequences.

[0017] The detection of a specific character sequence after the end-of-sequence tag of normalized data indicates to the payment terminal that secondary data is present in the data stream, and that the terminal can read and process this secondary data. Furthermore, this indicator allows the terminal to know the type of secondary data even before receiving it, so that it can subsequently process this secondary data accordingly.

[0018] According to a particular embodiment, said processing step includes, where the secondary data takes the form of at least one authentication token: a step of performing a cryptographic calculation, from said normalized data; a step of comparing a result of said cryptographic calculation with said at least one authentication token, delivering an authenticity information of said normalized data.

[0019] The payment terminal can therefore perform a cryptographic calculation, the result of which is compared to an authentication token contained within the received secondary data, in order to verify the authenticity of the standardized data representing a payment method. If necessary, the payment terminal can block a payment transaction if the result of the cryptographic calculation is inconsistent with the authentication token (the payment data provided could then have been obtained fraudulently).

[0020] According to another particular embodiment, said processing step includes, where the secondary data takes the form of at least one loyalty program identifier, a step of transmitting said at least one loyalty program identifier to a loyalty program management server.

[0021] Thus, the payment terminal is able to simultaneously manage the execution of a payment operation (using standardized data), and the associated loyalty aspects (using secondary data, which allows, for example, the identification of the user with a loyalty program management server).

[0022] According to a particular embodiment, said step of comparing the character string with at least one reference data includes comparing this character string with a plurality of reference data representative of secondary data types.

[0023] According to yet another particular embodiment, the data processing method further comprises: a step of obtaining said at least two consecutive identified normalized data sequences; a step of comparing said at least two normalized data sequences, delivering control information.

[0024] In this way, the control information makes it possible to verify that the normalized data received has not been altered during the transmission of the data (it is unlikely that the same transmission error will occur twice in a row during the transmission of a sequence of normalized data).

[0025] According to a preferred implementation, the various steps of the processes according to the proposed technique are implemented by one or more software or computer programs, comprising software instructions intended to be executed by a data processor of a relay component according to the proposed technique and designed to control the execution of the various steps of the processes.

[0026] Consequently, the proposed technique also targets a program defined by claim 11.

[0027] This program can use any programming language, and be in the form of source code, object code, or code somewhere between source code and object code, such as in a partially compiled form, or in any other desirable form.

[0028] The proposed technique also aims for an information support readable by a data processor, and containing instructions from a program as mentioned above.

[0029] The information medium can be any entity or communication terminal capable of storing the program. For example, the medium can include a storage means, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or a magnetic recording means, for example a floppy disk or a hard disk.

[0030] On the other hand, the information medium can be a transmissible medium such as an electrical or optical signal, which can be transmitted via an electrical or optical cable, by radio, or by other means. The program, according to the proposed technique, can in particular be downloaded from a network such as the Internet.

[0031] Alternatively, the information carrier may be an integrated circuit in which the program is incorporated, the circuit being adapted to execute or to be used in the execution of the process in question.

[0032] In one embodiment, the proposed technique is implemented using software and / or hardware components. In this context, the term "component" may refer in this document to a software component, a hardware component, or a set of hardware and software components.

[0033] A software component corresponds to one or more computer programs, one or more subroutines of a program, or more generally to any element of a program or software capable of implementing a function or set of functions, as described below for the component in question. Such a software component is executed by a data processor of a physical entity (terminal, server, gateway, router, etc.) and is capable of accessing the hardware resources of that physical entity (memory, storage media, communication buses, input / output electronic cards, user interfaces, etc.).

[0034] Similarly, a hardware component corresponds to any element of a hardware assembly capable of implementing a function or set of functions, as described below for the component in question. This could be a programmable hardware component or one with an integrated processor for software execution, for example, an integrated circuit, a smart card, a memory card, an electronic board for running firmware, etc.

[0035] Each component of the system described above naturally implements its own software components.

[0036] According to another aspect, the proposed technique also relates to a payment terminal as defined by claim 9.

[0037] According to yet another aspect, the proposed technique relates to a signal defined by claim 10.

[0038] The different embodiments mentioned above are used for the implementation of the proposed technique. 4. Drawings

[0039] Other features and advantages of the invention will become clearer upon reading the following description of a preferred embodiment, given by way of simple illustrative and non-limiting example, and the accompanying drawings, among which: there figure 1a presents the general structure of a data stream transmitted from an electronic device to a magnetic read head of a payment terminal, according to a prior art technique; the Figure 1b presents the general structure of a data stream transmitted from an electronic device to a magnetic read head of a payment terminal, according to the general principle of the invention; figure 2illustrates the main steps of a data transmission process implemented in an electronic device, in a particular embodiment of the invention; the figure 3 illustrates the main steps of a process for processing data received by a magnetic read head of a payment terminal, in a particular embodiment of the invention; the figure 4 describes a simplified architecture of an electronic device capable of implementing a data transmission process to a magnetic read head, in a particular embodiment; - - there Figure 5 describes a simplified architecture of a payment terminal in a particular embodiment. 5. Description 5.1. General principle

[0040] The general principle of the invention consists of cleverly exploiting certain possibilities offered by the previously described technique of emulating, using an electronic device, the magnetic field generated by a magnetic stripe card, with the aim of overcoming certain current constraints related to payment transactions. More specifically, it is proposed to take advantage of the data transmission operation representing a payment method to transmit secondary data to a payment terminal, intended, for example, to confirm, enrich, or supplement the payment transaction.For example, with the proposed technique, when a user makes a payment to a retailer to purchase a good or service, secondary data relating to the user's membership in that retailer's loyalty program is transmitted to the payment terminal simultaneously with the user's payment card information. In other words, the transmission of payment method data and secondary data is no longer carried out in two separate steps, but in a single operation: the number of actions required for both the user and the merchant is reduced, and both save time. This is achieved by inserting the secondary data within the data stream containing the primary payment method data, in a specific manner which is the subject of this technique and is detailed below.

[0041] It is necessary to first recall some information useful for understanding the invention.

[0042] On a conventional magnetic stripe payment card, the payment card data—which represents a means of payment—is recorded on the magnetic stripe according to a specific format defined by the international standard ISO / IEC 7813. The magnetic stripe of the payment card may include up to three tracks (numbered 1 to 3), each track containing a predetermined amount of information about the payment card. The data recorded on each track is structured precisely. This ensures the payment card's compatibility with a large number of payment terminals (a payment terminal capable of reading one of the tracks is sufficient for the payment transaction to be completed). For the purposes of this invention, it is not necessary to detail the specific format of each track further.However, it should be noted that all tracks share the same general structure, namely: . a start tag (also called "start sentinel" in English); data, called main data in the context of the present invention, which includes data relating to the payment card (account number also called "Primary Account Number" or PAN in English, expiry date, etc.); an end tag (also called "end sentinel" in English); a longitudinal parity check character (also called LCR character, from the English "Longitudinal Redundancy Check").

[0043] All of this data forms a standardized dataset, conforming to the formalism described in ISO / IEC 7813. The main data is located between the start and end tags, and the longitudinal parity check character is located immediately after the end tag. The start and end tags are specific characters that delimit the payment card data, thus facilitating its retrieval at the payment terminal. These start and end tags are different, which allows the payment terminal to determine the direction in which a magnetic stripe payment card was swiped (and, if necessary, reverse the order of the received data if the end tag is detected before the start tag).The longitudinal parity check character is the result of a calculation performed on previous data, particularly the master data. This character is used to detect potential transmission errors that might occur when the magnetic stripe data of the payment terminal is read by the payment terminal's magnetic stripe reader. When a payment terminal receives data, it is expected to calculate a longitudinal parity check character based on the received data and compare this calculated character to the longitudinal parity check character received from the magnetic stripe card. When a difference is detected, the data has likely been corrupted during transmission.

[0044] When using a magnetic stripe bank card to make a payment, the card is physically slid, along its entire length, into a slot of a magnetic stripe card reader, so that the magnetic stripe is fully read by at least one magnetic read head with which it is aligned as the card moves through the slot. The slot thus acts as a guide, and a single pass of the card through the reader slot is normally required for the data on the magnetic stripe to be correctly and completely read, provided the movement is performed at a reasonable speed.In the technique implemented within the framework of the present invention, the passage of a magnetic stripe card through the slot of the payment terminal reader is replaced by the action of positioning an electronic device near such a slot, and therefore near a reading head capable of detecting the magnetic field fluctuations generated by the electronic device. The slot no longer acts as a guiding means, and various parameters can then influence the correct reading of the data at the payment terminal: the orientation or distance of the electronic device from the payment terminal, or the moment at which the electronic device is brought near the payment terminal.It is therefore preferable, at the level of the electronic device, to cyclically emit the standardized data representing a means of payment, in order to allow, for example, the user to adjust the position of the electronic device in relation to the payment terminal until this standardized data is correctly received by the payment terminal.

[0045] This is particularly illustrated in relation to the figure 1a ,which presents a data stream FD_AA emitted in the form of magnetic field fluctuations by an electronic device, according to the principle of emulating the magnetic field created by a magnetic stripe card already described in relation to the prior art. The data transmission method implemented at the level of this electronic device thus comprises a plurality of transmissions of the same sequence of standardized data D_Nor, said standardized data being representative data of a means of payment formatted according to the ISO / IEC 7813 standard, as previously described. This data therefore comprises a start tag BD, then main data D_Princ, followed by an end tag BF, and finally a longitudinal parity check character CC.This repeated transmission of the normalized D_Nor data significantly increases the chances that this data will be correctly received by a payment terminal to which the electronic device is brought close.

[0046] We now describe, in relation to the Figure 1b , A data stream FD emitted in the form of magnetic field fluctuations by an electronic device, according to the general principle of the present invention. This data stream FD differs from the prior art data stream FD_AA in that it includes the transmission of secondary data D_Sec, emitted between two successive transmissions of the standardized data sequence D_Nor. The fact that the transmitted data is no longer the data recorded on the magnetic stripe of a payment card, but rather data inserted into a data stream constructed within an electronic device, depending on the circumstances of a payment transaction, allows for the insertion of secondary data D_Sec within such a stream. This secondary data D_Sec is thus transmitted simultaneously with the standardized data D_Nor to the payment terminal.The secondary D_Sec data is cleverly inserted between the BF end tag of the current normalized data sequence and the BD start tag of the next normalized data sequence, so that the payment terminal's reading of a normalized data sequence is not disrupted by this secondary D_Sec data. More specifically, according to a preferred characteristic, the secondary D_Sec data is inserted after the BF end tag of the current normalized data sequence, immediately following a number of characters corresponding to the length of the longitudinal parity check data (usually one character), and it extends to the BD start tag of the next normalized data sequence.This ensures compatibility of the solution with existing and already deployed payment terminals, while allowing the implementation of new payment terminals for the processing of this secondary data in addition to the standardized data. 5.2. Data transmission method

[0047] In its first aspect, the proposed technique relates to a method of transmitting data to a magnetic read head of a payment terminal. This method is implemented by an electronic device capable of generating a magnetic field representative of an encoding of said data. As already presented in relation to the prior art, such an electronic device can, for example, be a communication terminal such as a smartphone or tablet, a dedicated standalone electronic device, or an electronic device intended to be coupled to a communication terminal (the electronic device can then, for example, be integrated into a protective case of the communication terminal).

[0048] There figure 2This describes the main steps of such a data transmission process in a particular embodiment. This process includes a step 21 for obtaining primary data D_Princ, which consists of data relating to a means of payment, for example, a Personal Account Number (PAN), a cardholder's name, and a payment card expiry date. The process also includes a step 22 for obtaining secondary data D_Sec. In a step 23 for constructing the data to be transmitted, the primary data D_Princ and the secondary data D_Sec are organized and structured to form the basic pattern that will be repeated cyclically in the emitted FD data stream. In particular, the primary data D_Princ is formatted according to the ISO / IEC 7813 standard, thus delivering a sequence of standardized data D_Nor.The process finally includes a step 24 of transmission of an FD data stream, comprising the repeated emission of the previously constructed basic pattern, in the form of a fluctuating magnetic field.

[0049] In one particular embodiment, the primary data D_Princ and the secondary data D_Sec are obtained within a secure element of the electronic device. If the electronic device is not a standalone device, but a device intended to be connected to a communication terminal, the data may also be obtained within a secure element of the communication terminal. This data may, for example, have been previously provisioned by the user within a dedicated application installed on the electronic device or on the communication terminal. Such an application may, in particular, be an electronic wallet application, which allows, among other things, the storage of information associated with several cards as well as additional information.Through this application, the user can choose the payment information and secondary data to use for a payment transaction on a case-by-case basis. They can also configure "default" payment information and "default" secondary data, which will be used by default for a payment transaction (unless the user specifies otherwise).

[0050] Depending on the various embodiments of the proposed transmission method, the transmitted secondary data D_Sec may include at least one bank authentication token and / or at least one loyalty program identifier. The advantages of transmitting secondary data of this type are presented later, in connection with the description of different embodiments of the data processing method implemented at the payment terminal receiving the FD data stream. 5.3. Data processing method

[0051] The proposed technique also relates to a method for processing data received by a magnetic read head of a payment terminal. This method, implemented by the payment terminal, is described in relation to the figure 3 , in a particular embodiment.

[0052] In an identification step 31, the payment terminal identifies at least two successive normalized data sequences D_Nor within a data stream FD received at its magnetic read head. The normalized D_Nor data represents a payment method and is formatted according to the ISO / IEC 7813 standard. Therefore, the identification of this normalized D_Nor data can be based on the identification of start tags BD and end tags BF of the normalized data sequence.

[0053] The payment terminal then performs a determination step 32, in which it determines whether specific data, referred to as secondary data, is present within the received data stream. Such secondary data D_Sec consists of data located between two successive normalized data sequences D_Nor from among the previously identified successive normalized data sequences. This determination step 32 for the presence of secondary data can be implemented in various ways. In one particular embodiment, the payment terminal listens for data located between the longitudinal parity check character—whose length is known and which is known to be located immediately after the end tag BF of a normalized data sequence in the received data stream, thus enabling its detection—and the start tag BD of the next normalized data sequence within the stream.For example, as soon as the payment terminal detects that it has received a longitudinal parity check character (which it infers after detecting the reception of a BF end tag), it stores the received data in a buffer as it receives the FD stream, until it detects the reception of a BD start tag from the next normalized data sequence. If such data exists, then it is secondary data D_Sec on which the payment terminal can attempt to perform processing. In another particular embodiment, the character immediately following the normalized data end tag is cleverly repurposed from its primary function as a longitudinal parity check character to serve as a presence marker and / or secondary data type.Indeed, unlike the data written on the magnetic stripe of a payment card, the data stream is constructed and transmitted by the issuing electronic device, and its content can be adapted to suit the specific circumstances of a payment transaction. Therefore, it is possible to replace the longitudinal parity check character with a specific character appropriate to the needs of an ongoing payment transaction within the transmitted data stream. Ideally, this specific character is the same length as the longitudinal parity check character to remain compliant with the format described in ISO / IEC 7813.In this case, the determination step 32 includes a reading step within the received data stream, of a predetermined number of characters located immediately after the end-of-sequence tag of normalized data in the received data stream, delivering a string of characters (this predetermined number of characters corresponds to the length of the longitudinal parity check data, usually an alphanumeric character, or a byte or eight bits). This string of characters is then compared with at least one reference data point, to deliver a reference indicator in the event of a positive comparison.

[0054] This reference indicator can, in particular, be a representative indicator of the presence of secondary data. Thus, the detection of a particular sequence of characters after the end-of-sequence tag of normalized data indicates to the payment terminal that secondary data is present in the data stream, and that the payment terminal can read and process this secondary data.

[0055] According to a specific characteristic, the character string is compared with several reference data points, each representing a type of secondary data. Thus, the payment terminal can be informed, even before receiving them, that the following data in the stream is secondary data. The payment terminal also knows their type and is therefore able to adapt its processing of this secondary data accordingly.

[0056] If the payment terminal detects the presence of secondary data during the determination step 32, it retrieves them in a retrieval step 33 (for example within a buffer), then it implements a processing step 34 of this secondary data.

[0057] In one particular embodiment, the processing performed in step 34 differs depending on the type of secondary data obtained within the data stream received by the magnetic read head. According to a specific feature, the type of secondary data can be deduced from its format. In this case, it is necessary to have already retrieved the secondary data in order to identify its type. Alternatively, the type of secondary data can be determined by the payment terminal even before receiving the secondary data in question, for example, by inserting a specific, appropriate character into the normalized data stream instead of a longitudinal parity check character, as described previously.

[0058] In one particular embodiment, the data processing method also includes a step of obtaining at least two of the previously identified consecutive standardized data sequences, and a step of comparing these standardized data sequences, providing control information. This control information makes it possible, in particular, to verify that the received standardized data has not been altered during data transmission between the sending electronic device and the payment terminal. Indeed, it is unlikely that the same transmission error will occur twice in succession during the transmission of a standardized data sequence. Thus, when at least two consecutive received standardized data sequences are identical (at least with regard to the main data between the start and end tags), it can be considered that this data has not been altered during transmission.Thus, replacing the longitudinal parity check character with a specific character that acts as an indicator of the presence and / or type of secondary data, as proposed in one particular embodiment, is not problematic: the proposed solution also offers another way to verify that the data received at the payment terminal matches the data transmitted by the electronic device. It should be noted that this same strategy can also be applied to secondary data to ensure that it has not been altered during transmission, in another particular embodiment.

[0059] We now briefly present two examples of differentiated processing of secondary data, depending on their type. Example 1: Secondary data of type "authentication token"

[0060] In one particular embodiment, the secondary data takes the form of a bank account authentication token. Processing step 34 then involves the payment terminal performing a cryptographic calculation on the received standardized data, and then comparing the result of this calculation with at least one authentication token received as secondary data. Such a comparison makes it possible, for example, to verify the authenticity of the transmitted bank account data, or to ensure that it is not being used to make a payment from an unknown electronic device, which would mean that it could have been obtained fraudulently. If the comparison is negative, meaning that the result of the cryptographic calculation differs from the authentication token, the payment method data is rejected, and the payment transaction is canceled.

[0061] According to a specific feature, the authentication token is provided by a secure element of the electronic issuing device or a communication terminal to which it is connected, and / or by a secure third-party application such as a banking application. In the particular embodiment associated with the example just described, secondary data is therefore used to validate or invalidate a payment transaction, thereby increasing the security of a payment made using this type of technique, which is not possible with prior art techniques. Example 2: Secondary data of the type "loyalty program identifier"

[0062] In another specific embodiment, the secondary data takes the form of a loyalty program identifier. Processing step 34 then involves the transmission, by the payment terminal, of this loyalty program identifier to a loyalty program management server. The user making the payment transaction can thus be identified (within a data structure of the loyalty program management server, for example) and benefit from the advantages conferred by their membership in the loyalty program (obtaining a discount automatically applied to the amount to be paid, adding loyalty points to a loyalty account, etc.).This process is relatively transparent for both the user and the merchant: the loyalty program ID is transmitted to the payment terminal along with the payment method data. The user did not need to present a loyalty card, and the merchant therefore did not have to scan the barcode associated with such a card. This results in time savings for all parties, and consequently, an increase in the number of payment transactions that can be processed by an operator (such as a cashier). A key feature of this process is that the loyalty program ID transmitted as secondary data is a unique loyalty program identifier, which an intermediary server can use to retrieve a specific loyalty program ID for the user in a given payment transaction.In the particular embodiment associated with the example just described, secondary data is therefore used to complete or enrich a payment operation. 5.4. Other features and advantages

[0063] We describe, in relation to the figure 4 An electronic device comprising means for carrying out the data transmission process described above, in a particular embodiment. Such an electronic device comprises: means of obtaining primary data D_Princ, relating to a means of payment, such as an account number (PAN), a holder's name, and / or an expiry date of a payment card; means of obtaining secondary data D_Sec; means of constructing data to be transmitted from the primary data D_Princ and the secondary data D_Sec, said construction means being in particular capable of formatting the primary data D_Princ in accordance with the ISO / IEC 7813 standard to deliver normalized data D_Nor, and of organizing and structuring the normalized data D_Nor and the secondary data D_Sec so as to form a basic pattern of a data stream to be issued; means of transmitting said data to be transmitted, in the form of a data stream comprising a plurality of alternations of the same sequence of normalized data and secondary data, by modulation of a magnetic field.

[0064] For example, the electronic transmission device includes a memory 41 consisting of a buffer, a processing unit 42, equipped, for example, with a microprocessor, and controlled by the computer program 43, implementing, in particular, a data transmission method by modulation of a magnetic field. At initialization, the code instructions of the computer program 43 are, for example, loaded into a memory before being executed by the processor of the processing unit 42. The processing unit 42 receives, for example, at least one request as input E for the transmission of data necessary to carry out a payment transaction.The microprocessor of the processing unit 42 then implements the steps of the transmission process, according to the instructions of the computer program 43, in order to retrieve primary data relating to a payment card and secondary data intended to confirm, enrich, or complete the payment transaction, and to structure this data to generate, as output S, a modulation of a magnetic field emitted by a coil of the electronic device. The modulation of the magnetic field may be preceded by encoding the data to be transmitted.

[0065] For this purpose, the electronic device includes, in addition to the buffer memory 31, means of communication, such as network communication components, a data transmission component and possibly a dedicated encryption processor.

[0066] All of these means can take the form of a specific processor implemented within the device. This processor is a secure processor capable of handling confidential data, such as payment information or bank authentication tokens. In one particular embodiment, this electronic device implements a specific application responsible for encryption and data transmission. This application may be provided, for example, by the processor manufacturer to enable its use. To this end, the processor includes unique identifiers. These unique identifiers ensure the processor's authenticity.

[0067] The proposed technique also relates to a payment terminal incorporating a magnetic read head and including means for performing the data processing procedure described above. Such a payment terminal is described in particular in relation to the Figure 5 in a particular embodiment, and it includes: means of identifying, within a data stream received at the level of the read head, at least two successive normalized data sequences, said normalized data being data representative of a means of payment, formatted according to the ISO / IEC 7813 standard; means of determining the presence, within the received data stream, of so-called secondary data included between two successive normalized data sequences among said at least two successive normalized data sequences previously identified; means of obtaining said secondary data; means of processing said secondary data obtained.

[0068] For example, the payment terminal includes a memory 51 consisting of a buffer, a processing unit 52, equipped, for example, with a microprocessor, and controlled by the computer program 53, implementing, in particular, a process for processing the data received at the magnetic read head of the payment terminal. At initialization, the code instructions of the computer program 53 are, for example, loaded into memory before being executed by the processor of the processing unit 52. The processing unit 52 receives, for example, at least one instruction for the initialization of a payment transaction as input E. The microprocessor of the processing unit 52 then implements the steps of the processing procedure, according to the instructions of the computer program 53.It listens to the data received at the magnetic read head of the payment terminal in order to identify, within the received stream, normalized data sequences representative of a payment method, and to determine the possible presence of secondary data between two normalized data sequences. If a positive determination is made, the secondary data is obtained and processed, and the result of this processing is reported at output S.

[0069] To this end, the payment terminal includes, in addition to the buffer memory 41, means for transmitting and receiving data, which may take the form of an interface for connecting to one or more communication networks. These means may also allow for establishing a link with partner servers for managing loyalty programs. The payment terminal may also include cryptographic calculation means, enabling it to verify the authenticity of data representing a received payment method by comparing the result of a cryptographic calculation with an authentication token.

[0070] In another respect, the proposed technique also relates to a signal emitted as a magnetic field by an electronic device. This signal comprises multiple alternations of the same sequence of normalized data and the same secondary data. The normalized data represents a means of payment and is formatted according to the ISO / IEC 7813 standard. The normalized data sequence includes a start tag (BD) followed by the primary data (D_Pr) and terminated by an end tag (BF). In a particular feature, the normalized data sequence also includes, immediately following the end tag (BF), a presence indicator indicating the presence of secondary data within the signal. This presence indicator is, for example, encoded as a single character.In this way, additional data is transmitted while respecting the formalism dictated by the ISO / IEC 7813 standard.

[0071] The embodiments previously described in the context of the present invention are given by way of illustrative and non-limiting examples, in order to best illustrate the general principle of the invention as defined in the claims. With the already described ability to transmit a type of secondary data, it is particularly possible to consider a specific embodiment in which several distinct secondary data items are transmitted within the same data stream, each of these secondary data items being interleaved between two identical sequences of standardized data. Upon receiving a single data stream, and based on the types of secondary data identified within this stream, the payment terminal is then able to initiate multiple processing steps in addition to a primary payment operation, each of these steps being adapted to the secondary data being processed.

Claims

1. A method of transmitting data to a magnetic read head of a payment terminal, said method being implemented by an electronic device suitable for generating a magnetic field representative of an encoding of said data, said data transmission comprising a plurality of transmissions of a same standardised data sequence (D_Nor), said standardised data being data representative of a means of payment formatted in accordance with the ISO / I EC 7813 standard, said standardised data sequence comprising a start tag for the standardised data sequence and an end tag for the standardised data sequence, said method being characterised in that it further comprises the transmission of secondary data (D_Sec), said secondary data (D_Sec) being transmitted between two successive transmissions of said standardised data sequence (D_Nor), said standardised data sequence further comprising a predetermined number of characters located immediately after the end tag of said standardised data sequence, said predetermined number of characters corresponding to a sequence of characters representative of a presence and a type of said secondary data, said secondary data being to be processed by the payment terminal as a function of said type.

2. A method of transmitting data as claimed in claim 1, characterised in that said secondary data comprises at least one data item representative of a bank authentication token.

3. A method of transmitting data as claimed in claim 1, characterised in that said secondary data comprise at least one loyalty programme identifier.

4. A method of processing data received by a magnetic read head of a payment terminal, said method being implemented within said payment terminal and characterised in that it comprises: - a step of identifying, within a data stream received at said read head, at least two successive standardised data sequences, said standardised data being data representative of a means of payment formatted in accordance with the ISO / IEC 7813 standard, said identification step comprising at least one identification of a standardised data sequence start tag and a standardised data sequence end tag ; - a step of determining the presence, within said received data stream, of so-called secondary data comprised between two successive standardised data sequences from among said at least two previously identified successive standardised data sequences, said determination step comprising : - a step of reading, within the received data stream, a predetermined number of characters located immediately after said standardised data sequence end tag in said received data stream, delivering a sequence of characters ; - a step of comparing said sequence of characters with at least one reference data item, delivering a reference indicator of said secondary data in the event of a positive comparison. and when the step of determining a presence delivers a positive result: - a step for obtaining said secondary data ; - a step of processing said secondary data obtained as a function of said type of secondary data.

5. Method of processing data according to claim 4, characterised in that said processing step comprises, when said secondary data takes the form of at least one authentication token: - a step of performing a cryptographic calculation, on the basis of said normalised data ; - a step of comparing a result of said cryptographic calculation with said at least one authentication token, delivering information about the authenticity of said standardised data.

6. Method of processing data according to claim 4, characterised in that said processing step comprises, when said secondary data take the form of at least one loyalty program identifier, a step of transmitting said at least one loyalty program identifier to a loyalty program management server.

7. A method of processing data as claimed in claim 4, characterised in that said step of comparing the character string with at least one reference data item comprises comparing the character string with a plurality of reference data items representative of secondary data types.

8. A method of processing data according to claim 4, characterised in that it further comprises: - a step of obtaining said at least two consecutive standardised data sequences identified ; - a step of comparing said at least two standardised data sequences, delivering control information.

9. Payment terminal comprising a magnetic reading head, said terminal being characterised in that it comprises : - means for identifying, within a data stream received at said read head, at least two successive standardised data sequences, said standardised data being data representative of a means of payment, formatted in accordance with the ISO / IEC 7813 standard, said identification means being adapted to identify at least one standardised data sequence start tag and a standardised data sequence end tag; - means for determining the presence, within said received data stream, of so-called secondary data comprised between two successive standardised data sequences from among said at least two previously identified successive standardised data sequences, said determination means comprising : - means for reading, within a received data stream, a predetermined number of characters located immediately after said standardised data sequence end tag in said received data stream, delivering a sequence of characters ; - means for comparing said sequence of characters with at least one reference data item, delivering a reference indicator representative of a presence and a type of said secondary data in the event of a positive comparison; - means for obtaining said secondary data; and - means for processing said secondary data obtained, as a function of said type of secondary data.

10. Signal emitted in the form of a magnetic field by an electronic device to a magnetic read head of a payment terminal, said signal being characterised in that it comprises a plurality of alternations of the same standardised data sequence and the same secondary data, said standardised data being data representative of a means of payment, formatted in accordance with the ISO / IEC 7813 standard, said standardised data sequence comprising a start tag (BD) for a standardised data sequence followed by main data (D_Pr) and terminated by an end tag (BF) for a standardised data sequence, said standardised data sequence further comprising, immediately after said end tag (BF) for standardised data sequence, a predetermined number of characters corresponding to a sequence of characters representative of the presence and a type of said secondary data within said signal, the processing of said secondary data by the payment terminal being implemented as a function of said type.

11. A computer program product downloadable from a communications network and / or stored on a computer-readable medium and / or executable by a microprocessor, characterised in that it comprises program code instructions for executing a method according to any one of claims 1 to 3 and / or claims 4 to 8, when executed on a computer.