How the system actually works

Interactive maps of the services in your target repositories. Every claim carries the file, thread, or ticket it came from.

OrbitPay demo data. Connect your sources to generate this from your own repositories, Slack, and Linear.

SystemIn progress

Trace a checkout request through the payment stack

Follow one request from the storefront to the ledger, with the code and the conversations that explain each hop.

12 min

Why this module: PAY-231 touches the retry scheduler. Maya cannot evaluate a scheduling change without first seeing where scheduling sits in the request path.

CodeSlackLinear7 sources

Open

Indexed repositories

checkout-api
Public HTTP surface. Accepts checkout requests, enforces idempotency, and hands work to the worker.
TypeScript · 412 files · owned by Dev Shah
payments-worker
Background authorization, retry scheduling, and ledger reconciliation. Where the interesting failures live.
TypeScript · 358 files · owned by Dev Shah
merchant-dashboard
Merchant-facing Next.js app for settlements, disputes, and payout history.
TypeScript · 514 files · owned by Lucas Moreau

Indexed conversations

#payments
Day-to-day payments platform work, design decisions, and rollout coordination.
2,841 messages indexed
#incidents
Live incident response and postmortem threads.
736 messages indexed
#engineering
Org-wide engineering announcements, ownership, and context.
583 messages indexed