Exchange API credentials for a short-lived Bearer token (~20 minutes). Reuse the same token string on every later call in this flow.

Subscribe to Money Movement, Cross-Border, balance credit/debit, and self_custodian_wallet status events for the full omnibus treasury lifecycle.

Provision the COP Cobre Balance that receives converted funds (Cross-Border destination_id) and funds every local payout (source_id).

Create the Mexican MXN Payout balance first (primary account). It must exist before the Payin balance — Payin accounts reference it via metadata.primary_account for automatic sweeps. Also the source for local payouts and Cross-Border FX.

Provision the USD Global Cobre Balance that holds treasury funding (SWIFT / local USD transfer) and is the source_id of every Cross-Border Money Movement. Request US funding instructions from your KAM after creation.

Pre-register the payer as an r2p counterparty and pass source_id when creating the Checkout. Email is used for PSE authentication; phone for Nequi push. Cobre can collect payer data on the hosted page if you skip this step — this flow shows explicit counterparty creation for faster checkout and pre-filled payer details.

Create a hosted Checkout link credited to your COP Cobre Balance. Set checkout_rails to all four Colombia options: pse, bancolombia, nequi, breb — the payer chooses the method on Cobre's hosted page. Pass source_id from the registered counterparty. Amount is integer cents (500000 = COP 5,000.00). Share checkout_url with the customer or redirect them there.

POST /checkouts does not return a Money Movement. When the payer finishes on the hosted page, Cobre creates an R2P MM and sends money_movements.status.*. Poll GET /money_movements/{mm_id} if needed (nested defaults to false — source and destination are null). batch_id equals the Checkout chk_…; creator is the r2p source counterparty. This demo is a completed PSE payment; other rails produce r2p_nequi, r2p_bancolombia, or r2p_breb.

Match the MM completion webhook to your platform ledger on external_id. Use content.batch_id to tie the payment back to the Checkout (chk_…). Cross-check the COP balance credit via GET /accounts/{acct_id}/transactions. For D+1 close, export payins with POST /reports.

Mapping the webhook payload from an earlier step onto Platform ledger. No API call is made — this step closes the loop in your own system.

Register the Colombia merchant beneficiary for Fast Pay / ACH payout from the COP omnibus balance.

Create a Money Movement to the bank counterparty. Cobre routes it over Fast Pay (near real-time) when the destination bank supports it, automatically falling back to ACH (batch) otherwise — the response type tells you which rail was used ('fast_pay' here). checker_approval is false for immediate payout; set true for maker–checker (Money Movements Approval guide).

Identical reconciliation to Bre-B: key on mm_id + external_id from the completion webhook. The response/webhook 'type' field (fast_pay vs ach) is the only thing that differs between the two bank rails.

Mapping the webhook payload from an earlier step onto Your Ledger. No API call is made — this step closes the loop in your own system.

Provision a Virtual CLABE linked to your MXN Cobre Balance for one end user or order. Share the returned value (18-digit CLABE) with the payer — inbound SPEI transfers credit your balance automatically. Create one reference per end-user sub-account or per payment intent.

The payer sends MXN via SPEI to the Virtual CLABE (703013052111000099). Cobre credits acc_PspMexOmnibus01 with spei_credit — reconcile using metadata.account_reference matching ref_MerchantMx01. No Money Movement is created.