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

View on GitHub

Install

$ npx -y skills add butterbase-ai/butterbase-skills --skill payments --agent claude-code

Installs 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.