Paysell
SolutionsPricingDocsBlog
BejelentkezésFiók létrehozása
product

How your payouts are protected at Paysell

What happens to a withdrawal request after you hit the button: automated anti-fraud checks, isolated signing, cold storage — and the part that is up to you.

Published
2026. szept. 12.
Reading time
2 min read
On this page
  • What happens after you request a payout
  • The layers that are always on
  • Hot and cold storage
  • Destination address screening
  • Anti-fraud on unusual requests
  • The part that is up to you
On this page
  • What happens after you request a payout
  • The layers that are always on
  • Hot and cold storage
  • Destination address screening
  • Anti-fraud on unusual requests
  • The part that is up to you
productsecurity

Withdrawals are the most sensitive operation any payment service performs — they are exactly what an attack on a merchant account is aiming for. Here is what happens to a request after you press "Withdraw", and why the money ends up with you.

What happens after you request a payout#

You create the request in the dashboard: asset, amount, destination address. If two-factor authentication is on, a TOTP code is required as well — for payouts that is a hard requirement, not an option you can skip.

The request then goes through automated checks: balance and limits, the destination address, account behaviour. After that the transaction is signed — and this is the part that matters: the application has no access to the keys. Signing happens in a separate, isolated service with no public interface and no way to send money anywhere other than the approved request. Even a full compromise of the web layer does not let an attacker sign someone's payout.

The layers that are always on#

Hot and cold storage#

Hot wallets hold only a working balance — enough for current payouts. Everything above that moves to cold storage automatically, where the online perimeter cannot reach it at all. That caps the worst case for any attack on the infrastructure.

Destination address screening#

USDT issuers do freeze addresses tied to sanctions lists and documented fraud — this happens in practice. A payout to a "tainted" address creates a problem for everyone: you, the recipient and us. So the destination is screened before the transfer goes out, not after the funds are already frozen.

Anti-fraud on unusual requests#

Account takeover looks predictable: a brand-new withdrawal address, an amount unlike the store's normal activity, an attempt to drain the balance at once. Requests like that are held for an additional check — a rare event, but it is the one that separates "the money went to an attacker" from "the money stayed yours".

The part that is up to you#

Three things make withdrawals faster and your account harder to take over:

  1. Turn on 2FA. A request confirmed with a TOTP code is a far stronger signal that it is really you than a password alone.
  2. Withdraw to the same address. Changing it is a normal thing to do, but the first payout to a new address gets a closer look.
  3. Keep your store profile complete and current. An account with no gaps in its data clears checks faster.

The point: none of this exists to make withdrawals harder. It exists so that the payout reaches you, and only you.

If a payout is taking longer than you expected, open a ticket from the dashboard — we will look at that specific request and tell you where it stands.

← All posts
Share

Start accepting USDT and TON

A merchant account, an API key and a hosted checkout page — 0.2% per payment, no monthly fee.

Create an account
On this page
  • What happens after you request a payout
  • The layers that are always on
  • Hot and cold storage
  • Destination address screening
  • Anti-fraud on unusual requests
  • The part that is up to you
On this page
  • What happens after you request a payout
  • The layers that are always on
  • Hot and cold storage
  • Destination address screening
  • Anti-fraud on unusual requests
  • The part that is up to you
Share

Related posts

Introducing Paysell: accept USDT and TON on the TON networkPaysell is a payment processor built specifically for the TON network, giving merchants a cabinet, API, hosted checkout, and webhooks to accept USDT and Toncoin.TON vs. Tron for merchant paymentsA practical comparison of accepting USDT on TON versus USDT TRC-20 for merchants, and why Paysell started with TON.Accept USDT on TON in 5 minutesA step-by-step guide to creating a store, generating an API key, creating an invoice with curl, and confirming payment through a webhook.
Paysell

Crypto payments for online business — fast, chargeback-free, no red tape.

Product

  • How it works
  • Pricing
  • Payment methods
  • Security
  • FAQ
  • Blog

Solutions

  • E-commerce
  • Digital goods
  • SaaS & subscriptions
  • Online education
  • Freelance & services
  • Games
  • iGaming
  • Trading platforms
  • All solutions

Developers

  • Documentation
  • Quick start
  • Webhooks
  • API reference (OpenAPI)
  • llms.txt for AI agents
  • Bejelentkezés
  • Fiók létrehozása

Legal

  • Terms of Service
  • Privacy Policy
  • Fee Schedule and Limits
  • Acceptable Use Policy and Prohibited Businesses
  • AML/CTF and Sanctions Policy
  • Merchant Verification (KYC/KYB) Policy
  • Refunds, Disputes and Chargebacks
  • Crypto-Asset Risk Disclosure
  • All legal documents

© 2026 Paysell

Paysell is a crypto-asset payment service. Balances are not bank deposits, and the value of crypto-assets depends on the market.