Your First 90 Days on a New Merchant Account: Volume Caps, Delayed Funding, and the Reviews That Trip Up New Businesses

Getting approved for a merchant account is an important milestone, but approval does not necessarily mean underwriting is permanently finished. Once transactions begin flowing, the processor, acquiring bank, payment facilitator, or risk team can compare real activity with the business profile presented during onboarding.

That comparison matters most when the account has little or no processing history. Actual transaction volume, average ticket, highest ticket, refund activity, chargebacks, sales channels, fulfillment patterns, fraud signals, and settlement behavior can provide information that simply was not available when the application was reviewed.

There is no universal card-network rule stating that every new merchant account must pass a formal 90-day probation period. Different processors and acquiring institutions use different underwriting models, monitoring systems, funding policies, and contractual terms. 

Some providers conduct periodic reviews based on internal risk criteria rather than a fixed schedule; for example, Square states that account-review frequency can range from monthly to annually depending on internal criteria.

Still, the first several weeks of processing are operationally important because the merchant is establishing its real payment history for the first time.

A useful way to understand the process is:

Approved Merchant Profile → Expected Volume & Ticket Size → Actual Processing Activity → Funding & Settlement → Fraud/Chargebacks/Refunds → Risk Monitoring → Possible Review → Stable Processing History

The safest approach is not to figure out how close a business can get to a risk threshold. It is to process consistently with the profile disclosed during merchant account underwriting, maintain good records, reconcile deposits, manage customers effectively, and communicate material changes before they occur.

For background on how processors assess a business before processing begins, this guide to how merchant accounts are approved explains the documentation, website, banking, processing-volume, and underwriting information commonly reviewed during onboarding.

What Happens During the First 90 Days of a Merchant Account?

The merchant account first 90 days should be viewed as an early operating period rather than a standardized industry probation program. During this period, a provider finally gets to see whether real payment activity resembles the estimates and business characteristics that supported approval.

A merchant may have told the underwriter that it expects a certain monthly processing volume, typical transaction size, highest transaction size, sales channel, product category, fulfillment period, and refund policy. Once processing starts, transaction data can confirm those assumptions—or reveal something materially different.

A processor risk review may consider factors such as:

• Total processing volume
• Average transaction amount
• Largest transactions
• Daily or weekly sales velocity
• Card-present versus card-not-present activity
• Keyed or manually entered transactions
• Refund frequency and amounts
• Chargeback activity
• Fraud indicators
• Transaction geography
• Settlement and deposit patterns
• Fulfillment exposure
• Products or services being sold
• Business-model consistency
• Merchant Category Code alignment

Network and acquirer risk programs illustrate why monitoring continues beyond onboarding. Mastercard has specifically highlighted ongoing merchant website review and transaction-pattern analysis, including abnormal transaction spikes, suspicious refund behavior, and inconsistent average ticket sizes. 

Visa likewise describes transaction-monitoring tools that evaluate patterns and transaction characteristics to identify potentially risky activity.

That does not mean an unusual transaction automatically creates an account problem. Businesses naturally grow, receive large orders, run promotions, experience seasonality, or change product mix.

The problem occurs when activity changes materially and the provider has insufficient information to understand why.

A newly approved online sporting-goods store, for example, might forecast $40,000 in monthly card sales with an average ticket around $120. If a successful promotion suddenly produces several times the projected volume and a cluster of transactions much larger than normal, the activity may warrant additional review even though the sales are legitimate.

The merchant’s job is not to suppress legitimate growth. It is to make legitimate growth understandable.

Why New Merchant Accounts Can Receive More Attention

A processor has much more information about an established merchant that has processed consistently for several years than it does about a newly opened business. A new merchant may have excellent financials and a legitimate operation, yet still lack historical transaction data showing how customers behave after purchases.

The uncertainty matters because card transactions can create obligations after the original sale.

Customers may request refunds. Cardholders can dispute transactions. Fraud can be identified after authorization. Merchandise may fail to arrive. A business that takes payment today for a service delivered months later creates future-delivery exposure that does not disappear just because the payment initially cleared.

These realities help explain why acquiring institutions care about:

• Fraud exposure
• Chargeback liability
• Refund obligations
• Fulfillment delays
• Future-delivery periods
• Rapid transaction growth
• Financial stability
• Customer complaints
• Business-model changes
• Prohibited or restricted activity

Visa’s Acceptance Risk Standards explain that acquirers should monitor changes in merchant credit risk, including increases in refunds or disputes, inconsistencies between current and historical business activity, and changes in delivery periods. 

The standards also recognize additional reviews, changes in reserve requirements, and funding holds as possible risk-management actions when supported by the merchant relationship and applicable policies.

Visa’s merchant-screening documentation describes acquiring due diligence as a tool for reducing exposure to fraudulent, unreliable, illegal, or otherwise problematic merchant activity. Its screening framework also recognizes issues such as excessive disputes, agreement violations, insolvency risk, suspicious activity, and processing transactions for third parties.

A merchant therefore should not assume that an approval email represents a promise that no additional information will ever be requested.

