iyzico Turkey Payment Gateway API
iyzico Turkey payment gateway REST API for Turkish merchants to accept credit/debit cards, BKM Express, bank transfers, installment payments, and international cards with Turkish banking ecosystem integration and BRSA-regulated compliance. Enables AI agents to manage card payment authorization for Turkey e-commerce automation, handle installment payment configuration for Turkish installment commerce automation, access BKM Express (Turkey national card network) for Turkish wallet automation, retrieve payment 3DS flow for Turkish card security automation, manage subscription and recurring payment for Turkey subscription automation, handle refund processing for Turkey order management automation, access sub-merchant registration for Turkey marketplace automation, retrieve fraud protection and bin check for Turkey payment security automation, manage payment reporting for Turkish financial reconciliation automation, and integrate iyzico with Turkish e-commerce, marketplace, and fintech platforms for end-to-end Turkey payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Turkey payments. PCI-DSS, BRSA. HMAC signature. TR. Card payment data.
⚡ Reliability
Best When
A Turkish merchant or marketplace wanting AI agents to automate card, installment, BKM Express, and subscription payment acceptance through iyzico's BRSA-compliant Turkey-native payment gateway.
Avoid When
BRSA REGULATORY COMPLIANCE: iyzico operates under Turkey Banking Regulation and Supervision Agency (BRSA); automated payment operations must comply with BRSA payment institution regulations; automated payment without merchant BRSA compliance creates regulatory violation. INSTALLMENT PLAN BANK-SPECIFIC CONFIGURATION: Turkish installment plans vary by card-issuing bank (3, 6, 9, 12 months); automated installment checkout must configure installment options per bank; automated generic installment offer creates non-eligible installment for some bank cards. 3DS FLOW MANDATORY FOR TURKISH E-COMMERCE: Turkish e-commerce requires 3DS authentication for card payments; automated checkout must implement 3DS redirect flow; automated server-side card charge without 3DS creates declined transaction for Turkish domestic cards. LOCALE AND CURRENCY TRY: iyzico transactions are in Turkish Lira (TRY); automated international checkout with foreign currency must use iyzico currency conversion; automated foreign currency amount without conversion creates currency mismatch error.
Use Cases
- • Accepting Turkish credit/debit cards from Turkey e-commerce merchant agents
- • Processing installment payments from Turkish consumer commerce agents
- • Handling BKM Express payments from Turkish national wallet agents
- • Managing sub-merchant marketplace payments from Turkish platform agents
Not For
- • Non-Turkish payments (iyzico is Turkey-focused; use Stripe for international)
- • Enterprise global payments (use Adyen or Checkout.com for enterprise global)
- • Mobile money payments (iyzico is card and bank transfer focused)
Interface
Authentication
iyzico uses API Key and Secret Key with HMAC-SHA256 signature for authentication. REST API with JSON. Istanbul, Turkey HQ. Founded 2013 by Barbaros Özbugutu. Acquired by PayPal in 2022. Products: Card processing, 3DS, installments, BKM Express, subscription, marketplace/sub-merchant. SDKs: Java, PHP, Python, .NET, Node.js, Ruby, Go. BRSA licensed. PCI DSS. Serves 30,000+ Turkish merchants. Competes with PayTR and Sipay for Turkey payments.
Pricing
Istanbul TR. PayPal subsidiary. Per-transaction fees in TRY. BRSA licensed. VAT registered.
Agent Metadata
Known Gotchas
- ⚠ HMAC-SHA256 SIGNATURE GENERATION: iyzico API requires HMAC-SHA256 signature of concatenated request parameters; automated request must implement correct signature algorithm; automated request without valid signature creates authorization error
- ⚠ CONVERSATION ID UNIQUENESS: iyzico requires unique conversationId per request for idempotency; automated retry must generate new conversationId; automated same-conversationId retry creates duplicate detection or status confusion for in-flight payments
- ⚠ INSTALLMENT NUMBER vs BANK ELIGIBILITY: iyzico installment requires BIN check to determine which installment counts are eligible for specific card; automated checkout must query installment options per card BIN; automated generic installment list creates invalid installment option error for non-eligible bank/count combinations
- ⚠ 3DS CALLBACK URL CONFIGURATION: iyzico 3DS requires callbackUrl registered in iyzico settings; automated 3DS checkout must use registered callback URL; automated unregistered callbackUrl creates 3DS flow rejection
- ⚠ SUB-MERCHANT APPROVAL BEFORE MARKETPLACE PAYMENTS: iyzico marketplace requires sub-merchant registration and approval; automated marketplace payment requires pre-approved sub-merchant ID; automated sub-merchant payment without prior approval creates sub-merchant not found error
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for iyzico Turkey Payment Gateway API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.