CENTRAL BANK OF THE REPUBLIC OF TURKEY

FAST – TR QR Code Technical
Principles and Rules Guide

October 2021

Version 1.2

For Service Use

FAST-TR QR CODE TRANSITION PROVISIONS 4

1. INTRODUCTION 5

2. SCOPE AND LEGAL BASIS 5

3. DEFINITIONS AND ABBREVIATIONS 5

4. GENERAL PRINCIPLES 7

5. QR CODE USAGE MODELS FOR THE FAST SYSTEM 8

5.1. Merchant Payments (Sale) 8

5.1.1. Merchant Payment with Dynamic Verification Service Received from FAST Participant 8

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

5.2. Merchant Payments (Refund) 13

5.2.1. Long QR Code Refund Flow Presented by the Merchant 13

5.2.2. Short QR Code Refund Flow Presented by the Merchant 14

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 Presented by the Merchant 19

6.1.2. Short QR Code Structure Presented by the Merchant 26

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

7. SAMPLE QR CODE VERIFICATION SCENARIOS 31

7.1. QR Code Payment Scenario Resulting in Successful Verification 31

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

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

8. REFERENCES 35

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	Workplace payment flows and transition provisions have been revised.
28 May 2021	1.1	Transition provisions have been revised. Workplace payment (refund) flows have been added. Template 31 has been added to the long QR code data structure provided by the Workplace, 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 Person-to-Person QR Code and the reading of the QR Code Provided by the Workplace to 31.12.2021, and it has been decided that the date for the generation of the QR Code Provided by the Workplace shall be the same as the date determined in the Regulation.

FAST-TR QR Code Transition Provisions

Based on 2020 data, if the top 15 banks1 performing the highest number of Account Payment transactions in the CBRT Payment Systems become FAST participants, within the scope of compliance with the rules set forth in this document;

(1) To have the infrastructure ready by no later than 31.12.2021 for generating the QR code offered in person-to-person payments to accept FAST payments and for reading the QR code to initiate FAST payments,

(2) To have the infrastructure ready by 31.12.2021 to offer the possibility of reading the long and short QR codes provided by the workplace to initiate FAST payments,

(3) Within the scope of Article 1, second paragraph of the Transitional Provisions of the Regulation, to have the infrastructure ready by the date determined in Article 1, second paragraph of the Regulation that enables the generation of a long or short QR code to accept FAST payments for workplace payments where dynamic verification service is obtained from a FAST participant for the contracted workplaces

is mandatory. The CBRT is authorized to extend these periods.

FAST-TR QR Code Transition Provisions Table

No	QR Code Type	Reading2 / Generation3	Date
1	QR code presented in person-to-person payments	Reading + Generation	Until 31.12.2021
2	Long and short QR code presented by the merchant	Reading	Until 31.12.2021
3	Long or short QR code with dynamic verification presented by the merchant	Generation	Until the date determined by Article 1, second paragraph, of the Regulation

