Skip to content
DisputeDashDisputeDash Docs

Connect Stripe

Connecting Stripe is a three-step flow: enter your secret key, register a webhook, then paste the webhook’s signing secret back into DisputeDash. Each brand’s merchant account is then mapped in Brands.

What you’ll need

Section titled “What you’ll need”
  • Your Stripe secret key (sk_live_…, or sk_test_… for testing).
  • Access to Developers → Webhooks in your Stripe Dashboard.

Step 1 — Enter your secret key

Section titled “Step 1 — Enter your secret key”
  1. Go to Integrations → Payments → Stripe.
  2. Paste your Secret key.

Step 2 — Register the webhook

Section titled “Step 2 — Register the webhook”

DisputeDash gives you a webhook URL unique to your workspace — copy the exact value shown. It looks like:

https://app.disputedash.com/webhooks/stripe/<your-workspace-id>

In Stripe:

  1. Go to Developers → Webhooks → Add endpoint.
  2. Paste the URL as the endpoint.
  3. Select these events: charge.dispute.created, charge.dispute.updated, charge.dispute.closed.
  4. Add the endpoint.

Step 3 — Paste the signing secret

Section titled “Step 3 — Paste the signing secret”
  1. In Stripe, open the endpoint you just created and reveal its Signing secret (whsec_…).
  2. Paste it into the third field in DisputeDash and save.

Step 4 — Map each brand’s merchant account

Section titled “Step 4 — Map each brand’s merchant account”

In Brands → Connections, add a Stripe account to each brand and enter its merchant account ID.

Important: order IDs in charge metadata

Section titled “Important: order IDs in charge metadata”

DisputeDash resolves the underlying order from the Stripe charge’s metadata. Make sure your checkout writes the order ID into the charge metadata (as order_id) — without it, DisputeDash can’t look up the order to gather evidence. If you’re seeing cases that can’t find their order, this is the usual cause.