Settlement reconciliation

When a transaction is created with a payment service, the reconciliation_id is passed to the payment service if possible.

This ID is used to link the transaction from the payment service’s report back to the system. In the reports, this ID is reported, along with the transaction_id as well as the ID of the transaction in the payment service’s system (the payment_service_transaction_id).

The reconciliation_id is actually just a Base62-encoded version of the transaction_id. This ID is used because not all payment services can handle the full length of UUID transaction IDs.

Reconciling to the system

Storing the reconciliation_id or the transaction_id in systems against an order is recommended, so that reports can be reconciled against the system.

This reconciliation_id allows matching the settlement of funds against the order and closing of any open position in the system.

In the near future, support for marking the transaction as settled in the system is added, and additional data from requests, like an external_identifier reference in reports is offered. This allows seeing in the dashboard which transactions are settled, and reconciling reports based on a custom identifier.

Identifying the original report

It is possible to identify each line to the original report it was imported from using the raw_report_id.

This ID identifies the report imported from the payment service in which this settlement line was reported. In the settlement tab of the connector’s configuration page the list of imported reports for that payment service is visible. The last 30 days of imported reports are kept available for download. After that, only the report names are visible.

Those reports are still available in the dashboard of the payment service the report was imported from.