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.
All Core Plans Include the Tri-Pillar System
This complete system is what makes CertNode unique
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
Customer pays $500
- β’ Payment timestamp
- β’ Amount: $500
- β’ Customer email
- β’ Order ID
Product delivered
- β’ Delivery photo uploaded
- β’ Shipping label
- β’ Tracking number
- β’ Parent: Transaction 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)
Your Action
Customer makes a purchase. CertNode creates receipt with transaction data.
Hash Created
CertNode creates SHA-256 hash of the receipt data (tamper-proof fingerprint).
TSA Signature
Timestamp authority signs hash with current time + their private key (independent proof).
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
500 receipts/month
Perfect for:
Small e-commerce ($50K-$500K revenue)
- β’ All 3 receipt types
- β’ Receipt Graph
- β’ Evidence export (PDF)
- β’ Email support
Professional
7,500 receipts/month
Perfect for:
Established businesses ($500K-$5M revenue)
- β’ Everything in Starter
- β’ Batch API operations
- β’ Webhooks
- β’ Priority support (24hr)
Business
50,000 receipts/month
Perfect for:
Large e-commerce ($5M-$50M revenue)
- β’ Multi-tenant
- β’ SSO/SAML
- β’ Support (8hr SLA)
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.