DEV Community: Ram Kl

Loan API Orchestration vs. API Aggregation: Why the Architecture Decision Determines What Your Lending Stack Can Actually Do

Ram Kl — Wed, 26 Aug 2026 07:41:34 +0000

Your engineering team can build an API aggregation layer in four to six weeks. It will pull data from your credit bureau, your KYC vendor, your document service, and your lender partners, normalize the responses, and return a single unified object to the frontend. It will work.

And for a loan origination workflow, it will be wrong.

The distinction between loan API orchestration and API aggregation is not an academic architecture debate. It is a question of which pattern matches the structural reality of a lending workflow, and building the wrong one means creating an integration stack that cannot enforce compliance timing, cannot track workflow state, and cannot execute the conditional logic that turns a multi-lender submission into a measurable approval rate lift.

The Difference Between Loan API Orchestration and API Aggregation - In Lending Terms

Both patterns involve multiple API calls. The similarity ends there.

API aggregation operates on a fan-out/fan-in model: one request triggers parallel calls to multiple independent services, responses are collected and merged, and a unified result returns to the caller. The calls are stateless — none depends on the result of another. The pattern is fast because the underlying services execute simultaneously without shared context.

Loan API orchestration manages a sequence of dependent API calls where the output of each step is the input to the next. It maintains state throughout the workflow, applies conditional logic at each branch point, handles failures with defined retry or rollback behaviors, and tracks progress from initiation to completion.

In a consumer lending workflow, the dependency structure is explicit at every step:

Identity verification must succeed before the credit bureau pull initiates — pulling a file on an unverified identity is both a data quality failure and a regulatory exposure
The bureau response determines which underwriting rules apply and which lender tiers are eligible for this applicant
Underwriting evaluation must complete before any lender submission can proceed
Lender responses must be received and normalized before TILA disclosures are generated — presenting a disclosure before the offer exists violates the Regulation Z timing requirement
Borrower e-signature must be captured before the funding instruction is released to the merchant

None of these steps can execute in parallel without violating either the logical dependency between them or the regulatory sequence governing their order. That structural reality is the case for loan API orchestration in lending: this is not a data collection problem. It is a coordination problem.

Where API Aggregation Actually Fits in a Lending Stack

This is not an argument that aggregation has no place in lending infrastructure — it has a defined and valid role in specific contexts where the services called are genuinely independent, and the result is a display output rather than a workflow execution.

Aggregation is the correct pattern for:

Borrower account dashboards — pulling current balance, payment history, application status, and available offers from separate services simultaneously; none of those calls depends on any other
Merchant portal views — assembling pipeline metrics, origination volume, approval rates, and payment confirmation status from independent data sources for a unified reporting interface
Portfolio analytics — pulling delinquency data, funded volume, and average ticket size across lender partners simultaneously for a consolidated performance view
Offer display surfaces — presenting normalized lender offers to the borrower after the orchestration layer has already generated and validated them

These are legitimate aggregation use cases because the underlying service calls are independent. If the analytics call to one lender's reporting API fails, the dashboard renders with partial data and the failure is logged without disrupting anything downstream. Graceful degradation is a feature, not a risk.

The loan origination workflow shares none of those properties. A failure at identity verification does not produce a partial result — it stops the workflow. The absence of a bureau response means there is no application to route. These are not display problems with graceful fallback. They are binary success/failure gates that determine whether the next step is permitted to execute at all.

Where the Architecture Choice Shows Up in Outcomes

Approval rate mechanics. The most visible consequence of applying aggregation logic to an orchestration use case is approval rate loss at the multi-lender decisioning step. In a properly orchestrated lending workflow, a single application is submitted simultaneously to all eligible lender partners. The orchestration engine manages concurrent lender calls, normalizes divergent response schemas, and returns a ranked offer set to the borrower. The US digital lending market is projected to grow from $339.22 billion in 2026 to $592.87 billion by 2031 (Mordor Intelligence, United States Digital Lending Market, 2026). Lenders able to cover the full credit spectrum — prime through near-prime — capture a larger share of that origination volume. Those running architectures that cannot support simultaneous multi-lender submission cap their approval rates at a single credit box.

