Via One — Manual Roadmap¶
Generated: May 2026
Purpose: master inventory of every surface that needs user-facing documentation, ranked by audience and priority. Use this to plan which manuals to write next.
Audience taxonomy¶
Every surface falls into one of four audiences:
| Code | Audience | Examples |
|---|---|---|
| OPS | Internal Via One operators / on-call engineers | Brain Hub, Testing Command Center, Live Transaction Console, NOC, OFAC admin |
| PARTNER | External partner technical teams (their devs integrating against us) | RISE wallet API, MobiSend API, HAZ API, Latcom Digital LATCOM-format API |
| DISTRIBUTOR | End-distributor users hitting partner-facing surfaces | Optimus dashboard, RISE wallet UI, Operator POS |
| END-USER | Real customers (consumers) using a wallet or service | El Vecino store clerks, EV bot users, RISE wallet end-users, support portal customers |
Section 1 — Internal cockpits (OPS audience)¶
These are admin-only surfaces. Critical for daily ops + launch readiness. Highest priority because they're the tools you actually use to run the business.
| # | Surface | URL | Status | Manual priority |
|---|---|---|---|---|
| 1 | Live Transaction Console | app.via.one/console/ |
✅ Manual written (this folder) | DONE |
| 2 | Via One Command Center (Optimus dashboard) | app.via.one/app (Brain Hub, CRM, Testing CC, NOC) |
❌ No manual exists | HIGHEST — explicitly requested |
| 3 | Brain Hub (sub-area of Command Center) | app.via.one/app/brain-hub |
Embedded in Command Center | (covered by #2) |
| 4 | Testing Command Center (sub-area) | app.via.one/app/testing |
Embedded in Command Center; 122KB of routes | (covered by #2) |
| 5 | NOC Monitor | app.via.one/app/noc |
Claude-powered incident diagnosis | (covered by #2) |
| 6 | Provider Health page | /health/providers (public JSON) |
No UI, just API | Low — internal devops only |
| 7 | OFAC Admin | /admin/ofac/* |
API-only, no UI | Medium — compliance team |
| 8 | Webhook Delivery Admin | /api/webhooks/admin/* |
API-only, no UI | Medium |
| 9 | viaone-command task app (dash/cmd/ops/my.via.one) |
(multi-domain) | Lightweight task tracker, separate Railway service | Low — not user-facing critical |
| 10 | viaone-support agent UI | support.via.one |
React + Prisma, Socket.IO live updates | Medium — for support agents |
Section 2 — Partner integration (PARTNER audience)¶
Partner-facing API documentation. Several already exist (this folder). Gaps marked.
| # | Surface | Existing manual? | Gap |
|---|---|---|---|
| 1 | MobiSend D2C API (/api/mobisend/*) |
✅ MobiSend - API Reference.pdf + .md |
Refresh for current state |
| 2 | MobiSend CashApp checkout (/api/mobisend/cashapp/*) |
✅ MobiSend - CashApp API.md |
Convert to PDF |
| 3 | RISE wallet API (/api/rise/*) |
✅ RISE Holdings - API Documentation.md + Quick Start |
Convert to PDF, update for v1 yield |
| 4 | HAZ API (/api/relier/*, /api/enviadespensa/*) |
✅ Multiple — Guia Cliente, Guia Integracion | Consolidate to one canonical doc |
| 5 | SmartBiz Telecom API | ✅ SmartBiz - API Integration Guide.md + DOCX |
Convert to PDF |
| 6 | Latcom Digital LATCOM-format (/api/dislogin, /api/tn/latcom) |
✅ Distributor API.md, Via One API v1.0.md |
Refresh — should reflect Apr 29 + May 5 buprolat.latcom.co cutover |
| 7 | Pockyt payment proxy (/api/pockyt/*) |
❌ None | NEW — Pockyt is a major payment surface, deserves a partner doc |
| 8 | Generic ViaOne CashApp (/api/cashapp/*) |
✅ ViaOne - CashApp API.md |
Convert to PDF |
| 9 | Hybrid processing | ✅ Hybrid Processing Guide.md |
Convert to PDF |
| 10 | MAS integration | ✅ MAS Integration Guide.md |
Convert to PDF |
| 11 | IP Whitelisting setup | ✅ IP Whitelisting Guide.md |
Convert to PDF (operational doc, not partner-only) |
| 12 | Optimus partner integration (Telefónica MX) | ⚠️ Reference specs only (Telefónica's, not ours) | NEW — operator-facing doc for Optimus distributors using our platform |
Section 3 — Distributor / customer-facing dashboards (DISTRIBUTOR / END-USER)¶
UIs end-users actually click around in.
| # | Surface | URL | Existing manual? | Gap |
|---|---|---|---|---|
| 1 | Optimus distributor dashboard | optimus.via.one (and app.via.one/app) |
❌ No formal user manual | NEW — distributor-facing how-to-use guide |
| 2 | RISE wallet web app | (TBD) | ⚠️ API docs only, no end-user manual | NEW — end-user wallet guide |
| 3 | Operator POS portal | app.via.one/operator |
❌ No manual | NEW — for store clerks |
| 4 | Customer self-service portal | app.via.one/customer |
❌ No manual | NEW — for end customers |
| 5 | Relier KYB onboarding | onboarding.relier.group |
❌ No manual | NEW — applicant-facing how-to |
| 6 | El Vecino store clerk bot (WhatsApp) | (Meta WhatsApp number) | ❌ No formal manual; baseline scripts in code | Medium — store clerks can self-discover |
| 7 | EV (El Vecino consumer) bot | (Meta WhatsApp number) | ❌ No manual | Medium |
| 8 | Telegram bot | grammY | ❌ No manual | Low |
| 9 | Siri voice integration | iOS Shortcut | ❌ No manual | Low — limited rollout |
| 10 | RCS / iMessage | Carrier registration | ❌ No manual | Low — mostly silent channel |
Section 4 — Compliance & regulatory (CROSS-AUDIENCE)¶
Documents that may have a regulatory or audit-trail purpose.
| # | Subject | Status |
|---|---|---|
| 1 | OFAC compliance engine | Memory-only doc (ofac-compliance-engine.md); needs formal procedure manual for compliance officer audience |
| 2 | DR / Backup procedure | docs/DR-RUNBOOK.md (technical); needs partner-facing data residency / RTO/RPO summary |
| 3 | Webhook signature spec | Implicit in code; needs a one-pager for partners verifying our X-ViaOne-Signature: sha256=… header |
| 4 | PCI-relevant flows (CashApp, Pockyt, Stripe) | Needs scoping doc; redaction policy should be public |
| 5 | OFAC screening workflow | Needs a "what gets blocked, when, what to do" runbook |
Recommended writing order (priority + effort)¶
| Order | Manual | Effort | Why |
|---|---|---|---|
| 1 | ✅ Live Transaction Console | Done | Built fresh, easiest to document while in head |
| 2 | Via One Command Center (Brain Hub + Testing + NOC + CRM) | Large (~50 pages) | Explicitly requested. Most complex internal surface. Most ops value. |
| 3 | Optimus distributor dashboard guide | Medium (~20 pages) | Most-touched external partner UI. Ahead of Thu May 7 launch. |
| 4 | Latcom-format distributor API refresh | Small (~10 pages) | Existing Distributor API.md is stale; refresh for buprolat.latcom.co cutover. |
| 5 | Convert all existing partner manuals to PDF | Mechanical (~30 min total) | One-time cleanup so partner-facing docs are consistent format. |
| 6 | Pockyt partner integration manual (NEW) | Medium (~15 pages) | Pockyt is a major payment processor for us, no doc exists |
| 7 | OFAC compliance procedure manual | Medium (~15 pages) | Compliance officer needs this for audits |
| 8 | DR / runbook partner-facing summary | Small (~5 pages) | Needed for partner due-diligence questions |
| 9 | Operator POS + Customer portal guides | Small each (~5 pages) | Dummy-proof for store clerks / end-users |
| 10 | El Vecino bot user guides (clerk + consumer) | Small (~5 pages each) | Improves rollout adoption |
What's in this folder right now¶
~/Downloads/Via One Manuals/
├── 00 - MANUAL ROADMAP.md ← this file
├── Via One — Live Transaction Console (User Manual).pdf ← NEW (May 6 2026)
├── Via One — Live Transaction Console (User Manual).md ← markdown source
├── Via One — Command Center (Master Manual).OUTLINE.md ← outline only — needs scope agreement
│
├── Existing Partner Manuals/
│ ├── HAZ - Guia Cliente.pdf / .docx / .md (UPDATED Nov2025)
│ ├── HAZ - Guia Integracion API.docx / v2.docx / .md
│ ├── HAZ API Integration Guide.md
│ ├── MobiSend - API Reference.pdf / .docx / .md
│ ├── MobiSend - CashApp API.md
│ ├── RISE Holdings - API Documentation.md
│ ├── RISE Holdings - Quick Start.md
│ ├── SmartBiz - API Documentation.docx / Integration Guide.md
│ ├── ViaOne - CashApp API.md
│ ├── Distributor API.md
│ ├── Hybrid Processing Guide.md
│ ├── IP Whitelisting Guide.md
│ ├── MAS Integration Guide.md
│ ├── Via One API v1.0.md
│ └── Via One Integration Quickstart.md
│
└── Reference Specs/
├── Servipagos - Manual Operador App.pdf
├── Servipagos - Manual Backoffice Comercio.pdf
├── Servipagos - Manual Administrador App.pdf
├── Telefonica - Especificaciones Genericas V5.3.pdf
├── Telefonica - ISO8583 Transactionality.pdf
└── Telefonica TFMX - Web Service Recharge Specification.pdf
Next decisions for Richard¶
- Approve the Command Center master manual outline — see the OUTLINE.md sibling. This is the biggest manual; agreeing scope prevents 100+ pages of wasted work.
- Decide priority order for items #3-#10 above. Right now I'm guessing based on "most touched + most launch-relevant."
- Confirm format preferences — PDF + markdown source for every manual (like Live Console). Or PDF only? Or do partner-facing ones in DOCX too (like HAZ)?
- Confirm language strategy — most existing partner manuals are bilingual (Spanish + English). New manuals should follow the same convention?