Steam Trade Holds and Trade Locks: What Merchants Need to Know

hunbenji

AssetPay team · August 9, 2026

Every skin that moves through your platform moves through Steam's trade system, and Steam's trade system is full of timers. Holds, locks, cooldowns, protection windows. They're behind most of the "why can't I deposit this skin?" tickets you'll ever get, and behind a fair amount of mispriced inventory too.

This is the reference we keep writing out by hand for partners: what each restriction is, when it applies, and what it changes for a business taking skins as payment.

#The three kinds of restriction

Community shorthand lumps all of it together as "trade locks", but there are three separate mechanisms, and they attach to different things:

Each is covered in turn below.

#Trade holds: the 15-day account penalty

If a Steam account trades without the Steam Mobile Authenticator, or enabled it less than 7 days ago, Steam holds outgoing trades for up to 15 days before delivering the items. The reasoning is sound: a hijacked account's items can't be instantly laundered, and the delay gives the real owner time to notice and recover.

What that means on your side is straightforward. A user paying with skins from an unauthenticated account can't deliver the items now — the "payment" would arrive two weeks later, assuming they don't cancel it in the meantime. No serious platform treats a held trade as payment.

In practice this mostly filters itself, because anyone active in the skin economy already runs the authenticator. The part that doesn't filter itself is the error message. If your checkout detects the condition and explains it, the user fixes it. If it fails generically, you pay for that in support volume.

A gateway should reject held trades outright and say why. AssetPay's checkout does this at the eligibility check, before an offer is ever created.

#Item cooldowns: the 7-day locks

Separately from account holds, individual items carry their own time locks. A CS2 item bought on the Steam Community Market can't be traded for 7 days after purchase. And since 2018, CS2 items received in a trade are trade-locked for a period before they can move on again — the cooldown that ended instant item-flipping between accounts.

The merchant-side consequence is subtle, and it's the thing most people miss: an item's lock status is part of its value. A tradable AK-47 | Redline and an identical one locked for another six days are different assets. The locked one can't be resold or moved until the timer runs out.

Any pricing engine worth using tracks tradability timestamps per item rather than market price alone. When you're evaluating a gateway, ask specifically what happens to locked items at deposit: rejected, accepted at a discount, or accepted blind. Accepting blind is how platforms end up holding inventory they can't liquidate. (Related: how CS2 skin pricing actually works.)

#CS2 trade protection: the 2025 change that rewrote the rules

In late 2025 Valve introduced trade protection for CS2. Items that change hands via trade now enter a protection window during which the trade can be reversed if the original account turns out to have been compromised — Valve's answer to the hijacking economy that trade holds never fully solved.

For the skin economy this was an earthquake, and the market repriced sharply when it landed. Reversibility touches the one property merchants liked most about skin payments: finality.

Three things follow from it. Finality now has a timer, so a freshly received CS2 item is not settled the way it would have been in 2024, and platforms have to account for the protection window in how quickly they re-sell or pay out against received items. The scam-recovery burden has shifted, which is good for players — someone who gets scammed can be made whole — but it means recipient-side businesses need to treat recently traded items as carrying reversal risk, roughly the way card merchants treat a brand-new card differently from a repeat customer. And Rust is a different regime entirely: trade protection is a CS2 system, Rust trading continues under the general Steam rules, so a gateway covering both games has to model the two economies separately.

This is the class of risk a gateway exists to absorb. Valve changes trade mechanics without warning, and when they do, an in-house bot operation has a bad week. The gateway's job is to have already updated eligibility, pricing and settlement so that your webhooks keep meaning what they meant.

We'd add one caveat: trade protection is recent, and Valve has adjusted its trading rules more than once since. Treat any specific window length you read online, including ours, as something to re-check against Valve's own documentation before you build logic around it.

The commercial half of this — who actually absorbs the loss when a trade is reversed, and what collateral stands behind "instant" credit — is its own subject: who bears CS2 reversal risk.

#Frequently asked questions

#Why can't my user deposit a skin they just bought?

Almost always one of the 7-day locks. The item either came off the Community Market or arrived in a recent trade and hasn't cleared its cooldown. The Steam inventory screen shows the unlock date; a good deposit flow surfaces that inline instead of failing with a generic error.

#Do trade holds apply if both accounts have the Mobile Authenticator?

With a long-standing authenticator on both sides and trades confirmed through it, no 15-day hold. The hold targets accounts without an authenticator, or with a freshly added one.

#Can a gateway bypass any of these restrictions?

No, and treat any claim otherwise as a red flag. These are Steam-side rules enforced on Valve's infrastructure. What a gateway can legitimately do is detect restrictions before money is involved: check eligibility, price in lock status, and refuse trades that can't settle cleanly.

#As a merchant, do I need to track all this myself?

If you build in-house, yes — all of it, forever, including the next rule change. If you integrate a gateway, your surface is an eligibility answer and a settlement webhook, and the timers above become someone else's problem. That trade-off is most of the case for using one, and the full picture is in our guide to accepting CS2 skins as payment.

Got a specific restriction scenario you're not sure about? Ask the team — these edge cases are most of what we deal with.