skills.rest
remorses
remorsesCOMMUNITY
Explore all skills by this author →
Website𝕏@__morseGitHub

stripe

Automate Stripe Checkout and Billing Portal flows for org-scoped customers.

40|2|Updated Sep 24, 2025
Search Tags:#billing#error-handling#stripe#checkout#subscription#portal
One-click install
npx skills add https://github.com/remorses/opencode-config --skill stripe-remorses
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stripe
Source: https://github.com/remorses/opencode-config/tree/main/skills/stripe
Command: npx skills add https://github.com/remorses/opencode-config --skill stripe-remorses

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires stripe, errore, zod, drizzle-orm, spiceflow.

What problem does it solve?

Stripe-based billing patterns used in unframer-private. The skill enforces a single Stripe customer per Org, uses stable price lookup keys with multi-currency support, and coordinates end-to-end Checkout and Billing Portal flows with robust error handling.

Core Features & Use Cases

  • One Stripe customer per Org, stored in Org.stripeCustomerId and reused across checkout/portal calls.
  • Lookup prices by stable lookup_key and apply multi-currency pricing via currency_options to align EUR with USD.
  • End-to-end billing flows: Checkout for new subscriptions, Billing Portal for management, and a rigorous errore-based error handling pattern.
  • Use case: An Org initiates a subscription, reuses a single customer, and seamlessly transitions between checkout and portal while preventing duplicates.

Quick Start

Create a new Checkout session for an Org using the stripe skill.

Frequently Asked Questions about stripe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle Stripe checkout for org-scoped customers without creating duplicates?▼

Stripe checkout for org-scoped customers is handled by enforcing a single customer per organization, storing the ID in the database, and reusing it across checkout and portal calls to prevent duplicates and maintain data integrity.

What is the best way to manage multi-currency Stripe subscriptions with lookup keys?▼

Multi-currency Stripe subscriptions are managed by looking up prices using stable lookup_keys and applying currency_options to align regional pricing, such as matching EUR with USD, for accurate billing.

How does error handling work with Stripe billing flows in a spiceflow API?▼

Error handling in Stripe billing flows uses a rigorous errore-based pattern across server and spiceflow routes to catch and tag errors, ensuring data integrity during checkout and portal transitions.

Can I use Stripe and drizzle-orm to reuse a single customer ID for subscription management?▼

Yes, you can use Stripe with drizzle-orm to map a single customer ID to your organization entity, allowing seamless transitions between the Stripe Billing Portal and Checkout without creating duplicate records.

When should I use the Stripe Billing Portal instead of creating a new Checkout session?▼

The Stripe Billing Portal should be used when an existing organization customer wants to manage their current subscription, while Checkout is for initiating new subscriptions, ensuring correct multi-currency billing flows.

Related Skills

Explore More Software Engineering Skills→
goodnessibehgoodnessibeh
1

stripe-integration

Integrate Stripe checkout sessions, subscriptions, and billing portal webhooks into web applications.

Community
Advanced
ollieb89ollieb89

stripe-payments

Integrate Stripe payments and subscriptions into Next.js App Router applications.

Community
Advanced
RevealUIStudioRevealUIStudio
4

db-migrate

Coordinate Drizzle ORM migrations across NeonDB and Supabase schemas.

Community
Advanced
refly-airefly-ai
199

stripe

Process Stripe payments, invoices, and subscription billing with customer details.

Official
Intermediate