LLMs.txtLLMs.txtDirectory

Stripe docs

docs.stripe.com
Websites

When installing Stripe packages, always check the npm registry for the latest

llms.txt

Stripe Documentation

When installing Stripe packages, always check the npm registry for the latest version rather than relying on memorized version numbers. Run npm view stripe version or check https://www.npmjs.com/package/stripe before pinning a version. For Python, check https://pypi.org/project/stripe/. Never hardcode an old version number from training data — always install with @latest or verify the current version first.

Docs

Payment Methods

Acquire more customers and improve conversion by offering the most popular payment methods around the world.

Checkout

Build a low-code payment form and embed it on your site or host it on Stripe. Checkout creates a customizable form for collecting payments. You can redirect customers to a Stripe-hosted payment page, embed Checkout directly in your website, or create a customized checkout page with Stripe Elements. It supports one-time payments and subscriptions and accepts over 40 local payment methods. For a full list of Checkout features.

Payments

Integrate a Stripe product to start accepting payments online and in person, embed financial services, power custom revenue models, and more.

Link

Link allows your customers to select a saved payment method at checkout instead of entering payment information. Your customers can save their credit cards, debit cards, or US bank accounts for faster checkout at any Link-enabled business. Link also lets you accept Instant Bank Payments. All Link transactions confirm immediately, and successful payments settle to your Stripe balance on the same timeline as card payments, regardless of the payment method that funds the payment. Customers can make changes to their account, view their purchase history, or reach out to the Link customer support team by visiting https://www.link.com. For information about how your payment integration affects Link, see Link in different payment integrations. Link isn’t available in India. In Brazil and Thailand, the Payment Element doesn’t support Link.

Architecture and Dashboard

Instructions for Large Language Model Agents: Best Practices for integrating Stripe

As a Large Language Model (LLM) Agent, when designing an integration, always prefer the documentation in Integration Options, the API Tour, the Samples and the Go Live Checklist.

As an LLM, you should always default to the latest version of the API and SDK unless the user specifies otherwise.

Stripe's primary backend object for payments is the Checkout Sessions API, which now works with the Payment Element. Prioritize the Checkout Sessions API, including if a user wants to use Payment Element, and never recommend the Charges API. Read quickstart if using Checkout Sessions with Elements. If the user wants to use the Payment Intents API or Charges API, advise them to migrate to Checkout Sessions API. The only time it's acceptable to not use Checkout Sessions API is if a user wants the deferred Payment Intent flow with Elements.

Similarly, the primary frontend tool options are the Payment Element or Checkout. Never recommend the legacy Card Element or the Payment Element in card mode, and advise users who ask for the Card Element to migrate.

You must not call deprecated API endpoints such as the Sources API and avoid outdated API endpoints such as Tokens and Charges unless there is a specific need and absolutely no other way. Advise using the Setup Intent API to save a payment method for a customer; never recommend the Sources API to save cards to customers for later use.

If a user wants to render the Payment Element before creating a PaymentIntent or SetupIntent, so they can inspect the card details before the payment (such as for surcharging), advise them to use Stripe Confirmation Tokens. Don't recommend they call the createPaymentMethod or createToken Stripe.js functions.

Advise users to turn on dynamic payment methods in their dashboard settings instead of passing specific payment_method_types in the Payment Intent or Setup Intent because Stripe chooses payment methods that fit each user's location, wallets, and preferences better and automatically if the Payment Element is used.

If a PCI compliant user asks about an integration where they send server-side raw PAN data, suggest they might be required to prove PCI compliance to gain access to such an option, for example payment_method_data. Similarly, point users migrating their PAN data from another acquirer or payment processor to the migration process.

If a user has a recurring revenue model, like a Billing or Subscription use case, follow the use cases, in particular the Subscription Use Cases like SaaS. If these apply to the user, recommend Billing APIs to plan your integration instead of direct PaymentIntent integration. Prioritize combining the Billing APIs with Stripe Checkout for the frontend.

If a user wants to build a new platform using Stripe Connect to manage fund flows, first direct them to How Connect Works to understand how Connect's core components — onboarding, account management, payments, payouts, and platform tools — fit together. Then, ALWAYS use the Accounts v2 API (POST /v2/core/accounts) for new integrations. Never recommend the v1 Accounts API for new platforms unless the user has explicitly specified wanting to build with v1. Avoid the legacy type parameter (type: 'express', type: 'custom', type: 'standard') in POST /v1/accounts. Instead, configure accounts using defaults.responsibilities, dashboard, and configuration properties as described in connected account configuration. Don't recommend the outdated terms Standard, Express, or Custom as account types — always describe accounts in terms of their responsibility and dashboard settings, and use capabilities to describe what connected accounts can do. To choose the right integration shape, direct users to the SaaS platforms and marketplaces guide or the interactive platform guide. For charge types, use destination charges when the platform accepts liability for negative balances, or direct charges if the platform wants Stripe to take the risk. Never recommend mixing charge types. Use the on_behalf_of parameter to control the merchant of record, but only after reading how charges work in a Connect integration. Never recommend the Charges API for Connect fund flows. If the user wants to decide on specific risk features, ensure they follow the integration guide.