Compliance execution timing. Regulation Z's TILA requirements create hard timing constraints that a stateless aggregation layer cannot enforce. The disclosure must follow offer generation; it cannot precede it. Adverse action notices must be generated on decline and delivered within defined regulatory timelines. State licensing verification must confirm jurisdiction-specific eligibility before an offer is presented to the borrower.

In an orchestration architecture, these compliance events fire automatically when the workflow reaches the correct state — there is no manual trigger. In an aggregation architecture — which has no concept of "state in the workflow" — compliance execution becomes a manually managed exception queue. That queue is where regulatory exposure accumulates.

Decisioning speed without sacrificing sequence. A well-designed orchestration layer identifies which steps within the lending workflow can be parallelized without violating dependencies, and executes them concurrently. Identity verification and passive fraud screening, for example, can often run simultaneously — both can initiate without waiting for the other. The bureau pull triggers as soon as identity is confirmed. This is not aggregation. It is orchestration with strategic parallelism at dependency-safe steps.

The J.D. Power 2025 US Automotive Finance Digital Experience Study identified speed as one of the top criteria driving customer satisfaction in digital finance interactions. The lenders reaching fastest decisioning are the ones whose orchestration layers compress latency at eligible steps without sacrificing the dependency sequence that produces accurate and compliant offers.

Error handling and state recovery. When a bureau API is slow or temporarily unavailable mid-workflow, an orchestration layer applies defined retry logic, timeout thresholds, and circuit-breaker behavior before determining whether to hold the application, fail it gracefully, or route it through a fallback path. An aggregation layer has no concept of mid-workflow state to recover. When the loan origination call is stateless, a service failure mid-execution produces a failed response with no recovery path that preserves the progress made up to that point.

What a Correctly Structured Orchestration Architecture Looks Like at Scale

FinMkt's API Orchestration Engine was built around the sequential dependency structure of consumer lending workflows. It handles the complete origination sequence as a single managed workflow: identity and fraud verification, credit bureau pull, underwriting evaluation, simultaneous submission to all eligible lender partners, offer normalization and ranking, TILA disclosure delivery, e-signature, and funding release to the merchant.

Applications complete in under four minutes on average. Merchants are funded within 48 hours of origination. Across more than 150,000 consumers and $1 billion+ in annual funding volume, that consistency is an orchestration outcome — not a throughput ceiling.

The simultaneous multi-lender submission warrants a specific note: all eligible lenders receive the application at the same moment. Offers return concurrently. The orchestration engine normalizes divergent response schemas and presents a unified, ranked offer set. This is not sequential routing with a cascade fallback — it is simultaneous evaluation across the full lender network, with the approval rate ceiling set by the combined credit coverage of all partners rather than any single credit box.

Platform-level compliance management is embedded directly in the orchestration layer. TILA disclosures fire when the workflow reaches the post-offer-generation state — automatically, not on a manual trigger. Adverse action notices generate on decline without a human-initiated queue. State licensing checks execute as a pre-condition to offer presentation.

FinMkt is the technology layer — not the lender. The institution retains control over its underwriting configuration, financing program parameters, and borrower relationship through the embedded lending platform. The orchestration engine manages the coordination between every external service the lending program depends on, handling the sequencing, error recovery, and compliance execution that determines whether a single application event produces a funded loan or a dropped workflow.

The Compounding Cost of Getting This Wrong

Institutions that build aggregation patterns into orchestration use cases do not discover the problem at launch. They discover it during their first high-volume period, when workflow exceptions start accumulating faster than operations teams can clear them. They discover it in compliance reviews, when manual adverse action backlogs produce adverse examination findings. They discover it in approval rate reports, when multi-lender submission mechanics break down under concurrent load because the architecture was never designed to coordinate dependent service calls at scale.

Rebuilding an integration architecture is not a sprint-level fix. It is a platform rebuild — with the origination volume it was supposed to handle still going to competitors who got the architecture right the first time. In a US digital lending market projected to approach $592.87 billion by 2031 (Mordor Intelligence, United States Digital Lending Market, 2026), every quarter spent on that rebuild is origination capacity not deployed. The institutions that understand from the design stage that loan origination is a coordination problem — not a data consolidation problem — avoid that cost entirely.

