CRM and POS vendors have a privilege most lenders pay for: they are already open all day. The funding CTA can live on a deal record, a ticket, or an end-of-day cash view. That privilege disappears if you ship a clunky “API integration” that never leaves the partner roadmap. Ship a button. Preserve a unique partner link. Let the marketplace work.
Loanable does not expose a public REST API that injects offers into a terminal or a Salesforce-shaped object. Embedded solutions are branded or co-branded apply flows with partner attribution. Loanable is not a lender. 150+ lenders. 50/50 of Loanable profit, Monday ACH, no minimum. If your POS roadmap said “one-tap underwriting,” change the roadmap before you demo it at a trade show.
Object-level placement
CRM: a closed-won implementation that needs equipment, or a customer who stalled on budget. POS: a cash drawer that cannot cover a supplier. Do not put “get funded” on every SKU lookup. Object-level placement keeps the story business-purpose and keeps employees from applying as consumers by accident.
- Role-gate the CTA to owners or managers
- Pass the ref even from desktop shells and iPads
- Do not print funding ads on customer-facing receipts
- Deep-link type= when the object is clearly equipment versus cash gap
Offline and flaky networks
POS networks are messy. If the webview fails, give a copyable URL with the code already on it. A QR code to a clean homepage without ref is how you lose attribution at a restaurant. Test in the field, not only on office Wi-Fi. Working capital as soon as 24 hours does not help if the owner never finished the form because the iPad dropped the parameter.
Sales orgs on CRM
If your CRM customers are agencies, they may want their own codes. That is a channel design question. Loanable pays the partner on the ref that hit the application. Facilities up to $50M will not appear as a column in the CRM unless you build that yourself from human process — there is no funding API to sync it. Start with starts and fundings in the Loanable dashboard.
Permissions on the floor
A line cook with POS access should not open a business funding application for the restaurant. A junior AE should not apply for a customer’s company from a CRM record. Role gates are part of embedded solutions even though the “API” is a URL. If you skip them, you will get unauthorized applications and angry owners.
Put the rule in the same admin guide as refunds and voids. Mention that Loanable is not a lender, that 150+ lenders may match, that working capital can fund as soon as 24 hours, and that the unique partner link must remain. 50/50 Monday ACH is not a reason to loosen permissions. $50M facilities are not a reason to put the button on the guest-facing display.
Put funding on the object you already own. Add Loanable embedded solutions to CRM or POS with a unique partner link, not with a terminal lending API that does not exist here.