How Fox Ridge Capital's Credit Policy Build Reveals What MCA Underwriting Best Practices Look Like from Scratch

Building Credit Policy from Zero Is Rare. It's Also Revealing.

Most MCA funders inherit their underwriting workflows. They bolt new rules onto old processes, patch gaps when regulators come knocking, and layer verification steps on top of systems that were never designed for the volume they now handle. That is why Fox Ridge Capital's recent decision to appoint Stan Dumont as Senior Vice President of Credit is worth watching. According to deBanked's coverage of the hire, Dumont will "lead and define credit policy and governance from the ground up." That phrase, "from the ground up," is the key detail. It means Fox Ridge is not retrofitting. It is designing MCA underwriting best practices with a blank slate.

For funders and brokers reading this, the question is not whether Fox Ridge gets it right. The question is what a clean-sheet credit policy build tells us about where the industry's verification standards are heading, and whether your own workflows would survive the same level of scrutiny.

What Clean-Sheet Credit Governance Looks Like for MCA Funders

Starting with Verification, Not Scoring

When experienced credit leaders build from scratch, they almost never start with pricing models or risk tiers. They start with data integrity. The first question is always: how do we know the information in front of us is real? In MCA, that means bank verification comes before everything else. A funder can have the most sophisticated scoring algorithm in the industry, but if the bank statements feeding that algorithm are fabricated or manipulated, the model is useless.

This is where most legacy operations fall short. They added bank verification as an afterthought, a step squeezed into a workflow that was originally designed around phone calls and PDF submissions. A greenfield build has the luxury of putting verification at the center of the architecture. Every subsequent policy decision, from approval thresholds to stacking limits to holdback percentages, flows from verified data rather than assumed data.

The Equipment Finance Crossover Complicates Things

Fox Ridge describes itself as a "hybrid business equipment financing company," which means Dumont's credit policy will need to span both equipment finance and merchant cash advance workflows. This crossover is increasingly common in the alternative lending space, and it creates specific verification challenges. Equipment deals often require proof of business revenue alongside asset valuations. MCA deals require granular transaction-level bank activity. A single credit framework has to accommodate both, without letting the simpler verification requirements of one product type dilute the rigor needed for the other.

We have seen this pattern before. As we explored in our coverage of how equipment finance expansion is reshaping MCA underwriting workflows, funders that straddle multiple product lines often default to the least demanding verification standard across all products. That is a mistake. The merchant cash advance side of the business carries unique fraud vectors, including synthetic bank portals, manipulated transaction histories, and stacking across multiple funders, that equipment finance alone does not encounter with the same frequency.

Codifying Audit Trails from Day One

One advantage of building credit policy from scratch is the ability to embed audit trail requirements into every step before volume makes retrofitting painful. Funders that grow first and formalize later inevitably discover gaps when auditors, regulators, or prospective portfolio buyers ask for documentation of how specific funding decisions were made. The question is never "did you verify the bank statements?" The question is "can you prove it?"

This is the distinction between verification as a process and verification as a record. Live phone calls are a process. They happen, the underwriter makes a judgment, and the deal moves forward. But unless that call is recorded, timestamped, and stored with the deal file, there is no record. The same principle applies to screen-share sessions where an applicant walks through their banking portal in real time. The session happens, but the evidence disappears the moment the call ends.

Asynchronous bank verification solves this by design. When an applicant records their banking session through a tool like Exact Balance, the recording itself becomes the audit artifact. Every frame is timestamped. Every step is logged. The underwriter's review is documented. This is the kind of infrastructure that a clean-sheet credit policy should include from inception, not bolt on three years later when an investor or regulator asks uncomfortable questions. For context on why this matters during audit cycles, our analysis of how MCA audit season exposes bank verification documentation gaps covers the most common failures in detail.

Choosing Between API-Based and Visual Bank Verification

A credit leader building policy today faces a genuine architectural decision: rely on API-based bank data aggregation, use visual bank verification through recorded sessions, or layer both. Each approach has tradeoffs that matter for MCA specifically.

API-based connections pull structured data directly from banking systems. They are fast, automated, and excellent for transaction categorization and cash flow scoring. But they also have blind spots. Not every bank supports third-party API access, particularly among smaller regional institutions and credit unions that serve many MCA applicants. API data can also be spoofed at the source if a fraudster controls the account being connected. The data arrives clean and structured, which ironically makes manipulation harder to detect because there are no visual cues to flag inconsistencies.

