dLocal

To connect with dLocal’s APIs securely, valid credentials must be used to authenticate requests. The required credentials depend on the product and the API version.

Each environment, whether a sandbox or a live environment, has its own set of credentials.

API credentials are used in headers and require signing with the <code>x-secret-key</code>.

OAuth credentials are used to generate access tokens when working with Payouts v3.

- API credentials are used in headers and require signing with the <code>x-secret-key</code>.
- OAuth credentials are used to generate access tokens when working with Payouts v3.

<a href="https://docs.dlocal.com/docs/generate-signature" rel="nofollow noopener noreferrer" target="_blank">Read more about how authentication works</a>.

All credentials are available in the dLocal Merchant Dashboard.

Log in to the <a href="https://dashboard.dlocal.com" rel="nofollow noopener noreferrer" target="_blank">dLocal Merchant Dashboard</a>.

Go to Settings → Integrations

Depending on your integration, you’ll see:

1. Log in to the <a href="https://dashboard.dlocal.com" rel="nofollow noopener noreferrer" target="_blank">dLocal Merchant Dashboard</a>.
2. Go to Settings → Integrations
3. Depending on your integration, you’ll see:

- <code>x-login</code>
- <code>x-trans-key</code>
- <code>x-secret-key</code>

- For Payins and Payouts (v2)
 - <code>x-login</code>
 - <code>x-trans-key</code>
 - <code>x-secret-key</code>

- <code>client_id</code>
- <code>client_secret</code>

- For Payouts (v3)
 - <code>client_id</code>
 - <code>client_secret</code>

These values are used to authenticate requests or generate OAuth tokens.

Can’t find your credentials? Contact your Technical Account Manager or email <a href="" rel="nofollow noopener noreferrer" target="_blank">integrations@dlocal.com</a>.

Keep all credentials secure. Do not expose them in frontend code or public repositories.

Use the appropriate credentials for each environment.

- Keep all credentials secure. Do not expose them in frontend code or public repositories.
- Use the appropriate credentials for each environment.

Learn about the types of API keys and where to find them.

Understand API Credentials

___________________________________________________________

Dlocal LLP (Company Number UK OC413287) is a limited liability partnership incorporated in England and Wales. DLocal Limited (Company Registration Number C77538) is authorised by the Malta Financial Services Authority under the Financial Institutions Act for the issuance of electronic money and the provision of payment services. Dlocal Corp LLP (Company Number UK OC 424987) is registered as a Money Service Business (MSB) with Financial Crime Enforcement Network in United States of America (USA) under MSB Registration Numbers 31000193620515. Dlocal Corp LLP acts as agent of e-commerce merchants based in the USA, and collects payments from end users based in emerging markets, on behalf of the merchants.

About dLocal

Developer docs

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

No tickets created by you

Try using different keywords or checking for typos.

No tickets found

Title

Track the progress of all tickets related to your company.

Tickets portal.

{assigneeName} needs more information from you

Tickets

No access to tickets portal

English

url(https://downloads.intercomcdn.com/i/o/c28cxdcq/736506/6c68fab6537c695b2db838ec7f5c/9f4bc0fb6a885d8471008d43b8d158ef.png)

Credential type	Used for	Authentication method	Credentials
API Credentials	Payins and Payouts (v2)	API Key Pair + Secret	`x-login`, `x-trans-key`, `x-secret-key`
OAuth Credentials	Payouts (v3)	OAuth 2.0 How authentication works	`client_id`, `client_secret`

Credentials	Type	Description
`x-login`	String	Sent as a header to identify the merchant making the request.
`x-trans-key`	String	Sent as a header along with `x-login` to authenticate the request.
`Secret key`	String	Used to generate the signature for the `Authorization` header in API requests.
`Smartfields API key`	String	Used in the tokenization process; acts as the merchant ID for identification. Only for Smart Fields integration.

Credentials	Type	Description
`client_id`	String	Unique identifier assigned to your application. Used when requesting an access token.
`client_secret`	String	Secret associated with your `client_id`. Used for secure token exchange.

Understand API Credentials

Credential types

Where to find credentials

API credentials detail

API Credentials

OAuth Credentials

Best practices