Payment and Refund Policy

Information required before approval

• Billing contact, notice address, and confirmed assumed-name/DBA status
• Approved deposit, milestone, cancellation, refund, and dispute rules
• Tax treatment and invoicing requirements
• Support subscription renewal and cancellation timing
• Governing client agreements and any mandatory state-law rights

Scope and governing agreement

This policy should explain the technical payment flow for project invoices and support services. The signed proposal, statement of work, or services agreement must define the actual fees, schedule, deliverables, and remedies.

If this policy conflicts with a signed client agreement, the final documents must state which controls. Counsel must approve that hierarchy.

Invoices and authorized amounts

Invoices are created by authorized company personnel in U.S. dollars unless a signed agreement states otherwise. Amount, currency, purpose, and invoice association are controlled by server records; clients cannot enter or modify the amount charged.

An invoice should identify the project or support service, issue and due dates, status, and any milestone or billing period without exposing sensitive payment credentials.

Payment methods

Payments may be processed by Stripe using eligible cards or Apple Pay where supported by the payer’s device, browser, region, account, and Stripe configuration.

Stripe or the wallet provider handles payment credentials through its interfaces. Availability of a particular method is not guaranteed, and another approved method may be required.

Deposits and milestones

A signed agreement may require an initial deposit, milestone payments, a final delivery payment, time-and-materials billing, or recurring support charges. A payment does not change scope or constitute acceptance except as the authorized agreement expressly provides.

Recurring support

Recurring support must be authorized through clear subscription or contract terms that state the amount or pricing method, billing interval, coverage, renewal, cancellation process, and treatment of work outside scope.

Cancellation should stop future renewals according to the approved terms; it does not automatically refund services already delivered or charges already incurred. Counsel must define notice periods and mandatory exceptions.

Refund requests

Refund eligibility must be evaluated against the signed agreement, work completed, committed third-party costs, payment status, and applicable law. The production policy must not promise a fixed outcome before these rules are approved.

A refund request should identify the invoice and reason through the monitored billing channel. Do not ask a client to send full card details, authentication codes, or wallet credentials.

Failed, duplicate, and disputed payments

A failed payment does not mark an invoice paid. Duplicate provider events must be handled idempotently, and an apparent duplicate charge should be investigated against provider and internal records.

Clients should contact the monitored billing channel promptly before initiating a charge dispute when practical. Nothing in the final policy may waive rights that cannot lawfully be waived.

Third-party charges, taxes, and changes

Infrastructure, model usage, vendor services, payment processing, and taxes may be handled as stated in the signed agreement. The company must not add undisclosed charges.

Material policy changes should be dated and communicated as required. Billing contact and legal notice details must be completed before publication.