FAST – TR QR Code Technical Principles and Rules Guide

January 2025
Version 1.5

CENTRAL BANK OF THE REPUBLIC OF TÜRKİYE

FOR OFFICIAL USE ONLY

Transition Process to FAST-TR QR Code Application

1. Introduction ...................................................................................................................6

2. Scope and Basis ........................................................................................6

3. Definition and Abbreviations.......................................................................................6

4. General Principles .....................................................................................................7

5. QR Code Usage Models for the FAST System .............................................9

5.1. Business Payments (Sale) .................................................................................................................... 9

5.1.1. FAST Business Payment with Dynamic Verification Service Received from FAST System Participant .............. 9

5.1.2. FAST Business Payment with Static Verification Service Received from FAST System Participant ................. 12

5.2. Business Payments (Refund) ................................................................................................................... 14

5.2.1. Long QR Code Refund Flow Provided by the Business......................................................................... 14

5.2.2. Short QR Code Refund Flow Provided by the Business........................................................................... 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 Business ............................................................................... 18

6.1.2. Short QR Code Structure Provided by the Business ................................................................................. 29

6.1.3. Person-to-Person Payment QR Code Structure ................................................................................................ 30

7. Sample QR Code Verification Scenarios ......................................................33

7.1. QR Code Payment Scenario Resulting in Positive Verification ..................................... 33

7.2. QR Code Payment Scenario with Incorrectly Entered QR Code Flow Type .................................. 34

7.3. QR Code Payment Scenario with Incorrectly Entered Recipient Information ............................................. 35

8. References.....................................................................................................37

Version History

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	Business payment flows and transition provisions have been revised.
28 May 2021	1.1	Transition provisions have been revised. Business payments (refund) flows have been added. Template no. 31 has been added to the long QR code data structure provided by the business, 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, and the deadlines for generating and reading the Person-to-Person QR Code and for reading the QR Code Provided by the Business have been postponed to 31.12.2021, and it has been decided that the flow for generating the QR Code Provided by the Business shall be the same as the date specified in the Regulation.
11 September 2023	1.3	The transition provisions section has been updated. The business definition has been deleted and various updates have been made in this context. Incorrect CRC values have been corrected.
13 May 2024	1.4	The title and content of the transition provisions section have been updated.
02 January 2025	1.5	The Transition Process to FAST-TR QR Code Application has been updated. The Summary Security Value description in the long QR code data structure provided by the business has been updated.

Transition Process to FAST-TR QR Code Application

As of 2020 data, if the top 15 banks1 that execute the highest number of payments in terms of volume in the Account Payment transaction type in the CBRT Payment Systems are FAST System participants, within the scope of compliance with the rules in this document;

1. To prepare the infrastructure for generating the QR code offered in person-to-person payments, accepting FAST payments, and initiating FAST payments by reading the QR code, by 31.12.2021 at the latest,

2. To prepare the infrastructure to offer the possibility of initiating FAST payments by reading the long and short QR codes provided by the business by 31.12.2021,

3. Within the scope of the second paragraph of Provisional Article 1 of the Regulation, to prepare the infrastructure that enables accepting FAST payment by generating a long or short QR code for FAST workplace payment where dynamic verification service is received from a FAST System participant at their contracted workplaces, until the date specified in the second paragraph of Provisional Article 1 of the Regulation

is mandatory.

As of 2020 data, other FAST System participants, excluding the top 15 banks that execute the highest number of payments in terms of volume in the Account Payment transaction type in the CBRT Payment Systems, within the scope of compliance with the rules in this document;

1. Those who started message exchange as a FAST System participant before 01 January 2024,

a. All payment service providers offering FAST service to their users via mobile application shall prepare the infrastructure for accepting FAST payment by generating the QR code presented in person-to-person payments and for initiating FAST payment by reading the long and short QR code presented by the workplace along with the person-to-person QR code, by 30.04.2024,

b. Payment service providers offering the opportunity to accept payments to workplaces via payment cards or the FAST System shall prepare the infrastructure for initiating FAST payment by generating a long or short QR code for FAST workplace payment where dynamic verification service is received from a FAST System participant at their contracted workplaces, by 30.04.2024

2. Those who start 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 mobile application shall prepare the infrastructure for accepting FAST payment by generating the QR code presented in person-to-person payments and for initiating FAST payment by reading the long and short QR code presented by the workplace along with the person-to-person QR code, within at most 4 months from the date they go into production in the FAST System,

b. Payment service providers offering the opportunity to accept payments to workplaces via payment cards or the FAST System shall, within at most 6 months from the date they go into production in the FAST System, at their contracted workplaces, for FAST workplace payment where dynamic verification service is received from a FAST System participant

prepare the infrastructure for initiating FAST payment by generating a long or short QR code, is mandatory.

Those who start message exchange as a FAST System participant,

