Operational Evidence Collection in Crypto Payment Reconciliation

Reconciliation disputes are won or lost on evidence quality, not on how quickly someone can open a block explorer. When commerce, provider, and finance planes disagree, teams need a shared evidence package that explains what each system knew, when it knew it, and who approved transitions.

Minimum evidence package

• payment_id and merchant reference used across planes.
• Provider lifecycle timeline from verified events (not handler logs alone).
• Commerce order state at detection, confirmation, and fulfillment gates.
• Finance posting records with approval metadata.
• Matcher outcome: auto-matched, exception class, or manual override code.

Collection discipline during operations

Collect evidence at exception creation—not only at month end. Exception queues should store structured fields finance can export. Support narratives belong in supplemental notes, not as the sole system of record.

Provider plane specifics

Store verification outcomes (pass/fail) with correlation ids. For duplicates, retain idempotency keys that explain why later events no-oped. For outages, retain gap windows and backfill batches used after recovery.

Kobbopay emphasizes signed webhooks and explicit lifecycle semantics as inputs—your evidence model should show how those signals mapped to internal states under your policy.