Direct answer
Does Stripe warn you when you leave money behind?
No. A refund without `reverse_transfer` is a valid instruction, and Stripe executes valid instructions without commentary — there is no error, warning email, dashboard flag or log line. This is correct behaviour, not an oversight: platforms are entitled to absorb refunds deliberately, and inferring negligence from a parameter choice would make Stripe wrong constantly. The consequence is structural rather than personal — absence-based problems need someone watching for absences.
Where people hoped to see it
Dashboard: shows the refund succeeded, because it did. Logs: contain a successful API call, because it was. Emails: receipts confirm what happened, not what failed to happen. Every surface reports truthfully on execution and none report on omission — because omission produced no object to report about.
Why silence is the correct design
Platforms legitimately choose absorption: goodwill policies, terms-based fee retention, simplifying seller relationships. A system that scolded every flagless refund would nag thousands of deliberate choices daily. Stripe’s silence is neutrality working as designed — which transfers responsibility for the check to whoever cares about the outcome.
Whose job it actually is
Yours, operationally — but "yours" means systems, not vigilance. Humans cannot watch absences reliably; event-driven detectors can, comparing expected movements against actual ones continuously. That inversion — from remembering to measure — is the entire product category this site describes.
Common questions
Does the dashboard show unreversed transfers anywhere?
Only derivable through manual reconciliation — never flagged. The information exists across objects; the judgment never runs automatically.
Will Stripe add a warning?
Unknown and not ours to promise. Designing as if none will arrive is the safe posture either way.