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[Embedded Checkout or SDK]
    E -- No --> S2S1[Server-to-Server]

    F -- Yes --> SDK2[Embedded Checkout or SDK]
    F -- No --> S2S2[Server-to-Server]

---

At a glance

---

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-Of header.
• 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 template in the Dashboard (Product catalog → Subscription templates) and share its 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

---

Embedded Checkout — the full checkout inside your page

The complete Checkout V2 page (email, billing country, order summary, tax, every payment method) in an iframe on your site. Your backend creates a session with uiMode: "embedded", your frontend mounts it with the SDK.

• One-time payments and subscriptions.
• Cards, Apple Pay, Google Pay, and local bank transfer for one-time payments.
• React: <EmbeddedCheckout />. Vanilla JS: provider.initEmbeddedCheckout().mount().
• Requires a verified domain.

Start here → Embedded Checkout

---

SDK (iframe payment form) — card and wallets inside your own form

Mount a PCI-compliant card form in your page. The customer never leaves your domain.

• Two-step flow: your backend creates the payment, your frontend mounts the card form.
• React: <CardElement /> component.
• Vanilla JS: provider.createCardElement().mount().
• 3DS modal opens automatically when required.
• Free trials and save-card supported via Payment Setups.
• Supports card, Apple Pay and Google Pay. Choose the methods offered in Settings → Checkout; see SDK Checkout Methods. Local bank transfer is not available via SDK.

Start here → SDK Overview & Security → React or Vanilla JS

---

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).
• Card payments via the API. For Apple Pay, Google Pay, or local bank transfer, use hosted checkout (payment links).
• Must be enabled for your account — contact [email protected].

Start here → Server-to-Server Payments

---

Still unsure?