BlueSnap Embedded Payments is a flexible multi-party solution that lets you onboard merchants, accept payments on behalf of your users, collect platform fees, split funds, and manage payouts all through a single integration.
You control the customer's software and payment experience while BlueSnap handles payment processing, merchant verification, compliance, and payouts behind the scenes.
Benefits
BlueSnap Embedded Payments helps platforms launch and scale payment capabilities without building merchant onboarding, payment processing, compliance, and payout infrastructure from scratch.
It provides the following benefits:
- Single integration for merchant onboarding, payments, platform fees, split payments, and payouts
- Global payment acceptance with local acquiring and multiple payment methods
- Built-in merchant verification and compliance workflows
- Flexible fund splitting for platform fees, commissions, and revenue share
- Payment and payout reporting for reconciliation
- Faster time to market for embedded payments programs
Use Cases
Use BlueSnap Embedded Payments if your platform helps merchants sell products or services to their own customers. Common examples include:
- SaaS platforms that let their users accept payments
- Multi-merchant ecommerce platforms
- Vertical software platforms with embedded checkout
- Platforms that collect commissions, service fees, or revenue share
Implementation Lifecycle
Getting started with Embedded Payments follows four steps.
- Choose your implementation model: Decide how your platform wants to handle merchant applications, verification follow-up, and post-approval merchant management.
- Implement onboarding: Set up the merchant onboarding experience and connect your platform to BlueSnap payment APIs.
- Onboard merchants: Create merchant applications, collect required information, and track verification status.
- Process transactions: After the merchant is approved, begin to accept payments and collect platform fees while letting BlueSnap manage payment processing and payouts behind the scenes.
Embedded Payments or Marketplace?
Use Embedded Payments when your platform provides software that helps businesses accept payments from their own customers. Embedded Payments usually fits when:
- The buyer thinks they are buying from the merchant, not your platform.
- The merchant is the Merchant of Record.
- The merchant name appears on the receipt or card statement.
- Buyers contact the merchant for product, service, refund, or order support.
- Your platform powers the payment experience, but the merchant owns the customer relationship.
For example, Embedded Payments would be best for a scheduling platform where each business accepts payments from its own customers for appointments, classes, or services.
Use Marketplace when buyers come to your platform to buy from multiple sellers or service providers, and your platform owns the buyer-facing transaction experience. Marketplace usually fits when:
- The buyer thinks they are buying from your platform.
- Your platform is the Merchant of Record.
- Your platform name appears on the receipt or card statement.
- Buyers contact your platform for order, service, refund, or dispute support.
- Your platform pays sellers or service providers after the transaction.
For example, Marketplace would be best for a ride-sharing platform where riders book through the platform, pay the platform, and contact the platform if there is a problem.
Next Steps
If you're interested in implementing Embedded Payments, continue with:
- Implementation Models to decide which approach is best for you.
- Platform Onboarding to prepare for implementation with BlueSnap.
- Merchant Onboarding to create your application and onboard merchants.
- Merchant Verification & Setup to handle additional document requests and testing.
- Payments & Payout to handle payments for your merchants.