Answering 12 Embedded Lending Questions Merchants Ask Before Rolling Out Financing

Ram Kl — Fri, 07 Aug 2026 09:35:56 +0000

Your sales rep just closed a $22,000 kitchen remodel. The homeowner loved the design. Then came the pause — "how do we actually pay for this?" and the deal sat there, stalled, while your rep fumbled through a financing pitch they'd never fully understood themselves.

That pause costs you money. Contractors who introduce financing before the price conversation stalls see close rates jump 20–30% compared to those who don't (DrillDown Solution, 2025). But you can't sell what you don't understand, and most merchants adopting embedded lending for the first time are working off half-answers from a sales deck instead of straight answers to the questions that actually matter.

We get these embedded lending questions constantly — from home improvement contractors, dental practices, and healthcare providers rolling out financing for the first time. Here are the 12 that come up most, answered the way we'd answer them across a conference table.

How Embedded Lending Actually Works

What is embedded lending, exactly?

Embedded lending means your customer can apply for and get approved for financing right inside your sales process, not through a separate bank visit, not through a third-party website they have to leave your business to use. The application lives inside your checkout flow, your in-home sales tablet, or your patient intake process.

The technology stack behind it typically includes a front-end application widget, an API layer connecting to one or more lenders, a bank partner that actually funds the loan, and a payment rail that gets you paid. None of that complexity is visible to your customer. They fill out one form and get an answer in seconds.

How is embedded lending different from a customer just applying for a personal loan on their own?

Speed and context. A customer applying for a personal loan on their own goes to a bank, waits days, and often walks in with only a vague idea of what they need financed. Embedded lending puts the offer in front of them at the exact moment they're deciding whether to move forward with your service — mid-estimate, mid-treatment plan, mid-checkout.

That timing matters more than most merchants expect. The median U.S. homeowner now carries a mortgage rate well below current market rates, which means fewer people want to tap home equity for renovations (Freddie Mac, 2025). Point-of-sale financing fills that gap by offering a way to pay without touching the mortgage at all.

Is "embedded lending" the same thing as "embedded finance"?

Not quite. Embedded finance is the broader category — it covers lending, but also insurance, payments, and other financial products built into a non-financial business. Embedded lending is specifically the credit piece: the loan or installment plan a customer gets access to at the point of sale. When people talk about offering "financing" to their customers, they're almost always talking about embedded lending.

Who Actually Qualifies

What credit score does my customer need to get approved?

This is the question that determines whether financing helps you close deals or just becomes another dead end in your sales process. It depends entirely on how many lenders are evaluating the application and what credit tiers they cover.

A setup built around a single lender typically approves 40–60% of applicants, because that one lender is underwriting to one credit box (FormPiper, 2026). A true multi-lender waterfall works differently: your customer completes one universal application, and it flows through a customized sequence of lenders and financing plans until it lands on a fit. Overall approval coverage for a real multi-lender setup runs 70–90%+ (FormPiper, 2026). That 30-point gap is the difference between a homeowner who signs today and one who walks out to "think about it," which in practice means they don't come back.

What happens if my customer doesn't get approved by the first lender in the sequence?

Nothing your customer has to deal with. The offers presented are prequalified through a soft credit pull, so checking multiple lenders in the sequence doesn't ding their credit score the way shopping around for a personal loan on their own would. Your customer sees their prequalified offers, compares them side by side, and picks the one that fits — prime, near-prime, or subprime — all from that one application. They never have to know how many lenders the sequence checked to get there.

Can I offer financing to customers with poor or thin credit history?

Yes, but only if your platform actually reaches that segment. This is where a lot of merchants get burned by vendors who market themselves as full-spectrum but quietly only serve prime borrowers. Roughly 14% of U.S. consumers now fall into the subprime credit tier by recent estimates (Fortune/subprime lending data, 2025), and personal loan originations overall are climbing — unsecured personal loan originations rose 35% year-over-year, reaching 6.9 million in Q2 2025 (TransUnion, 2025). If your financing program doesn't cover near-prime and subprime, you're turning away a growing share of the people asking you for financing in the first place.

What It Actually Costs You