In fact, the merchant agreement may expressly authorize ongoing monitoring, document requests, payout changes, reserves, limits, or other remedies under specified conditions. Those rights vary by provider and contract, which is why merchants should read their own agreement rather than relying on generic industry claims.

An informative overview of common merchant service contract terms explains how processing limits, restricted activities, reserves, settlement provisions, business-model changes, and other contractual provisions can affect an account after approval.

Limited Processing History Creates More Uncertainty

The key issue is uncertainty, not an assumption that a new merchant is untrustworthy.

Imagine two businesses selling the same custom furniture. One has processed for three years with relatively consistent monthly volume, documented fulfillment, predictable refunds, and an established dispute history. The second begins processing this week and collects substantial deposits several months before delivery.

The second merchant may be perfectly legitimate, but the provider has less evidence showing what happens after those transactions settle.

A new merchant account review can therefore be triggered when real activity reveals exposure that was not obvious during initial underwriting. Examples include unexpectedly long fulfillment periods, unusually high ticket sizes, international expansion, sudden recurring billing, or significant prepayment.

The right response is transparency and documentation. Merchants should be able to explain what changed, why it changed, whether the change is temporary or permanent, and how customers will receive what they purchased.

This becomes especially important for startups experiencing rapid growth. Fast growth can be good for the business while simultaneously increasing the acquiring side’s potential exposure.

Merchant Account Volume Caps, Ticket Expectations, and Transaction Velocity

Merchant account volume caps are limits or approved processing expectations associated with the merchant’s underwriting profile. Depending on the provider and agreement, a merchant may have an approved monthly processing amount, maximum ticket, expected average ticket, transaction-frequency controls, or other parameters.

There is no standard monthly merchant volume cap for all businesses.

Individual providers may nevertheless impose account-specific limits. For example, Square’s payment limits guidance describes temporary caps that can restrict how much an account processes when transactions present increased potential payment-dispute exposure. That policy is specific to Square and should not be treated as a universal merchant-account threshold.

A neighborhood service company, enterprise software vendor, subscription merchant, online retailer, travel company, and high-volume supermarket have very different payment patterns. 

Underwriting decisions can reflect the business category, anticipated sales, fulfillment model, financial condition, prior processing history, dispute exposure, card-present versus card-not-present mix, and many other factors.

Some providers explicitly use payment limits. Square, for example, describes payment limits as temporary restrictions on the amount an account can process when transactions appear likely to create payment-dispute exposure. That is one provider’s policy, not a universal rule for all merchant accounts.

Merchants should therefore find the answer to a basic question as soon as the account opens:

What payment volume and ticket characteristics did the provider actually approve?

Do not assume the number submitted on an application automatically equals an approved contractual limit. Confirm the account terms.

Monthly Merchant Volume Cap vs. Sales Forecast

A sales forecast and an approved processing profile are related, but they are not necessarily identical.

Sales Forecast = the business’s expected economic activity

Approved Processing Volume = the payment activity the provider has underwritten or permitted under the account arrangement

Suppose a startup forecasts $150,000 in monthly revenue but expects only $90,000 to be paid by cards because some customers pay by ACH or invoice. The processor may underwrite the card-processing relationship around the expected payment mix rather than gross business revenue.

Problems can arise when a merchant’s card volume increases substantially beyond the profile known to the provider.

Exceeding an expected amount does not automatically mean processing will be shut down. Depending on the account, it could lead to no immediate action, an automated alert, additional documentation, a funding hold, a payment limit, a reserve review, or full underwriting review.

The merchant agreement and provider’s actual policies control the outcome.

Why Sudden Processing Volume Increases Can Trigger Review

Legitimate reasons for sudden growth include:

• A viral social-media campaign
• Seasonal demand
• A successful product launch
• Influencer promotion
• A large corporate order
• Expansion into a new geographic region
• Acquisition of another business
• A new retail location
• A new ecommerce channel
• A major recurring-billing launch

From the merchant’s perspective, these events are successes. From a risk system’s perspective, they may look like a significant departure from prior behavior until someone supplies context.

Mastercard has specifically recommended that acquirers monitor abnormal transaction spikes, suspicious refund patterns, and inconsistent average ticket sizes. That is why merely saying, “Sales went up because business is good,” may not be enough when the change is substantial.

Supporting information might include purchase orders, marketing plans, supplier invoices, inventory records, customer contracts, shipping capability, or updated financial projections.

Transaction Velocity and High-Ticket Activity

Transaction velocity describes the frequency, amount, or concentration of transactions over time. Risk systems may examine velocity because an unusual burst of payments can signal fraud, card testing, account compromise, a major promotion, or simply legitimate demand.

Mastercard’s Security Rules and Procedures require acquirers to monitor merchant transaction counts and values for abnormal or suspicious increases. For a new merchant without sufficient historical activity, Mastercard says monitoring parameters should reflect expected turnover from the merchant’s business plan rather than relying on an established processing history.

Merchants should not seek or rely on “safe” velocity thresholds. Exact monitoring logic is provider-specific, frequently confidential, and may combine many signals rather than one cutoff.

High-ticket transactions present a similar issue.

