Skip to main content
POST
Open a virtual account
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

The corridor (which fiat rail in, which chain out) and the margin come from the deployment's configuration, not from the request.

accountId
string
required

From the onboarding answer.

Minimum string length: 1
walletId
string
required

From the onboarding answer.

Minimum string length: 1

Response

The account and its bank details.

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"

id
string
required

The virtual account id; the one status is polled by.

Example:

"va_1"

key
string
required

The provider's account key.

schemaIn
string
required

Input payment schema.

Example:

"bank_sepa"

details
object
required

Schema-specific bank details to show the depositor (IBAN, ACH, ...).

Example:
applicationFeeBps
number
required

Rheon's margin in basis points.