Protect
Keep the ratio boring. Chargebacks are a threat to your processing itself.
Cheapest prevention first: pre-auth checks tuned per vertical, descriptors people recognise, early alerts refunded before they count, and a countdown on every evidence deadline.
Cheapest prevention first
Obvious fraud is blocked pre-auth with velocity checks tuned per vertical, before it can become a chargeback. A strike ledger locks repeat offenders platform-wide.
Charges people recognise
Billing text cardholders connect to their purchase, and a dynamic descriptor on rails that support it. Fewer disputes that start with I don’t recognise this.
Refund before it counts
Many disputes arrive as card-network early alerts you can refund before they hit your ratio. Alerts, not chargebacks, with refund automation built in.
A 3DS policy that shows its price
Off, prefer or strict, per terminal, each with the observed cost in approvals and fraud over the last 30 days. You choose with the number in front of you.
Dispute desk
Chargebacks arrive on the card networks’ schedule, and a missed evidence deadline is an automatic loss. So the dashboard counts every deadline down and drafts the pack from the payment’s own trail.
Countdowns
Every dispute shows its due date and time remaining. Nothing expires quietly.
Early alerts
Network alerts with their refund window, and the playbook that refunds the small ones for you.
Evidence packs
Descriptor, 3DS result, delivery proof and prior history assembled from rows. You review, it submits.
Ratio per terminal
Dispute ratios watched per terminal against scheme thresholds, so one bank’s programme never surprises you.
Our take on a
dashboard
or
For operations
One queue for flagged payments, one desk for disputes, with the reason recorded on every decision.
For your bank
Every run, every refund and every pack is an audit row. Exportable. Readable by the people who decide your appetite.
Got questions?
We’ve got answers.
Straight ones,
in writing
How do disputes affect my ledger?
A dispute references its payment and its financial impact lands as ledger entries, never annotations. Early alerts you refund in time never count against your ratio.
What is same-call rescue?
When a gateway refuses a card before any issuer saw it (a country rule, a BIN block, a terminal policy), the payment hops to the next eligible terminal inside the same request. Depth cap two. Issuer declines and fraud verdicts are never retried.
Can an automation move my money?
No. The Copilot proposes; a person confirms. Playbooks are bounded to traffic shares, pauses, policies, refunds of early alerts, drafts and notifications. No automation can create a payout or change a destination.
Nine rails, one contract
Ready to
keep it boring?
Tell us your current ratio and your vertical. We will tell you what the rails will require.