Workflow
Connect. Capture. Preserve. Export.
ProofRail is built so relevant events become one chronological record during normal operations - not a reconstruction project after a dispute notice.
Four stages
A clear operating loop
Each stage has one job. Together they turn fragmented activity into a merchant-owned evidence record.
Connect
Connect the supported checkout, delivery, access, or transaction source.
Capture
Relevant events are recorded as the transaction progresses.
Preserve
Events are linked into a structured, chronological record with source references.
Export
When needed, generate a readable evidence package without rebuilding the case manually.
Animated illustrations on this site respectprefers-reduced-motion. If you enable reduced motion in your system settings, scroll reveals and decorative motion collapse to a static presentation.
The problem shape
Facts often exist. They rarely agree.
Checkout, payment, email, course hosts, and support tools each hold a slice. ProofRail is designed to bring labeled slices into one chronology.
Fictional product data
Payment processor
- Charge confirmed
- Refund path open
Email
- Welcome message sent
- Delivery notice queued
Course host
- Enrollment created
- Lesson 1 opened
Merchant notes
- Order flagged complete
- Support ticket linked
ProofRail chronology
- Order createdCheckout
- Payment confirmedPayment
- Delivery link issuedCourse host
- Buyer authenticatedCourse host
- File accessedCourse host
The facts may exist. The problem is that they are scattered, inconsistently formatted, and often reconstructed only after the dispute begins.
Lifecycle
From purchase to export
A static walkthrough of the intended timeline. Exact connectors and fields depend on what you connect and what is available in beta.
- 01
Purchase
A buyer selects a digital offer. The purchase event becomes the anchor for everything that follows - product, amount, and merchant reference.
- 02
Terms and consent
The terms version shown at checkout is recorded with a timestamp. Later disputes often turn on what the buyer agreed to, not only whether a charge cleared.
- 03
Payment
Payment confirmation from the connected provider is captured with a source label. ProofRail does not process the payment or hold funds; it records that the provider reported a paid state.
- 04
Delivery
Delivery actions - welcome email queued, download link issued, enrollment created - are written into the same chronology as they happen.
- 05
Access and use
Authentication, lesson opens, file downloads, or entitlement activations may be recorded when those systems are connected. Client-observed events stay labeled as such.
- 06
Support
Support messages and refund conversations can be attached when available, so the record includes what was said after the sale - not only the checkout receipt.
- 07
Dispute later
If a dispute arrives weeks later, the merchant starts from a preserved chronology instead of rebuilding from memory across checkout, email, and course tools.
- 08
Export
The merchant generates a readable evidence package from the record. Illustrations on this site show the intended outcome; availability depends on beta progress.