Bespoke dispute arguments · comparison
Justt vs FeeGuard: bespoke chargeback arguments vs automated recovery
A dispute programme and a leak detector answer different questions. Justt 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 Justt is the better tool.
What Justt does
a payment-dispute mitigation firm building tailored argument libraries backed by data science for ongoing merchant portfolios. Source: https://www.justt.ai.
That is real capability in its lane — and the lanes below show precisely where it ends.
Everything said here about Justt 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 Justt
Eight capabilities a Connect platform needs. No empty cells — every row states what each product actually does.
| Capability | FeeGuard | Justt |
|---|---|---|
| Unreversed-transfer detection | Yes — computed on every `charge.refunded` event: proportional expectation, rounding tolerance, ratio clamping | No — argument craft addresses representation, not fund mechanics. |
| Application-fee leak detection | Yes — application fees tested against reversals via Net Platform Margin; zero- and three-decimal currencies handled | No — fee layer untouched. |
| Dispute-loss clawback support | Yes — recoverable figure computed on `dispute.closed` (transfer remainder, fee excluded); early warning on `created`; gated automation | Partial — post-loss clawback remains platform-side API work. |
| Cross-border FX monitoring | Yes — realised rates measured against same-day currency-pair baselines; directional loss flagging beyond 0.8% | No — fX vector 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 Justt genuinely wins
- — Argument-quality focus produces win-rate lifts generic templates cannot match.
- — Portfolio-level optimisation across many merchants compounds learning.
Why platforms choose FeeGuard over Justt
- 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
The best representment on earth cannot reverse a transfer it never sees. Disputes close; transfers stay stranded until something reverses them. If your problem lives in bespoke dispute arguments, Justt 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
Does Justt touch transfer reversals?
No — argumentation is the service; reversal execution lives in platform APIs and tooling like ours.
Is FeeGuard a better choice than Justt?
For bespoke dispute arguments, Justt 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 Justt does not perform that function. Most platforms comparing the two are feeling the second problem.
Can we run Justt 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.