An open format.
JSON in the RFC 8785 canonical form, signed with Ed25519. lyntway-verify accepts the same receipt as a COSE_Sign1 envelope (RFC 9052), and the format follows the SCITT architecture.
Portability
Your evidence is yours. It verifies anywhere.
A Lyntway receipt is a signed document in an open format. It checks against a published key, with free and open-source tools, on any machine, with no account — this year, and long after the subscription that produced it.
Why it holds up on its own
Four things a receipt needs, and none of them is an account.
A published key.
/.well-known/lyntway-keys.json, with the list of keys withdrawn and when. Save it beside your receipts; fetch it again when you check them later.
A verifier anyone can read.
lyntway-verify, Apache-2.0, with no third-party dependencies. Or none of our tools at all: the whole check is about thirty lines against any standard crypto library, and the docs give every step.
A log nobody can quietly edit.
Hosted receipts are appended to a public, append-only transparency log (RFC 9162). An inclusion proof shows a receipt is in it; a consistency proof shows nothing was removed since you last looked.
Export everything
What you can take with you today.
| What | How it leaves | How it is checked |
|---|---|---|
| Every receipt, as it is issued | On the response to your application, or forwarded to a destination you choose: your own endpoint, Splunk or Datadog. | Signature against the published key, offline. |
| A compliance pack for any period | From the console, on demand or on a weekly or monthly schedule, or from the API. | Signed; lyntway-verify reads it directly. |
| The evidence bundle | One archive: the pack, a snapshot of the key file, a README that states every limit, and SHA256SUMS. | Entirely offline, with the key file inside it. |
| Content you chose to keep | An auditor export, decrypted in your browser if it is sealed, carrying the hash of each body. | Each hash matches the digest its signed receipt names. |
| Usage and traffic | CSV from any table in the console, per client, and one roll-up for a partner. | Plain data, and says so. |
| Evidence in Vanta or Comp AI | Pushed through their APIs with the instructions to check it. Requires your account with them. | Points back to the bundle and the offline check. |
Not built yet: one archive holding all of the above in a single download. Today it is the exports in this table.
The promise
Leaving costs you nothing you need to prove what happened.
- Receipts reach you as they are made, so there is no stock of your evidence that only we hold. Choose where they go on day one: without a destination, nobody keeps them.
- Packs and bundles verify with no subscription and no account, for as long as you keep them.
- Verification is free for anyone, on any plan or none, and always will be.
- When the only member deletes an account, its token mappings, stored content, traffic history and stored provider keys go with it, and its keys are revoked.
What stays: the transparency log is append-only by design, so the digests it holds remain — digests, never content. That is what lets a receipt you kept be checked after you have gone.
Check one now, on any machine you choose.
Make a receipt on the home page, copy its link, and open it in a private window or on your phone.