The principles
Three rules apply to every product, and the specific rules for each product sit underneath them.
- Evidence, not timers. A refund decision is made on the order record and the confirmed state of the order. The expiry of a window is not, by itself, evidence of anything.
- Uncertain is not failed. When the final state of an order is not known, it is reconciled before anything is decided. An order is not refunded while its outcome is unknown, and it is not retried or replaced either.
- Separate the facts. A confirmed cancellation, a released hold and a completed refund are three separate facts with three separate timings. None of them implies another.
Verification numbers
A number order is refunded where the activation was cancelled and the cancellation was confirmed by the route, and where the route's rules for that activation do not exclude it. The specific route rules are published on the number route page and are repeated in the review you accept before paying.
It is not refunded where a code arrived. A message that arrives before a cancellation completes is a successful activation, and the code is shown to you and the order is never silently reversed. It is not refunded where the cancellation was refused because the activation was still inside its protected window, and the order remains active. It is not refunded where the activation timed out, unless the route's own confirmed state records the activation as failed or cancelled.
A second message that arrives is a further successful activation on the same order and is charged on the same basis as the first.
Telegram accounts
Every account route carries the same central risk: the issuing platform can restrict or remove an account at any time, for reasons that are not within the control of the seller or of this platform. That is not a seller failure and not a product defect, and it is excluded from a refund on every route.
Manual stock
Not refunded where the account was restricted or removed by the issuing platform, where the estimate of age turned out to be wrong, where the health classification was accurate when observed but the account later changed, or where the failure was caused by your device, your network or your proxy. It is reviewed where the delivered session file does not function as described, where the delivered account does not match the attributes shown on the listing, or where the origin shown on the listing cannot be substantiated.
Auto account delivery
This route has no published cancellation, resend or replacement entitlement, and no refund arises from a cancellation that was never offered. It is reviewed where the assigned number never produced a login code, where the delivered account did not match the country shown, or where the two-factor interaction described at purchase did not occur as described.
Global catalogue
This route delivers a number, not an account, and the number rules above apply. A refund is not available because a delivered number is not an account.
Global inventory
Not refunded where an account was restricted or removed by the issuing platform, where days offline was read as creation age, or where the item was refused for origin. It is reviewed where a listing was represented as having a password, email access, premium status or a health classification that the delivered item did not have, or where the delivered item did not match the country shown.
Social growth services
A service order that completes partially is charged for the delivered part and is not refunded for the remainder, because a remaining count is a normal outcome of a service, not a failure. Where a service fails outright, before any part of the work is performed, the unresolved portion is released in full.
A refill is a separate charge. It is not refunded as a matter of course if the original order subsequently completes, because the refill was a separate act. It is reviewed where the refill was refused by the service, and the outcome is shown on the order.
No service can promise a completion time, a delivery speed, a retention period, a reach figure or a platform-safe outcome, and no refund arises from an outcome that was never promised.
Bulk and readymade delivery
A bulk order is settled on its per-item outcomes. Confirmed items are charged. Items that failed are not charged and their hold is released. Items that are still being reconciled keep their hold until the state is resolved, and are then either charged or released.
No refund arises from a bulk order completing partially, because partial completion is an expected outcome of a multi-item order and is the reason the outcome is reported per item.
Source codes and panels
A digital product is reviewed per order against the version, the contents and the requirements declared in the product record. It is not refunded because the delivered version does not do something that was never declared, and it is not refunded because you preferred a different implementation of the same declared capability.
A panel is reviewed where the access record does not function, where the declared feature scope is not available, or where the declared setup requirements were not met. A panel whose access has been revoked following a breach of the acceptable use rules is not refunded.
Selling submissions
Submission does not guarantee acceptance and carries no refund, because nothing has been paid. A rejected submission keeps your account; what is lost is the review time. The credit is agreed at approval, and the amount agreed is the amount credited, so a credit below what you had in mind is not a refundable discrepancy.
Payments and wallet credits
Where a payment is made and evidence is matched, the credit is applied. Where evidence is matched but the amount differs from what was requested, the difference is not credited, and the difference is released, not retained. Where evidence cannot be matched, the payment is not credited, and the decision is communicated with the reason.
A wallet amount that has been held and then released is not a refund. It is the absence of a charge. Where an amount has been charged and a refund is due, it is returned to the same wallet, not to a payment instrument, and appears as a distinct ledger entry with its own reference.
Making a claim
A claim is made against the order, with the order reference. What is needed is the reference, what you expected, what happened and when. It is not needed, and must not be included, is your password, a banking one-time password, a UPI PIN, a session file or a mailbox password.
Claims are assessed against the order record, the terms version accepted at the time of the order, and the confirmed state of the order. A claim made after the underlying product has been superseded by a change in the supplier's behaviour is assessed against the terms that applied at the time of the order.
General exclusions
No refund arises from a failure caused by the receiving platform's enforcement, by your device, your network or your proxy, by a change in a third party's terms after delivery, by your own action such as changing two-factor protection incorrectly, by disclosure of your credentials to a third party, or by a use that breaches the acceptable use rules.
No refund is issued for a product that was delivered and then lost its value because the market moved, or because a platform changed its own rules, or because a supplier increased its price after delivery.