Payment Processor Statements Decoded: How MCA Funders Read Square, Toast, and Clover Data

Are you a business owner rather than a broker? See what your business qualifies for.

Why Payment Processor Statements Matter in MCA Underwriting

When most brokers think about MCA underwriting documents, they picture bank statements. And yes, bank statements remain the cornerstone of any MCA submission. But in 2026, payment processor statements from platforms like Square, Toast, Clover, PayPal, and Stripe have become a powerful secondary data source that savvy brokers use to pre-qualify merchants faster and package deals more effectively.

Payment processor statements offer something bank statements can't always show cleanly: a granular breakdown of how a business earns its revenue. For retail shops, restaurants, and service businesses that run the majority of transactions through a point-of-sale (POS) system, the processor statement is often a more accurate representation of business health than the bank statement itself. That's because cash deposits, owner transfers, and loan proceeds can muddy bank statement revenue figures, while processor data reflects only actual sales transactions.

Understanding how funders interpret this data will help you identify stronger deals earlier, prepare better submissions, and avoid wasted time on merchants whose processor data disqualifies them before underwriting even starts. To build your core underwriting knowledge, first see our MCA glossary for terms like holdback, retrieval rate, and split funding.

The Major Processor Platforms and What They Reveal

Square

Square is the dominant processor for small retail businesses, food vendors, service providers, and mobile businesses. Square's monthly and annual summary reports include:

• Gross sales volume by week and month
• Number of transactions and average ticket size
• Card type breakdown (Visa, Mastercard, Amex, debit)
• Refund and dispute amounts
• Net deposits after Square fees
• Sales by item category (useful for determining industry fit)

Funders love Square data because it's standardized, hard to fabricate, and provides a clean month-by-month trend line. A merchant with 24 months of Square history showing consistent or growing gross sales is a much easier story to tell than one with lumpy bank deposits.

One nuance brokers miss: Square's gross sales figure includes tax collected and tips. When comparing to bank statement deposits, the net deposit (after Square's processing fee, typically 2.6% + $0.10 per swipe) is what actually hits the bank. If a merchant runs $80,000/month through Square but their bank shows only $72,000-$75,000 in deposits from Square, that's normal and expected. Funders know this.

Toast

Toast is the POS platform of choice for restaurants, bars, cafes, and food service businesses. Toast reports are slightly more complex than Square's because they include:

• Gross food and beverage sales
• Third-party delivery platform revenue (DoorDash, Uber Eats, Grubhub)
• Dine-in vs. takeout vs. online order breakdown
• Void and refund percentages
• Labor cost data (in some configurations)
• Average covers per day

For restaurant deals, the Toast statement is often more telling than the bank statement. A busy restaurant may have 40-50 separate bank deposits per month across credit card batches, delivery platform payouts, and cash deposits. Toast consolidates the card revenue cleanly.

One red flag funders watch for in Toast data: a high percentage of third-party delivery revenue (DoorDash, Uber Eats). Delivery platforms take 20-30% commissions, meaning the restaurant's true margin on that revenue is razor thin. A restaurant running 60%+ of volume through third-party delivery is a much riskier deal than one primarily doing in-house dining or direct online orders. If you're submitting restaurant deals, find MCA funders that specialize in restaurant businesses who understand this nuance.

Clover

Clover is popular with retail shops, salons, healthcare providers, and service businesses that process through traditional bank merchant accounts. Because Clover is distributed through banks and ISOs (not direct-to-merchant like Square), the processor statement format can vary more. That said, Clover reports typically include:

• Monthly transaction summaries
• Batch settlement reports
• Chargeback and dispute history
• Refund percentages
• Card-present vs. card-not-present breakdown

For brokers submitting Clover users, get at least the last 4 months of Clover batch settlement reports. These are usually available through the Clover dashboard or the acquiring bank's merchant portal. Funders will use these to verify that the card volume showing up on bank statements is legitimate and consistent.

Stripe and PayPal

Stripe is the dominant processor for e-commerce, SaaS, and online service businesses. PayPal covers a wide range of online merchants, freelancers, and small businesses. For these platforms:

• Stripe dashboard exports show gross payment volume, refunds, disputes, and net payouts by month
• PayPal statements show total received, fees, withdrawals, and dispute history
• For Stripe users, look for the payout schedule -- daily payouts are favorable; weekly or monthly may indicate higher chargeback risk

E-commerce merchants are a specialized niche -- find funders that work with e-commerce businesses and understand the Stripe/PayPal data they receive. For deals with significant online revenue, always pull both the Stripe or PayPal export and the bank statement so funders can reconcile the two.

What Funders Actually Look For in Processor Data

Once you understand what each platform reports, you need to know how underwriters use that data. Here are the key metrics funders pull from processor statements:

1. Gross Monthly Processing Volume (GMPV)

This is the most fundamental number. Funders use GMPV to determine how much revenue is flowing through the business. Most funders will calculate an offer as a percentage of GMPV -- typically 50-150% of monthly gross processing volume, depending on the merchant's risk profile and positions. Use our underwriting calculator to model offer amounts against different GMPV figures.

Key nuance: funders average GMPV over 3-6 months and often weight recent months more heavily. If the last 3 months are trending up significantly, the offer will reflect the stronger recent performance.

2. Transaction Frequency and Average Ticket Size

Funders prefer merchants with high transaction frequency and low average ticket size. A restaurant doing 150 transactions per day at an average of $45 is a much better MCA candidate than a landscaping company doing 8 transactions per month at $3,500 each. High-frequency, low-ticket businesses produce predictable daily ACH repayments. Low-frequency businesses are harder to collect from and have more erratic cash flow.

Ideal transaction profile for MCA:

• 100+ transactions per month (the more the better)
• Average ticket under $500
• No single customer representing more than 20-25% of volume

