Mollie
On hold after review: Mollie is built for one-off e-commerce, and its recurring model doesn't fit our webhook-relay approach. Only one-time payments would map cleanly, so it's parked until demand justifies the effort. See the changelog.
Razorpay
Requested via community feedback, a leading India-based payment provider.
Crypto payments
Requested via community feedback (e.g. Coinbase for BTC and other coins). No committed timeline yet.
Whop
Digital marketplace popular with online communities and newsletter creators.
Hotmart
Leading provider for digital products and online courses in Latin America.
Building in public, out loud
A running series of posts on what shipped, what got reconsidered, and what we decided not to build, including the reasoning. Word of mouth is how a tool like this actually spreads, so the work happens in the open rather than behind a launch announcement.
Support requests you can actually follow
Writing in from the dashboard used to hand you a reference and little else. Your request now carries a subject you wrote yourself, and its status moves on its own as we work on it, so you can see where it stands without asking. The address we reply to is yours to change, which used to look like a choice and quietly was not. And a status change reaches you by email rather than waiting for you to open the page.
A warning that means something
Six of eight provider cards claimed they needed attention while the connection behind them was perfectly healthy. They were counting every delivery that had ever failed, including the ones from setup months earlier, and nothing ever aged out. A card now describes the connection, delivery trouble stands next to it with a date behind it, and amber only appears when something is genuinely waiting for you. A warning that is always on is not a warning.
One product, one outcome, whichever button they clicked
A payment tells us which product was bought, never which button or table column it was bought from. That means there can only be one answer to "what happens when somebody buys this". Until now the same product could carry a different answer per widget, and a purchase quietly applied all of them, so which newsletter setting you ended up with depended on the order they had been saved in. There is one rule per product now, and the database refuses anything else.
What is new, written once instead of twice
The changelog you are reading and the bell in the dashboard used to be two hand-written lists in the source code. Every announcement had to be written twice, in two voices, and shipping one meant releasing the whole application. They are one thing now, and publishing a line no longer waits on a release. Each item in the bell links to its own entry here rather than dropping you at the top of the page.
Pages that arrive finished, instead of drawing themselves
Every public page was one application that assembled itself in your browser, so a search engine received the same empty file for eighteen different addresses. The landing page, the comparisons, the roadmap, the changelog, the legal pages, both forms and this board now ship as finished HTML, each with its own title and its own description. The dashboard stays an application, which is what it should be.
Run it yourself without signing up anywhere else
PayGlue is source-available, but starting your own copy meant first creating an account with a hosted identity service, or it would not even boot. That is a strange first step for software you were about to run on your own machine. An installation can now keep its accounts in its own database, and a setup wizard walks through the first account and your first publication. Whichever way you sign in, you can still run more than one publication of your own.
Test any connection without a real purchase
A "Send test" button on each mapping fires a real event through the full pipeline against a test email, so you can confirm a connection works before your first customer does.
Founding Member: from one-time to subscription
Done differently than planned: rather than build a hand-off for one-time buyers, founding spots are now plain monthly subscriptions at a rate that never rises. Nothing to convert at launch, and nothing to miss. The single buyer who joined before the switch keeps the deal they were promised.
Patreon provider support
Connect Patreon so an active pledge automatically grants your mapped Ghost access, and a cancelled pledge revokes it. Map each Patreon tier to the access it unlocks.
Grace periods for downgrades and cancellations, plus reminder emails
Downgrading to a lower plan or canceling your subscription now comes with a clear grace period before anything actually changes, with a few reminder emails along the way.
Creem provider support
Creem.io joins the supported payment providers, and became the default for PayGlue's own billing too.
Ko-fi provider support
Ko-fi fully integrated: donations and memberships sync to Ghost access, popular with the Ghost community for tips.
Paddle provider support
Paddle fully integrated as a merchant-of-record option: webhook verification, product picker, and Ghost membership sync, tested against a real live purchase.
Gumroad provider support
Gumroad fully integrated: webhook sync for sales and subscriptions, product picker in the Buy Button dashboard.
Social login providers
Sign in with Google or GitHub instead of, or alongside, a magic link email. Connect or disconnect either anytime from account settings.
Two-factor authentication
Optional TOTP via any authenticator app (Google Authenticator, 1Password, Authy) plus one-time backup codes, for accounts using magic-link sign-in.
Automated dependency scanning + CI pipeline
Dependabot security scanning and a CI pipeline with full test coverage across the open-source and production codebase.
Open Source release
Full codebase public at github.com/PayGlue/PayGlue-OS under BUSL 1.1, including a complete self-hosting setup guide.
PayPal provider support
PayPal subscriptions fully integrated: webhook verification, plan picker, and Ghost membership sync.
Lemon Squeezy provider support
Lemon Squeezy fully integrated: webhook verification, product picker, and Ghost membership sync.
API Proxy on api.payglue.io
Cloudflare Worker proxies all API calls, so Supabase and Railway URLs are no longer exposed to users.
Railway Django backend live
Django backend deployed on Railway with gunicorn, PostgreSQL, and secure environment secrets.
Webhook event log with failure visibility and replay
Full inbound event log with status filters, payload inspector, error details, and one-click replay for failed or skipped events.
Founding Member Beta Launch
Post-checkout auto-login, dynamic pricing tiers, Polar production checkout, Cloudflare Turnstile.
Waitlist + landing page live
payglue.io live with waitlist signup, Prefinery integration, and real-time pricing.
Dashboard and tenant architecture
Multi-tenant dashboard: orgs, roles, Ghost API key management, event log.
Webhook relay engine
Webhook receiver, event normalization, automatic retry with exponential backoff, dead-letter queue.
Provider mapping system
Product-to-tier mapping, multi-provider support, Stripe coexistence.
Cloudflare Access + WAF for dev tunnels
Secure Cloudflare tunnels for internal dev environments.