Digital services, completed safely in one place.

1. Confirm that the bot came from a store entry you trust, then send /start.
2. Select Chinese or English and read the service rules shown to you.
3. Read the service rules, then follow the current screen to select a language and continue. Review the product conditions and payment confirmation for each purchase.
4. Return to the same bot later. Do not switch stores because of an unfamiliar private message.

General USDT product totals are quoted in 0.01 USDT increments and displayed with two decimals. Quantity is applied before rounding the total; historical orders, refunds and ledger records retain their original precision. Dedicated Premium and Stars quotes still follow their own confirmation screens.

Social services show the total for the minimum order quantity, then recalculate for the quantity entered. A reference unit price is not the minimum payable total.

After opening Featured Services, browse by menu category or search supported catalogs by country, region, calling code, name or keyword.

Before every payment, confirm at least:

• the product, specification, destination account, link or address, and quantity;
• the usable region, validity, stock, order range and conditions;
• the current unit price, total, payment currency and expected delivery method; and
• whether cancellation, refill, renewal or refund is available and under what limits.

What to check in each Menu Center entry

1. Open Personal Center → Funds Center → Deposit.
2. Choose only a deposit method currently shown and create a new order for every deposit.
3. Verify the order number, network, currency, full address, exact amount and expiry before paying.
4. Return to the order or bill after payment. Do not pay again while the screen is waiting.

USDT and TRX are separate balances with separate bills. Never use one currency's balance, payment address or amount as the other. A bot balance is an internal balance in the current store, not an on-chain wallet whose private keys you control.

Payment-platform deposits

1. Select a payment platform shown on the current screen and create an order.
2. Open only the payment entry created for that order and verify the amount.
3. A successful payment page does not by itself prove that the bot balance was updated; return to the bot and check the order and ledger.
4. If a callback is delayed, wait for order lookup. Do not create and repeatedly pay another order for the same amount.

TRON on-chain deposits

1. Select USDT or TRX first; the two cannot be mixed.
2. Copy the complete address and exact amount from the current order and confirm the TRON network.
3. Send one transfer only, do not alter decimals, and do not reuse an old order.
4. Keep the TXID, wait for chain finality, then check the bill for that currency.

No Personal Center withdrawal

Personal Center has no balance-withdrawal entry. Do not trust a private message, link, QR code or address claiming to withdraw a personal store balance. Agents may withdraw eligible business profit only through the separate profit-withdrawal flow in their own Agent Center, subject to that flow's currency, amount, address and review rules.

1. After entering the destination details, read the final confirmation shown by the bot.
2. When paying from a balance, enter the six-digit payment password configured in Personal Center.
3. Some balance purchases within the password-free limit may complete directly; changing that limit still requires the payment password.
4. Wait for an order number and the debit result before leaving the screen.

If a message times out, the screen stalls or the result is unclear, check Personal Center → Orders & Bills and the bill for the payment currency. Do not click Pay again or create another order for the same destination.

Interpret the payment result correctly

Service-channel login recovery and availability checks have improved, with order intake restricted when a channel is unhealthy. Verified Premium delivery receipts feed into order completion and profit notifications promptly.

Payment success is not delivery confirmation. Check the original order when it is processing or under review; a delayed notification is not a reason to pay again.

• Personal Center → Orders & Bills → My Orders shows progress for orders in the current bot.
• Awaiting Delivery / Awaiting Receipt shows delivery for store virtual or physical products.
• A 24-hour automatic-confirmation window begins only after successful virtual delivery; inspect and confirm earlier if appropriate.
• A seven-day automatic-confirmation window begins after a physical product ships; inspect tracking and the item first.
• Do not repurchase while an order is processing or under review. Keep its order number and wait for the result.

Common order states

1. Confirm that the phone supports eSIM and is carrier-unlocked.
2. The actual destination must appear under Works in; Exit IP and card origin do not determine where the plan works.
3. Confirm allowance, validity, plan type and price. A data plan has no number; a registration plan normally shows its number after activation and does not guarantee registration on every platform.
4. Install over stable Wi-Fi by scanning the QR code or entering the LPA manually. At the destination, enable data roaming and keep network selection automatic.
5. A successful delivery includes a QR code or directly usable LPA. ICCID appears only when returned. A missing ICCID does not block LPA installation, but lookup or renewal that depends on ICCID must wait until it is available.
6. Never publish the QR code, LPA or ICCID, and do not casually delete an installed eSIM.
7. Renew only when the screen says the card is eligible. Renewal replaces the old package and may discard remaining data.

Mainland-China, Hong Kong, Macao and international device variants can have different eSIM capabilities. A programmable physical eUICC card for a phone without native eSIM also depends on the writer, software and exact phone model. Read the eSIM device, coverage and installation guide before payment.

If the eSIM cannot connect

1. Confirm that you are at a covered destination and the package remains valid.
2. Confirm the eSIM is enabled, selected for mobile data and has data roaming enabled.
3. Keep network selection automatic, wait a few minutes, then toggle airplane mode or restart.
4. Do not edit the APN unless the current screen expressly tells you to.
5. If it still fails, keep the model, location, error screenshot and order number for support.

View your cards in the bot

eSIM Center can show your delivered cards, status, remaining data, expiry and registration-card number. A registration plan normally returns its number only after activation; a data-only plan never has a number. Cross-bot recovery verifies the same Telegram UID and never returns another user's card.

TG account products are grouped by region, calling code, account age, number attributes and stock. Delivery may include TData, Session + API, direct-login data or another combination shown on the product screen. Download, inspect and back up the files offline immediately; never publish or forward them.

Other virtual products may deliver a key, account, text, link, file, file plus key or an automated result. Rely on the delivery type shown in the order and perform a practical basic check before confirming receipt.

TRX and GRAM use a quantity-based purchase flow with both unit pricing and the corresponding conversion amount. Reciprocal rate displays describe the same quote; they do not enable reverse exchange.

The GRAM minimum purchase is configured as a USDT amount. Check the current purchase screen for its minimum, stock and limits; previews follow the executable cost floor.

Store-specific shared-energy receiving addresses and compatibility with older address records have improved, along with the flash-rental layout and tap-to-copy addresses. Read the current service screen again for each operation.

• Before buying TRX, verify the destination, payment asset, quote, fee and estimated receipt. Obtain a new quote after expiry.
• GRAM purchases use only the current bot's USDT balance. Verify the TON mainnet address, live unit price, stock, limits and short-lived single-use quote.
• Before buying Energy, verify the destination, resource amount, validity and estimated transfer count. Correctly delivered on-chain resources are normally irreversible.
• If a flash rental requires native TRX from the Energy destination, follow the current screen exactly and do not use an unsupported third-party payer.
• Address lookup can show 23 mainnets, while monitoring is available only on networks currently enabled on its own screen. Read the address-monitoring rules.
• Lookup and monitoring read public blockchain information only. They never need a private key and cannot control or transfer assets.

• Set or update the six-digit payment password under Personal Center → Account Security.
• Back Up Account protects your personal identity, USDT/TRX balances, payment settings and personal orders in the current bot.
• Store the recovery key offline and separately from the payment password; the system cannot recover its plaintext for you.
• Account recovery requires the original UID, original payment password and custom recovery key, followed by at least a 24-hour cooling-off period and manual review.
• During review, deposits, balance purchases, new orders and related balance operations for the account are paused.

Personal Center paths

1. Return to the bot where the order or deposit occurred and tap Contact Support.
2. Describe the issue and provide the order number, time, destination details and necessary screenshots; include the TXID for an on-chain issue.
3. Redact unrelated personal data. Never send a payment password, code, private key, seed phrase or recovery key.
4. An authorized handler claims the support ticket and closes it after resolution. Start a new ticket for a new issue after closure.
5. The support bot may first answer common questions or look up only the current Telegram user's own orders; uncertain issues move to a human ticket.

Prepare the right evidence

• I am in the original store bot and did not follow an unfamiliar private message to another entry.
• I verified the product, destination, region, quantity, price and currency.
• My deposit uses a newly created order, not an old link, address or amount.
• I entered sensitive data only in the bot's built-in flow, never in a support chat or with a third party.
• If a result is unclear, I will check orders and bills instead of paying or ordering again.

