Sub-Platforms
Business accounts of a platform: Connect Business, PayLink Business, Shogun Business.
A Sub-Platform is a business that runs on your platform with its own dashboard, team, API key,
checkout and webhooks. It replaces the former merchant ("Business") account: there are no
separate business accounts, business API keys (gr_live_biz_*) or managed business accounts any
more. The business sees Connect Business, PayLink Business or Shogun Business, by Open
Connect (brands).
Base path: /api/connect/sub-platforms (https://api.openconnect.cc/connect/sub-platforms).
The account
A Sub-Platform is a connected platform account under your fintech or platform:
| Field | Values |
|---|---|
connected_kind | sub_platform (sub_fintech under a network partner or financial platform) |
relation | customer (an independent client) or subsidiary (an entity of your group) |
sub_profile_type | standard (full dashboard) or custom (white label: no Open Connect dashboard, everything goes through your app) |
balance_mode | managed (money goes through you) or standalone (own balance, you take a fee) |
A Sub-Platform has Connect Treasury and Connect Commerce for itself, plus the Connect products you enable for it. It does not get Connect Ramp as a product (rails, partners); it can create ramp links and read its ramp operations for its own payments.
Its API key
A business uses the key of its Sub-Platform account (oc_live_*). It reaches product routes
once the Sub-Platform's KYB is approved. The fintech reveals or rotates it with
POST /api/connect/sub-platforms/{id}/api-keys/reveal and /rotate; the Sub-Platform rotates it
itself with POST /api/openconnect/ocplatform/api-keys/rotate, or from the business portal
(/api/openconnect/ocplatform/portal/api-keys).
Same routes, your own key
A Sub-Platform has no routes of its own: it calls the same product routes as its fintech, with
its own key. The key decides the scope (its payments module); a path that is not open to a
Sub-Platform key answers 404. See Same routes, your own key for the list.
| Area | Path | Key |
|---|---|---|
| Accounts (create, list, read, update, provision, migrate, keys, transfer, customer link) | /api/connect/sub-platforms, /api/connect/sub-platforms/{id}/* | Fintech |
| Hosted onboarding | /api/connect/sub-platforms/onboarding/{accounts,account-links,verify} | Fintech |
| Payment requests | /api/connect/treasury/payment-requests/core | Sub-Platform |
| Ramp links, operations, embed token | /api/connect/ramp/core/{links,operations,embed-token} | Sub-Platform |
| Ramp settings | /api/connect/ramp/settings (GET, PUT) | Sub-Platform |
| Portal payment methods | /api/connect/commerce/payment-methods | Sub-Platform |
| Webhooks (its own subscriptions) | /api/webhooks | Sub-Platform |
| Profile and key rotation | /api/openconnect/ocplatform/me, /api/openconnect/ocplatform/api-keys/rotate | Sub-Platform |
| Member portal (OC ID session) | /api/openconnect/ocplatform/portal/* | Member JWT |
/api/connect/sub-platforms/merchant/* and /api/connect/sub-platforms/ops/* no longer exist.
Platform without a fintech → Open Connect Foundation
A platform that signs up without a fintech (self-service or created by an admin) is attached to the Open Connect Foundation, the default fintech of record:
- it becomes a Sub-Platform of the Foundation:
managed,standard,relation: customer, with its payments module created at signup; - the Foundation is its fintech of record: it holds the funds and carries the ramp, rails and provider settings and the compliance of the money layer;
- its KYB stays at platform level (
platform_standard), not the full fintech KYB.
Nested Sub-Platforms. An attached platform manages its own Sub-Platforms with its key
(POST /api/connect/sub-platforms; their parent is the platform). Money and customers belong to
the fintech of record, the first fintech up the parent chain (here the Foundation). Maximum depth:
fintech → platform → Sub-Platform; a third level answers 400. Each account manages only its own
Sub-Platforms (a Sub-Platform no longer acts on behalf of its parent).
Upgrade to fintech. An attached platform can become a fintech (KYB fintech_full, then
POST /api/openconnect/ocplatform/upgrade, see Upgrade to fintech). It leaves the Foundation and becomes a
primary account. Its Sub-Platforms stay Sub-Platforms (they do not become Sub-Fintechs); the payments
modules already created stay with the Foundation (their balances are to be transferred).