Refund and Delivery Policy

1. Scope

This Refund and Delivery Policy applies to marketplace purchases, WoTrade packages, plugin access, project configuration, domain-related setup, delivery of admin credentials, support services, and other digital or service-based items purchased through WoPixel.

2. Delivery Timeline

After payment, we confirm the order and prepare the selected project, domain, plugins, access details, and handoff information. Most workspaces are prepared within 24 hours. Delivery may take longer if manual review is required, a payment is pending, a domain needs additional checks, selected plugins require validation, support volume is high, or the order appears risky.

The customer purchase page may show order states such as order received, setup in progress, ready, delivered, or on hold. These states are operational updates and do not guarantee a specific delivery deadline unless a separate written agreement says otherwise.

3. What Counts as Delivery

Delivery may occur when we provide one or more of the following: project access, admin login URL, admin username, admin password, client access accounts, plugin access, purchase code, delivery notes, domain instructions, configuration confirmation, or other handoff details. Delivery may be partial where some components are available before others.

4. Digital Products and Services

Purchases are for digital software, configuration, plugin access, and service delivery. Once work has started, access has been provisioned, credentials have been delivered, a domain has been configured, plugin or license access has been granted, or custom preparation has begun, refunds may be limited or unavailable except where required by non-waivable law.

5. Non-Refundable Items

Unless required by law, refunds are not available for completed delivery, issued credentials, activated plugin access, purchase codes, domain-related costs, third-party fees, payment processor fees, custom configuration work, manual setup time, abuse investigation time, renewal periods already started, or services already performed.

6. Refund Requests Before Work Starts

If you request cancellation before any work starts and before any credentials, plugins, domains, or access details are delivered, we may review the request and decide whether a full or partial refund is appropriate. Approved refunds may exclude payment processor fees, currency conversion differences, crypto network fees, domain costs, or other non-recoverable third-party costs.

7. Refund Requests After Work Starts

If setup, configuration, plugin access, domain preparation, support, or delivery has already started, any refund is discretionary and may be partial. We may deduct the value of work performed, time spent, third-party costs, payment fees, and delivered access. We are not required to refund because a customer changes their mind, no longer wants the product, failed to read the terms, chose the wrong plan, or used the software for a prohibited purpose.

8. Abuse and Policy Violations

No refund is owed for accounts suspended, revoked, or terminated because of fraud, scam reports, abuse, chargeback abuse, prohibited activity, false information, legal risk, payment risk, impersonation, illegal use, or violation of our Terms or Acceptable Use Policy, except where non-waivable law requires otherwise.

9. Chargebacks and Payment Disputes

Customers should contact support before opening payment disputes. Unauthorized chargebacks, false disputes, or payment reversals may result in immediate suspension of accounts, plugins, licenses, domains, support, and delivered access. We may provide purchase records, acceptance logs, IP addresses, user agents, delivery logs, support records, and handoff records to payment providers to respond to disputes.

10. Crypto Payments

Crypto payments may be affected by network fees, confirmation times, exchange rates, underpayments, overpayments, wrong networks, wrong addresses, or irreversible transfers. Refunds, when approved, may be issued in the original currency, a supported currency, account balance, or another method we choose, minus non-recoverable fees and costs.

11. Customer Duties After Delivery

After delivery, the customer must review the handoff details, change passwords, secure admin accounts, configure legal pages, manage staff access, verify domain settings, test the project, and operate the business lawfully. Failure to secure delivered access or configure the project properly is not a basis for refund.

12. On-Hold Orders

We may place an order on hold because of payment review, abuse screening, incomplete information, domain issues, legal risk, suspicious activity, or support review. While an order is on hold, delivery may pause. If the issue is not resolved, we may cancel, suspend, or refuse delivery according to the Terms.

13. How to Request Review

To request a refund or delivery review, contact support with your account email, order ID, project name, payment reference, domain, and a clear explanation. We may request additional information before making a decision. Submitting a request does not guarantee approval.

14. Delivery Status Explanations

An order marked as received means payment or account information has been recorded and the order is waiting for preparation or review. Setup in progress means work has started or the order is being configured. Ready means access details are prepared or nearly prepared. Delivered means handoff details have been provided. On hold means delivery is paused for review, missing information, payment status, abuse risk, or another operational reason.

