dLocal
Keep dLocal in step with your orders, invoices and payments without re-keying, with the right person approving what changes.
20 ways to read.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with dLocal, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Get payout balanceRead
Example flow
- dLocal · Get payout balanceDone
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches dLocal.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to dLocal
- dLocal's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a dLocal test account before you go live.
For developers
Technical detail
dLocal Payins lookups (payments, orders, refunds, chargebacks, cards, payment methods, FX), Payouts v3 payout and balance lookups, and dLocal for Platforms account, balance, KYC, bank and transfer reads.
dLocal API docs- Source actions
- 20
- Data types
- 19
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Cards1
- Get saved cardSource
A saved card's brand, last four and expiry; the holder name is not mapped.
Chargeback statuses1
- Get chargeback statusSource
Lightweight status lookup for a chargeback.
Chargebacks1
- Get chargebackSource
A chargeback by ID (IDs arrive in chargeback notifications).
Enrollments1
- Get enrollmentSource
A recurring-payment enrollment with type, status and schedule.
Exchange rates1
- Get exchange rateSource
dLocal's current rate from USD to a local currency.
Orders1
- Get payment by order IDSource
The payment made for one of your order IDs.
Payment methods1
- List payment methods for a countrySource
Payment methods dLocal accepts in a country, with type and allowed flows.
Payment statuses1
- Get payment statusSource
Lightweight status lookup for a payment.
Payments1
- Read existing paymentSource
Read one dLocal payment: status, amount, payment method, masked card and refunds, using a signed request.
Payout balances1
- Get payout balanceSource
The balance available for Payouts v3, in your settlement currency.
Payouts1
- Get payoutSource
Read one Payouts v3 payout by dLocal payout ID or your external ID: status, amount, dLocal fee, taxes and the amount debited from your balance. Beneficiary and remitter details are not mapped. Nexra never creates, cancels or releases payouts.
Platform account balances1
- Get platform account balanceSource
Current balance, funds available for withdrawal, pay-ins in transit and pending settlements for a platform account.
Platform account KYC1
- Get platform account KYC statusSource
Which KYC fields and documents are completed or missing for a platform account, and any document errors. Field values are not returned.
Platform accounts1
- Get platform accountSource
A dLocal for Platforms user account: status, country and capabilities. Company, representative and contact details are not mapped.
Platform bank accounts2
- Get platform account bank accountSource
One bank account on a platform account, with status and masked number.
- List platform account bank accountsSource
Active bank accounts on a platform account, with status and masked number.
Platform transfers1
- Get platform transferSource
A transfer between platform accounts, by transfer ID. Nexra never creates or cancels transfers.
Refund orders1
- Get refund by your refund order IDSource
A refund looked up by the ID you assigned when it was requested.
Refund statuses1
- Get refund statusSource
Lightweight status lookup for a refund.
Refunds1
- Get refundSource
A refund already issued, by refund ID. Nexra never creates refunds.
Access and limits
- Authentication
- dLocal Payins login, transaction key and secret, plus optional Payouts client credentials
- Plans and access
- A dLocal merchant account with Payins API credentials (X-Login, X-Trans-Key, secret key). Country and payment-method availability depend on the merchant agreement. Payout reads need a separate Payouts client ID and secret from your dLocal Technical Account Manager.
- Test environment
- Use sandbox credentials from the dLocal Merchant Dashboard with sandbox.dlocal.com.
- Rate limits
- dLocal does not publish fixed limits. HTTP 429 and Retry-After are honoured with bounded retries.
- Pagination
- dLocal Payins, Payouts and Platforms have no paginated list or search endpoints; every read is a single lookup or a full list.
- Provider events
- dLocal posts payment, refund and chargeback notifications to the notification_url given at creation; their IDs can be read with these lookups. Flows can start the moment something happens: when a payment is paid; when a card payment is authorised; when a payment is rejected; when a payment is cancelled or expires.
Before you build a flow
- Read only. Intentional exclusions: creating payments, authorizations, captures, cancellations, refunds, enrollments and their cancellation, saving or deleting cards, installment plans, virtual-account references, and submitting, cancelling or releasing payouts and payout quotes.
- dLocal Payins and Payouts have no list or search endpoints, so there is no incremental or date-filtered sync for payments, refunds, chargebacks or payouts; use the IDs from dLocal notifications, your order IDs or your payout external IDs.
- Payout reads (Get payout, Get payout balance) need the separate Payouts v3 client ID and client secret; without them those two reads are refused before any call. Bring-your-own-key: the connection exchanges them for a 180-second token itself.
- Settlements and payout lines: dLocal has no API for settlement batches or their transaction lines. The Daily Payins, Settlement and Daily Payouts reports are delivered only by email or SFTP, arranged with your Technical Account Manager.
- Fees: Payins payment, refund and chargeback records carry no fee or net amount; processing fees appear only in the emailed or SFTP settlement reports. Payout fees and taxes are on Get payout (feeAmount, taxAmount, debitAmount).
- Payments older than 12 months are unavailable. Card holder names, payer documents and 3-D Secure values are not mapped.
- Exchange rates are available only from USD.
- dLocal for Platforms reads (accounts, balances, KYC status, bank accounts, transfers) call marketplace-api.dlocal.com (sandbox marketplace-api.dlocal-sbox.com) and need dLocal for Platforms enabled by your Technical Account Manager.
- Platforms exclusions: account creation, KYC updates and document uploads, settings changes, block, unblock and cancel, adding or disabling bank accounts, and creating or cancelling transfers. Company, legal-representative and contact details and full bank account numbers are never mapped.
- Gated: KYC Verifications use separate credentials and are not covered.
Developer reference
- Create the dLocal credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose dLocal, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/dlocal and the Connections API.