This field guide is being reviewed and revised for accuracy. Some content may change before the target freeze on 30 July 2026.
StablePeg
Achala Arunalu Achala Arunalu Fintech Stablecoin IC Stablecoin banking | Cards | Crypto payments | Fraud/AML | Treasury ops LinkedIn

Operations reference section

Ops Playbooks & Glossary

Turn complex payment operations into repeatable playbooks, clear escalation paths, shared glossary terms, and evidence-driven incident learning across product, support, risk, finance, and engineering.

4 operating flows One shared vocabulary Every case has an owner

Interactive flow lab

Run payment operations with discipline

Switch between triage, incidents, escalation, and glossary governance.

Runbook

From incident to a durable control

Every break should end as a playbook, an owner, and a metric — not a hero fix.

On-call Incident lead Engineering Comms Treasury · Ops
  1. 1
    DetectOn-call

    A monitoring alert or customer report opens an incident.

  2. 2
    TriageIncident lead

    Assess severity, scope, and customer impact.

  3. 3
    ContainEngineering

    Stop the bleeding — feature flag, throttle, or freeze payouts.

  4. 4
    CommunicateComms

    Status page and stakeholder updates on a cadence.

  5. 5
    ResolveEngineering

    Fix, verify, and restore normal operation.

  6. 6
    ReconcileTreasury · Ops

    True-up the ledger, refunds, and any money moved.

  7. 7
    Post-incidentTeam

    Blameless review → a new control, an owner, and a metric.

Endpoint map

Find the operating surface

Filter playbook, case, incident, escalation, glossary, postmortem, and metrics endpoints.

Concept notes

The operating ideas worth remembering

Questions

Check your understanding

Pick an answer and the page will explain the reasoning.

Reference snapshot

Playbooks, glossary, and escalation