Connect Magento (Adobe Commerce) with Opayo to process cards reliably, cut checkout friction, and keep payment data clean for reporting, refunds, and reconciliation.
• Magento (Adobe Commerce) sends order totals, currency, billing details, and customer identifiers to Opayo during checkout via hosted or direct payment flows, depending on the chosen method.
• Payment responses are returned to Magento with transaction references, authorization results, AVS/CV2 outcomes, and 3DS status, and are stored on the order payment record.
• Order state transitions are mapped to Opayo events so successful authorizations create an order and failed attempts keep the cart available for retry.
• Capture and refund requests are initiated from Magento and routed to Opayo using the original transaction reference, with partial amounts handled when supported.
• Asynchronous updates (for example, 3DS or delayed settlement callbacks) are processed via webhook-style notifications, updating payment status and adding order history comments.
• Errors, declines, and gateway timeouts are logged with request/response metadata, enabling reconciliation against Opayo back office reporting.
.avif)
We configure the Opayo module, align it with your checkout, and validate success and failure flows in staging before release. The goal is stable payments without breaking existing promotions, shipping rules, or tax logic.
Yes, we implement Opayo 3DS2 where required and test edge cases like retries and partial payments. This helps reduce authentication-related checkout failures.
Yes, we map Opayo transaction actions to Magento order states so captures, voids, and partial refunds stay consistent. That reduces reconciliation work and “where did the money go” tickets.
We implement clean purchase and payment events via GTM or server-side tracking, and reconcile them against Magento orders. This prevents inflated revenue when customers retry payments or return from 3DS challenges.
Yes, we support multi-store configurations, different currencies, and localized checkout rules, including post-launch monitoring. scandiweb has delivered 2,100+ eCommerce projects since 2003, so payment edge cases are familiar territory.