Explore how PayPal, Stripe, and Adyen use idempotency keys to prevent duplicate payments, ensuring secure, single transactions in digital payments.

Henrique Schroeder

Selenium

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Learn how PayPal and Stripe prevent duplicate payments using idempotency keys. Idempotency ensures transactions are executed once, preventing customers from being charged multiple times for the same purchase. The workflow of idempotency involves sending a payment request with an idempotency key, checking if the key has been seen before, and processing the request accordingly. Idempotency keys have expiration timeframes to prevent system overload. This innovation in digital payments enhances security and user experience.

Idempotency Keys: How PayPal and Stripe Prevent Duplicate Payment

The Essence of Idempotency in Payment Systems

Efficient Retry Strategy for Failed Payments with Idempotency Keys

Expiration Timeframes of Idempotency Keys

Back in the days, I remembed when I did something similar to implement a robust pgsql-based events storage.
Same approach: the event uuid was created starting from an hash deterministically.
For every event family (30 or 40 different events across a dozen of families) there were factories which picked relevant information to compute the reproducible ids.
2B events partitioned over 128 tables, and not a single dup ever reached the CQRS core, it wouldn’t be able by design.