Drive one simulated authorization against a named card

Requires an API client bearer token.

Drives one simulated authorization against a card the operator issued and funded, over the same wire path a real network would use. The caller passes a card id, never a PAN — the PAN is resolved server-side against a single-use grant and never returned. NOT idempotency-keyed: each accepted call is a deliberately distinct wire transaction (press twice = two payments); the console disables the button while a request is in flight instead. Returns 202 with an acceptance handle plus the wire identity (stan/rrn, nullable). null does NOT mean nothing was sent — it covers both a leg refused before any message was built (safe to retry) and a leg whose outcome is genuinely unknown, e.g. a response that could not be read (NOT safe to assume nothing reached the wire — do not retry on this response alone; poll GET /v1/simulated-spends/{id} first). The decision itself is queryable via that same GET endpoint and arrives asynchronously as an authorization.decided event. A simulator-leg failure is recorded and reported there too, rather than surfacing as an error response here.