Live topology
?
Reading the map โ health and error states always carry a non-colour cue (icon / dash), never colour alone. Moving dots show live request flow; thicker edge = more throughput.
- OK healthy ! degraded X unreachable
- edge ok raised errors high errors (dashed = non-colour cue)
- Try Start, drag Clients in parallel up to 200 (watch the envelope cap), inject a fault to see the breaker throttle/halt, or click a bank to turn it off โ cross-bank transfers to it then skip ("no destination").
Synthetic cohort live activity per user
login0
Payment flows observed lifecycles
every step is drawn only after the real call that proved it, and carries that call'sX-Correlation-ID โ click a flow to inspect its steps. A โ step is real but not observable through the API (a direct debit settles on D-day via an external CSM), so the flow stops there rather than claiming the funds arrived.
show:
No flows in progress โ press Start to see payment lifecycles advance through their steps.
Live request feed
X-Correlation-ID
Request inspector
the selected call stays pinned here while the feed flows (bearer token redacted)Money across both banks
evaris.esโ
evairi.comโ
totalโ
drift since startโ
Bank benefit (fees)
evaris.esโ
evairi.comโ
Live mode: gross fees (net + VAT) collected by each bank since the start of the pricing window (90 days). Polled every 30 s via GET /pricing/revenue using admin credentials. Not available in simulated mode.
Scorecard
Settled
0
Fraud blocked
0
Sanctions
0
Conserved
โ
EUR total moved
โ
Live TPS
0.0 req/s
TPS ยท last 60s
Bank latency
evaris.es
evairi.com
Rail activity
Recent blocks
No blocks yet this run