When orvacon is the right tool.
orvacon fits when you take card payments through your own gateway account and want the orchestration handled cleanly. It's deliberately not a fit for everything — here's both sides.
Checkout you own
A storefront or app that charges customers directly. You keep the cart and product logic; orvacon runs authorize3DScapturerefund and keeps the ledger straight.
Subscriptions & recurring
Charge on a cycle from your own scheduler. Today you wire the recurring authorize/capture yourself; a subscription kit that schedules and retries is on the roadmap.
Avoiding gateway lock-in
Start on one provider and keep the option to add or switch. Because application code calls one interface, moving to a new connector is a configuration change — not a rewrite.
Turkish-market products
Apps that need Iyzico with proper 3-D Secure today, and bank virtual POS later — all behind the same code path, with money typed in integer kuruş and a tamper-evident ledger.
Where you'd want something else.
orvacon never custodies money. Anything that depends on holding, splitting, or moving other people's funds needs a different category of tool.
Marketplaces with split payouts
Paying out many sellers from one charge needs fund custody and split settlement — orvacon doesn't hold balances, so it can't split them.
Wallets & stored balances
Holding customer balances is money custody and the regulation that comes with it. That's explicitly out of scope.
A full e-commerce platform
No catalog, cart, inventory, or storefront. orvacon handles the payment, not the shop around it.
Unsure if your case fits? It's a good sign if money flows straight from the cardholder to your own gateway account. If you need to hold or redistribute other people's money, look at a payment facilitator instead.
Sound like your stack?
If you charge through your own gateway account, orvacon takes the orchestration off your plate — cleanly, and in your own runtime.