- What is a payment failure refund?
- Why it matters for your books
- How Synder handles it
- The accounting flow
- Which payment methods does this apply to?
- Related: Stripe payout failures
This guide explains what payment failure refunds are in Stripe, why they appear in your accounting, and how Synder handles them automatically.
What is a payment failure refund?
A payment failure refund occurs when a Stripe bank-debit charge initially appears to succeed, but then fails after Stripe has already reflected it in your Stripe balance.
Unlike card payments — which either succeed or fail immediately — bank-debit methods are delayed notification payment methods. After a charge is initiated, Stripe can take several business days to receive final confirmation from the receiving bank. During that window, the charge may appear as settled, but the bank can still return it as failed.
When that happens, Stripe issues a reversal — the payment failure refund — to remove the funds from your Stripe balance.
Common reasons a bank-debit charge can fail after the fact:
- Insufficient funds in the customer’s bank account
- Account closed or frozen
- Customer dispute or mandate cancellation
- Invalid account details
Why it matters for your books
When Synder first syncs a failed bank-debit charge, it records it as a deposit to your Stripe clearing account. This is intentional: Synder uses a deposit rather than an invoice so that Accounts Receivable is not affected by a payment that has not definitively settled.
If the charge then fails and nothing corrects it, the clearing account shows a deposit for money that never actually settled — throwing off your reconciliation. The payment failure refund is Stripe’s mechanism for flagging that reversal, and Synder picks it up automatically.
How Synder handles it
When Stripe sends the payment failure refund event, Synder automatically records an expense entry against the clearing account. This expense offsets the original deposit, correcting the clearing account balance.
No action is required on your part. This is fully automatic and not controlled by any setting in Synder.
The accounting flow
- Charge initiated — Synder syncs it as a deposit to the Stripe clearing account.
- Charge fails (days later) — Stripe issues a payment failure refund to reverse the funds from your Stripe balance.
- Synder syncs the refund — recorded as an expense against the clearing account.
- Net result — the deposit and the expense cancel each other out. The clearing account is back to its correct balance, as if the failed payment never happened.
Please note: Depending on the timing of Stripe’s settlement for the bank charge, Synder may create an invoice or a sales receipt instead of a deposit. Resyncing the transaction after it fails will make sure it shows as a deposit on your books.
Which payment methods does this apply to?
Payment failure refunds only occur with bank-debit payment methods — methods where Stripe uses delayed confirmation:
- ACH Direct Debit (US) — up to 4 business days to confirm
- SEPA Direct Debit (EU) — up to 6 business days
- Bacs Direct Debit (UK) — up to 4 business days
- ACSS Debit (Canada) — same delayed-notification family
Card payments are not affected. Cards succeed or fail immediately, so no delayed reversal is possible.
Stripe payout failures
The same core dynamic — Stripe initially treating a transfer as settled, then reversing it — can also happen at the payout level. A payout failure occurs when Stripe attempts to transfer funds from your Stripe balance to your bank account, but the bank rejects the transfer. Like payment failure refunds, Synder handles payout failures with offsetting entries to keep your clearing account accurate.
For details on how payout failures work and how Synder handles them, see: Stripe Payout Failures: What They Are and How Synder Helps You Handle Them.
Reach out to Synder Team via online support chat or email with any questions — we are always happy to help!
