Build, improve or fix your WordPress website with expert support. Post a Project → Post a Project →

Refunds Policy

Project fairness · Professional WordPress Solutions

Refunds Policy.Clear terms. Fair outcomes.

Learn how cancellations, refund requests and payment concerns are reviewed for professionally managed WordPress Projects. Search the policy, find the clause relevant to your situation and understand the next step before submitting a request.

Draft reviewed 3 November 2026Esposearch.netAgency Projects only
Refunds at a glance

Know what matters before making a decision.

A clear Project agreement and documented progress make refund reviews more predictable, without removing anyone’s applicable rights.

For Clients

Understand how deposits, completed work, milestones and payment records are assessed.

Explore this topic

For Experts

See how approved assignments and demonstrable work contribute to an agency review.

Explore this topic

For Everyone

Understand how disputes are documented and mandatory rights are protected.

Explore this topic
Important: Cancellation, a payment refund and an internal account credit are different outcomes. A request is evaluated against the approved Project, evidence of delivery, actual payment route and applicable legal rights.
How reviews are approached

Fair resolutions begin with the facts.

Neither a blanket refund guarantee nor a blanket no refund rule fairly reflects a custom WordPress Project.

A clear agreement

Start with the approved scope, costs, acceptance criteria and agreed payment schedule.

Read guidance

Work and evidence

Examine completed deliverables, unfinished obligations and documented costs fairly.

Read guidance

Correct payment treatment

Distinguish returning money from editing a balance or offering Project credit.

Read guidance

Protected customer rights

Never treat a contract label or software limit as an automatic override of legal remedies.

Read guidance
Find the right next step

Explore a typical Project refund situation.

Choose a situation to view general preparation guidance. This is not an automatic refund assessment or promise of a particular decision.

No implementation has started

Check whether the Project was accepted, whether money was collected and whether any separately approved paid preparation or documented third party commitment exists.

  • Review the agreed Project terms.
  • Keep the relevant Project record.
  • Contact Support with a concise explanation.
What to prepare

Confirm the Project and funding status. Note any agreed chargeable work.

Request a Review

Your selection remains on this page. It is not transmitted, saved as a claim or used to decide eligibility. A written case review is required.

The complete Refunds Policy

Explore 30 searchable Project refund sections.

Use the sticky contents index or live search to explore cancellation, completed work, approved milestones, repayment methods, disputes and your rights.

SECTION 01 / 30Overview

Purpose, operator and policy coverage

Who this policy applies to

The operating model

Esposearch.net is operated by Esposearch Limited Company, registered under the laws of the Republic of Kenya. The agency coordinates Professional WordPress Solutions through individually assessed and approved Projects. This Refunds Policy addresses cancellations, repayment requests and payment disputes relating to those Projects.

What the policy does not cover

Submitting a Project brief is not automatically a paid engagement. This policy does not establish a separate purchase route for predefined purchases, downloadable store items or transactions made on Esposearch.courses. Those activities, where offered elsewhere, require their own applicable terms.

Read the Project documents together

The approved scope, written quotation, accepted milestones, payment instructions and applicable Terms and Conditions provide the commercial context. Mandatory legal rights continue to apply where they cannot lawfully be limited.

SECTION 02 / 30Overview

Cancellation, refund and credit are different

Understand the outcome being requested

Cancellation

Cancellation asks that future Project work stop or that an approved engagement end. It may lead to an accounting review, but it is not by itself a determination that a full refund is payable.

Refund

A refund returns an amount properly due to the Client through an available lawful payment route. Eligibility depends on the approved terms, work performed, documented costs, circumstances and legal rights.

Account credit and adjustments

A platform account credit, corrected invoice, reversed milestone entry or other ledger change is not necessarily a cash refund. Any proposed outcome should identify its form clearly before the Client is asked to accept it.

SECTION 03 / 30Overview

The documents used in a decision

Scope and payment records matter

