Business analysis glossary
Idempotency
What it is
An operation is idempotent when doing it several times has the same effect as doing it once. In APIs, clients often send an Idempotency Key header with a request, so that if the request is retried after a timeout, the server returns the first result instead of creating a duplicate payment, order or record.
Why it matters
Networks fail, and a client often cannot tell whether a request reached the server. Without idempotency, a retry can charge a customer twice. Analysts writing requirements for payments, orders or any create operation should ask how duplicates are prevented and how retries behave, and write that down as a rule.
Example
A merchant app sends a payment request to Tapti Payments and the connection drops. It retries with the same idempotency key. The server recognises the key, sees the first payment succeeded and returns that result. The customer is charged once, as the analyst's requirement stated.