Check region, plan, account age, validity or resource type.
TRANSACTION RULES · EN
From quote to delivery,
every trade has a record.
These rules follow the actual store-bot transaction flow: pre-order checks, deposits, balance payments, payment passwords, order formation, processing, digital delivery, exception review, cancellation, refunds and after-sales evidence.
Current storeTransaction confirmation
Final confirmation before payment
Review product details
Product · Target · Quantity · Unit price · Total · Restrictions
- Order status
- Awaiting confirmation
- Payment
- Current store balance
- Security
- 6-digit payment password
- Duplicate guard
- One order, one submission
1Confirm
2Pay
3Process
4Deliver
If a page or message is delayed, check the order and ledger before paying or submitting again.
BEFORE YOU PAY
Confirm five things before payment.
Only the final confirmation page in the current bot forms the basis of that transaction. Catalog previews, old screenshots, expired quotes and private-chat statements do not replace it.
Check the account, link, number, eSIM destination or TRON address.
Check the range, conditions and cancellation or refill marking.
Prices may change with the catalog and inventory; use the final total.
Check delivery contents, refund boundaries and what must be saved.
An unavailable, sold-out or paused item cannot be ordered.
Without a valid order, the platform does not charge the current store
balance. An incorrect on-chain transfer can be irreversible, so use
only the address, asset, network, contract and exact amount on the
current order. Never bypass the current store through another chat,
personal address or bot.
TRANSACTION LIFECYCLE
How a transaction is formed and completed.
Browsing and data entry do not necessarily create permanent records. Key payment, order, ledger, delivery and refund events should remain verifiable in the current store.
-
01
Browse products
Review live inventory, pricing and availability.
-
02
Enter the target
Submit the account, link, region, address or plan.
-
03
Review the final page
Confirm product, target, quantity, total and restrictions.
-
04
Make a secure payment
Enter the 6-digit password for balance, or pay the exact current on-chain invoice.
-
05
Create a valid order
Processing begins after an atomic balance order, or after finalized on-chain payment is verified.
-
06
Process and deliver
Follow the relevant service record and receive the result.
-
07
Verify or request support
Save delivery data; use the original store and order number for support.
CORE TRANSACTION RULES
Deposit, balance and payment boundaries.
Create a new deposit order every time
Depending on current-store configuration, the deposit page may show KKPay, OKPay or TRON-USDT. Create a new order first, then use its payment link or copy its full on-chain address and exact amount. A method not shown there is not currently enabled.
- A deposit does not require the payment password
- Never reuse an old link, screenshot, address or amount
- Provider balance updates only after a verified signed callback or order lookup
- On-chain balance updates only after successful, finalized chain execution
- An order number or TXID assists review; it does not prove credit
- Callback delays, short, excessive, duplicate, late, wrong-address, wrong-contract, wrong-asset or wrong-chain payments must not trigger a blind repeat payment
The balance belongs to the current store
It is an internal balance for services in the current store, not a user-controlled on-chain wallet, and is not automatically shared with another store bot.
- Balances, ledger entries and orders are isolated by store
- Charges and refunds should create ledger records
- Eligible refunds normally return to the original store balance
Balance payments use a separate 6-digit password
The payment password confirms a balance charge or sensitive operation. It is different from a Telegram login code and should never be given to support.
- Repeated errors may cause a temporary lock
- Use the in-bot recovery flow if it is forgotten
- Support does not request the password
Processing starts only after a successful order record
Browsing, entering a target or viewing a quote does not form a transaction. Payment must be accepted and a valid order recorded.
- After password approval, price, inventory and available balance are checked again
- A failed payment or missing order must not cause a duplicate charge
- The store order number is the main support reference
Uncertain results stop automatic retries
If a charge, service submission or delivery cannot be safely confirmed, the order enters exception review to avoid duplicate charges, purchases or delivery.
- Do not pay again because of a message delay
- Check the order and ledger first
- Verifiable records determine the next step
An incorrect target may not be reversible
The user must provide an accurate, authorized account, link, region, number or address. Changing or deleting a target after processing starts may cause failure.
- Do not change the target after payment
- Do not use services for fraud, abuse or illegal activity
- Save digital delivery securely and promptly
ORDER STATUS
Let the order status determine your next step.
Labels may vary slightly by product, but payment, processing, delivery, review and refund have consistent meanings.
Pay within the validity period. If no funds were sent, create a new order after expiry.
Wait for finality or store confirmation; do not pay the same order again.
Wait for updates; do not buy or submit the same target again.
Verify, download and store the delivery immediately.
Failure does not mean refunded; continue checking refund status and the store ledger.
Cancellation does not mean refunded; payment and delivery records still decide eligibility.
If an on-chain payment was sent, do not pay again; request review with the order and TXID.
Automatic repeats have stopped. Keep the order number and wait.
Check the current store balance and ledger; do not pay again.
PRODUCT-SPECIFIC RULES
Delivery and refund boundaries differ by product.
These are key checks for store-bot product types; actual sale status comes from the live catalog. Current product details and the final confirmation page remain decisive.
← Swipe horizontally on mobile to read the complete product rules →
| Product | Confirm before payment | Delivery evidence | Cancellation and support |
|---|---|---|---|
| Premium and Stars | Recipient username, Premium term or Stars quantity, unit price and total; review each recipient in a batch | Current-store order, payment record and fulfillment result | Fulfillment may start immediately. Uncertain results stop retries; do not pay again or reorder with a renamed target |
| Social growth | Target link, quantity, public access and whether the current details mark refill or cancellation | Order progress, completed quantity and final status | No refill or cancellation is promised by default; it applies only when the current product details say so |
| Telegram accounts | Region, calling code, age, number attributes, inventory and delivery format | TData, Session, login data and store delivery record | Save files immediately; platform policy, device, network and usage mean long-term or permanent availability is not promised |
| Global eSIM | Quantity is one per purchase; verify device support, coverage, data, validity, number and activation conditions | QR code when provided, LPA, ICCID, usage and expiry records | Usually no unconditional refund after delivery; egress IP is not coverage, and a new plan may replace an existing plan |
| Buy TRXwhen offered | TRON address, payment asset, quote, fee, expected receipt and quote validity | Current-store order, ledger and on-chain delivery result | Store balance can buy TRX. Reverse TRX-to-USDT has been retired, and an expired quote must be refreshed |
| TRON energy | TRON address, address state, resource amount, validity, planned transfers and the payment asset shown | Resource status, on-chain result and order record | The 1-hour flash plan uses exact native TRX on-chain only; longer plans use store balance or USDT-TRC20 as shown |
| Address monitoringwhen offered | Use only an explicitly visible TRON mainnet monitoring entry; check address, term, amount-alert range and purchase-page renewal status | Subscription order, ledger, risk label, copyable transaction ID, alert and monitoring state | Alerts begin after activation and do not backfill history. An eligible non-permanent plan renews at the then-current price only when the purchase page enables it; it can be disabled |
| Transfers and red packetssame store | Recipient, total, number of shares, equal or lucky mode and claim validity | Claim credential, current-store ledger, claim or expiry return | A credential claimed by someone else is normally irreversible; unclaimed funds return after expiry under the displayed rules |
Energy payment and term details
- The 1-hour flash plan accepts native TRX only—not store balance or USDT—and requires the exact amount within the usual 30-minute window.
- Do not use batched exchange withdrawals for an exact TRX invoice. Late payment enters manual exception review.
- 1-, 3- and 30-day terms begin after successful delivery. Count-based plans support 5–1,000 transfers and stop consuming after one continuous day without a transfer.
- An incorrect address or delivery to the confirmed address is normally irreversible. Failed, partial or unknown results are reviewed before any refund decision.
- For an energy USDT invoice, the unique tail amount above the service price returns to the current store balance by record.
Use the current quote when buying TRX
Use this only when the current store bot visibly offers the buy entry. Store balance can buy TRX; reverse TRX-to-USDT has been retired. Verify the address, payment asset, rate or unit price, fee, expected receipt and quote expiry. A missing entry is unavailable and must not be arranged privately.
CANCELLATION & REFUNDS
Verifiable status decides whether cancellation or refund is possible.
Digital services may be immediate. Eligibility depends on whether payment occurred, processing started, part completed, delivery happened and the result can be safely confirmed.
Read the service-rule refund boundaries →If no accepted payment occurred, let it expire and create a new order at current pricing if needed.
If an on-chain payment was sent, do not pay again; provide the order and TXID for manual review.
Eligible social, account or eSIM balance orders return to the original store balance. Energy and other on-chain orders are reviewed first.
It is considered only when the product permits it and processing can still be stopped safely.
The completed portion, product terms and verifiable result determine support.
Delivered digital data or on-chain resources generally do not support unconditional refunds.
Wait for confirmation. The same transaction is not blindly resubmitted or refunded.
AFTER-SALES EVIDENCE
Prepare verifiable information before contacting support.
Use only the “Contact support” button in the store bot where the order was placed. This keeps the customer, balance, order and support relationship in the same store.
Locates the transaction and status records.
Describe the status, message and requested review.
Needed only for an on-chain payment or delivery issue.
Hide unrelated personal data and sensitive credentials.
Never send: a Telegram login code, payment password, private
key, seed phrase, full recovery key or unredacted sensitive delivery
data.
TRANSACTION FAQ
Transaction FAQ
When something is delayed, check the order status before acting.
Does viewing a quote form a transaction?
No. Payment must be accepted and a valid order recorded before processing begins. Reconfirm after a price or inventory change.
Why was the product not delivered immediately after payment?
Processing differs by product. If the order is processing normally, wait for an update and do not purchase the same target again.
Does an incorrect payment password charge my balance?
A failed payment verification should not complete the balance charge. Repeated failures may trigger a temporary lock.
What does “exception review” mean?
The charge, submission or delivery result cannot yet be confirmed safely, so automatic repetition has stopped. Keep the order number and wait.
Can I change an incorrect account, link or address?
Before payment, exit and enter it again. After payment and processing, a change is normally unavailable and depends on verifiable status.
Where does an eligible refund go?
It normally returns to the current store balance that owns the original order and creates a ledger entry.
What if a deposit is short, excessive or late?
Do not pay again. Use the original store support route with the deposit order, TXID, amount and time. On-chain mistakes cannot always be recovered.
Are KKPay, OKPay and on-chain deposits always available?
No. Use only a method shown on the current store's deposit page. Provider payments follow a verified callback or lookup; on-chain payments follow the required finalized state. Check the original order during a delay and do not pay again.
Can I buy Premium or Stars again while processing?
No. Verify the recipient, term or quantity and check the original order. An uncertain result stops automatic retries; a duplicate order can create irreversible duplicate digital entitlements.
Can a leaked transfer or red-packet claim be reversed?
Usually not after someone has claimed it. Unclaimed funds return to the current-store balance after expiry under the displayed rules. Never publish a claim credential or use it across stores.
Does /cancel revoke a paid order?
No. /cancel exits an unfinished input flow only. It does not revoke a paid, processing or delivered order; an existing order follows its status and refund rules.
What if these rules differ from the product page?
These are general transaction rules. Product region, quantity, pricing, timing, delivery and support follow the current product details and final confirmation page.
MBOTJ.COM
Confirm clearly before paying.
Transaction rules explain the common flow. Read the full service rules for account, privacy, product-specific and dispute terms.