Billing

Invoices & payment

Last updated: August 15, 2026

This page describes how payment works for custom software development services provided by Viewport Solutions. It is intended for clients, accountants, and payment processors reviewing how charges are initiated and supported.

1. Merchant information

2. What you are paying for

Custom software development performed by a single independent contractor. Services include designing and implementing web application dashboards, administrative interfaces, internal tools, bug fixes, and small feature work inside existing products built with Vue, Nuxt, Ruby on Rails, Phoenix LiveView, JavaScript, and related technologies. I do not sell physical goods, downloadable products, subscriptions, or access to software hosted by me. I do not operate a marketplace. Each client receives a written scope and a Stripe invoice in USD before payment is due. Work is delivered as code changes, configuration, or documentation in the client’s repository or environment, as specified in the agreement.

Each invoice describes a specific engagement, for example:

• “Dashboard UI — filters, export, and revenue chart — March 2026”
• “Admin user management module — fixed scope per email agreement dated [date]”
• “Production bug fix — checkout validation — as scoped in thread [reference]”
• “Retainer — 10 hours internal development — April 2026”

There is no standing subscription sold on this website. Recurring invoices, if any, are created manually per retainer agreement and sent through Stripe — not via a checkout button on this site.

3. How an engagement becomes a charge

1. You submit a project brief via the contact form or email
2. We discuss requirements and I provide a written scope and price in USD
3. You accept the scope in writing (email reply is sufficient)
4. I create a Stripe invoice with line items matching the agreed scope
5. Stripe emails the invoice with amount, due date, and secure payment link
6. You pay on Stripe’s hosted page — not on this website
7. Work begins per the start condition stated in the scope (usually after payment)

4. Payment methods and currency

Invoices are denominated in USD. Available payment methods (credit card, debit card, bank transfer, etc.) are shown on Stripe’s invoice page at the time of payment. Stripe may charge currency conversion or processing fees according to their terms and your bank.

This website does not collect, transmit, or store payment card numbers, CVV codes, or online banking credentials. All payment data is entered on stripe.com or Stripe-hosted invoice URLs.

5. Pricing model

Prices are custom-quoted per project. This site does not display a public price list because scope varies widely. The invoice you receive is the binding price for that engagement. Additional work requires a new quote and invoice.

See pricing on the homepage for typical engagement types (hourly/discovery, fixed deliverable, retainer).

6. Receipts and records

After payment, Stripe provides a receipt to the email address on the invoice. I retain invoice copies for tax and accounting purposes as required by applicable law. You may request a copy of an invoice or written scope by emailing contact@viewportsolutions.com.

7. Refunds and cancellations

Refunds are handled according to the Refund & cancellation policy. Summary: full refund within 48 hours if work has not started; pro-rata for unused prepaid hours; no refund for completed work per agreed scope.

8. Billing support & disputes

For questions about an invoice, duplicate charges, or delivery concerns:

• Email contact@viewportsolutions.com with the invoice number
• Typical response time: 1–2 business days
• Please contact me before opening a chargeback with your bank

For card security questions, see Stripe’s privacy policy and this site’s privacy policy.

9. What this website does not do

• Does not sell physical products or ship goods
• Does not sell downloadable software licenses unrelated to custom work
• Does not offer self-serve subscription signup or automatic recurring billing on this domain
• Does not store card data or run its own payment form