Payments, routed like infrastructure.
A gateway plus switch that focuses on uptime, traceability, and clean integrations. Built for single-tenant installs with compliance-ready operations.
Gateway APIs
Provider Switching
Ledger-first
Postgres core
What CronosPay does
- Accept payment intents from merchants through API-first integrations
- Route to providers based on rules, health, and operator control
- Record every event in a reconciliation-friendly ledger
- Provide observability hooks through health, metrics, and audit trails
Public pages are intentionally concise. Merchant, operator, and wiki experiences live behind their dedicated entry points.
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 operations to settle, reconcile, and investigate disputes with less guesswork.
Deployable anywhere
Single-tenant installs, Apache reverse proxy, external Postgres by default, and optional Redis.
Architecture Snapshot
Modules
- gateway - merchant-facing APIs
- switch - routing, retry, and provider policy
- adapters - provider integrations
- ledger - canonical records and reconciliation
Data
- Postgres - source of truth
- Redis (optional) - caching, locks, and queues
- Actuator - health endpoints with restricted access
Service status
Public runtime status is available here through /api/status. Internal actuator endpoints are intentionally not exposed on the public app port.
Health
Checking...
Server time (UTC)
-
Endpoint
/api/status