Skip to main content
Treasury settlement is merchant settlement where the receiving account is your own: a business taking payment for its own goods, a platform accumulating its revenue share, or a company converting collected fiat into a stablecoin position. The calls are the same; what changes is who owns the destination and what governs it afterwards.

​
Choose a connected wallet or a Vault

A treasury destination is an ordinary settlement destination on an account you control. A Vault is a smart account governed by an on-chain policy that states which tokens may move, to whom, and how much inside a fixed window. Spending that breaks the policy fails at the contract rather than at a backend check, so the control holds even if an API credential is compromised.

​
Provision a Vault before you settle into it

1

Create it

POST /v2/accounts/{accountId}/vault returns as soon as an address is allocated: a predictedSafeAddress with status: provisioning, while deployment and policy installation finish in the background. If the response is lost, repeat the request with the same Idempotency-Key to get back the same Vault and address.
2

Authorise the initial policy

With ownershipMode: "stableyard", an account email that is already verified authorises it automatically; otherwise, complete the returned authorisation action. A business account cannot take the email path, because a code sent to a shared inbox is not company authorisation, so use ownershipMode: "external" with its own signer.
3

Wait for it to go active

Continue onboarding meanwhile, but wait for status: active or the vault.policy_active event.
Do not offer deposits or use the Vault for payments, settlement or yield until it reports status: active.

Next: Acquirer and PSP settlement

Convert local-currency processing balances into stablecoin.