Skip to navigation

List Transactions for a Deposit Preauthorization

Deprecated

Warning – Deprecated feature

This endpoint is deprecated. Use GET List Transactions for an Extended Preauthorization instead.

The Deposit Preauthorization endpoints are scheduled for decommissioning at the end of 2027. Platforms with existing integrations need to move to the new endpoints at their earliest convenience before then.

The Extended Preauthorization feature is a like-for-like renaming of the legacy Deposit Preauthorization – the behavior is otherwise unchanged.

The previous use of the term “deposit” was for convenience only and does not constitute a traditional banking deposit under applicable banking regulations, including the EU Capital Requirements Directive (Directive 2013/36/EU) or the Deposit Guarantee Schemes Directive (Directive 2014/49/EU). Accordingly, these funds are not covered by any statutory deposit protection schemes, and Mangopay does not operate as a licensed banking institution.

This call returns all preauthorized pay-ins, both captures and complements, made against a given deposit preauthorization, whether they were successful or not.

Authentication

AuthorizationBearer

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

ClientIdstringRequired
Platform's API account identifier, associated with the API key.
DepositIdstringRequired
The unique identifier of the deposit preauthorization.

Query parameters

StatusstringOptional

Allowed values: CREATED, SUCCEEDED, FAILED

The status of the transaction. You can filter on multiple values by separating them with a comma.

ResultCodestringOptional
The code indicating the result of the operation. You can filter on multiple values by separating them with a comma.
BeforeDateintegerOptional

The date before which the transaction was created (based on the transaction's CreationDate parameter). You can filter on a specific time range by using both the AfterDate and BeforeDate query parameters.

AfterDateintegerOptional

The date after which the transaction was created (based on the transaction's CreationDate parameter). You can filter on a specific time range by using both the AfterDate and BeforeDate query parameters.

Response

Success
Array (Transactions)list of objectsOptional
The list of transactions created by the platform.