The internal SOP for the funding team. How any specialist submits an application on behalf of a client, across every rail, end to end, with no silent failures. One universal flow, then the specifics for each rail. Built so any specialist can run any application from received to funded.
Submit on behalf4 rails, one flowConfirm it landed, alwaysInternal use only
One job, no silent failures. When an application comes in, a specialist owns it from received to funded. The biggest risk in submission is an application that looks sent but never lands, so every rail in this guide ends the same way: confirm it arrived before you move on. Exact portal steps not yet confirmed are marked [confirm].
Start here01
The universal flow
Every application follows the same shape, whatever the rail. Learn this once and the rails are just variations on it. This is also what we tell the client to expect, so keep it consistent.
Receive and reviewAs soon as it landsThe application comes into our system from the client's finance link. Review it straight away for completeness and the client's profile.
Match to the networkThe right rail and lendersStart connecting with the lender network on the client's behalf, matching their profile to the rails and lenders most likely to serve them.
Discuss the best optionsBack to the clientCome back to the client with the best viable options for their situation, so they choose from real choices, not a single take-it-or-leave-it.
Final submissionOnly with their yesOnce they are happy, do the final submission to the chosen lender or rail and keep them updated on the outcome.
Funds and finalise24 to 48 hours of settlingOn approval, the client receives funds within 24 to 48 hours of the loan settling. Hand back to their point of contact to finalise payment and start onboarding.
Say it to the client like this. "We review it straight away, connect with a broad network of lenders on your behalf, come back to you with the best options, then do the final submission and keep you updated. Once approved, funds land within 24 to 48 hours."
The rails02
Eaze, the US application
The primary consumer rail and the merchant's day-one funding. One application link opens a panel of prime and near-prime consumer lenders.
Lenders
20+ prime / near-prime
Type
Consumer
Profile that approves
$40k+ income, 650+, low DTI
The link. Submissions run through the Eaze US application link: loans.eazeconsulting.com, the link the whole team uses. [Confirm the login.]
The panel. One application is worked across the 20+ prime and near-prime consumer lenders.
The profile. Income ideally $40,000+ a year, credit 650+, low debt-to-income. Guidance, not a hard cut-off, the lender decides.
Submit and confirm. Submit through the platform, then confirm it registered (section 06). [Confirm the exact submit and status steps in the Eaze Platform.]
The rails03
Queen Street
The widest coverage. Through Queen Street the team can place a client across 800 or more credit cards and 20 or more lenders, covering the full credit spectrum.
Cards
800+
Lenders
20+
Spectrum
Super-prime to deep-prime
Submitted via our application. The specialist submits through our Queen Street application. [Confirm the submission screen, login and any API steps.]
Full spectrum. Super-prime, prime, near-prime, subprime, deep-prime, so even tough files have options.
Cards and lenders. Both business and consumer card products plus lenders, another route to getting a client funded.
Confirm it landed. Queen Street is the rail most prone to a silent failure, so confirming receipt (section 06) is non-negotiable here.
The rails04
Grow Funders
The business-loan rail. When a client needs capital for the business itself rather than consumer financing for their customers, this is the route.
Business loans. Working capital for the business, not point-of-sale consumer financing.
When to use it. The client wants funds for their own operations, inventory, hiring, or to finance their AIFS purchase as a business loan.
The portal. Submit through the Grow Funders portal: growfunders.com/Eazecap. [Confirm the login, exact submission steps and document requirements.]
Confirm it landed. As with every rail, confirm receipt before moving on.
Portal confirmed. The Grow Funders portal link is set. The remaining items to document are the login, exact submission steps, requirements and SLA. [Provide those and this becomes a full per-rail SOP.]
The rails05
MagWitch
Instant-decision financing the merchant uses day to day. Submission is simple once the merchant is onboarded; the onboarding itself is the heavier part and has its own guide.
Instant decision. Once the merchant is onboarded, decisions come back at the point of sale.
Onboarding first. The merchant must be onboarded (documents submitted, dashboard provisioned) before they can submit. That process is in the MagWitch Onboarding guide.
Submission. The merchant submits through their MagWitch dashboard. [Confirm the portal submission steps with David.]
If it stalls or declines, move to the Lumino contingency (section 07).
Run it06
Confirming it landed
The most important habit in this guide. An application that looks sent but never registered is the worst kind of failure, because nobody knows until the client asks why nothing happened. Never assume, always confirm.
Check the status after every submissionEvery rail, every timeAfter submitting, confirm the application shows as received in that rail's system before you consider it done.
Log itIn our trackerRecord the submission, the rail, and the timestamp, so the application is visible to the team and not living only in one person's head.
Set a follow-upNo application goes quietIf you do not have an outcome within the expected window, chase it. A submission with no status update is a submission to chase, not to wait on.
The rule. A submission is not done when you click submit. It is done when you have confirmed it landed and logged it. Until then it is in progress.
Run it07
Declines & the swap
A decline from one lender is never a dead end, that is the whole point of working a network. Here is how to handle it, and when to move to a contingency.
One lender, not the market. A decline is one credit box. Work the rest of the network for the client's profile before telling them anything.
Try the spectrum. If prime declines, near-prime and the wider Queen Street panel may serve. Use the full spectrum.
The contingency. If MagWitch cannot serve, move to Lumino, the client is live on Affirm inside 24 hours, framed as an upgrade. See the contingency plan.
Eaze covers the gap. Throughout any swap, Eaze keeps the client funded so there is never a moment with no way to fund a deal.
"One of the lenders couldn't make that one work, which is normal, that's exactly why we work a broad network. The team's already looking at the best options and I'll come back to you as soon as we have a path." Never present a decline as the end.
Run it08
Scenarios
What comes up in submission, and what to do.
A submission shows no status after the expected window
Treat it as a possible silent failure. Re-check the rail's system, confirm it actually registered, and if it did not, resubmit. Chase a status, never sit and wait. Escalate to Harvey if the rail itself is unresponsive.
The application is incomplete or the profile is thin
Do not submit a weak file blind. Note what is missing, get it from the client through their point of contact, then match it to the rail most likely to serve that profile. A clean submission beats a fast one.
The client is declined across the first rail
Work the spectrum and the wider network before telling them. Use Queen Street for breadth. If it is a MagWitch decline, move to Lumino. Eaze covers funding throughout. Only update the client once you have a path or genuinely exhausted the options.
A client needs business funding, not consumer
Route to Grow Funders for a business loan rather than the consumer rails. Confirm the requirements and submit through that portal. [Grow Funders steps to be confirmed.]
Two specialists are unsure who owns an application
One application, one owner. Whoever received it owns it to funded unless explicitly handed over and confirmed. Log ownership in the tracker so it is never ambiguous.
Run it09
Definition of done & SLA
A submission is done when all of this is true.
Reviewed for completeness and profile on receipt.
Matched and submitted to the right rail with the client's agreement.
Confirmed landed in the rail's system and logged in the tracker.
Outcome tracked to approval or a clear next step, never left silent.
Funds confirmed within 24 to 48 hours of settling, and handed back to the point of contact.
SLA. Review on receipt, options back to the client within [confirm], final submission same day on the client's yes, outcome chased if no status within the rail's window. [Confirm the exact internal SLAs with Harvey and David.]
Run it10
Who to contact
The funding team.
H
Harvey
Lead Broker
Leads the specialists, owns the network and the contingency swaps. Escalate stuck or unresponsive rails here.
D
David
Lender relationships
Owns every lender relationship, including MagWitch. Escalate relationship-level issues.
EJA
Edson, Johan, April
Funding Specialists
Submit on behalf across the rails, each owning their applications to funded.
Received to funded. No silent failures.
One universal flow, four rails, and a confirm-it-landed habit on every single submission.