Enterprise platform acquiring · comparison
Checkout.com for platforms vs Stripe Connect — plus the audit layer either way
Moving money well and auditing money that moved wrongly are separate jobs. Checkout.com (Platforms) handles the first, across borders and at volume. This page is about the transfers a refund should have pulled back and did not — including where Checkout.com (Platforms) wins outright.
What Checkout.com (Platforms) does
the enterprise PSP’s platform/marketplace proposition, positioned on performance and direct integration. Source: https://www.checkout.com.
That is real capability in its lane — and the lanes below show precisely where it ends.
Everything said here about Checkout.com (Platforms) 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 Checkout.com (Platforms)
Eight capabilities a Connect platform needs. No empty cells — every row states what each product actually does.
| Capability | FeeGuard | Checkout.com (Platforms) |
|---|---|---|
| Unreversed-transfer detection | Yes — computed on every `charge.refunded` event: proportional expectation, rounding tolerance, ratio clamping | Not applicable — head-to-head structure mirroring Adyen page. |
| Application-fee leak detection | Yes — application fees tested against reversals via Net Platform Margin; zero- and three-decimal currencies handled | Not applicable — fee models differ. |
| Dispute-loss clawback support | Yes — recoverable figure computed on `dispute.closed` (transfer remainder, fee excluded); early warning on `created`; gated automation | Not applicable — dispute flows differ. |
| Cross-border FX monitoring | Yes — realised rates measured against same-day currency-pair baselines; directional loss flagging beyond 0.8% | Not applicable — fX per configuration. |
| Runs on your live Stripe Connect account today | Yes — read-only restricted key, roughly ten minutes to first findings, revocable anytime | Competing rail |
| Performs recovery actions | One-click manual reversals (free tier); risk-gated automation with idempotency keys on Monitor Pro | Rail-dependent |
| Evidence & audit trail | Append-only trail on every action; finding-level evidence ids exportable as CSV | Rail-dependent |
| Pricing model | Detection and the 90-day lookback free · monitoring is a subscription from $49/mo · success fee only when eligible funds are recovered | Enterprise |
Where Checkout.com (Platforms) genuinely wins
- — Performance-first positioning resonating at scale.
- — Direct-integration enterprise ethos.
Why platforms choose FeeGuard over Checkout.com (Platforms)
- The return path, not the send path. Payout rails optimise money going out; these detectors watch what should have come back and did not.
- 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
Pick rails on merits; pick audits on independence — the decisions share no dependencies. If your problem lives in enterprise platform acquiring, Checkout.com (Platforms) 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
FeeGuard on Checkout rails?
Stripe-Connect-native today; broader support is roadmap without dates — stated as such.
Is FeeGuard a better choice than Checkout.com (Platforms)?
For enterprise platform acquiring, Checkout.com (Platforms) 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 Checkout.com (Platforms) does not perform that function. Most platforms comparing the two are feeling the second problem.
Can we run Checkout.com (Platforms) 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.