Stripe Connect in white label

5 October 2026 — your clients can now connect their Stripe account to a tax ID without leaving your product. You start the connection from your server, the person finishes on Stripe, and Factuarea sends the browser back to a host you registered. The step-by-step is in Connect Stripe in white label.

• New operations.
  • POST /v1/companies/{company}/connected-accounts/authorizations starts the connection of a tax ID and returns the Stripe link to open. It takes a required return_url and a required Idempotency-Key, with scope stripe_autoinvoicing:write.
  • GET /v1/accounts/{account}/connected-accounts/return-domains, POST on the same path and DELETE …/return-domains/{return_domain} manage the hosts your account allows as the destination of the return_url.
• New codes. connect_return_url_not_allowed (422), connect_return_domain_already_exists (409), connect_return_domain_limit_reached (422) and connect_return_domain_not_found (404).
• Live only. The three operations that write need a fact_live_ key, also for the test accounts your account provisions. A fact_test_ key is rejected before anything is written.
• The return_url is checked twice. It must be https and its host must match one of your return domains exactly when you start, and it is checked again against your current list when the person comes back. If you removed the domain in between, the person lands on the Factuarea app instead of your site.
• What comes back in the redirect. status, provider and authorization_id always; company_id, connected_account_id and account on success; error and error_subcode on error.
• Nothing existing changes. The operations of the connected-accounts family keep their shape, and there is no MCP tool for the new ones because the flow needs a browser redirect.