Connect BigCommerce to Checkout.com to run card payments with local methods, 3DS flows, and cleaner reporting, while reducing checkout drop-offs across markets.
• Bigcommerce checkout routes card payments to Checkout.com via a payment app/integration that exchanges order totals, currency, and customer context at time of authorization.
• Payment intents/transactions are created in Checkout.com and mapped back to the Bigcommerce order using stored references (order ID, transaction ID, and PSP reference).
• Authorization results and error responses are returned in real time to the checkout session, with declines and soft failures recorded against the order/payment attempt.
• Capture logic is handled either immediately at purchase or as a separate event, with capture status synchronized back to Bigcommerce for accurate paid/partially paid states.
• Refunds initiated from Bigcommerce create corresponding refund requests in Checkout.com, and refund IDs, amounts, and timestamps are persisted for reconciliation.
• Chargebacks and disputes are surfaced through Checkout.com events/webhooks, with lifecycle updates logged and linked to the originating Bigcommerce transaction.
.png)
We install and configure the Checkout.com payment method in BigCommerce, then map auth, capture, refund, and chargeback flows to your order statuses. Setup includes webhooks, 3DS rules, and test transactions before go-live.
Yes, it can support 3DS2 flows and tokenization so returning customers can pay faster without storing raw card data in BigCommerce. The exact setup depends on your Checkout.com account configuration and risk rules.
Payment IDs, statuses, amounts, refunds, and dispute events can be tied back to the BigCommerce order so finance can match payouts without manual exports. We also align references so support can trace a transaction in seconds.
Yes, webhooks can trigger status updates in BigCommerce when payment events happen in Checkout.com, including partial captures and refunds. We add retries and logging so missed callbacks do not silently break reporting.
We configure currencies, settlement preferences, and local methods per market, then validate how they appear in checkout and in order data. This matters for stores running multiple storefronts or region-specific payment rules.










