Data availability periods

​

Transactions

The Mangopay API retains live transaction data for 13 months. This means that any transaction object can be retrieved via the API for 13 months after its CreationDate.

This limitation applies: 

• To transactions of every Type (PAYIN, TRANSFER, CONVERSION, PAYOUT) and Nature (REGULAR, REPUDIATION, REFUND, SETTLEMENT) 
• On all relevant GET endpoints, both to retrieve by Object ID (e.g. GET View a Payout) and to list transactions (e.g. GET List Transactions for a User)
• In both the Production and Sandbox environments

Past the 13-month period, transaction data is archived. Once archived:

• A GET call on the archived Transaction ID (e.g. GET View a PayIn, GET View a Refund, etc.) returns 404 Not Found
• A GET call to list transactions call (e.g. for a User) doesn’t return the archived transaction

For example, here is a 404 response on GET View a PayIn:

{
    "Message": "The ressource does not exist",
    "Type": "ressource_not_found",
    "Id": "5ca01f7f-99f4-4ba4-82a1-3af3b702f727#1718224387",
    "Date": 1718224388,
    "errors": {
        "RessourceNotFound": "Cannot found the ressource PayIn with the id=158250465 "
    }
}

This limitation does not apply to resources that enable a user to make payments, such as Cards, Recurring PayIn Registrations, Bank Accounts, and Mandates.

However, Preauthorizations and Deposit Preauthorizations, given their limited validity and use, are also limited to 13 months.

Limiting the duration of data retention is essential to maintain performance. The retention period is sufficient for operational usage (such as refunds, fraud investigations, and user experience) and most auditing purposes.

All data is archived securely and provisions are in place to ensure we address any legal or business requirements that may arise.

​

Reports

The POST Create a Transactions Report endpoint can be used to create a report containing transactions whose CreationDate is up to 36 months in the past. To do so, use the AfterDate child parameter of the Filters parameter.

For more information about generating reports, see the Reports article.

​

Events

GET List all Events returns events up to 45 days after the Date they occur.

​

API responses

If an API call contains an idempotency key, it can be retrieved up to 24 hours after the Date it was sent, using the GET View an API Response endpoint.