> ## Documentation Index
> Fetch the complete documentation index at: https://public-openfx.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# COP payout integration guide
> Pay a Colombian bank account or Bre-B key in COP: register the account or key, then meet the memo and limit rules.
Pay a Colombian recipient in Colombian pesos (COP), to a bank account or a Bre-B key.
For the general flow, see [Payout lifecycle](/v3/payouts). The quote, confirm, and webhook steps are the same as for EUR, and so is the fee model. [Supported payout currencies](/v3/payouts#supported-payout-currencies) compares every payout currency side by side.
## Before you start
* Your organization must be enabled for COP. Until it is, a request in it fails with `403` PAYOUT\_CURRENCY\_NOT\_ENABLED.
* The recipient's account needs the Colombian-peso receiving capability, ACTIVE before you pay. [Capabilities](/v3/capabilities#the-capability-catalog) lists the id, and [Be paid in Colombian pesos](/v3/capabilities#be-paid-in-colombian-pesos) lists the identity the recipient owes.
* COP has no sending capability. Don't send a `sender` on a quote or payout, or it fails with `422` SENDER\_NOT\_SUPPORTED.
* Every `POST` needs an `Idempotency-Key` header. See [Idempotency](/v3/idempotency#payments-endpoints).
## Register the bank account or Bre-B key
A Colombian recipient can be paid in two ways, and the address you register decides which. The recipient owes a nationality and an identity document, or for an organization a NIT. See [Be paid in Colombian pesos](/v3/capabilities#be-paid-in-colombian-pesos).
Register the account with `routingFamily` CO\_LOCAL, the four-digit `bankCode`, the `accountNumber`, and the `bankAccountType`. The payout goes over CO\_ACH. OpenFX decides whether it settles the same day or in the next clearing batch, and you can't choose.
The `bankAccountType` is checked against the kinds the bank accepts, and a kind it doesn't accept is rejected when you create the address. No name check runs, so `verifications[]` stays empty.
```bash cURL theme={"theme":{"light":"poimandres","dark":"poimandres"}}
curl -X POST https://api.openfx.com/v3/payments/payout-addresses \
-H "Authorization: Bearer $OPENFX_JWT" \
-H "X-Request-Signature: $OPENFX_SIGNATURE" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{
"payoutAddressType": "BANK_ACCOUNT",
"accountId": "acc_BMY3UenpGBn8ZQ8hio4BgE",
"bankAccount": {
"routingFamily": "CO_LOCAL",
"bankCode": "1007",
"accountNumber": "24512345678",
"bankAccountType": "SAVINGS"
}
}'
```
Register the key with `routingFamily` CO\_BREB and the `brebKey`, written exactly as the account holder gave it: a mobile number, an email address, an identity document number, or a handle with its leading `@`. You don't say which kind it is. The payout goes over BREB, Colombia's instant transfer system.
A key lookup (BREB\_KEY\_LOOKUP) runs while you create the address and compares the holder the key is registered to with the account holder's name. Only a NO\_MATCH result rejects the address. A lookup that can't complete leaves it payable.
Each BREB payout is capped at about COP 12,110,000. A larger `receiveAmount` is refused when the payout is priced, with `422` AMOUNT\_OUT\_OF\_RANGE. `error.details` carries the exact bound.
```bash cURL theme={"theme":{"light":"poimandres","dark":"poimandres"}}
curl -X POST https://api.openfx.com/v3/payments/payout-addresses \
-H "Authorization: Bearer $OPENFX_JWT" \
-H "X-Request-Signature: $OPENFX_SIGNATURE" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{
"payoutAddressType": "BANK_ACCOUNT",
"accountId": "acc_BMY3UenpGBn8ZQ8hio4BgE",
"bankAccount": { "routingFamily": "CO_BREB", "brebKey": "@camilarestrepo" }
}'
```
## Memos
On CO\_ACH and BREB, a `receiverMemo` is at most 40 letters, digits, and spaces. A memo that is too long or holds any other character fails with `400` RECEIVER\_MEMO\_INVALID. OpenFX never truncates it.
## Track settlement
[Trace a payout with the receiving bank](/v3/payouts#trace-a-payout-with-the-receiving-bank) lists the `settlementTraceId` key for CO\_ACH and BREB.
## Common mistakes
* **Naming a `sender`.** COP has no sending capability. Remove `sender` from the quote and the payout.
* **Sending `purpose`.** Only AED takes one.
* **Paying a Bre-B recipient more than the cap.** A `receiveAmount` above about COP 12,110,000 fails with `422` AMOUNT\_OUT\_OF\_RANGE.
## What's next
The general payout flow.
The receiving capability and identity each currency needs.
Paying euro accounts over SEPA or SWIFT.
Paying Mexican bank accounts over SPEI.
Paying UAE bank accounts by IBAN.
Every payout and address event.