1. Refund approach
- Before agreed work starts: cancellation of a paid project receives a full refund of the project payment.
- After work starts: the portion of the payment attributable to work not performed is refundable. Highlink LLC explains the completed work, the agreed scope and the calculation of any partial refund in the customer-visible project conversation before processing it. No arbitrary fixed percentage is used.
- After delivery: if the delivered work does not match the agreed scope, Highlink LLC first offers to correct that issue within the agreed scope at no additional charge. If the issue remains unresolved, a partial or full refund is reviewed according to the undelivered or deficient work and the seriousness of the issue.
This approach does not limit any mandatory customer rights. Refund review is based on the agreed work and its actual stage; bank arrival times are outside Zikap’s direct control.
When paid work begins
Before beginning paid work, Highlink LLC records a dated, customer-visible project update confirming the scope and start of work and marks the project In progress. The customer can read that update in the dashboard. Payment, acceptance of a request or running a free website check alone does not establish that the paid project work has started.
The existing dashboard status and project update fields support this process. They do not automatically start work, calculate a refund or transfer money.
2. How to request cancellation or refund review
- Open the corresponding project in your customer account or use the original receipt-based tracking route. In Payments, choose Refund review to open the support form with that topic selected.
- Use the project conversation or the support form to state the order reference, what you want cancelled or reviewed, and the reason for your request. A support request can be opened without an existing linked project. Do not send card numbers, passwords or receipt keys in the message.
- Zikap reviews the accepted scope, payment record and current work stage, then records the outcome and any agreed next step.
Support and refund contact: support@zikap.site.
3. Unpaid requests and incomplete checkout
Submitting a project request does not charge you. If no payment was completed, there is no completed project charge to refund. Closing a checkout page is not a refund action; the saved project and Stripe record are used to determine payment status.
The project payment-status control can check a pending checkout. An expired checkout is not proof of a collected payment. Do not make repeated payments merely because a browser page is slow or a return screen is unclear.
4. Accepted refund decisions
Financial refunds are initiated by the merchant in Stripe. A project note, delivered status, cancelled request or action-plan update does not itself move money. A refund cannot exceed the payment amount that was collected.
After a refund is processed and its event is received, the Zikap project can show the recorded refund status. Use the payment provider’s financial record if the project status is delayed or needs investigation. Partial refunds and complete refunds are distinct.
5. Where the money goes and timing
An approved Stripe refund is sent back to the original payment method used for the charge. Bank/payment-method processing and failed or pending refund outcomes can affect when it appears. The time taken depends on the payment method and processing by the bank or provider.
If a refund is recorded as pending or failed, ask for a review through the corresponding project or support conversation. Do not treat a pending record as proof that the money has reached your account.
The merchant may still incur provider costs even when it refunds a customer. Provider processing costs are not deducted from the customer refund described in this policy.
6. Delivery questions, duplicate payments and test mode
If a delivered report needs clarification, the included scoped revision route may resolve the issue. Asking for clarification does not itself waive any mandatory right. Report a suspected duplicate or unrecognized payment through the corresponding project or support request so Highlink LLC can review it against the Stripe record. Do not submit another payment to resolve a suspected duplicate.
Payments explicitly labelled Stripe test mode are simulated. They do not charge real funds, and a test-mode refund does not return real money.
7. Questions, changes and mandatory rights
- This version applies to new service arrangements from November 9, 2026. Existing agreed project arrangements and mandatory rights are preserved.
- Future versions will identify their effective date. A later revision does not silently alter the agreed scope or stored price of an existing project.
- Use the dated project-update process above to document work commencement and account for any applicable mandatory consumer requirements.
Nothing in this policy excludes rights that cannot lawfully be excluded. Mandatory rights may differ according to the customer’s location and the service arrangement.