Connect Airwallex

Airwallex connects per brand. You paste a Client ID + API key and register a webhook in your Airwallex web app. After that, new disputes flow in automatically and are fought for you.

What you’ll need

From your Airwallex web app (Developer → API keys):

• Client ID and API key — exchanged for a short-lived access token on every call.
• Webhook secret — set when you create the webhook (below); used to verify inbound events.
• Your environment — Demo (sandbox) or Production. Demo and live keys are separate.

The API key needs these permissions: Payment Disputes (Read + Write), Payment Acceptance (Read), and Upload Files (Write). And admin access to the brand in DisputeDash.

Connect the brand

1. Go to Brands → Connections for the brand (or the Airwallex card on the Integrations page).
2. Add an Airwallex account and paste your Client ID and API key, and choose the environment. The form shows your webhook URL — copy it.
3. In the Airwallex web app, go to Developer → Webhooks, add a webhook for the DisputeDash URL, enable the dispute events, and copy the webhook’s secret.
4. Back in DisputeDash, paste the webhook secret and save, then use Test connection.

📷 Screenshot

The Brands → Connections Airwallex form (Client ID, API key, environment, webhook secret). Replace this note with: ![Airwallex connection](/images/integrations/airwallex-connect.png)

How disputes flow in

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

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

Airwallex dispute reasons

DisputeDash maps every Airwallex dispute reason to the right evidence set, across the RFI, chargeback, and pre-arbitration stages:

Airwallex reason	Handled as
FRAUDULENT	Fraud
UNRECOGNIZED	Not recognized
PRODUCT_NOT_RECEIVED	Item not received
PRODUCT_NOT_AS_DESCRIBED	Product unsatisfactory
DUPLICATE	Duplicate
CREDIT_NOT_PROCESSED	Credit not processed
INCORRECT_AMOUNT	Incorrect amount

DisputeDash also reads the underlying card-scheme reason code (e.g. Visa 10.4), so reasons map correctly even when the label is unfamiliar.

Good to know

• Per brand. Connect a separate Airwallex account to each brand — one DisputeDash workspace can hold many. Each brand’s webhook URL carries that brand’s ID, so events route correctly.
• Demo or Production. Pick the environment that matches your keys — Demo keys only work against Airwallex’s sandbox, Production keys against live.
• Evidence formats. DisputeDash submits PDF and JPEG evidence to Airwallex (PNG screenshots are converted automatically, since Airwallex doesn’t accept PNG).
• Nothing to re-enter. Editing an Airwallex account lets you change one field without re-typing the others — leave a field blank to keep its current value.
• Signature required. DisputeDash rejects any Airwallex event that fails signature verification, so make sure the webhook secret in DisputeDash matches the one on your webhook.