Ask three separate questions
Identity asks who is acting. Intent describes what a person wants. Authorization defines the permitted action and its constraints. A valid connection or authenticated tool call does not automatically authorize a purchase. Your integration needs a clear handoff from human intent to deterministic validation.
Make the scope inspectable
A useful authorization record should be bounded to the relevant transaction or permitted action. In its documented scope, AP2 uses checkout/payment mandates and receipts. Do not infer that a generic agent token carries the same meaning. Read the exact protocol version and provider responsibilities before implementing any verifier.
Preserve evidence and handle failure
Define what happens when a constraint is no longer satisfied, a request is repeated or a user revokes access. Keep the data required by your approved provider workflow, minimize unrelated information and ensure the merchant can explain the decision. The L0 scanner cannot verify these private controls.