One sale far above the account’s normal or approved ticket profile can create greater financial exposure if it later becomes fraudulent, disputed, refunded, or undelivered. The provider may therefore request documents confirming what was sold and how the order will be fulfilled.

A legitimate merchant expecting a large transaction should consider contacting its processor beforehand, especially when the transaction falls well outside ordinary activity.

How to Increase a Merchant Account Volume Cap Legitimately

When sustained growth is approaching the limits or assumptions of an existing profile, the merchant should request an increase rather than trying to work around the account.

A practical workflow is:

1. Contact the processor before the expected increase: Explain when additional volume is expected to begin.
2. Describe the business reason: Identify whether the increase comes from marketing, seasonality, contracts, additional locations, or another legitimate source.
3. Provide updated projections: Include expected monthly volume, average ticket, largest expected ticket, and timing.
4. Supply requested evidence: Financial statements, bank statements, contracts, invoices, inventory documentation, or prior processing statements may be requested.
5. Disclosing new products or channels: Ecommerce, recurring payments, international sales, mobile transactions, or other additions can change the risk profile.
6. Confirm fulfillment capacity: A large sales increase is less reassuring if the merchant cannot deliver orders.
7. Obtain written confirmation: Preserve communications showing approved changes to limits or profile assumptions.

Never Split Transactions to Avoid a Volume Cap

Merchants should not attempt to make activity look smaller or different merely to avoid monitoring.

Problematic behavior can include:

• Artificially shifting transactions between unrelated merchant IDs
• Opening duplicate accounts to hide total volume
• Breaking transactions into smaller charges to defeat controls
• Running another business’s payments through the account
• Hiding new products or services
• Misrepresenting the business category
• Routing payments through a different merchant simply because the original account is under review

Visa’s merchant-screening documentation identifies processing transactions for a third party and agreement violations among serious merchant-risk concerns.

Separate MIDs can be entirely legitimate when they represent real locations, legal entities, brands, channels, or operational structures approved by the acquiring institution. What matters is that the configuration accurately reflects the business rather than being designed to conceal activity.

New Merchant Account Delayed Funding, Settlement Holds, and Reserves

A new merchant account delayed funding situation can be stressful because the merchant may already have shipped goods, paid employees, or committed to suppliers.

The first step is determining what “delay” actually means.

Authorization, capture, clearing, settlement, provider funding, and final bank posting are not the same event. An approved card transaction does not mean the money immediately becomes spendable in the merchant’s bank account.

The Federal Reserve’s materials on merchant acquiring describe a flow in which merchant transactions move through batch processing, clearing, settlement, the acquiring side, and ultimately merchant funding.

For a deeper explanation of this distinction, see payment authorization versus settlement and how merchants get paid after card transactions. These resources explain why authorization, settlement, processor funding, and the bank deposit can occur at different times.

Possible reasons for a funding difference include:

• Standard settlement timing
• Batch cutoff times
• Weekends
• Banking holidays
• First-deposit procedures
• Bank-account verification
• Receiving-bank posting schedules
• Incorrect banking details
• Risk review
• Large or unusual transactions
• Unexpected processing volume
• Refunds or chargebacks
• Reserve deductions
• Other adjustments permitted by the agreement

A delayed deposit is therefore an operational signal to investigate—not proof that the account is being terminated.

Normal Settlement vs. Risk-Related Funding Hold

Situation	Possible Explanation	Recommended Merchant Action
Weekend delay	Banking or processor schedule	Compare the deposit against the documented funding calendar
First settlement	Initial funding or bank verification procedure	Confirm account details and first-payout requirements
Unusually large batch	Batch is materially outside historical activity	Preserve invoices and fulfillment documentation; contact provider if requested
Sudden volume spike	Actual activity exceeds expected profile	Explain the source of growth and provide updated projections
Bank-account verification	Deposit instructions changed or require confirmation	Complete verification through official provider channels
Underwriting review	New risk information requires evaluation	Respond promptly and accurately to document requests
Reserve withholding	Contractual reserve terms are being applied	Review the reserve notice, amount, release conditions, and agreement

Stripe’s current service terms, for example, distinguish the payout schedule from circumstances in which a provider may impose an initial holding period, delay payout, establish a reserve, or suspend transaction processing under specified risk conditions. 

These provisions demonstrate why merchants must read the particular contract governing their account rather than assuming every provider follows the same funding rules.

First Deposit Delays

An initial deposit can sometimes differ from later routine funding.

Possible reasons include settlement-account verification, first-batch procedures, an initial holding period permitted under the agreement, bank processing, or simply misunderstanding the provider’s stated payout schedule.

There is no universal first-deposit timeline that applies to every merchant account.

A merchant that was told “next-day funding,” for example, should determine precisely what that means. Does the timeline begin after batch cutoff? Are weekends excluded? Are certain transactions ineligible? Is the first payout treated differently? Is “next day” the day the processor initiates the deposit or the day the receiving bank posts it?

Document these details before cash-flow planning depends on them.

Delayed Funding Is Not the Same as a Reserve

These concepts should not be used interchangeably.

Delayed Funding: Eligible settlement proceeds are released on a slower schedule or temporarily withheld before becoming available.