Open 🤖 Agent Center in the current store. If you do not yet own an agent bot, the page shows the application guide and the creation methods currently available to you.

1. Use the native Telegram creation entry when it is available.
2. In Telegram, choose a display name and a username ending in bot.
3. Return to the application flow and submit the bot as instructed. Use the Token-compatible method only when the native entry is not supported by your client.
4. If an authorization fee applies, use only the amount and payment method shown on the current confirmation page. Complimentary or free authorization depends on the page status.
5. After setup completes, open the new bot and send /start.

Application statuses

Bot authorization and deployment completion now have a notification and agent-guide entry. Existing agents can reach their own store more directly from the platform entry.

When you open Agent Center from a parent store, the page can show the agent bot you already own and an entry such as Open @your_bot. Open that bot first, then use its own 🤖 Agent Center to manage the business.

Customer data, customer orders, pricing, inventory, profit, support settings, order notifications and start messages should all be managed from the bot they belong to. Full-bot backup and recovery protect the agent bot; personal balances and personal orders remain separate in Personal Center.

Five checks for a new agent bot

1. Confirm that the chat header shows your own bot username.
2. Send /start and verify the language, rules and main menu.
3. Open Agent Center and confirm the bot identity, reporting timezone and business-data ownership.
4. Review pricing and Product Listings so that unpriced or unwanted products are not presented accidentally.
5. Configure support and the start message, then test browsing, ordering and support from an ordinary customer account.

The home page summarizes the current bot's users, orders, sales, profit by asset, products and agent network. Its main functions are grouped into the sections below.

How to read the summary

• Users shows today's, monthly, yearly and total user counts.
• Orders shows customer orders for this bot and supports status-based pages.
• Profit Details separates USDT and TRX allocation, available balance, pending withdrawals and ledger entries when those assets are enabled here.
• Agent Network shows direct children and the complete descendant hierarchy.

Recommended order-review sequence

1. Open Orders and review the total and status counts.
2. Filter processing, abnormal and completed orders to find the cases that need attention.
3. Open an order and verify the customer, product, amount, creation time and latest progress.
4. For owner-fulfilled products, use the Fulfillment Queue to deliver or ship the matching order.
5. For a refund or profit discrepancy, compare the order with Profit Details and the related ledger entries.

Agent price changes refresh the catalog and purchase quotes promptly, with improved downstream Premium and Stars synchronization. Bulk changes preserve individual and fixed rules; parent-cost changes may still affect the executable price under those rules.

Open Products & Fulfillment → Pricing and read the chain in this order:

Cost (read-only) → downstream agent price → customer sale price

• eSIM, Telegram accounts, traffic services and other standard products can be priced together with a percentage rule.
• You can also price a product group, subcategory, search result or individual item.
• The all-products action uses percentage markup. Use a narrower scope for an exact price.
• The downstream price cannot be below cost. The customer price cannot be below the downstream price or the direct parent bot's current public sale-price floor.
• Percentages are calculated from the current basis shown by the flow, not added to an old saved price.
• Two percentage stages compound along the price chain; they are not added together. A 20% stage followed by 30% produces a 1.2 × 1.3 factor.
• After the first markup is entered, the page previews the next stage's current minimum valid markup and a recommended value that can be applied directly.
• If a value is too low, nothing is saved. The bot explains the failing constraint and, where calculable, shows a minimum valid price or percentage that can be entered directly in the active step.
• The applicable prices and fees are locked from the actual customer price when the customer pays.
• GRAM has separate pricing and availability controls. Customer purchase appears only when the current bot's page confirms that pricing, inventory, limits and payout readiness are available.

Pricing scopes

Pricing workflow

1. Select a scope and review the product count shown by the bot.
2. Set the downstream agent price with a percentage, or an exact value where the selected scope permits it.
3. Review the displayed minimum and recommended customer markup; use the recommendation directly when it matches the intended margin.
4. Set the customer sale price and keep it above every displayed floor.
5. If the bot returns a minimum valid retry value, review the reason and re-enter that value or a higher one in the current step; cancel and narrow the scope if one bulk rule is unsuitable.
6. Review the affected range, old values and new rule on the final confirmation page before saving.
7. After saving, sample a standard product and an exception, then confirm their Product Listings status.

• ➕ List Product creates an agent-owned product by selecting its product type and delivery mode, then entering name, cost, downstream agent price and customer sale price.
• 📤 Product Listings lists or delists eligible products by group, subcategory or item, with name and SKU search for exceptions.
• Agent-owned products remain under their owner's listing control and can be made available to child agents where the current product status permits it.
• A platform catalog product still needs its Product Listings state confirmed after pricing. A newly created agent-owned product also needs complete inventory or delivery material before customers can see it.
• 📦 Inventory stores virtual inventory and automatic-delivery material.
• 🚚 Fulfillment Queue contains orders that require the product owner to deliver a virtual item or ship a physical item.

Virtual delivery may use a code, account, text, link, file, file plus code, or another delivery mode shown by the submission flow. Choose only a mode you can fulfill completely. A virtual order enters its post-delivery confirmation period only after successful delivery; a physical order follows the shipping and confirmation timing shown by the current order page.

Submit an agent-owned product

1. Open List Product and choose Virtual or Physical. For a virtual item, also choose its fixed delivery mode.
2. Complete the four steps: name, cost, downstream agent price and customer sale price. Cost must be no higher than agent price, which must be no higher than sale price.
3. Final confirmation immediately places the product in the owner's listing.
4. For a virtual product, complete the required codes, account details, text, links, files or other selected delivery material. Missing required material keeps it hidden from customers.
5. For a physical product, maintain available stock and provide the carrier and tracking number when fulfilling an order.

Inventory and delivery standards

Fulfillment Queue

1. Prioritize paid orders that are waiting for delivery.
2. Before sending virtual material, match the order number, customer and product.
3. For a physical product, verify the delivery details and record the carrier and tracking number.
4. If the result is uncertain, keep the order under review and do not send the same item again.

• Support Settings configures the support entry shown by this bot.
• Announcement composes a message for eligible active users of this exact bot.
• Start Message controls the introduction and buttons shown after /start.
• Order Notifications binds a verified Telegram group and selects the order categories that group may receive.
• Child Cloning controls whether future customers may submit new child-bot applications from this bot.

Rich announcements

1. Set the announcement text and, where needed, an image, video or GIF.
2. Add message buttons and preserve supported Telegram Premium custom Emoji when they are part of the draft.
3. Use Full Preview to inspect the complete message, media and buttons before publishing.
4. Editing updates only the draft. The announcement enters the send queue only after the final confirmation.
5. The current bot sends only to its eligible active users; the bot owner is not counted as a recipient. Review the sent, pending and undeliverable totals after queueing.

Order-notification group and categories

Bind or replace the notification group through the Agent Center, complete the group and bot-owner permission check, then send a test notification. The page displays whether notifications are ON or OFF and the order scope currently available to this bot.

Each category can be enabled or disabled independently. A bound group does not override bot ownership or order scope; use only the scope and switches shown on the current settings page.

A completed-order notice includes product detail and quantity where safe, plus amount, payment method and completion time. Sensitive recipient, account and target identifiers are omitted.

Co-administrators

1. The original administrator may add up to five co-administrators. A candidate should send /start to the bot first.
2. A co-administrator receives the same Agent Center business permissions, including products, pricing, orders, fulfillment, profit withdrawals, backup and recovery, permanent disable and administrator management.
3. The original administrator remains the non-removable identity anchor. Adding or removing a co-administrator requires the acting administrator's own six-digit payment password.
4. Removal takes effect immediately. A removed administrator cannot continue pending sensitive actions, and their recovery authority and pending recovery flow are invalidated.

Three-level start-message inheritance

1. A custom start message saved for this bot has highest priority and remains independent.
2. If the bot has no custom message, it inherits the current platform default, including the MBOTJ official-website button when provided.
3. If no platform default is available, the built-in system default is used.
4. Editing inherited content creates a custom message for this bot; existing custom messages remain unchanged and another bot is not rewritten.

