This integration is currently in beta and the exact mapping of fields might still change.
To enable settlement reporting for dLocal, please follow this guide to enable SFTP access.
You will need to set up reporting with dLocal with the following considerations:
- The report must be a Settlement - Cross-border Payins Model report.
- The report must be in CSV format to be delivered via SFTP.
- Please contact us to get a list of IP addresses for dLocal to whitelist.
- The report file name must follow the naming convention
<merchant_name>_cross_border_report_YYYYMMDD_HHMMSS.csv.
After SFTP access has been set up, you will receive SFTP credentials from dLocal which will be used when enabling settlement reporting in the dLocal connector configuration in our dashboard.
To set up these credentials, please go to the “Connections” tab, select your dLocal connector and navigate to the “Settlement” tab.
Here you can enable settlement reporting, after which you will be prompted to fill out the following:
- The SFTP username.
- The SFTP SSH key.
- The SFTP address, which should include a port number. If it is not provided, the port number will be defaulted to
22.
- The file name prefix, which is the expected report file name without the
_YYYMMDD_HHMMSS.csv part, e.g. <merchant_name>_cross_border_report.
Below is the mapping of dLocal’s report to ours. This data is pulled from dLocal’s Settlement - Cross-border Payins Model report.
| Settlement report | dLocal field? | dLocal report |
|---|
payment_service_transaction_reconciliation_id | Yes | TRANSACTION_ID |
transaction_id | No | - |
payment_service_transaction_id | Yes | DLOCAL_TRANSACTION_ID (only when starting with ‘T-’) |
payment_service_id | No | - |
payment_service_definition_id | No | - |
payment_service_display_name | No | - |
journal_type | Yes | Check journal type mapping table below |
raw_journal_type | Yes | ROW_TYPE |
payment_service_transaction_created_at | Yes | CREATION_DATE (only when DLOCAL_TRANSACTION_ID starts with ‘T-’) |
posted_at | Yes | TRANSFER_DATE |
processing_amount_plain | Yes | LOCAL_AMOUNT |
processing_currency | Yes | LOCAL_CURRENCY |
exchange_rate | Yes | FX_RATE |
currency | Yes | SETTLEMENT_CURRENCY |
gross_credit_plain | Yes | GROSS_AMOUNT (only for chargeback_reversal and settlement) |
net_credit_plain | Yes | NET_AMOUNT (only for chargeback_reversal and settlement) |
gross_debit_plain | Yes | (-1) * GROSS_AMOUNT (only for chargeback and refund) |
net_debit_plain | Yes | (-1) * NET_AMOUNT (only for chargeback and refund) |
fee_markup_plain | Yes | Always null |
fee_interchange_plain | Yes | Always null |
fee_scheme_plain | Yes | Always null |
fee_total_plain | Yes | FEE_AMOUNT |
method | Yes | Standardized value of raw_method |
raw_method | Yes | PAYMENT_TYPE for card transactions, PAYMENT_METHOD_CODE otherwise |
scheme | Yes | Standardized value of raw_scheme |
raw_scheme | Yes | PAYMENT_METHOD_CODE for card transactions, null otherwise |
batch | Yes | TRANSFER_ID |
report_id | No | - |
raw_report_ids | No | - |
ingested_at | No | - |
description | Yes | DESCRIPTION |
transaction_external_identifier | No | - |
transaction_metadata | No | - |
report_payment_service_id | No | - |
report_payment_service_definition_id | No | - |
report_payment_service_display_name | No | - |
payment_service_modification_reference | Yes | DLOCAL_TRANSACTION_ID |
Notes
- Timestamp columns do not contain any timezone info, so they are assumed to be in the
UTC timezone.
Journal type mapping
| dLocal raw journal type | Our journal type |
|---|
CAPTURE | settlement |
CHARGEBACK | chargeback |
CHARGEBACK_REVERSAL | chargeback_reversal |
PAYMENT | settlement |
REFUND | refund |
| any other value | other |
Fields marked as not a dLocal field are populated from our internal data and not
from the ingested payment service report.