Payouts to Dominican Republic

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

Supported configurations

Dominican Republic payouts support the following participant types:

• C2C (consumer-to-consumer) — individual customer to individual counterparty
• B2C (business-to-consumer) — business customer to individual counterparty
• B2B (business-to-business) — business customer to business counterparty

All three use the bank_account route.

Trading account requirement

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

Verify DOP payout availability

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

ℹ️

Bank configuration required

Contact Cybrid support to enable DOP payouts and configure the Dominican Republic 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: DOP-USD or DOP-USDC_SOL
• country_code: DO
• participants_type: C2C, B2C, or B2B
• route: bank_account

You can also query prices for the Dominican Republic:

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

Identity verification requirements

The platform validates all required KYC fields when you create a plan for DOP payouts. Requirements differ by participant type.

Originator (Customer)

Individual originator (C2C):

• name.first, name.last
• date_of_birth
• address.street, address.city, address.country_code

Business originator (B2C, B2B):

• name.full
• address.street, address.city, address.country_code
• identification_numbers with tax_identification_number

⚠️

Business originator tax ID required

Unlike Colombia (which has no originator KYC), the Dominican Republic requires a tax_identification_number on the business originator.

Receiver (Counterparty)

Create the counterparty with the standard required fields for the appropriate type (individual or business), plus the corridor-specific fields below. The counterparty must be in verified state before you can create the external bank account and plan.

Individual counterparty (C2C, B2C):

• name.first, name.last
• address.country_code
• identification_numbers with national_identification_number (Cédula)

Business counterparty (B2B):

• name.full
• address.country_code
• identification_numbers with tax_identification_number (RNC)

⚠️

Receiver identification required

Unlike India and Bangladesh, the Dominican Republic requires identification numbers on all counterparties: a national ID (Cédula) for individuals or a tax ID (RNC) for businesses.

Individual counterparty example:

{
  "type": "individual",
  "name": {
    "first": "John",
    "last": "Doe"
  },
  "address": {
    "country_code": "DO"
  },
  "identification_numbers": [
    {
      "type": "national_identification_number",
      "issuing_country_code": "DO",
      "identification_number": "00100000001"
    }
  ],
  "customer_guid": "customer_guid"
}

Purpose of transaction

For Dominican Republic payouts, purpose_of_transaction is required for all participant types. The allowed values depend on participant type:

• C2C: family_support, personal_transfer
• B2C: Standard business purpose values (such as salary_payment, service_charges)
• B2B: Standard business purpose values (such as service_charges, trade_settlement)

See the API reference for the complete list of purpose values.

External bank account setup

Dominican Republic payouts use LBTR (Liquidación Bruta en Tiempo Real), the country's real-time gross settlement system, routing via SWIFT/BIC codes.

Requirements:

• SWIFT/BIC Code: Bank identifier (for example, BPDODOSX for Banco Popular Dominicano)
• Account Number: Beneficiary account number
• Account Type: checking or savings (required)

⚠️

Account type required

The account_type field is required for LBTR routing. This is shared with Colombia's PSE rail. Other corridors like India, Bangladesh, and Pakistan do not require account_type.

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

{
  "account_kind": "raw_routing_details",
  "name": "Dominican Republic beneficiary account",
  "counterparty_bank_account_details": [{
    "bank_code_type": "SWIFT_BIC",
    "bank_code": "BPDODOSX",
    "account_identifier": "0012345678901234",
    "payment_rail": "LBTR",
    "account_type": "checking"
  }],
  "counterparty_guid": "counterparty_guid",
  "customer_guid": "customer_guid",
  "asset": "DOP"
}

ℹ️

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.

Supported banks

The following institutions are available for DOP payouts to the Dominican Republic. All support C2C, B2C, and B2B participant types. Use the SWIFT/BIC code when setting up the external bank account.

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