What does embedded lending cost me as a merchant?

Most consumer financing platforms charge merchants a dealer fee — a percentage of the transaction taken by the platform or lender in exchange for funding you upfront and taking on the credit risk. The exact percentage varies by lender, credit tier, and platform, and it's one of the first things you should get in writing before signing anything, rather than estimating from a sales call.

The math still tends to work in your favor. Homeowners using payment plans spend an average of 44% more on their projects than those paying out of pocket (HFS Financial, 2025), so even after the fee, the larger ticket size usually more than covers it.

Am I on the hook if my customer doesn't pay back the loan?

No, and this is one of the most misunderstood parts of embedded lending. The lender takes on the credit risk, not you. Once the loan is funded and you're paid for the work, the repayment relationship is between the lender and your customer. You're not a collections agency, and you shouldn't sign with anyone who tries to make you one.

Running It Day to Day

How fast do I actually get paid?

This varies by platform, but funding within 24–48 hours of project completion or service delivery is standard for a well-built embedded lending setup. If a platform can't tell you a specific funding window, that's a red flag — ask directly and get it in writing.

What does the customer actually see when they apply?

A single form, ideally completed in under two minutes, with a decision back in seconds. If the process your platform offers takes longer than that or requires the customer to leave your sales conversation to complete it elsewhere, it's going to lose deals regardless of what the approval rate looks like on paper. The application experience is a top driver of consumer financing satisfaction and repeat engagement, according to J.D. Power's 2024 U.S. Consumer Lending Satisfaction Study and that satisfaction shows up directly in whether a customer finishes the application at all.

Compliance and Reliability

Am I responsible for compliance — disclosures, licensing, and so on?

Not on your own, but you need to know who is. Consumer financing is a regulated product. Truth in Lending Act disclosures, adverse action notices, and state lending licenses all apply, and a legitimate platform manages that infrastructure rather than leaving you to figure it out. Ask directly who holds the licenses and who's liable if a disclosure requirement is missed. Note that for some states a special financing license may be required.

What happens if one of my lenders changes their underwriting or exits the program?

This is the scenario single-lender merchants dread, and multi-lender merchants barely notice. If your program runs on one bank and that bank tightens its credit box in response to a downturn, your entire financing pipeline can dry up overnight — right when your customers need it most. A multi-lender platform absorbs that shock, because no single lender's policy shift determines whether your customers can get approved. Businesses using more than one lender have reported meaningfully higher overall approval rates for exactly this reason (McKinsey & Company, 2022).

Where FinFi Fits Into This

We built FinFi around the questions above because they're the ones that determine whether a financing program actually works for a merchant, not just for a lender's balance sheet.

One application. Multiple lenders are evaluated in a real-time waterfall. Prime, near-prime, and subprime coverage, so a lower credit score doesn't automatically mean a lost sale. The whole thing runs white-label under your brand, whether your customer applies online or in person, so there's no unfamiliar logo interrupting the sales conversation you already built trust in.
Want to see the FinFi waterfall in action? Check out FinFi or request a demo to see how it fits into your sales process.

What to Do Before You Sign With Anyone

Ask for your actual expected approval rate, not an industry average, based on a realistic sample of your customer base and credit mix.
Get the dealer fee structure in writing before you roll financing out to your sales team, not after.
Confirm funding timing in writing. "Fast" isn't a number; ask for the specific window.
Ask how many active lending partners are actually in the waterfall, not just listed on a slide.
Find out what happens to active customer applications if a lending partner exits the program. If the answer is vague, that's your answer.

The Bottom Line

The merchants who get the most out of embedded lending aren't the ones who adopted it first. They're the ones who asked the right questions before they did, and didn't find out the hard way what a single-lender program couldn't cover. Ask these twelve before your next sales conversation depends on the answer.
FinFi is powered by FinMkt - reach out anytime if you want to talk through what a program like this could look like for your business.

FinMkt's Infrastructure for HVAC Contractor Financing

Ram Kl — Mon, 27 Jul 2026 08:17:04 +0000

FinMkt is not a lender. We are the technology layer that powers enterprise-grade point-of-sale financing programs — including the infrastructure behind a multi-lender financing platform purpose-built for high-volume contractor operations.

