Support · Set up
Connecting your Stripe account (read-only)
FeeGuard requests five read scopes via a Stripe restricted key you create and control. Validation runs against Stripe before anything is stored; encryption happens immediately after.
The scopes, with reasons
charges:read (read charges/refunds) · transfers:read (reversals to connected accounts) · application_fees:read (platform fees) · balance:read (key validation, balances) · events:read (replay/backfill). Each maps directly to a detector’s inputs.
Creating the key in Stripe
Developers → API keys → Restricted key. Grant exactly the five reads; skip everything else unless enabling automation later.
Optional write scopes
transfers:write and application_fees:write gate automated clawback only. Detection never needs them, and they are requested explicitly at enablement time, not bundled.
Validation before storage
On submission, the key performs a balance read against Stripe. Failure rejects immediately; success encrypts (AES-256-GCM) before persistence.
Common questions
Can I change or revoke the key later?
Anytime, from settings — rotation validates the new key before overwriting; revocation halts detection immediately.