STEP 1
Connect dLocal and Swish
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 Swish Integration
Build finance integration workflows between dLocal and Swish applications in 3 simple steps. Pick an action inside dLocal, then subsequent action inside Swish, map fields once and automation will run exactly how you set it in visual builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about dLocal and Swish
Detailed info you need to know about dLocal and Swish integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect dLocal to Swish
Set up your dLocal and Swish integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected dLocal and Swish 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 Swish. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between dLocal and Swish work in WEXTL?
WEXTL exposes actions and triggers for dLocal and Swish 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.
dLocal actionsSwish actions
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.
Swish modules
- Cancel Payment RequestCancel a Swish payment request that has not yet been completed.
- Check Recurring Availability (Alias)Check if a user is eligible for recurring payments using their phone number.
- Check Recurring Availability (TIN)Check if a user is eligible for recurring payments using their tax identification number.
- Create ConsentCreate a consent request to allow recurring payments from a customer.
- Create Consent TokenCreate a consent token for recurring payments that can be used to open the Swish app.
- Create Payment RequestCreate a Swish payment request for a customer. The customer will receive the request in the Swish app and can approve the payment there.
- Create PayoutCreate a payout to send money to a Swish user.
- Create RefundCreate a refund for a completed Swish payment.
- Delete Scheduled PaymentDelete a scheduled recurring payment before it is processed.
- Generate Prefilled QR CodeGenerate a QR code with pre-filled payment details that the customer can review and confirm.
- Generate QR CodeGenerate a QR code for a Swish payment request that customers can scan to pay.
- Make An API CallPerforms an arbitrarily authorized API request.
- Retrieve ConsentRetrieve the details and current status of a consent.
- Retrieve Payment RequestRetrieve the details and current status of a Swish payment request.
- Retrieve PayoutRetrieve the details and current status of a Swish payout.
- Retrieve RefundRetrieve the details and current status of a Swish refund.
- Update Consent Callback URLUpdate the callback URL for an existing consent.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with dLocal and Swish 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 Swish.
Connect your dLocal and Swish accounts once, pick an action in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: use dLocal's "Add a Bank Account" action to perform Swish's "Cancel Payment Request" action. dLocal has 31 actions (including Add a Bank Account, Cancel a Payment, and Cancel a Payout); Swish has 17 actions (including Cancel Payment Request, Check Recurring Availability (Alias), and Check Recurring Availability (TIN)). Add filters and transforms between steps when you need them. [1]
Yes — pick an action in either app, then an action in the other, and map the fields between them. [2]
No. dLocal-to-Swish 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 Swish) 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 + Swish 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 Swish integration.
- dLocal and Swish integration source code, module specs and credentials implementation.
- Our dLocal and Swish integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for dLocal and Swish — 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
- Swish integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library