Webhook idempotency for stablecoin checkout

Short summary

Design payment webhook handlers as idempotent state machines: validate signatures, deduplicate events, check payment intent state, and verify amounts before transitioning orders. Use atomic database transactions to commit webhook records and order state changes together, preventing duplicate side effects from retries. Model comprehensive payment states beyond binary success/failure to improve merchant clarity and support predictability.

• •Implement idempotency checks (signature validation, event deduplication, state verification) before processing payment webhooks
• •Use atomic database transactions to ensure webhook records and order transitions commit together, preventing retry-induced duplicates
• •Model detailed payment states (pending, paid, expired, underpaid, overpaid, wrong_network, manual_review) rather than binary success/failure

Generated with AI, which can make mistakes.