Payment terminal devices and methods

Abstract

To provide a payment terminal device that offers currency conversion, and a method of operation thereof.SOLUTION: A method of operating a payment terminal device comprising a contactless payment carrier reader for communicating with a contactless payment carrier, a communication module for communicating messages with a remote location, and a controller, the method comprising: receiving, by the controller, payment data from the contactless payment carrier for completing a transaction from the contactless payment carrier reader; storing the received payment data including encryption; determining whether the transaction will be completed in foreign currency or terminal currency; generating a first type authentication request message if it is determined that the transaction will be completed in the foreign currency; generating a second type authentication request message if it is determined that the transaction will be completed in the terminal currency; and transmitting the generated authentication request message to a remote location via a communication module to complete the transaction.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present disclosure relates to a payment terminal device that presents currency conversion and a method for operating a payment terminal device that presents currency conversion.

Background Art

[0002] In recent years, the use of contactless payments through the use of contactless payment carriers and contactless payment terminals has increased significantly. However, this increase has been somewhat hindered by the improved convenience provided to users, and for this convenience, further speed-up and simplification of the payment procedure have been carried out. In this context, the user can refer to either the user of the payment carrier or the user of the payment terminal (if any) in, for example, point-of-sale management. Examples of contactless payment carriers include contactless credit or debit cards, mobile applications. On the other hand, the increasingly widespread use of this contactless solution has also been accompanied by the use of tokenization services.

[0003] However, while the contactless payment procedure seems to have been simplified from the user's perspective, certain security procedures need to be generated to address the fact that this payment procedure is necessarily different from the payment procedure in which the card is physically inserted into the terminal for most of the duration of the transaction. Such security procedures are very important in ensuring that the transaction is not fraudulent and thus must be complied with as a regulation and as a result of practical considerations. An example of a specification regarding contactless payments is [1] "EMV (Registered Trademark) Contactless Specifications for Payment Systems", Book C-3, the entire content of which is incorporated herein by reference and defines the security and authentication procedures for performing contactless transactions using "EMV" cards of Europay, MasterCard, and Visa.

[0004] While such procedures are currently relatively well-established, they are designed with conventional transactions (which still constitute the majority of transactions conducted globally) in mind and are not necessarily adequately suited to non-conventional transactions. An example of a non-conventional transaction is one that involves a currency conversion option to settle a transaction in a currency different from the one used by the terminal. For example, when a transaction is conducted using a payment instrument associated with another country and / or a foreign currency, the transaction may be presented in the domestic currency or the currency of the payment instrument. As will become clear from the following considerations, current contactless payment procedures are not adequately suited to these types of situations. Therefore, it may be desirable to provide a configuration that addresses such cases. [Overview of the project] [Means for solving the problem]

[0005] The present invention is defined in the accompanying claims.

[0006] A first example of this disclosure provides a payment terminal device for contactless payments that offers currency conversion from a terminal currency to another currency, wherein the terminal is associated with a terminal currency. The payment terminal device comprises a contactless payment carrier reader configured to communicate with a contactless payment carrier, a communication module configured to communicate messages with a remote location, and a control unit. The control device is configured to receive payment data from a contactless payment carrier reader to complete a transaction, to store the received payment data containing encryption, to determine whether the transaction will be completed in foreign currency or terminal currency, and if it is determined that the foreign currency is a different currency from the terminal currency, generate a first type of authentication request message, which includes a foreign currency indicator to identify the foreign currency, a converted transaction amount corresponding to the transaction amount converted into the foreign currency, a terminal currency indicator to identify the terminal currency, the transaction amount, and encryption; if it is determined that the transaction will be completed in terminal currency, generate a second type of authentication request message, which includes a terminal currency indicator, the transaction amount, and encryption; and transmit the generated authentication request message to a remote location via a communication module to complete the transaction.

[0007] Another example of this disclosure provides a method for operating a payment terminal device for contactless payments that presents currency conversion from a terminal currency to another country's currency, wherein the terminal is associated with the terminal currency. The method includes the steps of: receiving payment data from a contactless payment carrier to complete a transaction from a contactless payment carrier reader, wherein the payment data includes cryptography and the transaction is associated with a transaction amount in the terminal currency; storing the received payment data including cryptography; determining whether the transaction will be completed in a foreign currency or the terminal currency, wherein if it is determined that the foreign currency is a different currency from the terminal currency and the transaction will be completed in the foreign currency, a first type of authentication request message is generated, wherein the first type of authentication request message includes a foreign currency indicator that identifies the foreign currency, a converted transaction amount corresponding to the transaction amount converted into the foreign currency, a terminal currency indicator that identifies the terminal currency, the transaction amount, and cryptography; and if it is determined that the transaction will be completed in the terminal currency, a second type of authentication request message is generated, wherein the second type of authentication request message includes a terminal currency indicator, the transaction amount, and cryptography; and transmitting the generated authentication request message to a remote location to complete the transaction.

