Skip to main content
πŸ” Digital Notary β€’ Independent Records β€’ Court-Admissible

Independent Records for Fair Business

Turn every transaction, content delivery, and operational event into independent proof that protects everyone.

Digital receipts for payments, content, and operations. Clear records prevent confusion, prove authenticity, automate complianceβ€”all from one platform.

30-40%
Dispute reduction
<15min
To first test receipt
3
Compliance frameworks

All Core Plans Include the Tri-Pillar System

This complete system is what makes CertNode unique

πŸ’°
Transaction Records
Payment proof
πŸ“„
Content Records
Delivery proof
πŸ›‘οΈ
Operations Records
Activity proof
πŸ”—
Receipt Graph
Connects everything

Why this matters: Other platforms only do one thing (just payments, just content, just logs). CertNode connects all three domains with the Receipt Graph, creating complete evidence chains that resolve disputes and pass audits.

Business Without Cryptographically-Verified Records Creates Confusion

Every day, businesses lose money because they can't prove what happened.

πŸ’Έ

Chargebacks Cost 1-3% of Revenue

"I never ordered this" claims drain profits. Without independent proof, confusion leads to lost revenue.

Example: $1M in sales = $10K-30K lost to chargebacks

Source: Chargebacks911 2024 Report

βš–οΈ

Copyright Defense Averages $50K-$150K

"You stole my content" or "I never received it" lawsuits are expensive to defend. Complex cases can exceed $500K.

Real case: Hermès v. Rothschild (MetaBirkin NFT) = $133K judgment

Source: Copyright Alliance 2023 Survey

πŸ“‹

SOC 2 Takes 6-12 Months + $50K-$200K

First-time certification requires 500-2000 hours gathering evidence. CertNode receipts reduce prep time by 60-80%.

Breakdown: $50K (startups) to $200K (enterprises with 50+ controls)

Source: Vanta 2024 Compliance Report

Three Products. One Platform. Complete Protection.

Every CertNode plan includes all three receipt products.
Pay once. Get everything.

πŸ’³

Transaction Receipts

What is it? Independent proof of every payment, refund, and financial transaction.

Problem it solves:

Customer: "I never ordered this $500 product"
Bank: Chargeback filed
You: Unclear what happened

With CertNode:

Submit independent receipt showing:
β€’ Order timestamp
β€’ Payment confirmation
β€’ Customer acknowledgment
β€’ Cryptographic signature
Result: Clear records resolve confusion

  • βœ“Chargeback defense evidence
  • βœ“Secure payment records
  • βœ“Instant verification via JWKS
  • βœ“Audit-ready transaction logs
πŸ“„

Content Delivery Verification

What is it? Proof of content delivery, access, and timestamps.

Problem it solves:

Customer: "I paid but never got my course"
Platform: Needs proof of delivery
You: Can't prove it was delivered

With CertNode:

Submit content receipt showing:
β€’ Content uploaded timestamp
β€’ Customer download timestamp
β€’ IP address & device
β€’ Content hash (proves exact file)
Result: Clear records resolve confusion

  • βœ“C2PA standard compatible (pending certification)
  • βœ“Ownership & licensing proof
  • βœ“Delivery confirmation
  • βœ“Proves it wasn't altered
πŸ›‘οΈ

Operations Trust

What is it? Secure records of security incidents, policy changes, and compliance events.

Problem it solves:

Auditor: "Prove you had access controls in Jan 2024"
You: Scramble to find logs
Logs: Can be edited (not trusted)

With CertNode:

