Skip to content

Search

"Disputes"

73 articles found

Illustration of personal data protection under the Turkish Personal Data Protection Law (KVKK)

Merchant & POS

What is the Personal Data Protection Law (KVKK)?

The Personal Data Protection Law was adopted by the Grand National Assembly of Turkey on 24/03/2016 and published in Official Gazette No. 29677 on 07/04/2016. It protects individuals' rights in the processing of personal data and sets the rules that data controllers must follow.

Illustration of ways merchants can reduce chargebacks on card transactions

Chargeback

How to Reduce Chargebacks (For Merchants)

Chargeback is inherent to card transactions, so it may be impossible to prevent entirely, but taking precautions keeps the risk to a minimum. Here are the key points merchants should pay attention to in order to reduce chargebacks.

GO Secure Payment logo

Merchant & POS

What Is Secure Payment (GO)?

GO Secure Payment is a system developed by BKM that verifies cardholders using a one-time password (OTP) during online purchases made with TROY cards, providing banks with a secure verification platform without needing to store card data.

Illustration of a Card Not Present (CNP) online payment transaction

Credit Card

What Is a CNP (Card Not Present) Transaction?

CNP refers to a transaction made through a website or a company's own app payment page, where the card is not read by any device and its details are entered manually. It is short for Card Not Present.

ISO 8583 field 13 local transaction date

ISO 8583

ISO 8583 Field Descriptions (F13)

DE 13 — Date, Local Transaction: the date on which the transaction took place at the point of transaction (ATM, POS). It is 4 digits in MMDD format.

Example of RRN printed on a POS receipt used to trace ISO 8583 transactions

ISO 8583

ISO 8583 Field Descriptions (F37)

F37 - RETRIEVAL REFERENCE NUMBER: a 12-digit alphanumeric value generated by the Acquirer that initiates the transaction. It must be printed on the POS receipt or ATM slip. RRN is the reference number that allows a transaction to be located.

Diagram illustrating the structure of an ISO 8583 message field

ISO 8583

ISO 8583 Field Descriptions (F41)

F41 - CARD ACCEPTOR TERMINAL IDENTIFICATION: the terminal where a transaction took place. An 8-character alphanumeric value generated by the acquirer bank and assigned to the POS, managed as a unique terminal number at the acquirer.

Diagram illustrating the ISO 8583 F42 card acceptor identification code field

ISO 8583

ISO 8583 Field Descriptions (F42)

F42 - CARD ACCEPTOR IDENTIFICATION CODE: the merchant number of the terminal where a transaction took place. It is a 15-character alphanumeric value. Transactions are settled to the merchant's account based on the merchant number in this field.

ISO 8583 field table showing the F38 authorization identification response field

ISO 8583

ISO 8583 Field Descriptions (F38)

DE 38 (AUTHORIZATION IDENTIFICATION RESPONSE) is the authorization code generated when a transaction is approved. It is alphanumeric, 6 characters long, and left empty for declined transactions.

Diagram illustrating ISO 8583 field F23, the card sequence number

ISO 8583

ISO 8583 Field Descriptions (F23)

F23 - CARD SEQUENCE NUMBER: Information used to distinguish cards sharing the same card number. For example, the Card Sequence Number is incremented by 1 when a card is renewed. In an authorization transaction, if the F22 value is '05x'...

Merchant choosing between a bank POS and a virtual POS service

Merchant & POS

Is it mandatory to work with a bank to get a POS terminal?

The answer depends on the type of POS terminal. A physical POS (GPRS, Dial-Up, IP, or cash-register POS) requires working with a bank. A virtual POS can also be obtained from a payment institution without a separate bank agreement.