You are not a risky business. You look like one.

Processors do not publish their scoring models, but they do publish what triggers a review or a reserve. Read those lists with a wedding calendar next to you and every item lights up.

The four signals

1. You take money long before you deliver

The Knot's Real Weddings Study puts the average US engagement at 14 months for 2025 weddings;¹ Zola's 2026 First Look report says 18 months.² Couples book their main vendors early in that window, so a deposit routinely lands nine to fifteen months before the service, and the final gallery or film arrives weeks after that.

To a processor this is the single most important fact about you. Square's reserves page lists, as a reason for a reserve, "if you are collecting payment in advance of delivering the purchased goods or services."³ Stripe's Reserves FAQ names a business that "belongs to an industry with longer-than-average delivery windows" and one with "an increased risk of not fulfilling customer orders."⁴ Whop's list includes "long gaps between payment and delivery."⁵ Three processors, three phrasings of the same thing, and all three describe a wedding deposit.

The reason is liability. If a vendor closes before the wedding, every couple with an undelivered booking can dispute their payments, and because the dispute clock for a future service starts on the event date,⁶ the processor's exposure lasts until about four months after the last booked wedding. Stripe says it directly: when a business cannot fulfil, Stripe "is responsible for the disputes and refunds that arise."⁴ A reserve is the processor making you fund that exposure instead.

2. Your tickets are large and your transactions are few

The average US wedding cost $34,000 in 2025 and couples hired 13 vendors on average,¹ so a single vendor's payment is often in the low thousands. A photographer taking 30 weddings a year might process 60 to 90 card payments, many of them over $2,000.

Two problems follow. First, a $3,000 charge from a new account with no history scores as an anomaly on its own; Square names "if you don't have a processing history with us" as a reserve trigger.³ Second, your dispute ratio is fragile. Stripe warns that for businesses with "fewer than 100 payments per month," one or two disputes can have "a very outsized impact on your dispute rate."⁷ One upset couple in a slow month is a 30% dispute rate for that month. The card networks will never see it; your processor's model will.

3. Your volume is seasonal and lumpy

Engagement season runs from Thanksgiving to Valentine's Day, so deposits cluster in winter; balances cluster in the weeks before peak wedding months. A quiet February followed by $20,000 of deposits in March is normal for you. Stripe lists "sharp, unexplained jumps in volume" as a reserve trigger;⁴ Whop lists "sudden shifts in sales patterns."⁵ The word that matters is unexplained. Volume the processor expected is not a signal; volume it did not is.

4. The card belongs to someone who is not the client

Parents pay. Planners pay. A partner pays with a card in the other partner's name. Every one of those is a card-not-present transaction where the cardholder's name does not match the person who signed the contract, which is the fingerprint of fraud in a risk model and the easiest "I did not authorise this" dispute for a bank to accept. The fix is on your side: put the payer on the agreement or on a payment authorisation. See Contract language.

Why the instant sign-up makes it worse

Stripe, Square, PayPal and Whop are aggregators: they sign up thousands of small sellers under one master account and carry the risk themselves. The trade they offer is approval in minutes with little underwriting up front, and the right to review you later. So the first time a real human at the processor looks at your business is usually after a trigger fires, when the questions arrive with a hold attached. A traditional merchant account asks the same questions before approval, which is slower and sometimes more expensive, but means the surprises come at the start. See Choosing a processor.

What the processors say a reserve is for

None of this is personal. It is also not something you can argue your way out of with a complaint. What you can do is change what the model sees: a described business, a matching descriptor, visible contracts, a documented delivery history, balances taken by bank, and a dispute count that stays at zero. The next guides are about exactly that.

What this resource will not tell you

It will not tell you that any processor is safe, or that one is a villain. Every aggregator's terms give it the right to hold funds, and every one of them uses it. It will not tell you to avoid card payments; couples expect them and the networks' dispute rights protect your clients too, which state consumer offices actively recommend.⁹ It will tell you how the system works and how to run a wedding business inside it without losing a season's income to a hold.