- Requests signed by Iris with iyzico's IYZWSv2 HMAC-SHA256 — the secret key never leaves your tenant
- Hosted checkout form, 3-D Secure, BKM Express, BIN check and installment queries from the catalogued routes
- Cancel, refund and payment-detail routes for post-sale operations; sub-merchant onboarding for marketplaces
- Inbound webhooks verified with X-IYZ-SIGNATURE-V3 before anything is applied
- Live and sandbox hosts (api.iyzipay.com / sandbox-api.iyzipay.com) selected by the credential's environment
- Selectable as a payment provider on Iris payment records; 63 routes tryable from the integrations hub
iyzico Payment API Connector
Türkiye's iyzico payment API — checkout form, 3-D Secure, BIN check, installments, cancel and refund, sub-merchant onboarding — connected to Apivom Iris with your own API key pair: requests are signed by Iris, webhooks verified, and no card number ever passes through Apivom.
What you can do
Use cases
- Turkish card acceptance with local installments — Offer installment plans and domestic card schemes to Turkish customers through iyzico while the payment record and its status live in Iris.
- Refunds and cancellations from the support desk — Look up a payment by conversation id, then cancel or partially refund it from Iris, with the signed request and iyzico's answer logged on the record.
- Marketplace payouts to sub-merchants — Create and update sub-merchants and approve items for payout using the onboarding and item routes, under your own iyzico marketplace agreement.
iyzico is one of Türkiye's leading payment service providers, and its API covers the full card-payment lifecycle for Turkish merchants: a hosted checkout form, direct 3-D Secure authorisation, BKM Express, BIN and installment lookups, payment details, cancellation and refunds, card storage and sub-merchant onboarding for marketplaces. Apivom Iris connects to it as a selectable payment provider. The credential is your own API key and secret key; because iyzico signs every request with the IYZWSv2 scheme, Iris computes the HMAC-SHA256 signature itself and Apivom Atlas only forwards the finished headers — the secret key is never transmitted to or stored by Atlas. The environment on the credential decides between the live and sandbox hosts. iyzico's webhooks are received per tenant and verified with the X-IYZ-SIGNATURE-V3 header before they touch a payment record. Today the hosted-checkout automation in Iris is built for Stripe; iyzico operations run from the integrations hub (any catalogued route, writes behind a confirmation) and through verified webhooks, with every call logged in your tenant.
API key + secret key from your iyzico merchant panel. Iris computes the per-request IYZWSv2 signature (HMAC-SHA256 with a random x-iyzi-rnd) and Apivom Atlas forwards only the signed headers — the secret key is never sent to Atlas. Both keys are encrypted in your Iris tenant.
Frequently asked questions
Why does Iris sign the requests instead of Apivom Atlas?
iyzico's IYZWSv2 scheme needs the secret key to compute each signature. Keeping that computation inside Iris means the secret never leaves your tenant — Atlas receives only the signed Authorization and x-iyzi-rnd headers, forwards them and logs the call.
Is the hosted checkout flow automated for iyzico like it is for Stripe?
Not yet. iyzico is selectable as the provider on a payment record and its routes — including checkout-form initialisation — can be run from the integrations hub, and webhooks are verified and applied; the end-to-end automated Checkout Session flow currently exists for Stripe only.
Does Apivom handle card numbers?
No. The hosted checkout form collects the card on iyzico's side, and the integration is kept to SAQ-A scope — Apivom works with iyzico's payment and conversation ids, never with card data.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.