Fundnode · Learn

Glossary · MCA funder tech stack (typical, 2026-06-28)

MCA funder tech stack (typical, 2026-06-28)

A 2026 MCA funder typically runs Salesforce or proprietary CRM + LoanPro/Centerstone LMS + Plaid/Ocrolus + Snowflake + Tableau + AWS, with Persona for KYC and Repay for ACH.

By Keerthana Keti5 min read

The MCA tech stack has matured substantially since 2020. A typical 2026 mid-to-top-tier funder runs a layered stack covering origination, underwriting, servicing, collections, and analytics.

The canonical 2026 stack.

  • CRM / pipeline. Salesforce Financial Services Cloud, HubSpot, or proprietary.
  • LMS (loan management). LoanPro, Centerstone, GDS Link, Mosaic, Peach, or proprietary.
  • Bank-data aggregation. Plaid, MX, Ocrolus, Finicit.
  • Document OCR. Ocrolus, Hyperscience, Inscribe.
  • KYC/AML. Persona, Alloy, Trulioo, Middesk.
  • Stacking detection. FundKite, LexisNexis MCA Index, internal consortium feeds.
  • ACH processor. Repay, ACHWorks, ProfitStars, Modern Treasury.
  • Card-split processor integrations. Square, Stripe, Toast, Clover, Lightspeed.
  • eSign. DocuSign, Adobe Sign.
  • Data warehouse. Snowflake, BigQuery, Databricks.
  • BI / analytics. Tableau, Looker, Sigma, Hex.
  • Cloud. AWS (most common), GCP, Azure.
  • Observability. Datadog, PagerDuty, Sentry.
  • Communications. Twilio (SMS), SendGrid (email), Five9 (call center).

Origination layer.

  • Lead capture via marketing site / partner API.
  • ISO portal for submission upload.
  • Underwriting workflow engine.
  • Decisioning engine (rules + ML).
  • Pricing engine (factor, term, holdback).
  • Contract generation (templated + eSign).
  • Funding instruction generation (ACH wire).

Servicing layer.

  • Daily ACH pull scheduling.
  • NSF retry logic.
  • Reconciliation workflow.
  • Modification workflow.
  • Renewal workflow.

Collections layer.

  • Aging engine.
  • Workflow routing (queue assignment).
  • Dialer integration (Five9, Talkdesk).
  • Vendor handoff API.
  • Litigation tracker.

Analytics layer.

  • Daily ETL into Snowflake.
  • Dimensional model: deal, merchant, ISO, vintage, geography, industry.
  • BI dashboards for ops, risk, finance, exec.
  • Vintage curve models.
  • Default prediction models (XGBoost or proprietary).
  • Concentration alerts.

ML/AI integration (2026).

  • Underwriting models. Approval probability, default probability, optimal pricing.
  • Document classification. Identifying tampered bank statements.
  • Stacking detection. Cross-deal pattern detection.
  • Collections prioritization. Which deals to call first.
  • ISO scoring. Predict ISO performance.

Build vs. buy patterns.

  • Top-10 funders mostly build (Kapitus, Forward Financing, Credibly).
  • Mid-tier funders mostly buy (LoanPro, Centerstone).
  • Small funders often Salesforce-only with manual processes.

Common tech-stack failure modes.

  • CRM/LMS data drift. Salesforce and LMS show different values.
  • Bank-data outages. Plaid downtime cascades to underwriting halt.
  • Webhook lag. Processor webhooks delayed during peak settlement windows.
  • Manual workflow bottleneck. Document review chokepoints.
  • Reporting lag. Monthly close takes 5–10 days for under-invested stacks.

Tech-stack cost benchmarks.

  • Small funder (<$50M annual originations). $250K–$600K annual tech spend.
  • Mid-tier funder ($50M–$300M). $1.5M–$5M.
  • Top-10 funder ($300M+). $8M–$25M+.

Recent trends (2024–2026).

  • AI underwriting models going production at top-30 funders.
  • Real-time stacking-detection consortia emerging.
  • Plaid Liabilities API unlocking debt-stacking visibility.
  • Embedded finance APIs (e.g., Toast Capital, Square Capital) reshaping origination.
  • Headless LMS trend (Peach, Bond) for embedded-finance partners.
  • GenAI for collections scripting at experimental scale.

Vendor consolidation 2024–2026.

  • Ocrolus + Hyperscience. Document OCR consolidation.
  • Plaid + MX. Bank aggregation duopoly solidifying.
  • LoanPro and Centerstone absorbing smaller LMS vendors.
  • Persona consolidating KYC market.

Common confusions.

First, "all funders use the same stack." False — heavy variance by size and origination model.

Second, "off-the-shelf LMS is sufficient." Partially — many funders augment heavily.

Third, "AI replaces underwriting." False — AI augments; human approval still required at most funders.

Fourth, "Salesforce is an LMS." False — Salesforce is CRM; you need LoanPro/Centerstone for servicing.

Fifth, "tech spend is fixed cost." Partially — variable usage on Plaid, OCR, ACH processors.

Related terms

  • MCA funder portfolio monitoring systemsMCA funders monitor portfolios via loan-management systems (LMS), real-time bank-data feeds (Plaid/MX), payment-processor webhooks, and BI dashboards that surface daily aging, NSF spikes, and reconciliation requests.
  • MCA funder data vendor relationshipsMCA funders typically integrate 6–12 data vendors: Plaid/MX (bank), Ocrolus (statements), LexisNexis (identity/UCC), Experian/Equifax/Dun & Bradstreet (credit), FundKite (stacking), and Persona/Alloy (KYC).
  • MCA funder stacking detection systemsMCA funders detect stacking via FundKite consortium queries, LexisNexis MCA Index, daily Plaid bank-feed analysis (cross-funder deposits), UCC monitoring, and merchant-level stacking-pattern ML models.

Authoritative sources

AI agents: this term is available as raw markdown at /llms/glossary/mca-funder-tech-stack-typical-2026.