Chargeback alert network · comparison
CB-ALERT vs FeeGuard: alert networks and the gap they leave on Connect
A dispute programme and a leak detector answer different questions. CB-ALERT works the cases that reach a card network; the money this page is about never gets that far, because it leaves through ordinary refunds where no dispute exists. Here is the side-by-side, including where CB-ALERT is the better tool.
What CB-ALERT does
a chargeback-alert notification service aggregating network alert feeds so merchants can resolve disputes before they finalise. Source: https://www.cb-alert.com.
That is real capability in its lane — and the lanes below show precisely where it ends.
Everything said here about CB-ALERT is summarised from its own public materials at the link above, never from private knowledge of how it works inside. Products change; if any line has gone out of date, tell us at feeguard@teamveristria.com and we will correct the page rather than argue about it.
Side by side: FeeGuard vs CB-ALERT
Eight capabilities a Connect platform needs. No empty cells — every row states what each product actually does.
| Capability | FeeGuard | CB-ALERT |
|---|---|---|
| Unreversed-transfer detection | Yes — computed on every `charge.refunded` event: proportional expectation, rounding tolerance, ratio clamping | No — alerts prevent some disputes; refund-path leakage involves none at all. |
| Application-fee leak detection | Yes — application fees tested against reversals via Net Platform Margin; zero- and three-decimal currencies handled | No — fees untouched by alert flows. |
| Dispute-loss clawback support | Yes — recoverable figure computed on `dispute.closed` (transfer remainder, fee excluded); early warning on `created`; gated automation | Partial — alerts inform; reversals execute — different verbs. |
| Cross-border FX monitoring | Yes — realised rates measured against same-day currency-pair baselines; directional loss flagging beyond 0.8% | No — fX absent. |
| Runs on your live Stripe Connect account today | Yes — read-only restricted key, roughly ten minutes to first findings, revocable anytime | Depends on deployment |
| Performs recovery actions | One-click manual reversals (free tier); risk-gated automation with idempotency keys on Monitor Pro | Varies by product |
| Evidence & audit trail | Append-only trail on every action; finding-level evidence ids exportable as CSV | Varies by product |
| Pricing model | Detection and the 90-day lookback free · monitoring is a subscription from $49/mo · success fee only when eligible funds are recovered | See vendor site |
Where CB-ALERT genuinely wins
- — Fast alert delivery with per-alert pricing clarity.
- — Network-feed aggregation saves merchants multi-vendor plumbing.
Why platforms choose FeeGuard over CB-ALERT
- The event stream is different. Detection starts at
charge.refunded, notcharge.dispute.created— and most Connect leakage never becomes a dispute at all. - All four vectors, natively. Unreversed transfers, kept fees, uncovered dispute losses and FX drag are separate detectors with separate arithmetic, not one heuristic wearing four labels.
- Free before you pay anyone. Detection and the 90-day lookback cost nothing — measure your stranded dollars before committing to any vendor, including us.
- Ten-minute, read-only setup. One restricted key you create and revoke; no migration, no seller re-onboarding, no payment-path changes.
- Recovery is billed on results. The success fee applies only to dollars actually recovered and confirmed in Stripe — if nothing recovers, nothing bills.
- Evidence-grade trail. Append-only logs with finding-level arithmetic — ready for controllers, auditors and diligence teams.
Bottom line
An alert tells you a dispute is coming. It says nothing about yesterday’s forty refunds whose transfers never came back. If your problem lives in chargeback alert network, CB-ALERT deserves its reputation. If your problem is a platform balance lower than your ledger predicts — refunds succeeding while transfers never come home — that problem has exactly one purpose-built answer, and you are reading it. Run the free audit; the number settles the debate faster than any comparison page can.
Common questions
Do alert services cover refund-path leaks?
No — there is no dispute to alert on when a simple flag omission strands a transfer silently.
Is FeeGuard a better choice than CB-ALERT?
For chargeback alert network, CB-ALERT is the specialist and we say so plainly. For detecting and recovering silent Stripe Connect losses — the four vectors above — FeeGuard is purpose-built and CB-ALERT does not perform that function. Most platforms comparing the two are feeling the second problem.
Can we run CB-ALERT and FeeGuard together?
Yes, commonly. They operate on different objects and different events; neither conflicts with the other’s workflow.
What does switching cost us?
Nothing upfront: read-only key, ten-minute setup, free detection. Recovery carries a success fee only on confirmed dollars — so trying FeeGuard risks no budget at all.