.NET backend · payments · subscriptions · recovery

VpnMediator

Payment, subscription, and actual access can diverge after duplicate webhooks, timeouts, or process restarts.

The project code is private. This case study intentionally excludes secrets, personal data, and operational identifiers.
01

Problem

Payment, subscription, and actual access can diverge after duplicate webhooks, timeouts, or process restarts.

02

Constraints

Duplicate webhooks, network timeouts, restarts, migrations, and private production data.

03

Solution

Explicit access and payment states, idempotent operations, audit trails, background reconciliation, migrations, and verifiable recovery paths.

04

Outcome

Verifiable state transitions, backup/restore, health gates, and rollback-aware deployment; the public case study excludes secrets and user data.

05

Verification

State-transition checks, negative webhook cases, audit records, backup/restore rehearsal, health gates, and rollback verification.

06

My ownership

Backend architecture, state transitions, payment integrations, recovery, migrations, and operational gates.