Historical Backfill

Historical backfill supplies past transaction activity for context, investigation, or an archive review. Agree the date range, source identifiers, duplicate handling, and intended result before running it. Past timestamps alone do not select a historical ingestion mode.

HISTORICAL_CONTEXT, OFFLINE_REPLAY, and SUMMARY_BOOTSTRAP are historical ingestion modes. For historical ingestion without explicit archive screening, the canonical ingestion path skips control evaluation, returns CONTEXT_ONLY, and suppresses alerts and automatic case creation. These are not instructions to release or block a payment.

Explicit archive screening runs through the authenticated import workflow using OFFLINE_REPLAY. It evaluates current watchlists and a restricted set of controls, excluding stateful behavioral reconstruction. Findings can return REVIEW and create cases under the organization’s case policy. It does not start payment challenges or block a completed payment.

A historical screening finding reflects the current enabled sources and controls. It does not prove that the same record was listed, or the same policy was active, on the original transaction date.

POST /api/v1/transactions defaults to LIVE. Setting a historical mode on that endpoint does not authorize a backfill: historical modes are restricted to trusted backfill workflows. Use the configured console import or an agreed backfill integration.

Organizations with historical context built but no live cutover can record incoming activity as SUMMARY_BOOTSTRAP with CONTEXT_ONLY rather than live decisions. Confirm the cutover state and test decision handling before routing production payment decisions.

Use CSV and Excel Import for file preparation and mapping. Verify the resulting records and review the actual decision and case counts before expanding the import.