Crypto payments for marketplaces and classifieds

One merchant account, one invoice per deal, and a webhook that tells your platform the money is really there. Paysell collects from buyers in USDT and TON; paying the sellers stays your logic, exactly as it already is.

USDT and TON on the TON network
0.2% per payment, no monthly fee
Your own order id in every webhook
Payments cannot be charged back

Create an account Read the docs

What usually goes wrong

Acquirers treat a marketplace as somebody else's risk

One contract, hundreds of sellers the bank has never seen, and a category that shifts with every new vertical. The result is a rolling reserve, a fresh document request each quarter, or a flat refusal to underwrite a platform model.

Disputes land on the platform, not on the seller

A buyer files a chargeback, the seller has already been paid out, and the difference leaves the platform's balance together with a dispute fee. On-chain transfers have no reversal mechanism, so a confirmed payment stays where it landed.

Buyer and seller do not share a payment rail

A buyer in one region, a seller in another, and card networks in between that decline, hold, or do not serve one of them. Wallet transfers ignore which passports the two sides hold.

Manual crypto collection breaks at platform scale

One shared wallet address for a hundred deals a day means matching amounts to listings by hand, buyers underpaying by fractions, and every dispute starting with an explorer tab. That is a reconciliation problem, not a payment method.

How Paysell helps

One invoice per deal, keyed by your own id

Create an invoice with the amount and your identifier — a deal id, a listing id, a seller id — and read it back from the HMAC-signed payment.credited webhook. Matching a payment to a listing becomes a single database lookup.

Several stores under one login

Run a separate store per vertical, region or brand, each with its own API keys, webhook endpoint and statistics, all under one account with 2FA, session control and team roles. Your sections stop sharing one opaque ledger.

Money that cannot be pulled back

A confirmed transfer on the TON network is final for everyone involved, so the platform never pays for a dispute filed months after delivery. There are no chargebacks, and refunds are handled through support rather than an API call — a return to a buyer is a transfer you decide to make.

Predictable economics on every deal

0.2% of the payment, fixed when you register the store, with nothing for connection, nothing per month and network fees on incoming payments on us. An underpaid invoice stays open for another 24 hours; an overpayment is credited to you in full.

Where it fits

Buyer payments for listings taken on the platformListing fees and promoted placementsSeller subscriptions and storefront plansDeposits that unlock contact with a sellerCross-border orders where card rails declineWholesale invoices from a fixed amount

Integration in minutes

The pattern that works: the platform receives, the platform settles

Your backend creates one invoice per deal and sends the buyer to the hosted page at /pay/{id}, with a QR code and Tonkeeper and MyTonWallet buttons. On payment.credited you mark the deal paid and run your own payout logic: a seller balance, a scheduled transfer, a withdrawal request. Paysell does not divide an incoming payment between recipients, so that ledger stays inside your platform.

Full API reference

Create an invoice for a deal

curl -X POST https://paysell.me/api/merchant/v1/invoices \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"asset":"USDT_TON","amount":"25","order_id":"order-1042"}'

Respons

{
  "invoice_id": "12c22c1a-a496-4c1e-abe3-72661ef8706e",
  "payment_url": "https://paysell.me/pay/12c22c1a-a496-4c1e-abe3-72661ef8706e",
  "asset": "USDT_TON",
  "amount": "25",
  "status": "pending",
  "expires_at": "2026-09-06T17:20:55Z"
}

Pricing at a glance

One rate for every payment, whatever you sell and wherever your customer is.

0.2%

per payment

setup and monthly fee

0.7 USDT / 0.52 TON

withdrawal fee

25 USDT / 19 TON

minimum withdrawal

Withdraw to any TON wallet in a couple of clicks from the dashboard.

Before you apply

How platform payouts work here

Every payment is credited whole to the store that issued the invoice: Paysell does not divide a payment between recipients, hold it in escrow or run per-seller sub-accounts. Holding funds for sellers, releasing them on delivery and resolving disputes are your platform's responsibility, and your terms should say so. Under the Acceptable Use Policy you answer for what is sold through you.

Questions

Does Paysell support split payments between the platform and sellers?

No. A payment is credited in full to the store that created the invoice, and Paysell does not divide it between several recipients. The workable pattern is that the platform collects on its own account and then pays sellers from its balance, on whatever schedule it sets.

Is there escrow for marketplace deals?

Paysell does not provide escrow and does not hold funds until delivery is confirmed. If your model needs a hold, implement it on your side: mark the deal paid on the webhook, keep the seller's share as an internal balance, and release it when your conditions are met.

Can each seller have their own Paysell account?

A seller can register independently and connect their own store, but that is a separate merchant relationship, not a sub-account under your platform. Within one account you can create several stores, each with its own keys and webhooks.

How do I match a payment to a listing?

You pass your own identifier when creating the invoice and receive it back in the payment.credited webhook, signed with HMAC and retried for up to 24 hours if your endpoint is unavailable. One lookup connects the transfer to the deal, the listing and the seller.

What if a buyer disputes a deal after paying?

There are no chargebacks on the TON network, so the money does not leave your balance automatically, and refunds are handled through support rather than an API call. Whether to return the amount is your decision under your own rules, executed as a normal transfer.

Are there limits on how many invoices a busy platform can create?

A store can create up to 60 invoices per hour, and each invoice can be between 3 and 10,000 USDT or between 0.1 and 7,000 TON. If your throughput needs more, raise it with support through a ticket before launch rather than after.

Ready to take your first crypto payment?

Create an account, connect a store and issue your first invoice today — no setup fee, no waiting for approval.

Create an account