Crypto payments for mobile apps and web versions
Most apps sell more than the store can bill for: a web dashboard, a desktop build, a mini app, real-world services. Paysell adds USDT and TON to those channels, confirms each payment on the TON network and tells your backend which account to credit.
- USDT and TON on the TON network
- For web, desktop and outside-store channels
- Account credited on a signed webhook
- 0.2% per payment, no monthly fee
What usually goes wrong
Store billing takes a cut and sets the calendar
Platform commissions reach 30% on many products, and proceeds arrive on the store's payout schedule rather than yours. For a small team, the gap between a sale and usable cash is a planning problem long before it is a margin problem.
Whole regions cannot pay in your app
Store payment methods vary by country, and in several markets users have no working card at all. They keep a crypto balance instead, so the limiting factor on revenue is the checkout you offer rather than the demand for your product.
Refunds and disputes are decided elsewhere
A platform or an issuer can refund a purchase without asking you, sometimes after the content has been fully consumed. You learn about it from a report, and the balance you already recognised as revenue quietly changes.
Rolling your own crypto flow is a project
Watching addresses, matching amounts, handling underpayments and expired invoices is weeks of backend work that has nothing to do with your app. Most teams start it, get it 80% right and quietly leave the rest to support.
How Paysell helps
Monetise the channels store billing does not cover
A web account, a desktop build, a Telegram mini app, a version distributed outside the stores, physical goods or real-world services — these are the places a crypto checkout fits cleanly. One store and one API key serve all of them.
Credit the account on a signed webhook
Put your user id and SKU in the invoice order id, then grant the entitlement when `payment.credited` arrives with a valid HMAC signature. Retries continue for up to 24 hours, and the entitlement syncs to the app the same way any other server-side purchase does.
Revenue that does not get clawed back
A confirmed transfer on the TON network cannot be reversed by a bank or a platform, so recognised revenue stays recognised. Refunds are yours to send from your own balance if your policy calls for one — a decision, not a surprise.
Fees you can model in advance
0.2% of the received payment, fixed when you register the store, with no setup fee, no monthly fee and network fees on incoming payments paid by Paysell. A withdrawal has its own flat fee of 0.7 USDT or 0.52 TON taken from the amount, and payments are credited to your balance about a minute after the transfer.
Where it fits
Integration in minutes
A web checkout your app can read
Create a store in the dashboard and call the invoice endpoint from your web backend with the user id and SKU as the order id. The hosted page shows a QR code and opens Tonkeeper or MyTonWallet, so a user on a phone pays in the wallet they already have. When the signed webhook arrives, write the entitlement to the same account record your app already reads, and the purchase appears on the next sync.
Full API referencecurl -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"}'{
"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.
Withdraw to any TON wallet in a couple of clicks from the dashboard.
Store rules still apply — read them before you build
Apple and Google require their own in-app purchase systems for digital content consumed inside an app, and they restrict how an app may point users to outside payment. Those rules differ by country, app category and platform version, and they change — Paysell is not a way around them and we will not tell you otherwise. Where an external checkout is legitimate is your web or desktop product, builds distributed outside the stores, mini apps, physical goods and real-world services, plus the specific exemptions the platforms grant. Check the current guidelines for your category, and take legal advice if the answer is not obvious.
Questions
Can I use crypto payments to avoid App Store or Google Play commission?
No. Both platforms require their own in-app purchase system for digital content consumed inside an app, and they limit how an app may steer users to external payment. Paysell fits the parts of your product the stores do not bill for — the web version, desktop builds, outside-store distribution, mini apps, physical goods and real-world services.
Where does a crypto checkout legitimately fit for an app business?
Anywhere the purchase does not happen inside the store-distributed app: your website and web dashboard, a desktop client, a Telegram mini app, a build you distribute yourself, and anything physical or real-world. Rules vary by platform, category and country, so confirm the current guidelines before you ship.
Can I accept USDT for a subscription to my app's web version?
Yes, with an invoice for each period rather than an automatic charge, since nobody can debit a self-custody wallet on a schedule. Your backend issues the renewal invoice, reminds the user before the term ends and extends access when the payment webhook arrives.
How fast do I get paid?
A payment reaches your store balance about a minute after the user sends it — we wait for a masterchain block plus three confirmations and reconcile against an independent source. Moving that balance to your own wallet is a separate withdrawal request: it goes to your own wallet from the dashboard, passes automated anti-fraud checks and is signed by an isolated signing service.
What does it cost?
0.2% of each received payment, with the rate fixed when your store is registered, and no setup or monthly fee. Paysell pays the network fees on incoming payments. A withdrawal to your wallet carries its own flat fee of 0.7 USDT or 0.52 TON taken from the amount, with a minimum withdrawal of 25 USDT or 19 TON.
Which coins and networks are supported?
USDT and TON, both on the TON network, credited in the coin the user paid because nothing is converted in transit. Balances stay in the asset that was received, with no conversion between assets. Coming next: Tron.
How do I sync the purchase back into the app?
Treat it like any other server-side entitlement: the webhook writes the purchase to the user's account record, and the app picks it up on its next sync or refresh. Because the order id is yours, matching a payment to a user is one lookup, and repeated webhook deliveries should be handled idempotently.
Related solutions
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