Data Retention
Orchestrapay automatically purges and archives data on a daily basis to keep the platform performant. This page describes what is retained, for how long, and what happens to it afterwards.
Retention periods
| Resource | Retention in live database | Notes |
|---|---|---|
| Webhooks | 30 days | All webhook delivery records, including retries |
| Canceled payments | 90 days | All canceled_* statuses (see below) |
| Card attempts | 90 days | Purged together with their parent payment |
| Refunds on canceled payments | 90 days | Purged together with their parent payment |
| Payment Intents | 90 days | |
| Successful payments | Indefinitely | Never purged from the live database |
Canceled payment statuses
The following statuses are subject to the 90-day retention window:
canceledcanceled_failurecanceled_rejectedcanceled_timeoutcanceled_timeout_e2ecanceled_timeout_refund_e2e
Impact on API responses
Fetching a canceled payment or webhook delivery record via the API after its retention window will return a 404 Not Found. Successful payments are never affected.
If you need access to historical data beyond the retention window, contact support.