pr_stable_omnibus_cobre. The same provider supports two currencies, selected via metadata.currency:metadata.currency | Balance | On-chain wallets | Payins / Payouts | Rewards |
|---|---|---|---|---|
usd_stable | USD stablecoin | Yes | Yes | No |
copco | COPco (closed loop) | No | No | Yes |
connectivity.status: connecting, and clients should poll the account until it reaches connected.usd_stable balances support self-custodian wallets and on-chain payins/payouts. copco balances only support on/off-ramp with COP fiat and daily rewards — see Stablecoin Funding and COPco Rewards.self_custodian_wallet on a usd_stable balance via the Create an Account Reference API, specifying the network in metadata.chain:metadata.chain | Networks covered | Supported tokens |
|---|---|---|
evm_compatible | Ethereum, Polygon (single wallet address) | USDC, USDT |
tron | Tron | USDT |
stellar | Stellar | USDC |
connectivity.status: processing with an empty value, and transitions to enabled once the address is provisioned by the wallet infrastructure provider.copco balances — they are closed loop in the current phase.provider_id: pr_stable_omnibus_cobre, holding either usd_stable or copco.self_custodian_wallet, representing an on-chain address that receives stablecoins on behalf of a balance.evm_compatible, tron, stellar).usd_stable or copco).connecting status, transitioning to connected once provisioned.usd_stable if you need on-chain payins/payouts and wallets, or copco if you only need to hold COP-denominated value and earn rewards.evm_compatible, tron, or stellar based on where your counterparties or senders operate.usd_stable, payins and payouts.value contains the real on-chain address. Share this address with senders to start receiving stablecoin payins — see Stablecoin Payins.