Reserve: Funds are specifically set aside under applicable account terms to cover potential obligations or risk exposure.

An account can have delayed funding without a rolling reserve. It can also have a reserve while the non-reserved portion continues to follow the regular payout schedule.

Current processor documentation illustrates these distinctions. Square describes a reserve as funds set aside to help cover disputes and explains that its rolling reserve structure can withhold part of qualifying card payments for later release. Stripe’s service terms separately address payout schedules, payout delays, and reserves.

Merchant Account Rolling Reserve

A rolling reserve generally withholds part of eligible processing proceeds and releases those funds later according to the provider’s reserve terms.

At a conceptual level:

Reserve Amount = Contract-Specified Percentage of Eligible Processing Volume

That formula is deliberately generic. There is no responsible universal percentage to publish because reserve amounts, transaction eligibility, release timing, reserve caps, review conditions, and replenishment rules vary by provider and merchant.

A rolling reserve is also different from several related structures:

• Rolling reserve: Portions of successive processing proceeds are held and later released according to reserve terms.
• Fixed reserve: A defined amount is maintained as security against potential obligations.
• Capped reserve: Funding into the reserve stops or changes when a specified contractual balance is reached.
• Delayed settlement: Entire eligible payouts or designated transactions follow a slower availability schedule rather than a percentage being placed into a reserve.

Specific terminology varies, so the agreement controls.

Why a Reserve May Be Added After Approval

A merchant approved without a reserve should not assume one could never be imposed later. Whether a provider has authority to change reserve requirements depends on the agreement and applicable law.

Potential risk developments include:

• Increased chargebacks
• Greater refund exposure
• Unexpected processing growth
• Material financial deterioration
• Longer fulfillment periods
• Increased prepayment
• Significant changes in transaction patterns
• New products or services
• Business-model changes
• Other circumstances specified in the agreement

Square’s current reserve guidance says factors can include prepayment for goods or services, dispute activity, inconsistent transaction sizes or processing methods, sporadic activity, and limited processing history.

The important question is not whether someone online considers the reserve “normal.” It is what the merchant’s notice and contract say about the amount, basis, release conditions, review process, and available remedies.

What Triggers a Payment Processor Underwriting Review?

Payment processor underwriting review does not necessarily end when the merchant account goes live. New information can justify additional review when the processor needs to understand whether the account still fits the business it approved.

Possible requests include:

• Recent bank statements
• Processing statements
• Supplier invoices
• Proof of inventory
• Purchase orders
• Fulfillment evidence
• Shipping records
• Customer agreements
• Ownership information
• Business licenses
• Financial statements
• Website information
• Refund and cancellation policies

No single list is mandatory for every merchant. The provider should tell the merchant what documents it requires.

The strongest trigger patterns generally involve material inconsistency between expected and actual activity.

Common Triggers for a New Merchant Account Review

A new merchant account review may follow:

• Processing materially above the approved profile
• Very large tickets compared with expected ticket size
• Rapid transaction velocity changes
• Significant refund increases
• Rising dispute or chargeback activity
• Fraud patterns
• Customer complaints
• Fulfillment delays
• Long future-delivery exposure
• New product categories
• Different business activity from the assigned MCC
• New website or sales channel
• International expansion
• Subscription billing not previously disclosed
• New settlement bank account
• Ownership or legal-entity changes

Mastercard recommends ongoing website review to confirm that products, terms, branding, and other business information remain consistent with underwriting information. It also emphasizes checking whether merchant activity aligns with the assigned MCC. Visa’s current risk standards similarly say acquirers should review business activity when transaction or dispute information suggests that actual activity may not align with the assigned MCC.

For more detail on why accurate classification matters, see this explanation of Merchant Category Codes and how they affect underwriting and monitoring.

Refund and Chargeback Spikes

Refunds are a normal part of commerce. A sudden surge, however, can indicate a meaningful change in customer outcomes.

Possible causes include:

• Product defects
• Shipping delays
• Overpromising in advertising
• Failed launches
• Cancellation problems
• Billing confusion
• Inventory shortages
• Customer-service failures
• Fraud

Chargebacks deserve particular attention because a dispute can create financial exposure after the original payment.

Visa describes chargebacks as payment disputes that can result from true fraud, unrecognized transactions, dissatisfaction, authorization errors, duplicate processing, and other problems. Visa also recommends monitoring transaction activity, making policies clear, and communicating effectively with customers.

Early chargebacks can receive additional attention simply because the merchant has limited history against which to compare them. Merchants should not rely on generic internet claims about a universally “safe” dispute ratio. Networks and providers maintain their own monitoring programs and methodologies, and those programs can change.

A better objective is operational: reduce avoidable disputes by fulfilling orders correctly, making descriptors recognizable, communicating delivery expectations, processing valid refunds promptly, and monitoring fraud.

Business-Model and Website Mismatch

One of the most avoidable merchant account problems is operating a materially different business from the one that was approved.

Examples include:

