cs2 gc storepurchaseinit returns result=200, not result=1. what authorizes a session to purchase?

[passtheprt]

minting a cs2 store offer through the gc (steam-user + globaloffensive): storepurchaseinit (2510) > initresponse (2511) > finalize (2504). my init comes back result=200 and never reaches finalize. the same account in a different client, same moment, sends a byte-identical init and gets result=1 plus a txn id. so it looks session-scoped, not an account or throttle problem.

ruled out:

• throttle: other client buys fine, same account
• clienthello version: working client reports an older version and still succeeds.
• pre-purchase service calls (generateaccesstokenforapp, gettradeofferaccesstoken, getownedgames) all return eresult=1. still 200

questions:

1. is result=200 a known store code (epurchaseresultdetail or similar)? what does the gc check before allowing storepurchaseinit?
2. does it gate on how you logged in? my token is from a qr/mobile-approved login. would a password-authenticated steamclient session be treated differently?
3. is there a pre-init step that opens the store for a session (storegetuserdata 2500, a web-login binding) that i'm missing?

stack: [email protected], [email protected], [email protected].

can share scrubbed dumps.

---