Add Revolut Pay to your Commercetools checkout so shoppers can pay in seconds with a trusted wallet flow, while you reduce friction, failed payments, and support load.
• Revolut Pay is exposed in Commercetools as a payment method that creates a Payment object and attaches it to the cart or order using custom fields for Revolut references.
• Authorization requests are routed from Commercetools to Revolut Pay through a backend payment service, returning a redirect or tokenized payment session for the shopper flow.
• Revolut payment IDs, statuses, amounts, currency, and failure reasons are mapped to Commercetools Payment transactions and interface interactions for traceability.
• Asynchronous updates are handled via Revolut webhooks, with events validated and translated into Commercetools payment state changes and order state transitions.
• Idempotency keys and correlation IDs prevent duplicate authorizations, captures, or refunds when callbacks are retried or network timeouts occur.
• Refunds and captures are initiated from Commercetools-triggered actions, while the resulting settlement state is synced back from Revolut to keep order, payment, and reporting consistent.
.png)
We add Revolut Pay as a payment method and wire authorization steps into your Commercetools checkout flow. The same integration supports responsive web and app-based checkouts via API-first calls.
We map Revolut Pay events to Commercetools payment objects so your team can see authorized, captured, refunded, and failed states. This keeps order handling and customer communication in sync with the actual payment outcome.
Yes, we implement backend flows for capture and refunds, including partial refunds when your business logic requires it. We also log and validate state transitions to avoid “refunded in PSP, stuck in OMS” scenarios.
We implement verified webhook endpoints, idempotency keys, and replay-safe processing so repeated callbacks do not create duplicate captures or refunds. This is critical during retries, timeouts, and peak traffic.
It works well when you need payment availability and rules to vary by store, currency, or region while keeping one Commercetools backend. We can scope the routing logic so each market gets the right payment option without adding checkout forks.




