Stripe account on hold? Understand your next steps.

First, find out what is actually on hold.

“Stripe is on hold” can describe several different situations. Read the notice in your Dashboard and record what it says about accepting payments, transferring your balance and any action required. A bank payout that failed is different from a review of your merchant account.

Check the affected currency, the date of the notice and whether your customers can still complete checkout. Use the status shown for your own account; another merchant’s release timeline is not a reliable forecast for yours.

Build a response that describes the business you run.

Assign one person to keep the notice, requested documents and follow-up messages together. Submit requested material through the secure route in your Stripe Dashboard. The goal is a complete, consistent explanation of your activity.

Stripe’s business-information guidance lists examples such as itemised invoices and processing or bank statements. The relevant evidence depends on what you sell. Explain the fulfilment behind a charge: what the customer bought, when it was delivered and how you handle support or refunds.

• List each outstanding request and its deadline.
• Match the company name, website and product description across your records.
• Gather relevant invoices, delivery records and processing statements.
• Ask Stripe support to clarify any request you do not understand.

Separate today’s obligations from tomorrow’s checkout.

Make a list of orders awaiting delivery, upcoming renewals, refunds and disputes. Tell your finance and support teams which payment functions remain available. A change in checkout does not move existing transactions or remove the responsibilities attached to them.

Build a short cash-flow plan using funds you can access and dates confirmed by your providers. Keep unconfirmed release dates outside that plan. If future acceptance is at risk, prepare a truthful brief for another PSP while the existing account issue follows its own process.

What to tell a prospective payment provider.

Describe your products, legal entity, customer markets, monthly volume and current account situation accurately. Include the storefront, gateway and billing tools you need to keep. A provider needs to assess your actual business before it can offer processing.

Compare the proposed settlement schedule, reserve, transaction limits, integration work and total fees. Ask what is required before you can process your first live payment. ShieldBill Pay can review this brief and discuss suitable options; the PSP makes its own approval decision.

• Can this provider support our entity, business model and customer countries?
• What needs to be approved before we start taking payments?
• How will refunds, disputes and settlements work?
• What must change in our checkout and recurring billing?

Plan saved-payment migration with both providers.

Saved payment details need their own assessment. Ask the receiving processor and Stripe whether a supported transfer is possible for the payment methods involved. Stripe publishes a secure processor-to-processor export process; copying an API identifier into a new gateway is not that process.

Inventory customer records, billing schedules and renewal dates separately from payment credentials. Stripe’s card export does not include subscriptions or payment history. Confirm any exclusions and whether some customers will need to update their payment method before you choose a cutover date.