[0008] Such examples provide configurations that can effectively offer currency conversion for transactions completed using contactless payment carriers. [Brief explanation of the drawing]

[0009] List of figures Hereinafter, the exemplary implementations of the present disclosure are described with reference to the accompanying drawings, where similar parts throughout are referred to by the same reference numerals. [Figure 1] This is a flowchart illustrating an example transaction processing using a contactless payment carrier. [Figure 2] This figure shows an exemplary method for operating a contactless payment terminal device that displays currency conversion. [Figure 3A] This is an illustrative flowchart of a transaction processing using a contactless payment carrier that involves currency conversion. [Figure 3B] This is an illustrative flowchart of a transaction processing using a contactless payment carrier that involves currency conversion. [Figure 4] This figure shows an abstract payment system equipped with a payment terminal device. [Figure 5] This figure shows another exemplary payment system equipped with a payment terminal device. [Modes for carrying out the invention]

[0010] Examples of the present disclosure are provided below for illustrative purposes only, but those skilled in the art will understand that the teachings provided with respect to one or more examples are equally applicable to any other possible examples, insofar as they are technically feasible.

[0011] Figure 1 shows a flowchart of a transaction using a contactless payment carrier, extracted from Figure 2-1 of [1] (some formatting may have been slightly adjusted). This flowchart is discussed in sections 2.3, 2.4, and 2.5 of the same document. This flowchart is for executing a transaction that may be a purchase transaction, cash withdrawal, or refund. In most purchase transactions, it is assumed that only the relevant steps from S101-S111 for the reader and S151-S154 for the EMV card will be executed. In some cases, for example, when updating information on the card, steps S113-S115 (for the reader) and S155-S157 (for the card) may also need to be executed to complete such an update. These steps require the contactless card to be presented to the reader again, i.e., a second presentation, in order to complete the process. Typically, in contactless transactions, the contactless card is presented to the reader once, and the second presentation for card update is optional.

[0012] According to this flow, for example, if a customer wishes to purchase goods or services using a contactless card from another country (for the currency and / or country of the POS) at a Point-of-Sale (POS) facility, under the current configuration, the customer must present the card to the reader, which automatically generates an encryption and an authentication message that is sent to a remote system (for the POS) in the "Online Processing" step S110. By default, the system is not designed to handle currency conversion when using contactless cards from other countries in this manner.

[0013] In some exemplary implementations, the current configuration can be modified or used to handle currency conversion. In such examples, if currency conversion eligibility is detected and currency conversion is selected (e.g., after receiving input from the customer and / or POS operator), the first encryption in the domestic currency in which the card was initially presented may be canceled. A new, separate transaction is then initiated using the same Application ID (AID) previously selected, but in a foreign currency and with the conversion amount selected by the customer in that foreign currency. However, since this is a new, separate transaction, the customer must present the contactless card again to complete this second transaction. Examples of Application IDs include A0000000041010=MasterCard Credit, A0000000031010=VISA Credit, and A000000025010801=Amex. Note that a card may have multiple Application IDs. In this case, if the terminal accepts both Application IDs, the card may prioritize one Application ID, and / or the terminal may allow the customer to choose.

[0014] Therefore, it is possible to provide a system that offers currency conversion services using the current contactless procedure. However, in practice, such a configuration would require either presenting the contactless card to the reader twice or keeping the contactless card on the reader for the entire duration of the transaction in another currency. Thus, it may be desirable to provide a configuration in which the flow and terminal for contactless transactions that offer currency conversion are simplified. It should be noted that this issue is clearly specific to contactless situations and is not an issue in other cases, because in all other cases, the contact card is inserted into the reader and remains there until the transaction is completed. In contrast, in the case of contactless transactions, the contact between the card and the contactless reader is brief, before it is determined whether the transaction is eligible for currency conversion and before currency conversion becomes available. Also, since input is generally required (so that the user / cardholder can consider the exchange rate and / or conversion amount and make a decision accordingly) in order to decide whether to use currency conversion, it is not usually expected that the cardholder will maintain contact between the card and the reader for the duration of the transaction. In particular, it cannot be expected that the cardholder will maintain contact between the card and the reader while the cardholder, merchant staff, or any other relevant user reviews and decides on the currency conversion information and then enters any necessary currency conversion selections into the contactless reader itself.

[0015] Figure 2 illustrates an exemplary method of operating a payment terminal device for contactless payments that presents currency conversion. This method facilitates the completion of contactless transactions involving currency conversion from a transaction amount in the terminal currency to a converted amount in another country's currency (relative to the terminal currency). When the method is initiated, in S201, payment data (e.g., card data) from the contactless payment carrier to complete the transaction is received from the contactless payment carrier reader, and the payment data includes encryption. The encryption is generated using the transaction amount in the terminal currency and the terminal currency as the transaction currency. Furthermore, the payment data may include one or any combination of the following: card number, account number, payment token, application data (see, e.g., [1]), currency code, country code, one or more applications or services supported by the card / payment carrier, one or more transaction amount thresholds, etc.

