Create a wallet
Creates a custodial wallet under the association resolved from the token. Only walletName and assetCode are accepted — network, wallet type, and custody are fixed platform-side. assetCode funds the wallet and establishes the asset trustline. Balances are attached best-effort on the response.
This creates a real, permanently persisted wallet — including real on-chain funding — even when called with sandbox credentials. Sandbox only simulates off-ramp payout execution; it does not sandbox record creation.
Authorizations
Access token issued by POST /v1/auth/token.
Application secret (the apiKey issued at registration), required on every request.
Body
Asset code for the initial trustline (e.g. USDZ). Discover valid codes via GET /v1/assets.
Whether the wallet belongs to your own business. When false, metadata is required and the wallet starts in status Pending until its KYC review completes.
Third-party FICA details. Required when ownAccount is false; must be omitted when true.
Response
Wallet created.
Stellar public key (G...)
Zeam account number.
Platform network name.
Whether the wallet belongs to the association's own business (false = held on behalf of a third party).
Verification status. Only a Verified wallet may be transacted on; own-account wallets are Verified at creation, third-party wallets start Pending until their KYC review completes.
Pending, Verified, Rejected On-chain balances. Populated best-effort; may be empty if the Horizon lookup failed. Native XLM is excluded.