• Approved for one-time retail sales but adding subscriptions
• Approved for domestic ecommerce but suddenly expanding internationally
• Approved for physical goods but switching primarily to digital services
• Adding a regulated or restricted product category
• Extending fulfillment from days to several months
• Taking payments for another company
• Moving from card-present transactions to mostly remote transactions

These changes do not necessarily mean the merchant account cannot support the new model. They mean the processor should be given an opportunity to evaluate the change.

A website review may examine products, pricing, refund policies, shipping information, terms, customer-service contacts, prohibited or restricted products, and checkout behavior.

The goal should be consistency:

Application → Website → MCC → Descriptor → Transaction Pattern → Fulfillment

When those pieces tell the same story, unusual activity is easier to explain.

Descriptor Reviews and Customer Recognition

A billing descriptor is the identifying information a cardholder sees for a transaction on a statement or banking interface.

If customers know a business by “North Valley Fitness” but their statements show an unfamiliar legal-company abbreviation, avoidable “I don’t recognize this” disputes may result.

Descriptors must comply with processor and network requirements, so merchants should not manipulate them deceptively. Instead, verify that the approved descriptor is recognizable, accurate, and appropriate for the transaction.

A merchant should also confirm that customer-service information shown at checkout, on receipts, in order confirmations, and in account statements is consistent enough for customers to connect the purchase with the business.

Changing the Settlement Bank Account

A bank-account change can trigger verification because controlling where merchant proceeds are deposited is financially sensitive.

A processor may need to confirm that the new account belongs to the correct business and that the person requesting the change is authorized. Extra verification is particularly sensible when a newly opened account changes deposit instructions shortly after onboarding.

Use only the provider’s approved bank-change process.

Do not send banking credentials through informal channels merely because someone claiming to represent the provider requests them. Confirm unusual requests independently using verified contact information.

How to Respond to a Funding Hold or Processor Review

A review is easier to resolve when the merchant treats it as a documentation problem rather than an adversarial negotiation.

The processor may simply be trying to answer several questions: What was sold? Was the cardholder legitimately charged? Can the business fulfill the order? Does the transaction match the approved business? Are future disputes or refunds likely? Is the settlement account valid?

A Practical Review Response Workflow

1. Respond promptly: Ignoring a legitimate underwriting request usually does not make it disappear.
2. Read the request carefully: Determine exactly which transactions, documents, or business changes are under review.
3. Provide accurate records: Submit the requested documents through the provider’s authorized secure process.
4. Never alter documentation: If a requested record does not exist, explain why rather than manufacturing one.
5. Explain unusual transactions: Provide concise business context for high tickets, volume spikes, refunds, or changed fulfillment.
6. Disclose upcoming changes: If another large promotion or new channel is imminent, mention it instead of creating a second surprise.
7. Maintain a communication log: Record dates, representatives, documents submitted, and requested follow-up.
8. Confirm resolution: Ask whether the review is closed and whether account terms, limits, funding, or reserves have changed.

Documentation that may be useful depending on the case includes supplier invoices, customer contracts, shipping tracking, proof of delivery, order records, financial statements, bank statements, or fulfillment timelines.

Requirements differ by provider.

What Not to Do During a Review

Never attempt to “fix” a review by making activity appear different from reality.

Do not:

• Create fake invoices
• Alter shipping records
• Hide products
• Falsify customer agreements
• Change descriptors deceptively
• Route volume elsewhere merely to escape scrutiny
• Process through another merchant’s account
• Submit transactions for another business
• Repeatedly rerun declined customer payments without a legitimate reason
• Break charges apart to defeat limits
• Misstate delivery dates
• Conceal a new business model

These actions can create a much larger risk problem than the transaction that triggered the review.

If information on file is wrong, correct it openly. A legitimate merchant benefits from making the processor’s understanding of the business more accurate, not less.

Merchant Account Suspension and How to Reduce Avoidable Risk

“Merchant account suspension” can refer to different operational situations, so a merchant should identify precisely what has been restricted.

A provider might:

• Prevent new card transactions
• Delay or suspend funding
• Restrict particular transaction types
• Impose a payment limit
• Request additional underwriting
• Establish or modify a reserve where contractually permitted
• Terminate the entire processing relationship

Suspension and termination are not interchangeable.

Some current provider agreements explicitly distinguish these remedies. Stripe’s service terms, for example, list payout delays, reserves, refusal of particular transactions, suspension of processing, and termination as separate possible actions under applicable contractual circumstances.

No checklist can guarantee that a merchant account will never be restricted. Fraud attacks, regulatory issues, network rules, legal requirements, or other events can occur even when the merchant operates responsibly.

But merchants can reduce avoidable surprises.

Key practices include:

• Process consistently with the disclosed business profile
• Monitor actual volume against approved expectations
• Track average and highest ticket sizes
• Manage valid refunds promptly
• Review disputes as they arrive
• Maintain fulfillment records
• Keep website information accurate
• Use appropriate fraud controls
• Keep the settlement account current
• Respond to underwriting requests
• Disclose material business changes
• Maintain applicable PCI DSS obligations
• Monitor processor emails and portal messages

