INTEGRATION

Getting Started

REPORTING

Report: Settlement Details

FILE SUBSCRIPTIONS

Settlement Details Report

Link icon

Description

The Settlement Details report provides a complete, transaction-level breakdown of all items included in your card network settlements. These includes captures, disputes, card network billing, and adjustments. Each transaction has the information needed to reconcile including the settlement amounts, the chargeKey and a networkFundsTransferKey. This data is specifically designed to support acquirers with reconciliation of settlement activity.

Link icon

Audience

  • Product / Engineering

  • Finance

Link icon

Purpose

The Settlement Details report serves several key purposes for financial operations:

  • Reconcile the transaction lifecycle by connecting settlement activity with authorizations sent for capture.

  • Reconcile incoming bank transfers with each underlying transaction including captures, disputes, fees and adjustments.

  • Verify deducted card network fees with the corresponding scheme fee invoices.

Link icon

Functionality

Create reports

Via API

Generate via portal

Access reports

Via API

Download via portal

Push to SFTP or e-mail

Schedule reports

Hourly

Daily

Query patterns

The report is generated by specifying a date range using the createdFrom and createdTo parameters. Also, reports can be generated using the networkFundsTransferKey

Data types

NDJSON

CSV

Data sources

Card network reporting

  1. API Reference: Create Settlement Details Report: Documentation for generating a new Settlement Details report via the API.

  2. API Reference: Get Report File: Documentation for downloading a report file that has already been generated.

  3. API Reference: Schedule Report: Documentation for creating a recurring report schedule.

Link icon

Considerations

  • detailType: The report includes various detailType that impact the settlement activity of the acquirer.

    • capture: initial charges performed and cleared on the Silverflow platform (purchase, refund, payout, funding).

    • dispute: chargebacks and all consecutive dispute stages with a financial impact.

    • card_network_billing: scheme fees that are deducted from settlement by the card networks. These amounts can be reconciled back to the invoices sent by the networks to the acquirer.

    • adjustment: any other adjustments that the card networks apply on the daily settlement position of the acquirer. These can relate to rounding precision, double bookings, and other corrections on booking errors.

  • How to reconcile with your bank transfers:

    • Silverflow attaches a networkFundsTransferKey to each bank transfer to the acquirer (network, settlement service, settlement day). Clients can find the networkFundsTransferKey corresponding to the bank transfer by creating Network Funds Transfers reports each day. The reported amount in the Network Funds Transfers report matches the total amount received on your bank account.

    • The Settlement Details report provides a transaction-level breakdown of that bank transfer. Each settlementDetail entry has a networkFundsTransferKey for the bank transfer that it is included in. Using that key, clients can tie individual transactions to an incoming bank transfer. The netSettlementAmount for each entry represents the ultimate settlement amount included in the bank transfer.

  • How to reconcile with your authorizations:

    • Silverflow attaches a chargeKey and transactionReference to each settlementDetail. This chargeKey is returned to the Agent when creating a charge on our platform.

    • Matching both keys allows clients to perform transaction lifecycle reconciliation.

Link icon

Content

You will be able to find a detailed schema of available fields on the API Reference. Please navigate to:

  • Response: 307 Report File

  • Response schema: application/x-ndjson

  • One Of: Settlement Details

The report schema's are further separated by other types, such as the card network and transaction category. This helps users understand what fields are available, required or optional for each type.