Keep the start message concise. Buttons may point to store menus, Personal Center, support, Agent Center or verified HTTPS pages such as the official website.

• When enabled, customers can apply from this bot's Agent Center with their own Telegram accounts.
• A successfully created bot becomes a direct child of the bot where the application began.
• An agent bot owner cannot submit the application on behalf of a customer.
• Each child may allow its own customers to apply, so the agent hierarchy has no fixed depth limit.
• Turning cloning off blocks only future applications. Existing child bots and already-submitted applications are not deleted or cancelled.
• Both enabling and disabling require confirmation.

Profit summaries and details are grouped by USDT and TRX, with improved owner and agent attribution and refund reversals. Match profit entries to the original order and distinguish available profit from pending withdrawals.

1. Open Data & Orders → Profit Details.
2. Review cumulative allocated, available and pending balances separately for USDT and TRX when those rows are available in this bot.
3. To withdraw, select an asset offered by the current page and verify the destination, amount and fee.
4. Track the request through Profit Details and Withdrawal Details. A profit reversal related to a refund appears as a negative entry.

Match profit and withdrawal records

Withdrawal workflow

1. Select USDT or TRX only if that asset is offered by the current Agent Center page.
2. Enter and recheck the destination address.
3. Enter the amount and review the fee, total hold and expected payout.
4. Complete the payment-password check, submit once and keep the request number.
5. Follow Withdrawal Details and do not submit the same amount again while it is processing.

Bot Management provides Back Up Bot Data and Recover Bot. A full-bot backup protects the agent bot's customers, orders, products, business configuration, ledger ownership and child hierarchy.

A recovery application requires:

1. the bot manager's Telegram UID;
2. the bot username;
3. the bot's independent backup key; and
4. the six-digit Personal Center payment password of the account that configured the backup.

Passing those checks and validating the replacement bot submits a recovery application; it does not immediately change the original bot. The request waits at least 24 hours and requires manual review. Personal balances and personal orders still use Personal Center recovery separately.

Back up before operating

1. Open Bot Management → Back Up Bot Data.
2. Choose a dedicated bot backup key that is different from a personal account recovery key.
3. Record the bot manager UID, bot username and the personal account used for backup verification.
4. Store the backup key offline and never send it to customers, groups or support chats.
5. After an important bot-manager or bot change, revisit the page and confirm the backup status.

A cloned bot can be permanently disabled only from its direct parent bot's Agent Center and only after explicit confirmation. After completion, the bot cannot be recovered, re-enabled or recreated under its old identity.

Users, balances, orders, ledger entries, product prices, backup data and recovery records remain as read-only history for review, but they do not provide a path to resume operation.

• Confirm that you are operating inside @your_bot.
• Review order, profit, inventory and notification exceptions before publishing or repricing.
• After changing a price, verify the Product Listings status.
• Keep virtual inventory usable and process owner-fulfilled orders promptly.
• Preview announcement media and buttons before final confirmation.
• Test the bound order-notification group after changing its scope or categories.
• Review USDT and TRX profit separately and withdraw only through the assets offered by the current page.
• Keep the bot backup key offline and separate from personal recovery credentials.
• Confirm permanent disable, bulk pricing and child-cloning changes carefully.

• Verify the software, exact service name, required target type, complete HTTPS link, minimum and maximum quantity, customer unit price, total, and any explicit refill or cancellation marker.
• Similar names may carry different speed, quality, geography, duration and after-sales conditions. Old screenshots, earlier quotes, chat summaries and another store's page do not replace the current confirmation screen.
• For a new platform or service type, place a small test order first and confirm link recognition, counting and fit before scaling.
• Entering the payment password confirms the selected product, target, quantity, price and these rules. A buyer cannot demand an unconditional refund merely for not reading the rules, choosing the wrong product or entering the wrong target.

• You must own or manage the target, or hold lawful authorization from its rights holder, and ensure the use complies with the target platform's rules and applicable law.
• The submitted link must be complete, accurate, accessible without login and point directly to the post, video, channel, group, page or profile required by the product.
• From payment until final status, keep the target public and accessible. Do not rename it, change its link, make it private, delete content, close comments, add geographic or age restrictions, remove member access or otherwise obstruct fulfillment.
• MBOTJ processes only the target finally confirmed by the buyer and does not guess, search for, replace or correct it. A link opening successfully does not prove that its target type matches the selected product.

• Where available, the order may show a starting count and remaining quantity. A starting count supports review but may differ from a buyer screenshot because of page caching, collection time or regional display differences.
• Concurrent identical or similar services, organic gains or losses, other promotions, target-platform cleanup and statistical corrections all affect the observable difference.
• Unless the product expressly says otherwise, completion is assessed from the MBOTJ order record, target accessibility, service execution record and reviewable target-platform changes together—not from one screenshot selected by the buyer.
• A target platform may publish metrics in batches, update them late, hide some counts or show different values to different viewers. A short-lived display difference is not automatically non-delivery.

• Start speed, daily speed, estimated completion or similar wording is a normal-condition reference and may be affected by target state, maintenance, rate limits, review, algorithms and network delay.
• MBOTJ does not promise permanent retention, permanent availability, a fixed retention rate, search ranking, recommendation traffic, interaction quality, organic conversion, sales revenue, verification or official endorsement.
• Followers, members, views, likes, reactions, comments, shares and live audiences may decrease or be recalculated because of user behavior, target-platform cleanup or statistical changes.
• Only attributes expressly shown for the product form part of the service. Geography, gender, language, activity, source, content or duration not shown on the confirmation screen is not promised.

• An order may enter processing immediately after successful payment. Unconditional cancellation, target replacement, product exchange and quantity change are normally unavailable.
• A “cancellation supported” marker means a request may be reviewed under the order's current conditions; it does not guarantee cancellation. Quantity already started, partially completed or completed is not automatically reversed.
• A definitive system rejection, cancellation or confirmed non-delivery is refunded according to the final order status. An uncertain payment or submission result stops automatic retry and enters review to prevent duplicate execution.
• Partial delivery, count disputes and uncertain results require manual review. MBOTJ may provide completion, refill, a refund for the confirmed unfulfilled scope or another reasonable solution; a full advance refund is not promised.
• Wrong links, inaccessible targets, buyer changes, concurrent duplicate orders, target-platform restrictions, prohibited content or buyer conduct are not MBOTJ delivery failures, and execution cost already incurred is non-refundable.

• The product must have displayed a refill marker before payment, and the request must remain inside its applicable period and satisfy its conditions. A product without that marker carries no drop-replacement service.
• Refill review addresses a verifiable reduction after fulfillment. It is not permanent maintenance, unlimited replenishment or a guarantee to restore any count selected from a buyer screenshot.
• MBOTJ may reject refill where the target was renamed, made private, deleted, blocked or restricted; concurrent orders cannot be separated; or continuous evidence is unavailable.
• Refill timing and outcome remain subject to these target, counting and platform rules. A refill request does not pause unrelated order deadlines.

1. Report promptly: raise a basic quantity, target or status dispute through the originating store within 24 hours after the order becomes final. A refill request follows the product's stated period.
2. Identify the order: provide the order number, product name, purchased quantity and complete target link—not only a nickname, cropped link or verbal description.
3. Preserve continuous evidence: provide uncropped screenshots or a recording showing device time, complete target, public status, metric screen and the operating sequence. Keep continuous before-and-after records where reasonably needed.
4. Keep the target unchanged: do not delete, privatize or rename it, or add the same service, before review is complete; otherwise the disputed scope may become unverifiable.

• Fraud, harassment, infringement, impersonation, deceptive commercial claims, spam, illegal content, evasion of platform enforcement and manipulation of elections, public events or public opinion are prohibited.
• The buyer is responsible for target content, authorization, promotion purpose and its own business conduct. MBOTJ may reject, pause or terminate service where it finds illegality, a rights dispute, security risk or clear abuse.
• A target platform may independently remove metrics, restrict content or act against an account. That action is outside MBOTJ's control and is not automatically a breach or refund basis.
• These rules do not exclude rights that cannot lawfully be excluded. If one term cannot be enforced, the remaining terms continue to the extent permitted.

