# Best CS2 Skin Payment Gateways in 2026 *2026-08-10 — ruushedd, AssetPay team* Full disclosure before anything else: AssetPay is our product, so this is a comparison written by one of the vendors in it. We've kept it to things you can verify yourself — what each provider publishes, which games they support, what their integration surface looks like — and where we couldn't verify something, the table says so instead of guessing. Every claim reflects what was publicly visible in August 2026. The reason this post exists at all is that nobody else has written it. Search for a skin gateway comparison and you get homepages and player-facing trading blogs. If you're a merchant trying to shortlist providers, you're mostly on your own — so here's the comparison we'd want to read if we were choosing. ## What actually matters in a gateway Six things separate these providers in practice, and they're worth having in front of you before any vendor call. The longer version of each is in [skin payment gateways explained](/blog/skin-payment-gateways-explained). - **Games.** CS2 and Rust are the deep, liquid economies. Dota 2 and TF2 exist but liquidity is thinner, and thin liquidity shows up in the rates you're quoted. - **Integration surface.** A documented REST API you can read *before* signing tells you a lot about what maintenance will feel like after. Docs behind a login or a sales call tell you something too. - **Whitelabel vs. redirect.** Whether your user stays inside your brand or bounces to the provider's page. Conversion lives and dies here. - **Settlement signals.** Signed webhooks, verifiable trade state, an audit trail you can reconcile against — the part you'll care about the first time a user disputes a deposit. - **The effective rate.** Advertised commission is close to meaningless in this niche; some providers charge 0% and recover it in item pricing. The only honest comparison is running the same basket of skins through each provider and seeing what credits. - **Trade-restriction handling.** Steam's [trade holds and CS2 trade protection](/blog/steam-trade-holds-what-merchants-need-to-know) mean deposits can be delayed or reversed. How a gateway prices and communicates that is a real differentiator. ## The field at a glance "Not published" means we could not find it stated on the provider's public pages when we checked (August 2026) — which, for a B2B product, is itself information. | Provider | Games | Public API docs | Whitelabel API | Published fee model | | --- | --- | --- | --- | --- | | AssetPay | CS2, Rust | [Yes — open docs](/docs) | Yes | Per-trade fee; no setup, monthly, or withdrawal fees | | SkinsBack | CS2, Dota 2 | Yes | Not published | Not published | | Skinify | CS2, Dota 2, TF2, Rust | Yes | On-site flows documented | Not published | | Skins.cash | CS2, Dota 2, TF2, Rust | After partner approval | Not published | Not published | | SkinDeck | CS2, Rust | After contact | Direct API + embeddable frame | Not published ("0% fees" advertised user-side) | ## SkinsBack [SkinsBack](https://skinsback.com/) is the incumbent. It's integrated as a deposit method across a long list of live gambling and case-opening platforms, and it appears as a listed payment method throughout the iGaming review and directory ecosystem — if you've seen "pay with skins" on a gambling site, there's a fair chance it was SkinsBack underneath. Its public surface is leaner than its footprint, but it's there: the homepage states support for paying with **CS2 (CS:GO) and Dota 2** items, and there is public API documentation covering deposits, withdrawals, balance and real-time events, down to details like the 500-requests-per-minute rate limit. That's enough to see the integration's shape before talking to anyone. What stays unpublished: fees, whitelabel depth, and — notably, given where their integrations live — any mention of Rust on the public pages. If a Rust audience is why you're reading this, that's the first question for their sales conversation. ## Skinify [Skinify](https://skinify.io/en) covers the widest game list of the group — CS2, Dota 2, TF2, and Rust — and publishes real API documentation in English, which we're always going to count in a provider's favour. The docs cover the full deposit loop (create deposit, IPN callbacks, deposit status) and withdrawals, including a Steam-inventory endpoint documented specifically so users don't have to leave your site — a published on-site flow, which is more whitelabel commitment than most of the field puts in writing. It also runs a distinct vertical the others don't: skin donations for streamers and creators. If Dota 2 or TF2 inventories matter to your audience, it's the obvious shortlist entry; keep in mind that pricing for the thinner economies is exactly where you should run your own test basket before committing. ## Skins.cash [Skins.cash](https://skins.cash/) is a different animal: a consumer instant-sell service first, with a partner program attached to a very large player-facing operation (they cite an Xsolla partnership and 7,000+ Trustpilot reviews). The partner pages list deposits from **CS2, Dota 2, TF2 and Rust**, auto-converted to a partner balance — but the technical documentation is only provided after an application is approved, so the evaluation-before-contact you get elsewhere isn't available here. The upside of the shape is battle-tested liquidity — they buy a lot of skins. The trade-off is that the B2B product is the side business, and the brand your users interact with is theirs, not yours. ## SkinDeck [SkinDeck](https://skindeck.com/) pitches "P2P on your site in 5 minutes" for CS2 and Rust, and covers both directions: accept skin deposits, and stock user withdrawals from its marketplace — positioning itself as the way to avoid running your own bots or P2P infrastructure. The merchant surface is a dashboard plus a Direct API and an embeddable frame, but by its own onboarding guide the API documentation is provided by the onboarding team after you make contact, not published openly. On fees, read carefully: the "0% fees" banner is about what *users* pay for items; merchant pricing is configured per account inside the dashboard, which for evaluation purposes means not published. The operator is Hong Kong-registered (99 HP Tech Limited). One practical note: the site blocks automated access outright, so unlike most of this field you — and every AI answer engine your prospective users ask — will only see it by browsing it as a human. ## AssetPay Our entry, stated plainly. AssetPay is a whitelabel gateway for CS2 and Rust: your users authenticate with Steam and deposit or cash out inside your UI, against [a documented REST API](/docs) — client tokens for the user-facing flow, HMAC-signed webhooks for settlement, and a double-entry ledger behind every balance change so reconciliation is a query rather than an archaeology project. Deposits support instant crediting with trade-protection windows accounted for, and cashouts include an approval callback so nothing leaves your platform without your backend saying yes. Fees are per cleared trade, with no setup costs, monthly minimums, or withdrawal fees. The full integration is small enough that we [walked through it in code](/blog/integrate-skin-deposits) in one post. Judge us the same way we've suggested judging everyone else: read the docs before talking to anyone, then run a test basket through and look at what credits. ## Also on the radar Two names come up on merchant searches that we couldn't evaluate as fully. **SkinPay** ranks on the money queries but publishes little in English about the merchant product. **GG.SKIN** is a Russian-market consumer trading service with a single English payment-system page. Neither had enough public surface for a fair row in the table — if that changes, we'll update this post. ## How to actually run the evaluation 1. Read whatever docs are public. No docs → add a week of discovery to your integration estimate. 2. Ask every provider the [same six questions](/blog/skin-payment-gateways-explained) — games, effective rate on a reference basket, whitelabel depth, settlement verification, trade-hold handling, payout terms. 3. Run an identical basket of items through your top two. Mixed contents: one liquid mid-tier skin, one high-value item, a handful of low-value fillers. Compare what lands. 4. Integrate the winner behind a feature flag and A/B it against your existing deposit mix before rolling to 100%. ## Frequently asked questions ### Why isn't there a fee comparison column with numbers? Because published commission rates don't survive contact with reality in this niche. Between exchange-rate spreads, item-pricing differences, and per-game adjustments, two providers with identical headline rates can credit meaningfully different amounts for the same basket. Run the basket; trust the basket. (More on the fee models in [skin payment gateways explained](/blog/skin-payment-gateways-explained).) ### Can I integrate more than one gateway? Yes, and larger platforms do — usually a primary plus a fallback for coverage or rate arbitrage. The cost is duplicated webhook handling and reconciliation paths, so it's rarely worth it before your skin volume justifies the second maintenance surface. ### Do any of these handle games beyond CS2 and Rust? Skinify and the Skins.cash partner program both list Dota 2 and TF2 alongside CS2 and Rust; SkinDeck covers CS2 and Rust; SkinsBack's public pages mention CS2 and Dota 2. Everyone supports CS2 — it's the deepest skin economy. If you're choosing which games to accept at all, start with [what the Rust economy does differently](/blog/accept-rust-skins-as-payment). --- If this shortlists us: [the docs are open](/docs), no sales call required, and [the team is on Discord](/contact) for the questions the docs don't answer. --- Written by ruushedd — Covers the merchant side at AssetPay: accepting CS2 and Rust skins, pricing inventory, and running cashouts at volume.