[0016] In particular, the received payment data regarding encryption is then stored in the terminal system (S202). At this stage, the contactless card can be removed from the card reader.

[0017] Next, instead of generating and immediately sending an authentication message containing encryption as in conventional systems, the method proceeds to step S203, which determines whether the transaction will be completed in foreign currency or terminal currency. For example, it may be determined that the transaction is eligible for currency conversion, and if so, a currency conversion service may be offered to the customer and / or POS operator. Once the currency conversion offer is accepted, the currency conversion may be detected. In other examples, automatic selection of currency conversion may be performed based on one or more of the following: the card's currency and / or country, currency conversion parameters set on the card, currency conversion parameters set on the terminal, etc. In yet another example, manual selection may be required for all transactions at the terminal (e.g., an in-store terminal configured to handle transactions with foreign cards). In some cases, it may be determined that the payment carrier is a card from the same country as the terminal, in which case the transaction will be completed in the domestic currency. Regardless of the specific currency conversion detection and / or detection technique, in S203, the terminal may determine whether the transaction will be executed in the converted transaction amount in foreign currency or the original transaction amount in terminal currency.

[0018] If it is determined that the transaction will be completed in a foreign currency, a first type of authentication request message is generated. The first type of authentication request message includes a foreign currency indicator that identifies the foreign currency, the converted transaction amount in the foreign currency, a terminal currency indicator that identifies the terminal currency, the transaction amount, and a cryptographic code (S204). The cryptographic code is the same one generated in S201.

[0019] In some cases, the terminal may have the exchange rate and / or the conversion amount in advance (for example, if one or both are provided to assist in the selection of currency conversion), while in other cases, one or both may be obtained after the currency conversion is selected. Also, a suitable exchange rate may be determined in any appropriate manner. For example, the exchange rate and / or the conversion amount can be obtained from a local rate table in the terminal or any other POS device (such as a cash register) to which the terminal is connected. In other examples, the exchange rate and / or the conversion amount can be obtained from a remote system such as a currency conversion system, an exchange rate system, etc. As those skilled in the art will understand, these rates can be real-time rates or rates that are updated periodically (for example, daily, twice a day, hourly, etc.). Also, the terminal can, in some cases, receive a pre-converted amount, while in other cases, it can obtain the exchange rate locally or remotely and calculate the conversion amount based on the obtained exchange rate to obtain the conversion amount.

[0020] In any case, when the use of currency conversion to complete a transaction is detected, a first type of authentication request message can be generated including a currency indicator that identifies the foreign currency and the converted transaction amount. As discussed above, the converted transaction amount corresponds to the transaction amount converted into the foreign currency. For example, a part of the generated authentication message can be the same as a second type of authentication request message for completing the transaction in the terminal currency, such as a cipher, while on the other hand, additional information is also included.

[0021] Next, in S206, the generated authentication request message is sent to a remote location and the transaction is completed. The remote location can be any of an acquirer, a bank, a currency conversion system (for example, dedicated to settling transactions in foreign currency), or any transaction settlement element (for example, related to a direct transaction between two parties not involving a conventional banking system).

[0022] On the other hand, if it is determined in S203 that the transaction will be completed in the terminal currency, the method proceeds to S205 where a second type of authentication request message is generated. The second type of authentication request message includes a terminal currency indicator, a transaction amount, and a cipher. For example, the second type of authentication request message can be a conventional authentication request message for completing a transaction (e.g., an online transaction without currency conversion). Therefore, the second type of authentication request message may not include a foreign currency indicator or a conversion amount as used in the first type of authentication request message.

[0023] In other words, by retaining the first type of authentication request message that identifies a foreign currency as the currency for settling a transaction and by retaining the second type of authentication request message that identifies the terminal (franchise) currency as the currency for settling a transaction (as well as the original franchise currency for the transaction), the method shown in FIG. 2 enables the execution of a contactless - like transaction using a single "tap" of a contactless card / payment carrier by avoiding the generation and transmission of an authentication request message immediately after the cipher is generated and communicated to the terminal. Thus, this simplifies the payment authentication process in a secure manner without the need for generating a second cipher that would require a second "tap" of the contactless card.

[0024] FIGS. 3A - 3B collectively show exemplary flowcharts of online transaction processing using contactless payment and currency conversion. In particular, this figure mainly shows the flow from the perspective of the control device of the terminal system, and the control device actually provides payment functionality or a payment application.

[0025] The teachings of this disclosure are not limited to the use of contactless payments as described in [1], but since [1] substantially specifies the specifications for most contactless EMV payments, Figure 3 (Figures 3A and 3B combined) is provided to illustrate an example of how [1] can be modified to provide a currency conversion service to contactless transactions without requiring a second presentation of the contactless payment instrument. Those skilled in the art will understand that this disclosure is not limited to this example, and the teachings provided in this example apply equally to other examples.

