Paddle's approved-domain check only applies in the browser
I ship a lot of small products. Browser extensions, little SaaS tools, one game. Most of them live on their own subdomain and do exactly one job. For a long time the worst part of starting a new one wasn't the product. It was billing. Bank verification, ID verification, waiting for approval, recreating the same plans, wiring the same webhooks, testing the same four subscription states. Every…
Paddle has introduced a domain check process that applies only within a browser environment. This change streamlines the billing process for small products, such as browser extensions and SaaS tools, by consolidating billing verification, ID checks, and subscription states into a single domain. The critical aspect of this process is the Paddle.js checkout overlay, which must open from an approved domain.
The server-side does not care about the domain, and webhook signature verification, customer portal sessions, and internal endpoints all remain unaffected by this domain restriction. By having the checkout process occur on an approved domain, the system ensures a secure and efficient payment experience without any user notice of the transition.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
