Choose Your Integration Path
Decision tree
flowchart LR
A([Start]) --> M{Building a marketplace or SaaS platform?}
M -- Yes --> CON[Connect]
M -- No --> B{Need recurring billing?}
B -- No --> C{Need custom checkout?}
B -- Yes --> D{Need custom checkout?}
C -- No --> PL[Payment Links]
C -- Yes --> E{Embed on your site?}
D -- No --> SL[Subscription Links]
D -- Yes --> F{Embed on your site?}
E -- Yes --> SDK1[SDK]
E -- No --> S2S1[Server-to-Server]
F -- Yes --> SDK2[SDK]
F -- No --> S2S2[Server-to-Server]
At a glance
| Payment Links | Subscription Links | SDK | Server-to-Server | Connect | |
|---|---|---|---|---|---|
| Code required | None | None | Frontend + backend | Backend only | Backend + onboarding flow |
| Where customer pays | Inflow hosted page | Inflow hosted page | Your site (iframe) | Your app / redirect | Your marketplace flow |
| Cards (Visa, MC, Amex, Discover) | ✅ | ✅ | ✅ | ✅ | ✅ |
| Apple Pay / Google Pay | ✅ | ✅ | ❌ | ✅ | ✅ |
| Local Bank Transfer | ✅ | ✅ | ❌ | ✅ | ✅ |
| Recurring billing | ❌ | ✅ | Via API | Via API | Via merchant routes on behalf of sellers |
| Multiple sellers / sub-merchants | ❌ | ❌ | ❌ | ❌ | ✅ |
| 3D Secure | Auto | Auto | Auto | Manual + Auto | Depends on payment route |
| Branding / custom UI | Basic | Basic | Full | Full | Full platform experience |
| PCI scope | None | None | None (iframe) | Must handle | Depends on payment route |
| Activation required | No | No | No | Yes (support) | Yes (Connect access) |
Path details
Payment Links — no code, fastest to launch
Create once from the Dashboard or with one API call. Customer opens the link, pays, and is redirected to your successUrl.
- Email, Slack, social, QR code — any channel works.
- Supports all payment methods: cards, Apple Pay, Google Pay, local bank transfer.
- Minimal setup: product name + price + currency.
Start here → Generate a Payment Link or First Payment in 5 Minutes
Connect — marketplaces and SaaS platforms
Use Connect when your product has multiple sellers, creators, vendors, or sub-merchants. Connect gives each seller their own onboarding, KYC/KYB status, balance, and payout destination while your platform can collect a fee.
- Onboard sub-merchants through the Connect API.
- Act on behalf of a seller with the
X-On-Behalf-Ofheader. - Split each payin between the seller, your platform fee, and Inflow fees.
Start here → Connect → Getting Started with Connect
Subscription Links — recurring billing with zero code
Create a subscription offer, share a link. Inflow handles retries, trial periods, entry fees, and waitlists.
- Discord role assignment on active subscription.
- Customize billing interval, trial period, entry fee.
Start here → Subscription Overview
SDK (iframe card form) — embedded checkout on your site
Mount a PCI-compliant card form in your page. The customer never leaves your domain.
- React:
<CardElement />component. - Vanilla JS:
provider.createCardElement().mount(). - 3DS modal opens automatically when required.
- Cards only — Apple Pay, Google Pay, and local bank transfer are not available via SDK.
Start here → SDK Overview & Security → Installation
Server-to-Server — full API control
You control the entire flow. Create payments from your backend, redirect the customer or handle everything in-app.
- Mobile apps, headless frontends, marketplaces.
- Save and reuse customer payment methods (
savePaymentMethod,useCustomerPaymentMethod). - All payment methods available: cards, Apple Pay, Google Pay, local bank transfer.
- Must be enabled for your account — contact [email protected].
Start here → Server-to-Server Payments
Still unsure?
| I want to… | Use |
|---|---|
| Just collect money, no code | Payment Links |
| Sell subscriptions, no code | Subscription Links |
| Embed a card form in my React app | SDK |
| Build a mobile app or custom flow | Server-to-Server |
| Build a marketplace, creator platform, or multi-seller SaaS | Connect |
| Try everything in 5 minutes | First Payment in 5 Minutes |
Updated 7 days ago