[0026] According to this exemplary implementation, the terminal system can process transactions using contactless payment methods, in which case currency conversion eligibility and processing are achieved by presenting the card to the reader only once (referred to earlier as a single "tap").

[0027] Steps 1 through 4 may be standard EMV processing steps, such as those described and defined in [1], and should therefore not be described in detail in this document. The processing flow shown in Figure 3 may vary depending on the EMV kernel used. However, the teaching for presenting the currency conversion remains the same, and the same or similar currency conversion steps can be performed using, for example, different kernels.

[0028] Returning to the various steps shown in Figure 3, as soon as the contactless card is presented to the reader after step 2, the payment transaction begins. The payment application requests relevant card data from the contactless card through the EMV kernel to perform online authentication. When requesting card data from the contactless card, the payment application can use, for example, the transaction amount as the Authorized Amount (tag "9F02") and the terminal currency code as the Transaction Currency Code (tag "5F2A").

[0029] The card and EMV kernel can then perform standard EMV processing and other appropriate risk management checks, for example, to select the appropriate application (step 3), initiate application processing (step 4), and read application data (step 5). In particular, in step 5, "Read Application Data," the card will also read the application currency code (tag 9F42) and issuer country code (tag 5F28) from the card if they have not already been read in "Initiate Application Processing" (step 4). After these steps, the EMV kernel will request online authentication encryption from the card to complete or authenticate the transaction.

[0030] In step 6, the card, for example, performs card risk management and decides either to reject the transaction and go offline or to provide the EMV kernel with data related to the online authentication request, in which case the related data particularly includes the authorization request cryptogram (ARQC). If the card rejects the transaction and goes offline without returning the ARQC, the process can proceed to step 17, at which point the transaction will be rejected and terminated.

[0031] On the other hand, if an ARQC is returned, the method proceeds to step 7, where the EMV kernel holds all the necessary EMV data and provides it to the payment application for constructing the authentication request message. The payment application will generate the authentication request message based on the card / payment data received from the contactless card. However, in some other embodiments, the card itself generates the authentication request message. In this case, the authentication request message is sent directly to the cardholder's issuing bank, but further communication from the issuing bank to the merchant terminal must go through a channel trusted by the merchant, such as its acquirer.

[0032] Although steps 6 and 7 are expressed as being performed while the card is still in a contactless connection with the reader, it should be noted that those skilled in the art will understand that all or part of steps 6 and 7 may be performed after the card is no longer connected to the reader. Since the authentication message is usually generated when the encryption is obtained and conventionally sent immediately to complete the transaction, it will be understood that the generation of the authentication message must be quickly intercepted or stopped before the authentication message is sent and completed. Consequently, in practice this is likely to occur while the card is still near the reader. However, it is clear that this is not a requirement for the card to be near the reader in order to perform steps 6 and 7 or similar steps.

[0033] The technique described herein eliminates the need to keep the contactless card near the reader. This makes it possible to facilitate the use of contactless cards in a way that cardholders expect, while maintaining compatibility with existing system technologies (and potentially future contactless payment system technologies), in which case the transaction can be completed by simply placing the card near the reader once. In particular, steps 7-16 provide processing similar to authentication retention in online transactions, but without requiring an AAC (Application Authentication Cryptogram). More specifically, from step 7 onward, the payment application can complete the EMV processing, the cardholder can remove the card from the reader, and the payment application temporarily stores the authentication data received from the EMV kernel for later use without completing the transaction. In both online and offline modes, once the card is removed from the reader (which, as previously discussed, requires a "double-tap" configuration to support currency conversion), the authentication request message becomes final and confirmed. However, if currency conversion is selected and appropriate, the generation of this normally used authentication request message is delayed, thereby reducing the need for the cardholder to present the card to the contactless reader again.

[0034] Returning to the example in Figure 3, in step 8, the payment application will determine whether the transaction amount is greater than the Cardholder Verification Method (CVM) limit. While this step may not always be performed, it is expected to be a common check / determination in practice, considering, for example, [2] and [3]. Note that the CVM limit can be set according to country standards.

[0035] If, in step 8, the transaction amount is determined to be below the CVM limit, the transaction is not eligible for currency conversion, and the execution of CVM is not required. As a result, the transaction can proceed to step 13, where online transaction processing (for online transactions) can be performed without currency conversion. A payment application can construct an authentication request message, for example, according to the following rules (e.g., using message types from ISO 8583), and these rules can also be used for any contactless payment transaction that does not involve currency conversion.

number

