# Proof behind every booking

*Product · Booking receipts*

[Request early access](https://notaray.ca/design-partners)

A booking receipt is the record Notaray will leave for every finished booking attempt: what was asked, what was checked, what the calendar returned and what the outcome was. So when someone asks “did that really get booked?”, the answer is on the receipt, not in someone’s memory.

## Rules behind every receipt

- Notaray is built so that every finished booking attempt leaves a receipt.
- Notaray is built to confirm a booking after the calendar shows it, not before.
- Notaray is built so that a retried request returns the original outcome instead of booking twice.

## Everything on the record

- The request as it was understood
- The consent and business rules that applied
- The calendar that was checked and what it showed
- The write that was attempted and what the calendar returned
- The read-back and whether it matched
- Timestamps with the time zone
- Any human step that followed

*Illustrative workflow*

## A record to check, not a celebration

A receipt is an audit record. It will say Confirmed when the calendar returned an identifier and the read-back matched, and not before. A reply from a server isn’t enough.

If verification isn’t available, the receipt will say so plainly instead of faking success.

## What would you want to check?

Design partners tell us which facts belong on a receipt before they’d rely on it. Spots are limited.

[Request early access](https://notaray.ca/design-partners)