If a payment platform bans or terminates a creator's account, money already sitting in the connected payment balance is not automatically forfeited, but it is also not released instantly. The processor typically holds the existing balance for a window — often tied to how long a card issuer can still file a dispute — before paying out whatever remains after refunds, chargebacks, and amounts owed are settled.
An account ban is unsettling on its own. When there's a real balance sitting behind it — a week of tips, a service that hasn't shipped yet, a shoutout batch waiting on payout — the uncertainty gets worse. The core mechanics are the same across most card-based payment processors, including Stripe, which is the processor FanBell's payments and payouts run on. A ban stops future activity, but it does not instantly zero out a balance or mean the creator forfeits money already, legitimately earned. What it does mean is a hold, a review period, and — depending on why the ban happened — sometimes a deduction to cover refunds or chargebacks that arrive afterward.
What actually happens to a balance when a creator account is banned?
A ban stops new charges and payouts, but published processor terms describe it as an end to access rather than a confiscation of funds. Stripe's Services Agreement says suspension blocks "access to the Stripe Technology and use of any or all of the Services," and its termination clause covers access and amounts owed, not forfeiture of a balance.
"Upon termination of this Agreement, User's rights to use the Services and the Stripe Technology immediately cease."
The Stripe Services Agreement gives Stripe a 10-day cure window before it terminates for a curable material breach, under §10.1(b)(ii) of the General Terms. What normally follows a ban is a hold period during which the processor waits to see whether refunds, chargebacks, or other liabilities land against the balance. Only after that window closes, and only for whatever isn't consumed by those claims, does the remaining balance typically become payable.
Why do payment processors hold funds after a ban instead of releasing them?
Processors hold funds after a ban because a cardholder can still file a dispute weeks after the account stops operating, and the processor remains financially responsible for that dispute. A held balance is the cheapest way to cover the exposure. Releasing every dollar at closure would leave the processor paying disputes out of its own pocket.
Card networks typically allow cardholders to initiate a dispute within 120 days of the original payment, though network rules allow longer in some situations, according to Stripe's dispute documentation (Stripe Docs: How disputes work). Once a dispute is filed, the card issuer usually takes 60–75 days to evaluate submitted evidence and decide the outcome, and the full dispute lifecycle can take 2–3 months from initiation to final decision (Stripe Docs: How disputes work). Holding a balance across a comparable stretch is how the processor absorbs whatever arrives during that tail.
Stripe's own explanation of why it reserves funds is explicit that reserved money is the creator's money waiting on a clock, not money taken:
"Funds held in reserve will be paid out as soon as possible once the reserve term has ended (minus any customer refunds or disputes that may have been covered by the reserve)."
— Stripe Support: Reserves
How long can a processor hold your money after a creator account ban?
No processor publishes a single universal ban-hold length, because the answer depends on the reason for the ban, whether disputes are open, and whether the balance goes negative. Stripe does publish two hard numbers that bracket the question: a typical reserve term of 30–90 days, and a 180-day ceiling on any single connected-account reserve hold.
Stripe's help centre states that when it places a reserve, the term is "normally 30—90 days to give time for customers' refunds and chargebacks to process". For funds reserved on a connected account specifically, Stripe's developer documentation states that a reserve hold's scheduled release date "can never be more than 180 days after its creation date, regardless of how it was created" (Stripe Docs: Set reserves on your connected accounts).
The separate 180-day figure that circulates online describes something narrower than a payout hold. Stripe's Connect documentation states that when a connected account holds a negative balance for 180 days, Stripe zeroes that account by transferring funds from the platform's own balance (Stripe Docs: Understanding Connect account balances). That rule governs how an aged negative balance is written off against the platform — it is not a published guarantee that every banned account with a positive balance is held for six months, and it is not a promise that a positive balance clears on day 180 either.
| Situation after a ban | What the published rules say happens | Primary source |
|---|---|---|
| Positive balance, no open disputes | Funds sit until the reserve or review term ends, then pay out minus any refunds or disputes the reserve covered | Stripe Support: Reserves — term "normally 30—90 days" |
| Positive balance, dispute filed | Disputed amount plus a dispute fee is debited while the issuer decides, usually 60–75 days | Stripe Docs: How disputes work |
| Funds sitting under a connected-account reserve | Release date can never fall more than 180 days after the hold was created | Stripe Docs: Set reserves on your connected accounts |
| Balance goes negative and stays negative | After 180 days Stripe zeroes the connected account using the platform's balance | Stripe Docs: Understanding Connect account balances |
| Refunds, fees, or dispute costs are owed to Stripe | Stripe may "deduct, recoup or setoff" those amounts from a Reserve, funds payable, or the account balance | Stripe Services Agreement, §7.2(c) |
| Termination for a material breach of the agreement | Access to the Services ends immediately; the clause covers access and amounts owed, not forfeiture of a positive balance | Stripe Services Agreement, §10.1–10.2 |
Every row above reflects language published by Stripe. Rows describing suspected fraud or a compliance investigation are deliberately absent from the table: Stripe publishes its setoff and reserve authority, but it does not publish a fixed hold length for fraud-related closures, so any specific number for that case would be invented rather than sourced.
Does FanBell have a separate fund-freezing policy of its own?
No. FanBell does not operate a fund-freezing or confiscation system of its own, because FanBell does not custody creator money — payments and payouts run on Stripe Connect, so hold, reserve, and termination mechanics come from Stripe's published terms rather than a FanBell layer on top. FanBell's enumerated enforcement powers stop short of taking a balance.
FanBell's Terms of Service, §9 (Payments and payouts), states that "payments are processed by Stripe" and that "for creator payments, the platform uses Stripe Connect," with a connected Stripe account required to receive money from paid widgets. §13 (Enforcement) lists what FanBell itself can do: "remove or hide content, reject prohibited requests, restrict or disable monetization, block payments, block users, suspend or terminate creator accounts, and refund or reverse transactions". Refunding and reversing a specific transaction appears on that list; seizing or forfeiting a creator's Stripe balance does not.
That distinction matters in practice. A FanBell-level ban stops new orders on a FanBell page, while whatever has already been processed sits under the state of the underlying Stripe account (how it works) — the same Stripe-run checkout fans use without ever needing an account of their own, as covered in whether fans have to sign up to pay a creator. For the broader mechanics of holds and freezes outside a ban specifically, see can a platform freeze your creator earnings.
What can actually trigger a creator account ban?
Bans follow identifiable, published triggers rather than ordinary business performance. The Stripe Services Agreement lists suspension grounds including a legal or regulatory conflict, a user insolvency event, a breach of the agreement, and activity that Stripe reasonably believes degrades the security or reliability of its services. Prohibited-business activity and failed identity verification are the other two common causes.
Stripe maintains a published Prohibited and Restricted Businesses list, last updated 2026-05-13, which names industries that cannot use Stripe at all and industries requiring additional due diligence (Stripe: Prohibited and Restricted Businesses). Identity checks are the other frequent trigger: Stripe's Connect documentation states that every country imposes Know Your Customer requirements that an account must meet before Stripe can pay out funds to that individual or company (Stripe Docs: Identity verification for connected accounts).
Dispute volume is the third published trigger, and it has numbers attached. Under Visa's Acquirer Monitoring Program, an account is flagged as non-compliant at a VAMP ratio of 0.5% and as excessive at 1.5% outside the CEMEA region, with a non-compliant VAMP count threshold of 5 disputes-plus-fraud events (Stripe Docs: Dispute monitoring programs). Those are network thresholds for monitoring and fines, not automatic ban thresholds, but a sustained breach of them is what turns into an account review. FanBell's own review and reporting flows are documented at safety.
Can a creator get their money back after a ban?
Often yes, for whatever remains once the hold ends and any disputes or refunds have settled, because a ban terminates access rather than automatically forfeiting funds already earned. The realistic path is to wait out the processor's review window and check the payout dashboard once the hold clears. No published Stripe policy lets a user accelerate that timeline on request.
Stripe states that a dispute's timeline cannot be reliably accelerated except by accepting the dispute outright in the Dashboard or API. If a ban was triggered by a misunderstanding rather than a genuine violation, processors generally provide a support or appeal channel to contest it; Stripe does not publish a fixed appeal decision timeline, so any specific number quoted elsewhere should be treated as anecdote rather than policy. If the ban was tied to non-delivery of a specific paid order, ordinary refund handling still applies to that order — see FanBell's purchases and refunds policy, which is separate from the account-level hold question, and what happens legally when a paid request goes unfulfilled for the non-delivery angle itself.
Is an account ban the same as a routine payout hold?
No. A routine payout hold is a risk review on an account that keeps operating and keeps accepting payments, while a ban stops the account from processing new transactions at all. The fund-holding mechanics look similar from the outside, but the underlying account status differs, and so does the timeline for getting paid.
Stripe is explicit that an ordinary reserve is not a shutdown: "Reserves do not affect a business' ability to continue accepting payments with Stripe, so businesses will still be able to continue operating as normal". A banned account has lost exactly that ability, which is why its balance clears on a dispute-driven schedule rather than a payout schedule. For payout-speed mechanics on an account in good standing, see creator payout speed and minimum payout thresholds compared.
How can a creator reduce the risk of losing access to funds?
The most reliable protections are the ones tied to published triggers: keep account activity inside what the account was set up to do, answer identity and compliance requests promptly, and resolve buyer complaints before they become formal disputes. None of that guarantees an account is never reviewed, but it removes the causes that processors actually publish.
Practical habits follow from the numbers above. Deliver what was promised on time, because the dispute filing window runs 120 days from the payment under Stripe's published dispute documentation. Use decline-and-refund rather than letting a request sit unanswered, since a refund never enters a card network's dispute count while a chargeback does. Keep records of what was delivered and when. Respond quickly when a processor asks for verification, because Stripe's Connect documentation ties payout eligibility directly to meeting Know Your Customer requirements. Keeping payout details current matters too, since incorrect bank information can stall a payout independently of any ban — see what happens if your bank details are wrong.
This page describes general payment-processor mechanics and is not legal or financial advice. Specific hold lengths, appeal processes, and ban criteria are set by each processor's own published terms — consult the processor's own policy and, if the money at stake is significant, a licensed professional.
Frequently asked questions
Does a banned creator account lose all the money in its balance?
Not automatically. Stripe's Services Agreement describes suspension and termination as ending access to the Services rather than forfeiting a balance, and Stripe's reserve policy states that reserved funds "will be paid out as soon as possible once the reserve term has ended" minus refunds and disputes covered.
How long does a hold last after a creator account ban?
No processor publishes a single fixed ban-hold number. Stripe publishes a typical reserve term of 30–90 days and a rule that a connected-account reserve hold can never release more than 180 days after it was created.
Does the 180-day rule mean every banned account is frozen for six months?
No. The 180-day figure in Stripe's Connect documentation describes two specific things: the maximum life of a connected-account reserve hold, and the point at which a persistent negative balance is zeroed out using the platform's balance. Neither is a blanket six-month freeze on positive balances.
Does FanBell have its own separate policy for freezing creator funds?
No. FanBell's Terms of Service §9 states that payments are processed by Stripe and that creator payments use Stripe Connect, and §13 limits FanBell's enforcement powers to removing content, blocking payments, suspending or terminating accounts, and refunding or reversing transactions. Forfeiting a creator's balance is not among them.
What triggers a creator account ban in the first place?
Published triggers include prohibited-business activity under Stripe's Prohibited and Restricted Businesses list, last updated 2026-05-13 (Stripe: Prohibited and Restricted Businesses), failing Know Your Customer verification, breaching the Stripe Services Agreement, and sustained dispute levels above card-network monitoring thresholds.
Is losing access the same as losing the money?
No. Losing access stops new transactions on the account, while the existing balance is governed by the processor's reserve and dispute-resolution timelines. Stripe's dispute documentation puts the cardholder filing window at 120 days from the original payment and the full dispute lifecycle at 2–3 months.
Keep reading
Ready to get paid for the interactions you already get?
Create your free FanBell link