Connect Salesforce Commerce Cloud with Opayo to process card payments securely, reduce checkout friction, and keep authorization, capture, and refunds in sync across orders.
• Payment requests are initiated from Salesforce and routed to Opayo using API calls with order, amount, currency, and customer reference fields.
• Opayo transaction IDs and authorization results are written back to Salesforce and linked to the related Order, Account, and payment custom objects via external IDs.
• Webhook notifications from Opayo are validated and processed to update payment status in Salesforce for events such as authorized, captured, refunded, voided, or failed.
• Field mappings normalize gateway values to Salesforce picklists, including status codes, card type, AVS/CV2 outcomes, and risk flags where available.
• Idempotency keys and deduplication logic prevent double-processing when Opayo retries callbacks or Salesforce retries outbound requests.
• Error responses and callback processing outcomes are logged in Salesforce with correlation IDs for traceability across Salesforce and Opayo.
.png)
We connect SFCC checkout to Opayo APIs and map payment statuses back to Salesforce order records, including auth, capture, and void. This keeps payment state consistent for ops and support teams.
Yes – refunds and partial refunds are pushed back to the right order and customer records, with transaction IDs stored for traceability. Support can verify what happened without jumping between tools.
Typically you sync transaction reference, auth code, capture/refund amounts, status, timestamps, and failure reasons. That gives finance clean reconciliation, and support the context needed to resolve cases fast.
Yes, and we implement the redirect or embedded flow based on your SFCC storefront and risk rules. The goal is strong authentication without adding avoidable checkout steps.
We configure per-site settings such as merchant accounts, currencies, and region rules, and validate end-to-end settlement behavior. This avoids “it works in one locale” payment bugs.





