NestJS checkout hits 78.2% success under 60% payment failure

Mairon José Cuello Martinez built a NestJS checkout system that sustains a 78.2% order success rate under a 60% payment gateway failure rate, using idempotency, selective retry, and runtime configuration tuning [devto]. The system is implemented as a typed pipeline: POST /orders triggers four sequential steps, each operating on a shared OrderContext and halting at the first failure.

The payment step generates a UUIDv4 idempotency key to prevent duplicate charges. Retry logic activates only on HTTP 500 and 503 errors — not business-level rejections — limiting retries to avoid amplifying load during outages [devto]. A circuit breaker isolates the payment service during sustained failures, reducing cascade risk.

A self-tuning mechanism adjusts retry count and timeout windows every 30 seconds using real-time feedback on error rates and latency distributions. During testing, this allowed the system to maintain throughput without manual intervention, even as simulated gateway success dropped to 40% [devto].

The full implementation, including test suites that simulate degraded gateways, is open in the BackendKit Labs monorepo [BackendKit-labs]. The tests compare baseline performance against failure-injected scenarios, showing how the combination of idempotency, bounded retry, and adaptive thresholds preserves functionality under stress.

Most resilient systems require manual tuning during incidents. This design closes that gap by automating configuration changes based on observed behavior — a practical approach for teams without 24/7 on-call bandwidth.