Skip to main content
Dlocal Gateway Integration
Support avatar
Written by Support
Updated over a year ago

Created 7/22/2022

Updated 7/22/2022

To configure Dlocal Gateway into your sticky.io CRM, you will go to Payments>Gateways, under ACTIONS select Add New Provider Profile. Select the type = Payment/Gateway and select Dlocal from the drop down. Fill out the gateway parameters which are outlined below and click “Save”.

If you are using Smartfields the integration work is done on the front end to use that API etc. Dlocal documentation on Smartfields can be found here

**NOTE** This gateway cannot be used in any Payment routing or Cascade option from a different Gateway.

For more information on this Gateway click here

These parameters are briefly described here for your reference:

Alias: name that you will assign to the gateway. This is for internal purposes only; it helps you identify a specific gateway account among several of them in your CRM.

Login ID: Dlocal will provide you with the API Login.

Transaction Key: Dlocal will provide you with the Trans Key.

Secret Key: This will be provided to you by Dlocal.

Currency: Dlocal currently supports dozens of currencies. Click the drop down when setting up the profile for the full list.

Test Mode: Set to YES if you would like to use this gateway in test mode.

***NOTE*** if you use the Delayed Capture feature below, it is IMPERATIVE that you do not change the gateway if your Order status is pending. These transactions will ONLY settle on the MID they were authorized on.

Enable Delayed Capture: Set to YES if you want to capture an authorization up to seven days from the day of the auth. Also an order will remain as pending in the system until the authorization is captured upon the count of days defined. Set to No if you want the standard authorization and capture process for your orders

Capture on Shipment: Set to YES if you want to capture an authorization once an order is marked a shipped in the CRM. Also, an order will remain as pending in the system until the authorization is captured upon shipment. Set to No if you want the standard authorization and capture process for your orders.

**NOTE**

The Document Id is required when using this gateway. This value is provided by the customer, and reflects the customers valid identity document. When creating an order from the UI via the 'New Order' button, you will see a field for 'Document Id':

If creating orders via API, you will need to include the 'documentId' parameter and value within the New Order call to create the order.

Please refer to the following Dlocal article for further information on supported values: https://docs.dlocal.com/api-documentation/payins-api-reference/country-reference

ADDITIONALLY

There are 2 Required Fields on the Merchant Account Details tab.

· *Descriptor - This will be the MID Descriptor

· *Customer Service Number - The customer service number assigned to the MID

There is 1 Required Field on the Limits and Fees tab

· *Global Monthly Cap - This will be the sales amount allowed monthly on this MID

To maximize the efficiency of sticky.io Reporting Analytics we suggest you take a moment and fill out the rest of the fields. These will all be used in sticky.io’s profitability reports.

For field definitions on all of the fields on the Merchant Account Details Tab and the Limits & Fees Tab - click here- overview of gateway providers

Once your gateway profile has been created, then you will go through your campaigns and assign the gateway to the corresponding campaign(s).

Did this answer your question?