Stripe mutation calls are not idempotent #47

New Issue

2026-04-23T18:12:09Z

userAdityaa commented

2026-04-23 18:12:09 +00:00

Summary

Stripe create/update/pay mutation requests do not include idempotency keys.

Why this matters

Retry after network uncertainty can produce duplicate subscriptions/items or repeated payment side effects.

Expected behavior: All non-read Stripe mutations use deterministic idempotency keys derived from business identity plus operation type.

### Summary Stripe create/update/pay mutation requests do not include idempotency keys. ### Why this matters Retry after network uncertainty can produce duplicate subscriptions/items or repeated payment side effects. **Expected behavior:** All non-read Stripe mutations use deterministic idempotency keys derived from business identity plus operation type.

userAdityaa commented

2026-04-23 18:30:06 +00:00

I believe there are only a few remaining issues before we can proceed with the launch. I’ll be traveling and attending a hackathon over the next couple of days, but I’ll do my best to address and close them by Sunday.

👍 1

hodlbod commented

2026-04-23 19:48:06 +00:00

Awesome, thank you!

❤️ 1

userAdityaa referenced a pull request that will close this issue

2026-04-25 05:20:56 +00:00

fix: add idempotency keys to all Stripe mutation calls #49

hodlbod closed this issue

2026-04-25 12:34:35 +00:00

Sign in to join this conversation.