[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ı

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

[3] The process of generating the QR code and accepting a FAST payment 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, which is an annex to this Regulation, were prepared in order to ensure interoperability among the actors within the payments ecosystem by creating common rules and a language, to support innovative initiatives, and thereby to contribute to the widespread use of QR codes in payment services, and entered into force by being published 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 prepared 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.

QR code payment flows to be carried out through the FAST System are Layer Services defined in the FAST System Operating Rules and detailed 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, prepared in compliance with the Regulation and the TR QR Code Principles and Rules document, which is an annex to the Regulation, the workflows of payments made through the FAST System in accordance with the QR code usage models presented by merchants (eng. merchant-presented) and 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 contained 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 on the basis of 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 receiving a message sent to FAST,

BKM: Interbank Card Center Incorporated Company,

Dynamic Verification: the online verification, at the time of the transaction, by the receiving participant of certain transaction-specific information such as recipient name/title, account number and amount in a payment transaction initiated using a dynamic QR code,

Dynamic QR code: the QR code generated specifically for the payment transaction to be used and valid for single use,

EMVCo: the consortium consisting of American Express, Discover, JCB, Mastercard, UnionPay and Visa,

FAST: the Instant and Continuous Fund Transfer System operated by the CBRT,

FAST – TR QR Code: the TR QR Code to be used in payment transactions to be carried out via FAST,

Sender: the natural or legal person giving a payment order from their own payment account or without having a payment account,

Sending Participant: the participant transmitting a message to FAST for processing,

Merchant: the natural or legal persons who, within the framework of the contract they have concluded with the payment service provider, accept as the receiving party that a payment for the price of a good or service be made via FAST using QR codes produced within the scope of this document,

Merchant Registration System: the system holding information regarding merchants that accept electronic payment at BKM, for the purpose of facilitating the processes of 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 customers reading the QR code presented by the merchant through the application they use and initiating the payment transaction,

Law: Law No. 6493 on Payment and Securities Settlement Systems, Payment Services and Electronic Money Institutions dated 20/6/2013,

QR code: the two-dimensional code created for use in payment transactions by scanning; storing alphanumeric data, characters and symbols; consisting of three square pattern markers at the bottom left, top left and top right corners relative to the viewer; and having black and white modules in the form of square black-and-white dots or pixels,

QR code producer code: the code required to generate a TR QR Code,

QR Code Routing System (KYS): the structure enabling 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 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 transmitting the account information belonging to the recipient of the payment to the sender,

Customer: the natural or legal persons transmitting the payment for the price of the goods and services offered by the merchant to 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 fund depositing, transferring or withdrawal activity carried out upon the instruction of the sender or 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 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 acquiring participant at the time of the transaction of the recipient name/title and account number and certain information specific to the merchant and the QR code,

Static QR code: the QR code whose content is fixed and which 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.

4. General Principles

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

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

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

    ii. Merchant payments for which static verification service is received from a FAST 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 fields whose counterparts exist in the FAST System.

3) Although both static and dynamic QR code flows are supported in the FAST System, 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, and 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 acquiring participant is responsible for accurately reflecting this field in the generated QR code, while the sending participant is responsible for carrying this field into FAST messages without modification.

5) In merchant payments to be made with FAST – TR QR Code, the acquiring participant (the participant providing payment service to the merchant) must necessarily 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, remain obliged to fulfill all their other obligations arising from the Law and other relevant legislation and not otherwise specified in this document.

7) In order for FAST 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.

5. QR Code Usage Models for the FAST System

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

5.1. Merchant Payments (Sales)

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

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

In merchant payments for which dynamic verification service is received from a FAST 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 Presented by the Merchant

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

4. The sending participant performs the balance and other necessary checks of its customer, 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 acquiring participant.

6. In line with the incoming message, the acquiring participant performs the QR code verification for the transfer of the payment to the recipient merchant account 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, having received 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 informs the merchant, and the sending participant informs its customer, instantly about the result of the transaction.

5.1.1.2 Short QR Code (KK) Flow Presented by the Merchant

The short QR code (KK) application is a model that can be used in devices presented by the merchant 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, instead of the information belonging to the payment transaction, a unique reference number and summary information generated by the QR code generator (acquiring participant). The customer who scans the short QR code with their application obtains the information on which the payment is based from the acquiring participant through the sending participant by 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 later stages, the following fields where verification will be performed must be registered 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 QR code generated via the device displaying the 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 information to the sending participant.

3. The sending participant sends the reference information contained in the QR to the acquiring participant via the QR Routing Service (KYS).

4. The acquiring participant verifies the information contained in the QR, primarily the reference, creates the payment and business 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 business.

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 to perform fund allocation, 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 recipient business account 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,

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 business, and the sending participant informs their customer, about the result of the transaction.

5.1.2. Business Payment with Static Verification Service Obtained from FAST Participant

The workflow regarding the FAST – TR QR Code to be used in payments made to businesses that receive static verification service from a FAST participant and that will be realized via FAST will be as follows:

1. The business displays to the customer the static QR code that it previously obtained from the FAST participant and that contains the business 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 included in the QR code and the FAST participant must have registered this information in its system:

a. QR Code Reference Number

b. Business account name/title,

