Skip to main content
POST
Master Wallet Get Quote
Include customerId when the deposit belongs to an existing customer and requires corridor-specific KYC. The provider adapter infers the corridor from the selected fiat currency. The response can include data.additionalDataRequirements.schema and reusable customer values in data.additionalDataRequirements.data. Use the saved values as form defaults, then complete and validate the current schema before creating the payment order. See Dynamic Forms for the schema-processing flow.

Authorizations

x-api-key
string
header
required

Path Parameters

id
string<uuid>
required

Wallet identifier.

Body

application/json
assetId
string<uuid>
required

Stablecoin asset identifier returned by the supported-assets endpoint.

Example:

"ae455f23-3824-4125-baab-d158315cbcbd"

currency
string
required

ISO 4217 fiat currency code.

Required string length: 3
Example:

"NGN"

amount
string
required

Decimal amount encoded as a string to preserve precision.

Pattern: ^\d+(\.\d+)?$
Example:

"100.00"

rail
enum<string>
required

Payment collection rail.

Available options:
one_time_virtual_account,
payment_link,
qr_code
Example:

"one_time_virtual_account"

sessionId
string<uuid>

Existing deposit session. When supplied, the original route values are authoritative.

customerId
string<uuid>

Existing Blockradar customer identifier. Include it when requesting a new quote so saved provider KYC can be returned and reused.

Example:

"18d2f159-e0cd-4a45-b735-e9dfe0f7520a"

provider
string

Optional provider slug. Omit it to let Blockradar select an eligible provider.

Example:

"example-provider"

Response

200 - application/json

Successful response.

statusCode
integer
required
Example:

200

message
string
required

Human-readable result.

Example:

"Deposit quote fetched successfully"

data
object
required