Introduction
What the Disputely Merchant API does and how it fits into your stack.
Disputely catches disputes before they become chargebacks. When a cardholder questions a charge, the card networks tell us first — and we tell you, so you can refund proactively and keep your chargeback rate clean.
The Merchant API gives your backend direct access to that data:
- Alerts — every dispute warning we receive for your account. Read them, match them to your orders, and resolve them (refund the customer) straight from your own systems.
- Lookups — a log of every time a cardholder's bank asked "what is this charge?" and Disputely answered on your behalf with your order details.
Base URL
All requests go to https://api.disputely.com. Every endpoint requires an API
key — see Authentication.
How it works
- A cardholder disputes or questions a charge with their bank.
- The card network (Visa, Mastercard, or the Ethoca/CDRN networks) routes it to Disputely instead of opening a chargeback immediately.
- Disputely creates an alert on your account.
- You refund the customer and mark the alert resolved — the dispute ends there, and no chargeback is filed.
Start here
Quickstart
Create a key and make your first API call in under 5 minutes.
Authentication
API keys, permissions, and keeping your key safe.
Alerts
List, inspect, and resolve dispute alerts.
Lookups
See every time a bank asked about one of your charges.
Connect your AI (MCP)
Use your dispute data from Claude, ChatGPT, or Cursor — no code.
Good to know
- Read-only by default. A key can only resolve alerts if you give it the
alerts:writepermission when you create it. - Your data only. A merchant key is bound to your account. It can never see another merchant's alerts or lookups.
- Stable responses. We only ever add fields to responses. Your integration won't break when we ship new data.