c. Business 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 displayed via their application and sees the information regarding the payment and the business. 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 to perform fund allocation, 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 recipient business account 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 [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 business, and the sending participant informs their customer, about the result of the transaction.

5.2. Business Payments (Refund)

Refunds of business payments made via 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 Business

0. The acquiring participant, upon the online request of the business, 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 Business 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 business displays the QR code generated via a device displaying the QR code (virtual/physical POS, cash register, etc.).

2. The customer scans the QR code via their application and views the payment information for which a refund is requested.

3. The customer approves the refund request transaction.

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

a. Relevant message sender participant code

b. Relevant message date

c. Relevant message query number and

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

5. The merchant approves the refund transaction to be realized 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 controls 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 account and sends the confirmation (T01) message to FAST.

9. FAST, upon receiving the T01 message, performs the necessary controls, initiates the reconciliation process, and transmits the T02 result notification messages to the participants.

10. The acquirer participant instantly informs the merchant, and the sender participant informs its customer, 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 online request of the merchant, creates the refund QR code containing the message reference information of the purchase transaction previously performed 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 via 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 QR Routing Service (KYS).

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

5. The sender participant, using the Relevant Message Reference Number field received from KYS, presents the payment for which a refund is requested to the customer's approval by verifying the

a. Relevant message sender participant code

b. Relevant message date

c. Relevant message query number and

d. Customer account information (whether the sale was made to the relevant customer). The customer views the information regarding the refund request transaction transmitted by its 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 realized 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 account and sends the confirmation (T01) message to FAST.

10. FAST, upon receiving the T01 message, performs the necessary controls, initiates the reconciliation process, and transmits the T02 result notification messages to the participants.

11. The acquirer participant instantly informs the merchant, and the sender participant informs its customer, 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 displayed via their application and sees the payment and recipient information in a masked form.

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

4. The sender participant performs the 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 segregation, and routes the message to the acquirer participant.

6. The acquirer participant, in line with the incoming message, performs the necessary verification and controls in the FAST Operating Rules for the transfer of the payment to the recipient account and sends the confirmation (T01) message to FAST.

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 instantly informs the recipient, and the sender participant informs the sender, 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" indicate different data from each other.

• 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 within the QR code supports the following data types:

• Character String (K): A data type containing characters created in accordance with UTF-8 6 character encoding.

• Özel Alfa Nümerik (ÖAN): ‘0’-‘9’ arasındaki rakamları, alfabedeki harfleri ve noktalama işaretlerini içeren veri tipidir. It is a subset of the Character String data type.

[4] An object that is not under any data template.

[5] The relevant information is taken from the document "TR QR Code Principles and Rules", 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.

• Nümerik (N): ‘0’-‘9’ arasındaki rakamları içeren veri tipidir. It is a subset of the Special Alphanumeric data type.

In the QR code data organization, the following notation is used for the presence status of objects:

• Zorunlu (Z): İlgili veri nesnesi karekodda her zaman bulunmalıdır.

• İsteğe Bağlı (İ): İlgili veri nesnesinin karekodda bulunması isteğe bağlıdır.

• Koşullu (K): İlgili veri nesnesinin karekodda bulunması birtakım koşullara bağlıdır. For example, if only one of two data objects is desired to be included 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 the 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 offered by the workplace to be used in payments made through FAST and offered in person-to-person payments.

6.1.1. Long QR Code Structure Provided by the Merchant

The following table shows the long QR code data organization provided by the merchant as 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 flows given in Section 5.1.1.1 and Section 5.1.2.

Table 1: Long QR code data organization provided by the merchant

Alan Adı	Alan Kodu	Alt Alan Kodu:Adı	Veri Tipi	Uzunluk	Bulunma Durumu	Örnek Veri Değeri	Açıklama
Karekod Biçim Göstergesi	00	-	N	02	Z	000201	It is the value used for the QR code data organization provided 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".
Karekod Türü	01	-	N	02	Z	For static QR code: 010211 For dynamic QR code: 010212	It is used to distinguish 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.
İşyeri Hesap Bilgileri	02-46	ÖAN	99’a kadar değişken	En az bir tane zorunlu	FAST için: 30uuVD	The merchant must place its account information under the relevant field code of the relevant payment system in a manner compatible with the payment system's workflows. VD: The data value of the template uu: The total length of the template's data value (VD) in characters.
	02-03	VISA için ayrılmıştır.					These are fields reserved by EMVCo for EMV members.
	04-05	Reserved for Mastercard.
	06-08	EMVCo için ayrılmıştır.
	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	Variable up to 99	Z	30uuVD	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.
		00: Universally Unique Identifier	ÖAN	16	Z	0016TR.GOV.TC MB.FAST	Reverse domain name of FAST
		01: Merchant IBAN	ÖAN	26	Z	0126TR1234567 8901234567890 1234	The account number to which the merchant wants the payment sent by the customer to be transferred, field to be carried in the FAST A01 message
		02: QR Code Flow Type	N	2	Z	For payment for which online service is received from a FAST participant: 020201	If the EFT code is within the AlHesN Merchant IBAN, it is moved to the AlKK field. Specifies the flow type to be used: 01: Merchant payment for which dynamic verification service is received from a FAST participant 02: Merchant payment for which static verification service is received from a FAST participant 04: Merchant payment return The participant receiving this field in the FAST system is obliged to verify this field and transmit the verification result with the T01 message. Field to be carried in the FAST A01 message KtmSrvBlg + Krkd ++ KrkdAksTur
		20: Summary Security Value (Hash)	ÖAN	32	Z	2032E200C014A 30EFCDC7E9F37 9CE0766A68	The hash value is used to check whether this QR code was actually generated by the QR code generator. The QR code generator may fill it with a value of its own determined length when creating the QR code, may create summary information by mixing it with different information (customer-specific information such as Turkish ID number), or may assign random values.
31	-	ÖAN	Variable up to 99	İ	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 return of the FAST message with query number 123456 sent by participant code 0062 dated 18.12.2020 0128201218006 2000000000000 123456	Contains the FAST message reference information (date, sender participant code, query number) of the payment to be returned. Mandatory if QR Code Flow Type is “04”. Formatted as follows. [Trh][GonKK][SN] Trh: Message date of the payment to be returned. Entered as 6 characters in YYMMDD format. Example: 20201218 GonKK: Indicates the sender participant code of the payment to be returned. Entered as 4 characters. Example 0062

Field Name
Field
Code
Sub Field
Code:Name
Data
Type
Length
Presence
Status
Sample Data
Value
Description
SN: Contains the FAST query number of the payment to be refunded. It is entered as 18 characters.
Query numbers shorter than 18 characters are padded with 0 at the front.
Example:
000000000000123456
32 Used for mobile payments. Will not be used for FAST.
33-40 Reserved for TCMB
41-46 Reserved for other payment systems in Türkiye.
Reserved.
Will not be used for FAST.
Merchant Free
Templates 47-48 ÖAN up to 99 up to variable
I
47uuVD
48uuVD
Merchants may freely use these fields in the form of simple data and/or data templates in order to carry additional information related to the payment and not defined in the other fields of the table (for example, product information, check, etc.) within the QR code. etc.) within the QR code. VD: The data value of the relevant template. uu: The total length in characters of the data value (VD) of the relevant template. Merchant Code 49 N 10 I 49100023415672 The unique reference number of the merchant in the Merchant Registry System. Values shorter than 10 digits will be completed with the '0' character on the left side. Location 50 N between 16-34 between variable I For latitude 39.939423 and longitude 32.851791, the location value is:
501639939423
32851791
It is the location information that can be used for QR code payment transactions and is created according to the Decimal Degrees (DD) format.
The location value is of equal length and the first is latitude and the second is longitude, two consists of the section.
Latitude: EE.eeeeee and Longitude:
For BB.bbbbbb, the location value is specified as EEeeeeeeBBbbbbbb and within it, a separator such as '.', ',', etc. is not used. The number of 'e' and 'b' digits is equal, and depending on the precision level to be used, it can be at least 6 and at most 15. QR Code Identity Template 51 ÖAN up to 99 variable 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 TR QR Code Version 1.0 data organization for:
000210
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 QR code producer's code. For FAST participants, the FAST participant code will be used (For detailed information, see:
TR QR Code Technical Principles and Rules
Field Name
Field Code
Subfield Code:Name
Data Type

