Virtual Accounts

Create a virtual account

Creates a US_BANK virtual account for a VERIFIED, product-eligible user. US_BANK is the only supported type today; choose fiat (a USD-balance account funded by inbound wire/ACH) or crypto (an on-chain stablecoin deposit address) via mode, and select the bank/provider rail with bank (or its provider alias).

⚠️ bank is REQUIRED for US_BANK VAs — including crypto. Omitting it returns 400 "bank is required for US_BANK virtual accounts". (An earlier support answer that said to remove bank for crypto was incorrect.)

The bank value is environment-scoped:

Sandbox (this collection): use slovak_savings_bank (the international/crypto rail). Sending portage here returns 400 "Invalid bank" — portage is only authorized in production.
Production: the same crypto rail is portage.

bank selects the provider/rail; mode: "crypto" + destination make it a crypto VA — both are needed, they are not redundant. Note: Tron (tron) is accepted on slovak_savings_bank in sandbox even though the destination.network enum historically documented only solana | polygon.

Production variant — change one line: "bank": "portage" (everything else stays the same). slovak_savings_bank and portage are both international/crypto-capable banks; the value is just environment-scoped. Precondition: the user must be status: VERIFIED and eligible for the product.

Not-ready marker: this VA type shows account_number: null until provisioned (the "PENDING-ACT-ACCOUNT" sentinel is ACT-only). Funds-ready = account_number non-null AND != "PENDING-ACT-ACCOUNT".

You can also pass an optional description (string) — a human-readable label for the account. When provided, it is echoed back on the create response and on GET /v1/virtual-accounts/{id}.

Fiat vs crypto mode. Omit destination and send mode: "fiat" to create a USD-balance account (no automatic crypto conversion); provide a destination for crypto mode. Mode is fixed at creation and cannot be changed. mode: "fiat" must omit destination, and fiat mode is not supported on certain banks (returns 400 "Fiat mode (omitting destination) is not supported for this bank.").

Required-for-VA fields (product eligibility). The user must satisfy the product’s pre-submission required fields before a virtual account can be created: expected_monthly_volume and expected_transaction_count (the sponsor-bank rule), plus every product-specific field and document the user’s missing_fields map reports for the product on GET /v1/users/{id}. If any is absent, this call returns 422 with code: "missing_required_fields" and a top-level missing_fields array naming exactly which are missing — the account is not created in a silently-ineligible state and no virtual_account.created webhook is emitted. Supply the fields on POST /v1/users (bucketed enums that differ for individuals vs businesses — see Creating users) or backfill with PUT /v1/users/{id}, then retry — the same idempotency-key may be reused after a 422.

POST

virtual-accounts

curl --request POST \
  --url https://api.balampay.com/v1/virtual-accounts \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'Idempotency-Key: <idempotency-key>' \
  --header 'x-api-key: <api-key>' \
  --data '
{
  "user_id": "{{verified_user_id}}",
  "type": "US_BANK",
  "mode": "fiat",
  "bank": "slovak_savings_bank"
}
'

{
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "status": "<string>",
  "type": "US_BANK",
  "mode": "fiat",
  "created_at": "<string>",
  "bank": "portage",
  "destination": {
    "currency": "<string>",
    "network": "<string>",
    "address": "<string>"
  },
  "source_deposit_instructions": {},
  "description": "<string>",
  "markup": {},
  "metadata": {}
}

{
  "code": "<string>",
  "message": "<string>",
  "error": "<string>",
  "errors": [
    {
      "field": "<string>",
      "message": "<string>"
    }
  ],
  "details": "<array>"
}

{
  "message": "<string>",
  "code": "<string>",
  "statusCode": 123,
  "error": "<string>",
  "timestamp": "<string>",
  "path": "<string>",
  "details": "<unknown>"
}

{
  "code": "missing_required_fields",
  "message": "Virtual account creation requires expected_monthly_volume and expected_transaction_count. Provide these fields on the user before creating a virtual account.",
  "missing_fields": [
    "expected_monthly_volume",
    "expected_transaction_count"
  ]
}

Changed in this version.

Authorizations

Authorization

string

header

required

Access token from POST /auth (the data.access_token value).

x-api-key

string

header

required

API key issued by Kira. Required on every request, including /auth.

Headers

X-Api-Version

string

Optional. The date-versioned API version to apply for this request (e.g. 2026-04-14). When sent it always wins, even over your pinned account default. When omitted, the API uses your account's pinned version if set, otherwise a baseline default.

