Skip to main content
connect is the capability that lets your account create and manage connected accounts. Upgrade your platform account to a registered business in the dashboard to use Connect in sandbox. Complete the business compliance requirements before Connect can be enabled for production use.
Upgrading to a registered business converts your account from an individual to a company. This is immediate and cannot be reversed.Requirements resolve by country and entity type, so every capability you already hold is re-evaluated as a company and its company fields become due. Capabilities already active stay active.

Enable Connect

Upgrade your platform account to a registered business in the dashboard. This makes Connect available in sandbox; you do not need to finish live compliance to build and test there. To use Connect in production, complete the business requirements and wait for review and enablement. You provide your business registration, ownership and control, what you sell, and a bank account in the business name. The exact fields depend on your country. See Requirements.

Check the status

GET /v1/accounts/me
enabled_capabilities lists only what is active in the environment whose key you used. Check it with a sandbox key before creating test accounts, and with a live key after compliance and review before creating production accounts. While connect is absent in that environment, you cannot create accounts there. See Capabilities.

What connect gates

Requires connect to be active:
  • Creating an account
  • Issuing an account link
  • Writing an account’s requirements
  • Transferring to an account
Does not require it:
  • Reading accounts, their balances, and their capabilities
  • Charges collected by your existing accounts
  • An account link already issued, so an account mid-onboarding can finish
  • Transferring from an account back to you
connect governs creating and onboarding accounts. It does not restrict funds held in accounts you have already created.

What you decide per account

connect active only gets you to POST /v1/accounts. Three choices on that call are worth deciding deliberately:
  • Which capabilities the account needs. Naming a capability is what applies the persona behind it, and decides what the person behind the account has to give. You can add capabilities later, and withdraw one that has not gone live yet. See Capabilities.
  • Whether the person behind the account can log in, dashboard: none by default, or light. You can raise it later, but not lower it. See Give an account a dashboard.
  • Who collects the Bachs processing fee on that account’s charges, responsibilities.fees.collector: bachs by default, or platform if you absorb it. This has no update path. It is set at creation and fixed for the account’s lifetime, because changing it later would retroactively disagree with ledger history that already settled under the old value. See Processing fees.