For ecommerce businesses, payment security is part of this operating discipline. The PCI Security Standards Council notes that card-not-present environments need to be evaluated and protected under applicable PCI DSS requirements, and even outsourced ecommerce arrangements can leave merchants with specific responsibilities.

First 90 Days Checklist: Build a Stable Processing History

The following merchant first 90 days checklist is an operational framework, not an industry-mandated schedule.

Period	Main Focus
Days 1–30	Confirm funding, statements, descriptor, approved volume, ticket expectations, and reconciliation
Days 31–60	Review transaction trends, refunds, chargebacks, fraud signals, batch sizes, and projected growth
Days 61–90	Prepare for scaling, request legitimate limit changes, verify account profile, and document upcoming changes

The purpose of the framework is to identify problems while they are still small.

Days 1–30: Establish a Clean Baseline

During the first month, learn how the account actually behaves.

Confirm:

• Settlement bank account
• First deposits
• Batch cutoff schedule
• Funding schedule
• Approved monthly volume
• Expected average ticket
• Expected high ticket
• Billing descriptor
• Fees and statement structure
• Refund workflow
• Chargeback notification process
• Processor contact information
• Portal access
• Relevant reserve provisions

Reconcile frequently.

A simple payment trail is:

POS/Orders → Gateway → Processor Batch → Fees/Adjustments → Expected Deposit → Bank Deposit

If an ecommerce business collects $8,420 on Tuesday and receives $8,110 later, the finance team should know whether the difference represents net settlement, fees, refunds, adjustments, multiple batches, or something that needs investigation.

Do not wait until quarter-end to understand how deposits are calculated.

Days 31–60: Watch Emerging Patterns

Once several weeks of data exist, trends become more meaningful.

Review:

• Approval and decline patterns
• Monthly processing volume
• Average ticket
• Largest ticket
• Refund activity
• Chargebacks and inquiries
• Fraud declines
• Batch sizes
• Keyed transactions
• Funding delays
• Customer complaints
• Product and channel mix

The goal is not to panic about every fluctuation. The goal is to recognize when actual behavior is becoming materially different from what the processor originally understood.

Suppose an ecommerce merchant’s average sale remains stable but monthly volume is climbing quickly because a campaign is succeeding. That is generally easier to explain than unexplained growth accompanied by larger tickets, new international orders, more refunds, and a new product category.

Look at patterns together rather than in isolation.

Days 61–90: Prepare for Growth

By the final third of the framework, the merchant should have enough information to improve its processing forecast.

Consider upcoming:

• Marketing campaigns
• Seasonal peaks
• Product launches
• Subscription offerings
• Sales-channel changes
• Additional locations
• New geographic markets
• Major customer contracts
• Increased average ticket
• Large one-time orders

If sustained growth is likely to exceed the approved account profile, request a limit or underwriting update before it becomes urgent.

An underwriter reviewing a planned increase can consider projections and documentation. An underwriter reacting to repeated unexplained excess volume may have to make a decision while transactions and funding are already active.

Merchant First 90 Days Dashboard and Reconciliation Routine

A small-business owner does not need an elaborate risk department to manage a new merchant account well. A basic spreadsheet or reporting dashboard can make changes visible.

Metric	Why Monitor It
Monthly processing volume	Shows growth relative to approved expectations
Average ticket	Reveals changes in customer purchase size
Largest ticket	Identifies transactions far outside normal activity
Refund activity	Highlights customer or fulfillment problems
Chargeback activity	Shows disputes requiring action
Fraud declines	Helps identify attacks or changes in customer mix
Expected settlement	Establishes what the processor should fund
Actual deposit	Confirms what reached the bank
Funding delay	Identifies timing exceptions
Reserve withheld	Separates reserve activity from other deposit differences

Do not force universal target percentages into this dashboard. Compare performance against the merchant’s own history, contractual terms, network requirements, provider policies, and business model.

Daily Settlement Reconciliation

New merchants should reconcile settlement activity frequently until the process is well understood.

Start with completed orders. Match them to gateway and processor records. Confirm the batch. Account for refunds, reversals, fees, chargebacks, reserves, and other documented adjustments. Then compare the expected funding amount with the bank deposit.

Investigate differences promptly.

The first months often reveal operational issues that have nothing to do with underwriting: batches closing after cutoff, duplicated bookkeeping entries, gross-versus-net funding misunderstandings, refunds assigned to a later deposit, or bank posting differences.

Recognizing those issues prevents normal settlement timing from being mistaken for a funding hold.

Weekly Account Review

Once a week, review:

• Volume versus approved expectations
• Average and high ticket
• Refunds
• Chargebacks
• Failed payments
• Fraud alerts
• Funding
• Reserve activity
• Processor notices
• Upcoming campaigns

Also review manual-entry activity.

A card-present business that suddenly processes a large percentage of transactions as keyed card-not-present payments may look different from its approved operating model. Sometimes there is a legitimate explanation—such as temporary terminal failure or telephone orders—but the merchant should identify the cause.

Merchant Statements and Account Notices

Review the first merchant statements carefully.

Check:

• Pricing structure
• Monthly fees
• PCI-related charges
• Chargeback fees
• Adjustments
• Reserve activity
• Funding deductions
• Minimum or contractual fees where applicable
• Account identifiers
• Business information

