stripe-integration
Stripe payment integration with Node.js SDK. Covers Checkout Sessions, Payment Intents, Subscriptions, Customer Portal, webhooks, and Stripe Elements. Use when implementing checkout flows, payment processing, subscription billing, webhook handlers, or payment forms with Stripe Elements. Use for stripe, payments, checkout, subscriptions, billing, webhooks, payment intents, stripe elements.
What this skill does
# Stripe Integration
## Overview
Stripe provides a complete payments platform with server-side SDKs (Node.js) and client-side libraries (Stripe.js, React Stripe.js). The Node.js SDK handles server operations like creating Payment Intents, managing Subscriptions, and verifying webhooks. The React Stripe.js library provides pre-built UI components (PaymentElement, Elements provider) for secure client-side payment collection.
**When to use:** One-time payments, recurring subscriptions, usage-based billing, marketplace payouts, hosted checkout pages, custom payment forms, webhook-driven fulfillment.
**When NOT to use:** Cryptocurrency payments (not supported), regions where Stripe is unavailable, simple static product sales without payment processing (use a hosted storefront).
## Quick Reference
| Pattern | API | Key Points |
| ------------------- | ----------------------------------------------------- | --------------------------------------------------------------------- |
| Hosted checkout | `stripe.checkout.sessions.create()` | Stripe-hosted page, supports `payment`, `subscription`, `setup` modes |
| Payment Intent | `stripe.paymentIntents.create()` | Server-side, returns `client_secret` for client confirmation |
| Confirm payment | `stripe.confirmPayment({ elements, clientSecret })` | Client-side, requires Elements instance |
| Create subscription | `stripe.subscriptions.create()` | Use `payment_behavior: 'default_incomplete'` for SCA |
| Update subscription | `stripe.subscriptions.update()` | Set `proration_behavior` explicitly |
| Cancel subscription | `stripe.subscriptions.cancel()` | Use `prorate: true` to credit unused time |
| Customer Portal | `stripe.billingPortal.sessions.create()` | Self-service billing management, returns short-lived URL |
| Webhook verify | `stripe.webhooks.constructEvent()` | Requires raw body, signature header, and endpoint secret |
| Elements provider | `<Elements stripe={stripePromise} options={options}>` | Wraps payment components, pass `clientSecret` or `mode` |
| PaymentElement | `<PaymentElement />` | Renders all supported payment methods automatically |
| Retrieve + expand | `stripe.checkout.sessions.retrieve(id, { expand })` | Expand nested objects to reduce API calls |
| Search | `stripe.paymentIntents.search({ query })` | Stripe Query Language for filtering |
## Common Mistakes
| Mistake | Correct Pattern |
| ------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| Parsing webhook body as JSON before verification | Use `express.raw({ type: 'application/json' })` to pass raw body to `constructEvent` |
| Hardcoding payment method types | Use `automatic_payment_methods` or let Checkout choose based on currency and region |
| Creating PaymentIntent client-side | Create on server, pass only `client_secret` to client |
| Not awaiting `elements.submit()` before confirm | Call `elements.submit()` first to trigger validation, then `confirmPayment` |
| Missing `return_url` in `confirmPayment` | Always provide `return_url` for redirect-based payment methods |
| Using test keys in production | Store keys in environment variables, validate `STRIPE_SECRET_KEY` prefix (`sk_live_` vs `sk_test_`) |
| Not handling `requires_action` status | Check PaymentIntent status after confirmation, handle 3D Secure or other authentication |
| Creating Customer Portal session without settings | Save portal settings in Dashboard first, otherwise API returns an error |
| Not expanding related objects | Use `expand` parameter to include nested objects like `latest_invoice.payment_intent` |
| Ignoring webhook idempotency | Use `event.id` to deduplicate, webhook events can be delivered more than once |
## Delegation
- **Payment flow architecture**: Use `Explore` agent to discover integration patterns
- **Webhook debugging**: Use `Task` agent for end-to-end event tracing
- **Code review**: Delegate to `code-reviewer` agent for security review of payment handlers
## References
- [Checkout Sessions, Payment Intents, and one-time payments](references/checkout-and-payments.md)
- [Subscription lifecycle, pricing models, trials, and Customer Portal](references/subscriptions.md)
- [Webhook endpoints, signature verification, and event handling](references/webhooks.md)
- [React Stripe.js, Elements provider, PaymentElement, and custom forms](references/stripe-elements.md)
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.