ECP Pay

Complete documentation of the 4 product cycle phases — from strategic context to operations.

Product Vision

Make payments invisible to the ECP ecosystem

Any app processes any payment method with a single call — without knowing gateways, without duplicating code, without depending on external services to develop.

ECP Pay centralizes Pix, Card and Boleto in a unified API with Provider Pattern — allowing the entire ecosystem (bank, emps, food) to integrate payments in hours, swap gateways without touching the apps, and test everything offline with Internal mode.

Key Metric

Payment Centralization

100% of transactions via ECP Pay
Percentage of ECP ecosystem financial transactions that go through ECP Pay instead of direct gateway calls. Goal: 100% of bank, emps and food processed via unified API.

Target Users

3 Ecosystem Personas

ECP Developers — Integrate payments in apps via unified API.
Financial Operators — Monitor transactions, webhooks and system health via admin panel.
Super Admin — Configure providers, feature flags, register apps and manage the ecosystem.

Endpoints

Tables

HITLs Approved

Epics

82/100

QA Score

Phase Timeline

Phase 01

Strategic Context HITL #1 Approved

OKRs, 5 measurable Key Results, 6 product principles, OST with 15 opportunities mapped to 5 KRs, 4 open questions and 4 assumptions.

Phase 02

Product Discovery HITLs #2-#6 Approved

9 opportunities prioritized via WSJF across 3 pillars, 7 hypotheses with 26 assumptions, low-fi and high-fi prototypes, 3 epics, 13 features, 29 user stories with BDD, evaluation of Cagan's 4 risks.

Phase 03

Product Delivery HITLs #7-#10 Approved

DDD with 6 bounded contexts, 6 ADRs, Fastify API with 29 endpoints (9 payment + 20 admin), SQLite with 10 tables, React SPA with 8 pages, QA score 82/100.

Phase 04

Operations HITLs #11-#12 Approved

Local deploy strategy, 3 SLOs defined, DORA metrics, 3 A/B experiments planned, monitoring endpoints.

Quick Access

🎯 Phase 01 — Strategy 🔍 Phase 02 — Discovery ⚙ Phase 03 — Delivery 🚀 Phase 04 — Operations 📊 Dashboard App

Phase Summaries

Phase 01 — Strategic Context

OKRs, Principles and Opportunity Solution Tree

Definition of strategic objective: "Make payments invisible to the ECP ecosystem", with 5 measurable Key Results. OST with 15 opportunities mapped to 5 KRs. 6 product principles guide all decisions: contract above implementation, development without external dependencies, observability as a first-class citizen.

phase-01-output.json

Phase 02 — Product Discovery

Opportunities, Hypotheses and Structured Backlog

9 opportunities prioritized via WSJF across 3 pillars (Core Infrastructure, Development Velocity, Production Reliability). 7 solution hypotheses with 26 critical assumptions. Backlog with 3 epics, 13 features and 29 user stories with BDD/Gherkin acceptance criteria. Cagan's 4 risks evaluated, all approved.

prioritized-opportunities.json ideation-output.json backlog-and-risks.json

Phase 03 — Product Delivery

Architecture, API, Frontend and QA

DDD architecture with 6 bounded contexts. Stack: Fastify 5.0 + SQLite3 + React 18.3 + Vite 5.4 + Tailwind CSS. API with 29 endpoints (9 payment + 20 admin). Provider Pattern with InternalAdapter and AsaasAdapter. React SPA with 8 admin pages. QA score 82/100 — approved with observations.

architecture-output.json backend-status.json frontend-status.json qa-report.json

Phase 04 — Operations

Deploy, SLOs and A/B Experiments

Deploy strategy for local environment (v1). 3 SLOs defined: 99.9% availability, >99% webhook delivery, p95 latency <300ms. DORA metrics adapted for local development. 3 A/B experiments planned for continuous optimization.

operations-output.json