Retrieve a simulated-spend attempt

The wire identity (DE11/DE37), if one was minted. Null covers two different causes: (1) state is failed and this stan is null — the leg was refused before a message was ever built, genuinely safe to retry — or (2) state is still accepted past a safe interval — the wire state is unknown, a message may already be on the wire, do not retry. A failed row with a NON-null stan here reached sent first and is not case (1).

The wire identity (DE11/DE37) minted alongside stan — always null/non-null together. See stan above: null does not by itself mean safe to retry, check state too.

Sandbox WIRE vocabulary, derived from the simulated DE39 response code alone — NOT the closed decline-reason contract that transactions and webhooks publish. Tokens are the standard ISO 8583 meanings of the code (do_not_honor, lost_card, stolen_card, insufficient_funds, not_permitted_to_cardholder, ...), with an unrecognised code reported as declined_<code>. Several published decline reasons share one wire token (mcc_denied, entry_mode_denied and refund_float_not_configured all ride DE39 57, so all three appear here as not_permitted_to_cardholder), and the spellings near-miss across the two surfaces (wire lost_card vs published card_lost) — so never match these tokens against the published vocabulary. Read the published reason from the transaction or the authorization.decided event. See the Decline reasons guide.