Your dispute process is only as good as your worst dashboard

Every dispute has two properties that make it operationally nasty: it arrives unannounced, and it comes with a deadline. Miss the deadline and you lose by default — the evidence you had doesn't matter.

Now multiply that by the number of payment providers you use. Each has its own dashboard, its own dispute terminology, its own evidence form, its own notification emails landing in whichever inbox was used to set up the account in 2021. In a multi-processor setup, the most common way to lose a dispute isn't weak evidence — it's not seeing the dispute in time.

One queue, deadline first

SpicePay pulls chargebacks from every connected processor into a single Disputes queue, sorted by respond-by deadline. The row tells you what stage the dispute is in (opened, evidence_required, under_review, won, lost) and how many days you have. Webhook events (dispute_opened) fire the moment a dispute lands, so you can page the right team instead of hoping someone checks a dashboard.

Context attached, not hunted

Opening a dispute shows the full payment context on one page: the transaction and its timeline, the customer's history with you, previous refunds, and the 3-D Secure authentication result where one exists. That last one matters — an authenticated payment usually carries a liability shift, and SpicePay attaches the authentication proof to your evidence automatically.

Evidence formatted per processor

Every processor wants evidence packaged its own way. In SpicePay you attach the facts — invoice, delivery confirmation, correspondence — and the platform formats the submission for the specific processor's requirements. Your ops team learns one workflow, not five.

Before the chargeback

The cheapest dispute is the one that never opens:

• The Blocklist blocks cards, emails, and IPs with prior fraudulent activity at checkout.
• On processors that support network alerts (Verifi/Ethoca), pre-dispute cases surface in SpicePay so you can refund before they escalate into chargebacks.

The refunds & disputes doc covers the full workflow.