Accepted scope

We examine the confirmed work, deliverables, exclusions, milestones, revisions, estimated timing and Client obligations. A broad aspiration such as more sales or better search visibility is not automatically a guaranteed result.

Specific approved terms

Project terms can specify lawful payment events and agreed commitments. Where documents conflict or a material term is unclear, the issue should be reviewed fairly rather than resolved by relying on a hidden or uncommunicated condition.

Legal protections

Applicable consumer, contract, payment provider and dispute resolution rights may override an inconsistent contract term or software limitation. This policy should not be interpreted as excluding a protection that the law requires.

SECTION 04 / 30Overview

Principles for fair review

No automatic full refund and no blanket exclusion

Evidence and proportionality

A fair assessment considers what was agreed, what has actually been delivered, what remains unperformed and whether a concern relates to an in scope obligation. Claims should be supported by reasonably available records.

Accuracy and communication

Clients should receive a clear explanation of the assessment and any amount approved for repayment or adjustment. The agency should not describe an internal wallet balance as cash already returned.

No false guarantees

Every cancellation does not produce a full refund, and every paid amount is not automatically nonrefundable. The decision must reflect the facts, applicable agreement and legal rights.

SECTION 05 / 30Before Work

Requests that have not been accepted

Posting a Project is not a chargeable contract

Unaccepted Project requests

A Client may withdraw an unaccepted Project request. If no funds have been collected and no separately accepted chargeable preparation has occurred, there is normally no Project payment to refund.

Assessments and preliminary quotes

A discussion, draft estimate or technical enquiry does not alone create an obligation to proceed. Any paid discovery or assessment must be disclosed and accepted separately before charges arise.

When funds were collected early

If money was received before the Project was accepted, its treatment must be reviewed against the actual payment record, disclosed agreement and applicable rights. No amount should be retained simply because a request was posted.

SECTION 06 / 30Before Work

Confirming price, scope and milestones

Know the commitment before approving it

The quotation

Clients should review total fees, specific deliverables, exclusions, expected contributions, milestones, revision arrangements and relevant third party purchases before accepting an engagement.

Deposits and advance funding

A deposit or advance payment is not automatically nonrefundable. The applicable agreement should state what the payment covers, any agreed prerequisites and how it will be treated if the Project ends before completion.

Written changes

Material additions to functionality, integrations, content or delivery expectations may need a revised quote. Unapproved work or charges should not be silently added to the original agreement.

SECTION 07 / 30Before Work

Cancellation before implementation starts

Funding and work commencement must be distinguished

No substantive work performed

Where an approved funded Project ends before substantive work begins, the assessment should identify any properly disclosed, demonstrable commitments and applicable rights. The starting assumption should not be that funding alone proves the full amount has been earned.

Agreed preparation

Paid discovery, design planning or assessment may count as performed work only where it was actually undertaken under applicable accepted terms.

Communicating the result

The agency should explain whether the outcome is a refund, reversal of an unreleased amount, agreed charge for completed preparatory work or another lawful adjustment.

SECTION 08 / 30Before Work

Third party products and commitments

Licenses and external purchases need clarity

Items purchased for the Project

Hosting plans, domains, premium plugins, themes, APIs and other vendor products can have separate cancellation and refund rules. The Client should be informed when a third party commitment is material to the Project.

Nonrecoverable expenses

An external charge can be considered only where it was properly authorized, adequately supported and lawfully allocable to the Client. Not every stated outside expense is automatically deductible.

Ownership and access

A third party subscription or license may remain subject to its own provider terms regardless of the agency Project outcome. Handover or transfer obligations should follow the accepted scope.

SECTION 09 / 30Active Projects

Cancellation after work has begun

Consider progress and value already supplied

Documented partial performance

If a Project ends while implementation is underway, the review should distinguish completed in scope work, unfinished deliverables, approved milestones and outstanding obligations. A proportionate financial adjustment may be appropriate.

