Support & frequently asked questions

No; the article's core rule is never miss twice, and it gives a smaller recovery version for the next day.

No; the program relies on low-cost regular activities, and the per-person budget in the dossier's table is a small worked figure.

No; it is general information, and for important decisions you should consult a qualified legal adviser.

No; the article uses the European Union's 14-day period as an example and stresses checking the current rules where you operate.

You can begin the steps, but the structure choice and contract templates should pass a legal adviser's review.

No; it is educational, and for any treatment decision you should consult your doctor or pharmacist.

No; it covers preventive habits and timely screening, and refers warning signs to urgent medical attention.

Yes; the flow map, pre-visit registration and flow board all work at a small scale too.

No; it presents published evidence, an assessment method and an action plan, but it states at each step which work needs a licensed professional, and leaves specialist decisions to them.

No; it comes with a data table, findings and a weekly working routine, and its workbook records and tracks that very routine.

Yes; it is written with a one-page charter, phase-gate inspections and sign-off checklists so the owner can verify work without technical expertise — although specialist work still needs a specialist.

No; it presents published evidence, an assessment method and an action plan, but it states at each step which work needs a licensed professional, and leaves specialist decisions to them.

No; it comes with a data table, findings and a weekly working routine, and its workbook records and tracks that very routine.

Yes; it is written with a one-page charter, phase-gate inspections and sign-off checklists so the owner can verify work without technical expertise — although specialist work still needs a specialist.

No; it presents published evidence, an assessment method and an action plan, but it states at each step which work needs a licensed professional, and leaves specialist decisions to them.

No; it comes with a data table, findings and a weekly working routine, and its workbook records and tracks that very routine.

Yes; it is written with a one-page charter, phase-gate inspections and sign-off checklists so the owner can verify work without technical expertise — although specialist work still needs a specialist.

No; it presents published evidence, an assessment method and an action plan, but it states at each step which work needs a licensed professional, and leaves specialist decisions to them.

No; it comes with a data table, findings and a weekly working routine, and its workbook records and tracks that very routine.

Yes; it is written with a one-page charter, phase-gate inspections and sign-off checklists so the owner can verify work without technical expertise — although specialist work still needs a specialist.

No; it presents published evidence, an assessment method and an action plan, but it states at each step which work needs a licensed professional, and leaves specialist decisions to them.

No; it comes with a data table, findings and a weekly working routine, and its workbook records and tracks that very routine.

Yes; it is written with a one-page charter, phase-gate inspections and sign-off checklists so the owner can verify work without technical expertise — although specialist work still needs a specialist.

No; the course starts from intermediate formulas and builds step by step to pivot tables and a dashboard, but you should already know SUM, AVERAGE and sorting.

Yes; the course starts with short, gradual exercises and teaches anxiety control, breathing and preparation step by step, but it is not a substitute for professional treatment for anxiety.

No; students, freelancers and homemakers can fill the same three columns — priorities, focus blocks and weekly review — with their own work.

Yes; most tools — one-to-ones, meeting agendas and written feedback — are written the same for on-site and remote teams, and only the communication examples differ.

The texts are editable templates; you must replace them with your own product name, delivery time and return policy so the reply is accurate and correct.

No; no course can guarantee a ranking. This course teaches the correct method for keywords, content and technical fixes, and results depend on competition, content and time.

No; ingredient, rent and labour prices differ in every city. The guide teaches the pricing calculation method, and you must replace the samples with your own local real prices.

No; this is a general educational course and gives no official certificate. For a certificate you must join a recognised in-person course with practical training.

No; planting time depends on the cold, heat and season where you live. The guide teaches how to read a seed packet and adapt to your local climate.

No; the three course projects are designed for a small space, a folding workbench and basic tools, but you still need a dry space, good light, and eye and ear protection.

