# Billing Proof — sample verification report

Reference demonstration, 8 September 2026. This is our application, not a customer audit.

Agreed rule: a paid invoice grants 100 credits once. Delivering the identical event again must not grant additional credits.

| Observation | Expected credits | Observed credits |
|---|---:|---:|
| Before delivery | 100 | 100 |
| First delivery | 200 | 200 |
| Identical-event replay | 200 | 200 |

Result: PASS for this sequence in the local reference application.

A Stripe-originated sandbox invoice.paid event reached the local receiver through Stripe CLI. The receiver accepted its signature and persisted the grant. Replaying the same event left the stored balance unchanged and recorded the duplicate as ignored.

The sandbox invoice was marked paid outside Stripe. No card was charged. This check does not establish Checkout behavior, subscription lifecycle coverage, concurrent delivery safety, another application's behavior or production readiness.

The demonstration uncovered an invoice payload compatibility issue before the successful run: the receiver needed to inspect status=paid rather than rely on the older paid boolean. The receiver and its regression fixture were corrected.

Customer pilots report expected versus observed state and provide reproduction steps and a regression check for the agreed supported integration. Compatibility and scope are confirmed before payment.

Billing Proof — by Bodenhamer & Co. Contact: hello@bodenhamer.co