Length	Presence Status	Example Data Value	Description	Document). Values shorter than 4 digits will be padded on the left with the character "0".	03: QR Code Reference Number	ÖAN	variable up to 12
							Z
		030823451017	Unique reference number generated for the QR code. Provided by the workplace application or QR code producer and used for end-to-end verification, transaction recording, or receipt generation. It can be specified by the workplace 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: KtmSrvBlg + Krkd ++ KrkdRef	04: Terminal Type	N	02	İ
		For POS: 040202	N	02	İ	For POS: 040202	Type of device that generated the QR code. 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
		05: Terminal Device Serial Number	ÖAN	Variable up to 23	İ	052312345678 901234567890 ABC	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: 061220072915 3059	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: 071220072916 3059	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.
Merchant Category Code	52		N	04	Z	52045499	The transaction's ISO 18245-compliant Merchant Category Code (MCC). Examples of 4-digit codes include “5661” (shoe seller) or “5499” (Markets). If this field is not used, the value “0000” must be written.

Field Name	Field Code	Subfield Code:Name	Data Type	Length	Presence Status	Sample Data Value	Description
Currency	53		N	03	Z	5303949	The transaction's ISO 4217-compliant currency code. For FAST, it must contain the fixed value “949”.
Amount	54		N	12	K	For 150,5: 541200000001 5050	Specifies the transaction amount. The last two digits specify the kuruş part, and the left side of the number is padded with “0” to complete the amount to 12 digits. It is mandatory for 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
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 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: The data value of the template. uu: The total length in characters of the data value (VD) of the template.
		01: Invoice Number	ÖAN	Variable up to 25	İ	0111TLK01230405	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	İ	0212903125075000	The customer's mobile phone number. It can be specified by the workplace in the QR code or can be an indication 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 specific store from others. It can be specified by the workplace in the QR code or can be an indication for the consumer to enter the store label into the application they use. The consumer's application that reads the QR code can display this store information on the screen.
		04: Customer Loyalty Number	ÖAN	Variable up to 25	İ	04102315634123	The customer's loyalty card number. It may be specified by the merchant within the QR code or may be an indication for the consumer to enter the loyalty number into the mobile application they use.
		06: Customer Number	ÖAN	Variable up to 25	İ	06100518894111	The tag 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 an indication for the customer to enter the tag number into the mobile application they use. It can be used as the 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: Merchant payment return”, this field must be entered as “00” and must not be carried in the FAST message. The field to be carried in the FAST A01 message in the sales transaction is OdmAmc

