Example Purchase Authorization Record (PAR)

A formal record of purchase approval created before payment.

Purchase Authorization Record (PAR)

This record documents purchase approval on the buyer’s device before payment.

Created (UTC)

2026-01-14T22:58:41Z

PAR ID

par_3f2c9e1a7b0d4a8b

Merchant order ID	`ORDER-1008`
Amount + currency	117.00 USD
Payment provider reference	`pp_ref_8e12…4bd`
Transaction window	Authorization valid for 10 minutes

Authorization method	Passkey confirmation on buyer’s device
Buyer device confirmation	Device-bound confirmation (no personal data)
Buyer action	Approved purchase
Authorization timestamp (UTC)	`2026-01-14T22:57:09Z`

Record hash	`15c2cb0f4a35a31706671c6d56bbbfbe5fce8d0d84166f605ef810b60e6181e`
Signature	`ed25519:5f77b8d6a9c9c4f2c1a0b8d9e3b2c4d1a0f9c8e7d6b5a4c3b2a1908f7e6d5c4b`
Verification instructions	Verify by matching hash + signature to this record.

Scope statement	This record proves purchase approval before payment.
Non-scope statement	It does not prove delivery, condition, or satisfaction.

Coming soon

Record header

PAR ID — Exists so a specific record can be referenced unambiguously.
Status — Exists to state the outcome of the authorization event.
Created (UTC) — Exists to show when the record was issued by the system.
Merchant — Exists to identify which seller the authorization relates to.
Buyer reference — Exists to link repeated authorizations without storing personal identity.

Transaction link

Merchant order ID — Exists to tie the record to the seller’s own order system.
Amount + currency — Exists to describe what value the buyer approved.
Payment provider reference — Exists to connect this record to the external payment system.
Transaction window — Exists to define how long the authorization is valid for this purchase attempt.

Authorization event

Authorization method — Exists to note which confirmation method was used at the time of approval.
Buyer device confirmation — Exists to indicate the approval occurred on the approving device, without exposing personal data.
Buyer action — Exists to state the specific action the buyer took.
Authorization timestamp (UTC) — Exists to show when the buyer approval occurred.

Integrity / verification

Record hash — Exists to detect changes to the record content.
Signature — Exists to show the record was produced by the system and remains unchanged.
Verification instructions — Exists to state, in one line, how this record can be checked against its integrity fields.

Notes / scope

Scope statement — Exists to define what this record is intended to demonstrate.
Non-scope statement — Exists to state what the record does not claim to cover.