Skip to main content
A deposit is when a user sells their skin to your platform. The user sends their item via a Steam trade offer, and you receive the value as balance.

The Deposit Flow

1

Fetch inventory

Call GET /client/inventory to get the user’s tradeable items with current offer prices.
2

User selects items

Display the inventory in your UI. The user picks one or more items to sell.
3

Initiate deposit

Call POST /client/trading/deposit with the selected items and their offer prices.
4

Trade offer sent

AssetPay sends a Steam trade offer to the user. The trade moves to active — sitting in the user’s Steam inbox awaiting acceptance.
5

User accepts

The user accepts the trade offer in Steam. The trade moves to hold.
6

Hold period (CS2 only)

For CS2, Steam enforces a 7-day trade protection period. The trade stays in hold until it ends. Rust trades skip this step entirely and transition active → completed directly.
7

Completed

After the hold period (CS2) or immediately after acceptance (Rust), the trade reaches completed. You receive a callback and credit the user’s balance.

Single-Item Deposit

Multi-Item Deposit

You can deposit multiple items in a single trade. Pass them all in the items array:
For Rust items that are stackable, you can specify an amount:

Request Fields

Rate Limits

Two layers apply to /client/trading/deposit:
  • Per-merchant tier throttle (shared across all clients): 500 req/min verified, 5 req/min unverified.
  • Per-client guard (scoped per merchant + client Steam ID):
    • Max 5 concurrent active deposits (not-yet-accepted: initiated | active) — TOO_MANY_ACTIVE_TRADES (HTTP 429).
    • Max 10 deposits per 5-minute rolling windowRATE_LIMITED (HTTP 429).
These guard against runaway behavior on a single user. They run before pricing/inventory fetches, so a rate-limited request fails fast and cheap.

Response

The response contains the full trade object:

Instant Deposits

By default, isInstant is true. When enabled, AssetPay calculates how much of the deposit value can be credited instantly based on collateral, rather than waiting for the full 7-day hold period. When a deposit enters hold status, the trade object includes:
  • preCredit - the amount credited instantly (USD)
  • pendingCredit - the remaining amount held until the hold period ends
  • collateral - breakdown of collateral sources
If isInstant is set to false, the entire amount waits until completed. The collateral field in the inventory response tells you the total instant credit available for that user before they start depositing.

External ID

The externalId field is your own tracking identifier. Use it to link AssetPay trades back to records in your system.
External IDs must be unique per trade. Reusing an ID will result in an EXTERNAL_ID_EXISTS error.

Balance Handling for Deposits

When to credit: When NOT to credit: See the Callbacks guide for full details on processing each event.