Execute a transaction (send)
Executes a transfer by accepting an open quote. Reference the quote by its ID; OMS pulls funds from the quote’s source and delivers them to its destination. Pass an Idempotency-Key header to safely retry without sending twice.
Authorizations
Token from POST /auth/token
Headers
Required on POST and PUT requests. Use a unique value per logical mutation attempt, for example a UUID.
Body
Request body for executing a transaction. References the quote to accept; the remaining fields are optional routing hints and metadata.
Response
The request has succeeded and a new resource has been created as a result.
A single movement of money from a source to a destination. Created by accepting a quote, or generated automatically by a deposit address, virtual account, or cash-in. Track its progress with status.
Details for collecting a cash payout: the pickup code, amount, and location.
When the transaction reached a terminal completed state. Absent until completion; distinct from updatedAt.
On-chain instructions for funding a transaction: the address, asset, network, and exact amount to send.
The destination side of a transaction: where funds are delivered, with the amounts and fees on that side.
Details of an asynchronous failure, such as a transaction or webhook that failed after the initial request succeeded. Present only once a failure has occurred.
source, destination transaction Payment rail for this leg: e.g. "wire", "international_wire", "ach", "crypto". Lets clients label the rail without re-deriving it from other fields.
Exchange and effective rates.
Recipient customer when resolvable: internal dest wallet's owner, or the sender for cash/fiat rails. Absent for external blockchain destinations.
Present only when the request supplies customer context; see CustomerRole.
sender, recipient, both Sender customer (the quote owner). OMSX customer TypeID (cst_…).
The source side of a transaction: where funds are pulled from, with the amounts and fees on that side.
USD cost of gas absorbed by the developer when sponsoring gas. Always "0" in alpha - gas is sponsored. Spec § 4.1.
Lifecycle of a transaction. processing: funds in motion. completed: delivered. failed: terminal failure. cashPickupReady: a cash pickup code is ready to collect.
processing, completed, failed, cashPickupReady Direction of value across rails: cryptoToCrypto, fiatToCrypto, or cryptoToFiat.
cryptoToCrypto, fiatToCrypto, cryptoToFiat