When a homeowner submits a financing application through a FinMkt-powered program, that application goes simultaneously to FinMkt's full lender network. Every eligible offer is returned and presented to the customer in a single comparison view — nothing routed sequentially, nothing withheld pending a prior decline. The homeowner sees what they actually qualify for, all at once.

For HVAC contractors, the operational impact is direct:

Full credit spectrum coverage — prime, near-prime, and subprime applicants surface eligible offers through the same application flow
Approval decisions in minutes, available before your technician leaves the driveway
48-hour merchant funding — your receivables are not waiting on lender processing timelines after the install is complete
White-label capability — the financing experience runs under your brand, not a third-party financial institution's name
$1B+ in annual funding volume processed across 150,000+ consumers funded to date
FinMkt integrates into existing contractor workflows through an API-first architecture. The financing application lives inside your sales process — not as a separate tab the homeowner navigates to on their own.

Practical Takeaways: Evaluating HVAC Financing for Contractors

Before signing a dealer agreement renewal or accepting the default program your current software partner offers, get concrete answers to these questions:

What is your funded approval rate? Not the application approval rate — the rate at which submitted applications result in a disbursed loan and a funded merchant. These numbers can diverge significantly; a program that approves 70% of applications but funds 45% due to documentation drop-off is a 45% program.
What happens to a FICO 620 applicant with documented income? Ask for a specific answer, not "they're reviewed on a case-by-case basis." Either your program has lenders who underwrite near-prime applicants or it does not.
How quickly does your account fund after installation? 48 hours is the operational benchmark. Programs paying in 7-10 business days create a working capital gap that compounds under volume.
Is the application submitted simultaneously to all lenders? Programs that route sequentially — submit to lender 1, wait for decline, submit to lender 2 — add decision time and structurally underperform simultaneous-submission models at the same network size.
Is the experience white-labeled? Every financing interaction that displays a third-party lender's brand is replacing your brand relationship with the homeowner at the exact moment they are making a purchase decision.
Approval rate is not a fixed variable in HVAC contractor financing. It is a program design output, and it is fully solvable with the right infrastructure.

The contractors gaining ground in HVAC right now are not running more leads than their competitors. They are converting more of the calls they already have. The financing program is where that conversion either holds or breaks, and the difference between a 55% approval rate and an 80%+ approval rate is not a rounding error. At real volume, it is the revenue trajectory of your operation.

The Questions You Must Ask Before Adopting Embedded Finance

Ram Kl — Fri, 26 Jun 2026 10:02:46 +0000

A homeowner approves a $22,000 kitchen remodel. Your sales rep pulls out a tablet to process financing. One lender. One shot. Declined. The deal dies on the spot — not because the customer couldn't afford monthly payments, but because your financing platform couldn't serve their credit profile.

That scenario plays out every day for contractors who jumped into embedded finance without asking the right questions first.

How Does Embedded Finance Work and Why Does the Architecture Matter?

Before you evaluate any platform, you need to understand what you're actually buying into.

Embedded finance is the integration of financial services — in this case, consumer lending directly into your sales workflow. Instead of sending a customer to their bank to apply for a home equity loan and hoping they come back, the application happens in the moment: on your tablet, your website, or your customer portal. The customer applies, gets approved, and you get paid. The entire process can take under two minutes.

That's the baseline. But how it works under the hood varies enormously between platforms, and those differences determine whether your financing program drives revenue or quietly bleeds deals.

The most important architectural distinction: does the platform run through a single lender or a multi-lender waterfall?

Single-lender platforms partner with one financial institution. That lender has its own underwriting criteria, typically focused on prime credit profiles. If your customer's FICO doesn't fit, the application is declined, and you have nothing to fall back on.

Multi-lender platforms route one application through a hierarchy of lenders in sequence — prime, near-prime, subprime, and sometimes lease-to-own — until the best available offer is found. The customer sees a clean experience. You see significantly more approvals. According to data from FinMkt's platform, businesses using a multi-lender approach have reported up to 30% more customer approvals compared to single-lender setups — approvals that would otherwise have been lost.

With that foundation in place, here are the questions that matter before you sign anything.

