How ZyroPay is built

Every box here is a real part of the system. Click one to see what it does, why it exists and what it guarantees, or play a request from start to finish.

Pick a flow and press Play, or click any box to see what it does.

You and your assistant

Ways in

ZyroPay core

Data

Keys

Chains

Running it

The life of a payment request

A request is created, policy-checked, then either waits for the user (PENDING_APPROVAL) or is approved outright, and moves through SIGNING and BROADCAST to CONFIRMED. A deny ends in REJECTED, the expiry sweep moves CREATED, POLICY_CHECK, PENDING_APPROVAL and APPROVED requests to EXPIRED, and only requests that have not started signing can be CANCELLED; once signing starts, only the chain decides the outcome.

CREATED
POLICY_CHECK
PENDING_APPROVAL
APPROVED
SIGNING
BROADCAST
CONFIRMED

REJECTEDyou said no, or a rule did
EXPIREDnobody decided in time
FAILEDthe chain or a check refused it
CANCELLEDstopped before signing began

Sources: API.md listAgentRequests (state enum) · API.md cancelRequest · API.md Implementation notes: Transaction requests · ARCHITECTURE.md §2.5 Expiry · SECURITY.md C15

Everything on this page comes from ZyroPay's engineering documents (ARCHITECTURE, SECURITY, API, MCP and INTEGRATIONS). Where a part is designed but not yet verified live, its panel says so.

← Back to the start