← Fundnode · Learn

Glossary · MCA funder ISO broker portal data (typical)

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.

By Keerthana Keti5 min read

MCA funder ISO broker portal data describes the specific data captured, stored, and used by funder ISO portals — including merchant business data, financial data, submission documents, decision data, payment history, and commission tracking. As of 2026-06-28, portal data has become increasingly valuable as funders deploy AI/ML on accumulated data and as data-sharing requirements expand under regulatory pressure.

Data category structure.

ISO portal data falls into categories:

  1. Merchant business data: Company information, operations.
  2. Principal data: Owner information, personal details.
  3. Financial data: Bank statements, revenue, expenses.
  4. Submission data: Application details, documents, ISO information.
  5. Decision data: Underwriting decisions, conditions, reasons.
  6. Funding data: Funded deals, terms, payment schedules.
  7. Payment history data: ACH payments, modifications, defaults.
  8. Commission data: ISO commissions, payments, clawbacks.
  9. Communication data: Notes, emails, calls.
  10. Compliance data: Disclosure delivery, audit trails.

Merchant business data fields.

Standard merchant data:

  • Business identification: Legal name, DBA, EIN, formation state, formation date.
  • Business contact: Address, phone, email, website.
  • Industry classification: NAICS code, industry description.
  • Business operations: Years operating, employee count, locations.
  • Banking information: Operating bank, account numbers (encrypted).
  • Processor information: Card processor, processing volume.
  • Existing financing: Other MCAs, loans, lines of credit.
  • Business performance: Monthly revenue, average daily balances.

Principal data fields.

For each principal (>25% ownership):

  • Identity: Full legal name, SSN (encrypted), date of birth.
  • Contact: Personal address, phone, email.
  • Ownership: Percentage ownership, role/title.
  • Credit information: Credit score (soft pull), credit history summary.
  • Background: Background check results.
  • Personal financial: Personal financial statement (if required).
  • Identification: Driver's license, passport scans.

Financial data fields.

Comprehensive financial data:

  • Bank statements: 3–6 months PDF/parsed data.
  • Bank account analytics: Average daily balance, deposit count, NSF count.
  • Revenue metrics: Monthly revenue, daily revenue patterns.
  • Expense patterns: Major payment categories, payment frequency.
  • Tax returns: Business tax returns if required.
  • Financial statements: P&L, balance sheet for larger advances.
  • Accounts receivable: AR aging if relevant.
  • Cash flow: Cash flow analysis from bank data.

Submission data fields.

Per-submission data:

  • Submission timestamp: Date/time of submission.
  • ISO information: ISO ID, sales rep, submission source.
  • Requested terms: Advance amount, term, use of funds.
  • Application data: Full application fields.
  • Documents uploaded: Document list with timestamps.
  • Pre-screen results: Soft credit, MCA history, knockout checks.
  • Submission status: Current stage in funnel.

Decision data fields.

Underwriting decisions:

  • Decision: Approved, declined, conditional, pending.
  • Decision timestamp: When decision was made.
  • Underwriter: Underwriter ID and team.
  • Decision rationale: Free-text and structured reasons.
  • Conditions: Pre-funding conditions (if conditional approval).
  • Approved terms: Advance amount, factor rate, term, payment.
  • Decline reasons: Standardized decline reason codes.
  • Counter-offer history: If terms were negotiated.

Funding data fields.

Per-funded deal:

  • Funding timestamp: When deal was funded.
  • Final terms: Final agreed terms.
  • Disbursement details: Amount disbursed, fees deducted.
  • Banking destination: Where funds were sent.
  • Contract documents: Signed agreements.
  • ISO commission: Commission earned by ISO.
  • Funding ID: Unique identifier for tracking.

Payment history fields.

Comprehensive payment tracking:

  • Payment schedule: Expected payments and dates.
  • Actual payments: Each ACH payment with date/amount.
  • Payment status: Successful, failed, modified.
  • NSF events: Insufficient funds events.
  • Reconciliations: Reconciliation requests and results.
  • Modifications: Term modifications, payment plan changes.
  • Default status: Default events with timestamps.
  • Collections activity: Collections actions if applicable.

Commission data fields.

ISO commission tracking:

  • Commission earned: Per-deal commission amounts.
  • Commission components: Base + bonuses + MDF breakdown.
  • Commission status: Pending, paid, clawed back.
  • Payment dates: When commissions were paid.
  • Clawback events: Clawback amounts and reasons.
  • Annual commission totals: Year-to-date and historical.
  • Tax reporting: 1099 information.

Communication data fields.

Interaction tracking:

  • Notes: Underwriter notes, ISO notes, account manager notes.
  • Emails: Email communications archived.
  • Phone calls: Call logs and recordings (where permitted).
  • Portal messages: In-portal messaging.
  • Chat sessions: Live chat transcripts.

Compliance data fields.

