Developer docs
Payment lifecycle
NITY0X uses explicit payment states so integrations can distinguish created intents, detected deposits, confirmation progress, terminal success, expiry, and failure.
- intent_created
- awaiting_payment
- pending
- confirming
- confirmed
- expired
- failed
Only the payment state machine should mutate payment status. Confirmed payments credit merchant balance exactly once and write event/audit evidence.
Use webhook events for automation, but keep your own handler idempotent. Network confirmations and retry timing differ by chain.