# Contact AssetPay AssetPay is a B2B [payment gateway for CS2 and Rust skin trading](/about). If you run a marketplace, gaming site, or store and want to accept skins as payment, we're happy to talk through your use case, pricing, and how the integration fits your stack. ## Email The fastest way to reach us is email. We typically respond within one business day. - **General & support:** [support@assetpay.gg](mailto:support@assetpay.gg) - **Integration & partnerships:** email the same address and mention "integration" in the subject so it reaches the right person. ## Before you reach out If you're evaluating an integration, it helps to include a short description of your platform, roughly how much trade volume you expect, and which titles (CS2, Rust, or both) you need to support. That lets us point you to the right setup on the first reply. You can also read the [developer documentation](/docs) to see the API, webhook events, and authentication model before getting in touch — many integration questions are answered there directly. ## What to expect After you email us, we'll confirm your use case is a fit, share the details you need to provision a merchant environment, and walk through connecting the API and verifying signed webhooks. There's no setup fee to get started — pricing is a fixed percentage per settled trade. ## Support and account questions If you already run on AssetPay and need help with a specific trade, settlement, or webhook event, email support with your merchant identifier and, where relevant, the trade or event ID. Including those details lets us trace the exact record in the ledger and reply with a precise answer rather than a round of clarifying questions. For anything touching account access or credentials, write in from the email address associated with the merchant account so we can verify the request before making changes. For product details and how the gateway works end to end, see the [About page](/about). Prospective partners evaluating whether AssetPay fits their platform are welcome to reach out before writing any integration code — we're happy to talk through the model first.