Your first month accepting online payments will be slower, more frictional, and less predictable than your sign-up call suggested. I've watched dozens of first-time online merchants hit the same issues in the same order, so the pattern is consistent enough to plan against. You'll see a delayed first deposit, get caught by at least one fraud filter false positive, watch decline rates run higher than the published industry baselines, and probably field a few customer support questions you weren't prepared for. None of this means something's broken. It's how the system actually works for a brand-new merchant, and the friction usually starts to settle around day 45 to 60.
When You'll Get Paid for Your First Online Sale
Your first deposit doesn't follow the same timeline as your hundredth deposit. With a traditional acquirer, settled funds typically move on a T+1 or T+2 schedule, meaning a transaction settled Tuesday lands Wednesday or Thursday. With a payment aggregator, the rolling 7-day window many new accounts start on means your first batch can take a full week or more to arrive. Add a holiday or a weekend and you can stretch that to 10 or 12 calendar days.
The first deposit is also the most likely to get held for review. Acquirers run risk algorithms on every new merchant's opening transactions, looking at ticket size, customer geography, refund timing, and a dozen other signals. If your first sale is for $4,000 and your underwriting paperwork said your average ticket would be $80, expect a review.
Plan your launch cash flow around the assumption that you won't see real money for at least two weeks after your first sale. Treat that as fixed.
What a Rolling Reserve Means for New Merchants
A rolling reserve is a percentage of your sales the processor holds back as collateral against future chargebacks, refunds, and fraud losses. It's the most common form of merchant-side risk mitigation, and new accounts in any category with elevated dispute risk are likely to encounter one.
The structure is simple. The processor withholds a set percentage of every batch, often 5 to 10 percent, and releases each held amount 90 to 180 days later. Today's reserve gets paid out next April. Tomorrow's gets paid out next April plus one day. The reserve "rolls" forward continuously. After the release window closes, you've got a steady-state where releases match new holds, but until you reach that point, you're effectively financing the processor's risk position out of your working capital. The cash impact adds up fast. If your reserve is 10 percent and you do $50,000 in monthly sales, roughly $30,000 will be sitting in the reserve account by the end of month six before any of it begins releasing back to you. New merchants in industries with higher chargeback rates, including subscription services, digital goods, travel, and event ticketing, often face heavier reserves than the category baseline. Federal Reserve payments research and CFPB merchant complaint records both reflect that reserve terms are most punitive in the first six months and typically ease as transaction history accumulates.
Most welcome packets I've reviewed don't mention reserves prominently. They appear in the merchant agreement, often under a section about reserves, fraud monitoring, or risk-based holds. If you didn't read the contract carefully and you're now seeing 5 to 10 percent missing from your deposits, that's almost certainly where it went.
Fraud Flag False Positives Will Happen
The fraud rules baked into your gateway and your acquirer aren't tuned to your specific business yet. They're tuned to the average ecommerce account in your assigned merchant category, with whatever risk profile new merchants in that category historically present. Your first month is when you find out which legitimate transactions those defaults flag.
Common false-positive triggers in the first 30 days include high-ticket transactions on a new account, first-time international cards, billing addresses that don't perfectly match the AVS check, and customers using prepaid or virtual cards. You'll see authorization holds, soft declines, and the occasional outright refusal of a card that the customer swears worked everywhere else. Most of these resolve when you contact the customer and ask them to retry, but you'll lose some sales to abandonment in the meantime.
The fix isn't tighter fraud rules. It's gradually loosening the defaults as you accumulate enough transaction history for the processor to build a real baseline for your account. That usually takes 60 to 90 days of consistent volume.
Why Decline Rates Run High in Your First Month of Online Payments
Industry benchmarks for card-not-present declines typically hover around 5 to 10 percent. New merchant accounts often run 12 to 20 percent in the first month. The gap is mostly explained by the false positives above, plus issuer-side caution against unfamiliar merchants in their authorization data.
When a customer's bank sees an unfamiliar acquirer-merchant combination on a new account, the issuer's own fraud system applies extra scrutiny. The customer doesn't see "your processor declined this." They see "your card issuer declined this," and they often blame the merchant. There's not much you can do about issuer-side declines except wait for the merchant identifier to age into the issuer's data, which typically takes 30 to 90 days.
What you can do is reduce your own contribution to the decline rate. Soften the AVS check from "exact match required" to "match street number only." Allow CVV-mismatched authorizations to retry rather than auto-decline. Set a sensible velocity rule that doesn't reject a customer trying their card three times in five minutes, which is normal human behavior, not fraud.
Your First Chargeback Will Catch You Off Guard
You'll get one. Usually within the first 60 days. The reason will likely be "transaction not recognized" or "service not as described," and the dollar amount will be a refundable order you didn't realize the customer hadn't received yet, or a friendly fraud claim from a buyer who simply forgot they ordered.
The chargeback fee is on top of the refunded amount. Most processors charge $15 to $25 per dispute regardless of outcome. If you win the representment, you keep the sale revenue, but you don't get the chargeback fee back in most cases. If you lose, you're out the merchandise, the sale, the chargeback fee, and any related shipping cost. The math on a $35 product with a $20 dispute fee isn't pretty.
The card networks publish their chargeback ratio thresholds publicly. Visa's monitoring programs flag merchants exceeding 0.9 percent chargebacks-to-transactions, with stricter thresholds for excessive programs. Mastercard publishes parallel thresholds. Crossing them can mean program enrollment, fines, and in repeated cases, account termination. Track the ratio from day one, not after you've gotten the first warning letter.
When the Underwriting Team Wants Another Look
The most common reason new merchants see their funds frozen in the first month is exceeding the projected sales volume listed on their underwriting application. If you told the processor you'd do $20,000 a month and you do $80,000 in your first three weeks, the system flags the account for re-underwriting. That's a freeze.
What that looks like in practice: a hold notice on incoming deposits, a request for additional documentation, and a delay of one to two weeks while the risk team reviews bank statements, fulfillment evidence, and your marketing materials. The Consumer Financial Protection Bureau has documented patterns where merchants in this position receive limited communication during the review, leaving them unable to plan around the freeze. Your remedy is to over-communicate with the risk team, send everything they ask for the same day, and be ready to update your projected volume on file.
You can avoid most of these reviews by giving the processor a heads-up before you launch a campaign you know will spike volume. A short email explaining you're running a promotion or expecting a press placement creates a paper trail that the risk system can reference. It doesn't always prevent a hold, but it shortens one substantially when it happens.
Set Up Reporting Before the Volume Gets Heavy
Reconciliation in month one is easy. You can probably eyeball your daily batch totals against your bank deposits in five minutes. Reconciliation in month four, after you've got refunds, chargebacks, reserve holds, processing fees, gateway fees, and a sales tax engine all stacking on the same transactions, is much harder.
Set up the systems while volume is still low. Connect your processor's reporting export to your accounting software. Create a transaction log that includes gross sale, processor fee, gateway fee, refund (if any), reserve held (if any), and net deposit. Tag every transaction with a source so you can isolate which marketing campaign generated which sales. Build a daily reconciliation habit that takes five minutes when volume is small and won't take five hours when volume isn't.
Your accountant will thank you. Your auditor, if you ever face one, definitely will.
Required Records and Retention
PCI DSS requires merchants to retain transaction records and security-related logs for at least one year. Your card brand agreements often require longer for chargeback evidence, typically two years minimum. State sales tax authorities have their own retention rules that vary by state. Save everything for at least three years to cover the longest reasonable requirement, and keep redundant backups offline where a ransomware event can't reach them.
What Settles Down by Month Three
By month three or four, deposits arrive on schedule, decline rates settle into normal ranges, fraud flags trigger less often, and the underwriting team stops looking at every batch. You'll still get the occasional chargeback, but the rate stabilizes. Reserves either reduce or graduate off entirely, depending on the contract. The friction tax of month one becomes the operating cost of month three, which is much smaller and much more predictable.
If you're still picking your processor or considering a switch, our reviews of providers in this market cover what each one's onboarding looks like in practice and where new accounts tend to hit friction first.