Rule · CBRT · 13 May 2024
All payment service providers offering FAST service via mobile application must have infrastructure ready by 30.04.2024, or within 4 months of going live, to accept person-to-person QR payments and read long and short merchant QR codes; those offering merchants card or FAST acceptance have 6 months for dynamic-verification merchant payments. Acquirer participants must verify QR codes and reject failed payments; the QR Code Flow Type field (30/02) determines fees. Participants must complete TCMB test scenarios.
May 2024
Version 1.4
CENTRAL BANK OF THE REPUBLIC OF TÜRKİYE
CONFIDENTIAL
1. Introduction ............................................................................................................................6
2. Scope and Basis .................................................................................................6
3. Definitions and Abbreviations................................................................................................6
4. General Principles ..............................................................................................................7
5. QR Code Usage Models for the FAST System.....................................................9
5.1. Merchant Payments (Sales)...................................................................................................................................................9
5.1.1. FAST Merchant Payment with Dynamic Verification Service Obtained from a FAST System Participant............................. 9
5.1.2. FAST Merchant Payment with Static Verification Service Obtained from a FAST System Participant ................................12
5.2. Merchant Payments (Refunds) .................................................................................................................................................14
5.2.1. Long QR Code Refund Flow Provided by the Merchant ...................................................................................................14
5.2.2. Short QR Code Refund Flow Provided by the Merchant......................................................................................................15
5.3. Person-to-Person Payments ..............................................................................................................................................16
6. FAST-TR QR Code Specifications ...............................................................................17
6.1. QR Code Data Organization and Naming Rules.....................................................................................17
6.1.1. Long QR Code Structure Provided by the Merchant...........................................................................................................18
6.1.2. Short QR Code Structure Provided by the Merchant .............................................................................................................28
6.1.3. Person-to-Person Payment QR Code Structure ..............................................................................................................................29
7. Sample QR Code Verification Scenarios...............................................................32
7.1. QR Code Payment Scenario Resulting in Positive Verification .......................................................32
7.2. QR Code Payment Scenario with Incorrectly Entered QR Code Flow Type ....................................................33
7.3. QR Code Payment Scenario with Incorrectly Entered Recipient Information.................................................................34
8. References..............................................................................................................36
| Date | Version Number | Note |
|---|---|---|
| 2 July 2020 | Draft Version 1.0 | First Version. |
| 07 September 2020 | Draft Version 2.0 | Data structures and transition provisions have been arranged. |
| 29 December 2020 | 1.0 | Merchant payment flows and transition provisions have been revised. |
| 28 May 2021 | 1.1 | Transition provisions have been revised. Merchant payment (refund) flows have been added. Template no. 31 has been added to the long QR code data structure provided by the merchant, and the QR Code Flow Type and Payment Purpose fields have been updated. Some spelling errors have been corrected. |
| 25 October 2021 | 1.2 | Transition provisions have been revised, postponing the final dates for the generation and reading of the Person-to-Person QR Code and the reading of the QR Code Provided by the Merchant to 31.12.2021, and it has been decided that the final date for the generation of the QR Code Provided by the Merchant shall be the same as the date determined in the Regulation. |
| 11 September 2023 | 1.3 | The transition provisions section has been updated. The merchant definition has been deleted and various updates have been made within this scope. Incorrect CRC values have been corrected. |
| 13 May 2024 | 1.4 | The title and content of the transition provisions section have been updated. |
Based on 2020 data, if the first 15 banks that performed the most payments by number in the Account Payment transaction type in CBRT Payment Systems become FAST System participants, within the scope of compliance with the rules contained in this document;
1. By no later than 31.12.2021, to have the infrastructure ready for generating the QR code presented in person-to-person payments to accept FAST payments and for reading the QR code to initiate FAST payments,
2. By 31.12.2021, to have the infrastructure ready to provide the ability to read the long and short QR codes provided by the merchant to initiate FAST payments,
3. Within the scope of Article 1, paragraph 2 of the Provisional Article of the Regulation, to have the infrastructure ready by the date determined in Article 1, paragraph 2 of the Provisional Article of the Regulation that enables accepting FAST payments by generating a long or short QR code for a FAST merchant payment where a dynamic verification service is obtained from a FAST System participant at the merchants they have agreements with
is mandatory.
Based on 2020 data, other FAST System participants other than the first 15 banks that performed the most payments by number in the Account Payment transaction type in CBRT Payment Systems, within the scope of compliance with the rules contained in this document;
1. All payment service providers that began message exchange as a FAST System participant before 01 January 2024,
a. All payment service providers offering FAST service to their users via a mobile application must have the infrastructure ready by 30.04.2024 to accept FAST payments by generating the QR code presented in person-to-person payments and to initiate FAST payments by reading the long and short QR codes presented by the merchant in person-to-person QR code transactions,
b. Payment service providers offering merchants the option to accept payments via payment cards or the FAST System must have the infrastructure ready by 30.04.2024 to initiate FAST payments by generating a long or short QR code for FAST merchant payments where dynamic verification service is obtained from a FAST System participant at their contracted merchants,
2. All payment service providers that began message exchange as a FAST System participant on or after 01 January 2024,
a. All payment service providers offering FAST service to their users via a mobile application must have the infrastructure ready within a maximum of 4 months from the date they go live in the FAST System to accept FAST payments by generating the QR code presented in person-to-person payments and to initiate FAST payments by reading the long and short QR codes presented by the merchant in person-to-person QR code transactions,
b. Payment service providers offering merchants the option to accept payments via payment cards or the FAST System must have the infrastructure ready within a maximum of 6 months from the date they go live in the FAST System to initiate FAST payments by generating a long or short QR code for FAST merchant payments where dynamic verification service is obtained from a FAST System participant at their contracted merchants
is mandatory.
Payment service providers that begin message exchange as a FAST System participant,
a. All payment service providers that do not yet offer FAST service to their users via a mobile application but will start offering it from a certain date must have the infrastructure ready within a maximum of 4 months from the date they start offering this service to accept FAST payments by generating the QR code presented in person-to-person payments and to initiate FAST payments by reading the long and short QR codes presented by the merchant in person-to-person QR code transactions,
b. Payment service providers that do not yet offer merchants the option to accept payments via payment cards or the FAST System but will start offering it from a certain date must have the infrastructure ready within a maximum of 6 months from the date they start offering this service to initiate FAST payments by generating a long or short QR code for FAST merchant payments where dynamic verification service is obtained from a FAST System participant at their contracted merchants
is mandatory.
The CBRT is authorized to change these periods.
[1] Garanti Bankası, Ziraat Bankası, Yapı ve Kredi Bankası, İş Bankası, Akbank, Vakıflar Bankası, Halkbank, QNB Finansbank, Kuveyt Türk Katılım Bankası, Denizbank, TEB, ING Bank, Türkiye Finans Katılım Bankası, Albaraka Türk Katılım Bankası, Vakıf Katılım Bankası
FAST-TR QR Code Application Transition Process Table
| No | QR Code Type | Reading2 / Generating3 | Criteria | Date |
|---|---|---|---|---|
| 1 | QR code presented in person-to-person payments | Reading + Generating | All payment service providers that were FAST System participants before 01 January 2024 and offer FAST service via a mobile application | By 30.04.2024 |
| All payment service providers that are FAST System participants on or after 01 January 2024 and will offer FAST service via a mobile application | within at most 4 months from the date they go into production in the FAST System | |||
| All payment service providers that start message exchange as a FAST System participant, do not yet offer FAST service via mobile application but will offer it as of a certain date | within at most 4 months from the date they start offering the said service | |||
| 2 | Long and short QR code presented by the merchant | Reading | All payment service providers that are FAST System participants before 01 January 2024 and offer FAST service via mobile application | by 30.04.2024 |
| All payment service providers that are FAST System participants on or after 01 January 2024 and will offer FAST service via mobile application | within at most 4 months from the date they go into production in the FAST System | |||
| All payment service providers that start message exchange as a FAST System participant, do not yet offer FAST service via mobile application but will offer it as of a certain date | within at most 4 months from the date they start offering the said service | |||
| 3 | Long or short QR code with dynamic verification presented by the merchant | Generating | All payment service providers that are FAST System participants before 01 January 2024 and offer merchants the possibility to accept payments via payment cards or the FAST System | by 30.04.2024 |
| All payment service providers that are FAST System participants on or after 01 January 2024 and will offer merchants the possibility to accept payments via payment cards or the FAST System | within at most 6 months from the date they go into production in the FAST System | |||
| All payment service providers that start message exchange as a FAST System participant, do not yet offer merchants the possibility to accept payments via payment cards or the FAST System but will offer it as of a certain date | within at most 6 months from the date they start offering the said service |
[2] The process of initiating a FAST payment by reading the QR code must be evaluated as a whole.
[3] The process of accepting a FAST payment by generating the QR code must be evaluated as a whole.
The "Regulation on the Generation and Use of TR QR Code in Payment Services" (the Regulation), prepared with the aim of ensuring interoperability among the actors in the payments ecosystem by establishing common rules and a common language, supporting innovative initiatives and thereby contributing to the dissemination of QR code use in payment services, and the "TR QR Code Principles and Rules" document annexed to this Regulation entered into force upon publication in the Official Gazette dated 21 August 2020 and numbered 31220.
This document, which contains the detailed technical principles and rules regarding the use of the TR QR Code in transactions to be carried out through the FAST System, has been created based on the Regulation on the Generation and Use of TR QR Code in Payment Services and the TR QR Code Principles and Rules document.
The QR code payment flows to be carried out through the FAST System are in the nature of Layer Services defined in the FAST System Operating Rules and whose details are included in the FAST System Reference Document, and FAST System participants are obliged to comply with the rules to which the Layer Services are subject.
In this document, which has been created in compliance with the Regulation and the TR QR Code Principles and Rules document annexed to the Regulation, the workflows of payments carried out through the FAST System in accordance with the QR code usage models presented by merchants (ing. merchant-presented) and presented in person-to-person payments are provided, and the TR QR Code data organization for FAST System payments is defined for both usage models.
Within the scope of the principles and rules set out in this document, the definitions included in the TR QR Code Principles and Rules document are used for the characteristics of QR code technology, the encoding of data objects, data types and formats, the QR code data organization according to the business model used, and the characteristics of data objects.
This document has been prepared based on the first paragraph of Article 6 of the Regulation.
Within the scope of this document;
Recipient: The real or legal person to whom the funds subject to the payment transaction are intended to reach,
Receiving Participant: The participant that receives a message sent to FAST,
BKM: Interbank Card Center Joint Stock Company,
Dynamic Verification: In a payment transaction initiated using a dynamic QR code, the online verification by the receiving participant at the time of the transaction of certain transaction-specific information such as the recipient's name/title and account number and the amount,
Dynamic QR code: The QR code that is generated specifically for the payment transaction to be used and is single-use,
EMVCo: The association consisting of American Express, Discover, JCB, Mastercard, UnionPay and Visa,
FAST: The Instant and Continuous Transfer of Funds System operated by the CBRT,
FAST – TR QR Code: The TR QR Code to be used in payment transactions to be carried out through FAST,
Sender: The real or legal person who issues a payment order from their own payment account or without having a payment account,
Sending Participant: The participant that transmits a message to FAST for processing,
Merchant Registry System: The system maintained at BKM in which information related to merchants accepting electronic payments is kept, for the purpose of facilitating the processes related to payment transactions made with TR QR Code and preventing fraud and malicious use activities in the field of payments,
Merchant-presented QR code: The QR code model based on the principle that customers read the QR code presented by the merchant through the application they use and initiate the payment transaction,
Law: The Law on Payment and Securities Settlement Systems, Payment Services and Electronic Money Institutions dated 20/6/2013 and numbered 6493,
QR Code: The two-dimensional code created to be used in payment transactions by scanning; storing alphanumeric data, characters and symbols, consisting of three square pattern markers in the lower left corner, upper left corner and upper right corner according to the reader, and having black and white modules in the form of square black-and-white dots or pixels,
QR code generator code: The code required to generate a TR QR Code,
QR Code Routing System (KYS): The structure that enables the transfer of QR codes and the information contained therein between payment service providers,
Participant: The payment service provider that can directly send and receive messages to and from FAST,
Short QR Code: The QR code with limited data content used in cases where all the data required for the payment transaction cannot be stored,
QR code presented in person-to-person payments: The QR code model presented by the recipient in person-to-person (ing. P2P, person-to-person) payment transactions for the purpose of transferring the account information of the recipient of the payment to the sender,
Customer: The real or legal persons who transmit to the merchant the payment for the price of the goods and services offered by the merchant,
Payment service: The services specified in Article 12 of the Law,
Payment service provider: The institutions specified in Article 13 of the Law,
Payment transaction: The activity of depositing, transferring or withdrawing funds carried out upon the instruction of the sender or the recipient,
CBRT: Central Bank of the Republic of Turkey Joint Stock Company,
TR QR Code: The QR code created in accordance with the procedures and principles set out in the TR QR Code Principles and Rules Document and that can be used in payments within the scope of the Law,
Static Verification: In a payment transaction initiated using a static QR code, the online verification by the receiving participant at the time of the transaction of certain information specific to the merchant and the QR code, as well as the recipient's name/title and account number,
Static QR code: The QR code whose content is fixed and can be used in more than one transaction,
Regulation: Refers to the Regulation on the Generation and Use of TR QR Code in Payment Services.
1) Payment transactions made with FAST – TR QR Code are classified under two main usage scenarios:
a. Merchant payments: Payments made in return for the purchase of goods and services within the scope of commercial activity.
i. FAST merchant payments for which dynamic verification service is received from a FAST System participant
ii. FAST merchant payments for which static verification service is received from a FAST System participant
b. Person-to-Person Payments: Payments made using the QR code model presented in person-to-person payments
2) All fields in the QR Code must be carried with a data structure compatible with the fields for which equivalents exist in the FAST System.
3) Although both static and dynamic QR code flows are supported in the FAST System, FAST merchant payments for which dynamic verification service is received must be carried out using a dynamic QR code together with a unique reference number generated specifically for the purchase transaction, while merchant payments for which static verification service is received must be carried out together with a unique reference number generated specifically for the QR code.
4) The data field to be taken as basis in distinguishing merchant payments from other payments and, accordingly, in determining FAST fees and commissions is the QR Code Flow Type (Field Code: 30/02), and the acquirer participant is responsible for accurately reflecting this field in the generated QR code, while the sender participant is responsible for transferring this field to FAST messages without modification.
5) In merchant payments to be made with FAST – TR QR Code, the acquirer participant (the participant providing payment services to the merchant) must absolutely subject the payment coming through the FAST system to QR code verification and reject payments that fail verification with the appropriate rejection code.
6) In payments to be made using FAST – TR QR Code, all parties, especially payment service providers, continue to be obliged to fulfill all other obligations arising from the Law and other relevant legislation and not otherwise specified in this document.
7) In order for FAST System participants to be able to make QR-coded FAST payments within the scope of this document, they must have successfully completed the test scenarios to be determined by the TCMB.
FAST-TR QR code flows are addressed under two different headings: merchant payments and person-to-person payments.
Merchant payments can be realized in two different scenarios: FAST merchant payment for which dynamic verification service is received from a FAST System participant and FAST merchant payment for which static verification service is received.
In FAST merchant payments for which dynamic verification service is received from a FAST System participant, FAST – TR QR code flows consist of two different flows: Long QR Code and Short QR Code.
0. The acquirer participant creates a QR code specific to the purchase transaction upon the merchant's online request. Since the generated QR code must be verified by the acquirer participant in subsequent stages, the following fields to be used for verification must be present in the QR code and recorded in the participant's system:
a. QR code reference number,
b. Merchant account name/title,
c. Merchant account number,
d. Amount,
e. Last validity time,
f. QR Code Flow Type = 01
1. The merchant displays the generated QR code via a device that displays QR codes (virtual/physical POS, cash register, etc.).
2. The customer scans the QR code via their application and, if the QR code supports multiple payment flows (Credit Card, FAST, etc.), selects FAST payment as the payment method and the account from which the payment will be made.
3. The customer approves the purchase transaction and sends the payment instruction to the sender participant.
4. The sender participant performs checks on its customer's balance and other necessary controls, creates the instant payment message, and transmits it to FAST.
5. FAST performs its checks on the message, places the transaction in the queue to perform fund reservation, and routes the message to the acquirer participant.
6. In line with the incoming message, the acquirer participant performs QR code verification for the transfer of the payment to the account of the merchant, who is the recipient, according to the following fields and sends the confirmation (T01) message to FAST:
a. QR code reference number,
b. Merchant account name/title,
c. Merchant account number,
d. Amount,
e. Last validity time,
f. QR Code Flow Type = 01,
7. FAST, upon receiving the T01 message, performs the necessary checks, initiates the reconciliation process, and sends T02 result notification messages to the acquirer participant and the sender participant.
8. The acquirer participant informs the merchant, and the sender participant informs its customer, instantly about the result of the transaction.
The short QR code (KK) application is a model that can be used in devices provided by the merchant but where long QR code usage is not possible (for example, older generation POS devices), in cases where all data required for the payment transaction cannot be stored.
In the short QR code workflow, the generated QR code contains a unique reference number and summary information created by the QR code generator (acquirer participant) instead of the information pertaining to the payment transaction. The customer who scans with the short QR code application obtains the information necessary for payment from the acquirer participant via the sender participant using this reference number, and after this stage initiates the actual payment transaction.
0. The Acquirer Participant creates a short QR code (KK) specific to the purchase transaction upon the merchant's online request. Since the transaction must be verified by the Acquirer Participant in subsequent stages, the following fields to be used for verification must be recorded in the participant's system:
a. QR code reference number,
b. Merchant account name/title,
c. Merchant account number,
d. Amount,
e. Last validity time,
f. QR Code Flow Type = 01,
1. The merchant displays the generated QR code via a device that displays QR codes (virtual/physical POS, cash register, etc.).
2. The customer scans the QR code via their application, and the mobile application automatically transmits the KK information to the sender participant.
3. The sender participant sends the reference information contained in the KK to the acquirer participant via KYS.
4. The acquirer participant verifies the information contained in the KK, primarily the reference, creates the payment and merchant information, and transmits it to the sender participant via KYS.
5. The sender participant presents the transaction to the customer's approval together with the masked information regarding the payment and the merchant.
6. The customer checks and approves the payment information in their application and sends the actual payment initiation instruction to the sender participant.
7. The sending participant creates the payment message by checking the payment request, its customer's balance and other necessary controls, and transmits it to FAST.
8. FAST performs its controls on the message, queues the transaction for fund segregation, and routes the message to the receiving participant.
9. The receiving participant, in line with the incoming message, performs the QR code verification for the transfer of the payment to the account of the payee merchant according to the following fields and sends the confirmation (T01) message to FAST:
a. QR code reference number,
b. Merchant account name/title,
c. Merchant account number,
d. Amount,
e. Last validity time,
f. QR Code Flow Type = 01,
10. FAST, upon receiving the T01 message, performs the necessary controls, initiates the reconciliation process, and sends the T02 result notification messages to the receiving participant and the sending participant.
11. The receiving participant instantly informs the merchant, and the sending participant informs its customer, about the result of the transaction.
The workflow regarding the FAST – TR QR Code to be used in payments made to merchants that receive static verification service from a FAST System participant and that will be realized through FAST will be as follows:
1. The merchant shows its customer the static QR code that it has previously obtained from the FAST System participant and that contains the merchant and payment information. Since the QR code shown in this flow must be verified by the receiving participant at the time of payment, the following information must be included in the QR code and the FAST System participant must have recorded this information in its system:
a. QR Code Reference Number
b. Merchant account name/title,
c. Merchant account number,
d. Amount [Optional]
e. Last validity time [Optional]
f. QR Code Flow Type must be ‘02’.
2. The customer scans the QR code shown via its application and sees the information regarding the payment and the merchant. If there is no amount in the QR code, the customer enters the amount information.
3. The customer confirms the payment and transmits it to the sending participant.
4. The sending participant creates the payment message by checking the payment request, its customer's balance and other necessary controls, and transmits it to FAST.
5. FAST performs its controls on the message, queues the transaction for fund segregation, and routes the message to the receiving participant.
6. The receiving participant, in line with the incoming message, performs the QR code verification for the transfer of the payment to the account of the payee merchant according to the following fields and sends the confirmation (T01) message to FAST:
a. QR Code Reference Number
b. Merchant account name/title,
c. Merchant account number,
d. Amount [Verified if an amount was entered when the QR code was created]
e. Last validity time [Checked if this field was entered when the QR code was created]
f. QR Code Flow Type ‘02’
7. FAST, upon receiving the T01 message, performs the necessary controls, initiates the reconciliation process, and sends the T02 result notification messages to the receiving participant and the sending participant.
8. The receiving participant instantly informs the merchant, and the sending participant informs its customer, about the result of the transaction.
Refunds of merchant payments made through the FAST System can be made using dynamic QR codes (long or short) within the scope of the following flows.
The use of these flows is not mandatory for the receiving participant (acquirer), and participants that wish may initiate the refund transaction directly by entering the FAST message reference information. However, sending participants (issuer) must be able to read QR codes containing refund information.
0. Upon the merchant's online request, the receiving participant creates the refund QR code that also includes the message reference information of the purchase transaction previously realized with FAST. (For this flow, the Long QR code Provided by the Merchant will be used by including template 31. The amount information in the refund QR code must be equal to or less than the amount in the transaction.)
1. The merchant displays the QR code generated via a device displaying a QR code (virtual/physical POS, cash register, etc.).
2. The customer scans the QR code via their application and views the payment information to be refunded.
3. The customer approves the refund request process.
4. The sending participant, using the Related Message Reference Number (Id: 31/01) field contained in the QR code, verifies the payment to be refunded by
a. The sending participant code of the related message
b. The date of the related message
c. The query number of the related message and
d. The customer account information (whether the sale was made to the relevant customer), creates and sends the Request Refund (H31) message via the FAST System.
5. The merchant approves the refund transaction to be carried out based on the Request Refund (H31) message conveyed by the receiving participant (Optional).
6. The receiving participant creates the Payment Refund (A09) message and sends it to the FAST System.
7. FAST performs its checks on the message, queues the transaction for fund segregation, and routes the A09 message to the counterparty participant.
8. The sending participant, in line with the incoming message, performs the verification for the transfer of the payment to the customer's account and sends the confirmation (T01) message to FAST.
9. FAST, upon receiving the T01 message, performs the necessary checks, initiates the reconciliation process, and conveys the T02 result notification messages to the participants.
10. The receiving participant informs the merchant, and the sending participant informs the customer, in real time about the result of the transaction.
0. The receiving (accepting) participant, upon the online request of the merchant, creates a refund QR code containing the message reference information of a purchase transaction previously carried out via FAST. (The Short QR Code Offered by the Merchant will be used for this flow)
1. The merchant displays the QR code generated via a device displaying a QR code (virtual/physical POS, cash register, etc.).
2. The customer scans the QR code via their application, and the mobile application automatically transmits the QR code information to its participant.
3. The sending participant sends the reference information contained in the QR code to the receiving participant via KYS.
4. The receiving participant verifies the information contained in the QR code, including the reference, and conveys the refund information to the sending participant via KYS. The amount information in the refund parameters must be equal to or less than the amount in the transaction.
5. The sending participant, using the Related Message Reference Number field contained in the information conveyed via KYS, verifies the payment to be refunded by
a. The sending participant code of the related message
b. The date of the related message
c. The query number of the related message and
d. The customer account information (whether the sale was made to the relevant customer), and presents it for customer approval. The customer views the information regarding the refund request process conveyed by their participant and approves the transaction.
6. The sending participant creates and sends the Request Refund (H31) message via the FAST System with the payment information to be refunded.
7. The merchant approves the refund transaction to be carried out based on the Request Refund (H31) message conveyed by the receiving participant (Optional).
8. The receiving participant creates the Payment Refund (A09) message and conveys it to the sending participant via the FAST System.
9. The sending participant, in line with the incoming message, performs the verification for the transfer of the payment to the customer's account and sends the confirmation (T01) message to FAST.
10. FAST, upon receiving the T01 message, performs the necessary checks, initiates the reconciliation process, and conveys the T02 result notification messages to the participants.
11. The receiving participant informs the merchant, and the sending participant informs the customer, in real time about the result of the transaction.
1. The recipient shows the generated static or dynamic QR code to the Sender. In this flow, the QR Code Flow Type must be '03'.
2. The Sender, by scanning the displayed QR code via their application, sees the information related to the payment and the recipient in masked form.
3. The Sender, if the amount has not been entered, enters the amount of the payment and transmits it to the sending participant by approving the payment.
4. The sending participant performs the necessary checks, creates the real-time payment message, and transmits it to FAST.
5. FAST performs its checks on the message, queues the transaction for fund segregation, and routes the message to the receiving participant.
6. The receiving participant, in line with the incoming message, performs the necessary verifications and checks for the transfer of the payment to the recipient's account as set forth in the FAST Operating Rules, and sends the confirmation (T01) message to FAST.
7. FAST, upon receiving the T01 message, performs the necessary checks, initiates the reconciliation process, and conveys the T02 result notification messages to the receiving participant and the sending participant.
8. The receiving participant informs the recipient, and the sending participant informs the sender, in real time about the result of the transaction.
The data within a QR code are organized in a tree structure as objects, and this structure is divided into two main classes: simple data objects and data template objects, located under the root4 part of this structure. While simple data objects can store a single piece of information such as date, amount, reference number, data template objects can contain one or more simple data objects and other data template objects (Figure)5.
Figure: QR Code Data Structure Organization
Each object within a QR code has a data structure consisting of three parts:
Field code: Consists of two digits between "00" and "99" and indicates the identity of the object. Within a QR code, all field names have a unique value at the root level or within the data template they are contained in. For example, the object indicated by the field code "01" under the root and the object indicated by the field code "01" under a data template with field code "62" refer to different data.
Length: A two-digit number with a value between "01" and "99" that indicates the length in characters of the data value belonging to the object.
Data value: The value of the data, which is at least one character and at most 99 characters long.
Example:
An object with field code "02", length "08" and data value "20200530" is represented in the form "020820200530".
The data values of the objects contained within the QR code support the following data types:
Character String (K): A data type containing characters created in accordance with UTF-8 6-character encoding.
Special Alphanumeric (ÖAN): A data type containing digits between '0'-'9', letters of the alphabet and punctuation marks. It is a subset of the Character String data type.
Numeric (N): A data type containing digits between '0'-'9'. It is a subset of the Special Alphanumeric data type.
For the presence status of objects within the QR code data organization, the following notation is used:
Mandatory (Z): The relevant data object must always be present in the QR code.
Optional (İ): The presence of the relevant data object in the QR code is optional.
Conditional (K): The presence of the relevant data object in the QR code is subject to certain conditions. For example, if only one of two data objects is required to be present in the QR code, the presence status of these objects is indicated as conditional. The necessary condition information is contained in the descriptions of the relevant objects.
[4] An object that does not appear under any data template.
[5] The relevant information has been taken from the "TR QR Code Principles and Rules" document, which is an annex to the Regulation.
[6] UTF-8 (8-bit Unicode Transformation Format) is the name of the general standard that enables the representation of all universally available characters using a variable number of bytes ranging from 1 to 4.
The QR Code Format Indicator, which is the first data object of the QR code, specifies the type of the QR code in accordance with its usage model, and accordingly, the structure, representation and version of the remaining data. Applications parse all data by first reading this object in the QR code.
In this section, definitions of QR code data structures are provided for the QR code usage models presented by the merchant for payments to be made via FAST and those presented in person-to-person payments.
The table below shows the long QR code data organization presented by the merchant arranged for FAST and the corresponding fields in the instant payment message where the relevant fields will be carried; the said data structure is used in the flows given in Section 5.1.1.1 and Section 5.1.2.
Table 1: Long QR code data organization presented by the merchant
| Field Name | Field Code | Sub-field Code:Name | Data Type | Length | Presence Status | Sample Data Value | Description |
|---|---|---|---|---|---|---|---|
| QR Code Format Indicator | 00 | - | N | 02 | Z | 000201 | This is the value used for the QR code data organization presented by the merchant. The last two digits (data value) indicate the version number of the EMVCo Standard to which the QR code data organization conforms and have the fixed value "01". |
| QR Code Type | 01 | - | N | 02 | Z | For static QR code: 010211 For dynamic QR code: 010212 | Used for the distinction between Static and Dynamic QR Code. Data value: "11": Static QR Code where the same QR Code is used for multiple transactions. "12": Dynamic QR Code where a different QR Code is used for each transaction. |
| Merchant Account Information | 02-46 | OAN | Variable up to 99 | Mandatory at least one | For FAST: 30uuVD | Merchant account information must be placed under the relevant field code of the relevant payment system in a manner compatible with the workflows of the payment system. VD: Data value of the template. uu: Total length of the data value of the template (VD) in characters. | |
| 02-03 | Reserved for VISA. | ||||||
| 04-05 | Reserved for Mastercard. | ||||||
| 06-08 | Reserved for EMVCo. | ||||||
| 09-10 | Reserved for Discover. | ||||||
| 11-12 | Reserved for Amex. | ||||||
| 13-14 | Reserved for JCB. | ||||||
| 15-16 | Reserved for UnionPay. | ||||||
| Fields reserved by EMVCo for EMV members. |
| Field Name | Field Code | Sub-Field Code:Name | Data Type | Length | Presence Status | Sample Data Value | Description |
|---|---|---|---|---|---|---|---|
| 17-25 | Reserved for EMVCo. | ||||||
| 26-27 | Used by BKM | ||||||
| 28-29 | Reserved for BKM. | ||||||
| 30 | - | OAN | Variable up to 99 | Z | 30uuVD | Merchant account information data template to be used for FAST. VD: Data value of the relevant template. uu: Total length of the data value of the relevant template (VD) in characters. | |
| 00: Universal Unique Identifier | OAN | 16 | Z | 0016TR.GOV.T CMB.FAST | Reverse domain name of FAST | ||
| 01: Merchant IBAN | OAN | 26 | Z | 0126TR123456 789012345678 901234 | The account number that the merchant wants the payment sent by the customer to be transferred to, carried in the AlHesN field in the FAST A01 message. If it contains the EFT code within the Merchant IBAN, it is carried to the AlKK field. | ||
| 02: QR Code Flow Type | N | 2 | Z | For payment of an online service obtained from a FAST System participant: 020201 | Specifies the flow type to be used: 01: FAST merchant payment obtained with dynamic verification service from a FAST System participant 02: FAST merchant payment obtained with static verification service from a FAST System participant 04: Merchant payment refund. The receiving participant in the FAST system has the obligation to validate this field and communicate the validation result with the T01 message. The field to be carried in the FAST A01 message is KtmSrvBlg + Krkd ++ KrkdAksTur |
| Field Name | Field Code | Sub-Field Code:Name | Data Type | Length | Presence Status | Sample Data Value | Description |
|---|---|---|---|---|---|---|---|
| 20: Summary Security Value (Hash) | ÖAN | 32 | Z | 2032E200C014 A30EFCDC7E9F 379CE0766A68 | The hash value is used to check whether this QR code was actually generated by the QR code producer. When creating the QR code, the QR code producer can fill it with a value of a length it determines itself, create summary information by mixing it with different information (customer-specific information such as ID number), or assign random values. | ||
| 31 | - | ÖAN | Variable up to 99 | I | 31uuVD | Data template for merchant account information to be used for FAST. VD: Data value of the relevant template. uu: Total length in characters of the data value (VD) of the relevant template. | |
| 01: Relevant Message Reference | ÖAN | 28 | K | For the refund of a FAST message with query number 123456 sent by participant with code 0062 dated 18.12.2020: 012820121800 620000000000 00123456 | Contains the FAST message reference information (date, sender participant code, query number) of the payment to be refunded. Mandatory if the QR Code Flow Type is "04". Formatted as follows. [Trh][GonKK][SN] Trh: The message date of the payment to be refunded. Entered as 6 characters in YYAAGG format. Example: 20201218 GonKK: Indicates the sender participant code of the payment to be refunded. Entered as 4 characters. Example 0062 SN: Contains the FAST query number of the payment to be refunded. Entered as 18 characters. Query numbers shorter than 18 characters are padded with 0 on the left. Example: 000000000000123456 | ||
| 32 | Used for mobile payments. | Will not be used for FAST. | |||||
| 33-40 | Reserved for CBRT | ||||||
| 41-46 | Reserved for other payment systems in Türkiye. | Will not be used for FAST. |
| Field Name | Field Code | Sub-Field Code:Name | Data Type | Length | Presence Status | Sample Data Value | Description |
|---|---|---|---|---|---|---|---|
| Merchant Free Templates | 47-48 | ÖAN | Variable up to 99 | I | 47uuVD 48uuVD | Merchants can freely use these fields in the form of simple data and/or data template in order to carry additional information related to the payment that is not defined in the other fields of the table (e.g., product information, bill, etc.) within the QR code. VD: Data value of the relevant template. uu: Total length in characters of the data value (VD) of the relevant template. | |
| Merchant Code | 49 | N | 10 | I | 4910002341567 2 | The unique reference number of the merchant in the Merchant Registration System. Values shorter than 10 digits will be padded with the character '0' on the left. | |
| Location | 50 | N | Variable between 16-34 | I | Position value for latitude 39.939423 and longitude 32.851791: 50163993942 332851791 | Position information that can be used for QR code payment transactions and created according to the Decimal Degrees (DD) format. The position value consists of two parts of equal length, the first being the latitude and the second the longitude. For Latitude: EE.eeeeee and Longitude: BB.bbbbbb, the position value is specified as EEeeeeeeBBbbbbbb and no separator such as '.', ',' etc. is used within it. The number of digits for 'e' and 'b' is equal and can be at least 6 and at most 15 depending on the precision degree to be used. | |
| QR Code Identity Template | 51 | OAN | Variable up to 99 | 51uuVD | QR code identity template generated by the QR code producer. VD: The data value of the template. uu: The total length of the template's data value (VD) in characters. | ||
| 00: Version Number | N | 02 | Z | For TR QR Code Version 1.0 data organization: 000210 | TR QR Code version number. For a version number of "S.s", the data value is created as "Ss" without using a punctuation mark. |
| Field Name | Field Code | Sub-Field Code:Name | Data Type | Length | Occurrence Status | Sample Data Value | Description |
|---|---|---|---|---|---|---|---|
| 02: QR Code Producer Code | N | 04 | Z | 02040010 | The code of the QR code producer. Payment Service Providers and payment system operators deemed appropriate by the CBRT will be able to obtain a QR code producer code by applying for registration to BKM in order to generate TR QR Codes. Banks will use their EFT codes and there is no need for them to register separately. Values shorter than 4 digits will be padded on the left with the character "0". | ||
| 03: QR Code Reference Number | OAN | Variable up to 12 | Z | 03082345101 7 | Unique reference number created for the QR code. It is provided by the merchant application or the QR code producer and is used in end-to-end verification, transaction recording, or receipt generation. It can be specified within the QR code by the merchant or it can be an indicator for the consumer to enter the reference information into the mobile application they use. The field to be carried in the FAST A01 message: KtmSrvBlg + Krkd ++ KrkdRef | ||
| 04: Terminal Type | N | 02 | I | For POS: 040202 | The type of device where the QR code was generated. Defined values: "01": Static QR code "02": POS/mPOS/ÖKC/Kiosk etc. payment acceptance software and hardware "03": ATM "04": Merchant application "05": Web "06": Payment service provider merchant application |
| Field Name | Field Code | Sub-Field Code:Name | Data Type | Length | Occurrence Status | Sample Data Value | Description |
|---|---|---|---|---|---|---|---|
| 05: Terminal Device Serial Number | OAN | Variable up to 23 | I | 05231234567 89012345678 90ABC | Distinctive value belonging to the QR code generating device or terminal (e.g., terminal number and/or terminal serial number) | ||
| 06: Creation Time | N | 12 | Z | For 29 July 2020 at 15.30:59: 06122007291 53059 | Time information when the QR code was generated. YYAAGGSSDDss YY: Year, AA: Month, GG: Day, SS: Hour (24-hour), DD: minute, ss: Second | ||
| 07: Last Validity Time | N | 12 | K | For 29 July 2020 at 16.30:59: 07122007291 63059 | Time information for the last time the QR code is valid. YYAAGGSSDDss YY: Year, AA: Month, GG: Day, SS: Hour (24-hour), DD: minute, ss: Second Optional for static QR codes, mandatory for dynamic QR codes. | ||
| Merchant Category Code | 52 | N | 04 | Z | 52045499 | The ISO 18245-compliant Merchant Category Code (MCC) of the transaction. As examples of 4-digit codes, "5661" (shoe seller) or "5499" (Markets) can be given. If this field is not used, the value "0000" must be written. | |
| Currency | 53 | N | 03 | Z | 5303949 | The ISO 4217-compliant currency code of the transaction. For FAST, it must contain the fixed value "949". | |
| Amount | 54 | N | 12 | K | For 150,5: 54120000000 15050 | Specifies the amount of the transaction. The last two digits indicate the kuruş part, and the left side of the number is filled with "0" so that the amount is completed to 12 digits. Its use is mandatory in dynamic QR codes. If this field is not present or is 0, the payment amount must be entered by the customer in the application. The field to be carried in the FAST A01 message is Ttr |
| Field Name | Field Code | Sub-Field Code:Name | Data Type | Length | Presence Status | Sample Data Value | Description |
|---|---|---|---|---|---|---|---|
| Tip or Other Amount Indicator | 55 | N | 02 | Will not be used for FAST. | |||
| Tip or Other Amount Value (Fixed) | 56 | N | 12 | Will not be used for FAST. | |||
| Tip or Other Amount Value (Percentage) | 57 | N | 05 | Will not be used for FAST. | |||
| Country Code | 58 | ÖAN | 02 | Z | 5802TR | The 2-digit country code of the workplace as specified in ISO 3166-1 alpha 2. For FAST, “TR” | |
| Workplace Name | 59 | OAN | Variable up to 25 | Z | 5908ABC GIDA | The account name of the workplace. Displayed on the customer's device screen during the transaction. The field to be carried to the FAST A01 message is AlAd | |
| Workplace City | 60 | OAN | Variable up to 15 | Z | 6008İSTANBUL | The city name of the workplace. | |
| Postal Code | 61 | OAN | Variable up to 10 | I | 610534100 | The postal code of the workplace | |
| Additional Data Fields Template | 62 | - | K | Variable up to 99 | I | 62uuVD | Contains additional data needed by the business for FAST. Since the total length of the field belonging to the template is at most 99 characters, the subfields whose presence status is "optional" must be determined in a way that does not exceed this limit and the QR code must be created accordingly. VD: The data value of the template. uu: The total length of the data value (VD) of the template in characters. |
| Field Name | Field Code | Subfield Code:Name | Data Type | Length | Presence Status | Sample Data Value | Description |
|---|---|---|---|---|---|---|---|
| 01: Invoice Number | ÖAN | Variable up to 25 | İ | 0111TLK012304 05 | This field contains the invoice number or serves as an indicator for the customer to enter the invoice number with an appropriate content (for example, "***"). The field to be carried to the FAST A01 message is RefBlg | ||
| 02: Customer's Phone Number | ÖAN | Variable up to 15 | İ | 0212903125075 000 | The customer's mobile phone number. It may be specified by the merchant within the QR code or may be a prompt for the consumer to enter the phone number into the mobile application they use. | ||
| 03: Store Label | ÖAN | Variable up to 25 | İ | 0306AVMSTR | A label information that can be used to distinguish a particular store from others. It may be specified by the merchant within the QR code or may be a prompt for the consumer to enter the store label into the application they use. The consumer's application that reads the QR code may display this store information on the screen. | ||
| 04: Customer Loyalty Number | ÖAN | Variable up to 25 | İ | 0410231563412 3 | The customer's loyalty card number. It may be specified by the merchant within the QR code or may be a prompt for the consumer to enter the loyalty number into the mobile application they use. | ||
| 06: Customer Number | ÖAN | Variable up to 25 | İ | 0610051889411 1 | A label value used specifically for the customer. For example, it may be the customer's membership number for a membership. It may be specified by the merchant within the QR code or may be a prompt for the customer to enter the label number into the mobile application they use. It can be used as a subscriber number in invoice payments. |
| Field Name | Field Code | Sub-Field Code:Name | Data Type | Length | Presence Status | Sample Data Value | Description |
|---|---|---|---|---|---|---|---|
| 08: Payment purpose | ÖAN | 2 | Z | For dues payment: 080209 | The field to be carried to the FAST A01 message is RefBlg In the Instant Payment (A01) message, it can take the values in the FAST Message Structure and Transaction Types document regarding the payment purpose. If the QR Code Flow Type is "04: Merchant payment refund", this field must be entered as "00" and must not be carried to the FAST message. In a sales transaction, the field to be carried in the FAST A01 message is OdmAmc | ||
| 09: Additional Consumer Data | ÖAN | Variable up to 3 | İ | Will not be used for FAST. | |||
| Merchant Language Information Template | 64 | K | Variable up to 99 | İ | Will not be used for FAST | ||
| EMVCo Reserved Fields | 65-79 | K | variable up to 99 | İ | Will not be used for FAST | ||
| Free Templates | 80-99 | K | variable up to 99 | İ | Will not be used for FAST | ||
| CRC | 63 | ÖAN | 04 | Z | 63043F2E | It is the integrity check value calculated over the entire QR code (excluding the CRC value in this field) and is the last field of the QR code (see: TR QR Code Principles and Rules) |
Example:
Plain Text Value:
00020101021230920016TR.GOV.TCMB.FAST0126TR1234567890123456789012340202012032E200C014A30EFCDC 7E9F379CE0766A684910002341567250163993942332851791519100021002040010030823451017040202052312 345678901234567890ABC0612200729153059071220072916305952045499530394954120000000150505802TR59 08ABC GIDA6008İSTANBUL61053410062750111TLK0123040502129031250750000306AVMSTR041023156341230610051 889411108020963043F2E
QR Code:
Refund QR Code Example:
Plain Text Value:
00020101021230920016TR.GOV.TCMB.FAST0126TR0200950001000003540000100202042032E200C014A30EFCDC 7E9F379CE0766A68313201282012180960000000000000123456491000234156755193000210020409500310REF0 950D12040202052312345678901234567890ABC06122102150000000712221231000000520454995303949541200 00000150505802TR5913MERKEZ OLUMLU6006ANKARA620608020063048B01
QR Code:
The following table shows the short QR code data organization provided by the merchant for FAST and the corresponding fields in the instant payment message where the relevant fields will be carried, and the said data structure is used in the flow given in Section 5.1.1.2.
Table 2: Short QR Code (KK) data organization provided by the merchant
Field Name Data Type Length
Presence
Status
Example Data
Value
Description
QR Code Format
Indicator N 02 Z
FAST KK for: 97
Usage model determines the data structure in accordance with.
"97": FAST KK
"96"7
: FAST KK and BKM KK
QR Code Producer
Code N 04 Z 0010
Code of the QR code producer.
Will be given and recorded by BKM. Payment
Service Providers and TCMB deemed appropriate by payment system operator TR QR Code in order to generate, to BKM by making a registration application QR code producer code they will be able to obtain. Banks EFT codes will be used and also registration to have them made there is no need. 4 for values shorter than digits, the left side with the "0" character will be filled. QR Code Reference Number ÖAN 12 Z REF666777 888 In a manner that will not follow each other created merchant payment service provider based unique transaction reference number. For FAST mandatory field. Field to be carried in FAST A01 message:
area:
KtmSrvBlg
[7] It is the short QR code indicator that both payment systems are supported by the merchant and the merchant's bank, and the customer can choose between these payment systems.
| CRC | ÖAN | 04 | Z | 5BFD | It is the integrity check value calculated over the entire QR code (excluding this field) (see: TR QR Code Principles and Rules). |
|---|---|---|---|---|---|
| Other Data | ÖAN | variable up to 214 | - | - | It will not be used for FAST. |
Example:
Plain Text Value:
970010REF666777888E7054DBB31781D7A15F5043372E802C55BFD QR Code:
The following table shows the person-to-person payment QR code data organization arranged for FAST and the corresponding fields in the instant payment message where the relevant fields will be carried, and the said data structure is used in the flow given in Section 5.3.
Table 3: Person-to-person payment QR code data organization
| Field Name | Field Code | Sub-Field Code:Name | Data Type | Length | Presence Status | Sample Data Value | Description |
|---|---|---|---|---|---|---|---|
| QR Code Format Indicator | 75 | N | 02 | Z | For TR QR Code Version 1.0 data organization: 750210 | This is the value used for the QR code data organization offered in person-to-person payments. The last two digits (data value) indicate the version number of the TR QR code data organization. For version number "S.s", the data value is formed as "Ss" without using a punctuation mark. | |
| QR Code Type | 01 | N | 02 | Z | For static QR code: 010211 For dynamic QR code: 010212 | Used to distinguish between Static and Dynamic QR Codes. Data value: "11": Static QR Code where the same QR code is used for more than one transaction. "12": Dynamic QR Code where a different QR code is used for each transaction. | |
| QR Code Producer Code | 02 | N | 04 | Z | 02040010 | The code of the QR code producer. It will be given and registered by BKM. Payment Service Providers and the payment system operator deemed appropriate by the TCMB will be able to obtain a QR code producer code | |
| by applying to BKM for registration in order to generate TR QR Codes. Banks will use their EFT codes and do not need to register separately. Values shorter than 4 digits will be padded with the "0" character on the left side. | |||||||
| QR Code Reference Number | 03 | ÖAN | Variable up to 12 | K | 0310RFR234510 1 | Unique reference number created specifically for the QR code. It is mandatory if created as a dynamic QR code, and optional for static QR codes. Field to be carried in FAST A01 message: KtmSrvBlg + Krkd ++ KrkdRef | |
| Creation Time | 06 | N | 12 | İ | For 29 May 2020 at 14.01:59: 0612200529140 159 | The time information when the QR code was generated. YYAAGGSSDDss YY: Year, AA: Month, GG: Day, SS: Hour (24-hour), DD: minute, ss: Second | |
| Last Validity Time | 07 | N | 12 | İ | For 30 May 2020 at 14.01:59: 0712200530140 159 | The last time information when the QR code is valid. YYAAGGSSDDss YY: Year, AA: Month, GG: Day, SS: Hour (24-hour), DD: minute, ss: Second | |
| Amount | 54 | N | 12 | İ | For 150,5: 5412000000015 050 | Indicates the amount of the payment. The last two digits show the decimal part (kuruş, etc.). To complete the amount to 12 digits, “0” is added to the left side. Field to be carried in FAST A01 message: Ttr | |
| Application Template | 61 | ÖAN | Variable up to 99 | Z | 61uuVD | It is the application template to be used for FAST. Since the total length of the field belonging to the template is at most 99 characters, the subfields whose presence is “optional” must be determined in a way that does not exceed this limit and the QR code must be created accordingly. VD: Data value of the template. uu: Total length of the data value (VD) of the template in characters | |
| 01: Account Number (IBAN) | ÖAN | 26 | Z | 0126TR123456 789012345678 901234 | The account (IBAN) number that the payment recipient wants to use to receive the payment. Field to be carried in FAST A01 message: AlHesN | ||
| 02: Card Number | N | 16 | It will not be used for FAST. | ||||
| 04: Easy Address Type | K | 01 | It will not be used for FAST. |
| 05: Easy address value | ÖAN | Variable up to 50 | It will not be used for FAST. | ||||
|---|---|---|---|---|---|---|---|
| 07: Name and Surname of the Payment Recipient | ÖAN | Variable between 2-26 | Z | 0712HASAN YILDIZ | Name and surname of the payment recipient. Field to be carried in FAST A01 message: AlAd | ||
| 10: QR Code Flow Type | N | 02 | Z | 100203 | Indicates the QR code flow type used. The fixed value "03" must be entered. Field to be carried in the FAST A01 message: KtmSrvBlg + Krkd ++ KrkAksTur | ||
| Summary Security Value (Hash) | 20 | ÖAN | Variable up to 32 | I | 2032F93CC13E 3E6410C1BADE EAF349E09A56 | The summary security (hash) value calculated by the application that generates the QR code. The application used can use this field to check whether the QR code data is the QR code it generated itself. | |
| Location | 50 | N | Variable between 16-34 | I | For Latitude: 39.939423 Longitude: 32.851791: 501639939423 32851791 | Location information that can be used for payment transactions with the QR code and created according to the Decimal Degrees (DD) format. The location value consists of two parts of equal length, the first being latitude and the second longitude. For Latitude: EE.eeeeee and Longitude: BB.bbbbbb, the location value is specified as EEeeeeeeBBbbbbbb and no separator such as '.', ',', etc. is used within it. The number of 'e' and 'b' digits is equal and can be at least 6 and at most 15 depending on the precision degree to be used. | |
| CRC | 63 | - | ÖAN | 04 | Z | 63045E7C | It is an integrity control value calculated over the entirety of the QR code (excluding the CRC value in this field) (see: TR QR Code Principles and Rules). It is the last field of the QR code data. |
Plain Text Value:
750210010212020400100310RFR234510106122005291401590712200530140159541200000001505061520126TR 1234567890123456789012340712HASAN YILDIZ1002032032F93CC13E3E6410C1BADEEAF349E09A565016399394233285179163045E7C
QR Code:
In this section, sample scenarios regarding online verifications in FAST Merchant Payment (Section 0) flows where the Dynamic Verification Service is requested from a FAST System Participant are examined.
In all of the following scenarios, it is assumed that Esat Koç, a Z-Bank customer who wants to make a payment of 100 ₺ to ABC Cafe, which receives online service from F-Bank, will make the payment with a QR code.
In this context, F-Bank generates a QR code containing the following basic information upon the request of ABC Cafe and registers it in its system:
| QR Code Information | |
|---|---|
| QR Code Reference Number | 444455556666 |
| Merchant IBAN | TR123456789012345678901234 |
| Merchant Name | ABC Cafe |
| Amount | 100,00 |
| Last Validity Time | 200529120220 |
| Layer Service Indicator | 10 |
Esat Koç scans the displayed QR code with the Z-Bank mobile application, sees the payment information on his screen, selects the FAST payment and the account from which the payment will be made, and confirms the payment.
The part of the flow up to this step is common in all scenarios, and only the subsequent steps will differ.
Z-Bank creates the A01 instant payment message containing the following basic information and transmits it to FAST:
| A01 Message | |
|---|---|
| GonKK | Z-Bank KK |
| AlKK | F-Bank KK |
| GonAd | Esat Koç |
| AlAd | ABC Cafe |
| AlHesN | TR123456789012345678901234 |
| Ttr | 100,00 |
| KtmSrvBlg | |
| + Krkd | |
| ++ KrkdAksTur | 01 |
| ++ KrkdRef | 444455556666 |
FAST forwards the A01 message to F-Bank. F-Bank compares the basic information in the incoming A01 message with the information it recorded at the beginning of the transaction:
| Information recorded at F-Bank | Information received from Z-Bank via FAST | |||
|---|---|---|---|---|
| QR Code Reference Number | 444455556666 | 444455556666 | KtmSrvBg + Krkd ++ KrkdRef | |
| Merchant IBAN | TR123456789012 345678901234 | TR12345678901234567 8901234 | AlHesN | |
| Merchant Name | ABC Kafe | ABC Kafe | AlAd | |
| Amount | 100,00 | 100,00 | Ttr | |
| Last Validity Time | 200529120220 | 200529120215 | (This is the time the A01 message is read by F-Bank and is not sent by FAST.) | |
| QR Code Flow Type | 01 | 01 | KtmSrvBg + Krkd ++ KrkdAksTur |
The QR code is verified using the information recorded at F-Bank and the relevant fields in the A01 message received from FAST. (The security digest value (Hash) can also be used for verification purposes.)
F-Bank sends a positive T01 message to FAST.
FAST performs the reconciliation and sends the positive result notification to F-Bank and Z-Bank. The banks inform their customers.
Z-Bank creates an A01 instant payment message containing the following basic information and forwards it to FAST:
| A01 Message | |
|---|---|
| GonKK | Z-Bank KK |
| AlKK | F-Bank KK |
| GonAd | Esat Koç |
| AlAd | ABC Kafe |
| AlHesN | TR123456789012345678901234 |
| Ttr | 100,00 |
| KtmSrvBlg | |
| + Krkd | |
| ++ KrkdAksTur | 02 |
| ++ KrkdRef | 444455556666 |
FAST forwards the A01 message to F-Bank. F-Bank compares the basic information in the incoming A01 message with the information it recorded at the beginning of the transaction:
| Information recorded at F-Bank | Information received from Z-Bank via FAST | ||
|---|---|---|---|
| QR Code Reference Number | 444455556666 | 444455556666 | KtmSrvBlg + Krkd ++ KrkdRef |
| Merchant IBAN | TR123456789012 345678901234 | TR12345678901234567 8901234 | AlHesN |
| Merchant Name | ABC Kafe | ABC Kafe | AlAd |
| Amount | 100,00 | 100,00 | Ttr |
| Last Validity Time | 200529120220 | 200529120215 | (This is the time the A01 message was read by F-Bank; it is not sent by FAST.) |
| QR Code Flow Type | 01 | 02 | KtmSrvBlg + Krkd ++ KrkdAksTur |
The QR code is verified using the information recorded at F-Bank and the relevant fields in the A01 message received from FAST.
Since the QR Code Flow Type registered in F-Bank's system is not equal to the QR Code Flow Type in the A01 message, F-Bank transmits a negative (QR code could not be verified) T01 message to FAST.
FAST sends the negative result notification to F-Bank and Z-Bank. The banks inform their customers.
Z-Bank creates an A01 instant payment message containing the following basic information and transmits it to FAST:
| A01 Message | |
|---|---|
| GonKK | Z-Bank KK |
| AlKK | F-Bank KK |
| GonAd | Esat Koç |
| AlAd | XYZ Kafe |
| AlHesN | TR123456789012345678901234 |
| Ttr | 100,00 |
| KtmSrvBlg + Krkd ++ KrkdAksTur | 01 |
| ++ KrkdRef | 444455556666 |
FAST forwards the A01 message to F-Bank. F-Bank compares the basic information in the incoming A01 message with the information it recorded at the beginning of the transaction:
| Information recorded at F-Bank | Information received from Z-Bank via FAST | |||
|---|---|---|---|---|
| QR Code Reference Number | 444455556666 | 444455556666 | KtmSrvBg + Krkd ++ KrkdRef | |
| Workplace IBAN | TR123456789012 345678901234 | TR12345678901234567 8901234 | AlHesN | |
| Workplace Name | ABC Kafe | XYZ Kafe | AlAd | |
| Amount | 100,00 | 100,00 | Ttr | |
| Last Validity Time | 200529120220 | 200529120215 | (This is the time the A01 message is read by Bank F and is not sent by FAST.) | |
| QR Code Flow Type | 01 | 01 | KtmSrvBg + Krkd ++ KrkdAksTur |
Since the QR Code Flow Type of the incoming A01 message is 01, the QR code is verified using the information recorded at Bank F and the relevant fields in the A01 message coming from FAST.
Since the Workplace Name matched with the relevant QR Code reference number in Bank F's system is not the same as the AlAd field in the A01 message, Bank F transmits a negative (QR code could not be verified) T01 message to FAST.
FAST sends the negative result notification to Bank F and Bank Z. The banks inform their customers.
ISO 3166-1 alpha 2: Codes for the representation of names of countries and their subdivisions—Part 1: Country codes, using two-letter country codes.
ISO 4217: Codes for the representation of currencies and funds
ISO 18245:2003: Retail financial services — Merchant category codes
FAST System Operating Rules
FAST System Reference Document
QR Code Routing System Rules
Regulation on the Production and Use of TR QR Code in Payment Services
TR QR Code Principles and Rules
Note from RegAlert. AI assistants can read this document in full, and search 70,000+ more, through the RegAlert MCP connector (https://mcp.regalert.today/mcp). Free with an account. How to connect ChatGPT, Claude or Cursor.
RegAlert holds no document that amends or replaces this one. This is not a check that it is in force: confirm with the regulator.
“This document... has been created based on the Regulation on the Generation and Use of TR QR Code in Payment Services and the TR QR Code Principles and Rules document.”
More like this from CBRT
CBRT published 3 documents in the last 30 days. We email you each new one the day it's published.
Source: Central Bank of Republic of Turkey — original document · Summary generated with machine assistance and checked by an AI reviewer before publication; the authoritative text is the regulator's original document. How RegAlert works
In RegAlert: added