Product designers want the funding application to look like it lives inside the SaaS app. Compliance wants it to be obvious someone else is matching lenders. Both are right. A co-branded apply flow is the compromise: your brand is present, Loanable’s marketplace identity is present, and the user is not tricked into thinking your software company just became a bank.
Loanable offers Loanable-branded or co-branded apply experiences with partner attribution via a unique partner link. That is the embedded product. It is not a public REST API that renders offers in your React tree. Loanable is not a lender. 150+ lenders receive matched files. You earn 50/50 of Loanable profit on fundings, Monday ACH, no minimum.
What co-brand should say in the first screen
Who is matching lenders. Who is not the lender. That you are the software they already use. That completing the application is optional. If you hide Loanable entirely, the user will email your support when a lender asks for a statement. If you hide yourselves entirely, you wasted the partnership on a generic redirect they could have Googled.
- Keep the ref code on the URL even when the page is co-branded
- Do not invent an “instant decision” spinner you cannot finish
- Do not imply your SaaS fees include credit approval
- Align screenshot marketing with the real apply screens
Legal and support copy
Your terms should not say you originate business loans unless you actually do. Point users to the apply flow disclosures. Your success team should have a one-pager: marketplace, 150+ lenders, some working capital as soon as 24 hours, larger products including up to $50M on eligible facilities, partner payouts are your company’s economics not the user’s loan.
Design the return path
When they finish or abandon, send them back into the product with a calm message, not a fake funded toast. If you want status, operationalize looking at the partner dashboard rather than scraping pages. Users who think they were approved because your UI said “submitted to lenders” will be angry in public. Submitted is not funded.
Brand QA before you screenshot for the sales deck
Load the real co-branded apply flow on a phone. If the logo is a stale PNG or the disclosure is cut off, do not put that screenshot in a Series B data room. Users will hit the real page. Legal will compare it to the deck. Loanable is still the marketplace. You are still not the lender. The screenshot should say so.
Version the co-brand. When you change your product name, file a ticket to update the apply chrome. Dead brand names on a credit form look like a phishing clone. Attribution via unique partner link still works with an old logo, but trust does not. 50/50 of profit on fundings, Monday ACH, 150+ lenders — none of that survives a user who bounced because the page looked abandoned.
Run a five-user usability pass before GA: can they tell who is matching lenders, can they get back into your product, and does the ref still show in the address bar after the first redirect? Those three answers matter more than padding. Loanable remains a marketplace of 150+ lenders, not your balance sheet. 50/50 of profit posts Monday via ACH when the file funds with your code. Working capital as soon as 24 hours is a lender outcome, not a spinner you add for polish.
Co-brand the trust, not a fake bank. Review Loanable embedded solutions and launch a co-branded unique partner link flow your support team can actually explain.