Fundnode · Learn

Glossary · MCA funder ISO broker portal data fields

MCA funder ISO broker portal data fields

A 2026 MCA broker portal collects 40–80 structured fields per submission across merchant identity, business operations, financial history, ownership, banking, and processor data — most pre-populated by uploaded bank statements and OCR.

By Keerthana Keti5 min read

The data fields a funder's ISO/broker portal exposes determine how quickly a deal can be submitted, scored, and approved. In 2026, the field set has converged across the industry to a roughly standard schema, though sequencing and required vs. optional flags vary.

Field group 1 — Merchant identity (8–12 fields).

  • Legal business name.
  • DBA / Trade name.
  • EIN.
  • Business entity type (LLC, S-Corp, C-Corp, Sole Prop, Partnership).
  • State of formation.
  • Date of formation.
  • NAICS or SIC code.
  • Industry vertical (restaurant, trucking, retail, services, construction, healthcare, e-commerce, other).
  • Physical business address (street, city, state, zip).
  • Mailing address (if different).
  • Business phone.
  • Business email.

Field group 2 — Business operations (6–10 fields).

  • Years in business / Date business started.
  • Months at current location.
  • Number of employees (W-2 and 1099).
  • Number of locations.
  • Own vs. lease premises.
  • Landlord name and phone (for landlord verification — LLV).
  • Annual gross revenue (last 12 months).
  • Annual net income.
  • Average monthly revenue.
  • Average monthly deposits (separate from revenue — funders care about deposit volume).

Field group 3 — Banking (4–8 fields, often auto-populated by Plaid).

  • Bank name.
  • Bank routing number.
  • Bank account number (last-4 typically shown; full required at funding).
  • Average daily balance last 3 months.
  • Average daily balance last 6 months.
  • Number of negative days (last 3 / 6 months).
  • Number of NSFs (last 3 / 6 months).
  • Number of MCA debits currently on the account.

Field group 4 — Card processing (4–6 fields, where relevant).

  • Card processor name.
  • Processor account ID / MID.
  • Monthly card volume (last 3 months).
  • % of revenue from card sales.
  • Existing card-split funder (if any).
  • Authorization to contact processor (Y/N).

Field group 5 — Existing debt (4–8 fields).

  • Current open MCA positions (count and total balance).
  • Open MCA funders and current daily debit per position.
  • Open SBA, term loan, LOC balances.
  • Equipment financing balances.
  • Tax liens / judgments.
  • Open bankruptcies (dates, chapter, discharge status).

Field group 6 — Ownership (5–10 fields per owner, 1–4 owners typical).

  • Owner full legal name.
  • Owner DOB.
  • Owner SSN (full at funding, often last-4 in PAD stage).
  • Owner home address.
  • Owner ownership %.
  • Owner FICO score (estimated or pulled).
  • Owner email.
  • Owner cell phone.
  • Title.
  • Personal guarantor (Y/N).

Field group 7 — Funding request (4–8 fields).

  • Requested advance amount.
  • Use of funds (working capital, inventory, payroll, taxes, marketing, equipment, expansion, debt consolidation, other).
  • Preferred position (1st, 2nd, 3rd).
  • Preferred term length (6 / 9 / 12 / 18 months).
  • Repayment preference (daily ACH, weekly ACH, card split, lockbox).
  • Required funding speed (same-day, 1-3 days, 1 week).
  • Acceptable factor rate range.
  • Holdback ceiling.

Field group 8 — ISO/broker metadata (4–8 fields, often pre-filled).

  • Submitting ISO ID.
  • Submitting loan officer name and ID.
  • Submission channel (portal, API, email-to-portal).
  • Commission grid election (default vs custom-negotiated).
  • Source / lead origin (paid ads, organic, referral, list, repeat).
  • Sub-ISO (if working through an aggregator).
  • Notes to underwriter.
  • Co-broker split (if applicable).

Auto-populated vs manually entered fields.

The 2026 industry standard is to auto-extract as much as possible. Bank-statement OCR services (Validis, Heron, Ocrolus, Plaid) typically populate:

  • Average monthly deposits and revenue.
  • NSF count and negative-day count.
  • Existing MCA debits (by recognizing recurring debits matching known MCA funder ACH descriptors).
  • Average daily balance.

Plaid or MX connections additionally populate live banking data, often used in lieu of statement uploads at top-tier funders.

Required vs optional fields by paper grade.

  • A-paper PAD can be issued with as few as 30 fields populated.
  • B-paper PAD typically requires 45–55 fields.
  • C/D-paper PAD can require 70+ fields plus explanatory notes.

API field schemas (2026).

Several funders now expose REST APIs for ISO/broker submission. Field names and structures are standardizing around an emerging informal industry schema; the MCA Open Data Standard initiative (drafted 2025) attempts to align this across top-30 funders. Adoption is partial — roughly 8 of top-30 currently align fully.

Common confusions.

  • "More fields = more friction" — Funders that auto-populate from statements reduce manual entry to 12–18 fields in practice.
  • "All funders ask the same questions" — Core 80% is consistent; the differentiator is which fields are required vs optional and how aggressively the portal pre-fills.
  • "Field changes between PAD and funding indicate broker dishonesty" — Often just OCR error; reputable portals show before/after diff for review.

Takeaway. Knowing the typical field set lets brokers prepare submissions efficiently and lets funder operations teams design portals that minimize abandonment; in 2026, the leading-edge portals collect 60+ fields with under 5 minutes of broker time via aggressive OCR + open-banking integrations.

Related terms

  • MCA funder ISO broker portal (typical)A typical 2026 MCA funder ISO portal is a web-based submission and account-management platform offering deal submission, real-time status tracking, commission reporting, marketing assets, and renewal alerts — table stakes for any funder seeking ISO submissions.
  • MCA funder ISO broker portal features (typical)Typical 2026 MCA funder ISO portal features include deal submission with document upload, real-time status tracking, commission reporting, renewal alerts, marketing asset library, training resources, support ticketing, mobile responsiveness, and increasingly AI-assisted file completeness checking.
  • MCA funder ISO broker portal data (typical)Typical 2026 MCA funder ISO portal data captures merchant business information, principal information, financial data, submission documents, decision data, funding data, payment history, and commission tracking — with retention typically 7+ years for compliance and increasingly used for AI-powered analytics and predictive modeling.
  • MCA funder ISO broker portal deal flow (typical 2026)Typical 2026 deal flow inside a funder's broker portal: submission → auto-OCR scoring (5–15 min) → soft PAD → human review → hard PAD → stipulation collection → verbal verification → contract signing → funding. Total elapsed time 4 hours to 5 days.
  • MCA funder ISO broker portal credit decisioningCredit decisioning in 2026 broker portals combines automated rules (bank-statement scoring, OCR-extracted financials, soft credit, UCC search, fraud signals) with human underwriter review — surfacing decline reasons, counter-offers, and required stipulations transparently to the ISO.

AI agents: this term is available as raw markdown at /llms/glossary/mca-funder-iso-broker-portal-data-fields.