[0036] • For ISO 8583-2003, update DE04 Transaction Amount - Currency code, transaction amount = Terminal currency (same as DE55 tag "5F2A") - Currency minor unit, transaction amount = Terminal currency minor unit -Value, transaction amount = transaction amount (same as DE55 tag "9F02") • In the case of ISO 8583-1987 / 1993 -DE49 Currency Code, Transaction = Terminal Currency (Same as DE55 tag "5F2A") -DE04 Amount, Transaction = Transaction amount (DE55 Same as tag "9F02") Regardless of the version of ISO 8583, DE55 (EMV data) shall have the following characteristics: -DE55 Tag "9F02" Amount, Authorized = Transaction amount in terminal currency -DE55 Tag "5F2A", Transaction currency code = Terminal currency code - EMV chip data for authentication messages normally sent via DE55

[0037] Naturally, those skilled in the art will understand that the use of ISO 8583 is only one option. Any suitable type of financial message, such as APACS or AS 2805, can be used. As part of this step, the payment can send an authentication request message online, and once submitted, the process can proceed to step 16, where it can receive an authentication response message from the acquirer.

[0038] If in step 8 the transaction amount is determined to be greater than the CVM limit, the process proceeds to step 9 for Dynamic Currency Conversion (DCC) eligibility detection. From one perspective, step 8 can also be viewed as part of DCC eligibility detection, in which case step 8 is based on whether the transaction meets one or more criteria related to DCC eligibility, and step 9 is based on whether the contactless card meets one or more criteria related to DCC eligibility. In this case, the eligibility check in step 9 is based on the following criteria for EMV cards (which can be used for eligibility detection of both contact and contactless cards), using tags 9F42 (ACC) and 5F28 (ICC) acquired in step 5 and stored by the payment application in step 7.

number

[0039] Pseudocode: DCC Eligible The following (i) ACC (Tag 9F42) <> Terminal currency code; or (ii) ACC (tag 9F42) is unavailable, but ICC (tag 5F28) <> terminal country code; and if (iii) ACC (Tag 9F42) is a supported currency for DCC, or (iv) ACC (tag 9F42) is unavailable, but ICC (tag 5F28) is a supported traveler country for DCC;

[0040] Other DCC eligibility checks can be performed, but the above example is assumed to be the most widely used. Furthermore, depending on the actual implementation, conditions (iii) and (iv) may, in some cases, be performed remotely rather than by the payment application. If the DCC eligibility check response is unsuccessful, the method proceeds to step 12, which involves cardholder verification, which is generally assumed to be performed for transactions exceeding the CVM limit. If the cardholder verification is successful, an appropriate authentication request message is generated in step 13. Note that the cardholder verification in steps 12 and 14 may potentially occur after step 16, after authentication is complete, if the cardholder verification method is signature-based.

[0041] If the DCC eligibility check is successful, the method then proceeds to step 10, where the payment application constructs a rate request message and forwards this rate request to obtain the rate for the foreign currency and / or country identified in step 9. In other examples, the terminal may be configured to access a local table, database, or similar means for retrieving currency conversion rates for the foreign currency and / or country, rather than a remote host or location. Also, if the foreign currency and / or country identified in step 9 can be associated with two or more possible currencies, multiple rates may be obtained. For example, a card may be associated with a first currency as the account currency for this card, but may also be associated with a country where a second currency is the official currency, or the card may be a multi-currency card. Preferably, in the currency conversion process, the first currency is used as preferred because it is associated with the card, and the second currency is not used. However, depending on the circumstances, rates may be obtained for the first and second currencies, and the cardholder may be offered currency conversion in both currencies, or multiple rates may be obtained for a multi-currency card, and the cardholder may be offered currency conversion in the identified supported currencies. The cardholder may then decide to reject the offered currency conversion or to accept the currency conversion in one of the two or more currencies offered.

[0042] Returning to step 10, the payment application retrieves exchange rate information to determine the converted amount of the transaction from the terminal currency to another currency. Note that the exchange rate information may include one or more of the following: the exchange rate from the terminal currency to the other currency, the exchange rate from the other currency to the terminal currency, the converted amount (if determined remotely, for example), and markup information. Accordingly, regardless of the converted amount determined in another element of the terminal system or remotely (for the payment terminal or point-of-sale terminal), the payment application can then indicate to the cardholder that the transaction will be completed in another currency by providing the converted amount and, optionally, the effective exchange rate from the transaction amount to the converted amount (which may differ from the retrieved exchange rate if, for example, a markup rate and / or fees are added). In other words, the cardholder is asked whether they prefer to use currency conversion or complete the transaction in the terminal currency (step 11).

[0043] If the cardholder decides not to accept the currency conversion offer, the process proceeds to step 12, where appropriate cardholder verification is performed. From step 12, if the cardholder verification is successful, the process moves to step 13, where the payment application proceeds to construct an authentication request message as considered in the considerations for step 13 above, and submits the message to the acquirer for processing. The payment application then proceeds to step 16, where it can receive an authentication response message from the acquirer.

[0044] On the other hand, if the cardholder decides in step 11 to accept the presentation of the DCC, the process proceeds to step 14 to perform appropriate cardholder verification.

