Payouts to Colombia

This guide covers Colombia-specific requirements for COP payouts. For the general cross-border payment flow, see Sending Cross-Border Payments.

Supported configurations

Colombia payouts support the following participant types:

• C2C (consumer-to-consumer)
• B2C (business-to-consumer)
• B2B (business-to-business)

Both individual and business customers can originate payouts, and both individual and business counterparties can receive them.

The primary route is bank_account, available for all participant types and source account assets. A mobile_wallet route is also available for COP-USD payouts.

Trading account requirement

Colombia payouts require a USDC_SOL trading account as the source. Other trading account types (such as USDC or USDC_NPL) are not supported for COP payouts.

Verify COP payout availability

Confirm your bank supports COP payouts for your participant type and route.

ℹ️

Bank configuration required

Contact Cybrid support to enable COP payouts and configure Colombia as a supported corridor for your bank.

GET /api/banks/{bank_guid}
Authorization: Bearer YOUR_TOKEN

Look for an entry in supported_payout_symbols where:

• symbol: COP-USD or COP-USDC_SOL
• country_code: CO
• participants_type: C2C, B2C, or B2B
• route: bank_account

You can also query prices for Colombia:

GET /api/prices?payout_country_code=CO
Authorization: Bearer YOUR_TOKEN

Recipient requirements

Colombia payouts require identification numbers and an email address on the counterparty beyond the standard name fields. The platform validates these fields when you create a plan.

⚠️

Stricter recipient KYC

Colombia requires more recipient information than other corridors. Ensure the counterparty has identification numbers and an email address before creating the external bank account and plan.

Individual counterparty

Required fields:

• name.first, name.last
• email_address
• identification_numbers with one of:
  • passport
  • identification_card (Cédula de Ciudadanía)

Business counterparty

Required fields:

• name.full
• email_address
• identification_numbers with:
  • tax_identification_number (NIT)

The counterparty must be in verified state (watchlist screening passed) before you can create the external bank account and plan.

Individual counterparty example:

{
  "type": "individual",
  "name": {
    "first": "John",
    "last": "Doe"
  },
  "address": {
    "street": "123 Main St",
    "city": "New York",
    "country_code": "US"
  },
  "email_address": "[email protected]",
  "identification_numbers": [
    {
      "type": "identification_card",
      "issuing_country_code": "CO",
      "identification_number": "1234567890"
    }
  ],
  "customer_guid": "customer_guid"
}

ℹ️

No originator KYC required

Colombia payouts do not require additional KYC fields on the originator (customer). The customer must be verified, but no specific PII fields are validated at plan creation.

Purpose of transaction

For Colombia payouts, purpose_of_transaction is optional. The platform accepts all standard purpose values. See the API reference for the complete list.

External bank account setup

Colombia payouts use PSE (Pagos Seguros en Línea), which operates through Colombia's ACH network.

Requirements:

• Account Number: Colombian bank account number
• Bank Code: Colombian institution identifier
• Account Type: checking or savings

Send a POST request to /api/external_bank_accounts with the following body:

{
  "account_kind": "raw_routing_details",
  "name": "Colombian beneficiary account",
  "counterparty_bank_account_details": [{
    "bank_code_type": "PSE",
    "bank_code": "064",
    "account_identifier": "87654321",
    "payment_rail": "PSE",
    "account_type": "checking"
  }],
  "counterparty_guid": "counterparty_guid",
  "customer_guid": "customer_guid",
  "asset": "COP"
}

ℹ️

API versioning

Creating external bank accounts with foreign raw routing details requires Accept-Version: 2025-10-01 or later.

For the full account model and field reference, see Create Foreign Fiat External Bank Accounts.

Common validation errors

Related resources

• Sending Cross-Border Payments
• Create Foreign Fiat External Bank Accounts
• Creating a Counterparty
• Verifying a Counterparty
• Create Plan API Reference