Payment-tracking is the daily operational view inside a funder's broker portal that lets the ISO monitor the health of every merchant in their funded portfolio. Strong payment-tracking infrastructure is what enables ISOs to intervene on NSFs before they cascade into default and to time renewal pitches optimally.
Core payment-tracking metrics per merchant.
- Original advance amount.
- Total repayment owed (advance × factor).
- Total repaid to date.
- Balance remaining.
- % paid back (drives renewal eligibility).
- Daily debit amount or current holdback %.
- Last successful debit date and amount.
- Last failed debit (NSF) date and reason.
- NSF count lifetime.
- Days-past-due (DPD).
- Projected payoff date (assuming current pace).
- Pace vs schedule (ahead / on / behind).
Daily debit status dashboard.
The default morning view for many ISOs. Shows for each merchant whose debit was scheduled the prior business day:
- Debit attempted (Y/N).
- Debit successful (Y/N).
- Amount pulled.
- Reason for failure (NSF, account closed, debit blocked, ACH return code).
- Number of cure attempts (most funders attempt 2–3 times within 48 hours).
NSF and return-code visibility.
ACH return codes are standardized (R01 = insufficient funds, R02 = account closed, R03 = no account, R04 = invalid account number, R08 = payment stopped, R09 = uncollected funds, R29 = corporate customer advises not authorized). Portals decode the raw codes into plain-English reasons. R01 (NSF) is the dominant return reason in MCA (~85% of returns).
Recovery actions tracked.
- Re-attempt scheduling (funder auto-attempts; some allow ISO to nudge).
- Merchant contact log (funder-side outreach to cure).
- Bank-of-record changes (merchant moved accounts).
- Restructure / reconciliation requests in flight.
- Payment plan modifications.
Pace and payoff projection.
A "pace vs schedule" chart compares cumulative payments against the schedule implied by the agreement. Merchants ahead of schedule are renewal-strong; merchants behind warrant intervention.
A "projected payoff date" updates daily. Funders typically also display a payoff quote valid for a short window (24–72 hours) that the merchant can act on if they want to early-pay.
Card-split vs daily-ACH tracking.
- Daily ACH: fixed daily dollar amount. Tracking is simple — pull / no pull.
- Card split: variable amount based on daily card sales. Tracking requires processor integration to show daily card volume + funder split. Some portals show per-batch detail.
- Lockbox: deposits routed into a lockbox account; funder sweeps. Tracking shows daily lockbox balance.
Reconciliation views.
If the merchant has invoked reconciliation (the contractual right to adjust payments when revenue drops), the portal shows:
- Reconciliation request date.
- New holdback % or new debit amount.
- Effective period.
- Outstanding "make-up" amount (if any).
- Status of the reconciliation review.
Default and collections visibility.
- Default trigger date.
- Days since default.
- Collections actions taken (notices, attorney engagement, COJ filed where applicable).
- Outstanding balance + accrued default charges.
- Settlement offers received.
- Bankruptcy / litigation flags.
Bank-statement re-pull integration.
Top-tier 2026 portals integrate with Plaid or MX for continuous bank-data visibility on the merchant's account, allowing ISOs to see:
- Recent deposit volume (revenue trend).
- New ACH debits (other MCA stacks).
- Negative balance days.
- NSF events including non-MCA ones.
This is a leading indicator of trouble that lags the funder's own debit history by days.
Notifications and alerts.
- NSF on a merchant: instant push/email/SMS to the originating ISO.
- 3+ NSFs in 30 days: escalation alert with recommended ISO action.
- Merchant reaches 50% paid: renewal-readiness alert.
- Merchant requests payoff: alert with payoff quote.
- Merchant defaults: alert with collections action plan.
Portfolio-level payment-tracking views.
- Default rate (last 30 / 90 / 365 days).
- NSF rate (last 30 / 90 days).
- Average DPD across portfolio.
- Renewal-readiness count.
- Total balance remaining across portfolio.
Reporting and export.
- Per-merchant payment history CSV/Excel.
- Per-month commission report tied to payments.
- Portfolio-health summary.
- API endpoints for ISO CRM ingestion.
Use cases for ISOs.
- Early intervention on NSFs: ISO calls merchant the morning of an NSF to understand cause and head off cascade.
- Renewal timing: ISO times renewal pitch around the day merchant crosses renewal threshold.
- Buyout opportunity: ISO sees a competitor's merchant becoming eligible for buyout based on balance + months remaining.
- Default exposure tracking: ISO sees their clawback exposure for the month.
- Cashflow forecasting: ISO projects commission income based on the portfolio's payment trajectory.
Common confusions.
- "NSF means the merchant defaulted" — False. One or two NSFs are common; default is typically 5+ business-day delinquency or specific contractual default triggers.
- "Payment tracking is a funder responsibility, not mine" — Partially true on collections, but the ISO is the relationship owner; proactive intervention preserves the renewal and the relationship.
- "All payment data is visible in real time" — Most portals are near-real-time (T+1 hours to T+1 day) rather than instantaneous.
Best-practice ISO behavior.
- Set a daily 10-minute morning review of NSFs and outreach to affected merchants.
- Pull a weekly portfolio health report.
- Track clawback exposure monthly.
- Cross-reference payment-tracking data with renewal-readiness flags weekly.
Takeaway. Payment-tracking views in 2026 broker portals are the operational nerve center of the funded book — they enable early intervention, renewal optimization, and clawback management; ISOs who treat the dashboard as a daily discipline outperform on retention and lifetime broker commission.
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 merchant management — Merchant-management features in 2026 broker portals let ISOs see the funded portfolio in real time — payment status, days-past-due, renewal eligibility, balance remaining, and merchant contact preferences — across all deals the ISO has originated with that funder.
- MCA funder ISO broker portal renewal process — Renewal in 2026 broker portals is mostly automated: merchants flagged eligible at 50%–60% paid down, pre-qualified offers generated automatically, ISO clicks to pitch, refinance closes in 1–3 days with the prior balance rolled into the new advance.
- Daily ACH debit (MCA) — A fixed-dollar daily withdrawal from the merchant's bank account during MCA repayment. The most common MCA repayment structure in 2026, distinct from card-sale split (holdback) structures.
- MCA bounce fee (NSF fee, returned ACH fee) — Fee the funder charges when a daily ACH debit fails for insufficient funds — typically $25-$50 per bounce, on top of the merchant's bank NSF fee. Often triggers default review at 3+ bounces.
AI agents: this term is available as raw markdown at /llms/glossary/mca-funder-iso-broker-portal-payment-tracking.