STEP 1
Select dLocal in workflow
Pick dLocal app in the workflow builder [4] - just one click to select the app.
dLocal Integration
Cross-border payment infrastructure for accepting and disbursing funds in emerging markets across Latin America, Asia, and Africa. Connect dLocal financial events to workflows that update records and notify the right teams. Start from Get a Bank Account, then automate actions such as Get a Card and Get a Payment.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Supported triggers and actions for dLocal integration
Triggers can detect changes in dLocal and run actions that can create, search or modify data inside dLocal automatically [3] — exactly how you set them.
- Get a Bank AccountRetrieves details of a specific bank account by its ID.
- Get a CardRetrieve information about a saved card.
- Get a PaymentRetrieve information about an existing payment.
- Get a PayoutRetrieve a payout information based on the payout ID or the external ID.
- Get a RefundRetrieve information about a refund.
- Get a TransferRetrieve the details of a transfer.
- Get an EnrollmentRetrieve information about an existing enrollment by its dLocal enrollment ID.
- Get an OrderRetrieve information about an existing order.
- Get BalanceRetrieves the available balance for making payouts.
- Search Payment MethodsReturns a list of valid payment methods for the requested country.
- Add a Bank AccountAdds a new bank account to an existing account.
- Cancel a PaymentCancel pending payments for alternative payment methods (APMs).
- Cancel a PayoutCancels a payout by its ID.
- Cancel a TransferCancels an existing transfer by its ID.
- Cancel an EnrollmentCancels an active enrollment. Once cancelled, no further recurring payments can be initiated against this enrollment.
- Cancel Wallet TokenCancels an active wallet token so it can no longer be used for payments.
- Check a Refund StatusRetrieve information about the status of a refund.
- Create a CardSecurely register a card with dLocal and receive a card_id to use for future payments.
- Create a PaymentCreates a new payment using any of the available payment methods.
- Create a Scheduled TransferCreates and requests a scheduled fund transfer for a future date.
How to integrate dLocal in automation workflow?
3 simple steps to make your dLocal connected with other apps in automation workflows on WEXTL. Up to 10 minutes integration set up.
STEP 2
Connect dLocal
When prompted, authorize access to dLocal in WEXTL once. dLocal credentials are encrypted and never shared with WEXTL. Authorization will be reused in any future API calls [3].
WEXTL wants to integrate with your dLocal account. Approve?
STEP 3
Build a workflow
Build your workflow with dLocal yourself or with WEXTL® AI Builder. Connect dLocal to any available integrations [5], or use HTTP node to go beyond them.
dLocal
How dLocal connects and integrates with WEXTL
Save and approve your credentials once — WEXTL® stores authorization information encrypted and reuses the authentication whenever dLocal app is called in workflows. That allows your finance automations to run without your attention, per defined schedule [7]. Explore documentation [6] for a detailed list of fields that dLocal supports.
The following table illustrates what fields dLocal integration require during authorization flow inside our workflow builder [4].
Video slide demonstrates how dLocal is connected in WEXTL builder [4].
| Field | Type | Help |
|---|---|---|
| Environment | select | Select the environment to use for the API. |
X-LoginRequired | text | Login to your dashbaord, Navigate to Integration > API Credentials in the Merchant Dashboard.Create API credentials, then copy your x-login credentials. |
X-Trans-KeyRequired | text | Copy your x-trans-key from the recently created API credentials |
Secret KeyRequired | text | Copy your secret_key from the recently created API credentials |
Connect dLocal to popular apps on WEXTL
Enter a name of the other app you want to sync with dLocal below. Click on selected app to explore integration options with dLocal. If the app you search for is not available in WEXTL yet, you can use HTTP node [10] instead to integrate it directly.
Example automation with dLocal integration
Select Search Payment Methods action from dLocal - this will be a starting point in your automation. Whenever event happens in dLocal, workflow will start [7] from Search Payment Methods node.
Search for Create a Payment, connect it as the next step of integration sequence. You can use filters between Search Payment Methods and Create a Payment, so only important data pass from Search Payment Methods to the next step. WEXTL gives you full control over the process of dLocal automation. All parts of workflow are visible on the canvas [4].
dLocal on WEXTL has 31 modules for building finance automations. Explore dLocal documentation for more.
Video slide demonstrates how Search Payment Methods and Create a Payment [6] nodes are used in dLocal workflow.
Frequently asked questions
Common questions about automating dLocal in your workflows.
dLocal has no triggers, but it provides 31 actions including "Get a Bank Account", "Get a Card", and "Get a Payment". Pair them with triggers from other apps to automate dLocal tasks.
Integration has 31 actions, including "Get a Bank Account", "Get a Card", and "Get a Payment", and more. Refer to our dLocal Documentation for detailed inputs and outputs.
No. Most automations are built visually on the canvas by picking triggers, actions, and mapping fields. You can add custom JavaScript with Functions when advanced logic is needed — but our customers do that in rare cases [4].
Yes. Connections are authenticated per account, credentials are encrypted at rest, and you can enforce approvals and team-level access controls on any automation.
The dLocal integration on WEXTL runs directly on its vendor public API — every field name, authentication method, and rate limit is controlled by dLocal official API and covered in documentation [3]. WEXTL handles the request signing and pagination for you.
Absolutely. Where dLocal provides native webhooks, you can use instant triggers to eliminate polling delay. For custom webhooks, WEXTL offers Custom Webhook node, so you can start automation whenever dLocal or any other service sends event to webhook URL.
WEXTL is an AI-first visual canvas. The platform allows you to describe automation in plain text — and AI will wire nodes for dLocal inside the workflow builder [4]. You can also use built-in workflow nodes (AI Agent, Human in the Loop, Condition, Aggregate Results) in pair with dLocal modules to craft complex integration flows with branches, filtering, and conditional logic. There are absolutely no limits of what you can build.
References
List of sources used to gather information about the dLocal integration.
- dLocal integration source code, module specs and credentials implementation.
- Internal dLocal integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official dLocal vendor API documentation — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
- WEXTL® Apps Library
- WEXTL® dLocal App Documentation
- WEXTL® Workflow Scheduler
- WEXTL® HTTP node documentation