Payment link states

PENDING → PROCESSING → CONFIRMED
   │
   ├─→ EXPIRED    (terminal — not paid before TTL)
   └─→ CANCELLED  (terminal — cancelled via API)

State	Meaning
PENDING	Created, awaiting payment on any enabled rail
PROCESSING	M-Pesa STK push sent, waiting for PIN confirmation
CONFIRMED	Payment received and confirmed. Webhook delivered.
EXPIRED	Link TTL elapsed without payment
CANCELLED	Manually cancelled via API

Key differences from invoices

Payment links are rail-agnostic and reusable until confirmed or expired:

• One link, multiple rails — the customer picks M-Pesa, TRON, or BSC at checkout
• PROCESSING is M-Pesa-specific: the STK push was sent but the customer hasn't entered their PIN yet
• There is no DETECTED / CONFIRMING split — crypto payments move directly to CONFIRMED once the required depth is reached
• Once CONFIRMED, the link cannot receive further payments

Confirmation depth

Rail	Required confirmations
USDT_TRON	20 blocks (~60 seconds)
USDT_BSC	15 blocks (~45 seconds)
MPESA	Instant (Safaricom callback received)

Terminal states

CONFIRMED, EXPIRED, and CANCELLED are terminal. A link in any of these states will not accept further payments and will not match incoming on-chain transactions.