howitworks.io logohowitworks
← Saari reels
BackendReel #38 · 7 Nov 2026

Interview: Pay button 2 baar daba, paise 2 baar na katein. Kaise rokoge? Idempotency key

Double payment ki asli wajah double click nahi, retry hai: request server tak pahunch gayi aur paise kat gaye, par response raaste mein kho gaya, toh app (ya user) ne dobara bheja. Button disable karna sirf UX hai, network retry ko nahi rokta. Fix: idempotency key. Client har payment attempt ke liye ek unique key banata hai (jaise UUID v4) aur har retry mein wahi key bhejta hai. Server pehli request ka result us key ke saath save karta hai; wahi key dobara aaye toh kaam dobara nahi karta, saved result lauta deta hai. Stripe ka Idempotency-Key header aur Razorpay X payouts ka X-Payout-Idempotency header yahi karte hain.

Links

Aaj ye karo

  1. Client par Pay click hote hi ek key banao: crypto.randomUUID(), aur use is payment attempt ke saath save rakho.
  2. Har retry mein wahi key header mein bhejo: Idempotency-Key: <key>. Naya payment = nayi key.
  3. Server par table banao jisme key UNIQUE ho, saath mein request ka hash aur saved response.
  4. Request aate hi pehle key INSERT karo (ON CONFLICT DO NOTHING). Insert hua toh payment karo aur response save karo; key pehle se thi toh saved response lautao.
  5. Same key ke saath alag amount ya body aaye toh error do (Stripe bhi original params compare karta hai).
  6. Keys ko expiry do: Stripe v1 purani keys 24 ghante baad hata sakta hai, Razorpay payout key 7 din valid rehti hai.
  7. Button disable bhi rakho, par sirf UX ke liye. Asli safety server pe hai.
crypto.randomUUID()
Idempotency-Key: <uuid>
CREATE TABLE idempotency_keys (key TEXT PRIMARY KEY, request_hash TEXT NOT NULL, response JSONB, created_at TIMESTAMPTZ DEFAULT now());
INSERT INTO idempotency_keys (key, request_hash) VALUES ($1, $2) ON CONFLICT (key) DO NOTHING RETURNING key;

Sources

Stripe API docs (idempotent requests) aur Razorpay X payout idempotency docs; 7 Nov 2026 ko check kiya.

Aise hi tech cases ke liye follow karo