Connect commercetools with Revolut to accept card and digital wallet payments, reduce checkout friction, and keep settlements and refunds consistent across markets.
• Commercetools carts and orders are mapped to Revolut payment objects, with order IDs, amounts, currency, and customer context passed as payment metadata.
• Payment initiation returns a Revolut payment reference that is stored on the Commercetools Payment resource and linked to the related order.
• Asynchronous events are handled via Revolut webhooks, with event types mapped to Commercetools payment transactions and state changes.
• 3DS and other redirect or challenge flows are represented as intermediate payment states, then reconciled once Revolut confirms the final outcome.
• Capture and refund operations are represented as separate transaction entries in Commercetools, with partial amounts supported when the provider response includes them.
• Idempotency keys and duplicate webhook detection are used to prevent double-processing, while errors and provider responses are logged with correlation IDs.
.png)
We map Revolut payment intents to commercetools Payment objects and keep authorization, capture, cancel, and refund states in sync via API calls and webhooks.
Support typically covers cards and eligible digital wallets via Revolut’s APIs, with the exact methods depending on your Revolut setup, regions, and checkout UX.
We implement idempotency, event sequencing, and retries so duplicate or late webhooks do not overwrite the correct commercetools payment and order state.
Yes, if your fulfillment flow needs it, we model multiple transactions per payment and reconcile amounts so captures and refunds match what Revolut settles.
Yes, we pass transaction IDs and status timestamps into commercetools and can export them to your BI or ERP for settlement and refund reconciliation.














