# Stripe Stripe development plugin for Krypton: best practices, API/SDK upgrade guidance, and the Stripe MCP server. Stripe is a comprehensive payment processing platform that enables businesses to accept online payments, manage subscriptions, handle refunds, and access detailed financial reporting. It provides secure payment infrastructure for e-commerce, SaaS, marketplaces, and mobile applications. - Category: Finance - Connection: Sign in. Sign in with your Stripe account, or paste an API key instead. - Plans: Free: Not included; MCP only ($9/mo): 2,000 calls a month; Pro: 20,000 calls a month; Max: 20,000 calls a month - Consent: Payments consent (https://krypton.bot/terms/#publishing). Before Stripe connects, you confirm the payments consent: your bots can create charges, refunds, invoices and payouts in the account you connect, and you are responsible for every transaction, chargeback and fee. - Vendor site: https://stripe.com ## Tools - Create coupon (`STRIPE__CREATE_COUPON`): Creates a new coupon object for use in Stripe. - Create customer (`STRIPE__CREATE_CUSTOMER`): Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications. - Create invoice (`STRIPE__CREATE_INVOICE`): Creates a new draft stripe invoice for a customer; use to revise an existing invoice, bill for a specific subscription (which must belong to the customer), or apply detailed customizations. - Create invoice item (`STRIPE__CREATE_INVOICE_ITEM`): Creates an item to be added to a draft invoice (up to 250 items per invoice). If no invoice is specified, the item will be on the next invoice created for the customer specified. - Create payment link (`STRIPE__CREATE_PAYMENT_LINK`): Creates a payment link that you can share with customers to collect payment. - Create payment method (`STRIPE__CREATE_PAYMENT_METHOD`): Creates a new payment method object that can be attached to customers for future payments. - Create price (`STRIPE__CREATE_PRICE`): Creates a new stripe price for a product, defining its charges (one-time or recurring) and billing scheme; requires either an existing product id or product data. - Create product (`STRIPE__CREATE_PRODUCT`): Creates a new product in stripe, encoding the request as application/x-www-form-urlencoded by flattening nested structures. - Create refund (`STRIPE__CREATE_REFUND`): Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id. - Create subscription (`STRIPE__CREATE_SUBSCRIPTION`): Creates a new subscription for a customer with specified pricing and billing details. - List coupons (`STRIPE__LIST_COUPONS`): Retrieves a list of discount coupons from a stripe account, supporting pagination via limit, starting after, and ending before. - List customers (`STRIPE__LIST_CUSTOMERS`): Retrieves a list of stripe customers, with options to filter by email, creation date, or test clock, and support for pagination. - List disputes (`STRIPE__LIST_DISPUTES`): Returns a list of your disputes. - List invoices (`STRIPE__LIST_INVOICES`): Retrieves a list of stripe invoices, filterable by various criteria and paginatable using invoice id cursors obtained from previous responses. - List payment intents (`STRIPE__LIST_PAYMENT_INTENTS`): Retrieves a list of stripe paymentintents, optionally filtered and paginated using paymentintent ids as cursors. - List prices (`STRIPE__LIST_PRICES`): Returns a list of your prices. - List products (`STRIPE__LIST_PRODUCTS`): Retrieves a list of stripe products, with optional filtering and pagination; starting after/ending before cursors must be valid product ids from a previous response. - List subscriptions (`STRIPE__LIST_SUBSCRIPTIONS`): Retrieves a list of stripe subscriptions, optionally filtered by various criteria such as customer, price, status, collection method, and date ranges, with support for pagination. - Update customer default payment method (`STRIPE__UPDATE_CUSTOMER_DEFAULT_PAYMENT_METHOD`): Updates a customer's default payment method for invoices and subscriptions. - Update dispute (`STRIPE__UPDATE_DISPUTE`): Updates the specific dispute by setting the values of the parameters passed. - Update subscription (`STRIPE__UPDATE_SUBSCRIPTION`): Updates an existing, non-canceled stripe subscription by its id, ensuring all referenced entity ids (e.g., prices, coupons) are valid and automatic tax liability is correctly specified if enabled. - Attach payment method (`STRIPE__ATTACH_PAYMENT_METHOD`): Attaches a payment method to a customer for future payments and subscriptions. - Cancel subscription (`STRIPE__CANCEL_SUBSCRIPTION`): Cancels a customer's active stripe subscription at the end of the current billing period, with options to invoice immediately for metered usage and prorate charges for unused time. - Finalize invoice (`STRIPE__FINALIZE_INVOICE`): Stripe automatically finalizes drafts before sending and attempting payment on invoices. However, if you'd like to finalize a draft invoice manually, you can do so using this method. - Get account info (`STRIPE__GET_ACCOUNT_INFO`): Retrieves the details of the Stripe account. - Retrieve balance (`STRIPE__RETRIEVE_BALANCE`): Retrieves the complete current balance details for the connected stripe account. ## Skills included - connect-recommend: Use this skill when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform, multi-vendor store, gig platform, or subscription platform, needs to pay out sellers, vendors, or providers, mentions split payments, revenue sharing, multi-party payments, or similar payment distribution concepts, provides a company URL or business description for a recommendation, builds SaaS that routes money between parties (for example, POS, booking, invoicing — not operational SaaS without payment routing), asks about onboarding or KYC for merchants, sellers, and vendors, mentions connected account Dashboard or responsibility configurations, or asks about payment flows, white-label payments, or embedded payments. - connect-required-verification-information: Use this skill when the user asks what information a Stripe Connect connected account must provide for verification, onboarding, KYC, or account requirements; when they need to compare requirements between connected-account setups; or when they ask which verification fields, documents, or business details are required for a particular platform country, account country, business type, dashboard, service agreement, or capability. - metronome: Guides Metronome usage-based billing integration decisions — event ingestion (single and batch, idempotency, billable metrics), contract design (rate cards, overrides, dimensional pricing, products), invoicing lifecycle (grace periods, finalization, Stripe sync), credit and commit management (prepaid, postpaid, thresholds, auto-recharge), and Stripe integration (arrears invoicing, tax providers, line item limits). Use when building, modifying, or reviewing any Metronome integration — including ingesting usage events, creating customers, contracts, or rate cards, designing billable metric group keys, managing credits and commits, configuring invoicing, syncing invoices with Stripe Billing, billing AI applications for token usage, setting up self-serve (PLG) pricing, reviewing customer health, commit burn, portfolios, or renewals, or migrating from Stripe Billing Meters to Metronome. - stripe-apps: Build, modify, or review Stripe Apps and extensions using the relevant documentation and reference guides. Use for custom Stripe Dashboard UI, stripe-app.yaml, @stripe/ui-extension-sdk, @stripe/extensibility-sdk, script extensions, extension interfaces, custom workflow actions, and apps that authenticate to Stripe or react to events. Also use when deciding whether a Stripe extension can support the user's billing or workflow requirements. - stripe-best-practices: Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatic_tax, product tax codes), Treasury financial accounts, integration options (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, API key permissions, webhooks, OAuth). Use when planning, building, modifying, testing, or reviewing any Stripe integration, including choosing a development environment, accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, collecting sales tax, VAT, or GST, creating connected accounts, or implementing secure key handling. - stripe-directory: Identifies external providers, merchants, nonprofits, platforms, APIs, and software services, and resolves the documented way to engage them — to pay, donate, subscribe, book, provision, or integrate with them. MUST be used BEFORE web search, model memory, or any other directory/vendor-lookup skill for ANY request that requires selecting, finding, or engaging an external provider or organization — whether a specific one is named ("pay my Twilio bill"), implied ("donate to the Red Cross"), or only a category is stated ("set up a mailing client", "I need a database", "find me a CRM"). Directory supplies verified recipients and their documented payment or engagement path. Results are ranked by agent-readiness (how reliably an agent can complete the interaction), relevance and popularity. Don't treat this as a search-only tool. Examples: "setup a database", "find hosting", "pay X", "use Twilio", "donate $50 to the Red Cross", "book a table at Y", "subscribe to a CRM". - stripe-docs: Use when the user or agent needs to read, search, or look up Stripe documentation or API reference. Prefer this over curl or WebFetch for any docs.stripe.com content. Use to fetch gated documentation. - stripe-pay: Helps users send funds to another Stripe business, transfer money to a Stripe Profile handle or network ID, or ask whether an agent can pay a Stripe business. Use Stripe Directory to find or verify a recipient when the user doesn't provide an exact Stripe Profile handle or network ID. - stripe-projects: Use when the user wants to provision infrastructure or third-party services using Stripe Projects. - upgrade-stripe: Guide for upgrading Stripe API versions, webhook endpoints, server-side SDKs, Stripe.js, and mobile SDKs - company-researcher: Research a company from its URL or description to infer Stripe Connect integration shape - explain-error: Explain Stripe error codes and provide solutions with code examples - test-cards: Display Stripe test card numbers for various testing scenarios ## Questions ### How do I connect Stripe to Krypton? Open Integrations in Krypton, find Stripe and choose Sign in. Every bot in the workspace can then use it, and you choose which bots get which apps. ### Which plan includes Stripe? MCP only with 2,000 calls a month, Pro and Max with 20,000. Calls are shared by every catalog app in the workspace. Past the monthly number they keep working from AI credits at $0.90 per 1,000 calls; the count resets on the 1st (UTC) and a retried call counts once. ### Can I use Stripe from Claude or Cursor? Yes. Connect it in your workspace, then add https://mcp.krypton.bot as a streamable HTTP MCP server with your kmcp_ workspace key. Calls count toward the same monthly number. Back to the [MCP catalog](https://krypton.bot/mcp-catalog/).