Verify a receipt
BotFare signs a statement when an agent pays, when the site delivers the page, and when a fare is refunded. Anyone can check them here, in the browser, with BotFare's public key.
Check a receipt
Paste a receipt number such as rcpt_9d2e41b7c03a5f18, or a receipt link.
This is a real receipt from Saffron & Salt, our demo recipe blog. Press Verify to check it.
How this works
- Signed once, when it happens
- BotFare signs a payment statement when it settles, a delivery statement when the site reports what it sent, and a refund statement when it refunds. It never signs the same event twice.
- Ed25519 JWS
- Each statement is a compact JWS (RFC 7515) signed with EdDSA over Ed25519 (RFC 8037), typ botfare-receipt+jwt. Its kid header names the signing key.
- Public keys
- The public keys are a JWKS (RFC 7517) at /.well-known/botfare-receipt-keys.json. Private keys never leave the server. This page fetches the keys and checks every signature in your browser.
- Content digests
- A delivery statement carries the RFC 9530 SHA-256 digest of the exact body the site sent. Hash your copy and compare. One changed byte gives a different digest.
- Limits
- A valid signature proves BotFare issued the statement. It does not prove that BotFare never deleted a receipt or that the content was accurate. A tamper-evident log of every receipt is not built yet.
To check offline, call verifyStatement() from @botfare/contracts/receipts with a saved copy of the keys. It runs in Node and in the browser. Signed receipts in the README (opens in a new tab)