3. Consistency and Trend

Funders look at month-over-month consistency. They want to see that the merchant's processing volume is stable or growing, not declining or highly seasonal. A merchant who did $120k/month last year and is now doing $60k/month is a declining business -- funders will either pass or significantly reduce the offer.

If your merchant has a legitimate seasonal explanation (a landscaping company that processes more in spring/summer), have that conversation upfront and pull 12+ months of data to show the full seasonal pattern. Many funders that work with seasonal businesses will take an annualized view rather than penalizing a merchant for their slow season.

4. Refund and Chargeback Rate

High refund rates signal customer dissatisfaction or possible fraud. Most funders want to see refund rates below 5% and chargebacks below 1%. A merchant consistently running 10%+ in refunds is a red flag regardless of overall volume. For e-commerce merchants especially, Stripe chargeback rates are scrutinized heavily.

If you see elevated refunds in a merchant's processor data, ask for an explanation before submitting. A business that switched product lines, had a one-time bad batch of inventory, or recently resolved a customer service issue may have a perfectly valid reason for a temporary spike.

5. Deposit Reconciliation

Funders cross-reference the net processor deposits with what actually shows up on the bank statement. If a merchant reports $80,000/month in Square volume but only $50,000 in bank deposits that can be traced to Square, the underwriter will want to understand the gap. Common explanations include:

• Multiple bank accounts receiving deposits
• Merchant holding funds in Square Savings
• Cash outs via Square debit card before bank transfer
• Multiple business entities sharing processor accounts (a red flag)

Reconciliation gaps aren't always disqualifying, but unexplained gaps will slow or kill a deal. Resolve them before submission.

How to Use Processor Data in Pre-Qualification

One of the most valuable skills you can develop as a broker is using processor data to pre-qualify merchants before you spend time packaging a full submission. Here's a quick pre-qualification framework based on processor statements alone:

Quick Pre-Qual Checklist

• GMPV above $20,000/month? (minimum for most funders; $50k+ for better programs)
• 12+ months of processor history? (3 months minimum; 12+ for best rates)
• Refund rate below 5%?
• No major volume drops in last 3 months?
• Transaction frequency of 50+ per month?
• Single-entity account? (no shared processor across multiple businesses)

A merchant who passes all six of these should be a fundable deal at minimum. A merchant who fails two or more is likely a waste of your submission time -- or at minimum, needs more investigation and explanation before you go to a funder.

For more detailed pre-qualification guidance, see our MCA merchant pre-qualification checklist and our guide on bank statement analysis for brokers.

Packaging Processor Data in Your Submissions

When you submit a deal to a funder, how you present the processor data matters. Sloppy, incomplete, or unorganized processor data creates friction in underwriting and slows your approval. Here's how to package it right:

What to Submit

• Full monthly statements for the last 4-6 months from the processor dashboard (PDF export preferred)
• Annual summary if available (Square and Stripe both offer this)
• Bank statements for the same period to allow reconciliation
• Brief explanation in your deal notes of any anomalies (seasonal dip, one-time event, etc.)

Organizing the Package

Label each document clearly: "Square Statements - Jan-Jun 2026" rather than just dropping in raw exports. Funders process dozens of deals per day. A clearly organized submission gets reviewed faster and makes you look more professional -- which translates to better relationships with funder reps over time.

If you want to build the kind of funder relationships that get your deals reviewed first, read our guide on how to achieve preferred ISO status with funders. The quality and organization of your submissions is one of the primary factors funders evaluate when deciding who to elevate.

Common Scenarios and How to Handle Them

Scenario 1: High Processor Volume, Low Bank Deposits

Your merchant shows $90,000/month in Square but only $70,000 in bank deposits. Before submitting, ask the merchant directly: Do they have a Square Savings account? Do they use a Square debit card for business expenses? Do they have a second business account? Get the explanation in writing and include it in your submission notes.

Scenario 2: New Processor, Limited History

Your merchant just switched from Clover to Square 4 months ago. They have 4 months of Square data and 20 months of Clover data before that. Submit both. Funders can and will look at prior processor history if you provide it. Explain the switch in your notes (upgraded POS system, switched acquiring bank, etc.) so the underwriter doesn't waste time asking.

Scenario 3: Multiple Processors

Some businesses run multiple processors simultaneously -- Toast for in-house dining, DoorDash as its own payout stream, and Square for catering events. This is common and not a red flag, but it requires you to aggregate the data correctly. Submit each processor's statements separately and include a one-line summary in your deal notes: "Total monthly processing volume: $X (Toast $Y + Square $Z + DoorDash $W)."

Scenario 4: High Delivery Platform Percentage

Your restaurant merchant runs 70% of volume through DoorDash and Uber Eats. This is fundable but requires a funder that specializes in restaurant deals. Mainstream funders may pass or offer unfavorable terms because of the thin margins and dependence on third-party platforms. Use our funder directory to find funders with specific restaurant programs.

The Bottom Line for Brokers

Payment processor statements are an underutilized tool in most brokers' pre-qualification workflow. Getting comfortable with Square, Toast, Clover, Stripe, and PayPal data will help you:

• Identify strong deals earlier, before pulling bank statements
• Spot red flags that will kill a deal in underwriting
• Package submissions that get reviewed and approved faster
• Have more intelligent conversations with merchants about their business
• Build credibility with funder underwriters who see you sending clean, well-organized packages

The brokers who move quickly in this industry are the ones who can pre-qualify a merchant in 10 minutes based on a processor statement export. That speed compounds over hundreds of deals per year into a massive competitive advantage.

Ready to start finding funders that match your merchant's processor profile and revenue tier? Search our funder directory to compare programs, or create your free broker account to get direct access to ISO rep contact information for verified funders.