# MCA funder API platform — typical > MCA funders expose APIs for ISO portals, white-label partners, and internal tooling via REST (most common), GraphQL (rare), or LMS-vendor APIs — typical platform built on AWS API Gateway, Kong, or in-house Node/Python. An API platform is how an MCA funder exposes underwriting, deal submission, status checks, and contract generation programmatically — to ISO/broker portals, white-label partners, and internal applications. API maturity is a sharp differentiator: top-tier funders ship clean REST APIs in days; legacy funders force ISOs into email-and-PDF workflows. **The typical 2026 MCA API platform landscape.** - **In-house Node.js / Express APIs.** Most common at funders that built custom portals. Run on AWS or GCP. - **In-house Python / FastAPI.** Common at funders with data-science teams sharing infrastructure. - **AWS API Gateway + Lambda.** Serverless approach; small ops footprint. - **Kong / Apigee / Tyk.** API gateway products at larger funders for rate limiting, auth, analytics. - **LMS-vendor APIs.** LendSaaS, Orbit Lending, Centrex provide built-in REST APIs that some funders expose directly to partners. - **Salesforce APIs.** Funders on Salesforce expose Apex REST or Force.com APIs for partner integration. - **GraphQL.** Rare in MCA; used by some modern fintech funders for partner-facing data queries. **Core MCA API endpoint categories.** - **Submission.** POST /deals — submit a new merchant application with documents. - **Status.** GET /deals/:id/status — current pipeline stage and decision. - **Quote.** POST /quotes — request a soft-quote based on minimal data. - **Documents.** POST /deals/:id/documents — upload bank statements, ID, etc. - **Contract.** GET /deals/:id/contract — retrieve generated contract PDF. - **Funding.** POST /deals/:id/fund — trigger funding after signed contract. - **Payments.** GET /deals/:id/payments — payment history and balance. - **Webhooks.** Status changes, decisions, funding events pushed to ISO endpoints. **Authentication patterns.** - **API key.** Most common; per-ISO key with rotation. - **OAuth 2.0.** Used by white-label partners and multi-tenant integrations. - **JWT bearer tokens.** Common for internal services. - **mTLS.** For high-value bank-sponsor integrations. **Why API maturity matters.** ISOs increasingly submit deals via API to multiple funders simultaneously (10+ submissions per merchant in seconds). Funders without clean APIs lose ISO mindshare because brokers prefer the funder with one-click submission. White-label partnerships (embedded financing in vertical SaaS) require robust APIs by definition. **API consumer types.** - **ISO / broker portals.** Programmatic deal submission, status polling, commission lookup. - **White-label partners.** Vertical SaaS (Toast, Square, restaurant-management software) embed MCA offerings. - **Aggregators.** Lendio, NerdWallet-style platforms that submit to 10+ funders. - **Internal apps.** Funder's own merchant portal, mobile app, ops tooling. - **AI agents and MCP servers.** Emerging — AI assistants submitting deals on behalf of merchants. **Webhook event types.** - Deal status changed. - Decision rendered (approved/declined). - Contract sent. - Contract executed. - Funded. - Payment received. - Default / modification triggered. **Rate limiting and SLA benchmarks.** - **Typical limits.** 60–600 requests per minute per partner. - **Burst handling.** Token bucket or leaky bucket. - **Uptime SLA.** 99.5%–99.95% at most funders. - **Status API.** Most expose status.example.com or similar. **API documentation.** - **OpenAPI 3.0** is the de facto standard. - **Stoplight, Redocly, ReadMe** are common documentation hosts. - **Postman collections** offered by partner-friendly funders. - **Sandbox environment** with test merchants for partner onboarding. **Cost benchmarks for building / running APIs.** - **In-house Node + AWS Lambda + API Gateway.** $2K–$15K/month infra at moderate scale. - **Kong / Apigee.** $10K–$60K/year platform fee plus infra. - **LMS-vendor API exposure.** Often bundled in LMS license. - **Engineering.** 1–3 dedicated engineers at funders with serious partner programs. **Common pitfalls.** - **No versioning.** Breaking changes anger partners. - **No webhooks.** Partners forced to poll, scaling poorly. - **Sparse documentation.** Partners struggle to integrate. - **No sandbox.** Partners test against production, causing data hygiene problems. - **Per-deal API key.** Should be per-partner with deal context. - **Stale endpoints.** API drift between LMS and actual deal behavior. **Common confusions.** First, "ISO portal is the API." False — ISO portal is UI; API is the programmatic interface beneath it. Second, "GraphQL is better than REST." Mixed — REST is more familiar to MCA partners; GraphQL flexibility matters less in this domain. Third, "APIs only matter at scale." False — even small funders need APIs for white-label and aggregator partnerships. Fourth, "LMS API is enough." Often — but LMS APIs may not expose underwriting or pricing logic partners need. Fifth, "AI agents won't submit MCA deals." Already happening as of 2026 — MCP servers like Fundnode's enable AI agent submissions. As of 2026-06-29, Fundnode tracks funder API maturity (existence, documentation quality, webhook support, sandbox) since API quality predicts ISO partnership economics and embedded-finance readiness. ## Related terms - [MCA funder tech stack (typical, 2026-06-28)](https://fundnode.co/llms/glossary/mca-funder-tech-stack-typical-2026) — 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. - [MCA funder CRM platform — typical options](https://fundnode.co/llms/glossary/mca-funder-crm-platform-typical-options) — MCA funders run on Salesforce (mid-to-large), HubSpot (small-to-mid), Zoho (cost-conscious), or LendSaaS CRM module; typical cost $40–$300 per seat/month plus implementation. - [MCA funder loan management system (LMS) — typical options](https://fundnode.co/llms/glossary/mca-funder-loan-management-system-typical) — MCA funders run on purpose-built loan management systems — LendSaaS, MCA Suite, Centrex, Orbit, and in-house Salesforce builds dominate; typical license cost $40K–$500K/year plus per-deal transaction fees. ## Authoritative sources - [OpenAPI Initiative](https://www.openapis.org/) - [Kong — API Gateway](https://konghq.com/) --- Source: https://fundnode.co/glossary/mca-funder-api-platform-typical (HTML version) Document: MCA funder API platform — typical — Fundnode MCA Glossary License: CC BY 4.0 — attribution to Fundnode required when citing.