Can Checkout trigger actions in dLocal, and dLocal in Checkout?

Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it.

Do I need to write code to integrate Checkout and dLocal?

No. Checkout-to-dLocal automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.

Checkout + dLocal Integration

Build finance workflows between Checkout and dLocal on a visual canvas — map fields once and let data flow.

Example: when Checkout's "Watch Disputes" fires, WEXTL can "Add a Bank Account" in dLocal. Checkout has 3 triggers (including Watch Disputes, Watch Payments, and Watch Transactions); dLocal has 31 actions (including Add a Bank Account, Cancel an Enrollment, and Cancel a Payment).

Explore Documentation

GDPR
Data Encryption
2FA
Local Data Region

Checkout triggersdLocal actions

Checkout workflow triggers

dLocal workflow actions

Frequently asked questions

Common questions about connecting Checkout and dLocal.

Connect your Checkout and dLocal accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.

CheckoutBrowse all Checkout triggers, actions, and integrations.

dLocalBrowse all dLocal triggers, actions, and integrations.

Checkout + dLocal Integration

Frequently asked questions

How do I connect Checkout and dLocal?

What can I automate between Checkout and dLocal?

Can Checkout trigger actions in dLocal, and dLocal in Checkout?

Do I need to write code to integrate Checkout and dLocal?

Explore Checkout and dLocal, or get started

Checkout + dLocal Integration

Frequently asked questions

How do I connect Checkout and dLocal?

What can I automate between Checkout and dLocal?

Can Checkout trigger actions in dLocal, and dLocal in Checkout?

Do I need to write code to integrate Checkout and dLocal?

Explore Checkout and dLocal, or get started