Multi-Jurisdictional Checkout with Stripe for DE/AT/CH
Edge-based checkout with regional payment method selection, €2.4M GMV in the first quarter.
Starting Point
VaultLedger expanded from DE to AT and CH. The existing checkout was Node.js-based, monolithic, and only supported credit cards. Local payment methods (Klarna, giropay in DE; EPS in AT; TWINT in CH) were completely missing — conversion killer #1 according to customer surveys.
Our Approach
Complete rewrite of the checkout on Edge Runtime with dynamic payment method selection based on accept-language + Geo-IP. Redis for session state instead of database hits, Stripe SDK with region-specific configs per checkout session.
Technical Highlights
- Edge-based routing: Sub-50ms TTFB in DACH via Vercel Edge Network
- Idempotency-first: All Stripe calls with deterministic idempotency keys
- SCA compliance for European markets
- Observability: Stripe webhook events in Postgres, dashboards in Grafana
Result
€2.4M GMV in the first quarter after launch. Checkout conversion +34% because users see their familiar payment method. TTFB reduced by 62% (from 340ms to 130ms median).
What We Learned
Edge Runtime isn't worth it for everything — but for checkout with regional variability, it's unbeatable. The combination of latency sensitivity and regional config needs fits perfectly with edge workers.