Export checkout - 0xArchive

Use Export Checkout when a Data Catalog selection becomes a quoted file order. The flow should preserve the market, schemas, date range, estimate or quote, payment or credit context, delivery state, and support identifiers so the resulting files are traceable after purchase. Export checkout is a product flow, not a public REST contract. The public OpenAPI bundle does not expose export checkout routes, so programmatic clients should use documented market-data routes or contact Enterprise for scheduled/custom delivery.

Checkout Model

Step	Product behavior	What to preserve
Configure	User chooses market, schema set, and UTC date range	Venue family, symbol, schema keys, start/end dates
Estimate	Product estimates size, rows, and price	Estimate source, selected schemas, coverage window
Credits	Subscriber credits apply before card charge	Credit application and subtotal/total context
Checkout	User authenticates, pays through a trusted Stripe redirect, or uses credits to cover the order	Job ID and checkout result
Delivery	Export appears in the dashboard when ready	Job ID, status, file format, download links, and support context

If checkout requires login, preserve the selected market, schemas, date range, and estimate so the user returns to the export flow or dashboard without rebuilding the cart.

Delivery Expectations

Data Catalog exports are file-style products delivered as Apache Parquet with ZSTD compression. Treat the dashboard job state as the place to check readiness, file format, download links, and support context. The dashboard export list is an authenticated product view and can filter abandoned pending quotes; keep the export detail page as the source for a named job. Dashboard status values include pending, paid, processing, completed, and failed. Common orders may show as ready in 1-2 minutes, but the dashboard state is authoritative. Completed exports remain available from the export detail page for 30 days. Individual download links expire after 7 days and can be regenerated from that page while the order remains available. User-visible labels can differ from raw status values: pending maps to Awaiting Payment, paid maps to Queued, processing maps to Processing, completed maps to Ready to Download, and failed maps to Failed.

Checkout State Checklist

Use this checklist to connect the browser checkout flow, billing state, and export files.

State	Meaning	User-visible next step
`pending`	The order exists but payment or credit resolution has not finished.	Preserve cart state and return path.
`paid`	Payment or credit coverage has cleared and processing can begin.	Show queued state and keep the job ID.
`processing`	Files are being generated.	Poll the dashboard export detail page and keep estimate context.
`completed`	Files are ready.	Show file size, processed time, download links, and days remaining in the 30-day availability window.
`failed`	Export generation did not complete.	Preserve job ID, selected schemas, quote context, and error message for support.

Error And Support Fields

Keep the job ID

Support should be able to locate the export order by job ID.

Keep the selected items

Store market, venue family, schema keys, UTC start, and UTC end for every checkout item.

Keep billing context

Preserve subtotal, credits applied, total, and whether checkout was Stripe-paid, credit-covered, or partially covered by credits before card charge.

Keep data-rights context

Record whether downstream use passes the transformation/source-exposure test and whether any benchmark, index, financial-product, standalone/substitute, raw-redistribution, white-label, or OEM use has written permission before shipping.

When To Use API Instead

Use REST, WebSocket, SDKs, CLI, or MCP when the job is recurring application behavior. Use Data Catalog checkout when the job is a file purchase or bulk historical delivery. Use Enterprise when the buyer needs custom delivery, custom limits, scheduled export operations, security review, or written terms for a named route set. Use Export schemas, Data catalog, Rate limits, and Enterprise delivery together when a browser export becomes a recurring production workflow.

​Checkout Model

​Login And Return Path

​Delivery Expectations

​Checkout State Checklist

​Error And Support Fields

​When To Use API Instead

​Related Pages

Checkout Model

Login And Return Path

Delivery Expectations

Checkout State Checklist

Error And Support Fields

When To Use API Instead

Related Pages