Live merchant identity-continuity demo
Approve once. Verify every order.
A merchant approves the identity and Agent Card it has actually reviewed. When that autonomous customer returns, the gate checks whether it is still the same registered agent, using the same wallet, same anchored card and same cross-chain identity.
If the website is compromised, the order stops. If the agent legitimately changes its anchored identity, the merchant is asked to review it again. No silent substitutions.
Repeat customerAccept automatically when the current evidence still matches the merchant-approved identity.
Compromised websiteBlock when the served Agent Card no longer matches its on-chain fingerprint.
Legitimate updatePause and request reapproval when a new, internally consistent card has been anchored.
1Verify nowRead CIS-8004, fetch the card and check its exact hash.
2ApproveSave the owner, wallet, URI, hash and selected identity rail.
3Customer returnsRun the same checks before granting order or API access.
4DecideAccept, block, or require merchant reapproval—with a receipt.
Step 1 · Merchant onboarding
Approve the identity you have reviewed
Gregers #40 is the live example. Choose the identity rail presented to the merchant; the API verifies external keys through CIS-8.ownerOfKey, not merely by trusting the website.
No merchant approval stored in this browser yet.
Step 2 · Repeat-order preflight
Is this still the customer we approved?
Run the real check, then compare it with two clearly labelled simulations. Simulations modify only the displayed evidence and never touch the website or chain.
Approve the agent first, then run a repeat-order check.
Merchant audit receipt
Evidence for the decision
Every decision binds the approved identity, current evidence, individual checks and scenario boundary into a SHA-256 receipt.
No receipt yet.