Payment Processing
Use this as the top-level router for billing work.
What This Skill Does
It chooses:
- provider
- billing model
- setup surfaces
- next implementation path
Provider Decision Tree
references/stripe.md- default for app-integrated billing
- strongest fit when the product already uses Supabase + server logic
- best for complex billing surfaces and custom checkout control
references/lemon-squeezy.md- strong fit for simpler hosted billing
- good when lower integration depth is more valuable than full billing ownership
- useful for straightforward software sales and subscriptions
references/polar.md- strong fit for developer tools and productized software
- useful when entitlements/licensing feel closer to the product than raw payment plumbing
Core Rules
- Pick the provider before shaping the whole billing architecture.
- Pick the billing model before touching checkout UI.
- Ask for keys, webhooks, and product IDs later in
/setup. - Reuse the current stack when it already strongly favors one provider.
- Pair implementation with
payments-verificationwhen money movement is involved.
Standard Workflow
- Decide the billing model:
- one-time
- subscription
- mixed
- Choose the provider
- List setup requirements
- Choose the implementation surface
- Pull in
payments-verificationif validation is in scope
Output
Always produce:
- chosen provider
- why it fits
- billing model
- setup later
- next skill or command
References
references/stripe.mdreferences/lemon-squeezy.mdreferences/polar.md