1. What Credit Spectrum Does This Platform Actually Cover?

This is the first question, and most merchants ask it too late, after they've already seen the approval rate.

Ask any platform vendor: what percentage of your approvals come from prime borrowers? What happens to a customer with a 620 FICO? What about 580?

Single-lender platforms often don't publish this. They'll talk about "competitive rates" and "fast approvals" without disclosing that their coverage collapses below a certain credit threshold. In home improvement, healthcare, and dental verticals where project sizes run from $5,000 to $50,000 and where customers often carry significant existing debt, a prime-only platform will leave a substantial portion of your pipeline unserved.

Single-lender platforms typically focus on prime credit applicants — those with excellent to good credit and the most favorable variables. If the application doesn't meet those criteria, the deal is over.

The right question isn't just "do you cover subprime?" It's: "What is my estimated approval rate across a realistic distribution of my customer base?" Any platform that can't answer that with real data is asking you to make a high-stakes operational decision on a guess.

2. Is This a True Waterfall or Just Multiple Logins?

Not every "multi-lender" platform is actually a waterfall.

Some vendors market multi-lender capability but deliver it as a manual process: your team submits to Lender A, waits for a decision, then submits to Lender B, then Lender C. That's not a waterfall — that's three separate applications, three separate experiences, and three opportunities for the customer to get frustrated and walk away.

A genuine waterfall processes one application against multiple lenders simultaneously or in rapid sequence, with automated routing, and surfaces the best available offer to the customer in a single session. The customer never sees the back-end. They apply once and get an answer.

Be wary of platforms that claim to be "multi-lender" but still force your team to manage five different logins and re-enter data into multiple portals. This creates friction that leads reps to default to their one "favorite" lender — even if it isn't the best fit for the homeowner.

Ask directly: Does a single application trigger evaluation across all your lending partners? How many lenders are in the waterfall? What is the automated routing logic? If the answers are vague, the technology may not be what's being marketed.

3. How Does the Platform Handle Approval Rate Volatility?

Here's a risk that almost no one talks about during the sales process: approval rates change over time, and often without warning.

Individual lenders tighten or loosen underwriting criteria in response to their own portfolio risk, macroeconomic conditions, and seasonal factors. If your platform routes all applications through one lender — or even relies heavily on one — you're exposed to their risk appetite, not just your customers' credit quality.

The impact is real. A contractor doing $2 million in annual revenue with a 65% approval rate generates roughly $1.3 million in financed revenue. If that approval rate drops to 50% for a single quarter, the lost revenue is approximately $75,000, during a period that may already be cash-flow sensitive.

If you're relying on a single lender for your customer financing, seasonal volatility isn't just an inconvenience. It's an existential threat to your cash flow.

Ask any platform: what happens to my approval rates when your primary lender tightens credit? Can you show me historical approval rate data across economic cycles? A **multi-lender waterfall **naturally hedges this risk because if one lender tightens, the waterfall routes to the next. But you need to confirm the platform has enough lenders in the stack to make that hedge meaningful.

4. What Does Integration Actually Look Like?

"Easy integration" is one of the most overused claims in fintech. Ask for specifics.

For a home improvement contractor, integration means the financing offer needs to appear in the places your sales conversations happen: your website, your CRM, your in-home proposal tool, your customer-facing tablet. For a dental practice, it means the financing experience needs to fit into your patient workflow at the front desk or in the treatment room — not after a separate phone call to a lender.

The key technical questions to ask:

Does the platform offer an API, a hosted application link, or both?
What does the in-person mobile experience look like? Is it optimized for a tablet or only for a desktop?
How long does a typical integration take? What does the go-live process look like?
Do you offer a white-label option so the financing experience reflects my brand, not the platform's brand?

That last point matters more than it might seem. Homeowners respond better to emotional framing and trust cues. Contractors who use embedded financing platforms with clear, branded interfaces build more trust. A white-label platform means the financing feels like your offering — not an afterthought from a third-party lender your customer has never heard of.

5. What Are the Real Costs and How Are They Structured?

Financing platforms make money in a few different ways, and not all of them are aligned with your interests.

