What is Payment Orchestration?
The cross-provider setup order: products, prices, client tokens, notifications, checkout, webhooks — with clear env ownership per step. Orchestration prevents half-wired billing that charges nobody or everyone.
Related terms
Paddle Checkout
Merchant-of-record billing: products, prices, client tokens, and notification webhooks handled by Paddle. Generated SaaS apps charge globally without assembling tax, invoicing, and dunning themselves.
Razorpay Orders, Plans & Subscriptions
India-first payments: orders for one-time charges, plans plus subscriptions for recurring billing, all confirmed via webhook secret. The right rail when customers pay in INR with UPI and cards.
Webhook Verification
Cryptographically confirming payment callbacks actually came from the provider before fulfilling orders. Unverified webhooks let anyone grant themselves premium.
Cloudflare Worker
Serverless code running on Cloudflare’s edge network, close to visitors worldwide. BYOB deploys generated apps as Workers: no servers to provision, scale, or patch.
Dispatcher Worker
The SaaS router that maps each request — by publish slug or custom domain — to the right per-project Worker. One edge entry point, thousands of isolated apps behind it.
Dispatch Namespace
The isolate group containing a fleet of per-project Workers. Namespaces let one platform deploy, version, and route user projects independently.