# AffixIO offline resilience pilot checklist

https://www.affix-io.com/offline-payments-verification/
Reviewed 2026-10-26

[ ] Define the claim: what exact action, item, site, amount or entitlement does a successful check authorise?

[ ] Choose the evidence: identify the authoritative source, snapshot age and fields that must be signed together.

[ ] Separate authorities: keep signing keys on the issuer; provision only trusted public keys to independent verifiers.

[ ] Set the stop conditions: expired evidence, stale trust data, unknown keys, unavailable policy, full storage and corrupt state must have explicit handling.

[ ] Protect usage state: test a repeat scan, simultaneous scans, process restart, power interruption and restore from backup.

[ ] Prove the offline path: disconnect networking, including DNS and local services that may secretly depend on the internet. Test after a cold start, not only a warm cache.

[ ] Test recovery: include a revoked key, duplicate upload, provider decline and reconciliation conflict. Keep approvals distinct from settlement.

[ ] Measure and review: capture battery endurance, verification latency on target hardware, storage use, false rejects and unresolved records. Obtain the required security, accessibility, operational and payment-provider reviews.

Not a payment certification or emergency safety plan. Keep human and physical fallback options.