Connect Checkout.com

Checkout.com connects per brand. You paste a secret key and register a webhook in your Checkout.com Dashboard. After that, new disputes flow in automatically and are fought for you.

What you’ll need

From your Checkout.com Dashboard:

• Secret key — from Developers → Keys (sk_sbox_… for test, sk_… for live). DisputeDash detects test vs live automatically from the key.
• Webhook signature key — set when you create the webhook (below); used to verify inbound events.

And admin access to the brand in DisputeDash.

Connect the brand

1. Go to Brands → Connections for the brand (or the Checkout.com card on the Integrations page).
2. Add a Checkout.com account and paste your secret key. The form shows your webhook URL — copy it.
3. In the Checkout.com Dashboard, go to Developers → Webhooks → New webhook, paste the DisputeDash webhook URL, enable the dispute events, and copy the webhook’s signature key.
4. Back in DisputeDash, paste the signature key and save.

📷 Screenshot

The Brands → Connections Checkout.com form (secret key, signature key, webhook URL). Replace this note with: ![Checkout.com connection](/images/integrations/checkout-com-connect.png)

How disputes flow in

Once connected, DisputeDash receives Checkout.com dispute events in real time. When a dispute opens:

1. DisputeDash verifies the webhook signature, creates the case, and maps the Checkout.com category to a dispute category.
2. Evidence is gathered from your connected stack.
3. The files are uploaded, attached to the dispute as typed evidence, and submitted through the Disputes API before the deadline.
4. When Checkout.com resolves the dispute, the case updates to Won or Lost automatically.

Checkout.com dispute reasons

DisputeDash maps every Checkout.com dispute category to the right evidence set:

Checkout.com category	Handled as
fraudulent	Fraud
unrecognized	Not recognized
product_service_not_received	Item not received
product_service_not_as_described	Product unsatisfactory
duplicate	Duplicate
canceled_recurring	Cancelled subscription
credit_not_issued	Credit not processed
incorrect_amount	Incorrect amount
general	General

Good to know

• Per brand. Connect a separate Checkout.com account to each brand — one DisputeDash workspace can hold many. Each brand’s webhook URL carries that brand’s ID, so events route correctly.
• Test or live is automatic. A sk_sbox_ key routes to Checkout.com’s sandbox; a sk_ key to live — no environment toggle to set. Use a sandbox key + a sandbox webhook to test disputes end to end.
• Nothing to re-enter. Editing a Checkout.com account lets you change one key without re-typing the other — leave a field blank to keep its current value.
• Signature required. DisputeDash rejects any Checkout.com event that fails signature verification, so make sure the signature key in DisputeDash matches the one on your webhook.