Navigation variant: B7-4 GROUPED dropdowns (Programs, Company, Resources)

API Integrations · Intermediate

Idempotency & Safe Retries

Hybrid · 3 weeks · 11 live hours

Focus on double-submit prevention, optimistic locking, and client-generated keys. Labs simulate card authorization stubs and refund windows—scenarios chosen to resonate with Korean fintech hiring loops.

Tuition (informational)

₩480,000

No checkout here—request details via Contact. See Money-Back Policy.

Developer reviewing retry logic in an IDE with side-by-side diff
Portrait for lead mentor Kai Song

Kai Song

Payments engineer; mentors on duplicate charge prevention drills.

What you build and discuss

  • Idempotency key lifetimes and storage choices
  • Exactly-once illusions: what you can honestly promise
  • UI patterns for stuck payments with transparent states
  • Database constraints that enforce dedupe
  • Testing matrices for retry storms
  • Observability: metrics that show duplicate attempts

Outcomes we assess

  1. 01 Implement a retry-safe endpoint with explicit key semantics
  2. 02 Author user-facing copy for ambiguous payment states
  3. 03 Run a chaos test that proves dedupe holds

Participant notes

“The double-submit UX copy exercise was uncomfortable and useful.”
— Nari · internal feedback

Logistics & candor

Includes a limitation-focused FAQ item per program requirements.

We use vendor-agnostic patterns; no certification with a live PSP is included.