• Submit and verify the complete Telegram username, spelling, characters, term and price.
• A display name, avatar, phone number, forwarded message or similar username does not replace the unique username. MBOTJ does not guess or correct the recipient.
• Confirm that the recipient's account works and that the recipient agrees to receive Premium.

• The screen may show 3-, 6-, 12-month or other currently enabled terms. A hidden or paused term is unavailable.
• Recipient, term, unit price, quantity, total and payment asset shown at confirmation form the order. Old or other-store prices do not apply.
• Entering the payment password completes the buyer's final check and authorizes platform processing.

• Region, account type, existing membership, privacy, safety status or Telegram rules may prevent receipt.
• A recipient who renames, disables, deletes or restricts the account after ordering may cause failure or delayed verification.
• Telegram defines the included benefits and regional availability. MBOTJ does not promise those rules remain unchanged forever.

• Review every username and term. If batch creation fails, it does not leave a partially created batch charge.
• After successful creation, each recipient is fulfilled individually and may be complete, pending or failed independently.
• An issue for one recipient is resolved only for that verified scope and does not reverse recipients already completed correctly.

Order intake pauses when the service channel is unhealthy. Verified Premium delivery receipts update the order and related notifications. Payment success or notification timing alone does not prove delivery or justify a repeat payment.

• Any displayed estimate is a reference under normal conditions, not a guaranteed completion time or automatic-refund trigger.
• An order may be pending, processing, complete, failed or under manual review. The final verifiable status controls.
• An uncertain result stops automatic repeat purchase. Do not reorder merely because a message or benefit display is delayed.

• Processing may begin immediately. A wrong username, wrong term, recipient regret or unread rule does not create unconditional cancellation.
• An automatic refund applies only when the platform confirms the order was unsigned, unsubmitted and finally failed with zero delivery.
• A submitted, started, completed, partly completed or unknown result is reviewed first. Completion, partial refund or another reasonable outcome follows the verified scope; an automatic full refund does not apply.
• Correctly activated Premium is not refunded because it is unused, the account is later restricted or Telegram changes benefits.

1. Provide the original-store order number, recipient username, purchased term and current bot status.
2. For a batch, identify the exact affected usernames rather than stating only that some did not arrive.
3. Provide uncropped screenshots or recordings showing username, device time, Premium state and the complete flow.

• Premium purchase never requires a recipient code, password, two-step verification or device control.
• Obtain recipient consent and do not use the service for harassment, impersonation, fraud or unlawful conduct.
• These rules do not exclude rights that cannot lawfully be excluded.

• Submit the complete Telegram username. A display name, phone number, avatar or similar account does not replace it.
• Verify every character and the account on the confirmation screen. MBOTJ does not search, guess or correct the recipient.
• Confirm recipient consent and keep a record of the agreed username before payment.

• Available tiers, limits, unit price, total, payment asset and status follow the current store confirmation screen.
• Old quotes, other-store prices, chat descriptions or recipient expectations do not change the confirmed order.
• Entering the payment password accepts the username, quantity, price and these rules.

• Region, account type, age, safety state, privacy settings or Telegram restrictions may affect receipt.
• Renaming, disabling, deleting or restricting the account after order can cause failure or delayed verification.
• Ineligibility alone does not establish failed platform delivery; submission status, reason and zero-delivery facts must be reviewed.

• Spending, gifting, withdrawal, conversion, creator settlement and other uses depend on Telegram's current features, region and account eligibility.
• MBOTJ does not promise use with a specific bot, channel, product, game or monetization route, or that Telegram rules never change.
• After correct delivery, later use, accidental spending, account restriction or feature change is not short delivery.

• A displayed estimate is a normal-conditions reference and may change with account and Telegram state.
• An order may be pending, processing, complete, failed or under manual review. Delayed messages or display refresh do not by themselves mean failure.
• An uncertain result stops automatic repeat purchase. Review the original-store order before any retry.

• Processing may begin immediately. A wrong username, wrong quantity, recipient regret or unread rule does not create unconditional cancellation.
• An automatic refund applies only when the platform confirms the order was unsigned, unsubmitted and finally failed with zero delivery.
• A submitted, started, completed, partly completed or unknown result is reviewed first. Completion, partial refund or another reasonable outcome follows the verified scope; an automatic full refund does not apply.
• Correctly delivered Stars are not refunded because they remain unused, have limited use, change perceived value or the account later changes.

1. Provide the original-store order number, complete username, quantity, balance ledger and current bot status.
2. Provide uncropped screenshots or recordings showing username, device time, Stars view and complete steps.
3. Keep the username stable and do not add overlapping purchases during review.

• Stars purchase never requires a code, password, two-step verification or device control.
• Do not use the service for fraud, laundering, restriction evasion, non-consensual purchase or unlawful activity.
• These rules do not exclude rights that cannot lawfully be excluded.

• Check country or region, calling code, account age, number attributes, live stock, quantity, customer price and delivery format. Similar product names do not guarantee the same specification.
• For a first purchase or an unfamiliar format, buy a small quantity and complete the download, import, login, backup and business-validation flow before ordering in bulk.
• Prepare a stable, lawful device and network under your control. Do not wait until after purchase to introduce many devices, rapid network changes or unknown automation.
• Make sure you can safely open ZIP files, import TData or Session material, store API data and protect two-step-verification information.

• All three bundles must belong to the same order batch. Stop if a file is missing, empty, damaged, short in quantity or visibly mismatched.
• Save them immediately to encrypted storage or an offline backup you control. A chat, temporary download folder or single device is not a durable backup.
• Keep one untouched copy with original names and archive structure for delivery-integrity review.
• Phone numbers, Session, JSON, TData, API data, two-step verification and recovery data are sensitive credentials. Never post or hand them to an untrusted remote operator.

1. Record the order: keep its number, product, purchased quantity and complete-delivery time.
2. Inspect the files: verify that all three arrived, open or extract correctly, are non-empty and contain matching quantities and batches.
3. Run a basic check: use one stable environment and the delivered method. Bulk orders require item-level inspection; one successful sample does not prove every item.
4. Stop on failure: do not rotate networks or devices, repeatedly import, change the phone, email, password or two-step verification, or continue bulk automation.
5. Contact support within 30 minutes: provide the order number, affected quantity, file or redacted identifier, complete error and continuous screenshots or recording that show the relevant process.

• API.txt, Protocol.zip or Direct-login.zip was not sent, is empty, damaged, unreadable or cannot be extracted.
• Bundle quantities do not match the order, or Session, JSON, TData and API material clearly belong to different batches.
• With original files preserved and no security settings changed, the delivered credentials themselves are invalid or mismatched and prevent the first basic login.
• An objectively verifiable country, calling code, quantity or delivery format differs from the purchased specification.

These claims still require submission within 30 minutes and verification against platform delivery logs, original files and reviewable processing results. “It does not work,” “it was banned,” or one cropped screenshot is usually insufficient to distinguish delivery failure from environment or Telegram verification.

• Telegram requests SMS, email, device, face or other official verification after correct credentials are accepted, or applies a restriction, freeze, ban or forced logout.
• Restrictions follow rapid IP or device changes, multi-instance use, bulk messaging, mass contacts or groups, unsolicited outreach, prohibited scripts or other abnormal activity.
• The buyer changes the phone number, email, password, two-step verification or security settings, or removes sessions before the issue appears.
• The account or original material is resold, transferred, shared or used concurrently by multiple people.
• A proxy, VPN, data-center network, polluted IP, client version, operating-system permission, file path or device environment is incompatible.
• The first report arrives more than 30 minutes after complete delivery or lacks the order number, original material and verifiable evidence.

• Use a lawful, stable network and device under your control and a current client from a trusted source.
• Validate only a small number at first. Avoid simultaneous login to one account across multiple devices or networks.
• After login, confirm the session and create your own backup before carefully changing eligible security settings. Do not remove every fallback session first.
• Never disclose the store payment password, complete account credentials, two-step verification, recovery-email codes or device control.
• Any automation, marketing or bulk operation must comply with Telegram rules and local law. Do not attempt to bypass platform safety controls.