Show operations receipt with:
β€’ Policy implementation timestamp
β€’ Access control logs
β€’ Change history
β€’ Cryptographic signature (can't be edited)
Result: Generate audit evidence in 15 minutes

  • βœ“Security incident documentation
  • βœ“Policy version tracking
  • βœ“Compliance audit trails
  • βœ“SLA & uptime proof

All Three Products Included in Every Plan

No add-ons. No hidden fees. One subscription gives you transaction receipts, content certification, and operations trust.

Plans start at $29/month for 500 receipts across all three products.

Independent Records Protect Everyone

CertNode acts as a digital notaryβ€”an independent third party creating trusted records that both sides can verify.

πŸͺ

For Businesses

Clear records resolve confusion: "Customer logged in 47 times, completed 8 lessons, downloaded materials."

Result: Prevents disputes, passes audits, proves compliance

πŸ‘€

For Customers

You can verify your own records anytime at certnode.io/verify. Independent proof you can trust.

Result: Know what you paid for, when you got it, who delivered it

βš–οΈ

For Everyone

Fair record-keeping builds trust. Honest customers feel protected. Clear proof prevents disputes.

Result: Less confusion, fewer disputes, faster resolutions

Connected by Receipt Graph

Link receipts across all three products to create complete evidence chains

Example: E-Commerce Order

1. Transaction Receipt

Customer pays $500

  • β€’ Payment timestamp
  • β€’ Amount: $500
  • β€’ Customer email
  • β€’ Order ID
2. Content Receipt

Product delivered

  • β€’ Delivery photo uploaded
  • β€’ Shipping label
  • β€’ Tracking number
  • β€’ Parent: Transaction receipt
3. Operations Receipt

Customer confirms

  • β€’ Confirmation timestamp
  • β€’ Customer signature
  • β€’ IP address
  • β€’ Parent: Content receipt

Result: Complete evidence chain from payment β†’ delivery β†’ confirmation.
When customer has questions: Submit all 3 receipts as proof. Clear records resolve confusion.

Without Receipt Graph

  • Γ—Receipts scattered across systems
  • Γ—No connection between payment & delivery
  • Γ—Manual evidence gathering takes hours
  • Γ—Incomplete stories lead to confusion

With Receipt Graph

  • βœ“All receipts in one platform
  • βœ“Automatic linking (parent/child)
  • βœ“One-click evidence export
  • βœ“Complete story resolves confusion

Why RFC 3161 Timestamps Matter

Not all timestamps are created equal. Here's why RFC 3161 matters for legal defensibility.

Regular Timestamp (not RFC 3161)

What it is:

Database timestamp, server time, or `new Date()` in your code. Created by your own system.

Problems:

  • Γ—Easily manipulated: You control the server clock. Anyone can question: "Did you just backdate this?"
  • Γ—Not independently verifiable: No third party can confirm the timestamp's accuracy
  • Γ—Court challenges: Opposing counsel will argue "this could have been created yesterday"
  • Γ—Burden of proof: You need expert testimony to defend your own timestamp

Good enough for: Internal logs, analytics, development

RFC 3161 Timestamp (CertNode)

What it is:

Cryptographic timestamp from an independent third-party authority (FreeTSA, DigiStamp). Not controlled by you.

Benefits:

  • βœ“Tamper-proof: Uses cryptographic hash + timestamp authority signature. Cannot be backdated.
  • βœ“Independently verifiable: Anyone can verify via timestamp authority's public key (JWKS)
  • βœ“Court-admissible: Meets Federal Rules of Evidence 902(13-14) for self-authenticating documents
  • βœ“Legal precedent: Accepted in federal courts (U.S. v. Vayner 2014, Lorraine v. Markel 2007)

Required for: Lawsuits, compliance audits, disputes, legal evidence

How RFC 3161 Works (Technical Explanation)

1

Your Action

Customer makes a purchase. CertNode creates receipt with transaction data.

2

Hash Created

CertNode creates SHA-256 hash of the receipt data (tamper-proof fingerprint).

3

TSA Signature

Timestamp authority signs hash with current time + their private key (independent proof).

4

Public Verification

Anyone can verify using TSA's public key. Proves: "This data existed at this time."

Why This Matters in Court:

Without RFC 3161:

"Your Honor, the defendant's own system created this timestamp. They could have backdated it to fabricate evidence. We request this be excluded."

With RFC 3161:

"Your Honor, this timestamp was created by FreeTSA, an independent third-party authority. It's cryptographically verifiable under RFC 3161 standards and meets FRE 902(13-14)."

Real-World Impact

❌ Without RFC 3161

Customer dispute: "I never received the product. Your email 'proof' could have been created today."

Result: You lose the dispute. Chargeback + $50 fee + product lost.

βœ… With RFC 3161

Customer dispute: "I never received the product." You submit: Delivery receipt with RFC 3161 timestamp from March 15.

Result: Dispute resolved in your favor. Independent timestamp proves delivery date.

πŸ“Š Cost Comparison

RFC 3161 cost: $0.002-0.005 per receipt

Dispute cost without it: $50-$500 per dispute

ROI: 1 prevented dispute = 100-100,000 timestamps paid for

Sources & Further Reading:

Legal Standards:

  • β€’ Federal Rules of Evidence 902(13-14): Self-Authenticating Documents
  • β€’ U.S. v. Vayner, 769 F.3d 125 (2014): Digital timestamps admissible
  • β€’ Lorraine v. Markel, 241 F.R.D. 534 (2007): ESI authentication standards

Technical Standards:

  • β€’ RFC 3161: Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)
  • β€’ RFC 7518: JSON Web Algorithms (JWA) - ES256 signatures
  • β€’ RFC 7517: JSON Web Key (JWK) - Public key verification

Simple, Transparent Pricing

All three products included in every tier. No hidden fees.

Starter

$29/mo

500 receipts/month

Perfect for:

Small e-commerce ($50K-$500K revenue)

  • β€’ All 3 receipt types
  • β€’ Receipt Graph
  • β€’ Evidence export (PDF)
  • β€’ Email support
Get Started β†’
MOST POPULAR

Professional

$199/mo

7,500 receipts/month

Perfect for:

Established businesses ($500K-$5M revenue)

  • β€’ Everything in Starter
  • β€’ Batch API operations
  • β€’ Webhooks
  • β€’ Priority support (24hr)
Get Started β†’

Business

$999/mo

50,000 receipts/month

Perfect for:

Large e-commerce ($5M-$50M revenue)

  • β€’ Multi-tenant
  • β€’ SSO/SAML
  • β€’ Support (8hr SLA)
Get Started β†’

Note: All plans include transaction receipts, content certification, and operations trust.

View full pricing details β†’

Ready for Cryptographically-Verified Records?

Join forward-thinking businesses building with cryptographically-verified records to prevent confusion, prove authenticity, and automate compliance.