For insurers
Cargo, parcel, and last-mile insurance claims hinge on proof of delivery. SnapAct provides claim-grade signed evidence in one API call.
Verified Delivery Proof API
For every order SnapAct delivers, the platform records a cryptographically signed audit trail — KYC-verified rider, GPS pickup, GPS drop, buyer-confirmed handoff phrase. Insurers, lenders, FMCG distribution auditors, and marketplaces consume these proof records by API.
Why it matters
Cards-on-delivery, BNPL fulfilment, FMCG distribution audits, and B2B supplier-to-retailer movement all rely on someone trusting "yes, it arrived." SnapAct turns that trust into a verifiable record — multi-signal, signed, and queryable.
Cargo, parcel, and last-mile insurance claims hinge on proof of delivery. SnapAct provides claim-grade signed evidence in one API call.
BNPL and inventory-financing decisions need post-disbursement proof the goods reached the borrower. Delivery Proof closes the audit loop.
Distribution audits, secondary-sales verification, and trade-marketing rebate validation — proof your products moved from depot to retailer to consumer.
API surface
Approved integrators get a Trust API key with the delivery_v1_proof scope. Query a specific delivery by escrow ID, or subscribe to a webhook stream for delivery state transitions.
/v1/delivery/{escrow_id}Returns the signed delivery record — rider trust signals, GPS pickup & drop, timing, buyer phrase verification result.
delivery.dispatchedFires when a rider accepts an offer. Carries the rider's anonymized trust signals + estimated delivery window.
delivery.picked_upFires when the rider confirms physical pickup at the partner location. Includes pickup timestamp + GPS.
delivery.confirmedFires the moment the buyer's handoff phrase matches at drop-off. Includes drop GPS, total time, signed proof token.
GET /v1/delivery/snapact_escrow_a3f7b2c1-... Authorization: Bearer $SNAPACT_TRUST_API_KEY Response (200): { "escrow_id": "snapact_escrow_a3f7b2c1-...", "status": "DELIVERY_CONFIRMED", "rider": { "kyc_tier": "gold", "bond_posted": true, "acceptance_rate": 0.94 }, "pickup": { "at": "2026-05-16T14:02:11Z", "lat": 6.4474, "lng": 3.4737 }, "drop": { "at": "2026-05-16T14:14:38Z", "lat": 6.4541, "lng": 3.4061, "phrase_match": true }, "signed_at": "2026-05-16T14:14:39Z", "signature": "v1=4a8f..." }
What's verifiable
Every delivery on SnapAct contributes multiple independent signals to the proof record. Any one signal is forgeable in isolation; the combination is not.
Built for trust
Delivery proof is only valuable to the parties downstream if the chain of custody is honest. Every link is designed for that.
Rider identity, GPS, buyer phrase, and admin audit trail must all agree. No single party can falsify a delivery alone.
State transitions are append-only. Even SnapAct ops cannot modify a confirmed delivery record retroactively — only correct via a new audit entry.
Every API response and webhook carries an HMAC-SHA256 signature over canonical fields. Integrators can re-verify proof records months after receipt.
Early access
Insurer, lender, brand, distributor, or marketplace — request a sandbox key and integrate against the SnapAct delivery audit trail. Pilot terms include 90 days free + named integration support.