Connect Salesforce Commerce Cloud with Adyen to accept local and global payment methods, improve authorization rates, and reduce fraud with smart risk checks.
• Adyen webhooks push authorization, capture, cancellation, refund, chargeback, and dispute events into Salesforce, with idempotency to avoid duplicate processing.
• Adyen PSP references (pspReference, merchantReference) are mapped to Salesforce Order/Payment records to keep a stable join key across retries and partial operations.
• Payment status changes are translated into Salesforce fields and state models (for example, authorized, captured, refunded, or failed) with timestamped event history.
• Refund requests can be initiated from Salesforce and routed to Adyen APIs, while webhook callbacks confirm execution and update the originating record.
• Multi-currency amounts, fees, and settlement metadata are normalized and stored for reporting and reconciliation, with handling for partial captures and partial refunds.
• Errors and unexpected webhook payloads are logged with correlation IDs, and retries are processed using queue-based async handling to protect Salesforce limits.
.png)
We implement Adyen’s SFCC cartridge or an API-based setup, then map payment actions like authorize, capture, cancel, and refund to your order flow.
At minimum, you want authorization, capture, refund, chargeback, and dispute updates, plus failure reasons, so agents see the latest state on the right order.
Yes – we align Adyen accounts, currencies, and payment method availability to each SFCC site, locale, and channel rules.
We wire capture and refund logic to shipment and item-level states, so partial captures, split shipments, and returns reconcile correctly.
We keep card data out of Salesforce, rely on Adyen tokenization, and harden webhook validation, logging, and access controls.





