← Projects / Nexus
💳

Nexus

Backend Production Microservice

Overview

Nexus is a backend payment processing orchestrator that abstracts over multiple payment providers — Stripe, PayPal, Klarna, Primer, and Adyen. It normalizes payment data into a unified model and exposes a single consistent API that the rest of the platform uses regardless of which provider processed a given transaction.

Other services — like Resolve for refunds and Shield for disputes — delegate all payment operations to Nexus, ensuring provider-specific logic is centralized in one place. Asynchronous workers handle operations with retry logic and fallbacks to maintain reliability under provider-side failures.

Payment orchestration & provider routing flow

Features

  • Unified API for receiving payment operation requests from other internal services
  • Normalized payment data model across Stripe, PayPal, Klarna, Primer, and Adyen
  • Asynchronous workers with retry logic and fallbacks for reliable operation handling
  • Refund and dispute operations routed to the correct provider per transaction

Architecture

Part of a broader microservices ecosystem. Nexus acts as the payment abstraction layer — consumed by services like Resolve and Shield to execute financial operations without needing to know which provider handled the original transaction.

API
Exposes a provider-agnostic API for payment queries and operations. Routes requests to the correct provider integration based on transaction metadata.
Workers
Inngest functions execute payment operations asynchronously with retry logic, exponential backoff, and fallback handling for provider-side failures.
Database
PostgreSQL stores normalized payment records, operation logs, and provider mappings — serving as the source of truth for all payment state across the platform.

Tech Stack

Backend
TypeScript Bun Elysia.js Inngest PostgreSQL Docker GCP
Payments
Stripe PayPal Klarna Adyen Primer