[0045] Once cardholder verification is complete, the process proceeds to step 15, where the payment application constructs an authentication request message to support currency conversion, for example, according to the following rules. The underlined fields below are those that will have different values ​​compared to their corresponding fields in an authentication request message that does not perform currency conversion (see consideration in step 13 above). Note that "home" currency here refers to the "foreign" currency discussed above. In practice, the home currency is the foreign currency when the home currency (for the card) is different from the terminal currency (sometimes called "local" or "merchant"). In other cases, the home currency and terminal currency may be the same. Returning to the above case where the home currency is the foreign currency and the cardholder accepts the currency conversion offer, the payment application can generate an authentication request message based on the following rules, using the ISO 8583 message type as an example:

number

[0046] • For ISO8583-2003, update DE04 Transaction amount -Currency code, transaction amount = selected local currency (may be the value in EMV tag "9F42") -Currency subunit, transaction amount = selected local currency subunit -Value, Transaction amount = Transaction amount converted in local currency • In the case of ISO 8583-1987 / 1993 -DE49 currency code, transaction = selected local currency (may be the value in EMV tag "9F42") -DE04 Amount, Transaction = Transaction amount converted in local currency Regardless of the version of ISO 8583, DE55 (EMV data) shall have the following characteristics: -DE55 Tag "9F02" Amount, Verified = Original amount in terminal currency -DE55 Tag "5F2A", Transaction currency code = Terminal currency code - EMV chip data for authentication messages normally sent via DE55

[0047] Here again, those skilled in the art will understand that ISO 8583 is just one of several possible types of financial messages that can be used. In particular, the same encryption (which is already part of the EMV chip data that has been received and stored) is included in this message and in the message that is sent without currency conversion. The payment application can then send an authentication request message to the acquirer for processing and then await an authentication response message from the acquirer (step 16).

[0048] More specifically, in step 16, the online authentication response to the payment application indicates whether the transaction is approved or rejected. The payment application can then display an appropriate message indicating whether the transaction was approved or rejected. For example, if the transaction is approved and the cardholder verification method is signature, the payment application can print out a receipt or display a signature panel for signing, so that it can also perform a CVM and simultaneously complete the CVM step (step 14).

[0049] The above has provided examples of terminal systems that can display currency conversions for transactions settled using contactless EMV cards, particularly online transactions.

[0050] Figure 4 shows an exemplary payment system comprising a payment terminal device. This payment system includes a terminal device 200 that can be used with one or more contactless payment carriers 300 connected to a remote payment system 400 and a point-of-sale (POS) system 100.

[0051] The contactless payment carrier 300 may be any suitable contactless payment carrier, such as a contactless card 310 (either an EMV, debit card, and / or credit card), a mobile phone 320 (e.g., having a payment application 321), a token payment system 330, or an EMV device 340 (e.g., of any form factor). It should be noted that the above is not exhaustive and is merely illustrative. For example, the mobile phone 320 may be configured to make payments using tokenization, which sends a token to complete the payment rather than an account number or card number. In other words, the mobile phone 320 and / or the mobile application 321 may be configured to operate as a token payment system (e.g., a token payment device) 330.

[0052] A remote payment system is a system located at a remote location (from the terminal's perspective) that is configured to settle transactions. For example, a remote payment system may connect to an acquirer (the merchant's bank or financial institution), another bank or financial institution, or any other transaction settlement element or system. For example, a terminal may connect to a payment system that uses blockchain or blockchain-like technology to settle transactions directly to the cardholder, to a financial institution, or to any other financial system. It should be understood that a remote payment system may include a DCC rate server that determines or adjusts the exchange rates of the currencies used.

[0053] In the example in Figure 4, the terminal device 200 is connected to a separate POS system 100, but from a certain perspective, the terminal device 200 can be considered part of the POS system 100, since the two elements work together to present and settle transactions. The terminal device 200 includes a contactless reader 210 configured to read data and transmit that data to a contactless payment carrier 300. For example, the contactless reader 210 may transmit a request for a data card and / or crypto, transaction amount, and / or terminal currency to the payment carrier, and may also receive card / payment data, such as crypto for completing the transaction, from the payment carrier. As those skilled in the art will recognize, although the contactless reader 210 is called a “reader”, this is not limited to a reader that can actually transmit signals to a contactless payment means and therefore has only a contactless receiver and does not have a contactless transmitter.

[0054] The terminal device 200 also includes a control unit 220 configured to control the terminal device in accordance with the techniques discussed herein, a processor 240 for executing instructions received from the control unit 220, and a memory 250 operable to store card / payment data received from a contactless payment carrier 300 for use, for example, generating first or second type authentication request messages. Furthermore, the terminal includes a communication module 230 operable to send and / or receive messages to and from a remote payment system 400 located at least a remote location.

