Accept Hamster Kombat (HMSTR) payments
HMSTR is the token of the Telegram game Hamster Kombat, issued as a jetton on TON, and a large number of Telegram users hold it. easyway accepts it next to Gram and the other TON jettons, on the same checkout, payment links and API. Below: which HMSTR counts, what paying looks like for the customer, and what holding a non-stable token means for you.
Token, network and limits
| Token | Network | Master contract | Confirmations | Smallest invoice | Fee taken from the payment |
|---|---|---|---|---|---|
| Hamster Kombat (HMSTR) | TON · Jetton | EQAJ8uWd7EBqsmpSWaRdf_I-8R8-XHwh3gsNKhy-UrdrPcUo | 1 | 3500 HMSTR | None |
This is the master contract that TON explorers list as the verified HMSTR jetton. Only transfers of exactly this jetton count; a look-alike token called "HMSTR" from another contract is ignored. Customers withdrawing from an exchange should pick the TON network there.
What paying looks like for the customer
HMSTR needs no setup of its own: it is paid to the TON address of your own wallet that you set on the Wallets page of the dashboard, the same one that receives Gram and the other jettons. easyway only watches it and cannot move what arrives. Every TON invoice goes to that one address and is told apart by a numeric memo (comment), so the address must be a wallet you control, not an exchange deposit address that needs a memo of its own. The checkout shows the address, the exact HMSTR amount and the memo, plus a QR code with a ton://transfer/… link that fills in all three and picks the HMSTR jetton, so a customer who scans it cannot forget the memo. The transfer needs a little Gram for the network fee, which the customer's wallet pays.
HMSTR was airdropped as a mintless jetton: a holder who has never moved their airdrop sends a proof with their first transfer that claims it, and wallets that support mintless jettons add that proof on their own. If a customer's wallet shows an HMSTR balance it cannot send, they need a wallet that supports mintless jettons. Nothing changes for you: your wallet receives an ordinary HMSTR transfer.
A payment counts only when two independent TON indexers both report the same amount, jetton and memo as a finished, successful transfer — that defeats forged jetton notifications. TON blocks are final, so this takes seconds. Transfers below 70 HMSTR (about a cent) are skipped as spam. A transfer without the memo, or with one that belongs to no open invoice, is parked as an unmatched transaction that you assign or ignore. Late and short payments follow the underpaid and late payments guide.
Price risk and costs
HMSTR's price moves. For a USD invoice the HMSTR amount is locked from the exchange rate when the customer chooses the coin; after the payment, HMSTR stays in your wallet as HMSTR, so later price moves are yours. Pricing an invoice in HMSTR itself (currency = "HMSTR_TON") skips the conversion.
No fee is taken from a payment: 100,000 HMSTR paid puts 100,000 HMSTR in your wallet. easyway earns from subscription plans instead. If you would rather end up with dollars, also offer USDT on TON and choose per invoice with allowed_assets. All coins are on the pricing page.
Integrating
Nothing is HMSTR-specific: set your TON wallet in the dashboard, then create an invoice through the API (or a payment link without code), redirect to the hosted checkout, and fulfil on the signed invoice.paid webhook. The quickstart has runnable examples, and the sandbox guide shows how to try the flow without real funds.
Common questions
Who holds the HMSTR? You do. It is paid to your own TON wallet; there is no balance at easyway and nothing to withdraw. easyway holds no keys and cannot move or recover coins, and refunds are sent by you from your own wallet; see security.
Which other TON coins are accepted? Gram itself, Notcoin, DOGS and Catizen (see Gram and TON jettons) and USDT on TON, all on the same address and memo flow.