Frequently Asked Questions

Open Login / Register in the header, choose registration and enter the requested details. Use an email address you can access and complete any verification steps.

Use the lost-password link on the account login page. Check your inbox and spam folder for the reset link, and create a unique password.

Check the email spelling, autofill, keyboard layout and password. If the reset link expired, request a fresh one. If you still cannot sign in, submit a ticket without including the password.

Sign in to the account used at checkout and open My Account / Orders. If no order appears, check the confirmation email and make sure you are using the right account.

Do not immediately pay again. Check the order status and keep the payment reference. Submit a ticket with the order number, date/time and masked transaction reference; never share PINs or full card information.

Enter the code in the cart or checkout coupon field and apply it before payment. Check validity, minimum spend, included products and expiry. Only trust the final live order total.

Refund eligibility depends on the current Refund & Cancellation Policy and product/order status. Submit a ticket with your order number, email and reason for review.

After payment is confirmed, open the order details and check Downloads or the product’s access instructions. If a completed order has no link, contact support with the order number.

Only if the product listing offers a sample preview. Review coverage, fields, format, update notes and permitted use; a sample is not the complete purchased dataset.

Include the product name, order number, download time and the error. Avoid sharing the full purchased database publicly.

Define the use case, use an appropriate permission-based audience, confirm sender/header and template setup, test the message and monitor delivery reports.

Promotional messages typically market offers or products; transactional/service messages convey permitted information tied to a user or transaction. Classification and routing must match the actual purpose and current rules.

Provider acceptance is not the same as final delivery. Check the message ID, delivery report, recipient number, sender/template configuration and provider error code.

Use the current account documentation, keep API credentials server-side, validate requests, handle timeout/retry safely and correlate delivery reports. Never put API keys in public browser code.

Follow current business onboarding, number setup, template and policy requirements. Keep credentials secure, validate webhooks and test delivery failures before going live.

Include the service, concise subject, steps to reproduce, timestamp, error text and relevant order/message ID. Mask customer data and remove credentials.

The ticket form accepts selected image, PDF and text/log formats, up to three files and 5 MB each, where secure file storage is available on the site.

Use Ticket Status with the ticket number and the email used to submit the request. If the details match, a new secure access link will be emailed.

No. Database access does not automatically grant consent to send marketing. You must assess lawful use, recipient expectations, privacy requirements and each channel’s current policies.

DLT is part of India’s commercial messaging registration and filtering framework. Sender/header, content template and related steps depend on message type and current rules; verify the latest official guidance and provider process.

Never send passwords, login OTPs, API secrets, UPI PINs, full card numbers or unnecessary personal data. Share only details needed to investigate the issue.