• Support checks the bot order, complete-delivery status, file records, platform processing result and the buyer's original evidence.
• When missing, damaged, mismatched, short or intrinsically invalid delivery is confirmed, the affected scope may be redelivered, replaced or refunded according to the order state.
• An uncertain platform-processing or Telegram send outcome is not blindly repeated or redelivered. It enters manual review to avoid duplicate delivery and charges.
• Correctly delivered material, buyer-modified accounts and official or environmental restrictions are not eligible for unconditional refund merely because the rules were not read.

• Accounts may be used only for lawful testing, software development, research, learning or authorized business.
• Fraud, gambling, money laundering, account theft, harassment, spam, infringement, abusive industries and other illegal activity are prohibited.
• The buyer must have a lawful basis for login, content, contact handling and automation, and remains responsible for subsequent use.
• Telegram policy and verification can change at any time. Current official requirements prevail over an older description on this page.

References

• Telegram Terms of Service
• Telegram Privacy Policy
• Original Chinese purchase and after-sales notice

On August 28, 2026, the public catalog contained 21 available plans whose coverage fields collectively named: Mainland China, Hong Kong, Macao, Taiwan, Singapore, Thailand, Japan, South Korea, Malaysia, Indonesia, Vietnam, Australia, the UAE, Canada, the United States, the United Kingdom, France, Spain, the Philippines and Cambodia.

Do not decide from labels such as US, Hong Kong or Mainland-China version alone. The reliable checks are an Add eSIM control in Settings, an EID in device information, and an unlocked carrier status.

1. Connect the phone to stable Wi-Fi and show the delivered QR code on another screen. Never post the QR, LPA activation details or ICCID publicly.
2. On iPhone, open Settings → Cellular → Add eSIM → Use QR Code. Supported software can also add a QR code by long-pressing it in the default mail app or browser.
3. On Galaxy, open Settings → Connections → SIM manager → Add eSIM → Scan QR code. On Pixel and other Android phones, choose add or download eSIM in SIM settings.
4. If scanning fails, choose manual entry and provide the delivered LPA or SM-DP+ address and activation code exactly as requested. Do not alter spaces, letter case or symbols.
5. Label the new profile. At a covered destination, enable it, select it for mobile data, turn on data roaming and keep network selection automatic.
6. Disable cellular-data switching or its equivalent on the primary SIM to avoid accidental roaming charges.

Case A: the phone exposes native eSIM

If Settings genuinely shows Add eSIM and an EID, and the device is carrier-unlocked, use the native steps above. No writer is needed. Connectivity still depends on the purchased plan's Works in list.

Case B: the phone has no native eSIM control

A third-party programmable physical eUICC card may be an option: download the standard LPA profile to that special physical card, then insert it as a nano-SIM. The phone needs a working physical SIM slot, and the card, writer, writing software and exact phone model must all be mutually compatible.

1. Prepare compatible hardware: use a physical eUICC card that supports consumer eSIM profile download and the USB writer or supported Android writing method expressly paired by its vendor. Do not mix tools from unrelated systems.
2. Check the blank card: confirm that the software detects a writable eUICC, the card is healthy and profile space is available. Never format a normal SIM that is in use.
3. Use trusted software: install it only from the hardware vendor's official channel and keep the connection stable. Never upload the QR or LPA to an online decoder, writing service or unknown remote-control site.
4. Add the profile: choose Add or Download eSIM profile. Scan the QR or enter the complete activation content beginning with LPA:1$. If the tool separates fields, enter the SM-DP+ address and activation code as prompted. Do not invent a confirmation code when none was delivered.
5. Wait for completion: do not unplug the card, disconnect the network or close the software during download and installation. Eject the writer only after the tool confirms that the profile is installed or enabled.
6. Insert it into the phone: place the physical eUICC in the nano-SIM slot, enable it in SIM management and select it for mobile data. At a covered destination, enable data roaming and keep network selection automatic.
7. Verify: confirm the phone detects the card and test data. When the delivery includes an ICCID, also match its suffix. Never expose the full ICCID in a public screenshot.

• A data-only eSIM has mobile data but no phone number.
• A registration eSIM normally receives its number after installation and activation. It is intended for receiving codes, cannot make calls or send SMS, and does not guarantee registration on every platform.
• The bot's eSIM Center can show your card status, used, total and remaining data, expiry, coverage and registration-card number. A newly issued or not-yet-connected card may temporarily have no usage result.
• Renew only when the page says the card is eligible. Registration cards must use the same carrier's renewal package; data-only cards cannot be renewed.
• Registration renewal replaces the old package and normally opens only below 100 MB remaining or within 10 days of expiry. A successful renewal can immediately discard the old package and remaining data.

• QR, LPA and SM-DP+ activation details, plus any returned ICCID and registration-card number, are sensitive delivery data. Do not post them, include them in reviews or let an unknown person write the card remotely.
• The website is a static guide and never asks you to upload eSIM data. Purchase, card lookup and after-sales support remain inside the original store bot.
• An eSIM that has been issued, downloaded, written or activated normally cannot be refunded without cause. Incompatibility involving a third-party eUICC card, writer, software, driver, phone slot or radio bands is not the same as failed eSIM delivery.
• For an installation issue, keep the order number, exact model, sales region, operating-system version, current location and a redacted full error screenshot, then contact the original store.

Manufacturer verification

• Apple: Set up eSIM on iPhone
• Google: Use dual SIMs and eSIM on Pixel
• Samsung: Galaxy eSIM and country-of-origin notes

• Confirm TRON mainnet, the full destination, resource type and amount, duration, payment asset, amount due and expected delivery.
• Only terms shown on the current confirmation screen form the order. Old screenshots and chat descriptions do not replace it.
• Entering the payment password or completing the stated payment confirms the destination, plan, price and these rules.

• The bot may show an approximately one-hour flash rental, 24-hour, 72-hour, 30-day or estimated-transfer plans. Only currently visible options are available.
• An estimated transfer count uses a common transaction model and is not a fixed guarantee. Existing resources, recipient state and contract type change consumption.
• Select enough resources and time for the real use. A self-selected undersized plan, short duration or prior consumption is not short delivery.

• The one-hour flash rental requires payment from the Energy destination: the payer and destination must be identical and the exact tier must be paid in native TRX on TRON mainnet.
• Exchange withdrawals, payment from another address, a wrong network, a same-name token, split payment or an inexact amount may not match or activate.
• Do not pay again when status is uncertain. Preserve the transaction identifier and request review from the original store.

• The term starts when Energy is actually delivered or a transfer-count policy is actually activated. The displayed completion time is the first platform confirmation record, not the exact on-chain arrival time; first use, first view or first support contact does not control.
• Release at expiry is normal. Unused capacity, early completion or delayed use does not pause, extend or convert the remaining period.
• Review the delivered resources and expiry promptly after purchase.

• Contract calls, recipient state, transaction parameters and TRON rules affect Energy use. An estimate does not replace the wallet's pre-send resource display.
• Approvals, swaps, staking and complex contracts may use more than an ordinary transfer. Leave a reasonable margin.
• Energy may reduce eligible resource cost but does not guarantee transaction success, zero fees, receipt time or contract safety.

• Processing may begin immediately after payment. A destination, plan or duration cannot normally be changed or cancelled without cause.
• Correctly delivered, active or consumed resources are normally irreversible and are not refunded because they were not fully used.
• A balance-funded timed or transfer-count order pays from this bot's USDT or TRX balance and payment password; it never asks for a USDT address transfer. Only the one-hour flash flow uses the exact native-TRX payment shown on screen.
• An automatic balance refund applies only when the platform confirms zero delivery and final failure. Partial or uncertain results are reviewed first and may receive completion, a partial refund or another reasonable resolution; a full advance refund is not promised.

1. Submit the original-store order number, full destination, plan, payment record and transaction identifier.
2. Keep uncropped screenshots or recordings showing time, address, Energy balance, expiry and transaction resource use.
3. Do not add overlapping resources to the same address during review, as separate delivery may become impossible to attribute.