No automatic forfeiture

A Project cancellation must not automatically make every funded amount earned. Likewise, the mere fact that a Client changes direction does not mean duly performed authorized work has no value.

Cooperative handover

Where practical, the parties should document the work completed, materials prepared, access to be removed and any files or reports that can be lawfully delivered or returned.

SECTION 10 / 30Active Projects

Milestones and staged deliverables

Review each approved stage on its merits

Accepted milestones

Completed milestones that satisfy agreed acceptance criteria may be evaluated separately from later work not delivered. Acceptance records are relevant but do not erase valid claims arising from defects or legal rights.

Incomplete stages

Amounts allocated to work not properly performed remain subject to the agreed funding arrangements and fair refund review. A milestone label does not substitute for evidence of delivery.

Milestone corrections

An in scope correction should be distinguished from an additional requested feature. The Project record should show any review comments, accepted changes and agreed resolution.

SECTION 11 / 30Active Projects

Material defects and quality concerns

A clear opportunity to identify and address issues

What counts as a defect

A concern should be assessed against accepted requirements, such as agreed functionality, accessibility provisions, responsive layouts, compatible integrations or deliverables, rather than an uncommunicated personal preference.

Correction or alternative remedy

Where reasonable and lawful, an appropriate correction may address an in scope defect. Serious nonperformance, failed remedies or other circumstances can instead justify cancellation, repayment or another appropriate lawful remedy.

Proof of the issue

Helpful materials include the approved scope, steps to reproduce a problem, affected URLs, screenshots without secrets and relevant Project messages. A complaint does not require public disclosure of sensitive website access.

SECTION 12 / 30Active Projects

Revisions and changes in requirements

Corrections differ from new work

Included revisions

Agreed revision rounds and acceptance criteria guide requests for changes to the original deliverable. They should be communicated at approval and applied fairly.

Additional requirements

A new page, integration, design direction or feature not included in the accepted Project may require a new scope and fee. Rejecting an unapproved addition does not by itself prove that contracted work was deficient.

Disagreement about scope

Where the parties interpret requirements differently, the agency should review the written record and request clarification rather than automatically treating either position as correct.

SECTION 13 / 30Active Projects

Delays and missed delivery expectations

Review causes, communication and agreed dates

Actual timeline

The approved Project should identify time estimates, milestones and relevant dependencies. A material delay should be explained against agreed dates and any recorded extensions.

Causes beyond one party

Late Client approvals, unavailable hosting, external API limits or other dependencies can affect timing. Such factors should be documented but must not become an automatic excuse for avoidable nonperformance.

Suitable outcomes

Depending on the circumstances, an updated schedule, correction, partial adjustment, cancellation or repayment may be appropriate. Mandatory remedies remain available where applicable.

SECTION 14 / 30Active Projects

Client cooperation and unavailable access

Missing inputs may affect what can be delivered

Necessary contributions

A Client may need to provide lawful access, content, feedback, test accounts or decisions within agreed timeframes. Failure to do so can affect performance and schedule.

Reasonable notice

Before treating missing cooperation as grounds for termination or charges, the agency should identify the specific missing input and provide a reasonable opportunity to respond where practical.

Fair allocation

A Client caused delay does not automatically entitle the agency to retain all funds. Any financial outcome should be supported by the agreed terms, performed work and applicable rights.

SECTION 15 / 30Active Projects

Technical impossibility and external dependencies

Some constraints change what is feasible

Unexpected constraints

Plugin compatibility, hosting restrictions, external vendor changes and security findings may reveal an obstacle not reasonably identifiable before assessment.

Propose a documented choice

The agency should explain available alternatives, revised costs, timing or the need to stop a particular element. Materially different paid work should not proceed without the required agreement.

Unperformed commitments

Where a Project cannot continue, the treatment of paid amounts depends on what was earned or properly committed, responsibility for the obstacle and any applicable legal rights.

