How to switch chargeback alert providers without paying both of them


TL;DR
Switching alert providers is not a software migration, it is a re-enrollment of your billing descriptors with the same two networks. Running the old and new vendor in parallel does not double your coverage, because both resell identical network access; it doubles your bill on every dispute that fires. Keep the overlap to the shortest window that proves the new descriptor match works, get the old vendor's cancellation terms in writing before you start, and confirm the enrollment has actually moved rather than assuming a dashboard reflects it.
Switching alert providers feels like changing software. It is not. You are re-enrolling the same billing descriptors with the same two networks through a different reseller, and the networks do not care which company holds the integration.
That has one expensive consequence. During any overlap, both vendors are enrolled against your descriptor, both receive the same alert, and both bill you for it.
Running two providers does not double your coverage
It is worth being blunt about this, because the instinct to overlap "for safety" is exactly wrong here.
Every vendor resells access to Verifi, owned by Visa, and Ethoca, owned by Mastercard. Two vendors connected to Ethoca see the identical Ethoca feed. The second one adds no signal. Chargeback.io states the rule plainly on its own Shopify listing: its alerts do "not work together with alerts from Chargeblast, Disputifier, Chargeflow, or any other provider."
So a month of parallel running buys you one thing only: confirmation that the new vendor's descriptor match works. It costs you a second fee on every alert that fires in that month.
Note
Overlap is a test, not a safety net. Price it as a test and keep it as short as the test requires.What actually has to move
| Step | What it depends on | Typical friction |
|---|---|---|
| Descriptor re-enrollment | Every variation you use, soft and hard, static and dynamic | Missed variations fail silently |
| Verifi customer service number | The number registered in the descriptor | Often registered to the old vendor |
| Network activation | Per network, not instantaneous | RDR is slower than the others |
| Old vendor cancellation | Notice period and any minimum | The part nobody reads until they want out |
| Historical alert data | Whether the old vendor exports it | Usually a CSV at best |
The Verifi row is the one that surprises people. The registered customer service number is tied to the enrollment, not to you, so moving it is a step rather than an inheritance.
Get the exit terms before you start the entry
The single most common mistake is signing with the new vendor before reading the old contract.
Four things to establish in writing:
- Notice period. Thirty days is common, and it starts when you tell them, not when you stop using it.
- Minimum commitment. A discounted rate frequently carries a monthly minimum, and leaving mid-term can trigger the difference.
- What happens to in-flight alerts. Alerts fired before cancellation but actioned after may still bill.
- Whether they de-enroll your descriptor, and when. If they do not, you keep paying. If they do it immediately, you have a coverage gap.
Point four is the one that determines how long your overlap has to be. If the old vendor de-enrolls the moment you cancel, you need the new enrollment live first. If they de-enroll at the end of the notice period, you have a window and should use the shortest part of it.
A migration that does not double-bill more than it must
Read the old contract first
Enumerate your descriptors from settled transactions
Enroll the new vendor and confirm the match end to end
Give notice the day the new enrollment is confirmed live
Reconcile both invoices for the overlap month
Step five is also your proof. Two invoices listing the same order IDs is the confirmation that the new vendor is seeing what the old one saw.
What to compare while you are looking
If you are switching, you are already in a comparison, and the useful axes are narrower than the sales decks suggest. Since every vendor resells the same two networks, coverage is not one of them.
Price per network, whether the volume tiers are published, whether duplicate alerts are waived, and whether you are billed on alerts received or chargebacks deflected. That is most of it.
Our rates are on the published card: $15 per Visa RDR or CDRN alert, $24 per Ethoca alert, tiers printed, duplicates waived, no minimum and no term commitment. The absence of a minimum is worth weighing specifically when you are switching, because a minimum is what makes the next switch expensive.
Deflecting a dispute before it is filed is the paid product. I would rather you moved on a published number than on a quote you cannot check.
The honest part
A switch is genuinely disruptive and the gain is often small. If your current vendor is within a dollar or two per alert, waives duplicates, and matches your descriptors reliably, the migration probably costs more in attention than it returns in rate. The strongest reasons to move are an unwaived duplicate policy, a minimum you are not hitting, or a match rate you have measured and found wanting.
I have also described notice periods and de-enrollment timing as things that vary, because they do. No vendor in this category publishes contract terms, ours included, so every point in the exit-terms section is a question to ask rather than a fact I can state for your specific agreement.
And there is a real coverage gap risk that the overlap advice above trades against. Cutting the overlap to nothing saves fees and risks a window where neither enrollment is live. If your dispute ratio is close to a threshold, pay for the overlap and stop optimising.
Frequently asked questions
Can I run two chargeback alert providers at once?
You can, but it does not increase coverage. Both resell the same Verifi and Ethoca access, so the second vendor sees the identical feed and bills you a second fee for the same dispute. Chargeback.io states on its own listing that its alerts do not work together with other providers. Use an overlap only to verify the new enrollment, then end it.
How long does switching alert providers take?
Enrollment is per network and not instantaneous, and Verifi RDR activates more slowly than Ethoca or CDRN. The bigger variable is usually your old vendor's notice period, commonly thirty days from the day you give notice. Sequence it so you give notice the day the new enrollment is confirmed live.
What do I need to move to a new alert provider?
Every billing descriptor variation you use, including truncated and dynamic forms, and the customer service number registered in the descriptor for Verifi. That number is tied to the enrollment rather than to you, so it is a step rather than something you inherit. Confirm the match end to end before cancelling anything.
Will I lose coverage while switching?
Only if the old enrollment ends before the new one is live. Ask the old vendor exactly when they de-enroll your descriptor: immediately on cancellation or at the end of the notice period. That answer determines whether you need a paid overlap or can cut across cleanly.
The document to read before you do anything else: your current alert agreement, specifically the notice period and whether a monthly minimum applies. If it carries a minimum you are not consistently hitting, you have been paying for coverage you did not receive, and that number is the real argument for moving rather than the per-alert difference.