Skip to content

Logo

dLocal

Local payments in emerging markets made easy

Supports in this guide: Payouts

Provider website: dlocal.com

What you need to do for start processing transactions (brief summary)

  1. Get your credentials (from dLocal)
  2. Connect in Dashboard
  3. Send an API request

Prerequisites: get from dLocal

Send a connection request at dlocal.com/lets-talk or contact your dLocal account manager directly to get your account verified and receive the following credentials.

  • X-Login -> Corefy field x_login.
  • X-Trans-Key -> Corefy field x_trans_key.
  • PG secret key -> Corefy field pg_secret_key -> required by the connection form, but not currently used for anything - Corefy's dLocal integration only covers Payouts.
  • Cashout (Payouts) secret key -> Corefy field pog_secret_key -> used to sign your payout requests; this is the key that actually matters.
  • Currencies -> Corefy field currencies -> choose the currencies available for your dLocal account (multi-select).

Important

Whitelist Corefy's IP addresses on dLocal's side - see the integration docs. Make sure the correct whitelist is set for whichever mode (Test/Live) you are configuring.

Payouts processing (connect Provider account, create payout-invoice)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

Open dLocal in the provider directory and press Connect at dLocal Provider Overview page in the New connection section.

Step 2 - Fill in fields and select settings

  • X-Login
  • X-Trans-Key
  • PG secret key
  • Cashout secret key
  • Currencies -> select all that apply to your account
  • Test Mode -> (enable if you are using sandbox credentials; make sure this matches whichever credential set - test or live - you entered)

Success

You have connected dLocal Provider account!

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds to a bank account in one of dLocal's supported countries. The destination country is derived automatically from the service you choose - one service per supported currency/country.

Payout - MIN (Argentina example)

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "7a8b9c0d-1e2f-4031-8c24-7d8e9f0a1b2c",
      "service": "dlocal_ar_ars",
      "currency": "ARS",
      "amount": 1000,
      "fields": {
        "document_id": "20-17254359-7",
        "bank_account": "0240015010003005018060",
        "bank_code": "005",
        "bank_branch": "1797",
        "account_type": "C",
        "beneficiary_name": "Pedro",
        "beneficiary_lastname": "Romero"
      }
    }
  }
}

Important

fields is a direct passthrough to dLocal's own cashout API - whatever keys you send under fields are forwarded to dLocal exactly as named (document_id, bank_account, bank_code, bank_branch, account_type, beneficiary_name, beneficiary_lastname, etc.), with no field-name translation. The exact set of required fields depends entirely on the destination country's banking requirements - check dLocal's own API documentation for the country you're paying out to. customer data is not used at all; everything comes from fields.

Payout - MAX

There is no separate MAX variant - which fields are needed (and whether they're required) depends on the destination country, not on optional enrichment the way other connectors work. Consult dLocal's cashout API reference for the field set required by each supported country.

Supported countries/currencies

  • Argentina - ARS - dlocal_ar_ars
  • Colombia - COP - dlocal_co_cop
  • Mexico - MXN - dlocal_mx_mxn
  • Chile - CLP - dlocal_cl_clp
  • Brazil - BRL - dlocal_br_brl
  • Peru - PEN - dlocal_pe_pen
  • India - INR - dlocal_in_inr
  • Bolivia - BOB - dlocal_bo_bob
  • Paraguay - PYG - dlocal_py_pyg

No Options or Constants are configured for this connector.

Refunds

Refunds don't apply - this connector only supports Payouts.

Additional info

  1. No merchant-triggered active status request - payout statuses are updated via dLocal's own asynchronous notification and Corefy's own periodic reconciliation with dLocal, not an on-demand check you can trigger per payout.
  2. Payments are not supported - only Payouts are implemented for this connector.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify X-Login, X-Trans-Key and the Cashout secret key match the selected environment (test_mode), and that your IPs are whitelisted on dLocal's side for that environment
  • Payout rejected for missing field -> check dLocal's own cashout API documentation for the required fields in the destination country and pass them all under fields
  • Currency or service is not supported -> confirm the currency is both selected on your dLocal Provider account and enabled on your dLocal account itself

Question

Still looking for help connecting your dLocal account? Please contact our support team!