SECTION 16 / 30Active Projects

Security risks and serious termination

Stopping risky work does not decide the refund automatically

When work may be stopped

Serious unlawful instructions, unauthorized system access, account abuse, material breach or unacceptable security risks can justify declining or pausing a Project under the applicable Terms.

Financial separation

The decision to stop work and the accounting treatment are separate questions. The agency should still assess what was lawfully performed, the relevant agreement and any remaining refundable amounts.

Protection of materials

Upon termination, handle entrusted Client information, temporary credentials and confidential files according to the Content Privacy Policy and any applicable data obligations.

SECTION 17 / 30Payments

Refund method and return of funds

Cash refunds must use a real authorized route

Method of repayment

Where a money refund is due under applicable law, accepted terms or an approved resolution, it should be arranged through a lawful supported provider route, ordinarily considering the original payment method where practical.

Provider restrictions

Banking, gateway or platform limitations may affect the procedure but do not automatically eliminate mandatory repayment obligations. Alternate arrangements should be explained and agreed where legally permissible.

Confirmation

A clear decision should identify the amount, currency, intended route and any verification steps. Do not describe a pending refund as completed until the provider or responsible finance process confirms it.

SECTION 18 / 30Payments

Internal credits and platform balances

An accounting credit is not a cash repayment

Different instruments

An internal account balance, unused project credit or milestone adjustment may have different legal and practical effects from returning funds to a payment account.

No forced substitution

An internal credit should not be represented as satisfying a cash refund obligation where applicable law or an agreed enforceable resolution requires repayment.

Configuration dependent

The available account and refund actions depend on the actual WorkReap and payment provider configuration. This policy does not claim that customer balances are a separately regulated escrow or trust facility.

SECTION 19 / 30Payments

Processing times, currency and charges

Avoid unverified timelines or deductions

Timing

The time for a properly approved refund can depend on its payment route, provider review, bank processing and transaction facts. The agency should provide an accurate status when known and avoid inventing a fixed universal deadline.

Currency and conversion

Exchange rates or provider conversion steps may affect the amount received in another currency. Such differences should be explained in accordance with applicable provider rules and law.

Fees and taxes

Any proposed deduction for gateway fees, taxes or external costs must be grounded in the agreement, advance disclosures and applicable rights. No blanket fee deduction is established by this policy.

SECTION 20 / 30Payments

Duplicate charges and unauthorized payments

Report transaction errors promptly

Duplicate or incorrect charges

If a Client sees a duplicate charge, incorrect amount or an apparently unauthorized payment, they should contact the agency using the relevant Project record or Support Center and, where appropriate, their payment provider.

Verification

To protect account holders, the agency may verify that the requesting person is authorized to discuss the transaction. Do not send full payment card data, banking passwords or account recovery codes.

Preserve provider remedies

The agency should investigate legitimate errors and cooperate with applicable provider processes without interfering with mandatory payment protections or proper fraud investigations.

SECTION 21 / 30Payments

Expert assignments and earned compensation

The Client contracts through the managed agency

Agency relationship

Esposearch coordinates approved Experts under its agency model. A Client refund claim relates to the Client Project agreement rather than an automatic direct contractual claim against an individual Expert.

Professional remuneration

Any Expert payment, suspension or adjustment follows the applicable professional assignment, verified work and agency arrangements. Client funding is not automatically unrestricted Expert earnings.

Fair review

The agency may obtain information from the relevant Expert while protecting Client confidentiality. A financial resolution should distinguish work properly performed from disputed or unearned amounts.

SECTION 22 / 30Disputes

How to request cancellation or repayment

One clear support route for Project concerns

Start with your Project

Where available, use the authenticated Project conversation or relevant administrative control so that the request remains linked to the accepted scope and payment record.

Contact Support

If the necessary action is unavailable, contact the Support Center or email admin@esposearch.net. Include the Project reference and a short description of the concern; do not publish confidential payment information.

