Skip to main content
POST
Resolve Payment Order Requirements
Call this operation only when the returned schema contains an x-resolution definition whose url points to this endpoint. We recommend passing the sessionId returned by the deposit quote together with the current additionalData. The session keeps the wallet, asset, fiat currency, amount, rail, and selected provider route consistent throughout the flow. sessionId is optional: when it is omitted, send assetId, currency, amount, and rail instead. Do not send those routing fields again when a session ID is present. The response returns the same sessionId and sessionExpiresAt. Use that session when creating the payment order. If it expires or the selected route is no longer available, request a new quote and repeat requirement resolution.
For customer identity, session binding, onboarding recovery and fee semantics, see Customer fiat flows.

Authorizations

x-api-key
string
header
required

Path Parameters

id
string<uuid>
required

Wallet identifier.

Body

application/json

Supply sessionId, or all original routing fields. Repeated fields must match the session. Customer identity is inherited from the session.

sessionId
string<uuid>
required

Session ID returned by the deposit quote.

customerId
string<uuid>

Optional existing active customer owned by the authenticated business. Omit for the business-owned flow. Start a new session to change customer identity.

assetId
string<uuid>
deprecated

Stablecoin asset identifier.

Example:

"ae455f23-3824-4125-baab-d158315cbcbd"

currency
string
deprecated

ISO 4217 fiat currency.

Required string length: 3
Example:

"NGN"

amount
string
deprecated

Stablecoin amount as a decimal string.

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

"100.00"

rail
enum<string>
deprecated

Collection method being resolved.

Available options:
one_time_virtual_account,
payment_link,
qr_code
additionalData
object

Current values from the dynamic requirements form.

Example:
provider
string
deprecated

Provider slug selected during quote discovery.

Example:

"example-provider"

Response

Successful response.

message
string
required

Human-readable result.

Example:

"Payment order requirements resolved successfully"

data
object
required
status
boolean
required
Example:

true