FX and PSP integrations

Use Omega's exchange capabilities as one part of a larger treasury or payment workflow.

Conversion is the exchange step#

Discover exact asset representations, obtain an indicative estimate if useful, authorize executable terms once the execution contract is released, and reconcile the resulting operation and funds.

An indicative JIT estimate is neither a fixed-rate commitment nor a 30-minute quote guarantee. The fee and slippage bounds still need an explicit execution contract.

Movement is a separate step#

A same-asset internal transfer moves funds between eligible Omega accounts. It does not perform FX or pay an external wallet or bank.

A conversion followed by an onward transfer comprises separate actions. If the transfer fails, preserve the already completed conversion and reconcile the remaining balance. Do not describe the sequence as atomic conversion-to-recipient.

External delivery has its own evidence#

A requested withdrawal, claim issuance, claim submission and confirmed token delivery are separate facts. Supported withdrawal chains and routes must be established by the released environment contract; arbitrary destination-chain support is not specified.

These docs make no current fiat-ramp, bank-payout provider or guaranteed-arrival promise. A PSP must separately establish its delivery contract and applicable provider behavior.

Reference material#

See funding and balances for the target exchange views and settlement and delivery for the separate completion checks.