Use case · Card testing & chargebacks

Card testing costs you twice. Chargebacks three times.

Bursts of small authorizations, geo mismatches, reused instruments, and the evidence pack when a dispute lands.

The pattern

Dozens of $1 authorizations in minutes, card BINs from one issuer, a billing country that doesn't match the device, then the disputes arrive weeks later.

The tags

card.testing_patternpayment.geo_mismatchpayment.instrument_reusedchargeback.risk_highrefund.abuse_patterndispute.evidence_ready

The preset

When	Then
`card.testing_pattern`	`block`
`payment.geo_mismatch (≥ 0.8)`	`step_up`
`chargeback.risk_high`	`review`

Ship it

Connect Stripe, Razorpay, Xendit or Midtrans: payment events arrive by webhook, nothing to code. When a dispute lands, download the evidence pack.

Recommended mode · Recommend, Autopilot on card.testing_pattern

your backend

// Nothing to send: payment events arrive from your PSP webhook.
// When a dispute lands:
const pack = await ordent.disputes.evidence({ payment: "pay_7c21" });
// → device, IP, timeline, prior step-ups, as a PDF and JSON

What you'll see

Authorizations blocked, disputes with evidence, win rate.

Start today

Your risk team starts here.

$99 a month, 10,000 events, sandbox before you pay, money back in 14 days if it doesn't fit.

Start for $99 Install with your AI agent