The problem it solves
A request can fail to receive a response — a dropped connection, a timeout — without the underlying action actually failing. A naive retry in that situation risks performing the same action twice.
How an idempotency key fixes it
An idempotency key is a unique value the client generates and attaches to a request. If the same key arrives twice, the server recognizes it as a retry of the same operation and returns the original result instead of processing it again.
Why it matters more for identity operations
For an operation like linking a NIN to an account or logging a 1:N identification scan, a duplicate from a retried request isn't just wasteful — it risks double-enrollment or a duplicated audit record, which is exactly what idempotency keys are built to prevent.