Field Name	Field Code	Sub Field Code:Name	Data Type	Length	Presence Status	Sample Data Value	Description
		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	63040D9E	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.FAST0126TR1234567890123456789012340202012032E20 0C014A30EFCDC7E9F379CE0766A684910002341567250163993942332851791519100021002040 010030823451017040202052312345678901234567890ABC061220072915305907122007291630 5952045499530394954120000000150505802TR5908ABC GIDA6008İSTANBUL61053410062750111TLK0123040502129031250750000306AVMSTR04102315 634123061005188941110802096304513B

QR Code:

Return QR Code Example:

Plain Text Value:

00020101021230920016TR.GOV.TCMB.FAST0126TR0200950001000003540000100202042032E20 0C014A30EFCDC7E9F379CE0766A683132012820121809600000000000001234564910002341567 55193000210020409500310REF0950D12040202052312345678901234567890ABC061221021500

0000071222123100000052045499530394954120000000150505802TR5913MERKEZ OLUMLU6006ANKARA620608020063048B01 Karekod:

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
Sample Data
Value
Description
QR Code Format
Indicator N 02 Z
For FAST KK:
97
Determines the data structure in line with the usage model.
"97": FAST KK
"96"
7
: FAST KK and BKM KK
QR Code Producer Code N 04 Z 0010
Code of the QR code producer. It will be given and registered by BKM. For FAST participants, the FAST participant code will be used and they do not need to register separately. For short values of 4 digits, the left side will be filled with the "0" character. QR Code Reference Number ÖAN 12 Z REF666777888 Unique transaction reference number on the basis of the merchant payment service provider, generated in a non-sequential manner. It is a mandatory field for FAST. Field to be carried in FAST A01 message:
KtmSrvBlg

• Krkd
  ++ KrkdRef

[7] This is the short QR code indicator where both payment systems are supported by the merchant and the merchant's bank, and the customer can choose between these payment systems.

Summary Security Value (Hash)	ÖAN	32	Z	E7054DBB317 81D7A15F504 3372E802C5	Security summary (hash) value calculated specifically for the QR code produced by the merchant by the QR code producer. The merchant QR code producer can use this field to check that the QR code data is the QR code it produced.
CRC	ÖAN	04	Z	5BFD	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:

