What happened
The current token belongs to the Steam account, while browser bookmarks and saved website settings can retain earlier copies. Device switching makes that difference easy to miss. Two screens showing the same nickname do not prove they contain the same recipient address. First establish the correct account and current Steam source before updating the copies you personally rely on.
What to check
Copy the current link from the correct Steam account. Update the private CASECS2 recipient and any personal bookmark used for that account. Reload the profile on your other device and compare the stored value privately. Perform a fresh check instead of trusting an earlier screenshot. Keep the update timeline if a delivery request already exists; changing personal copies does not necessarily rewrite a record created before the token changed.
Worked example
For example, you regenerate the token on a phone, then open a laptop bookmark with the old address. Both devices show your familiar account name. The stale token is revealed by comparing the actual addresses, not the avatars. Another copy may live in a note or browser suggestion; review only the copies you genuinely use, rather than distributing the new token broadly to make everything match.
Result and next step
Completion means the service’s persisted recipient matches the current Steam address, regardless of which personal device loads the profile. Note where and when regeneration happened and when the saved copy was updated. Do not synchronize real tokens through a shared public document. Read Steam trading guidance and CASECS2 service stages. Multi-device consistency concerns saved settings; it is not proof that a particular item is in stock or that a pending delivery completed.