Reverse Transfer and Refund Application Fee: The Stripe Connect Leak FeeGuard Finds

FeeGuard scans your Stripe Connect event stream for the hidden money left behind when reverse_transfer or refund_application_fee is missing from a refund, surfaces exactly which charges are affected, and gives you a one-click manual clawback for each one. Detection and the 90-day lookback are free; monitoring starts at $49/mo, and you pay a success fee only when a clawback actually recovers a dollar.

The hidden leakage: reverse_transfer and refund_application_fee failures

When a destination charge is refunded without a reverse_transfer, Stripe refunds the buyer from the platform’s balance while the connected account retains the original transfer. Likewise, a refund that does not include refund_application_fee leaves the platform fee attached to revenue that no longer exists. Both situations create unrecovered balances on connected accounts and are part of the four failure modes defined for Stripe Connect.

The four silent loss modes in Stripe Connect

Stripe Connect can lose money in four ways that do not raise errors or appear in logs: 1) a destination charge refunded without reverse_transfer, 2) a refund without refund_application_fee, 3) a lost dispute where Stripe debits the platform in full while the connected account that received the funds is untouched, and 4) FX slippage that compounds across cross‑border payouts. These modes operate silently, eroding platform margins.

How FeeGuard detects each loss mode using exact Stripe events

FeeGuard scans Stripe’s event stream and matches each finding to the exact event that caused the loss. It looks for charge.refunded, application_fee.refunded, charge.dispute.closed, and balance.available events, then identifies the missing parameter—reverse_transfer or refund_application_fee—and calculates the amount still reachable. By naming the specific Stripe event behind each loss, FeeGuard provides a clear, auditable path to recovery, and leaves the decision to actually claw a finding back to you.

Secure, read‑only monitoring with zero impact on the payment flow

FeeGuard operates in read‑only mode on standard Stripe scopes, ensuring no write permissions are required. Data is encrypted with AES‑256‑GCM using a per‑tenant key, and every action is recorded in an append‑only audit trail. Because FeeGuard only observes the event stream, it has zero impact on the payment flow and does not sit in the transaction path.

Pricing that aligns with recovery: free detection, pay only on reclaimed dollars

Detection and the 90-day lookback are provided at no cost, forever. Ongoing monitoring starts at $49/mo (Monitor Pro is $99–149/mo; annual billing is ten times the monthly rate). FeeGuard charges a success fee only when dollars are successfully reclaimed — 20% of the first $50,000 recovered and 15% of everything above that — with no upfront spend. This aligns cost directly with the value delivered.

Getting started: free 90‑day audit and self‑service reconciliation checklist

The quickest check needs no credentials at all: paste your own charge.refunded events or charge objects into the free scanner and get your recoverable baseline back in under 90 seconds, nothing stored. Continuous monitoring of your full 90-day Stripe history uses a read-only, restricted API key scoped to events and charges only — FeeGuard never requests write access. The page also includes a seven-step manual reconciliation checklist that teams can execute independently. Run the free instant scan at feeguard.dev/audit — no credentials, no signup.