Frequently asked questions
Payments, delivery and support explained clearly—without hidden steps.
Delivery depends on the item. In-stock automated products can be delivered after verified payment. Custom services and manually fulfilled products show an estimated delivery window in the product or order details.
Sign in and open the customer dashboard. It shows payment status, verification progress, delivery status, invoices, downloads and support activity for each order.
BDT checkout supports bKash Personal and Nagad Personal through Send Money. The official receiving number and exact payable amount appear only on the order payment page.
Send the exact BDT amount, then submit your sender number and transaction ID. Staff checks the transaction before the order moves to processing. Never send money to a number shared outside the official order page.
Send the order number and a clear description. Never share passwords, recovery codes or one-time verification codes.
No. Each bKash or Nagad transaction ID can be submitted only once. This protects customers and prevents one payment from being attached to multiple orders.
Crypto checkout currently supports Litecoin (LTC), Solana (SOL), USDT on Polygon and Bitcoin (BTC). Always send only the selected asset on the network shown on the payment page.
Blockchain and payment-provider network minimums change by asset. When an order is below the selected network minimum, checkout will explain the issue so you can add another item, choose another supported coin or pay in BDT.
For bKash and Nagad, confirm that you submitted the correct transaction ID and sender number. For crypto, wait for the required network confirmations. If the status does not update, open a support ticket with the order number—do not pay again.
Refund eligibility depends on the product-specific terms and delivery state. A delivered, revealed, downloaded, activated or already-used digital item is normally not refundable. Contact support before starting a chargeback or duplicate payment.
Provide only the details requested at checkout, such as a target link, player ID, design brief or technical requirements. Never include passwords, recovery codes or unrelated sensitive information unless a clearly documented service absolutely requires it.
Use the contact page or open a ticket from the customer dashboard. Include your order number and a clear description of the issue. Support can review the order without asking you to send the same payment again.
Checkout requires a signed-in account, uses duplicate-order protection, validates payment methods server-side and blocks reused manual transaction IDs. Keep your account access private and use only the official martech.lol website.
