Economic / Payment Gateway
BEATOZ CPG (Core) - Crypto Payment Gateway
Solo-built crypto payment gateway monorepo that served as the payment-facing domain inside a shared Beatoz dev-pilot rollout spanning issuer, treasury, custody, CKYC, and adjacent financial services. Combines a NestJS API, chain-specific monitoring workers, HMAC-signed webhooks, and admin/merchant dashboards.
- Role
- Solo builder · architecture, implementation, and operational tooling
- Period
- 2025.11 - Present
- Context
- Beatoz Labs
Solo-built crypto payment gateway monorepo that served as the payment-facing domain inside a shared Beatoz dev-pilot rollout spanning issuer, treasury, custody, CKYC, and adjacent financial services. Combines a NestJS API, chain-specific monitoring workers, HMAC-signed webhooks, and admin/merchant dashboards.
What made the system difficult.
Had to keep payment state consistent across heterogeneous networks while supporting both API-driven flows and direct wallet transfer detection. The domain also needed merchant/store onboarding, integrated payment UX (widget/session/custom payments), custody wallet operations, settlement processing, webhook delivery tracking, and clean integration points for issuer, treasury, and compliance-oriented services inside the shared dev rollout.
How boundaries and flows answered it.
Implemented merchant/store APIs including a public merchant list for store pages and a Developer Site registration flow (auto-approve), backed by SSOT API credentials. Built a unified payment orchestrator (Strategy/Adapter) with SSOT QR persistence and conditional chain scanning, plus chain-specific workers/processors. Implemented payment products APIs (integrated payments, widgets, custom payments) with session/status endpoints and supporting services (exchange rate/gas fee calculation). Added custody wallet management, issuer-facing integration hooks, settlement flows that can hand off into treasury-side processing, and an HMAC-signed webhook delivery system with retry + persistence. The runtime was structured to fit a central dev-pilot rollout layer rather than a standalone service-only deployment.
The path of responsibility through the system.
Backend API
Payment Engine & Settlement
Responsibilities
- — Unified payment orchestrator (Strategy/Adapter)
- — Chain-specific workers & processors
- — Settlement queues & controllers
Dashboards
Admin & Merchant UI
Responsibilities
- — Admin dashboard
- — Merchant dashboard
- — Operational tooling
Payment Products
Widget / Session / Custom Payment
Responsibilities
- — Integrated payment sessions
- — Payment widget config
- — Custom payment flows
Overview
- Solo-built crypto payment gateway monorepo: API + monitoring workers + webhooks + operations dashboards.
- Operated as the payment-facing domain inside a broader Beatoz dev-pilot rollout that also covered issuer-facing flows, treasury, custody, CKYC, and other adjacent services.
Key Components
- Merchant/store onboarding (public merchant list + Developer Site store registration)
- Strategy/Adapter payment orchestration per chain/payment type
- Integrated payment products (widget/session/custom payment) and configuration endpoints
- Custody wallet management and provider-based key signing
- Issuer-facing synchronization hooks and shared runtime wiring for downstream financial/compliance domains
- Queue-separated monitoring workers for transaction detection/confirmation
- HMAC-signed webhooks with retry policies and delivery tracking
- Settlement and operational dashboards (Admin/Merchant)
- Runtime conventions aligned with a central AWS-based dev-pilot rollout layer