Refund, Cancellation & Dispute Policy

1. Purpose

This policy describes how DevNetLynx handles customer cancellations, refund requests, project disputes and payment-related exceptions. Decisions remain subject to applicable law and the rules of the payment provider.

2. Before Payment

A customer may generally cancel an unfunded project without a payment refund being required because no customer funds have been confirmed.

3. After Payment but Before Work Begins

Where payment has been confirmed but the developer has not started the funded work, a customer may request cancellation. DevNetLynx will assess the payment state, any provider charges, fraud/compliance considerations and the applicable project terms before initiating an eligible refund through the approved payment-provider process.

4. After Work Begins

Once funded work has begun, refunds are not automatically guaranteed. The amount, if any, depends on work completed, milestones, usable deliverables, scope compliance, the reason for cancellation and applicable law. A fair partial settlement may be appropriate where only part of the agreed work has been performed.

5. Approved/Completed Work

Work that has been accepted or completed is generally not refundable solely because the customer later changes their mind. This does not remove rights that cannot lawfully be excluded, including remedies for fraud, material misrepresentation or other rights under applicable law.

6. Developer Non-Performance

Where a developer materially fails to perform the agreed work, abandons a project, or supplies materially non-conforming work and does not remedy the issue within a reasonable opportunity where appropriate, DevNetLynx may facilitate cancellation, reassignment, partial refund or refund, depending on the circumstances and payment-provider capability.

7. Dispute Process

1. The customer or developer raises the issue through the available support/dispute channel and supplies relevant project evidence.
2. DevNetLynx may restrict release of the disputed developer amount while the matter is reviewed, where the payment structure permits.
3. Both parties may be asked for messages, deliverables, scope records and other relevant evidence.
4. DevNetLynx evaluates the recorded project terms, milestone state, evidence, payment status and applicable policy.
5. A resolution may include continued work, revision, milestone adjustment, cancellation, partial refund, refund, developer release, or escalation to the payment provider where required.

8. Chargebacks and Payment-Provider Disputes

A payment-provider chargeback or reversal is handled according to the provider's process. DevNetLynx and the relevant developer may be required to provide transaction/project evidence. No internal platform status overrides a payment provider's lawful reversal or compliance action.

9. Refund Method

Approved refunds are processed through the approved payment-provider method where possible. DevNetLynx will not request a customer to provide card credentials to process a refund.

10. Abuse

Fraudulent refund claims, deliberate chargeback abuse or manipulation of the dispute process may result in account restriction or termination and may be reported or escalated where legally appropriate.

Version 1.0 — 24 September 2026