Chargeback dispute
Most chargebacks trace back to fraud you let in earlier, so the cheapest way to cut disputes is to stop the fraud before and at checkout.
Step 1: Block fake accounts first
Fraudulent purchases come from fraudulent accounts, so start by keeping those out. Set up Fake account detection, and keep your block lists ready. When you see a flood of accounts created from one IP (hundreds or thousands), add that IP to a block list and deny it on the spot. Lists are how you react fast in the middle of an attack, so set them up before you need them.
Step 2: Gate the checkout (coming soon)
A dedicated checkout action is coming soon. When it ships, you'll evaluate the purchase itself and challenge when it looks risky. A real cardholder clears the challenge; a card tester can't.
| Challenge when | Check | Status |
|---|---|---|
| The buyer looks automated | bot risk | Coming soon (read the score now, can't gate yet) |
| Purchase rate spikes well above the buyer's normal | per-buyer velocity | Coming soon (event_count gives the raw rate today) |
| The purchase is from a new, untrusted device | is_new_fingerprint | Available |
| The email isn't verified | is_email_verified | Available |
The fingerprint and email checks are live today, but the checkout trigger and the bot/velocity gating land with the checkout action, so this whole step arrives together.
When a chargeback does come through, the evaluation from that purchase is also your evidence: it holds the device, location, and risk at the moment of sale.
Related
- Fake account detection and Ban enforcement: keep fraudulent accounts out.
- Card testing prevention: the same checkout signals, framed for stolen-card runs.
- Need help? Contact support.
- Want to see Rupt in action? Request a demo.
- Questions? Talk to sales.
- Check out our changelog.
- Check our status page.
- LLM? Read llms.txt.