Tranzify
Payments in the Middle East

Payment methods in Türkiye in 2026: Havale and FAST transfers, cards with instalments, and cascading

What a checkout for Turkish payers needs in 2026: Havale and EFT bank transfers on the FAST rail, cards with instalments through local acquirers, wallets, and how a PSP cascades between SafePay, PusulaPays and card acquirers through an orchestration layer.

TTTranzify teamPayments engineering 5 min read
In this article
  1. The methods, and what each is for
  2. What the checkout needs
  3. Transfers in detail
  4. Cards and instalments
  5. Why cascading matters here
  6. Compliance
  7. Related reading

Türkiye pays with cards and with bank transfers, and for a payment business the second matters as much as the first. Havale, a transfer between accounts of the same bank, settles at once; EFT, a transfer between banks, runs during banking hours in its classic form and within seconds around the clock through FAST, the central bank’s instant system, up to the limit per transfer that FAST sets. Neither has chargebacks. For verticals where cards decline, they are the first method on the checkout; for e-commerce, cards with instalments stay first. This post goes through both and through the way a PSP cascades between providers in each.

The methods, and what each is for

Method Who uses it How the payer pays Notes
Havale and EFT, FAST for instant interbank transfers Payers in verticals where cards decline; large amounts Transfers from the banking app to the payee shown on the checkout Havale at once, EFT within seconds through FAST up to its limit, no chargebacks
Cards with instalments Most e-commerce Enters the card and chooses the instalments Domestic acquiring with the Troy scheme next to Visa and Mastercard; 3-D Secure
Apple Pay and Google Pay Mobile payers One tap Small amounts
Wallets and prepaid Younger payers, gaming Pays from the wallet or a prepaid code Per provider
Payouts on bank rails Withdrawals, refunds, partners Receives to an account Seconds on FAST

What the checkout needs

  1. Havale and EFT with the payee’s details shown and the payer’s transfer matched automatically by the provider.
  2. Cards with instalments: Turkish issuers and acquirers support instalments at the checkout; the local acquirer must be in the route.
  3. Apple Pay and Google Pay for small amounts on mobile.
  4. Payouts on the same bank rails for withdrawals and refunds.
  5. Lira and local acquiring: card payments in lira through a local acquirer; cross-border acquiring of Turkish cards declines far more often.

Transfers in detail

A transfer payment is created by the provider with a payee account, an amount and a reference; the checkout shows them to the payer with a deadline, the payer sends the transfer from the banking app, and the provider matches the incoming transfer to the payment by the reference, the amount and the sender’s name, then reports the result. The matching is where providers differ: coverage of banks, limits per transfer, speed of matching and the handling of a transfer with a wrong reference. A payment business therefore runs two transfer providers as two terminals of one route group, with priorities by approval rate, so that a transfer one cannot match goes to the other and the payer sees one checkout. Unmatched transfers are listed in the back office with the amount and the reference received, for the operator to resolve.

Cards and instalments

Turkish issuers and acquirers support instalments at the checkout for cards enrolled in the banks’ programmes, and e-commerce payers expect them for larger purchases; an acquirer outside those programmes loses the purchase. Troy, the domestic scheme, sits next to Visa and Mastercard, and a local acquirer accepts all three with 3-D Secure. A route group of two local acquirers with a cascade on declines, and a time window for each acquirer’s maintenance, is the standard setup; cards issued abroad go to the cross-border acquirer.

Why cascading matters here

Transfer providers in Türkiye differ in bank coverage, limits and matching speed. A client on Tranzify enables SafePay and PusulaPays as two terminals of one route group, with priorities by approval rate; a transfer that one cannot match goes to the other, and the payer sees one checkout. Cards sit in a second group of acquirers with their own cascade. The routing by amount decides which group comes first: for a deposit above a threshold the transfer, for a small purchase the card or the wallet.

Vertical First on the page Then Payouts
iGaming and betting Havale and EFT Cards cascaded across acquirers Bank transfers on FAST
Forex and crypto Havale and EFT above a threshold, cards below Wallets Bank transfers
E-commerce Cards with instalments Apple Pay and Google Pay, transfers for large amounts Refunds to the card

Compliance

The payment and electronic money institutions in Türkiye are licensed by the central bank; a client contracts with them under its own licence, and the platform runs under that contract. Tranzify integrates the providers, routes, journals every attempt for five years and calls the webhook; it never holds the funds. The client’s own licence and the providers’ policies decide which verticals are served; the catalogue shows each provider’s position.

The method page for Havale describes the flow step by step; the Türkiye country page lists the providers and the methods with their share; the industry pages for iGaming, forex and crypto show how transfer methods combine with cards in each vertical; the post on measuring cascade recovery explains how to judge whether the second provider earns its place.

See the platform on your own flows

Thirty minutes with an engineer, not a sales deck: your providers, your routing rules, your merchants' checkout.

  • ✓ Not a financial institution
  • ✓ Money never passes through us
  • ✓ Built to PCI DSS requirements

By sending the form you agree to the privacy policy.