Payment Policy
Payment Policy
This Payment Policy explains how Zaya Web Studio handles project payments, advance payments, invoices, milestones, third-party costs, cancellations, refunds, overdue payments and final project handover.
Overview
Zaya Web Studio provides website development, e-commerce solutions, Shopify development, mobile application development, backend systems, admin panels, integrations, SEO-related services and other custom digital solutions.
Because every project can have a different scope, technology stack, development timeline and level of customization, the applicable payment structure may differ from project to project.
The quotation, proposal, invoice or project agreement provided for a particular project may contain additional payment terms that apply to that project.
Services Covered by Payment Terms
Payment arrangements under this policy may apply to different services offered by Zaya Web Studio.
Website Development
Business websites, custom websites, landing pages, corporate websites and other web projects.
E-commerce
Online stores, product systems, shopping carts, checkout systems and e-commerce integrations.
Shopify
Shopify store development, customization, themes, integrations and related services.
Mobile Applications
Android applications, custom application systems, APIs and associated backend development.
API & Integrations
Payment gateways, third-party APIs, external services and custom integrations.
Digital Services
Technical SEO, website support, optimization, maintenance and other agreed digital services.
Payment Structure
Depending on the project, payments may be structured as a complete upfront payment, advance plus balance, milestone-based payments or recurring payments.
| Payment Model | Typical Application | Description |
|---|---|---|
| Full Payment | Small / fixed services | The complete service amount is paid before or at the beginning of the service. |
| Advance + Balance | Development projects | An agreed advance is paid before development and the remaining amount becomes payable according to the agreed project stage. |
| Milestone | Larger projects | The project is divided into stages with separate payment obligations. |
| Recurring | Maintenance / support | Payments may occur monthly, quarterly, annually or according to the applicable service agreement. |
Advance Payments
An advance payment may be required before development begins. An advance confirms the client's intention to proceed and may allow Zaya Web Studio to allocate development resources and begin project preparation.
What the advance may cover
- Project planning and technical preparation.
- Initial design and development work.
- Developer time reserved for the project.
- Project-specific configuration.
- Certain third-party resources where agreed.
Clients should keep the transaction reference, receipt or payment confirmation until the relevant project payment has been completely reconciled.
How Project Payments Work
A typical development project may follow a sequence similar to the following.
Requirement Discussion
Project requirements, features, technology, timeline and deliverables are discussed.
Quotation & Scope
The applicable project price and scope are communicated to the client.
Project Confirmation
The client confirms the project and the agreed payment arrangement becomes applicable.
Initial Payment
The agreed advance or first payment is received before applicable development work begins.
Development
Development proceeds according to the approved scope and project requirements.
Review / Milestone
Depending on the project, a milestone review and additional payment may become applicable.
Final Settlement
Any remaining balance is settled according to the agreed payment terms.
Final Delivery
Applicable final deliverables and handover are completed according to the project agreement.
Milestone Payments
For larger projects, the total project value may be divided into multiple payment milestones. A milestone can correspond to a defined stage of the project.
Planning → UI/Design → Development → Integration → Testing → Deployment → Final Handover.
The exact number of milestones, amount payable at each stage and delivery conditions should be specified in the applicable project quotation or agreement.
Invoices & Payment Records
Payment-related documentation may include quotations, invoices, receipts, payment confirmations, project references and transaction records.
A payment document may contain
- Client name or business name.
- Project or service description.
- Invoice or reference number.
- Amount payable.
- Applicable taxes or charges.
- Payment due date.
- Payment status.
Third-Party Costs
Some projects require external products, platforms, subscriptions, licenses or services. These costs may be separate from Zaya Web Studio's development fee unless specifically included in the quotation.
Domain Registration
Domain registration, transfer and renewal charges may be controlled by the applicable registrar.
Hosting
Hosting plans, renewals, resource upgrades and server-related charges may be separate.
API Usage
Some APIs charge according to usage, requests, subscriptions or transaction volume.
Software Licenses
Premium themes, plugins, software, fonts and licensed assets may have separate costs.
Domain & Hosting Payments
Where domain or hosting services are purchased for a client, the applicable quotation should identify whether these services are included, separately charged or provided directly by the client.
Renewal responsibility
Domain and hosting services are generally recurring services. Renewal costs may differ from the initial purchase price because providers can change pricing, plans, taxes or available resources.
Failure to renew a domain or hosting service on time may result in suspension, expiration or additional restoration requirements imposed by the external provider.
Taxes & Applicable Charges
Where applicable, taxes, government charges, payment processing fees or other legally applicable charges may form part of the amount payable.
The applicable treatment can depend on the service, customer location, transaction structure and applicable laws and regulations.
Clients should refer to the applicable quotation or invoice for the amount payable for their specific transaction.
Additional Work & Scope Changes
A project price is normally based on the agreed scope. Requests that materially expand that scope may require additional charges.
Examples
- Additional pages.
- Additional application features.
- New API integrations.
- Additional payment gateways.
- New admin modules.
- Major redesign after approval.
- Additional revisions beyond the agreed scope.
- Data migration or recovery work not included originally.
Where practical, additional work should be discussed and its applicable pricing confirmed before the work begins.
Project Cancellation
A client may request cancellation of a project by contacting Zaya Web Studio through an authorized communication channel.
Cancellation does not automatically mean that all previously paid amounts are refundable.
Cancellation review may consider
- Work already completed.
- Development time already used.
- Resources reserved for the project.
- Third-party purchases.
- Domain or hosting registration.
- Premium software or licenses.
- Project milestone already completed.
Refunds
Refund eligibility depends on the applicable project terms, stage of development, completed work, third-party expenses and other circumstances relevant to the transaction.
Completed work
Amounts relating to work already completed may be treated differently from amounts relating to work that has not yet started.
Third-party expenses
Domain registrations, hosting purchases, licenses, subscriptions, transaction fees and other irreversible third-party expenses may be non-refundable where the external provider does not provide a refund.
Submitting a refund request does not automatically guarantee approval. The request should be evaluated against the applicable project and payment terms.
Failed, Reversed or Unsuccessful Payments
A payment attempt is not necessarily considered a successful payment until the transaction has been successfully processed and received.
If a transaction fails, is reversed, cancelled or otherwise does not settle successfully, the applicable amount may remain outstanding.
Duplicate payments
If a client believes that the same invoice or project amount has been paid more than once, the client should provide the relevant transaction references so the payment records can be reviewed.
Overdue Payments
Where a payment becomes overdue, Zaya Web Studio may pause affected development, delivery, deployment or support activities until the outstanding payment is resolved.
Development Pause
Work may be temporarily paused when a required milestone payment remains unpaid.
Delivery Delay
Final delivery or handover may be delayed while applicable balances remain outstanding.
Timeline Adjustment
A payment-related work pause can require the original timeline to be adjusted.
Service Renewal
External services may have separate renewal deadlines regardless of the development project.
Final Payment & Project Handover
Depending on the project agreement, final project handover may be subject to settlement of the applicable outstanding balance.
Handover can include website deployment, application delivery, administrative access, source code where included, documentation or other agreed deliverables.
“Project completion and payment completion are two related but separate parts of the project lifecycle.”
Payment & Ownership
Ownership and usage rights for project deliverables depend on the applicable project agreement and the nature of the deliverable.
Third-party software, libraries, themes, plugins, APIs, fonts, stock media and other externally licensed resources remain subject to their respective licenses.
Where source-code transfer or intellectual-property transfer is included in a project, the applicable quotation or agreement should define the relevant scope of that transfer.
Payment Security
Clients should make payments only through payment instructions communicated by authorized representatives of Zaya Web Studio.
Never share card numbers, passwords, OTPs, banking PINs or other sensitive authentication credentials with another person claiming to represent Zaya Web Studio.
Payment Disputes
If a client believes that an invoice, transaction, payment status or refund decision is incorrect, the matter should first be raised directly with Zaya Web Studio.
Information that may help
- Client name.
- Project name.
- Invoice number.
- Transaction reference.
- Payment date.
- Amount involved.
- Description of the issue.
- Relevant supporting documents.
Policy Updates
Zaya Web Studio may update this Payment Policy from time to time to reflect changes in services, payment methods, commercial practices, technology, applicable requirements or internal processes.
The latest published version should be treated as the current general Payment Policy for website visitors, subject to specific terms agreed for an individual project.
Frequently Asked Questions
Is an advance payment required for every project?
Not necessarily. The payment structure depends on the project and the terms communicated in the applicable quotation or agreement.
Can a large project be divided into milestones?
Yes. Larger projects may use milestone-based payments where each stage has a defined scope and applicable payment obligation.
Are domain and hosting included in development fees?
This depends on the applicable package or quotation. Clients should check the specific project quotation for inclusion and renewal terms.
What happens if I request an extra feature?
If the request falls outside the agreed project scope, additional pricing may apply.
What happens if a payment fails?
The amount may remain outstanding until the transaction is successfully processed and verified.
Are refunds automatic?
No. Refund requests are subject to the applicable project terms, completed work, third-party costs and other relevant circumstances.
Can payment delays affect project delivery?
Yes. Where a payment is required before a milestone or final handover, an outstanding payment can cause work or delivery to be paused until the payment is resolved.
What if I accidentally make a duplicate payment?
Contact Zaya Web Studio with the relevant transaction references so the duplicate payment can be reviewed.
Zaya Web Studio — Payment Policy
This document is part of the Zaya Web Studio Legal & Information Center and describes the general framework for payments, billing, project charges and related matters. Project-specific quotations, invoices or agreements may contain additional terms applicable to individual services.