What we do
Tools
Industries
Department
How we workLet's talk →
Home/Checkout.com
Checkout.com

Checkout.com for the Team Integrating It: Routes In, Webhooks and Reconciliation

Looking for Checkout.com itself, or its Dashboard? That's at checkout.com. This page is for the people around it: whoever is deciding whether to use it, whoever is wiring it in, and whoever has to make its payouts agree with the books. Checkout.com is a payment gateway and acquirer in one, with cards and local payment methods through a single Unified Payments API.

Where Checkout.com stops

It processes the payment, and everything that's supposed to happen next is left to your team.

Stuck on Checkout.com? Let's solve it →
Which part you need

Evaluating it? Pricing is quoted through sales, not a public rate card, so the questions you ask before signing matter. See the checklist below.

Integrating it? Pick a front end first: Flow, the Hosted Payments Page, Payment Links, or the API on its own. Then build the webhook receiver.

Reconciling it? You need three of its reports together, not the payout report alone.

Which Checkout.com integration route fits

Route Suits What you still own
Flow, its pre-built payment UI embedded in your checkout A site or app that wants the payment form on its own page, with local methods shown per customer. The webhook server that confirms each payment. Flow's own setup steps include it.
Hosted Payments Page Teams that want the least card handling on their side. Customers leave your site to pay, sessions expire after 24 hours, and the page can't sit in an iframe.
Payment Links Invoices, phone orders and B2B payments, with no checkout to build. Matching each paid link back to the invoice or order it was sent for.
Unified Payments API, no front end Platforms with their own payment flow, recurring charges or server-to-server payments. Everything around the call: authorization and capture timing, retries and idempotency.
A platform plugin Stores on a supported platform. Checkout.com maintains a WooCommerce plugin and lists Shopify and Salesforce Commerce Cloud among its partners. Getting payment and payout data out of the store and into accounting or an ERP.

Questions for the Checkout.com sales call

Enterprise payment contracts are negotiated, so the answers vary by business.

  • How are our fees broken down, and where do we see each part?

    Its reports separate scheme fees from Checkout.com's own charges. Ask how your pricing maps to those lines, so finance can check the invoice against them.

  • Which local payment methods are live in each market we sell in?

    The single API is the selling point. Coverage by country and method is what decides whether you still need a second processor.

  • Which currencies do we settle in, and how often are payouts made?

    This decides how many currency accounts finance reconciles and how long cash sits before it lands.

  • Can our reporting run monthly in UTC from the start?

    Checkout.com recommends monthly reports to match its invoices, and switching is done through your account manager.

  • How will disputes reach us?

    There's a Disputes API and webhooks for dispute events. If nobody builds against them, disputes live in the Dashboard and deadlines slip.

How Checkout.com webhooks behave, and the bugs that follow

Assuming events arrive once and in order

How you'll know: An order flips to paid, then back to pending, because a late event overwrote a newer one.

Fix: Delivery is at least once and not ordered. Store each event's ID, skip repeats, and only move a payment's state forwards.

Skipping the signature check

How you'll know: The endpoint accepts anything posted to it.

Fix: Each webhook carries an HMAC in the Cko-Signature header, signed with the key set on the workflow's webhook action. Verify it against the raw body before trusting the payload.

A receiver that was down for an hour

How you'll know: Payments from the outage window never reached your order system.

Fix: Checkout.com retries up to eight times, starting five minutes after a failure, and lets you resend from the Dashboard or API. Add a daily check against the API for anything still missing.

Reconciling Checkout.com payouts, fees and invoices

This follows Checkout.com's own reconciliation guidance. Each report answers a different question.

  1. 1

    Check balances for the period

    Run the Balance Report for the month, then the Financial Actions by Date Range Report for the same dates. The first gives opening and closing balances per currency account. The second lists every action behind them.

  2. 2

    Tie fee categories out

    Filter Financial Actions by action type and breakdown type, then match the totals to the fee fields on the Balance Report.

  3. 3

    Match each payout to the bank

    Take each payout ID from the Payouts Report, open the Financial Actions by Payout ID Report for it, and match the total to the deposit on your bank statement. That's also where each payment links back to an order.

    Watch for: a payout can include fees charged the month before, so payouts won't tie to an invoice. Use the Balance Report for invoice totals.

  4. 4

    Reconcile the monthly invoice

    Check Checkout.com's invoice against Balance Report totals, with Financial Actions by Date Range for line detail.

Let's talk

Checkout.com is taking payments. The ledger is the part that lags.

n-frames builds the parts around Checkout.com: the webhook receiver that keeps order status right, the dispute routing with the order attached, and a reconciliation that runs these reports into your accounting system or ERP every day. If you also run Stripe or Adyen in some markets, both processors land in one view.

Reconcile Checkout.com daily →

Questions people ask

What is Checkout.com?

A global payment gateway and acquirer. It takes card payments and many regional payment methods through one API, which it calls the Unified Payments API, so a business doesn't need a separate integration for every country or method.

How much does Checkout.com cost?

It doesn't publish a standard rate card. Pricing is per transaction and depends on region, card type, payment method and volume, and it's negotiated with Checkout.com directly. Ask for a breakdown you can match to the fee lines in its reports.

What's a good Checkout.com alternative?

Stripe, Adyen and Braintree come up most, each with different strengths in coverage, pricing and developer tools. Our Adyen vs Stripe page compares two of them. We don't resell any of them; we connect whichever one you choose.

What is Checkout.com's unified payments API?

Its name for the core integration: one API for card acceptance, alternative payment methods and payment management across markets, rather than a separate integration per region. It's the route to use when you don't need its front-end components.

Is Checkout.com a payment gateway or a full processor?

Both. It captures and routes the payment like a gateway and acts as the acquirer that settles funds to the merchant, so you don't need a separate acquiring bank behind it.

Does Checkout.com integrate with other business systems?

Through its API, webhooks, reports and a set of platform plugins such as WooCommerce. Getting payments, fees and payouts into accounting or an ERP automatically is custom work against those, and it's what n-frames builds for Checkout.com merchants.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.