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 transactions	90 days	All canceled_* statuses (see below)
Card attempts	90 days	Purged together with their parent transaction
Refunds on canceled transactions	90 days	Purged together with their parent transaction
Payment Intents	90 days
Successful transactions	Indefinitely	Never purged from the live database

Canceled transaction statuses

The following statuses are subject to the 90-day retention window:

• canceled
• canceled_failure
• canceled_rejected
• canceled_timeout
• canceled_timeout_e2e
• canceled_timeout_refund_e2e

Impact on API responses

Fetching a canceled transaction, preflight, or webhook delivery record via the API after its retention window will return a 404 Not Found. Successful transactions are never affected.

If you need access to historical data beyond the retention window, contact support.