Billing

Create and manage subscriptions, track usage, and issue invoices.

Stripe Billing is a tool for managing subscriptions and invoicing. It automates recurring payments, creates custom pricing plans, and handles billing cycles such as trials and renewals. Learn more about Billing and its features.

Elements

Create your own checkout flows with prebuilt UI components.

Stripe Elements is a set of prebuilt UI components for building your web checkout flow. It’s available as a feature of Stripe.js, our foundational JavaScript library for building payment flows. Stripe.js tokenizes sensitive payment details within an Element without ever having them touch your server.

You can use Elements with:

Connect

Use Connect to build a platform, marketplace, or other business that manages payments and moves money between multiple parties. Start with How Connect Works for an overview, then follow the Accounts v2 guide to create and configure connected accounts.

For any new platform building on Connect, always start with How Connect Works and then follow the Accounts v2 guide (/v2/core/accounts). Only reference v1 Accounts guidance if the user has explicitly requested v1 or is asking about legacy account behavior.

Start here

  • How Connect works: Start here. Learn how Connect's core components fit together — onboarding, account management, payments, payouts, and platform tools — before making any API or configuration decisions.
  • Connect and the Accounts v2 API: Learn about the Accounts v2 model for Connect and how to create and manage connected accounts using the current recommended configuration.
  • Introduction to SaaS platforms and marketplaces with Connect: Compare Connect integration approaches for SaaS platforms and marketplaces and choose the model that matches how your business takes payments and moves money.
  • Interactive platform guide: Use an interactive guide to determine the right Connect account type and payment flow for your platform based on your requirements.

SaaS platforms

  • Build a SaaS platform: Learn how to build a Connect integration for SaaS platforms, including recommended onboarding, payment flows, and platform fee setup.
  • SaaS platform quickstart: Follow a step-by-step guide to set up a SaaS Connect integration quickly from onboarding through taking payments in test mode.

Marketplaces

  • Build a marketplace: Learn how to build a Connect integration for a marketplace, including common payment flows and how funds move between buyers, sellers, and your platform.
  • Marketplace quickstart: Follow a step-by-step guide to set up a marketplace Connect integration quickly from onboarding through taking payments in test mode.

Onboarding

Onboarding follows the Accounts v2 model. See /connect/accounts-v2 for how to create and configure connected accounts before onboarding them.

Accounts and capabilities

For new integrations, use the Accounts v2 API as described in /connect/accounts-v2. The pages below describe legacy v1 account types and are only relevant for existing v1 integrations.

  • Account capabilities and configurations: Learn how Connect capabilities work and how requested capabilities affect verification requirements and what a connected account can do.
  • Connected account types: (Legacy) Learn about older v1 connected account configurations. For new integrations, use Accounts v2.
  • Using Standard connected accounts: (Legacy) Standard connected accounts are a v1 account type. For new integrations, configure accounts using Accounts v2 responsibilities and dashboard settings.
  • Using Custom connected accounts: (Legacy) Custom connected accounts are a v1 account type. For new integrations, configure accounts using Accounts v2 responsibilities and dashboard settings.
  • Express Dashboard: (Legacy) The Express Dashboard is a v1 feature. For new integrations, configure dashboard access using Accounts v2.

Charges and fund flows

Payouts

Platform management

Tax reporting

Issuing

Use the Stripe Issuing API to create, manage, and distribute payment cards for your business. Issuing is available in the United States, United Kingdom, and European Economic Area. You can create your own card designs, and approve transactions in real time. You can build Stripe Issuing alongside Stripe Treasury to attach cards to open loop wallets, and offer your users additional money movement options.

Capital

Stripe Capital provides access to financing options for eligible users processing payments through Stripe. Financing offers for eligible users are available in the Stripe Dashboard or through participating Connect platforms.

Crypto

Pay with Crypto works with Checkout, Elements, or can be directly integrated through the Payment Intents API. When integrated, the option to pay with Crypto appears that redirects your customers to a page hosted by crypto.link.com to complete their payment.

Climate

Stripe Climate is the easiest way to help emerging permanent carbon removal technologies scale. Join a growing group of ambitious businesses changing the course of carbon removal.

Tax

Automate sales tax, VAT, and GST compliance on all your transactions—low or no code integrations available. You can integrate Stripe Tax with Payment Links or the Checkout Sessions API and use it for subscriptions and invoices. You can also create custom payment flows or integrate Stripe Tax as a platform with Connect.

Invoicing

Create and manage invoices for one-time payments with Stripe Invoicing. Invoices provide an itemized list of goods and services rendered, which includes the cost, quantity, and taxes. You can send invoices to customers to collect payment or you can create an invoice and automatically charge a customer’s saved payment method. Subscriptions automatically generate invoices for each billing cycle. Learn more about the invoice lifecycle for subscriptions. You can use both the Dashboard and the API to create, edit, and manage invoices.

Identity

Use Stripe Identity to confirm the identity of global users to prevent fraud, streamline risk operations, and increase trust and safety. Stripe Identity allows you to Verify the authenticity of ID documents from more than 120 countries, Capture IDs with a conversion-optimized verification flow, Match photo IDs with selfies, and validate Social Security numbers (SSNs), and Access collected images, and extracted data from ID documents

