Skip to main content
Every account belongs to one customer. Choose it using two dimensions: who manages it and whether it is a wallet or bank account.

Choose an account

issued means Swipelux creates and manages the resource. external records an endpoint owned by the customer. A third-party endpoint belongs under a recipient and destination, not under the customer account list.

Create the account

Use POST /v3/customers/{customerId}/accounts. Send these headers with one of the request bodies below:
Use only currencies, networks, methods, and account types returned for the current customer and capability. Do not copy availability from another customer or environment.

Wait for the account to be usable

Store data.id, data.status, and data.openTaskIds from the create response. Read the latest account with GET /v3/customers/{customerId}/accounts/{accountId} before you quote a transfer or show bank details. Use the account only when its current status permits the next operation. If task IDs are open, complete them through Capabilities and tasks. An issued bank account can return details: null while provisioning. Present bank details only after a current read returns the complete set. If details.referenceRequired is true, show the exact details.reference with the bank coordinates.

Keep account roles explicit

For a payout, the issued wallet is the source in in.accountId. A customer-owned bank account is the destinationId. For an issued bank account, settlement.accountId is the issued wallet that receives matched deposits. Next, use a ready account in Receive funds, Send funds, or Issue a bank account.