Connect PayArc

PayArc is configured entirely per brand. There’s no webhook secret to set up: DisputeDash verifies every incoming dispute by re-fetching it directly from PayArc’s API using your API token, so a webhook can only ever trigger a lookup — it can’t inject data on its own.

What you’ll need

• Your PayArc API token.
• The brand’s MID (merchant number) — this goes in the merchant account ID field.
• Whether it’s Live or Sandbox.

Connect a brand

1. Go to Brands → Connections for the brand.
2. Add a PayArc processor account.
3. Enter the API token, set the brand’s MID as the merchant account ID, and choose Live/Sandbox.
4. Save.

📷 Screenshot

The Brands → Connections PayArc credential form. Replace this note with: ![PayArc connection form](/images/integrations/payarc-connect.png)

Register the webhook

In PayArc, register the DisputeDash webhook URL (shown when you connect):

https://app.disputedash.com/webhooks/payarc

No signature, secret, or custom header is required. When PayArc calls that URL, DisputeDash takes only the merchant number and case ID from the payload, then pulls the authoritative dispute straight from PayArc’s API with your API token before creating or updating anything.

One dispute, one case

A PayArc dispute moves through stages — retrieval, chargeback, representment, and sometimes pre-arbitration or arbitration — and PayArc records each stage as its own record. DisputeDash groups all of those stages into a single case and advances it as the dispute escalates. You’ll never see duplicate cases for the same dispute, and the case’s win/loss outcome always reflects the primary chargeback.

Pre-arbitration and arbitration escalations are handled by your pre-arbitration policy.

Order matching

PayArc sends the merchant order reference without its dashes — an order like AB1-1234567 arrives as AB11234567. DisputeDash rebuilds the real order number and confirms it against your checkout platform before attaching it to the case.

For this to work reliably on UltraCart, set your brand’s Order ID prefixes on the UltraCart connection (for example AB1, CD, EFG). Prefixes that contain a digit — like AB1 — can’t be recovered automatically, so configuring them is what lets DisputeDash split AB11234567 back into AB1-1234567. See Connect UltraCart.

If the order still can’t be matched — for example an Amex fraud dispute that carries no order reference at all — the case is created in Needs Attention rather than started with nothing to gather. You can enter the order ID on the case and retry. See Needs Attention.

Good to know

• Because every dispute is re-fetched from PayArc, a stray or malformed webhook simply results in a harmless lookup — no bad data is ever written from the webhook body alone.
• A short reconciliation poll also runs in the background as a safety net, so a dispute is still picked up even if a webhook is missed. It only brings in new disputes; it never re-opens ones you’ve already resolved.
• PayArc’s reason text is mapped to a DisputeDash category automatically. A brand-new reason pauses the case at Unmapped until you map it — see Reason mapping.
• Duplicate webhooks are automatically de-duplicated for 24 hours, so retries won’t create double cases.