The payment provider decides what's possible
Payments touch every part of the e-commerce business — checkout UX, fraud protection, settlement timing, fees, compliance, refund handling.Stripe
Strengths: best-in-class developer experience, broad geographic coverage, deep feature set (Stripe Billing, Stripe Connect, Radar fraud).Trade-offs: not directly available for some markets (TR domestic acquiring is a workaround). Fees on the higher end.
Use when: global business, dev-team-led implementation, customer base is global rather than TR-only.
iyzico
Strengths: established TR market position, strong local features (3DS handling, BKM Express, taksit), TL-native, fully TR-acquired.Use when: TR-focused business, customer expects local payment options, taksit is part of the offering.
PayTR
Strengths: popular TR option, competitive fees, broad payment method support including BKM Express.Use when: cost-sensitive TR-focused business, comfortable with iyzico-equivalent feature scope.
Adyen
Strengths: enterprise-grade, supports the major card networks + many alternative payment methods globally, strong unified-commerce story.Use when: enterprise-scale, multi-channel, multi-region.
The TR-specific features that matter
- Taksit (instalments) — splitting purchases into monthly payments
- Bank-specific campaigns — promotional taksit terms by issuer
- BKM Express — wallet-style payment for TR consumers
- e-Fatura / e-Arşiv integration — tax invoice generation
- KDV handling — appropriate VAT treatment per product type
- TROY card support — TR domestic card scheme
The fee structure
- Per-transaction percentage (typically 1.5-3.5 %)
- Fixed fee per transaction
- Currency conversion fee
- Refund fee
- Chargeback fee (~15-30 USD per chargeback)
The headline rate is the easy comparison. The actual cost is the headline rate + the long tail of fees.
3DS / SCA compliance
- 3D Secure 2.x (3DS2) is the standard authentication flow
- EU SCA requires it for most transactions above a small threshold
- TR similarly enforces 3DS for most card transactions
Fraud handling
- Provider-side rules (Radar at Stripe, similar at others)
- Custom rules — block certain BIN ranges
- Manual review queue for flagged orders
- Chargeback management
Recurring billing / subscriptions
- Stripe Billing is the reference; comprehensive
- Local providers have subscription support but with smaller feature sets
- Dunning (failed-payment retry) is the under-invested part
- Card-on-file storage and PCI scope reduction
Multiple processors
For larger businesses:- Primary processor for most volume
- Secondary for failover
- Routing logic by region / card type / amount
One pattern we'd warn about
Switching processors mid-campaign or mid-subscription. Card-on-file migration is non-trivial.One pattern that always pays off
Reconciliation discipline. Daily / weekly reconciliation of transactions in your system vs the processor's settlement.What payment stack are you running?
