STEP 1
Connect dLocal and onPay
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
dLocal and onPay Integration
Keep dLocal and onPay in sync by integrating their events and actions. When finance events happen in dLocal, update the onPay automatically - without any line of code in visual workflow builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about dLocal and onPay
Detailed info you need to know about dLocal and onPay integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect dLocal to onPay
Set up your dLocal and onPay integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected dLocal and onPay nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between dLocal and onPay. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between dLocal and onPay work in WEXTL?
WEXTL exposes actions and triggers for dLocal and onPay that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
onPay triggersdLocal actions
onPay modules
- Cancel a SubscriptionCancels a subscription for a specified user or service.
- Cancel a TransactionCancels a transaction.
- Capture a TransactionCaptures a transaction.
- Create a PaymentCreates a new payment.
- Create a Transaction From a SubscriptionCreates a new transaction from a subscription.
- Get a SubscriptionRetrieves a specific subscription by its identifier.
- Get a TransactionRetrieves transaction events.
- Get an AcquirerRetrieves a specific acquirer.
- List AcquirersRetrieves a list of acquirers.
- List ProvidersRetrieves a list of providers.
- List SubscriptionsRetrieves all subscriptions.
- List Transaction EventsRetrieves transaction history events from onPay. This endpoint is optimized for keeping systems in sync with the latest transaction activity and supports cursor-based pagination to avoid refetching already processed events.
- List TransactionsRetrieves a list of transactions.
- List WalletsRetrieves a list of wallets.
- Make an API CallPerforms an arbitrary authorized API call.
- Refund a TransactionRefunds a transaction.
- Update an AcquirerUpdates settings of an acquirer.
- Watch SubscriptionsTriggers when a subscription is created or updated.
- Watch Transaction EventsTriggers when transaction events occur.
- Watch TransactionsTriggers when a transaction is created or updated.
dLocal modules
- 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.
- Create an AccountCreates a new account.
- Create an EnrollmentCreates a new enrollment to enable recurring payments for a payer.
- Create an Installments PlanCreate customized installment plans for card payments.
- Create an Instant TransferCreates and submits an instant fund transfer.
- Delete a CardUnlink a card_id so that it cannot be used any further.
- Disable a Bank AccountDisables a bank account so it can no longer be used for payouts.
- 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.
- Make a RefundIssues a refund against an existing payment.
- Make an API CallPerforms an arbitrary authorized API request to any dLocal endpoint.
- Release a PayoutReleases a payout that is currently on hold.
- Search Payment MethodsReturns a list of valid payment methods for the requested country.
- Submit a PayoutSubmits a new payout disbursement request.
- Update an AccountUpdates account information and uploads supporting documents.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with dLocal and onPay integrations. Pick any from the list below if the current combination isn't the one you need.
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. [3]
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 a Payment, and Cancel a Payout); onPay has 17 actions (including Cancel a Subscription, Cancel a Transaction, and Capture a Transaction). Add filters and transforms between steps when you need them. [1]
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. [2]
No. dLocal-to-onPay automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment dLocal (or onPay) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your dLocal + onPay automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the dLocal and onPay integration.
- dLocal and onPay integration source code, module specs and credentials implementation.
- Our dLocal and onPay integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for dLocal and onPay — 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.
- dLocal integration information
- onPay integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library