a. Payment service providers that do not yet offer the opportunity to accept payments to workplaces via payment cards or the FAST System but will start offering it as of a certain date shall prepare the infrastructure for initiating FAST payment by generating a long or short QR code for FAST workplace payment where dynamic verification service is received from a FAST System participant at their contracted workplaces, within at most 6 months from the date they start offering this service,

b. In the event that payment institutions become electronic money institutions by applying to the CBRT and obtaining the necessary permissions, they shall prepare the infrastructure for initiating FAST payment by reading the long and short QR code presented by the workplace, within at most 6 months from the date they start offering electronic money service

is mandatory.

Within the scope of compliance of FAST System participants with the rules in this document;

a. All payment service providers that started message exchange as a FAST System participant before 01 January 2025 and do not yet offer FAST service to their users via mobile application shall prepare the infrastructure for accepting FAST payment by generating the QR code presented in person-to-person payments and for initiating FAST payment by reading the long and short QR code presented by the workplace along with the person-to-person QR code, by 30.06.2025 at the latest,

b. All Payment Service Providers that start message exchange as a FAST System participant on or after 01 January 2025 shall, from the date they go into production in the FAST System (instead of the 4-month period given on the subject in the paragraphs above), within at most 6 months, prepare the infrastructure for accepting FAST payment by generating the QR code presented in person-to-person payments and for initiating FAST payment by reading the long and short QR code presented by the workplace along with the person-to-person QR code

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	Criterion	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 mobile application	by 30.04.2024
			All payment service providers that are FAST System participants on or after 01 January 2024 and 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 started message exchange as a FAST System participant before 01 January 2025 and do not yet offer FAST service via mobile application	by 30.06.2025
			All payment service providers that will be FAST System participants on or after 01 January 2025	within at most 6 months from the date they go into production in the FAST System
2	Long and short QR code presented by the workplace	Reading	All payment service providers that were 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 offer FAST service via mobile application	within at most 4 months from the date they go into production in the FAST System
			Banks and e-money institutions that started message exchange as a FAST System participant before 01 January 2025 and do not yet offer FAST service via mobile application	by 30.06.2025
			Banks and e-money institutions that will be FAST System participants on and after 01 January 2025	Within at most 6 months from the date it goes into production in the FAST System
			Payment institutions that are currently FAST System participants and that become electronic money institutions by applying to the TCMB and obtaining the necessary permissions	Within at most 6 months from the date it starts providing electronic money services
3	Dynamic verified long or short QR code presented by the merchant	Generation	All payment service providers that were FAST System participants before 01 January 2024 and that offer merchants the ability to accept payments via payment cards or the FAST System	Until 30.04.2024
			All payment service providers that are FAST System participants on and after 01 January 2024 and that will offer merchants the ability to accept payments via payment cards or the FAST System	Within at most 6 months from the date it goes into production in the FAST System
			All payment service providers that have started message exchange as FAST System participants and that do not yet offer merchants the ability 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 it starts providing the said service

[2] The process of initiating a FAST payment by reading the QR code should be evaluated as a whole.

[3] The process of accepting a FAST payment by generating the QR code should be evaluated as a whole.

1. Introduction

The "Regulation on the Generation and Use of TR QR Code in Payment Services" (the Regulation) and the "TR QR Code Principles and Rules" document annexed to this 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, were published in the Official Gazette dated 21 August 2020 and numbered 31220 and entered into force.

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 set out in the FAST System Reference Document, and FAST System participants are obliged to comply with the rules to which the Layer Services are subject.

2. Scope and Basis

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 (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 contained in the TR QR Code Principles and Rules document have been 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.

3. Definitions and Abbreviations

Within the scope of this document;

Recipient: The natural 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 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 TCMB,

FAST – TR QR Code: The TR QR Code to be used in payment transactions to be carried out through FAST,

Sender: The natural or legal person who gives a payment order from its 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 the BKM in which information relating to merchants accepting electronic payments is kept, for the purpose of facilitating the processes related to payment transactions made with the TR QR Code and preventing fraud and malicious use activities in the field of payments,

QR code presented by the merchant: 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 (P2P, person-to-person) payment transactions for the purpose of transferring the account information of the recipient of the payment to the sender,

Customer: Real or legal persons who transmit the payment for the price of goods and services offered by the business to the business,

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: Türkiye Cumhuriyet Merkez Bankası Anonim Şirketi,

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 which 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 acquirer participant at the time of the transaction of the recipient name/title and account number, as well as certain information specific to the business and the QR code,

Static QR code: A QR code with fixed content that can be used in more than one transaction,

Regulation: The Regulation on the Generation and Use of TR QR Code in Payment Services.

4. General Principles

1) FAST – Payment transactions made with TR QR Code are classified under two main usage scenarios:

a. Business payments: Payments made in return for the purchase of goods and services within the scope of commercial activity.

