Status Model - KarFlows

KarFlows uses clear statuses so API clients and admins can understand what happened.

Message statuses

Status	Meaning
`pending`	Request was created but not completed
`sent`	Channel accepted the message and returned a message ID
`delivered`	Delivery report confirmed delivery
`failed`	Channel rejected the request or a later delivery report confirmed failure
`skipped`	Channel was not attempted

sent is an acceptance state, not handset delivery. An SMS can move from sent to either delivered or failed.

OTP statuses

Status	Meaning
`sent`	OTP was created and sent
`verified`	Customer entered the correct code
`incorrect`	Customer entered the wrong code
`expired`	Code expired before verification
`attempts_exceeded`	Too many verification attempts
`failed`	OTP send failed

Sender name statuses

Status	Meaning
`pending`	Customer submitted the application
`submitted`	Application is under network review
`approved`	At least one configured network can be active
`rejected`	Customer must update or replace application

The overall sender status and each mobile-network status are separate. Sending is permitted only when the sender route is active and the recipient network is approved.

SMS top-up statuses

Status	Meaning
`pending`	Checkout started but not confirmed
`paid`	Payment confirmed and credits added
`failed`	Payment failed
`cancelled`	Checkout was cancelled