Payee requests, payer consents, and funds settle over instant rails
Guided views
Explore this system
Step through curated paths without changing the source diagram.
Beat
Next
ReadyChapter 01 / 01
Guided chapter
Diagram guideExplore this system
Inspecting compiled semantics
E ExportT ThemeS Style0 Reset+ Zoom in- Zoom outEsc Close
Find a node
⌕/
No matching nodes
Semantic passport
Verified source
Authored reach
Route probeChoose a start node
Pick two semantic nodes on the diagram
Choose the source, then the destination. Direction matters.
Semantic lensCompare system roles
Choose up to two semantic kinds. One reveals its real traffic; two compare only direct authored relationships.
Choose a kind to inspect its nodes and touching relationships.
Semantic radar
Building overview
Click nodeDrag to pan
Pull becomes push
• The payee sends a request, not a debit
• The payer holds the approve decision
• No pre-authorized pull sits on the account
Consent is explicit
• Approve, decline, and defer are first-class replies
• Mandates carry amount and frequency limits
• Every reply is stored for reconciliation
Instant settlement
• Approved requests settle over instant rails
• Confirmation closes the request loop
• The hub reconciles request against settled funds
Sequence diagram • Built with Archify • Create yours ↗ • Hover to trace • R route • Click to focus • +/− zoom • M radar • [/] views • P play story • T theme • E export