• Energy rental never requires a private key, seed phrase or wallet control.
• The user is responsible for the destination, purpose, contract and lawful on-chain activity.
• These rules do not exclude rights that cannot lawfully be excluded.

• Product, payment asset, destination asset, network, limits, inventory and availability follow the current bot screen.
• Buying TRX does not offer TRX-to-USDT sale. Buying native GRAM does not offer arbitrary TON assets or unrestricted token exchange.
• A hidden, paused, sold-out or unconfirmed item cannot be arranged through old links, screenshots, private messages or another store's balance.

• Confirm that the destination wallet supports the exact native asset and compare every character of the full address.
• A same-name asset, wrong network, contract token and native coin are not interchangeable. A custodial destination may also impose a memo or minimum credit.
• MBOTJ sends only to the final confirmed destination and does not guess, correct or replace it.

TRX and GRAM quotes use the purchase quantity and show unit pricing and the corresponding conversion amount. Reciprocal rate displays do not enable reverse exchange. The GRAM minimum is set as a USDT amount and is shown on the current screen.

• The screen shows quantity, live rate or sale price, USDT due, expected receipt, limits and expiry, and shows any applicable fee.
• Market, inventory and risk controls may change a refreshed quote. An expired quote and old screenshot do not lock price.
• Each quote is bound to the user, store, asset, quantity, destination and one payment; it cannot be reused across orders or bots.
• Entering the payment password accepts the displayed price, any applicable fee, expected receipt and delivery terms.

• A successful balance charge is not the same as final on-chain confirmation. Status may be pending, sending, confirming, complete, failed or under review.
• The order, transaction and target-mainnet confirmations determine delivery. Congestion, wallet display lag or custodial credit review does not by itself mean no broadcast.
• Use the mainnet explorer to verify asset, amount, destination and confirmation state.

• Once sent to the confirmed destination and reaching the required verifiable state, an order normally cannot be cancelled, redirected, moved to another network or returned to balance.
• A wrong destination, unsupported wallet, custodial non-credit, lost key or later user transfer is not failed platform delivery.
• MBOTJ does not promise asset price, future value, profit, wallet compatibility or an investment outcome.

• TRX and GRAM purchases use this bot's USDT balance only. A result that is not clearly final stops automatic repeat handling.
• An automatic refund applies only when the platform confirms no transaction was broadcast and the order finally failed with zero delivery.
• A broadcast, partly completed or unknown result is reviewed first. Completion, partial refund or another reasonable outcome follows the verified scope; a full advance refund is not promised.
• Duplicate orders or payments are reviewed separately and do not reverse an already correct transaction.

1. Provide the original-store order number, direction, quantity, full destination and final bot status.
2. If a transaction exists, provide the complete identifier and an explorer view showing network, asset, amount, destination and confirmation.
3. Keep the confirmation screen, balance ledger and complete error display. A wallet balance screenshot alone is insufficient.

• Token purchase never requires a private key, seed phrase, remote wallet control or extra payment to a private address.
• The user is responsible for lawful funds, destination control, tax and local reporting duties.
• MBOTJ may pause suspicious, illegal, sanctioned, fraudulent or abusive activity for reasonable review.
• These rules do not exclude rights that cannot lawfully be excluded.

• The bot dynamically displays purchasable monitoring mainnets from current health. The address-query catalog does not define monitoring availability.
• Each mainnet recognizes only assets expressly listed for that network. Unlisted tokens, same-name assets, testnet assets, internal ledger movements or non-standard events may not alert.
• A paused, hidden or delisted network or asset cannot be purchased through an old entry, screenshot or another store.

• Compare every character of the public address and confirm authorization to monitor it.
• Even when characters match, the same address on different mainnets is a separate object and must be added, allocated and configured separately.
• MBOTJ does not determine the actual controller, correct the selected network or migrate records across mainnets.

• An alert may be sent only when mainnet, asset, direction, amount range and recognizable event conditions all match.
• Thresholds use on-chain asset units and parsing precision. Rates, fees, internal contract transfers and display rounding may create apparent differences.
• An amount filter does not limit or block any blockchain transfer.

• Activating address slots, duration and configuration rights completes purchase; delivery does not depend on a matching transaction or first alert.
• Monitoring begins from the system scan time after the address is successfully added and configured. Transactions before that scan time are normally not scanned or resent.
• Promptly review mainnet, address, asset, amount range, expiry and the Telegram account receiving alerts.

• Only a non-permanent term plan whose rules allow renewal, whose renewal conditions are met and whose confirmation screen expressly shows auto-renewal enabled renews from the current store balance under the current terms. Disable it through the bot before expiry if no renewal is wanted.
• Insufficient balance, plan pause or unmet renewal conditions may enter a limited grace period; monitoring pauses after grace if not renewed.
• Disabling renewal prevents the next term only. It does not cancel the active term or refund remaining days.

• Chain confirmation, reorganization, node sync, event parsing, queues and Telegram message state can delay, reorder or duplicate display.
• Any timing estimate is a reference under normal conditions, not a guaranteed deadline. Independently verify high-value transfers on the mainnet explorer.
• Alerts, risk labels and public data are not receipt confirmation, compliance, legal, tax or investment advice.

• Address slots, mainnets, assets, duration, message allowance and frequency follow the confirmation screen. High-frequency, abnormal, over-limit or abusive use may be limited, paused or rejected.
• After benefit activation, unused address slots, no matching transaction, unread alerts or early configuration removal do not earn a proportional refund.
• A finally failed order whose benefits never activated follows its verified state. Activated, partly used or uncertain cases are reviewed first; a full advance refund is not promised.
• A wrong network, address or threshold, or alerts missed because the bot was blocked, muted or offline, is not failure to grant monitoring benefits.

• Monitoring never requires a private key, seed phrase, signature permission or wallet control and cannot freeze, reverse or transfer assets.
• The user is responsible for address authorization, lawful purpose and decisions made after alerts.
• After-sales requests should include order number, mainnet, full address, asset, threshold, transaction identifier, event time and complete alert image.
• These rules do not exclude rights that cannot lawfully be excluded.

These rules apply to the general service information on mbotj.com and to store bots that expressly adopt them. Product name, quantity, region, price, estimated timing, delivery method and after-sales conditions are governed by the product page and final confirmation screen presented before payment.

Agreeing to the rules, creating an order, depositing, paying or continuing to use a service means you accept the version shown at that time. If you do not agree, do not create or pay for an order.

• The only brand website is mbotj.com. Look-alike spellings, added prefixes or unfamiliar short links are not this website.
• Purchases and after-sales support must remain in the store bot you originally used. Do not switch bots or pay a personal address because of an unsolicited message.
• The website does not publish fixed deposit addresses. Use only the details generated for the current order.
• Support will never request your Telegram login code, six-digit payment password, private key, seed phrase or recovery key.

You must have the legal capacity required in your location and ensure that buying, paying for, holding and using a service complies with applicable law, network rules and third-party platform policies. Restricted regions, sanctioned persons or users who cannot complete necessary verification may be denied access to some services.

Services may not be used for fraud, account theft, harassment, extortion, malicious automation, unlawful gambling, money laundering, infringement, bypassing platform safety measures or any other unlawful activity.

Identity, balance, ledger entries, orders, pricing and support relationships created in one store bot belong to that store entry. Do not assume that balances, discounts, orders or support rights automatically transfer between different store bots.

A bot balance is an internal ledger balance used to buy services in the current store. It is not a self-custody on-chain wallet and does not give you control of a private key or an address that can perform arbitrary blockchain transactions.

Each store may independently configure its brand entry, enabled catalog, dynamic pricing, support and management tools. A current-store administrator can manage only that store's scope and does not thereby gain access to another store's customers, balances, orders or operating data.

• Catalog items, stock, regions, quantity limits, delivery estimates and prices can change.
• Website catalog counts show general scope and are not a promise of permanent stock or a fixed price in any store.
• Only the product, quantity, unit price, total and version shown on the final confirmation screen govern that order.
• An item that is hidden, sold out or marked unavailable cannot be ordered. No order means no charge.
• A custom item submitted by a store operator may appear only after current-store review and while enabled. Submission, approval or prior listing does not guarantee continued sale.

