Accept card payments and let shoppers pay with Revolut Pay on your BigCommerce store, with secure authorization, smoother checkout, and cleaner payment reporting.
• Bigcommerce creates an order and sends the payable amount, currency, and customer context to the Revolut payment gateway during checkout.
• Revolut returns an authorization result and a transaction reference; these values are stored on the Bigcommerce order for traceability.
• Payment state is mapped to order payment status, including authorized, captured, failed, canceled, and refunded outcomes.
• Capture behavior is handled as immediate capture or separate capture, depending on the configured payment flow and order state.
• Refund requests initiated from Bigcommerce are routed to Revolut with the original transaction reference; refund IDs and amounts are written back to the order.
• Webhook callbacks from Revolut update the order when asynchronous events occur, with idempotent handling to avoid duplicate state changes.
• Event logs record request, response, and webhook payload metadata to support auditing and troubleshooting across Bigcommerce and Revolut.
.png)
We configure the Revolut payment method in BigCommerce, map the right checkout flows, and validate authorization, capture, and refund behavior in a staging environment before go-live.
Yes, we align Revolut payment events with BigCommerce order states, including refunds and partial captures, so support and finance see the same truth.
It can, as long as currency settings, settlement logic, and rounding rules are set correctly across BigCommerce and Revolut to avoid mismatches in payouts and revenue.
Typical data includes order ID references, payment authorization and capture status, refund events, amounts, currency, and timestamps needed for reconciliation.
scandiweb has delivered 2,100+ eCommerce projects since 2003, and we build payment integrations that stay stable across multiple stores, currencies, and operating teams.