i. FAST business payments for which dynamic verification service is received from a FAST System participant

ii. FAST business 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 offered in person-to-person payments

2) All fields in the QR Code must be carried with a data structure compatible with the corresponding fields in the FAST System.

3) Although both static and dynamic QR code flows are supported in the FAST System, FAST business 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, and business 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 business 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 carrying this field into FAST messages without modification.

5) In business payments to be made with FAST – TR QR Code, the acquirer participant (the participant providing payment service to the business) must subject the payment coming through the FAST system to QR code verification and reject payments that fail verification with an appropriate rejection code.

6) In payments to be made using FAST – TR QR Code, all parties, especially payment service providers, remain 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 CBRT.

5. QR Code Usage Models for the FAST System

FAST-TR QR Code flows are addressed under two different headings: business payments and person-to-person payments.

5.1. Business Payments (Sales)

Business payments can be carried out in two different scenarios: FAST business payment for which dynamic verification service is received from a FAST System participant and FAST business payment for which static verification service is received.

5.1.1. FAST Business Payment for Which Dynamic Verification Service Is Received from a FAST System Participant

In FAST business 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.

5.1.1.1 Long QR Code Flow Offered by the Business

0. The acquirer participant creates a QR code specific to the purchase transaction upon the online request of the business. Since the generated QR code must be verified by the acquirer participant in subsequent stages, the following fields where verification will be performed must be present in the QR code and recorded in the participant's system:

a. QR code reference number,

b. Business account name/title,

c. Business account number,

d. Amount,

e. Last validity time,

f. QR Code Flow Type = 01

1. The business displays the generated QR code through a device that displays a QR code (virtual/physical POS, cash register, etc.).

2. The customer scans the QR code through their application, and if the QR code supports more than one payment flow (Credit Card, FAST, etc.), they select 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 checks the customer's balance and other necessary controls, creates the instant payment message and transmits it to FAST.

5. FAST performs its controls on the message, queues the transaction for fund reservation and routes the message to the acquirer participant.

6. In line with the incoming message, the acquirer participant performs the QR code verification for the transfer of the payment to the account of the business, who is the recipient, according to the following fields and sends the confirmation (T01) message to FAST:

a. QR code reference number,

b. Business account name/title,

c. Business account number,

d. Amount,

e. Last validity time,

f. QR Code Flow Type = 01,

7. FAST, upon receiving the T01 message, performs the necessary controls, initiates the reconciliation process and transmits the T02 result notification messages to the acquirer participant and the sender participant.

8. The acquirer participant informs the business, and the sender participant informs the customer, instantly about the result of the transaction.

5.1.1.2 Short QR Code (KK) Flow Offered by the Business

The short QR code (KK) application is a model that can be used in devices offered by the business but where the use of a long QR code is not possible (for example, older generation POS devices), in cases where all the 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 (acquiring participant) instead of information pertaining to the payment transaction. The customer who scans with the short QR code application obtains the payment-related information from the acquiring participant via the sending participant using this reference number, and after this stage initiates the actual payment transaction.

0. The Acquiring 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 Acquiring Participant in subsequent stages, the following fields where verification will be performed 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 sending participant.

3. The sending participant sends the reference information contained in the KK to the acquiring participant via KYS.

4. The acquiring participant verifies the information in the KK, including the reference, creates the payment and merchant information, and transmits it to the sending participant via KYS.

5. The sending participant presents the transaction to the customer's approval along with the masked information regarding the payment and the merchant.

6. The customer checks and approves the payment information in their application and transmits the actual payment initiation instruction to the sending participant.

7. The sending participant creates the payment message by performing the payment request, their customer's balance, and other necessary checks, and transmits it to FAST.

8. FAST performs its checks on the message, queues the transaction for fund reservation, and routes the message to the acquiring participant.

9. The acquiring participant, in line with the incoming message, performs the 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,

10. FAST, upon receiving the T01 message, performs the necessary checks, initiates the reconciliation process, and transmits the T02 result notification messages to the acquiring participant and the sending participant.

11. The acquiring participant instantly informs the merchant, and the sending participant informs their customer, about the result of the transaction.

5.1.2. FAST Merchant Payment with Static Verification Service Received from a FAST System Participant

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 displays to the customer the static QR code that they previously received 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 acquiring participant at the time of payment, the following information must be present 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 displayed QR code via their application and sees the payment and merchant information. If there is no amount in the QR code, the customer enters the amount information.

3. The customer approves the payment and transmits it to the sending participant.

4. The sending participant creates the payment message by performing the payment request, their customer's balance, and other necessary checks, and transmits it to FAST.

5. FAST performs its checks on the message, queues the transaction for fund reservation, and routes the message to the acquiring participant.

