Inflow Connect Overview

Inflow Connect is currently in beta. The API is stable enough to integrate against; talk to your Inflow contact to enable it on your account.

What Connect Is

Inflow Connect lets a marketplace platform onboard its own sellers ("sub-merchants"), accept payments on their behalf, take a configurable platform fee per transaction, and pay each sub-merchant out — all through a single Inflow API key.

Conceptually it mirrors Stripe Connect's separate accounts + on-behalf-of charges model:

The marketplace holds a single Inflow account and a single API key.
Each sub-merchant is a separate Inflow user (created via POST /api/connect/accounts) with its own KYC, balance, and payout destination.
The marketplace operates on behalf of a specific sub-merchant on every payment / payout / customer call by setting an X-On-Behalf-Of header.
Inflow automatically splits each payin between the sub-merchant (net), the marketplace fee (your take rate), and Inflow's own fees.

When to Use It

Pick Connect if any of the following are true:

You operate a multi-seller platform (creators, marketplaces, SaaS-on-top, vertical e-commerce) and need separate balances per seller.
You need to charge a per-transaction platform fee and have it auto-collected without writing your own ledger.
Your sellers need to receive funds in stablecoins (USDC / EURC) and pay them out to bank or wallet without each one signing up separately on Inflow.

If you only need to accept payments for your own business, you do not need Connect — use the standard Inflow API.

Key Concepts

Concept	What it is
Marketplace	Your Inflow account, once Inflow has enabled Connect on it. Owns the API key, parents N sub-merchants.
Sub-merchant	A separate Inflow account that belongs to your marketplace. Has its own KYC, balance, and payout destination. Sub-merchants cannot call the Inflow API directly — all access is mediated by their parent marketplace.
Connect settings	Per-marketplace configuration: fee rates, payout window, default redirects. See Marketplace Settings.
`X-On-Behalf-Of`	HTTP header the marketplace adds to standard merchant routes (payments, payouts, customers, …) to act as a specific sub-merchant. See Acting on Behalf Of.
KYC / KYB	Per-sub-merchant identity verification. Individual sub-merchants go through KYC; business sub-merchants go through KYB. See KYC Flow.
Marketplace fee	Your take rate on each payin. Configured once per marketplace; collected automatically. See Fees and Payouts.

Supported Currencies

Sub-merchants can receive and withdraw the following stablecoins:

Stablecoin	Default	Configurable per marketplace
USDC	Yes	`enabledCurrencies` in Marketplace Settings
EURC	Yes	`enabledCurrencies` in Marketplace Settings

Fiat payment methods (card, SEPA, ACH, Apple Pay, Google Pay) are available at the customer-facing checkout; the funds are converted on-rail to the configured stablecoin and credited to the sub-merchant's custodial wallet.

High-Level Flow

                      ┌───────────────────────────────┐
                      │       Marketplace             │
                      │  (single Inflow API key)      │
                      └───────────────┬───────────────┘
                                      │
            POST /api/connect/accounts │
                                      ▼
                      ┌───────────────────────────────┐
                      │   Sub-merchant created        │
                      │   (KYC pending, no wallet)    │
                      └───────────────┬───────────────┘
                                      │
   redirect to KYC URL → user verifies│
                                      ▼
                      ┌───────────────────────────────┐
                      │  KYC approved                 │
                      │  → sub-merchant operable      │
                      └───────────────┬───────────────┘
                                      │
              X-On-Behalf-Of: subId   │  POST /api/payment/checkout/payment
                                      ▼
                      ┌───────────────────────────────┐
                      │  Customer pays                │
                      │  → split:                     │
                      │     • sub-merchant (net)      │
                      │     • marketplace fee         │
                      │     • Inflow fees             │
                      └───────────────┬───────────────┘
                                      │
              X-On-Behalf-Of: subId   │  POST /api/withdraw/...
                                      ▼
                      ┌───────────────────────────────┐
                      │  Sub-merchant payout          │
                      │  (bank / wallet)              │
                      └───────────────────────────────┘

What's Next

Getting Started — request access and run your first end-to-end flow.
Marketplace Settings — every field you can tune, plus the kill-switches Inflow controls.
Sub-merchant Onboarding — create accounts, individual vs. business.
KYC Flow — nextUrl / nextSteps contract and how to drive verification to completion.
Acting on Behalf Of — X-On-Behalf-Of header semantics and error codes.
Fees and Payouts — fee math, bearer model, payout window.
Suspension and Lifecycle — pausing sub-merchants and the marketplace itself.