Payment Order Number Design and Idempotency Tables: Generation Rules and Unique Index Backstop
The order number looks like the simplest field in a payment system and is actually its foundation. Choose the generation strategy badly and the failures surface six months later: colliding numbers, values rejected as too long after switching channels, auto-increment IDs leaking real volume, and the same payment processed twice under concurrency. This article gives implementable designs.