The primary cost to understand is the dealer fee — a percentage of the funded loan amount that you pay to the platform or lender in exchange for offering the product. Dealer fees vary significantly depending on the promotional terms of the loan (0% interest, deferred payment, etc.) and the credit profile of the borrower. Standard dealer fees on promotional programs in home improvement financing typically range from roughly 11% to 22% of the funded amount, though this varies by program and lender.

The question isn't just "what's your dealer fee?" It's: how does the fee structure change across your different products and promotional programs? Are there additional platform or subscription fees? And critically: are promotional loan programs available, and at what cost?

Promotional terms — like 12-months same-as-cash — are powerful sales tools, but they carry higher dealer fees. Understanding that tradeoff before you deploy the program saves painful surprises later.

6. What Happens After the Customer Signs?

The moment a customer approves a financing offer is not the end of the story. It's the beginning of a relationship that will either run smoothly or generate friction for months.

## Ask about the full post-approval workflow:

How quickly does funding reach you after project completion?
What is the chargeback and dispute process? Who handles it?
What happens if a customer cancels or changes scope mid-project?
Is there a merchant dashboard where you can track application status, funded deals, and approval rates in real time?

Reporting matters more than most contractors expect going in. Customers can apply, get approved, and finalize payment plans in minutes — but the backend data on approval rates, application volume, and funding speed is what tells you whether your financing program is actually performing or just running in the background. If you can't see that data clearly, you can't improve the program.

7. Who's Behind the Platform and Who Are the Lending Partners?

A financing platform is only as reliable as the infrastructure behind it.

This matters for two reasons. First, regulatory: the financing you offer your customers is a regulated financial product. The platform you partner with should be operating under appropriate licensing and compliance frameworks in the states where you operate. Ask who holds the lending licenses, who the bank partners are, and how consumer data is handled.

Second, stability: the embedded finance space has seen consolidation and disruption. Platforms that lack robust banking relationships or that rely on a single bank sponsor carry concentration risk. If something changes at the lender level, your program can be disrupted.

Ask specifically: who are your current lending partners? How long have those partnerships been in place? What happens to my active customer accounts if a lending partner exits the program?

How FinFi Answers These Questions

We built FinFi specifically because we saw what happens when merchants adopt the wrong financing infrastructure. A contractor who can't approve a 610 FICO customer loses that job. A dental practice whose patient financing declines 40% of applicants loses treatment acceptance. A healthcare provider whose financing partner tightens credit in Q4 feels it in December revenues.

FinFi is a multi-lender embedded finance platform powered by FinMkt, connecting merchants to a network of lending partners through a single application and a true waterfall. One application. Multiple lenders are evaluated in real time. The best available offer surfaces automatically, without your team having to manage separate processes or portals.

We cover the full credit spectrum: prime, near-prime, and subprime. We offer white-label capability so your brand leads. And we work both online and in-person, built for the realities of how contractors and healthcare providers actually sell.

The platform includes real-time reporting so you can see exactly what's happening with approval rates, funded volume, and where deals are being lost.

Before You Sign Anything: A Practical Checklist

Use this the next time you're evaluating a financing platform:

Credit coverage

What is the minimum credit score the platform can serve?
Does the waterfall cover prime, near-prime, and subprime?
What is the expected approval rate across a realistic mix of my customer base?
Platform architecture
Is this a true single-application waterfall or a manual multi-submission?
How many active lending partners are in the stack?
How does approval rate volatility get managed across lenders?

Integration and experience

How does the platform integrate with my existing sales workflow?
Is there a mobile-optimized in-person experience?
Is white-label branding available?

Costs

What are the dealer fees for standard vs. promotional loan programs?
Are there additional platform, subscription, or per-application fees?
How does the fee structure change as my volume grows?

Post-funding operations

How long does merchant funding take after project completion?
What does the merchant dashboard show, and how often is it updated?
What is the dispute and chargeback process?

Compliance and stability

Who holds the lending licenses?
Who are the bank and lending partners?
How long have those partnerships been active?

Financing programs don't fail because the concept is wrong. They fail because the platform couldn't serve the actual customer who walked through the door. The questions above won't guarantee a perfect fit — but they'll tell you fast whether a platform is built for your business or built for someone else's.