Statements are not merely accounting records. They can reveal whether the account was configured as expected.

Monitor the processor portal and the official email address associated with the account as well. Underwriting requests, fraud notices, dispute alerts, reserve notices, or requests for additional information may have response deadlines.

Managing Growth, Ecommerce, Subscriptions, and Other Higher-Change Scenarios

Growth itself is not a merchant-account violation. Growth that materially changes the risk profile without corresponding communication can create avoidable friction.

This is especially relevant for businesses whose payment model can change quickly.

Large Product Launches and Seasonal Businesses

Before a launch expected to materially increase transaction count, monthly processing volume, ticket size, or geographic reach, contact the provider.

Explain:

• Launch date
• Expected duration
• Forecasted volume
• Expected average ticket
• Expected highest ticket
• Fulfillment capacity
• Inventory availability
• Refund policy
• Marketing source

Seasonal businesses should make seasonality clear during onboarding. A company that generates most of its card volume during a short annual period naturally looks different from a business with even monthly sales.

Accurate seasonality projections help the provider distinguish an expected peak from an unexplained spike.

Subscription Businesses

Recurring billing introduces additional operational considerations because the customer’s relationship with the merchant extends beyond the initial purchase.

Pay attention to:

• Clear customer authorization
• Accurate billing frequency
• Cancellation procedures
• Renewal communications
• Recognizable descriptors
• Stored-credential requirements
• Refund handling
• Customer support
• Applicable network rules

A merchant approved primarily for one-time transactions should not assume it can convert a large part of the business to recurring billing without telling the processor.

Subscriptions change how transactions are initiated and can change dispute exposure.

Preorders and Future Delivery

Preorders and future-delivery businesses deserve particular attention because the merchant may receive funds long before the product or service is delivered.

If a customer pays today for an event, custom product, trip, furniture order, or service delivered months later, the provider can face continued exposure if the merchant later fails to fulfill.

Maintain records showing:

• What was promised
• Expected fulfillment date
• Customer agreement
• Order status
• Supplier or inventory arrangements
• Shipping progress
• Refund terms

Do not disguise long fulfillment periods to obtain more favorable processing treatment.

New Ecommerce Merchants

New ecommerce merchants should give early attention to fraud and payment security.

Useful controls may include:

• Fraud screening appropriate to the business
• Address and identity signals where supported
• Strong checkout security
• Authentication where applicable
• Order review for suspicious high-value sales
• Shipping verification
• Protection of customer data
• PCI DSS compliance responsibilities

PCI SSC emphasizes that ecommerce merchants retain security obligations depending on how their payment system is implemented, even when a third-party provider performs part of the payment function.

A fraud-control strategy should reduce fraudulent orders without being designed around guessing the processor’s monitoring thresholds.

Card-Present and Keyed Transactions

Card-present merchants should train employees to use the intended acceptance methods, maintain terminal security, process EMV transactions properly, manage refunds consistently, and reconcile terminal batches.

Unexpected keyed transactions deserve attention.

Manual entry may be legitimate for certain businesses and scenarios, but a merchant underwritten as primarily card-present can create a different risk profile if substantial volume suddenly becomes keyed.

If the business is adding phone orders, remote invoices, ecommerce, mobile sales, or another new channel, confirm that the processing setup supports it.

Documents, Forecasting, and Communication That Make Reviews Easier

Good payment operations depend on records that can explain the merchant’s activity without reconstructing the business from memory.

Documents worth maintaining may include:

• Business formation records
• Business licenses where applicable
• Bank-account documentation
• Supplier invoices
• Inventory records
• Customer invoices
• Contracts
• Fulfillment records
• Shipping and tracking information
• Refund and cancellation policies
• Processing statements
• Ownership records
• Website screenshots where useful

Do not submit sensitive information unless requested through an authorized channel. The purpose of keeping records ready is faster legitimate verification—not sending every document proactively.

Maintain a Processing Volume Forecast

A rolling payment forecast can help a merchant identify growth before it reaches the processor’s risk system.

Month	Expected Volume	Expected Average Ticket	Expected High Ticket	Reason for Change
Month 1	Internal forecast	Internal forecast	Internal forecast	Baseline
Month 2	Internal forecast	Internal forecast	Internal forecast	Campaign/seasonality
Month 3	Internal forecast	Internal forecast	Internal forecast	New product/channel

Update the forecast when meaningful new information appears.

If a campaign changes expected card volume materially, compare the new forecast with approved processing expectations. That is the time to contact the provider—not after multiple months have already exceeded the expected profile.

Keep a Processor Communication Log

Track:

• Date
• Provider representative
• Issue
• Transactions involved
• Documents requested
• Documents submitted
• Promised action
• Account changes
• Resolution

Written records are particularly valuable when a volume increase, bank change, reserve adjustment, or business-model update is discussed across several departments.

Do not rely solely on remembering a telephone conversation from six weeks ago.

Common First-90-Day Mistakes to Avoid

