The 4-party PAY (push) flow: VPA resolution, PIN authorization, debit/credit legs, and deferred net settlement
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
PAY (push) — the drawn flow
• Payer initiates: scans a QR or enters the payee VPA
• VPA is resolved to a real account before money moves
• UPI PIN authorizes; NPCI drives debit then credit
COLLECT (request-to-pay) variant
• Payee's PSP sends the ReqPay first (a collect request)
• Payer receives a request and approves with a UPI PIN
• From authorization onward the debit/credit legs are identical
Instant UX, deferred settlement
• Success reaches the payer in ~seconds
• Interbank money is netted multilaterally by NPCI
• Actual settlement clears in deferred RTGS cycles
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