Skip to content

Integrations overview

DisputeDash connects to the tools that hold your dispute, order, shipping, and support data. This page explains the one concept that makes the rest of the integration guides click: where each connection lives.

  • Integrations page (workspace-level) — connect a tool once for your whole workspace. Credentials are stored here and shared across every brand. This is where Braintree, Stripe, ShipStation, Zendesk, and BigQuery live.
  • Brands → Connections (brand-level) — attach a processor to a specific brand and tell DisputeDash which merchant account that brand uses. Some processors are configured entirely here.

Think of it as: workspace = the credentials, brand = which account those credentials point at.

Which processors are workspace-level vs per-brand

Section titled “Which processors are workspace-level vs per-brand”

This is the single most common source of confusion, so it’s worth stating plainly:

Processor Where you configure it
Braintree Workspace credentials + per-brand merchant account ID
Stripe Workspace credentials + per-brand merchant account ID
PayPal Entirely per-brand (each brand has its own PayPal app)
PayArc Entirely per-brand
Shopify Payments Entirely per-brand
Square Entirely per-brand (one-click OAuth — no keys)
Adyen Entirely per-brand (API key + webhook HMAC key)
Checkout.com Entirely per-brand (secret key + webhook signature key)
Klarna Entirely per-brand (API credentials — username + password)
Airwallex Entirely per-brand (Client ID + API key + webhook secret)
Finix Entirely per-brand (API key — username + password)

If a processor is “entirely per-brand,” you won’t enter credentials on the Integrations page — that card just links you to Brands → Connections, where you add the account.

Carrier tracking, transactional email, and other platform services are managed by DisputeDash — there’s nothing for you to connect. See What DisputeDash manages for you.

You must verify your email first — it’s the one gate on connecting a payment processor.