The customer paid, and the money can sit on hold for 21 days
The order came in overnight. The store marked it paid, the fulfilment workflow picked it up, the packing slip printed, and the bookkeeping tool recorded a sale. In the payment account the same amount sits with a small label next to it: on hold, unavailable. Nobody disputed anything. The customer is happy. The money has arrived and it cannot be spent.
This article is about that label. It uses the PayPal User Agreement for the United States as its worked example, because the agreement is public and it is specific about days. Other countries have their own editions of the agreement, with their own wording and day counts, and nothing below should be read as applying to them. Everything quoted comes from pages I read on 12 September 2026; the agreement itself says it was last updated on 1 September 2026, eleven days earlier, which is a reminder that these texts move. I am not a lawyer and none of this is advice about your account.
The subject is narrower than the law. Somewhere in your business a process starts on the word "paid", and the processor has a second word that comes later.
Paid in the store and available in the balance are two different facts
A hold is the processor keeping money that has already been sent to you. The agreement describes it in one sentence:
"When PayPal places a temporary hold on a payment, the money is not available to either the sender or the recipient."
PayPal, User Agreement, United States, "Holds", last updated 1 September 2026
The customer's side of the transaction is finished. Their card was charged, their bank shows the debit, your store sent them a confirmation. On your side the same payment "will appear in your PayPal account with an indication that they are unavailable or pending". The agreement promises notice: "We'll notify you, either through your PayPal account or directly by phone or email, whenever we place a hold."
So there are two statuses for one payment. The store, the order system and most automations read the first one, because that is the one the checkout reports back. The balance carries the second, and a standard integration leaves it there.
The clock runs from the day the money came in
The number everyone remembers is 21 days, and it is in the agreement, with three qualifications attached that the number usually travels without.
"Risk-based holds generally remain in place for up to 21 days from the date the payment was received into your PayPal account. We may release the hold earlier under certain circumstances (for example, if you've uploaded shipment tracking information related to the transaction), but any earlier release is at our sole discretion. The hold may last longer than 21 days if the payment is challenged as a payment that should be invalidated and reversed based on a disputed transaction as discussed in the following paragraph below. In this case, we'll hold the payment in your PayPal account until the matter is resolved (but no longer than 180 days)."
PayPal, User Agreement, United States, "Holds based on PayPal's risk decisions"
Read the three qualifications in order. The word is "generally": 21 is the usual ceiling, and the same sentence leaves room for longer. The clock starts on "the date the payment was received", the checkout date; by the time you ship, part of the 21 days has already run. And early release "is at our sole discretion", including the release that follows uploading tracking, which the agreement offers only as an example.
The second number is 180. If the payment is challenged, the hold lasts "until the matter is resolved (but no longer than 180 days)". A separate section on court orders and regulatory requirements adds that a hold placed for those reasons "may remain in place longer than 180 days". The honest range for a single payment runs from a few days to six months, and in narrow cases past that.
For a business that pays staff fortnightly, 21 days is longer than the payroll cycle; for one on 30-day supplier terms, it eats most of it.
The categories are public, the decision behind each hold is confidential
The agreement lists the situations in which holds are common. It also says, in the same section, that the reasoning behind any particular hold is not something it obliges PayPal to explain.
"Our decision about holds, limitations and reserves may be based on confidential criteria that are essential to our management of risk and the protection of PayPal, our customers and/or service providers. We may use proprietary fraud and risk modeling when assessing the risk associated with your PayPal account. In addition, we may be restricted by regulation or a governmental authority from disclosing certain information to you about such decisions. You agree that we have no obligation to disclose the details of our risk management or security procedures to you."
PayPal, User Agreement, United States, "What are holds, limitations, and reserves"
Two paragraphs later the agreement names the factors it reviews: "account tenure, transaction activity, business type, past customer disputes, and overall customer satisfaction". It lists three common situations: new sellers or sellers with limited activity, payments in "higher-risk categories like electronics or tickets", and sellers with "performance issues, or a high rate of buyer dissatisfaction or disputes". The help centre goes further, with seven headed reasons on its page about payments on hold. Two of them are "You haven't sold in a while" and "Your selling pattern appears to have changed or seems unusual". The page explains the second as "an unexpected surge in sales, a change in business type, a change in average selling price, or the type of item being sold".
The categories are public, and they are broad enough that a good month qualifies: a surge in sales is on the list. Whether your good month triggered a hold is decided on criteria the agreement says may be confidential.
The forum version of this rule is "PayPal holds new sellers for 21 days". That rule comes from PayPal's own help centre; the agreement puts it more widely. A page for new accounts says: "As you begin your selling journey, or start selling after a while, we hold the initial payments you receive for up to 21 days."
The same page describes a "monthly release limit", after which "the next payments will be put on hold for up to 21 days". The new-seller rule is real, and it is one instance of a wider power. The agreement attaches the 21 days to risk-based holds in general and puts new sellers at the top of a list of three.
The route to release is published, with day counts
The route to release is written down, with figures, on the help page about releasing payments:
"Add Tracking. Use one of our approved shipping carriers, and we'll release the hold approximately 24 hours after the courier confirms delivery to the buyer's address."
"Update the order status if the held payment is for a service or intangible item (e.g, piano lessons, or an e-book). We'll release the hold 7 days after you confirm the order status as Completed."
PayPal, How can I release my payment(s) on hold?
Below those steps the page adds a line that closes the loop back to the agreement: "In rare cases, after these steps are completed, we may need to hold the payment for up to 21 days. For example, this can happen if we notice an unusual change in your selling patterns."
To release the money, you ship the goods, with a carrier PayPal recognises, and wait for confirmed delivery. The money comes back roughly a day after the customer has the product. So the processor's exit path runs through your fulfilling the order first, which is the opposite of the advice a seller usually hears from the store side: do not fulfil an order until the hold is removed and the funds are paid out.
Both pieces of advice are reasonable from where each is standing. The processor wants delivery evidence before it releases funds; the platform does not want you shipping against money you may never see. The business in the middle has to choose, per order, and most automations have already chosen: the fulfilment flow started the moment the order was marked paid.
A hold is per payment, a reserve is per business
Holds are the visible instrument, and the least severe. The same section of the agreement describes two others, and both reach further.
A reserve is a percentage of everything you take, kept back on a schedule. The agreement's example:
"A Rolling reserve is a reserve where a percentage of each transaction you receive each day is held and then released later on a scheduled basis. For example, your reserve could be set at 10% and held for a 90-day rolling period – meaning 10% of the money you receive on day 1 is held and then released on day 91, 10% of the money you receive on day 2 is held until day 92, etc. Rolling reserves are the most common type of reserve."
PayPal, User Agreement, United States, "Reserves placed on business accounts"
Those figures are an illustration. PayPal's guide for merchants uses a different example, "5% and held for a 60-day rolling period". It also adds a sentence the agreement does not: "depending on your industry and credit history, you may never be able to fully remove a reserve from your account." A minimum reserve is the other category: "a specific minimum amount of money that you're required to keep available in the balance of your business account at all times". It is built up either upfront or from a slice of sales.
The factors for a reserve are listed too, six of them, and they include "Your delivery time frames" and "Whether your industry has a higher likelihood of chargebacks". A business that takes deposits for work delivered weeks later, which describes most trades, studios and travel sellers, fits those two on its ordinary day.
A limitation is broader again. It restricts the account itself, and the agreement's own example is "restricting your ability to send money or make withdrawals". And one line in the section on withdrawals matters for anyone who moves money out on a schedule:
"If we place a limitation on your PayPal account, a payment is subject to a hold, or your account or an associated account has a negative balance in any currency while a withdrawal from your PayPal account is pending, you will have to reinitiate the withdrawal once the limitation or hold has been lifted, or negative balance is fully paid off."
PayPal, User Agreement, United States, "Restrictions on transfers or withdrawals from PayPal accounts"
If a hold lands while a withdrawal is pending, the withdrawal stops, and restarting it is your job. A weekly bank transfer that a person or a script set up and forgot fails on this sentence, without a message.
Every processor has a version of this
PayPal is the worked example because its agreement is the most explicit about days. The instrument is standard across the industry, and I read three other processors' pages on the same date. The rows below are what each page said on 12 September 2026; help pages change without notice.
| Processor | Instrument named on the page | What the page says about time |
|---|---|---|
| PayPal | risk-based hold on a payment; rolling and minimum reserves; account limitation | hold "up to 21 days" from receipt; disputed, "no longer than 180 days"; reserve example 10% for 90 days |
| Stripe | reserve, fixed or rolling; payout availability delay | first payout "within 7–14 days"; a delayed payout "automatically ... released 14 days from the notification date"; a reserve "in some rare cases ... may be required indefinitely" |
| Square | rolling reserve; account review | during a review "we suspend all transfers — including instant transfers"; reviews "usually ... within one business day"; reserved accounts "reviewed after a minimum of six months" |
| Shopify Payments | reserve, "a portion, in some cases a full amount" | terms "communicated to you using email"; "Some reserves can't be appealed" |
Two phrases in the table say more than they look. Square's wording, "all transfers — including instant transfers", means the paid-for fast route out of the balance is the first thing a review switches off. And Stripe's "indefinitely" is the plainest admission in the table that a reserve might never end.
The instruments differ in scope. A PayPal hold sits on one payment; a Stripe or Shopify reserve takes a slice of every payment; a Square review stops the whole outflow. What they share is the order of events: the sale completes, the customer is charged, and then the processor decides how much of that you can reach and when.
Which of your money flows depends on which of these statuses is a question most businesses have never written down, and writing it down is one of the things a process audit produces.
What the hold does to everything that starts on "paid"
A hold leaves the order exactly as it was and puts the cash out of reach, and most small-business processes were built on the order.
Fulfilment. The workflow that packs and ships starts on the payment status the checkout reports, which is "paid". The hold arrives on a different status, in a different system, and does not travel back. A business that wants to ship only against released funds has to build that check, because nothing standard performs it. The question of which system's field is the one that counts is the subject of when two systems write the same field, and it applies to payment status word for word.
The books. The sale is recorded on the order date, at full value. The cash arrives later, less fees, and under a reserve it arrives in two pieces months apart. Reconciling those two pictures without a connector is its own job, described in how to reconcile marketplace payouts without a connector; a hold is one more reason the payout date and the sale date do not match.
Cash planning. Every business has its own version of the food truck: Saturday's takings are Sunday's stock, and a one-business-day review - which is what Square's page describes as usual - falls across the only day that matters. Sunday's event goes ahead without you. The larger version is the seller whose payouts stop for a review while suppliers, payroll and the other essential expenses fall due on their usual dates. Both are ordinary weeks planned on money that, in the store's terms, had already arrived.
The published schedule. If you have worked out when your marketplace money actually lands, a hold is the case that method cannot see coming. It is a delay on one payment, on one day, for a reason the export does not contain. The best a schedule can do is leave room for it.
The nature of the balance. Two sentences from the agreement belong in any cash plan, because they describe what a PayPal balance is: "Any funds you hold in your business account represent unsecured claims against PayPal. PayPal is not a bank, does not take deposits and is not FDIC insured." Money sitting in the balance, held or not, is a claim on the processor, and moving it to the bank on a schedule is the step that takes it off the processor's books and onto yours.
Where this leaves you
Three questions, none of them about PayPal in particular.
Which of your automations start on "paid", and which of those would you want to wait for "available"? Shipping is the obvious one, and the processor's own release mechanism depends on your shipping first, so some order types will keep shipping on "paid". Which ones is a design decision, the sort that an automation that fails without telling you makes badly on its own.
Where is the "received but unavailable" money in your numbers? In the store it is revenue; in the balance it is pending. If your cash forecast reads from the store, it is counting money you cannot reach for up to 21 days, or 180.
What happens to the transfer that was already on its way? A pending withdrawal is cancelled by a hold and must be restarted by hand. If nobody owns that restart, it does not happen, and the first sign is a supplier asking where their money is.
Every one of these has an answer on a page somewhere. Reading the page before that day is cheaper than reading it on the day. If you would rather have someone map which of your money flows depend on which payment status, and where a 21-day gap would land: that is part of the process audit. $299, three business days, and a written map you keep whether or not you hire us.
Nothing here is legal or financial advice.
Related: how to keep track of every automation your business runs is where the "starts on paid" column belongs.