Verification infrastructure for digital finance
Rail Proof turns company, regulatory, payment and on-chain claims into permanent records anyone can independently verify.
One API call. One verification link. No screenshots. No email chains. No repeated diligence.
The Proof Gap
Your company knows something is true. Your counterparty still has to verify it. Rail Proof closes the distance between the claim and the evidence.
The product is the proof
Every live record exposes its status, evidence standard, issuer, timestamp and lifecycle—without requiring a Rail Proof account.
No opted-in production records are currently listed publicly.
Open the public directoryPublic verification
Start with the difficult claim
Do not book a demo or integrate an API. Give us one claim you repeatedly have to explain, document or defend.
Product-led onboarding
We first confirm that the claim fits a supported standard evidence path. Third-party data fees and complex human review are scoped before any work begins.
Create my first record ↗ Automate it when you are ready.How Rail Proof works
Define exactly what the business says is true.
Connect the registry, chain, API, document or attestation.
Apply a named methodology and record what was checked.
Issue the signed link, QR code and visible lifecycle status.
Before and after
Built first for digital finance
Lead with the claim your counterparties already ask you to prove.
Prove licence, entity, payment and settlement claims.
Prove transactions and stablecoin settlements.
Prove regulatory, wallet and on-chain claims.
Prove payouts, settlements and performance-related claims.
Explore Verified Performance →Rail Proof can support any business where the same claim must repeatedly be proven. Explore all products →
Now issuing on Rail Proof
Founding use case · opted-in public verification
See the actual records, current status and verification methodology. No invented customer count, volume or testimonial.
Open the Alpine Gate proof wallAutomate it when ready
Start manually with one claim. When the output is useful, issue records from your own product with idempotency, signatures, webhooks and lifecycle controls.
POST /api/v1/records
Authorization: Bearer ••••••
Idempotency-Key: settlement-1842
{
"subject": "Settlement 1842",
"claim_type": "settlement_finality",
"visibility": "public"
}Before choosing a plan
Experience the output first. Automate it when you are ready.
Create my first record →Subscription + usage
Subscriptions begin when you want API issuance, lifecycle controls and repeatable workflows—not before you see the product.
For pilots and product teams proving the first workflow.
For live platforms issuing proof every day.
For regulated and high-volume verification programmes.
For custom assurance, monitoring and commercial terms.
Basic issuance records a participant-attested claim. Source verification, evidence review and continuous monitoring are scoped separately because the assurance work differs.
Founding 10: launch fees are waived for the first ten qualifying customers who provide structured product feedback. Publicity always requires separate approval.
If you claim it, prove it.
Give them something they can verify.