A tracking number for digital goods
Physical sellers prove delivery with a carrier scan. Digital sellers have nothing. CertNode Delivery Receipts is the equivalent: a sealed, timestamped, independently verifiable record that your download, course, license, or subscription was delivered and accessed — that you can send the buyer, and that’s yours to keep.
Works on any platform via API — Stripe, Shopify, Gumroad, your own store.
When a customer says “I never got it”
For a digital good there’s no shipment, no carrier scan, no signature. So when a buyer charges back as “product not received” — the most common digital dispute — the merchant usually has nothing to show, and loses. The strongest digital category, friendly fraud (people who did receive it and dispute anyway), is exactly where a contemporaneous, non-backdatable delivery record changes the conversation.
Three steps
Capture
One API call when you deliver or grant access — a download, a course login, a license activation. CertNode seals it (RFC 3161 + a public transparency log) at the moment it happens, so the record can’t be backdated.
POST https://certnode.io/api/v1/access
Authorization: Bearer cn_live_…
{ "eventType": "download", "resourceId": "ebook-42",
"externalOrderId": "order-1001" }Get the receipt
Fetch a clean, shareable receipt page for the order — a verifiable record you can send the buyer or drop into your order-confirmation email.
GET https://certnode.io/api/v1/delivery-receipt?externalOrderId=order-1001
→ { "receiptUrl": "https://certnode.io/r/…" }Show the badge
Add the “Delivery recorded by CertNode” badge to your checkout, download page, or order email. Buyers who see their access is on record are less likely to dispute.
<img src="https://certnode.io/badge/delivery-recorded.svg"
alt="Delivery recorded by CertNode" height="40">What a receipt shows
- ✓The order it belongs to, and when it was purchased.
- ✓That you marked it delivered — and exactly when.
- ✓Access events you (or your platform) recorded — and when.
- ✓That each event was independently timestamped and committed to a public, append-only log at the time it happened.
What it doesn’t claim
- —It does not assert the identity of the person behind an access beyond a supplied one-way hash.
- —It does not claim the buyer “used” the good — “accessed” means access was recorded by the named source.
- —It is not a statement about any dispute outcome, and it is never “court-admissible.”
Real proof, not a screenshot
Every receipt is an ES256-signed cn.receipt.v1, content-hashed (RFC 8785), timestamped against an RFC 3161 authority, anchored to Bitcoin via OpenTimestamps, and written to an append-only transparency log — then independently verifiable by anyone at certnode.io/verify. The records are self-authenticating under FRE 902(13)/(14) and portable: you own them, and they work across processors and in arbitration, not just on one platform.
Built for digital sellers
Course & coaching
Prove enrollment, access, and completion — high-ticket disputes turn on it.
Downloads & files
A verifiable record that the file was delivered and fetched.
Licenses & keys
Seal issuance and activation, hashed — never the raw key.
Memberships & SaaS
Prove access during the billing period.
Marketplaces
A neutral delivery record per order for both sides.
Compliance & audit
A durable, self-authenticating delivery trail you own.
Free to start
Delivery Receipts is in beta and free to use while we build it out. Get an API key, capture your first delivery, and see the sealed receipt in about a minute.