Automated workflows ensure prompt response handling.
Connect
Follow these steps to connect your dLocal account to Chargebackhit. The dLocal integration supports dispute management only, so it does not include alert matching, refunds, or subscription cancellation.
Representment applies to new disputes only. Disputes created before the integration is connected are not imported retroactively.
Step 1. Get API credentials in dLocal
Chargebackhit requires the dLocal x-login, x-trans-key, and secret key to connect to your account.
You need the developer or admin role in the dLocal merchant dashboard to access API credentials.
Make sure the environment toggle is not set to Test mode.
Click on + Create new and enter the description Chargebackhit.
Copy and securely store the x-login, x-trans-key, and secret key shown on screen.
x-login, x-trans-key, and the secret key display only once, at creation, and cannot be viewed again. If you already have an active credential, create a new one to complete this integration.
After you submit the credentials, HUB generates three webhook URLs: Payins, Chargebacks, and Refunds. Copy all three URLs. You need them for the next step.
Step 3. Set webhook URLs in dLocal
To set the webhook URLs
In the dLocal merchant dashboard, go to Developers > Integration > Endpoint.
Paste the URLs copied from HUB into the matching fields:
Payins notification URL
Chargebacks URL
Refunds URL
Leave Callback URL as is.
This field applies to payment redirects only.
Click on Save.
Chargebackhit now receives payment, chargeback, and refund webhooks from dLocal to make your evidence stronger.
dLocal supports a single Chargebacks URL field. Pointing it to Chargebackhit stops chargeback webhooks from reaching any system currently configured at that field. Update your existing setup accordingly before you save.
If your notification URLs are already in use for another purpose, connect the dispute management service with the Chargebacks URL alone. Skipping the Payins and Refunds URLs means Chargebackhit does not receive payment data from dLocal and cannot enrich chargebacks with full payment information for evidence. Add this information manually through Guide Add supporting evidence, such as receipts or delivery confirmations, to a dispute before it is submitted to the card network.evidence enrichment
instead.
Final checklist
Before completing the integration, confirm you:
Created a new dLocal API credential with the description Chargebackhit
Saved the x-login, x-trans-key, and secret key
Entered the credentials in the dLocal provider configuration in the Chargebackhit HUB
Copied the Payins, Chargebacks, and Refunds webhook URLs from HUB
Pasted the webhook URLs into the matching fields in the Endpoint settings of the dLocal merchant dashboard
Completed your Guide Add your business information to the HUB settings to enable and fully support the dispute representment process.business details
in the Chargebackhit HUB settings