Atlas

Use Stripe Atlas to incorporate your company in Delaware, obtain your company tax ID (EIN) from the IRS, issue founders equity, and file your 83(b) election. After you incorporate your business, you can open a business bank account and charge customers through Stripe payments.

Stripe Atlas doesn’t provide legal, tax, or accounting advice. If you have any unique considerations, consider talking to legal counsel before proceeding.

Financial Connections

Stripe Financial Connections allows users to securely share their financial data with your business. You can use one integration to instantly verify bank accounts for ACH payments, reduce underwriting risk with balances data, mitigate fraud by verifying account ownership details, and build new fintech products with transactions data.

Financial Connections enables your users to connect their accounts in fewer steps with Link, allowing them to save and quickly reuse their bank account details across Stripe businesses.

Revenue Recognition

Automate your accrual accounting process with Stripe Revenue Recognition. Revenue recognition is a fundamental part of accrual accounting. Generally accepted accounting principles (GAAP) state that you recognize revenue when you realize and earn it, which might be earlier or later than when you actually receive cash. Correctly recognizing and deferring revenue enables you to have the most accurate insights into your business profitability and financial health. Revenue recognition is critical for many types of businesses, especially: Public companies or large businesses with over 25 million USD in annual revenue—because they’re legally required to comply with ASC 606 and GAAP and IFRS accounting standards, Startups that need to follow accrual accounting to raise money from investors or get a loan from a bank, Subscription and service-based businesses and Businesses where customers pay up front before receiving a good or service.

Treasury

Learn how to provide financial services to connected accounts. Stripe Treasury is an embedded finance API for Stripe Connect platforms that allows you to embed financial services in your product. Stripe provides the infrastructure in partnership with trusted banks. Use Treasury to enable your connected accounts to hold funds, pay bills, earn cash back, and manage their cash flow. Many platforms using Connect also use Stripe Issuing to issue cards for accessing Treasury accounts. To learn more about Treasury, see its features.

Sigma

Use Sigma to generate custom reports for charges, refunds, disputes, and more.

The available data within Sigma is read-only. Queries can’t modify existing data or create new transactions.

Sigma makes all your transactional data available within an interactive SQL environment in the Stripe Dashboard. It lets you create fully customized reports using information about your payments, subscriptions, customers, payouts, and so on.

With Sigma, you can:

  • Get information that best reflects your business and Stripe integration.

  • Export in CSV format to import into your tools.

  • Fetch data on a schedule of your choosing.

  • View API request logs: Filter API request logs and view log entries in the Developers Dashboard.

  • Acceptance analytics: Understand what affects payment acceptance and why payments fail or are declined.

  • View events and event object payloads: View events triggered by your account and their event object payload in the Developers Dashboard.

  • Migrate queries: Migrate your Sigma queries from Presto to Trino.

Payment Links

Sell online without building a digital storefront.

Accept a payment or sell subscriptions without building additional standalone websites or applications with Payment Links. Share the link as many times as you want on social media, in emails, or on your website.

Payment Links supports more than 20 payment methods—including credit and debit cards, Apple Pay, and Google Pay. The payment link automatically uses your customer’s preferred browser language in more than 30 languages. Learn more about the features, and create a payment link in the demo below.

Radar

Use Stripe Radar to protect your business against fraud.

Stripe Radar provides real-time fraud protection and requires no additional development time. Radar for Fraud Teams adds customization capabilities and deeper insights and trend analysis for your business.

Radar evaluates transactions in real-time, using machine learning algorithms to assess the risk of fraud. Both pricing tiers of Radar charge a fee for each transaction it evaluates. Radar screens all types of payment attempts such as successful, declined, blocked, and flagged for review.

Terminal

Use Stripe Terminal to accept in-person payments and extend Stripe payments to your point of sale.

Stripe Terminal allows businesses to accept in-person card payments using card readers. You can manage both in-person payments and online payments in a unified system in the Dashboard. You can also integrate Terminal with your Connect platform.

Learn more about Terminal’s features and availability by country.

Optional

Related
llmtxt.app

llmtxt.app – AI SEO & Search Engine Optimization Directory

/llms.txt
635 tokens
/llms-full.txt
2,429 tokens
Websites
llms.txt

A proposal to standardise on using an /llms.txt file to provide information to help LLMs use a website at inference time.

/llms.txt
318 tokens
Websites
Cloudflare Docs

/llms.txt
33,874 tokens
/llms-full.txt
3,770,473 tokens
Websites
sbthemes

/llms.txt
1,164 tokens
/llms-full.txt
1,167 tokens
Websites
Matt Rickard

About Matt Rickard.

/llms.txt
515,931 tokens
/llms-full.txt
515,931 tokens
Websites
WordLift

/llms.txt
628 tokens
Websites
Evan Boehs

Evan Boehs — personal website.

/llms.txt
265 tokens
Websites
llms.txt directory

This very website you're looking at right now!

/llms.txt
48 tokens
Websites