| name | sales-paddle |
| description | Paddle (paddle.com) platform help — Merchant of Record (MoR) billing for SaaS, apps, and digital products: localized checkout, subscriptions, global sales-tax/VAT compliance + remittance (300+ markets), invoicing, fraud, Retain dunning, and ProfitWell Metrics. Paddle Billing REST API (api.paddle.com, Bearer key, sandbox) with HMAC-SHA256 signed webhooks and a Docs MCP. Use when building a Paddle Billing API or webhook integration, migrating off the legacy Paddle Classic API to Billing, verifying webhook HMAC signatures or handling out-of-order/duplicate events, subscriptions or transactions not provisioning access, amounts wrong because money is cents-as-a-string, syncing MRR/subscriptions to a warehouse, or understanding Paddle's percentage-plus-per-transaction MoR fee and payout timing. Do NOT use for choosing a Merchant of Record across providers (use /sales-merchant-of-record), checkout-conversion optimization across tools (use /sales-checkout), or Lemon Squeezy-specific help (use /sales-lemonsqueezy). |
| argument-hint | [describe what you need help with in Paddle] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","payments","checkout","platform"] |
| github | https://github.com/PaddleHQ |
Paddle Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
-
What are you trying to do?
- A) Build an API integration — create products/prices, manage subscriptions/transactions, pull reports
- B) Set up + verify webhooks (HMAC-SHA256) to provision access / run dunning
- C) Migrate from the legacy Paddle Classic API to Paddle Billing
- D) Understand the MoR model — fees (5% + $0.50), tax handled for you, payout timing
- E) Fix a problem — wrong amounts (cents-as-string), out-of-order/duplicate webhooks, signature failures
- F) Decide if Paddle vs another provider — that's a selection question (route in Step 2)
-
Billing or Classic? Build everything new on Paddle Billing (api.paddle.com). Only touch Classic to migrate an existing integration off it.
-
Sandbox first? Use sandbox-api.paddle.com with separate keys before production.
Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2.
Step 2 — Route or answer directly
| If the question is about... | Route to... |
|---|
| Choosing a Merchant of Record / payments provider across tools (Paddle vs Lemon Squeezy vs Polar vs Stripe) | /sales-merchant-of-record {question} |
| Checkout-conversion optimization across tools (order bumps, upsells, cart recovery) | /sales-checkout {question} |
| Lemon Squeezy-specific setup/API | /sales-lemonsqueezy {question} |
| Subscription churn / dunning strategy across tools | /sales-membership {question} |
| Connecting Paddle to a CRM/other tools generically (iPaaS) | /sales-integration {question} |
When routing, give the exact command, e.g. "This is a provider-selection question — run: /sales-merchant-of-record Paddle vs Lemon Squeezy for my B2B SaaS".
Step 3 — Paddle platform reference
Read references/platform-guide.md for the full reference — the module map (what's API vs MoR-handled vs UI-only), the MoR fee/payout model (5% + $0.50, global tax included, scheduled payouts), the data model with JSON shapes, and quick-start recipes (provision access on a subscription webhook; create a product+price; sync MRR to a warehouse).
