Payment accounts examples: find the case that matches you

A payment account that pauses payouts, withholds part of each disbursement or freezes after a change is doing what its design requires: it is pricing risk it has not yet been paid for. The fastest fix starts by matching your symptom to the trigger the provider saw.

Seven cases cover the common symptoms: a pause after a spike, a withheld reserve, mismatched receipts, a dispute reserve, a freeze after a change, a restriction in payroll week, and an outage.

What to take away

Find the case that matches you

Start from what you noticed, then read the matching case. The trigger column explains why the provider acted, and the last column shows what ended the episode. No provider is right for every business, so compare the reserve terms, the settlement timing and the dispute threshold before you sign.

For who decides what in each case, see what an account can do.

Payouts paused after a sales spike

A kitchen-tools maker runs a Kickstarter campaign and takes pre-orders through Stripe. One week of sales equals several normal months. Stripe pauses payouts and opens a review.

Stripe carries the risk that pre-orders will not ship and will be disputed. A volume jump with delivery still weeks away is that risk in its purest form.

The business sent one package: the factory production schedule, the freight contract, and the campaign terms. Stripe resumed payouts with a reserve against part of the pre-order value until shipments were confirmed. Warning Stripe before the campaign would have shortened the episode.

Part of every payout is withheld

An Amazon seller notices part of every disbursement is withheld and released weeks later. Amazon holds a rolling reserve against returns and A-to-z claims, sized to the category rather than to the seller. It is written into the seller agreement and it does not move on request.

Nothing changed the reserve. What changed was the seller's forecast: the withheld money was modeled as a timing lag, so the business stopped spending it. The account that money finally lands in is the subject of business checking.

Receipts that do not match invoices

A translator invoices clients in three countries. Wise handles the euro and pound payments, PayPal the dollar ones. The fee shown on each payout is small, yet her accountant asks why receipts do not match invoices.

Wise converts at a margin from the mid-market rate. PayPal converts at its own rate, which is wider. Neither margin appears as a fee, and on some corridors a correspondent bank also deducts a charge in transit.

She began recording the amount invoiced, the reference rate on the day, and the amount landed, then computing the gap. That number, not the fee, became the basis for choosing between Wise and PayPal and for pricing clients in their own currency.

What a provider must disclose about the rate and the amount that will arrive is set out in subpart B of Regulation E.

A reserve that rises with disputes

A subscription-box business on Stripe sees its dispute count rise after a billing change. Stripe raises the reserve and warns the account is under review. Dispute rate is Stripe's main risk signal. Cross the threshold in its terms and reserves come first, termination after.

The business fixed the source. It changed the billing descriptor so customers recognized the charge, moved the renewal reminder earlier, and simplified cancellation. The dispute rate fell over the next cycles and Stripe reduced the reserve. Contesting individual disputes would have addressed none of it.

A freeze after the business changed

A shop onboarded with Square as selling home goods later added supplements, which sell well. Months on, the account is frozen pending review. The observed activity no longer matched the business Square approved, and supplements carry a different risk profile under Square's prohibited and restricted list.

The business supplied its full current product list, supplier documentation and compliance material for the new category. Square restored the account under revised terms. Telling Square before adding the category would have avoided the freeze.

Describing the business accurately at onboarding, and again when it changes, is covered in account opening mistakes.

Two cases where a second place for the money decided it

A cafe takes cards through Adyen, and the account is restricted for two days during an unrelated review. Payroll is due on the second day and runs anyway, because the owner swept settled funds to a bank account every Friday and kept only the working float.

Payroll came from the bank account, which the review never touched. A schedule did it. Sweeping is the one habit that separates an inconvenience from a crisis, and it costs a calendar entry. What opening that account involves is covered in what a bank account requires.

Shopify Payments has a service outage on a busy weekend. A store using it as its only card channel loses the weekend's takings. A neighboring store, with WorldFirst already set up for a small share of volume, switches within minutes.

The second route existed before it was needed. It carried little traffic, but it was live, tested and reconciled, so switching was a habit rather than an emergency. Which business shapes suit a branchless second account is covered separately, and the running cost is priced on the banking fees page.

What the seven share

In every case the provider was doing what its design requires: pricing risk it had not yet been paid for, or failing the way any single system fails.

The businesses that came through cleanly had done four cheap things in advance. They described themselves accurately, warned before anything unusual, swept on a schedule, and kept a second route alive. None treated a payment account as the place their money lived. The balance was always heading to a bank account.

Where that money sits, and who insures it, is a question to settle against the deposit insurance rules the FDIC publishes before you rely on any provider's answer.

Common questions

Is a hold a sign the provider distrusts me?

It is a sign the provider's model flagged a pattern. Treat it as a request for information and answer the exact request quickly and completely.

Can I negotiate a reserve away?

Rarely up front. Reserves fall when the risk they cover falls: disputes down, delivery evidence provided, history built up.

What should I send when payouts pause?

Send what answers the trigger. After a spike, that was the production schedule, freight contract and campaign terms. After a change in what the shop sold, it was the product list and supplier documentation. After disputes, it was the fix to the source.

How much should I keep in the payment account?

Enough to run the operation between sweeps, and no more. Anything beyond that is exposed to a review it does not need to be exposed to.