Skip to main content
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:
  1. The report must be a Settlement - Cross-border Payins Model report.
  2. The report must be in CSV format to be delivered via SFTP.
  3. Please contact us to get a list of IP addresses for dLocal to whitelist.
  4. 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:
  1. The SFTP username.
  2. The SFTP SSH key.
  3. The SFTP address, which should include a port number. If it is not provided, the port number will be defaulted to 22.
  4. 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 reportdLocal field?dLocal report
payment_service_transaction_reconciliation_idYesTRANSACTION_ID
transaction_idNo-
payment_service_transaction_idYesDLOCAL_TRANSACTION_ID (only when starting with ‘T-’)
payment_service_idNo-
payment_service_definition_idNo-
payment_service_display_nameNo-
journal_typeYesCheck journal type mapping table below
raw_journal_typeYesROW_TYPE
payment_service_transaction_created_atYesCREATION_DATE (only when DLOCAL_TRANSACTION_ID starts with ‘T-’)
posted_atYesTRANSFER_DATE
processing_amount_plainYesLOCAL_AMOUNT
processing_currencyYesLOCAL_CURRENCY
exchange_rateYesFX_RATE
currencyYesSETTLEMENT_CURRENCY
gross_credit_plainYesGROSS_AMOUNT (only for chargeback_reversal and settlement)
net_credit_plainYesNET_AMOUNT (only for chargeback_reversal and settlement)
gross_debit_plainYes(-1) * GROSS_AMOUNT (only for chargeback and refund)
net_debit_plainYes(-1) * NET_AMOUNT (only for chargeback and refund)
fee_markup_plainYesAlways null
fee_interchange_plainYesAlways null
fee_scheme_plainYesAlways null
fee_total_plainYesFEE_AMOUNT
methodYesStandardized value of raw_method
raw_methodYesPAYMENT_TYPE for card transactions, PAYMENT_METHOD_CODE otherwise
schemeYesStandardized value of raw_scheme
raw_schemeYesPAYMENT_METHOD_CODE for card transactions, null otherwise
batchYesTRANSFER_ID
report_idNo-
raw_report_idsNo-
ingested_atNo-
descriptionYesDESCRIPTION
transaction_external_identifierNo-
transaction_metadataNo-
report_payment_service_idNo-
report_payment_service_definition_idNo-
report_payment_service_display_nameNo-
payment_service_modification_referenceYesDLOCAL_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 typeOur journal type
CAPTUREsettlement
CHARGEBACKchargeback
CHARGEBACK_REVERSALchargeback_reversal
PAYMENTsettlement
REFUNDrefund
any other valueother
Fields marked as not a dLocal field are populated from our internal data and not from the ingested payment service report.