1. Use only a method actually shown on the current bot's deposit page. A missing method is not enabled there.
2. Create a new deposit order every time and verify its order number, actual amount and validity.
3. For KKPay or OKPay, use only the official entry generated for that order. Never reuse an old link or pay a personal account.
4. For TRON-USDT, follow the network, specified asset, complete address and exact amount shown. Do not substitute another network or asset.
5. A provider payment must pass a signed callback or order lookup; an on-chain payment must reach the required finalized state. Only then does the current store balance and ledger update, and the same payment is credited no more than once.

A delayed provider callback, order-lookup exception, underpayment, overpayment, duplicate or late payment, payment to an old order, or use of the wrong network, token or contract may not credit automatically. Check the current order and ledger before attempting another payment.

Keep the current-store order number when requesting review. For an on-chain payment, also provide the TXID, amount and time. Blockchain transfers are irreversible; recovery, manual credit or return depends on verifiable receipt, handling capability, cost and compliance requirements and cannot be guaranteed.

Balance purchases and sensitive settings may require a separate six-digit payment password. It is not a Telegram login code. Keep it private and never disclose it to support or any third party.

Personal-balance charges, refunds and deposits should appear in the ledger. Personal Center balance is limited to purchases in the current store and eligible order refunds; personal-balance withdrawal is not offered. Agent profit withdrawal is a separate Agent Center business function. If a result is unclear, check the order and ledger before trying again. Password or account recovery may require multiple factors, a cooling-off period and manual review.

Before payment, verify the product, target account or address, region, quantity, specification, price and delivery conditions. Treatment of a wrong target, an ineligible target or a target changed after payment depends on the verifiable order status and the product-specific rules.

Delivery may occur through a bot message, file, QR code, code, account material or status update. Verify, download and secure the material promptly. Do not publish sensitive delivery data, forward it to unrelated people or leave it on an uncontrolled device.

Redelivery after device loss, deletion, account restriction, credential disclosure or expiry of a stated retention period is handled according to verifiable records and the specific product conditions; permanent redelivery is not guaranteed.

A virtual product may deliver a code, account, text, link, file, file plus code, automated result or another stated material. Only actual delivery success may record a delivery time and start the 24-hour auto-confirmation window; creating an order, reserving stock or uploading unverified material is not delivery. A physical product starts its seven-day auto-confirmation window after the publisher records shipment and tracking.

This store does not offer user balance transfers, red packets or personal receiving, and the menu has no creation entry. The website also never processes deposits, receiving or any fund operation. A related code, link, QR code or personal address from an unsolicited contact does not mean the store offers that service.

Historical statements and existing old records may remain for reconciliation, but they cannot create a new transaction, hold a balance or charge funds. Any future capability is available only when shown in the bot's real current menu, final confirmation screen and latest rules.

The currently supported direction is buying TRX with the store balance; the reverse TRX-to-USDT entry has been retired. When the purchase entry is enabled, its confirmation screen shows the destination, payment asset, rate or unit price, expected receipt, quote expiry and any applicable fee. A missing entry is unavailable and must not be arranged privately. Refresh an expired quote.

GRAM is available only as a purchase funded by this bot's USDT balance and is delivered as native GRAM on TON mainnet. Enter the GRAM quantity and verify the TON destination, live sale price, USDT amount, inventory, per-order and daily limits, and quote expiry. A quote is short-lived and single-use. A wrong destination or finalized on-chain payout is normally irreversible. Do not bypass a hidden, out-of-stock, price-paused or payout-paused entry through private messages; reverse GRAM sales and cross-bot balance offsets are not offered.

Energy services may include an approximately one-hour flash rental, 24-hour, 72-hour and 30-day options, plus plans based on expected transfer count. The one-hour flash flow requires the exact native-TRX tier from the receiving address. Timed and transfer-count plans use this bot's USDT or TRX balance and payment password and never request a USDT address transfer. Actual use depends on the destination, contract and chain execution. The rental term begins on actual delivery or transfer-policy activation. The displayed completion time is the first platform confirmation record, not the exact on-chain arrival time; unused capacity normally does not roll over, and only a finally failed balance order with confirmed zero delivery receives an automatic refund.

When enabled, the confirmation screen may offer 3-, 6- or 12-month Premium for a specified username, or quantity-based Stars. Before payment, verify the recipient, Premium term or Stars quantity, unit price, total and expected fulfillment. For batch Premium, review every recipient individually.

These digital entitlements may enter fulfillment immediately after submission. A wrong recipient, an ineligible recipient or an order already processing normally cannot be freely renamed or cancelled. Premium batch creation and charging are atomic, but each recipient is fulfilled individually after creation. Only an unsigned, unsubmitted order confirmed as zero-delivery failure is automatically refunded. Submitted, partly completed or uncertain results are reviewed first. Any estimated completion time is a reference only; do not create or pay again merely because a message is delayed.

• Confirm that the actual device exposes Add eSIM and an EID, is carrier-unlocked, and verify covered countries or regions, data allowance, validity, activation method and plan type. Country variants of the same model can expose different capabilities.
• Neither card origin nor internet exit-IP location is the service coverage area. Rely on the exact product's complete Works in list and final confirmation screen.
• QR codes, LPA details, ICCID and phone numbers are sensitive delivery information and must not be shared publicly.
• A successful delivery contains an installable QR code or LPA. ICCID appears only when returned. A missing ICCID is not failed delivery and does not block LPA installation, although ICCID-dependent lookup or renewal must wait until it is available.
• Once issued, downloaded or activated, an eSIM normally cannot be refunded without cause. Keep an error screenshot if installation fails.
• A data eSIM has no phone number. A registration eSIM normally displays its number after activation, is intended for receiving codes, cannot make calls or send SMS, and does not guarantee registration on every platform.
• Install over stable Wi-Fi using the QR code or LPA details. At the destination, enable the eSIM, select it for mobile data, enable roaming and keep network selection automatic. Do not change APN unless the service explicitly instructs you.
• Native eSIM support on Mainland-China iPhone variants follows Apple's current guidance and the actual phone menu. Hong Kong, Macao, international and Android variants must also be verified by full model, sales region and the on-device Add eSIM control, not by family name alone.
• A phone without native eSIM may use a third-party programmable physical eUICC only after the user confirms compatibility among the card, matched writer or writing method, software, phone SIM slot, operating system and radio bands. An ordinary SIM reader, copier or blank SIM cannot install eSIM; incompatible third-party hardware is not failed eSIM delivery.
• Writing may download a delivered profile to only one compatible eUICC. It must not be copied to multiple cards or devices. A profile that has been downloaded, written or consumed is not reissued merely because the user changes a writer, physical card or phone.
• Renewal depends on the existing plan and may affect remaining data; the confirmation warning takes priority.
• A My Cards or recovery entry checks the same Telegram UID and returns only that user's own deliveries. It does not share balance, orders or customer data between stores.

Account products are classified by country or region, dialing code, age, number attributes and current stock. Verify the specification before payment. After delivery, promptly download TData, Session or related login material, follow the delivery instructions and create your own secure backup. Once the bot has sent every delivery file, inspect file integrity, quantity, batch consistency and basic login within 30 minutes.

Digital accounts are affected by device, network, login behavior and Telegram safety controls, so permanent stability cannot be promised. Fraud, account theft, harassment, spam and attempts to evade platform enforcement are prohibited.

• You must own, manage or be authorized to use the submitted target and comply with the target platform's rules.
• Minimum and maximum quantities, speed, geographic targeting, refill and cancellation are governed by the product details.
• Standard services are priced per unit and may also show a 1,000-unit example; packages show a fixed package price. Verify the total for the actual quantity before payment.
• Renaming, making a target private, deleting content, restricting access or submitting a wrong link after processing begins may prevent completion and a full refund.
• Metrics may change because of platform cleanups, user behavior or algorithm updates. Permanent retention, ranking or official platform endorsement is not promised.
• False claims, harassment, infringement and manipulation of public events are prohibited.

