Stripe payout hold check

Account closure or termination

This is a different file from a payout review. Ordinary payout-release messages may not apply, and the notice decides how the remaining balance is treated.

Do first

1. Save the closure notice and the account ID, and record the balance and any balance treatment the notice states.
2. Ask Stripe in writing whether the business was reported to the MATCH list, and under what reason.
3. Line up a backup way to get paid before your next sales day.

Proof to gather

• The closure notice and every email about it
• Balance, pending amounts, and any stated release date
• Your written question about a MATCH report and the answer

Matching kit: Merchant Account Termination + MATCH List Response Kit ($49)

A failed payout, not a hold

A payout returned by the bank is usually a bank-detail or account problem, not a risk review. A reserve or review appeal would send the wrong evidence.

Do first

1. Save the failure message and the payout ID.
2. Verify the bank details through the Stripe dashboard itself, not through a link in an email.
3. Track the retry, and keep the failed payout out of your cash plan until the bank confirms receipt.

Proof to gather

• Failure message and payout ID
• Bank confirmation of the account and routing details
• Date of the correction and the retry status

Free guide: payment processor payout hold triage

Verification or a document request

Stripe needs to confirm who runs the account. This is about matching records, not about your sales.

Do first

1. Open the request in the Stripe dashboard and list each item it asks for, one row per item.
2. Submit current records that match each other: legal entity, tax ID, owner ID, and bank ownership. Redact full account numbers.
3. Add one short cover note that names the legal entity, the store name, and the bank account (last four digits) and who owns it.

Proof to gather

• Entity documents and owner ID
• Tax ID record for the legal entity
• Bank record that matches the payout account, with full numbers redacted

Business details that do not match

A reviewer should see the same legal name, website, bank, and offer in the notice and in your files. A recent change can look like a different business.

Do first

1. Reconcile the legal entity, bank account owner, domain, product description, and refund-policy page so they tell one story.
2. List each change you made, the date, and why. Fix what is wrong before you upload anything.
3. Explain any real difference in one sentence with a document behind it. Never alter or relabel documents to make them match.

Proof to gather

• Entity documents and the current website pages
• Bank record for the payout account
• A dated list of what changed and why

Restricted or unclear business model

Stripe may read the offer as prohibited or high risk, or it cannot tell what you sell. Stripe publishes its own restricted-business guidance, so start with the category the notice named.

Do first

1. Read Stripe's restricted-business guidance for the category in the notice and compare it honestly to what you sell.
2. Remove risky or unclear claims from product pages. Make price, delivery timing, refund terms, and support contact visible before purchase.
3. Send a short explanation of the business model with screenshots and a few fulfilled transaction examples.

Proof to gather

• Product pages, terms, and policies as a customer sees them
• A plain description of the offer and who buys it
• A few fulfilled transactions from start to finish

Rolling or fixed reserve

A reserve keeps a percentage or a fixed amount of the balance under stated terms. It is not the same as a payout hold, and an identity upload alone does not change it.

Do first

1. Capture the exact reserve terms in Stripe's words: percentage or amount, start date, review date, and release schedule.
2. Pull recent order, refund, and dispute numbers before you contact support, so you can compare the reserve to your real exposure.
3. Ask for the specific conditions for reducing or releasing the reserve, not general reassurance.

Proof to gather

• Reserve notice and terms
• Recent order, refund, and dispute numbers
• Fulfillment and refund-policy proof

Matching kit: Merchant Account Payout Hold Release Kit ($49)

Disputes, chargebacks, or refunds

Rising disputes and refunds signal possible future losses, which is what holds and reserves protect against.

Do first

1. List every open dispute and its response deadline. Answer each dispute in its own case, separate from the review packet.
2. Pull your dispute and refund numbers, the refund policy, and the support log.
3. Show what you changed to prevent more disputes, such as a clearer card statement descriptor, faster support replies, or order confirmation emails.

Proof to gather

• Dispute list with deadlines
• Refund policy and support log
• Proof of the prevention changes and their dates

Matching kit: Chargeback Evidence Response Guide ($49)

Paid now, delivered later

Processors worry when customers paid before they received the goods or service. Preorders, events, programs, and long delivery windows raise that exposure.

Do first

1. Separate fulfilled revenue from future obligations in one transaction table.
2. If new charges would create more undelivered orders while payouts are held, slow new sales until you can fulfill them from confirmed cash.
3. Send the delivery schedule, the customer notices, and the refund path for undelivered orders.

Proof to gather

• Transaction table split into delivered and not yet delivered
• Delivery schedule and customer notices
• Tracking, access logs, or service-completion records

Sudden volume spike

A large jump in sales can look like fraud or unproven scale, even when the launch was real.

Do first

1. Write a short explanation of what caused the jump: the launch, promotion, or large order, with dates.
2. Attach order summaries and sales history that show the normal level and the spike.
3. Show that the new orders were delivered or are scheduled, and how refunds and support are handled.

Proof to gather

• Sales history before and during the spike
• Campaign or launch calendar
• Delivery proof for the new orders

Account review with payouts paused

Stripe is reviewing the account and holding payouts while it does. Charges often still work. The reviewer needs to see that recent charges are real, delivered, and low risk.

Do first

1. Record the available balance, the pending balance, the amount on hold, and the next expected payout.
2. Build a transaction table for the review window: charge ID, amount, fulfillment status, refund status, dispute status, and days since charge.
3. Ask for review of eligible payouts tied to completed transactions, and ask Stripe to name any transaction-specific risk that blocks release.

Proof to gather

• Dashboard notice, email, and a screenshot of payout status
• Transaction table for the review window
• Order, invoice, or service-completion proof for recent charges

New account or first payouts

Stripe's own payout guidance describes delayed first payouts for new accounts. A missing first payout is not always a review.

Do first

1. Check the payout schedule and status in the dashboard before you treat this as a review.
2. Complete any onboarding or verification items the dashboard still lists.
3. If a review notice is present, answer it with the same proof packet as any other review.

Proof to gather

• Payout schedule screenshot
• Any open onboarding or verification items
• Entity and bank records, ready if Stripe asks

Cash is at risk while the money is held

This is not why Stripe held the money, but it decides what you do this week. Plan as if the held amount will not arrive until it lands in the bank.

Do first

1. Rebuild the next two weeks from cleared cash only. Do not count held funds.
2. Rank payroll, taxes, refunds, and critical vendors, and decide what waits.
3. Do not promise staff, customers, or vendors that funds will clear on an estimated date.

Proof to gather

• Cleared bank balance today
• Payroll, tax, refund, and vendor dates for the next two weeks

Matching kit: Cash Flow Forecast + Vendor Payment Prioritization Kit ($49)