- Request, capture, void and refund payments; manage payment instruments and customers
- Disputes, payouts, balances, reserve rules and marketplace sub-entities from the account routes
- Live vs sandbox chosen by the key prefix (sk_ / sk_sbox_); per-merchant base URL honoured when issued
- Inbound webhooks verified with your Checkout.com webhook secret before they reach a payment record
- 206 catalogued routes (81 read-only), selectable as a payment provider on Iris payment records and tryable from the hub
Checkout.com Unified Payments API Connector
Checkout.com's Unified Payments API — payments, captures, refunds, payment instruments, customers, disputes, payouts and account entities — connected to Apivom Iris with your own secret key, live or sandbox by prefix, per-merchant base URLs supported and webhooks verified with your webhook secret.
What you can do
Use cases
- Multi-currency acquiring from the CRM — Take and capture payments in the currencies and regions your Checkout.com account is enabled for, with the payment record and its status kept in Iris.
- Dispute and refund handling with context — When a chargeback lands, open the dispute, pull the original payment and refund or submit evidence from the customer's Iris record.
- Marketplace sub-entity operations — Read sub-entities, payout schedules and reserve rules for the sellers on your platform and keep their payment instruments current from one place.
Checkout.com is a global acquirer and payment processor whose Unified Payments API handles the full transaction lifecycle — payment requests, authorisations, captures, voids and refunds — alongside payment instruments, customers, disputes, payouts, balances and, for platforms, the sub-entities, reserve rules and payout schedules of a marketplace. Apivom Iris connects to it as a selectable payment provider. The credential is your own secret key: a live key or a sandbox key (sk_sbox_…) picks the environment, and if Checkout.com has issued your account a dedicated base URL, that host is used for every call. Webhooks are received per tenant and verified with the webhook secret you configure in the Checkout.com dashboard before anything is applied to a payment record. Apivom Atlas catalogues 206 routes, 81 of them read-only; an administrator can run any of them from the Iris integrations hub — reads directly, writes behind a confirmation — with request and response logged in your tenant. The automated hosted-checkout workflow in Iris is currently built for Stripe; Checkout.com operations run through the hub and verified webhooks.
Your Checkout.com secret key (sk_… live, sk_sbox_… sandbox) sent as Bearer per request; mode follows the prefix. Optional per-merchant base URL (https://{prefix}.api.checkout.com) and webhook secret for signature verification. All encrypted in your Iris tenant; Apivom Atlas stores nothing.
Frequently asked questions
Which Checkout.com environment does the connector use?
Whichever your key belongs to: an sk_sbox_ key routes to the sandbox, an sk_ live key to production. If your account has a merchant-specific base URL, store it with the credential and every call uses it.
How are Checkout.com webhooks verified?
Each tenant has its own receiver; the webhook secret from your Checkout.com workflow configuration is used to check the signature on every inbound notification. Unsigned or badly signed events are rejected and never touch a payment record.
Does Apivom handle card numbers?
No. Cards are tokenised on Checkout.com's side (Frames, hosted pages or your own PCI-compliant front end); Apivom works with payment, instrument and customer ids only.
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.