State the request

Explain whether you seek cancellation before work starts, cancellation during implementation, correction of a defect, refund of an amount, or review of an unauthorized transaction.

SECTION 23 / 30Disputes

Information needed for an assessment

Keep the request clear and evidence based

Basic details

Provide the Project identifier, agreed deliverables, relevant payment reference, dates, milestone or deliverable affected and the outcome requested.

Supporting materials

Useful evidence can include relevant messages, accepted scope, testing notes, review comments, delivery records and appropriately redacted screenshots.

Privacy and security

Do not send full bank account access, API tokens, unnecessary identity documents or unrestricted administrator passwords in an ordinary refund enquiry. Follow an approved restricted channel if further technical evidence is needed.

SECTION 24 / 30Disputes

Review, communication and possible resolutions

A decision should explain its basis

Fact gathering

Authorized administration may compare the Project agreement, milestone status, performed work, invoices, Client submissions and relevant Expert information. Additional clarification may be requested.

Possible outcomes

Depending on the case, a correction, revised delivery plan, termination, full or partial refund, lawful account adjustment or other appropriate remedy may resolve the concern.

Written outcome

The final response should identify the affected Project, key reasons for the decision and the financial or practical next step. The agency should avoid promising an outcome before reviewing the evidence.

SECTION 25 / 30Disputes

Escalation and external remedies

Internal review does not remove legal rights

Concerns about the first decision

A Client can request clarification or further review through the Support Center where material information was overlooked or a factual error may have occurred.

Payment provider remedies

Where available under the provider rules, a Client may pursue a chargeback, unauthorized transaction claim or other buyer protection process. Relevant timelines and eligibility depend on the provider and jurisdiction.

Consumer rights and regulators

Nothing in this policy prevents a person from exercising applicable statutory remedies or approaching a competent authority or court. Duplicate recovery of the same amount may still need appropriate accounting treatment.

SECTION 26 / 30Rights

Digital deliverables and software licensing

Downloads and code require careful rights treatment

Project deliverables

A custom WordPress Project may produce downloadable files, theme or plugin code, designs, technical documentation or configured features. These are Project deliverables and must be assessed against the accepted scope.

Acceptance and defects

Delivery or downloading of a file does not automatically exclude legal or contractual remedies where that file is defective, incomplete or materially inconsistent with what was agreed.

Licenses and ownership

Open source and other third party licenses continue to apply. Any transfer or grant of rights in newly produced custom work follows the applicable written Project terms.

SECTION 27 / 30Rights

Records, confidentiality and data handling

Refund enquiries should not expose client websites

Evidence retention

Relevant Project correspondence, payment status, invoices and resolution records may be retained for lawful contract administration, financial reconciliation, investigations or disputes.

Confidentiality

Sensitive website information must be handled under the Content Privacy Policy. Personal data in messages and records remains subject to the Privacy Policy and applicable data protection obligations.

Secure contact

Never post passwords, secret keys or full payment card details to public Project fields. Use a suitably restricted evidence route where needed.

SECTION 28 / 30Rights

Questions raised after Project completion

Completion does not automatically erase valid claims

Post completion review

A Client can report a genuine concern after a Project is marked complete. The agency should review the accepted scope, completion evidence, any agreed correction period and applicable statutory rights.

Maintenance and new requests

Ongoing maintenance and later upgrades are not automatically included after handover. A new requirement may need a separate Project, while a genuine prior defect should be assessed under the original agreement.

Records and resolution

Supporting documents, testing evidence, relevant dates and communications help distinguish a technical defect from new or changed expectations.

SECTION 29 / 30Rights

Training and separate websites

Do not confuse website Project purchases with courses

Separate destinations

Esposearch.courses operates as a separate training and resource destination. Its course and resource purchases should be assessed under the terms actually presented for that transaction.

Other providers

