GetPaidHQ

What GetPaidHQ does

GetPaidHQ handles recurring subscription billing on infrastructure you operate. A single subscription can combine fixed, usage-based, tiered, or hybrid pricing, with usage events metered through its API.

It can create invoices, hosted checkouts, and shareable payment links. Charges can be routed by region, customer, or failover need. Its intended users include teams working with regional, in-house, or multiple processors, as well as organizations with data-residency or ownership requirements.

Fees and plans

There is no software charge for the MIT-licensed Self-hosted plan. It includes fixed, usage-based, and hybrid pricing, built-in dunning and invoicing, your own gateway, and community support. You pay for the infrastructure you run and operate.

The Cloud plan is listed as price on request. The maker says pricing is being finalized and asks teams to contact it for early-access terms. It is described as fully managed hosting with priority support, an SLA, onboarding assistance, and custom adapter development on request.

Where it runs

The published platforms are API, self-hosted, and web. The project is not identified in the Apple App Store, Google Play, Chrome Web Store, or Microsoft Store, so no native phone app is listed.

Self-hosting requires Docker, Go 1.26 or later, make, databases, configured processors, services, and environment variables. The stated stack includes Go, PostgreSQL, Temporal, and NATS.

Protection and rules, as published

The maker says that running the software yourself keeps payment and customer data on your own infrastructure. The self-hosted version carries no software charge under the MIT License.

Its API documentation says to keep API keys on servers and out of browser code, mobile apps, logs, and URLs. Most API requests use bearer API keys, with an x-api-key header option also described. Signed webhooks include automatic retries, and idempotency keys support safe write retries.

The maker labels its privacy policy a placeholder and says qualified counsel should review it before reliance.

Strengths

Self-hosting gives teams control over infrastructure and data location without a software fee. The API covers customers, catalogs, orders, subscriptions, usage, invoices, payments, webhooks, and dunning.

The listed processors are Checkout.com and Paystack; developers can connect others using the adapter interface. Its dunning feature detects failed payments, chooses retries based on decline reason and customer history, and offers links for customers to update payment details.

Official SDKs are listed for Node.js, Python, PHP, and Go. Documentation covers deployment, architecture, billing, metering, dunning, authentication, pagination, errors, rate limits, webhooks, and endpoints.

Catches and conditions

The managed Cloud service is not yet available. The maker describes it as coming soon, with pricing still under review, and requests contact for early access.

Running the free plan means operating infrastructure and configuring services, databases, processors, and environment variables.

The pages describe open beta availability. There is no customer billing portal listed, and no native store listing is identified.

Who may want another tool

Skip GetPaidHQ if you need an available managed service today, a native iPhone or Android app, or a customer billing portal. A team that does not want to run its own infrastructure may also prefer a hosted product.

Verdict

GetPaidHQ fits engineering-led teams that can operate a billing stack and need processor choice, regional routing, usage metering, or control over where payment data sits. The free self-hosted plan includes a broad API, dunning, invoicing, and gateway adapters.

Cloud hosting is not available yet, its price is unsettled, and the privacy policy is expressly a placeholder.

Questions