In most cases, nothing is lost: if the account or routing number doesn't match a real account, the receiving bank rejects the transfer and the money returns to the creator's Stripe balance, then reattempts once the correct details are saved. The riskier case is entering a valid but wrong account number, since funds can land in someone else's real account.
A payout doesn't fail loudly — a creator usually just notices the money hasn't shown up. Because FanBell payouts run on Stripe, not a rail FanBell controls directly, what happens next depends on exactly what was wrong: a typo that produces an unmatchable account number behaves very differently from one that happens to match someone else's real account. That's a distinct risk from what happens to a creator's balance if the account itself gets banned, which follows a different process entirely.
What happens when a payout has incorrect bank details?
A payout sent with incorrect bank details usually bounces: the receiving bank cannot match the account, returns the funds to Stripe, and the money lands back in the creator's Stripe balance. The other outcome — a mistyped number that matches a real account belonging to someone else — does not bounce, and no published Stripe or Nacha data splits the two.
Stripe's payout documentation describes the bounce-and-retry path directly: "If a payout fails, make sure your bank account details are correct by re-entering them. Stripe then reattempts the payout at the next scheduled payout interval" (Stripe, "Receive payouts"). Stripe's same documentation states that it can take up to 5 additional business days for a bank to return a failed payout and inform Stripe that it failed. Stripe also warns that a failed payout's status "might initially show as paid, but then change to failed within 5 business days," so an apparently successful payout is not final for that window.
Why does a bank reject a payout in the first place?
A bank rejects a payout when the account number, routing number, or account holder name on file doesn't match what that bank has on record. It is a data-matching check run by the receiving bank, not a fraud review, which is why a single mistyped digit fails in the same way a completely wrong number does.
Stripe's guidance on rejected payouts states: "Your bank may reject a payout if the bank account information entered on Stripe doesn't match what your bank has on file" (Stripe, "Rejected payouts"). Stripe names the account holder name as one of the matched fields alongside the account and routing numbers, so registering an account under a business name while entering an individual's name can trigger a rejection even when every digit is correct; Stripe does not publish how often each individual field is the cause. Currency is a separate check — the bank account has to accept the currency the payout is issued in.
Do wrong bank details ever make the money just disappear?
No. A payout sent to an account that cannot be matched is returned to the creator's Stripe balance rather than lost, though the return can take several business days to appear. The genuinely hard scenario is a valid-but-wrong account, where recovery depends on a third party's cooperation instead of an automatic return.
Stripe's support guidance for a payout sent to the wrong account states that "if [the account] doesn't exist or is closed, the bank will typically return the funds to your Stripe balance," and advises contacting support "if your funds haven't returned after 5 business days" (Stripe, "My payout was sent to the wrong bank account").
A mistyped digit that happens to match someone else's real, open account is the harder case, because Stripe's own documentation says recovery may not be possible on Stripe's side:
"If you provide incorrect information, such as a mistyped account number or an incorrect routing number, Stripe might send payouts to the wrong bank account and might not be able to recover the funds. Any fees or losses that you incur because of incorrect information fall under your responsibility." — Stripe, "Receive payouts"
Stripe's instruction in that situation is to contact the receiving bank directly and ask whether it can return or redirect the funds, providing the account details, the expected transfer date, the exact amount, and the payer name ("Stripe"). Recovery in that case depends on the receiving bank's cooperation, not on Stripe or FanBell.
How common are wrong-account payment failures across the banking system?
Wrong-account and wrong-routing-number errors are a tracked, rule-governed category of payment failure across the US banking system rather than something unique to Stripe or FanBell. Payment networks and federal agencies both publish handling rules for them, which indicates the risk is routine and procedural rather than rare or catastrophic.
Nacha reported that total ACH payment volume for 2025 was 42.1 billion payments, up 4.6% over 2024, a figure that includes off-network "on-us" payments. The ACH Network itself processed 35.2 billion payments valued at $93 trillion in 2025.
Nacha's most-cited account-data threshold does not govern creator payouts directly, and it is worth being precise about why. Nacha's ACH Network Risk and Enforcement rule, effective September 18, 2015, set an administrative return rate level of 3.0 percent that "would apply to debit entries returned due to administrative or account data errors (Return Reason Codes R02, R03 and R04)". A creator payout is an ACH credit, not a debit, so that inquiry threshold is not applied to it — the relevant point is the return reason codes themselves, which cover an account that cannot be located or whose number structure is invalid. As a scale reference from the same rule, Nacha put the industry-average ACH Network debit return rate for account data errors at 0.33 percent in 2013.
Government direct deposit — which, like a creator payout, is an ACH credit — shows the same handling pattern at scale. The IRS issued 99,225,000 direct deposit refunds during the 2026 filing season through May 8, 2026. The IRS's own FAQ for an incorrectly entered routing or account number sets responsibility squarely on whoever typed the numbers:
"The IRS assumes no responsibility for tax preparer or taxpayer error." — IRS, "Refund Inquiries 18"
The IRS describes the same three-outcome split creators face: a number that fails validation, a number that passes validation but is rejected and returned by the bank, and a number belonging to someone else, where the taxpayer "must work directly with the respective financial institution to recover your funds".
How do you fix incorrect bank details on FanBell?
Fixing incorrect bank details means updating the bank account inside Stripe's own onboarding and payout settings, not a FanBell-hosted field, because Stripe — not FanBell — collects and holds a creator's account and routing numbers (how it works). Once the corrected account is saved, Stripe uses it for the next payout automatically.
A creator should:
- Re-check the account number, routing number, and account holder name against a current bank statement rather than a memorized number.
- Confirm the name on file matches how the bank has the account registered, since Stripe lists the account holder name as one of the fields the receiving bank matches.
- Update the bank account in the Stripe payout settings reached through FanBell's setup flow.
- Expect the corrected payout on the normal schedule, because Stripe "reattempts the payout at the next scheduled payout interval" rather than firing an immediate off-schedule retry.
- If a payout landed in a valid account that isn't the creator's own, contact that receiving bank directly, since Stripe states it "might not be able to recover the funds" in that situation.
The full mechanics of how a payout moves from a fan's payment to a creator's bank — including the standard payout schedule and what a "pending" payout usually means — are covered in how direct-to-bank payouts work for creators.
Does a wrong-details payout failure cost the creator anything extra?
No. Stripe does not charge a fee to initiate a normal payout, and FanBell adds no separate charge for a payout that fails and retries, so a bank-details typo costs the creator time rather than money. The one cost Stripe does put on the creator is any fee or loss caused by funds landing in someone else's account.
Stripe's payout documentation states plainly: "Stripe doesn't charge you a fee to initiate normal payouts". On the FanBell side, the only charge is the 12% platform fee applied when a fan pays, with no monthly fee and no separate payout or retry fee (pricing). The exception Stripe names is the valid-but-wrong-account case, where "any fees or losses that you incur because of incorrect information fall under your responsibility". That's a very different situation from the creator-side exposure covered in what happens legally if you don't deliver on a paid request, where the money problem isn't a bank error at all.
| Scenario | What happens | Extra cost | Who acts |
|---|---|---|---|
| Account number can't be matched | Bank returns transfer; funds go back to Stripe balance | None | Creator updates details; Stripe retries next interval |
| Name or routing mismatch | Bank rejects payout at the matching check | None | Creator corrects the mismatched field in Stripe |
| Valid but wrong account (someone else's) | Funds land in a real account Stripe "might not be able to recover" | Any resulting fees or losses fall on the creator | Creator contacts the receiving bank directly |
| Details corrected before next payout | Normal payout proceeds on the regular schedule | None | No action needed beyond the correction |
A creator does pay separately if they choose Instant Payouts instead of the standard schedule, but that fee buys speed and is unrelated to fixing bad account details — see do creators pay a fee to receive payouts for that breakdown.
Can wrong bank details delay a payout even after they're fixed?
Yes. Correcting the details does not move the money instantly: the corrected payout waits for the next scheduled payout interval, and if the original attempt is still working its way back from the receiving bank, that return can add up to five more business days before the balance is available again.
Stripe's documentation puts both delays on the record: a failed payout can take "up to 5 additional business days" to be returned and reported, and a brand-new Stripe account's first payout is typically scheduled to complete within 7–14 days after the first successful live payment. A details mistake on a first payout therefore stacks on top of that initial verification window.
Careful entry during setup is cheaper than a correction cycle. For the related question of who ever sees those details in the first place, see is it safe to share your bank details to get paid as a creator.
Frequently asked questions
Short answers to the questions creators ask most often after a payout with wrong bank details fails, each sourced to Stripe's payout documentation, Stripe support guidance, or FanBell's own pricing page. Every answer below reflects sources verified in September 2026.
Do I lose my money if I enter the wrong bank account number?
Usually not. If the number can't be matched to a real account, the bank returns the transfer and it lands back in the creator's Stripe balance, and Stripe "reattempts the payout at the next scheduled payout interval" once the details are corrected. Money is only genuinely at risk when the wrong number matches someone else's real, open account.
How do I know if my payout failed because of bad bank details?
Stripe notifies the account by email and in the Dashboard when a payout fails, and the payout status changes from paid to failed, which can take up to 5 business days. The underlying reason is typically a mismatch between the entered account information and what the bank has on file (Stripe).
Does FanBell charge extra for a failed payout caused by wrong bank details?
No. Stripe states that it "doesn't charge you a fee to initiate normal payouts", and FanBell's only charge is the 12% platform fee applied when a fan pays, with no additional fee for a payout that fails and retries.
What if the payout went to a real account that isn't mine?
Contact the bank that received the funds directly and provide the account details, expected transfer date, exact amount, and the payer name ("Stripe"), because Stripe says it "might not be able to recover the funds" once they reach someone else's valid account (Stripe, "Receive payouts" and Stripe, "My payout was sent to the wrong bank account").
Where do I actually update my bank details for FanBell payouts?
Bank account details are entered and updated inside Stripe's own secure onboarding form, reached through FanBell's setup flow rather than typed into a FanBell-hosted field, because Stripe and not FanBell holds that information.
Keep reading
Ready to get paid for the interactions you already get?
Create your free FanBell link