Quick answer: back up the original, pick the right format/settings, run a small batch, spot-check the output. Dispute ratio = disputes / transactions; a high ratio can trigger risk controls, reserves or account limits.
Why it matters
Get the shortest path working before optimizing.
Count-based, not amount-based.
Step by step
- Confirm amount, card type, country and currency.
- Separate base rate, fixed fee, international surcharge and conversion.
- Model refunds/disputes separately; do not use only successful-transaction rates.
- Calculate effective rate from actual monthly volume, not just the headline 2.9%.
Common mistakes
- Treating 2.9% + $0.30 as the rate for every transaction.
- Ignoring international card/conversion surcharges.
- Assuming the fixed fee is returned after a refund.
- Ignoring dispute fees and chargeback ratios.
Checklist
- Amount, card type, issuer country and settlement currency are explicit.
- Base + fixed + international + conversion are separated.
- Refunds, disputes, subscriptions and invoices are modeled separately.
- Effective rate is based on real monthly volume.
- Compare PayPal/Shopify/Wise on the same transaction.
Key facts
- Count-based, not amount-based.
- Ratio affects account health.
- Prevention beats fighting.
FAQ
What is the quick answer for Dispute ratio?
Quick answer: back up the original, pick the right format/settings, run a small batch, spot-check the output. Dispute ratio = disputes / transactions; a high ratio can trigger risk controls, reserves or account limits.
How long does it take?
Usually 1-3 minutes; for intermittent issues, run 30 seconds and retest elsewhere.
Is data uploaded?
Runs locally and does not upload video/audio; extensions may still read the page.
Source: Stripe