Regulatory documentation:

  • Disclosure delivery: When disclosures were delivered.
  • Disclosure acknowledgment: Merchant acknowledgments.
  • Compliance training: ISO training completion records.
  • Audit trail: Complete activity log.
  • Data retention compliance: Retention period tracking.

Data retention periods.

Standard retention:

  • Active loan data: Retained throughout loan life.
  • Funded merchant data: 7+ years post-payoff (regulatory requirement).
  • Submitted-but-not-funded: 3–5 years.
  • Communication data: 7+ years for compliance.
  • Compliance documentation: 7+ years.
  • Some data: Indefinite retention for analytics purposes.

Data security and privacy.

Standard protections:

  • Encryption at rest: AES-256 standard.
  • Encryption in transit: TLS 1.3 standard.
  • Access controls: Role-based access control.
  • Audit logging: All access logged.
  • PII redaction: Sensitive fields masked in some views.
  • Data segregation: ISO data isolated from other ISO data.
  • Backup and disaster recovery: Standard practices.

Regulatory compliance for data.

Applicable regulations:

  • GLBA: Gramm-Leach-Bliley Act for financial data.
  • CCPA/CPRA: California Consumer Privacy Act.
  • State data breach laws: All 50 states have breach notification laws.
  • Section 1071: CFPB small business lending data collection.
  • State disclosure laws: Data needed for disclosure compliance.
  • Anti-money-laundering: SAR reporting requirements.

Data analytics use cases.

How portal data is used:

  • Underwriting model training: Default prediction models.
  • Pricing optimization: Risk-based pricing models.
  • Fraud detection: Pattern recognition for fraud.
  • Renewal prediction: Identifying renewal candidates.
  • ISO performance analysis: ISO profitability scoring.
  • Marketing optimization: Channel attribution and ROI.
  • Portfolio analytics: Default rate, recovery rate analysis.
  • Regulatory reporting: Section 1071 and state reporting.

Data sharing patterns.

Common data sharing:

  • Funder-to-ISO: Decision data, commission data, performance metrics.
  • ISO-to-funder: Application data, documents, merchant data.
  • Funder-to-vendor: Data shared with credit bureaus, fraud services, collections.
  • Funder-to-regulator: Required regulatory reporting.
  • Funder-to-funder: Industry data sharing (DataMerch, others) on defaults/fraud.

AI/ML applications on portal data.

Increasing use of:

  • Predictive default modeling: Forecasting which deals will default.
  • Approval prediction: Real-time approval likelihood scoring.
  • Document classification: Auto-classifying uploaded documents.
  • OCR and data extraction: Extracting structured data from documents.
  • Anomaly detection: Identifying fraud or unusual patterns.
  • Recommendation engines: Suggesting actions to ISOs.
  • Natural language processing: Analyzing notes and communications.

Data quality challenges.

Common issues:

  • Incomplete merchant data: Required fields left blank.
  • Document quality: Poor-resolution document scans.
  • Inconsistent data: Same merchant data varies across submissions.
  • Stale data: Outdated information for repeat merchants.
  • Manual data entry errors: Typos and transcription errors.
  • Data integration failures: Mismatches between systems.

2026 data trends.

  1. AI-powered data extraction from documents automating data entry.
  2. Real-time data validation preventing errors at submission.
  3. Cross-funder data sharing for industry-wide fraud prevention.
  4. Open banking integration for direct bank data access.
  5. Privacy-preserving analytics with differential privacy techniques.
  6. Section 1071 implementation driving standardized data capture.

Data as competitive asset.

Funder data advantages:

  • Underwriting model accuracy improves with more data.
  • Pricing optimization through historical pricing data.
  • Risk segmentation more refined with larger datasets.
  • Fraud prevention stronger with cross-funder data sharing.
  • AI capability dependent on data quality and quantity.

Common confusions. - "All portal data is for compliance only." False — portal data drives analytics, underwriting models, and product development. - "Data retention is optional." False — regulatory minimums (7+ years) apply. - "ISO data is private to ISO." False — funder owns submission data subject to ISO agreement.

Takeaway. Typical 2026 MCA funder ISO portal data captures comprehensive merchant business, principal, financial, submission, decision, funding, payment, commission, communication, and compliance data with retention typically 7+ years. Data security follows industry standards (AES-256 encryption, TLS 1.3, role-based access). AI/ML applications on portal data (default prediction, document extraction, anomaly detection, recommendation engines) are increasingly central to funder competitive advantage. Section 1071 implementation and cross-funder data sharing are major 2026 trends reshaping data practices.

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 network economics — ISO broker networks in 2026 typically deliver 60–80% of an MCA funder's origination volume at all-in acquisition cost of 10–14% of advance (commission plus marketing reimbursements plus portal infrastructure), making ISO economics the single largest variable cost line in MCA P&Ls.
  • MCA funder ISO broker vetting process — MCA funder ISO vetting in 2026 is a 5–15 business day onboarding process including business verification, principals background checks, state licensing review, references from 3+ funder partners, compliance training, and tier-1 commission negotiation.

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