Refund Policy
Our refund and warranty terms, stated plainly. Please read this entire page before placing an order. By paying for an order, you accept these terms.
What you are agreeing to.
Accounts are verified as alive and accessible before delivery, and we keep delivery-time verification records. The warranty covers accessibility and ban status at delivery time only. After successful delivery with no ban issue present, there are no refunds, replacements, or cancellations. The full terms below spell out exactly what that means.
Pricing, Delivery and Refund Policy
1. Pricing
All prices are listed per account. The accepted payment method is USDT only.
2. Supported delivery formats
- Session + JSON
- TData
3. Account verification and warranty scope
The warranty covers account accessibility and ban status based on delivery-time verification only. All accounts are verified as alive and accessible prior to delivery, and delivery-time verification records are kept.
Accounts are digital and copyable products. If no ban issue is present based on delivery-time verification, no refund or replacement is supported after successful delivery.
Once payment is completed, orders are considered confirmed and enter the processing and verification stage. Orders cannot be canceled due to the buyer's change of mind.
4. After-sales window
After-sales support is available within 24 hours from the time the account files are sent to the buyer. This period serves solely as a claim and verification window.
5. Test order recommendation
Buyers are strongly recommended to start with a small test order (minimum 10 accounts) before proceeding with large-volume purchases. After confirming stability, compatibility with your environment, and suitability for your specific use case, bulk orders can be arranged.
Why the policy is strict.
Digital account files can be copied the moment they are received. That single fact shapes the entire policy. Once files are in a buyer's hands, there is no way to verify whether an account was used, shared, or run through automation that triggered a restriction. A refund policy that ignored this would not survive its first dispute, so we state the limits up front instead of burying them.
What we can stand behind, we do: every account is checked for accessibility and ban status before it is sent, and we keep the verification records. If an account was already dead or banned at the moment of delivery, the 24-hour after-sales window is your channel to report it with specifics, and that claim will be judged against the delivery-time record.
What we cannot stand behind is what happens after delivery. Login environment, proxy quality, device setup, and behavior after login all affect whether an account stays alive, and all of them are in the buyer's hands. Telegram's own risk controls can restrict any account regardless of who sold it. No seller can warranty against that, and we will not pretend otherwise.
The practical takeaway: test with 10 accounts, confirm they are stable in your environment, and only then scale. That recommendation is in the policy itself because it is the single best protection a buyer has.
How to file a claim inside the window.
If an account was dead, banned, or inaccessible at the moment of delivery, report it within 24 hours of the files being sent. A claim needs three things to be actionable: which account (identify it from the file name or JSON metadata), what you observed (exact error or behavior), and when you observed it. Vague reports like "some accounts don't work" cannot be checked against the delivery-time record and will stall.
Valid claims are judged against the verification record kept for your order. If the record shows the account was alive at delivery and your report shows it dead on arrival, the discrepancy is investigated. If the record and your report agree that the account was healthy at delivery, the issue arose afterwards and falls outside the warranty.
What is not covered
- Accounts banned or restricted after successful delivery, regardless of cause.
- Session invalidations or login issues caused by the buyer's environment, IP changes, or device switches.
- Lost, deleted, or corrupted files after delivery.
- Orders the buyer changed their mind about after payment.
- Delays caused by the buyer, such as late payment or missing order details.
This list is not here to be adversarial. It exists because every item on it has been disputed before, and settling the boundaries in advance is fairer to both sides than arguing them after the fact.
When in doubt about whether something is covered, ask before you pay. A two-minute question in the Telegram chat is cheaper than a dispute after delivery, and we would rather turn away an order with mismatched expectations than take money for one.