Visual verification, where the applicant navigates their actual banking portal on screen, provides something APIs cannot: context. An underwriter watching a recorded session can see the browser URL, the banking interface layout, the way transaction details render in real time. Synthetic bank portals, a growing fraud vector in 2026, are much harder to maintain convincingly when the applicant must scroll through months of transaction history in a live browser session rather than upload a static PDF or connect a spoofed API endpoint.

The strongest credit policies use both. API data provides the quantitative foundation. Visual verification provides the qualitative confirmation. When a new SVP of Credit is designing governance from scratch, building this dual-layer approach into the workflow from the start is far easier than adding the visual layer after the API infrastructure is already embedded in every approval pathway.

What This Means for Funders Who Did Not Start from Scratch

Most MCA funders reading this did not have the luxury of a blank-slate credit build. Their verification workflows evolved incrementally, shaped by whatever tools were available when they launched and whatever patches they applied as problems surfaced. The Fox Ridge hire is a useful prompt to ask: if you were rebuilding your credit policy today, what would you change?

Three areas deserve immediate attention. First, documentation standards. Can your team produce a verifiable record of how every funded deal's bank activity was confirmed? If the answer involves relying on an underwriter's memory of a phone call, that is a gap. Second, fraud coverage. Are your verification methods equipped to catch the fraud techniques that are actually prevalent right now, including synthetic portals, manipulated PDFs, and stacking across multiple funders? Static document review alone is increasingly insufficient. Third, scalability. As deal volume grows, does your verification process scale without proportionally increasing headcount? Scheduling live verification calls is inherently linear. Each call requires a dedicated time slot for both the applicant and the underwriter. Asynchronous workflows break that constraint by decoupling recording from review.

The Federal Reserve's small business lending surveys consistently show that alternative funders face growing pressure to demonstrate institutional-grade risk management practices as they seek capital market funding. Portfolio buyers and credit facility providers want to see formalized verification procedures, not ad hoc processes that depend on individual underwriter judgment. Building or rebuilding those procedures now, before the next capital raise or portfolio review, is substantially cheaper than doing it under pressure.

Frequently Asked Questions

What are MCA underwriting best practices for new funders?

MCA underwriting best practices start with verified bank data as the foundation for every credit decision. New funders should codify their verification workflows before scaling deal volume, embed audit trail requirements into every step, and use both API-based data aggregation and visual bank verification to create redundant fraud detection layers. Documenting how each deal's banking activity was confirmed is essential for compliance, investor due diligence, and dispute resolution.

Why would an MCA funder build credit policy from scratch instead of copying competitors?

Building from scratch allows a funder to design verification workflows that match current fraud patterns and regulatory expectations rather than inheriting legacy processes that were designed for a different era. Competitors' workflows often contain workarounds and gaps that are invisible from the outside. A clean-sheet build also ensures that audit trail infrastructure, documentation standards, and scalability considerations are architected into the foundation rather than patched on later.

How does asynchronous bank verification help new credit teams scale?

Asynchronous bank verification decouples the recording step from the review step. Applicants record their banking portal session at their convenience using a browser-based tool. Underwriters review recordings on their own schedule. This eliminates the scheduling bottleneck that limits live verification calls, allowing a small credit team to handle significantly more verifications per day without adding headcount. Every recording is automatically timestamped and stored, creating the audit trail documentation that new credit teams need from day one.

What unique fraud risks do hybrid equipment finance and MCA funders face?

Hybrid funders risk applying equipment finance verification standards, which focus primarily on asset valuation and business revenue confirmation, to MCA deals that require granular transaction-level bank verification. MCA-specific fraud vectors like synthetic bank portals, manipulated transaction histories, and stacking across multiple funders require specialized detection methods. A unified credit policy must maintain the higher verification standard required by MCA even when the same team also processes simpler equipment finance applications.

Conclusion

Fox Ridge Capital's decision to build credit policy from scratch is a reminder that verification infrastructure belongs at the center of any MCA underwriting framework, not at the periphery. Whether you are standing up a new credit operation or pressure-testing an existing one, the same principles apply: verify before you score, document before you fund, and build workflows that scale without multiplying headcount. Exact Balance gives credit teams the asynchronous bank verification layer that makes all three possible. Applicants record their banking portal in minutes, underwriters review on demand, and every session is stored as a timestamped audit artifact. Visit exactbalance.ca to see how async verification fits into your credit workflow from day one.