Skip to main content
Requests represent executable operational instructions created from active quotes. Partners may create:
  • subscription requests
  • redemption requests
Each request is associated with a previously issued quote.

​
Supported Request Types

​
Subscription

​
Redemption

​
Request Creation

A request starts life as a quote: POST /otc/orders/quote creates an order in the QUOTED state, and POST /otc/orders/{id}/confirm turns it into an executable request (PENDING_FUNDING). A valid, unexpired quote is required — confirmation fails with quote_expired or quote_already_used otherwise. Settlement uses your approved payout addresses; no address is passed at confirmation time.

​
Request Lifecycle

Requests support the following lifecycle states.

​
QUOTED

The quote was created and is awaiting confirmation. It expires at quote.expiresAt if not confirmed.

​
PENDING_FUNDING

The request was confirmed and is awaiting funding.

​
PARTIALLY_FILLED

Funding was partially received. The request remains operationally open.

​
FULFILLED

Required funding has been fully received. Payout is prepared next.

​
PROCESSING_PAYOUT

The payout is currently in progress.

​
SETTLED

The payout completed and the request is fully settled.

​
PAYOUT_FAILED

The payout attempt failed. Payouts are retried operationally, returning the request to PROCESSING_PAYOUT.

​
CANCELLED

The request was cancelled before completion.

​
EXPIRED

The request expired before confirmation or before funding completed.

​
Funding Model

Requests support:
  • partial funding
  • multiple funding events
  • asynchronous settlement lifecycle
A single request may receive funding through multiple funding events.

​
Settlement Rules

Settlement only occurs after:
  • operational validation
  • funding validation
  • lifecycle eligibility checks
Settlement timing may vary depending on operational conditions.

​
Request Cancellation

Requests may only be cancelled while in a cancellable state: QUOTED, PENDING_FUNDING, or PARTIALLY_FILLED. Cancelling in any other state returns 409 Conflict.

​
Funding Requirements

Funding must:
  • match the expected asset
  • originate from approved operational sources
  • satisfy request funding requirements
Invalid or incompatible funding may prevent fulfillment.

​
Address Validation

Settlement addresses must:
  • be approved
  • be active
  • match the request asset/network combination
Invalid settlement addresses block settlement until resolved operationally.

​
Precision Rules

​
Operational Visibility

Partners may track:
  • request lifecycle
  • funding lifecycle
  • balances
  • operational statuses
through the Partner API.

​
Error Scenarios

Request creation or processing may fail for reasons including:
  • expired quote
  • invalid address
  • unsupported asset
  • insufficient funding
  • invalid lifecycle state
  • operational restrictions