Global employment platform · comparison
Oyster vs FeeGuard: global employment vs platform-payout integrity
Paying a global workforce and recovering a stranded Connect transfer are different problems acting on different objects. Oyster owns the first comprehensively. Here is where the second begins, and where Oyster is plainly the better answer.
What Oyster does
global employment/EOR platform with SMB-friendly tiers and mission-forward branding. Source: https://www.oysterhr.com.
That is real capability in its lane — and the lanes below show precisely where it ends.
Everything said here about Oyster 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 Oyster
Eight capabilities a Connect platform needs. No empty cells — every row states what each product actually does.
| Capability | FeeGuard | Oyster |
|---|---|---|
| Unreversed-transfer detection | Yes — computed on every `charge.refunded` event: proportional expectation, rounding tolerance, ratio clamping | Not applicable — employment rail. |
| Application-fee leak detection | Yes — application fees tested against reversals via Net Platform Margin; zero- and three-decimal currencies handled | Not applicable — fees n/a. |
| Dispute-loss clawback support | Yes — recoverable figure computed on `dispute.closed` (transfer remainder, fee excluded); early warning on `created`; gated automation | Not applicable — employment disputes. |
| Cross-border FX monitoring | Yes — realised rates measured against same-day currency-pair baselines; directional loss flagging beyond 0.8% | Not applicable — payroll FX. |
| Runs on your live Stripe Connect account today | Yes — read-only restricted key, roughly ten minutes to first findings, revocable anytime | Different rail category |
| Performs recovery actions | One-click manual reversals (free tier); risk-gated automation with idempotency keys on Monitor Pro | Their tooling |
| Evidence & audit trail | Append-only trail on every action; finding-level evidence ids exportable as CSV | Within platform |
| 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 Oyster genuinely wins
- — SMB-friendly EOR tiers.
- — Strong brand trust with distributed teams.
Why platforms choose FeeGuard over Oyster
- Platform-side, not payee-side. The exposure here sits on your balance rather than the recipient’s, and it is recovered with transfer operations.
- 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
They globalise your team; we localise your truth — per transfer, per refund, per account. If your problem lives in global employment platform, Oyster 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
Oyster for marketplace payouts?
Employment-shaped; Connect merchant rails need their own audit layer.
Is FeeGuard a better choice than Oyster?
For global employment platform, Oyster 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 Oyster does not perform that function. Most platforms comparing the two are feeling the second problem.
Can we run Oyster 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.