List all Settlements
Retrieve a paginated list of settlements, with optional filters for provider, currency, date range, and status.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
If your platform is using a proxy to take SCA-triggering action on behalf of users, you also need to integrate mTLS authentication and use the api-mtls base URL.
Path parameters
Query parameters
The date before which the object was created (based on the object's CreationDate parameter). You can filter on a specific time range by using both the AfterDate and BeforeDate query parameters.
The date after which the object was created (based on the object's CreationDate parameter). You can filter on a specific time range by using both the AfterDate and BeforeDate query parameters.
Allowed values: PENDING_UPLOAD, UPLOADED, CREATED, UNMATCHED, PARTIALLY_MATCHED, PENDING_FUNDS_RECEPTION, INSUFFICIENT_FUNDS, RECONCILED, FAILED, CANCELLED
The status of the Settlement. You can filter on multiple values by separating them with a comma.
The third-party PSP name to filter by.
The three-letter ISO 4217 code of the currency to filter by.
Start value: 1
Default value: 1
Indicates the index of the page for the pagination.
Min. value: 1; max. value: 100
Default value: 10
Indicates the number of items returned for each page of the pagination.
Response
The status of the Settlement:
PENDING_UPLOAD– Settlement object andSettlementFileUploadUrlgenerated.UPLOADED– A file was uploaded.CREATED– The uploaded file was considered valid and reconciliation is in progress. A file is considered valid when it includes all required columns and a properly formatted footer.UNMATCHED– None of the entries in the settlement file match the declared intents.PARTIALLY_MATCHED– Settlement file parsed and some lines matched successfully. If at least one line is incorrectly formatted, the file remains in this status and does not progress further. Cancel the Settlement and re-submit.PENDING_FUNDS_RECEPTION– Settlement file parsed and fully matched with Intents; waiting for funds to arrive on the technical wallet.INSUFFICIENT_FUNDS– Partial amount received:FundsMissingAmountshows the shortfall.RECONCILED– Full settlement amount (ActualSettlementAmount) received on the technical wallet.FAILED– Settlement file rejected due to a technical error (e.g. format, timeout).CANCELLED– Settlement file invalidated due to a reconciliation error. Once canceled, no further actions can be taken on this Settlement.
If status becomes FAILED or CANCELLED, then call POST Create a Settlement and secure URL for file upload to create a new object. If the status becomes UNMATCHED or remains in PARTIALLY_MATCHED unexpectedly, then call PUT Update a Settlement and generate a new upload URL only a new URL is required for the existing SettlementId.
The supported third-party PSP processing the transaction.
Note: The uppercase value is expected. The API returns the sentence-case value.
The total amount declared through Intent API calls, using the following calculation:
(Sum of captured intents) - (Sum of refunded amounts) + (Sum of refund reversed amounts) - (Sum of DISPUTED disputes) + (Sum of DISPUTED_WON disputes)
The total amount due to the platform, to be held in the technical wallet. This amount corresponds to the TotalNetSettlementAmount of the settlement file.
A negative amount results in this parameter being set to zero, indicating no incoming funds to the technical wallet.
The difference between ActualSettlementAmount and the amount received on the technical wallet
The FileName submitted to the POST Create a Settlement and generate upload URL endpoint, with a timestamp of the Settlement creation date automatically appended by Mangopay.