Verification infrastructure for digital finance
Proof Rail takes a payout, a licence, a settlement or an on-chain claim, checks it against the exchange, the register or the chain where a connector exists, and issues a signed record anyone can verify in one click. Where nothing can be checked, the record says so.
One API call. One verification link. Every record states what was checked, against which source, and when. "Trust us" becomes "verify it".
The Proof Gap
Your company knows something is true. Your counterparty still has to verify it. Proof Rail 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 Proof Rail account.
Nothing is listed here yet, and we will not pad it. A record appears on this page only once it is live, public and the issuer has explicitly opted it in. We apply our own evidence rules to ourselves before we apply them to you, which is the only reason the numbers on this site mean anything.
Open the public directoryPublic verification
What “verified” actually means
Most proof products have one tier and one word for everything they issue: a self-reported number and an independently checked one look identical. Proof Rail names the standard on the face of every record, so the reader knows which of four they are looking at before they decide what it is worth.
The issuer says it. Proof Rail records who said it, when, and that nothing was checked. Useful, and never dressed up as more.
Confirmed against a named registry, chain, API or signed instruction. The record states the source and the time it was checked.
A reviewer examined the underlying documents against a published policy and recorded the result, the limitations and their reasoning.
Re-checked on a schedule. If the underlying fact changes, the record changes: it can be suspended, superseded or revoked, in public.
A record that can never be withdrawn is worth less, not more. Every Proof Rail record carries a live lifecycle and a signature you can recompute yourself against our published signing key. Read the verification standard →
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 Proof Rail works
Define exactly what the business says is true.
Connect the registry, chain, API, document or declaration.
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.
Turn a payout or phase pass into a certificate the trader can share, checked against the exchange where a connector exists, not just hosted. Signed, revocable, one POST from your payout flow.
Proof Rail Certs for prop firms →A settlement record shows that money moved. It does not show that the program moving it was allowed to. Record the mandate an agent acted under, the principal, the act, the limit, the session, and what was checked about it.
How agent authorization works →A guest is asked to pay an account. Is it really yours? Bind a listing to your licence, your website and your payee, so a customer can check the IBAN, wallet or link before they transfer.
Try the public payee check →Proof Rail can support any business where the same claim must repeatedly be proven. Explore all products →
Now issuing on Proof Rail
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 prop firms and brokers issuing payout certificates.
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.
Developer starts without us. Create an organization and get a sandbox key immediately, no card, no call, no approval queue. Sandbox records are never public and never billable. Live issuance and paid subscriptions are activated once you have seen the output and decided it is worth it.
Basic issuance records a self-reported 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.