Payments
Start Merchant Onboarding
Create (or resume) a merchant’s Stripe Connect account and return an embedded onboarding session
POST
Ensures the organization has a Stripe connected account — creating one on the platform if it doesn’t exist yet — and returns everything you need to run Stripe’s embedded onboarding: a Connect Account Session
client_secret and the platform publishable_key. The merchant submits their own banking and identity details directly to Stripe. The platform never receives or stores merchant API keys.
The call is safe to repeat: account creation is idempotent per organization, and each call mints a fresh, short-lived session secret. Use it both to start onboarding and to resume it (e.g. the merchant closed the tab before finishing).
This endpoint prepares onboarding; it does not by itself make a merchant charge-ready. Poll
GET /v1/organizations/{organization_id}/payments/status after the merchant completes Stripe’s flow to confirm can_accept_payments is true.What you need
You do not need a Stripe account or any Stripe key of your own — the connected account lives on Telzino’s platform.
Path Parameters
string
required
UUID of the organization (merchant) to onboard. Must belong to your account.Example:
123e4567-e89b-12d3-a456-426614174000Response Fields
Feature Administration gating
When Feature Administration is enabled and Card Payments (Stripe) is locked for the organization — directly or inherited from its reseller or partner — this endpoint returns403 forbidden and no onboarding session is created.
Only the entry point is gated. A merchant that already completed onboarding keeps its connected account and continues to settle, payment status stays readable, and in-flight charges always complete.