Route one application to many lenders.
Run your own multi-lender program on your own infrastructure. Take one home-improvement application and one soft-pull consent, and fan it out to the lenders you choose, in parallel or as a waterfall. The borrower compares, picks, and the chosen lender becomes the creditor. Your panel, your brand, your data. OneApp Finance is the engine underneath, not a network you plug into.
One intake, fanned out, one pick
The channel routes one application out to the lenders you choose. OneApp Finance provides the rails. It never brokers the loan and never runs a marketplace. The borrower shops on a single soft pull, and the lender who can serve them wins.
- Intake once. The borrower fills out one application. Identity and authorization happen on the borrower's own device, not the salesperson's.
- One soft pull. Run eligibility and a single soft credit pull under one consent scope. A soft pull means no ding to the borrower's score for shopping.
- Light first look. An optional first-look eligibility filter applies your own rules before the application is routed; it is a pre-screen, not a credit decision.
- Fan out to many lenders. The one application is sent to the lenders you chose. Each runs its own decision and prices its own offer.
- Aggregate offers. Approvals, prices, and declines come back and collect in one place. Every declining lender's adverse-action obligation is tracked.
- Borrower compares and picks. The borrower sees the offers side by side and chooses. The chosen lender becomes the creditor of record on that loan.
Parallel or waterfall, on one soft pull
Different lender agreements call for different routing, so OneApp Finance does both, configured per program, on a single soft pull with no repeated hard inquiries either way. A creditworthy applicant one lender can't serve still gets an offer instead of a dead end.
Parallel
Send the application to every lender on the panel at the same time. Offers come back together and the borrower picks the best one. The fastest path to an offer, and the most choice for the borrower.
Waterfall
Offer the application down your panel in the order you set, one lender at a time, until one approves. Honors first-look and tiered lender agreements, so your preferred lenders see it first.
Your network, not someone else's
Routing your applications into someone else's lending network is the fast path, but it's their brand, their lender panel, their data, and their economics. Run your own program on OneApp Finance and the lender relationships, the data, and the upside stay with you.
- Your brand, end to end. Every borrower screen, email, and offer wears your brand, never a network's.
- Your lender panel and relationships. You choose the lenders and own the deals you bring them. They aren't shared with a network's other channels.
- Your data, in your cloud. A single-tenant instance you run, not a seat in a shared marketplace.
- Your routing rules and economics. You set the panel, the order, the criteria, and the terms. No network sits in the middle of your margin.
- Operator-neutral. Nothing ships pre-wired to a particular lender, so you're never routing into someone else's book by default.
What stays yours
- Your brand on every screen
- Your lender panel and relationships
- Your data, single-tenant in your cloud
- Your routing rules and order
- Your economics, with no middle layer
One soft-pull consent, fanned out the right way
Sending one application to many lenders is the easy part. Doing it so it holds up in an exam is the part most platforms skip. OneApp Finance builds the routing on a consent and notice model designed for the fan-out from the start.
- One soft-pull consent scope: a single soft credit pull, authorized once, covering the lenders you route to. The borrower consents to shop, not to many separate hard inquiries.
- Who gets what data, and when. Data sharing is governed per lender and per stage, not handed out wholesale the moment the form is submitted.
- The creditor is named, per application. The instant a lender's offer is chosen, that lender becomes the creditor of record on that loan, recorded in the role ledger.
- Declines are handled, not dropped. On a multi-lender decline, adverse-action notices are tracked per the consent and notice model so the borrower is told the right way.
- Non-selected lenders, cleaned up. Retention and deletion for lenders that were not chosen is part of the model, not an afterthought.
What you get
- One soft-pull consent scope
- Per-lender, per-stage data sharing
- Creditor named on the chosen offer
- Adverse-action tracked on every decline
- Retention and deletion for non-selected lenders
From one OneApp Finance lender to another, or any other system
The panel is yours: your lender relationships, your order, your rules. The fan-out goes only to the lenders you select, and the deals stay between you and them. The channel routes; OneApp Finance just provides the rails.
From one OneApp Finance lender to another
If a receiving lender also runs OneApp Finance, the two Cores speak the same contract natively. Routing out is the same API as taking applications in, just reversed.
Any other system
Route to a lender on a different platform. The receiving end integrates over the public REST API and signed webhooks, the same contract every partner uses.
Your lender panel
You choose which lenders are on the panel for each program. The fan-out goes to the lenders you select, in the order your policy sets.
The contract an integrator builds against
Routing runs on the same public REST API and signed webhooks the OneApp Finance head and ops console use. There is no private backdoor. A channel partner submits a complete application with one idempotent call, keyed so a retry never creates a duplicate. The example below is the inbound submit; outbound routing uses the same contract, reversed, to fan one application out to many lenders.
// one idempotent submit: a retry never duplicates
"partner_external_ref": "acme-2026-04812",
"look": "first",
"applicant": {
"phone": "+1XXXXXXXXXX",
"dob_partial": "MM-DD"
},
"project": {
"amount_cents": 1850000,
"state": "TX"
},
"consent": {
"soft_pull": true,
"consent_evidence_id": "ev_8f3..."
}
// 201 → status "decisioned", offers[] returned
// money + legal moves carry dedicated scopes;
// there is no consent:true shortcut anywhereQuestions operators ask
Do you route in parallel or as a waterfall?
Does shopping multiple lenders hurt the borrower's credit?
Who becomes the lender on the loan?
Can I route to lenders who do not run OneApp Finance?
Is OneApp Finance the lender or the broker?
What happens when more than one lender declines?
What about data for lenders who were not chosen?
Where to go next
Three ways to connect
Run the full LOS, embed the pieces you want, or route to many lenders. See how the same Core flexes across all three.
Explore →One lender, your brand
If you are the lender taking applications directly, see the single-lender mode of the same platform.
Explore →The compliance floor
The 16 invariants and the evidence model that hold no matter how the application is routed.
Explore →See routing on your lender panel
Bring the lenders you work with and we will walk one application through the fan-out, offer by offer.