6. The acquiring participant, in line with the incoming message, performs the 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 [Verified if 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 checks, initiates the reconciliation process, and transmits the T02 result notification messages to the acquiring participant and the sending participant.

8. The acquiring participant instantly informs the merchant, and the sending participant informs their customer, about the result of the transaction.

5.2. Merchant Payments (Refund)

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 acquiring participant (acquirer), and participants who 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.

5.2.1. Long QR Code Refund Flow Provided by the Merchant

0. The acquiring participant creates the refund QR code, which also includes the message reference information of the purchase transaction previously realized with FAST, upon the merchant's online request. (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 sales transaction.)

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 through their application and views the payment information for which a refund is requested.

3. The Customer approves the refund request transaction.

4. The Sender participant, using the Related Message Reference Number (Id: 31/01) field received within the QR code, verifies the following for the payment for which a refund is requested:

a. Related message sender participant code

b. Related message date

c. Related message inquiry number and

d. Customer account information (whether the sale was made to the relevant customer), and creates and sends the Refund Request (H31) message via the FAST System.

5. The Merchant approves the refund transaction to be carried out based on the Refund Request (H31) message transmitted by the Acquirer participant (Optional).

6. The Acquirer 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 Sender 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 transmits the T02 result notification messages to the participants.

10. The Acquirer participant informs the merchant, and the Sender participant informs its customer, instantly about the result of the transaction.

5.2.2. Short QR Code Refund Flow Presented by the Merchant

0. The Acquirer (accepting) participant, upon the merchant's online request, creates the refund QR code containing the message reference information of the purchase transaction previously carried out with FAST. (The Short QR code Presented by the Merchant shall be used for this flow)

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 through their application, and the mobile application automatically transmits the QR information to its participant.

3. The Sender participant sends the reference information contained in the QR to the Acquirer participant via the KYS.

4. The Acquirer participant verifies the information in the QR, primarily the reference, and transmits the refund information to the Sender participant via the KYS. The amount information in the refund parameters must be equal to or less than the amount in the sale transaction.

5. The Sender participant, using the Related Message Reference Number field received within the information transmitted from the KYS, verifies the following for the payment for which a refund is requested:

a. Related message sender participant code

b. Related message date

c. Related message inquiry number and

d. 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 transaction transmitted by their participant and approves the transaction.

    6. The Sender participant creates and sends the Refund Request (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 Refund Request (H31) message transmitted by the Acquirer participant (Optional).

8. The Acquirer participant creates the Payment Refund (A09) message and transmits it to the Sender participant via the FAST System.

9. The Sender 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 transmits the T02 result notification messages to the participants.

11. The Acquirer participant informs the merchant, and the Sender participant informs its customer, instantly about the result of the transaction.

5.3. Person-to-Person Payments

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 scans the QR code shown through their application and sees the payment and recipient information in a masked form.

3. If the amount has not been entered, the Sender enters the payment amount and, approving the payment, transmits it to the sender participant.

4. The Sender participant performs the necessary checks, creates the instant 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 Acquirer participant.

6. The Acquirer participant, in line with the incoming message, performs the necessary verification and checks set out in the FAST Operating Rules for the transfer of the payment to the recipient's account and sends the confirmation (T01) message to FAST.

7. FAST, upon receiving the T01 message, performs the necessary checks, initiates the reconciliation process, and transmits the T02 result notification messages to the Acquirer participant and the Sender participant.

8. The Acquirer participant informs the recipient, and the Sender participant informs the sender, instantly about the result of the transaction.

6. FAST-TR QR Code Specifications

6.1. QR Code Data Organization and Naming Rules

The data within a QR code is organized in a tree structure as objects under the root4 part of this structure and is basically divided into two classes: simple data objects and data template objects. Simple data objects can store a single piece of information such as date, amount, reference number, while 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 the QR code has a data structure consisting of three parts:

• Field code: Consists of two digits between '00' and '99' and specifies 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 in which they are located. For example, the object specified by the field code '01' under the root and the object specified by the field code '01' under a data template with field code '62' refer to different data.

• Length: A two-digit number indicating the length of the data value of the object in characters and having a value between '01' and '99'.

• Data value: The value of the data with a length of at least one character and at most 99 characters.

Example:

An object with field code '02', length '08', and data value '20200530' is shown as '020820200530'.

The data value of the objects contained in the QR code supports the following data types:

• Character String (K): It is the data type that contains characters created in accordance with UTF-8 6 character encoding.

• Special Alphanumeric (ÖAN): It is the data type that contains digits between '0'-'9', letters in the alphabet, and punctuation marks. It is a subset of the Character String data type.

• Numeric (N): It is the data type that contains 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.

[4] Object that is not under any data template.

[5] The relevant information is 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 from 1 to 4.

• Conditional (K): The presence of the relevant data object in the QR code depends on certain conditions. For example, if only one of two data objects is desired to be present in the QR code, the presence statuses of these objects are specified as conditional. The necessary condition information is included in the descriptions of the relevant objects.

The QR Code Format Indicator, which is the first data object of the QR code, specifies the type of the QR code suitable for 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 given for the QR code usage models presented by the merchant and presented in person-to-person payments to be used in payments realized through FAST.

6.1.1. Long QR Code Structure Presented by the Merchant

In the table below, 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 are shown, and 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	Subfield Code:Name	Data Type	Length	Presence Status	Sample Data Value	Description
QR Code Format Indicator	00	-	N	02	Z	000201	It 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 with which the QR code data organization is compatible and have a fixed value of "01".
QR Code Type	01	-	N	02	Z	For static QR code: 010211 For dynamic QR code: 010212	It is used to distinguish between Static and Dynamic QR Codes. 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	ÖAN	Variable up to 99	At least one mandatory	For FAST: 30uuVD	The merchant must place the account information under the relevant field code of the relevant payment system in compliance with the workflows of the payment system. VD: Data value of the template uu: Total length of the data value (VD) of the template as characters.
02-03	Reserved for VISA.

Field Name Field
Code
Subfield
Code:Name
Data
Type Length Presence
Status
Sample Data
Value Description
04-05 Reserved for Mastercard. EMV members by EMVCo 06 are fields reserved for. -08 Reserved for EMVCo.
09-10 Reserved for Discover.
11-12 Reserved for Amex.
13-14 Reserved for JCB.
15-16 Reserved for UnionPay.
17-25 Reserved for EMVCo.
26-27 Used by BKM
28-29 Reserved for BKM.
30

• ÖAN
  to 99 up to variable n
  Z 30uuVD merchant account information data template to be used for FAST. account information data template.
  VD: Data value of the relevant template. uu: Data value (VD) of the relevant template in characters total length as characters.
  00:
  Universal
  Unique
  Identifier
  ÖAN 16 Z
  0016TR.GOV
  .TCMB.FAST
  Reverse domain name of FAST
  01:
  Merchant
  IBAN
  ÖAN 26 Z
  0126TR1234
  5678901234
  5678901234
  The account number that the merchant wants the payment to be sent by the customer to be transferred to number to which the payment to be sent by the customer is requested to be transferred to be transferred number Field to be carried in FAST A01 message field AlHesN If the EFT code contained in the merchant IBAN is then it is carried to the AlKK field. is carried to the AlKK field. 02:
  QR Code
  Flow Type
  N 2 Z
  For payment received from the FAST System participant via online service:
  from FAST System participant online service received for payment:
  020201
  Indicates the flow type to be used:
  belirtir:
  01: FAST System from the participant dynamic verification service received FAST merchant payment 02: FAST System from the participant static verification service received FAST merchant payment 04: Merchant payment refund

Field Name	Field Code	Sub Field Code:Name	Data Type	Length	Presence Status	Sample Data Value	Description
							In the FAST system, the participant has the obligation to transmit this field with the verification and verification result via the T01 message. Field to be carried in the FAST A01 message KtmSrvBlg + Krkd ++ KrkdAksTur
	20: Summary Security Value (Hash)	Numeric	32	Z	2032E200C0 14A30EFCDC 7E9F379CE0 766A68	The hash value is used to check whether this QR code was actually generated by the QR code generator. The QR code generator can fill it with a 32-character value of its own choosing when creating the QR code, can create summary information by mixing it with different information (customer-specific information such as TC identity number), or can assign random values.
31	-	Numeric	Variable up to 99	I	31uuVD	Merchant account information data template 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	Numeric	28	K	For the refund of the FAST message with query number 123456 sent by the participant with code 0062 dated 18.12.2020	Contains the FAST message reference information (date, sender participant code, query number) of the payment to be refunded. If the QR Code Flow Type is "04", it is mandatory. It is formatted as follows. [Trh][GonKK][SN] Trh: It is the message date of the payment to be refunded. 6 characters

Field Name Field Code	Sub Field Code:Name	Data Type	Length	Presence Status	Sample Data Value	Description
					0128201218 0062000000 0000001234 56	is entered in YYAAGG format. Example: 20201218 GonKK: Indicates the sender participant code of the payment to be refunded. It is entered as 4 characters. Example 0062 SN: Contains the FAST query number of the payment to be refunded. It is entered as 18 characters. Query numbers with fewer than 18 characters are padded with 0 at the front. Example: 000000000000123456
	32		It is used for mobile payments.			It will not be used for FAST.
	33-40		Reserved for TCMB
	41-46		Reserved for other payment systems in Turkey.			It will not be used for FAST.
Merchant Free Templates	47-48	Numeric	up to 99 variable	İ	47uuVD 48uuVD	Businesses may freely use these fields as simple data and/or data template in order to carry additional information related to payment and not defined in other fields of the table (for example, product information, check, 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.
Business Code	49		N	10	İ	49100023415 672	The unique reference number of the business in the Business Registry System. Values shorter than 10 digits will be completed with the '0' character on the left side.
Location	50		N	variable between 16-34	İ	For latitude 39.939423 and longitude 32.851791, the location value:	It is the location information that can be used for QR code payment transaction and created according to Decimal Degrees (DD) format. The location value consists of two parts of equal length, the first being latitude and the second being longitude.

Field Name	Field Code	Sub Field Code:Name	Data Type	Length	Presence Status	Example Data Value	Description
						501639939 423328517 91	For Latitude: EE.eeeeee and Longitude: BB.bbbbbb, the location value is specified as EEeeeeeeBBbbbbbb and no separator such as '.', ',', etc. is used in it. The number of 'e' and 'b' digits is equal and can be at least 6 and at most 15 depending on the precision level to be used.
QR Code Identity Template	51		ÖAN	up to 99 variable		51uuVD	It is the QR code identity template generated by the QR code producer. VD: Data value of the template. uu: Total length in characters of the data value (VD) of the template.
		00: Version Number	N	02	Z	For TR QR Code Version 1.0 data organization: 000210	It is the TR QR code version number. For version number "S.s", the data value is created as "Ss" without using punctuation marks.
		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 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 filled with the '0' character on the left side.
		03: QR Code Reference Number	ÖAN	variable up to 12	Z	030823451 017	The unique reference number generated for the QR code. It is provided by the business application or the QR code producer and is used for end-to-end verification, transaction recording or receipt generation.
							It can be specified by the business within the QR code or can be a marker for the consumer to enter the reference information into the mobile application they use. The field to be carried in the FAST A01 message is KtmSrvBlg + Krkd ++ KrkdRef
		04: Terminal Type	N	02	İ	For POS: 040202	The type of device on which the QR code is generated. Defined values: "01":Static QR code "02":POS/mPOS/ÖKC/Kiosk etc. payment acceptance software and hardware "03": ATM "04": Business application "05": Web "06": Payment service provider business application
		05: Terminal Device Serial Number	ÖAN	variable up to 23	İ	052312345 678901234 567890ABC	Distinctive value belonging to the QR code generating device or terminal (for example: terminal number and/or terminal serial number)
		06: Creation Time	N	12	Z	For 29 July 2020 at 15.30:59: 061220072 9153059	Time information when the QR code was generated. YYAAGGSSDDss YY: Year, AA: Month, GG: Day, SS: Hour (24 hours), DD: minute, ss: Second
		07: Last Validity Time	N	12	K	For 29 July 2020 at 16.30:59: 071220072 9163059	Last time information when the QR code is valid. YYAAGGSSDDss YY: Year, AA: Month, GG: Day, SS: Hour (24 hours), DD: minute, ss: Second Optional for static QR codes, mandatory for dynamic QR codes.

Field Name	Field Code	Subfield Code:Name	Data Type	Length	Presence Status	Sample Data Value	Description
Merchant Category Code	52		N	04	Z	52045499	ISO 18245-compliant Merchant Category Code (MCC) of the transaction. Examples of 4-digit codes include “5661” (shoe seller) or “5499” (Markets). If this field is not used, the value “0000” must be written.
Currency	53		N	03	Z	5303949	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: 541200000 0015050	Specifies the amount of the transaction. The last two digits specify the kuruş part, and the left side of the number is padded with “0” to complete the amount quantity to 12 digits. It is mandatory to use in dynamic QR codes. If this field is not present or is 0, the payment amount must be entered into the application by the customer. The field to be carried in the FAST A01 message is Ttr
Tip or Other Amount Indicator	55		N	02			It will not be used for FAST.
Tip or Other Amount Value (Fixed)	56		N	12			It will not be used for FAST.
Tip or Other Amount Value (Percentage)	57		N	05			It 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. "TR" for FAST

Field Name	Field Code	Subfield Code:Name	Data Type	Length	Presence Status	Sample Data Value	Description
Workplace Name	59		ÖAN	Variable up to 25	Z	5908ABC GIDA	The account name of the workplace. It is 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		ÖAN	Variable up to 15	Z	6008İSTANBUL	Workplace city name.
Postal Code	61		ÖAN	Variable up to 10	İ	610534100	The postal code of the workplace
Additional Data Fields Template	62	-	K	Variable up to 99	İ	62uuVD	It contains the additional data needed by the workplace for FAST. Since the total length of the field belonging to the template must be 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.
		01: Invoice Number	ÖAN	Variable up to 25	İ	0111TLK0123 0405	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	İ	02129031250 75000	The customer's mobile phone number. It can be specified by the workplace in the QR code or can be a sign for the consumer to enter the phone number into the mobile application they use.

Field Name	Field Code	Subfield Code:Name	Data Type	Length	Presence Status	Sample Data Value	Description
		03: Store Label	ÖAN	Variable up to 25	İ	0306AVMSTR	A label information that can be used to distinguish a specific store from others. It may be specified by the business 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	İ	04102315634 123	The customer's loyalty card number. It may be specified by the business 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	İ	06100518894 111	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 business 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 bill payments. The field to be carried in the FAST A01 message is RefBlg
		08: Payment purpose	ÖAN	2	Z	For dues payment: 080209	In the Instant Payment (A01) message, it can take the values in the FAST Message Structure and Transaction Types document for the payment purpose. If the QR Code Flow Type is "04: Business payment refund", this field must be entered as "00" and must not be carried in the FAST message.

Field Name Field
Code
Sub Field
Code:Name
Data
Type Length Presence
Status
Sample Data
Value Description
In the sales transaction, the field to be carried in the FAST A01 message OdmAmc 09: Additional Consumer Data ÖAN up to 3 variable İ Will not be used for FAST.
Business Language
Information
Template
64 K up to 99 variable variable
İ Will not be used for FAST
EMVCo
Reserved
Fields
65-79 K up to 99 up to variable
İ will not be used for FAST
Free
Templates 80-99 K to 99 up to variable
İ will not be used for FAST
CRC 63 ÖAN 04 Z 63043F2E
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) field (see: TR QR Code Principle and Rules)

Example:

Plain Text Value:

00020101021230920016TR.GOV.TCMB.FAST0126TR1234567890123456789012340202012032E200C014A30 EFCDC7E9F379CE0766A68491000234156725016399394233285179151910002100204001003082345101704 0202052312345678901234567890ABC06122007291530590712200729163059520454995303949541200000 00150505802TR5908ABC GIDA6008İSTANBUL61053410062750111TLK0123040502129031250750000306AVMSTR0410231563412306 10051889411108020963043F2E

QR Code:

Refund QR Code Example:

Plain Text Value:
00020101021230920016TR.GOV.TCMB.FAST0126TR0200950001000003540000100202042032E200C014A30 EFCDC7E9F379CE0766A68313201282012180960000000000000123456491000234156755193000210020409 500310REF0950D12040202052312345678901234567890ABC06122102150000000712221231000000520454 99530394954120000000150505802TR5913MERKEZ OLUMLU6006ANKARA620608020063048B01

QR Code:

6.1.2. Short QR Code Structure Provided by the Merchant

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
Determines the data structure in accordance with the usage model. determines.
"97": FAST KK
"96":
: FAST KK and BKM KK
QR Code Producer
Code N 04 Z 0010
Code of the QR code producer.
It will be given and recorded by BKM. Payment
Service Providers and TCMB deemed appropriate payment system operator to generate TR QR Code by applying to BKM for registration, they will be able to obtain a QR code producer code. Banks EFT codes will be used and also registration to have them done there is no need. 4 values shorter than the house on the left side with the “0” character will be filled. QR Code Reference Number ÖAN 12 Z REF666777 888 Not to follow each other in a way created workplace payment service provider based unique transaction reference number. Mandatory for FAST field. To be carried in FAST A01 message field:
KtmSrvBlg

• Krkd
  ++ KrkdRef
  Summary Security
  Value (Hash) ÖAN 32 Z
  E7054DB
  B31781D
  7A15F50
  43372E8
  02C5
  By the QR code producer
  Workplace specific to the generated QR code calculated security summary (hash) value. Workplace QR code producer, to check that the QR code data is the QR code it produced itself can use this field. can use this field.

[7] It is the short QR code indicator that both payment systems are supported by the workplace and the workplace bank, and the customer can choose between these payment systems.

CRC	ÖAN	04	Z	5BFD	It is the integrity control value calculated over the entire QR code (excluding this field) (see: TR QR Code Principles and Rules).
Other Data	ÖAN	variable up to 214	-	-	Will not be used for FAST.

Example:

Plain Text Value:

970010REF666777888E7054DBB31781D7A15F5043372E802C55BFD

QR Code:

6.1.3. Person to Person Payment QR Code Structure

In the table below, the person-to-person payment QR code data organization arranged for FAST and the corresponding fields to be carried in the instant payment message of the relevant fields are shown, 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	Subfield 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 presented 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 multiple transactions. "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 issued and registered by BKM. Payment Service Providers and payment system operators deemed appropriate by the TCMB 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 do not need to register separately. Values shorter than 4 digits will be padded on the left with the "0" character.
QR Code Reference Number	03		ÖAN	Variable up to 12	K	0310RFR234510 1	Unique reference number created specifically for the QR code. Mandatory if created as a dynamic QR code, 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 indicate the decimal part (kuruş, etc.). "0" is added to the left to complete the amount to 12 digits. 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 generated accordingly. VD: The data value of the template. uu: The total length in characters of the data value (VD) of the template
		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 the 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	The name and surname of the payment recipient. Field to be carried in the 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	İ	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 that the QR code data is the QR Code it generated itself.
Location	50		N	Variable between 16-34	İ	For Latitude: 39.939423 Longitude: 32.851791: 501639939423 32851791	It is the location information that can be used for the QR code payment transaction and is 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 being longitude. For Latitude: EE.eeeeee and Longitude: BB.bbbbbb, the location value is specified as EEeeeeeeBBbbbbbb and no separator such as '.', ',', etc. is used in it. The number of 'e' and 'b' digits is equal and can be at least 6 and at most 15 depending on the precision level to be used.
CRC	63	-	ÖAN	04	Z	63045E7C	It is the integrity check value calculated over the entire 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:
750210010212020400100310RFR2345101061220052914015907122005301401595412000000001505061520 126TR1234567890123456789012340712HASAN YILDIZ1002032032F93CC13E3E6410C1BADEEAF349E09A565016399394233285179163045E7C

QR Code:

7. Sample QR Code Verification Scenarios

This section examines sample scenarios regarding online verifications in FAST Workplace Payment (Section 0) flows where the FAST Workplace receives Dynamic Verification Service from a FAST System Participant.

In all of the following scenarios, it is assumed that Z-Bank customer Esat Koç, who wants to make a payment of 100 ₺ to ABC Kafe, which receives online service from F-Bank, will make the payment via QR code.

In this context, F-Bank generates the QR code containing the following basic information upon the request of ABC Kafe and records it in its system:

QR Code Information
QR Code Reference Number	444455556666
Workplace IBAN	TR123456789012345678901234
Workplace Name	ABC Kafe
Amount	100,00
Last Validity Time	200529120220
Layer Service Token	10

Esat Koç reads the QR code displayed with the Z-Bank mobile application and, seeing the payment information on his screen, selects the FAST payment and the account to which the payment will be made and confirms the payment.

The part of the flow up to this step is common to all scenarios, and only the subsequent steps will differ.

7.1. QR Code Payment Scenario Concluding with Positive Verification

Z-Bank generates the A01 instant payment message containing the following basic information and sends 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	01
++ KrkdRef	444455556666

FAST transmits 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 coming 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	ABC Kafe	AlAd
Amount	100,00	100,00	Ttr
Last Validity Time	200529120220	200529120215	(It 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 with the information recorded at F-Bank and the relevant fields in the A01 message coming from FAST. (For verification purposes, the security summary value (Hash) may also be used.)

F-Bank transmits the positive T01 message to FAST.

FAST performs the reconciliation and sends a positive result notification to F-Bank and Z-Bank. Banks inform their customers.

7.2. QR Code Payment Scenario Entered with Incorrect QR Code Flow Type

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 Kafe
AlHesN	TR123456789012345678901234
Ttr	100,00
KtmSrvBlg
+ Krkd
++ KrkdAksTur	02
++ KrkdRef	444455556666

FAST transmits 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 coming from Z-Bank via FAST
QR Code Reference Number	444455556666	444455556666	KtmSrvBlg + Krkd ++ KrkdRef
Business IBAN	TR123456789012 345678901234	TR12345678901234567 8901234	AlHesN
Business Name	ABC Kafe	ABC Kafe	AlAd
Amount	100,00	100,00	Ttr
Last Validity Time	200529120220	200529120215	(It is the time the A01 message is read by F-Bank, and is not sent by FAST.)
QR Code Flow Type	01	02	KtmSrvBlg + Krkd ++ KrkdAksTur

The information recorded at F-Bank and the relevant fields in the A01 message from FAST are used to verify the QR code.

Since the QR Code Flow Type registered in F-Bank's system and the QR Code Flow Type in the A01 message are not equal, F-Bank sends a negative (QR code could not be verified) T01 message to FAST.

FAST sends a negative result notification to F-Bank and Z-Bank. The banks inform their customers.

7.3. QR Code Payment Scenario Where Recipient Information Is Entered Incorrectly

Z-Bank creates the A01 instant payment message containing the following basic information and sends 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 transmits 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 coming from Z-Bank via FAST
QR Code Reference Number	444455556666	444455556666	KtmSrvBg + Krkd ++ KrkdRef
Business IBAN	TR123456789012 345678901234	TR12345678901234567 8901234	AlHesN
Business Name	ABC Kafe	XYZ Kafe	AlAd
Amount	100,00	100,00	Ttr
Latest Validity Time	200529120220	200529120215	(It 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

Since the QR Code Flow Type of the incoming A01 message is 01, the QR code is verified using the information recorded at F-Bank and the relevant fields in the A01 message from FAST.

Since the Business name matched with the relevant QR Code reference number in F-Bank's system and the AlAd field in the A01 message are not the same, F-Bank sends a negative (QR code could not be verified) T01 message to FAST.

FAST sends a negative result notification to F-Bank and Z-Bank. The banks inform their customers.

8. References

• 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 Generation and Use of TR QR Code in Payment Services

• TR QR Code Principles and Rules