Humsana sits at the point where a consequential action crosses from one authority context into another. It asks whether the authority still covers what is being executed, and refuses when it does not.
A refusal names the field, both values and the rule, and nothing executes.
Inside one system, the caller and the executor share a boundary, so the check is a formality and the authority context never leaves the place that issued it. Across two systems inside one company, identity travels and answers who is calling, but the authority for this specific action stays behind in the system that granted it. Across two companies, the executor holds the request and almost nothing else, so it will not trust the request and the request cannot prove itself.
Each stage can be held, checked or lost.
Who is acting, and on whose behalf.
How that authority reached the actor.
What the agent is trying to do.
What the authority covers.
What arrives at the executor.
What can later be reconstructed.
Authorized push payment fraud is the class where a payment the account holder approved is redirected to an account they never named.
The integrating party places the check on the path that acts, on its own side of the irreversible call.