In the same Telegram bot, open “My orders” and tap an order to open its detail screen. It shows: the order code, product name, payment method (USDT, card-to-card, or credit), discount percent and source (if any), applied credit, the order amount (for card orders: the unique amount and tracking code), and for a USDT order still being paid, the partial-payment progress (how much has arrived, how much is left). Status is also shown as a three-dot stage: ●○○ means waiting, ●●○ means paid and sending, ●●● means delivered or credited. If you cannot find an order, send its order code via the Support button.

• “Waiting for the payment receipt (TxID)”: a USDT order and you have not sent a TxID yet; your next step is sending the TxID. • “Waiting for transfer (card-to-card)”: a card order and you have not transferred yet or not tapped “I have paid”. • “Waiting for store approval”: your receipt (tracking code or receipt photo) is recorded and it is now the store owner's turn to review; you have nothing to do but wait. • “Verifying the transaction on the blockchain…”: your TxID was sent and the bot is checking it on the Tron network right now; the result will be announced in the same chat in a few moments. In all of these states no file has been sent yet.

• “Paid”: your payment is confirmed and the files are being prepared for sending; if you cannot see them in the chat, scroll up a little in the same chat. • “Sending the files…”: the bot is sending the product files one by one in the same chat; do not leave the chat mid-delivery. • “Paid — file delivery failed (being followed up)”: your money is safe and the payment is confirmed, but automatic file sending failed at that moment; the case was registered for the store at once and sending will be retried. Keep your payment receipt, and if the files still do not arrive, message Support.

• “Delivered”: the files were successfully delivered in the chat and the order is closed. • “Credited”: this was a wallet top-up that was successfully added to your balance (not a product purchase). • “Not approved”: the store owner rejected a card order; the credit and discount reserved on it are released and you can use them on another order. • “Cancelled”: you cancelled the order, or the order is closed; on a cancelled or rejected order, no credit or discount is consumed. Note: cancelling or rejecting an order does NOT mean an automatic money-back; a card-to-card money-back is only ever a manual decision by the store owner.

• “The previous check for this order is still running”: a check for this same order is in flight right now; wait until its result is announced, then resend the TxID only if needed. If a check has been stuck without a result for over 10 minutes, resending runs it again. • “The previous check was only seconds ago”: after the first 2 checks, further checks must be at least 15 seconds apart; sending sooner does not make the result faster. • “Too many checks in the past hour”: at most 12 checks per order per hour; wait a little and try again, or send the receipt via Support. A string that does not look like a TxID at all (not 64 characters) never counts toward this limit and is rejected immediately.

When you submit your receipt, the bot builds a review card for the store owner containing: the order type (purchase or wallet top-up), your name, your unique deposit amount in local currency plus its Rial (×10) figure, the order code, your tracking code, and if you sent a receipt photo, that photo in the next message. The owner matches the deposit in his own banking app against the amount and tracking code, then taps either “Approve and send files” or “Reject”. At this stage you should neither resend the receipt nor make a second transfer; a second transfer does not speed the order up and its settlement becomes manual.

You can cancel a card-to-card order while it is “Waiting for transfer” or “Waiting for store approval”, using the cancel button on that same order; on cancel, the reserved wallet credit and discount are released immediately and can be used on another order. If you cancel after submitting a receipt, the owner is also told, because your deposit may already have arrived; settling that deposit (for example a money-back) is only ever the owner's manual decision and the bot never returns money automatically. A delivered, paid, or sending order cannot be cancelled with the cancel button; for those, message Support. For an unpaid USDT order nothing needs cancelling: just do not send a TxID; you will get at most one reminder after 24 hours, and starting a fresh purchase releases the old order's reservations.

1. In your wallet app (for example Trust Wallet) open the transaction history and find the exact transaction where you sent the USDT. 2) Tap it to open the transaction details; there you will see a field labelled Transaction Hash or TxID. 3) Tap the copy button next to that field and paste the copied text into the bot chat; do not type it by hand, because a single missing character is enough for it not to be found. If you sent from an exchange, the TxID is on that withdrawal's receipt in the exchange history — copy it from there. After you send it, the bot checks the transaction automatically on the Tron network.