UID, TON collectible, blockchain address, public market rate and calculator tools are for verification. Public-network results may be delayed by synchronization or congestion and are not investment, legal, tax or trading advice.

The address-query catalog may show 23 mainnets, but query support does not mean that long-term monitoring is enabled for the same network. Monitoring lists only mainnets enabled by the platform's current runtime state. A paused, delisted or hidden network must not be treated as purchasable monitoring merely because it is queryable.

Address monitoring reads public blockchain data only. It does not require or control your private key and cannot transfer assets. Each network recognizes only assets expressly listed by the bot, and the same address must be added separately across mainnets. Plan benefit activation completes purchase. Monitoring starts from the system scan time after the address is successfully added and configured and normally does not backfill earlier transactions. Only an eligible non-permanent term plan whose rules allow renewal and whose confirmation screen expressly shows auto-renewal enabled renews automatically; the user can disable it. Monitoring pauses after an unpaid grace period. Unused allowance and no matching transaction do not earn a proportional refund. High-frequency, abnormal or over-quota requests may be limited, paused or rejected.

A balance order that is verifiably failed and undelivered is returned to the current store balance according to the product process. An order that has started, partly completed, been delivered, sent on-chain or remains uncertain is handled using the verifiable result, actual completed portion and product-specific rules.

Digital services may be immediate and, except where mandatory law requires otherwise, do not provide unconditional returns after delivery. Refunds follow the order and ledger record and are never arranged through a personal account, unfamiliar bot or privately messaged address.

If the system cannot determine the result of a charge, on-chain payment, service submission or delivery, it stops automatic retries and marks the order for exception review. This reduces the risk of duplicate charges, purchases or delivery.

To prevent fraud, mispayment and abuse, the store may request an order number, TXID, target details, operation time or limited proof of order ownership. It will not request your full payment password, login code, private key, seed phrase or recovery key.

• Protect your Telegram account, device lock, two-step verification, payment password and recovery material.
• Do not store delivery files on shared devices or forward complete bot messages to strangers.
• Before acting, verify the current store name, order number, destination and final price.
• If your account, device or credentials may be compromised, stop paying and contact support through the original entry.
• User-account or store-management recovery may require the original UID, payment password or built-in recovery credential, multiple checks, at least a 24-hour cooling period and manual review. No single item guarantees success.
• Enter a recovery credential only in the bot's built-in recovery screen and keep it offline. Support will not ask for the full credential in chat or tell you to forward it to a third party.
• Security alerts identify the event, reason, result, operation ID, risk score, related object, source, time and a specific next action. A risk score prioritizes review and is not proof of loss; a high-risk operation alert does not by itself prove an attack.

To provide account, order, payment, delivery, security and support functions, the service processes necessary Telegram identifiers, current-store identifiers, order content, balance ledger entries, product targets, blockchain transaction identifiers, risk status and support records. Customer data, balances and orders are isolated by store entry.

The service does not need your private key or seed phrase. You must restrict access to sensitive eSIM QR codes and account delivery files. Necessary records are retained for service, security audit, dispute handling and legal requirements and are protected with reasonable safeguards.

Blockchain networks, Telegram, mobile operators, social platforms, connectivity, maintenance or force majeure may delay catalog updates, payment confirmation, processing or delivery. A store may pause a service for safety, stock, compliance or maintenance reasons. No order means no charge during a pause.

A paid order will be handled according to its verifiable state: processing may continue, wait for recovery, use an agreed alternative, or be refunded under these rules. Estimated times are not absolute guarantees unless the final screen expressly states otherwise.

Use the “Contact Support” button in the store bot where the order was placed. Provide the order number, description, time and any necessary TXID or redacted screenshot. Never send a payment password, login code, private key, seed phrase or recovery key.

Disputes are assessed using the current store's order, ledger, blockchain, delivery and product records together with these rules. Material updates may require fresh acceptance. New orders follow the new version; an existing order normally follows the rules visible when it was placed.

The support bot may answer common questions from its knowledge base and may look up only the current Telegram user's own orders. An automated answer does not change order status, refund boundaries or manual-review requirements; unresolved cases move to the current store's formal support ticket.

A user may self-apply for an agent bot from Agent Center when the entry is enabled. Telegram native creation is preferred; the Token compatibility method is available when the client does not support the native entry. The applicant must use their own Telegram account, and a bot administrator cannot create a bot on a customer's behalf. Any fee, grant, review and deployment status is governed by the current application screen.

After deployment, management occurs inside the owner's own bot. Customers, USDT/TRX balances, ledgers, orders, prices, profit, support settings, business configuration and descendants are isolated per bot. Do not manually alter bot connectivity settings or casually reset the Token in @BotFather.

• The price chain is read-only cost → downstream agent price → customer sale price.
• eSIM, Telegram accounts, traffic services and other products may be configured together, by group, subcategory, search result or individual product.
• Configure-all uses percentage markups; exact prices belong at group, subcategory or product level.
• Agent price cannot be below cost. Sale price cannot be below the downstream agent price or the protection floor formed by the direct parent bot's current public sale price.
• Percentage rules recalculate from current cost. If an entry is too low, the screen explains why and shows a currently valid minimum so the agent can re-enter that step.
• Two percentage stages compound along the price chain rather than being added. After the first stage, the screen previews the next minimum valid markup and a recommended value that may be applied after the margin is reviewed.
• A current layer may adjust prices within the floors shown by the screen. Recheck the live screen before saving whenever cost or a protection floor changes.
• Pricing does not itself list a product. Platform catalog products must still be enabled or disabled in Product Listings.
• The publisher maintains self-owned stock and delivery material. Automated virtual inventory and manually fulfilled or shipped orders must be handled in their corresponding Agent Center queues.
• GRAM pricing may combine the platform baseline with the current bot's rule into cost, agent and customer sale prices. Price, inventory, order and daily limits, and payout controls must all be available before the customer entry may accept payment.

Operations & Customers controls the store's support entry, announcements with text, media, Premium Emoji and buttons, category-scoped order-notification groups, the start message and child-cloning policy. Preview announcements and verify their recipient scope before sending; notification settings do not make an unavailable product sellable. Public copy must not impersonate others, enable illegal use, publish unknown payment destinations, request sensitive credentials or promise an outcome the store cannot deliver. Support tickets follow a claim, handle and close lifecycle.

Order notices show product detail and quantity where safe, plus amount, payment method and completion time, while omitting complete account, phone or other sensitive targets. An agent bot may add up to five co-administrators with full Agent Center business authority. The original administrator cannot be removed; every add or removal requires the acting administrator's own six-digit payment password, and removal immediately invalidates access, pending sensitive actions and related recovery authority.

Start-message precedence is store-specific configuration, platform default, then system default. A bot without its own saved configuration inherits the platform introduction and MBOTJ official-website button. Existing custom content remains local to that bot and is not overwritten by the platform default.

When child cloning is enabled, customers must self-apply using their own Telegram accounts. Each completed bot becomes a direct child; administrators cannot clone for customers. Disabling blocks future applications only and does not alter existing bots or open applications.

USDT and TRX agent profit is allocated separately. When a given asset is offered by the current page, eligible profit is held and requested for withdrawal in its original currency. It never passes through Personal Center, converts across currencies or transfers between bots. Verify currency, withdrawable amount, destination, fees and ledger details before requesting withdrawal. Available assets, minimums, fees and the withdrawal entry follow the current bot's Agent Center page.

Back Up Bot Data protects the entire agent bot's customers, orders, products, business configuration, ledger ownership and descendant hierarchy. Recovery requires the original administrator Telegram UID, bot username, independent bot backup key and the six-digit Personal Center payment password used when backup was configured. Passing verification submits a request only; a minimum 24-hour cooling period and manual review apply before any change.

Permanent disable may be initiated only from the direct parent bot's Agent Center and requires explicit confirmation. It is irreversible: the bot cannot be recovered, re-enabled or cloned again under the same identity. Its customers, balances, orders, ledgers, products, backup and recovery records remain read-only history. Temporary failure, an invalid Token or planned bot replacement should use status checks or recovery, not permanent disable.