TEST-ONLY · MONEY_MOVED=FALSE

Run the complete authority-to-evidence lifecycle.

One click exercises challenge, pinned issuer trust, registered mandate, signed decision evidence, atomic reservation, one-use permit redemption, replay suppression, provider attestation and terminal reconciliation with isolated test fixtures. The separate provider key is generated inside the same sandbox run; it is not an external provider or independent audit. No production authority or money movement occurs.

Run the complete strict test →
01

Real returned stages

The page renders the server response. Missing, malformed or incomplete results fail visibly instead of becoming a demo success.

02

Strict mechanics

The sequence exposes the role separation, reservation and one fresh redemption that distinguish production authority from a rule check.

03

Zero execution power

Test fixtures contain no payment credential. Every accepted response must explicitly affirm money_moved=false.

ONE-CLICK STRICT TEST

Watch authority become one bounded attempt—and nothing more.

The browser requests one isolated server-side test run. It does not send account cookies, accept payment credentials or infer missing evidence.

TEST FIXTURES ONLY · NO ACCOUNT · NO PAYMENT

Ready. The expected contract is shown below; no result is marked as completed until the endpoint returns it.

  1. Fresh challenge issued

    EXPECTED

    Bind freshness, audience and the exact purchase attempt.

  2. Account-pinned authority verified

    EXPECTED

    Verify the test issuer against a pinned key and audience.

  3. Active mandate evaluated

    EXPECTED

    Load immutable merchant, currency and budget constraints.

  4. Decision evidence signed

    EXPECTED

    Sign the bounded decision before any budget can be reserved.

  5. Budget reserved atomically

    EXPECTED

    Reserve test budget before any execution handoff exists.

  6. Authorization consumed once

    EXPECTED

    Move the reservation once with a separate processor role.

  7. Provider-bound permit issued

    EXPECTED

    Issue a short-lived permit for one exact test operation.

  8. Fresh permit claim granted

    EXPECTED

    Claim one exact provider-bound operation atomically.

  9. Permit replay suppressed

    EXPECTED

    Prove that only the first server-side claim grants MandateShield authority; this does not prove exactly-once provider delivery.

  10. Sandbox provider attested

    EXPECTED

    Bind the simulated outcome to the isolated provider fixture.

  11. Terminal reconciliation recorded

    EXPECTED

    Close the test outcome and return non-production evidence.

NEXT: VERIFY YOUR DEPLOYMENT

Keep the invariant. Bind what you control.

The free private pilot replaces isolated fixtures with an externally controlled domain or public repository, one server-observed strict live reservation and one fresh permit redemption. It still submits no payment and contacts no provider.

Start verified private pilot →Read the production lifecycle