What happened
A trade address that worked yesterday may contain an old token after its owner generates a replacement. An explicit token rejection is different from a timeout, unavailable checker, or Steam sign-in page. Preserve that distinction: replacing the address is appropriate when the saved token is stale, while changing it repeatedly cannot repair a server authentication problem. First identify the exact response you received.
What to check
Open the trade-offer privacy settings of your own Steam account and copy the current address directly. Inspect both partner and token parameters privately. In CASECS2, open the saved recipient in your profile, replace the outdated value, and save deliberately. Reload the profile to check persistence. Then use the separate link-check control; saving alone does not perform a live verification or create an offer.
Worked example
For example, you regenerate the token on your phone, but a laptop bookmark and the website profile retain yesterday’s address. Updating only the bookmark leaves the delivery recipient unchanged. Compare the source address with the saved field, not with a screenshot of an earlier success message. If the account identifier changed too, investigate whether you copied the link from another signed-in account before proceeding.
Result and next step
The useful outcome is a saved current address and a fresh result for that same value. If checking is unavailable, report the last save time and visible error without calling the link invalid. Hide the token in screenshots. Regeneration does not send a trade or enable paused withdrawals. Read Steam trading guidance and how CASECS2 works before confusing recipient preparation with delivery.