Example:

"2026-04-14"

Idempotency-Key

string<uuid>

required

Example:

"{{idempotency_key}}"

Body

application/json

Request body for POST /v1/virtual-accounts. bank is required for US_BANK unless provider is supplied. destination is required for crypto mode and must be omitted for mode: "fiat". A Idempotency-Key (UUID) request header is also required.

user_id

string<uuid>

required

A user with status: VERIFIED, eligible for the product.

type

enum<string>

required

Virtual-account product. The US_BANK path is the documented golden path.

Available options:

US_BANK

bank

enum<string>

Selects the provider/rail for US_BANK. Recommended default: the international/crypto rail — slovak_savings_bank (sandbox) / portage (production). Environment-scoped: sandbox accepts slovak_savings_bank, austin_capital_trust; production accepts portage, austin_capital_trust. Required for US_BANK unless provider is given.

Available options:

portage,

slovak_savings_bank,

austin_capital_trust

provider

enum<string>

Alias that selects a bank (act → austin_capital_trust). Provide this instead of bank to satisfy the bank requirement for US_BANK.

Available options:

act

mode

enum<string>

Fixed at creation and cannot be changed. fiat must omit destination; crypto requires it.

Available options:

fiat,

crypto

destination

object

Crypto payout target. Omit entirely for fiat mode.

Show child attributes

description

string

Human-readable label, echoed back on create and on GET /v1/virtual-accounts/{id}.

metadata

object

Stripe-style key/value map: up to 50 keys; key ≤ 40 chars (no [ or ]); value ≤ 500 chars.

Show child attributes

markup

object

Optional per-VA fee-markup overrides (decimal strings).

Show child attributes

Response

Created. Returns the new virtual account.

Response for POST /v1/virtual-accounts (HTTP 201).

string<uuid>

required

status

string

required

KYB-mapped status at version 2026-04-14: typically approved, rfi, or declined. approved does not mean funds-ready — confirm readiness via account_number and the virtual_account.activated webhook.

type

enum<string>

required

Virtual-account product type — US_BANK for the US virtual accounts documented in this reference.

Available options:

US_BANK

mode

enum<string>

required

Funding mode echoed back. crypto accounts return a populated destination (wallet address); fiat accounts return destination: null.

Available options:

fiat,

crypto

created_at

string

required

ISO 8601.

bank

enum<string>

Present for US_BANK; the effective bank (after any provider alias is resolved).

Available options:

portage,

slovak_savings_bank,

austin_capital_trust

destination

object | null

Null for fiat virtual accounts.

Show child attributes

source_deposit_instructions

object | null

Provider deposit details; null while the VA is still activating.

description

string

Present only when supplied on create.

markup

object

Present only when a non-empty markup was supplied on create.

metadata

object

Your own key/value metadata, echoed back verbatim. {test_key: "test_value"} sent on create was returned unchanged.

curl --request POST \
  --url https://api.balampay.com/v1/virtual-accounts \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'Idempotency-Key: <idempotency-key>' \
  --header 'x-api-key: <api-key>' \
  --data '
{
  "user_id": "{{verified_user_id}}",
  "type": "US_BANK",
  "mode": "fiat",
  "bank": "slovak_savings_bank"
}
'

{
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "status": "<string>",
  "type": "US_BANK",
  "mode": "fiat",
  "created_at": "<string>",
  "bank": "portage",
  "destination": {
    "currency": "<string>",
    "network": "<string>",
    "address": "<string>"
  },
  "source_deposit_instructions": {},
  "description": "<string>",
  "markup": {},
  "metadata": {}
}

{
  "code": "<string>",
  "message": "<string>",
  "error": "<string>",
  "errors": [
    {
      "field": "<string>",
      "message": "<string>"
    }
  ],
  "details": "<array>"
}

{
  "message": "<string>",
  "code": "<string>",
  "statusCode": 123,
  "error": "<string>",
  "timestamp": "<string>",
  "path": "<string>",
  "details": "<unknown>"
}

{
  "code": "missing_required_fields",
  "message": "Virtual account creation requires expected_monthly_volume and expected_transaction_count. Provide these fields on the user before creating a virtual account.",
  "missing_fields": [
    "expected_monthly_volume",
    "expected_transaction_count"
  ]
}

Authentication

Versioning

Users

Virtual Accounts

Quotations

Payouts

Recipients

Reference

Create a virtual account

Authorizations

Headers

Body

Response