Connect Finix

Finix connects per brand. You paste a Finix API key and register a webhook in the Finix Dashboard. After that, new disputes flow in automatically and are fought for you.

What you’ll need

From your Finix Dashboard (Developer → API Keys):

• An API key — its ID is the username and its password is the secret. Sent together as HTTP Basic auth on every call.
• Your environment — Sandbox (test) or Live (production). Sandbox and Live keys are separate.

There’s no webhook signing secret — DisputeDash verifies each event by re-fetching the dispute from Finix. And you’ll need admin access to the brand in DisputeDash.

Connect the brand

1. Go to Brands → Connections for the brand (or the Finix card on the Integrations page).
2. Add a Finix account and paste your API username and API password, and choose the environment. Save — the form shows your webhook URL; copy it.
3. In the Finix Dashboard, create a webhook for that URL. Set the Authentication Type to None (DisputeDash authenticates each event by re-fetching the dispute, so no signing secret is needed), and enable the Dispute entity — Created and Updated.
4. Back in DisputeDash, use Test connection to confirm the API key reaches the Disputes API.

Connect the brand before creating the webhook

Finix validates the webhook URL when you save it by sending a test call. That call only succeeds once the Finix account exists for the brand in DisputeDash — so add the Finix connection first, then create the webhook.

How disputes flow in

Once connected, DisputeDash picks up Finix dispute events. When a dispute opens:

1. DisputeDash re-fetches the dispute from Finix (that’s how each event is authenticated), creates the case, and maps the Finix reason to a dispute category.
2. Evidence is gathered from your connected stack.
3. The files are uploaded to the Finix dispute, then the response is submitted through the Disputes API before the deadline.
4. When Finix resolves the dispute, the case updates to Won or Lost automatically.

A scheduled sweep also runs hourly as a backstop and can be triggered on demand with Sync now in Brands → Connections — so a missed webhook is still picked up.

Finix dispute reasons

Finix groups disputes into a small set of reasons. DisputeDash maps each to the right evidence set, and also reads the underlying card-scheme reason code so it fights the right way even when the label is broad:

Finix reason	Handled as
FRAUD	Fraud
QUALITY	Product unsatisfactory
CLERICAL	Processing error (duplicate, credit not processed, incorrect amount — refined by the scheme code)
TECHNICAL	Authorization / processing
INQUIRY	Retrieval / request for information

Good to know

• Per brand. Connect a separate Finix account to each brand — one DisputeDash workspace can hold many. Each brand’s webhook URL carries that brand’s ID, so events route correctly.
• Sandbox or Live. Pick the environment that matches your keys — Sandbox keys only work against Finix’s sandbox, Live keys against production.
• Evidence formats. DisputeDash submits PDF, JPEG and PNG evidence to Finix (Finix converts files to the card networks’ required format for you). Finix accepts up to 8 files per dispute.
• Nothing to re-enter. Editing a Finix account lets you change one field without re-typing the others — leave a field blank to keep its current value.
• No signing secret. Finix doesn’t sign its webhook, so there’s nothing to paste — DisputeDash re-fetches every dispute to confirm it’s genuine. Set the webhook’s Authentication Type to None.