6.1.3. Person-to-Person Payment QR Code Structure

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
Subfield
Code:Name
Data
Type
Length
Presence
Status
Example Data
Value
Description
QR Code Format
Indicator 75 N 02 Z
TR QR Code
Version 1.0 data organizatio n for:
750210
In person-to-person payments offered for QR code data organization the value used. 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 created without using a punctuation mark as "Ss". It is formed as "Ss". QR Code Type 01 N 02 Z Static for QR code:
010211
Dynamic
QR code for: 010212
Used for Static and Dynamic QR Code distinction Data value:
"11": Static QR Code where the same QR code is used for more than one transaction for.
"12": Dynamic QR Code where a different QR code is used for each transaction .
QR Code
Producer Code 02 N 04 Z 02040010
QR code producer's code. By BKM will be given and recorded.
For FAST participants, FAST participant code will be used and additionally registration is not required.
For values shorter than 4 digits, the left side is filled with "0" character.
QR Code
Reference
Number
03 ÖAN up to 12 up to variable
K
0310RFR234
5101
Unique reference created specifically for the QR code number.
In case of creation as a dynamic QR code mandatory, for static QR codes optional.
Field to be carried in FAST A01 message:
KtmSrvBlg

• Krkd
  ++ KrkdRef
  Creation
  Time 06 N 12 İ
  29 May 2020 at 14.01:59 for:
  0612200529
  140159
  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 İ 30 May 2020 at 14.01:59 for:
  0712200530
  140159
  Last time the QR code is valid information.
  YYAAGGSSDDss
  YY: Year, AA: Month, GG: Day, SS: Hour (24 hour), DD: minute, ss: Second Amount 54 N 12 İ for 150,5 5412000000 015050 Specifies the amount of the payment. The last two digits indicate the decimal part (kuruş, etc.) shows. 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 up to 99 up to variable
Z 61uuVD application to be used for FAST template.
The total length of the field belonging to the template due to being a maximum of 99 characters, the sub-fields 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: The template's data value. uu: The template's data value (VD) total length in characters 01:
Account
Number
(IBAN)
ÖAN 26 Z
0126TR123
456789012
345678901
234
The account (IBAN) number that the payment recipient wants to use to receive the payment. number.
Field to be carried in the FAST A01 message:
AlHesN
02:
Card
Number
N 16 Will not be used for FAST.
04:
Easy Address
Type
K 01
Will not be used for FAST.
05:
Easy address value
ÖAN up to
50 variable
Will not be used for FAST.
07:
Payment
Recipient's
Name and
Surname
ÖAN
2-26 between variable
Z
0712HASAN
YILDIZ
Payment recipient's name and surname.
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 to 32 up to variable
  I
  2032A23ED
  34AEAE0F7
  12AEFCB90
  54ED180EC
  By the application that generates the QR code the calculated summary security (hash) value.
  The application used can use this field to check that the QR code data is the QR code it generated itself.
  Location 50 N
  16-34 between variable
  I
  Latitude:
  39.939423
  Longitude:
  32.851791 for:
  501639939
  423328517
  91
  For QR code payment transaction the location information that can be used 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.
  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	63049372	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:
750210010212020400100310RFR2345101061220052914015907122005301401595412000000015 05061520126TR1234567890123456789012340712HASAN YILDIZ1002032032F93CC13E3E6410C1BADEEAF349E09A565016399394233285179163047CE6

QR Code:

7. Example QR Code Verification Scenarios

This section examines example scenarios regarding online verifications in the Workplace Payment (Section 5.1.1) flows where the Dynamic Verification Service is received from the FAST 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 Kafesi, which receives online service from F-Bank, will make the payment with a QR code.

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

QR Code Information
QR Code Reference Number	444455556666
Business IBAN	TR123456789012345678901234
Business 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 the screen, confirms the payment by selecting the FAST payment and the account to which the payment will be made.

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 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	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	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 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. The banks inform their customers.

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

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
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	(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 QR code is verified with the information recorded at F-Bank and the relevant fields in the A01 message coming from FAST.

Since the QR Code Flow Type recorded in F-Bank's system and the QR Code Flow Type in the A01 message are not equal, F-Bank transmits 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 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 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
Merchant IBAN	TR123456789012 345678901234	TR12345678901234567 8901234	AlHesN
Merchant Name	ABC Kafe	XYZ 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

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

Since the Merchant 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 transmits 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

• Regulation on the Generation and Use of the TR QR Code in Payment Services

• TR QR Code Principles and Rules