Sandbox / Guided walkthrough

A scoped PDPP grant, end to end, in your browser.

Click through a fictional tax-prep app asking a fictional owner for three pay statements. Approve the grant, see only the granted fields come back, then revoke and watch the next read get refused. The transcript on the right shows the API-shaped JSON for each step.

Simulated walkthroughAll data is fictional. Nothing leaves your browser.
  1. 0
  2. 1
  3. 2
  4. 3
  5. 4
Owner
Sam Rivera

Decides what to share, can revoke at any time.

Client app
Quill Tax

Import the last three pay statements so you can finish your tax return without re-keying numbers.

Connector
Acme Payroll (simulated)

Stand-in payroll connector used only inside this sandbox. No real Acme Corporation, employer, or paycheck data is involved.

Start here

A small, end-to-end PDPP story

Press Stage the request to begin. You'll play the fictional owner, Sam, deciding what Quill Tax can read from a simulated payroll connector.

Grant scope
Pay statements
Not requested yet

Net and gross pay totals from the last three pay periods, plus the issuing employer name.

  • period_end
  • employer
  • gross_pay_cents
  • net_pay_cents
  • currency
Access modesingle_use
Purpose codetax_filing
Grant idgrant_sb_2026_demo
Expires2026-05-25T00:00:00Z
Records pane

No grant yet, so no records to project. PDPP refuses unscoped reads by construction, not by convention.

  • Stage the request. Simulates a client POST to /par with the proposed scope.
Inspectable transcript

API-shaped requests & responses

Simulated JSON

Each panel reveals as you advance the walkthrough. Shapes are representative of PDPP, not byte-for-byte from a live reference run. See /docs for normative semantics.

  1. 1. Client requests access
    Locked
  2. 2a. Owner denies the request
    Locked
  3. 2. Owner consent + grant issued
    Locked
  4. 3. Resource query returns scoped records
    Locked
  5. 4. Owner revokes / next query refused
    Locked