MM type | Source balance | Destination |
|---|---|---|
stable_payout | usd_stable balance (pr_stable_omnibus_cobre) | Global counterparty (global_deposit_le / global_deposit_np) |
global | usd Global fiat balance (pr_global_cobre) | Global counterparty (global_deposit_le / global_deposit_np) — funded via automatic on-ramp |
source_id account's provider. For the global variant (payout funded from a fiat balance), see the existing Global payouts in stable guide, which covers supported chains, tokens, and counterparty types in detail.stable_payout is only available for usd_stable balances. copco balances do not support payouts — they are closed loop.usd_stable balance (stable_payout type).global type).global_deposit_le or global_deposit_np with the beneficiary's wallet information and wait for verified status.account_id (usd_stable or Global fiat balance) from which the funds will be debited, used as the source_id.counterparty_id from the previous step as the destination_id.initiated status. If all validations pass, the status changes to processing and the transaction is broadcast on-chain.completed, the beneficiary has received the funds and tracking_key contains the on-chain hash.failed or rejected, the funds are automatically credited back to the source balance.stable_payout or global.initiated status, progressing through processing to completed, failed, or rejected.global_deposit_le or global_deposit_np counterparty and wait for verified status before attempting a payout. See Managing Counterparties.usd_stable or Global fiat) has sufficient funds before creating the payout.initiated status while Cobre validates funds and the counterparty.processing, the source balance is debited and the transaction is executed on-chain.completed, the transaction's tracking_key contains the on-chain hash. On failed, funds are automatically returned to the source balance.