Licenses, domains, hosting subscriptions or products purchased directly from third party providers may be subject to their own cancellation terms, subject to applicable law.

Approved agency Projects

This policy focuses on custom Project engagements commissioned through Esposearch.net and does not create a general digital product returns route on this site.

SECTION 30 / 30Rights

Updates and official refund contact

Clear version control and available help

Version and publication

This draft was prepared on 3 November 2026 and must receive operational and legal approval before publication. The approved effective date should be displayed once confirmed.

Changes

Material revisions should be explained as required by applicable law. A later version should not be used retroactively to remove rights already accrued under a binding agreement.

Official channel

For Project cancellation, repayment or dispute questions, use the authenticated Project record where available, visit https://esposearch.net/support/ or write to admin@esposearch.net with the Project reference. The agency will assess the request using its actual records and applicable terms.

Making a refund request

A clear process for raising a Project concern.

Use the authorized Project channel where available or reach out through Support. A request should never require publicly sharing secrets.

01 / REVIEW PROCESS

Identify the Project

Locate the accepted scope, transaction and milestone in the relevant account.

02 / REVIEW PROCESS

Describe the concern

Explain cancellation, missing work, a defect or a payment error clearly.

03 / REVIEW PROCESS

Review the evidence

The agency considers applicable terms, work records and information from relevant parties.

04 / REVIEW PROCESS

Communicate the outcome

Receive the decision and any eligible correction, accounting adjustment or repayment route.

Please do not send passwords, API secrets, complete card numbers or unrelated personal records in ordinary refund messages. Use the Project reference, redacted evidence and an explanation of the remedy sought.
Common refund questions

Understand the details before you decide.

These answers introduce the policy. The accepted Project terms, evidence and applicable law remain the basis of an actual decision.

Can I cancel a Project before work begins?
You may request to stop an unaccepted Project or an approved Project that has not started. Any money already collected must be assessed against accepted terms, properly performed preparation, documented commitments and applicable rights.
Does cancelling a Project always mean a full refund?
No. A cancellation and a refund are distinct. The outcome depends on what was agreed, what has been done, financial commitments, any failure to perform and the rights that apply.
Are deposits always nonrefundable?
No blanket nonrefundable deposit rule is established. The accepted agreement, actual work or costs, and applicable consumer or payment rights determine treatment.
What happens if a milestone has been completed?
Completed and properly accepted milestones may be evaluated separately from unfinished work. A valid quality concern or statutory remedy can still affect an accepted deliverable.
What if the work does not match the approved scope?
Identify the difference using the relevant requirements and evidence. Depending on the case, the remedy could involve an in scope correction, revised delivery, cancellation, refund or another lawful resolution.
Is a platform credit the same as a cash refund?
No. An account credit is not automatically money returned to your original payment method. Where repayment of money is due, the arrangement must use an appropriate lawful route.
How long does a refund take?
No universal timeframe is promised. Provider handling, the payment method and the actual circumstances affect processing. The agency should communicate an accurate status when one is available.
Can I request review after a Project is marked complete?
Yes, you can raise a genuine issue. The accepted scope, deliverables, acceptance record, applicable limitations and legal rights will determine the available remedy.
What if an external plugin or hosting provider fails?
An external dependency must be considered in context. The review should distinguish vendor responsibility, the agency’s agreed obligations, approved alternatives and what work was actually performed.
How do I contact the agency about a disputed payment?
Use your relevant Project communication or visit the Support Center. You can also email admin@esposearch.net with a Project reference and a concise summary, without sharing banking credentials.
Important related information

Review the documents that govern your Project.

Understand the agency agreement, data practices and support routes before submitting confidential evidence or authorizing payment.

Clarity before commitment

Have a Project payment question?

Share the Project reference, approved scope and a concise explanation of your concern. The agency can review the evidence and explain the available next step without promising a predetermined outcome.

For new WordPress requirements, you can also start a separate Project after reviewing the agreed scope and payment terms.