Payments, routed like infrastructure.
A gateway + switch that focuses on uptime, traceability, and clean integrations. Built for single-tenant installs with compliance-ready ops.
Gateway APIs
Provider Switching
Ledger-first
Postgres core
What CronosPay does
- Accept payment intents from merchants (API-first)
- Route to providers based on rules & health (switch)
- Record every event in a recon-friendly ledger
- Observability hooks (health, metrics, audit trails)
This is an early MVP deployment. Public marketing pages are intentionally minimal.
Feature highlights
Switching logic
Provider routing based on rules, availability, error rates, and manual overrides.
Compliance readiness
Audit logs, least-privilege service layout, and clear operational SOPs.
Reconciliation
Ledger-first approach to settle, reconcile, and investigate disputes with less guesswork.
Deployable anywhere
Single-tenant installs, Apache reverse proxy, external Postgres by default; Redis optional.
Architecture (MVP)
Modules
- gateway — merchant-facing APIs
- switch — routing / retry / provider policy
- adapters — provider integrations
- ledger — canonical record + reconciliation
Data
- Postgres — source of truth
- Redis (optional) — caching/locks/queues
- Actuator — health endpoints (restricted)
Service status
If you need deeper status, use the health endpoint directly.
Health
Checking…
Server time (UTC)
—
Endpoint
/api/status