Many early merchant account problems are not caused by a merchant intentionally doing something wrong. They come from businesses growing faster than expected, misunderstanding funding, failing to monitor communications, or treating the merchant account as a passive utility.

Common mistakes include:

• Exceeding expected processing volume without communication
• Accepting unusually large transactions inconsistent with underwriting
• Ignoring unexplained deposit delays
• Missing processor emails
• Failing to reconcile settlements
• Allowing refunds to accumulate
• Weak ecommerce fraud controls
• Changing product categories without disclosure
• Operating under an inaccurate MCC
• Switching settlement bank accounts without proper verification
• Processing transactions for another business
• Splitting transactions to avoid account controls
• Expanding into new payment channels without updating the provider
• Assuming initial approval prevents future underwriting review

The broader lesson is consistency.

The merchant’s business records, website, product offering, MCC, descriptor, transaction behavior, fulfillment model, processing volume, and communications should describe the same operation.

A significant mismatch between those elements is much more likely to create questions than ordinary day-to-day variability.

Merchant Account Stability Checklist and Questions to Ask at Opening

Use this checklist during the first 90 days and again whenever the business changes materially.

Area	What to Verify
Approved monthly volume	Confirm the processor’s actual approved expectation or limit
Average/high ticket	Confirm expected transaction profile
Funding schedule	Understand batch cutoffs and payout timing
Settlement bank account	Verify correct ownership and routing details
Reserve terms	Determine whether a reserve exists and how it works
Descriptor	Make sure customers can recognize charges
Refund policy	Keep it accurate and accessible
Chargeback monitoring	Know where disputes are reported
Fraud controls	Match controls to sales channels and risks
Website/products	Keep them consistent with underwriting
Processing channels	Confirm ecommerce, retail, recurring, mobile, or MOTO activity
Processor notices	Monitor portal and authorized email
Daily reconciliation	Compare expected and actual funding
Growth forecast	Identify volume changes before they arrive

At account opening, ask the processor:

• What monthly processing volume was approved?
• Is there a maximum ticket or expected ticket range?
• What funding schedule applies?
• Are initial funding procedures different?
• Is a reserve currently in place?
• How do reserve releases work?
• What account changes require underwriting?
• Who should we contact before a major volume increase?
• How will funding holds be communicated?
• What documents may be requested during a review?
• Where can we see disputes and chargebacks?
• How do we request a higher processing limit?
• What should we do before changing sales channels?
• Which portal notices and email addresses should we monitor?

These questions turn vague expectations into specific operational information.

What Happens After the First 90 Days?

A stable first three months can create a useful processing history, but ongoing merchant account monitoring does not end on day 91.

Processors, acquirers, payment facilitators, card networks, and fraud systems can continue evaluating transaction behavior, chargebacks, fraud, business activity, compliance, financial exposure, and other risk factors.

Mastercard’s merchant-risk recommendations expressly address ongoing website and transaction-pattern monitoring. Visa likewise maintains ongoing acquiring and merchant-risk programs rather than treating approval as the final point of oversight.

The advantage of a successful early period is that the merchant now has real data.

Instead of relying only on projections, the business can demonstrate transaction volume, ticket distribution, fulfillment, refunds, disputes, deposit history, and operational controls.

That history can also support legitimate future requests for higher processing limits or other account changes.

The best long-term approach remains the same:

Operate consistently, reconcile carefully, communicate material changes early, maintain accurate records, and treat processor notices as operational priorities.

Frequently Asked Questions

Conclusion

The first 90 days on a new merchant account are best treated as a period for establishing a reliable processing history—not as a universal network-mandated probation period.

A processor approved the account using information about the merchant’s business, expected processing volume, ticket size, channels, products, fulfillment, banking, ownership, and risk profile. Once live transactions begin, actual activity gives the provider a way to test whether those assumptions still make sense.

Merchant account volume caps, delayed funding, reserves, high-ticket reviews, and underwriting requests should therefore be viewed in context.

There is no universal monthly volume cap, reserve percentage, funding-delay period, ticket threshold, or suspension trigger. The merchant’s agreement, provider policies, acquiring relationship, network requirements, and actual risk characteristics determine what applies.

For new merchants, the most effective operating strategy is straightforward:

• Know the approved processing profile.
• Reconcile deposits frequently.
• Understand settlement and funding timing.
• Track volume and ticket changes.
• Watch refunds and chargebacks.
• Keep fulfillment evidence.
• Maintain fraud and payment-security controls.
• Keep the website and business model consistent with underwriting.
• Monitor processor notices.
• Communicate material growth or operational changes before they create surprises.
• Request legitimate limit increases instead of trying to avoid controls.

A growing business should not be afraid of processing more legitimate sales. It should make sure its payment provider understands why those sales are increasing and that the merchant account is structured to support them.

That discipline turns the first several months from a period of uncertainty into the foundation for more predictable funding, better reconciliation, stronger processor communication, and a processing history that can support future growth.

This article is for general payment-processing, operational, contract, and compliance information. Merchant-account terms, funding schedules, reserves, processing limits, underwriting requirements, network obligations, and legal rights vary. Review your merchant agreement and applicable provider documentation, and consult appropriate professional advisers when necessary.