Connect Commercetools to Opayo to accept card payments securely, reduce checkout drop-offs, and keep orders, refunds, and payment statuses aligned across your commerce stack.
• Checkout requests create Opayo transactions, and the returned transaction reference is stored on the commercetools cart or order as a custom field for traceability.
• Authorization, capture, void, and refund operations are routed through an integration layer that maps commercetools payment states to Opayo transaction statuses.
• Asynchronous Opayo notifications (webhooks/callbacks) are validated and translated into commercetools Payment updates to reflect real-time payment outcomes.
• Idempotency keys and correlation IDs are used to prevent duplicate charges and to link retries to the original commercetools payment attempt.
• Amount, currency, and order identifiers are validated before processing, with rejected or inconsistent messages logged for review and reprocessing.
• Payment-related errors and status transitions are recorded with timestamps, and updates are applied as deltas so only changed fields are written back to commercetools.
.png)
We implement Opayo as a payment service for Commercetools, map payment states to your order workflow, and validate auth, capture, and error handling in staging before go-live.
Yes. We configure the full payment lifecycle so operations can void uncaptured payments and finance can run full or partial refunds with clean status updates.
Opayo webhooks update Commercetools Payments and Orders in near real time, so support sees the same payment state as finance, without manual reconciliation.
Yes. We design the integration around your stores, currencies, and settlement rules, including per-market routing when your Opayo account structure requires it.
We keep sensitive card data in Opayo, and set up tokenization and 3-D Secure flows based on your risk and SCA requirements.














