Embed
Overview
Supercharge your platform payments with Straddle Embed
What is Straddle Embed?
Straddle Embed is a purpose-built solution that enables software providers, marketplaces, and payment facilitators to easily integrate Straddle’s open banking payment capabilities into their own offerings. With Straddle Embed, platforms can extend and monetize payments infrastructure with all the benefits of a “PayFac” program, but without the regulatory headaches or liabilities.Straddle Embed allows platforms to focus on building compelling software while Straddle manages payments, compliance, and risk. Embed integrators carry no payment liability or flow of funds exposure.
Key Platform Benefits
Key Platform Benefits
Leverage Straddle Embed to enhance your platform:
- Massive Scale: Extend all core Straddle features through a single, platform-level integration
- Competitive Edge: Differentiate with next-generation payment capabilities for platform stickiness.
- Instant Merchant Onboarding: Get new merchants transacting in minutes, document-free.
- Monetization: Benefit from a flexible revenue sharing model (up to 60% of monthly earnings).
Versatile Use Cases
Versatile Use Cases
Straddle Embed powers diverse platforms with specific payment needs:
- SaaS Platforms: Embed subscription billing, automated invoicing, and varied payment options for your clients.
- Marketplaces: Integrate secure buyer-to-seller payments, escrow, and automated commission payouts.
- Payment Facilitators: Offer open-banking, reduced transaction costs, and faster settlements.
- Enterprise Solutions: Embed customizable payment flows, ERP integrations, and high-volume transaction handling.
Unified Architecture
Unified Architecture
Designed from the ground up for embedded scenarios:
- Multi-Tenant Design: Natively manage and isolate multiple merchants under your single platform account.
- Flexible Authentication & Context: Supports platform-level and account-specific API interactions, with API responses automatically including relevant account/platform context.
- Webhooks: Receive real-time event notifications at both platform and individual merchant levels.
Platform models
Straddle Embed supports two distinct platform models, each with unique customer management approaches:SaaS Platform
Vertical-specific software with embedded payment capabilities
Marketplace Platform
Platforms facilitating transactions between users and sellers/vendors
SaaS Platform Model
Overview
A SaaS platform provides specialized software to businesses in specific industries. In this model, end users do not register with the SaaS platform itself—they are customers of the businesses that use the SaaS. When payments occur, they happen through the business’s interface, with the SaaS platform processing transactions in the background.Key Characteristics
- Customer Relationship: End users are customers of the SaaS client (account), not the SaaS platform itself
- Customer Management: 1:1 relationship between customers and accounts
- Branding: The business’s brand is front-and-center, platform operates behind the scenes
- User Experience: End users interact with payment forms embedded in the business’s workflow
- Payment Flow: Directed through the business’s branded interface
Typical User Journey
- Interaction with a Business: The end user is a customer of a business that uses your SaaS platform
- Payment Initiation: When payment is needed, the user sees a payment form within the business’s interface
- Behind-the-Scenes Processing: Your platform handles the payment flow and compliance checks
- Account-Specific Experience: The customer’s profile exists within the context of that specific business
Use Cases
- Practice Management Software: Medical offices, law firms, or accounting practices
- Loan Servicing Platforms: Lenders offering payment options to borrowers
- Subscription Billing Solutions: SaaS companies managing recurring payments
- Invoice Management Systems: Businesses sending invoices to their customers
Marketplace Platform Model
Overview
In a marketplace model, end users (customers) register directly with your platform and can interact with multiple sellers (accounts) within your ecosystem. The marketplace facilitates transactions between parties and maintains centralized customer profiles.Key Characteristics
- Customer Relationship: End users register directly with the marketplace platform
- Customer Management: One:Many relationship - platform-level customers can transact with multiple accounts
- Branding: The marketplace brand is prominent throughout the experience
- User Experience: Centralized profile, payment methods, and transaction history
- Payment Flow: All transactions occur through the marketplace’s ecosystem
Typical User Journey
- Platform Registration: The end user creates a profile directly with your marketplace
- Identity & Payment Setup: The user provides identity information and connects payment methods
- Browsing & Transactions: The user interacts with multiple sellers, merchants, or vendors from your application
- Centralized Experience: All transaction history, communication, and dispute resolution happen through the marketplace
Use Cases
- E-commerce Marketplaces: Platforms where multiple merchants sell to consumers
- Wallets: Tap-to-pay or stored value wallets where customers can interact with any seller or vendor connected to the wallet
- Service Marketplaces: Platforms connecting service providers with clients
- Rental Marketplaces: Property or equipment rental platforms
- Gig Economy Platforms: Connecting freelancers with those needing services
Key Differences Between Models
| Aspect | SaaS Platform | Marketplace Platform |
|---|---|---|
| User Registration | No direct profile with platform; user is a customer of the SaaS client | Customer creates a direct profile on the marketplace |
| Customer Model | 1:1 (customers tied to specific accounts) | Many:Many (platform customers can transact with multiple accounts) |
| User Profile | Maintained by the business, not the platform | Centralized on the marketplace (profile, payment methods, history) |
| Payment Flow | Embedded in business workflow | Centralized within marketplace ecosystem |
| Branding | Business brand is front-and-center | Marketplace brand is front-and-center |
| Compliance/KYC | Managed through the business, typically invisible to user | Per marketplace requirements, managed directly |
| Revenue Model | Subscription + transaction fees paid by businesses | Marketplace fees + transaction fees |
| Ongoing Engagement | Users typically interact only when making payments | Users return to marketplace for future needs |
Generate Revenue with Straddle Embed
For SaaS Platforms
- Embedded Payments: Add payment capabilities without building payment infrastructure
- Increased Revenue: Generate additional revenue through transaction fees
- Enhanced Value: Provide a more complete solution to your business clients
- Reduced Complexity: No need to handle payment compliance or risk management
- White-labeled Experience: Keep your platform in the background while highlighting your clients’ brands
For Marketplace Platforms
- Centralized Customer Management: Create and manage customers at the platform level
- Seamless Customer Experience: Allow customers to transact with multiple sellers without re-registering
- Reduced Friction: Simplify payment flows for repeat transactions
- Unified Profile: Maintain payment methods, preferences, and history in one place
- Enhanced Control: Manage compliance, disputes, and refunds centrally
Choosing the Right Model
Consider these factors when deciding between SaaS and Marketplace models:- Business Relationship: Who owns the relationship with the end user?
- Transaction Flow: Do you need a central payment hub or embedded payment capabilities?
- User Experience: Should users maintain one profile or separate profiles with each business?
- Branding Strategy: Should your platform brand be prominent or in the background?
You're a SaaS if...
You're a SaaS if...
- End users are primarily customers of your clients
- Your platform provides industry-specific software
- Payments should be embedded into business workflows
- Client branding should be prominent during payment flows
You're a Marketplace if...
You're a Marketplace if...
- End users register directly with your platform
- You facilitate transactions between buyers and sellers
- You need centralized control of payments
- Platform branding should be consistent across transactions
Getting Started with Straddle Embed
Ready to enhance your platform with Straddle Embed? Here’s how to get started:- Register for Straddle Sandbox access
- Schedule a consultation with our platform specialists
- Define your platform model and customer management approach
- Work with our team to design your ideal payment experience
- Begin integration with our comprehensive API documentation