Status labels are provided to help customers understand the timeline. They are not a promise that every part of an order is finished at the same time, and they do not remove the customer's responsibility to review the handoff details after delivery.

15. The 24-Hour Preparation Estimate

We usually prepare standard orders before 24 hours, but this is an estimate and not a guaranteed deadline. Delivery may take longer for manual configuration, suspicious activity review, domain checks, payment confirmations, provider delays, support workload, custom plugin combinations, wrong customer information, or requests outside the normal package scope.

A delay alone does not automatically create a refund right if work has started, third-party costs were incurred, access was prepared, or the delay is caused by payment review, missing information, customer changes, provider issues, or risk review.

16. Customer Information Required for Delivery

We may need accurate email addresses, domain details, package choices, plugin selections, account information, language preferences, or other setup details to complete delivery. If the customer provides incorrect, incomplete, changing, or delayed information, delivery may be delayed and refunds may be denied or reduced.

Customers are responsible for checking the purchase page, support messages, and handoff information. Failure to read delivered credentials, missing emails, using the wrong inbox, or failing to respond to setup questions is not a service failure by itself.

17. Partial Delivery and Partial Refunds

Some orders include multiple components, such as software access, plugins, domain instructions, support, configuration, and credentials. If only part of an order is incomplete, we may provide a fix, replacement, credit, additional time, or partial refund at our discretion. A partial issue does not automatically entitle the customer to a full refund for completed or usable components.

18. Technical Issues After Handoff

If a delivered project has a technical issue within the purchased scope, the normal remedy is review and reasonable correction, not an automatic refund. We may ask for access, screenshots, error messages, reproduction steps, server details, or other information to diagnose the issue.

We are not responsible for problems caused by customer edits, unsupported third-party changes, deleted files, changed passwords, external developers, hosting restrictions, domain misconfiguration, malware, abuse reports, payment provider blocks, or attempts to modify licensing or plugin checks.

19. Plugin and License Refund Limits

Paid plugin access may be tied to a purchase code, account, project, or domain. Once a plugin is activated, delivered, assigned, verified, downloaded, or configured, refunds may be unavailable because the digital value has been provided. If plugin access is revoked because of policy violations, chargebacks, license sharing, or prohibited use, no refund is owed except where required by law.

20. Domains, Hosting, and External Costs

Domain registrations, renewals, DNS work, hosting costs, provider charges, payment processor charges, blockchain network fees, currency conversion differences, and other external costs may be non-refundable even if a broader order is cancelled. Some providers do not allow reversals after a domain, service, or transaction is created.

21. Fraud Screening and Refused Orders

We may refuse, cancel, pause, or manually review orders that appear suspicious, abusive, illegal, high risk, connected to previous violations, or inconsistent with our policies. If an order is refused before work starts, we may return eligible funds minus non-recoverable costs. If work has started or risk is caused by the customer, refunds may be denied or reduced.

22. No Refund for Prohibited Business Use

A customer is not entitled to a refund because they intended to use the software for scams, fraud, unlicensed regulated activity, impersonation, phishing, fake trading, misleading withdrawals, or another prohibited activity and later lost access. The customer is responsible for reading and following the Terms and Acceptable Use Policy before purchase.

23. Refund Method and Timing

Approved refunds may be issued to the original payment method, account balance, supported crypto wallet, bank method, or another method we choose. Processing time depends on payment providers, banks, networks, compliance checks, and internal review. We may require wallet confirmation, payment reference verification, or identity checks before issuing a refund.

24. Evidence Used in Refund Decisions

Refund decisions may consider order records, policy acceptance logs, payment status, IP address, user agent, support messages, delivery timestamps, handoff records, plugin activation, domain records, complaint reports, chargeback history, abuse signals, and the amount of work already performed.

25. Non-Waivable Rights

Nothing in this policy is intended to remove consumer rights that cannot legally be waived. If a law gives you mandatory rights that apply to your purchase, those rights continue to apply. The rest of this policy applies to the maximum extent permitted by law.