Refund & Cancellation Policy
This policy explains how cancellations, refunds, duplicate payments, subscriptions, support charges, and digital-service payment disputes are handled on our platform.
1. Digital Services Nature
Our platform provides digital products and digital services. These include platform-managed project work, template-based deployments, custom development, support, subscriptions, and meeting-based service workflows. Because these are digital and labor-based services, refunds are limited once work has started.
2. General Refund Rule
Payments may be refundable only in limited and approved cases. Once planning, execution, deployment, service activation, subscription cycle consumption, or resource allocation has begun, the payment may become partially refundable or fully non-refundable depending on the service stage.
3. Custom Project Advance Payment
- If a custom project is cancelled before planning, scheduling, or execution begins, a refund request may be reviewed.
- Once requirement handling, planning, assignment, proposal preparation, or project work has begun, the advance may be non-refundable.
- Where partial work has already been performed, only a limited partial refund may be considered at our discretion, after deducting work already consumed.
4. Template / Basic Plan Refund Rule
- If a Basic Plan order is cancelled before deployment activity starts, a refund request may be reviewed.
- Once deployment has started, template setup has begun, configuration work has started, or branding/content updates have been applied, the payment may be non-refundable.
- No refund may apply after digital delivery, activation, or trial enablement has already been completed.
5. Trial Rule for Basic Plan
Where a Basic Plan service is delivered with a trial mode, the trial is intended as limited access and service enablement. Trial availability does not automatically create a refund right for setup work already performed.
6. Subscription / Monthly Support Refund Rule
- Monthly support or maintenance payments are generally non-refundable once the billing cycle has started.
- Prepaid months may be reviewed only for unused future periods and only if no service activation or reserved service commitment has begun for that future period.
- Consumed billing cycles are non-refundable.
7. Support Ticket Charge Refund Rule
- If a support ticket was created and diagnostic or resolution work has started, the charge may be non-refundable.
- If a ticket charge was paid in error and no support work has started, a refund request may be reviewed.
- If only partial work was consumed, a partial refund may be reviewed after deducting actual service effort.
8. Cancellation Policy
8.1 Client-Initiated Cancellation Before Work Starts
A cancellation request submitted before service execution, deployment activity, planning work, or support activity begins may be reviewed for refund eligibility.
8.2 Client-Initiated Cancellation After Work Starts
Once work starts, a cancellation does not guarantee any refund. Costs already consumed through meetings, planning, deployment activity, developer allocation, support handling, or active service provisioning may be deducted or may make the payment fully non-refundable.
8.3 Company-Initiated Cancellation
If we are unable to deliver a service for reasons solely attributable to us and no practical replacement or resolution is provided, a refund or partial refund may be considered depending on the work already completed.
9. Limited Refund Cases
Refunds may be considered in limited cases such as:
- duplicate payment,
- successful charge with failed order creation,
- incorrect excess payment,
- service not started and cancellation approved,
- billing error confirmed by us.
10. Duplicate Payment Handling
If the same invoice or service is accidentally paid more than once, the duplicate excess amount may be reviewed and refunded after verification of the transaction records.
11. Failed Payment / Partial Payment Handling
- A failed payment does not create a refund right if no amount was actually settled.
- If an amount is debited but payment confirmation is pending, reconciliation may require payment gateway or bank processing time.
- Partial payment may not activate service unless the required payable amount is fully satisfied.
12. Chargeback and Payment Dispute Rule
Users must first contact us before raising a chargeback or payment dispute. Unjustified chargebacks after service consumption, planning, deployment, or access delivery may lead to account suspension, service suspension, recovery action, or dispute defense.
13. Refund Request Process
Refund requests should be sent to billing@evisiontechnolab.com with the invoice number, order number, transaction reference, registered email, registered phone number, and reason for the request.
14. Refund Timeline
If a refund is approved, it may be processed within a reasonable internal review timeline. Final credit timing depends on payment gateway, bank processing, issuer processing, and network settlement cycles.
15. Payment Gateway / Bank Delay Disclaimer
We are not responsible for bank-side, gateway-side, or card/UPI processor-side delays once an approved refund has been initiated from our end.
16. Contact for Refund Requests
Billing Email : billing@evisiontechnolab.com
Support Email : support@evisiontechnolab.com
Business Name : Evision Technolab Private Limited