Every gateway, one interface.
A connector teaches orvacon how to talk to one payment gateway. They all implement the same contract — so adding or switching a provider is a configuration change, never a rewrite.
Iyzico
Raw-card and stored-card 3-D Secure, verified end-to-end against the gateway sandbox: authorize3DScapturerefundreconcile. Both flows are sandbox-verified.
PayTR
A planned connector behind the same contract. When it lands, point a config entry at it — your application code that calls orva.authorize() stays untouched.
Bank virtual POS
Turkish bank VPOS (3D Pay / 3D Secure) integrations, planned behind the same connector contract.
Supabase adapter
Generates a Postgres schema with default-deny row-level security out of the box.
Next.js adapter
App Router route handlers and webhook verification, wired up for you.
Postgres
Any Postgres works through the postgres driver — Supabase, Neon, RDS, or your own.
Every connector, the same shape.
A connector implements one set of operations. The orchestrator handles state, money typing, idempotency and signing around them — so a connector only has to map calls to its gateway.
Implement these against a gateway and it drops into any orvacon app.
Start with Iyzico.
Add the rest later.
Ship the verified Iyzico connector today; new gateways slot in behind the same contract without touching your application code.