Connect Salesforce with Checkout.com to accept cards and local payment methods, reduce checkout drop-offs, and keep tokenization and compliance handled in one setup.
• Checkout.com payment requests are created from Salesforce checkout or order context and routed to Checkout.com via API, returning a payment ID used as the cross-system reference.
• Authorization, capture, void, and refund events are synchronized back to Salesforce and stored against the related Order and Payment/Transaction records, with status mapped to Salesforce fields.
• Webhook notifications from Checkout.com trigger near real-time updates in Salesforce for success, failure, 3D Secure, and asynchronous outcomes, with retries handled idempotently.
• Customer identifiers, order totals, currency, and billing details are mapped from Salesforce objects to Checkout.com request payloads, with validation for required fields and formats.
• Disputes and chargeback states are ingested from Checkout.com and linked to the original payment reference in Salesforce for case handling and reconciliation.
• Logs for API calls, webhook processing, and mapping errors are recorded in Salesforce for traceability, supporting audit and troubleshooting on Salesforce payments data.
.png)
We map your payment flows and wire Checkout.com APIs to Salesforce order and customer objects so payment status updates are visible where teams work. Payment methods and routing follow your market setup and risk rules.
Typical sync covers authorization, capture, refund, void, chargeback, and dispute status changes. We also align event timestamps and IDs so finance and support can trace each transaction end to end.
Yes – tokenization stays with Checkout.com, and Salesforce stores only the references needed to manage the order lifecycle. This helps keep sensitive card data out of your CRM and reduces compliance overhead.
Yes, we can configure store, country, and currency logic so the right payment settings apply per site or business unit. This includes localized payment methods, settlement preferences, and reporting fields.
Refund and dispute actions can be triggered from Salesforce, with the resulting status updates written back to the related order and customer record. That gives Customer Service a single place to see what happened and what’s pending.