[0055] A POS system may, in some cases, be considered to include a whole POS system comprising, for example, one or more POS terminals and one or more POS servers connected to the POS terminals and used for accounting purposes, data backup, communication with acquirers, etc.

[0056] As already mentioned, the payment system in Figure 4 is an illustrative example, and in other cases the system may have more, fewer, or different elements, these elements may be distributed in various ways, and / or communication between different elements may follow different paths. For example, the control device 220 of the terminal device 200 may be configured to cause the POS system 100 to send an authentication request message to the remote payment system 400, thereby transmitting this message via the POS system to a remote location for the remote payment system.

[0057] Figure 5 shows another exemplary payment system comprising a payment terminal device. This payment system is similar to the one discussed above in relation to Figure 4, so the discussion of the system elements will not be repeated. However, in this second exemplary example, the terminal device 200 is part of a POS system and has access to, for example, the communication module 130 of the POS system. Also, the control unit 220 of the terminal device 200 is at least partially shared with one or more control units of the POS system 100. For example, the POS system may include a cash register device for receiving contactless payments, which is physically connected to the terminal device, and these two devices can be considered as a single logical entity having contactless and currency conversion functions. Also, the memory 250 and / or processor 240 may, in practice, be shared with the corresponding resources of the point-of-sale system 100, where appropriate.

[0058] While this disclosure is primarily applicable to online transactions in point-of-sale (POV) transactions, please note that it can also be used for other transactions that face the same limitation of requiring two card contacts when using currency conversion.

[0059] With respect to contactless payment carriers, as has already been discussed, the techniques discussed herein are primarily developed with contactless card transactions in mind. However, as those skilled in the art will understand, these techniques may be configured to be used in conjunction with other types of contactless payment means, such as mobile payment applications, tokenization means, and so on.

[0060] Furthermore, while the above description considers the generation of a first or second type of authentication request message once the eligibility and selection of currency conversion is determined, those skilled in the art will understand that this may be done in different ways, all of which are within the scope of this disclosure. For example, in some cases, a terminal device may generate a temporary message using the transaction amount in the terminal currency, a terminal currency identifier, and a cryptographic code before or during the determination of DCC eligibility and / or selection. If DCC is applicable and selected, the preparatory message can then be modified to generate a first type of preparatory message (with DCC applied). On the other hand, if DCC is not applicable and not selected, the preparatory message may be used as a second type of authentication message (if it is already in an appropriate format and contains relevant information), or the preparatory message may be modified to generate a second type of authentication request message. In other words, a terminal device may be configured to generate a preparatory authentication request message and to generate a first or second type of authentication request message based on the preparatory authentication request message.

[0061] In some cases, the CVM limit can be used to determine DCC eligibility, requiring a transaction to have a transaction value equal to or greater than the CVM limit in order to offer DCC (transactions with a transaction value less than the CVM limit will not be offered DCC). In other cases, no check against the CVM limit may be performed as part of the DCC eligibility detection.

[0062] Furthermore, terminal currency can sometimes be called domestic currency or merchant currency because it is assumed that terminal currency is the currency used in the country of the terminal device or by the merchant. Also, as already mentioned, foreign currency is foreign to the terminal currency, but it is sometimes called "domestic" currency because it is assumed to be the currency of the cardholder, i.e., the person whose contactless payment carrier is this card.

[0063] References [1] "EMV (Registered Trademark) Contactless Specifications for Payment Systems," Book C-3, Kernel Specification, Version 2.6, EMVCo, February 2016. [2] Visa TADG v3 (May 15, 2015), H.1.3, 237 pages [3] MasterCard Transaction Processing Rules (January 21, 2016), page 79

Claims

1. A contactless payment or cash withdrawal device that provides currency conversion from terminal currency to another country's currency, wherein the device is associated with the terminal currency, and the device is A contactless payment carrier reader configured to communicate with a contactless payment carrier, A communication module configured to communicate messages with a remote location, The contactless payment carrier reader receives payment data from the contactless payment carrier to complete the transaction, the payment data includes encryption, and the transaction is associated with the transaction amount in the terminal currency. The received payment data, including the aforementioned encryption, is stored. Determine whether the transaction will be completed in the foreign currency or the terminal currency, and if the foreign currency is a different currency from the terminal currency, If it is determined that the transaction will be completed in the foreign currency, a first type of authentication request message is generated, the first type of authentication request message includes a foreign currency indicator that identifies the foreign currency, a converted transaction amount corresponding to the transaction amount converted into the foreign currency, a terminal currency indicator that identifies the terminal currency, the transaction amount, and the cryptographic code. If it is determined that the transaction will be completed in the terminal currency, a second type of authentication request message is generated, the second type of authentication request message includes the terminal currency indicator, the transaction amount, and the cryptographic code. The generated authentication request message is transmitted to the remote location via the communication module to complete the transaction. At least the terminal currency and the transaction amount in the terminal currency are used as parameters for generating the encryption. An apparatus comprising a control device configured in such a manner.

