Synthetic payments generated on dispute.markets:$0

The payment gateway you can actually break.

dispute.markets is a sandbox payment gateway for chargebacks, evidence, and reports — purpose-built for agentic workflows. Real product surface, fake data, no consequences.

Free to use. No card required. Synthetic data only.

disputes / dsp_8KQH3

Visa · reason 10.4

$487.50 USD

Evidence required

Respond by

14 days

Network case

VROL-A92F1B30

Cardholder

Al Capone

Card

•••• 4242

ChallengeAccept

12+

Visa & Mastercard reason codes modeled

15

MCC categories in the generator

10

Dispute lifecycle states tracked

<1s

Reset the entire dataset in

Why dispute.markets

Built like a real gateway, behaves like a sandbox.

Every surface in dispute.markets mirrors what merchants see in production gateways — transactions, disputes, evidence, reports — so your agents and your team learn against the real shape of the problem.

Synthetic data

Realistic synthetic payments — accurate enough to fool your validators.

Geo-consistent IPs and issuing banks, Luhn-safe card numbers, MCC-coded merchants, and a card-expiry distribution that lines up with the response code. Generate thousands of transactions with knobs for dispute rate, reason-code mix, currencies, and time range.

txn_8FQH3X · Visa 4242$487.50
txn_2K9LMP · Mastercard 5512$129.00
txn_W7RT3Q · Amex 3782$2,140.99

Lifecycle

Real dispute lifecycle

Visa & Mastercard reason codes, RFI → chargeback → arbitration transitions, evidence uploads, response deadlines.

Agents

Drive it through API or UI

Same data, same lifecycle, same audit trail. Let your agent click through the portal like a human, or skip the chrome and call REST directly.

Dev panel

Built-in dev tooling

Generate, inspect, advance lifecycle, and reset state without leaving the portal. First-class UI, not a settings page.

RBAC

Per-tenant roles, granular

Owner, full-access, disputes-only, reports-only, view-only. Synthetic accounts inherit a role and can never escalate.

Webhooks

Outbound events on everything

HMAC-signed events to your endpoint on every dispute, payment, and evidence action. Retried on failure, replayable from history.

In control

In control. Like it should be.

Production-grade data shape. Production-grade lifecycle. None of the consequences. Every transaction, dispute, and event in dispute.markets is generated by us and ends inside your tenant — no card networks touched, no acquirer relationship needed, no real cardholders involved.

You run scenarios that would be too expensive, too sensitive, or simply too slow to run in production, then wipe the slate clean and run them again. No strings, no contracts, no audit footprint outside the sandbox.

  • Realistic enough to pass your validators — Luhn-safe cards, MCC-coded merchants, geo-consistent IPs, valid date math.
  • Reset the entire dataset in under a second. The next test run starts from a known shape, every time.
  • Nothing leaks. Nothing reaches a bank. Nothing follows you home.

Data leaks?

we'll make them disappear.

Synthetic-account portrait — a figure consulting their phone, evoking the calm confidence of a sandbox owner in full control of their data.
Drive it your way

One product, two surfaces.

The browser portal is a thin client over dispute-api. Your agents can click through the UI like a human, or skip the chrome and call the API directly — whichever fits the workflow. Same data, same events, same audit trail.

  • Generate synthetic transactions with a single POST
  • Advance the dispute lifecycle by status
  • Reset the entire dataset between test runs
  • Webhook events fired identically to a real gateway
How it works

Three steps to a live sandbox.

01

Sign up, get a workspace

Create an account, name your company, and you land on a clean tenant with the dev panel ready to go.

02

Generate synthetic data

Pick a transaction count, dispute rate, currency, and time range. The generator hands you a believable dataset in under a second.

03

Let your agent drive

Your agent can operate the portal UI or call the API directly — pick whichever fits the workflow. Actions appear in the dashboard in real time either way.

Nothing leaks. Nothing reaches a real bank.

Every payment, dispute, and evidence record is synthetic. Cards never authorise; webhooks fire to your endpoints only. Resets in the dev panel wipe the tenant clean — no cross-contamination between sessions.

Sandbox-onlySynthetic cardholdersNo real money movementResettable state

Ready to break a payment gateway on purpose?

Spin up a workspace, point your agent at the API, and watch the disputes pile up. All synthetic, all reversible.