Resolve a funding transfer held for compliance review (sandbox only)
Resolves the transfer into this order’s funding address that is currently held for compliance review. The transfer is itself a readable deposit transaction on GET /v2/transactions, but this lever takes the order id, the same handle as the funding lever — the decision applies to the transfer the order is waiting on. outcome: "approve" clears the hold and the transfer goes on to fund the order; it is available only while the review is still pending, and returns 409 once the review has already rejected the transfer, matching production. outcome: "reject" holds the funds permanently — they neither fund the order nor go back — and the order goes unfunded and expires at its deadline. Returns 202: the resolution is applied asynchronously, and the body is the order as of the call, so poll GET /v2/orders/{orderId} for the outcome. Repeating the call while the review is still open is safe; once it has resolved, a repeat is a 409.
Authorizations
Path Parameters
Body
approve clears the compliance hold and the transaction resumes (deposit credits / withdrawal proceeds). reject terminalizes the transaction using the transaction type's default compliance terminal (deposit → frozen, withdrawal → rejected).
approve, reject Response
The order as of the compliance resolution
^ord_[0-9A-Za-z]{22}$^cus_[0-9A-Za-z]{22}$pending, succeeded, failed, cancelled onramp, offramp, conversion - Option 1
- Option 2
source, destination ISO 8601 timestamp
"2026-01-15T09:30:00.000Z"
ISO 8601 timestamp
"2026-01-15T09:30:00.000Z"
^txn_[0-9A-Za-z]{22}$Client-supplied reference, unique per resource within your organization. 1-255 characters from A-Za-z, 0-9, underscore, hyphen, colon, and period — no spaces.
^[A-Za-z0-9_\-:.]{1,255}$The funding resource, when the order named one. Omitted entirely on a deposit-funded order (created without a source): the funding wallet is Conduit-managed infrastructure with no client-resolvable id, and depositInstructions carries the address to fund at instead. The presence of depositInstructions is the discriminator.
- Option 1
- Option 2
AutoPayout payload. Crypto recipients omit rail/ach/swift/instant/remittance; fiat (us|swift) recipients require rail and may carry the matching per-rail context block.
ISO 8601 timestamp
"2026-01-15T09:30:00.000Z"
client, auto ISO 8601 timestamp
"2026-01-15T09:30:00.000Z"
expired, client_cancelled insufficient_funds, provider_unavailable, provider_rejected, internal_error, cancelled Where to send funds to fund this order. Exactly one crypto_address block.
1 elementTransfers that funded this order, with how much of each it draws. Present on the order detail read for an order funded at a Conduit funding address; omitted on the list read and on an order that names its own source.