For digital merchants
ProofRail Core helps digital merchants create a structured, chronological record of the transaction, agreement, delivery, and access events that may matter later.
No payment required for beta signup. Built for digital merchants.Private beta currently uses sandbox and test data. Fictional data shown in product illustrations.
Fictional product data
Private beta
ProofRail Core is the current product. Status labels describe access honestly.
ProofRail Core is the foundation layer for contemporaneous, source-labeled evidence of agreement, payment context, delivery, and access. Merchants assemble organized evidence bundles from a provider-independent ledger rather than reconstructing a story under a dispute deadline.
Also in private beta
Fraud tools ask whether a transaction should be approved. ProofScore asks whether the transaction record would be understandable and defensible if challenged later.
Evidence readiness only. Not a fraud score and not a prediction of dispute outcomes.
Included in plan / Premium add-on
Explore ProofScoreThe problem
When a dispute lands, merchants reconstruct events from checkout systems, payment processors, email, course platforms, file hosts, support tools, and notes that were never designed to agree.
Fictional product data
Payment processor
Course host
Merchant notes
ProofRail chronology
The facts may exist. The problem is that they are scattered, inconsistently formatted, and often reconstructed only after the dispute begins.
The fix is a record created during normal operations, not assembled under a response deadline.
How it works
A clear workflow designed so relevant events become one chronological record with source references.
Connect the supported checkout, delivery, access, or transaction source.
Relevant events are recorded as the transaction progresses.
Events are linked into a structured, chronological record with source references.
When needed, generate a readable evidence package without rebuilding the case manually.
Illustrative ledger - fictional layers
Product preview
Illustrative private-beta interface views. Labeled as fictional product data.
Fictional product data
Source systems
Illustrative record. Not a live merchant account.
Fictional product data
Product concept - fictional data
Evidence package
PR-00481 - prepared 2026-07-27 09:18:11 UTC
Export timestamp recorded with the package.
Differentiation
Most preparation starts after the dispute notice. ProofRail is designed to begin while the transaction is happening.
ProofRail supports record preparation. It does not promise dispute outcomes or replace processor requirements. Outcomes are decided by payment providers, card networks, and issuers.
Proof record
Categories depend on your stack and what you connect. Availability is labeled honestly.
Order ORD-10482 - Course: Systems Design Intensive
buyer@example.com - customer_cus_demo
Entitlement: course_access_v3
Terms v2026.04 accepted at checkout
Payment confirmed via Stripe - pi_demo_10482
Delivery link issued - expires in 72h
Buyer signed in - session started
Lesson 3 opened - file downloaded
Partial refund requested - status open
Welcome email sent - template welcome_v2
Ticket #4412 - access help - resolved
Sources: Stripe - Course host - Email
Integrity check passed - 11 linked events
Illustrative assembly - fictional data
Evidence package prepared
PR-00481 - 7 sections - Integrity check passed
Use cases
Courses, downloads, memberships, SaaS access, consulting deliverables, and licenses.
When a dispute questions whether a buyer received the course they paid for, a chronological record of enrollment, access, and lesson activity reduces reconstruction.
Designed to capture / may include
File and template sellers need evidence that a delivery link was issued and that access occurred, not only that a charge cleared.
Designed to capture / may include
Subscription and community products benefit from records that show activation, login, content access, and cancellation events over time.
Designed to capture / may include
Software sellers need a processor-independent chronology of entitlement, authentication, and usage milestones when a dispute arrives.
Designed to capture / may include
Agencies and freelancers selling digital or remote work need dated proof of agreement, delivery milestones, and acceptance communications.
Designed to capture / may include
License sellers benefit from records that link purchase, key issuance, activation, and revocation or refund events.
Designed to capture / may include
Integrations
Status labels are current. Available means the Stripe adapter is built. Planned and requested are not live.
Built and sandbox-verified. First live adapter.
Designed for custom checkouts and merchant servers.
Security and privacy
Only claim what is implemented or formally committed. Planned items stay labeled.
Current private-beta access is intended for sandbox, fictional, and non-sensitive test records. Real customer transaction evidence waits until remaining live-data readiness items (including the object-storage write path) are closed.
Hard product rule. Not a payment processor or money transmitter.
Merchants are billed. Buyers are not.
Site and product endpoints are served over HTTPS.
Each evidence item carries its source class and trust level (T1–T6). Client/SDK events stay client-reported and are never shown as provider-verified.
Hash-chained ledger records, signed checkpoints, and offline bundle verification detect alteration. Tamper-evident — not a claim that records cannot be changed.
Sensitive buyer fields use application-layer encryption; the database and object store use platform encryption at rest. Private beta still limits merchants to sandbox and test data until remaining live-data readiness items close.
Sample record
Print it, copy a link, or walk through the tamper-evidence demo. No real personal data.
Pricing
ProofRail has not launched checkout. These are the plans we intend to launch with, priced by included transaction records.
Planned launch pricing
Free
$0/mo
25 included transaction records
Limited proof records
Starter
$19/mo
$190/year
100 included transaction records
$0.08 per additional transaction record
Growth
$49/mo
$490/year
1,000 included transaction records
$0.04 per additional transaction record
Pro
$129/mo
$1,290/year
5,000 included transaction records
$0.02 per additional transaction record
Platform / API
From $299/mo
Contracted volume
Volume pricing
Planned launch pricing, not a live checkout. Annual billing reflects roughly two months free against paying monthly. Numbers may change before launch based on what beta merchants actually need. ProofRail does not charge buyers and does not hold merchant customer funds. A transaction record is a billing unit for planned plans - not a promise about dispute outcomes.
Beta
Leave your email and what you sell. Optional details help us prioritize. We will email you when places open, and nothing else.
FAQ
ProofRail helps digital merchants create a structured, chronological record of the transaction, agreement, delivery, and access events that may matter later. It is designed so the record exists before a payment dispute arrives, rather than being reconstructed under a deadline.
Merchants selling digital goods, services, access, subscriptions, licenses, courses, memberships, downloads, consulting deliverables, and similar non-physical products.
No. ProofRail does not recover funds, influence issuers, or replace payment-network requirements. It supports record preparation so you are not assembling a case from scattered dashboards after the fact.
No. Dispute outcomes are decided by payment providers, card networks, and issuers. ProofRail does not control those parties and does not claim to influence them. Be wary of anyone who promises otherwise.
No. ProofRail sits alongside your checkout. It does not process payments, hold funds, or charge buyers. Stripe is built today; PayPal, Shopify, and Square support are on the roadmap.
Tamper-evident does not mean impossible to change. It means changes can be detected when the record is checked against its preserved state. The sample record page includes a small interactive demonstration of that idea using fictional data.
No. ProofRail never holds merchant customer funds and never charges end buyers. It bills merchants only, when billing launches.
Current private-beta access is intended for sandbox, fictional, and non-sensitive test records while production evidence-storage controls are completed and verified. See the security page for the readiness gate.
The product is in private beta for design partners. Applying puts you on the list and tells us what you sell. We are not announcing a public launch date.
ProofRail is an independent company. Business, security, and beta questions all go to sales@proofrail.site. A public founder identity will be listed on the About page when the owner publishes it.
See the pricing page for planned launch pricing. Nothing is billed while you are on the waitlist, and applying for the beta does not charge you anything.
ProofRail is being built to give digital merchants a durable, independent record of what happened during a transaction. Evidence should be created during normal operations, not assembled in panic after a dispute appears.