Create a new account.

Account status and lifecycle

The status field reflects where the account is in its lifecycle. Possible values are:

• PROVISIONING: the account is being set up and is not yet operational.
• ACTIVE: the account is operational.
• SUSPENDED: operations are temporarily disabled (e.g. compliance, fraud, legal hold or review).
• CLOSED: terminal state — the account has been closed.
• REJECTED: terminal state — onboarding was deliberately denied (KYC/KYB/compliance).

Depending on the rail, a new account may be returned as ACTIVE right away, or start in PROVISIONING and move to ACTIVE once setup finishes. The status in this endpoint's response is the account's initial state.

Every time the status changes afterwards, a webhook is sent as an HTTP POST to the status_callback_url provided in the request body. The body of that webhook is the account object, using the same schema as the Get Account Details response. No webhook is sent for the initial state, nor when an update leaves the status unchanged.

Testing in sandbox

Account creation is currently synchronous: the account's status is returned directly in this endpoint's response. In the sandbox, create the account with label set to SIMULATE_STATUS_<STATUS> (e.g. SIMULATE_STATUS_SUSPENDED) to have it created directly in that status, or to SIMULATE_PROVISIONING_FLOW to simulate the PROVISIONING → ACTIVE transition and its webhook.