Built for teams that run more than one product.

Nexus sits between your applications and your payment provider accounts. Here is everything it handles for you.

Orchestration

Create, read and cancel payments through one REST API, regardless of the provider behind it.

Priority-ordered rules by method, country and currency with capability checks and logged decisions.

Same key and payload returns the original result; a different payload with the same key is rejected.

Uncertain outcomes are reconciled with the provider before any new charge is attempted.

Raw bodies preserved, signatures verified with each provider’s documented method, duplicates detected.

Events are committed with the state change, so nothing is lost between your database and the queue.

Exponential backoff, a dead-letter queue, manual retry and full event replay.

Timestamped HMAC-SHA256 signatures with rotation and replay protection.

One-time and recurring prices; amounts never change once used — new versions are created instead.

Trials, renewals, past-due handling and cancellation at period end — with payable invoices where recurring debits aren’t available.

Volume per currency, success rates and trends per application — currencies are never summed together.

Owner, Admin, Developer, Finance Viewer and Read-only roles enforced on the server.

Per application and environment, shown once, stored hashed, rotatable and revocable.

Provider secrets are encrypted at rest and never sent to the browser or written to logs.