About

Nothing errors. The money is simply gone.

FeeGuard reconciles what your Stripe Connect platform actually moved against what it should have moved, and recovers the difference.

Trust & recovery controls

• A restricted key, not a secret key

  FeeGuard asks for five read permissions. A full secret key also works, but it is more access than the job needs, and the connection screen says so.

• Write permissions are yours to grant

  transfers:write and application_fees:write exist only for automatic recovery. Detection works without them, and recovery runs only for the rules you switch on.

• Every finding is checkable in Stripe

  A discrepancy names the charge, transfer and fee objects behind it, so you can open them in your own dashboard before anything is reversed.

• You can cut us off at any time

  Revoke or roll the key in your Stripe dashboard and FeeGuard stops that instant, without a request to us.

• No certification is claimed

  We hold no SOC 2 report today, and the security page says exactly what we do and do not claim. Enterprise customers can request a written security overview, the subprocessors list and a signed DPA from legal@teamveristria.com.

Questions we get asked

Why did my Stripe Connect refund lose money?

Almost certainly because the transfer to the connected account was never reversed. A Connect charge is three separate movements — the charge, the application fee and the transfer — with independent lifecycles. Refunding the charge returns the customer their money from your balance and touches nothing else, because reverse_transfer defaults to false.

What does reverse_transfer do, and why does it default to false?

It reverses the transfer that paid the connected account when you refund the charge. The default is false because Stripe cannot know whose commercial loss a given refund is — that is a decision only the platform can make. The consequence is that a refund path written without it means the platform absorbs every refund.

Should I refund the application fee as well?

It depends whose fault the refund is, which is why refund_application_fee is also a parameter rather than a default. Keeping the fee is usually right for a buyer-remorse refund on a marketplace; returning it is usually right when the platform caused the problem. What matters is that the choice is deliberate and consistent with your terms.

How do partial refunds split between platform and connected account?

However you tell Stripe to split them, and whatever you do not allocate explicitly, the platform absorbs. Refund 40 of a 100 charge with a 10 fee and you can reverse 36 of the transfer and 4 of the fee to keep the split proportional, reverse the full 40 from the transfer, or reverse nothing. Stripe will do any of the three without comment.

How long can I still reverse a transfer?

In practice, only while the connected account still holds the balance to reverse against. There is no single deadline, but the further back a discrepancy goes the more likely it is unrecoverable — which is why a quarterly reconciliation tends to find losses that have already aged out. Detection close to the event is what makes recovery possible.