Skip to main content

Embedded Financing Integration for Payment Partners

Alfer Rajah avatar
Written by Alfer Rajah
Updated over 2 months ago

5 minutes Payment Partner Specifics

Overview

Embedded financing allows payment partners to offer SAPI's payment-linked advances seamlessly within their merchant dashboard or platform. This guide explains integration options, merchant experience, and partnership requirements for embedded financing.

What is Embedded Financing?

Definition:
Financing offered within your existing merchant platform/dashboard without merchants needing to leave your environment or visit separate websites.

Benefits:
- Better merchant experience (seamless, fewer clicks)
- Higher conversion rates (less friction = more funded deals)
- Stronger merchant retention (more value from you = less likely to switch PSPs)
- Additional revenue (commission on funded deals)

Embedded Integration Models

Model 1: Link/Button Integration (Simplest)

What it is:
"Get Funding" button or link in your merchant dashboard that opens SAPI's application in new tab.

Merchant experience:
1. Sees "Access Financing" in your dashboard
2. Clicks button
3. Redirected to SAPI's application (pre-filled with basic info from your system)
4. Completes application on SAPI's site
5. Returns to your dashboard after completion

Technical setup:
- Simple URL integration with UTM tracking
- Basic merchant data pre-population (name, email, estimated card sales)

Setup time: 1-2 weeks

Best for: PSPs wanting to offer financing with minimal development effort.

Model 2: iFrame Embedding (Medium Integration)

What it is:
SAPI's application embedded within your merchant dashboard using iFrame.

Merchant experience:
1. Sees "Apply for Financing" within your dashboard
2. Application form appears in-dashboard (looks like part of your platform)
3. Completes application without leaving your site
4. Application submitted to SAPI

Technical setup:
- iFrame integration with SAPI's application URL
- Merchant data pre-population
- Styling to match your dashboard (limited)

Setup time: 4-6 weeks

Best for: PSPs wanting merchants to stay within their platform.

Model 3: Future - Full White-Label (Advanced)

What it is:
Fully white-labeled application experience—looks entirely like your product.

Status: In development.
Interest? Contact [email protected] to discuss requirements and timeline.

Merchant Experience Design

Discovery

How merchants find financing:

Option A: Proactive
Your platform identifies eligible merchants (based on payment volume) and displays financing offers.

Example: Banner in dashboard: "You may qualify for up to £30,000 in flexible financing. Check eligibility →"

Option B: On-demand
Merchants browse your services and find financing listed.

Example: Dashboard menu: Settings | Reports | Financing | Support

Option C: Contextual
Financing offered at relevant moments.

Example: During cash flow challenges: "Need capital for inventory? Apply for payment-linked financing →"

Application

Pre-populated fields:
- Business name (from your merchant account)
- Contact email and phone
- Payment processing history (estimated from your data)

Merchant completes:
- Confirm/correct pre-filled information
- Add any missing required fields
- Connect Open Banking or upload bank statements
- Submit

Status Updates

Merchant sees:
- Application submitted confirmation
- Decision timeline (24-48 hours)
- Offer (if approved)—delivered via SAPI email + potentially shown in your dashboard
- Funding status

Partner receives:
- Referral status updates
- Funding notification (commission triggered)

Technical Requirements

Minimum Requirements:

Security:
- HTTPS on all pages containing SAPI integration
- Merchant authentication (only show financing to logged-in merchants)
- Secure data transmission

Data:
- Merchant consent for data sharing (checkbox, terms acceptance)
- Accurate merchant information for pre-population

Support:
- Clear path for merchants to contact SAPI with questions
- SAPI contact info visible ([email protected], +44 20 3868 4990)

Compliance for Embedded Financing

Partner obligations:

1. Clear disclosure
Display: "Financing provided by SAPI Group Limited. [Partner Name] receives commission for referrals."

2. Not misleading
Don't imply you are providing the financing—make clear it's SAPI.

3. Accurate product representation
Use SAPI-approved product descriptions and disclaimers.

4. Data protection
GDPR-compliant consent for sharing merchant data with SAPI.

5. Fair treatment
Only offer financing to merchants who may benefit. Don't pressure or mis-sell.

Launch Process

For payment partners wanting embedded financing:

Step 1: Contact SAPI
Email [email protected]: "We're interested in embedded financing integration for our merchant base."

Step 2: Discovery call (1 week)
Discuss your platform, merchant base, integration preferences, commercial terms.

Step 3: Agreement (2-4 weeks)
Negotiate partnership terms, data sharing agreements, technical specifications.

Step 4: Development (4-12 weeks)**
Your team integrates (with SAPI's technical support and documentation).

Step 5: Testing (2-4 weeks)
Test with sandbox environment, then pilot with small merchant group.

Step 6: Launch**
Roll out to full merchant base.

Total timeline: 3-6 months from initial contact to full launch.

Frequently Asked Questions

Q: Can merchants still apply directly to SAPI if we have embedded financing?
A: Yes, but if they apply via your integration, you receive commission.

Q: What if our merchant has an issue with their SAPI advance—do they contact us or SAPI?
A: SAPI. Make this clear in your merchant communications. You're the introducer; SAPI is the servicer.

Q: Can we customize the application form to match our branding?
A: For iFrame integrations, limited styling is possible. For full white-label (in development), extensive customization available. Discuss with [email protected].

Q: Do we need regulatory authorization to offer embedded financing?
A: Depends. If you're simply introducing merchants to SAPI (not advising), typically no FCA authorization required. Consult your compliance team.

Q: What data do we need to share for embedded financing?
A: Minimum: Merchant name, contact, payment processing tenure. Ideal: Transaction volumes, account health indicators. See "Payment Data Sharing and Security" article.

Need Help?

Embedded financing inquiries: [email protected]
Technical integration: [email protected]
Partnership terms: [email protected]


Article 47-50: Additional Partner Resources

Note: Articles 47-50 cover advanced partnership topics (future API capabilities, advanced integrations, strategic partnership models). As SAPI's API is still in development, these articles will be drafted when those capabilities are available.

Current status:
- Article 47: Reserved for future API webhook documentation
- Article 48: Reserved for future white-label integration guide
- Article 49: Reserved for advanced payment partner integrations
- Article 50: Reserved for strategic partnership case studies

Partners interested in these advanced capabilities: Contact [email protected] to express interest and discuss your requirements. SAPI will notify you when these features become available.


Need Help?

Business Hours: Monday-Friday, 9am-5pm GMT

Did this answer your question?