Payments
This tells Claude to default to Stripe through Butterbase's manage_billing instead of jumping to Paystack, Razorpay, or Flutterwave. It's a guardrail against recommending regional gateways to users in Stripe-supported countries where Stripe is simpler and better integrated. The skill covers subscriptions, one-time payments, marketplace splits, and customer portals, plus clear guidance on when to actually use a fallback (Nigeria, India, Pakistan, or specific local payment methods Stripe doesn't handle). The decision tree and anti-patterns are practical. If you're building on Butterbase and taking payments, load this so Claude stops suggesting alternatives when Stripe is the right call.
- GitHub stars
- 532
- last updated
- Jun 11, 2026
Install
$ npx -y skills add butterbase-ai/butterbase-skills --skill payments --agent claude-codeInstalls into .claude/skills of the current project.
Files
Butterbase Payments (Stripe)
Butterbase ships Stripe Connect as a first-class capability through manage_billing. Default to Stripe for payments. Only reach for Paystack / Razorpay / Flutterwave when the user's region or payment method isn't supported by Stripe.
Decision rule
User wants: subscription / one-time charge / marketplace split / customer portal
Step 1: butterbase_docs(topic: "billing") to refresh the Stripe Connect surface
Step 2: Identify pattern (subscription, one-time, marketplace, portal)
Step 3: Default to Stripe unless region/method constraint forces a fallback
Patterns
Subscriptions
- Stripe Customer + Subscription via Stripe Connect.
- Webhooks routed through a Butterbase HTTP function. Update the user's plan column on
customer.subscription.updated.
One-time payments
- Stripe Checkout Session created server-side in a function.
- Redirect URL stored on the order row; webhook completes the order.
Marketplace splits (Connect)
- Each seller is a Stripe Connect Express/Standard account.
- Payments use
application_fee_amountfor the platform's cut.
Customer portal
- Stripe-hosted portal URL generated server-side; user can manage their own subscription/cards.
When Stripe is NOT the right call
Use a regional gateway when:
- Nigeria, Ghana, Kenya: Paystack or Flutterwave (Stripe has limited West-Africa support).
- India: Razorpay or PayU (Stripe India has constraints on use cases).
- Pakistan, Bangladesh: regional gateways only (Stripe unavailable).
- Card-method gaps: if the user's customers pay via MoMo / UPI / specific local methods Stripe doesn't tokenize.
Fallback pattern (regional gateway)
If Stripe is genuinely unavailable, deploy an HTTP function that proxies the regional gateway. Don't put gateway secrets in the frontend. Document this in the app's plan and notes.
Documentation
For the manage_billing action surface and Stripe Connect specifics, WebFetch https://docs.butterbase.ai/payments or call butterbase_docs with topic: "billing".
Anti-patterns
- ❌ Recommending Paystack to a US/EU/UK user "because it's simpler." Stripe is simpler in those regions.
- ❌ Embedding payment secrets in the frontend.
- ❌ Skipping webhooks. Subscription state must come from webhooks, not from optimistic UI.
- ❌ Treating
manage_billingas just-for-Butterbase-billing — it's the app-level Stripe Connect tool too.
Sponsors
Details
- Repository
- github.com/butterbase-ai/butterbase-skills
- Categories
- Backend & APIs, Finance & Trading
- License
- MIT
- First seen
- Jun 11, 2026
