Skip to main content
POST
Whether the bank transfer has landed
Provider sandbox on this deployment. Our backend targets the bank provider’s sandbox: bank details are test details, no real transfer settles, and settlement lands on a testnet (read network from GET /v1/config). Known limits: only the EUR/IBAN rail is wired for the simulated pay-in, and identity checks run on test-mode applicants. Every response says which environment answered in its environment field.

Authorizations

Authorization
string
header
required

Your API key, issued by us and shown once at creation.

Body

application/json
accountId
string
required
Minimum string length: 1
virtualAccountId
string
required
Minimum string length: 1

Response

The funding state.

environment
enum<string>
required

Which environment answered. sandbox: at least one money upstream is the provider's sandbox - no real money moves there, and the card corridor is the sandbox's asset (read GET /v1/config), not the documented production one. production: every configured upstream is real. Derived from the configured upstream hosts at boot, never a flag.

Available options:
sandbox,
production
Example:

"sandbox"

status
enum<string>
required
Available options:
awaiting_deposit,
funded
transactions
any[]
required

Raw provider transactions, retained for debugging. Not a contract.

deliveredAmount
string

USDC delivered to the wallet, decimal string in major units, once funded.

Example:

"112.350172"

depositedAmount
string

Fiat deposited, decimal string in major units, once funded.

Example:

"100"

txHash
string

Settlement transaction hash, once funded.