Skip to main content
The values each enumerated field on a virtual account takes, and on the deposits it receives. Check it when you are branching on a field’s value.

status

Where the account is in its lifecycle. Which set comes back depends on the version you are pinned to. The status query filter always takes the raw values, whichever version you read.

deposit status

Where an inbound deposit has got to.
A seventh value, NEEDS_ACTION, can come back on a row. It is not a stage. Treat the set as open. Read a value you do not recognise as a deposit still in progress, and keep polling it.

deposit events stage

What happened to a crypto inbound, one entry per stage in its events list.

deposit failure_reason

Why a crypto inbound was not credited, on virtual_account.deposit_funds_failed. A failed settlement on a crypto account sends the same event with free text instead.

bank

Which bank a US_BANK virtual account runs on, and with it the rail. A user’s capabilities.requested_banks takes the same values. austin_capital_trust and jp_morgan are the banks that open new accounts, in sandbox and in production. Kira answers Invalid bank to a bank your account is not authorized for.

mode

What happens to money that arrives in a virtual account. Set when the account is created, and you cannot change it. A crypto account reads fiat while it is frozen.

destination currency

The token a crypto-mode deposit is converted to.

destination network

The chain the token is sent on.

payment_methods status

Whether a rail on the account can be used right now.