Status of these terms
These terms describe a marketplace that is being configured. They are written to be read before trading begins, not after something has gone wrong, and they are marked as a draft because the commercial details that belong in them are not yet decided.
New accounts cannot be created under these terms yet, so ordering is limited to accounts that already exist. The sections that describe how trading works are drafted against the live behaviour, so what you are promised matches what Account Market does. Where a figure, a deadline or a jurisdiction is still open, it is labelled as pending and never filled in with a plausible value.
No payment is accepted, and no obligation to trade arises, while this document is marked as a draft. The version identifier and the date of your acceptance are recorded against your account when registration is enabled.
Who you are contracting with
Account Market is the trading name of an independent marketplace operator. The registered entity name, the registered address, the company or tax registration details, the jurisdiction and the governing law are not yet confirmed, and are published in this section before any payment is accepted.
- The registered legal entity and its registration number
- The registered address for service of notices
- The governing law and the courts or arbitration route
- The tax treatment applied to wallet credits and to any invoice
What Account Market is, and is not
Account Market operates a marketplace. It lists products supplied by third parties, it takes payment into a customer wallet, it records orders, and it provides delivery and support for those orders.
It does not operate, own, control or guarantee any third-party account, number, service or platform. It has no affiliation with, and no authority to speak for, any platform whose products appear in the marketplace. Where a product is delivered by a third party, the third party's own rules continue to apply to that product after delivery, and buying it here does not suspend them.
Where a supplier makes a representation about a product, that representation is a supplier statement. It becomes a commitment of Account Market only where these terms say so explicitly.
Accounts, eligibility and acceptance
An account is for a named individual or a named business, and it may be used only by that person or those people. Creating an account requires acceptance of these terms and an acknowledgement of the privacy policy. The two are separate, and neither is bundled with any marketing consent.
Acceptance is recorded on the server with the document version, the time and your account. A tick in a browser is not the record; the server entry is. Where a material change is made to these terms, the change is versioned, and where the change is material to your use of a product, you are asked to accept it again before the next purchase of that product.
You must be old enough to enter a contract where you live, and you must not be barred from trading by a law that applies to you. Verification of identity or of business is required before any withdrawal or a bulk arrangement is enabled, and the specific checks are published when they are configured.
Acceptable use
Every order is subject to the acceptable use rules, which are incorporated into these terms. Those rules prohibit fraud, impersonation, harassment, credential theft, the evasion of safeguards, and the acquisition of anything through deception or theft. A breach can suspend an account and can void a refund, and the specific grounds are listed on the acceptable use page, not hidden here.
Marketplace listings whose origin cannot be established are not offered, and are refused if they reach a buyer by another route.
Product-specific terms
Each product family has terms that apply to it alone. They are shown on the product page and repeated at the point of purchase, and the version of them accepted is recorded against the order.
Telegram accounts
Four distinct routes supply accounts, and they are not interchangeable. An account can be logged out, restricted or removed by the issuing platform after delivery, including without notice and without a reason being given to you. Where a route offers a session file, that file carries exactly the access of the account it came from and exactly as much remaining life. Where an account's age is shown, it is an estimate with its basis stated, and not a guaranteed creation date. Where an account's health is shown, it describes the account at the time it was observed. No route carries a guarantee of permanence, and no route can assure continued platform approval.
Verification numbers
A verification number is a reservation for one message, for one service, for one attempt. It is not an account. A reported count is a snapshot and not a reservation, and a number can be unavailable at the point of reservation even where a count was published seconds earlier. Cancellation availability, and the point at which cancellation can be refused, are determined by the route contract. A message that arrives before a cancellation completes is a successful activation and is charged, and the code is shown to you.
Social growth services
A service performs an action against a target you supply. Completion is not guaranteed, and a remaining count is a normal outcome, not a failure. A partial order is charged for the delivered part. A refill is a separate charge, available only for services that publish refill support. The rate basis for a service is shown with the quote, and a service description, start time, average time or duration that is not published by the service is not stated by us.
Bulk and readymade delivery
A bulk order can complete partially. Confirmed, reconciling and failed items are reported separately and are never presented as a single number. An item whose final state is uncertain keeps its hold until the state is resolved, and it is not replaced, retried or refunded automatically. A readymade account carries the same platform-enforcement risk as any other account.
Source codes and panels
You receive the version declared in the product record at the time of purchase, with the declared requirements and the declared licence. A download link is private, expiring and tied to your account. A panel is sold with an access record and a destination controlled by this platform; no third-party panel destination is advertised. A defect is assessed against the declared version, contents and requirements, and a difference of preference is not a defect.
Selling an account
You may submit an account only if you lawfully own it, can produce the credentials, and can truthfully declare its provenance. A false provenance declaration permanently bars you from the scheme. Submission is not acceptance, and acceptance is not a credit. The credit is a ledger entry recorded after approval, at the amount agreed at approval.
Prices, quotes and charges
A price is built from an upstream cost, a currency conversion and the most specific pricing rule that matches your selection. The rule that applied is recorded with the quote. A quote identifies the amount, the expiry, the selection it covers and the version of the terms it is made under, and it is binding until it expires.
Your charge is the confirmed quote, held in whole paise. A charge cannot increase without a new quote and a new confirmation from you. Bonus thresholds, if configured, are published before they apply, apply at settlement, change the amount credited, not the amount charged, and are never applied retrospectively.
Wallet, holds, capture and release
Your wallet holds available and held amounts as separate figures, and every movement is a ledger entry with its own reference. A hold is a reservation against an order that has not settled. A capture is a charge. A release returns a hold. A held amount is not a spent amount, and a released hold is not a refund unless it says so.
The balance you see is derived from the ledger. There is no separate balance that can disagree with it. Deleting your account requires the current password, your exact account name, a zero available balance, and no active order or pending deposit.
Payments and settlement
Only verified payment evidence credits a wallet. A payment that has been made is not proof that it settled. A browser redirect, a returned checkout page, an uploaded screenshot and a customer-typed identifier are all insufficient on their own, and none of them is a credited state.
Where a payment method is enabled, the exact credit amount and any fee or network rules are shown before the payment is created. A payment reference is bound to an order uniquely and atomically, so a reference cannot be claimed twice, and callbacks are idempotent, so a repeated callback cannot credit twice.
- The payment methods that will be enabled, and their fees
- The settlement arrangements used for each method
- The tax treatment applied to a credited amount
Delivery
Delivery is per product, and the format is stated on the product page before you pay. A session file is delivered through a private, expiring, owner-scoped download. A number and code are shown in the order view. A service result is shown as a status with a remaining count where one is reported. A digital product is delivered as an expiring download. A panel is delivered as an access record.
Every delivery is tied to the order and to the account that placed it. A delivery cannot be transferred to another account, and a copied link grants nothing to somebody else. Delivery data must not appear in a public review, a public listing or a public message.
Cancellation, refunds and exclusions
Refund rights are set per product, and the refunds page states them in full. The general position is that a confirmed cancellation and a released hold are separate facts, and that a refund is decided on the order record and the evidence for that order, never on a timer alone.
Refunds are generally excluded where the failure was caused by the receiving platform's enforcement, by your device, your network or your proxy, by a change in the third party's own terms after delivery, or by your own action such as changing two-factor protection incorrectly or sharing a session. Exclusions are shown on the product page before you pay, not discovered afterwards.
Disputes
Disputes are handled against the order record, with the order reference, the timeline and the terms version accepted at the time of the order. Where a supplier decision is disputed, the supplier's recorded state is obtained and reviewed. Where the dispute cannot be resolved on the record, it is escalated to a reviewer who is not the person who handled the original request.
- The dispute route, including any external mediation provider
- The response times for each stage of a dispute
Changes to these terms
These terms are versioned. A change that is material to your use of a product requires renewed acceptance of the new version before your next purchase of that product. A change that is not material is published with its effective date and does not require a new acceptance. Previous versions remain available on request, so a dispute can always be assessed against the version that actually applied.
Liability
Nothing in these terms limits liability that cannot lawfully be limited. Subject to that, and to the product-specific terms, liability arising from a product that is subject to third-party enforcement is limited to the amount you paid for that order. This platform does not control third-party accounts, and it cannot make a promise about a decision made by a third party.
- The final liability cap and any carve-outs the business will accept
- The process for claims brought in a jurisdiction other than the governing law
Contact
Support and abuse channels are published once they are confirmed. Until then, no unverified address is listed, because a published but unmonitored address is worse than an acknowledged gap. Order and payment references are the identifiers used in every communication, and a support request never needs your password, a banking one-time password or a UPI PIN.