Support
Support centre
Everything about using, paying for, trusting or troubleshooting FeeGuard. Answer-first articles grouped by category; the Stripe events reference lives alongside under /docs.
Start here
What FeeGuard does
Monitors eight Stripe events, finds money that silently moved the wrong way, and quantifies what is recoverable. What it never does, too.
Quick start: first findings in ten minutes
Account, restricted read-only key, webhook endpoint, historical scan, read findings — the five-step path to your baseline number.
Trying FeeGuard without connecting Stripe
The paste-in scanner and the interactive demo — both zero-auth, nothing stored. What each can and cannot show you.
Set up
Connecting your Stripe account (read-only)
Which restricted-key scopes we request and why, how validation works before storage, and how optional write scopes relate to automation.
Registering the webhook endpoint
Why one endpoint per organisation, the eight required events, adding the endpoint in Stripe, and confirming delivery.
Running your historical scan
What the 90-day lookback checks, honest duration expectations by volume, reading results, and safe re-runs.
Inviting your team
Roles today, organisation switching, what members can see under row-level security, and removing access.
Setup checklist (printable)
One-page table: step, where, acceptance criterion. Print it, tick it, done.
Dashboard
Overview screen
The four headline metrics, activity sparkline semantics, and status banners you might encounter.
The discrepancies table
Columns explained, filters worth saving, sorting for recovery order, pagination behaviour.
Reading a single finding
The evidence panel, net-position math rendered inline, available actions, and why amounts differ from refund values.
Finding states and what they mean
Open, investigating, resolved, dismissed, clawback pending/failed — what each asserts about the money, and dismissal reason codes.
Exporting to CSV
Column dictionary, mapping to journals and working papers, ERP-import notes.
Settings that matter
Digest threshold, immediate-email threshold, auto-clawback switches, per-account overrides.
Detectors
Unreversed transfers — how detection works
Trigger events, formula block, tolerance reasoning, exclusions, worked example, automation behaviour.
Application fees left behind
Proportional half-up rule, double-count guard, zero-decimal currencies, standalone fee refunds, worked example.
Disputes the platform paid for
Created versus closed events, recoverable figure definition, liability preconditions, automation exclusion for open disputes.
FX slippage
Same-day baselines, directional loss-only flagging, the 0.8% tolerance, and honest monitoring-only framing.
Risk scores explained
Inputs, bands (Severe ≥80 / Moderate 50–79 / Low <50), where scores act, and what they are not.
False positives and the self-test
Why false positives kill monitoring, the 38-scenario corpus, known noise sources, reporting suspects.
Recovering money
Manual clawback, step by step
Pre-flight checks, the action’s exact behaviour, post-conditions, and where failures surface.
Automated clawback rules (Monitor Pro)
Default-off posture, the five gates in plain language, per-account thresholds, audit coverage.
Idempotency: why you will never claw back twice
Key derivation from findings, Stripe’s 24-hour expiry, the live-state double-guard, worker retry behaviour.
Money-moving actions and their guardrails
Caps, circuit breakers, failure surfacing, and the reversal-asymmetry rule shaping conservative defaults.
After the clawback: verify and record
Confirming amount_reversed, locating balance transactions, exporting evidence, negative-balance outcomes.
When a seller pushes back
Evidence the finding carries, exporting for conversations, write-off path when commercial reality wins.
Alerts
Email alerts and digests
Immediate threshold ($500), digest cadence and default floor ($100), contents, changing settings.
Slack integration
Connecting a channel, payload anatomy, recommended channel topology.
Beating alert fatigue
The mute-test heuristic, raising thresholds deliberately, per-account scoping.
Account & billing
Plans and pricing
The four tiers, what each one unlocks, and the exact free scanner scope.
How the success fee works
What the recovery fee is charged on, what it is never charged on, and how you verify the total against Stripe.
Invoices and payment
Monthly service invoices, recovery-fee invoices referencing confirmed recoveries, billing contact changes.
Upgrading, downgrading, cancelling
When changes take effect, what stops or starts, and data-export reminders on cancellation.
Self-serve checkout
Checkout is live on the pricing page for Monitor and Monitor Pro; existing customers unaffected.
Your account: login, billing and receipts
Signing in, resetting a password, where your plan is shown, and how to download every receipt yourself.
Security & your data
Security overview
Observe-don’t-intermediates principle, read-only posture, the three credibility properties expanded.
How your Stripe key is protected
AES-256-GCM envelope encryption, HKDF-SHA256 per-tenant derivation, in-memory-only plaintext.
What we store — and never store
Stored: finding records, transient claims, audit entries. Never stored: card data, raw payloads beyond processing, scanner inputs.
Database isolation
RLS on every table scoped to your org, plus column-level revocations on key material and why both layers exist.
Rotating or revoking your key
Zero-downtime rotation flow, revocation effects timeline, what happens to history.
Server-side request authentication
Why server actions re-authenticate from scratch and never trust arguments.
Subprocessors and data locations
Current factual list with roles, plus the update-before-change commitment.
Deleting data / reporting vulnerabilities
Deletion request path and scope; disclosure process routing to private channel.
Troubleshooting
Connected but seeing no findings
Ordered decision tree ending honestly: sometimes zero means clean.
Findings of $0.01–$0.02 keep appearing
Multi-partial rounding accumulation, the two-unit tolerance, when noise becomes signal.
Amounts look wrong for JPY/KRW/etc.
Zero-decimal display semantics, minor-unit meaning per currency, three-decimal outliers, verifying your own amounts.
Flagged fee but we refunded separately
Why standalone fee refunds look like leaks to naive checks, charge-outward reasoning, the dismissal flow.
Findings that resolved themselves
The ordering race between paired events, delay-plus-lock mitigation, residual races and live-state clearing.
Duplicate webhook deliveries
Stripe retries on timeout, claim-and-dedupe at ingress, replay appearance in audit logs.
A connected account deauthorized us
Automation freezes instantly, evidence persists, reconnect path, options when reconnection fails.
Scan stuck or failed
Queue redelivery semantics, rate-limit backoff, safe re-runs, which identifiers to send support.
Events arriving late or out of order
Retry/backoff behaviour, effect on detection latency and windows, manual re-scan remedy.
We clawed back, then the dispute was won
Post-clawback win reconciliation, funds returning via normal flow, closing loops without phantom residue.
FAQ
Questions left?
Email feeguard@teamveristria.com with your organisation id and, for finding questions, the charge or finding id — it lets us answer properly on the first reply instead of asking for context. A person reads it and answers within one business day (Norwegian business hours, CET).