A TxID is exactly a 64-character string of letters and numbers (letters a to f, plus digits) — no shorter, no longer, and with no extra spaces at the start or end. The bot checks this shape first: if the text you sent does not look like a TxID, it is rejected at once with “This text does not look like a TxID” and no network check starts at all. So always copy the TxID directly from your wallet or the exchange receipt and send it exactly as it is; a photo of a receipt does not replace the TxID text.

On the first time a TxID is not found, the bot only shows the failure message and tells you to copy the TxID from that transaction's details in your wallet app and send it again; a wrong TxID never opens a support case by itself. Only when you have now tried twice for the same order and the transaction is still not found does the bot add: “If you are sure the transaction is correct, give Support the deposit screenshot + product name + TxID for a manual check.” So on the second attempt, send exactly those three things together to Support; until a payment is confirmed, no file is sent.

Before sending any file, the bot runs these 5 checks on the Tron network, and all must pass: 1) the transaction exists, succeeded, and is confirmed on the network (the “not found”, “not yet confirmed”, and “not successful” messages come from here). 2) the token is the official Tron USDT (a plain TRX transfer is not USDT and is rejected). 3) the recipient is exactly the store wallet address the bot showed. 4) the received amount is at least the order's expected amount (the expected amount is the final price after discount, minus reserved wallet credit). 5) the transaction is fresh for this order, and this TxID has never been used for another order (each receipt is valid only once).

Because the freshness check says a transaction must belong to this order: if you made the transfer before this order started — even if the amount and address are right — it cannot be used for this purchase, and you get the message “This transaction was made before this order started”. The correct way is to make a fresh transfer for this same order, to the same address the bot showed, and send the fresh TxID. If you believe you already paid for this same product, send the receipt to Support for a manual check; but an old transfer is never linked to a new order automatically.

Each TxID is valid only once, for one order. If you resend the same TxID, the bot tells you this order was already paid and finalised and no further payment is needed. If you send a different, genuinely valid TxID for an already-paid order, the bot records that transfer (the TxID is burned so it can never be reused) and alerts the owner for manual handling — but the files are never sent a second time. In that case you are also told this is an extra payment and to keep this transaction's receipt; its manual handling takes at most 24 hours.

You can send a product's amount in several transactions: after each transaction, send that transaction's TxID in the chat. Each confirmed deposit is recorded on the same order and added to the previous ones, and after each one the bot tells you exactly how much has arrived so far, what the full amount is, and how much is still missing. When the total reaches the full amount, the files are sent automatically. Three conditions apply to every part: TRC20 network only, only to the same address the bot showed, and fresh for this same order. Each partial TxID is burned the moment it is counted, so the same transfer can never be counted twice or reused for another order. Until the total is complete, the payment session stays open for the next TxID.

The order completes and delivery happens; overpaying does not block delivery. But the excess is NOT added to your wallet automatically. The bot honestly tells you how much you sent in total, what the order amount was, and how much extra you paid. To settle the excess, message Support so the store owner can decide; there is no automatic return and no method is promised in advance.

Send exactly the unique amount the bot showed — no less, no more, and no rounding. The unique amount is the product price plus a small random number between 100 and 999 in local currency, unique to this order and unique among all the store's open card orders, because the owner finds your payment in his banking app by this very amount. If you already sent a different amount (for example the card price without the random number), send that tracking code and tell Support exactly how much you actually sent; settling that deposit is only ever the owner's manual review, and the bot never returns money automatically. Do not make a second compensating transfer without talking to Support.

After transferring, tap “I have paid” in the same bot chat and send the tracking code (or a receipt photo); with that single submission the order moves to “Waiting for store approval” and the owner's review card is built. If you send anything again afterwards, the bot tells you your receipt was already submitted and accepts no new submission. So if you mistyped the tracking code, do not make a fresh transfer; message Support with the order code + the correct tracking code so the owner can review that same open order with the correct information. In your first message always include the product name and order code so the review is faster.