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

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 dLocal and onPay?

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

dLocal + onPay Integration

Keep dLocal and onPay aligned: when finance events happen in one, update the other automatically.

Example: when onPay's "Watch Subscriptions" fires, WEXTL can "Add a Bank Account" in dLocal. dLocal has 31 actions (including Add a Bank Account, Cancel an Enrollment, and Cancel a Payment); onPay has 17 actions (including Cancel a Subscription, Cancel a Transaction, and Capture a Transaction).

Explore Documentation

GDPR
Data Encryption
2FA
Local Data Region

onPay triggersdLocal actions

onPay workflow triggers

dLocal workflow actions

Frequently asked questions

Common questions about connecting dLocal and onPay.

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

dLocalBrowse all dLocal triggers, actions, and integrations.

onPayBrowse all onPay triggers, actions, and integrations.

dLocal + onPay Integration

Frequently asked questions

How do I connect dLocal and onPay?

What can I automate between dLocal and onPay?

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

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

Explore dLocal and onPay, or get started

dLocal + onPay Integration

Frequently asked questions

How do I connect dLocal and onPay?

What can I automate between dLocal and onPay?

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

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

Explore dLocal and onPay, or get started