payments Skill
Stripe payments integration guidance — native Vercel Marketplace setup, checkout sessions, webhook handling, subscription billing, and the Stripe SDK. Use when implementing payments, subscriptions, or processing transactions. Published by openai in plugins.
Decision snapshot
Is this a fit?
Developers using plugins, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
API key required authentication, Credentials required
Copy skill directory
19 days ago
Access note: API key required.
What is payments Skill?
Stripe payments integration guidance — native Vercel Marketplace setup, checkout sessions, webhook handling, subscription billing, and the Stripe SDK. Use when implementing payments, subscriptions, or processing transactions. Published by openai in plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using plugins
Declared skill metadata
- Source file: plugins/vercel/skills/payments/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
- API key required
Requirements and access
Security and permissions
Review permissions before connecting any MCP server to an agent. Pay special attention to whether it can read local files, write data, call external services, or perform destructive actions.
When to use payments Skill
- Use it for developers using plugins.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/plugins
- Skill file: plugins/vercel/skills/payments/SKILL.md
What it does
Stripe payments integration guidance — native Vercel Marketplace setup, checkout sessions, webhook handling, subscription billing, and the Stripe SDK. Use when implementing payments, subscriptions, or processing transactions.
Skill instructions
Stripe Payments Integration You are an expert in Stripe payments for Vercel-deployed applications — covering the native Vercel Marketplace integration, Checkout Sessions, webhook handling, subscription billing, and the Stripe Node.js SDK. Vercel Marketplace Setup (Recommended) Stripe is a native Vercel Marketplace integration with sandbox provisioning and unified billing. Install via Marketplace bash Install Stripe from Vercel Marketplace (auto-provisions sandbox + env vars) vercel integration add stripe Auto-provisioned environment variables: - STRIPESECRETKEY — server-side API key - STRIPEPUBLISHABLEKEY — client-side publishable key - STRIPEWEBHOOKSECRET — webhook endpoint signing secret SDK Setup bash Server-side SDK npm install stripe Client-side SDK (for Stripe Elements / Checkout) npm install @stripe/stripe-js @stripe/react-stripe-js Initialize the Stripe Client ts // lib/stripe.ts import Stripe from "stripe"; export const stripe = new Stripe(process.env.STRIPESECRETKEY!, { apiVe
Verified compatibility and discovery
Frequently asked questions
What is payments?
payments is a open-source AI agent skill with Copy skill directory. Stripe payments integration guidance — native Vercel Marketplace setup, checkout sessions, webhook handling, subscription billing, and the Stripe SDK.
Who is payments best for?
payments is best for reusing agent instructions, scripts, and references.
How do I install payments?
Install or run payments using Copy skill directory. Check payments for the latest setup command.
Is payments actively maintained?
payments may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
