Lookups
Every time a cardholder's bank asked about one of your charges.
Before a dispute is ever opened, banking apps often show the cardholder a "what is this charge?" screen. The card network asks Disputely, and Disputely answers instantly with your order details — store name, amount, card used. Seeing the real details is frequently enough to stop the dispute cold.
A lookup is a record of one of those question-and-answer exchanges. They're read-only and great for two things:
- Visibility — see which charges customers are questioning, before any alert exists.
- Confidence — confirm Disputely found and returned your order data
(
orderFound: true).
List lookups
GET /v1/resolve/lookupsRequires resolve_lookups:read. Returns your lookups, newest first.
curl "https://api.disputely.com/v1/resolve/lookups?limit=20" \
-H "Authorization: Bearer dspm_live_YOUR_KEY"There are two sources, picked with the source query param:
source | Network | Default? |
|---|---|---|
clarity | Mastercard (Clarity) | Yes |
verifi | Visa (Order Insight) | No |
Mastercard lookups (source=clarity)
The default. Each item is one Mastercard Clarity inquiry:
{
"data": [
{
"id": "clk_01JD4X8YQK2M",
"source": "clarity",
"receivedAt": "2026-09-29T16:42:10Z",
"respondedAt": "2026-09-29T16:42:11Z",
"originatorChannel": "CALL_CENTER",
"transactionCategory": "PURCHASE",
"orderFound": true,
"resultCode": "SUCCESS",
"resultMessage": null,
"transaction": {
"merchantId": "acct_2ZK8Q1M4",
"amount": 29.97,
"currency": "USD",
"cardBin": "511111",
"cardLastFour": "4242",
"arn": "74537604221234567890",
"authCode": "081224"
}
}
],
"next_cursor": null,
"has_more": false
}| Field | Meaning |
|---|---|
receivedAt | When the bank's question arrived. |
respondedAt | When Disputely answered. |
originatorChannel | Where the question came from (e.g. CALL_CENTER, mobile banking). |
transactionCategory | What kind of transaction was asked about. |
orderFound | true if we matched the inquiry to one of your orders and returned details. |
transaction | The card and amount the bank asked about — same matching keys as alerts. |
Supported filters: receivedSince and receivedBefore (RFC 3339), plus
limit and cursor. Other filters return 400 with source=clarity.
Visa lookups (source=verifi)
curl "https://api.disputely.com/v1/resolve/lookups?source=verifi&limit=20" \
-H "Authorization: Bearer dspm_live_YOUR_KEY"Each item is one Visa Order Insight inquiry:
{
"data": [
{
"id": "oi_01JD4X8YQK2M",
"accountId": "acct_2ZK8Q1M4",
"receivedAt": "2026-09-29T16:42:10Z",
"forwardedAt": null,
"respondedAt": "2026-09-29T16:42:11Z",
"upstreamAt": "2026-09-29T16:42:11Z",
"inquiry": {
"correlationId": "c0rr3lati0n1d",
"issuerName": "CHASE BANK USA",
"issuerId": "a1b2c3d4",
"sourceId": "e5f6a7b8",
"originatorChannel": "CALL_CENTER",
"transactionCategory": "PURCHASE",
"locale": "en_US",
"disputeContext": null
},
"transaction": {
"paymentType": "credit",
"authCode": "081224",
"acquirerReferenceNumber": "74537604221234567890",
"amount": 29.97,
"currency": "USD",
"date": "2026-09-28T14:05:00Z",
"cardInfo": { "bin": "411111", "lastFour": "4242" },
"merchantId": "acct_2ZK8Q1M4",
"transactionIdentifier": null,
"cardAcceptor": null,
"clearing": null
},
"outcome": "order_returned",
"upstreamResponseSummary": "order_details_returned"
}
],
"next_cursor": null,
"has_more": false
}source=verifi also supports filtering by outcome, originatorChannel,
transactionCategory, authCode, arn, cardLastFour, and
receivedSince / receivedBefore.
Lookups are informational — there's nothing to act on. If a questioned charge escalates, it shows up as an alert.