Payments Are Lifecycles, Not Objects: Why SDK Status Fields Mislead

A payment isn't a single status; it's a lifecycle of authorization, capture, refund, and settlement events. Many SDKs flatten this into a Payment object with one status field, leading to bugs when developers fulfill orders on authorizations instead of captures. Hyperswitch Prism models payments as state machines with 30+ states, exposing verbs instead of a mutable status.