Paddle?

NOT REALLYA prototype of the interface is possible, but the durable product depends on difficult systems beyond the UI. Build a safer adjacent workflow instead.

BUILD FIRST

A non-sensitive or read-only version of the core experience
A manual review step wherever correctness or trust matters
A narrow companion tool that removes a real piece of work

LEAVE FOR LATER

Regulated decisions, payments, or irreversible actions
Claims of correctness, compliance, or uptime that the MVP cannot support
Sensitive integrations until security, support, and auditability are ready

RESEARCH NOTES

What this tool actually does.

Checked 2026-09-06

Paddle is a payments and billing platform that acts as the Merchant of Record (MoR) for SaaS, mobile app, AI, and digital product companies. As MoR, it takes legal responsibility for transactions: it calculates, collects, and remits sales tax (VAT, GST, sales tax) across 200+ countries and handles refunds, chargebacks, fraud screening, and buyer support. It offers a subscription billing engine supporting trials, proration, pauses, upgrades, one-time charges, invoices, and credit notes; localized pricing in 30+ currencies; and global payment methods (cards, Apple Pay, Google Pay, PayPal, iDEAL, Bancontact, Pix, UPI). Paddle Retain automates failed-payment recovery (dunning), cancellation win-back offers, and monthly-to-annual term optimization. Integration is via a versioned REST API with idempotency keys, 50+ webhooks, official SDKs (Node.js, PHP, Python, Go), Paddle.js for embedded or b

SOURCES

RESEARCHED BUILD PROMPT

Give this to your coding agent.

Build 'Remit', a self-hosted merchant-of-record billing engine inspired by Paddle's workflow (do not copy Paddle's brand, UI, or proprietary assets). Core workflow: a seller registers products and plans with base prices; the system localizes prices into multiple currencies, computes and collects tax at checkout, and appears as the legal seller on receipts. Implement: (1) a checkout API plus an embeddable JS widget supporting cards and wallets via mock PSP adapters; (2) a subscription lifecycle engine with trials, proration, upgrades, pauses, one-time charges, invoices, and credit notes; (3) a tax calculation and remittance ledger with pluggable per-country tax rules; (4) a webhook event stream (subscription.created, payment.succeeded, etc.) with signature verification and replay; (5) a hosted customer portal for payment-method updates, invoice downloads, and cancellation with win-back offers; (6) a dunning engine that retries failed payments on configurable schedules and nudges monthly-to-annual upgrades; (7) an admin dashboard with revenue metrics and refund/chargeback handling. Technical approach: Node.js or Python backend, Postgres, versioned REST API with idempotency keys, a webhook simulator for local development, and Docker Compose. Out of scope: real payment processing, real tax filing, PCI compliance, multi-acquirer routing, and fraud ML. Include a README with setup steps and important limitations (mock payments, no legal MoR liability).

Visit the official product page