2. The control device is configured to determine whether the transaction will be completed in the foreign currency or the terminal currency, If the aforementioned transaction is determined to be eligible for currency conversion services, The system receives a user selection indicating whether the use of the aforementioned currency conversion service has been selected. The apparatus according to claim 1, which is configured to determine that the transaction will be completed in the foreign currency upon receiving a user selection indicating that the use of the currency conversion service has been selected.

3. The control device is configured to determine whether the transaction is eligible for the currency conversion service, The apparatus according to claim 2, comprising being configured to detect, based on the payment data, that the contactless payment carrier is associated with a currency different from the terminal currency, and / or that the contactless payment carrier is associated with a country different from the country associated with the apparatus.

4. The control device is configured to determine whether the transaction is eligible for the currency conversion service, The apparatus according to claim 2 or 3, further comprising a configuration that determines when the transaction amount exceeds a predetermined threshold.

5. The control device is configured to generate a preparatory authentication request message including the terminal currency indicator, the transaction amount, and the cryptographic code. The control device being configured to generate the first type of authentication request message includes being configured to modify the preparatory authentication request message to include the foreign currency indicator and the converted transaction amount, The apparatus according to any one of claims 1 to 4, wherein if it is determined that the transaction will be completed in the terminal currency, the control device is configured to use the preparatory authentication request message as the second type of authentication request message.

6. The apparatus according to any one of claims 1 to 5, wherein the control device is configured to request the payment data from the contactless payment carrier for completing the transaction.

7. The apparatus according to claim 6, wherein the control device is configured to request the payment data from the contactless payment carrier, and the control device is configured to transmit a request to the contactless payment carrier, the request including the transaction amount and the terminal currency.

8. The apparatus according to any one of claims 1 to 7, wherein the contactless payment carrier is one of a contactless credit card, contactless debit card, contactless card, contactless EMV card, contactless chip card, EMV device, mobile phone, mobile application, and token payment system.

9. A method for operating a contactless payment or cash withdrawal device that provides currency conversion from a terminal currency to another country's currency, wherein the device is associated with the terminal currency, and the method Receiving payment data from a contactless payment carrier to complete a transaction, wherein the payment data includes encryption and the transaction is associated with a transaction amount in the terminal currency; The steps include storing the received payment data including the encryption, A step of determining whether the transaction will be completed in the foreign currency or the terminal currency, wherein the foreign currency is a different currency from the terminal currency, If it is determined that the transaction will be completed in the foreign currency, a first type of authentication request message is generated, the first type of authentication request message includes a foreign currency indicator that identifies the foreign currency, a converted transaction amount corresponding to the transaction amount converted into the foreign currency, a terminal currency indicator that identifies the terminal currency, the transaction amount, and the cryptographic code. If it is determined that the transaction will be completed in the foreign currency, the process involves generating a second type of authentication request message, and determining that the second type of authentication request message includes the terminal currency indicator, the transaction amount, and the cryptographic code. The steps include: sending the generated authentication request message to a remote location to complete the transaction; At least the terminal currency and the transaction amount in the terminal currency are used as parameters for generating the encryption. method.

10. The step of determining whether the transaction will be completed in another country's currency or the terminal currency is: Determining whether the aforementioned transaction is eligible for currency conversion services, Receiving a user selection indicating whether the use of the aforementioned currency conversion service has been selected, The method according to claim 9, comprising: receiving a user selection that the use of the currency conversion service has been selected, determining that the transaction will be completed in the foreign currency.

11. The step of determining whether the transaction is eligible for the currency conversion service is: The method according to claim 10, comprising detecting, based on the payment data, that the contactless payment carrier is associated with a currency different from the terminal currency, and / or that the contactless payment carrier is associated with a country different from the country associated with the device.

12. The method according to claim 10 or 11, wherein the step of determining whether the transaction is eligible for a currency conversion service includes determining whether the transaction amount exceeds a predetermined threshold.

13. The process further includes the step of generating a preparatory authentication request message including the terminal currency indicator, the transaction amount, and the cryptographic code, The step of generating the first type of authentication request message includes modifying the preparatory authentication request message to include the foreign currency indicator and the converted transaction amount, The method according to any one of claims 9 to 12, wherein generating the second type of authentication request message when it is determined that the transaction will be completed in the terminal currency includes using the preparatory authentication request message as the second type of authentication request message.

14. The method according to any one of claims 9 to 13, comprising the step of requesting payment data from the contactless payment carrier in order to complete the transaction.

15. The method of claim 14, wherein the step of requesting the payment data from the contactless payment carrier includes transmitting a request to the contactless payment carrier, wherein the request includes the transaction amount and the terminal currency.

16. The method according to any one of claims 9 to 15, wherein the contactless payment carrier is one of a contactless credit card, contactless debit card, contactless card, contactless EMV card, contactless chip card, EMV device, mobile phone, mobile application, and token payment system.

Images