# https://docs.stripe.com

> Stripe's comprehensive documentation provides guidance on integrating their payment platform, covering API usage, subscription management, Connect features for platforms and marketplaces, Issuing cards, financial accounts, tax compliance, and security best practices. It offers detailed information on various payment methods, dispute resolution, fraud prevention, and developer tools like the CLI and SDKs, enabling businesses to manage online and in-person transactions effectively.

## Pages

- [Acceptable verification documents by country | Stripe Documentation](https://docs.stripe.com/acceptable-verification-documents): This page lists the acceptable identity, address, and legal entity verification documents required by Stripe for each supported country. It outlines common requirements for document formats, image quality, and validity to ensure successful verification.
- [Account checklist | Stripe Documentation](https://docs.stripe.com/get-started/account/checklist): This checklist outlines essential steps to complete before taking your Stripe account live, focusing on security and customer clarity. Key actions include enabling two-factor authentication and confirming your statement descriptor.
- [Activate your account | Stripe Documentation](https://docs.stripe.com/get-started/account/activate): This page explains how to activate your Stripe account to move from testing to live mode for accepting real payments. Activation requires providing business and personal information for Stripe's Know Your Customer (KYC) compliance, and the account's country cannot be changed after activation.
- [Import payment method data | Stripe Documentation](https://docs.stripe.com/get-started/data-migrations/payment-method-imports): This guide details how to import payment method data, such as cards, ACH, and SEPA, from other processors into Stripe. It explains the differences between default payment method (pm_) objects and legacy card (card_) objects and when to use each.
- [Export file formats | Stripe Documentation](https://docs.stripe.com/get-started/data-migrations/export-file-formats): This page describes the file formats Stripe uses for exporting payment data, primarily CSV and JSON. It outlines the fields included in card exports and provides an example of a card data export.
- [Map payment data | Stripe Documentation](https://docs.stripe.com/get-started/data-migrations/map-payment-data): This guide explains how to map imported payment data to existing Stripe Customers to prevent duplicate entries. It details the process of creating a mapping file with old customer IDs and their corresponding Stripe customer IDs.
- [Copy PAN data across Stripe accounts | Stripe Documentation](https://docs.stripe.com/get-started/data-migrations/pan-copy-self-serve): This page describes Stripe's self-serve data copy service, which allows secure copying of customer and payment data between Stripe accounts. It clarifies that data is copied, not merged, and exists on both the source and destination accounts after completion.
- [Request a payment data export | Stripe Documentation](https://docs.stripe.com/get-started/data-migrations/pan-export): This page explains how to request a secure export of sensitive payment data from Stripe, especially when migrating to another processor. Stripe transfers card data only to PCI DSS Level 1-compliant processors and requires specific information about the new processor.
- [Request a payment data import | Stripe Documentation](https://docs.stripe.com/get-started/data-migrations/pan-import): This guide details the process for securely importing existing customer and payment data into Stripe, ensuring no downtime for customers. It emphasizes the need for a Data Migration Request for sensitive payment information to maintain PCI compliance.
- [Upload supplementary  data | Stripe Documentation](https://docs.stripe.com/get-started/data-migrations/supplementary-data): This page explains how to upload supplementary data to Stripe during payment data migration, focusing on data encryption for PCI compliance. It provides step-by-step instructions for encrypting data using Stripe's PGP key.
- [Stripe accounts | Stripe Documentation](https://docs.stripe.com/get-started/account): This page provides an overview of Stripe accounts, covering creation, activation for live mode, and management. It highlights features like creating multiple accounts, managing teams, setting up custom domains, and migrating sensitive data.
- [Linked external accounts | Stripe Documentation](https://docs.stripe.com/get-started/account/linked-external-accounts): This page explains how to link external financial accounts to your Stripe account to enhance services and streamline risk reviews. Linking accounts allows Stripe to access financial data for payouts, product eligibility, and reserve balance evaluations.
- [Multiple separate accounts | Stripe Documentation](https://docs.stripe.com/get-started/account/multiple-accounts): This page details how to create and manage multiple separate Stripe accounts for independent projects, websites, or businesses. It explains that each account is subject to standard policies and pricing and can be managed centrally through organizations.
- [Build an organization | Stripe Documentation](https://docs.stripe.com/get-started/account/orgs/build): This page guides users on how to create a Stripe organization to manage multiple accounts from a single location in the Stripe Dashboard. It outlines the prerequisites for creating an organization, including Super Administrator roles and SSO consolidation.
- [Stripe Organizations | Stripe Documentation](https://docs.stripe.com/get-started/account/orgs): This page introduces Stripe Organizations, a feature that unifies and centralizes the management of multiple Stripe accounts under consolidated ownership. It enables centralized reporting, operations, and team management for businesses with multiple business lines or subsidiaries.
- [Supported Organization setups | Stripe Documentation](https://docs.stripe.com/get-started/account/orgs/setup): This page outlines the supported account setups for Stripe Organizations, including multiple standalone accounts, platforms, and connected accounts. It differentiates Organizations from Connect platforms, explaining that Organizations act as a container for managing separate businesses.
- [Share customers and payment methods across accounts in an organization | Stripe Documentation](https://docs.stripe.com/get-started/account/orgs/sharing/customers-payment-methods): This page explains how to share customers and payment methods (specifically card types) across multiple Stripe accounts within an organization. This feature, currently in public preview, helps avoid redundant data entry and maintain consistency for customers.
- [Manage access to your organization | Stripe Documentation](https://docs.stripe.com/get-started/account/orgs/team): This page details how to manage access for team members within a Stripe organization through the Team and security settings. It explains organization-level versus account-level roles and how to assign permissions and manage two-factor authentication.
- [Statement descriptors | Stripe Documentation](https://docs.stripe.com/get-started/account/statement-descriptors): This page explains statement descriptors, which appear on customer bank statements to clarify charges and reduce disputes. It covers requirements for static and dynamic statement descriptors, including character limits and allowed characters.
- [User roles | Stripe Documentation](https://docs.stripe.com/get-started/account/teams/roles): This page describes user roles within Stripe, allowing controlled access for team members to an account. It details the 'Administrator' role, outlining the extensive permissions granted, including managing payments, customers, and API keys, while noting limitations.
- [Start a team | Stripe Documentation](https://docs.stripe.com/get-started/account/teams): This page explains how to invite and manage team members within your Stripe account. You can assign specific roles and permissions to users, and they will receive email invitations to join. Team members can also be mentioned in payment notes for easy notification.
- [ACH Direct Debit with Charges | Stripe Documentation](https://docs.stripe.com/ach-deprecated): This guide details a legacy method for accepting ACH payments using Stripe's older Charges API. It's recommended to migrate to the Payment Intents API for new integrations due to built-in verification. This method requires customer authorization and bank account verification, with payments taking several business days to process.
- [Add funds to your Stripe balance | Stripe Documentation](https://docs.stripe.com/get-started/account/add-funds): You can add funds to your Stripe balance to cover potential increases in refunds or disputes, or to maintain a stable account balance. Funds can be added via wire transfer or local bank credit transfer, with availability and processing times varying by region. Adding funds directly to the payments balance is recommended for most businesses.
- [Build agentic AI SaaS Billing workflows | Stripe Documentation](https://docs.stripe.com/agents-billing-workflows): This guide demonstrates how to automate recurring SaaS billing workflows using Stripe's API and AI-driven agents. It covers provisioning customers and subscriptions, responding to lifecycle events via webhooks, and invoking billing actions through an AI agent toolkit.
- [Accept a payment | Stripe Documentation](https://docs.stripe.com/agentic-commerce/apps/accept-payment): This page explains how to accept payments within an AI agent's context using a prebuilt Stripe-hosted Checkout page. It involves defining Model Context Protocol (MCP) tools to display products, collect payment details, and monitor webhooks for successful payments.
- [Monetize your Model Context Protocol (MCP) app | Stripe Documentation](https://docs.stripe.com/agentic-commerce/apps): This guide explains how to monetize Model Context Protocol (MCP) apps by adding a checkout flow. Options include redirecting customers to a prebuilt checkout page or using Instant Checkout for an integrated experience within platforms like ChatGPT, with varying integration efforts and features.
- [Key concepts | Stripe Documentation](https://docs.stripe.com/agentic-commerce/concepts): This page introduces the core concepts of agentic commerce, where AI agents manage transactions between sellers and buyers within an AI interface. Agents maintain customer relationships and can make personalized purchase recommendations, utilizing shared payment tokens for secure payment method management.
- [Shared payment tokens | Stripe Documentation](https://docs.stripe.com/agentic-commerce/concepts/shared-payment-tokens): This document explains how to use shared payment tokens (SPTs) to receive a customer's payment method from an AI agent. Sellers can create SPTs with defined usage and expiration limits, and scope them to specific sellers or transactions for enhanced security.
- [Enable in-context selling on AI agents | Stripe Documentation](https://docs.stripe.com/agentic-commerce/enable-in-context-selling-on-ai-agents): This guide details how e-commerce businesses can enable in-context selling on AI agents by setting up their Stripe account and configuring taxes and legal policies. It covers joining the waitlist for agentic commerce and setting up a Stripe Profile for optimal configuration.
- [Agentic commerce | Stripe Documentation](https://docs.stripe.com/agentic-commerce): Agentic commerce enables secure transactions between buyers, AI agents, and businesses through AI interfaces. It uses AI agents to discover, evaluate, and complete transactions, with options for businesses to integrate using the Agentic Commerce Protocol or for AI platforms to facilitate direct transactions via shared payment tokens.
- [Product catalog | Stripe Documentation](https://docs.stripe.com/agentic-commerce/product-catalog): This page describes how to share structured product and inventory data with Stripe for AI agent discovery using a product feed specification. You can submit a full catalog and then send incremental updates to maintain accurate stock levels and availability for AI agents.
- [Integrate the Agentic Commerce Protocol | Stripe Documentation](https://docs.stripe.com/agentic-commerce/protocol): This guide explains how to integrate the Agentic Commerce Protocol (ACP), an open-source specification enabling commerce between applications like ChatGPT and sellers. ACP allows AI agents to manage checkout interfaces and collect payment credentials, while sellers handle payment processing.
- [Build the Agentic Commerce Protocol checkout endpoints | Stripe Documentation](https://docs.stripe.com/agentic-commerce/protocol/specification): This page outlines the Agentic Commerce Protocol (ACP) specification for building checkout endpoints, enabling AI agents to manage commerce transactions. It defines the methods and data structures for creating, updating, and completing checkout flows, with examples provided for REST integrations.
- [Add Stripe to your agentic workflows | Stripe Documentation](https://docs.stripe.com/agents): This guide explains how to integrate Stripe into agentic workflows using the Stripe agent toolkit, which supports various LLM providers and SDKs. The toolkit allows agents to create and manage Stripe objects, such as Payment Links, to enhance their financial service capabilities.
- [See all products | Stripe Documentation](https://docs.stripe.com/products): This page provides an overview of Stripe's product offerings, categorizing them into Payments, Connect, Radar, Climate, Identity, Financial Connections, Crypto, Revenue, Money Management, and Atlas. It also lists prebuilt components like Payment Links, Checkout, and Elements.
- [API v2 overview | Stripe Documentation](https://docs.stripe.com/api-v2-overview): This document provides an overview of Stripe's API v2 namespace, highlighting key differences from v1, such as JSON encoding for requests and responses, and improved idempotency handling. It also covers testing strategies using Sandboxes and test mode.
- [Automated testing | Stripe Documentation](https://docs.stripe.com/automated-testing): This page explains how to use automated testing in Stripe integrations by simulating API requests and interface outputs with mock data. It details how to generate simulated error objects for client-side testing, particularly for handling transaction declines.
- [Stripe-Context header | Stripe Documentation](https://docs.stripe.com/context): This page describes the Stripe-Context header, which allows API requests to be performed in the context of related accounts beyond the one associated with the API key. This header expands the scope to include connected accounts, v2 accounts, and accounts within an organization.
- [Advanced error handling | Stripe Documentation](https://docs.stripe.com/error-low-level): This page covers advanced error handling at the HTTP level for Stripe API interactions, focusing on HTTP responses that represent errors and idempotency with retries. It categorizes errors into content, network, and server errors, each requiring different handling approaches.
- [Error codes | Stripe Documentation](https://docs.stripe.com/error-codes): This page details Stripe's error codes, which help in resolving API errors and can be triggered for testing. It includes a table of error codes with descriptions and links to further documentation, as well as specific decline codes for card transactions.
- [Error handling | Stripe Documentation](https://docs.stripe.com/error-handling): Stripe's error handling documentation outlines how to catch and respond to various errors, including declined payments, invalid data, and network issues. It details the structure of error data provided by Stripe, such as error codes, messages, and documentation URLs, to help developers implement effective error handling strategies.
- [File upload guide | Stripe Documentation](https://docs.stripe.com/file-upload): This guide explains how to use Stripe's File Upload API to securely send documents like dispute evidence and identification to Stripe. It covers the process of uploading files via multipart/form-data requests and lists various valid purpose values, each with specific file format and size requirements.
- [Include-dependent response values in API v2 | Stripe Documentation](https://docs.stripe.com/api-includable-response-values): This documentation explains how to manage API v2 responses that may contain null values for certain properties by default. To retrieve the actual values, developers must specify them using the 'include' array request parameter, with the specific values depending on the request endpoint.
- [Stripe's APIs | Stripe Documentation](https://docs.stripe.com/apis): Stripe provides a unified set of REST APIs for payments, billing, and financial workflows, with support for API v1 and v2. The documentation covers essential API features like authentication, request shaping, response handling, localization, testing, and error management.
- [Domains and IP addresses | Stripe Documentation](https://docs.stripe.com/ips): This page lists the fully qualified domain names and IP addresses that integrations must be able to reach to function correctly with Stripe. It emphasizes the importance of allowlisting these domains and verifying communication with Stripe's API endpoints for secure and reliable integration.
- [Best practices for managing secret API keys | Stripe Documentation](https://docs.stripe.com/keys-best-practices): This guide provides best practices for managing secret API keys, stressing that they must be kept secure in the server environment and never exposed in source code. It recommends using secrets management tools or environment variables and periodically auditing code for exposed keys.
- [API keys | Stripe Documentation](https://docs.stripe.com/keys): Stripe uses API keys to authenticate requests, with sandbox keys for testing and live keys for production. The documentation explains the different types of keys (secret and publishable) and how to manage them through the Developers Dashboard, including webhook signing secrets.
- [Metadata use cases | Stripe Documentation](https://docs.stripe.com/metadata/use-cases): Metadata allows you to store additional, non-sensitive key-value pair data on Stripe objects for your own reference. Common use cases include storing IDs from external systems to link Stripe objects with your own records, such as associating a cart ID with a Checkout Session.
- [Metadata | Stripe Documentation](https://docs.stripe.com/metadata): Metadata in Stripe enables you to attach custom key-value pairs to certain Stripe objects for your own use, with limits on key and value lengths. Stripe generally does not use this metadata unless for Radar, and it is not visible to customers unless explicitly shared.
- [Manage default payment methods in the Dashboard | Stripe Documentation](https://docs.stripe.com/upgrades/manage-payment-methods): Stripe has updated its API to manage default payment methods in the Dashboard for PaymentIntents and SetupIntents. If the payment_method_types parameter is not specified, Stripe now defaults to using eligible payment methods configured in the Dashboard, rather than just cards.
- [How pagination works | Stripe Documentation](https://docs.stripe.com/pagination): Stripe's API endpoints that return multiple objects, like listing customers, use pagination to manage performance. Results are returned in pages, with a default of up to 10 results per call, and the 'has_more' property indicates if additional pages are available.
- [Rate limits | Stripe Documentation](https://docs.stripe.com/rate-limits): Stripe implements API rate limits to ensure stability, returning 429 error responses for excessive requests. The documentation details these limits, including global and per-operation restrictions for live and sandbox modes, and advises on handling rate limiting and requesting increases.
- [API upgrades | Stripe Documentation](https://docs.stripe.com/upgrades): This page details changes and upgrades to the Stripe API, distinguishing between backward-compatible monthly releases and major releases that may require code updates. API versioning controls behavior like request parameters and response properties, and is set by the first API request made.
- [Apple Pay liability shift, disputes, and refunds | Stripe Documentation](https://docs.stripe.com/apple-pay/disputes-refunds): This guide covers managing disputed or refunded Apple Pay payments, including contesting disputes and understanding liability shifts. The dispute process for Apple Pay is similar to card payments, and liability shift is supported globally, with specific limitations for Visa on older iOS versions.
- [Apple Pay merchant tokens | Stripe Documentation](https://docs.stripe.com/apple-pay/merchant-tokens): Apple Pay merchant tokens (MPANs) tie a payment card, business, and customer together, enabling better management of card access and continuity across devices. They are recommended over device tokens for recurring and deferred payments, ensuring payment information remains active.
- [Manage recurring payments on Apple Pay | Stripe Documentation](https://docs.stripe.com/apple-pay/apple-pay-recurring): This guide explains how recurring payments work with Apple Pay, differentiating between customer-initiated transactions (CIT) and merchant-initiated transactions (MIT). It highlights that Apple Pay processes card PANs to generate Device Primary Account Numbers (DPANs) to maintain card privacy.
- [Apple Pay Best Practices | Stripe Documentation](https://docs.stripe.com/apple-pay/best-practices): Implementing Apple Pay best practices can significantly improve conversion rates and reduce payment risks. Key recommendations include offering express checkout options on product pages and leveraging Apple Pay's ability to allow customers to authorize payments with biometrics or a side button.
- [Cartes Bancaires with Apple Pay | Stripe Documentation](https://docs.stripe.com/apple-pay/cartes-bancaires): This guide details how to integrate Cartes Bancaires with Apple Pay for EUR payments, emphasizing that Cartes Bancaires should only be enabled if the transaction is in Euros and the account supports these charges. It outlines the necessary setup steps within Stripe and the Apple Pay SDK.
- [Apple Pay | Stripe Documentation](https://docs.stripe.com/apple-pay): Apple Pay allows customers to make secure payments on Apple devices and the web, supporting Strong Customer Authentication (SCA) requirements in Europe. It is compatible with most Stripe products and features, with no additional fees beyond standard card transaction pricing.
- [Accept payments after incorporating | Stripe Documentation](https://docs.stripe.com/atlas/accept-payments): Atlas startups can accept US card payments immediately after incorporation, even before receiving an EIN, using Stripe's no-code options like Payment Links and Invoicing. Stripe automatically retrieves and adds the EIN to the account once it's available from the IRS.
- [Business taxes | Stripe Documentation](https://docs.stripe.com/atlas/business-taxes): Companies incorporated in Delaware have yearly tax obligations, including federal and state income tax, and Delaware franchise or LLC tax. Stripe Atlas can assist with incorporating a US company and provides information on tax requirements, but advises consulting tax professionals for specific advice.
- [Company types | Stripe Documentation](https://docs.stripe.com/atlas/company-types): Stripe Atlas allows incorporation of a Delaware C corporation or LLC, each suited for different business needs. C corporations are favored by institutional investors and offer equity options, while LLCs have different tax treatments.
- [Founder equity terms | Stripe Documentation](https://docs.stripe.com/atlas/equity-terms): Stripe Atlas offers default founder equity vesting terms, which can be customized regarding the vesting period, start date, and inclusion of a cliff. Vesting ensures gradual ownership of equity over time, with common terms including a four-year period and a one-year cliff.
- [Fundraise with SAFEs | Stripe Documentation](https://docs.stripe.com/atlas/fundraise-with-safes): After incorporating a C corp with Atlas, founders can begin fundraising by sending Simple Agreements for Future Equity (SAFEs) to investors. Atlas assists in obtaining board approval for fundraising and uses a standard Y Combinator-drafted SAFE template.
- [Incorporation documents | Stripe Documentation](https://docs.stripe.com/atlas/incorporation-documents): Stripe Atlas provides key incorporation documents such as the Certificate of Incorporation, Action by Written Consent of Sole Incorporator, and Bylaws, created in collaboration with Cooley LLP. These documents are essential for establishing the company and can be accessed via the Atlas Dashboard.
- [Incorporate a company with Indian resident founders | Stripe Documentation](https://docs.stripe.com/atlas/indian-founder-guide): Indian resident founders can use Stripe Atlas to create a US company while complying with India's Overseas Direct Investment (ODI) regulations. This is particularly relevant for founders seeking venture capital with a US C corp, with specific considerations for residents and those not seeking external capital.
- [File Section 83(b) elections as a non-US founder | Stripe Documentation](https://docs.stripe.com/atlas/83b-elections-non-us-founders): Non-US founders who file US tax returns are advised to make a Section 83(b) election to potentially save on future US taxes. This election allows founder stock to be taxed at the time of purchase rather than vesting, and is unnecessary for those not subject to US taxes.
- [Stripe Atlas | Stripe Documentation](https://docs.stripe.com/atlas): Stripe Atlas helps founders worldwide start a US company in Delaware, providing incorporation, tax ID (EIN), founder equity setup, and 83(b) tax filings. It offers legal documents, partner perks, and Stripe credits, streamlining the process of opening bank accounts and accepting payments.
- [Business bank accounts | Stripe Documentation](https://docs.stripe.com/atlas/payments-business-bank): Immediately after incorporation or receiving an EIN, Stripe Atlas founders can apply for business bank accounts with partner banks like Mercury and Brex. Eligibility is determined by the partners, and some offer pre-EIN signup options.
- [Section 83(b) elections | Stripe Documentation](https://docs.stripe.com/atlas/83b-election): A Section 83(b) election allows founders to have their stock taxed at the time of purchase instead of vesting, potentially saving significant future taxes. This election is filed by Atlas for C-corp founders, as LLC equity does not vest.
- [Incorporating a US company from Singapore | Stripe Documentation](https://docs.stripe.com/atlas/singapore-founder-guide): Founders in Southeast Asia can use Stripe Atlas to incorporate a US company, either as a parent or subsidiary to their Singapore company. This is beneficial when investors require a US parent entity or for operating in the US market while managing tax implications.
- [How to incorporate your company | Stripe Documentation](https://docs.stripe.com/atlas/signup): Stripe Atlas incorporates your company in Delaware, obtains an EIN, issues founder equity, and files 83(b) elections for a fee covering incorporation and the first year of registered agent services. It provides legal information and tools but does not offer legal, tax, or accounting advice.
- [Querying authentication conversion | Stripe Documentation](https://docs.stripe.com/payment-authentication/writing-queries): Stripe Sigma allows querying authentication conversion data, including attempts, PaymentIntents, and SetupIntents, using the `authentication_report_attempts` table. Example queries demonstrate how to retrieve authenticated payments using the challenge flow and information on SCA exemptions.
- [Customer support for Issuing and Financial Accounts for platforms | Stripe Documentation](https://docs.stripe.com/issuing/customer-support): This guide provides example issues and resolutions for customer support related to Stripe Issuing and Financial Accounts for Platforms. It emphasizes equipping support teams with necessary information and tools, potentially augmenting existing systems with Stripe APIs or training staff.
- [Money management | Stripe Documentation](https://docs.stripe.com/money-management): Stripe's Money Management tools include Financial Accounts for holding funds and currency conversion, Global Payouts, Cards for managing expenses, and Capital for business financing. These can be used directly or embedded within platforms for customers.
- [B2B payments integration guide | Stripe Documentation](https://docs.stripe.com/issuing/integration-guides/b2b-payments): Stripe Issuing enables the creation of virtual cards for business, employee, or contractor purchases in the US. This guide covers funding the Issuing Balance, creating cardholders and cards, and using these cards to spend funds from the Issuing Balance.
- [Embedded Finance integration guide | Stripe Documentation](https://docs.stripe.com/issuing/integration-guides/embedded-finance): This guide details building an embedded financial services offering using Stripe Issuing and Financial Accounts for platforms in the US. It covers creating verified customer accounts, financial accounts for balances, and virtual cards for spending funds.
- [Fleet integration guide | Stripe Documentation](https://docs.stripe.com/issuing/integration-guides/fleet): A Fleet integration guide using Stripe Issuing allows for the creation of cards and transaction processing for customers' businesses. It covers creating verified connected accounts for business customers and issuing cards for them to spend funds.
- [Integration guides | Stripe Documentation](https://docs.stripe.com/issuing/integration-guides): This page lists integration guides for launching Stripe Issuing or Financial Accounts for platforms. It highlights guides for Embedded Finance, B2B Payments, and Fleet, emphasizing the need for supported business types and integrated systems for going live.
- [Onboarding overview | Stripe Documentation](https://docs.stripe.com/issuing/onboarding-overview): This guide helps take Stripe Issuing (US, EU, UK) or Financial Accounts for platforms (US only) integrations live. It requires use case approval, obtaining live mode access, and testing the program with real funds before launch.
- [Issuing and Financial Accounts for platforms sample app | Stripe Documentation](https://docs.stripe.com/issuing/sample-app): This page introduces a sample app for Stripe Issuing and Financial Accounts for platforms, demonstrating how to onboard customers, issue cards, and process outbound payments. It allows users to test these functionalities without writing code by copying the sample app and observing API logs.
- [About the Billing APIs | Stripe Documentation](https://docs.stripe.com/billing/billing-apis): This page explains the core API objects that power Stripe Billing, including Products, Prices, Customers, Invoices, and PaymentIntents. It details how these objects interact to manage subscriptions, recurring charges, and payment processing.
- [Billing collection methods | Stripe Documentation](https://docs.stripe.com/billing/collection-method): This page outlines the collection methods for Stripe invoices and subscriptions, detailing 'charge_automatically' for automatic payment processing and 'send_invoice' for manual payments. It explains how to configure these methods via the API or Dashboard to manage payment collection.
- [Add a cancellation page to the customer portal | Stripe Documentation](https://docs.stripe.com/customer-management/cancellation-page): This page describes how to add a cancellation page to the Stripe customer portal, allowing customers to cancel subscriptions directly. It also covers options to collect cancellation reasons and deflect cancellations, with reasons visible in the Dashboard, Sigma, and via webhooks.
- [Deep links in the customer portal | Stripe Documentation](https://docs.stripe.com/customer-management/portal-deep-links): This page explains deep links and flows within the Stripe customer portal, enabling streamlined customer actions like updating payment methods or canceling subscriptions. Flows are customizable deep links that hide navigational components for a focused user experience and allow custom redirect behavior.
- [Integrate the customer portal with the API | Stripe Documentation](https://docs.stripe.com/customer-management/integrate-customer-portal): This page details how to integrate the Stripe customer portal with your application using the API. It involves configuring portal features in the Dashboard, implementing redirects, and listening to webhooks for updates, allowing customers to manage their subscriptions and billing.
- [Activate the no-code customer portal | Stripe Documentation](https://docs.stripe.com/customer-management/activate-no-code-customer-portal): This page guides users on activating the no-code Stripe customer portal, which allows customers to self-manage payment details and subscriptions. Activation involves obtaining a Stripe account, activating a link on the website or sharing it directly, and configuring portal options in the Dashboard.
- [Provide a customer portal to your customers | Stripe Documentation](https://docs.stripe.com/customer-management): This page explains how to provide a customer portal for customers to manage their accounts and subscriptions, reducing customer service interactions. It covers activating and configuring the portal through the Dashboard or API, and enabling features like deep links and cancellation management.
- [Configure the customer portal | Stripe Documentation](https://docs.stripe.com/customer-management/configure-portal): This page details how to configure settings for the Stripe customer portal within the Dashboard after initial setup. It covers options for subscription management, such as allowing customers to switch plans, update quantities, and manage downgrades, with specific best practices for each.
- [Customer invoice balance | Stripe Documentation](https://docs.stripe.com/billing/customer/balance): This page explains the customer invoice balance in Stripe Billing, which represents credits or debits applied to a customer's account. This balance can be adjusted using credit and debit transactions and is automatically applied to future invoices, providing an audit trail.
- [Customers | Stripe Documentation](https://docs.stripe.com/billing/customer): This page describes the Stripe Customer resource, a core entity for storing profile, billing, and tax information needed to bill customers for subscriptions and invoices. It explains how to create and manage customers via the API or Dashboard, setting essential details for billing and Smart Retries.
- [Entitlements | Stripe Documentation](https://docs.stripe.com/billing/entitlements): This page explains how Stripe Entitlements map internal service features to Stripe products, enabling automated provisioning and de-provisioning of feature access based on subscription status. This simplifies billing integration and allows for dynamic pricing experimentation without code changes.
- [Billing | Stripe Documentation](https://docs.stripe.com/billing): This page provides an overview of Stripe Billing, a service for managing subscriptions, usage tracking, and invoicing. It automates recurring payments, supports custom pricing, and handles billing periods, offering no-code options like pricing tables and customer portal integration.
- [Subscription invoices | Stripe Documentation](https://docs.stripe.com/billing/invoices/subscription): This page details how Stripe handles subscription invoices throughout their lifecycle, from creation to payment. It explains that Stripe generates an invoice for each billing period, and how the invoice status transitions based on payment success or failures, impacting the subscription's active state.
- [How subscriptions work | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/overview): This page explains how Stripe Subscriptions manage recurring payments and customer lifecycles, supporting various pricing models, discounts, and trials. It outlines the subscription flow, involving customer creation, subscription setup, and the use of Invoices and PaymentIntents for processing payments.
- [Use Accounts as customers | Stripe Documentation](https://docs.stripe.com/connect/use-accounts-as-customers): This page describes how to use Stripe Accounts as customers with the Accounts v2 API, enabling them to be used in API requests that typically require a customer object. This allows for using Stripe-hosted integrations like Checkout with accounts configured as customers.
- [Manage products and prices | Stripe Documentation](https://docs.stripe.com/products-prices/manage-prices): This page explains how to manage products and prices in Stripe, either through the Dashboard for simpler use cases or via the API for advanced scenarios like variable pricing or large catalogs. It covers creating, updating, and archiving products and prices for subscription-based businesses.
- [Overview | Stripe Documentation](https://docs.stripe.com/products-prices/overview): This page provides an overview of Stripe products and prices, which are fundamental for modeling a business on Stripe. It explains different pricing models like flat rate, per-seat, and usage-based, and how to manage products and prices through the Dashboard or API.
- [Integrate a SaaS business on Stripe | Stripe Documentation](https://docs.stripe.com/saas): This page guides users on integrating a Software as a Service (SaaS) business on Stripe, focusing on subscriptions and recurring payments. It highlights key components like product modeling, entitlements, pricing tables, trials, discounts, subscription management via the customer portal, and tax collection.
- [Program your business logic directly on Stripe with scripts | Stripe Documentation](https://docs.stripe.com/billing/scripts): This page introduces Stripe scripts, allowing users to program custom logic directly on Stripe using a subset of TypeScript. Scripts can define logic for specific Stripe objects, tailor the Stripe account, and extend functionality, such as creating custom discount logic for coupons.
- [Script language definition | Stripe Documentation](https://docs.stripe.com/billing/scripts/script-language): Stripe's scripting language is a restricted subset of TypeScript designed to prevent issues like long runtimes and excessive memory consumption. It supports basic types, variables, functions, objects, and arrays, with optional but recommended type annotations.
- [Benchmarking | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/analytics/benchmarking): Benchmarking on Stripe Billing allows businesses to compare their metric performance against similar companies using Stripe. To access benchmarks, a business needs at least five active subscriptions and one paid subscription within the past year. Stripe uses a k-nearest neighbors algorithm to identify peer groups based on various business factors.
- [Analytics | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/analytics): Stripe Billing analytics and downloadable reports offer a comprehensive view of business performance, allowing users to monitor, audit, and compare data. Users can access preview features and download reports in CSV format, including MRR per subscriber and subscription metrics summaries.
- [Backdate subscriptions | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/backdating): Backdating subscriptions allows billing customers for past elapsed time, useful for migrations or record keeping. The behavior of backdating depends on the subscription's billing mode, with 'classic' creating a single prorated line item and 'flexible' generating line items for each natural billing period.
- [Set the subscription billing renewal date | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/billing-cycle): A subscription's billing period is determined by its recurring interval and a billing cycle anchor. The billing cycle anchor sets the reference point for future billing dates, aligning with the day of the week, day of the month, or month of the year based on the interval.
- [Build a subscriptions integration | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/build-subscriptions): This guide details building a subscription integration for React Native apps using the Mobile Payment Element to create a custom payment form. It covers modeling the business, creating a registration process, collecting payment information, and managing subscription status.
- [Build a subscriptions integration | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/build-subscriptions?payment-ui=checkout&ui=embedded-form): This guide details building a subscription integration for React Native apps using the Mobile Payment Element to create a custom payment form. It covers modeling the business, creating a registration process, collecting payment information, and managing subscription status.
- [Build a subscriptions integration | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/build-subscriptions?payment-ui=elements&api-integration=checkout): This guide details building a subscription integration for React Native apps using the Mobile Payment Element to create a custom payment form. It covers modeling the business, creating a registration process, collecting payment information, and managing subscription status.
- [Build a subscriptions integration | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/build-subscriptions?payment-ui=elements&api-integration=paymentintents): This guide details building a subscription integration for React Native apps using the Mobile Payment Element to create a custom payment form. It covers modeling the business, creating a registration process, collecting payment information, and managing subscription status.
- [Build a subscriptions integration | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/build-subscriptions?payment-ui=mobile&platform=ios): This guide details building a subscription integration for React Native apps using the Mobile Payment Element to create a custom payment form. It covers modeling the business, creating a registration process, collecting payment information, and managing subscription status.
- [Build a subscriptions integration | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/build-subscriptions?payment-ui=mobile&platform=android): This guide details building a subscription integration for React Native apps using the Mobile Payment Element to create a custom payment form. It covers modeling the business, creating a registration process, collecting payment information, and managing subscription status.
- [Build a subscriptions integration | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/build-subscriptions?payment-ui=mobile&platform=react-native): This guide details building a subscription integration for React Native apps using the Mobile Payment Element to create a custom payment form. It covers modeling the business, creating a registration process, collecting payment information, and managing subscription status.
- [Cancel subscriptions | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/cancel): This guide explains how to cancel existing Stripe subscriptions using the Subscription API or the Dashboard. Subscriptions can be canceled immediately or at a custom date, and they automatically cancel after multiple unsuccessful billing attempts.
- [Modify subscriptions | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/change): This guide covers modifying existing Stripe subscriptions without requiring cancellation and recreation. Changes can impact billing and generate prorations, such as price or quantity adjustments, while non-billing updates apply immediately without prorations.
- [Compare classic and flexible billing mode | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/billing-mode/compare): This document compares Stripe's classic and flexible billing modes, recommending flexible mode for its improved behavior and features. Key differences lie in how credit proration amounts are calculated, with flexible mode using the original debited amount.
- [Handle subscriptions with deferred payment | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/deferred-payment): This guide explains how to handle subscriptions with deferred payments, such as those with free trials or usage-based billing, which result in non-payment invoices. SetupIntents are used to collect and authorize payment information without immediate charging, ensuring successful future payments.
- [Design a subscriptions integration | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/design-an-integration): This guide helps design a Stripe subscriptions integration by outlining different ways to charge customers and manage their checkout and payment process. It details various pricing models including flat rate, per-seat, tiered, and usage-based options.
- [Coupons and promotion codes | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/coupons): This guide explains how to apply discounts to Stripe subscriptions and subscription items using coupons and promotion codes. Coupons define discounts, while promotion codes are customer-facing codes that map to these coupons for redemption at checkout.
- [Set up flat rate pricing | Stripe Documentation](https://docs.stripe.com/subscriptions/pricing-models/flat-rate-pricing): This guide describes how to set up flat-rate pricing for subscriptions, where customers choose a service tier and pay a fixed price. It provides an example of a webfont service with different tiers and monthly/yearly pricing options for each.
- [Set up per-seat pricing | Stripe Documentation](https://docs.stripe.com/subscriptions/pricing-models/per-seat-pricing): This guide explains how to set up per-seat pricing for subscriptions, a model where the number of seats directly corresponds to the number of units charged. It uses an example of a business charging based on the number of users or licenses.
- [Set up tiered pricing | Stripe Documentation](https://docs.stripe.com/subscriptions/pricing-models/tiered-pricing): Tiered pricing allows the unit cost to change based on quantity or usage, offering non-linear pricing. Two common models are volume-based pricing, where the entire usage is billed at the tier's rate, and graduated pricing, which applies different rates to different usage blocks.
- [Set up usage-based pricing models | Stripe Documentation](https://docs.stripe.com/subscriptions/pricing-models/usage-based-pricing): Usage-based pricing enables charging customers based on their product or service consumption. Common models include fixed fee and overage, pay as you go, and credit burndown. The fixed fee and overage model charges a base rate with included usage, plus additional charges for exceeding the entitlement.
- [How products and prices work | Stripe Documentation](https://docs.stripe.com/products-prices/how-products-and-prices-work): Products in Stripe represent the goods or services a business offers, while prices define the cost and billing frequency. These resources are fundamental for various Stripe integrations, including Checkout Sessions, Payment Links, Invoices, Quotes, and Subscriptions. Products can be created and managed directly in Stripe or imported via the API, with unique, user-definable IDs.
- [Migrate subscriptions to Stripe Billing using toolkit | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/import-subscriptions-toolkit): The Stripe Billing migration toolkit simplifies importing existing subscriptions from third-party or in-house systems, or even other Stripe accounts. Before migration, ensure a Stripe Billing integration is set up and, if necessary, request a PAN data import from your current processor. Timing is crucial to avoid missing billing periods or double billing.
- [Migrate subscriptions to Stripe Billing using Stripe APIs | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/import-subscriptions): Existing subscriptions can be migrated to Stripe Billing using Stripe APIs, offering a programmatic approach for complex or large-scale imports. This process requires setting up a Stripe Billing integration and potentially importing payment method data. Legacy pricing models can be supported by creating placeholder products in Stripe.
- [Subscriptions | Stripe Documentation](https://docs.stripe.com/subscriptions): Stripe Subscriptions allow for the creation and management of recurring payment agreements through Stripe Billing APIs. Key features include designing integration strategies, utilizing webhooks for notifications, and integrating with platforms like Salesforce for automated workflows. Options for no-code integration, such as pricing tables and customer portals, are also available.
- [Manage subscriptions on iOS | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/manage-ios): The Billing SDK for iOS enables businesses to accept subscription payments and manage entitlements directly within their iOS applications. It provides pre-built UI components for purchases and subscription management, and requires a backend server to generate Customer Sessions for secure authentication with Stripe's billing APIs.
- [Migrate subscriptions to Stripe Billing | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/migrate-subscriptions): Existing subscriptions can be migrated to Stripe Billing from third-party systems, in-house solutions, or other Stripe accounts. This can be accomplished using the no-code Billing migration toolkit or programmatically via Stripe APIs. The migration process typically involves setting up the billing integration, migrating customer and payment processor data, and then importing the subscriptions.
- [Mixed interval subscriptions | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/mixed-interval): Mixed interval subscriptions allow multiple subscription items with different prices and billing periods to be included on a single subscription, with Stripe automatically handling invoice generation. This requires using the flexible billing mode and an updated API version. Stripe generates a single invoice when item-level billing periods align and separate invoices when they diverge.
- [Pause subscriptions | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/pause): Pausing a subscription temporarily suspends both service delivery and invoice generation, useful for scenarios like vacations or temporary non-usage. This feature requires flexible billing mode and can be managed via the Pause subscription endpoint. It differs from pausing payment collection, where invoices are still generated but not collected.
- [Pause payment collection | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/pause-payment): Pausing payment collection temporarily allows services to be offered for free, acting as a grace period for customers needing more time to pay. This can be configured in the Stripe Dashboard or API with options to void invoices, keep them as drafts, or mark them as uncollectible. Invoices generated before pausing collection continue to be retried unless voided.
- [Set payment methods per-subscription | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/payment-methods-setting): The `payment_settings` parameter allows specifying unique payment methods for individual subscriptions, offering more granular control than default customer settings. Payment methods must first be activated in the Stripe Dashboard and may have restrictions based on currency or amount limitations. Stripe does not automatically select a payment method if limitations prevent its use.
- [Pending updates | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/pending-updates): Updating a subscription can generate a new invoice and trigger pending updates, particularly when the subscription requires payment for the first time, the billing period changes, or prorations occur with `proration_behavior=always_invoice`. Many other updates, such as configuration changes or metadata updates, apply immediately without payment implications.
- [Embeddable pricing table for subscriptions | Stripe Documentation](https://docs.stripe.com/payments/checkout/pricing-table): An embeddable pricing table can be created in the Stripe Dashboard to display subscription pricing and direct customers to Stripe Checkout for purchases. This feature supports common subscription models like flat-rate, per-seat, tiered pricing, and free trials, and can be customized and embedded on a website using a script tag.
- [Enable increased flexibility for subscriptions | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/billing-mode): Flexible billing mode provides enhanced functionality and more accurate billing for subscriptions, including improved prorations, usage-based pricing, and flexible invoicing. It unlocks new capabilities such as mixed intervals on the same subscription. This mode is recommended for new subscriptions and requires migration for existing ones to access these benefits.
- [Prorations | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/prorations): Prorations manage partial charges or credits when subscriptions are modified mid-billing period, ensuring accurate customer billing. For example, upgrading a subscription may result in a credit for unused time on the old plan and a charge for the new plan. Negative prorations are not automatically refunded, and positive prorations are not immediately billed, requiring manual actions.
- [Set product or subscription quantities | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/quantities): Subscriptions can be configured to include multiple products or multiple quantities of a single product, all consolidated into a single invoice. This simplifies billing for customers by requiring only one payment per billing period. The `items` parameter in the API allows specifying the price and quantity for each product within a subscription.
- [Sales-led B2B billing | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/sales-led-billing): Sales-led B2B billing in Stripe Billing automates workflows for sales teams to manage complex contracts end-to-end. It utilizes Quotes for negotiating deals and shaping them within Stripe Billing, supporting various scenarios like renewals, upsells, and mid-cycle changes. This allows for automated and managed end-to-end deal flows within Stripe.
- [Recurring pricing models | Stripe Documentation](https://docs.stripe.com/products-prices/pricing-models): Recurring pricing models define how businesses present their products and services on Stripe, including cost, currency, and service period. These models are built using products (what is sold) and prices (how much and how often to charge). Common models include flat rate, per-seat, tiered pricing, and usage-based pricing.
- [Automation use-cases | Stripe Documentation](https://docs.stripe.com/billing/automation-recipes): Automation use-cases in Stripe provide examples for customizing billing processes, such as dunning flows for annual subscribers or notifications for overdue high-value invoices. These automations can be triggered by events like subscription payment failures and can include conditional logic and specific actions to improve recovery rates and cash flow.
- [How automations work | Stripe Documentation](https://docs.stripe.com/billing/automations): Stripe Billing automations provide a no-code solution to build custom workflows for streamlining business processes, enhancing customer communication, and improving revenue recovery. These workflows are configured using triggers, filter conditions, and actions, with recipes available for common use cases. Setting up automations involves selecting a trigger event, optionally adding filters, defining actions and delays, and arranging their priority.
- [Automate customer emails | Stripe Documentation](https://docs.stripe.com/billing/revenue-recovery/customer-emails): Customer emails in Stripe Billing help prevent involuntary churn by notifying customers about potential issues like failed payments and offering them a chance to intervene. You can configure emails for various notification types, including payment confirmations, failed payments, trial ending reminders, and expiring cards. These emails can link to a Stripe-hosted Customer Portal or your own subscription management page for customers to update payment methods or manage their subscriptions.
- [Revenue recovery | Stripe Documentation](https://docs.stripe.com/billing/revenue-recovery): Stripe's revenue recovery features help prevent lost revenue and reduce churn by automating the handling of failed subscription payments and missed trial conversions. Key features include recovery analytics, smart retries for failed payments, automated email notifications to customers, no-code automations for custom logic, and automatic card updates. These tools aim to recover recurring revenue without requiring manual intervention or coding.
- [Revenue recovery analytics | Stripe Documentation](https://docs.stripe.com/billing/revenue-recovery/recovery-analytics): Revenue recovery analytics in the Stripe Dashboard provide insights into subscription payment failure and recovery rates. Key performance indicators include the volume and rate of failed payments, as well as the volume and rate of recovered payments. These analytics help businesses understand the impact of payment failures and optimize their revenue recovery strategies by identifying trends and areas for improvement.
- [Automate payment retries | Stripe Documentation](https://docs.stripe.com/billing/revenue-recovery/smart-retries): Stripe Billing automates retries for failed subscription and invoice payments to minimize involuntary churn. Users can configure these retries in the Dashboard, with 'Smart Retries' leveraging AI to determine the optimal times for retrying payments. Stripe automatically handles retries based on available payment methods and decline codes, with specific rules for when retries are not performed.
- [Extend Stripe Billing with custom discount logic | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/script-coupons): Stripe Billing allows for custom discount logic on coupons to go beyond fixed percentages or amounts. This enables businesses to create flexible discount rules, such as offering different discounts for monthly versus annual subscribers, setting maximum discount amounts, or implementing tiered discounts based on purchase volume. These custom logic scripts can be built using Stripe's scripting language and are recommended to be tested in a sandbox environment.
- [Set up a subscription with pre-authorized debit in Canada | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/acss-debit): This guide explains how to set up subscriptions using Canadian pre-authorized debits (PAD) as a payment method. It covers creating products and prices within the Stripe Dashboard, which are essential for defining what you sell and how you charge. The process involves setting up the product details and recurring charge information for a subscription service.
- [Set up a subscription with BECS Direct Debit in Australia | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/au-becs-debit): This documentation explains how to set up subscriptions using BECS Direct Debit in Australia. It guides users through creating products and prices in the Stripe Dashboard, which define the items or services being sold and their associated costs and billing frequencies. The guide recommends using the Payment Element for new users for a streamlined integration.
- [Set up a subscription with bank transfers | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/bank-transfer): This guide details how to set up subscriptions using bank transfers as a payment method in Stripe. It outlines the necessary steps, including creating products and recurring prices in the Dashboard or via the API. The process also involves creating or retrieving a customer object with a valid email address, as funds are held in the customer's cash balance.
- [Set up a subscription with PayPal | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/paypal): This guide explains how to set up subscriptions with PayPal, enabling recurring payments for customers. It covers enabling PayPal recurring payments in the Stripe Dashboard, which is usually automatic but may require manual activation due to PayPal's policies. The process involves creating a Checkout Session to represent the customer's purchase intent and redirecting them to a Stripe-hosted payment form.
- [Integrate with third-party payment processors | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/third-party-payment-processing): Stripe Billing allows integration with third-party payment processors for subscriptions and invoices. Businesses can choose to integrate their own processor or use out-of-band invoices to manage payments made with off-Stripe methods. This integration enables creating payment requests, managing subscriptions with custom payment methods, and using webhooks to update the subscription lifecycle based on off-Stripe payment results.
- [Set up a subscription with stablecoin payments | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/stablecoins): This guide explains how to set up subscriptions that accept stablecoin payments, allowing recurring withdrawals from a customer's crypto wallet. It covers creating products and prices in the Stripe Dashboard for stablecoin transactions. The setup involves defining the product details and recurring charge information for a subscription service that utilizes cryptocurrency.
- [Subscription schedules | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/subscription-schedules): Subscription schedules automate changes to subscriptions over time by defining phases with specific properties and durations. These schedules can be used to start subscriptions on future dates, backdate them, or manage upgrades and downgrades. After all phases are completed, the schedule's behavior is determined by its end_behavior, and they are accessible via the Stripe Billing Dashboard and API.
- [Use trial periods on subscriptions | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/trials): You can initiate a customer's subscription with a free trial period by specifying a `trial_end` timestamp or `trial_period_days` when creating the subscription. During the trial, an invoice is generated with a zero amount and a 'Free trial' description. Once the trial concludes, the subscription transitions to its paid billing cycle, requiring a payment method to be present.
- [Change the price of existing subscriptions | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/change-price): This guide explains how to change the price of existing subscriptions, allowing for upgrades or downgrades to different tiers. It details the process of updating subscription items to reflect new pricing selections. To perform these changes, you need to retrieve the identifiers for the relevant subscriptions and items, which can be done using the list subscriptions method with appropriate filters.
- [Usage-based billing | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based-legacy): Usage-based billing allows charging customers based on their service consumption rather than fixed quantities, requiring usage to be recorded and reported. This model typically involves collecting payment in arrears and can be implemented with different pricing structures like per-minute charges or graduated tiers. Stripe provides tools to model these pricing strategies through the Dashboard or API.
- [Migrate to billing meters | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based-legacy/migration-guide): Stripe is deprecating its usage-records billing in favor of billing meters for usage-based billing. Billing meters offer advantages like high-throughput usage reporting and the ability to collect usage before a subscription is created. While migrating, you can continue using usage records temporarily, but the new system supports tracking usage across multiple customers and doesn't require a subscription to report events.
- [Model usage-based pricing | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based-legacy/pricing-models): Usage-based pricing models charge customers based on their consumption of a service during a billing period, necessitating the recording and reporting of usage. This model differs from per-seat or flat-rate pricing by requiring payment in arrears. Stripe supports various usage types, including 'metered' and 'licensed,' and offers 'Standard' and 'Package' pricing options within the Dashboard.
- [Record usage for billing | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based-legacy/recording-usage): Throughout each billing period, businesses must report customer usage to Stripe to ensure accurate billing for metered subscriptions. This is done by creating usage records that include the subscription item, quantity used, and a timestamp. Best practices include using idempotency keys to prevent duplicate reporting and ensuring timestamps fall within the current billing period.
- [How advanced usage-based billing works | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based/advanced/about): Advanced usage-based billing enables SaaS and AI businesses to charge based on usage while also incorporating recurring fees and managing credits. This system allows defining charges based on specific usage attributes (dimensions), managing numerous rates across meters, and implementing real-time credit management with automated issuance and top-ups. Supported pricing models include pay-as-you-go, flat fee with overages, and real-time credit burndown.
- [Advanced usage-based billing | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based-v2/overview): Stripe's advanced usage-based billing allows businesses to create complex hybrid pricing models by defining charges based on specific usage event attributes. It supports managing numerous rates, real-time credit burndown, automated credit issuance, and plan versioning for SaaS and AI companies.
- [Implement advanced usage-based billing with pricing plans | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based/pricing-plans): Pricing plans in Stripe enable the creation of complex billing models by grouping different pricing components, such as usage-based rate cards, recurring license fees, and recurring credit grants. These plans automatically enroll and bill customers for all recurring components at a configured cadence.
- [Advanced usage-based billing | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based/advanced/compare): Advanced usage-based billing in Stripe allows businesses to charge customers based on specific usage data characteristics and manage hundreds of prices per meter. It facilitates real-time credit burndown, automated credit issuance, and the rollout of new usage-based prices, supporting models like pay-as-you-go, flat fee with overages, and credit burndown with automatic top-ups.
- [Set up billing credits | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based/billing-credits/implementation-guide): Billing credits can be implemented in Stripe to offer prepaid or promotional usage-based services. Customers can use these credits to pay for usage, and they can be granted via the Stripe Dashboard or API with optional expiry dates and priority settings.
- [Billing credits | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based/billing-credits): Billing credits in Stripe can be used for prepaid services or as promotional offerings for usage-based products. Customers can utilize these credits for memberships, pay-as-you-go plans, or subscriptions, but they cannot be used for gift cards, stored value, or third-party payments.
- [How usage-based billing works | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based/how-it-works): Usage-based billing on Stripe allows charging customers based on their product or service consumption through a four-component lifecycle: ingesting usage data, setting up the product catalog, billing through subscriptions, and monitoring usage with alerts. Key concepts include customers, subscriptions, prices, and meters for tracking consumption.
- [Usage-based billing | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based): Usage-based billing enables charging customers based on their consumption of a product or service, integrating various pricing models with SaaS products. Key features include recording usage data, offering billing credits, and monitoring usage with alerts.
- [Manage your usage-based billing setup | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based/manage-billing-setup): After setting up a usage-based billing model, various aspects can be modified, such as updating subscription item prices or canceling subscriptions. The `transform_quantity` option allows for usage transformation before applying prices, useful for billing on packages of a product rather than individual units, though it's not compatible with tiered pricing.
- [Set up usage-based alerts | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based/alerts): Usage-based alerts notify businesses when customers exceed meter usage thresholds or trigger invoices at specific billing thresholds. These alerts can be configured for individual customers or all customers and can be set up via the Stripe Dashboard or API.
- [Analyze and query meter usage | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based/analytics): The Meter Usage Analytics API allows querying and analyzing customer meter usage data to build custom dashboards, generate reports, and understand consumption patterns. It enables querying by time periods, filtering by meter dimensions, and analyzing across multiple meters.
- [Monitor usage with alerts | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based/monitor): Alerts can be used to notify when customers exceed meter usage thresholds or to trigger invoices at specific billing thresholds, applicable to individual or all customers. These alerts can be integrated into business workflows like emailing users, deprovisioning access, or notifying sales teams for upsell opportunities.
- [Set up thresholds | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based/thresholds): Billing thresholds can be set up to limit the amount owed or products consumed between invoices or charges. Monetary thresholds trigger an invoice when accrued usage reaches a specific amount, while usage thresholds prevent frequent invoicing by setting a limit on units consumed.
- [Configure an invoice finalization grace period | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based/configure-grace-period): A default finalization grace period of 1 hour allows for reporting usage for the previous billing period before an invoice is finalized. This period can be extended up to 72 hours, but should not exceed the service period to avoid confusion with automatic invoice collection.
- [Create and configure a meter | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based/meters/configure): Meters are essential for usage-based billing, specifying how meter events (customer actions) are aggregated over a billing period and attached to prices. After creation, only the display name of a meter can be modified.
- [Record usage for billing | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based/recording-usage): Recording customer usage data in Stripe throughout each billing period ensures accurate billing amounts. Usage can be recorded via the Stripe Dashboard, API, or by using Amazon S3, with Stripe processing meter events asynchronously.
- [Record usage in the Dashboard | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based/recording-usage-in-bulk-dashboard): Usage data can be recorded in the Stripe Dashboard either manually by inputting values or by uploading a CSV file. Stripe then parses, validates, and transforms this data into meter events, which can be viewed in the live meter feed.
- [Record usage for billing using Amazon S3 | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based/recording-usage-in-bulk): Meter usage events can be recorded in bulk by sending them to Stripe from an Amazon S3 storage bucket using CSV, JSON, or JSON Lines file formats. Stripe parses and validates this data into meter events, which appear on the subscription invoice.
- [Record usage for billing with the API | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based/recording-usage-api): Usage can be recorded using the Stripe API by sending meter events that include the event name, customer ID, numerical value, and an optional timestamp. Idempotency keys can be used to prevent duplicate reporting of usage events.
- [Set up a credit-based pricing model | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based/use-cases/credits-based-pricing-model): A credit-based pricing model allows offering a fixed monetary amount of usage across products, providing upfront predictability for customers. Customers purchase credits and can spend them on various metered services, with overage charges applied if they exceed the purchased credit amount.
- [Set up a flat fee and overages pricing model | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based-v1/use-cases/flat-fee-and-overages): The flat fee and overages pricing model combines a predictable recurring fee for a base package with separate billing for additional usage beyond a set limit. This model ensures steady revenue while allowing customers to scale their consumption.
- [Set up a pay-as-you-go pricing model | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based/implementation-guide): This guide explains how to implement a pay-as-you-go pricing model using Stripe, where customers are charged based on their accrued usage. It involves creating meters to aggregate usage events, setting up products and prices, and recording customer usage through meter events.
- [Use cases | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/usage-based-v1/use-cases): This page outlines common use cases for Stripe's usage-based billing, including pay-as-you-go, flat fee with overages, and credit-based pricing models. It directs users to specific guides for implementing these models and recording usage data.
- [Subscription use cases | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/use-cases): This page explores various business use cases for Stripe subscriptions, such as integrating SaaS businesses, managing sales-led B2B contracts, billing for multi-entity businesses, and integrating with Salesforce. It also covers revenue recognition, recovery, and analyzing business performance with subscription metrics.
- [Migrate to Stripe Tax | Stripe Documentation](https://docs.stripe.com/billing/taxes/migration): This guide details how to migrate existing subscriptions to Stripe Tax to enable automatic tax calculation based on product and customer location. It outlines steps for activating Stripe Tax and using automated tooling or manual updates to ensure tax is calculated correctly for future billing cycles.
- [Collect taxes for recurring payments | Stripe Documentation](https://docs.stripe.com/billing/taxes/collect-taxes): This page explains how to collect and report taxes for recurring payments using Stripe Tax or Tax Rates. Stripe Tax automatically calculates taxes, while Tax Rates allow manual definition of rates for invoices and subscriptions.
- [Customer Tax IDs | Stripe Documentation](https://docs.stripe.com/billing/customer/tax-ids): This document explains how to store, validate, and display customer tax identification numbers within Stripe Billing. It provides a comprehensive list of supported Tax ID types by country, detailing their format and impact on tax calculations.
- [Tax rates | Stripe Documentation](https://docs.stripe.com/billing/taxes/tax-rates): This page describes how to define and apply tax rate objects to invoices, subscriptions, and one-time payments in Stripe. It differentiates between automated tax calculation with Stripe Tax and manual rate management using Tax Rates.
- [API and advanced usage | Stripe Documentation](https://docs.stripe.com/billing/testing/test-clocks/api-advanced-usage): This guide covers advanced strategies for using test clocks in Stripe for simulating Billing objects and testing integrations. It explains how to create simulations, set frozen times, advance time, and monitor changes to test various scenarios.
- [Use Simulations to simulate Billing objects | Stripe Documentation](https://docs.stripe.com/billing/testing/test-clocks): This page explains how to use simulations with test clocks to test Stripe Billing integrations by simulating how Billing resources change over time. It allows for testing complex scenarios like plan upgrades, handling payment failures, and validating webhook processing.
- [Simulate subscriptions | Stripe Documentation](https://docs.stripe.com/billing/testing/test-clocks/simulate-subscriptions): This guide demonstrates how to simulate subscriptions in a Stripe sandbox environment to view expected events like invoices and renewals. It explains how to run a simulation, advance time, and manage simulation objects, noting limitations on time advancement intervals.
- [Test your Billing integration | Stripe Documentation](https://docs.stripe.com/billing/testing): This page provides a comprehensive guide on testing Stripe Billing integrations to ensure production readiness. It outlines key components to test, such as customer sign-up and invoicing, and emphasizes the importance of webhooks for handling asynchronous events.
- [Billing for LLM tokens | Stripe Documentation](https://docs.stripe.com/billing/token-billing): This page introduces a private preview feature for billing LLM tokens, allowing businesses to manage pricing complexity and ensure consistent margins. It supports various AI pricing models like credit packs, fixed fees with included usage, and pure usage-based billing.
- [Billing for a multi-entity business | Stripe Documentation](https://docs.stripe.com/billing/multi-entity-business): This guide explains how to integrate Stripe Billing for businesses with multiple legal entities, recommending the use of Stripe Connect with connected accounts. Each account maintains its own customers and products, with the platform account serving as a single integration point.
- [Using webhooks with subscriptions | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/webhooks): This page details how to use webhooks to receive real-time notifications from Stripe about subscription activity. It explains how to set up webhook endpoints, handle events like payment failures and status changes, and verify incoming events for security.
- [Legacy extensions | Stripe Documentation](https://docs.stripe.com/building-extensions): This page discusses deprecated Stripe extensions, which are replaced by Stripe Apps for developing integrations. It provides historical reference information and directs users to migration guides for existing legacy extensions.
- [Legacy plugins | Stripe Documentation](https://docs.stripe.com/building-plugins): This page addresses deprecated Stripe plugins, which previously required users to authenticate with secret API keys. Stripe Apps is now the recommended method for authentication, supporting restricted API keys and OAuth 2.0.
- [Capital application component | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/capital-financing-application): This page describes the Capital application component, an embedded UI element that allows eligible connected accounts to complete a financing application directly within a platform's interface. It focuses on the application flow, excluding promotional content.
- [Capital promotion component | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/capital-financing-promotion): This page introduces the Capital promotion component, an embedded UI element that displays promotional content about Stripe Capital financing offers and launches the application process. It includes educational content before directing users to apply.
- [Capital financing component | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/capital-financing): This page details the Capital financing component, an embedded UI element that enables connected accounts to view and manage their active Capital financing status after accepting an offer. It allows tracking payment progress and transaction history.
- [Capital | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/capital): This page provides an overview of Stripe Capital embedded components for platforms, including the Capital promotion, promo tile, financing, and application components. These components help increase program discoverability and allow connected accounts to manage their financing.
- [Set up an embedded components integration | Stripe Documentation](https://docs.stripe.com/capital/embedded-component-integration): This guide explains how to set up Stripe Capital for platforms using embedded components, allowing you to customize the integration with pre-built UI elements. It covers launching a Capital program from the Stripe Dashboard and integrating these components to manage financing offers and track paydown progress for connected accounts.
- [Set up Capital | Stripe Documentation](https://docs.stripe.com/capital/getting-started): This page outlines how to set up Stripe Capital for platforms, offering two integration options: a no-code approach where Stripe handles communications, or a custom approach where you manage communications via APIs and webhooks. It guides users through launching a Capital program via the Stripe Dashboard to provide financing offers to eligible connected accounts.
- [How Stripe Capital works | Stripe Documentation](https://docs.stripe.com/capital/how-stripe-capital-works): Stripe Capital provides financing for eligible businesses through loans or merchant cash advances, with a flat fee instead of traditional interest and late fees. Payments are withheld directly from sales on Stripe, and financing types are determined by Stripe based on eligibility criteria like processing volume and history.
- [Import non-Stripe data into Capital underwriting | Stripe Documentation](https://docs.stripe.com/capital/import-non-stripe-data): This document details how to import non-Stripe payment data into Stripe Capital underwriting to expand financing eligibility for connected accounts. By incorporating transaction data from third-party sources, platforms can increase loan offer amounts and potentially decrease premium rates for their users.
- [Marketing your Capital program | Stripe Documentation](https://docs.stripe.com/capital/marketing): This guide provides instructions on creating marketing assets for Stripe Capital programs to educate and promote the offering to users. It emphasizes the need for Stripe approval for all customer-facing materials and outlines marketing requirements based on integration type (no-code, embedded components, or API).
- [Merchant cash advance marketing guidelines | Stripe Documentation](https://docs.stripe.com/capital/mca-marketing-guidelines): This guide outlines the marketing requirements for merchant cash advances (MCAs) offered through Stripe Capital, emphasizing the distinction between MCAs and loans. It provides specific terminology guidelines for accurately and compliantly representing MCAs in marketing materials, all of which require Stripe approval before publication.
- [Set up a no-code integration | Stripe Documentation](https://docs.stripe.com/capital/no-code-integration): This page explains how to set up a no-code Stripe Capital program using the Stripe Dashboard, which is available for US-based businesses. It covers previewing and customizing co-branded emails that Stripe sends to connected accounts for financing offers and servicing.
- [Stripe Capital | Stripe Documentation](https://docs.stripe.com/capital/overview): Stripe Capital offers financing solutions for businesses, either enabling platforms to provide financing to their connected accounts or allowing businesses to access financing offers directly. It details financing types like loans and merchant cash advances, and provides resources for setting up a Capital program or accessing offers.
- [Build a custom Capital program | Stripe Documentation](https://docs.stripe.com/capital/api-integration): This guide details how Connect platforms can integrate with the Stripe Capital API to build a custom Capital program, covering the entire lifecycle from marketing offers to providing financing reporting. It explains how to retrieve financing offers, make the application available, and ensure branding settings are correctly configured.
- [How Stripe Capital for platforms works | Stripe Documentation](https://docs.stripe.com/capital/how-capital-for-platforms-works): This document explains the functionality of Stripe Capital for platforms, available in the US and UK, outlining eligibility requirements for both platforms and connected accounts. It covers the daily automatic eligibility review of connected accounts based on their payment activity and other business criteria.
- [Capital promo tile component | Stripe Documentation](https://docs.stripe.com/capital/promotional-tile): The Capital promo tile component displays prequalified financing offers to connected accounts directly on a platform's website or app, aiming to increase adoption and reduce friction. This white-labeled component can be customized to match platform design and provides direct access to application, improving visibility and driving action.
- [Refills | Stripe Documentation](https://docs.stripe.com/capital/refills): This guide explains how to enable refills for Stripe Capital programs, allowing for additional financing offers to connected accounts that have made substantial repayment progress. It details the refill offer lifecycle, webhook notifications, and how connected accounts can accept refill offers, potentially receiving a discount on their existing balance.
- [Regulatory compliance guidelines | Stripe Documentation](https://docs.stripe.com/capital/regulatory-compliance): This page outlines the regulatory compliance guidelines for offering Stripe Capital to users in the US and UK, covering marketing and user interface requirements. It includes a compliance checklist and details on managing complaints, emphasizing the need for legal review and adherence to financial regulations.
- [Replacements | Stripe Documentation](https://docs.stripe.com/capital/replacements): This guide explains how to manage financing offer replacements within Stripe Capital API integrations, allowing platforms to track the history of updated offer terms for connected accounts. Enabling replacements ensures platforms can access both original and new offer details when eligibility changes.
- [Provide and reconcile reports | Stripe Documentation](https://docs.stripe.com/capital/reporting-and-reconciliation): This guide details how to provide Capital reports to connected accounts and reconcile Capital transactions within existing reports using Stripe APIs. It explains how to offer reports detailing outstanding balances and payment history, and how to synchronize payout, paydown, and reversal transaction data.
- [Capital metrics | Stripe Documentation](https://docs.stripe.com/capital/reporting): The Capital metrics page in the Stripe Dashboard provides insights into the performance of a Capital program, displaying data on originations, conversion rates, and offer engagement. It offers detailed views on the offer funnel, platform earnings, average accepted financing offers, and estimated eligibility for connected accounts.
- [Managing customer support | Stripe Documentation](https://docs.stripe.com/capital/servicing): This page describes how Stripe handles customer support for Capital programs, acting as the first line of defense for borrower inquiries. It outlines the servicing functions Stripe manages, such as reviewing applications and collecting payments, and provides approved messaging and templates for platforms that choose to field basic inquiries.
- [Testing Capital | Stripe Documentation](https://docs.stripe.com/capital/testing): This guide explains how to use Stripe's sandbox environment to test Capital integrations by simulating the end-to-end flow of connected account financing. It covers creating test offers with specified parameters and verifying their status in the Dashboard's Financing Reporting page.
- [Co-badged cards compliance | Stripe Documentation](https://docs.stripe.com/co-badged-cards-compliance): This document explains EU regulations requiring businesses to honor customer card brand choice for co-badged cards (e.g., Cartes Bancaires co-badged with Visa). It details how to display available card networks, abide by the cardholder's preferred network selection, and allow for updates to this preference during checkout.
- [Card Product Codes | Stripe Documentation](https://docs.stripe.com/card-product-codes): This page explains product codes used to identify specific credit card programs or products within the Stripe API. It details how to retrieve these codes from the PaymentMethod object and lists supported product codes for Visa and Mastercard, noting that the field may be null if the code is not collected or supported.
- [Adds support for ownership exemption reason to the Accounts API | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-01-27/ownership-exemption-reason-accounts-api): The Accounts API now supports an ownership_exemption_reason parameter within the company field. This allows businesses to submit an exemption reason for ultimate beneficial ownership requirements, which Stripe then verifies instead of individual owners. Supported reasons include 'qualified_entity_exceeds_ownership_threshold' and 'qualifies_as_financial_institution'.
- [Errors now produce exceptions for unrecognized API parameters | Stripe Documentation](https://docs.stripe.com/changelog/2011-06-21/exceptions-unrecognized-api-parameters): The API now raises exceptions for unrecognized parameters instead of silently ignoring them. This change improves error handling and helps prevent silent failures in integrations. Developers should upgrade their API version or update their requests to ensure compatibility.
- [Plans no longer include the identifier field | Stripe Documentation](https://docs.stripe.com/changelog/2011-06-28/plans-no-longer-identifier-field): The Plan object no longer includes the identifier field, as it was a duplicate of the id field. This change simplifies the data structure for Plan objects. Developers should upgrade their API version to ensure their integrations are compatible.
- [Lists now provide a total count of items and a data field | Stripe Documentation](https://docs.stripe.com/changelog/2011-08-01/lists-provide-total-count-data-field): List objects in the API have been updated to include a 'data' property containing an array of items (defaulting to 10) and a 'count' property indicating the total number of items. This provides clearer pagination and total count information for lists. Developers should upgrade their API version to utilize this new format.
- [Cards validate differently when creating tokens | Stripe Documentation](https://docs.stripe.com/changelog/2011-09-15/cards-validate-differently-creating-tokens): The card validation behavior when creating tokens has been updated. This change enhances security measures for token creation. Developers are advised to upgrade their API version to ensure their integrations are compatible with the new validation process.
- [Fields with null values are now included in API responses | Stripe Documentation](https://docs.stripe.com/changelog/2012-02-23/fields-null-values-included-api-responses): API responses now include all fields, even those with null values. Previously, fields with null values were omitted from responses. This change provides more comprehensive data representation. Developers should upgrade their API version to utilize this updated response format.
- [Customers no longer include a next_recurring_charge field | Stripe Documentation](https://docs.stripe.com/changelog/2012-03-25/customers-no-longer-next-recurring-charge-field): The Customer object no longer includes the next_recurring_charge property. Instead, developers should use the upcoming invoice call for this information. This change encourages the use of more accurate methods for retrieving recurring charge data. Developers should upgrade their API version to adapt to this change.
- [Tokens no longer include the amount and currency properties | Stripe Documentation](https://docs.stripe.com/changelog/2012-06-18/tokens-no-longer-amount-currency-fields): The Token object no longer includes the amount and currency properties. This change streamlines the data associated with tokens. Developers should upgrade their API version to ensure their integrations correctly handle token data without these properties.
- [Customers no longer include the uncaptured field | Stripe Documentation](https://docs.stripe.com/changelog/2012-07-09/customers-no-longer-uncaptured-field): The Customer object no longer includes the uncaptured property. This change removes potentially misleading information from the Customer object. Developers should upgrade their API version to account for this modification.
- [Discounts no longer include an extraneous id field | Stripe Documentation](https://docs.stripe.com/changelog/2012-09-24/discounts-no-longer-extraneous-id-field): The Discount object no longer includes an extraneous id property. This change reduces data redundancy within the Discount object. Developers should upgrade their API version to ensure their integrations are compatible with this updated structure.
- [Invoices now include a sublist of invoice line items | Stripe Documentation](https://docs.stripe.com/changelog/2012-10-26/invoices-include-invoice-line-items-sublist): Invoices now include a 'lines' property which is a paginated sublist of all items contributing to the invoice. This update provides more detailed and manageable information about invoice line items. Developers should upgrade their API version to leverage this enhanced invoice structure.
- [Renames the disputed field for Charges to dispute | Stripe Documentation](https://docs.stripe.com/changelog/2012-11-07/renames-disputed-field-charges-dispute): The 'disputed' field on the Charge object has been renamed to 'dispute'. This change provides more accurate terminology for charge disputes. Developers should update their integrations to use the new 'dispute' field name.
- [Failed invoice payments now return an HTTP error | Stripe Documentation](https://docs.stripe.com/changelog/2013-02-11/failed-invoice-payments-return-http-error): The Pay invoice call now returns an HTTP error when a charge is unsuccessful. Previously, it would return a 200 status with 'paid' set to false. This improves error handling and consistency for failed invoice payments. Developers should upgrade their API version to implement this change.
- [Disputes on charges are now tracked through the stripe_fee field and included in the fee total | Stripe Documentation](https://docs.stripe.com/changelog/2013-02-13/disputes-tracked-stripe-fee-field-fee-total): Disputed charges now include dispute fees in the 'fee_details' array and the total fee calculation on the Charge object. This provides more comprehensive fee information for disputed transactions. Developers should upgrade their API version to utilize this updated fee tracking.
- [Customers now include a cards sublist and default_card field | Stripe Documentation](https://docs.stripe.com/changelog/2013-07-05/customers-include-cards-sublist-default-card-field): The Customer object now replaces the 'active_card' property with a 'cards' sublist and a 'default_card' ID property. This allows for the management of multiple cards per customer. Developers should upgrade their API version to implement this change and manage customer cards more effectively.
- [Lets the description and email fields be null on several objects | Stripe Documentation](https://docs.stripe.com/changelog/2013-08-12/allows-description-email-fields-null): The description and email fields on several objects (Customer, Charge, InvoiceItem, Recipient) can now be set to null by providing empty string values in POST requests. This offers greater flexibility in managing data for these fields. Developers should upgrade their API version to utilize this new capability.
- [Fee details have moved from charges to their corresponding balance transactions | Stripe Documentation](https://docs.stripe.com/changelog/2013-08-13/fee-details-moved-balance-transactions): Fee and fee_details properties have been removed from the Charge object, with fee information now located in the corresponding balance transaction. This change centralizes fee information for better management. Developers should upgrade their API version to access fee data through balance transactions.
- [Fee details have moved from transfers to their corresponding balance transactions | Stripe Documentation](https://docs.stripe.com/changelog/2013-08-13/fee-details-moved-balance-transactions-transfers): Fee and fee_details properties have been removed from the Transfer object, with fee information now located in the corresponding balance transaction. This change centralizes fee information for better management. Developers should upgrade their API version to access fee data through balance transactions.
- [Coupons only apply to an invoice's total balance, no longer applying to zero-cost invoices | Stripe Documentation](https://docs.stripe.com/changelog/2013-10-29/coupons-apply-invoice-total-balance): Coupon behavior has been updated: amount-off coupons no longer increase the customer balance if the discount exceeds the invoice amount, and coupons are ignored for zero-cost invoices. This change prevents unexpected balance increases and clarifies coupon application. Developers should upgrade their API version to ensure compatibility.
- [Application fees now provide an expandable account field to obtain user details | Stripe Documentation](https://docs.stripe.com/changelog/2013-12-03/application-fees-provide-expandable-account-field): The Application Fee object now replaces the 'user' and 'user_email' properties with an expandable 'account' property. This allows for the retrieval of more detailed account information. Developers should upgrade their API version to utilize this new expandable field for account details.
- [Application fee refunds are now proportional to the charged amount | Stripe Documentation](https://docs.stripe.com/changelog/2013-12-03/application-fee-refunds-proportional-charged-amount): Stripe now refunds application fees proportionally to the amount of the charge refunded, rather than refunding the entire fee. This change provides more accurate fee adjustments when only a portion of a charge is refunded.
- [Customers now support multiple subscriptions | Stripe Documentation](https://docs.stripe.com/changelog/2014-01-31/customers-support-multiple-subscriptions): Customers can now have multiple subscriptions. The Customer object has been updated to replace the singular subscription property with a plural subscriptions property to reflect this change.
- [Trial end dates are no longer computed for canceled subscriptions | Stripe Documentation](https://docs.stripe.com/changelog/2014-01-31/trial-end-dates-canceled-subscriptions): Trial end dates are no longer computed for canceled subscriptions. This prevents unexpected trial extensions by ensuring that previous trial information does not affect new subscription trial calculations.
- [Renames the statement descriptor field | Stripe Documentation](https://docs.stripe.com/changelog/2014-03-13/renames-statement-descriptor-field-transfers): The statement_descriptor property on the Transfer object has been renamed to statement_description. This change aims to improve consistency in naming conventions within the API.
- [Lists no longer include the count field | Stripe Documentation](https://docs.stripe.com/changelog/2014-03-28/lists-no-longer-include-count-field): The "count" property has been removed from list responses. This change streamlines the data returned in API list responses.
- [Replaces the account field on transfers | Stripe Documentation](https://docs.stripe.com/changelog/2014-05-19/renames-account-field-transfers-bank-account): The 'account' property on the Transfer object is replaced by 'bank_account'. The 'bank_account' property is only present when the transfer is made to a bank account, providing more specific destination information.
- [Renames the type field on cards to brand | Stripe Documentation](https://docs.stripe.com/changelog/2014-06-13/renames-type-field-cards-brand): The 'type' property on the Card object has been renamed to 'brand'. This change is intended to improve clarity and better reflect the property's purpose.
- [Invoices now include a sublist of refunds through the refunds field | Stripe Documentation](https://docs.stripe.com/changelog/2014-06-17/invoices-include-refunds-sublist-refunds-field): The refunds property on the Charge object has been updated from an array to a sublist object. This change provides more consistent and detailed refund information for charges.
- [Invoice line items now include subscription plans and quantities | Stripe Documentation](https://docs.stripe.com/changelog/2014-07-22/invoice-line-items-include-subscription-plans-quantities): Invoice line items now include details about the associated subscription's plan and quantity. This provides more context for prorated charges within invoices.
- [Application fees now include a sublist of refunds through the refunds field | Stripe Documentation](https://docs.stripe.com/changelog/2014-07-26/application-fees-include-refunds-sublist-refunds-field): The refunds property on the Application Fee object has been changed from an array to a sublist object. This aligns application fee refunds with the structure of charge refunds, offering more consistent data.
- [You can now retrieve balance histories rather than relying on Transfer fields | Stripe Documentation](https://docs.stripe.com/changelog/2014-08-04/retrieve-balance-histories-transfer-fields): The 'other_transfers', 'summary', and 'transactions' properties have been removed from automatic transfer responses. Users should now retrieve balance history using the /v1/balance/history endpoint for centralized balance information.
- [Disputes now provide several new statuses | Stripe Documentation](https://docs.stripe.com/changelog/2014-08-20/disputes-provide-several-new-statuses): The Dispute object now includes three new values for its status property: 'warning_needs_response', 'warning_under_review', and 'charge_refunded'. These additions provide more granular information about dispute statuses.
- [Disputes now include multiple balance transactions | Stripe Documentation](https://docs.stripe.com/changelog/2014-08-20/disputes-include-multiple-balance-transactions): The 'balance_transaction' property on the Dispute object has been replaced with 'balance_transactions'. This change provides more detailed information about funds withdrawn and reinstated due to disputes.
- [Bank Accounts now include a status enum that replace multiple fields | Stripe Documentation](https://docs.stripe.com/changelog/2014-09-08/bank-accounts-include-status-enum): The 'disabled', 'validated', and 'verified' properties on the Bank Account object have been replaced by a single 'status' enum property. This simplifies the representation of bank account statuses.
- [You can no longer retrieve tokens with publishable keys | Stripe Documentation](https://docs.stripe.com/changelog/2014-10-07/no-longer-retrieve-tokens-publishable-keys): Publishable keys can no longer be used to retrieve Token objects. This change enhances security by preventing the retrieval of sensitive token information directly from the client.
- [Creating a Card or Bank Account with a publishable key omits fingerprints in API responses | Stripe Documentation](https://docs.stripe.com/changelog/2014-10-07/create-card-bank-account-omit-fingerprints): When creating card or bank account tokens using a publishable key, the 'fingerprint' property is no longer included in the API response. This change improves data privacy by omitting this identifier.
- [Account activation status terms updated for payments and transfers | Stripe Documentation](https://docs.stripe.com/changelog/2014-11-05/renames-charge-account-enabled-fields): The 'charge_enabled' and 'transfer_enabled' properties on the Account object have been renamed to 'charges_enabled' and 'transfers_enabled', respectively. These changes better reflect the functionality of these properties.
- [Disputes are now reported as won even if the charge is refunded | Stripe Documentation](https://docs.stripe.com/changelog/2014-11-20/disputes-reported-won-refunded-charge): Disputes that are won are now reported with the status 'won', even if the associated charge was refunded. Previously, such disputes would transition to 'charge_refunded', making the tracking of dispute resolution more accurate.
- [Invoice items now reflect the metadata for their associated subscription, rather than plan | Stripe Documentation](https://docs.stripe.com/changelog/2014-11-20/invoice-items-reflect-subscription-metadata): Invoice items associated with subscriptions now reflect the subscription's metadata instead of the plan's metadata. This provides more specific and relevant custom data for individual subscriptions.
- [Disputes now include an evidence_details object for evidence documentation | Stripe Documentation](https://docs.stripe.com/changelog/2014-12-08/disputes-include-evidence-details-object): The Dispute object now includes an 'evidence_details' object, which replaces the 'evidence_due_by' property. This allows for structured evidence submission, including due dates and submission counts, offering more detailed documentation.
- [Introduces the statement_description field and logic for how charges, invoices, plans, and transfers render statement descriptors | Stripe Documentation](https://docs.stripe.com/changelog/2014-12-17/introduces-statement-description-field-logic): Stripe introduces the statement_descriptor field, replacing statement_description on Charges, Invoices, Plans, and Transfers. This change offers greater control over how statement descriptors appear on customer transactions. The new field takes precedence, and the behavior does not apply to PaymentIntents.
- [Creating accounts using the API requires the 2014-12-17 version or newer | Stripe Documentation](https://docs.stripe.com/changelog/2014-12-17/creating-accounts-requires-2014-12-17-version): Creating accounts via the API now requires using API version 2014-12-17 or a newer version. This update ensures that users are leveraging the latest features and improvements available in the Accounts API. Developers should upgrade their API version to maintain compatibility and access to new functionalities.
- [Cards now use both the unchecked and unavailable values to describe address and CVC checks by issuing banks | Stripe Documentation](https://docs.stripe.com/changelog/2014-12-22/cards-use-unchecked-unavailable-address-cvc-checks): The Card object now uses 'unchecked' and 'unavailable' values to more accurately describe address and CVC check statuses performed by issuing banks. 'Unchecked' indicates a check that has not been performed, while 'unavailable' means the issuing bank does not support the check. This provides clearer insights into the card verification process.
- [Tokens with cards no longer include the customer field | Stripe Documentation](https://docs.stripe.com/changelog/2014-12-22/tokens-cards-no-longer-include-customer-field): The 'customer' field is no longer included in the Card object when it appears within a Token object. This change simplifies the token structure by removing potentially redundant information. Developers should be aware of this modification when processing card tokens.
- [File uploads describe their file type with the simpler type field and format | Stripe Documentation](https://docs.stripe.com/changelog/2015-01-11/file-uploads-describe-type-format): File uploads now use a simpler 'type' field to describe file types, replacing the 'mimetype' property. This change provides more straightforward file type information, such as 'pdf' instead of 'application/pdf'. This simplifies working with file type data in the File Upload object.
- [Events with the previous_attributes field now only render the differences to objects across updates | Stripe Documentation](https://docs.stripe.com/changelog/2015-01-26/events-previous-attributes-render-differences): The 'previous_attributes' field in events now only displays the differences between object states during updates. Instead of showing the entire previous state of nested hashes, it highlights only the changed attributes. This provides more focused and concise information about changes in event data.
- [Subscriptions now only report the timestamp for API or invoice payment failures for the canceled_at field | Stripe Documentation](https://docs.stripe.com/changelog/2015-01-26/subscriptions-report-api-invoice-failures): The 'canceled_at' field on the Subscription object now exclusively reflects the timestamp of an API call or invoice payment failure that resulted in cancellation. Previously, it also included timestamps for 'at period end' cancellations, which are now handled by the 'ended_at' property. This ensures 'canceled_at' accurately represents the direct cancellation event.
- [Dispute statuses now include the warning_closed value | Stripe Documentation](https://docs.stripe.com/changelog/2015-02-10/dispute-statuses-include-warning-closed): The Dispute object's status property now includes a 'warning_closed' value. This addition provides more granular information about the status of disputes. Developers can now differentiate this specific dispute outcome more precisely.
- [Transfers now require a sufficient account balance in test mode to better simulate live mode | Stripe Documentation](https://docs.stripe.com/changelog/2015-02-10/transfers-require-sufficient-balance-test-mode): Transfers in test mode now require a sufficient available balance, mirroring the behavior of live mode transfers. This change enhances the accuracy of test mode simulations by requiring funds to be present before processing. A special test card number is provided for adding funds to the available test balance.
- [Renames the transfer.canceled event type to transfer.reversed | Stripe Documentation](https://docs.stripe.com/changelog/2015-02-16/renames-transfer-canceled-event-transfer-reversed): The event type 'transfer.canceled' has been renamed to 'transfer.reversed'. This change provides a more accurate description of the event, distinguishing between a simple cancellation and a reversal of a transfer. Developers should update their event handling logic accordingly.
- [Charges that succeed now have a succeeded status | Stripe Documentation](https://docs.stripe.com/changelog/2015-02-18/charges-succeed-have-succeeded-status): Successful charges now have a 'succeeded' status, replacing the previous 'paid' status. This change standardizes the identification of successful charges, making it more consistent for developers. It simplifies the process of determining the outcome of a charge.
- [Charges now have a source field that accepts a source or card | Stripe Documentation](https://docs.stripe.com/changelog/2015-02-18/charges-have-source-field-accepts-source-card): The Charge object now features a 'source' field that accepts either a Source token or a Card token. This replaces the previous 'card' property, offering broader support for different payment methods. Older API versions will continue to return both 'card' and 'source' properties for compatibility.
- [Customers now have a source field that accepts a source or card, and updates related event types | Stripe Documentation](https://docs.stripe.com/changelog/2015-02-18/customers-have-source-field-accepts-source-card): The Customer object now utilizes 'sources' and 'default_source' fields, replacing 'cards' and 'default_card'. These new fields accommodate both Card objects and Source objects with a 'card' value, offering a more flexible payment method representation. Related event types have also been updated to 'customer.source.*'.
- [By default, coupons no longer apply to invoice items with negative amounts | Stripe Documentation](https://docs.stripe.com/changelog/2015-03-24/coupons-no-longer-apply-negative-invoice-items): By default, coupons no longer apply to invoice items with negative amounts. Previously, coupons applied to all non-proration invoice items. To apply a coupon to a negative invoice item, the 'discountable=true' parameter must now be explicitly set.
- [Updates how ending periods are calculated on prorated invoice line items | Stripe Documentation](https://docs.stripe.com/changelog/2015-04-07/updates-ending-periods-prorated-invoice-line-items): The calculation of ending periods for prorated invoice line items has been updated. The 'period[end]' property now reflects the subscription's 'current_period_end' at the time of the update and proration. This provides a more accurate representation of the prorated adjustment interval.
- [Changes the sorting order of lines for invoices | Stripe Documentation](https://docs.stripe.com/changelog/2015-04-07/changes-sorting-order-lines-invoices): The sorting order of lines within the Invoice object has been changed. Invoice items now appear first in reverse chronological order, followed by subscription items if applicable. This update provides a more logical and consistent arrangement of invoice line items.
- [Accounts on manual payout schedules now throw a new error | Stripe Documentation](https://docs.stripe.com/changelog/2015-06-15/accounts-manual-payout-schedules-throw-error): Accounts on manual payout schedules now trigger a new error if the 'payout_schedule[delay_days]' property is provided. Manual payouts inherently use the minimum delay days, making this property redundant and potentially confusing. This change enforces clearer logic for manual payout configurations.
- [Transfers submitted to the bank that haven't arrived now provide an in_transit status | Stripe Documentation](https://docs.stripe.com/changelog/2015-07-07/transfers-in-transit-provide-status): Transfers that have been submitted to the bank but have not yet arrived now display an 'in_transit' status. Previously, both pending and in-transit transfers were categorized as 'pending'. This distinction improves the accuracy of tracking transfer statuses.
- [Accounts now include the verification[disabled_reason] field to describe why they can't make transfers or charges | Stripe Documentation](https://docs.stripe.com/changelog/2015-07-13/accounts-include-verification-disabled-reason-field): The Account object now includes a 'verification[disabled_reason]' field, replacing the 'verification[contacted]' boolean. This new string field provides specific reasons why an account cannot make transfers or charges. This offers more detailed insight into account verification status and limitations.
- [Transfers that are immediately processed now trigger the balance.available event | Stripe Documentation](https://docs.stripe.com/changelog/2015-07-28/transfers-immediately-processed-trigger-balance-available): Immediate transfers now trigger the 'balance.available' event upon processing. This ensures that the balance available for use is updated in real-time when transfers are processed instantly. This improves the accuracy of real-time balance tracking for users.
- [Stripe now ensures the tos_acceptance[date] field on accounts is a valid timestamp | Stripe Documentation](https://docs.stripe.com/changelog/2015-08-07/stripe-ensures-tos-acceptance-date-valid-timestamp): Stripe now validates the tos_acceptance[date] field on accounts to ensure it is a valid timestamp. Accepted values must be after 2009 and before the current moment. This change enhances the accuracy of terms of service acceptance date tracking.
- [Balance transactions with refunds or disputes now specify the corresponding ID in the source field | Stripe Documentation](https://docs.stripe.com/changelog/2015-08-19/balance-transactions-refunds-disputes-specify-source): Balance transactions associated with refunds or disputes now specify the corresponding refund or dispute ID in the source field. Previously, this field showed the original charge ID. This update provides more specific transaction source information.
- [Requests that reuse idempotency tokens but alter request parameters now throw an error | Stripe Documentation](https://docs.stripe.com/changelog/2015-09-03/reuse-idempotency-tokens-alter-error): Stripe now returns an error if an idempotency token is reused with different request parameters than the original request. Previously, errors were only thrown for reusing the same token across different API endpoints. This change prevents unintended duplicate requests.
- [Rate-limited requests now return an HTTP 429 error, no longer including the rate_limit field | Stripe Documentation](https://docs.stripe.com/changelog/2015-09-08/rate-limited-requests-return-429-no-rate-limit): API rate-limited requests now return an HTTP 429 status code instead of 400, and no longer include the rate_limit error code. This change aligns Stripe's rate limiting error reporting with standard practices.
- [The charge field now always reflects the latest charge on invoices | Stripe Documentation](https://docs.stripe.com/changelog/2015-09-23/invoice-charge-field-reflect-latest-charge): The charge field on the Invoice object now consistently displays the invoice's latest charge, regardless of the charge's source. This provides more comprehensive and accurate charge information for invoices.
- [Invoices no longer include the payment property | Stripe Documentation](https://docs.stripe.com/changelog/2015-09-23/invoices-no-longer-include-payment-field): The payment property has been removed from the Invoice object. This property previously indicated a non-card charge. Its removal simplifies the invoice structure.
- [Listing all charges now includes payments from all funding sources | Stripe Documentation](https://docs.stripe.com/changelog/2015-09-23/listing-charges-includes-payments-funding-sources): The list all charges call now includes payments from all funding sources, not just cards. This provides a more comprehensive view of all charges processed.
- [Charges only support an offset for list pagination when filtering by source | Stripe Documentation](https://docs.stripe.com/changelog/2015-09-23/charges-support-offset-list-pagination-source): The deprecated offset parameter for listing charges now only supports pagination when filtering by source type. This change encourages the use of newer, more efficient pagination methods.
- [Bank account information renamed to external accounts on user profiles | Stripe Documentation](https://docs.stripe.com/changelog/2015-10-01/accounts-include-external-accounts-field): The bank_accounts property on the Account object has been replaced with external_accounts. This change broadens the types of accounts that can be managed and provides more versatile account linking.
- [Accounts now include an external_accounts field | Stripe Documentation](https://docs.stripe.com/changelog/2015-10-01/accounts-specify-additional-fields-bank-accounts): The bank_account value in the fields_needed property has been updated to external_account. This change increases versatility in account linking and financial operations.
- [Using invalid parameters to create cards or bank accounts for tokens, sources, or external bank accounts now throws an HTTP 400 error | Stripe Documentation](https://docs.stripe.com/changelog/2015-10-12/invalid-parameters-throw-400-error): Using invalid parameters to create cards, bank accounts for tokens, sources, or external accounts now throws an HTTP 400 error. Previously, a 402 error was returned for missing required parameters. This change allows for quicker identification and correction of errors.
- [Creating or updating customers must now include a plan if a tax percentage is specified | Stripe Documentation](https://docs.stripe.com/changelog/2015-10-16/customers-must-include-plan-tax-percentage): When creating or updating customers, a plan must now be specified if a tax percentage is provided. This change prevents inconsistent tax configurations by ensuring a plan is associated with any tax percentage.
- [Accounts now only show country-specific subfields for the legal_entity field | Stripe Documentation](https://docs.stripe.com/changelog/2016-02-03/accounts-only-show-country-fields-legal-entity): The Account object now only displays sub-properties of the legal_entity field that are applicable to the account's country or were previously provided. This change provides more focused and relevant account information.
- [Renames the name field on Bank Accounts to account_holder_name | Stripe Documentation](https://docs.stripe.com/changelog/2016-02-19/renames-name-field-bank-accounts-account-holder-name): The name property on the Bank Account object has been renamed to account_holder_name. This change provides clearer and more specific terminology for bank account information.
- [You can no longer add more than 250 invoice items to an invoice | Stripe Documentation](https://docs.stripe.com/changelog/2016-02-22/no-more-than-250-invoice-items): A limit of 250 invoice items per invoice has been implemented. Attempts to add more than 250 items will now result in an error. This change helps maintain system performance and data integrity.
- [Orders that are paid or fulfilled, and then become canceled or returned, now automatically refund associated charges | Stripe Documentation](https://docs.stripe.com/changelog/2016-02-23/orders-paid-fulfilled-refund-associated-charges): Orders that are paid or fulfilled and subsequently canceled or returned now automatically trigger a refund of associated charges. Previously, an error occurred if the charge was not manually refunded. This streamlines order management.
- [Creating or updating an account now validates the postal code for its legal entity | Stripe Documentation](https://docs.stripe.com/changelog/2016-02-29/creating-updating-account-validates-postal-code): Postal code validation has been added for legal entity addresses when creating or updating accounts. This enhances data accuracy by ensuring valid postal codes are provided.
- [Supported currencies are defined on the country spec for an account's country | Stripe Documentation](https://docs.stripe.com/changelog/2016-03-07/supported-currencies-defined-country-spec): The currencies_supported property has been removed from the Account object. Supported currency information is now available by retrieving the Country Spec object for the account's country. This simplifies the Account object.
- [Deactivating a product no longer automatically deactivates its SKUs | Stripe Documentation](https://docs.stripe.com/changelog/2016-06-15/deactivating-product-deactivates-skus): Deactivating a product no longer automatically deactivates its associated SKUs. This change provides more granular control over product and SKU management.
- [Filter lists of subscriptions for canceled subscriptions | Stripe Documentation](https://docs.stripe.com/changelog/2016-07-06/filter-canceled-subscriptions-retrieve-individually): The list all subscriptions call now includes canceled subscriptions and supports filtering by status=canceled. This provides more comprehensive subscription management capabilities.
- [Using insufficient permissions to make API requests now throws an HTTP 403 error | Stripe Documentation](https://docs.stripe.com/changelog/2016-10-19/insufficient-permissions-throw-403-error): API requests made with insufficient permissions now return an HTTP 403 error, a change from the previous 401 status code. This update provides more accurate error reporting for permission-related issues.
- [Balance transactions no longer include the sourced_transfers field | Stripe Documentation](https://docs.stripe.com/changelog/2017-01-27/balance-transactions-no-longer-include-sourced-transfers): The `sourced_transfers` field is removed from the Balance Transaction object. This change simplifies the object by removing direct access to this specific information.
- [Charges now specify the ID for the rule blocking a transaction, which can be expanded | Stripe Documentation](https://docs.stripe.com/changelog/2017-02-14/charges-specify-rule-blocking-transaction): The `outcome[rule]` property on the Charge object now contains the ID of the blocking rule instead of the entire Rule object. This change supports expandable fields for more streamlined data retrieval.
- [Charges now specify the ID for the dispute associated with a transaction, which can be expanded | Stripe Documentation](https://docs.stripe.com/changelog/2017-02-14/charges-specify-dispute-associated-transaction): The `dispute` property on the Charge object now contains the ID of an associated dispute rather than the full Dispute object. This change simplifies the object and allows for expandable fields to retrieve full dispute details.
- [Transfers are now split into payouts and transfers | Stripe Documentation](https://docs.stripe.com/changelog/2017-04-06/transfers-split-payouts-transfers): The Transfer object is split into two distinct objects: Payout and Transfer. The Payout object handles money moving to external accounts, while the Transfer object now exclusively represents money moving between Stripe accounts on a Connect platform.
- [Events for Connect now specify the originating connected account using the account field | Stripe Documentation](https://docs.stripe.com/changelog/2017-05-25/events-connect-specify-originating-account): Connect-related event objects now use the `account` field to specify the originating connected account, replacing the previous `user_id` property. This change provides clearer terminology for identifying associated Stripe accounts in Connect events.
- [The request field of the Events object now specifies both the request ID and idempotency key | Stripe Documentation](https://docs.stripe.com/changelog/2017-05-25/events-specify-request-id-idempotency-key): The `request` property on the Event object is updated to be a hash containing both the request ID and the idempotency key. Previously, it only contained the request ID, providing more detailed information about the API request that triggered the event.
- [Events with the previous_attributes field now render the complete affected sub-array | Stripe Documentation](https://docs.stripe.com/changelog/2017-05-25/events-previous-attributes-render-complete-sub-array): The `previous_attributes` property on Event objects now displays entire sub-arrays when changes occur, rather than just the specific fields that changed. This provides more comprehensive information about modifications within sub-arrays.
- [Accounts must now specify one of three types (Standard, Express, or Custom) | Stripe Documentation](https://docs.stripe.com/changelog/2017-05-25/accounts-specify-type-standard-express-custom): Account objects now require a `type` field, with possible values being standard, express, or custom, replacing the previous `managed` boolean property. This allows for more specific classification and creation of accounts.
- [Accounts can now specify why an account isn't enabled with the new reason under_review | Stripe Documentation](https://docs.stripe.com/changelog/2017-06-05/accounts-specify-under-review-reason): The Account object's `verification[disabled_reason]` field now includes `under_review` as a possible value, replacing the generic `other` value. This provides a more specific status when an account is pending review.
- [Sources can now specify that an authentication redirect isn't required | Stripe Documentation](https://docs.stripe.com/changelog/2017-08-15/sources-specify-no-authentication-redirect-required): The Source object's `redirect[status]` property now includes `not_required` as a possible value, differentiating it from the previous `succeeded` status for optional redirects. This offers clearer information about the requirement for authentication redirects.
- [Invoice line items now must always set a description | Stripe Documentation](https://docs.stripe.com/changelog/2017-12-14/invoice-line-items-must-set-description): Invoice line items, including those generated from subscription items, must now always have a description set. This change ensures consistent and informative details for all invoice line items.
- [Invoice payment failures now return a card_error when a charge is declined | Stripe Documentation](https://docs.stripe.com/changelog/2017-12-14/invoice-payment-failures-return-card-error): Invoice payment attempts now return a `card_error` when a charge is declined, aligning this behavior with direct charge error handling. This change ensures consistent error responses across payment endpoints.
- [Connect platforms can identify reused card or bank accounts across connected accounts as they now will share the same fingerprint | Stripe Documentation](https://docs.stripe.com/changelog/2018-01-23/connect-platforms-identify-reused-cards-bank-accounts): For Connect platforms, cards and bank accounts created on behalf of connected accounts now share a universal fingerprint across all connected accounts. This allows platforms to more easily identify and track unique payment methods.
- [Free plans with prorations now produce zero-dollar invoices | Stripe Documentation](https://docs.stripe.com/changelog/2018-02-05/free-plans-with-prorations-produce-zero-dollar-invoices): Prorations on free plans now generate zero-dollar invoices, whereas previously no invoices were created. This change ensures a complete record of all plan changes, providing better consistency in billing history.
- [Subscriptions can now delay the first full invoice to a future date (and optionally include a free trial) | Stripe Documentation](https://docs.stripe.com/changelog/2018-02-05/subscriptions-delay-first-full-invoice-future-date): Subscriptions can now delay their first full invoice to a future date using `billing_cycle_anchor`, with the option to include prorations and a free trial. This enables more flexible subscription management by combining trials, prorated periods, and fixed billing cycles.
- [Plans now link to individual products, with several fields moving to the product resource | Stripe Documentation](https://docs.stripe.com/changelog/2018-02-05/plans-link-individual-products-several-fields-moved): Plan objects now link to individual Product objects, with `statement_descriptor` and `name` attributes moved to the Product resource and a `nickname` attribute added to plans. Creating a plan now requires specifying a product.
- [Products now require a type field, differentiating their use with order SKUs or subscriptions and plans | Stripe Documentation](https://docs.stripe.com/changelog/2018-02-05/products-require-type-field-differentiating-use): Product objects now require a `type` field, specifying either `good` for order SKUs or `service` for subscriptions and plans. This change allows for more accurate categorization of products.
- [Sources now provide a recommended value when the issuer advises using 3D Secure | Stripe Documentation](https://docs.stripe.com/changelog/2018-02-06/sources-provide-recommended-use-3d-secure): The Source object's `card[three_d_secure]` property now includes `recommended` as a possible value, in addition to `not_supported`, `optional`, and `required`. This provides more nuanced information when 3D Secure is advised but not mandatory.
- [Updating a canceled subscription on a future date no longer resets its status | Stripe Documentation](https://docs.stripe.com/changelog/2018-02-28/updating-canceled-subscription-no-longer-resets-status): Updating a subscription that is set to cancel on a future date no longer clears its cancellation status. To remove a planned cancellation, `cancel_at_period_end=false` must now be explicitly specified during the update.
- [Products no longer embed lists of SKUs | Stripe Documentation](https://docs.stripe.com/changelog/2018-05-21/products-no-longer-embed-sku-lists): Products no longer embed lists of SKUs, simplifying the product data structure by removing embedded SKU lists from Product objects. This change impacts how product data is managed and may require updates to integrations relying on the previous structure.
- [Invoice line items now have unique IDs and can't be used in place of a subscription | Stripe Documentation](https://docs.stripe.com/changelog/2018-05-21/invoice-line-items-have-unique-ids-cannot-use-subscription): Invoice line items now have unique IDs and cannot be used in place of a subscription. The 'id' field for subscription-type line items is now a unique identifier for the line item itself, not the subscription, and can be used for pagination.
- [Coupons, SKUs, customers, products, and plans now limit the valid characters for IDs | Stripe Documentation](https://docs.stripe.com/changelog/2018-05-21/valid-characters-ids-coupons-skus-customers-products-plans): Coupon, SKU, customer, product, and plan IDs are now restricted to alphanumeric characters, underscores, and hyphens upon creation. This change ensures a consistent and predictable format for these identifiers, requiring updates to any systems that create these IDs.
- [Subscriptions now default to not defining their trial periods depending on a plan | Stripe Documentation](https://docs.stripe.com/changelog/2018-05-21/subscriptions-default-no-trial-period-plan): Subscriptions now default to not defining trial periods based on a plan. The 'trial_from_plan' parameter defaults to false, meaning subscriptions no longer automatically inherit trial periods from their associated plans. Explicitly setting trial periods per subscription is recommended.
- [Changing a subscription to a new plan with a trial now extends the trial period | Stripe Documentation](https://docs.stripe.com/changelog/2018-05-21/changing-subscription-new-plan-extends-trial): When changing a subscription to a new plan with a trial, the new plan's full trial period is now added to the subscription. This change extends the trial period without subtracting time from previous trials, offering more flexibility in managing subscription trials.
- [Subscriptions no longer support modifying the source parameter directly | Stripe Documentation](https://docs.stripe.com/changelog/2018-07-27/subscriptions-no-longer-support-modifying-source): Subscription endpoints no longer support the 'source' parameter for direct modification. To change a customer's default payment source, you must now use the Source Creation API followed by the Customer Update API to set the new default.
- [Ending a subscription trial now uses the timestamp of that API request | Stripe Documentation](https://docs.stripe.com/changelog/2018-07-27/ending-subscription-trial-uses-request-timestamp): Ending a subscription trial using 'trial_end=now' now sets the 'trial_end' timestamp to the time of the API request. This provides a precise record of when the trial ended, improving accuracy in subscription management but may require code adjustments.
- [Coupons now use floats rather than integers to specify percent_off | Stripe Documentation](https://docs.stripe.com/changelog/2018-07-27/coupons-use-floats-specify-percent-off): Coupons now use floating-point numbers instead of integers for the 'percent_off' field, allowing for more precise discount percentages. The deprecated 'percent_off_precise' field is replaced by 'percent_off', enabling discounts with fractional percentages like 10.50%.
- [Stripe now validates email addresses when creating or updating customers | Stripe Documentation](https://docs.stripe.com/changelog/2018-07-27/stripe-validates-email-addresses-customers): Stripe now validates email addresses when creating or updating customers, ensuring they have a valid format. This change improves data quality and reduces errors in customer communications by enforcing proper email structure.
- [A subscription's ending period can no longer be configured while canceling it | Stripe Documentation](https://docs.stripe.com/changelog/2018-08-23/subscription-ending-period-cannot-configured-canceling): A subscription's ending period can no longer be configured directly within the cancelation endpoint. Use the 'cancel_at_period_end' field on the subscription update endpoints instead of the 'at_period_end' parameter in the DELETE endpoint.
- [Customers now provide a tax_info object with their tax ID details | Stripe Documentation](https://docs.stripe.com/changelog/2018-08-23/customers-provide-tax-info-object): Customers now provide tax ID details within a 'tax_info' object, which includes 'tax_id' and 'type'. This change restructures customer tax information from a simple string to a more detailed hash, requiring updates to how tax data is managed.
- [Renames the amount field for plan tiers to unit_amount | Stripe Documentation](https://docs.stripe.com/changelog/2018-08-23/renames-amount-field-plan-tiers-unit-amount): The 'amount' field for plan tiers is now renamed to 'unit_amount'. This change provides clearer terminology for tiered pricing, ensuring that developers reference the correct field when configuring plans with multiple tiers.
- [SKU values no longer need to be unique | Stripe Documentation](https://docs.stripe.com/changelog/2018-09-06/sku-values-no-longer-need-unique): SKU attribute values no longer need to be unique when creating or updating SKUs. This allows for the creation of multiple SKUs with identical attributes or no attributes, providing greater flexibility in product management.
- [Renames the FileUpload object to Files, which now require secret keys to download files | Stripe Documentation](https://docs.stripe.com/changelog/2018-09-24/file-uploads-renamed-files-require-secret-keys): The FileUpload object is renamed to File, and its 'url' attribute now provides an authenticated URL requiring a secret API key for downloads. Publicly accessible URLs can be obtained by creating a file link, enhancing file security and management.
- [Descriptions for customers now have a character limit | Stripe Documentation](https://docs.stripe.com/changelog/2018-10-31/descriptions-customers-character-limit): Descriptions for customers now have a maximum character limit of 350. This change requires that customer descriptions be concise and within the specified limit, potentially necessitating revisions to longer existing descriptions.
- [Product names now have a character limit | Stripe Documentation](https://docs.stripe.com/changelog/2018-10-31/names-products-character-limit): Product names now have a maximum character limit of 250. This update requires product names to be concise and adhere to the new limit, which may involve shortening or restructuring existing product names.
- [Descriptions for invoice line items now have a character limit | Stripe Documentation](https://docs.stripe.com/changelog/2018-10-31/descriptions-invoice-line-items-character-limit): Descriptions for invoice line items now have a maximum character limit of 500. This change requires that line item descriptions be concise and within the specified limit, potentially necessitating revisions to longer existing descriptions.
- [The billing_reason of the first invoice of a subscription is now subscription_create | Stripe Documentation](https://docs.stripe.com/changelog/2018-10-31/first-invoice-subscription-billing-reason-subscription-create): The 'billing_reason' for the first invoice of a subscription is now 'subscription_create'. This new value distinguishes initial subscription invoices from regular updates, enabling more precise tracking of subscription lifecycles.
- [Invoices now specify their automatic collection behavior using the auto_advance field | Stripe Documentation](https://docs.stripe.com/changelog/2018-11-08/invoices-specify-auto-advance-field): Invoices now specify automatic collection behavior using the 'auto_advance' field, deprecating the 'closed' property. Setting 'auto_advance' to false prevents automatic collection, offering more specific control over the invoice lifecycle.
- [One-off Invoices no longer automatically collect payment by default | Stripe Documentation](https://docs.stripe.com/changelog/2018-11-08/one-off-invoices-no-longer-auto-collect-payment): One-off invoices now default to not automatically collecting payment, with 'auto_advance' defaulting to false. This change gives users more control over how long these invoices remain in draft status before payment is processed.
- [Replaces the forgiven field with a new uncollectible status for invoices | Stripe Documentation](https://docs.stripe.com/changelog/2018-11-08/mark-invoice-uncollectible-instead-forgiven): Stripe has replaced the 'forgiven' field for invoices with a new 'uncollectible' status. Developers should now check for the uncollectible status to identify invoices marked as uncollectible, requiring updates to existing code that processes invoice statuses.
- [Renames an invoice error code to invoice_already_finalized | Stripe Documentation](https://docs.stripe.com/changelog/2018-11-08/renames-invoice-error-code-invoice-already-finalized): The invoice error code 'immutable_frozen_invoice' has been renamed to 'invoice_already_finalized'. This change affects error handling code that specifically checks for the old error code when attempting to modify a finalized invoice.
- [Includes several changes for users of the Payment Intents API private beta  | Stripe Documentation](https://docs.stripe.com/changelog/2018-11-08/several-changes-payment-intents-private-beta): Several changes have been implemented for users of the Payment Intents API private beta, affecting the 'next_source_action' dictionary, 'attempt_confirmation' parameter, and 'return_url' usage. These updates require significant modifications to existing code that interacts with PaymentIntents, impacting payment flow and data processing.
- [Renames several statuses for PaymentIntents | Stripe Documentation](https://docs.stripe.com/changelog/2019-02-11/renames-several-statuses-payment-intents): Several PaymentIntent statuses have been renamed for clarity and consistency. 'requires_source' is now 'requires_payment_method', and 'requires_source_action' is now 'requires_action'. Developers must update their code to use these new status names when processing PaymentIntents.
- [Renames the save_source_to_customer field for sources to save_payment_method | Stripe Documentation](https://docs.stripe.com/changelog/2019-02-11/renames-save-source-to-customer-save-payment-method): The 'save_source_to_customer' field for sources has been renamed to 'save_payment_method'. This change updates the parameter name to provide more generalized terminology for saving payment methods to a customer, requiring code adjustments to reflect the new name.
- [Renames the allowed_source_types field for sources to payment_method_types | Stripe Documentation](https://docs.stripe.com/changelog/2019-02-11/renames-allowed-source-types-payment-method-types): The 'allowed_source_types' field for sources has been renamed to 'payment_method_types'. This modification aligns the terminology with the broader concept of payment methods, requiring developers to update their code to use the new parameter name when specifying acceptable payment methods.
- [Renames the next_source_action field for Payment Intents to next_action | Stripe Documentation](https://docs.stripe.com/changelog/2019-02-11/renames-next-source-action-next-action): The 'next_source_action' property on the PaymentIntent has been renamed to 'next_action'. This change provides more generalized terminology for handling additional actions required for payment processing, requiring code updates to reference the new property name.
- [Renames the authorize_with_url field for Payment Intents to redirect_to_url | Stripe Documentation](https://docs.stripe.com/changelog/2019-02-11/renames-authorize-with-url-redirect-to-url): The 'authorize_with_url' property on the PaymentIntent has been renamed to 'redirect_to_url'. This update provides more generalized terminology for handling URL-based authorization steps in the payment process, requiring code adjustments to use the new property name.
- [Changes statement descriptor behaviors for card payments created with Charges | Stripe Documentation](https://docs.stripe.com/changelog/2019-02-19/changes-statement-descriptor-behaviors-charges): Statement descriptor behaviors for card payments created with Charges have changed. Charges using 'on_behalf_of' or 'destination' now use the connected account's descriptor, and dynamic descriptors are prefixed. Statement descriptors also have new character restrictions.
- [Several account fields have been refactored to better describe legal entity, verification status and requirements, and configurable settings | Stripe Documentation](https://docs.stripe.com/changelog/2019-02-19/several-fields-accounts-refactored): Multiple fields within the Account API resource have been refactored for better organization and clarity. Key changes include restructuring 'legal_entity' and 'verification' properties, moving various configuration settings into subhashes like 'settings' and 'business_profile', and updating naming conventions.
- [Several fields describing an account's business details have moved to the business_profile subhash | Stripe Documentation](https://docs.stripe.com/changelog/2019-02-19/business-details-moved-business-profile-object): Several fields related to an account's business details have been moved into a new 'business_profile' subhash. Fields such as 'business_name', 'business_url', and 'product_description' are now accessed and updated under this new structure, requiring code modifications.
- [Verification of accounts or persons now supports uploading both front and back sides | Stripe Documentation](https://docs.stripe.com/changelog/2019-02-19/verification-accounts-persons-supports-front-back): Verification for accounts and persons now supports uploading both the front and back sides of documents. The 'legal_entity[verification][document]' property has been updated to a hash structure, and new error types have been added to provide more detailed feedback on verification failures.
- [Accounts no longer provide a keys field. Platforms should use their own API key to authenticate as their connected accounts | Stripe Documentation](https://docs.stripe.com/changelog/2019-02-19/accounts-no-longer-provide-keys-field): Accounts no longer provide a 'keys' field for creation. Platforms must now use their own API key and the 'Stripe-Account' header to authenticate when acting on behalf of connected accounts. This change impacts how platforms manage authentication for their connected accounts.
- [Accounts in the US now require specifying capabilities at creation time | Stripe Documentation](https://docs.stripe.com/changelog/2019-02-19/accounts-us-require-specifying-capabilities-creation): Accounts in the U.S. now require the 'requested_capabilities' property to be specified at creation time. This change provides more control over account functionalities by mandating the explicit declaration of desired capabilities for new U.S. accounts.
- [Renames the business_id_number for an account's legal entity to business_registration_number | Stripe Documentation](https://docs.stripe.com/changelog/2019-02-19/renames-business-id-number-business-registration-number): The 'legal_entity[business_id_number]' field for an account's legal entity has been renamed to 'legal_entity[business_registration_number]'. This change provides clearer terminology for business registration information and requires updates to code that accesses or provides this data.
- [Renames application_fee on invoices to application_fee_amount | Stripe Documentation](https://docs.stripe.com/changelog/2019-03-14/renames-application-fee-invoices-application-fee-amount): The 'application_fee' parameter on Invoice API methods and the 'application_fee' field on the Invoice object have been renamed to 'application_fee_amount'. This modification clarifies that the value represents an amount, not a fee object, and requires code updates to use the new name.
- [Subscriptions are now successfully created even if the first payment fails | Stripe Documentation](https://docs.stripe.com/changelog/2019-03-14/subscriptions-successfully-created-first-payment-fails): Subscriptions can now be successfully created even if the first payment fails. The subscription enters an 'incomplete' status for up to 23 hours, allowing time to resolve payment issues before it becomes 'incomplete_expired'. This change improves the subscription lifecycle management.
- [Invoices now provide timestamps for each state transition | Stripe Documentation](https://docs.stripe.com/changelog/2019-03-14/invoices-provide-timestamps-state-transitions): Invoices now include a 'status_transitions' hash containing timestamps for key state changes such as finalization, payment, being marked uncollectible, or voided. This provides precise timing information for these important invoice events.
- [Renames the date field for invoices to created | Stripe Documentation](https://docs.stripe.com/changelog/2019-03-14/renames-date-field-invoices-created): The 'date' property for invoices has been renamed to 'created'. This change aligns the invoice property naming with other objects in the API, requiring developers to update their code to reference 'created' instead of 'date' when accessing the invoice creation timestamp.
- [Invoices now specify when they're finalized alongside other status transitions | Stripe Documentation](https://docs.stripe.com/changelog/2019-03-14/invoices-specify-finalized-alongside-status-transitions): The 'finalized_at' property for invoices has been moved into the new 'status_transitions' hash. Developers must now access the finalization timestamp through 'status_transitions.finalized_at', organizing invoice status change information more coherently.
- [Bank pull payments no longer expose internal system refunds on failure | Stripe Documentation](https://docs.stripe.com/changelog/2019-05-16/renames-platform-payments-capability-card-payments): Bank pull payments no longer expose internal system refunds directly in the payment interface when they fail. These refunds are still accessible via the List refunds endpoint, ensuring data integrity while simplifying the main payment view.
- [Renames the platform_payments capability for accounts to card_payments, requiring the manual specification of the added transfers capability | Stripe Documentation](https://docs.stripe.com/changelog/2019-08-14/configuring-person-account-opener-no-longer-sets-executive): The platform_payments capability for accounts is renamed to card_payments, and it no longer implies transfers. When creating an account, you must now manually specify the transfers capability separately for clearer control over account features.
- [Configuring a person as an account opener no longer automatically sets them as an executive | Stripe Documentation](https://docs.stripe.com/changelog/2019-08-14/accounts-many-countries-require-specifying-capabilities): Configuring a person as an account opener no longer automatically designates them as an executive. You must now explicitly set the relationship[executive] attribute to true if required by the account's specific needs.
- [Accounts in many countries now require specifying capabilities at creation time | Stripe Documentation](https://docs.stripe.com/changelog/2019-09-09/2019-09-09-1): Accounts in numerous countries, including Australia, New Zealand, and many European nations, now require the explicit specification of requested capabilities at the time of creation. This ensures that all necessary account features are defined upfront.
- [Adds new details_code values to person document verification | Stripe Documentation](https://docs.stripe.com/changelog/2019-09-09/adds-detail-code-person-document-verification): New details_code values are added to the person document verification process. This enhancement provides more granular information regarding the verification status of a person's submitted documents.
- [Renames a Person object relationship attribute | Stripe Documentation](https://docs.stripe.com/changelog/2019-10-08/renames-person-object-relationship-attribute): The relationship attribute 'account_opener' on a Person object is renamed to 'representative'. This change offers more accurate and intuitive terminology for identifying the individual representing an account.
- [Renames and updates subscription schedule renewal properties | Stripe Documentation](https://docs.stripe.com/changelog/2019-10-17/updates-subscription-renewal-properties): Subscription schedule renewal properties are updated and renamed for clarity. renewal_behavior is now end_behavior, and renewal_interval is removed, providing a more intuitive way to manage how subscription schedules conclude.
- [Replaces the subscription start field with start_date | Stripe Documentation](https://docs.stripe.com/changelog/2019-10-17/replaces-subscription-start-field): The subscription start field is replaced by start_date. This new field accurately reflects the original start date of the entire subscription, regardless of subsequent plan changes.
- [Renames billing to collection_method on invoices, subscriptions, and subscription schedules | Stripe Documentation](https://docs.stripe.com/changelog/2019-10-17/renames-billing-attribute): The billing attribute on invoices, subscriptions, and subscription schedules is renamed to collection_method. This change provides clearer terminology, specifying how payments are collected rather than just the billing process.
- [The due_date property is always null on auto-billed invoices | Stripe Documentation](https://docs.stripe.com/changelog/2019-10-17/invoice-due-date-null): The due_date property is now consistently null for invoices with the 'charge_automatically' billing setting. This clarifies the behavior for auto-billed invoices, allowing for predictable data handling.
- [Renames account_balance to balance on Customer object | Stripe Documentation](https://docs.stripe.com/changelog/2019-10-17/renames-account-balance-customer-object): The Customer object's account_balance property is renamed to balance. A new Customer Balance Transactions API is introduced, allowing direct updates to a customer's balance and providing a history of these changes.
- [Adds requirement for requested_capabilities on custom account creation | Stripe Documentation](https://docs.stripe.com/changelog/2019-11-05/adds-requested-capabilities-requirement-custom-account): The requested_capabilities property is now a mandatory requirement when creating custom accounts in all countries. This ensures that all necessary capabilities are explicitly defined during the account creation process.
- [Nested subscription schedule settings under default_settings | Stripe Documentation](https://docs.stripe.com/changelog/2019-11-05/nests-subscription-schedule-settings): Subscription schedule settings, including invoice_settings, default_payment_method, billing_thresholds, and collection_method, are now nested under a new default_settings field. This change organizes and simplifies the management of subscription schedule configurations.
- [Standardizes invoice line item IDs | Stripe Documentation](https://docs.stripe.com/changelog/2019-12-03/standardizes-invoice-line-item-ids): Invoice line item IDs are standardized with a new 'il_' prefix, making them globally unique and suitable for pagination. The 'type' field should now be used to determine the line item's source, and 'invoice_item' references originating Invoice Item objects.
- [New requirement for out_of_band_amount when creating post-payment credit notes | Stripe Documentation](https://docs.stripe.com/changelog/2019-12-03/post-payment-credit-note-requirement): When creating post-payment credit notes, the out_of_band_amount is now required if the sum of credit_amount and refund is less than the credit note total. This change enforces more explicit definition of credit note components.
- [Customer balances are now returned when voiding invoices | Stripe Documentation](https://docs.stripe.com/changelog/2019-12-03/customer-balances-returned-voided-invoices): Customer balances applied to invoices are now automatically debited or credited back to the customer when the invoice is voided. Previously, these balances were consumed and not returned.
- [Removes deprecated tax information fields from the Customer object | Stripe Documentation](https://docs.stripe.com/changelog/2019-12-03/removes-deprecated-tax-information-fields): Deprecated tax information fields (tax_info, tax_info_verification) and parameters (tax_info) on the Customer object and related methods are removed. These are replaced by the more streamlined tax_ids field and associated parameters.
- [Invoices can now be numbered sequentially across your account | Stripe Documentation](https://docs.stripe.com/changelog/2020-03-02/sequentially-number-invoices): Invoices can now be optionally numbered sequentially across the entire account, rather than just for each customer. This feature can be enabled in the Stripe Dashboard for more flexible invoice management.
- [Removes the tax_percent attribute | Stripe Documentation](https://docs.stripe.com/changelog/2020-08-27/removes-tax-percent-attribute): The tax_percent attribute is removed from objects and requests. Taxation is now managed through the dedicated Tax Rates API, offering more flexible and precise tax handling.
- [Customer sources are no longer auto-expanded by default   | Stripe Documentation](https://docs.stripe.com/changelog/2020-08-27/deprecates-auto-expansion-customer-sources): The sources property on Customer objects is no longer auto-expanded by default. This change improves performance, and sources can still be expanded manually when needed.
- [Tax IDs are no longer auto-expanded on the Customer object | Stripe Documentation](https://docs.stripe.com/changelog/2020-08-27/deprecates-auto-expansion-tax-id-customer): Stripe has deprecated the auto-expansion of the tax_ids attribute on the Customer object. This change aims to optimize performance by not including tax IDs by default. Developers can still expand this list if needed, but it is not recommended for performance reasons.
- [Deprecates subscription prorate and subscription_prorate parameters | Stripe Documentation](https://docs.stripe.com/changelog/2020-08-27/deprecates-prorate-parameters-subscriptions): Stripe deprecates the prorate and subscription_prorate parameters for subscriptions. These are replaced by the more comprehensive proration_behavior parameter, allowing for more precise configuration of how prorating is handled. Developers should update their integrations to use the new parameter.
- [Renames phases attributes in subscription schedules | Stripe Documentation](https://docs.stripe.com/changelog/2020-08-27/renames-phases-attributes-subscription-schedules): Stripe renames the phases.plans attribute to phases.items in subscription schedules. This change aligns the terminology with the broader concept of subscription items, improving clarity and management of subscription schedule components. The renaming applies to the subscription schedule object and its create/update requests.
- [Renames event type that triggers on automatic updates | Stripe Documentation](https://docs.stripe.com/changelog/2020-08-27/renames-automatically-updated-event-type): Stripe renames the payment_method.card_automatically_updated event type to payment_method.automatically_updated. This broader event type now applies to any payment method that has been automatically updated, offering a more generic and flexible way to handle these events. Developers should update their webhook handlers accordingly.
- [Removes the display_items property from Checkout Sessions | Stripe Documentation](https://docs.stripe.com/changelog/2020-08-27/removes-display-items-checkout-session): The display_items property is removed from Checkout Sessions, and developers should now use the includable line_items property instead. This change simplifies the Checkout Session response by consolidating line item information into a single, consistent property. This update helps streamline the access to line item details.
- [Formats requirements for key persons associated with accounts | Stripe Documentation](https://docs.stripe.com/changelog/2020-08-27/formats-requirements-key-persons-accounts): Stripe updates the formatting of requirements for key persons associated with accounts. Strings related to key persons in the requirements and verification_fields hashes are now prefixed with their role (e.g., representative., owners., directors., executives.). This change provides a more intuitive naming convention for identifying and addressing specific information needed for each person role.
- [Adds new error codes to the Accounts, Persons, and Capabilities APIs | Stripe Documentation](https://docs.stripe.com/changelog/2020-08-27/adds-error-codes-accounts-persons-capabilities): The Accounts, Persons, and Capabilities APIs now include several new error codes. These codes, such as verification_document_issue_or_expiry_date_missing and verification_failed_tax_id_not_issued, allow for more precise identification of verification failures. Developers can use these codes to better diagnose and resolve account verification issues.
- [Updates to 3D Secure details in Charge object | Stripe Documentation](https://docs.stripe.com/changelog/2020-08-27/updates-3d-scure-charge-object): Stripe updates the 3D Secure details in the Charge object by replacing the succeeded and authenticated booleans with a new result enum. This change provides a more granular and accurate way to determine the 3D Secure status of a payment. Developers should use the new result enum for better insight into the authentication process.
- [Customer subscriptions are no longer auto-expanded by default | Stripe Documentation](https://docs.stripe.com/changelog/2020-08-27/deprecates-auto-expansion-customer-subscriptions): The subscriptions property on Customers is no longer automatically expanded by default in Stripe's API. This change is intended to optimize performance by reducing the data transferred when retrieving customer objects. Developers can still expand the subscriptions list if necessary, but it is recommended against for performance reasons.
- [Plan tiers are no longer auto-expanded by default   | Stripe Documentation](https://docs.stripe.com/changelog/2020-08-27/deprecates-auto-expansion-plan-tiers): The tiers property on Plan objects is no longer auto-expanded by default in Stripe's API. This change optimizes performance by excluding tier information unless explicitly requested. Developers can still retrieve plan tiers by listing them, but this is not recommended for performance reasons.
- [Removes the include_and_require value when creating invoices | Stripe Documentation](https://docs.stripe.com/changelog/2022-08-01/removes-include-require-value-invoices): Stripe removes the include_and_require value for the pending_invoice_items_behavior parameter when creating invoices. The default behavior is now exclude, giving users more control over managing pending invoice items. This change provides greater flexibility in invoice creation processes.
- [New error code for invalid terms of service acceptance in Accounts API | Stripe Documentation](https://docs.stripe.com/changelog/2022-08-01/error-code-invalid-tos-accounts): The Accounts API now includes invalid_tos_acceptance as a new error code within the requirements.errors array. This provides more specific error reporting for issues related to terms of service acceptance. Developers can use this code to better diagnose and resolve account setup problems.
- [New endpoints for managing a physical card's shipping status in test mode | Stripe Documentation](https://docs.stripe.com/changelog/2022-08-01/endpoints-shipping-status-cards): New endpoints are introduced for managing the shipping status of physical cards in test mode. The endpoints /v1/test_helpers/issuing/cards/:card/shipping/ship, /deliver, /return, and /fail allow developers to simulate various shipping scenarios for testing purposes. This provides more control over testing card issuance workflows.
- [Adds design_rejected as a possible cancellation reason for issued cards | Stripe Documentation](https://docs.stripe.com/changelog/2022-08-01/adds-design-rejected-value-cards): Stripe adds 'design_rejected' as a possible cancellation reason for issued cards. This new value indicates that the card's design was rejected by Stripe. This provides clearer information when a card is cancelled due to design issues.
- [Removes the default_currency attribute from the Customer object | Stripe Documentation](https://docs.stripe.com/changelog/2022-08-01/removes-default-currency-customer-object): The default_currency attribute is removed from the Customer object in Stripe's API. This change simplifies the Customer object and streamlines currency handling within the API. Developers should adjust their integrations to manage currency information accordingly.
- [Default customer creation in Checkout Session payment mode changed to if_required | Stripe Documentation](https://docs.stripe.com/changelog/2022-08-01/default-customer-creation-checkout-session): The default behavior for customer creation in Stripe Checkout Session's payment mode has changed from 'always' to 'if_required'. This change allows for more flexible customer handling, as a customer is now only created if it is necessary, reducing the creation of unnecessary customer records. This provides greater control over the checkout process.
- [Deferred PaymentIntent creation in Checkout Session payment mode | Stripe Documentation](https://docs.stripe.com/changelog/2022-08-01/deferred-paymentintent-checkout-session): Stripe introduces deferred PaymentIntent creation for Checkout Session payment mode. A PaymentIntent is now created only when the Checkout Session is confirmed, rather than during the initial session creation. This provides greater flexibility and control over the payment flow.
- [Removes the setup_intent property from Checkout Sessions in subscription mode   | Stripe Documentation](https://docs.stripe.com/changelog/2022-08-01/removes-setupintent-checkout-session): The setup_intent property is removed from Checkout Sessions when in subscription mode. This change simplifies the Checkout Session response by removing unnecessary SetupIntent details. Developers can now focus on the core subscription information.
- [Replaces line item parameters from the Create Checkout Session endpoint | Stripe Documentation](https://docs.stripe.com/changelog/2022-08-01/replaces-line-item-create-checkout-session): Stripe replaces the individual line item parameters (amount, currency, name, description, images) in the Create Checkout Session endpoint with the price and price_data parameters. This change simplifies the process of defining line items for Checkout Sessions. Developers should use the new parameters for specifying line item details.
- [Removes the subscription data parameter from the Create Checkout Session endpoint | Stripe Documentation](https://docs.stripe.com/changelog/2022-08-01/removes-subscription-data-create-checkout-session): The subscription_data[coupon] parameter is removed from the Create Checkout Session endpoint, and the discounts parameter should be used instead. This change provides a more generic way to handle discounts for Checkout Sessions, moving away from a coupon-specific approach. Developers should update their integrations to use the discounts parameter for applying discounts.
- [Removes the shipping rate parameter from Create Checkout Session endpoint | Stripe Documentation](https://docs.stripe.com/changelog/2022-08-01/removes-shipping-rate-create-checkout-session): Stripe's Create Checkout Session endpoint no longer accepts the shipping_rates parameter. Developers should now use the shipping_options parameter instead to specify shipping preferences. This change consolidates shipping option specification for a simpler Checkout Session creation process.
- [Updates Checkout Session shipping properties  | Stripe Documentation](https://docs.stripe.com/changelog/2022-08-01/updates-shipping-property-checkout-session): Stripe has updated several shipping properties within the Checkout Session resource. The shipping_rate is now located within a new shipping_cost hash, and the shipping property has been renamed to shipping_details. This change allows for more granular access and management of shipping-related information.
- [Adds 3D Secure exemption status to card charges | Stripe Documentation](https://docs.stripe.com/changelog/2022-08-01/adds-3d-secure-exemption-charges): The three_d_secure hash for card charges now includes an 'exempted' field to indicate when a 3D Secure exemption has been granted. This addition provides clearer information about 3D Secure exemptions for transactions.
- [The Charges object no longer auto-expands refunds by default | Stripe Documentation](https://docs.stripe.com/changelog/2022-11-15/deprecates-charges-auto-expand): The Stripe Charges object no longer automatically expands refunds by default to improve API performance and reduce data transfer. Developers can still manually expand refunds if needed, but Stripe advises against it for performance reasons.
- [Removes the charges attribute from the PaymentIntent object | Stripe Documentation](https://docs.stripe.com/changelog/2022-11-15/removes-charges-attribute-paymentintent): The charges attribute has been removed from the PaymentIntent object in Stripe's API. Developers should now use the latest_charge property to access the most recent charge associated with a PaymentIntent, simplifying charge retrieval.
- [Adds new decline codes to the PaymentIntent and PaymentMethod APIs | Stripe Documentation](https://docs.stripe.com/changelog/2022-11-15/adds-decline-codes-paymentintent-paymentmethod): Stripe has added new decline codes to the PaymentIntent and PaymentMethod APIs, including payment_intent_payment_attempt_expired, payment_method_customer_decline, payment_method_provider_timeout, payment_method_not_available, and payment_method_provider_decline. These additions improve error identification and handling for payment declines.
- [Adds new decline codes to the SetupIntent API | Stripe Documentation](https://docs.stripe.com/changelog/2022-11-15/adds-decline-codes-setupintent): New decline codes have been added to Stripe's SetupIntent API, specifically setup_intent_setup_attempt_expired, payment_method_customer_decline, payment_method_provider_timeout, payment_method_not_available, and payment_method_provider_decline. These codes enhance the accuracy of identifying reasons for SetupIntent declines.
- [Adds a new structure error code to the Accounts API | Stripe Documentation](https://docs.stripe.com/changelog/2022-11-15/adds-structure-error-code-accounts): Stripe's Accounts API now includes a new structure error code, verification_legal_entity_structure_mismatch, within the requirements.errors array. This code specifically identifies mismatches in the legal entity structure during account verification.
- [Enables automatic payment methods by default for PaymentIntents and SetupIntents | Stripe Documentation](https://docs.stripe.com/changelog/2023-08-16/automatic-payment-methods): PaymentIntents and SetupIntents now enable automatic_payment_methods by default, allowing configuration via the Stripe Dashboard. When confirming a PaymentIntent, a return_url is now required unless off_session is true, and error_on_requires_action is deprecated for this purpose.
- [One-time payments in Checkout Sessions support no-cost orders | Stripe Documentation](https://docs.stripe.com/changelog/2023-08-16/no-cost-orders-checkout-session): Stripe Checkout Sessions now support no-cost orders for one-time payments by changing the payment_method_collection value from always to if_required. This change streamlines the checkout process for zero-cost transactions, such as free trials or promotions.
- [Platform-scope rendering for select PaymentMethod fingerprints | Stripe Documentation](https://docs.stripe.com/changelog/2023-08-16/platform-scope-rendering-payment-method): PaymentMethod fingerprints for bank account-based payment types (us_bank_account, acss_debit, sepa_debit, bacs_debit, and au_becs_debit) are now rendered in platform scope when viewed by a platform. This aligns with previous changes for cards and bank accounts, providing consistent rendering for platforms.
- [Adds specific error codes for failed Klarna payments | Stripe Documentation](https://docs.stripe.com/changelog/2023-08-16/klarna-payment-failure-error-code): The Stripe PaymentIntent API now includes more specific error codes for failed Klarna payments: payment_method_customer_decline, payment_method_not_available, payment_method_provider_decline, and payment_intent_payment_attempt_expired. These codes provide detailed information for improved error handling.
- [Adds new director verification error codes to the Accounts API | Stripe Documentation](https://docs.stripe.com/changelog/2023-08-16/adds-director-verfication-error-accounts): Stripe's Accounts API has added four new error codes related to director verification: verification_missing_directors, verification_directors_mismatch, verification_document_directors_mismatch, and verification_extraneous_directors. These codes are part of the requirements.errors array and provide specific details on director verification issues.
- [Adds new account requirement error codes to the Accounts API   | Stripe Documentation](https://docs.stripe.com/changelog/2023-10-16/adds-account-requirement-error-accounts): The Stripe Accounts API now includes new error codes in the requirements.errors array for various issues, including invalid addresses, business profiles, company names, dates of birth, product descriptions, statement descriptors, tax IDs, and URLs. This provides more detailed error messages for better issue identification.
- [Auto-populates the statement descriptor and prefix in the Accounts API   | Stripe Documentation](https://docs.stripe.com/changelog/2023-10-16/auto-populates-statement-descriptor-accounts): Stripe's Accounts API now auto-populates the statement descriptor when it is unset, using business_profile.name, business_profile.url, company.name, or individual names as priority fields. Additionally, settings.card_payments.statement_descriptor_prefix now defaults to a shortened version of settings.payments.statement_descriptor when the descriptor is updated.
- [Makes automatic sync the default capture method for PaymentIntents when not specified | Stripe Documentation](https://docs.stripe.com/changelog/2024-04-10/automatic-sync-default-paymentintents): Stripe's PaymentIntents now use automatic_async as the default capture method when not explicitly specified during creation. This change allows developers to benefit from asynchronous capture by default, potentially improving payment success rates.
- [Renames the rendering_options attribute for invoices to rendering | Stripe Documentation](https://docs.stripe.com/changelog/2024-04-10/renames-rendering-options-invoicing): The rendering_options attribute for Stripe invoices has been renamed to rendering. Developers must update their code to access and modify these invoice rendering settings under the new attribute name.
- [Renames the features attribute of the Product object | Stripe Documentation](https://docs.stripe.com/changelog/2024-04-10/renames-features-attribute-product-object): The features attribute within Stripe's Product object has been renamed to marketing_features. This change more precisely defines the purpose of the attribute, and developers will need to update their code accordingly.
- [Renames a fuel attribute of the Authorization object  | Stripe Documentation](https://docs.stripe.com/changelog/2024-06-20/renames-fuel-attribute-authorization-object): Stripe has renamed the fuel.volume_decimal attribute to fuel.quantity_decimal on the Issuing Authorization resource and related test helper APIs. This change more accurately describes the number of items purchased in a fuel transaction.
- [Renames a purchase_details attribute of the Transaction object  | Stripe Documentation](https://docs.stripe.com/changelog/2024-06-20/renames-purchase-details-transaction-object): Stripe has renamed the purchase_details.fuel.volume_decimal attribute to purchase_details.fuel.quantity_decimal on the Issuing Transaction resource and related test helper APIs. This renaming clarifies that the attribute represents the quantity of items purchased.
- [Removes undocumented fuel fields | Stripe Documentation](https://docs.stripe.com/changelog/2024-06-20/removes-undocumented-fuel-fields-issuing): Stripe has removed undocumented fuel fields from the Issuing Transaction resource, replacing purchase_details.fuel.unit_cost and purchase_details.fuel.volume with their decimal equivalents. This change requires updating API versions and potentially SDKs to ensure compatibility with the new data structure.
- [Removes undocumented fleet fields | Stripe Documentation](https://docs.stripe.com/changelog/2024-06-20/removes-undocumented-fleet-fields-issuing): Stripe has removed undocumented fleet fields from the Issuing Transaction resource, replacing gross amounts and tax amounts with their decimal equivalents. This update necessitates API version upgrades and potential SDK adjustments for accurate financial reporting.
- [Adds enum values for fuel units | Stripe Documentation](https://docs.stripe.com/changelog/2024-06-20/adds-enum-fuel-units-issuing): Stripe has added new enum values to the Issuing Transaction purchase_details.fuel.unit property. These new values include imperial_gallon, kilogram, pound, charging_minute, and kilowatt_hour, providing more granular options for specifying fuel units.
- [Deprecates alphanumeric_id for Issuing Authorization | Stripe Documentation](https://docs.stripe.com/changelog/2024-06-20/deprecates-alphanumeric-id-issuing): Stripe deprecates the alphanumeric_id property for Issuing Authorizations, recommending the use of driver_id, vehicle_number, unspecified_id, or user_id instead. This change aims to provide clearer identifier categorization for fleet management scenarios.
- [Adds enum values for disabled reasons | Stripe Documentation](https://docs.stripe.com/changelog/2024-06-20/adds-enum-disabled-reasons-capabilities): Stripe has added 'paused.inactivity' and 'other' as new disabled reasons within the Capabilities API. This enhancement provides more specific information about why a capability might be disabled, improving clarity for users.
- [Deprecates the bank_transfer_payments capability type in favor of newer capability types | Stripe Documentation](https://docs.stripe.com/changelog/2024-06-20/deprecates-bank-transfer-payments-capabilities): Stripe deprecates the generic bank_transfer_payments capability type in favor of location-specific types like gb_bank_transfer_payments and sepa_bank_transfer_payments. This change offers more precise, geographically relevant capabilities for bank transfers.
- [Adds new enum values for request history reasons | Stripe Documentation](https://docs.stripe.com/changelog/2024-06-20/adds-enum-request-history-reasons-issuing): Stripe has added new enum values to the Issuing Authorization request_history.reason property, including card_canceled, card_expired, cardholder_blocked, insecure_authorization_method, and pin_blocked. These additions allow for more precise tracking and understanding of authorization request reasons.
- [Adds Switzerland UID as a supported customer tax ID | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/switzerland-tax-uid): Stripe now supports Switzerland's UID number (ch_uid) as a customer tax ID, in addition to the existing CH VAT. This expands the options for identifying customers for tax purposes within the Stripe platform.
- [Adds support for email types to Credit Notes | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/credit-note-email-type): Stripe now supports specifying email types when creating Credit Notes, allowing users to choose between sending a credit note email or no email by default. This provides more control over customer communication for credit note issuance.
- [Adds support for configuring the reboot time setting | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/terminal-reboot-window): Stripe introduces the reboot_window parameter for Terminal configurations, enabling users to set a custom time window for reader reboots and software updates. This feature helps prevent reboots from disrupting business operations.
- [Adds support for three new payment methods: Multibanco, Twint, and Zip | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/payment-links-new-payment-methods): Stripe expands Payment Links support by adding Multibanco, Twint, and Zip as new payment method options. This allows businesses to offer these popular payment methods to their customers through Payment Links.
- [Adds support for filtering by account subcategories on Financial Connections | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/financial-connections-filters): Stripe enhances Financial Connections by adding support for filtering Accounts by subcategories like 'checking' and 'savings' across multiple Payment APIs. This opt-in functionality allows for more granular control over the types of financial accounts that can be connected.
- [Expands filtering support for Financial Connections Sessions | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/financial-connections-additional-filters): Stripe expands filtering support for Financial Connections Sessions by introducing 'mortgage', 'line_of_credit', and 'credit_card' as allowable account subcategories. This builds upon existing 'checking' and 'savings' filters, offering more detailed options for account categorization.
- [Adds support for bulk invoice line item operations | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/invoicing-bulk-line-item-operations): Stripe introduces bulk operations for invoice line items, allowing creation, updating, and deletion through single API calls. This streamlines invoice management for users by reducing the number of API requests needed.
- [Adds support for posting time on tax transaction creation | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/tax-posting-time-on-creation): Stripe enables specifying and retrieving the posting time when creating tax transactions with the new 'posted_at' parameter. This improves the accuracy of recording tax liability for reporting within correct fiscal periods.
- [Adds address validation for physical cards | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/issuing-address-validation): Stripe adds address validation for physical cards, allowing users to specify the validation mode when creating or updating card shipping addresses. This feature enhances the accuracy of shipping information provided by customers.
- [Adds support for the Payment Element on a Customer Session | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/support-payment-element-customer-session): Stripe now supports configuring the Payment Element within a Customer Session, enabling the saving of customer payment methods. This integration enhances the checkout experience by allowing for saved payment details.
- [Adds option to retrieve CVC tokens on Confirmation Tokens | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/support-payment-method-options-confirmation): Stripe allows the retrieval of CVC tokens on Confirmation Tokens by introducing the 'payment_method_options.card.cvc_token' parameter. This change enables the use of CVC numbers with Confirmation Tokens for enhanced security during payment processing.
- [Adds customer ID to payment method preview on a confirmation token | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/support-customer-payment-method-preview): Stripe adds customer-specific information to the payment method preview on Confirmation Tokens. This feature allows for the display of customer details during the checkout preview stage.
- [Adds a new webhook event for when funds are deducted as part of a dispute | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/issuing-webhook-fund-deduction): Stripe introduces a new webhook event, 'issuing_dispute.funds_rescinded', which triggers when funds are deducted from an account due to an Issuing dispute. This event helps in monitoring and reacting to fund movements related to disputes.
- [Adds the Stripe S700 reader as a valid device type | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/terminal-reader-s700): Stripe now recognizes the S700 reader as a valid device type for Terminal. This update allows developers to specify 'stripe_s700' in API requests related to Reader objects. Users are advised to upgrade their API version or SDK to ensure compatibility with this change.
- [Adds support for using the Multibanco payment method with  billing | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/billing-mutlibanco-support): The Multibanco payment method is now supported for invoices and subscriptions within Stripe Billing. This integration expands payment options for customers and simplifies billing management for businesses. Developers should upgrade their API version to utilize this new feature.
- [Adds webhook events for when an invoice is due or overdue | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/billing-due-date-webhooks): Stripe introduces two new webhook events, 'invoice.overdue' and 'invoice.will_be_due', to enhance custom automations. These events allow businesses to trigger actions based on invoice due dates. Upgrading the API version is necessary to implement these new webhook capabilities.
- [Adds support for identifying the unique payer for the BLIK payment method | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/buyer-id-blik): Stripe now supports the 'buyer_id' parameter for BLIK payments, enabling better tracking of specific customers. This feature aids in identifying unique payers for BLIK transactions. Developers should update their API version to leverage this new tracking capability.
- [Adds support for identifying the case type for card disputes | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/disputes-case-type-card): The 'case_type' enum is now available for card disputes, allowing for the identification of dispute types such as chargebacks or inquiries. This provides clearer insights into dispute reasons and their potential financial impact. Users should upgrade their API version to access this new dispute information.
- [Adds support for Affirm transaction IDs | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/affirm-transaction-id-dashboard): Stripe now displays Affirm transaction IDs for payments within the Stripe Dashboard and via the API. This enhancement provides better visibility into Affirm payment details. Developers should upgrade their API version to access and utilize these transaction IDs.
- [Adds Twint to the PaymentMethodConfiguration API | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/twint-support-payment-method-configuration): The PaymentMethodConfiguration API now supports the Twint payment method, allowing it to be displayed without explicit type specification. This simplifies the integration of Twint as a payment option. An API version upgrade is recommended to implement this feature.
- [Adds support for in-person payment methods, including Interac cards | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/card-interac-present-support): Stripe enhances support for in-person payment methods, including Interac cards, by providing more detailed information for card_present and interac_present transactions. This includes issuer, description, brand product, and network transaction ID. Developers should upgrade their API version to access these new details.
- [Adds support for tax settings and registrations for Embedded Components | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/tax-registrations-settings-embedded-components): Stripe Embedded Components now support tax settings and registrations, allowing Connect platforms to manage tax integrations for connected accounts. This feature enables whitelabeling of Stripe Tax without custom UI development or dashboard redirects. An API version upgrade is required to use these new components.
- [Adds a method to update the metadata for Checkout Sessions | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/checkout-update-method): A new 'Update' method is available for Stripe Checkout Sessions, enabling the modification of metadata for existing sessions. This provides greater flexibility in managing checkout data. Developers should upgrade their API version to utilize this new update functionality.
- [Adds an Alerts API for usage-based billing | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/billing-alerts-api): Stripe introduces an Alerts API for usage-based billing, allowing the configuration of alerts based on customer usage. When a threshold is met, a 'billing.alert.triggered' event is emitted. This feature helps in managing and reacting to billing usage patterns. An API upgrade is necessary to implement this.
- [Adds an event for triggered billing alerts | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/billing-alert-trigger-event): A new 'billing.alert.triggered' event is now available, notifying integrations when a billing alert threshold is met. This event allows for automated responses to customer usage patterns. Developers should upgrade their API version to listen for and act upon this new event.
- [Adds support for listening to triggered billing alerts | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/billing-alert-webhook-listener): Stripe now supports creating listeners for the 'billing.alert.triggered' event, enhancing the functionality of webhook endpoints. This allows businesses to react to usage-based billing alerts. An API version upgrade is recommended for developers to implement this webhook listening capability.
- [Adds error code for exceeded transaction limits | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/error-code-transaction-limit): A new error code, 'charge_exceeds_transaction_limit', is added for invoices, payment intents, and setup intents. This code helps identify when a transaction using a bank debit method exceeds the merchant's volume limit. Developers should upgrade their API version to test for and handle this specific error.
- [Adds parameter to link Verification Sessions to Customers | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/identity-verification-session-related-customer): Stripe's Identity Verification Sessions now include a 'related_customer' parameter, allowing direct linking to existing Customer resources. This enhances visibility into customer risk profiles for better decision-making. Developers should upgrade their API version to utilize this new customer linking feature.
- [Adds new method to retrieve a Tax Calculation | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/retrieves-tax-calculation-api): A new method is added to retrieve Tax Calculations by their ID, providing access to previously computed tax data. These calculations expire after 90 days. Developers should upgrade their API version to utilize this retrieval method for tax management.
- [Adds details about offline collection on card_present PaymentMethod objects | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/terminal-offline-details-card-present-paymentmethods): Stripe now provides details about offline collection for card_present PaymentMethod objects, including a 'type' field set to 'deferred'. This allows for better tracking and reconciliation of offline transactions processed via the Terminal mobile SDKs. An API version upgrade is recommended to access these offline details.
- [Adds Girocard as a PaymentMethod brand and network | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/adds-girocard-paymentmethod-brand-network): Girocard is now supported as a card brand and network within Stripe's payment methods. This expansion allows for broader acceptance of Girocard payments across various Stripe features. Developers should upgrade their API version to utilize Girocard as a payment option.
- [Adds new error code for invalid mandate prefixes to Bacs Direct Debit and SEPA Direct Debit payments | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/error-code-invalid-mandate-reference-prefix): A new error code, 'invalid_mandate_reference_prefix_format', is introduced for Bacs Direct Debit and SEPA Direct Debit payments. This code helps identify issues with reference prefix formats in Mandates. Developers should upgrade their API version to test for and handle this specific error.
- [Adds billing alert resources and endpoints | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/adds-billing-alert-resources-endpoints): Stripe introduces new methods for managing the Alert resource, including activate, archive, create, deactivate, list, and retrieve. This enables the configuration and management of usage-based billing alerts and associated webhooks. An API upgrade is necessary to utilize these new billing alert resources and endpoints.
- [Displays CHIPS tracking details for outbound wire payments and transfers | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/displays-chips-tracking-details-treasury-outbound-wires): Stripe now provides CHIPS tracking details for US domestic wire payments and transfers through the new tracking_details.us_domestic_wire.chips field. This enhancement allows for better tracking of these specific types of outbound transactions.
- [Displays authorization_code for Charges | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/displays-authorization-code-for-charges): The authorization_code for card charges is now available in Stripe's API. This addition provides valuable information for tracking and verifying card transactions.
- [Adds wallet details for card_present Charges and Payment Methods | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/adds-offline-details-card-present-paymentmethods): Stripe has added a wallet.type field to card_present Charges and Payment Methods. This allows users to identify the specific mobile wallet used during a transaction.
- [Adds Croatian Personal Identification Number to supported Tax IDs | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/adds-tax-id-type-hr_oib-croatian-personal-id-number): Stripe now supports the Croatian Personal Identification Number (hr_oib) as a Tax ID type across various API endpoints. This improves support for Croatian customers and ensures accurate tax reporting.
- [Adds additional reasonable defaulting to the Account Link API v1 | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/account-link-api-default-fields-v1): The Account Link API v1 now applies 'currently_due' as the default value for the fields parameter when creating an Account Link. This change simplifies the process by removing the need to manually specify fields when using 'future_requirements' as a collection option.
- [Makes LineItem.description optional | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/description-optional-checkout-session-line-item): The description field for a Checkout Session's line item is now optional. This provides more flexibility when creating line items for checkout sessions.
- [Adds target_frozen_time for advancing test_helpers.test_clock objects | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/support-status-details-test-clock): Stripe has added the target_frozen_time parameter for advancing test_helpers.test_clock objects. This feature enhances test management and debugging by providing visibility into the state of test clocks.
- [Adds support for subscriptions and subscription items to billing alerts | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/billing-alerts-subscription-items-subscriptions): Stripe has expanded billing alerts to include support for subscriptions and subscription items. Users can now configure alerts and thresholds to monitor customer usage levels for these specific billing components.
- [Adds Invoice Rendering Templates for Invoices | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/invoice-rendering-template-resource): Stripe introduces Invoice Rendering Templates, allowing users to define rules for how invoices group and display line items, default descriptions, footers, and custom fields. These templates can be created in the Dashboard or via the API and applied to specific Invoices and Customers.
- [Adds retrieve and archive methods for Invoice Rendering Templates | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/invoice-rendering-template-methods): New methods have been added to retrieve, list, archive, and unarchive Invoice Rendering Templates in Stripe. This enhances the management capabilities for these templates.
- [Adds support for templates to Invoices and Customers | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/invoice-rendering-template-parameter): The 'template' field has been added to the Invoice and Customer resources in Stripe. This allows users to specify which Invoice Rendering Template to apply to individual invoices or all invoices for a specific customer.
- [Adds version support for Invoice Rendering Templates | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/invoice-rendering-template-version): Stripe now supports versioning for Invoice Rendering Templates. This enables the creation of iterated versions of these templates, providing better management and tracking of template changes.
- [Makes status details for Test Clock test helpers required | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/make-testclock-status-details-required): The status_details hash is now required for Test Clock test helpers in Stripe. This change improves the accuracy of Test Clocks by ensuring that status-related information is always available for tracking and debugging.
- [Adds support for requiring a customer tax ID on Checkout and Payment Links | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/requiring-customer-tax-id-checkout-session-paymentlink): Stripe now supports requiring a customer tax ID on Checkout Sessions and Payment Links using the new tax_id_collection[required] parameter. This ensures customers from supported countries provide their tax ID during payment if collection is enabled.
- [Adds risk verification details for connected accounts | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/additional-risk-verification-details-connected-accounts): Stripe has added new risk verification details for connected accounts, including a 'verification_supportability' error code. This helps users understand the reasons for verification issues and guide connected accounts on how to resolve them.
- [Adds country field for Charges that use Klarna | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/charges-klarna-payer-details-country): Stripe has added a country field to the payment_method_details object for Charges that use Klarna. This allows for associating a customer's Klarna account information with their country.
- [Adds support for specifying US state sales tax elections while creating tax registrations | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/support-us-state-sales-tax-elections-api): Stripe now supports specifying US state sales tax elections via the API when creating tax registrations. The new 'state_sales_tax' field in the Tax.Registration API aligns with Dashboard functionality for managing state-specific tax registrations.
- [Displays Amazon Pay dispute type on Disputes | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/display-amazonpay-dispute-type): The Amazon Pay dispute_type is now available within the Dispute.payment_method_details field in Stripe. This provides clearer insights into the specifics of Amazon Pay disputes.
- [Adds a new enum value representing a ReceivedDebit failure due to an international transaction | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/ef-features): Stripe has introduced an 'international_transaction' enum value for ReceivedDebit.failure_code. This new code identifies failures related to international transactions, as Treasury financial accounts cannot send or receive funds from international sources.
- [Adds option to automatically finalize invoices | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/automatically-finalizes-at-invoice): Stripe now includes an 'automatically_finalizes_at' parameter for Invoices. This allows users to understand when an invoice is scheduled to finalize automatically and to manage this process.
- [Add support for custom_unit_amount during product creation | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/products-custom-unit-amount): Stripe now supports the custom_unit_amount parameter during product creation, allowing for flexible pricing adjustments by customers in Checkout Sessions and Payment Links. This addition benefits businesses needing specific price configurations for their offerings.
- [Makes it optional to update the products and prices of a subscription | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/billing-portal-updates-optional): Stripe has made updates to the Billing Portal, allowing subscription update behaviors like product and price changes to be optional when subscription updates are disabled. This change prevents missing parameter errors and provides more flexibility for customer portal configurations.
- [Updates consent modeling for saving cards with Terminal | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/terminal-remove-customer-consent-require-allow-redisplay): Stripe Terminal now updates its consent modeling for saving cards by replacing the customer_consent_collected parameter with allow_redisplay. This change is required when using setup_future_usage and allows cards to be saved in more regions, ensuring regulatory compliance.
- [Updates the default value for shipping address validation | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/card-shipping-status-submitted-address-validation): Stripe has updated the default value for shipping address validation to validation_and_normalization for physical card shipments. This improves the accuracy of tracking card shipment status and reduces delivery errors by automatically validating and normalizing addresses.
- [Adds contextual filters to billing alerts | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/billing-alerts-contextualizing-filters): Stripe billing alerts now include contextual filters, moving the filter field into the alert type configuration and renaming fields to remove the '_config' suffix. This allows for unique filters per alert type and simplifies configuration by using 'usage_threshold' instead of 'usage_threshold_config'.
- [Adds support for retrieving thin events | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/api-v2-thin-events): Stripe now supports retrieving 'thin events' via the /v2/core/events endpoint, offering lightweight, unversioned payloads with a more granular permissions model. This simplifies webhook integration maintenance and improves the handling of events, particularly for the Meters API.
- [Adds Credit Grant APIs and resources | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/billing-credits-apis): Stripe introduces new Credit Grant APIs and resources for managing billing credits, allowing prepaid or promotional credits to be allocated to customers. These credits can then be drawn down using subscription invoices for billing meter prices.
- [Adds support for pre-tax credit amount information to invoices | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/billing-credits-invoice): Stripe invoices now include pretax_credit_amounts and total_pretax_credit_amounts attributes, providing a breakdown of credits and discounts applied before tax calculations. This enhances transparency by showing which credit notes were issued and their relation to the invoice.
- [Adds support for pre-tax credit amount information to credit notes | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/billing-credits-credit-note): Stripe credit notes now include the pretax_credit_amounts attribute, detailing credits and discounts applied to the original invoice before tax calculations. This provides a clearer understanding of how credit notes relate to the initial invoice.
- [Adds support for disabling Stripe user authentication for certain embedded components | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/disable-stripe-user-authentication-account-sessions): Stripe now supports disabling user authentication for certain embedded components within Account Sessions, particularly when external_account_collection is true. This allows for more control over authentication flows for custom account types.
- [Adds a test helper that updates the shipping status for physical cards | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/testmode-helper-shipping-status): Stripe has added a test helper method, submit_card, to the Issuing.Card resource. This allows developers to simulate the submission of a physical card's shipping status within the testing environment.
- [Adds created, updated, and failed events for all refund types | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/refund-webhook-update): Stripe now provides created, updated, and failed events for all refund types, including those without a corresponding charge. This simplifies refund tracking by offering a consistent event structure and eliminates the need for extra API calls to retrieve refund details.
- [Adds support for new countries to the Tax Registration API | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/tax-registration-new-countries): Stripe's Tax Registration API now supports new countries including Belarus, Costa Rica, Ecuador, Moldova, Morocco, Russia, Serbia, Tanzania, and Uzbekistan. This expands the API's geographic coverage, enabling businesses to manage tax information in these regions.
- [Adds support for tax ID types in several new countries | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/tax-ids): Stripe now supports new tax ID types for Belarus, Morocco, Moldova, Tanzania, and Uzbekistan across various API endpoints. This allows for the collection, storage, and processing of these specific tax identification types for customers in these countries.
- [Adds pricing groups to the Accounts API | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/pricing-groups-account-objects): Stripe's Accounts API now includes pricing groups, enabling connected accounts to be placed into specific groups and their membership to be retrieved. This provides greater programmatic flexibility in managing pricing structures for connected accounts.
- [Adds a metadata field to the Vault and Forward API | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/forwarding-api-metadata-field): The Stripe Vault and Forward API now includes a metadata field for forwarding requests. This allows for additional information to be included, aiding in the reconciliation of forwarding requests and improving attribution compared to relying solely on idempotency keys.
- [Adds support for new South Korean payment methods | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/south-korean-payment-methods): Stripe now supports several new South Korean payment methods, including local cards, Naver Pay, Kakao Pay, Samsung Pay, and PAYCO. These can be used with Checkout, Elements, Payment Links, Billing, and Invoicing integrations.
- [Adds scheduled subscription downgrades in the customer portal | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/customer-portal-schedule-downgrades): The Stripe customer portal now supports scheduled subscription downgrades, allowing them to occur at the end of the billing cycle instead of immediately. This feature can be configured via the Dashboard or the API using the schedule_at_period_end parameter.
- [Adds support for collecting retail delivery fees | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/tax-retail-delivery-fee): Stripe now supports collecting retail delivery fees for tangible personal property in Minnesota and Colorado by adding 'retail_delivery_fee' as a tax type. It also extends tax_rate_details for Tax Calculations to represent flat amount tax rates.
- [Adds Polish PLN currency support to Terminal tipping configuration | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/terminal-tipping-pln): Stripe Terminal tipping configuration now supports the Polish PLN currency. This allows users in Poland to collect on-reader tips in their local currency.
- [Adds support for Alma in France | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/alma): Stripe now supports Alma, a buy now, pay later payment method, in France. This allows French customers to pay in installments while merchants receive instant payment. The update includes changes to the REST API for integrating Alma.
- [Adds option to automatically validate customer tax location during an update | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/tax-validate-location-auto): Stripe introduces an 'auto' option for tax.validate_location to simplify Stripe Tax integrations. This feature automatically validates customer tax locations during updates, returning an error for unrecognized locations. It is recommended for new Stripe Tax integrations to avoid invoice finalization errors.
- [Supports domain registration for Amazon Pay | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/amazon-pay-domain-registration): Stripe now supports domain registration for Amazon Pay through the Payment Method Domain resource. Merchants must register all web domains, including subdomains, to use Amazon Pay with Elements or Checkout. This registration allows the domain to be used with any future enabled payment methods.
- [Makes business profile optional for customer portal configuration | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/customer-portal-config-business-profile): The business_profile parameter is now optional when creating a customer portal configuration in Stripe. This change simplifies the process of setting up a customer portal by removing a previously required field.
- [Adds event type for updated receipt data in Issuing transactions | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/issuing-transactions-updated-receipt-event): Stripe has added a new event type, issuing_transaction.purchase_details_receipt_updated, for Issuing transactions. This allows developers to receive webhook notifications when receipt data for an Issuing Transaction is updated, eliminating the need to poll the Transaction endpoint for this information.
- [Uses Visa's Compelling Evidence 3.0 to respond to qualifying disputes | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/visa-compelling-evidence-3-0): Stripe now utilizes Visa's Compelling Evidence 3.0 to respond to qualifying disputes. This is facilitated by a new enhanced_evidence object within the Dispute resource, which can improve dispute win rates by providing enhanced evidence.
- [Adds support for scheduling invoice finalization | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/schedule-invoice-finalization): Stripe now supports scheduling invoice finalization using the automatically_finalizes_at field. This allows invoices to be set to send or charge customers on a specific future date.
- [Adds network decline code field for Swish and BLIK refunds | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-11-20/refunds-network-decline-code): Stripe has added a network decline code field for Swish and BLIK refunds. This provides the decline code from financial partners for failed refunds, helping users understand the reason for the failure.
- [Converts properties on the Account object from a String to an enum | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-11-20/account-disabled-reason): Stripe has updated the Account object properties requirements.disabled_reason and future_requirements.disabled_reason to use enum values instead of strings. This change standardizes the reasons for account disabling without introducing new ones.
- [Adds support for SEPA Direct Debit and Bacs Direct Debit mandate reference prefixes in Checkout Sessions | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-11-20/checkout-sessions-sepa-debit-bacs-debit-mandate-options): Stripe Checkout Sessions now support SEPA Direct Debit and Bacs Direct Debit mandate reference prefixes. The new mandate_options.reference_prefix parameter allows customization of mandate references for SEPA Direct Debit and Bacs Direct Debit in Payment and Setup modes.
- [Adds support for advanced card features on Checkout Sessions | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-11-20/advanced-card-features): Stripe Checkout Sessions now support advanced card features like incremental authorization, extended authorization, multicapture, and overcapture for IC+ users. These features, previously only available for Payment Intents, can now be utilized directly within Checkout Sessions for payment mode with manual capture.
- [Adds indicator for connected accounts that must log in before using embedded components | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-11-20/account-sessions-stripe-authentication-response): Stripe's Account Sessions API now consistently returns the disable_stripe_user_authentication indicator. This indicator determines if connected accounts must log in before using embedded components, offering Connect platforms more control over authentication flows for custom accounts.
- [Adds SDK support for trace IDs | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/trace-id-sdk): Stripe SDKs now support the trace_id field on the Payout object. This allows users to track missing or delayed payouts with their bank, and for Connect users, it enables connected accounts to self-serve payout inquiries.
- [Allows Link card-only integrations to accept non-card payments under Link card brand | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-11-20/link-card-brand): Link card-only integrations can now accept non-card payments under the Link card brand. This expansion allows Link integrations to support non-card payment methods, providing more flexibility beyond traditional card payments.
- [Customize the submit button recurring Payment Links and Checkout Sessions | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-11-20/submit-type-recurring-cpl): Stripe allows customization of the submit button for recurring Payment Links and Checkout Sessions. The submit_type parameter can now be set to 'donate' for recurring payments, offering users more control over the button's appearance and behavior.
- [Adds support for Service Tax type | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-11-20/service_tax): Stripe has added support for the Service Tax type, specifically for collecting Service Tax in Malaysia on digital products. This update includes the 'service_tax' enum value for the tax_type field in the Tax Rate resource.
- [Adds additional beneficiary information for bank transfer payments | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-11-20/new-bank-transfer-beneficiary-information): Stripe now provides additional beneficiary information for bank transfer payments. This includes details like the beneficiary's name and address, and the bank's address, which are included in funding instructions for customers making bank transfer payments.
- [Adds tax ID support for Liechtenstein VAT | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-11-20/li_vat): Stripe now supports tax ID collection for Liechtenstein VAT. This enables businesses to collect, store, and process VAT IDs for customers in Liechtenstein through various Stripe resources like Checkout Sessions and Invoices.
- [Adds support for enabling Adaptive Pricing per Checkout Session | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-11-20/adaptive-pricing-param): Stripe now supports enabling or disabling Adaptive Pricing on a per-Checkout Session basis. A new API parameter allows programmatic control over Adaptive Pricing, overriding dashboard settings for granular control and incremental rollouts across multiple integrations.
- [Adds support for merchant amount and currency for test mode authorizations | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-11-20/add-merchant-currency-and-merchant-amount-on-create-testmode-authorization-method): Stripe allows specifying merchant amount and currency for test mode authorizations. The merchant_amount parameter is now optional, and the amount parameter becomes optional when merchant_amount is provided, enabling more flexible test authorization scenarios.
- [Specifying an originating payment method for Inbound Transfers is now optional | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-11-20/inbound-transfers-optional-pm): The origin_payment_method property for Inbound Transfers is now optional, improving compatibility with new money movement rails like check deposits. ACH network transfers still require this field. This change requires updating API versions to 2024-11-20.
- [Adds support for issuing fraud challenges | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-11-20/issuing-fraud-challenges): Stripe Issuing now supports fraud challenges, allowing cardholders to retry transactions incorrectly declined by fraud controls. A new verified_by_fraud_challenge field indicates when fraud risk controls were bypassed due to a completed challenge. This feature can be enabled in the Issuing settings Dashboard.
- [Adds support for authorizers to Person API | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-11-20/authorizer-person-api): The Person API now includes the 'authorizer' role, allowing an individual to be designated as authorized to represent a business on a Stripe account. This is used to fulfill Know Your Customer (KYC) requirements when the primary account representative does not match a registered business representative. Only one authorizer can be assigned per account, and they cannot be the account representative.
- [Adds additional beneficiary information for bank transfer payments | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/new-bank-transfer-beneficiary-information): Stripe now provides additional beneficiary information for customers making bank transfer payments. This includes details like the receiver's name and address, which are included in the funding instructions presented to customers, simplifying the process for banks that require this information.
- [Adds funding details to Amazon Pay and Revolut Pay charges | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/charge-pm-details): Underlying funding details are now included in charge.payment_method_details for Amazon Pay and Revolut Pay. This allows users to view card details for these payment methods in the Dashboard or in PaymentIntent responses, providing greater transparency.
- [Use configurable capture methods and set up future usage for South Korean payment methods | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-11-20/south-korea-payment-methods): South Korean payment methods, including cards, Naver Pay, Kakao Pay, Samsung Pay, and PAYCO, now support manual capture_method and setup_future_usage. This allows for overriding automatic capture and saving payment method details for future use, offering more flexibility in Checkout Sessions.
- [Adds disabled reason to invoices, subscriptions, and schedules | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/add-disabled-reason): A new disabled_reason field has been added to the Invoice, Subscription, and Subscription Schedule objects. This field identifies when Stripe disabled automatic tax calculation due to missing or incomplete location information for a customer, aiding in troubleshooting tax-related issues.
- [Trace payouts with a unique identifier | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-11-20/payout-trace-id-api): A new trace_id field is now available on the Payout resource to help track missing or delayed payouts. This unique identifier, provided by banking partners, can be shared with connected accounts to enable self-service for payout inquiries, reducing support load.
- [Adds new balance transaction types to support minimum balance | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/payout-minimum-balance): Two new balance transaction types, payout_minimum_balance_hold and payout_minimum_balance_release, have been introduced to support accounts limiting automatic payouts with a minimum balance. These transactions track the amount withheld to maintain the minimum balance and the amount subsequently released back to the account.
- [Adds support for SEPA Direct Debit and Bacs Direct Debit mandate reference prefix | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/mandate-reference-prefix): The reference_prefix parameter is now available for SEPA Direct Debit and Bacs Direct Debit in Payment Intents, Setup Intents, and Checkout Sessions. This allows customization of the mandate reference by specifying a prefix when creating a mandate.
- [Issuing authorizations now include merchant tax ID number | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/issuing-merchant-tax-id): Issuing authorizations now include a tax_id field within issuing_authorization.merchant_data, populated with the seller's tax ID number. This feature is currently available for French sellers and helps identify the business associated with an authorization.
- [Adds support for tax ID types in 19 new countries | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/tax-ids-19-new-countries): Stripe now supports new tax ID types for 19 additional countries across various API endpoints. This enables the collection, storage, and processing of tax identification types for customers in these new regions.
- [Adds support for 21 new countries to the Tax Registration API | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/tax-registration-21-new-countries): The Tax Registration API now supports 21 new countries, expanding its geographic coverage. This allows businesses operating in or selling to these countries to register and manage their tax information through Stripe.
- [Adds support for reinstating Billing Credits on Invoice voiding | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/billing-credits-invoice-voiding): Stripe now supports reinstating Billing Credits when an Invoice is voided. Voiding an invoice with applied credits will return the balance to the credit grant, with any expired credits expiring immediately. This change modifies the Billing.CreditBalanceTransaction type.
- [Adds signature request as a replacement option for the Vault and Forward API | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/vault-and-forward-request-signature-replacement): The Vault and Forward API now supports REQUEST_SIGNATURE as a replacement option. This enables the calculation of a request hash as part of the API, supporting Vault and Forward requests that require this functionality.
- [Adds support for responding to Visa compliance disputes | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/visa-compliance): A new visa_compliance object has been added to the Dispute resource, allowing users to submit evidence for Visa compliance disputes. This object helps determine eligibility for evidence submission and manage disputes related to Visa network rules.
- [Creates Issuing authorizations when Stripe is unavailable | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/issuing-auths-when-stripe-unavailable): Issuing authorizations can now be created when Stripe is unavailable, with the card network responding on Stripe's behalf. These authorizations trigger issuing_authorization.created webhook events and provide insight into the cardholder experience during Stripe outages.
- [Adds network advice and decline codes | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/network-advice-code-network-decline-code): Two new error codes, network_decline_code and network_advice_code, are now included in charge decline responses. These codes provide more detailed information from the card network about the reason for the decline and how to handle it.
- [Supports redisplaying payment methods for Cards and Sources | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/cards-sources-allow-redisplay): The allow_redisplay field is now supported for Cards and Sources via the v1/payment_method update endpoint. This field indicates whether a payment method can be shown again to a customer in a checkout flow, influencing how Stripe products display saved payment methods.
- [Adds field-level permissions for revenue and worker count in an Account's business profile | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/business-profile-revenue-worker-count): Field-level permissions for revenue and worker count in an Account's business profile are now supported. The annual_revenue and estimated_worker_count parameters can now return 'undefined' in addition to null or a value, allowing for more granular handling of Account data responses.
- [Adds network transaction ID to charges | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/charge-display-network-transaction-id): Stripe's Acacia API now includes a network_transaction_id property on the Charge object for successful Visa, Mastercard, Amex, Discover, and Cartes Bancaires transactions. This ID helps accurately map Stripe transactions with card network identifiers. Declined transactions and card validations do not include this property.
- [Modify trial subscriptions created by Payment Links | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/add-trial-days-update-payment-links-api): The subscription_data.trial_period_days parameter is updated for Payment Links, allowing modification of free trial durations for newly created subscriptions. This change only affects subscriptions created after the update and does not impact existing ones.
- [Adds regulated status field to card objects in several APIs | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/regulated-status): A new regulated_status field is added to Charge, Payment Methods, and Tokens API resources. This field indicates whether a card falls under a regulated account range, providing more information about card transactions.
- [Adds directorship declaration to the Accounts API | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-01-27/directorship-declaration): The Accounts API now includes directorship_declaration parameters (ip, date, user_agent) under the company field. These parameters allow attestation that the list of directors on a Stripe account accurately reflects the company's directors, aiding in Know Your Customer (KYC) compliance.
- [Adds advice code to Charges | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-01-27/charge-outcome-advice-code): The Charge object now includes an advice_code property, which provides detailed information about unsuccessful transactions. This code helps users understand how to proceed when a transaction fails.
- [Modify phone number collection on Payment Links | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-01-27/add-phone-number-collection-update-payment-links-api): The update Payment Link method now includes the phone_number_collection parameter. This allows for enabling or disabling phone number collection on the payment form of existing Payment Links, a feature previously only available at creation.
- [Adds proof of ultimate beneficial ownership as a document type | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-01-27/proof-of-ultimate-beneficial-ownership-document-support): The Accounts API now supports the proof_of_ultimate_beneficial_ownership document type for uploading documentation that identifies a business's ultimate beneficial owners. This feature aids in fulfilling Know Your Customer (KYC) requirements for businesses with complex ownership structures.
- [Adds support for the Pay by Bank local payment method | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-01-27/pay-by-bank-lpm): Stripe now supports the Pay by Bank local payment method (LPM), allowing customers to pay directly from their bank accounts. This single-use payment method runs on banking infrastructure and open banking APIs, usable with dynamic payment methods or Payment Intents.
- [Adds account holder information to Financial Address credentials for US bank accounts | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/financial-address-account-holder-information): The Financial Addresses API for US bank accounts now includes account_holder_name and account_holder_address properties in the us_bank_account object. This provides more detailed information about US bank account holders, enhancing accuracy and compliance.
- [Adds metadata field to the Products API for creating an inline default price | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-02-24/products-default-price-data-metadata-field): A metadata parameter is added to the Create a product method in the Products API. This allows for adding metadata fields to prices when creating products, eliminating the need for a separate API call to update the Price object.
- [Adds support for blocking specific card brands in Checkout Sessions | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-02-24/checkout_add_brands_blocked): The Create a Checkout Session method now supports blocking specific card brands via the payment_method_options.card.restrictions.brands_blocked parameter. This allows developers to specify an array of card brands that should not be allowed in the Checkout Session.
- [Checkout Sessions now group customer information in one field | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-02-24/checkout-sessions-collected-info): Checkout Sessions now include a collected_information object that groups customer-provided data, such as shipping_details. This change improves API organization and supports dynamic updates to shipping options in Checkout.
- [Credit grants can now be applied to specific prices | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-02-24/billing-credits-price-level-applicability): Credit grants can now be applied to specific prices or a price_type when created. This provides granular control over which prices a credit grant can affect, enabling more targeted balance summaries.
- [Credit grants can now be prioritized | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-02-24/billing-credits-priority): The Credit Grant resource now includes a priority parameter. This allows users to set custom priorities for applying credit grants, determining the order in which multiple grants are evaluated for an invoice or line item.
- [Adds ability to schedule debit payments for a specific date | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-02-24/target-date): The target_date parameter is now available for bank debit payment methods (ACH, SEPA, BACS, etc.) in Checkout Sessions and Payment Intents. This parameter allows scheduling debit payments for a future date between 3 to 15 days ahead, aiding financial planning.
- [Adds support for Klarna in the Hosted Invoice Page | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/klarna-send-invoice): Support for Klarna is added to the Hosted Invoice Page. For Subscriptions and Invoices with collection_method=send_invoice, Klarna can now be included in payment_settings.payment_method_types.
- [Checkout Session removes shipping details | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/checkout-session-remove-shipping-details): The shipping_details field has been moved from the top-level Checkout Session resource to the collected_information.shipping_details field. This is a breaking change that logically groups shipping information and improves API organization.
- [Adds reason code for Issuing authorizations created while Stripe is unavailable | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/new-network-fallback-issuing-authorization-reason-code): The Issuing authorization object's request_history.reason property now includes 'network_fallback' as an option. This allows identification of authorizations handled by the network when Stripe is unavailable, providing a new reason code for these scenarios.
- [HTTP Accept headers for webhooks now specify JSON during Issuing authorizations | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/issuing-json-webhook): Webhooks for Issuing real-time authorizations now specify 'application/json' in the request Accept header. This change ensures that webhook handlers expect and process JSON responses, preventing potential declines due to incorrect content negotiation.
- [Updates the Vault and Forward API to return a 402 status code for upstream request timeouts | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/vault-forward-api-returns-402): The Vault and Forward API now returns a 402 error code instead of 502 or 504 for upstream request timeouts that occur before a connection is established. This change allows for safe retries and distinguishes connection timeouts from other upstream errors.
- [Adds ability to configure saved payment methods for one-time payments on the Hosted Invoice Page | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/hosted-payment-method-save): Stripe now allows configuration of saved payment methods for one-time payments on the Hosted Invoice Page. This feature gives merchants control over whether customer payment methods are saved for future use, potentially increasing conversion rates.
- [Adds subscription item-level billing periods and removes subscription-level periods | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/deprecate-subscription-current-period-start-and-end): Stripe has updated its subscription billing to track billing periods at the item level instead of the subscription level. This change removes the `current_period_start` and `current_period_end` fields from the subscription resource, requiring developers to access these details directly from subscription items.
- [Removes total count expansion for list API methods | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/deprecate-total-count-expansion): Stripe is removing the `total_count` expansion for list API methods. Integrations that rely on `total_count` for pagination must now use the `has_more` response field instead, as attempting to expand `total_count` will result in a 400 error.
- [Removes manual capture method for Interac cards | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/deprecate-interac-present-manual-capture-method): The `interac_present` payment method no longer supports the manual `capture_method` for PaymentIntents. Integrations must now use automatic capture methods (`automatic_async` or `automatic`) for Interac payments, aligning with the network's single-message behavior.
- [Adds support for saving and reusing Naver Pay payment methods | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/naver-pay-recurring): Naver Pay payment methods can now be saved and reused for future payments through the SetupIntent and `setup_future_usage` parameters. The `buyer_id` parameter can be used to verify if two Naver Pay accounts are the same.
- [Adds jurisdiction level and taxability reason to manual tax amounts on invoices | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/invoice-manual-tax-amount-fields): Stripe now supports adding `taxability_reason` and `tax_rate_data.jurisdiction_level` to manual tax amounts on invoices. These fields were previously exclusive to automatically calculated taxes via Stripe Tax, providing more granular control over manual tax entries.
- [Adds default value to custom fields on Payment Links | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/default-value-payment-links-custom-fields): The `default_value` parameter is now available for custom text, numeric, and dropdown fields on Stripe Payment Links. This allows users to prefill form fields on the payment page, enhancing the user experience.
- [Removes coupon and promotion code parameters with stackable discounts | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/deprecate-singular-coupon-promotion-code): Stripe is removing singular `coupon` and `promotion_code` parameters in favor of the `discounts` parameter, which supports applying multiple discounts. This change impacts Subscription, Subscription Schedule, Customer, and Preview Invoice endpoints.
- [Replaces Upcoming Invoice API methods with the Create Preview Invoice API | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/invoice-preview-api-deprecations): Stripe is replacing the `GET /v1/invoices/upcoming` API methods with the Create Preview Invoice API. Developers must now pass specific subscription details to the Create Preview Invoice API, as the upcoming invoice preview functionality is being deprecated.
- [Removes support for discount coupons that don't have a specified end time | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/restrict-coupon-duration): Stripe is removing support for creating new `amount_off` coupons with a `forever` duration. Integrations can no longer apply indefinite `amount_off` coupons to subscriptions, invoices, and other resources; instead, these coupons should be applied directly to invoices.
- [Adds support for the Billie local payment method | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/add-billie): Stripe now supports the Billie local payment method, a B2B buy now, pay later solution. Businesses in Austria, France, Germany, the Netherlands, Sweden, and the UK can now accept single-use Billie payments from buyers across the EU.
- [Adds expired status for Issuing Authorizations | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/issuing-authorizations-expired): Issuing authorizations that expire by Stripe will now transition to an `expired` status instead of `reversed`. This change allows users to distinguish between authorizations that can be captured later (expired) and those that cannot (reversed).
- [Adds new error codes for required verifications | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/adds-requirement-error-codes): Stripe has introduced new error codes to the `requirements.errors` array in various APIs, including Accounts, Capabilities, Persons, and Bank Accounts. These new codes provide more specific feedback for issues like `information_missing`, `invalid_signator`, `verification_failed_authorizer_authority`, and `verification_rejected_ownership_exemption_reason`.
- [Checkout Session allows shipping option updates | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/checkout-session-shipping-options-update-param): Checkout Sessions now support updating `shipping_options` after creation. This provides greater flexibility for dynamically customizing shipping options available to customers during the checkout process.
- [Expanded availability of Account KYC data | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/availability_of_additional_kyc_data): Stripe now provides read-only access to additional Account KYC fields for all platforms, regardless of the `requirement_collection` value. These fields include various company and individual details, enhancing data availability for compliance and verification.
- [Payment Methods won't allow modifying fields for Naver Pay after the object is first created | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/naver-pay-payment-method): Stripe PaymentMethods no longer allow modification of Naver Pay parameters after the object is initially created. These parameters can only be set during the creation of a PaymentMethod object.
- [Adds new error code for failures with the Setup Intents API using mobile wallets | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/terminal-mobile-wallets-setup-intents-error-code): A new error code, `setup_intent_mobile_wallet_unsupported`, is now available when a SetupAttempt fails due to a mobile wallet payment method. This allows developers to specifically identify and handle failures related to mobile wallets in the Setup Intents API.
- [Adds custom UI mode to Checkout Sessions | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/add-checkout-session-custom-ui-mode): Stripe Checkout Sessions now support a `custom` ui_mode, enabling integration with Elements. This new mode allows developers to build custom checkout pages using Elements while leveraging the Checkout Sessions API for tax, discounts, shipping, and currency conversion management.
- [Adds permissions parameter to Checkout Sessions | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/cs_add_checkout_session_permissions): The `permissions` parameter has been added to Stripe Checkout Sessions, allowing specific properties like `update_shipping_details` to be server-only. This enhances control over shipping detail updates and enables custom shipping address validation.
- [Adds presentment details for Adaptive Pricing | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/add_presentment_details): Stripe Checkout Sessions now include a `presentment_details` object for Adaptive Pricing. This object provides information about the currency and amount presented to customers, maintaining Checkout Session currency consistent with the Stripe integration.
- [Adds support for the Satispay local payment method | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/satispay-lpm): Stripe now supports Satispay, a local wallet payment method, for single-use payments, allowing businesses in Italy to accept payments from EU buyers. This update impacts the REST API and various SDKs.
- [Replaces top-level price fields with improved price modeling on Invoice Items and Invoice Line Items | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/invoice-pricing-configurations): Stripe introduces a new polymorphic pricing concept for Invoice Items and Invoice Line Items, replacing the previous 'price' and 'plan' fields. This change unifies pricing object structures and moves unit amount data to a new 'pricing' field for future extensibility.
- [Adds optional items to Checkout Sessions and Payment Links | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/checkout_optional_items): Stripe Checkout Sessions and Payment Links now support optional items, allowing customers to add complementary products to their orders during checkout. This feature is configured using the 'optional_items' parameter in the respective APIs.
- [Adds support for last aggregation formula on meters | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/meters-last-agg-formula): Stripe Billing Meters now include a 'last' aggregation formula, which uses the value from the last event in a time range as the aggregate for that period. This provides more billing flexibility by allowing charges based on the final meter event within a billing cycle.
- [Replaces top-level tax-related properties with improved tax modeling on Invoices, Invoice Line Items, and Credit Note Line Items | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/invoice-tax-configurations): Stripe updates Invoices, Invoice Line Items, and Credit Note Line Items with a new 'taxes' concept for tax-related data, replacing top-level 'tax_rates' and 'tax_amounts' fields. A new 'total_taxes' property is also added to Invoice and Credit Note objects for aggregated tax information.
- [Adds a demographic information hash to the Persons API | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/add-us-cfpb-data-to-person): The Stripe Persons API now includes a 'us_cfpb_data' hash with ethnicity and race details, along with a self-identified gender field. This addition ensures compliance with Section 1071 of the Dodd-Frank Act for collecting demographic information from small business financing applicants.
- [Adds Affirm as a supported payment method for one-time invoices and subscriptions | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/affirm-send-invoice): Stripe now supports Affirm as a payment method for one-time invoices and subscriptions when using the 'send_invoice' collection method. Affirm can also be enabled on the Hosted Invoice Page for dynamic payment method displays.
- [Adds tax ID to Payment Method billing details | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/add-tax-id-to-billing-details): Stripe enhances its Payment Method billing details by adding a 'tax_id' field, which is required for buyers in Latin American countries transacting with sellers outside the region. This field is automatically collected by Checkout and the Payment Element, and must be handled by other integrations.
- [Adds a field explaining why refunds are pending | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/refund-pending-reason): The Stripe Refunds API now includes a 'pending_reason' field to explain why a refund is pending. Possible reasons include 'processing', 'insufficient_funds', and 'charge_pending', allowing users to identify and resolve issues more effectively.
- [Adds Pix to payment method configurations | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/add_pix_to_payment_method_configuration): Stripe's Payment Method Configurations API now supports Pix, a popular Brazilian payment method. This allows for dynamic display of payment methods to customers based on specific checkout scenarios.
- [Adds support for tax ID types in ten new countries | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/add-tax-ids): Stripe has expanded its tax ID support to ten new countries, including Aruba, Azerbaijan, and the Philippines. This allows for the collection, storage, and processing of tax ID types for customers in these regions across Checkout Sessions, Invoices, and Tax Calculations.
- [Adds registration date to the Accounts API | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/us_cfpb): The Stripe Accounts API now includes a 'registration_date' attribute within the 'company' object. This allows for specifying the business's incorporation or registration date directly via the API, which was previously only available in the Dashboard.
- [Adds provider to automatic tax | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/taxprovider): Stripe now allows the use of third-party tax providers to natively calculate tax across all automatic tax integrations. Users can install a third-party tax application and enable it in their automatic tax settings to leverage this feature.
- [Adds context field to event payload | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/additional-context-organization-events): A new 'context' field has been added to the Stripe Event object and delivered event payloads. This field helps identify the account that generated the event, particularly useful for organizations with multiple accounts and for handling Connect events.
- [Tax Registration API now supports twelve new countries | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/additional-tax-registration-countries): The Stripe Tax Registration API now supports twelve new countries, including India and the Philippines. This expansion allows businesses operating in or selling to these countries to manage their tax information through Stripe.
- [Adds South Korean payment methods to the Payment Method Configurations API | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/korea-payment-method-configuration): Stripe now supports managing South Korean payment methods through the Payment Method Configurations API. This enables programmatic enabling and disabling of payment methods like Kakao Pay, Naver Pay, and others for South Korean users.
- [Adds account capability for the Pix payment method for US-based sellers | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/adds-pix-capability-for-us-sellers): Stripe Connect users in the US can now request the 'pix_payments' account capability for connected accounts that have Brazilian buyers. This is recommended for US-based sellers with potential customers in Brazil.
- [Adds option to Checkout Sessions to let customers remove saved payment methods | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/checkout-payment-method-remove): Stripe Checkout Sessions now include an option to allow customers to remove saved payment methods. This is controlled by the 'saved_payment_method_options[payment_method_remove]' parameter when creating a Checkout Session.
- [Adds capture method option to Satispay payments | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/satispay-capture-method-option): Stripe now allows specifying the 'capture_method' for Satispay payments. This change benefits integrations that supply capture methods on a per-payment-method basis.
- [Adds balance types to the Balance Transactions API | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/add-balance-type-to-balance-transactions): The Stripe Balance Transactions API has been updated to include a 'balance_type' field. This field categorizes transactions by balance type, such as issuing, payments, and refund_and_dispute_prefunding, to speed up balance reconciliation.
- [Adds simulated S700 device type to Reader API | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/simulated-s700-device-type): The Stripe Reader API now supports a simulated S700 device type. This allows developers to test and develop applications simulating Terminal payments without needing physical hardware.
- [Adds support for setting up future usage of Naver Pay in Checkout Sessions | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/naver-pay-update): Stripe Checkout Sessions now support setting up future usage for Naver Pay. This enables customers to save their Naver Pay details for subsequent payments.
- [Adds support for WeChat Pay for Setup Intents | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/setup-intents-wechat-pay): Setup Intents now include support for WeChat Pay as a payment method option. This allows for the creation of Setup Intents for off-session recurring payments using WeChat Pay.
- [Adds more flexibility for how you manage subscription end-of-period cancellations | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/cancel-at-enums): Stripe introduces new cancel_at enum values, 'min_period_end' and 'max_period_end', for subscriptions with flexible billing. These values provide more flexibility in managing end-of-period cancellations, and the 'cancel_at_period_end' parameter is now deprecated.
- [Adds support for WeChat Pay and Affirm on Terminal | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/terminal-wechat-pay-and-affirm): Stripe Terminal now supports WeChat Pay and Affirm for in-person payments on smart readers. Integrations can collect these payments by including additional fields on the payment_method_details and can specify a return_url for non-card payments in server-driven integrations.
- [Reintroduces billing thresholds | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/reintroduce-billing-thresholds): The billing_thresholds parameter, previously deprecated, is now available again for use in subscriptions and invoicing API versions starting from 2025-03-31.basil. This reintroduces functionality for managing billing thresholds.
- [Adds refund and dispute prefunding balances to the Balance API | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/add-refund-and-dispute-prefunding-to-balances): The Balance API has been updated to include refund and dispute prefunding balances. This new 'refund_and_dispute_prefunding' field provides visibility into available and pending amounts for future refunds and disputes.
- [Extracts sex and place of birth from government-issued ID documents | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/extract-sex-and-place-of-birth): Stripe's Identity API now extracts sex and place of birth from government-issued ID documents, adding 'sex', 'unparsed_sex', and 'unparsed_place_of_birth' fields to the Verification Report. This is useful for platforms needing this information for KYC compliance.
- [Replaces tax association status fields | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/flatten-tax-association): The Tax Association resource now replaces the 'status' and 'status_details' parameters with 'tax_transaction_attempts'. This change requires an update to integrations that use the previous fields to accommodate the new parameter.
- [Adds network decline codes for PayPal refunds | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/paypal_refund_network_decline_code): Stripe now provides network decline codes for PayPal refunds through the 'network_decline_code' field within 'destination_details' on a Refund object. This helps users understand the specific reasons why PayPal declines a refund.
- [Adds metadata field on Tax Calculation line items | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/add-metadata-on-tax-calculation-line-item): A metadata field has been added to line items within the Tax Calculation API. This optional field allows users to store arbitrary data associated with each line item when creating tax calculations.
- [Adds the ability to migrate subscriptions to flexible billing mode | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/migrate-subscription): Stripe now allows existing subscriptions to be migrated to a flexible billing mode using a new '/v1/subscriptions/:subscription/migrate' method. The 'billing_mode_details.updated_at' field tracks the timestamp of this migration.
- [Renames Payment Intent field for linking tax calculation | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/rename-async-workflows): The 'async_workflows' parameter in Payment Intents has been renamed to 'hooks'. This change affects participants of the 'payment_intent_with_tax_api' private preview who need to update their integrations to use the new parameter name.
- [Updated validation errors for redaction jobs to specify affected objects | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/redaction-jobs-validation-error-erroring-object): Validation errors for redaction jobs now provide more specific information by including the 'id' and 'object_type' of affected objects. Integrations using the 'erroring_object' field should be updated to expect these new fields.
- [Adds two new Connect embedded components for Disputes | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/disputes-embedded-components): Two new Connect embedded components for Disputes are now available: 'Disputes for a payment' and 'Disputes list'. These components offer modular tools for connected accounts to manage disputes efficiently.
- [Verification Sessions can now collect verification information for a related Person | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-06-30/identity-related-person): Verification Sessions can now collect verification information for a related Person, allowing Connect platforms to gather necessary documents or proof-of-liveness for connected accounts during onboarding. The 'related_person' parameter associates the session with the correct person.
- [Adds optional filter by status when listing Financial Accounts | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-06-30/financial-accounts-status-filter): An optional 'status' filter has been added to the FinancialAccounts API for listing. This allows users to filter financial accounts by their status, either 'open' or 'closed', making it easier to identify active or inactive accounts.
- [Adds the ability to provide proof-of-address documents for connected accounts | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-06-30/accounts-proof-of-address): Platforms can now submit proof-of-address documents when creating or updating accounts using the 'proof_of_address' parameter. This helps meet address validation requirements for connected accounts.
- [Adds support for collecting card details and confirming Payment Intents to server-driven Terminal integrations | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-06-30/terminal-server-support-cards-payments): Server-driven Terminal integrations now support collecting card details and confirming Payment Intents via the Terminal Reader API. New action types 'collect_payment_method' and 'confirm_payment_intent' have been added, along with the 'terminal.reader.action_updated' event.
- [Adds new plan types for Japan installments | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-06-30/add_jp_installments_plan_types): New plan types, 'bonus' and 'revolving', have been added to the 'type' parameter for card installment plans in Japan. This expands options beyond 'fixed_count' for installment payments, supporting deferred bonus payments and revolving balances.
- [Adds Visa compliance disputes | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-06-30/visa-compliance-disputes): Stripe now supports Visa compliance disputes, allowing users to identify them via the payment_method_details.card.case_type parameter and acknowledge network fees when contesting. This update includes the 'visa_compliance' value in enhanced_eligibility_types and requires acknowledging the fee to submit evidence.
- [Adds a new event type for Payout Method updates | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/payout-method-updated-webhook-event): A new event type, v2.money_management.payout_method.updated, is introduced for the Payout Methods v2 API. This event triggers when payout method credentials are updated, enabling systems to stay synchronized with the latest payout method information and react to changes in fields like bank_account_type.
- [Adds submission method to dispute evidence details | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-06-30/add-submission-method-to-disputes-evidence-details): The Disputes API now includes a submission_method field within evidence_details. This allows users to determine whether dispute evidence was submitted manually or through Smart Disputes, providing better insight into dispute resolution processes.
- [Adds support for saving Klarna payment methods | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-06-30/klarna_saved_payment_methods_preview): Stripe now supports saving Klarna payment methods for future use, enabling both on-session and off-session charging. This feature can be utilized through Stripe Billing or direct API integrations with Payment Intents and Setup Intents for subscriptions and on-demand payments.
- [Adds support for saving Klarna payment methods | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-06-30/klarna-saved-payment-methods): Support for saving Klarna payment methods for future charging, both on-session and off-session, is now available. This integration can be managed via Stripe Billing or directly with Payment Intents and Setup Intents, facilitating subscriptions and faster on-demand payments.
- [Consolidates billing mode configuration across Billing products | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-06-30/billing-mode-hash): The billing_mode parameter and field format have been unified across all billing products, now using a consistent object with a 'type' field instead of a string. The billing_mode_details field is consolidated into the main billing_mode object, requiring integration updates for users of this parameter.
- [Adds BUUT as a supported bank when using iDEAL | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-06-30/ideal-buut-support): iDEAL payments now support the bank BUUT, allowing users to specify it when using iDEAL with Payment Intents and Setup Intents. This expands the available bank options for iDEAL transactions.
- [Adds support for deactivating configurations in Accounts v2 | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/v2_accounts_configuration_deactivation): Accounts v2 now supports deactivating and reapplying configurations, allowing for better management of user representations in Stripe. A new 'applied' field indicates a configuration's status, differentiating between active and deactivated states.
- [Adds more flexible schedules for monthly and weekly payouts | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-06-30/flexible-schedules-payouts): Payout schedules for accounts are now more flexible, with options to specify multiple payout days per month using monthly_payout_days or per week using weekly_payout_days. This provides greater control over when payouts are received.
- [Adds billing mode for more flexible subscriptions behavior | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-06-30/billing-mode): A new billing_mode parameter is introduced to enable more flexible subscription behavior, with 'flexible' mode offering accurate proration and proportional discount application. This mode also suppresses zero-amount line items and bills metered usage based on the price at the time of reporting.
- [Adds support for crypto payment method | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-06-30/crypto-payment-method): Stripe now supports the crypto payment method type in the Payment Methods API for US-based accounts. This allows businesses to accept crypto payments that settle as fiat currency in their Stripe balance.
- [Adds the ability to provide proof-of-address documents for connected accounts in v2 APIs | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-06-30/accounts-api-v2-proof-of-address): Connect platforms can now submit proof_of_address documents for connected accounts using v2 APIs to meet address validation requirements. This feature helps demonstrate physical presence and ensures compliance with product address validation rules.
- [Adds Account Links v2 API support for connected accounts created using the Accounts v2 API | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/enable-v2-account-links-api-for-connect): Account Links v2 API now supports connected accounts created with the Accounts v2 API, including additional configurations like merchant and customer. An optional collection_options parameter allows specifying requirements to be collected, and the v2.core.account_link.completed event is renamed to v2.core.account_link.returned.
- [Adds validation for active financial addresses to Outbound Payments and Transfers | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/add-financial-address-requirement): Outbound payments and transfers now validate for active financial addresses, returning a financial_address_creation_required error if one is needed. This prevents silent failures and ensures compliance with regulations requiring outbound transactions to originate from an active FinancialAddress.
- [Adds transaction ID to Charges for Cash App | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/add-cashapp-transaction-id-to-charges): The Cash App transaction_id property is now added to the Charge object under payment_method_details. This allows users to easily access and reconcile transactions made through Cash App directly within the Charge object.
- [Adds support for payment line items to incremental authorization | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/payment-line-items-increment-authorization): Support for payment line items is now available when incrementing an authorization for payments. This enhancement allows integrations using incremental authorization to also leverage payment line items for more detailed transaction tracking.
- [Adds support for the America/Coyhaique time zone | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/america_coyhaique_timezone): The America/Coyhaique time zone is now supported and can be specified anywhere in the API where a timezone value is accepted. This addition expands the available timezone options for reporting and other timezone-dependent operations.
- [Adds Smart Disputes to the Disputes API | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/adds-smart-disputes): Smart Disputes are now integrated into the Disputes API, allowing users to view the availability of the smart_disputes hash on a Dispute object. This enables users to decide between manual dispute countering or utilizing Smart Disputes for automatic management.
- [Enhances Checkout for app-to-web purchases | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/checkout-origin-context): Checkout Sessions can now indicate if they are part of an app-to-web purchase by setting the origin_context to 'mobile_app'. This optimizes the checkout flow for mobile browser interfaces in certain countries, linking to a Stripe-hosted payment page from iOS apps.
- [Adds support for disabling future usage of Pix in Checkout Sessions | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/disable-future-usage-of-pix-in-checkout-sessions): Users can now set setup_future_usage to 'none' for Pix payment method options in Checkout Sessions. This explicitly indicates that the Pix payment method is not intended for future use, ensuring it's only utilized for the current transaction.
- [Adds a new value to payment review closed reasons | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/add-new-enum-value-to-review-close-reasons): Stripe has introduced two new enum values, payment_never_settled and acknowledged, for the Review object's closed_reason. The payment_never_settled value provides a more specific reason for automatic review closure due to issuer bank declines, while acknowledged indicates a user manually closed the review. This change is considered breaking due to potential integration issues with handling new enum values.
- [Adds a new value to payment review closed reasons | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/add-new-enum-to-payment-review-close-reason): Stripe has introduced two new enum values, payment_never_settled and acknowledged, for the Review object's closed_reason. The payment_never_settled value provides a more specific reason for automatic review closure due to issuer bank declines, while acknowledged indicates a user manually closed the review. This change is considered breaking due to potential integration issues with handling new enum values.
- [Adds support for ad-hoc products and prices when creating Payment Links | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/ad-hoc-prices-for-payment-links): Stripe now supports creating ad-hoc products and prices directly when generating Payment Links. By using the price_data parameter within line_items, users can create a new Price and a Payment Link in a single API request, eliminating the need for two separate calls. This streamlines the process of setting up one-time payment links.
- [Adds a duration parameter for schedule phases | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/add-schedule-phase-duration): Stripe has introduced a new duration parameter for subscription schedule phases, allowing for time-based durations (day, week, month, year) to support mixed interval subscriptions. The iterations parameter is now deprecated as duration replaces its functionality. This change enables more flexible configuration of subscription schedule lengths.
- [Adds support for quantity adjustment to the Customer Portal Configuration API | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/customer-portal-subscription-update-quantity-limits): Stripe has added the adjustable_quantity parameter to the products field within the Customer Portal Configuration object. This allows programmatic control over the quantity customers can modify on a Customer Portal page, offering more flexibility than the previous Dashboard-only configuration. This enhances the ability to manage subscription updates for customers.
- [Adds support for accepting Apple's Tap to Pay on iPhone Terms and Conditions on the web | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/terminal-onboarding-links): Stripe now supports accepting Apple's Tap to Pay on iPhone Terms and Conditions via the web through a new Terminal onboarding link resource. This feature allows for the generation of a redirect URL to facilitate the acceptance of these terms on the web. It simplifies the onboarding process for merchants using Tap to Pay on iPhone.
- [Adds UPI support to the Subscriptions and Invoices APIs | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/cs-upi-pmo-subscription-support): Stripe now supports UPI (Unified Payments Interface) for Subscriptions and Invoices APIs, allowing customization of UPI mandates through the upi payment_method_options. This enables businesses to configure details like description, expiration date, and maximum amount for UPI eMandates, offering greater control over how mandates appear to customers. This feature is available in public preview.
- [Adds support for payment line items to multicapture | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/payment-line-items-multicapture): Stripe now supports adding payment line items when using the multicapture feature. This allows integrations that utilize multicapture to also send line item details associated with a payment. Including line item data can lead to cost savings, improved payment reconciliation, and better authorization rates, depending on the payment method.
- [Increases payment line items limit to 200 | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/increase-payment-line-items-limit-to-200): Stripe has increased the limit for payment line items to 200. This enhancement allows integrations using payment line items to include up to 200 individual line items per payment. This change is available in public preview and benefits integrations that require detailed itemization.
- [Renames the parameter for custom settlement timing on the Balance Settings API | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/balance-settings-delay-days-rename): Stripe has renamed the delay_days parameter in the Balance Settings API to delay_days_override. This change clarifies the distinction between Stripe's default settlement timing and a platform's requested override for custom settlement timing. Platforms can now explicitly set a custom delay for when charge funds become available.
- [Adds support for new tipping currencies to the Terminal Configuration object | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/add_terminal_tipping_currency_aed_bgn_huf_chf_ron): Stripe adds support for new tipping currencies (AED, BGN, HUF, RON) to the Terminal Configuration object. This allows merchants to configure their Terminal readers to accept tips in these local currencies. The new parameters enable tipping in the United Arab Emirates, Bulgaria, Hungary, and Romania.
- [Adds support for Invoice Rendering Templates on Checkout and Payment Links | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/checkout-payment-link-invoice-rendering-templates): Stripe now supports Invoice Rendering Templates for Checkout and Payment Links by adding a new template parameter to the invoice_creation settings. This allows users to apply custom templates when generating post-payment invoices for Checkout sessions and Payment Links. This enhances the branding and customization options for invoices.
- [Updates schedule customization for weekly and monthly payouts | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/payout_schedule_customization_on_balance_settings): Stripe updates schedule customization for weekly and monthly payouts through the Balance Settings API, allowing for more precise scheduling. The fields monthly_anchor and weekly_anchor are renamed to monthly_payouts_days and weekly_payouts_days respectively, enabling configuration of multiple payout days per week or month. This change is breaking and requires integration updates.
- [Adds helpers to cancel subscriptions for billing periods with mixed intervals | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/cancel-at-enums): Stripe introduces new enum values, min_period_end and max_period_end, for canceling subscriptions with mixed intervals. These values simplify scheduling cancellations at the earliest or latest end of a billing period, respectively. The existing cancel_at_period_end behavior is updated for mixed intervals, and developers need to adjust integrations to use the new enums or explicit timestamps.
- [Adds Connect embedded component for Instant Payouts promotion | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/instant-payouts-promotion-embedded-component-ga): Stripe introduces a new Connect embedded component designed to increase Instant Payout conversion for connected accounts. This component displays available funds for instant payout and provides a call-to-action for initiating the payout. It aims to improve user experience and encourage the use of Instant Payouts.
- [Adds Connect embedded component for Instant Payouts promotion | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/instant-payouts-promotion-embedded-component): Stripe introduces a new Connect embedded component to boost Instant Payout conversion for connected accounts. The component highlights the amount available for instant payout and prompts users to initiate the process. This feature is available in public preview and aims to simplify and encourage the use of Instant Payouts.
- [Adds support for the NZ BECS Direct Debit local payment method in Checkout and Payment Links | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/nz-bank-account-checkout-payment-links): Stripe adds support for the New Zealand BECS Direct Debit payment method in Checkout and Payment Links. Businesses in New Zealand can now accept BECS Direct Debit payments from buyers within New Zealand. This expands payment options for businesses operating in the region.
- [Public preview for Payout Details embedded component | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/embedded-payout-details-public-preview): Stripe introduces a new payout_details embedded component to the Account Session API for public preview. This component allows connected accounts to view individual payout details without needing to access the full payouts list. It provides a more focused view of payout information.
- [Adds Payout Details embedded component to the Account Session API | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/embedded-payout-details): Stripe adds a new payout_details Connect embedded component to the Account Session API. This component enables connected accounts to view specific payout details, offering a more granular view than the standard payouts list. This feature is available in public preview.
- [Adds support for payment line items with overcapture | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/payment-line-items-overcapture): Stripe now supports adding payment line items when using the overcapture feature, available in public preview. This allows integrations using overcapture to send detailed line item data for overcapture transactions. Providing accurate line item information can improve cost savings, reconciliation, and authorization rates.
- [Adds PayPay settings to the Account object | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/add_paypay_payments_settings): Stripe has added two new fields, settings.paypay_payments.goods_type and business_profile.specified_commercial_transactions_act_url, to the Account object. These fields are required for onboarding connected accounts to PayPay, allowing Connect platforms to streamline the process.
- [Adds support for simulating card payments on Terminal readers | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/card-present-payment-method): Stripe now supports simulating card payments on Terminal readers, enhancing the testing capabilities for card presentment. This feature allows developers to test integrations without needing physical card interactions.
- [Adds support for PayNow on Terminal | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/terminal-paynow-api): Stripe Terminal now supports PayNow charges, enabling businesses to collect payments in-person using PayNow on smart readers. This integration is achieved by adding new fields to the payment_method_details parameter.
- [Adds a Charge transaction ID for several payment methods | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/transaction-id): The Charge object now includes a transaction_id field within payment_method_details for several payment methods, including Alma, Amazon Pay, and Kakao Pay. This allows for easier identification and tracking of payments using external transaction IDs.
- [Adds a display name to the FinancialAccount object | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/financial-account-display-name): A new display name field has been added to the FinancialAccount object, allowing users to specify a name for their financial accounts. This name is utilized by the Stripe Dashboard and embedded components for labeling purposes.
- [Adds support for listing a payment method's mandates | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/mandates_listing_support): Stripe has improved mandate listing by introducing the latest_active_mandate property on PaymentMethod and a Mandates List endpoint. These enhancements provide more consistent access to mandate information, simplifying workflows.
- [Adds support for MXN currency in Terminal tipping configuration | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/terminal-tipping-configuration-mxn): Stripe Terminal now supports MXN currency for its tipping configuration. This allows businesses in Mexico to set up on-reader tips using Mexican Pesos as the local currency.
- [Adds the number of installments for Alma payments to Charge objects | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/alma-installments): The Charge object now includes the number of installments for Alma payments via a new installments property. This allows for tracking Alma payments based on the number of installments selected by the customer.
- [Adds Android APK for Terminal to purpose of file uploads | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/terminal-android-apk-file-purpose): The Files API now recognizes 'terminal_android_apk' as a valid file purpose. This change specifically impacts documentation and does not affect existing usages of this file purpose.
- [Additional properties on PaymentRecord and PaymentAttemptRecord | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/payment-records): The PaymentAttemptRecord and PaymentRecord resources now include additional properties for amounts (amount, amount_authorized, amount_refunded) and processor details. The top-level payment_reference property has been removed and replaced by processor_details.custom.payment_reference.
- [Adds a name field to the customer portal configuration object | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/customer-portal-config-name): A new name field has been added to the customer portal configuration object and related APIs. This field allows for internal organization of customer portal configurations and is not visible to customers.
- [Adds the ability to attest to the authorized company representative for Accounts v2 | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/v2-representative-declaration): Stripe Accounts v2 now allows recording the attestation of an authorized company representative through new parameters for identity.attestations. These include representative_declaration.ip, representative_declaration.date, and representative_declaration.user_agent.
- [Adds support for Dispute Preventions | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/add-preventions-to-dispute): Stripe now supports Dispute Prevention through the API by adding a new 'prevented' status and 'resolution' and 'block' case types. This enables blocking or resolving disputes before they become formal chargebacks, potentially lowering costs.
- [Adds support to include the IOF tax in the amount for Pix payments | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/pix-payments-iof-tax): The Pix payment method now supports including the IOF tax within the payment amount via the new 'amount_includes_iof' parameter. This allows businesses to choose whether to absorb or pass the IOF tax to the customer.
- [Adds support for admin menu passcodes on the Terminal Configuration object | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/terminal-configurable-admin-menu-passcode): Stripe Terminal now supports setting an admin menu passcode on the Terminal Configuration object. This allows users to set and retrieve a custom passcode for their Terminal smart reader's admin menu.
- [Adds excluded payment method types to the Payment Intents API | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/cs_add_excluded_payment_method_types_pi): The Payment Intents API now includes an 'excluded_payment_method_types' field. This allows developers to exclude specific payment methods from being displayed or used on a per-transaction basis.
- [Adds support for paying out to Financial Accounts v2 | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/add-payout-method-to-payouts): Stripe now supports creating payouts to Financial Accounts v2 by using the new 'payout_method' parameter. The value passed must be the ID of the financial account to which the payout should be made.
- [Nests the Balance Settings request object under a new Payments parameter | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/balance-settings-nested-in-payments-field): The Balance Settings request and response objects have been updated to nest under a new, required top-level 'payments' parameter. This change clarifies that these settings apply exclusively to the Payments Balance and is a breaking change for API version 2025-08-27.preview and later.
- [Adds support for invoice items metadata and period in subscriptions and schedules | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/add_invoice_items_metadata_and_period): Support for customizing metadata and period for one-off invoice items in subscriptions and schedules has been added. This allows direct attachment of metadata and specification of custom period start and end dates, overriding default billing cycles.
- [Makes CVC optional when presenting a payment method on a simulated reader | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/make-cvc-optional): The CVC field is now optional when presenting a payment method on a simulated reader via the 'present_payment_method' card object. This change simplifies testing by removing the requirement to enter a CVC.
- [Add the payout_method field as a property on the Payout object | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/payout-payout-method): Stripe has added the payout_method field as a property to the Payout object, which now indicates the v2 Financial Account that received the payout. This change impacts how payout information is returned and requires an API version upgrade to include the new field.
- [Adds the ability to update the metadata and display name of a Financial Account | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/update-financial-account): Stripe now allows updating the metadata and display_name fields for Financial Accounts, which were previously immutable after creation. This enhancement provides greater flexibility in managing and differentiating Financial Accounts through the API.
- [Adds support for custom expiration dates to Issuing virtual cards | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/issuing-custom-expiration-dates): Stripe Issuing now supports custom expiration dates for virtual cards through the API. Developers can specify the expiration month and year when creating virtual cards, offering more control over card validity periods.
- [Adds support for filtering by event type to Events v2 | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/v2-events-api-filtering): The Events v2 API now supports filtering events by type using the new types parameter, and the object_id parameter has become optional. This update enhances the ability to retrieve specific events more efficiently.
- [Adds support for microdeposits to US Bank Accounts | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/microdeposits-us-bank-accounts): Stripe has introduced API support for microdeposits to US Bank Accounts, including endpoints for sending and confirming them. A new verification field provides details and status for the bank account verification process.
- [Adds new error codes for failures when creating Payment Methods from Financial Connections Accounts | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/financial-connections-payment-method-error-codes): New error codes, financial_connections_account_pending_account_numbers and financial_connections_account_unavailable_account_numbers, are now provided for failures when creating Payment Methods from Financial Connections Accounts. These codes help differentiate between retriable errors and those requiring user intervention.
- [Adds customer portal configuration trial behavior | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/customer-portal-trial-behavior): Stripe's Customer Portal now allows configuration of trial behavior during subscription upgrades or downgrades. Users can choose whether trials continue or end when a subscription is modified, offering more flexibility than the previous behavior where all trials ended.
- [Adds a documented reason for Klarna chargeback losses to Disputes API | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/chargeback-loss-reason): The Disputes API now includes a chargeback_loss_reason_code field for Klarna chargeback disputes. This provides a documented reason for losses, enabling users to analyze and strategize to reduce future chargeback losses.
- [Adds specific descriptions for risk requirements during legal, PEP, and sanctions review | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/expanded-risk-requirement-descriptions): Stripe has updated risk requirement descriptions for legal, PEP, and sanctions reviews, introducing new error codes and resolution paths. This change categorizes previously generic inquiries into specific risk assessments, requiring integration updates for handling these new requirements.
- [Adds support for business and individual names on Customers | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/customer-business-individual-names): Stripe Customers API now supports business_name and individual_name fields, allowing for the storage of both types of names. When creating or updating a Customer without a specific name, the API prioritizes and sets either the business_name or individual_name.
- [Updates default behavior for saved payment methods in Elements with Checkout Sessions | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/custom-checkout-saved-payment-method-defaults): Stripe Elements with Checkout Sessions now automatically enable saved payment method collection and redisplay by default. This simplifies integration by removing the need for explicit client-side configuration when a customer ID is passed or when payment method saving is enabled.
- [Adds additional enum values for Radar manual reviews | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/radar-manual-review-enum): Stripe Radar manual reviews now include additional enum values for the closed_reason field: 'acknowledged' and 'payment_never_settled'. These new values accommodate asynchronous bank debit flows and require integration updates if the enum is handled directly.
- [Moves platform-specific identity fields to a default profile for Accounts | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/moving-identity-fields): Platform-specific identity fields (doing_business_as, url, product_description) have been moved from the identity hash to the new defaults.profile hash in the Accounts v2 object. Integrations using API version 2025-09-30.clover or later must update to reference these fields in the new location.
- [Adds per-currency minimum balances for automatic payouts on the Balance Settings API | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/minimum-balance-by-currency-on-balance-settings): The Balance Settings API now includes a minimum_balance_by_currency parameter for automatic payouts. This allows platforms to retain per-currency minimums on connected accounts, helping to prevent negative balances from refunds, disputes, or fees.
- [Adds the ability to itemize proration discount amounts | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/itemize-proration-discount-amounts): Stripe now allows itemizing proration discount amounts when creating subscriptions, subscription schedules, quotes, checkout sessions, or preview invoices. This feature, enabled via the proration_discounts parameter, provides a more detailed breakdown of gross and net amounts.
- [Adds a new error code for business type validations | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/business-type-error-code): A new error code, unsupported_business_type, has been added to the Accounts, Capabilities, Persons, and Bank Accounts APIs. This code is returned when a business type is not supported in the merchant's country, requiring updates for Connect integrations that handle these error codes.
- [Changes the set of decline codes used for Alma, Amazon Pay, Billie, Satispay, and South Korean payment methods | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/lpm-descriptive-decline-codes): Stripe has introduced more granular decline codes for Alma, Amazon Pay, Billie, Satispay, and South Korean payment methods. These updated codes provide more specific reasons for payment declines in the last_payment_error.decline_code field, necessitating integration updates if the field is relied upon.
- [Adds support for collecting business and individual names in Checkout Sessions | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/checkout-name-collection): Checkout Sessions now support the name_collection parameter, allowing businesses to collect business and individual names as optional or required fields. This enhances customer data collection during the checkout process.
- [Adds Japan-specific fields to the Terminal Locations API | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/add-japan-fields-to-terminal-locations): The Stripe Terminal Locations API now includes Japan-specific fields, such as address_kana and address_kanji, for creating locations associated with readers in Japan. These new fields replace the standard address field for Japanese locations.
- [Adds support for custom BBPOS WisePad 3 splash screens | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/custom-bbpos-wisepad3-splash-screens): The Terminal Configuration API now supports custom splash screens for BBPOS WisePad 3 devices. This allows users to assign a custom default screen that displays when the reader is ready to accept payments.
- [Adds support for listing US and GB bank accounts | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/list-bank-accounts): Stripe has added new API endpoints to list US and GB Bank Accounts, with US accounts offering a filter for verification status. This update allows users to programmatically retrieve bank account information for these regions.
- [Adds the ability to exclude payment methods from Checkout Sessions and Payment Intents | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/exclude-payment-methods-checkout-sessions): Stripe now allows exclusion of specific payment methods from Checkout Sessions and Payment Intents using the `excluded_payment_method_types` parameter. This provides greater control over the payment methods presented to users for individual transactions.
- [Adds support for printing a second line on Issuing physical cards | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/issuing_card_second_line): The Issuing API now supports adding a second line of text to physical cards during creation via the new `second_line` parameter. This allows for additional custom information to be printed beneath the cardholder's name on physical cards.
- [Adds support for setting the capture method for specific payment methods with the Checkout Sessions API | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/checkout-capture-method-per-payment-method): Stripe Checkout Sessions now support configuring the `capture_method` on a per-payment method basis within `payment_method_options`. This allows for selective use of manual or automatic capture for different payment methods, enhancing flexibility for integrations.
- [Updating Balance Settings no longer requires specifying payment settings | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/payments-field-optional-for-update-balance-settings): Updating Balance Settings in Stripe no longer requires the `payments` field, making it optional. This change simplifies the process of updating balance settings when payment-specific configurations are not needed.
- [Removes iterations parameter for subscription schedules | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/remove-iterations): The `iterations` parameter has been removed from subscription schedules, and its functionality is now replaced by the `duration` parameter. Integrations must be updated to use `duration` for specifying subscription schedule phase lengths to avoid errors.
- [Updates risk levels for Issuing Authorizations to use standard values | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/risk-levels-issuing-authorizations): Stripe has updated the risk levels for Issuing Authorizations to use standard enum values, aligning them with other Stripe APIs. This change renames existing values and introduces new ones, requiring updates to integrations that reference these risk levels.
- [Adds pagination and updates fields for aggregrated Billing meter usage data | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/update-meter-usage-fields): Aggregated Billing meter usage data now includes pagination and updated field names for better consistency with other Stripe APIs. Key changes include renaming parameters like `start_time` to `starts_at` and nesting data within `rows` for improved data retrieval.
- [Adds the ability to update automatic tax, invoice creation, and invoice settings for Checkout Sessions | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/checkout-sessions-tax-and-invoice-settings): Stripe Checkout Sessions now support updating automatic tax, invoice creation, and invoice settings. This enhancement allows Connect platforms to shift tax liability and comply with regulations requiring the liable merchant to issue invoices.
- [Promotion Codes now reference Coupons using a polymorphic field for promotions | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/polymorphic-coupon): Promotion Codes now reference Coupons through a polymorphic `promotion` hash, which includes `promotion.coupon` and `promotion.type`. This change is a breaking change, requiring updates to how coupons are referenced for promotion codes.
- [Removes postal code for card payments in certain regions on Checkout and Payment Element | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/postal_code_in_card_form_for_non_us_countries): The postal code is no longer collected for card payments on Checkout and Payment Element in Canada, the United Kingdom, and Puerto Rico. Integrations relying on this field may need to adjust their billing address collection settings.
- [Adds a processing status to submitted stablecoin payments | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/stablecoin-payments-processing-status): Stablecoin payments confirmed via the crypto payment method now include a `processing` status when submitted to the blockchain. This provides clearer feedback during the transaction confirmation period before finalization.
- [Adds the ability to choose how you submit a dispute response | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/dispute-submission-method): Stripe now allows users to specify how they intend to submit dispute responses using the `intended_submission_method` parameter. This parameter offers options like `manual`, `prefer_manual`, `prefer_smart_disputes`, and `smart_disputes` to control response submission.
- [Adds cash as a value for the  crypto token currency enum | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/crypto-cash-value): The `crypto.token_currency` enum for Charges now includes 'cash' as a valid value. This allows for the identification of charges that utilized cash as the token currency.
- [Adds a testing developer assistant in Elements with Intents | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/stripe-js-developer-assistant): A testing developer assistant is now automatically rendered in Stripe Elements when using a sandbox environment. This assistant provides features like payment method autofill and customer location mocking to streamline development and testing.
- [Adds the Discount source property and removes the Discount coupon property | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/add-discount-source-property): The `Discount` object now includes a new `source` property and the `coupon` property is no longer auto-expanded. This change modifies the Discount object's schema and requires adjustments in how coupon details are retrieved.
- [Prevents reusing client secrets for Intents in certain states when initializing Elements | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/client-secret-reuse): Stripe Elements now validates client secrets to prevent reuse for Intents in states such as succeeded, canceled, or processing with non-detachable payment methods. This prevents the rendering of broken payment forms and ensures a smoother checkout experience.
- [Removes currency conversion field from Checkout Sessions | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/remove-checkout-session-currency-conversion-field): The `currency_conversion` field has been removed from Checkout Sessions. For sessions created before March 30, 2025, currency and amount information can be found in top-level fields, while newer sessions use the `presentment_details` field.
- [Adds support for configuring branding settings for Checkout Sessions | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/checkout-sessions-branding-settings): Stripe Checkout Sessions now support configuring branding settings through the `branding_settings` parameter. This allows for customization of logos, colors, fonts, and brand names to enhance the checkout experience.
- [Enables prebilling for subscriptions | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/subscriptions-prebilling): Subscriptions using flexible billing mode can now be prebilled for durations longer than their current billing period using the `billing_schedules` parameter. This enables greater flexibility in managing subscription billing cycles.
- [Restructures Smart Disputes recommended evidence field | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/restructure-smart-disputes-recommended-evidence): Stripe has restructured the recommended_evidence field for Smart Disputes, changing it from an array of strings to an array of arrays. This update requires integration adjustments for users relying on this field to determine necessary evidence for disputes.
- [Adds the unit label parameter to the product data hash | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/add-product-data-unit-label-preview): The unit_label parameter is now available in the product_data hash for Checkout Sessions, Payment Links, Payment Intents, and Invoices. This allows specifying a product's unit of measurement, which is required for Level 2/Level 3 card network programs.
- [Enables specifying units of measurement for Products | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/product-data-unit-label): The unit_label parameter is added to the product_data hash, enabling the specification of a product's unit of measurement. This is important for meeting card network Level 2/Level 3 program requirements when creating products in Checkout Sessions, Payment Links, Payment Intents, or Invoices.
- [Adds tax calculation provider to Tax settings | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/tax-calculation-provider): A new 'provider' property has been added to the tax_settings.defaults object. This allows users to specify whether Stripe or a third-party provider is used for tax calculations by default within their Stripe account settings.
- [Adds support for the MB WAY payment method | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/mb-way-payments): Stripe now supports the MB WAY payment method, a popular digital wallet in Portugal. Customers can use MB WAY by authorizing payments via a push notification in their app after providing their phone number.
- [Adds Outbound Setup Intents to create usable payout methods | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/outbound-setup-intents): The Outbound Setup Intents API has been introduced, providing a way to create and configure usable payout methods. This API facilitates the setup of credentials for outbound money movement, referred to as a Payout Method.
- [Adds account balance and payout settings with the Balance Settings API | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/balance-settings-ga): The Balance Settings API now allows platforms to customize how connected accounts manage their balance and payouts. Features include options for reclaiming negative balances, setting minimum payout balances per currency, scheduling payouts, and defining statement descriptors.
- [Adds support for PayPay as a local payment method | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/add-paypay-public-preview): Stripe now supports PayPay, a local payment method from Japan, for single-use payments. Businesses in Japan can accept PayPay payments from buyers through their Stripe integration.
- [Adds MB WAY to payment method configurations | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/mb-way-payment-method-configuration): MB WAY, a Portuguese local payment method, can now be enabled and configured within Payment Method Configurations. This allows for dynamic presentation of MB WAY to customers at checkout based on factors like location and conversion rates.
- [Adds the ability to upload your platform's terms of service agreement | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/upload-file-terms-of-service): Stripe now allows uploading a platform's terms of service agreement by setting the purpose parameter in the Files object to platform_terms_of_service. This facilitates specifying terms of service for issuer programs.
- [Adds a field for a Terminal reader's last connection timestamp | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/terminal-reader-last-seen): A new 'last_seen_at' field has been added to Terminal Readers. This field provides a timestamp indicating when a reader last connected to Stripe, enabling easier determination of device activity.
- [Adds support for tipping in Gibraltar pounds on Terminal readers | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/terminal-tips-gip): Terminal readers now support tipping in Gibraltar pounds (GIP). This is enabled by specifying 'tipping.gip' in the Configuration settings, allowing businesses to accept tips in the local currency.
- [Adds TWINT payment method options to Checkout Sessions | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/twint-checkout-sessions): The Checkout Sessions API now includes the payment_method_options.twint.setup_future_usage parameter. This allows users to specify that the TWINT payment method is not intended for reuse, overriding the top-level setup_future_usage parameter.
- [Adds new error code for missing verification data from connected accounts | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/accounts-verification-data-error): A new error code, 'verification_data_not_found', has been added to the requirements.errors array for Accounts. This code indicates that Stripe could not find specific data for a connected account, potentially due to incorrect entry or unavailability in registries.
- [Adds Payment Records and Payment Attempt Records | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/payment-records): Stripe has introduced Payment Records and Payment Attempt Records to report payments processed outside of Stripe. This enables features like subscriptions and invoices to work with external payments and aids in accounting and reporting.
- [Adds support for remote sellers in Taiwan to Stripe Tax | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/stripe-tax-taiwan-remote-support): Stripe Tax now supports Taiwan for remote businesses selling digital goods. This expands the Tax Registrations API coverage to include Taiwan, facilitating automatic tax calculation and collection.
- [Adds support for specifying payment method configurations to the customer portal | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/customer-portal-payment-method-configurations): Users can now specify their own Payment Method Configurations for Customer Portal Sessions. This allows for customized display of payment methods based on customer or payment scenario within the customer portal.
- [Updates to Payment Record APIs | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/payment-records-updates): The Payment Records API has been updated with the addition of the report_refund API method and pagination for the PaymentAttemptRecord list method. These updates allow for reporting refunds on off-Stripe payments and paginating through payment attempt records.
- [Adds a shareable payment portal link for Rechnung invoices | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/rechnung-payment-portal-url): A new 'payment_portal_url' field is now available for Rechnung invoices. This provides a shareable URL for customers to view and pay their invoices, serving as an alternative if the invoice email is not received or accessible.
- [Adds the ability to attest to an Account's authorized company representative | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/representative-declaration): Stripe now allows recording the attestation of an authorized company representative for an account. This involves specifying representative declaration details like IP address, date, and user agent, which is required in certain countries for verification.
- [Adds support for managing stablecoin payments with Payment Method Configurations | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/stablecoin-payments-pmc): Stripe now supports managing stablecoin payments alongside other payment methods through Payment Method Configurations. This allows for programmatic enabling and disabling of stablecoin payments within existing integrations without additional API endpoints.
- [Adds crypto network support for Solana | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/crypto-network-solana): Stripe has added support for the Solana network for crypto payments. This allows merchants to accept payments from Solana wallets, with Solana specified in the charge details.
- [Adds MB WAY payment method to Payment Links and Checkout Sessions | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/mb-way-payment-link-checkout-sessions): The Portuguese local payment method MB WAY is now available for use with Stripe's Payment Links and Checkout Sessions. Customers in Portugal can use MB WAY for EUR payments, with the option automatically appearing for eligible transactions.
- [Adds support for payment line items | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/payment-line-items): Stripe Payment Intents now support line items through the `payment_details` and `amount_details` parameters. This enables cost savings for commercial cards, facilitates reconciliation for customers, and can improve authorization rates for certain payment methods.
- [Adds support for retrieving and listing closed v2 Accounts | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/return-closed-v2-accounts): Stripe now allows retrieval and listing of closed v2 Accounts, introducing a `closed` field to the Account v2 object. While only limited, non-personally-identifiable information is returned for closed accounts, this enables better history tracking.
- [Adds the ability to exclude payment methods when using Setup Intents | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/exclude-payment-methods-setup-intents): The `excluded_payment_method_types` parameter has been added to SetupIntents, allowing users to exclude specific dynamic payment methods from transactions. This provides greater control over payment method selection during the setup process.
- [Adds support for collecting business and individual names on Payment Links | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/payment-links-name-collection): Stripe Payment Links now include a `name_collection` parameter, enabling the collection of business and individual names during checkout. These fields can be configured as optional or required to gather necessary customer information.
- [Adds Tax ID Element support to Customer Sessions | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/cs-add-tax-id-element-to-customer-session): Stripe has added Tax ID Element support to Customer Sessions, allowing for the secure collection and saving of customer tax identification numbers. This feature enables client-side tax ID management through the `tax_id_element` component within a Customer Session.
- [Adds support for using Payment Records with Invoices and Credit Notes | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/invoicing-payment-records): Stripe now supports attaching Payment Records to Invoices and creating Credit Notes against Payment Record refunds. This integration with third-party payment processors maintains accurate accounting records within Stripe.
- [Updates the category field of Credit Grants to be optional | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/credit-grant-optional-category): The category field for Credit Grants in Stripe is now optional. If omitted, Stripe defaults the category to 'paid', allowing for more flexibility in creating credit grants without impacting existing integrations.
- [Adds new error codes for the crypto wallet payout method | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/crypto-wallet-errors): Stripe has introduced three new error codes for the crypto wallet payout method when using OutboundSetupIntents API. These codes (`blocked_payout_method_crypto_wallet`, `unsupported_payout_method_crypto_wallet`, `limit_payout_method_crypto_wallet`) provide more specific error handling compared to previous generic errors.
- [Adds a webhook event type for Invoices that require a non-Stripe payment | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/invoice-payment-attempt-required-event): A new webhook event type, `invoice.payment_attempt_required`, has been added by Stripe. This event signals when a finalized invoice requires payment via a custom, off-Stripe method, allowing for automated processing and reporting.
- [Adds support for using Accounts v2 payment method billing details for Stripe Tax location | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/payment-method-location-source): Stripe Tax now uses Accounts v2 payment method billing details for location determination. The `location_source` enum on the Accounts v2 Customer Configuration now includes a `payment_method` value, prioritizing invoice, subscription, or customer configuration billing details.
- [Adds a webhook event type for updates to the balance settings for connected accounts | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/balance-settings-updated-webhook): Stripe has introduced a `balance_settings.updated` webhook event type. This event is triggered when the balance settings for a connected account are modified, allowing platforms to monitor and react to changes in these settings.
- [Adds blockchain transaction hash to stablecoin refunds | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/stablecoin-refunds-reference-details): Stripe's stablecoin refunds now include the blockchain transaction hash in the reference field of the crypto destination details. This allows users to easily track the specific blockchain transaction associated with a refund.
- [Adds tracking for which tax provider resolved a Customer location | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/tax-provider-customer-location): Stripe now tracks which tax provider resolved a customer's location by adding a `tax.provider` field to Customers. This field indicates whether Stripe or a third-party tax provider was used to determine the customer's location.
- [Adds Klarna reference parameters for line items in Payment Intents | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/klarna-line-item-reference): Stripe has added `reference` and `subscription_reference` fields for Klarna line items within Payment Intents. These optional parameters allow for the inclusion of specific transaction and subscription identifiers, improving Klarna's order tracking and customer support.
- [Adds a subscription reference to Klarna line items in Payment Intents | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/klarna-items-payment-intents): The `subscription_reference` field has been added to Klarna line items in the Stripe PaymentIntents API. This allows for the inclusion of a subscription reference number when processing payments with Klarna for individual line items.
- [Adds support for Customer Sessions for Mobile Payment Element and Customer Sheet | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/customer-sessions-mpe-customer-sheet): Stripe now supports Customer Sessions for the Mobile Payment Element and Customer Sheet, enabling customers to save payment methods more efficiently. Integrations are recommended to use Customer Sessions instead of ephemeral keys for saving payment methods.
- [Adds support for custom payment methods | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/custom-payment-methods): Stripe now supports custom payment methods, allowing users to create and manage payment methods processed outside of Stripe. This enables recording external transaction details within Stripe using custom Payment Methods and Payment Records, though they are not compatible with Payment Intents or Setup Intents.
- [Adds the ability to specify the capture method for card present payments with Payment Intents | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/card-present-capture-method): Stripe's Payment Intents now allow specifying the capture method for card present payments. You can choose between 'manual' capture after authorization or 'manual_preferred' which prioritizes manual capture but defaults to automatic if necessary.
- [PaymentMethods can now list payment methods for a customer account using Accounts v2 | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/v2-accounts-payment-methods): The Accounts v2 API now supports listing a customer's payment methods with new parameters: customer_account to specify the customer and allow_redisplay to control visibility in checkout flows. This brings parity with existing Customer's PaymentMethods API functionality.
- [Adds support for using a web browser to accept Apple's terms and conditions for Tap to Pay on iPhone | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/terminal-onboarding-links): Stripe introduces an Onboarding Link for Terminal, allowing users to accept Apple's Tap to Pay on iPhone Terms and Conditions via a web browser. This simplifies the onboarding process for this feature.
- [Adds support for PayPay to Accounts | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/paypay-connect): Connect platforms can now onboard connected accounts to PayPay, a popular Japanese payment platform. This requires providing additional information like goods_type and commercial_transactions_act_url, and requesting the paypay_payments Capability.
- [Adds a fraud warning for potentially compromised Issuing Cards | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/issuing-fraud-warnings): Stripe Issuing Cards now include a 'latest_fraud_warning' property to indicate if a card has been reported as compromised. This allows issuers to proactively cancel and reissue cards, helping to prevent fraudulent transactions.
- [Adds support for Konbini payments and Japanese statement descriptors in Accounts v2 | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/accounts-v2-konbini-payments): Accounts v2 now supports Konbini payments and Japanese statement descriptors, enabling connected accounts in Japan to offer Konbini as a payment method. New fields for merchant configuration and localized statement descriptors in kana and kanji are introduced.
- [Adds the transaction ID to iDEAL payment method details | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/ideal-transaction-id): The transaction ID for successful iDEAL payments is now available in the payment_method_details.ideal.transaction_id property for Charges, Payment Attempt Records, and Payment Records. This provides a reference for tracking iDEAL transactions.
- [Adds fraud risk assessments to Issuing Authorizations | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/fraud-risk-assessments-for-issuing-authorizations): Issuing Authorizations now include a 'risk_assessment.fraud_risk' property, providing Stripe's assessment of fraud likelihood. This feature, available with Advanced Fraud Tools, includes a risk level and score to help inform authorization decisions.
- [Adds MB WAY and TWINT to destination details for refunds | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/mb-way-twint-destination-details-for-refunds): Refunds for MB WAY and TWINT payment methods are now supported, with additional details available in the destination_details.mb_way and destination_details.twint fields. MB WAY refunds include reference and status properties for tracking.
- [Adds industry-specific transaction details and purchase data for cards and Klarna | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/industry-fields-cards-klarna): The Payment Intents API now supports industry-specific transaction details for car rentals, lodging, and flights. Additionally, Klarna payments can include supplementary purchase data for various trip types, insurance, and event reservations.
- [Adds filtering by creation date to Customer Balance Transactions lists | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/customer-balance-transactions-list-created): Customer Balance Transactions lists can now be filtered by creation date using the 'created' parameter with operators like gt, gte, lt, and lte. This allows for more granular retrieval of transactions within specific date ranges.
- [Adds health alerts for when events fail to generate | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/event-generation-failure-alert): Stripe now provides a 'v2.core.health.event_generation_failure.resolved' webhook event to notify users when issues with event generation for webhook endpoints are resolved. This helps in monitoring and troubleshooting webhook delivery problems.
- [Adds filtering by creation date to Invoice Payment lists | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/invoice-payments-list-created): Invoice Payments lists can now be filtered by creation date using the 'created' parameter with operators like gt, gte, lt, and lte. This enables more precise retrieval of invoice payments within specified date ranges.
- [Meter Usage Analytics adds support for filtering multiple tenants and dimension values | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/meter-usage-tenant-dimension-filters): The Meter Usage Analytics API now accepts arrays of strings for 'tenant_filters' and 'dimension_filters', allowing filtering across multiple tenants or dimension values in a single API call. This change requires updating existing integrations to use the array format.
- [Updates requirements collection parameters for Accounts v2 | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/accounts-v2-requirements-collection): Accounts v2 has updated its requirements collection parameters, replacing 'requirements.collector' with 'defaults.responsibilities.requirements_collector'. Enum values for 'requirements.entries[].reference.type' are also more specific, potentially requiring integration adjustments.
- [Adds the capabilty to hold EUR funds to Accounts v2 | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/account-v2-storer-config-eur): Accounts v2 now supports holding EUR funds in a Financial Account through a new Storer Configuration. This is specified in the 'storer.capabilities.holds_currencies.eur' field, expanding multi-currency capabilities.
- [Adds future requirements field to Accounts v2 | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/accounts-v2-future-requirements): The Accounts v2 API now includes a 'future_requirements' property alongside 'requirements'. This separates currently required information from information that will be needed later, simplifying the management of account capabilities.
- [Adds account and person tokens to Accounts v2 to securely transmit sensitive data | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/accounts-v2-tokens): Stripe has introduced account and person tokens for Accounts v2, allowing sensitive PII to be transmitted directly from a customer's browser using a publishable key. This enhances the security of handling personal information.
- [Adds support for Argentine ID types | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/argentine-id-types): Support for Argentine ID types, 'ar_dni' and 'ar_cuit', has been added to Accounts v2 and Persons. This allows for the collection and storage of these specific Argentine identification numbers to improve verification and compliance.
- [Adds support for Accounts v2 to accept the terms of service for storing stablecoins | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/stablecoin-fa-tos): Accounts v2 now supports accepting the terms of service for storing stablecoins via the 'crypto_storer' parameter in the 'identity.attestations.terms_of_service' hash. This is required when creating accounts that will store cryptocurrency.
- [Tax Associations now always return the list of attempted tax transactions | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/tax-assocation-transaction-attempts): Stripe Tax Associations now consistently return the list of attempted tax transactions, ensuring reliable access to this information. This change makes the tax_transaction_attempts property required, simplifying integrations by removing the need to handle potentially missing data.
- [Adds support for automatic tax transactions to Payment Intents | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/payment-intents-tax-support): Stripe Payment Intents now support automatic tax transaction commitment, eliminating the need for manual API calls after capture. This new integration includes a hooks.inputs.tax.calculation parameter and a TaxAssociation resource for streamlined tax reporting.
- [Adds Finom as a supported iDEAL issuer | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/ideal-payments-finom): Finom is now a supported issuer for iDEAL payments, allowing customers who bank with Finom to use their accounts for iDEAL transactions. No integration changes are required; Finom will automatically appear as an option for Dutch customers.
- [Subscriptions updated from the Customer Portal can now also modify their billing cycle anchor | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/customer-portal-billing-cycle-anchor): Customers can now modify the billing cycle anchor for their subscriptions when updating them via the Customer Portal. This provides greater flexibility in resetting billing dates during subscription updates, a feature configurable through Customer Portal Configurations.
- [Adds the ability to specify a payment method configuration in the customer portal | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/portal-payment-method-configuration): The Stripe Customer Portal now allows specifying which payment methods are available to customers through a new payment_method_configuration field. This enables better control over customer-facing payment options, aligning them with business requirements.
- [Thin events now include field changes on related objects | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/thin-events-changes): Thin events now include a 'changes' field, providing a before-and-after representation of modified fields on related objects. This simplifies webhook processing by offering direct insight into specific changes, aiding in audit logging and debugging.
- [Makes client secret optional for Financial Connections Sessions | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/financial-connections-client-secret): The client_secret property is now optional for Financial Connections Sessions, specifically when the ui_mode is set to 'hosted'. This change is backward compatible and does not affect existing integrations.
- [Adds Mollie as a supported iDEAL issuer | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/mollie-ideal-issuer): Mollie has been added as a supported issuer for iDEAL payments, expanding options for Dutch customers. This integration is automatic and requires no changes to existing iDEAL payment flows.
- [Adds support for handling tokenized bank account numbers | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-11-17/tokenized-account-numbers): Stripe now supports handling tokenized bank account numbers (TANs) through the API, providing details on expiration and status. New events and enum values help track account number changes and deactivated TANs for ACH payments and payouts.
- [Adds the ability to filter customer balance transactions by invoice | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/customer-balance-transations-list-invoice): The ability to filter customer balance transactions by invoice has been added, allowing users to retrieve transactions related to a specific invoice ID. This simplifies reconciliation and identification of adjustments for particular invoices.
- [Adds additional card payment method details to Payment Records | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/card-payment-method-details-payment-record): Payment Records now include additional card payment method details, such as authorization code, issuer, and network decline codes. These details, previously only on the Charge object, are now accessible for enhanced analysis of card payment data.
- [Adds generic error types for Payout Methods | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/generic-error-types-payout-methods): Generic error types, such as 'payout_method_cannot_be_updated', are now used for Payout Methods, replacing specific error codes. This simplifies error handling by providing a consistent set of codes across different payout method actions.
- [Adds the ability to update line items on existing Checkout Sessions with a custom UI | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/update-line-items): Line items on existing Checkout Sessions with a custom UI can now be updated, including their price, quantity, and metadata. This allows for more dynamic checkout flows, such as modifying shopping cart contents or applying promotional pricing.
- [Account Tokens no longer require identity information on creation | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/account-tokens-identity-optional): Account Tokens no longer require identity information upon creation, making the identity parameter optional. This change simplifies token creation when identity details are not immediately available.
- [Creating a Payout Method now triggers an event | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/payout-method-created-event): The creation of a Payout Method now triggers a new event, v2.money_management.payout_method.created. This event allows for better tracking of Payout Method objects, ensuring consistency in payout processing workflows.
- [Adds support for tracking transfers from connected accounts to financial accounts | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/transfers-to-financial-accounts): Stripe now supports tracking transfers from connected accounts to financial accounts, with these transactions appearing as Received Credits. The balance_transfer property on Received Credits includes new details to help reconcile these fund movements.
- [Connect platforms can now use Accounts v2 to manage connected accounts and customers | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/accounts-v2): The Accounts v2 API is now available for new Connect users, allowing a single Account object to represent connected accounts and customers. This streamlines management by unifying user identities, reducing duplicate data entry and KYC collection.
- [Adds the customer account property to v1 APIs for Accounts v2 interoperability | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/accounts-v2-v1-api-support): The customer_account property is now available in v1 API endpoints for Accounts v2 interoperability, enabling Connect platforms to reference payments collected from connected accounts or customers. This facilitates tracking and management of payments within the Accounts v2 framework.
- [Accounts v2 now always returns the responsibilities field when the defaults field is included | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/accounts-v2-responsibilities): When the 'defaults' field is included in Accounts v2 objects, the 'responsibilities' field is now always returned. This change, impacting existing public previews, requires updates to handle the presence of this field even when sub-fields are null.
- [Removes requested field from Accounts v2 capabilities hashes | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/accounts-v2-capabilities-remove-requested): The 'requested' field has been removed from the capabilities hash in Accounts v2. Users should now rely on the 'status' field to determine the state of a capability (active, pending, restricted, or unsupported).
- [Adds expected debit date for bank debit payments | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/expected-debit-date-on-charges): Stripe now includes an expected_debit_date for bank debit payments, available in payment_method_details for various direct debit methods. This feature aids in cash flow forecasting and customer communication by indicating when funds are expected to be debited from a customer's bank account.
- [Global Payouts adds support for 13 new countries for cross-border payouts | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/cross-border-payouts-new-countries): Global Payouts has expanded its support to 13 new countries, allowing recipients in these regions to create bank accounts and receive cross-border payouts. This update enhances the utility of Global Payouts and Accounts v2 for international transactions.
- [Enables expansion for invoice pricing details | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/expandable-price-details-price): Stripe now allows expanding the price_details.price hash on Invoice Line Items and Invoice Items, enabling direct retrieval of Price object details. This change reduces the need for separate API calls, providing more granular pricing information for invoices in a single request.
- [Accounts now support digital attestation for proof of registration and beneficial ownership verification | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/accounts-digital-attestation): The Accounts API now supports digital attestation for proof of registration and beneficial ownership verification. This feature allows authorized signers to electronically sign attestation agreements, streamlining onboarding and compliance for European regulations.
- [Adds support for the PayTo payment method | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/payto): Stripe has added support for the PayTo payment method, a real-time payment solution in Australia. Businesses operating in Australia can now accept both one-time and recurring payments from Australian buyers using PayTo.
- [Adds support for retrieving information about reserves | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/reserves-retrieve-api): A new public preview feature allows retrieving information about reserves, including their status and balance. The Reserves API provides programmatic monitoring of fund holds and releases on accounts, offering visibility into temporary fund unavailability and availability for payout.
- [Updates error codes for the Outbound Setup Intents API | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/outbound-setup-intents-error-codes): The Outbound Setup Intents API has updated its error codes to use more generic types, replacing credential-specific codes. This standardization improves consistency in error handling across different Payout Method types and supports future extensibility.
- [Adds support for 3D Secure versions 2.3.0 and 2.3.1 | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/3d-secure-version-support): Stripe now supports 3D Secure versions 2.3.0 and 2.3.1 for importing authentication results from external providers. This ensures compatibility with the latest EMVCo specifications, allowing successful import of authentication data that previously would have failed validation.
- [Adds alternative reference field to bank account and payout method resources | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/alternative-reference-field): A new alternative_reference property is now available for GbBankAccount, UsBankAccount, and PayoutMethod resources. This read-only property allows tracing Payout Methods back to their originating External Accounts, facilitating credential management without altering existing integration code.
- [Adds fingerprint property to card payout methods | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/card-payout-methods-fingerprint-property): The fingerprint property has been added to card hashes on Payout Method objects, providing a merchant-scoped unique identifier for cards. This helps in identifying multiple payout methods referencing the same physical card, aiding in tracking, deduplication, and fraud prevention.
- [Adds the ability to detach a PaymentIntent from an Invoice | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/detach-payment-from-invoice): Stripe introduces a new detach payment API method, allowing PaymentIntents to be detached from Invoices. This action makes the PaymentIntent available for other uses and returns the invoice to an unpaid state, offering greater flexibility in payment and reconciliation management.
- [Adds the ability to monitor reserve activity on Balance Transactions and reconcile Risk Reserved balance changes | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/monitor-reserve-activity-on-balance-transactions): New Balance Transaction type values, reserve_hold and reserve_release, have been added to track reserve activity. Additionally, a risk_reserved balance type is introduced to reconcile changes impacting the Risk Reserved balance, enhancing monitoring of fund holds and releases.
- [Adds the ability to relink deactivated Financial Connections Accounts | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/financial-connections-relink): The ability to relink deactivated Financial Connections Accounts is now available via the relink_options parameter in Financial Connections Sessions. This allows for the reconnection of accounts that have become inactive due to authentication issues or changes at the financial institution.
- [Removes the source type parameter when creating new Stripe balance payment methods | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/stripe-balance-remove-source-type): The source_type parameter is removed when creating new Stripe balance payment methods. Stripe now returns an error if this parameter is included, and existing methods are unaffected, requiring updates to code that specifies source_type during creation.
- [Adds the ability to opt out of strict arithmetic validation for Payment Line Items | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/loosen-arithmetic-validation-for-payment-line-items): Stripe now allows opting out of strict arithmetic validation for Payment Line Items on a per-request basis using the amount_details.enforce_arithmetic_validation parameter. This provides flexibility when line item amounts do not precisely match the total, with validation error details available in the response.
- [Adds OpenAPI artifacts containing v2 API endpoints | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/openapi-with-v2-apis): New versions of Stripe's OpenAPI specifications, covering both v1 and v2 API namespaces, are now available in the stripe/openapi repository. These unified files in JSON and YAML formats are intended for developers of third-party SDKs and custom Stripe clients for code generation.
- [Adds event type for updates on a line of credit when using Capital for Platforms | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/line-of-credit-event): A new event type, capital.financing_summary.line_of_credit_update, is introduced for platforms using Capital for Platforms. This event notifies platforms when line of credit terms for a connected account are updated, enabling them to maintain accurate financing information.
- [Global Payouts adds support for 15 new countries for cross-border payouts | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/cross-border-payouts-new-countries): Global Payouts now supports cross-border payouts in 15 additional countries, allowing recipients to create bank accounts and receive funds. This expansion enhances the reach and utility of Global Payouts and Accounts v2 for international financial transactions.
- [Reintroduces the ability to set an amount-off coupon's duration to forever | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/reintroduce-forever-amount-off-coupon): The ability to set an amount-off coupon's duration to 'forever' has been reintroduced. This restores functionality for creating and applying such coupons to subscriptions, invoices, quotes, and checkout sessions, which was previously deprecated.
- [Adds Adyen as an issuer for iDEAL payments | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/adds-adyen-as-an-issuer-for-ideal-payments): Adyen has been added as a supported issuer for iDEAL payments, allowing customers who bank with Adyen to complete payments through the integration. No changes are required for existing iDEAL integrations, as Adyen will automatically appear as an option for Dutch customers.
- [Adds PayPay onboarding parameters to the Accounts API | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/accounts-paypay-onboarding): Stripe's Accounts API now supports additional PayPay onboarding parameters, allowing complete PayPay configuration data to be provided programmatically when creating or updating connected accounts. This includes website accessibility settings, supplementary documentation files, and the ability to update the specified_commercial_transactions_act_url. This change enables a fully programmatic onboarding flow for PayPay payments in Japan.
- [Adds support for Polish NIP tax ID type | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/polish-nip-tax-id-type): Stripe now supports the Polish NIP (Numer Identyfikacji Podatkowej) tax ID type, designated as 'pl_nip'. This allows businesses to collect and store Polish NIP tax identification numbers for customers based in Poland, enhancing tax compliance. The 'pl_nip' type is available via the API and in the Dashboard for Checkout, invoices, and customer profiles.
- [Adds the top-up field to Treasury ReceivedDebit linked flows | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/treasury-received-debit-linked-flows-topup): The 'topup' property has been added to the 'linked_flows' hash within Treasury ReceivedDebits. This new property identifies the ID of the top-up that generated a received debit when funds are transferred from a Financial Account to a Stripe balance. This provides better traceability for balance transfers initiated through top-ups.
- [Changes currency mapping for Bulgaria from BGN to EUR | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/bulgaria-currency-mapping-bgn-to-eur): Stripe has updated the default currency mapping for Bulgaria from Bulgarian Lev (BGN) to Euro (EUR). This change affects Terminal tipping configurations, which will no longer support BGN and should be updated to EUR. The update aligns Stripe's currency handling with Bulgaria's official adoption of the Euro.
- [Adds the contact phone parameter to the Accounts API | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/accounts-contact-phone): The Accounts API now includes an optional 'contact_phone' parameter for Account resources and Account Tokens. This parameter allows for the specification of a default contact phone number in E.164 format when creating or updating accounts. The addition is optional and does not impact existing integrations.
- [Adds the ability to specify a company's registration date on Accounts v2 objects | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/accounts-v2-registration-date): The Accounts v2 object now includes a 'registration_date' field within the 'identity.business_details' hash. This field allows for the direct specification of a company's incorporation or registration date within the Accounts v2 object. This enhances the data available for business accounts.
- [Adds adjustable quantity to the line items response | Stripe Documentation](https://docs.stripe.com/changelog/clover/2026-01-28/line-items-adjustable-quantity): The 'adjustable_quantity' property is now returned in the line items response for Checkout Sessions, Payment Links, and Quotes. This property indicates whether customers can adjust the quantity of a line item and specifies the minimum and maximum allowed quantities. Integrations parsing LineItem objects will now see this property in API responses and event payloads.
- [Adds error types for unsupported countries or entities when requesting capabilities for Accounts v2 | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-06-30/adds-unsupported-capability-status): Stripe has introduced new error types, 'unsupported_country' and 'unsupported_entity_type', for requesting capabilities with Accounts v2. When account identity information is updated, country eligibility is automatically recalculated. These specific error types replace generic 400 validation errors, improving clarity when a capability is not eligible for a given country or entity type.
- [Adds support for third-party tax on flexible billing mode subscriptions | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/3p-tax): Stripe now supports the use of third-party tax applications for calculating taxes on subscriptions configured with a flexible billing mode. This resolves a previous issue where creating or updating such subscriptions would result in a 400 error code when using a third-party tax app. This change ensures successful tax calculation and processing for these subscriptions.
- [Adds support for third-party tax providers in Accounts v2 | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/accounts-v2-3p-api-ref): Accounts v2 now supports third-party tax providers for tax calculations, in addition to Stripe Tax. This feature is available in public preview and allows businesses to integrate with external tax services for their v2 Accounts. This expands the options for managing tax calculations within the Stripe Connect and Billing ecosystem.
- [Additional ID number types in Accounts v2 | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/accounts-v2-support-more-id-types): Accounts v2 now supports 29 additional types of identification numbers for both businesses and individuals. This includes various national tax and identification numbers from countries such as Angola, Azerbaijan, Bangladesh, and more. The expanded support allows for more comprehensive and localized identification data collection within Accounts v2.
- [Adds the FX Quote API to provide extended exchange rate quotes | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/fx-quote-api): The new FX Quote API allows users to retrieve Stripe's current exchange rates for over 135 currencies and extend these rates for up to 24 hours. These extended rates can be attached to PaymentIntents or Transfers to hedge against currency fluctuations and localize global pricing. This API provides greater flexibility in managing foreign exchange for transactions.
- [Adds BalanceTransaction types related to pay with Stripe balance | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/add_pay_with_stripe_balance_bt_types): Two new balance transaction types, 'stripe_balance_payment_debit' and 'stripe_balance_payment_debit_reversal', have been added to represent payments and refunds made using a Stripe balance. These are primarily for Connect platforms collecting subscription fees from connected accounts' Stripe balances. This change provides clearer transaction data for such inter-account payments.
- [Adds support for script coupons | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/script-coupons): Stripe now supports script coupons, allowing businesses to customize discounting logic using scripts directly on Stripe's infrastructure. A new 'script' parameter on the Coupon create method enables associating custom code, defined by an ID and configuration, with a coupon. This extends Stripe Billing's core functionality for dynamic discount applications.
- [Adds new webhook event types for Billing Meters | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/billing-meter-webhooks): Four new webhook event types for Billing Meters have been introduced: 'billing.meter.created', 'billing.meter.updated', 'billing.meter.deactivated', and 'billing.meter.reactivated'. These events enable real-time monitoring and automatic synchronization of billing meter data with internal systems. This enhances automation and visibility into billing meter status changes.
- [Adds new webhook event types for billing credits | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/billing-credit-webhooks): Three new webhook event types for Credit Grants and Credit Balance Transactions are now available: 'billing.credit_grant.created', 'billing.credit_grant.updated', and 'billing.credit_balance_transaction.created'. These events allow for real-time monitoring of credit changes, enabling automated systems to respond to customer credit updates. They facilitate synchronization of credit data and provide notifications for various credit events.
- [Invoicing resources now specify how they were generated | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/adds-new-parent-field-to-invoicing-objects): Invoicing resources now include a new 'parent' field to specify how invoices, invoice items, and invoice line items were generated. This field replaces deprecated top-level fields like 'quote' and 'subscription' on Invoice objects, and 'subscription_item' on Invoice Item objects. This change provides a more structured way to reference the upstream object that created the invoicing resource.
- [Adds support for Global Payouts | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/adds-support-for-global-payouts): Stripe has launched Global Payouts, enabling users in the US and UK to send money to third parties via new money management APIs. This feature offers no-code, hosted, and API solutions for global payouts without requiring Stripe for payments. It introduces several new resources, including Financial Accounts, Outbound Payments, and various event types for tracking money movement.
- [Makes shipping information an optional parameter for Afterpay payments | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-02-24/afterpay-shipping-details-optional): Shipping information is now an optional parameter for Afterpay payments when using PaymentIntents. While not required, providing shipping details is still recommended for better conversion rates. This change simplifies the integration process for Afterpay payments by removing the mandatory shipping information requirement.
- [Adds capture method option to Billie payments | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/billie-capture-method-option): Stripe's Billie payments now support specifying the 'capture_method' as a payment method option. This allows integrations to supply the capture method on a per-payment method basis when accepting Billie payments. This enhances flexibility for developers managing payment capture workflows.
- [Makes flexible billing mode the default for new subscriptions | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/billing-mode-default-flexible): New subscriptions created via the API now default to flexible billing mode, offering more accurate and predictable billing. For API users, this default depends on the request API version, with 2025-09-30.clover and newer defaulting to flexible. Dashboard users can configure their account-wide default billing mode in Billing Settings.
- [Makes flexible billing mode the default for new subscriptions | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/billing-mode-default-flexible): Newly created subscriptions now default to flexible billing mode, providing enhanced accuracy and predictability. Users can still opt for classic billing by specifying the billing_mode.type parameter. This change impacts various integrations, including subscription creation and invoice previews.
- [Adds support for billing thresholds on flexible billing mode Subscriptions | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/billing-thresholds): Flexible billing mode subscriptions now support billing thresholds, resolving previous incompatibilities. This enables the combination of usage-based billing with the benefits of flexible billing mode for more accurate and predictable subscription management. Creating or updating subscriptions with thresholds will now succeed without errors.
- [Adds discounts field to Checkout Sessions | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-01-27/checkout-sessions-discounts-field): The Checkout Session object now includes a 'discounts' field, which is an array detailing all discounts applied to the session. This allows for retrieving discounts applied by either the merchant or the customer during Checkout Session creation. Developers should upgrade their API version to access this new feature.
- [Checkout Sessions have lower latency and new update semantics | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/checkout-legacy-subscription-upgrade): Checkout Sessions for subscriptions now have lower latency and improved update semantics, especially after the first payment attempt. Subscriptions are created after payment completion, and the checkout.session.status must be 'complete' before an invoice is generated. Integrations relying on invoice data in payment_intent webhooks should switch to the checkout_session.completed webhook.
- [Makes the client parameter optional for WeChat Pay until confirmation | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/lient-param-optional-wechatpay-before-confirmation): The 'client' parameter for WeChat Pay is now optional until the payment confirmation stage. While it remains required at confirmation, this change prevents missing parameter errors when creating or updating a Payment Intent without an initial client value. Developers should ensure the 'client' parameter is provided before confirming the payment.
- [Removes deprecated messaging and bank elements that were replaced | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/stripejs-deprecated-elements-removal): Deprecated Stripe.js elements for Affirm, Afterpay, and various bank payment methods (EPS, FPX, P24, iDEAL) have been removed. These have been replaced by the more versatile Payment Method Messaging Element and the Payment Element. Integrations using the old elements must be updated to avoid failures.
- [Updates computation of subscription schedule phase end date to consider billing cycle anchor changes | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/billing-cycle-anchor-resets-during-phase-computation): The computation of subscription schedule phase end dates now considers billing cycle anchor changes when an explicit end date is not set. This aligns the calculated end date more closely with the subscription's billing cycle. This change affects only new subscription schedules and does not impact existing ones.
- [Payouts are now a capability | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/payouts-are-now-a-capability): Payouts are now classified as a capability within both merchant and recipient configurations for Stripe Connect. Payout restrictions are now reflected under 'restricts_capabilities' instead of the deprecated 'restricts_payouts' field. This change impacts how payout-related requirements are reported.
- [Adds new event types for Accounts v2 | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/new-accounts-v2-events): The Accounts v2 API now includes new event types: v2.core.account.created, v2.core.account.updated, v2.core.account.closed, and v2.core.account[defaults].updated. These events allow for listening to state and field changes within Account v2, improving integration monitoring and responsiveness.
- [Adds wallet options to Checkout Sessions | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/checkout-link-wallet-options): The 'wallet_options' parameter has been added to the create Checkout Session method, allowing for wallet-specific configurations. Specifically, this enables disabling Link for a particular Checkout Session by including 'link' within the 'wallet_options'. This provides more granular control over available payment methods.
- [Adds Sudan to allowed shipping countries for Checkout | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-01-27/checkout-sudan-shipping-support): Sudan (SD) has been added to the list of allowed shipping countries for Checkout Sessions and Payment Links. This change allows customers to select Sudan as a shipping location, enabling transactions and shipments to the country. Developers can utilize this update by specifying 'SD' in the 'allowed_countries' parameter.
- [Adds a new ping event type for testing an event destination | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/cs_document_event_destination_ping_event): A new event type, v2.core.event_destination.ping, has been introduced for testing event destinations. This allows users to ping an event destination from Workbench and verify its ability to receive events. This enhances the reliability of event delivery configurations.
- [Adds Event Destinations v2 API endpoint | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-10-28/event-destinations-api): The Event Destinations v2 API is now available, enabling programmatic management of how Stripe events are received across various destinations like webhook endpoints and Amazon EventBridge. This update introduces new configuration options, including direct AWS integration and a thin event payload for smaller deliveries.
- [Makes Issuing and Treasury embedded components generally available | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-01-27/issuing-treasury-embedded-components): Issuing card, Issuing cards list, Financial account, and Financial account transactions embedded components are now generally available. These components simplify the deployment of embedded finance services for connected accounts, allowing for creation and management of cards and financial accounts with minimal code. An Account Session API is used to enable these components.
- [Adds support for multiple financial accounts per business | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-01-27/multi-fa): Support for multiple financial accounts per business is now generally available for accounts with Treasury enabled. Each business can now have more than one financial account, offering increased flexibility in managing funds. Updates include new parameters for creating outbound transfers and retrieving received credits.
- [Adds a minority-owned business designation field to the business profile hash | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/add-minority-owned-business-designation-to-business-profile): A 'minority_owned_business_designation' field has been added to the Accounts API's business profile hash, complying with Section 1071 of the Dodd-Frank Act. This field collects demographic information for small business financing applicants, which will be anonymized and reported to the CFPB. It includes options for women-owned, LGBTQI+-owned, minority-owned, and other designations.
- [Adds support for US sellers to accept cross-border Pix payments | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/pix_cross_border_in_public_preview): US sellers can now accept cross-border Pix payments from Brazilian buyers in public preview. Pix is a dominant payment method in Brazil, and enabling it is recommended for US-based sellers with potential customers in that market. This feature is available via the PaymentMethodConfiguration API.
- [Adds third-party tax providers for automatic tax calculation | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-10-29/automatic-tax-provider): Third-party tax providers can now be used for automatic tax calculation across all automatic tax integrations. The 'automatic_tax.provider' property identifies the tax calculation provider for Checkout Sessions, Invoices, and Quotes. Users can integrate third-party tax applications and enable them in their automatic tax settings.
- [Adds Meter Event v2 API endpoints | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-09-30/usage-based-billing-v2-meter-events-api): Meter Event v2 API endpoints have been introduced, featuring a Meter Event Stream resource that supports high-throughput usage reporting up to 10,000 events per second. To use this, a Meter Event Session must be created first to obtain an authentication token. This offers a significant increase in reporting capacity compared to the v1 endpoint.
- [Updated address validations for Tax | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/updated-address-validations-for-tax): Stripe now offers enhanced address validation for tax calculations with the new validate_location parameter on the Customer configuration. This feature helps prevent the use of unusable addresses for Stripe Tax calculations, improving accuracy and compliance.
- [Adds support for card installments on Confirmation Token | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/ct-pmo-card-installments): Confirmation Token objects created by the Payment Element now include payment_method_options.card.installments if a cardholder selects an installment plan. This update enhances visibility into cardholder installment choices and aligns with the release of card installments support on the Payment Element.
- [Updates the default layout for Payment Element | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/default-layout-of-payment-element): The Payment Element's default layout has been updated to an accordion instead of tabs, and the behavior of the defaultCollapsed value has changed. This change may impact integrations relying on the previous tabbed layout and aims to improve mobile conversion rates.
- [Removes legacy usage-based billing | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/deprecate-legacy-usage-based-billing): Stripe has removed support for legacy usage-based billing, meaning you can no longer create prices with a 'metered' usage_type without a specified meter. Billing thresholds and aggregate_usage parameters have also been removed from relevant API endpoints.
- [Adds the initCheckout method | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/add-init-checkout): A new stripe.initCheckout method has been introduced, enabling the creation of checkout pages using Elements with the Checkout Sessions API. This feature simplifies the integration process for managing taxes, discounts, shipping, and currency conversion.
- [Adds subtotal property to Invoice Line Items | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-12-15/invoice-line-item-subtotal): Invoice Line Items now include a new 'subtotal' property, representing the amount before discounts and taxes. This addition provides more granular visibility into invoice pricing calculations for each line item.
- [Makes billing country and email fields optional for Klarna payments | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-02-24/cs_make_billing_country_and_email_field_optional_for_klarna_payments): For Klarna payments, the billing country and email fields are now optional. The eligibility for Klarna payments is now determined by the payment's currency, simplifying integration and reducing potential errors, though providing this data is still recommended for better approval rates.
- [Adds new status and consolidates error codes for money management APIs | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-06-30/enhance-money-management-apis): Stripe's money management APIs have been enhanced with a new 'pending' status for Financial Accounts and the replacement of the 'description' property with 'metadata'. Error codes for outbound transfers and payments have also been consolidated for simpler error management.
- [Introduces new customer balance transaction types | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/new-customer-transaction-types): Two new customer balance transaction types, checkout_session_subscription_payment and checkout_session_subscription_payment_canceled, have been introduced, along with a new 'checkout_session' field. These updates improve tracking for transactions related to Checkout sessions.
- [Adds support for the New Zealand BECS Direct Debit local payment method | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/nz-bank-account): Stripe now supports the New Zealand BECS Direct Debit local payment method. Businesses located in New Zealand can now accept payments from buyers in New Zealand using this method.
- [Adds forms to Terminal readers to collect user information | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/collect-inputs): Terminal readers can now collect customer information using the new collect_inputs endpoint, and testing endpoints succeed_input_collection and timeout_input_collection have been added. This allows for collecting various data types directly on the reader.
- [Adds support for partial payments on invoices | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-05-28/partial-payments): Stripe now supports partial payments on invoices by allowing multiple Payment Intents to be attached. New fields for credit notes and a 'invoice_payment.paid' webhook are introduced to manage and track these partial payments and their associated credit notes.
- [Adds support for multiple (partial) payments on invoices | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/add-support-for-multiple-partial-payments-on-invoices): Stripe now supports multiple (partial) payments on invoices and credit notes, introducing the Invoice Payment object to represent the connection between payments and invoices. Several fields have been removed from the Invoice and PaymentIntent objects to accommodate this change.
- [Adds support for payment line items | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/payment-line-items): The Payment Intents API now supports payment line items through the 'payment_details' and 'amount_details' parameters. This feature can lead to cost savings for commercial cards, facilitate reconciliation, and improve authorization rates for certain payment methods.
- [Adds PayPal country property to the PaymentMethods and Charge objects | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-01-27/paypal-country): The 'country' property for PayPal is now available in the Payment Methods and Charge objects. This property, provided by PayPal, represents the buyer's country and can be retrieved from PayPal PaymentMethods or transactions.
- [Changes the political exposure property of the Person object from a string to an enum | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/political-exposure-persons-api): The 'political_exposure' property of the Person object has been changed from a string to an enum. This change requires updates to any code that uses invalid 'political_exposure' values or expects a string representation.
- [Billing Portal Configuration always returns period end date in responses | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2024-12-18/portal-config-schedule-at-period-end-required): The Billing Portal Configuration API now consistently returns the 'schedule_at_period_end' property in all responses. This change makes the property required and eliminates the need to handle null values, simplifying integrations.
- [Adds support for Billing Cadence, Billing Settings, and Billing Profile | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/billing-cadence-settings-profile): New Billing APIs for Billing Cadence, Billing Settings, and Billing Profile are now available. These APIs offer greater flexibility for managing subscription billing frequencies, reusable configurations, and payment flows.
- [Removes support for the page parameter | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/remove-page-event-destinations): Support for the 'page' parameter has been removed from v2_list_events and v2_list_event_destinations. SDKs now utilize auto-pagination or manual fetching of 'next_page_url' or 'previous_page_url' for list pagination.
- [Removes support for the redirectToCheckout method | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/remove-redirect-to-checkout): The stripe.redirectToCheckout method is no longer supported in Stripe.js. Integrations should migrate to Payment Links and Buy Buttons for client-only Checkout, or use standard redirect functions for client-side redirects.
- [Partially capturing or canceling payments no longer creates a Refund | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/remove-refund-from-partial-capture-and-payment-cancellation-flow): Stripe is removing the Refund object creation for partial payment captures and payment cancellations. This change impacts integrations that rely on the Refund object for these specific flows and introduces a new `expired` cancellation reason for PaymentIntents.
- [Removes iterations parameter for subscription schedules | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-08-27/remove_schedule_phase_iterations): The `iterations` parameter for subscription schedules is removed, with its functionality now handled by the `duration` parameter. Developers should update their API calls for creating and updating subscription schedules to use `duration` instead of `iterations`.
- [Versioning in Stripe JS | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-02-24/stripe-js-versioning): Stripe.js now supports versioning, introducing a new release cadence with major updates twice a year and continuous feature enhancements. This provides more predictability for engineering cycles and requires migration guidelines for users updating from Stripe.js v3.
- [Adds billing mode to control how prorations and invoices for subscriptions are calculated and orchestrated | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-04-30/subscriptions-billing-mode): A new `billing_mode` parameter is introduced to control subscription proration and invoice calculations, offering `classic` and `flexible` options. The `flexible` mode improves proration accuracy by considering original debit amounts, taxes, and discounts.
- [Adds support for mixed intervals on the same subscription | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-07-30/support-mixed-intervals): Subscriptions can now include multiple recurring prices with different billing intervals, such as a mix of monthly and annual fees. This feature requires API version 2025-07-30.basil or later and the subscription to be configured in `flexible` billing mode.
- [Adds support for collecting tips in JPY currency to Terminal | Stripe Documentation](https://docs.stripe.com/changelog/acacia/2025-01-27/terminal-jp-supported-country): Stripe Terminal now supports collecting tips in JPY currency for users in Japan. This functionality can be configured when creating or updating Terminal Configurations.
- [Adds ability to configure WiFi for Terminal readers | Stripe Documentation](https://docs.stripe.com/changelog/basil/2025-03-31/terminal-wifi-configuration): The Terminal Configuration API now allows for remote configuration of WiFi networks for sPOS readers. This enables readers to automatically connect to pre-configured networks, supporting WPA/WPA2 Personal and Enterprise with EAP-TLS certificates.
- [Updates initCheckout to be synchronous | Stripe Documentation](https://docs.stripe.com/changelog/clover/2025-09-30/update-init-checkout-synchronous): The `stripe.initCheckout` method in Stripe.js is now synchronous, reducing render latency for mounted Elements. Integrations using Checkout Sessions API need to adjust their code by removing `await` or `.then()` calls and using the new `checkout.loadActions()` function.
- [Changelog | Stripe Documentation](https://docs.stripe.com/changelog): The Stripe Changelog provides a record of changes and upgrades to the Stripe API across various products like Payments, Billing, and Terminal. It details new features, breaking changes, and general availability updates, with recent entries including enhancements for Bacs Direct Debit mandates and reserve holds.
- [Adaptive Pricing | Stripe Documentation](https://docs.stripe.com/payments/checkout/localize-prices/adaptive-pricing): Adaptive Pricing allows customers to pay in their local currency across over 150 countries using machine learning to determine the best presentment currency and calculate localized prices. It offers real-time exchange rates guaranteed for 24 hours and unlocks locally preferred payment methods.
- [Adaptive Pricing | Stripe Documentation](https://docs.stripe.com/payments/currencies/localize-prices/adaptive-pricing): Adaptive Pricing enables customers to pay in their local currency in over 150 countries by automatically calculating localized prices and handling currency conversions. This feature can be enabled in the Stripe Dashboard for Checkout and is always active for Payment Links.
- [Cross-sells | Stripe Documentation](https://docs.stripe.com/payments/checkout/cross-sells): Cross-sells allow customers to purchase complementary products during checkout, increasing average order value and revenue. Products offered as cross-sells must meet specific criteria regarding price association, currency, and recurring intervals.
- [Use your custom domain | Stripe Documentation](https://docs.stripe.com/payments/checkout/custom-domains): Stripe Checkout supports custom domains, allowing businesses to use their own subdomain for hosted checkout pages, Payment Links, and the customer portal. This is a paid feature that requires DNS record verification for activation.
- [Guest customers | Stripe Documentation](https://docs.stripe.com/payments/checkout/guest-customers): Checkout sessions that do not create a Customer object are associated with guest customers, who are automatically grouped in the Dashboard by payment details like card or email. Guest customers are a read-only grouping for completed transactions, and Stripe does not save their payment methods for future use.
- [Limit customers to one subscription | Stripe Documentation](https://docs.stripe.com/payments/checkout/limit-subscriptions): Businesses can limit customers to a single subscription by redirecting them to the customer portal or their website when they already have an active subscription. This functionality works with Checkout and Payment Links and relies on the Customer object or email address to detect existing subscriptions.
- [Let customers pay in their local currency | Stripe Documentation](https://docs.stripe.com/payments/checkout/localize-prices): Customers can pay in their local currency through Stripe Checkout by presenting and charging in over 100 currencies. Options include Adaptive Pricing for automatic localization, FX Quotes API for rate locking, and manual currency prices for direct control.
- [Manually approve payments on your server | Stripe Documentation](https://docs.stripe.com/payments/custom/manual-approval): Manual approval allows businesses to run custom server-side logic before finalizing a payment, such as fraud prevention checks or inventory verification. This feature is compatible with dynamic line items but is not available for the Payment Intents API.
- [Manual currency prices | Stripe Documentation](https://docs.stripe.com/payments/checkout/localize-prices/manual-currency-prices): Manual currency prices allow businesses to set prices in different currencies when creating products, overriding Adaptive Pricing for those specific currencies. This is recommended when Adaptive Pricing is not supported or when a business is comfortable with exchange rate fluctuations.
- [No-cost orders | Stripe Documentation](https://docs.stripe.com/payments/checkout/no-cost-orders): No-cost orders can be processed for one-time payments using line items with a unit amount of 0 or 100% off discounts via coupons and promotion codes. If the total amount is zero, Checkout does not collect a payment method from the customer.
- [Configure optional items | Stripe Documentation](https://docs.stripe.com/payments/checkout/optional-items): Optional items can be configured on a Checkout Session, allowing customers to add complementary products to their order during checkout. This feature can increase average order value and revenue, with up to 10 optional items supported per session.
- [Subscription upsells | Stripe Documentation](https://docs.stripe.com/payments/checkout/upsells): Subscription upsells allow customers to upgrade their subscription plan during checkout using Stripe Checkout. This feature enables businesses to increase average order value and cash flow by offering longer subscription intervals, such as monthly to yearly upgrades.
- [Display yearly prices in monthly terms | Stripe Documentation](https://docs.stripe.com/payments/checkout/yearly-price-display): Displaying yearly prices in monthly terms helps customers compare costs more easily across Stripe Checkout, Payment Links, pricing tables, and buy buttons. This feature shows the equivalent monthly rate for annual plans, and can highlight savings when an annual plan is an upsell from a monthly one.
- [Climate Commitments | Stripe Documentation](https://docs.stripe.com/climate/commitments): Stripe Climate Commitments allow businesses to direct a fraction of their revenue to support carbon removal projects. Contributions are managed and monitored in the Dashboard, helping to scale emerging carbon removal technologies.
- [Carbon removal inventory | Stripe Documentation](https://docs.stripe.com/climate/orders/carbon-removal-inventory): The carbon removal inventory lists available products from Frontier's offtake agreements, detailing product IDs, expected delivery years, prices per metric ton, and minimum order quantities. Stripe takes on the pricing risk, using excess funds to buy more carbon removal if the actual delivery cost is lower than the sold price.
- [How Climate Orders work | Stripe Documentation](https://docs.stripe.com/climate/orders/how-it-works): Climate Orders enable companies to purchase permanent carbon removal from Frontier's portfolio, contributing to net-zero goals and supporting new technologies. Frontier handles supply procurement, supplier progress monitoring, and delivery management, with rigorous vetting of carbon removal solutions.
- [Climate Orders overview | Stripe Documentation](https://docs.stripe.com/climate/orders): Climate Orders allow businesses to pre-order carbon removal tons from Frontier's portfolio, either programmatically via the Climate API or manually through the Dashboard. All orders are for future delivery, and carbon removal is verified by Frontier and a third-party before delivery.
- [Order carbon removal | Stripe Documentation](https://docs.stripe.com/climate/orders/order-carbon-removal): Ordering carbon removal involves creating a climate order, which deducts funds from your Stripe balance and tracks the purchase through confirmation and delivery. Orders can be canceled within 24 hours for a refund, excluding fees, and their status can be tracked in the Dashboard or via webhook events.
- [Webhooks for Climate Orders API | Stripe Documentation](https://docs.stripe.com/climate/orders/webhooks): Webhooks for the Climate Orders API notify your application about product availability and order status changes. Key events include product creation and pricing updates, as well as order delivery confirmation or delays.
- [Stripe Climate | Stripe Documentation](https://docs.stripe.com/climate): Stripe Climate offers two primary ways for businesses to support carbon removal: Climate Commitments, which directs a portion of revenue to scaling carbon removal technologies, and Climate Orders, for purchasing specific quantities of carbon removal to meet climate targets.
- [Understanding Connect account balances | Stripe Documentation](https://docs.stripe.com/connect/account-balances): When using Stripe Connect, both the platform and connected accounts have separate pending and available balances. Funds are allocated based on the type of charges, and the platform account can also maintain a 'connect_reserved' balance to offset negative balances on connected accounts.
- [Account capabilities and configurations | Stripe Documentation](https://docs.stripe.com/connect/account-capabilities): Account capabilities represent functionalities that can be enabled for connected accounts, such as processing payments or receiving transfers. Most capabilities require verification of business information, and requesting only necessary capabilities reduces the onboarding effort.
- [Debit connected accounts | Stripe Documentation](https://docs.stripe.com/connect/account-debits): Platforms can collect funds from connected accounts by debiting their Stripe balance, which is supported for Express and Custom accounts where the platform is responsible for negative balances. This process requires legally binding consent from the connected accounts and incurs additional costs.
- [Handle verification with tokens | Stripe Documentation](https://docs.stripe.com/connect/account-tokens): Account Tokens provide a secure way to collect identity verification information for connected accounts, ensuring Personally Identifiable Information (PII) does not touch your servers. Tokens are used for legal entity and person details, as well as for indicating acceptance of the Stripe Connected Account Agreement.
- [Connect and the Accounts v2 API | Stripe Documentation](https://docs.stripe.com/connect/accounts-v2): The Accounts v2 API simplifies interactions with connected accounts by allowing a single Account object to support all activities, eliminating the need for separate Customer objects. It offers flexible account configurations, centralized identity data, and a unified API for managing both connected accounts and customers.
- [Configure the behavior of connected accounts | Stripe Documentation](https://docs.stripe.com/connect/accounts-v2/connected-account-configuration): Configuring connected accounts via the Accounts v2 API defines interactions like funds flows and loss liability by setting properties such as defaults.responsibilities. These settings determine fee collection, identity verification responsibility, and how negative balances are handled.
- [Charge SaaS fees to your connected accounts | Stripe Documentation](https://docs.stripe.com/connect/integrate-billing-connect): SaaS platforms can use Accounts v2 and Stripe Billing to charge subscription fees directly to connected accounts. This integration requires creating connected accounts with customer and merchant configurations using the Accounts v2 API and is tested in a sandbox environment.
- [Use the Accounts v2 API in your existing integration | Stripe Documentation](https://docs.stripe.com/connect/accounts-v2/migrate-integration): Migrating to the Accounts v2 API allows existing Connect platform integrations to associate connected accounts with payments without creating Customer objects, enable payments from Stripe balance, and utilize v2 Financial Accounts. Existing v1 Accounts can be used with v2 endpoints after a short delay.
- [Compare SaaS platform configurations for Accounts v1 and Accounts v2 | Stripe Documentation](https://docs.stripe.com/connect/accounts-v2/saas-platform-payments-billing): The Accounts v2 API provides SaaS platforms with a unified representation for connected accounts, allowing a single Account object to manage multiple relationships and configurations. This simplifies charging subscription fees through Stripe Billing without needing separate Customer objects.
- [Connect account types | Stripe Documentation](https://docs.stripe.com/connect/accounts): Connect supports Standard, Express, and Custom account types, allowing platforms to distribute responsibilities between the platform, Stripe, and connected accounts. Newer integrations are recommended to use the Accounts v2 API or v1 Accounts with controller properties instead of legacy account types.
- [Use Adaptive Pricing with Connect | Stripe Documentation](https://docs.stripe.com/connect/currencies/adaptive-pricing): Adaptive Pricing enables customers of connected accounts to pay in over 150 local currencies by using machine learning to determine the most relevant currency and automatically calculate localized prices. This feature can unlock local payment methods and facilitate compliance.
- [Additional verifications | Stripe Documentation](https://docs.stripe.com/connect/additional-verifications): Stripe Connect allows platforms to request additional identity verification from connected accounts to reduce fraud, streamline risk operations, and meet compliance needs. This can be integrated into custom onboarding flows or handled automatically, with options to restrict funds based on verification status.
- [Identity Document Additional Verifications | Stripe Documentation](https://docs.stripe.com/connect/additional-verifications/identity-document): The Identity Document Additional Verifications API enforces the collection and verification of government-issued identity documents for connected account representatives. Stripe verifies document authenticity, extracts information, and can optionally match a selfie to the document's photo to reduce fraud and meet regulatory requirements.
- [API onboarding | Stripe Documentation](https://docs.stripe.com/connect/api-onboarding): API onboarding enables platforms to build their own custom onboarding flows for connected accounts using Stripe's APIs, making Stripe invisible to the end-user. Platforms are responsible for all user interactions, collecting necessary verification information, and staying updated on regional legal and regulatory requirements.
- [Making API calls for connected accounts | Stripe Documentation](https://docs.stripe.com/connect/authentication): Platforms can make API calls on behalf of their connected accounts by including the Stripe-Account header with the connected account ID in server-side requests. Client-side calls can be made by passing the connected account ID as an argument to the client library.
- [Manage payout accounts for connected accounts | Stripe Documentation](https://docs.stripe.com/connect/payouts-bank-accounts): Stripe Connect facilitates managing payout accounts for connected accounts, recommending the use of the Connect Onboarding web form or Stripe Financial Connections to collect external bank account and debit card details. These methods help save development time, eliminate the need to store sensitive data, and reduce errors from manual entry.
- [Platform Reporting for direct charge payment fees paid by platforms | Stripe Documentation](https://docs.stripe.com/connect/direct-charge-buy-rate-reporting-overview): Platforms that pay fees for direct charges on their connected accounts can use Stripe's reporting tools to understand these costs. Connect margin reports provide aggregated and transaction-level data on payment volumes, fees, and revenue, while the itemized_fees table offers a granular breakdown of all fees charged.
- [Understand how charges work in a Connect integration | Stripe Documentation](https://docs.stripe.com/connect/charges): Charges in Stripe Connect determine how funds are distributed between the platform, connected accounts, and Stripe, and influence customer statement information. Direct charges go to the connected account first, while indirect charges (destination or separate charges and transfers) are made to the platform first.
- [Clone customer payment information across connected accounts | Stripe Documentation](https://docs.stripe.com/connect/cloning-customers-across-accounts): The legacy feature for cloning customer payment information across connected accounts allows customers to reuse payment details with different sellers on a platform. This involves storing customers on the platform account, creating tokens to clone payment methods, and then creating charges using these tokens.
- [Connected account email configuration | Stripe Documentation](https://docs.stripe.com/connect/account-emails-config): Platforms can customize the appearance and branding of emails sent to their connected accounts through Stripe's Connect email settings. This includes modifying the 'From' address domain and the URLs of pages hosting Connect embedded components.
- [Migrate to a supported Connect configuration | Stripe Documentation](https://docs.stripe.com/connect/configuration-migration-guide): This guide explains how to migrate a Stripe Connect integration to a supported configuration, particularly addressing indirect charges where the platform is responsible for negative balances and fees. Recommendations include changing to direct charges or assigning responsibility for negative balances and fees to the platform.
- [Stablecoin payouts for Connect | Stripe Documentation](https://docs.stripe.com/connect/stablecoin-payouts): Stablecoin payouts are available in private preview for US-based Connect platforms, allowing payouts in stablecoins like USDC. The platform balance remains in fiat, while Stripe handles currency conversion and payout, enabling users to link crypto wallets and see a USDC balance in their Express Dashboard.
- [Customize Connect embedded components | Stripe Documentation](https://docs.stripe.com/connect/customize-connect-embedded-components): Stripe Connect offers customization options for its embedded components, allowing platforms to tailor the appearance and functionality to match their brand. This includes support for dark mode and various UI elements that can be integrated into the platform's experience.
- [Account management | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/account-management): The Account Management embedded component allows connected accounts to view and edit their details, including personal or business information and bank accounts for payouts. It prompts users to update outstanding requirements and can be configured to collect specific types of due requirements.
- [Account onboarding | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/account-onboarding): The Account Onboarding Connect embedded component generates a localized and validated onboarding form using the Accounts API. It handles various business types, company representatives, document uploads, and identity verification, and can be configured to collect specific 'currently_due' and 'eventually_due' requirements.
- [App install | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/app-install): The App Install embedded component, currently in private preview, renders a button that enables connected accounts to install an app. Integration involves creating an Account Session and specifying 'app_install' in the components parameter, along with the specific app ID.
- [App viewport | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/app-viewport): The App Viewport embedded component, in private preview, allows rendering a view from an installed app within the connected account's interface. It requires creating an Account Session and enabling 'app_viewport' in the components parameter, along with specifying the app ID and any necessary data.
- [Balances | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/balances): The Balances component displays balance summaries and upcoming payouts for connected accounts, enabling them to perform payouts and manage their bank accounts. It also allows connected accounts to add funds to avoid negative balances if the platform is liable for them.
- [Disputes for a payment | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/disputes-for-a-payment): The Disputes for a payment component allows connected accounts to view and manage disputes related to a specific payment. If dispute management is enabled, they can submit evidence and take other actions, with the component rendering nothing if no disputes are associated with the payment.
- [Disputes list | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/disputes-list): The Disputes List component displays all disputes associated with a connected account, allowing them to view details and manage disputes by submitting evidence or accepting them. Features include filtering by criteria and exporting the list for analysis.
- [Documents | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/documents): The Documents component renders a list of downloadable tax invoices for the connected account, such as 1099 tax forms. This enables easy access for pre-filing confirmation and e-delivery to connected accounts.
- [Export tax transactions | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/export-tax-transactions): The export tax transactions component allows connected accounts to generate and download summarized tax reports for filing. Users can select a date range and time zone to access tax data formatted for local jurisdictions without needing direct Stripe Dashboard access. This is a private preview component requiring specific SDK versions.
- [Financial account transactions | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/financial-account-transactions): The financial account transactions component displays a list of all transactions associated with a financial account for connected accounts. It is designed for users with access to all financial accounts, not those with restricted access. Features like card spend dispute management can be enabled.
- [Financial Account | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/financial-account): The Financial Account component renders the details of an individual financial account for connected accounts. It allows control over external account collection and Stripe user authentication. This UI should be shown to users with access to all financial accounts.
- [Instant Payouts promotion | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/instant-payouts-promotion): The Instant Payouts promotion component displays content to encourage connected accounts to use Instant Payouts. It shows the available amount for instant payout and allows initiation through a call-to-action button. The component's rendering depends on Stripe's responsibility for negative balances and available funds.
- [Issuing card | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/issuing-card): The Issuing card component displays the details of an individual card issued to connected accounts. It allows for card management, cardholder management, and dispute management features. This UI is intended for users with access to all issued cards.
- [Issuing cards list | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/issuing-cards-list): The Issuing cards list component renders a table view of all cards issued to connected accounts. It provides features for card management, cardholder management, and dispute management. This component is for users who have access to all issued cards.
- [Network cost passthrough report | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/network-cost-passthrough-report): The network cost passthrough report component displays plan-level and transaction-level views of network costs passed to connected accounts. This allows for understanding the breakdown of network costs associated with payment processing. This component is currently in private preview.
- [Notification banner | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/notification-banner): The Notification banner component displays a banner listing required actions for risk interventions and onboarding requirements for connected accounts. It renders when a connected account needs to respond to risk interventions or provide outstanding requirements. Requirements collection options can be controlled.
- [Payment details | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/payment-details): The Payment details component shows details of a specific payment and allows users to manage disputes and perform refunds. It provides an overlay view equivalent to clicking a payment row in the payments list. The destination_on_behalf_of_charge_management feature can be enabled for additional details and actions.
- [Payment method settings | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/payment-method-settings): The Payment method settings component, in private preview, allows connected accounts to customize the payment methods displayed at checkout. It enables customization and provides necessary compliance details for payment method usage. The component uses Payment Method Configurations and Account Capabilities APIs.
- [Payments | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/payments): The Payments component renders a transaction list for various charge types, offering capabilities for refunds, disputes, and payment capture. It provides limited information by default for certain charge types, but the destination_on_behalf_of_charge_management feature can be enabled for more details and actions. This component is in preview for iOS.
- [Payout details | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/payout-details): The Payout details component renders the details of a specific payout, mirroring the overlay shown in the payouts component. It allows direct invocation from a custom UI, such as a payouts list. The component requires a payout ID to display the relevant details.
- [Payouts list | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/payouts-list): The Payouts list component renders a filterable list of payouts for the connected account. This component displays a subset of the UI found in the main payouts component. It can be enabled by specifying 'payouts_list' in the Account Session components parameter.
- [Payouts | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/payouts): The Payouts component displays the balance summary, payout schedule, and a list of payouts for the connected account. It also allows users to perform instant or manual payouts and manage their payout schedule. Features like instant payouts and external account collection can be enabled.
- [Product tax code selector | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/product-tax-code-selector): The Product tax code selector component allows connected accounts to classify their products with a tax code, which is essential for accurate tax calculation by Stripe Tax. This component is suitable for software platforms and marketplaces, enabling connected accounts to select appropriate tax codes for their products. An event handler can be used to update product tax codes within the platform.
- [Reporting chart | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/reporting-chart): The Reporting chart component, in private preview, allows connected accounts to view charts similar to those on the Stripe Dashboard, such as Net Volume and Gross Volume. Users can specify the report name, start date, and end date for the displayed charts. This component requires using a Stripe beta SDK.
- [Tax registrations | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/tax-registrations): The Tax registrations component enables connected accounts to manage their tax registrations for Stripe Tax directly within the platform. This is crucial for platforms integrating Stripe Tax, as connected accounts must register with tax authorities to enable correct tax calculation and collection. The component uses the Tax Registrations API to display and manage these registrations.
- [Tax settings | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/tax-settings): The Tax settings component allows connected accounts to set up Stripe Tax by configuring their head office address and preset tax code within the platform. This component is suitable for software platforms where connected accounts are responsible for tax collection. It helps collect essential information for tax calculation with minimal integration effort.
- [Tax threshold monitoring | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components/tax-threshold-monitoring): The tax threshold monitoring component enables connected accounts to track their potential sales tax collection requirements by viewing sales volume and amounts across monitored tax locations. This component is for software platforms where connected accounts are liable for tax collection. It helps users stay informed about their obligations.
- [Upcoming requirements updates | Stripe Documentation](https://docs.stripe.com/connect/upcoming-requirements-updates): This page outlines upcoming changes to verification requirements for Know Your Customer (KYC) and ultimate beneficial owners (UBO) and directors, driven by global financial regulations. It emphasizes the need for API-based integrations to update their flows to handle these changes, recommending migration to Stripe-hosted or embedded flows for easier management.
- [Stripe-hosted onboarding for Custom accounts | Stripe Documentation](https://docs.stripe.com/connect/custom/hosted-onboarding): Stripe-hosted onboarding for Custom accounts is a web form hosted by Stripe that collects identity verification information from users. It dynamically adjusts the required information based on the connected account's capabilities, country, and business type, optimizing the user experience for mobile, accessibility, and conversion.
- [Connected account filters | Stripe Documentation](https://docs.stripe.com/connect/dashboard/filters): Connected account filters in the Stripe Dashboard help manage accounts and identify those requiring action. Various filters are available, including account name, country, status, business type, capabilities, and connection date, allowing for targeted account management and support.
- [Set reserves on your connected accounts | Stripe Documentation](https://docs.stripe.com/connect/connected-account-reserves): Reserves allow platforms to temporarily hold a portion of a connected account's funds to cover potential refunds and disputes. These reserves can be set up as a fixed hold with a specified release date or as a plan that automatically reserves a percentage of each charge.
- [Cross-border payouts | Stripe Documentation](https://docs.stripe.com/connect/cross-border-payouts): Cross-border payouts enable platforms to pay connected accounts in their local currencies, regardless of the platform's location. Platforms can choose between Connect payouts, which are bundled with payments and offer payee tools, or Global payouts, which allow direct international payments using only a recipient's email address.
- [Using Connect with Custom connected accounts | Stripe Documentation](https://docs.stripe.com/connect/custom-accounts): Custom connected accounts offer platforms complete control over the user experience, requiring the platform to manage all interactions and information collection. With Custom accounts, platforms can modify account details and settings via the API, but are responsible for building the entire onboarding flow, dashboard, and communication channels.
- [Onboarding solutions for Custom accounts | Stripe Documentation](https://docs.stripe.com/connect/custom/onboarding): Stripe offers multiple onboarding solutions for Custom connected accounts, recommending Stripe-hosted onboarding or embedded components for their automatic updates and reduced maintenance. API-based onboarding provides full control but is more complex and time-consuming to build and maintain.
- [Customize the Express Dashboard | Stripe Documentation](https://docs.stripe.com/connect/customize-express-dashboard): The Express Dashboard allows connected accounts to view their balance, upcoming payouts, and earnings, and can be customized with the platform's brand name and icon. Platforms can also configure the features available to connected accounts within the Express Dashboard.
- [Manage connected accounts with the Dashboard | Stripe Documentation](https://docs.stripe.com/connect/dashboard): The Stripe Dashboard provides tools to inspect, support, and understand connected accounts. The 'Connected accounts' page lists accounts with basic information, allowing filtering and sorting to identify issues, view large accounts, or review compliance information for action.
- [Change the owner of a connected account | Stripe Documentation](https://docs.stripe.com/connect/dashboard/change-connected-account-owner): Changing the owner of a connected account depends on the account's Dashboard access level. Platform administrators can change ownership for Express or no Stripe-hosted Dashboards, but verification of the change is required, including confirming business information and owner identities.
- [Manage individual accounts | Stripe Documentation](https://docs.stripe.com/connect/dashboard/managing-individual-accounts): The Connected accounts page in the Stripe Dashboard allows for the management of individual accounts, including creation and configuration. For platforms in France, connected accounts can only be created via Stripe-hosted onboarding due to regional regulations.
- [Connect margin reports | Stripe Documentation](https://docs.stripe.com/connect/margin-reports): Connect margin reports provide platforms with aggregated and transaction-level data on payment volumes, revenue, and fees. These reports help platforms calculate margins and set fees appropriately by analyzing their Connect volume and costs associated with pricing and fees.
- [Remediation link process walkthrough | Stripe Documentation](https://docs.stripe.com/connect/dashboard/remediation-links): Remediation links allow platform users to collect necessary verification information from connected accounts through a Stripe-hosted page. These links are generated in the Dashboard and sent to connected accounts via various communication channels to address updated requirements.
- [Review and take action on connected accounts | Stripe Documentation](https://docs.stripe.com/connect/dashboard/review-actionable-accounts): The 'Connected accounts' page in the Stripe Dashboard helps monitor account health by displaying accounts with open risk, onboarding, or compliance requirements. It allows proactive monitoring, identification of exact requirements, and filtering of accounts to resolve issues efficiently.
- [Review compliance information and take action on requirement updates | Stripe Documentation](https://docs.stripe.com/connect/dashboard/review-compliance-information): The Connect compliance page displays information about connected accounts that are restricted or will be soon, categorized into requirement updates, account restrictions, and top requirements. This section helps platforms stay informed about regulatory changes and take necessary actions to maintain account enablement.
- [Understand your Connect business | Stripe Documentation](https://docs.stripe.com/connect/dashboard/understand-your-connect-business): The Connect overview page in the Stripe Dashboard provides insights into the platform's payments business and connected accounts. It includes sections for Volume, Performance, Account growth, Tasks, and Opportunities, offering a high-level view of financial metrics and growth potential.
- [Design an advanced Connect integration using the Accounts v1 API | Stripe Documentation](https://docs.stripe.com/connect/design-an-integration): This guide explores advanced Connect integration configurations using the Accounts v1 API for existing platforms, recommending the Accounts v2 API for new integrations. It covers creating and onboarding accounts through hosted, embedded, or API methods.
- [Create destination charges | Stripe Documentation](https://docs.stripe.com/connect/destination-charges): Destination charges allow platforms to create charges on their account, collect fees, and immediately transfer the remaining funds to connected accounts. This charge type is optimal for marketplaces where customers transact for services provided by connected accounts.
- [Share payment methods across multiple accounts for direct charges | Stripe Documentation](https://docs.stripe.com/connect/direct-charges-multiple-accounts): This method allows platforms to save payment details from customers and clone them to connected accounts for making direct charges. It involves creating a customer and a SetupIntent on the platform to manage payment information efficiently across multiple accounts.
- [Create direct charges | Stripe Documentation](https://docs.stripe.com/connect/direct-charges): Direct charges enable customers to transact directly with a connected account, with the payment appearing on the connected account's ledger and the platform collecting application fees. This charge type is best suited for platforms providing software as a service, but platform visibility into transactions is limited.
- [Support dark mode | Stripe Documentation](https://docs.stripe.com/connect/embedded-appearance-support-dark-mode): To support dark mode with Connect embedded components, ensure UI consistency by determining dark mode appearance properties and specifying them during component initialization. This allows for a seamless user experience across different display modes.
- [Supported appearance options | Stripe Documentation](https://docs.stripe.com/connect/embedded-appearance-options): This page details the appearance options available for Stripe's Connect embedded components, emphasizing that these are the only methods to alter styles and cannot be overridden with CSS. It lists variables for font family, font size, and spacing, and notes that essential popups for functionality like user authentication cannot be removed.
- [Embedded onboarding | Stripe Documentation](https://docs.stripe.com/connect/embedded-onboarding): Embedded onboarding allows platforms to offer a localized and themeable onboarding UI for connected accounts directly within their application. This component uses the Accounts API to generate forms with data validation, supports networked onboarding for reusing information, and handles various aspects like business types, verification documents, and identity verification.
- [Pay out money with Accounts v1 | Stripe Documentation](https://docs.stripe.com/connect/legacy/add-and-pay-out-guide): This guide explains how to add funds to a Stripe account and transfer them to users' bank accounts without processing payments through Stripe, using the Accounts v1 API. It covers prerequisites for platform setup, branding customization, and server-side integration with Stripe libraries for managing funds and payouts.
- [Build a marketplace | Stripe Documentation](https://docs.stripe.com/connect/end-to-end-marketplace): This guide details how to build a marketplace using the Accounts v1 API by creating connected accounts, collecting customer payments, and then paying out sellers. It outlines prerequisites, server-side setup with Stripe libraries, and the process of creating connected accounts to represent users on the platform.
- [Email communications in embedded Connect integrations | Stripe Documentation](https://docs.stripe.com/connect/embedded-comms): This page explains how Stripe sends email communications to connected accounts in fully embedded integrations, directing them to specific embedded components on the platform's website for action. Platforms must provide Stripe with URLs for these components, and can customize the email messages to match their brand. It lists the types of emails sent, including account, compliance, risk, and tax notifications.
- [Fully embedded Connect platform integration | Stripe Documentation](https://docs.stripe.com/connect/build-full-embedded-integration): A fully embedded Connect platform integration allows platforms to provide Stripe-managed functionality to connected accounts directly within their own website or application. Connected accounts interact with Stripe features through embedded components, without accessing the Stripe Dashboard, while Stripe manages risk and compliance actions.
- [Embedded Stripe Managed Risk | Stripe Documentation](https://docs.stripe.com/connect/embedded-risk): Stripe Managed Risk offers an end-to-end business risk management solution for connected accounts, monitoring risk signals, applying interventions, and seeking to recover negative balances, thereby removing platform liability. For accounts without Stripe-hosted dashboards, integration requires specific embedded components like account onboarding and management, and a notification banner.
- [Embedded Connect Support | Stripe Documentation](https://docs.stripe.com/connect/embedded-support): Embedded Connect Support provides targeted support for connected accounts within the platform's own website when they lack access to a Stripe-hosted dashboard and the platform is not liable for negative balances. This includes a Stripe-hosted support site with self-serve content, email, and live chat support, reducing the platform's support load.
- [Build a SaaS platform with Accounts v1 | Stripe Documentation](https://docs.stripe.com/connect/end-to-end-saas-platform): This guide explains how to build a SaaS platform using the Accounts v1 API, enabling users to accept payments and facilitating fund transfers to their bank accounts. It covers platform registration, branding customization, server-side integration with Stripe libraries, and the creation of connected accounts to represent users.
- [Using Connect with Express connected accounts | Stripe Documentation](https://docs.stripe.com/connect/express-accounts): Express connected accounts offer platforms control over payout schedules, fund flow, and branding, while Stripe manages onboarding, account management, and identity verification. This page is for platforms using legacy connected account types and directs newer integrations to updated documentation.
- [Express Dashboard | Stripe Documentation](https://docs.stripe.com/connect/express-dashboard): The Express Dashboard is a user interface for connected accounts to monitor their balance, view payouts, manage payments, disputes, and refunds directly within the platform's application. Platforms can customize the features available in the dashboard, such as the transactions list, earnings chart, and payments list.
- [View payments | Stripe Documentation](https://docs.stripe.com/connect/express-dashboard/payments): Enabling the 'View payments' feature in the Express Dashboard allows connected accounts to see detailed payment information, including method, fees, customer details, and refund/dispute history for direct and on-behalf-of charges. For other charge types, they can only see limited transfer amount information.
- [Fee behavior on connected accounts | Stripe Documentation](https://docs.stripe.com/connect/direct-charges-fee-payer-behavior): The controller.fees.payer property on the Account object determines billing behavior for direct charges in Connect integrations, specifying whether Stripe collects fees directly from the connected account or if the platform pays them. This property can only be set during account creation.
- [Funds segregation for separate charges and transfers | Stripe Documentation](https://docs.stripe.com/connect/funds-segregation): Funds segregation allows platforms to hold funds from separate charges and transfers in a designated state before transferring them to connected accounts, preventing their use for other purposes like platform payouts or fees. This feature is available in specific countries and requires the platform to be responsible for negative balances on connected accounts.
- [Use the FX Quotes API in Connect | Stripe Documentation](https://docs.stripe.com/connect/currencies/fx-quotes-api): The FX Quotes API in Connect enables platforms to localize prices in customers' currencies and manage exchange rate uncertainty by specifying an FX quote when creating PaymentIntents or transfers. It details how currency conversion occurs for direct charges, including application fees, and mentions the use of extended rate quotes.
- [Get started with Connect embedded components | Stripe Documentation](https://docs.stripe.com/connect/get-started-connect-embedded-components): Connect embedded components allow platforms to integrate Stripe dashboard functionality directly into their websites or mobile applications, enabling users to access Stripe products without leaving the platform. An AccountSession is used to grant embedded components client-side access to a connected account's resources.
- [Handle verification updates | Stripe Documentation](https://docs.stripe.com/connect/handle-verification-updates): Platforms must collect Know Your Customer (KYC) information from connected accounts and use the Accounts and Persons APIs to submit it to Stripe for verification. This page explains how to handle verification updates, monitor requirement statuses, and respond to Stripe's requests, particularly for API-onboarded accounts.
- [Stripe-hosted onboarding | Stripe Documentation](https://docs.stripe.com/connect/hosted-onboarding): Stripe-hosted onboarding redirects connected accounts to a Stripe-hosted web form to collect business and identity verification information, requiring minimal platform effort. This form dynamically renders based on account capabilities and country, and supports networked onboarding for reusing information across multiple accounts.
- [How Connect works | Stripe Documentation](https://docs.stripe.com/connect/how-connect-works): Stripe Connect facilitates multiparty integrations for businesses like marketplaces and software platforms by managing and routing payments and payouts between various entities. It offers options for onboarding, account management, payments, payouts, and includes platform tools for monetization, support, risk management, and tax reporting.
- [Handle verification with the API | Stripe Documentation](https://docs.stripe.com/connect/handling-api-verification): Connect platforms using API onboarding must provide required KYC information via the Accounts and Persons APIs for verification and capability enablement. This involves monitoring account requirement statuses and handling updates, often by establishing a Connect webhook URL to receive account.updated events.
- [Identity verification for connected accounts | Stripe Documentation](https://docs.stripe.com/connect/identity-verification): Stripe Connect's identity verification process ensures compliance with Know Your Customer (KYC) requirements by collecting and verifying information about individuals and companies receiving funds. Platforms can integrate Connect Onboarding to manage this complex verification flow, which may involve collecting documents like IDs and proof of address.
- [Platforms and marketplaces with Stripe Connect | Stripe Documentation](https://docs.stripe.com/connect): Stripe Connect enables platforms and marketplaces to build businesses that manage payments and money movement between multiple parties. It offers tools for designing integrations, managing connected accounts, processing payments, and handling platform administration tasks like setting fees and managing taxes.
- [Instant Payouts for Connect | Stripe Documentation](https://docs.stripe.com/connect/instant-payouts): Instant Payouts for Connect allows connected accounts to access their funds immediately after a successful charge, available 24/7 and typically settling within 30 minutes. This feature helps attract and retain connected accounts and can generate additional revenue through fees, with availability depending on account onboarding and supported countries.
- [Integrate the Express Dashboard in your platform | Stripe Documentation](https://docs.stripe.com/connect/integrate-express-dashboard): The Express Dashboard provides connected accounts with a real-time view of their available balance, upcoming payouts, and earnings. Platforms can integrate this dashboard into their services by using the Login Link API to generate secure URLs that redirect connected accounts directly to their personalized Express Dashboard.
- [Recommended Connect integrations and charge types | Stripe Documentation](https://docs.stripe.com/connect/integration-recommendations): This document outlines Stripe Connect integration recommendations and charge type implications, advising on configurations for direct charges and other scenarios. It suggests assigning negative balance liability to Stripe for direct charges due to higher risk and notes variations in fee behavior for Express accounts.
- [Create invoices with Connect | Stripe Documentation](https://docs.stripe.com/connect/invoices): Connect allows platforms to create invoices for connected accounts, supporting both direct and destination charge models, with the option to include application fees. Invoices are created by authenticating as the connected account for direct charges or by specifying the connected account ID as the destination for destination charges.
- [Controlling bank and debit card transfers | Stripe Documentation](https://docs.stripe.com/connect/legacy-transfers): This page details legacy controls for bank and debit card transfers for Custom Connect accounts, allowing platforms to manage destination accounts and payout frequency. It explains how to add external accounts and outlines restrictions for using debit cards as transfer destinations.
- [Manage payout schedule | Stripe Documentation](https://docs.stripe.com/connect/manage-payout-schedule): Platforms can manage the automatic payout schedule for their connected accounts using the Balance Settings API. This includes configuring payout intervals, specific days for weekly or monthly payouts, and setting minimum balance thresholds for payouts in different currencies.
- [Stripe Managed Risk | Stripe Documentation](https://docs.stripe.com/connect/risk-management/managed-risk): Stripe Managed Risk offers platforms a comprehensive solution to protect against losses from negative balances on connected accounts. It includes ongoing monitoring, risk interventions, and assumes the risk of loss for unrecoverable negative balances, covering screening, detection, monitoring, and mitigation.
- [Using manual payouts | Stripe Documentation](https://docs.stripe.com/connect/manual-payouts): Manual payouts allow platforms to hold funds in a connected account's balance until explicitly paid out, with specific holding period limits based on the business's country. To trigger a payout, the Payouts API is used to move funds from the connected Stripe account's balance to their external account.
- [Understand the merchant of record in a Connect integration | Stripe Documentation](https://docs.stripe.com/connect/merchant-of-record): Understanding the merchant of record (MoR) is crucial in Connect integrations as it defines the entity legally responsible for a transaction. The MoR, which can be the platform or a connected account, dictates who appears on statements, handles disputes, and bears responsibility for purchased goods or services, with card networks enforcing these rules.
- [Migrate your onboarding and requirement update flows to Stripe-hosted or embedded onboarding | Stripe Documentation](https://docs.stripe.com/connect/migrate-from-api-onboarding): Platforms can reduce maintenance effort by migrating API-based onboarding flows for connected accounts to Stripe-hosted or embedded onboarding. These methods automatically determine and collect required information, are localized for all supported countries, and offer varying levels of customization and engineering effort.
- [Migrating accounts to Stripe | Stripe Documentation](https://docs.stripe.com/connect/migrate-to-stripe): Existing multiparty payment businesses can be migrated to Stripe Connect, supporting marketplace or SaaS platform setups. The process involves creating a migration plan, updating the integration for connected accounts, onboarding accounts with KYC data, and migrating historical payment and customer data.
- [Multi-currency settlement for Connect platforms and marketplaces | Stripe Documentation](https://docs.stripe.com/connect/multicurrency-settlement): Multi-currency settlement enables connected accounts to accept, hold, and pay out funds in various currencies beyond their primary one, facilitating payments to suppliers and refunds without immediate conversion. This feature can be enabled in the Dashboard, with cross-region settlement available in a private preview.
- [Work with multiple currencies | Stripe Documentation](https://docs.stripe.com/connect/currencies): Stripe supports processing charges in over 135 currencies, allowing for local presentment to improve customer conversion and authorization rates. Currency conversion (FX) occurs when transaction currencies differ, with Stripe generally applying mid-market rates subject to fees.
- [Multiple configurations for your Connect accounts | Stripe Documentation](https://docs.stripe.com/connect/multiple-payment-method-configurations): Platforms can enable connected accounts to display different payment methods to buyers based on transaction types or invoice amounts using multiple payment method configurations. This feature allows for dynamic payment method selection within defined constraints set by the platform.
- [Multiprocessor payouts for marketplaces | Stripe Documentation](https://docs.stripe.com/connect/multiprocessor-payouts-marketplaces): Multiprocessor payouts for marketplaces, currently in private preview, allow platforms to accept direct settlement from other payment service providers (PSPs) to Stripe. This simplifies payouts to connected accounts and helps platforms avoid holding customer funds and meet regulatory requirements.
- [Network cost passthrough | Stripe Documentation](https://docs.stripe.com/connect/network-cost-passthrough-platforms): Network cost passthrough allows platforms to pass network costs, such as IC++, directly to their connected accounts, enabling IC+ pricing instead of a blended rate. Stripe initially charges these costs to the platform and then recovers them from the connected account's balance.
- [Networked onboarding | Stripe Documentation](https://docs.stripe.com/connect/networked-onboarding): Networked onboarding simplifies the process for connected account users who already have a Stripe account by allowing them to reuse verified business information. This reduces friction during onboarding and eliminates redundant KYC verification, with shared information synchronizing across accounts.
- [OAuth changes for platform-controlled Standard accounts | Stripe Documentation](https://docs.stripe.com/connect/oauth-changes-for-standard-platforms): Stripe has updated OAuth for Connect to isolate processing activity on platform-controlled Standard accounts, preventing multiple platforms from connecting to the same Standard account unless they are Extensions. Users connecting to a platform-controlled account are directed to create a separate Standard account for that platform.
- [Connect OAuth reference | Stripe Documentation](https://docs.stripe.com/connect/oauth-reference): This reference details the available public methods for Stripe Connect's OAuth endpoints, enabling platforms to customize user experiences by passing additional parameters. It covers common examples like prefilling fields and dynamically setting redirect URIs for enhanced user interaction.
- [Using OAuth with Standard accounts | Stripe Documentation](https://docs.stripe.com/connect/oauth-standard-accounts): This page explains how to use the OAuth connection flow for Standard accounts, allowing users to connect to a platform. It outlines the steps of the flow and notes that OAuth is not recommended for new Connect platforms, suggesting Connect Onboarding instead.
- [Choose your onboarding configuration | Stripe Documentation](https://docs.stripe.com/connect/onboarding): Stripe offers three onboarding configurations for connected accounts: Stripe-hosted, Embedded, and API onboarding. Stripe-hosted and Embedded onboarding are recommended for their automatic updates and reduced integration effort, while API onboarding provides full control but requires more resources.
- [Pause payments and payouts on connected accounts | Stripe Documentation](https://docs.stripe.com/connect/pausing-payments-or-payouts-on-connected-accounts): Platforms can pause payments or payouts on connected accounts through the Dashboard if they are liable for negative balances, including Express and Custom accounts. Pausing payments blocks charge creation and deactivates payment capabilities, while pausing payouts stops both automatic and manual payouts.
- [Create payment links with Connect | Stripe Documentation](https://docs.stripe.com/connect/payment-links): Stripe Connect allows platforms to create payment links for connected accounts, optionally taking application fees. Payment links support all charge types, and platforms can configure fees as a fixed amount or a percentage when splitting payments.
- [Payment Method Configurations API | Stripe Documentation](https://docs.stripe.com/connect/payment-method-configurations): The Payment Method Configurations API enables platforms to give connected account owners more control over their offered payment methods. This allows account owners to opt in or out of specific payment methods through the platform's settings or an embedded component, without needing to access the Stripe Dashboard.
- [Update to use dynamic payment methods | Stripe Documentation](https://docs.stripe.com/connect/dynamic-payment-methods): This guide helps existing platforms integrate dynamic payment methods by providing instructions based on their integration setup, checkout solution, connected account types, and charge types. It also details how to enable payment methods for connected accounts and consults resources for payment method information.
- [Embed the payment methods settings component | Stripe Documentation](https://docs.stripe.com/connect/embed-payment-method-settings): The embedded payment methods settings component allows users to manage their payment methods directly on a platform's website without accessing the Stripe Dashboard. This component utilizes the Payment Method Configurations and Account Capabilities APIs and is a customizable alternative to building a custom UI.
- [Adding payment method capabilities | Stripe Documentation](https://docs.stripe.com/connect/payment-methods): This guide explains how existing platforms can check the eligibility of connected accounts for different payment methods and apply capabilities using the Stripe Dashboard. It details how to navigate to the connected account payment method settings page and view eligibility categories.
- [Payout reversals | Stripe Documentation](https://docs.stripe.com/connect/payout-reversals): Platforms responsible for risk and negative balances can reverse payouts sent to connected accounts from a US or Canadian bank account. This can be done via the Dashboard or the API, and specific requirements apply to payouts eligible for reversal, such as being expected within 90 days.
- [Payout statement descriptors | Stripe Documentation](https://docs.stripe.com/connect/payout-statement-descriptors): The statement descriptor for Stripe payouts varies based on connected account properties and payout conditions, with a precedence order for manual and automatic payouts. Connected accounts can customize their statement descriptor, and platforms can set a platform-wide default descriptor under certain criteria.
- [Payouts to connected accounts | Stripe Documentation](https://docs.stripe.com/connect/payouts-connected-accounts): By default, charges on behalf of connected accounts accumulate in their balance and are paid out daily. Platforms can manage payouts by scheduling frequency, performing manual payouts, or settling funds instantly, depending on the connected account's Dashboard access and platform configurations.
- [Platform controls in the Stripe Dashboard | Stripe Documentation](https://docs.stripe.com/connect/platform-controls-for-stripe-dashboard-accounts): Stripe Connect enables platforms to manage more features on behalf of connected accounts that use the full Stripe Dashboard. Platform controls allow for configuring third-party extensions, with options for full access, read-only, or no access, depending on the platform's risk liability.
- [Interactive platform guide | Stripe Documentation](https://docs.stripe.com/connect/interactive-platform-guide): This interactive guide helps create a personalized platform integration by selecting business models (Platform or Marketplace) and monetization strategies (application fees, SaaS subscriptions). It then provides setup guidance, including direct charges and risk/compliance responsibilities.
- [Card product codes in platform pricing tools | Stripe Documentation](https://docs.stripe.com/connect/platform-pricing-tools/card-product-codes): Product codes identify specific programs or products associated with credit cards, and can be used for conditional fees in pricing schemes. This page lists example card product codes for major brands like Visa and Mastercard, along with test card numbers for simulation.
- [Platform pricing tool | Stripe Documentation](https://docs.stripe.com/connect/platform-pricing-tools): The platform pricing tool allows platforms responsible for Stripe fees to set pricing logic for application fees charged to connected accounts. This enables various pricing strategies, such as transaction-based fees or different pricing for different account groups, without coding.
- [Create pricing groups | Stripe Documentation](https://docs.stripe.com/connect/platform-pricing-tools/pricing-groups): Pricing groups allow platforms to assign specific pricing schemes to multiple connected accounts simultaneously, saving manual effort. You can create up to 50 groups per pricing scheme, and each connected account can only have one pricing scheme enabled.
- [Define a custom pricing strategy | Stripe Documentation](https://docs.stripe.com/connect/platform-pricing-tools/pricing-schemes): A pricing scheme is a list of conditional fees evaluated in order, applying the first matching rule or a default fee if none match. Schemes can be created with rules based on transaction properties, with fee types including fixed, variable, and blended, and optional minimums and maximums.
- [Test pricing schemes | Stripe Documentation](https://docs.stripe.com/connect/platform-pricing-tools/testing): Pricing schemes can be tested before live deployment using test mode or sandboxes to simulate application fees on payments. The platform pricing testing tool allows simulation of historical charges to identify errors or margin loss in pricing configurations.
- [Standard accounts guide | Stripe Documentation](https://docs.stripe.com/connect/required-updates/standard-accounts-guide): Stripe has updated Connect to meet new financial regulations, requiring updated information for Standard accounts, particularly beneficial owner details. Stripe manages this collection for Standard accounts, automatically updating new businesses and contacting existing ones if needed.
- [Required verification information | Stripe Documentation](https://docs.stripe.com/connect/required-verification-information): Stripe Connect requires specific verification information from connected accounts to ensure compliance and functionality. Platforms must manage and update this information to avoid disruptions in services like payments and payouts. The documentation outlines the types of information needed and how to handle verification updates through the API or tokens.
- [Best practices for risk management | Stripe Documentation](https://docs.stripe.com/connect/risk-management/best-practices): This page details best practices for managing risk within Stripe Connect integrations. It emphasizes deciding on negative balance liability, enabling fraud prevention with Radar, and effectively managing notifications via webhooks. Implementing these practices helps protect the platform and its connected accounts from financial risks.
- [Risk and liability management with Connect | Stripe Documentation](https://docs.stripe.com/connect/risk-management): This document explains how to manage risk and liability within a Stripe Connect platform or marketplace. It covers deciding on responsibility for losses, understanding negative transactions like refunds and chargebacks, and differentiating between direct and indirect charges. Platforms can either assume liability for losses or assign it to Stripe, depending on their business model and risk tolerance.
- [Introduction to SaaS platforms and marketplaces with Connect | Stripe Documentation](https://docs.stripe.com/connect/saas-platforms-and-marketplaces): Stripe Connect supports SaaS platforms and marketplaces by enabling them to offer payment processing and other services to third parties (connected accounts). SaaS platforms provide services to connected accounts, which act as the merchant of record, while marketplaces facilitate transactions between buyers and sellers. The guide details how platforms can collect fees and manage payment processing for these business models.
- [Create separate charges and transfers | Stripe Documentation](https://docs.stripe.com/connect/separate-charges-and-transfers): Separate charges and transfers allow platforms to create a charge on their account and then distribute funds to multiple connected accounts. This method is useful for marketplaces that need to split payments among various parties, such as a restaurant delivery platform splitting funds between the restaurant and the deliverer. The platform account is debited for Stripe fees, refunds, and chargebacks.
- [Service agreement types | Stripe Documentation](https://docs.stripe.com/connect/service-agreement-types): Service agreement types define the relationship between Stripe, the platform, and connected accounts, determining account capabilities. A 'full' service agreement establishes a direct relationship between Stripe and the connected account holder, allowing them to process payments. A 'recipient' service agreement means the recipient only has a relationship with the platform and cannot process payments directly.
- [Set merchant category codes | Stripe Documentation](https://docs.stripe.com/connect/setting-mcc): Merchant Category Codes (MCCs) classify businesses by their goods or services and are crucial for payment authorization, interchange fees, and fraud prevention. Stripe automatically assigns MCCs to connected accounts, but platforms can set them manually for accounts they control. Accurate MCCs ensure compliance and proper business classification.
- [Smart Disputes fee passthrough | Stripe Documentation](https://docs.stripe.com/connect/smart-disputes-fee-passthrough): Smart Disputes fee passthrough enables platforms to automatically contest disputes on behalf of their connected accounts and pass through or mark up the associated fees. This feature helps monetize dispute management and reduces the platform's absorption of dispute costs. Eligibility requires specific charge types and regional capabilities for account debits.
- [Accept a payment | Stripe Documentation](https://docs.stripe.com/connect/marketplace/tasks/accept-payment): To accept a payment in a marketplace, platforms must create a charge, choosing between destination charges and separate charges and transfers. The charge type impacts fund splitting, customer statement appearance, and responsibility for refunds and chargebacks. Stripe debits fees from the platform account regardless of the charge type chosen.
- [Collect application fees | Stripe Documentation](https://docs.stripe.com/connect/marketplace/tasks/app-fees): Marketplaces can monetize their services by collecting application fees from transactions, which helps offset Stripe fees and ensure profitability. These fees are collected before transferring funds to connected accounts, making the application fee the only charge the connected account sees. Fees can be set using the platform pricing tool or directly in the PaymentIntent.
- [Create and prefill the connected account | Stripe Documentation](https://docs.stripe.com/connect/marketplace/tasks/create): A connected account is a Stripe account for a platform's user, enabling the marketplace to manage payments and funds on their behalf. Creating connected accounts is essential for facilitating payments, handling payouts, and ensuring compliance and reporting for each seller or service provider. This separation allows individual financial records while the marketplace manages the overall payment flow and charges application fees.
- [Set up Dashboard access | Stripe Documentation](https://docs.stripe.com/connect/marketplace/tasks/dashboard): Platforms can set up the Stripe Dashboard for their connected accounts, providing them access to view transactions, balances, and payouts. The Express Dashboard offers a user-friendly interface for connected accounts, or platforms can build custom dashboards using embedded components or the API. This setup is a crucial step after creating a connected account.
- [Accept a payment using destination charges | Stripe Documentation](https://docs.stripe.com/connect/marketplace/tasks/accept-payment/destination-charges): Destination charges are used when customers transact with a platform for services provided by connected accounts, with funds immediately transferred to those accounts. The platform acts as the merchant of record and is debited for Stripe fees, refunds, and chargebacks. This method requires specifying the connected account as the settlement merchant using the `on_behalf_of` parameter for cross-region transactions.
- [Enable payment methods | Stripe Documentation](https://docs.stripe.com/connect/marketplace/tasks/enable-payment-methods): Platforms can enable various payment methods for their marketplaces, including cards, Google Pay, and Apple Pay, which are enabled by default. Stripe evaluates currency, location, and other factors to prioritize and display the most relevant payment methods to customers. This configuration allows marketplaces to optimize conversion rates and customer experience.
- [Marketplace essential integration tasks | Stripe Documentation](https://docs.stripe.com/connect/marketplace/essential-tasks): This guide outlines essential tasks for setting up a Stripe Connect marketplace, covering fund flow, loss liability, and interaction methods between the platform, connected accounts, and Stripe. Key steps include registering the platform, adding business details, creating connected accounts, setting up Dashboard access, and onboarding connected accounts.
- [Onboard your connected account | Stripe Documentation](https://docs.stripe.com/connect/marketplace/tasks/onboard): After creating and prefilling a connected account, platforms must onboard them using an Account Link, a single-use URL for the Connect onboarding flow. Platforms can choose between upfront onboarding, collecting all required information at once, or incremental onboarding, collecting information as needed. Stripe-hosted onboarding is supported in web browsers.
- [Pay out to connected accounts | Stripe Documentation](https://docs.stripe.com/connect/marketplace/tasks/payout): Platforms can manage payouts to their connected accounts, which by default occur on a daily rolling basis. Options include scheduling payout frequency, performing manual payouts, settling funds instantly, or retaining funds in the platform balance. The Balance Settings API and Dashboard can be used to configure these payout preferences.
- [Marketplace quickstart | Stripe Documentation](https://docs.stripe.com/connect/marketplace/quickstart): This quickstart guide provides an overview of the essential integration tasks for building a Stripe Connect marketplace. It helps platforms navigate decisions regarding fund movement, loss coverage, account interaction methods, and charging connected accounts.
- [Handle refunds and disputes | Stripe Documentation](https://docs.stripe.com/connect/marketplace/tasks/refunds-disputes): This guide details managing refunds and disputes for marketplaces using indirect charges in Stripe Connect. It explains dispute terminology and outlines platform responsibilities for handling chargebacks and refunds, noting that Stripe debits the platform balance for disputed amounts and fees. Platforms can often recover these funds from connected accounts.
- [Accept a payment using separate charges and transfers | Stripe Documentation](https://docs.stripe.com/connect/marketplace/tasks/accept-payment/separate-charges-and-transfers): Separate charges and transfers are used to transfer funds from a single payment to multiple connected accounts or when a specific user is unknown at payment time. The platform acts as the merchant of record, and its account balance is debited for fees, refunds, and chargebacks. This method is ideal for marketplaces needing to split payments among various parties.
- [Build a marketplace | Stripe Documentation](https://docs.stripe.com/connect/marketplace): This guide explains how to build a marketplace using Stripe Connect, where you act as the merchant of record and facilitate transactions between customers and sellers. It covers essential tasks like onboarding accounts, processing payments, and managing payouts, recommending a configuration for getting started.
- [Enable merchants on your platform to accept payments directly | Stripe Documentation](https://docs.stripe.com/connect/saas/tasks/accept-payment): This page details how to enable merchants on your platform to accept direct payments from their customers using Stripe Checkout. It outlines the process of creating a Checkout Session on your server, including purchase details and application fees, and redirecting customers to complete their payment.
- [Collect application fees | Stripe Documentation](https://docs.stripe.com/connect/saas/tasks/app-fees): This guide explains how platforms can collect application fees from their connected accounts on each transaction. It details two methods for setting these fees: directly in the PaymentIntent or via the Platform Pricing Tool, and outlines limitations and currency considerations.
- [Create a connected account | Stripe Documentation](https://docs.stripe.com/connect/saas/tasks/create): This document explains how to create and configure connected accounts for your SaaS platform using the Accounts v2 API. It covers defining account identity properties and assigning configurations that determine interactions with your platform and Stripe, including payment distribution and fee responsibilities.
- [Set up Dashboard access | Stripe Documentation](https://docs.stripe.com/connect/saas/tasks/dashboard): This guide explains how to set up Stripe Dashboard access for your connected accounts, allowing them to manage their finances, view reports, and handle disputes. It emphasizes setting the dashboard property to 'full' for connected accounts acting as the merchant of record.
- [Enable in-context shopping on AI agents | Stripe Documentation](https://docs.stripe.com/connect/saas/tasks/enable-in-context-selling-on-ai-agents): This page introduces a private preview feature for enabling in-context shopping on AI agents, allowing businesses to sell products through AI chat agents. It discusses choosing charge types, preparing and uploading product catalog data to Stripe via the Files API.
- [SaaS platform essential integration tasks | Stripe Documentation](https://docs.stripe.com/connect/saas/essential-tasks): This guide outlines the essential integration tasks for building a SaaS platform with Stripe Connect. It covers key decisions such as fund flow, dispute management, and customer interaction methods, providing a best-practice set of steps for platforms charging per-transaction and service fees.
- [Onboard your connected account | Stripe Documentation](https://docs.stripe.com/connect/saas/tasks/onboard): This document explains the process of onboarding connected accounts for your platform, enabling them to complete necessary requirements for account activation. It details using Stripe-hosted onboarding to direct users to the Stripe Dashboard and discusses choosing between up-front and incremental onboarding.
- [Pay out to connected accounts | Stripe Documentation](https://docs.stripe.com/connect/saas/tasks/payout): This guide covers managing payouts and external accounts for your platform's connected accounts, allowing them to transfer accumulated funds. It details options for scheduling automatic or manual payouts, instant settlements, and tracking payout activity using webhooks.
- [Build a SaaS platform | Stripe Documentation](https://docs.stripe.com/connect/saas): This guide explains how to build a SaaS platform using Stripe Connect, enabling merchants to accept payments from their customers and receive payouts. It details two monetization models: Stripe-owned pricing, where merchants pay Stripe fees, and a buy rate model where the platform white-labels Stripe's services.
- [Handle refunds and disputes | Stripe Documentation](https://docs.stripe.com/connect/saas/tasks/refunds-disputes): This guide focuses on how SaaS platforms using direct charges manage refunds and disputes. It defines key terminology, explains how fund movement varies by charge type, and details the process for issuing refunds, including explicitly refunding application fees.
- [Charge SaaS fees to your connected accounts | Stripe Documentation](https://docs.stripe.com/connect/saas/tasks/service-fee): This page explains how to use Stripe Billing to charge connected accounts recurring subscription fees for using your platform. It covers creating products with recurring prices and setting up subscriptions that are collected directly from the connected account's Stripe balance.
- [Using Connect with Standard connected accounts | Stripe Documentation](https://docs.stripe.com/connect/standard-accounts): This guide explains the legacy use of Standard connected accounts with Stripe Connect, where Stripe handles most of the connected account experience. It details how to customize the Connect Onboarding form and use the Accounts API to create and link standard accounts.
- [Set statement descriptors with Connect | Stripe Documentation](https://docs.stripe.com/connect/statement-descriptors): This page explains how to set statement descriptors for charges within a Stripe Connect integration. It details how static and dynamic components work, who sets them (platform or connected account), and the various methods for setting these descriptors during account creation or onboarding.
- [Stripe Dashboard for connected accounts | Stripe Documentation](https://docs.stripe.com/connect/stripe-dashboard): This page describes the features of the Stripe Dashboard available to your platform's connected accounts. Connected accounts can use the Dashboard to view analytics, manage business information, handle disputes, and download reports after completing onboarding.
- [Create subscriptions with Stripe Billing | Stripe Documentation](https://docs.stripe.com/connect/subscriptions): This guide explains how to create subscriptions with Stripe Billing for SaaS and marketplace businesses using Stripe Connect. It outlines use cases for creating subscriptions for connected accounts' customers, for platform end customers, and for charging connected accounts a platform fee.
- [Supported Connect embedded components | Stripe Documentation](https://docs.stripe.com/connect/supported-embedded-components): This page lists the available Connect embedded components that allow you to build a custom, mobile-optimized dashboard for your connected accounts. It categorizes components for onboarding, account management, payments, disputes, and payouts.
- [Choose a calculation method | Stripe Documentation](https://docs.stripe.com/connect/calculation-methods): This guide explains the calculation methods available for Stripe's 1099 tax reporting product. It details options for reporting payments including or excluding fees, and for reporting payouts only, to help platforms file the correct 1099-K, 1099-MISC, or 1099-NEC forms.
- [1099-K form state requirements | Stripe Documentation](https://docs.stripe.com/connect/1099-K): This page outlines state-specific filing requirements for 1099-K forms, detailing which states Stripe files directly, which require additional information like a state tax registration ID, and which require direct filing by the platform. It notes that state requirements may differ from federal IRS guidelines.
- [1099-MISC form state requirements | Stripe Documentation](https://docs.stripe.com/connect/1099-MISC): This page details state-specific filing requirements for 1099-MISC forms, indicating which states Stripe files directly, which require a state tax registration or withholding ID, and which require direct filing by the platform. It also notes federal thresholds for specific box types and potential additional state reporting requirements.
- [1099-NEC form state requirements | Stripe Documentation](https://docs.stripe.com/connect/1099-NEC): This page details the state-specific requirements for filing 1099-NEC forms, outlining which states can be filed directly through Stripe's Dashboard and which require separate state tax registration or withholding IDs. It also highlights potential differences from federal filing requirements and advises consulting a tax advisor for specific situations like backup withholding.
- [Correct tax forms | Stripe Documentation](https://docs.stripe.com/connect/correct-tax-forms): This document explains how to correct previously filed 1099 tax forms, detailing reasons for corrections such as changes in identity data or form totals. It also lists common rejection reasons from the IRS or states, like missing or invalid Taxpayer Identification Numbers (TINs) and address issues, and advises contacting Stripe support for forms with a 'Rejected' status.
- [Deliver your 1099 tax forms | Stripe Documentation](https://docs.stripe.com/connect/deliver-tax-forms): This page covers the requirements for delivering 1099 tax forms to payees, emphasizing the need to provide a copy (typically 'Copy B' with a redacted TIN) in addition to filing with authorities like the IRS. It outlines options for postal mail delivery and electronic delivery, noting that electronic delivery is permissible with payee consent or if a mailed copy is also provided.
- [Deliver tax forms with an interface built by Stripe | Stripe Documentation](https://docs.stripe.com/connect/express-dashboard-taxes): This documentation explains how to use the Stripe Express Dashboard for e-delivery of tax forms to connected accounts. It details that accounts with Express Dashboard access can manage their tax forms, update information, and set delivery preferences, and that this feature is available for integrations that utilize Stripe-built interfaces.
- [File your 1099 tax forms | Stripe Documentation](https://docs.stripe.com/connect/file-tax-forms): This page guides users on how to file 1099 tax forms with the IRS and state tax authorities, stressing the importance of ensuring forms are complete and accurate before filing. It explains Stripe's form status categories ('Ready', 'Needs attention', 'Won't file') and details that forms must have a 'Ready' status, which requires complete name, address, and Taxpayer Identification Number (TIN) information.
- [Get started with tax reporting | Stripe Documentation](https://docs.stripe.com/connect/get-started-tax-reporting): This page serves as an introduction to Stripe's 1099 tax reporting product, enabling platforms to create, modify, file, and deliver tax forms for their connected accounts. It highlights the tax reporting dashboard within the Stripe account and provides a checklist with key dates for the 2025 tax season, including deadlines for e-filing and outreach to connected accounts.
- [Platform tax reporting for Connect platforms | Stripe Documentation](https://docs.stripe.com/connect/platform-tax-reporting): This page introduces Stripe's platform tax reporting capabilities for non-US regions, focusing on regulations like DAC7 and OECD requirements for EU, Canada, and other countries. It explains how platforms can collect and verify tax information from connected accounts, generate reports for authorities, and create seller statements, while noting it's not a comprehensive tax solution.
- [Remediate missing tax information | Stripe Documentation](https://docs.stripe.com/connect/identify-forms-missing-information): This document explains how Stripe automatically identifies forms that meet IRS or state filing thresholds and labels them as 'Ready' if they include the necessary name, address, and Taxpayer Identification Number (TIN). Forms missing this critical information are flagged as 'Needs attention,' and this section guides users on how to track and resolve these issues to achieve a 'Ready' status for filing.
- [Update and create 1099 tax forms | Stripe Documentation](https://docs.stripe.com/connect/modify-tax-forms): This page details how to update and create 1099 tax forms for connected accounts within Stripe. It outlines two primary methods: using the in-Dashboard tax form editor or exporting forms to a CSV file, modifying them, and then importing the updated data. The process also covers creating new forms via CSV imports.
- [Tax ID Additional Verification | Stripe Documentation](https://docs.stripe.com/connect/connect-tax-id-onboarding): This page describes the Tax ID Additional Verification (AV) feature, which allows platforms to collect and verify the Taxpayer Identification Numbers (TINs) of their connected accounts to prevent IRS fines for incorrect submissions. The AV performs name and TIN checks, ensuring accuracy before 1099 forms are issued.
- [Connect W-8 and W-9 | Stripe Documentation](https://docs.stripe.com/connect/connect-w8-w9-onboarding): This page introduces Stripe's W-8 and W-9 Connect product, designed to streamline the collection of necessary tax forms from users, particularly for US preview users. It explains that W-9 forms are for US residents to confirm TINs, while W-8 forms are for non-US residents to certify their tax information and potential treaty benefits, helping platforms avoid IRS penalties for incorrect filings.
- [US tax reporting for Connect platforms | Stripe Documentation](https://docs.stripe.com/connect/tax-reporting): This page explains Stripe Connect's role in US tax reporting for platforms, detailing responsibilities for issuing 1099-K forms based on transaction control and pricing. It clarifies scenarios where Stripe issues 1099-Ks and when platforms are responsible for filing other relevant 1099 forms for their connected accounts.
- [1099 Tax Reporting embedded components walkthrough | Stripe Documentation](https://docs.stripe.com/connect/platform-embedded-taxes-walkthrough): This walkthrough demonstrates how connected accounts manage 1099 tax forms using Stripe Connect embedded components within a platform's interface. It covers the user journey from receiving pre-filing confirmation emails to enabling e-delivery and managing tax information electronically.
- [1099 Tax Support proposed communication guidelines | Stripe Documentation](https://docs.stripe.com/connect/platform-express-dashboard-taxes-communication): This page provides a proposed communication timeline for platforms using Stripe Express or Connect embedded components for 1099 tax form delivery. It suggests specific emails and timings for Stripe and platform communications to connected accounts, starting with pre-filing confirmations in November and continuing through form filing.
- [Support recommendations and FAQ templates | Stripe Documentation](https://docs.stripe.com/connect/platform-express-dashboard-taxes-faqs): This guide offers FAQ templates and support recommendations for platforms assisting connected accounts with 1099 tax forms via Stripe Express. It addresses common questions about pre-filing confirmation emails and other tax season inquiries, enabling platforms to proactively support their users.
- [1099 Tax Support implementation and timeline | Stripe Documentation](https://docs.stripe.com/connect/platform-express-dashboard-taxes-implementation): This page outlines the implementation steps and timeline for using Stripe's interfaces for e-delivery of 1099 tax forms. It emphasizes configuring platform tax settings, ensuring connected accounts have email addresses, and identifying accounts needing updated tax information, with Stripe beginning outreach in early November.
- [1099 Tax Reporting Express Dashboard walkthrough | Stripe Documentation](https://docs.stripe.com/connect/platform-express-dashboard-taxes-walkthrough): This walkthrough details the product flow for connected accounts using the Stripe Express Dashboard to manage their 1099 tax forms. It shows how users can grant e-delivery consent, download forms, and update their tax information through the prebuilt web and mobile dashboard.
- [1099 tax support and communication guide | Stripe Documentation](https://docs.stripe.com/connect/platform-express-dashboard-taxes): This guide explains how platforms can use Stripe's interfaces (Stripe Dashboard, Express Dashboard, or Connect embedded components) to manage 1099 tax forms for connected accounts. It includes implementation timelines, product walkthroughs, and recommended communications and FAQs for supporting users during tax season.
- [Required Verification Information for Taxes | Stripe Documentation](https://docs.stripe.com/connect/required-verification-information-taxes): This page lists the required verification information for US federal 1099 tax reporting through Stripe Connect, including details needed for 1099-K, 1099-MISC, and 1099-NEC forms. It specifies that business tax details are generally required, with exceptions for Single Person Entities, and notes that payouts may be disabled if information is not collected and verified.
- [Split tax forms | Stripe Documentation](https://docs.stripe.com/connect/split-tax-forms): This page explains how to split a 1099 tax form to distribute reported amounts between two forms, typically after a change in ownership or legal entity during the tax year. It covers scenarios such as business sales, changes in legal entity type, or updates to Tax Identification Numbers (TINs).
- [Configure tax form settings | Stripe Documentation](https://docs.stripe.com/connect/tax-form-settings): This page explains how to configure the settings for 1099 tax forms sent to connected accounts via the Stripe Dashboard. You can modify default form types and other settings before filing, and assign roles like Tax Analyst for managing these forms.
- [File tax forms with states | Stripe Documentation](https://docs.stripe.com/connect/tax-forms-state-requirements): This document details how Stripe submits 1099 forms to both the IRS and qualifying states, automatically applying state thresholds. It outlines the necessary preparation steps, including choosing the correct tax form type and determining connected account locations.
- [Tax year changeover | Stripe Documentation](https://docs.stripe.com/connect/tax-year-changeover): This page guides users on managing tax forms when a new tax year begins. It explains that settings from the previous year are applied to the new year, and users can switch the selected year in the Dashboard to view and configure forms for the new tax period.
- [Testing account verification during API onboarding | Stripe Documentation](https://docs.stripe.com/connect/testing-verification): This page provides a walkthrough for testing the verification states of connected accounts during API onboarding. It covers testing initial requirements, such as setting account types and requesting capabilities, using test API keys.
- [Testing Stripe Connect | Stripe Documentation](https://docs.stripe.com/connect/testing): This guide explains how to test Stripe Connect integrations before going live, covering account creation, identity verification, and payouts using sandboxes and test mode. It details how to create test accounts and test the OAuth flow with a test client ID.
- [Add funds to your platform balance | Stripe Documentation](https://docs.stripe.com/connect/top-ups): Platforms can add funds to their Stripe balance to pay connected accounts for goods or services, enabling use cases like bonuses or faster payouts. Funds can also be added for cross-border payouts or to send to other owned accounts, but failed actions due to insufficient funds require manual retries.
- [Migrate your Connect integration to use controller properties instead of account types | Stripe Documentation](https://docs.stripe.com/connect/migrate-to-controller-properties): This page explains how to migrate Connect integrations to use account controller properties instead of account types for more flexible configuration. These properties define discrete account behaviors, such as Dashboard access and fee collection, and are backward compatible with existing account types.
- [Accounts API Argument Changes | Stripe Documentation](https://docs.stripe.com/connect/required-updates/accounts-arguments): This page maps old Accounts API arguments to their new names for newer Connect integrations. It details changes for both individual and company accounts, noting that many arguments have been updated or replaced with new APIs like Persons.
- [Update service agreement acceptances | Stripe Documentation](https://docs.stripe.com/connect/updating-service-agreements): This page describes how platforms can manage connected account service agreement acceptances and other disclosures via the API. It covers handling the Stripe Connected Account Agreement and identity verification for accounts without Stripe-hosted Dashboard access.
- [Update verified user information | Stripe Documentation](https://docs.stripe.com/connect/update-verified-information): This document outlines which verified user information can be updated for connected accounts after initial verification, including business details and personal names. It specifies a 14-day grace period for resolving verification issues and lists fields that cannot be updated post-verification.
- [Use Radar with Connect | Stripe Documentation](https://docs.stripe.com/connect/radar): This page explains how to use Stripe Radar with Connect to identify financial risk in real-time for connected accounts and their charges. It details how Radar applies to direct charges versus transferred charges and how Radar fees are calculated and can be passed to connected accounts.
- [View all accounts | Stripe Documentation](https://docs.stripe.com/connect/dashboard/viewing-all-accounts): This page describes the Connect accounts page in the Stripe Dashboard, which lists all connected accounts and allows filtering by status. Users can customize displayed columns and filter by platform if using Organizations, with most account data updating within a minute.
- [Connect webhooks | Stripe Documentation](https://docs.stripe.com/connect/webhooks): This guide explains how to use webhooks with Stripe Connect to receive notifications about Stripe activity. It differentiates between Account webhooks for platform activity and Connect webhooks for activity on connected accounts, emphasizing the need to configure Connect webhooks to listen for connected account events.
- [Stripe Crypto | Stripe Documentation](https://docs.stripe.com/crypto): Stripe Crypto allows users to integrate crypto payments, payouts, or a fiat-to-crypto onramp into their Stripe integration. It offers features like stablecoin payments, stablecoin payouts for platforms, and various onramp integration options.
- [Set up an Embedded onramp integration | Stripe Documentation](https://docs.stripe.com/crypto/onramp/embedded): This guide provides instructions for setting up an embedded fiat-to-crypto onramp integration, allowing customers to purchase crypto directly within an application. It covers SDK installation, customization of the onramp appearance, and handling customer supportability and fraud.
- [Embedded Components onramp | Stripe Documentation](https://docs.stripe.com/crypto/onramp/embedded-components): This page introduces the Embedded Components onramp, which enables building a native onramp flow within an app for fiat-to-crypto conversion. It outlines the customer flow, integration overview, and mobile SDK configuration, allowing for a customized user experience with minimal Stripe branding.
- [Integrate the Embedded Components onramp | Stripe Documentation](https://docs.stripe.com/crypto/onramp/embedded-components-integration-guide): This guide provides a step-by-step process for integrating the Embedded Components onramp into a mobile app, offering minimal Stripe branding. It details mobile SDK configuration, including installing the React Native SDK, adding the onramp dependency, and using StripeProvider.
- [Stripe fiat-to-crypto onramp | Stripe Documentation](https://docs.stripe.com/crypto/onramp): The Stripe fiat-to-crypto onramp allows users to securely purchase cryptocurrencies directly from a platform or Dapp. Stripe acts as the merchant of record, handling fraud, disputes, and regulatory requirements, with options for Stripe-hosted, embedded, or mobile SDK integrations.
- [Use the Stripe-hosted onramp | Stripe Documentation](https://docs.stripe.com/crypto/onramp/stripe-hosted): This page explains how to use the Stripe-hosted, standalone onramp by redirecting users to a prebuilt frontend integration. It details the process of submitting an onramp application and generating a redirect URL with customizable parameters for integrating the crypto onramp.
- [Upgrade your onramp integration | Stripe Documentation](https://docs.stripe.com/crypto/onramp/upgrade-onramp-integration): This guide details API changes for upgrading a beta fiat-to-crypto onramp integration to the public release version. It covers modifications to request bodies, field renames, and path changes, providing examples for fetching quotes and creating onramp sessions.
- [Supported currencies | Stripe Documentation](https://docs.stripe.com/currencies): Stripe supports charging customers in over 135 currencies and settling funds in a preferred currency. This guide explains currency conversion, API formatting, and charge limits.
- [The FX Quotes API | Stripe Documentation](https://docs.stripe.com/payments/currencies/localize-prices/fx-quotes-api): The FX Quotes API allows businesses to localize prices by providing current exchange rates, extended rate quotes for up to 24 hours, and FX fee information. This helps businesses manage currency conversion uncertainties and estimate settlement amounts.
- [Localize prices | Stripe Documentation](https://docs.stripe.com/payments/currencies/localize-prices): Localizing prices allows businesses to present and charge customers in over 135 currencies, potentially increasing conversion rates and lowering costs. Stripe offers Adaptive Pricing, the FX Quotes API, and manual currency pricing options to facilitate this.
- [Settle in additional currencies | Stripe Documentation](https://docs.stripe.com/payments/currencies/settlement-payouts): Settling funds in currencies other than your primary Stripe account currency affects processing fees. Businesses can choose to settle in their default currency or enable settlement in additional currencies, with associated fees for currency conversion and payouts.
- [Custom email domain | Stripe Documentation](https://docs.stripe.com/get-started/account/email-domain): Businesses can set up a custom email domain for sending invoices, receipts, and failed payment notifications to customers. This involves adding and verifying the domain through DNS records in the Stripe Dashboard to enhance brand consistency.
- [Web Dashboard | Stripe Documentation](https://docs.stripe.com/dashboard/basics): The Stripe Dashboard is the web interface for managing and configuring your Stripe account, including account resources, transactions, customers, and team members. It offers features like a customizable Home page, Balances, and Transactions views.
- [Perform searches in the Dashboard | Stripe Documentation](https://docs.stripe.com/dashboard/search): The Stripe Dashboard's search functionality allows users to quickly find payments, customers, invoices, payouts, and other resources. Users can employ various search terms, filters, and operators for more precise and efficient searching.
- [Stripe Dashboard mobile app | Stripe Documentation](https://docs.stripe.com/dashboard/mobile): The Stripe Dashboard mobile app, available for iOS and Android, enables users to monitor business metrics, manage payments and customers, and initiate payouts on the go. It also supports accepting in-person payments and creating basic invoices and payment links.
- [Set up group-based role assignment with SCIM synchronized groups | Stripe Documentation](https://docs.stripe.com/get-started/account/sso/group-role-assignments): Group-based role assignment, synchronized via SCIM, allows for automatic assignment of user roles based on group membership in an Identity Provider. This requires setting up Single Sign-On and SCIM, then configuring group synchronization and role assignments within Stripe.
- [Single sign-on with Entra ID | Stripe Documentation](https://docs.stripe.com/get-started/account/sso/entra-id): Single sign-on (SSO) with Microsoft Entra ID (formerly Azure AD) enables businesses to manage access to their Stripe account through their identity provider. This involves verifying domain ownership, configuring Entra ID for SSO, and assigning user roles for secure access.
- [Single sign-on with Google Workspace | Stripe Documentation](https://docs.stripe.com/get-started/account/sso/google-workspace): Integrating Stripe with Google Workspace for Single Sign-On (SSO) allows for centralized management of team access and roles. The process involves proving domain ownership, configuring Google Workspace, and setting up Stripe to work with Google Workspace.
- [Single sign-on with Okta | Stripe Documentation](https://docs.stripe.com/get-started/account/sso/okta): Setting up Single Sign-On (SSO) with Okta for Stripe involves managing team access through Okta as the identity provider. Key steps include verifying domain ownership and configuring both Okta and Stripe to enable seamless and secure user authentication.
- [Single sign-on with OneLogin | Stripe Documentation](https://docs.stripe.com/get-started/account/sso/onelogin): Integrating Stripe with OneLogin for Single Sign-On (SSO) allows for centralized management of team access and roles. This process requires proving domain ownership and configuring both OneLogin and Stripe to work together for secure authentication.
- [Single sign-on with SAML Identity Provider | Stripe Documentation](https://docs.stripe.com/get-started/account/sso/other): This guide explains how to set up Single Sign-On (SSO) with a generic SAML Identity Provider for the Stripe Dashboard. It involves proving domain ownership, configuring the SAML IdP, and setting up Stripe to work with the IdP for user authentication.
- [Single sign-on (SSO) | Stripe Documentation](https://docs.stripe.com/get-started/account/sso): Single Sign-On (SSO) enables teams to access the Stripe Dashboard using a single set of credentials managed by an Identity Provider (IdP) that supports SAML 2.0. Enabling SSO enhances security and simplifies the sign-in process for users.
- [Organization-level SSO | Stripe Documentation](https://docs.stripe.com/get-started/account/orgs/sso): Organization-level SSO allows businesses with multiple Stripe accounts to centrally configure and manage single sign-on settings. This consolidates authentication across all accounts within an organization, simplifying management and enhancing security.
- [Set up SCIM provisioning | Stripe Documentation](https://docs.stripe.com/get-started/account/sso/scim): SCIM provisioning automates the creation and deactivation of team members in Stripe, synchronizing with your Identity Provider (IdP). This complements SAML SSO by allowing pre-provisioning and on-demand deprovisioning of users.
- [Consolidate your SSO integrations | Stripe Documentation](https://docs.stripe.com/get-started/account/orgs/sso-consolidation): Stripe Organizations enables the consolidation of single sign-on (SSO) integrations across multiple Stripe accounts. This involves configuring a single identity provider application to authenticate users to multiple Stripe accounts, streamlining management.
- [Troubleshoot SSO | Stripe Documentation](https://docs.stripe.com/get-started/account/sso/troubleshooting): This guide helps troubleshoot common errors encountered during Stripe SSO configuration, such as expired SAML requests or invalid issuer IDs. It provides resolutions for issues like expired requests, invalid responses, incorrect issuer IDs, and unreachable IdP URLs.
- [Card declines | Stripe Documentation](https://docs.stripe.com/declines/card): Card payments can fail due to insufficient funds, incorrect card data, or suspected fraudulent activity. Stripe Sigma can be used to analyze decline rates, and businesses can consider offering Buy Now, Pay Later options to mitigate declines.
- [Stripe decline codes | Stripe Documentation](https://docs.stripe.com/declines/codes): Stripe provides specific decline codes that offer more detail than standard issuer codes, often including an advice_code for suggested next steps. These codes help identify the exact reason for a card payment decline, such as authentication requirements or network issues.
- [Declines | Stripe Documentation](https://docs.stripe.com/declines): Payments can fail due to issuer declines, blocked payments, or invalid API calls, with Stripe working to reduce decline rates. Each failure type requires a different handling approach, and details can be reviewed in the Dashboard or via the API's Charge object outcome.
- [Network decline codes | Stripe Documentation](https://docs.stripe.com/declines/network-codes): Network decline codes are alphanumeric codes from issuing banks, processors, or credit networks that explain payment declines. Examples include 'insufficient_funds' for ACH Direct Debit or 'debit_not_authorized' when a mandate is missing, with suggested next steps for resolution.
- [/dev/payments | Stripe Documentation](https://docs.stripe.com/dev/payments): This page is a placeholder for information related to payment processing within Stripe's developer resources.
- [Developers Dashboard | Stripe Documentation](https://docs.stripe.com/development/dashboard): The Developers Dashboard (now largely replaced by Workbench) allows users to view API request logs, monitor webhook events, and manage API keys. It helps in identifying integration errors and understanding account activity.
- [View events and event object payloads | Stripe Documentation](https://docs.stripe.com/development/dashboard/events): Users can view events triggered by their Stripe account and their corresponding object payloads within the Developers Dashboard or Workbench. Events are logged when API calls are made via the API, Dashboard, or Stripe CLI, and can be filtered by event name.
- [View API request logs | Stripe Documentation](https://docs.stripe.com/development/dashboard/request-logs): API request logs are created when API calls are made through user actions, the Stripe CLI, or the Dashboard. These logs can be filtered and viewed in the Developers Dashboard or Workbench to help manage and debug Stripe integrations.
- [Add a webhook endpoint | Stripe Documentation](https://docs.stripe.com/development/dashboard/webhooks): A webhook endpoint can be created using the Developers Dashboard or Workbench to receive events from Stripe. Users can configure endpoint types (Account or Connect) and select specific event types to listen for.
- [Training Scenarios | Stripe Documentation](https://docs.stripe.com/worksheets): Training Scenarios offer an interactive way to practice implementing key Stripe business processes using the in-browser Stripe Shell. These scenarios provide step-by-step guidance for using Stripe's products to achieve specific business goals.
- [Build on Stripe with LLMs | Stripe Documentation](https://docs.stripe.com/building-with-llms): Large Language Models (LLMs) can be integrated into Stripe workflows using tools and best practices provided by Stripe. The Model Context Protocol (MCP) enables AI agents to interact with the Stripe API and knowledge base.
- [Stripe health alerts | Stripe Documentation](https://docs.stripe.com/health-alerts): Stripe health alerts provide real-time monitoring and automated notifications for issues affecting API integrations and payment flows. These alerts are available on Premium and Enterprise Support plans and are communicated via email or the Workbench Health tab.
- [Developer resources | Stripe Documentation](https://docs.stripe.com/development): Stripe's developer resources offer tools and documentation for building and managing integrations, including SDKs, API management, testing tools, and the Developers Dashboard/Workbench. They also cover advanced topics like AI solutions and extending Stripe.
- [API authentication methods | Stripe Documentation](https://docs.stripe.com/stripe-apps/api-authentication): Apps can authenticate Stripe API requests using a Platform key, OAuth 2.0, or a Restricted API key (RAK). Each method suits different use cases, with RAKs offering a more secure, permissioned approach for user-specific integrations.
- [OAuth 2.0 | Stripe Documentation](https://docs.stripe.com/stripe-apps/api-authentication/oauth): OAuth 2.0 allows users to authenticate requests to the Stripe API on behalf of their accounts by redirecting them to Stripe to grant permissions. This industry-standard protocol is useful when integrating with other systems that already use OAuth.
- [Restricted API key authentication | Stripe Documentation](https://docs.stripe.com/stripe-apps/api-authentication/rak): Restricted API keys (RAKs) generated by Stripe Apps provide authenticated access to Stripe APIs with specific, predefined permissions. This offers a more secure alternative to users sharing their secret keys, potentially requiring minimal backend code changes.
- [App analytics | Stripe Documentation](https://docs.stripe.com/stripe-apps/analytics): App analytics provide insights into how Stripe Apps are used and how marketplace listings perform, with data like install counts and listing views available for export. The Dashboard offers tools for analyzing app performance over selected periods.
- [Add server-side logic | Stripe Documentation](https://docs.stripe.com/stripe-apps/build-backend): Server-side logic for Stripe Apps is handled by a self-hosted backend service, enabling secure third-party integrations, webhook event subscriptions, and long-lived or scheduled app logic. This backend authenticates users from the UI using a signature with a shared secret.
- [Add deep links | Stripe Documentation](https://docs.stripe.com/stripe-apps/deep-links): Deep links are URLs that reduce navigation steps for users to open a Stripe app within the Dashboard. They can be shared in emails or websites and are created using the Stripe account ID, a Dashboard view URL, and the application ID.
- [Embedded Stripe Apps integration guide | Stripe Documentation](https://docs.stripe.com/stripe-apps/embedded-apps): Embedded components for Stripe Apps allow customers to manage payments data within third-party applications by embedding Stripe integrations directly into platforms. This enables the use of prebuilt UI components that sync data with services like QuickBooks and Xero.
- [Accounting software integrations | Stripe Documentation](https://docs.stripe.com/stripe-apps/embedded-apps/accounting-integrations): Stripe offers integrations for accounting software like QuickBooks Online and Xero through Connect embedded components for Stripe Apps. These integrations automate accounting by synchronizing transactions, fees, payouts, and other data directly from a user's platform.
- [Marketing software integrations | Stripe Documentation](https://docs.stripe.com/stripe-apps/embedded-apps/marketing-integrations): Stripe Apps allow embedding marketing software integrations, like Mailchimp, directly into your platform. This enables users to automate customer email workflows by syncing data, triggering automations based on purchase activity, and enhancing marketing segmentation without requiring you to build the integration yourself.
- [Enable local network access | Stripe Documentation](https://docs.stripe.com/stripe-apps/enable-local-network-access): Local Network Access (LNA) permission is a security feature implemented by browsers like Chrome to protect users from network attacks. For Stripe Apps development, this permission is necessary when previewing your app, as it allows the browser to download assets from a local HTTP server started by the Stripe CLI.
- [Enable Sandbox support for your public app | Stripe Documentation](https://docs.stripe.com/stripe-apps/enable-sandbox-support): Enabling sandbox support for your public app allows businesses to test its features in an isolated environment before going live. Sandboxes are now the default testing method for new Stripe businesses, and implementing this support is strongly recommended for user evaluation.
- [Listen for events | Stripe Documentation](https://docs.stripe.com/stripe-apps/events): Apps can receive real-time alerts about events on user accounts using Webhooks, which helps in syncing data or triggering actions. To implement this, register a webhook endpoint in the Stripe Dashboard and ensure your app has the necessary 'event_read' permission, along with any specific event permissions.
- [Back-end app example | Stripe Documentation](https://docs.stripe.com/stripe-apps/back-end-app-example): This guide demonstrates how to build a back-end Stripe app that performs processing without a user interface beyond the default app settings page. It covers selecting authentication types like platform key, OAuth 2.0, or Restricted API Key (RAK) and setting up a Stripe account.
- [Common use cases | Stripe Documentation](https://docs.stripe.com/stripe-apps/common-use-cases): Stripe Apps can be built for various common business needs, categorized into back-end, front-end, and full-stack applications. Each app type serves a different purpose, from background data syncing to creating user interfaces within the Stripe Dashboard.
- [Front-end app example | Stripe Documentation](https://docs.stripe.com/stripe-apps/front-end-app-example): This guide explains how to build a front-end Stripe app that focuses solely on rendering a user interface within the Stripe Dashboard. It details the process of selecting an authentication type and setting up a Stripe account for development.
- [Full-stack app example | Stripe Documentation](https://docs.stripe.com/stripe-apps/full-stack-app-example): This guide shows how to build a full-stack Stripe app that combines both a user interface within the Stripe Dashboard and back-end processing capabilities. It covers selecting authentication methods and the initial steps of creating a Stripe account for development.
- [Build a UI | Stripe Documentation](https://docs.stripe.com/stripe-apps/build-ui): You can build a custom user interface that extends the Stripe Dashboard's functionality using TypeScript, React, and Stripe’s UI Extensions SDK. This involves creating 'views,' which pair a React component with a specific viewport within the Dashboard.
- [Getting started with Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/create-app): This guide introduces the basics of Stripe app development by building a simple 'Hello, world!' app with a UI extension. It covers prerequisites like installing the Stripe CLI and Node.js, and signing into your Stripe account.
- [Handle different modes | Stripe Documentation](https://docs.stripe.com/stripe-apps/handling-modes): Apps can be installed in live mode, test mode, or a sandbox environment, and your app needs to handle these different modes. The 'Try in test mode' option encourages users to test apps, and webhooks require additional setup for test and sandbox environments.
- [Distribution options | Stripe Documentation](https://docs.stripe.com/stripe-apps/distribution-options): Stripe Apps can be distributed either publicly through the Stripe App Marketplace or privately for team members only. Publishing on the App Marketplace involves completing an app listing and adhering to Stripe's review process and quality standards.
- [How Stripe Apps work | Stripe Documentation](https://docs.stripe.com/stripe-apps/how-stripe-apps-work): Stripe Apps allow embedding custom user experiences and orchestrating the Stripe API directly within the Stripe Dashboard. Apps can modify Stripe data, sync data with external systems, and customize the user interface, often consisting of a frontend UI extension and a backend component.
- [How UI extensions work | Stripe Documentation](https://docs.stripe.com/stripe-apps/how-ui-extensions-work): UI extensions allow you to render your own user interface within Stripe products using TypeScript and React, leveraging Stripe's UI toolkit. These extensions run in a secure, sandboxed iframe and differ from standard React applications by exclusively using Stripe's provided UI components.
- [Using install links | Stripe Documentation](https://docs.stripe.com/stripe-apps/install-links): Install links enable users to install public Stripe Apps directly from your website, outside of the Stripe App Marketplace. This integrated flow allows you to pass state, complete the app installation, and redirect users back to your application with an authenticated Stripe account.
- [How to publish an app to the Stripe App Marketplace | Stripe Documentation](https://docs.stripe.com/stripe-apps/publish-app): This guide details the process of publishing an app to the Stripe App Marketplace to make it publicly available. It covers updating the app manifest, preparing your app, and completing the app review process to ensure it meets Stripe's standards.
- [Stripe Apps quality requirements | Stripe Documentation](https://docs.stripe.com/stripe-apps/review-requirements): Apps submitted to the Stripe App Marketplace must meet specific quality requirements, focusing on transparency in pricing and correct date and time formatting. These qualitative requirements supplement the primary marketplace guide for app review.
- [Test your app externally | Stripe Documentation](https://docs.stripe.com/stripe-apps/test-app): External testing allows you to distribute test versions of your public app to other accounts before publishing to the App Marketplace. You can invite up to 25 testers via the Dashboard and manage access links for installation.
- [Migrate an extension to Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/migrate-extension): Extensions are legacy integrations that are being replaced by Stripe Apps as the preferred method for integrating Stripe with other tools. Migrating to Stripe Apps offers better discoverability, more granular permissions, and interactive functionality with embedded UI components.
- [Onboarding | Stripe Documentation](https://docs.stripe.com/stripe-apps/onboarding): Onboarding is the crucial first interaction users have with your app after installation, guiding them through setup with minimal friction. Tools and best practices, including specific UI components, are available to help design an intuitive and polished onboarding flow.
- [Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps): Stripe Apps allow developers to extend Stripe's functionality by building third-party applications that can be privately distributed or published on the Stripe Apps Marketplace. These apps can authenticate users, automate workflows using the Stripe API, and create custom user interfaces within the Stripe Dashboard.
- [Migrate a plugin to an OAuth 2.0 app | Stripe Documentation](https://docs.stripe.com/stripe-apps/plugins/oauth): This guide explains how to migrate existing Stripe plugins to use OAuth 2.0 authentication within Stripe Apps. This migration is required by September 30, 2024, to enhance user security by adopting secure authentication methods like OAuth 2.0, Restricted API Keys, or Stripe Connect.
- [Migrate a plugin to Stripe Apps or Stripe Connect | Stripe Documentation](https://docs.stripe.com/stripe-apps/plugins/decide-migration): This document outlines the options for migrating third-party integrations, previously known as plugins, to Stripe Apps or Stripe Connect. It emphasizes the mandatory shift by September 30, 2024, to secure authentication methods (OAuth 2.0, Restricted API Keys, or Stripe Connect) to protect users from fraud.
- [Migrate a plugin to a RAK app | Stripe Documentation](https://docs.stripe.com/stripe-apps/plugins/rak): This guide details the process of migrating a Stripe plugin to a Stripe App that utilizes Restricted API Keys (RAKs) for authentication. This is part of Stripe's security initiative, requiring all plugin developers to adopt secure authentication methods by September 30, 2024.
- [Promote your app | Stripe Documentation](https://docs.stripe.com/stripe-apps/promote-app): Developers can join the Stripe Partner Ecosystem to accelerate their app's growth after publishing to the Stripe App Marketplace. Benefits include co-marketing opportunities with Stripe, access to marketing resources, eligibility for Market Development Funds, and co-selling tools.
- [App manifest reference | Stripe Documentation](https://docs.stripe.com/stripe-apps/reference/app-manifest): The app manifest file (stripe-app.json) is a crucial configuration file for every Stripe app, describing its integration with the Stripe platform. It defines app details, distribution type, API access, and permissions, and can be managed via the Stripe Apps CLI or edited directly.
- [Stripe Apps CLI reference | Stripe Documentation](https://docs.stripe.com/stripe-apps/reference/cli): The Stripe Apps CLI is a command-line tool that simplifies the creation, development, configuration, and uploading of Stripe apps. It includes commands for creating new apps, starting a development server, and managing app configurations.
- [Permissions reference | Stripe Documentation](https://docs.stripe.com/stripe-apps/reference/permissions): Stripe Apps require explicit permissions to access user data, including Stripe API objects and events. These permissions must be declared in the app manifest file and accepted by account administrators during installation to ensure user data protection.
- [Extension SDK API reference | Stripe Documentation](https://docs.stripe.com/stripe-apps/reference/extensions-sdk-api): The Extension SDK API provides UI extensions with context props and utility functions to interact with users and the Stripe Dashboard ecosystem. It offers access to user information, environment details, and OAuth context, enabling rich integrations within the Dashboard.
- [Add authorization flows | Stripe Documentation](https://docs.stripe.com/stripe-apps/pkce-oauth-flow): This guide explains how to implement PKCE OAuth workflows within a Stripe app's UI extension, allowing it to retrieve access tokens from an OAuth provider directly. This eliminates the need for a separate OAuth backend and enables interaction with third-party services from the Stripe Dashboard.
- [Enable post-install actions and configurations | Stripe Documentation](https://docs.stripe.com/stripe-apps/post-install-actions): Post-install actions allow apps to require additional user configurations or credential entries after installation, either within the app's settings page or via an external link. These actions are defined in the app manifest file using the `post_install_action` field.
- [UI testing | Stripe Documentation](https://docs.stripe.com/stripe-apps/ui-testing): The Extension SDK provides utilities for writing unit tests for your app's user interface, recommending the use of Jest with custom matchers. These tools interact with the remote rendering engine that translates React code into a DOM tree within the Stripe Dashboard.
- [Viewports reference | Stripe Documentation](https://docs.stripe.com/stripe-apps/reference/viewports): Viewports define where a UI extension can appear within the Stripe Dashboard and can provide context objects for accessing current page data. Available viewports include specific pages like Payments, Customers, and Invoices, as well as broader areas like the Dashboard home and settings.
- [Sample apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/sample-apps): Stripe provides sample apps and design files to help developers get started with building their own Stripe Apps. The SuperTodo app is a complete example demonstrating API integration and UI components, while Figma files offer design patterns and UI component examples.
- [Add an app settings page | Stripe Documentation](https://docs.stripe.com/stripe-apps/app-settings): An app settings page is automatically created in the Stripe Dashboard when an app is uploaded, allowing administrators to configure app settings for their use case or authenticate with external applications. This page provides a dedicated space for custom configurations.
- [Store secret credentials and tokens in your app | Stripe Documentation](https://docs.stripe.com/stripe-apps/store-secrets): The Secret Store API securely persists sensitive data, such as authentication credentials, for Stripe Apps. Secrets are accessible only to the app and their owners, ensuring secure passing of tokens between UI extensions and backends without storing personal or PCI-sensitive data.
- [UI extension developer tools | Stripe Documentation](https://docs.stripe.com/stripe-apps/ui-extension-developer-tools): Stripe Apps include built-in developer tools for type checking, linting, and testing UI extensions, leveraging TypeScript and best practices. These tools, managed via the `tsconfig.json` file and the `@stripe/ui-extension-tools` package, streamline the development process.
- [Upgrade Stripe's UI extension SDK | Stripe Documentation](https://docs.stripe.com/stripe-apps/upgrade-stripes-ui-extension-sdk): This guide details how to upgrade your Stripe app to the latest version of the `@stripe/ui-extension-sdk`, including managing breaking changes. It recommends updating the Stripe Apps CLI plugin first for optimal compatibility and highlights new features like property validation in v9.
- [UI components | Stripe Documentation](https://docs.stripe.com/stripe-apps/components): Stripe offers a library of pre-built UI components that developers can use to quickly build interfaces for their apps, ensuring alignment with Stripe's design best practices. These components include various views like ContextView, FocusView, and SettingsView to structure layouts and create interactive experiences.
- [Accordion component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/accordion): The Accordion component allows developers to organize long or complex content into collapsible sections within Stripe Apps. It consists of Accordion and AccordionItem components, providing titles, content, optional actions, and a default open state for better content scanning and access.
- [Badge component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/badge): The Badge component is a read-only UI element used to indicate the state of an item or object within Stripe applications. It supports various types like 'neutral', 'info', 'positive', 'negative', 'warning', and 'urgent' to convey different statuses.
- [Banner component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/banner): The Banner component displays alerts or important messages to users, taking up the full width of its parent container. It is suitable for persistent information that may require user input and comes in 'default', 'caution', and 'critical' types.
- [BarChart component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/barchart): The BarChart component visualizes data using bars, allowing developers to represent data points graphically. It requires data, and specified properties for the x and y axes to render the chart effectively.
- [Box component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/box): The Box component acts as a container for other UI elements, enabling custom styling and layout arrangements. It functions similarly to a `div` element and supports various CSS properties for visual customization.
- [Button component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/button): Buttons in Stripe Apps allow users to perform actions, draw attention, or warn them of outcomes. They can be styled as 'primary', 'secondary', or 'destructive' and support various props for interaction and appearance.
- [ButtonGroup component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/buttongroup): The ButtonGroup component manages the layout of multiple buttons, intelligently collapsing them into an overflow menu when space is limited. This ensures a responsive and organized display of button actions.
- [Checkbox component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/checkbox): Checkboxes are used to indicate or control boolean values within Stripe applications. They can be managed with `checked` and `defaultChecked` props, and support features like labels, descriptions, and error states.
- [Chip component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/chip): Chips display and allow manipulation of values, often used for filtering or displaying attributes. They can be configured with labels, values, and trigger actions like dropdowns or closing, and can be presented in a ChipList.
- [ContextView component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/contextview): The ContextView component serves as the root view for Stripe Apps, rendering them in a side-by-side drawer with Stripe content. It allows apps to provide contextual information and actions within the user's existing workflow.
- [DateField component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/datefield): The DateField component is used to collect date information from users within Stripe applications. It supports features like labels, descriptions, default values, and validation states to ensure accurate data input.
- [DetailPageModule component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/detailpagemodule): The DetailPageModule component is designed to render applications within Stripe dashboard pages. It provides a structured way to integrate app content directly into the dashboard interface.
- [DetailPagePropertyList component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/detailpagepropertylist): The DetailPagePropertyList component is used for rendering applications within Stripe dashboard pages. It allows for the display of property lists in a structured format within the dashboard.
- [DetailPageTable component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/detailpagetable): The DetailPageTable component is utilized to render applications within Stripe dashboard pages. It facilitates the display of tabular data as part of the app's integration into the dashboard.
- [Divider component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/divider): The Divider component renders a simple horizontal rule, used to visually separate content sections. This component is straightforward and does not have any configurable props.
- [FocusView component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/focusview): The FocusView component opens a dedicated space for users to complete specific tasks within Stripe Apps, often used for wizards or confirmation steps. It must be a child of ContextView and is controlled using its `shown` property.
- [FormFieldGroup component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/formfieldgroup): The FormFieldGroup component groups related form fields together, providing a legend and optional description for context. It supports different layouts like 'row' and 'column' for organizing input elements.
- [FullPageTabs component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/fullpagetabs): The FullPageTabs component is used to display distinct sections of content within a full-page layout. It is currently in a private developer preview.
- [FullPageView component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/fullpageview): The FullPageView component is designed for implementing full-page Stripe Apps. This component is also in a private developer preview.
- [Icon component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/icon): The Icon component displays icon graphics in a compatible format within Stripe applications. Developers can select from a wide range of predefined icons by specifying their `name` prop.
- [Img component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/img): The Img component displays images within Stripe applications, supporting responsive design with `srcSet` and controlling dimensions via `width` and `height` props. Developers must include image base URLs in their app's content security policy.
- [Inline component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/inline): The Inline component is used for styling inline content such as text within Stripe Apps. It functions similarly to an HTML span and supports custom CSS for styling.
- [LineChart component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/linechart): The LineChart component visualizes data as a series of connected data points. It requires data, and specified properties for the x and y axes to generate the chart.
- [Link component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/link): The Link component is used to navigate users between pages or to perform actions subtly. It supports both primary and secondary link types and can be configured with an href or an onPress handler.
- [List component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/list): The List component displays information in various preconfigured formats, often used to present items like payments with titles and secondary titles. It supports an onAction handler to respond to press events on list items.
- [Menu component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/menu): The Menu component presents a group of actions for user selection, typically related to a specific object or context. It requires a trigger element and can contain multiple MenuItem components, which can be disabled.
- [OnboardingView component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/onboardingview): The OnboardingView component is used to implement an onboarding flow for Stripe Apps. It serves as a root component for UI elements within the onboarding process.
- [OverviewPage component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/overviewpage): The OverviewPage component is used to implement overview-style layouts within Stripe Apps. This component is currently in a private developer preview.
- [PropertyList component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/propertylist): The PropertyList component displays data as key-value pairs. This component is currently not available in the selected SDK version.
- [Radio component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/radio): The Radio component allows users to make selections from a set of mutually exclusive options. It can be configured with a label, and supports properties like checked, disabled, and error messages.
- [Select component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/select): The Select component is used to create a dropdown for picking an option from a set. It supports various props including label, onChange handler, and options defined within its children.
- [SettingsView component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/settingsview): The SettingsView component allows users to change app-specific details related to their account. It acts as a root component for the app settings page within the Stripe Dashboard.
- [SignInView component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/signinview): The SignInView component is used to display a sign-in screen for apps, ensuring users understand they are connecting to Stripe. It includes options for branding, descriptions, and action buttons.
- [Sparkline component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/sparkline): The Sparkline component displays data succinctly as a simple line, functioning as a compact line chart. It requires data and specified x and y axis properties.
- [Spinner component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/spinner): The Spinner component indicates that content is loading. It can be displayed in small, medium, or large sizes and accepts an optional delay for its animation.
- [Switch component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/switch): The Switch component is used to indicate or control boolean values, functioning similarly to checkboxes. It's often used for immediate settings changes rather than within larger forms.
- [Table component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/table): The Table component displays data in a tabular format with rows and cells. It includes sub-components like TableHead, TableBody, TableCell, and TableFooter for structuring table content.
- [Tabs component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/tabs): The Tabs component displays content in sections, with only one panel visible at a time, and tab elements along the top. It allows for organizing content into distinct, selectable views.
- [TaskList component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/tasklist): The TaskList component helps users track progress through a list of required tasks. This component is currently not available in the selected SDK version.
- [TextArea component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/textarea): The TextArea component creates an input field designed for multiple lines of text. It supports properties like label, placeholder, default value, and an onChange handler.
- [TextField component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/textfield): The TextField component creates a single-line text input field. It includes configurable options for labels, placeholders, and handling user input changes.
- [Toast component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/toast): The Toast component in Stripe Apps is used to inform users about the status of an action with temporary messages. It can display success, caution, or pending states and optionally include an action button.
- [Tooltip component for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/components/tooltip): The Tooltip component for Stripe Apps provides additional contextual information about an element. It can be used as a description or a label and appears when a user hovers or focuses on a trigger element.
- [Design patterns for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/patterns): Design patterns for Stripe Apps provide foundational structures for app design, combining components to create consistent and scalable user experiences. Following these patterns helps expedite the app review process.
- [Lists for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/patterns/lists): The List component in Stripe Apps is used to display collections of information, allowing rows to be clickable and optionally include icons and images. For more control, custom list items can be composed, but their rows are not clickable.
- [Additional context for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/patterns/additional-context): Additional context in Stripe Apps should be provided on a separate screen before users sign in, using components like FocusView or SignInView. This context should be brief and directly related to the user's understanding of the app's functionality.
- [Demo content for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/patterns/demo): When building a demo for a Stripe App, keep the content brief and highlight only the top functionality. A dedicated page view is recommended, providing just enough information to communicate the app's main features.
- [Onboarding for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/patterns/onboarding-experience): An ideal onboarding flow for Stripe Apps is effortless, customizable, and relevant, enabling users to start using the app quickly with minimal setup. The OnboardingView component can be used to clearly communicate required setup tasks.
- [Redirects for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/patterns/redirects): Redirects in Stripe Apps should clearly indicate to users how they can return to the Stripe Dashboard. A call-to-action button is suggested for this purpose, ensuring visual consistency with the app being built.
- [Settings sign in for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/patterns/settings-signin): For backend-only apps or connect extensions, users are onboarded via a settings page using the SignInView component. This approach is applied similarly to a drawer, avoiding extraneous context.
- [Sign in template for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/patterns/sign-in): The SignInView component is essential for Stripe Apps when user sign-in is required, ensuring users understand they are connecting to Stripe. It emphasizes security by not asking for full credentials and keeps the flow focused.
- [Sign out for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/patterns/sign-out): Users must be able to sign out of a Stripe App, and a sign-out link should be placed below the content on every page for easy access. This ensures users can easily disconnect their session.
- [Communicating state for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/patterns/communicating-state): Communicating state in Stripe Apps involves informing users when they need to take action. Toasts provide temporary feedback after an action, while banners are used for persistent notifications about system-level issues or requirements.
- [Empty state for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/patterns/empty-state): The empty state pattern in Stripe Apps clearly indicates when no data is available to load. It can include links to specific sections of the Dashboard, guiding users on where to find or create data.
- [Loading for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/patterns/loading): When data is loading in a Stripe App, a Spinner component should be used to indicate progress. Providing additional context about the type of data being loaded enhances the user experience.
- [Progress stepping for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/patterns/progress-stepping): Progress stepping in Stripe Apps uses components like FocusView to guide users through multi-step tasks, preventing accidental abandonment. Progress stepping components are typically placed in the footer, with the final action being a primary button.
- [Waiting screens for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/patterns/waiting-screens): Waiting screens in Stripe Apps keep users informed during the onboarding process, setting clear expectations for wait times and next steps. They are crucial for maintaining user engagement if they navigate away and return.
- [Action buttons for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/patterns/action-buttons): Action buttons in Stripe Apps should be placed consistently, typically in the header for visibility even when content scrolls off-screen. If content doesn't require scrolling, buttons can be placed below the content.
- [Back link for Stripe Apps | Stripe Documentation](https://docs.stripe.com/stripe-apps/patterns/back-link): Back links in Stripe Apps allow users to navigate to a previous page using a Link component with an Icon. The destination of the back link should be clearly labeled for user clarity.
- [Style your app | Stripe Documentation](https://docs.stripe.com/stripe-apps/style): Stripe Apps can be styled using provided design tokens to match the Dashboard's visual consistency. The Box and Inline components support custom styles via the 'css' prop, adhering to specific CSS syntax and typography rules.
- [Design your app | Stripe Documentation](https://docs.stripe.com/stripe-apps/design): Stripe Apps leverage provided UI components and design patterns to simplify the design process. Custom styling is intentionally limited to maintain platform consistency and ensure high accessibility standards.
- [Upload and install your Stripe App | Stripe Documentation](https://docs.stripe.com/stripe-apps/upload-install-app): This document explains how to upload and install your Stripe App within your Stripe account. It covers the steps for uploading in test mode and then installing it, making it available to team members. For wider distribution, publishing on the Stripe App Marketplace is also mentioned.
- [Using roles in UI extensions | Stripe Documentation](https://docs.stripe.com/stripe-apps/using-roles-in-ui-extensions): This page details how to use user roles within Stripe Apps UI extensions to tailor functionality. It explains that the UI Extension SDK provides access to the active user's roles via the userContext object. This allows apps to display different content or features based on the user's assigned role in the Dashboard.
- [Manage your app's versions and releases | Stripe Documentation](https://docs.stripe.com/stripe-apps/versions-and-releases): This guide explains Stripe Apps versioning and releases, providing a framework for managing app changes over time. A 'version' is defined by the app manifest, while a 'release' is a published version available to users. Stripe automatically upgrades users to the latest release, except when permission scopes change.
- [Stripe for Visual Studio Code | Stripe Documentation](https://docs.stripe.com/stripe-vscode): Stripe for Visual Studio Code is an extension that allows developers to build, test, and interact with Stripe directly within their editor. It offers features like an AI assistant for Stripe integrations, code snippet generation, real-time log streaming, and access to the Stripe Dashboard.
- [Use the API to respond to disputes | Stripe Documentation](https://docs.stripe.com/disputes/api): This documentation explains how to programmatically manage disputes using the Stripe API, including uploading evidence and responding to disputes. It provides examples of how to retrieve a dispute object and update it with structured evidence data. The process involves using API endpoints to interact with dispute and evidence details.
- [Dispute evidence best practices | Stripe Documentation](https://docs.stripe.com/disputes/best-practices): This guide outlines best practices for formatting and organizing evidence to effectively challenge a payment dispute. It recommends presenting evidence chronologically and grouping it by type, with clear summaries for each piece. Maintaining clarity and readability is crucial for the reviewer.
- [Dispute reason code categories | Stripe Documentation](https://docs.stripe.com/disputes/categories): This page categorizes dispute reason codes into eight main groups across different payment methods, simplifying the understanding of claim types and required evidence. It provides tables outlining Stripe's categories and corresponding codes for major networks like Visa. Managing disputes can be done via the Dashboard or API.
- [Configure Smart Disputes auto-respond settings | Stripe Documentation](https://docs.stripe.com/disputes/smart-disputes/auto-respond): This document explains how to configure Smart Disputes auto-respond settings to automatically submit evidence for eligible disputes. It details how this feature helps avoid missed deadlines and reduces manual effort. Settings can be configured for direct accounts via the Dashboard and managed by platforms for their connected accounts.
- [Disputes on Connect platforms | Stripe Documentation](https://docs.stripe.com/connect/disputes): This guide covers dispute responsibilities on Stripe Connect platforms, explaining how charge type and negative balance liability determine who responds to a dispute and which account is debited. For direct charges, connected accounts typically handle their own disputes unless the platform is liable for negative balances, in which case the platform is ultimately responsible.
- [Dispute withdrawals | Stripe Documentation](https://docs.stripe.com/disputes/withdrawing): This page explains what happens when a cardholder withdraws a dispute, clarifying that it's not an automatic win and still counts towards dispute rates. While a withdrawn dispute doesn't resolve faster, cardholders can only fully withdraw financial disputes (chargebacks), not early fraud warnings or inquiries.
- [How disputes work | Stripe Documentation](https://docs.stripe.com/disputes/how-disputes-work): This document outlines the lifecycle of payment card disputes, starting when an account owner contests a charge. Stripe notifies the merchant, debits the disputed amount and fee, and provides tools to submit evidence. While Stripe facilitates the process, the final decision rests with the account owner's bank.
- [Disputes | Stripe Documentation](https://docs.stripe.com/disputes): This page provides an overview of Stripe disputes, explaining that they occur when a cardholder questions a payment with their bank, leading to a reversal of funds and fees. Stripe guides users through responding to disputes in the Dashboard and offers tools for analysis, prevention, and automation.
- [High risk merchant lists | Stripe Documentation](https://docs.stripe.com/disputes/match): This document explains the criteria for inclusion in high-risk merchant lists like Mastercard's MATCH and Visa's VMSS. These lists contain information about merchants terminated for high chargebacks or rule violations, and being listed can significantly impact a business's ability to process payments.
- [Measuring disputes | Stripe Documentation](https://docs.stripe.com/disputes/measuring): This page details how Stripe measures disputes using 'dispute activity' and 'dispute rate' calculations. Dispute activity is based on the dispute date, while dispute rate is based on the charge date. These metrics are used by card networks for monitoring programs and can lead to fines if thresholds are exceeded.
- [Dispute and fraud card monitoring programs | Stripe Documentation](https://docs.stripe.com/disputes/monitoring-programs): This document explains card network monitoring programs that merchants are placed into if their dispute or fraud levels exceed acceptable thresholds. Exceeding these limits can result in fines and additional fees, requiring merchants to take immediate action to reduce their dispute or fraud rates.
- [How dispute prevention works | Stripe Documentation](https://docs.stripe.com/disputes/get-started/prevention): This page introduces Stripe's integrations with Verifi and Ethoca for dispute prevention, which help reduce dispute rates and retain revenue. These solutions offer features like Rapid Dispute Resolution (RDR) to automatically resolve disputes, preventing them from impacting dispute rates and avoiding fees.
- [Dispute prevention | Stripe Documentation](https://docs.stripe.com/disputes/prevention-preview): This document describes Stripe's dispute prevention tools, which help reduce costs and automate management by resolving or deflecting disputes. Features include setting resolution rules via Stripe Radar for automatic refunds and providing extra transaction data to block disputes with compelling evidence.
- [Understand fraud | Stripe Documentation](https://docs.stripe.com/disputes/prevention): This page discusses how Stripe helps identify and prevent fraud and disputed payments through various tools and resources. It covers different types of fraud, card testing identification, common fraud indicators, and best practices such as clear customer communication and multi-factor authentication.
- [Advanced fraud detection | Stripe Documentation](https://docs.stripe.com/disputes/prevention/advanced-fraud-detection): This document explains how Stripe.js and mobile SDKs provide advanced fraud detection by analyzing device characteristics and user activity. These signals enhance Stripe's fraud prevention systems like Radar, and hCaptcha can be optionally used to provide additional signals and stop fraud.
- [Best practices for preventing fraud | Stripe Documentation](https://docs.stripe.com/disputes/prevention/best-practices): This page outlines best practices for preventing fraud and disputes, emphasizing clear and transparent customer communication to reduce disputes and encourage timely issue resolution. It also mentions using tools like Radar and implementing safeguards such as strong customer service and clear refund policies.
- [Protect yourself from card testing | Stripe Documentation](https://docs.stripe.com/disputes/prevention/card-testing): Card testing is a fraudulent activity where criminals validate stolen card information to make unauthorized purchases. Merchants, card networks, and Stripe share responsibility in preventing it, with Stripe offering tools to detect and reduce fraud.
- [Customer abuse | Stripe Documentation](https://docs.stripe.com/disputes/prevention/abuse): Customer abuse exploits business policies through actions like refund abuse, where customers repeatedly exploit refund policies, or resale and trial abuse. Businesses can prevent, detect, and mitigate these issues by analyzing customer behavior and adapting policies.
- [Common types of online fraud | Stripe Documentation](https://docs.stripe.com/disputes/prevention/fraud-types): Online fraud occurs when a cardholder did not authorize a payment, often using stolen card details. Unlike physical retail, online environments make it harder to verify customer identity, necessitating awareness of various fraud types and potential liabilities.
- [Identifying potential fraud | Stripe Documentation](https://docs.stripe.com/disputes/prevention/identifying-fraud): Merchants are best positioned to identify potential fraud due to their direct customer information and order fulfillment role. While external indicators like Early Fraud Warnings exist, a combination of implicit indicators can more strongly suggest fraudulent activity, allowing for proactive review or blocking of payments.
- [Card verification checks | Stripe Documentation](https://docs.stripe.com/disputes/prevention/verification): Card verification checks, including CVC, postal code, and billing address verification, help protect against fraud and disputes. A failed verification can indicate fraudulent activity, and collecting this information is crucial for the card issuer to perform these checks.
- [Dispute reason codes | Stripe Documentation](https://docs.stripe.com/disputes/reason-codes-defense-requirements): Card networks define specific reason codes for disputes, which Stripe categorizes into seven main types. Understanding these codes and the required evidence for each network (Visa, Mastercard, American Express) is essential for challenging disputes.
- [Respond to disputes | Stripe Documentation](https://docs.stripe.com/disputes/responding): When a cardholder disputes a payment, their bank notifies Stripe, which then alerts the merchant via email, the Dashboard, or API events. Merchants must respond to disputes before a deadline to avoid automatic loss of funds, with options to manage them manually or programmatically.
- [Set up and configure Smart Disputes | Stripe Documentation](https://docs.stripe.com/disputes/set-up-smart-disputes): Smart Disputes automatically compiles and submits evidence packets for eligible disputes before the deadline, aiming to improve win rates and recover revenue. While it automates much of the process, users retain full control to review, edit, or submit their own evidence.
- [Smart Disputes | Stripe Documentation](https://docs.stripe.com/disputes/smart-disputes): Smart Disputes automates evidence collection, compilation, and submission for eligible card disputes using an AI rules engine. This process saves time and helps recover revenue by tailoring evidence packets to specific dispute reasons, requiring no additional integration for existing Stripe users.
- [Visa Compelling Evidence 3.0 disputes | Stripe Documentation](https://docs.stripe.com/disputes/api/visa-ce3): Visa Compelling Evidence 3.0 (CE 3.0) allows businesses to combat friendly fraud by demonstrating a non-fraudulent history with cardholders. Meeting specific criteria, such as previous undisputed transactions and providing detailed product descriptions, can increase the likelihood of a favorable dispute reversal.
- [Visa compliance disputes | Stripe Documentation](https://docs.stripe.com/disputes/api/visa-compliance): Visa compliance disputes arise when a transaction allegedly violates Visa's network rules. Contesting these disputes incurs a $500 fee from Stripe, which is refunded if the merchant wins, and can be identified by specific indicators in the dispute object.
- [Dispute sample evidence packets | Stripe Documentation](https://docs.stripe.com/disputes/visual-evidence): Sample evidence packets provide visual examples and best practices for navigating common network dispute categories like 'Credit not processed,' 'Duplicate,' and 'Fraudulent.' These resources help merchants effectively demonstrate proof for or against a dispute claim.
- [Charge for shipping | Stripe Documentation](https://docs.stripe.com/payments/during-payment/charge-shipping): Shipping rates allow businesses to offer various shipping options with estimated delivery times, charging customers accordingly. These rates support fixed amounts per order and can be created and managed through the Stripe Dashboard or API.
- [Address Element | Stripe Documentation](https://docs.stripe.com/elements/address-element): The Address Element is an embeddable UI component for collecting complete billing and shipping addresses, essential for tax purposes and order fulfillment. It offers customization options for theme, size, and phone number collection, localizing the UI based on customer location.
- [Currency Selector Element | Stripe Documentation](https://docs.stripe.com/elements/currency-selector-element): The Currency Selector Element is an embeddable UI component that automatically displays prices in the customer's local currency, enhancing the shopping experience with Adaptive Pricing. It requires integration with the Checkout Sessions API and adherence to local price localization laws.
- [Manage payment methods in settings | Stripe Documentation](https://docs.stripe.com/elements/customer-sheet): The Payment Method Settings Sheet (CustomerSheet) is a prebuilt UI component for iOS, Android, and React Native apps, allowing customers to manage their saved payment methods within app settings. It enables adding, removing, and setting default payment methods, integrating with the broader in-app payments solution.
- [Build an integration with an embeddable payment form | Stripe Documentation](https://docs.stripe.com/elements/embeddable-payment-form): An embeddable payment form allows for collecting comprehensive checkout information within a single iframe, offering granular control over the UI's look and feel. It supports over 100 payment methods, express checkout options, address collection, shipping, and tax details, with UI customization via the Stripe Appearance API.
- [Express Checkout Element | Stripe Documentation](https://docs.stripe.com/elements/express-checkout-element): The Express Checkout Element is a component for accepting payments through one-click buttons for methods like Link, Apple Pay, Google Pay, and PayPal. It dynamically sorts payment buttons based on customer location and can be integrated seamlessly with existing Elements instances.
- [Accept a payment with the Express Checkout Element | Stripe Documentation](https://docs.stripe.com/elements/express-checkout-element/accept-a-payment): The Express Checkout Element facilitates accepting payments via one-click buttons for various methods including Link, Apple Pay, Google Pay, and PayPal. Customers see relevant buttons based on their device and browser, with specific steps required for certain payment methods like Apple Pay and PayPal.
- [Migrate to the Express Checkout Element | Stripe Documentation](https://docs.stripe.com/elements/express-checkout-element/migration): Migrating from the Payment Request Button Element to the Express Checkout Element allows for accepting a wider range of card and wallet payments through multiple one-click buttons, including PayPal. This migration requires using the Payment Intents API and enabling desired payment methods in settings.
- [Payment Method Messaging Element | Stripe Documentation](https://docs.stripe.com/elements/payment-method-messaging): The Payment Method Messaging Element is a UI component that automatically informs customers about available buy-now-pay-later plans. It determines eligible plans, generates localized descriptions, and displays them in your form's theme. This element helps improve conversion rates by clearly presenting financing options to users.
- [Payment Request Button | Stripe Documentation](https://docs.stripe.com/stripe-js/elements/payment-request-button): The Payment Request Button Element is a deprecated feature that dynamically displays wallet options like Apple Pay, Google Pay, and Link during checkout. It offers a single integration for these payment methods, but the Express Checkout Element is now recommended as a replacement. This element aimed to streamline the checkout process for users with saved payment information.
- [Tax ID Element | Stripe Documentation](https://docs.stripe.com/elements/tax-id-element): The Tax ID Element is an embeddable UI component for collecting business tax identification numbers from customers. It can be used with either the Elements with Checkout Sessions API or the Payment Intents API integrations. This element is useful for businesses that need to collect tax IDs for invoicing or VAT refund purposes.
- [Send events to Amazon EventBridge | Stripe Documentation](https://docs.stripe.com/event-destinations/eventbridge): This page explains how to send Stripe events to Amazon EventBridge, an AWS serverless event bus. By enabling Workbench and creating an event destination, Stripe events can be routed directly to your AWS account. This integration allows for automated processing and triggering of business workflows based on Stripe events without managing integration code.
- [Integrate with events | Stripe Documentation](https://docs.stripe.com/event-destinations): Stripe event destinations allow you to send events from Stripe to various cloud services and webhook endpoints. You can receive either self-contained snapshot events or lightweight thin events for real-time data. This enables backend systems to respond to events like payment confirmations, disputes, or subscription renewals, automating actions and streamlining integrations.
- [Process incoming webhooks with event notification handlers | Stripe Documentation](https://docs.stripe.com/webhooks/event-notification-handlers): Event notification handlers provide a way to process incoming Stripe webhooks by encapsulating the mechanics of parsing and validation within SDKs. These handlers validate, parse, and route webhooks to your business logic, requiring you to write specific functions for each event type. A fallback callback can also be implemented to handle unexpected event types.
- [Handle payment events with webhooks | Stripe Documentation](https://docs.stripe.com/webhooks/handling-payment-events): Webhooks allow your application to be notified about payment events that occur outside of your direct payment flow, such as successful payments or disputes. By building a webhook handler on your server, you can manage offline payment flows and scale your integration. Stripe sends an Event object with each request, enabling your application to react to changes in your Stripe account.
- [Receive Stripe events in your webhook endpoint | Stripe Documentation](https://docs.stripe.com/webhooks): This document details how to set up a webhook endpoint to receive and process events from Stripe. It explains that Stripe pushes real-time event data to your application's endpoint via HTTPS as a JSON payload. Receiving these events allows your integration to automatically respond to asynchronous occurrences like payment confirmations or disputes.
- [Expanding responses | Stripe Documentation](https://docs.stripe.com/expand): The Expand feature allows you to retrieve additional properties from related objects in a single API call, reducing the number of requests needed. Instead of making multiple calls to fetch linked data, you can specify which related objects or properties to include in the initial response. This optimizes API usage by minimizing latency and complexity.
- [Use cases for expanding responses | Stripe Documentation](https://docs.stripe.com/expand/use-cases): This page illustrates common use cases for expanding API responses, such as retrieving payment processing fees within a single call. By using the `expand` parameter, you can include details like balance transactions directly in the response for payment intents. This avoids the need for separate API requests to gather related information.
- [Collect a bank account to use ACH Direct Debit payments with account data | Stripe Documentation](https://docs.stripe.com/financial-connections/ach-direct-debit-payments): Stripe's Financial Connections enables instant bank account verification for ACH Direct Debit payments, reducing failure rates and improving conversion. It allows for the collection of account data like balances and ownership information, saving development time by eliminating custom forms. Financial Connections is the default verification method for hosted ACH payment flows.
- [Access balances for a Financial Connections account | Stripe Documentation](https://docs.stripe.com/financial-connections/balances): The Financial Connections API allows you to retrieve up-to-date balances for a user's linked financial account with their permission. This balance data is valuable for reducing insufficient funds failures for ACH payments, underwriting, and building financial management tools. Accessing balances requires a completed Financial Connections registration.
- [Collect a bank account to enhance Connect payouts | Stripe Documentation](https://docs.stripe.com/financial-connections/connect-payouts): Financial Connections helps platforms collect bank account details for connected accounts to enhance payouts, especially when liable for negative balances. It increases onboarding conversion by keeping users on session and reduces payout failures by eliminating manual entry errors. Platforms can optionally request permission to access additional account data like balances and ownership for fraud mitigation.
- [Deployment checklist | Stripe Documentation](https://docs.stripe.com/financial-connections/deployment-checklist): This checklist ensures a smooth deployment for web-based Financial Connections integrations. Key steps include configuring the Cross-Origin-Opener-Policy and Referrer-Policy response headers correctly. It also advises on iframe sandbox properties to prevent interference with OAuth bank login flows.
- [Disconnect a Financial Connections account | Stripe Documentation](https://docs.stripe.com/financial-connections/disconnections): The Disconnect API allows you to unlink a user's Financial Connections Account, revoking data access. While associated PaymentMethods remain usable, new data cannot be refreshed without re-authentication. Disconnecting an account is necessary when data access is no longer needed or upon user request, and it triggers a `financial_connections.account.disconnected` webhook.
- [Financial Connections fundamentals | Stripe Documentation](https://docs.stripe.com/financial-connections/fundamentals): Stripe Financial Connections consists of two main parts: collecting bank account information through an authentication flow and retrieving data from those accounts. The process involves creating a Financial Connections Session on the server, returning a client secret to the client, and initiating the authentication flow. After users link their accounts, data refreshes can be initiated from the server to retrieve details.
- [Stripe Financial Connections | Stripe Documentation](https://docs.stripe.com/financial-connections): Stripe Financial Connections allows businesses to securely access permissioned financial data from users' bank accounts. It enables instant bank account verification for ACH payments, reduces underwriting risk with balance data, mitigates fraud with ownership details, and facilitates building fintech products with transaction data. Financial Connections is available for businesses using US bank accounts in supported countries.
- [Collect an account to build data-powered products | Stripe Documentation](https://docs.stripe.com/financial-connections/other-data-powered-products): This page describes how to collect user bank account information using Financial Connections to build data-powered products. It allows access to tokenized account numbers, balances, ownership details, and transaction history. This data can be used to mitigate fraud, help users track finances, and speed up underwriting for financial services.
- [Verify bank account ownership with Financial Connections | Stripe Documentation](https://docs.stripe.com/financial-connections/ownership-match): The Ownership Match API helps verify if a user owns a specific bank account by comparing Financial Connections ownership data with provided information. It computes match scores to assess ownership accuracy. Accessing this feature requires a completed Financial Connections registration and specific API version settings.
- [Access ownership details for a Financial Connections account | Stripe Documentation](https://docs.stripe.com/financial-connections/ownership): The Financial Connections API enables retrieval of ownership details for a linked financial account, which is useful for fraud reduction and underwriting. This process requires a completed Financial Connections registration and involves requesting access to ownership data. It is recommended to create a Customer object to represent the user and attach it to payments for better authentication flow.
- [Relink Financial Connections accounts used for data products. | Stripe Documentation](https://docs.stripe.com/financial-connections/relink/api/data-products): This page explains how to relink Financial Connections accounts that have become inactive, enabling the retrieval of data and updating of permissions. It details reasons for account deactivation, such as expired OAuth tokens or changes in financial institution requirements, and how to handle these situations using webhooks and the API.
- [Use the Financial Connections API to relink an account | Stripe Documentation](https://docs.stripe.com/financial-connections/relink/api): This document outlines how to use the Financial Connections API to integrate an account relinking flow directly into a website or application. It describes the server-side and client-side steps required to prompt customers to reauthorize accounts, restore data access, or update permissions.
- [Relink Financial Connections accounts used for payments or payouts. | Stripe Documentation](https://docs.stripe.com/financial-connections/relink/api/payments-or-payouts): This page details how to relink Financial Connections accounts specifically for payments or payouts, allowing for the reactivation of inactive accounts and tokenized account numbers. It explains scenarios where relinking is necessary, such as restoring data access or refreshing expired tokenized account numbers for transactions.
- [Hosted relink | Stripe Documentation](https://docs.stripe.com/financial-connections/relink/hosted): Hosted relink is a Stripe feature that enables the repair of broken connections to bank accounts linked via Financial Connections. Stripe contacts customers on your behalf to prompt them to relink their accounts, which helps repair data connections or tokenized account numbers for inactive accounts.
- [Relink a Financial Connections account with your user's permission | Stripe Documentation](https://docs.stripe.com/financial-connections/relink): This guide explains how to prompt users to relink their Financial Connections accounts to restore data access, refresh tokenized account numbers, and update data permissions. It covers reasons why accounts become inactive and how relinking helps maintain access to financial data and payment capabilities.
- [Supported institutions of Financial Connections | Stripe Documentation](https://docs.stripe.com/financial-connections/supported-institutions): This page provides a searchable list of financial institutions supported by Stripe's Financial Connections. It details which institutions offer account details, ownership details, balance data, and transaction data, helping users identify compatible banks for integration.
- [Test Financial Connections | Stripe Documentation](https://docs.stripe.com/financial-connections/testing): This documentation explains how to test Stripe Financial Connections using a sandbox environment and test API keys. It covers using test institutions, simulating user authentication scenarios, and how features like balances and transactions behave with test data.
- [Manage bank accounts with Tokenized Account Numbers | Stripe Documentation](https://docs.stripe.com/financial-connections/tokenized-account-numbers): This page introduces Tokenized Account Numbers (TANs), which are temporary bank account credentials used by Stripe Financial Connections. It explains how TANs function similarly to real account numbers for ACH payments and payouts but can be deactivated, potentially causing transactions to fail.
- [Access transactions for a Financial Connections account | Stripe Documentation](https://docs.stripe.com/financial-connections/transactions): This document describes how to access transaction data for a Financial Connections account with user permission. It highlights the use of transaction data for underwriting, fraud mitigation, and helping users manage their finances.
- [Financial Connections use cases | Stripe Documentation](https://docs.stripe.com/financial-connections/use-cases): This page outlines the various use cases for Stripe Financial Connections, including collecting ACH payments, facilitating Connect payouts, and building financial data products. It provides guidance on integration paths and common applications for financial data.
- [Get real-time updates from Financial Connections with webhooks | Stripe Documentation](https://docs.stripe.com/financial-connections/webhooks): This document explains how to use webhooks to receive real-time updates about activity on Financial Connections accounts. It details core webhooks like account creation, deactivation, and reactivation, as well as those triggered by data refreshes for balances, ownership, and transactions.
- [Forward card details to your own token vault | Stripe Documentation](https://docs.stripe.com/payments/forwarding-token-vault): This page describes how to forward card details collected by Stripe to your own token vault for storage. It outlines the process of creating a PaymentMethod and a ForwardingRequest to securely transfer sensitive card information.
- [Use Payment Element across multiple processors | Stripe Documentation](https://docs.stripe.com/payments/forwarding-third-party-processors): This guide explains how to use Stripe's Payment Element to build a custom payment flow for collecting card details and forwarding them to a third-party processor. It details the client-side and server-side steps involved in this integration.
- [Branding your Stripe account | Stripe Documentation](https://docs.stripe.com/get-started/account/branding): This page explains how to customize the appearance of your Stripe account and customer-facing elements, such as emails, checkout pages, and invoices. It details the types of branding assets and colors that can be configured and where they are applied.
- [Go-live checklist | Stripe Documentation](https://docs.stripe.com/get-started/checklist/go-live): This document provides a checklist for taking a Stripe integration live, covering essential steps like setting the API version and handling edge cases. It emphasizes ensuring the live and sandbox environments are synchronized and preparing for production.
- [Website checklist | Stripe Documentation](https://docs.stripe.com/get-started/checklist/website): This page offers a checklist for website best practices to ensure alignment with card network standards and e-commerce guidelines. It stresses the importance of clear product descriptions, explicit currency display, and readily available customer service contact information.
- [Set up your development environment | Stripe Documentation](https://docs.stripe.com/get-started/development-environment): This guide explains how to set up your development environment using the Stripe CLI and server-side SDKs. It covers installing necessary tools, interacting with Stripe APIs, and preparing for integration development.
- [Send your first Stripe API request | Stripe Documentation](https://docs.stripe.com/get-started/api-request): This page details how to send your first Stripe API request, focusing on creating a customer object. It explains the necessity of API secret keys and how to use the Stripe Shell for testing API interactions in a sandbox environment.
- [Accept in-person payments for a direct retail business | Stripe Documentation](https://docs.stripe.com/get-started/use-cases/in-person-payments): This guide explains how to set up a Stripe integration to accept in-person card payments for a direct retail business. It recommends using a Stripe Reader S700/S710 with a server-driven integration and outlines the steps for account creation and reader setup.
- [Get started | Stripe Documentation](https://docs.stripe.com/get-started): This page serves as a starting point for new Stripe users, guiding them through account creation and initial development steps. It highlights common use cases, migration guides, and resources for building on the Stripe platform.
- [Send invoices to collect payments for an online business | Stripe Documentation](https://docs.stripe.com/get-started/use-cases/invoices): This guide explains how to send invoices to collect payments for an online business, particularly for SaaS startups targeting enterprise clients. It covers creating a Stripe account, setting up test invoices, and integrating with Stripe for automated invoicing to reduce manual processes and payment delays.
- [Overview | Stripe Documentation](https://docs.stripe.com/get-started/data-migrations/overview): This page provides an overview of the Stripe data migration process, guiding users through understanding the steps, scoping timelines, and identifying required integration elements. It emphasizes building a Stripe integration, developing a data migration plan starting with new customers, and reviewing migration documentation.
- [Stripe profiles | Stripe Documentation](https://docs.stripe.com/get-started/account/profile): Stripe profiles allow businesses to create a public identity on Stripe, enabling them to be found, verified, and connected with by other businesses. Creating a profile involves inputting basic business information once for use across Stripe and optionally publishing selected charts and metrics.
- [Quickstart guides | Stripe Documentation](https://docs.stripe.com/quickstarts): This page lists all Stripe integration quickstart guides, offering interactive code samples and step-by-step instructions for various payment scenarios. Guides cover accepting carbon removal payments, in-person payments, subscriptions, custom checkouts, and creating/sending invoices.
- [Reporting and reconciliation | Stripe Documentation](https://docs.stripe.com/plan-integration/get-started/reporting-reconciliation): This document details how to use Stripe for reporting and reconciliation, focusing on automatic payouts and balance transactions for simplified financial management. It explains how to retrieve transactions included in automatic payouts using the balance transaction endpoint and highlights the use of auto-pagination for large transaction volumes.
- [Sell subscriptions as a SaaS startup | Stripe Documentation](https://docs.stripe.com/get-started/use-cases/saas-subscriptions): This guide helps SaaS startups launch a subscriptions integration to accept recurring flat-rate payments using Stripe-hosted Checkout. It covers creating a Stripe account, setting up test products and prices, and integrating with Stripe Checkout for a pre-built payment page experience.
- [Server-side integration | Stripe Documentation](https://docs.stripe.com/plan-integration/get-started/server-side-integration): This guide outlines how to set up an optimal Stripe backend integration by covering authentication, API request best practices, and webhook configuration. It explains using API keys for authentication, implementing idempotency keys for safe retries, and attaching PaymentMethods to Customer objects for storing payment details.
- [Accept simple payments for a startup | Stripe Documentation](https://docs.stripe.com/get-started/use-cases/startup): This guide explains how startups can accept simple, one-off payments using Stripe without writing code, focusing on Payment Links. It details creating a Stripe account, setting up products, generating a payment link, and sharing it with customers for online sales.
- [Build and test new features | Stripe Documentation](https://docs.stripe.com/get-started/test-developer-integration): This guide explains how to use Stripe developer tools to build and test new features without impacting live operations or customer data. It covers using Sandboxes for isolated testing, managing integrations with Workbench, and automating processes with event destinations.
- [Build a subscriptions solution for an AI startup with a usage-based pricing model | Stripe Documentation](https://docs.stripe.com/get-started/use-cases/usage-based-billing): This guide details how SaaS startups can build a usage-based pricing model for their services, using a fictional AI company as an example. It covers creating a Stripe account, setting up a testing environment with sandboxes and test clocks, and implementing a customized UI and payment flow for billing based on usage.
- [Common use cases | Stripe Documentation](https://docs.stripe.com/get-started/use-cases): This page provides an overview of common Stripe use cases, helping businesses choose the best integration for their needs, whether online or in-person. It categorizes use cases by business model, including accepting simple payments, selling subscriptions, usage-based billing, and in-person payments.
- [Create and manage cards | Stripe Documentation](https://docs.stripe.com/financial-accounts/cards): This page explains how to create and manage prepaid debit cards, both virtual and physical, using Stripe's Global Financial Accounts. It covers creating cards, activating them, and freezing them to manage expenses and pay bills directly within the Stripe Dashboard.
- [Manage money with Financial Accounts | Stripe Documentation](https://docs.stripe.com/financial-accounts): This page describes how to securely manage money using Stripe Financial Accounts, which are available in a limited public preview. Financial Accounts allow users to store funds, open local accounts, convert currencies, send money, manage expenses, and borrow money directly in the Stripe Dashboard.
- [Instant currency conversion | Stripe Documentation](https://docs.stripe.com/instant-currency-conversion): This page explains how to instantly convert between currencies using Stripe's Instant Currency Conversion feature, available for eligible funds in payments balances or financial accounts. It details how to perform conversions in the Dashboard and lists supported currencies and associated pricing.
- [Use stablecoins in Financial Accounts | Stripe Documentation](https://docs.stripe.com/financial-accounts/stablecoins): This page details how to use stablecoins within Stripe Financial Accounts for receiving, storing, and sending funds globally. It covers adding funds to a stablecoin balance from a bank account or crypto wallet, and setting up recurring transfers from a Stripe payments balance.
- [Create a Global Payout recipient with the API | Stripe Documentation](https://docs.stripe.com/global-payouts/api-recipient-creation): This page explains how to create Global Payout recipients using the Stripe API, focusing on building an information collection flow for recipient and payout method details. It outlines required parameters for creating an account ID and the payout methods that can be enabled, such as local bank transfers and wire transfers.
- [Get started with Global Payouts | Stripe Documentation](https://docs.stripe.com/global-payouts/get-started): This guide provides instructions on how to get started with Stripe Global Payouts, covering account activation, configuration, and communication settings. It details how to add team members with different access levels and configure optional payout settings for sending payouts from the Stripe Dashboard, Stripe-hosted forms, or the API.
- [Global Payouts | Stripe Documentation](https://docs.stripe.com/global-payouts): This page introduces Stripe Global Payouts, a feature that allows sending funds directly to third parties in their local currency across more than 50 countries. It highlights no-code and API-driven integration options for creating recipients and sending money, with features like recipient verification and multi-currency funding.
- [Manage payouts | Stripe Documentation](https://docs.stripe.com/global-payouts/manage-payouts): This page explains how to manage payouts after creation, including viewing payout statuses, receiving status change events, reversing payouts, and accessing reports. It details various payout statuses like processing, failed, canceled, posted, and returned, and how to interpret them in the Dashboard or via the API.
- [Create recipients | Stripe Documentation](https://docs.stripe.com/global-payouts/recipient-creation-options): This page outlines the options for creating recipients for Global Payouts, whether through the Stripe Dashboard or the API. It explains the required information such as country, business type, email, and intended payout method, and introduces different requirement collection methods including Stripe-hosted forms.
- [Compare with Connect | Stripe Documentation](https://docs.stripe.com/global-payouts/compare-with-connect): Stripe offers two payout integrations: Global Payouts for direct bank transfers and Connect payouts which stage funds in a payee balance first. Global Payouts is ideal for payouts-only solutions, while Connect payouts suit businesses needing bundled payment and payout services.
- [Pricing | Stripe Documentation](https://docs.stripe.com/global-payouts/pricing): Stripe Global Payouts has a tiered pricing structure based on payout methods and destination countries. Fees include standard payout fees, cross-border fees, and FX fees for currency conversions, with specific rates detailed for various methods like local bank transfers and wires.
- [Send money | Stripe Documentation](https://docs.stripe.com/global-payouts/send-money): Stripe Global Payouts allows sending money in local currencies to over 90 countries via the Dashboard or API. Payout methods vary in speed and cost, with options like standard bank transfers, wires, and instant debit card payouts available for US senders.
- [Stripe-hosted recipient creation | Stripe Documentation](https://docs.stripe.com/global-payouts/stripe-hosted-recipient-creation): Stripe-hosted recipient creation uses a dynamic web form to collect recipient information and payout credentials. This form can be customized with branding and programmatically generated via the Account Links API, simplifying the onboarding process for recipients.
- [Test Global Payouts | Stripe Documentation](https://docs.stripe.com/global-payouts/testing): Testing Stripe Global Payouts involves using a sandbox environment with a sandbox API key. Users can fund their sandbox storage balance and simulate sending payouts to confirm their integration functions correctly before going live.
- [Stripe Glossary | Stripe Documentation](https://docs.stripe.com/glossary): The Stripe Glossary defines key terms used across Stripe's documentation and services. It covers a wide range of concepts, from payment authentication methods like 3D Secure to financial network terms like ACH and specific Stripe features like Adaptive Acceptance.
- [Google Pay | Stripe Documentation](https://docs.stripe.com/google-pay): Google Pay integrates with Stripe to allow customers to pay using cards saved in their Google Account, supporting Strong Customer Authentication (SCA). It offers a faster checkout experience for online and in-app purchases of various goods and services.
- [Access verification results | Stripe Documentation](https://docs.stripe.com/identity/access-verification-results): Stripe Identity allows access to verification results through the Identity Dashboard or programmatically via API keys. Sensitive data access may require restricted API keys, and it's recommended to store only references to verification data to enhance security and compliance.
- [Before going live | Stripe Documentation](https://docs.stripe.com/identity/before-going-live): Before going live with Stripe Identity, businesses should ensure their use case is supported, configure branding, and understand pricing. Limiting submission attempts and sensitive information storage are key best practices for a production-ready integration.
- [Explain Identity to your customers | Stripe Documentation](https://docs.stripe.com/identity/explaining-identity): This guide provides pre-approved copy for explaining Stripe Identity to customers, covering how verification works, data access, and best practices. It also prompts businesses to answer open-ended questions about why verification is needed and how rejections are handled.
- [Handle verification outcomes | Stripe Documentation](https://docs.stripe.com/identity/handle-verification-outcomes): Handling verification outcomes in Stripe Identity involves listening for event notifications when a verification completes processing. Webhooks are used to notify your application about status updates, enabling automatic reactions to successful or failed verification checks.
- [Identity | Stripe Documentation](https://docs.stripe.com/identity): Stripe Identity verifies the identity of global users to prevent fraud and increase trust by analyzing government-issued ID documents, selfies, and other data. It supports various verification checks and offers features like reusable verification flows and API integration.
- [Insights | Stripe Documentation](https://docs.stripe.com/identity/insights): Stripe Identity provides insights into verification checks, analyzing signals like blurriness or authenticity to offer a nuanced view beyond simple pass/fail decisions. These insights assist in manual reviews and customer support by evaluating potential risks.
- [Review tools | Stripe Documentation](https://docs.stripe.com/identity/review-tools): Stripe Identity's review tools allow for manual intervention to supplement automated fraud detection. Businesses can perform manual reviews on unusual verifications through list or detailed views, incorporating human expertise to enhance fraud protection.
- [Supported use cases and locations for Stripe Identity | Stripe Documentation](https://docs.stripe.com/identity/use-cases): Eligibility for Stripe Identity depends on business location and use case, with general availability in the US, UK, and Japan, and public beta in several European and other countries. Specific use cases are supported, while reselling verification services is prohibited.
- [Verification checks | Stripe Documentation](https://docs.stripe.com/identity/verification-checks): Stripe Identity supports five types of verification checks: document, selfie, ID number, phone, and address. Each check requires different user information and has a distinct verification flow, allowing for modular integration and expansion.
- [Verification flows | Stripe Documentation](https://docs.stripe.com/identity/verification-flows): Verification flows in Stripe Identity allow for reusable configurations across different integration interfaces, ensuring consistency and managing various verification use cases. Flows can be created, named, and configured in the Dashboard for API, Dashboard, or static link usage.
- [The Verification Sessions API | Stripe Documentation](https://docs.stripe.com/identity/verification-sessions): The Verification Sessions API securely collects information and manages the entire identity verification process, from creation to results. It supports different session types like 'document' and 'id_number', and best practices recommend reusing existing sessions.
- [Verify your users’ identity documents | Stripe Documentation](https://docs.stripe.com/identity/verify-identity-documents): This guide details how to use Stripe Identity to securely collect and verify identity documents via a web modal or mobile SDKs. It covers adding a verification button, displaying a confirmation page, and handling verification results on the client and server sides.
- [Stripe Documentation](https://docs.stripe.com/): The Stripe documentation homepage provides an overview of all Stripe products and services, including Payments, Revenue, Connect, Identity, and more. It offers guides, examples, and quickstarts to help developers integrate Stripe into their applications.
- [Accept international payments from India | Stripe Documentation](https://docs.stripe.com/india-accept-international-payments): Stripe is available by invite only in India, focusing on businesses with international expansion goals. Businesses can accept international payments in over 135 currencies by declaring transactions as exports and localizing the presentment currency. Specific requirements include being a registered Indian business and providing an Importer Exporter Code (IEC) if selling physical goods.
- [India network tokenization | Stripe Documentation](https://docs.stripe.com/india-network-tokenization): The Reserve Bank of India (RBI) mandates card on file (CoF) tokenization for storing India-issued customer cards for future domestic transactions. Businesses must obtain explicit customer consent for tokenization and storage, with Stripe offering a managed consent flow as a default option. This regulation prohibits storing customer card information directly, making network and issuer tokenization the required method forward.
- [India recurring payments | Stripe Documentation](https://docs.stripe.com/india-recurring-payments): India's Reserve Bank of India (RBI) has introduced new security measures for recurring payments on India-issued cards, including e-mandate registration with additional factor authentication (AFA) and pre-debit notifications. Recurring transactions over 15,000 INR require AFA each time, and cardholders must be alerted 24 hours before charges with an opt-out option. This impacts both India-based and international Stripe users with customers using Indian cards for off-session payments or subscriptions.
- [Enable agents to accept payments based on usage | Stripe Documentation](https://docs.stripe.com/agents/quickstart): This page provides a quickstart guide for enabling agents to accept payments based on usage. It covers essential tools and features for building agentic AI SaaS billing workflows, including API versions, SDKs, testing, and utilizing Stripe's AI solutions and agent toolkit.
- [Build a pre-built subscription page with Stripe Checkout | Stripe Documentation](https://docs.stripe.com/billing/quickstart): This page offers a quickstart for building a pre-built subscription page using Stripe Checkout. It details how to manage subscriptions, set billing cycles, trial periods, and enable billing modes, alongside configuring collection methods and handling taxes for subscriptions.
- [Card Element quickstart | Stripe Documentation](https://docs.stripe.com/payments/card-element): This page is a quickstart guide for integrating the Card Element, a pre-built UI component for securely collecting card details on your website.
- [Build a Stripe-hosted checkout page | Stripe Documentation](https://docs.stripe.com/checkout/quickstart): This page provides a quickstart guide for building a Stripe-hosted checkout page. It covers customizing the look and feel, collecting additional information, managing the product catalog, and setting up future payments.
- [Accept carbon removal payments | Stripe Documentation](https://docs.stripe.com/climate/orders/quickstart): This page offers a quickstart guide for accepting carbon removal payments through Stripe Climate. It outlines how to manage commitments, orders, and webhooks for carbon removal transactions.
- [Build a Connect integration | Stripe Documentation](https://docs.stripe.com/connect/onboarding/quickstart): This quickstart guide focuses on building a Stripe Connect integration for SaaS platforms and marketplaces. It covers the fundamentals of Connect, onboarding accounts, managing connected accounts, and processing payments.
- [Integrate with Connect embedded components | Stripe Documentation](https://docs.stripe.com/connect/connect-embedded-components/quickstart): This quickstart guide details how to integrate with Stripe Connect embedded components. It explains how to customize these components for a seamless user experience within your platform, covering account onboarding and dashboard configurations.
- [Set up a Connect SaaS platform integration | Stripe Documentation](https://docs.stripe.com/connect/saas/quickstart): This quickstart guide focuses on setting up a Stripe Connect SaaS platform integration. It covers essential tasks for building a platform that onboards and manages connected accounts, processes payments, and handles platform administration.
- [Build a checkout page with the Checkout Sessions API | Stripe Documentation](https://docs.stripe.com/payments/quickstart-checkout-sessions): This quickstart guide explains how to build a checkout page using the Checkout Sessions API. It covers customizing the look and feel, managing payment methods, collecting additional information, and setting up subscriptions.
- [Embed a checkout page in your site | Stripe Documentation](https://docs.stripe.com/checkout/embedded/quickstart): This quickstart guide details how to embed a Stripe checkout page directly into your website. It covers customizing the payment form, collecting additional customer information, and managing product catalogs for a seamless checkout experience.
- [Embedded Components onramp quickstart | Stripe Documentation](https://docs.stripe.com/crypto/onramp/embedded-components-quickstart): This quickstart guide focuses on integrating embedded components for a fiat-to-crypto onramp. It provides instructions for implementing a seamless way for users to purchase cryptocurrency.
- [Create and send an invoice | Stripe Documentation](https://docs.stripe.com/invoicing/integration/quickstart): This API quickstart guide details how to create and send invoices using Stripe. It covers the invoicing lifecycle, previewing and editing invoices, sending customer emails, and managing invoice payments and credit notes.
- [Set up and manage real-time authorizations | Stripe Documentation](https://docs.stripe.com/issuing/controls/real-time-authorizations/quickstart): This quickstart guide explains how to set up and manage real-time authorizations for Stripe Issuing. It covers spending controls, advanced fraud tools, and integrating Issuing with Connect for card management.
- [Fiat-to-crypto onramp | Stripe Documentation](https://docs.stripe.com/crypto/onramp/embedded-quickstart): This quickstart guide focuses on building an embedded fiat-to-crypto onramp experience. It provides the necessary steps to integrate a seamless way for users to purchase cryptocurrency directly within your application.
- [Build an advanced integration | Stripe Documentation](https://docs.stripe.com/payments/quickstart): This quickstart guide covers building an advanced integration for accepting payments, focusing on custom integrations with Stripe Elements. It details designing advanced integrations, managing payment methods, and handling subscriptions and taxes.
- [Build an advanced integration | Stripe Documentation](https://docs.stripe.com/payments/quickstart?platform=ios): This quickstart guide focuses on building an advanced integration for iOS applications. It covers designing custom integrations, managing payment methods, and handling subscriptions and taxes within the iOS environment.
- [Build an advanced integration | Stripe Documentation](https://docs.stripe.com/payments/quickstart?platform=android): This quickstart guide focuses on building an advanced integration for Android applications. It covers designing custom integrations, managing payment methods, and handling subscriptions and taxes within the Android environment.
- [Accept in-person payments | Stripe Documentation](https://docs.stripe.com/terminal/quickstart): This page provides a quickstart guide for accepting in-person payments using Stripe Terminal. It covers setting up your integration, selecting a reader, and handling payment collection during checkout.
- [Set up and deploy a webhook | Stripe Documentation](https://docs.stripe.com/webhooks/quickstart): This page explains how to set up and deploy a webhook with Stripe. It covers handling payment events, managing webhook versions, and resolving common issues like signature verification errors.
- [Automatic charging | Stripe Documentation](https://docs.stripe.com/invoicing/automatic-charging): This page details how Stripe can automatically charge a customer's stored payment method when an invoice is created. It explains how to add payment methods and the implications for customer notifications.
- [Automatic collection | Stripe Documentation](https://docs.stripe.com/invoicing/automatic-collection): This page describes Stripe's automatic collection features for invoices, focusing on revenue recovery. It highlights 'Smart Retries,' which uses AI to optimize payment retries for failed attempts.
- [Automatic reconciliation | Stripe Documentation](https://docs.stripe.com/invoicing/automatic-reconciliation): This page explains automatic reconciliation for credit transfer payment methods, which is now deprecated. It details how Stripe auto-generates virtual bank account numbers for customers to facilitate payment and reconciliation.
- [Customer credit balance | Stripe Documentation](https://docs.stripe.com/invoicing/customer/balance): This page covers customer credit balances in Stripe Invoicing, which represent adjustments applied to future invoices. It explains how to issue credit or debit adjustments and how these sum up to a customer's balance.
- [Customer tax IDs | Stripe Documentation](https://docs.stripe.com/invoicing/customer/tax-ids): This page explains how to store, validate, and display customer tax ID numbers within Stripe Invoicing. It lists supported tax ID types by country and their impact on tax calculations.
- [Customers | Stripe Documentation](https://docs.stripe.com/invoicing/customer): This page guides users on managing customers within Stripe Invoicing. It explains how to create and update customer profiles to generate more accurate invoices and enable features like Smart Retries.
- [Products and prices | Stripe Documentation](https://docs.stripe.com/invoicing/products-prices): This page details how to manage products and prices using Stripe's Invoicing API. Products define what you sell, and prices specify the cost and frequency, serving as core entities for subscriptions and invoices.
- [Issue credit notes | Stripe Documentation](https://docs.stripe.com/invoicing/dashboard/credit-notes): This page explains how to issue credit notes using the Stripe Dashboard to adjust or refund finalized invoices. Credit notes decrease the amount owed on an invoice without voiding the original document.
- [Customize invoices | Stripe Documentation](https://docs.stripe.com/invoicing/customize): This page outlines how to customize invoices in Stripe, covering content and branding options. Customization can be done via the API, invoice editor, subscription editor, templates, or account settings.
- [Hosted Invoice Page | Stripe Documentation](https://docs.stripe.com/invoicing/hosted-invoice-page): This page describes the Hosted Invoice Page, a secure URL provided by Stripe for customers to view and pay invoices. It allows customers to download invoice PDFs and receipts, with URLs expiring after a set period.
- [Use the Dashboard | Stripe Documentation](https://docs.stripe.com/invoicing/dashboard): This page explains how to use the Stripe Dashboard to create, send, and modify invoices. It details the process of creating an invoice, selecting or adding customers, and adding line items.
- [Manage invoices | Stripe Documentation](https://docs.stripe.com/invoicing/dashboard/manage-invoices): This page guides users on managing invoices within the Stripe Dashboard. It explains how to track invoice statuses, filter and export invoices, and understand the different badges displayed for invoice states.
- [Scheduled payments | Stripe Documentation](https://docs.stripe.com/invoicing/hosted-invoice-page/scheduled-payments): This page explains how customers can schedule payments for future dates through the Hosted Invoice Page in the US. This feature allows customers to set payment dates and update payment methods on scheduled invoices.
- [Send customer emails | Stripe Documentation](https://docs.stripe.com/invoicing/send-email): This page details how to configure and send various invoicing emails to customers through Stripe. These include notifications for failed payments, receipts, expiring cards, and subscription updates.
- [Automated collections for invoices | Stripe Documentation](https://docs.stripe.com/invoicing/automated-collections): This page provides an overview of Stripe's automated collections for invoices, covering reconciliation, revenue recovery, and automatic charging. It groups features like automatic reconciliation, automatic collection (Smart Retries, email reminders), and automatic charging.
- [Automatic invoice advancement | Stripe Documentation](https://docs.stripe.com/invoicing/integration/automatic-advancement-collection): This page explains automatic invoice advancement in Stripe, which helps manage invoice state transitions and payment collection. It covers how to enable this feature via the API or Dashboard for overdue or failed payments.
- [Manage bulk invoice line items | Stripe Documentation](https://docs.stripe.com/invoicing/bulk-update-line-item): This page describes how to manage multiple invoice line items in bulk using the Stripe Invoices API. It details how to add, update, and remove line items on an invoice, particularly for draft invoices.
- [Create an invoice with Connect | Stripe Documentation](https://docs.stripe.com/invoicing/connect): This page explains how to create invoices for connected accounts using Stripe Connect. It covers both direct charges and destination charges, including the option to take application fees during the process.
- [Group invoice line items | Stripe Documentation](https://docs.stripe.com/invoicing/group-line-items): Stripe allows you to group invoice line items to improve customer clarity by categorizing them under different headings. This feature, configured using Common Expression Language (CEL) within Invoice Templates, helps in simplifying complex invoices by allowing you to display group subtotals instead of individual line items.
- [Invoice rendering templates | Stripe Documentation](https://docs.stripe.com/invoicing/invoice-rendering-template): Invoice rendering templates enable personalization of invoice appearance for specific customer groups by allowing you to store and reuse common values for invoice fields. These templates, created in the Dashboard, can customize footer text, memo notes, and line item grouping rules, offering flexibility in invoice presentation.
- [Integrate with the Invoicing API | Stripe Documentation](https://docs.stripe.com/invoicing/integration): Integrate with the Stripe Invoicing API to automate invoice creation and management, offering a programmatic alternative to the Dashboard. The API allows for the creation of products and prices, which define the cost, currency, and billing interval for charges.
- [Generate credit notes programmatically | Stripe Documentation](https://docs.stripe.com/invoicing/integration/programmatic-credit-notes): Programmatically generate credit notes using the Invoicing API to adjust or refund finalized invoices. Credit notes can discount line item amounts, quantities, or apply a custom discount to the total invoice, providing flexibility in financial adjustments.
- [Schedule invoice finalization to send or charge an invoice in the future | Stripe Documentation](https://docs.stripe.com/invoicing/scheduled-finalization): Schedule invoice finalization to automatically send or charge invoices on a future date, up to five years in advance. This feature requires automatic invoice advancement to be enabled and allows for flexible payment scheduling for both one-off and subscription invoices.
- [Invoice summary items | Stripe Documentation](https://docs.stripe.com/invoicing/line-item-grouping): Invoice summary items are an underlying API feature that enables the grouping and summarization of invoice line items. You can create summary items to act as group headers, and optionally hide individual line items to display only the group subtotal.
- [Test Stripe Invoicing | Stripe Documentation](https://docs.stripe.com/invoicing/integration/testing): Test your Stripe Invoicing integration using common scenarios and tools like the Stripe CLI. You can simulate webhook notifications, test events with fake or real data, and trigger payment failures to ensure your integration functions correctly before going live.
- [Status transitions and finalization | Stripe Documentation](https://docs.stripe.com/invoicing/integration/workflow-transitions): Understand invoice status transitions and finalization workflows to manage the lifecycle of your invoices. Invoices move through statuses like draft, open, paid, and void, with specific API endpoints and webhooks associated with each transition.
- [Edit invoices | Stripe Documentation](https://docs.stripe.com/invoicing/invoice-edits): Edit finalized invoices in open or uncollectible status to revise descriptions, customer details, line items, or apply discounts and taxes. However, invoices in void or paid status cannot be revised, and international compliance may require voiding and issuing a credit note instead.
- [Accept partial payments for invoices | Stripe Documentation](https://docs.stripe.com/invoicing/partial-payments): Accept partial payments on invoices to accommodate larger amounts by allowing multiple, smaller payments. Both the Dashboard and API support capturing partial payments, with specific considerations for subscription invoices based on their collection method.
- [Create invoice payment plans | Stripe Documentation](https://docs.stripe.com/invoicing/payment-plans): Create invoice payment plans to break down an invoice's total amount into multiple payments with different due dates, enhancing billing flexibility. This feature, currently in private preview, allows for deposits and staggered balance payments, with reminders for upcoming due dates.
- [Multi-currency customers | Stripe Documentation](https://docs.stripe.com/invoicing/multi-currency-customers): Bill customers in multiple currencies by changing their default billable currency using the Invoicing API. This feature allows for different currencies per customer and subscription, and also supports creating credit notes and inspecting customer credit balances across currencies.
- [Best practices for setting up invoices in Australia | Stripe Documentation](https://docs.stripe.com/invoicing/australia-invoicing): Follow best practices for setting up invoices in Australia to ensure compliance, especially when issuing tax invoices. Key fields like the invoice title, business details, ABN, date, description, and GST amount must be accurately populated according to Australian requirements.
- [Best practices for global invoices | Stripe Documentation](https://docs.stripe.com/invoicing/global-invoices): Adhere to best practices for global invoicing, particularly for Business-to-Business (B2B) sales, as invoice compliance varies by country. Stripe provides guidance for specific regions including Australia, the European Union, France, Germany, and Japan.
- [Invoicing | Stripe Documentation](https://docs.stripe.com/invoicing): Stripe Invoicing allows you to create and manage invoices for one-time payments, offering both no-code solutions via the Dashboard and automated options through the Invoicing API. Features include customization, automated collection, and multi-currency support.
- [No-code Invoicing guide | Stripe Documentation](https://docs.stripe.com/invoicing/no-code-guide): Get started with Stripe Invoicing without writing code by using the Dashboard to manage invoices, issue credit notes, and customize your business branding. You can automatically charge customer payment methods or email invoices with payment links.
- [How invoicing works | Stripe Documentation](https://docs.stripe.com/invoicing/overview): Invoices provide an itemized list of goods and services, enabling payment collection or automatic charging of saved customer methods. Invoices move through a lifecycle from draft to open status upon finalization, with subscriptions automatically generating invoices per billing cycle.
- [Invoicing and ACH Direct Debit | Stripe Documentation](https://docs.stripe.com/invoicing/ach-direct-debit): Configure, create, and process invoices using ACH Direct Debit for US customers with US bank accounts. This payment method is often preferred for larger invoice totals to reduce costs compared to card payments.
- [Bank transfer | Stripe Documentation](https://docs.stripe.com/invoicing/bank-transfer): Offer bank transfer payment options on your invoices, such as ACH in the US or Bacs in the UK, without exposing your bank details. Stripe generates unique virtual bank account numbers for reconciliation and supports automatic reconciliation of received transfers.
- [Payment methods | Stripe Documentation](https://docs.stripe.com/invoicing/payment-methods): Stripe Invoicing supports various payment methods, including ACH Direct Debit, Affirm, and Afterpay/Clearpay, with currency and regional limitations. Customers can pay using enabled methods in their Invoice template, though certain restrictions might prevent automatic selection.
- [Preview an invoice | Stripe Documentation](https://docs.stripe.com/invoicing/preview): Stripe Invoicing allows you to create a preview of an invoice for customers before it's finalized. This feature helps calculate total amounts, retrieve line items, and apply taxes or discounts without creating a formal invoice.
- [Account tax IDs | Stripe Documentation](https://docs.stripe.com/invoicing/taxes/account-tax-ids): Stripe Invoicing enables you to store and display up to 25 tax IDs on invoice and credit note PDFs. You can set default tax IDs to appear on all documents or specify them for individual invoices, but they cannot be changed after an invoice is finalized.
- [Taxes | Stripe Documentation](https://docs.stripe.com/invoicing/taxes): Stripe Tax automatically calculates sales tax, VAT, and GST for invoices based on your tax settings, the customer's location, and product tax codes. The tax rate applied is the published rate at the time of invoice finalization, and customer location data is crucial for accurate calculation.
- [Use tax amounts from unsupported systems with Stripe Billing | Stripe Documentation](https://docs.stripe.com/invoicing/taxes/manual-tax-amounts): When using an external tax system not supported by Stripe, you can manually set tax amounts on invoices using the `tax_amounts` parameter. This involves creating an invoice and then adding invoice items with the specified tax amounts.
- [Tax rates and IDs | Stripe Documentation](https://docs.stripe.com/invoicing/taxes/tax-rates): You can assign tax rates to draft invoices in Stripe, either to individual line items or as a default for the entire invoice. While assigning to individual items is recommended for flexibility, default rates can simplify tax calculation for simpler needs.
- [Cardholder authentication using 3D Secure | Stripe Documentation](https://docs.stripe.com/issuing/3d-secure): 3D Secure is an additional authentication layer for online card-not-present transactions that helps reduce fraud. It requires multi-factor authentication, often via a one-time passcode sent through SMS or email, to verify the cardholder's identity during checkout.
- [Add funds to your card program | Stripe Documentation](https://docs.stripe.com/issuing/adding-funds-to-your-card-program): To enable spending with Stripe Issuing cards, you must fund an Issuing balance using options like pull-funded top-ups, push-funded top-ups, Stripe balance transfers, or Connect balance transfers. The default funding method is an external bank account.
- [Choose which type of card to issue | Stripe Documentation](https://docs.stripe.com/issuing/choose-cards): Stripe Issuing offers the choice between virtual cards, which contain only digital transaction information, and physical cards that are shipped to cardholders. Both types can be issued simultaneously, and the choice depends on the specific use case and business needs.
- [How Credit Consumer Issuing works | Stripe Documentation](https://docs.stripe.com/issuing/consumer-issuing/how-it-works): Credit Consumer Issuing, currently in private preview in the US, allows you to create, launch, and manage a credit program for consumers using Stripe's APIs and a bank partner. It includes features like BIN sponsorship, credit ledger management, and dispute handling.
- [Credit Consumer Issuing | Stripe Documentation](https://docs.stripe.com/issuing/consumer-issuing): Stripe's Credit Consumer Issuing, available in private preview in the US, provides the components to build and operate a bank-sponsored credit program. This includes onboarding consumer accounts, issuing credit cards, managing the credit program, and customizing rewards.
- [Customize your card program | Stripe Documentation](https://docs.stripe.com/issuing/customize-your-program): Stripe Issuing allows extensive customization of your card program, managed through the Dashboard's Issuing settings. This includes configuring Bank Identification Numbers (BINs) and account ranges, which are essential for identifying card networks and issuing banks.
- [Use digital wallets with Issuing | Stripe Documentation](https://docs.stripe.com/issuing/cards/digital-wallets): Stripe Issuing enables cards to be added to digital wallets like Apple Pay and Google Pay through manual or push provisioning. When a card is added, a tokenized representation is created, and network tokens are managed separately from the physical or virtual card.
- [Integrate processor-only Issuing | Stripe Documentation](https://docs.stripe.com/issuing/processor-only-integration-guide): The processor-only Issuing model requires Know Your Customer (KYC) on cardholders, with each end customer represented by a Cardholder object. You must create a Cardholder object and then issue a card to that specific cardholder, passing the cardholder's ID in the API call.
- [Processor-only Issuing | Stripe Documentation](https://docs.stripe.com/issuing/processor-only-issuing): In the processor-only Issuing model, Stripe acts as the Issuer Processor, integrating with card networks, manufacturers, and BIN sponsors on your behalf. Setting up an authorization endpoint and integrating with Transaction APIs are key steps for managing the program and daily settlements.
- [Manage fraud with Stripe Issuing controls and tools | Stripe Documentation](https://docs.stripe.com/issuing/manage-fraud): Stripe Issuing provides tools and controls to manage and prevent transaction fraud, which is an inherent risk in payment facilitation. Understanding fraud types, liability, and utilizing Stripe's resources are crucial for businesses to mitigate these risks effectively.
- [Physical cards address validation | Stripe Documentation](https://docs.stripe.com/issuing/cards/physical/address-validation): Accurate and validated shipping addresses are essential for the successful delivery of physical Stripe Issuing cards. The Cards API includes address normalization and validation against a third-party database to correct issues and minimize delivery failures and returns.
- [Artwork templates | Stripe Documentation](https://docs.stripe.com/issuing/cards/artwork-templates): Stripe provides design templates in Adobe Illustrator for creating custom physical cards, carriers, and envelopes. Best practices include adhering to specific card and artwork sizes, maintaining safe zones for logos and text, and ensuring minimum line thickness for print quality.
- [Customize card bundle | Stripe Documentation](https://docs.stripe.com/issuing/cards/physical/card-bundle-selections): When designing physical cards, Stripe offers standard options for card bodies and core colors, along with innovative materials like LED-powered or wooden cards. You can select from these options or arrange sessions to explore more unique physical card market products.
- [Choose your physical bundle | Stripe Documentation](https://docs.stripe.com/issuing/cards/choose-bundle): Stripe helps set up physical card bundles, including the card, carrier, and envelope, with standard and custom options available. Standard bundles allow customization of your logo and carrier text, while custom options offer unique materials and features.
- [Create a design | Stripe Documentation](https://docs.stripe.com/issuing/cards/physical/create-design): You can create and name your card design in the Issuing Dashboard or via the API before issuing cards. The standard option allows selecting a black or white card, uploading a logo in a specific format, and setting up basic design elements.
- [Create physical cards | Stripe Documentation](https://docs.stripe.com/issuing/cards/physical/issue-cards): You can issue standard and custom physical cards to cardholders through the Stripe Dashboard or the Create a card endpoint. If a custom design is approved, the card is sent for fulfillment; otherwise, it's fulfilled after design approval.
- [Order a custom bundle | Stripe Documentation](https://docs.stripe.com/issuing/cards/physical/order-custom-bundle): Ordering a custom card bundle involves a process that can take 12-14 weeks, requiring input forms and design templates provided by Stripe. Stripe offers support through email and live sessions to guide you through each phase of the customization process.
- [Physical cards | Stripe Documentation](https://docs.stripe.com/issuing/cards/physical): Stripe offers options for issuing physical cards, ranging from standard cards with basic branding for quick deployment to fully custom designs. They partner with global card printers to produce cards, allowing for either rapid market entry or a high degree of customization.
- [Ship cards | Stripe Documentation](https://docs.stripe.com/issuing/cards/physical/ship-cards): Stripe provides two options for shipping physical cards: individual shipping, where each card is mailed to the cardholder, and bulk shipping, where multiple cards are batched into a single box. Various shipping services are available with different costs, speeds, and tracking capabilities.
- [PIN management | Stripe Documentation](https://docs.stripe.com/issuing/cards/pin-management): Cardholders can manage their PINs for physical and virtual cards using the Stripe API and Elements. PINs are randomly set at creation, and replacement cards do not inherit the old PIN; a default PIN of 0000 is used in testing environments.
- [Program management | Stripe Documentation](https://docs.stripe.com/issuing/program-management): Stripe offers two program management models for issuing: Stripe program management, which leverages Stripe's existing infrastructure and partnerships, and processor-only, where you manage all regulatory and operational aspects. The choice depends on your business needs for control and complexity.
- [Replacement cards | Stripe Documentation](https://docs.stripe.com/issuing/cards/replacements): You can replace physical cards that are expired, damaged, lost, or stolen, with slightly different processes for each scenario. Replacements for expired or damaged cards may result in a new card number, security code, and expiry date, while lost or stolen cards always receive entirely new details.
- [Virtual cards with Issuing | Stripe Documentation](https://docs.stripe.com/issuing/cards/virtual): Virtual cards can be created and their details displayed through the Stripe Dashboard, API, or Issuing Elements, ensuring PCI-DSS compliance. Issuing Elements is recommended for displaying card details without sensitive information passing through your servers.
- [Create virtual cards | Stripe Documentation](https://docs.stripe.com/issuing/cards/virtual/issue-cards): Virtual cards can be issued to cardholders via the Dashboard or the Create a card endpoint and are immediately available for use. Creating a cardholder requires specific information, including billing address and contact details, which are essential for features like digital wallets.
- [Issuing merchant categories | Stripe Documentation](https://docs.stripe.com/issuing/categories): Businesses are categorized using Merchant Category Codes (MCC), which are available as `merchant_data.category` on Authorization objects. These categories can be used to create spending controls to restrict card usage with specific business types.
- [Cardholder controls | Stripe Documentation](https://docs.stripe.com/issuing/connect/cardholders-controls): Stripe requires cardholder information screening to comply with legal and regulatory guidelines, impacting your Issuing and Connect integration. Updated validation requirements for cardholder names and street addresses apply to new and existing cardholders after October 31, 2024.
- [Embed Issuing card management into your website | Stripe Documentation](https://docs.stripe.com/issuing/connect/embedded-components): Connect embedded components allow you to integrate Issuing card management functionality directly into your website for connected accounts. These pre-built UI components, such as the Issuing Card and Issuing Cards List components, require minimal coding and configuration.
- [Inactive connected accounts offboarding | Stripe Documentation](https://docs.stripe.com/issuing/connect/inactive-accounts-management): Stripe disables issuing capabilities on inactive connected accounts to mitigate risks associated with lost or compromised cards. Issuing is disabled for accounts that haven't authorized any card transactions in the past 13 months, and notices are sent to affected accounts.
- [Connected accounts, cardholders, and cards | Stripe Documentation](https://docs.stripe.com/issuing/connect/cardholders-and-cards): In Stripe Connect, connected accounts represent business entities, and cardholders are individuals associated with them, with one account potentially having multiple cardholders. After creating a cardholder, you can issue them a virtual or physical card, with certain details being optional for physical cards.
- [Fund Issuing balances with Connect | Stripe Documentation](https://docs.stripe.com/issuing/connect/funding): Before issued cards can be used, funds must be allocated to the connected account's Issuing balance, which is separate from other Stripe funds. Funding options include pull funding (default in the US, with verification delays) and push funding.
- [Set up an Issuing and Connect integration | Stripe Documentation](https://docs.stripe.com/issuing/connect): Stripe Connect provides the infrastructure for Issuing platforms to manage fund flows and compliance when issuing cards for external users. The platform account makes API calls on behalf of connected accounts, enabling integrations like expense management products for small businesses.
- [Advanced fraud tools | Stripe Documentation](https://docs.stripe.com/issuing/controls/advanced-fraud-tools): Stripe Issuing's advanced fraud tools help identify and prevent transaction fraud using API signals and tooling. These tools provide authorization signals, notify you of compromised cards, and can trigger SMS-based fraud challenges to minimize fraud impact.
- [Migrate to direct webhook response | Stripe Documentation](https://docs.stripe.com/issuing/controls/real-time-authorizations/direct-webhook-migration): You can now respond directly to `issuing_authorization.request` webhooks with authorization decisions, simplifying real-time authorizations and reducing API calls. This direct webhook response method is recommended for new integrations and will eventually replace the approve and decline API endpoints.
- [Fraud challenges | Stripe Documentation](https://docs.stripe.com/issuing/controls/fraud-challenges): Fraud challenges add a layer of verification for authorizations, minimizing accidental blocks on legitimate transactions and conducting additional verification on high-risk authorizations. When enabled, Stripe sends an SMS to cardholders to verify suspicious transactions.
- [Using Issuing Elements | Stripe Documentation](https://docs.stripe.com/issuing/elements): Issuing Elements, part of Stripe.js, allows you to display sensitive Issuing card data on your web application in a PCI-compliant manner. This data is rendered within Stripe-hosted iframes, ensuring it never touches your servers.
- [Issuing real-time authorizations | Stripe Documentation](https://docs.stripe.com/issuing/controls/real-time-authorizations): Stripe Issuing allows real-time authorization of card transactions. You can approve or decline requests by configuring a webhook endpoint that receives issuing_authorization.request events and responds directly.
- [Issuing spending controls | Stripe Documentation](https://docs.stripe.com/issuing/controls/spending-controls): Stripe Issuing enables spending controls to manage card and cardholder behavior. You can block specific merchant categories, countries, or merchant IDs, and set spending limits per authorization or per month.
- [Stripe's risk score | Stripe Documentation](https://docs.stripe.com/issuing/controls/advanced-fraud-tools/stripes-risk-score): Stripe's risk score helps assess the fraud risk associated with an authorization on a scale of 0-99. It provides a composite score and a 'normal' or 'high' risk level to guide decisions on approving or rejecting transactions.
- [Token management | Stripe Documentation](https://docs.stripe.com/issuing/controls/token-management): Token management in Stripe Issuing creates virtual representations of cards for digital wallets and online payment methods. These tokens replace sensitive card details, reducing the risk of data exposure and enhancing payment security.
- [Available credit and flow of funds | Stripe Documentation](https://docs.stripe.com/issuing/credit/manage-account-obligations/available-credit): Available credit for connected accounts changes with each card transaction or adjustment. You can monitor and manage this by retrieving the account's credit ledger, which shows the credit limit, pending amounts, and obligations.
- [Set up credit for connected accounts | Stripe Documentation](https://docs.stripe.com/issuing/credit/connect-credit-setup): Setting up credit for connected accounts involves configuring credit terms and allowing them to spend funds from your platform. Connected accounts function as sub-accounts managed through your main Stripe account, enabling credit extension for their use.
- [Issuing Credit | Stripe Documentation](https://docs.stripe.com/issuing/credit): Stripe Issuing Credit allows platforms to use their Issuing balance or exposure limit for cards issued to connected accounts. This feature enables funding for connected accounts when their own balance is insufficient, utilizing Credit APIs for lines of credit.
- [Manage account obligations | Stripe Documentation](https://docs.stripe.com/issuing/credit/manage-account-obligations): Managing account obligations involves tracking the credit spend, lifecycle, and balances for connected accounts. After activating a CreditPolicy, Stripe creates a FundingObligation to monitor debt, which only includes cleared transactions, not pending authorizations.
- [Manage credit terms | Stripe Documentation](https://docs.stripe.com/issuing/credit/manage-credit-terms): You can manage credit terms for connected accounts by updating their credit limit amount and credit period interval. It's also possible to deactivate a connected account's ability to spend funds supported by your platform's Issuing account.
- [Obligation payments | Stripe Documentation](https://docs.stripe.com/issuing/credit/manage-account-obligations/obligation-payments): Obligation payments allow you to collect repayment from connected accounts for their credit spend. You can use Stripe's Payment Intents API or other methods to debit their bank accounts or accept card payments, and record these payments to reflect their available credit.
- [Obligation amounts, transactions, and adjustments | Stripe Documentation](https://docs.stripe.com/issuing/credit/manage-account-obligations/obligations-transactions-adjustments): View details of a Funding Obligation and make adjustments to track a connected account's credit spend. You can fetch current and past Funding Obligations, which detail amounts owed, outstanding, paid, and their status within a credit period.
- [Report other credit decisions and manage adverse action notices | Stripe Documentation](https://docs.stripe.com/issuing/credit/report-credit-decisions-and-manage-aans): Report credit decisions and manage adverse action notices (AANs) using the CreditUnderwritingRecord API. This allows you to record application and decision details for various credit underwriting scenarios, including those requiring AANs.
- [Report required regulatory data for credit decisions | Stripe Documentation](https://docs.stripe.com/issuing/credit/report-required-regulatory-data-for-credit-decisions): Platforms subject to regulatory reporting must use the CreditUnderwritingRecord API and upload required data to Stripe's Files API. The uploaded file's ID is then included in requests to report credit decisions, ensuring compliance with mandated reporting.
- [Test your integration | Stripe Documentation](https://docs.stripe.com/issuing/credit/test-credit): You can test your credit integration in a sandbox environment using the Credit API. This involves creating a connected account, requesting the funding_credit capability, updating and activating its CreditPolicy, and paying off its FundingObligation.
- [Issuing balance | Stripe Documentation](https://docs.stripe.com/issuing/funding/balance): Fund your Issuing balance to make money available for card spending. This balance is separate from other Stripe funds and can be topped up via push funding from an external bank account or pull funding (US-only) using the Stripe Dashboard or API.
- [Update the Issuing terms of service acceptance | Stripe Documentation](https://docs.stripe.com/issuing/connect/tos_acceptance): Platforms must present accurate business information and obtain confirmation from account representatives before submitting to Stripe Issuing. This includes details like Tax Identification Number, name, date of birth, address, and SSN, along with accepting relevant terms and disclosures.
- [Post-fund your integration with Dynamic Reserves | Stripe Documentation](https://docs.stripe.com/issuing/funding/post-fund-with-dynamic-reserves): Dynamic reserves allow platforms to adjust credit limits in real-time to manage capital between Stripe and authorization funds. This feature helps control capital usage, minimize funding costs, and manage authorization availability amidst financial volatility.
- [Postfund your integration with Stripe | Stripe Documentation](https://docs.stripe.com/issuing/funding/post-fund): Postfunding your Stripe integration allows you to accrue a negative Issuing balance on card spend and fund Stripe later. This means you fund your Issuing balance after authorizations are captured, rather than prefunding, with daily notifications of amounts owed.
- [Use Stripe Issuing in different countries | Stripe Documentation](https://docs.stripe.com/issuing/global): Stripe Issuing offers global availability with different integration options varying by country. You can use local issuing in 22 countries or explore early access for cross-border issuing to serve multinational companies and stablecoin-backed cards.
- [Issuing | Stripe Documentation](https://docs.stripe.com/issuing): The Stripe Issuing API enables the creation, management, and distribution of payment cards for businesses. It allows for custom card designs, real-time transaction approval, and integration with Financial Accounts for platforms to offer enhanced money movement options.
- [How Issuing works | Stripe Documentation](https://docs.stripe.com/issuing/how-issuing-works): Stripe Issuing allows businesses to programmatically create and manage payment card programs, offering virtual or physical cards with customizable spending controls. It partners with banks and card networks like Mastercard and Visa to provide embedded finance infrastructure.
- [Issuing beta migration guide | Stripe Documentation](https://docs.stripe.com/issuing/migration-from-beta): This guide details the necessary API changes and considerations for migrating from the Stripe Issuing beta to the generally available version. It highlights breaking changes, renamed attributes and parameters, and advises on supporting both old and new APIs during the transition before the beta API is discontinued.
- [Issuing for agents | Stripe Documentation](https://docs.stripe.com/issuing/agents): Stripe Issuing for agents enables the creation of programmable cards with built-in controls for agents to make purchases on your behalf. These cards support agentic commerce workflows by providing scoped, controlled, and real-time monitored payment credentials for online transactions.
- [Choose a cardholder type | Stripe Documentation](https://docs.stripe.com/issuing/other/choose-cardholder): When creating a Cardholder object in Stripe Issuing, you can specify the type as 'individual' or 'company', though this cannot be changed after creation. The choice of cardholder type may require collecting different information, such as names and terms acceptance for individuals.
- [Issuing and Financial Accounts product marketing, design, and compliance guidelines | Stripe Documentation](https://docs.stripe.com/issuing/compliance-us): This document provides product marketing, design, and compliance guidelines for launching and maintaining Stripe Issuing and Financial Accounts programs in the US. It outlines essential requirements for user interfaces and marketing materials to navigate financial regulations.
- [Issuing regulated customer notices | Stripe Documentation](https://docs.stripe.com/issuing/compliance-us/issuing-regulated-customer-notices): Issuing platforms must send regulated customer notices upon specific trigger events to comply with applicable laws. Stripe offers a no-code solution to automatically send these required emails on your behalf, ensuring compliance.
- [Issuing watchlist | Stripe Documentation](https://docs.stripe.com/issuing/issuing-watchlist): Stripe Issuing automatically screens users against international sanctions lists during onboarding and updates. If a user is flagged, a manual review is initiated, during which card authorizations may be declined with a specific reason until the review is complete.
- [Stripe Issuing marketing guidelines | Stripe Documentation](https://docs.stripe.com/issuing/marketing-guidance-europe-uk): This document outlines marketing guidelines for promoting Stripe Issuing products and services in the United Kingdom and Europe. It details requirements for user interfaces and advertising to ensure compliance with financial regulations governing product messaging.
- [Use cards at automated teller machines (ATMs) | Stripe Documentation](https://docs.stripe.com/issuing/purchases/atm-usage): US-issued Stripe Issuing cards can be used for ATM cash withdrawals if the feature is enabled and cards have valid PINs. ATM transactions are treated as standard, with specific merchant category codes and the possibility of an ATM fee being present.
- [Issuing authorizations | Stripe Documentation](https://docs.stripe.com/issuing/purchases/authorizations): Stripe Issuing handles authorization requests by checking sufficient funds, card status, and spending controls before potentially sending an issuing_authorization.request event. Developers can set up real-time authorization webhooks to synchronously approve or decline these requests.
- [Issuing disputes | Stripe Documentation](https://docs.stripe.com/issuing/purchases/disputes): Users or cardholders can dispute Issuing transactions through Stripe's Dashboard or API for issues like fraud or processing errors. Disputes are processed according to network rules and typically take 30-90 days for resolution; authorizations cannot be disputed directly.
- [Enriched merchant data | Stripe Documentation](https://docs.stripe.com/issuing/purchases/enriched-merchant-data): Enriched merchant data, available for US-based Stripe Issuing users, provides comprehensive information on card transactions to improve fraud prevention. This data includes unique counterparty IDs and detailed merchant activity, enabling better spending pattern analysis and transaction restrictions.
- [Issuing transactions | Stripe Documentation](https://docs.stripe.com/issuing/purchases/transactions): Once an authorization is approved and captured, it transitions to a 'closed' status, creating a Transaction object. This process deducts the purchase amount from the Issuing balance, and spending controls do not apply to the capture stage.
- [Stablecoin-backed card issuing with Connect | Stripe Documentation](https://docs.stripe.com/issuing/stablecoins-connect): Stripe's stablecoin-backed card issuing with Connect, currently in private preview for US-based platforms, allows for issuing prepaid debit cards backed by stablecoin balances. It also enables creating custodial wallets and direct transfers to external crypto wallets for connected accounts.
- [Test your Issuing integration | Stripe Documentation](https://docs.stripe.com/issuing/testing): You can test your Stripe Issuing integration in a sandbox environment by issuing test cards and simulating purchases with test funds. This allows for validation of your integration before going live, ensuring all components function correctly.
- [Stripe Android SDK | Stripe Documentation](https://docs.stripe.com/sdks/android): The Stripe Android SDK enables the creation of payment experiences within Android applications, offering customizable UI elements and low-level APIs. It supports features like PaymentSheet, Card Element, and Google Pay integration for collecting payment details.
- [Community SDKs | Stripe Documentation](https://docs.stripe.com/sdks/community): This page lists open-source, community-supported libraries for integrating Stripe across various languages and frameworks, including Angular, Flutter, PHP, and Vue. Stripe does not officially support or review these community SDKs for accuracy.
- [Stripe SDKs | Stripe Documentation](https://docs.stripe.com/sdks): Stripe provides official SDKs and libraries for various platforms like server-side applications, web frontends, and mobile apps to facilitate integration with Stripe's APIs. These libraries reduce boilerplate code and ensure secure interaction with Stripe features.
- [Stripe iOS SDK | Stripe Documentation](https://docs.stripe.com/sdks/ios): The Stripe iOS SDK allows developers to integrate payments into iOS applications using Swift or Objective-C. It offers prebuilt UI components like PaymentSheet and customizable elements for building payment forms and collecting customer payment details.
- [Mobile SDK versioning and support policy | Stripe Documentation](https://docs.stripe.com/sdks/mobile-sdk-versioning): This page outlines Stripe's versioning policy for its mobile SDKs (iOS, Android, React Native), detailing compatibility with Stripe API versions and update recommendations. It follows semantic versioning (MAJOR.MINOR.PATCH) for API changes and bug fixes.
- [Stripe React Native SDK | Stripe Documentation](https://docs.stripe.com/sdks/react-native): The Stripe React Native SDK enables developers to integrate payment functionality into native Android and iOS applications using React Native. It offers pre-built UI components like PaymentSheet and the Mobile Payment Element for seamless collection of customer payment details.
- [Introduction to server-side SDKs | Stripe Documentation](https://docs.stripe.com/sdks/server-side): Stripe's server-side SDKs simplify the process of interacting with Stripe's REST APIs. They are available for multiple programming languages including Ruby, PHP, Java, Python, Node.js, Go, and .NET, reducing the amount of code required for common API operations like creating, updating, and retrieving objects.
- [Set a Stripe API version | Stripe Documentation](https://docs.stripe.com/sdks/set-version): This page explains how to set a specific Stripe API version for your integrations, which determines available functionality and response formats. While SDKs often default to the API version current at their release, you can manually set a global or per-request API version, especially when using server-side SDKs like Ruby.
- [ES Module Stripe.js SDK | Stripe Documentation](https://docs.stripe.com/sdks/stripejs-esmodule): The ES Module Stripe.js SDK allows web applications to securely collect customer payment details using Stripe's prebuilt UI components called Elements. It can be installed via a script tag or a package manager and wraps the global Stripe function, making it accessible as an ES module for easier integration.
- [Stripe.js versioning and support policy | Stripe Documentation](https://docs.stripe.com/sdks/stripejs-versioning): Stripe.js uses an evergreen model with continuous updates and biannual major releases (e.g., Acacia) to introduce new features and breaking changes predictably. Non-breaking changes like optimizations and bug fixes are applied automatically to all versions, ensuring ongoing improvements without integration modifications.
- [Stripe versioning and support policy | Stripe Documentation](https://docs.stripe.com/sdks/versioning): Stripe follows a new API release process starting with the 2024-09-30.acacia release, offering monthly API versions without breaking changes and twice-yearly major releases. SDKs are updated monthly with minor versions and with major releases for breaking changes, adhering to semantic versioning principles.
- [Managed Payments changelog | Stripe Documentation](https://docs.stripe.com/payments/managed-payments/changelog): The Managed Payments changelog details recent updates to Stripe's service that allows them to act as the merchant of record. Recent additions include support for more payment methods, subscription schedules, free trials without upfront payment collection, and adaptive pricing for localized currency.
- [How Managed Payments works | Stripe Documentation](https://docs.stripe.com/payments/managed-payments/how-it-works): Managed Payments allows Stripe to act as the merchant of record, handling responsibilities like indirect tax compliance, fraud prevention, and customer support. This feature enables businesses to expand globally by selling digital products without needing to establish local entities, with Stripe managing sales tax, VAT, and GST.
- [Managed Payments | Stripe Documentation](https://docs.stripe.com/payments/managed-payments): Managed Payments enables businesses to sell digital products globally by having Stripe act as the merchant of record, managing global tax compliance, fraud prevention, dispute resolution, and customer support. It is compatible with Stripe Checkout and Link, and transactions are visible in Stripe Reporting.
- [Accept payments for digital products on iOS with Stripe as your merchant of record | Stripe Documentation](https://docs.stripe.com/payments/managed-payments/set-up-mobile): This guide explains how to accept payments for digital products on iOS using Stripe as the merchant of record, primarily by opening Stripe Checkout in a browser. It details how to sell in-app digital products or subscriptions, redirecting customers to a Stripe-hosted payment page, and mentions requirements like accepting the Managed Payments terms of service.
- [Set up Managed Payments | Stripe Documentation](https://docs.stripe.com/payments/managed-payments/set-up): To set up Managed Payments, businesses must accept the terms of service and ensure their products meet eligibility requirements. The process involves activating the feature in the Dashboard, setting up the development environment to use API version 2025-03-31.basil or higher, and creating products and prices for one-time or subscription payments.
- [Update a Stripe Checkout integration to use Managed Payments | Stripe Documentation](https://docs.stripe.com/payments/managed-payments/update-checkout): Updating an existing Stripe Checkout integration to use Managed Payments allows Stripe to handle tax compliance, fraud prevention, and customer support. This process requires creating Checkout Sessions in payment or subscription mode and ensuring that all products being purchased are eligible for Managed Payments.
- [Masterpass guide | Stripe Documentation](https://docs.stripe.com/masterpass): Masterpass is a deprecated service that allowed users to streamline online checkout by using stored payment and shipping information. Stripe no longer supports new Masterpass integrations, and existing users are advised to migrate to Secure Remote Commerce, which offers unified online checkout support for multiple card brands.
- [Model Context Protocol (MCP) | Stripe Documentation](https://docs.stripe.com/mcp): The Model Context Protocol (MCP) server allows AI agents to interact with the Stripe API and search Stripe's knowledge base. It provides tools for actions like retrieving account information, managing customers, creating coupons, and searching documentation, enabling AI-driven automation and integration with Stripe services.
- [Getting started with Sources in the Android SDK | Stripe Documentation](https://docs.stripe.com/mobile/android/sources): This guide explains how to use the Sources API in the Android SDK to create payment sources and process charges, although the Sources API is deprecated. It outlines a multi-step process involving creating a Source object, checking for further customer action, and confirming the source to create a charge on the backend.
- [Charge for shipping | Stripe Documentation](https://docs.stripe.com/payments/mobile/charge-shipping): Stripe Elements does not natively support calculating or defining shipping rates; developers are advised to implement this functionality themselves or use Stripe Checkout. If building it manually, shipping costs should be factored into the total amount presented to the customer before processing the payment.
- [Getting started with Sources in the iOS SDK | Stripe Documentation](https://docs.stripe.com/mobile/ios/sources): This guide details how to use the Sources API in the iOS SDK for creating payment sources and processing charges, noting that the Sources API is deprecated. The process involves creating an STPSource object, determining if further customer action is needed, and then using the source to create a charge on the backend.
- [Network sponsor reporting | Stripe Documentation](https://docs.stripe.com/network-sponsor-reporting): Stripe provides network sponsor reporting through CSV files delivered via SFTP, including Daily Settlement, Clearing Transaction Detail, Dispute Event, Transaction Summary, and Merchant Reports. These reports detail transaction volumes, cleared transactions, dispute events, and merchant metadata, with amounts provided in the smallest currency unit.
- [Stripe Dashboard assistant | Stripe Documentation](https://docs.stripe.com/assistant): The Stripe Dashboard assistant allows users to manage their account using natural language, answering questions by summarizing documentation and performing actions directly within the Dashboard. Users can ask about their data, like finding a customer's last payment, or issue commands, such as creating a product or a payment link.
- [No-code options for using Stripe | Stripe Documentation](https://docs.stripe.com/no-code): Stripe offers various no-code options for businesses to accept payments, sell products, and manage billing without writing code. Features include creating payment links, accepting in-person payments with Stripe Terminal, setting up recurring payments, and using Workflows for automating tasks via a visual builder in the Dashboard.
- [Create an embeddable buy button | Stripe Documentation](https://docs.stripe.com/no-code/buy-button): This page explains how to create an embeddable buy button using Stripe's Payment Links feature. You can customize the button's appearance and call to action to match your website's branding.
- [Set up the customer portal | Stripe Documentation](https://docs.stripe.com/no-code/customer-portal): Stripe's customer portal allows customers to manage their own billing information, subscriptions, and invoices. It is hosted by Stripe, meaning it can be used even without a website, or linked from an existing one.
- [Design a no-code integration | Stripe Documentation](https://docs.stripe.com/no-code/get-started): This guide helps businesses use Stripe without writing code by outlining various no-code products and services. These include accepting online and in-person payments, managing subscriptions, and creating quotes and invoices.
- [Accept in-person payments without writing code | Stripe Documentation](https://docs.stripe.com/no-code/in-person): You can accept in-person payments without code using the Stripe Dashboard mobile app's Tap to Pay feature or a Stripe Terminal Reader. This allows contactless payments directly from your phone or with a reader.
- [Use invoices | Stripe Documentation](https://docs.stripe.com/no-code/invoices): Stripe Invoicing allows you to send invoices that customers can pay online, either automatically charging a stored payment method or emailing them an invoice. You can brand your invoices and customize payment methods.
- [Create Payment Links | Stripe Documentation](https://docs.stripe.com/no-code/payment-links): Stripe Payment Links enable you to quickly accept payments for goods, services, subscriptions, tips, or donations through a single shareable link. You can configure these links for fixed prices or allow customers to choose their payment amount.
- [Pay out to people | Stripe Documentation](https://docs.stripe.com/no-code/payout): This guide explains how to add funds to your Stripe balance and pay out to sellers or service providers. It covers creating connected accounts for users and managing payout schedules.
- [Send quotes | Stripe Documentation](https://docs.stripe.com/no-code/quotes): Stripe quotes allow you to provide price estimates to customers that can be converted into invoices or subscriptions. You can include recurring and one-off items, discounts, and taxes in your quotes.
- [Create subscriptions | Stripe Documentation](https://docs.stripe.com/no-code/subscriptions): You can create subscriptions in Stripe to set up recurring payments for your services or products. Subscriptions can be managed manually through the Dashboard or allow customers to sign up via your website or a Payment Link.
- [Open banking support | Stripe Documentation](https://docs.stripe.com/open-banking): Stripe supports open banking, enabling authorized third-party providers to access user accounts with consent. This allows for account information access, fund availability confirmation, and payment initiation.
- [Apps partners | Stripe Documentation](https://docs.stripe.com/partners/apps): Apps partners build and list integrations with Stripe on the Stripe App Marketplace to extend Stripe's functionality. Partners can achieve different tiers of benefits and recognition based on their app's performance and volume.
- [Stripe Partner Ecosystem | Stripe Documentation](https://docs.stripe.com/partners): The Stripe Partner Ecosystem supports various partner tracks, including Services, SaaS platforms, Apps, Technology, and Payment Methods. Partners receive benefits like deal registration, training, and sales enablement.
- [Stripe certification for partners | Stripe Documentation](https://docs.stripe.com/partners/training-and-certification): Stripe offers architect and developer certifications for partners, with associate and professional levels. These certifications help partners become Stripe Verified Partners and demonstrate expertise in Stripe implementations.
- [Payment method partners | Stripe Documentation](https://docs.stripe.com/partners/payment-methods): Payment method partners integrate their payment methods into Stripe, allowing Stripe users to access them. This track is invite-only and provides partners with technical training, distribution support, and marketing resources.
- [SaaS platform partners | Stripe Documentation](https://docs.stripe.com/partners/platforms): SaaS platform partners embed payments and financial services into their own platforms, creating new revenue opportunities. They can join the Stripe Partner Ecosystem at Verified or Premier Partner tiers, gaining access to resources and revenue sharing.
- [Services partners | Stripe Documentation](https://docs.stripe.com/partners/services): Services partners, such as system integrators and agencies, advise, implement, or offer services using Stripe. Verified services partners receive training and resources, and can earn specializations to become Stripe recommended partners.
- [Technology partners | Stripe Documentation](https://docs.stripe.com/partners/technology): Technology partners offer products and solutions that integrate seamlessly with Stripe, including cloud providers and ISVs. Verified technology partners receive technical training, sales support, and marketing resources to support their solutions.
- [Use payment line items for flexible payments | Stripe Documentation](https://docs.stripe.com/payments/payment-line-items/flexible-payment-scenarios): Payment line items can be used with complex payments like multicaptures and overcaptures. By providing this additional transaction metadata, you can potentially achieve cost savings, facilitate reconciliation, and improve authorization rates.
- [Payment line items | Stripe Documentation](https://docs.stripe.com/payments/payment-line-items): Payment line items in the Payment Intents API offer benefits for card and local payment method processing. This includes potential interchange fee savings for eligible commercial cards, easier reconciliation, and improved authorization rates.
- [Authenticate with 3D Secure | Stripe Documentation](https://docs.stripe.com/payments/3d-secure/authentication-flow): You can integrate 3D Secure (3DS) authentication into your checkout flow across multiple platforms to comply with regulations like Strong Customer Authentication. Stripe automatically triggers 3DS2 when supported, falling back to 3DS1 if necessary.
- [3D Secure authentication | Stripe Documentation](https://docs.stripe.com/payments/3d-secure): 3D Secure (3DS) is an authentication protocol that adds a security layer to card transactions, helping to protect against fraud and meet regulatory requirements like Strong Customer Authentication (SCA). It may prompt cardholders to authenticate via familiar methods such as passwords or one-time codes. Stripe offers various ways to integrate 3DS, including native integration, SCA exemptions, standalone 3DS, and importing 3DS results.
- [Japan 3DS mandate exemptions | Stripe Documentation](https://docs.stripe.com/payments/3d-secure/japan-exemptions): Japan mandates online businesses to use 3D Secure (3DS) by March 2025, with specific exemption criteria available to reduce cardholder friction. Stripe generally attempts 3DS authentication at least once for cards, but does not automatically apply it to debit, prepaid, Apple Pay, Google Pay, or MOTO payments. Using an exemption means liability shift for fraudulent payments does not apply unless explicitly requested.
- [Secure corporate payments | Stripe Documentation](https://docs.stripe.com/payments/3d-secure/secure-corporate-payments): This page explains how to explicitly identify a card payment as a secure corporate payment within the PaymentIntents API. This allows for more secure handling and processing of corporate transactions.
- [Standalone 3DS | Stripe Documentation](https://docs.stripe.com/payments/3d-secure/standalone-three-d-secure): Standalone 3DS allows businesses to run EMV 3D Secure (3DS) authentication and then authorize the payment with any payment service provider. This decouples authentication and authorization, enabling the use of multiple payment processors or specialized workflows. Enterprise businesses can leverage Standalone 3DS for API-level control, observability into issuer responses, and customized transaction flows.
- [Strong Customer Authentication (SCA) exemptions | Stripe Documentation](https://docs.stripe.com/payments/3d-secure/strong-customer-authentication-exemptions): Strong Customer Authentication (SCA) exemptions, including Low Value and Transaction Risk Analysis (TRA), can be used to reduce cardholder friction for eligible transactions in the EEA, Switzerland, and the UK. Stripe requests these exemptions on your behalf to meet SCA requirements. It's important to note that when an exemption is approved by the customer's bank, the liability shift for fraudulent transactions does not apply.
- [Import 3D Secure results | Stripe Documentation](https://docs.stripe.com/payments/payment-intents/three-d-secure-import): Importing 3D Secure results is an advanced payment flow for processing payments when 3DS authentication occurs outside of Stripe. This is useful for industries like travel or when using a third-party provider for 3DS. You can pass card details and the 3DS cryptogram directly to the Payment Intents API, avoiding the need for Stripe Elements for collection and authentication.
- [A/B testing a payment method | Stripe Documentation](https://docs.stripe.com/payments/a-b-testing): A/B testing allows businesses to measure the impact of offering new payment methods to a percentage of buyers before a full rollout, without requiring code changes. It is useful for testing payment methods like Buy Now, Pay Later options, measuring the effect of targeting rules, or gradually introducing new payment methods. To use A/B testing, your integration must utilize dynamic payment methods and either Payment Element with the Payment Intents API or Checkout.
- [Balances and settlement time | Stripe Documentation](https://docs.stripe.com/payments/balances): Your Stripe account can have multiple balances for different products and currencies, impacting fund management and settlement times. Key balance types include the payments balance (for incoming transactions and deductions for refunds/disputes) and a dedicated refunds and disputes balance that can be funded via top-ups. Stripe may also establish a reserve balance to cover potential incoming refunds or disputes.
- [Receipts and paid invoices | Stripe Documentation](https://docs.stripe.com/receipts): Stripe automatically sends payment or refund receipts, each containing a unique receipt number and a link to view it online. These Stripe-hosted receipts reflect the latest charge status and expire after 30 days for security. You can enable automated receipts through Payment Links, Checkout Sessions API, or Stripe-hosted pages, and manually send or resend them from the Dashboard.
- [Accept a payment | Stripe Documentation](https://docs.stripe.com/payments/accept-a-payment): Stripe enables businesses to securely accept online payments through various integration methods, including building custom payment forms with Elements or using prebuilt checkout pages. For non-developers, Stripe offers no-code options and partner apps, or plugins for third-party platforms. The documentation outlines different integration types like Checkout, Elements, Mobile, and Stripe-hosted pages, along with API access via official libraries.
- [Accept a payment | Stripe Documentation](https://docs.stripe.com/payments/accept-a-payment?payment-ui=checkout&ui=embedded-form): Stripe allows businesses to securely accept online payments by embedding a prebuilt payment form on their site using Stripe Checkout. This integration offers limited UI customization through Dashboard branding settings. The process involves creating a Checkout Session on the server-side, configuring it with line items and options, and can be used for existing customers to prefill fields.
- [Accept a payment | Stripe Documentation](https://docs.stripe.com/payments/accept-a-payment?payment-ui=elements&api-integration=checkout): Businesses can build custom payment forms using Stripe Elements and the Checkout Sessions API to securely accept online payments. This approach is recommended for most integrations as it provides built-in support for tax calculation, discounts, shipping, and currency conversion. The client-side and server-side code constructs a checkout form that accommodates various payment methods.
- [Accept a payment | Stripe Documentation](https://docs.stripe.com/payments/accept-a-payment?payment-ui=elements&api-integration=paymentintents): Stripe facilitates building custom payment forms using Stripe Elements and the Payment Intents API for accepting online payments. While this offers lower-level control, it requires more code and maintenance compared to using Payment Element with Checkout Sessions. The process involves client-side and server-side code to create a checkout form that supports multiple payment methods.
- [Accept a payment | Stripe Documentation](https://docs.stripe.com/payments/accept-a-payment?payment-ui=mobile&platform=ios): Stripe's PaymentSheet class allows iOS apps to integrate a prebuilt payment UI for checkout, simplifying the collection of payment details and confirmation. The integration involves server-side endpoints to communicate with the Stripe API and client-side implementation using the Stripe iOS SDK. The SDK is open-source and compatible with apps supporting iOS 13 or above.
- [Accept a payment | Stripe Documentation](https://docs.stripe.com/payments/accept-a-payment?payment-ui=mobile&platform=android): Stripe's PaymentSheet class enables Android apps to integrate a prebuilt payment UI for checkout, streamlining payment collection and confirmation. Integration requires server-side endpoints for Stripe API communication and client-side implementation using the Stripe Android SDK. The SDK is open-source and provides comprehensive documentation for developers.
- [Accept a payment | Stripe Documentation](https://docs.stripe.com/payments/accept-a-payment?payment-ui=mobile&platform=react-native): For React Native applications, Stripe offers an SDK that integrates a prebuilt payment UI into a single sheet for checkout, simplifying payment collection and confirmation. This integration utilizes the native iOS and Android SDKs internally. Setup involves server-side endpoints for Stripe API communication and client-side implementation using the provided React Native SDK.
- [Accept payments for digital goods on iOS with a prebuilt payment page | Stripe Documentation](https://docs.stripe.com/mobile/digital-goods/checkout): iOS apps can accept payments for digital goods and subscriptions by redirecting customers to a Stripe-hosted payment page using Stripe Checkout. This method is suitable for selling credits within an app, and it models digital goods using Products, Prices, and Customers. Universal Links can be used to redirect customers directly back to the app from the payment page.
- [Accept payments for digital goods on iOS with your own checkout page | Stripe Documentation](https://docs.stripe.com/mobile/digital-goods/custom-checkout): For digital products, content, and subscriptions in the US or EEA, iOS apps can use Stripe Elements to accept Apple Pay on their own custom checkout page. This guide details how to collect payment information using Elements and redirect customers to your checkout page. It's recommended for businesses with a limited number of products or those needing more dynamic cart functionality.
- [Accept payments for digital goods on iOS using Payment Links | Stripe Documentation](https://docs.stripe.com/mobile/digital-goods/payment-links): iOS apps can sell digital goods and subscriptions using Payment Links, which redirect customers to a Stripe-hosted payment page. This low-code solution is ideal for a limited number of products and prices, and for those who don't want to run a server. It supports Apple Pay for digital products in the US and EEA, redirecting customers back to the app via Universal Links.
- [Adaptive Pricing | Stripe Documentation](https://docs.stripe.com/payments/custom/localize-prices/adaptive-pricing): Adaptive Pricing allows customers in over 150 countries to pay in their local currency by inferring their location via IP address and automatically calculating localized prices. This feature, accessible via the Checkout Sessions API, helps unlock payment methods requiring local currency and facilitates compliance. Pricing can be displayed using the Currency Selector Element, with real-time exchange rates guaranteed for 24 hours.
- [Make line item quantities adjustable | Stripe Documentation](https://docs.stripe.com/payments/advanced/adjustable-quantity): This page explains how to enable adjustable quantities for line items in Stripe Checkout Sessions, allowing customers to modify item quantities during the checkout process. It details the server-side implementation using the Payment Intents API and provides code examples for enabling this feature.
- [Charge for shipping | Stripe Documentation](https://docs.stripe.com/payments/advanced/charge-shipping): This document guides users on how to charge customers for shipping by creating various shipping rates in Stripe. It explains that shipping rates support fixed amounts per order and can be configured through the Dashboard or API.
- [Compare the Checkout Sessions and Payment Intents APIs | Stripe Documentation](https://docs.stripe.com/payments/checkout-sessions-and-payment-intents-comparison): This page compares Stripe's Checkout Sessions API and Payment Intents API, recommending Checkout Sessions as the preferred choice for most integrations due to its ease of use and lower coding requirements. The Payment Intents API is presented as a lower-level option for more custom checkout flows.
- [Collect additional information | Stripe Documentation](https://docs.stripe.com/payments/advanced/collect-additional-info): This page provides instructions on collecting additional customer information, such as physical addresses and phone numbers, during one-time payment flows using Stripe Elements. It also covers customizing billing details and charging for shipping.
- [Collect physical addresses and phone numbers | Stripe Documentation](https://docs.stripe.com/payments/advanced/collect-addresses): This guide explains how to collect physical addresses and phone numbers during one-time payment flows using Stripe's Address Element. It also details how the Payment Element can be configured to collect additional billing details and how to prefill information.
- [Redeem credits | Stripe Documentation](https://docs.stripe.com/payments/advanced/credits): This page describes how to integrate a credits system into Stripe Checkout Sessions, allowing customers to redeem store credit or gift cards to reduce the total amount due. Stripe does not manage credits; the amount must be passed into the Checkout Session, and the used credit amount retrieved for reconciliation.
- [Add discounts | Stripe Documentation](https://docs.stripe.com/payments/advanced/discounts): This document explains how to add discounts to purchases using the Checkout Sessions API through coupons and promotion codes. It covers applying discounts to entire purchases or specific products, either as a percentage or a fixed amount.
- [Dynamically update your Elements integration | Stripe Documentation](https://docs.stripe.com/payments/advanced/dynamic-updates): This page details how to dynamically update a Stripe Elements integration, allowing changes to the Checkout Session or Payment Intent based on customer actions. It covers updating shipping options, line items, trial durations, discounts, and payment amounts.
- [Dynamically update payment amounts | Stripe Documentation](https://docs.stripe.com/payments/advanced/dynamically-update-amounts): This guide explains how to dynamically update payment amounts in Stripe Checkout Sessions or Payment Intents when customers modify their selections or payment methods. It emphasizes recalculating totals on the server-side for security and lists common use cases like adding add-ons or changing shipping methods.
- [Dynamically update discounts | Stripe Documentation](https://docs.stripe.com/payments/advanced/dynamically-update-discounts): This page explains how to dynamically add or remove discounts during checkout for Stripe Checkout Sessions, currently in private preview. It outlines use cases such as loyalty discounts, cart value promotions, time-sensitive offers, and customer-specific offers.
- [Dynamically update line items | Stripe Documentation](https://docs.stripe.com/payments/advanced/dynamically-update-line-items): This guide explains how to dynamically add, remove, or update line items within a Stripe Checkout Session during the checkout process. Use cases include upsells, inventory checks, adding complimentary products, and updating tax or shipping rates based on cart contents.
- [Dynamically customize shipping options | Stripe Documentation](https://docs.stripe.com/payments/advanced/shipping): This page explains how to dynamically customize shipping options in Stripe Checkout based on the customer's entered address, available only with the embedded version of Checkout. It covers validating addresses, showing relevant shipping options, and dynamically calculating shipping rates.
- [Dynamically update trial durations | Stripe Documentation](https://docs.stripe.com/payments/advanced/dynamically-update-trials): This page describes how to dynamically update subscription trial durations during checkout for Stripe Checkout Sessions, currently in private preview. Use cases include managing trials based on promotions or customer actions and extending trials for upsells.
- [Email receipts | Stripe Documentation](https://docs.stripe.com/payments/advanced/receipts): This page explains how to automatically send customized email receipts and paid invoices for successful payments in Stripe. It also covers customization options for branding, public information, and custom text descriptions.
- [Build an advanced payments integration | Stripe Documentation](https://docs.stripe.com/payments/advanced): This page provides an overview of building advanced payment integrations using Stripe Elements with either the Checkout Sessions API or the Payment Intents API. It highlights Checkout Sessions as the recommended API for most integrations due to its lower coding effort and extensive customization options.
- [Let customers pay in their local currency | Stripe Documentation](https://docs.stripe.com/payments/custom/localize-prices): This page explains how to allow customers to pay in their local currency by displaying multiple currencies and supporting over 100 currencies. It introduces Adaptive Pricing, the FX Quotes API for currency conversion, and manual currency price settings.
- [Enable currency conversion using the FX Quotes API | Stripe Documentation](https://docs.stripe.com/payments/custom/localize-prices/fx-quotes-api): This page details how to use the FX Quotes API to enable currency conversion capabilities, including current exchange rates, extended rate quotes, and foreign exchange fee information. Displaying prices in local currencies can improve conversion and authorization rates.
- [Migrate payment methods to the Dashboard | Stripe Documentation](https://docs.stripe.com/payments/advanced/dashboard-payment-methods): This page explains how to migrate payment method preferences to the Stripe Dashboard, allowing Stripe to display compatible payment methods based on currency, location, or restrictions. Existing integrations need to remove the payment_method_types parameter to enable this feature.
- [Manual currency prices | Stripe Documentation](https://docs.stripe.com/payments/custom/localize-prices/manual-currency-prices): This page describes how to manually set prices in different currencies when creating products in Stripe, useful for regions with exchange rate fluctuations or when Adaptive Pricing is not supported. It recommends using Adaptive Pricing for reduced risk and broader currency support.
- [Manage payment methods | Stripe Documentation](https://docs.stripe.com/payments/advanced/payment-methods/manage): This page explains how to manage payment methods within Stripe, covering adding custom payment methods, customizing their display in the Payment Element, and saving/retrieving customer payment methods. It also mentions migrating payment methods to the Dashboard and using Express Checkout.
- [Build a subscriptions integration with Elements | Stripe Documentation](https://docs.stripe.com/payments/advanced/build-subscriptions): This guide explains how to build a subscription integration using Stripe Elements and the Checkout Sessions API. It details how to create a custom payment form for fixed-price subscriptions, leveraging the API's built-in support for taxes, discounts, and currency conversion.
- [Acceptance analytics | Stripe Documentation](https://docs.stripe.com/payments/analytics/acceptance): The Acceptance analytics page helps you understand and improve your payment success rate. It provides data on attempted and authorized card payments, allowing you to identify where and why payments fail to increase revenue.
- [Authentication analytics | Stripe Documentation](https://docs.stripe.com/payments/analytics/authentication): Authentication analytics, found on the Dashboard's Authentication page, shows how 3D Secure impacts your card payment success rate. Setting up 3D Secure is necessary to view these analytics, which help in managing fraud and liability.
- [Disputes analytics | Stripe Documentation](https://docs.stripe.com/payments/analytics/disputes): The Disputes analytics page allows you to analyze card dispute volume, rates, and outcomes. It helps monitor dispute and fraud rates, understand dispute reasons, and improve evidence submission performance to mitigate financial impact.
- [Payments analytics | Stripe Documentation](https://docs.stripe.com/payments/analytics): The Payments analytics page in the Stripe Dashboard provides a comprehensive overview of payment performance. It offers reports on acceptance, authentication, disputes, and payment methods, with options for advanced filtering and time period comparisons.
- [Payments optimization | Stripe Documentation](https://docs.stripe.com/payments/analytics/optimization): Payments optimization focuses on increasing payment success rates and reducing costs, particularly for card-not-present transactions. It highlights Stripe's Authorization Boost features, like Adaptive Acceptance, which use AI to reformat payment requests and recover declined payments.
- [Payment methods analytics | Stripe Documentation](https://docs.stripe.com/payments/analytics/payment-methods): Payment methods analytics helps you understand customer preferences by showing the frequency of alternative payment methods compared to cards. You can filter data by specific payment methods and currencies to gain insights into usage patterns.
- [Recommendations | Stripe Documentation](https://docs.stripe.com/payments/analytics/recommendations): The Recommendations page offers Stripe's suggestions to increase revenue and improve fraud detection. These data-driven insights are presented on the Acceptance page and should be carefully considered for their potential impacts and tradeoffs.
- [Bank redirects | Stripe Documentation](https://docs.stripe.com/payments/bank-redirects): Bank redirects enable customers to pay online using their bank accounts, significantly boosting online commerce in certain regions. This integration method is supported across Stripe products, including Stripe Checkout, by changing a single line of code.
- [Accept card payments without webhooks | Stripe Documentation](https://docs.stripe.com/payments/accept-a-payment-synchronously): This guide details how to confirm card payments on your server without using webhooks, handling authentication requests directly. It notes that while simpler, this synchronous method has limitations and recommends the Payment Element for broader support.
- [Save a card without bank authentication | Stripe Documentation](https://docs.stripe.com/payments/save-card-without-authentication): This integration allows collecting card details and charging customers later, particularly useful for US and Canadian cards where bank authentication isn't always required. Expanding to other regions may necessitate significant changes to comply with local regulations.
- [Card payments on the Charges API | Stripe Documentation](https://docs.stripe.com/payments/charges-api): This page covers legacy card payment processing using the Charges API, recommending the Payment Intents API for new integrations. The Charges API lacks support for modern features like Strong Customer Authentication and businesses in India.
- [Migrate your basic card integration | Stripe Documentation](https://docs.stripe.com/payments/payment-intents/upgrade-to-handle-actions): This guide helps migrate basic card integrations to handle bank requests for payment authentication. It involves updating server-side and client-side code to manage payments that require additional customer authentication, preventing declines.
- [More payment scenarios | Stripe Documentation](https://docs.stripe.com/payments/more-payment-scenarios): This page explores various payment scenarios, emphasizing the flexibility of Payment Intents and Setup Intents APIs. It covers holding payments, ignoring bank authentication, building two-step confirmations, and collecting details before creating an Intent.
- [How cards work | Stripe Documentation](https://docs.stripe.com/payments/cards/overview): This overview explains the process of online credit or debit card payments, including checking card details, customer authentication, authorization, and capture. It highlights how banks may prompt for additional authentication in regulated regions.
- [Payments for existing customers | Stripe Documentation](https://docs.stripe.com/payments/existing-customers): This guide explains how to charge existing payment methods for on-session customers using Stripe. It details how Checkout Sessions can prefill customer details and display saved cards for payment selection.
- [Save a customer's payment method when they use it for a payment | Stripe Documentation](https://docs.stripe.com/payments/save-during-payment): This guide explains how to save a customer's payment method for future purchases during a payment process. It is useful for e-commerce orders, initiating recurring payments, or charging deposits, and requires compliance with regulations.
- [Save a customer's payment method when they use it for a payment | Stripe Documentation](https://docs.stripe.com/payments/save-during-payment?platform=platform=ios&mobile-ui=payment-element): This guide explains how to save a customer's payment method for future purchases during a payment process. It is useful for e-commerce orders, initiating recurring payments, or charging deposits, and requires compliance with regulations.
- [Save a customer's payment method when they use it for a payment | Stripe Documentation](https://docs.stripe.com/payments/save-during-payment?platform=platform=android&mobile-ui=payment-element): This guide explains how to save a customer's payment method for future purchases during a payment process. It is useful for e-commerce orders, initiating recurring payments, or charging deposits, and requires compliance with regulations.
- [Save a customer's payment method when they use it for a payment | Stripe Documentation](https://docs.stripe.com/payments/save-during-payment?platform=platform=react-native&mobile-ui=payment-element): This guide explains how to save a customer's payment method for future purchases during a payment process. It is useful for e-commerce orders, initiating recurring payments, or charging deposits, and requires compliance with regulations.
- [Set up future card payments | Stripe Documentation](https://docs.stripe.com/payments/save-and-reuse-cards-only): This guide explains how to set up future card payments using Stripe Checkout's setup mode, which utilizes the Setup Intents API to create reusable Payment Methods. It's recommended for integrations requiring manual server-side confirmation or separate payment method presentation, and suggests using Checkout's setup mode for collecting customer payment details for later use.
- [Save a customer's payment method without making a payment | Stripe Documentation](https://docs.stripe.com/payments/save-and-reuse): This page details how to save a customer's payment method without immediately charging them, using Stripe's Checkout Sessions API in setup mode. This is crucial for complying with SCA regulations, ensuring future payments are authenticated upfront. It's ideal for setting up recurring payments or one-time payments where the final amount is determined later.
- [The Setup Intents API | Stripe Documentation](https://docs.stripe.com/payments/setup-intents): The Setup Intents API allows you to prepare a payment method for future use without creating an immediate charge. This is particularly useful for businesses that onboard customers before charging them, such as car rental companies or utility providers. The API ensures payment credentials are saved and optimized for future transactions, including necessary customer authentication.
- [Card payments without bank authentication | Stripe Documentation](https://docs.stripe.com/payments/without-card-authentication): This integration enables card payments without requiring bank authentication, specifically for businesses accepting only US and Canadian cards. It offers a simpler integration but does not support a global customer base. Stripe.js Elements provides secure, hosted UI components for collecting card information, ensuring PCI compliance.
- [Manage payment methods | Stripe Documentation](https://docs.stripe.com/payments/checkout/payment-methods): Stripe dynamically displays relevant payment methods based on dashboard preferences and eligibility factors like transaction amount and currency. You can override these defaults by manually specifying payment methods when creating a Checkout Session. Managing payment methods through the Dashboard is generally recommended unless your integration requires manual specification.
- [Recover abandoned carts | Stripe Documentation](https://docs.stripe.com/payments/checkout/abandoned-carts): This guide explains how to recover abandoned carts in Stripe Checkout to boost revenue by re-engaging customers who left the checkout flow. It covers collecting customer consent for promotional emails and receiving notifications when carts are abandoned, enabling follow-up communication to complete purchases.
- [Set the billing cycle date | Stripe Documentation](https://docs.stripe.com/payments/checkout/billing-cycle): You can explicitly set a subscription's billing cycle anchor to a fixed date when creating a Checkout Session. This anchor determines the first full invoice date and influences all future billing dates. Proration behavior for the initial billing period can be customized using the proration_behavior parameter.
- [Compliant promotional emails | Stripe Documentation](https://docs.stripe.com/payments/checkout/compliant-promotional-emails): This page outlines best practices for sending compliant promotional emails, which are used to inform customers about new products or share discounts. It emphasizes the importance of obtaining customer consent before sending such emails and honoring unsubscribe requests, in accordance with privacy and marketing laws.
- [Add custom fields | Stripe Documentation](https://docs.stripe.com/payments/checkout/custom-fields): You can add custom fields to Stripe's prebuilt payment form to collect additional customer information beyond standard fields. These fields can be text, numeric, or dropdown types, with limitations on the number of fields and characters. Custom fields are not available in setup mode and should not be used for sensitive data.
- [Customize redirect behavior | Stripe Documentation](https://docs.stripe.com/payments/checkout/custom-success-page): This guide explains how to customize the redirect behavior after a customer completes a payment using Stripe Checkout. For hosted pages, Stripe redirects customers to a success page you create, where you can use Checkout Session details to display order confirmation information. Webhooks are essential for reliable order fulfillment.
- [Add discounts | Stripe Documentation](https://docs.stripe.com/payments/checkout/discounts): Stripe Checkout allows you to apply discounts to customer purchases using coupons and promotion codes. These can reduce the total amount charged by a percentage or a fixed amount, and can be applied to entire purchases or specific products. You can create and manage coupons and promotion codes through the Stripe Dashboard or API.
- [Configure free trials | Stripe Documentation](https://docs.stripe.com/payments/checkout/free-trials): You can configure free trials for subscriptions within Stripe Checkout, with a maximum duration of two years. To set up a trial, you pass parameters like `trial_period_days` or `trial_end` when creating a Checkout Session. Checkout can collect a payment method upfront or allow sign-ups without payment details using `payment_method_collection=if_required`.
- [Collect customer names | Stripe Documentation](https://docs.stripe.com/payments/checkout/name-collection): This page explains how to enable the collection of business or individual names on Stripe Checkout's payment form. Name collection can be configured as required or optional when creating a Checkout Session. This information is available after the session is complete and is separate from billing and shipping details.
- [Collect customer phone numbers | Stripe Documentation](https://docs.stripe.com/payments/checkout/phone-numbers): You can enable phone number collection on Stripe Checkout for payment and subscription mode Sessions, but not in setup mode. A required phone number field is added to the payment form when enabled, useful for shipping or invoicing purposes. The collected phone number can be retrieved after the session is complete.
- [Collect consent for promotional emails | Stripe Documentation](https://docs.stripe.com/payments/checkout/promotional-emails-consent): Stripe Checkout facilitates collecting customer consent for promotional emails, which is required by privacy laws in many regions. When creating a Checkout Session, you can use the `consent_collection[promotions]` parameter to automatically display a consent checkbox. This helps ensure compliance when sending marketing communications.
- [After the payment | Stripe Documentation](https://docs.stripe.com/payments/checkout/after-the-payment): This section covers customizing the post-payment process in Stripe Checkout. It includes options for fulfilling orders, customizing the redirect behavior to a success page, recovering abandoned carts, analyzing conversion funnels with Google Analytics 4, and automatically sending email receipts and paid invoices.
- [Analyze your conversion funnel | Stripe Documentation](https://docs.stripe.com/payments/checkout/analyze-conversion-funnel): You can analyze your Stripe Checkout conversion funnel using Google Analytics 4 (GA4) by tracking user progression through the purchase flow. This involves setting up a GA4 account and property, and then integrating GA4 tracking into your product pages and server-side endpoints that create Checkout Sessions.
- [Elements with Checkout Sessions API beta changelog | Stripe Documentation](https://docs.stripe.com/checkout/elements-with-checkout-sessions-api/changelog): This changelog details updates to the beta version of the Elements with Checkout Sessions API integration. It highlights breaking changes, such as making the `stripe.initCheckout` method synchronous and enabling saved payment methods by default in the Payment Element. It also notes the removal of automatic postal code collection for card payments in specific regions.
- [One-time payments with Checkout | Stripe Documentation](https://docs.stripe.com/payments/checkout/client): The client-only integration of Stripe Checkout is deprecated and not recommended for new integrations, as it lacks many features of the client-server approach. For a no-code workflow, Payment Links are suggested. This older method requires defining products and prices in the Stripe Dashboard and referencing them by ID on the client side without server-side code.
- [Collect additional information | Stripe Documentation](https://docs.stripe.com/payments/checkout/collect-additional-info): This page describes how to collect additional customer information during a Stripe Checkout session. Options include collecting physical addresses, phone numbers, business and individual names, and adding custom fields. It also covers charging for shipping and obtaining consent for promotional emails.
- [Collect physical addresses | Stripe Documentation](https://docs.stripe.com/payments/collect-addresses): Stripe Checkout allows you to collect billing and shipping addresses from customers. You can configure Checkout Sessions to require billing addresses or specify allowed countries for shipping addresses.
- [Dynamically customize shipping options | Stripe Documentation](https://docs.stripe.com/payments/checkout/custom-shipping-options): This page explains how to dynamically update shipping options based on a customer's shipping address when using the embedded version of Stripe Checkout. This feature allows for address validation, showing relevant shipping methods, and calculating dynamic shipping rates.
- [Customize Checkout | Stripe Documentation](https://docs.stripe.com/payments/checkout/customization): Stripe Checkout offers extensive customization options for its appearance and behavior. You can personalize branding, text, policies, card brands displayed, and even use custom domains for a tailored customer experience.
- [Customize appearance | Stripe Documentation](https://docs.stripe.com/payments/checkout/customization/appearance): You can customize the visual appearance of your Stripe Checkout page, including colors, fonts, and shapes, to match your brand. This can be done through the Stripe Dashboard's Branding Settings or via the API.
- [Customize card brands | Stripe Documentation](https://docs.stripe.com/payments/checkout/customization/card-brands): Stripe Checkout enables you to customize which card brands are displayed to your customers. You can block specific card brands using the `brands_blocked` parameter when creating a Checkout Session.
- [Customize text and policies | Stripe Documentation](https://docs.stripe.com/payments/checkout/customization/policies): You can customize the text and policies displayed to customers within Stripe Checkout. This allows for adding information about shipping, processing times, or other relevant messages to enhance clarity.
- [Add product images | Stripe Documentation](https://docs.stripe.com/payments/checkout/customization/product-images): Adding product images and descriptions to your Stripe Checkout integration provides a visual representation for customers. This can be configured through the Dashboard or the Checkout Sessions API to potentially increase conversion rates.
- [Dynamically update checkout | Stripe Documentation](https://docs.stripe.com/payments/checkout/dynamic-updates): Stripe Checkout allows for dynamic updates during the checkout process, enabling features like customizing shipping options based on the customer's address and updating line items in response to checkout changes.
- [Track analytics events in Embedded Checkout | Stripe Documentation](https://docs.stripe.com/payments/checkout/embedded-analytics): Embedded Checkout provides real-time analytics events to monitor user behavior throughout the checkout process. These events can be used to track user actions, optimize conversion rates, and integrate with analytics platforms.
- [Fulfill orders | Stripe Documentation](https://docs.stripe.com/checkout/fulfillment): This guide explains how to fulfill orders after a customer makes a payment using the Checkout Sessions API. Fulfillment can be handled manually through the Dashboard or automatically by building a dedicated system.
- [How Checkout works | Stripe Documentation](https://docs.stripe.com/payments/checkout/how-checkout-works): Stripe Checkout is a low-code payment integration that offers a customizable form for collecting payments. It supports over 40 payment methods and can be embedded into your website or used as a Stripe-hosted page.
- [Use a prebuilt Stripe-hosted payment page | Stripe Documentation](https://docs.stripe.com/payments/checkout): Stripe Checkout provides a prebuilt, hosted payment page or an embeddable form for accepting payments. It utilizes the Checkout Sessions API and supports various payment methods for one-time and subscription purchases.
- [Checkout prices migration guide | Stripe Documentation](https://docs.stripe.com/payments/checkout/migrating-prices): The Prices API in Stripe Checkout offers a more unified model for managing products and prices, replacing older methods like SKUs and inline line items. This allows for features like rendering product images for recurring items and applying dynamic tax rates.
- [Checkout migration guide | Stripe Documentation](https://docs.stripe.com/payments/checkout/migration): This guide helps you migrate to Stripe's latest Checkout integrations, which are smart payment pages hosted by Stripe. These modern versions offer enhanced features compared to the legacy modal dialog.
- [Make line item quantities adjustable | Stripe Documentation](https://docs.stripe.com/payments/checkout/adjustable-quantity): You can enable customers to adjust the quantity of items directly within the checkout process. This is configured by setting the `adjustable_quantity` parameter on line items when creating a Checkout Session.
- [Dynamically update line items | Stripe Documentation](https://docs.stripe.com/payments/checkout/dynamically-update-line-items): This feature allows for dynamic updates to line items within a Checkout Session, enabling actions like checking inventory, adding products, or updating shipping and tax rates based on checkout changes. It is not supported for hosted pages.
- [Manage your product catalog | Stripe Documentation](https://docs.stripe.com/payments/checkout/product-catalog): Stripe Checkout allows you to manage your product catalog, including handling limited inventory by expiring sessions and enabling adjustable line item quantities. It also supports dynamically updating line items and allowing customers to choose their payment amount.
- [Manage limited inventory | Stripe Documentation](https://docs.stripe.com/payments/checkout/managing-limited-inventory): You can manage limited inventory in Stripe Checkout by expiring sessions to prevent customers from holding items for too long without purchasing. This can be done manually or by setting a specific expiration time when creating the session.
- [Let customers decide what to pay | Stripe Documentation](https://docs.stripe.com/payments/checkout/pay-what-you-want): Stripe Checkout supports 'pay-what-you-want' models, allowing customers to set their own price for products or services, or to add tips and donations. This feature has specific limitations, such as not supporting other line items or recurring payments.
- [Add discounts, upsells, and optional items | Stripe Documentation](https://docs.stripe.com/payments/checkout/promotions): Boost sales with Stripe Checkout's features for discounts, upsells, and optional items. You can offer coupons, promotion codes, free trials for subscriptions, allow customers to upgrade plans, or purchase complementary products.
- [Email receipts and paid invoices | Stripe Documentation](https://docs.stripe.com/payments/checkout/receipts): This page explains how to automatically send customized email receipts and paid invoices to customers. You can customize the appearance and content of these receipts through your Stripe Branding and Public details settings.
- [Save payment details during payment | Stripe Documentation](https://docs.stripe.com/payments/checkout/save-during-payment): This page details how to use Stripe Checkout to allow customers to save their payment details for future purchases. It outlines the server-side setup, including creating a Customer object to facilitate payment method reuse and tracking.
- [Save payment details during payment | Stripe Documentation](https://docs.stripe.com/payments/checkout/save-during-payment?payment-ui=embedded-form): This page describes how to use Stripe Checkout with an embedded payment form to enable customers to save their payment details for future purchases. It covers the server-side setup, emphasizing the creation of a Customer object for payment method reuse and tracking.
- [Set up future payments | Stripe Documentation](https://docs.stripe.com/payments/checkout/save-and-reuse): This page explains how to set up future payments by saving payment details within a Checkout session, allowing for later charges. It highlights the importance of customer authentication due to SCA regulations and introduces Checkout's setup mode which uses the Setup Intents API.
- [Set up future payments | Stripe Documentation](https://docs.stripe.com/payments/checkout/save-and-reuse?payment-ui=embedded-form): This page details how to use Stripe Checkout's setup mode to collect and save customer payment details for future use, leveraging the Setup Intents API. It emphasizes that SCA regulations require upfront customer authentication for subsequent charges and provides server-side instructions for creating a setup mode Checkout Session.
- [Set up a subscription with iDEAL and SEPA Direct Debit | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/ideal): This page guides on setting up subscriptions using iDEAL and SEPA Direct Debit. It explains that iDEAL is used for the initial authentication and payment, which also saves the customer's IBAN for SEPA Direct Debit, enabling future payments.
- [Set up a subscription with SEPA Direct Debit | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/sepa-debit): This page explains how to set up and charge subscriptions using SEPA Direct Debit in the EU. It describes the process of creating a Checkout Session for subscription initiation, where customers are redirected to complete their purchase and are then returned to your site.
- [Set up a subscription with ACH Direct Debit | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/ach-debit): This page provides instructions on setting up subscriptions with ACH Direct Debit for US bank accounts. It suggests using the Payment Element for a low-code integration and outlines the process of creating products and prices in the Stripe Dashboard.
- [Set up a subscription with Bacs Direct Debit | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/bacs-debit): This page details how to set up subscriptions using Bacs Direct Debit in the UK with Stripe Checkout. It covers the server-side setup and creating recurring products and prices, noting that the Prices API unifies the modeling of one-time and subscription purchases.
- [Build a subscriptions integration with Checkout | Stripe Documentation](https://docs.stripe.com/payments/checkout/build-subscriptions): This page explains how to build a subscription integration using Stripe Checkout for recurring payments. It covers creating a product catalog, adding a Checkout session, monitoring subscription events, and setting up a customer portal for subscription management.
- [Subscriptions | Stripe Documentation](https://docs.stripe.com/payments/subscriptions): This page provides an overview of creating subscriptions for customers using the Checkout Sessions API. It supports various pricing models and details how to configure free trials, limit customers to one subscription, and set billing cycle dates.
- [Collect customer tax IDs with Checkout | Stripe Documentation](https://docs.stripe.com/tax/checkout/tax-ids): This page explains how to collect customer tax IDs, such as VAT numbers, using Stripe Checkout. It details how to enable tax ID collection in Checkout sessions, which dynamically displays fields for business customers based on their location.
- [Collect taxes | Stripe Documentation](https://docs.stripe.com/payments/checkout/taxes): This page explains how to collect taxes on one-time and recurring payments using Stripe Tax with Checkout. It covers how Checkout uses shipping or billing addresses to calculate taxes and mentions requirements for offering Apple Pay and Google Pay.
- [Use manual Tax Rates | Stripe Documentation](https://docs.stripe.com/payments/checkout/use-manual-tax-rates): This page describes how to use manual Tax Rates in Stripe Checkout for collecting taxes like sales, VAT, and GST. It recommends Stripe Tax for automatic support in over 60 countries and explains the use of fixed or dynamic tax rates based on customer information.
- [Update payment details | Stripe Documentation](https://docs.stripe.com/payments/checkout/subscriptions/update-payment-details): This page guides on updating the payment method for future invoices using a Checkout page that collects payment details. It involves creating a setup mode Checkout Session and using Stripe REST APIs to update the payment method associated with existing subscriptions.
- [Online payments | Stripe Documentation](https://docs.stripe.com/payments/online-payments): This page outlines integration options for accepting online payments, including using prebuilt payment UIs like Payment Links and Stripe Checkout, or building custom flows with Stripe Elements. It also covers adding payment methods and optimizing checkout speed with Link.
- [South Korean payment methods | Stripe Documentation](https://docs.stripe.com/payments/countries/korea): This page details how to accept payments in South Korea using local wallets and cards without a local entity. It explains that customers are redirected to select their card issuer or authenticate through their bank's app for payment.
- [Nigerian payment methods | Stripe Documentation](https://docs.stripe.com/payments/countries/nigeria): This page describes how to accept Nigerian local payment methods, including Naira cards and bank transfers, without a local entity. It utilizes a merchant of record solution through a Nigerian partner, offering a localized checkout flow and requiring buyer VAT to be included in presentment pricing.
- [Migrate payment methods to the Dashboard | Stripe Documentation](https://docs.stripe.com/payments/dashboard-payment-methods): This page explains how to migrate payment method preferences to the Stripe Dashboard. By removing the `payment_method_types` parameter from your integration, Stripe automatically displays compatible payment methods based on customer location and currency.
- [Stripe Web Elements | Stripe Documentation](https://docs.stripe.com/payments/elements): This page introduces Stripe Elements, a set of prebuilt UI components for building custom web checkout flows. Elements allow for tokenizing sensitive payment details securely, offer access to over 100 global payment methods, and support features like Link for faster checkout and saved payment methods.
- [Link Authentication Element | Stripe Documentation](https://docs.stripe.com/payments/elements/link-authentication-element): The Link Authentication Element allows you to integrate Link, a service that saves and autofills customer payment and shipping information. It provides a single email input field for both email collection and Link authentication, simplifying the checkout process for returning users.
- [Payment Element integration best practices | Stripe Documentation](https://docs.stripe.com/payments/payment-element/best-practices): This page outlines best practices for integrating the Payment Element, a UI component that accepts over 100 payment methods. It provides a checklist to ensure optimal performance, covering aspects like choosing a layout and applying custom styling to match your website's design.
- [Build two-step confirmation | Stripe Documentation](https://docs.stripe.com/payments/build-a-two-step-confirmation-legacy): This legacy documentation describes a two-step confirmation process for payments, allowing an optional review page or additional validations after a user enters payment details. It is recommended to migrate to newer documentation for current integrations using createPaymentMethod.
- [Build two-step confirmation | Stripe Documentation](https://docs.stripe.com/payments/build-a-two-step-confirmation): This guide explains how to build a two-step checkout flow, enabling an optional review page or additional validations before confirming an order. This process allows for actions like presenting order details for review or calculating taxes before the final confirmation.
- [Control billing details collection | Stripe Documentation](https://docs.stripe.com/payments/payment-element/control-billing-details-collection): You can control how billing details are collected within the Payment Element using three modes: 'never' to skip collection, 'if_required' to collect only necessary fields, and 'auto' (default) where Stripe determines which fields to collect based on friction and authorization success rates.
- [Add custom payment methods | Stripe Documentation](https://docs.stripe.com/payments/payment-element/custom-payment-methods): This page details how to add custom payment methods to the Payment Element, enabling merchant-instructed payments. It mentions using the Checkout Sessions API or Payment Intents API for this integration.
- [Customize payment methods | Stripe Documentation](https://docs.stripe.com/payments/customize-payment-methods): The Payment Element dynamically displays and sorts enabled payment methods to optimize conversion rates. You can customize this behavior by enabling different payment methods through the Dashboard or by manually listing payment method types.
- [Finalize payments on the server | Stripe Documentation](https://docs.stripe.com/payments/finalize-payments-on-the-server-legacy): This legacy guide explains how to build a custom payment flow where the Payment Element is rendered before creating a PaymentIntent or SetupIntent, with the payment confirmed from your server. It is recommended to use newer documentation for current integrations.
- [Finalize payments on the server | Stripe Documentation](https://docs.stripe.com/payments/finalize-payments-on-the-server): This guide explains how to finalize payments on the server by rendering the Payment Element before creating a PaymentIntent or SetupIntent, and then confirming the Intent from your server. This allows for a custom payment flow accepting multiple payment methods.
- [Collect payment details before creating an Intent | Stripe Documentation](https://docs.stripe.com/payments/accept-a-payment-deferred): This integration allows you to render the Payment Element before creating a PaymentIntent or SetupIntent, collecting payment details from the buyer's browser. For server-side confirmation, a separate guide is available.
- [Design a custom integration | Stripe Documentation](https://docs.stripe.com/payments/payment-element/design-an-integration): Before building a custom Payment Element integration, you need to make several key choices. The Checkout Sessions API is recommended for most integrations as it covers similar use cases to Payment Intents and offers a single integration path.
- [External payment methods | Stripe Documentation](https://docs.stripe.com/payments/external-payment-methods): This guide explains how to add external payment methods to the Payment Element, which are processed and finalized outside of Stripe. It recommends using the custom payment methods feature instead, which allows extending integrations with payment methods processed outside of Stripe.
- [Stripe Payment Element | Stripe Documentation](https://docs.stripe.com/payments/payment-element): The Stripe Payment Element is a secure, embeddable UI component that allows you to accept over 100 payment methods globally. It validates input, handles errors, and can be used alone or with other elements in your web application.
- [Migrate to Confirmation Tokens | Stripe Documentation](https://docs.stripe.com/payments/payment-element/migration-ct): This guide explains how to finalize payments on the server using a ConfirmationToken instead of a PaymentMethod. A ConfirmationToken holds a superset of data, including shipping information, and enables new features.
- [Migrate to the Payment Element with the Checkout Sessions API | Stripe Documentation](https://docs.stripe.com/payments/payment-element/migration-ewcs): Migrate to the Payment Element with the Checkout Sessions API to accept many payment methods with a single Element. This approach also manages taxes, shipping, discounts, and currency conversion, offering an improved experience over previous methods.
- [Migrate to the Payment Element with the Payment Intents API | Stripe Documentation](https://docs.stripe.com/payments/payment-element/migration): Migrate to the Payment Element with the Payment Intents API to accept multiple payment methods using a single Element. For advanced features like subscriptions, tax, discounts, and shipping, consider migrating to the Checkout Sessions API.
- [Compare the Payment Element and Card Element | Stripe Documentation](https://docs.stripe.com/payments/payment-card-element-comparison): The Payment Element is strongly recommended over the legacy Card Element as it accepts a wider range of payment methods with a single integration. It offers the same integration effort as the Card Element but provides instant access to additional payment methods.
- [Save and retrieve customer payment methods | Stripe Documentation](https://docs.stripe.com/payments/save-customer-payment-methods): You can save customer payment methods on the Customer object for future use with the Payment Element's Saved Payment Method feature. This requires buyer consent and allows for displaying saved methods for future purchases.
- [Customer-Initiated Transactions (CIT) and Merchant-Initiated Transactions (MIT) | Stripe Documentation](https://docs.stripe.com/payments/cits-and-mits): Card payments are categorized as Customer-Initiated Transactions (CIT) or Merchant-Initiated Transactions (MIT) based on customer participation. Card networks assign different requirements and characteristics to each type, affecting aspects like authorization validity periods.
- [Place an extended hold on an online card payment | Stripe Documentation](https://docs.stripe.com/payments/extended-authorization): Extended authorizations allow you to capture online card payments up to 30 days after authorization, holding funds for longer than standard periods. This feature is available for Visa, Mastercard, American Express, and Discover, with some network and merchant category restrictions.
- [Migrate to the latest flexible payment scenarios | Stripe Documentation](https://docs.stripe.com/payments/flexible-features-migration): This guide helps users migrate from beta versions of Stripe's flexible payment scenarios to the general release. It details the improvements made, such as finer control at the PaymentIntent level and clearer usage expectations. Specific instructions are provided for upgrading features like incremental authorization, overcapture, extended authorization, and multicapture.
- [Increment an authorization | Stripe Documentation](https://docs.stripe.com/payments/incremental-authorization): Incremental authorization allows you to increase the authorized amount of a confirmed PaymentIntent before capturing it. Each increment appears as a separate pending entry on the customer's statement until the final capture. This feature is available for Visa, Mastercard, American Express, and Discover, with certain restrictions.
- [Flexible payment scenarios | Stripe Documentation](https://docs.stripe.com/payments/flexible-payments): Stripe's flexible payment scenarios support complex payment flows with customizable acquiring features. These include multicapture for multiple shipments, overcapture for tips, incremental authorization for order changes, extended authorization for longer holds, and partial authorization for insufficient funds. These features are generally available to users on IC+ pricing.
- [Capture a payment multiple times | Stripe Documentation](https://docs.stripe.com/payments/multicapture): Multicapture enables capturing a PaymentIntent multiple times for a single transaction, up to the authorized amount. This is useful for orders with multiple shipments where funds are captured as each part is fulfilled. It supports online card payments with specific card networks and has a limit of up to 50 captures per PaymentIntent.
- [Capture more than the authorized amount on a payment | Stripe Documentation](https://docs.stripe.com/payments/overcapture): Overcapture allows you to capture a payment for an amount exceeding the initially authorized amount for a card payment. Unlike incremental authorizations, overcapture does not create additional authorizations and the customer's statement is updated upon settlement. This feature is available for specific card networks and online payments, with limitations on the overcapture amount.
- [Partial authorization | Stripe Documentation](https://docs.stripe.com/payments/partial-authorization): Partial authorization enables requesting approval for a portion of a card transaction's amount when insufficient funds are available. This allows customers to use their available balance and then pay the remainder with an alternative method. Merchants must manage how to handle the remaining balance and ensure compliance with card network rules.
- [Place a hold on a payment method | Stripe Documentation](https://docs.stripe.com/payments/place-a-hold-on-a-payment-method): Placing a hold on a payment method separates authorization from capture, allowing funds to be reserved and captured later. This is common for scenarios like hotel reservations where the final amount is captured upon checkout. Authorizations have validity windows, and funds must be captured before they expire to avoid cancellation.
- [Payments | Stripe Documentation](https://docs.stripe.com/payments): Stripe Payments provides a comprehensive platform for accepting payments online and in person. It offers various integration options, including prebuilt payment pages, custom forms with Elements, and subscription management. Beyond core payments, Stripe supports features like Link for faster checkout, crypto payments, and platform services for marketplaces.
- [Build a custom checkout page that includes Link | Stripe Documentation](https://docs.stripe.com/payments/link/add-link-elements-integration): This guide explains how to integrate Stripe's Link feature into a custom checkout page using the Payment Element or Link Authentication Element. It details methods for securing a customer's email address for Link authentication and enrollment, recommending specific approaches based on existing checkout flows.
- [Link in the Card Element | Stripe Documentation](https://docs.stripe.com/payments/link/card-element-link): Stripe no longer recommends using the Card Element for Link integration, advising the use of Link Authentication, Express Checkout, or Payment Elements instead. Link in the Card Element previously allowed saving and autofilling payment information, displaying a Link button for authenticated customers to expedite checkout.
- [Link with Checkout | Stripe Documentation](https://docs.stripe.com/payments/link/checkout-link): Link can be used with Stripe's prebuilt Checkout page to allow customers to securely save and reuse payment information for faster checkout. For logged-in Link users, their information is autofilled automatically. Integrating Link with Checkout requires no additional fees and uses the same pricing as other card payments.
- [Link with Web Elements | Stripe Documentation](https://docs.stripe.com/payments/link/elements-link): Link can be embedded into custom payment pages using Stripe's Web Elements for a one-click checkout experience. Customers new to Link can save their payment and shipping details for future use. Recommended integrations include the Payment Element, Express Checkout Element, and Link Authentication Element.
- [Explore the Link Authentication Element | Stripe Documentation](https://docs.stripe.com/payments/link/link-authentication-element): The Link Authentication Element creates a single email input field for both collecting email addresses and authenticating Link customers within an Elements integration. If a customer doesn't have a Link account, they can sign up, and if they do, they are authenticated via a one-time password to autofill payment details.
- [Link in the Express Checkout Element | Stripe Documentation](https://docs.stripe.com/payments/link/express-checkout-element-link): The Express Checkout Element allows customers to pay faster with Link and other one-click payment methods like Apple Pay and Google Pay. This integration supports dynamic sorting of payment buttons and seamless reuse of existing Elements instances. Link is automatically added to the Express Checkout Element when enabled in payment settings.
- [Increase conversion and reduce costs with Link | Stripe Documentation](https://docs.stripe.com/payments/link): Link is Stripe's digital wallet that enables customers to save and reuse payment methods for faster checkout, increasing conversion rates and potentially reducing costs. It supports various payment methods, including lower-cost alternatives like Instant Bank Payments. Link transactions confirm immediately and settle similarly to card payments.
- [Instant Bank Payments | Stripe Documentation](https://docs.stripe.com/payments/link/instant-bank-payments): Instant Bank Payments, available through Link in the US, offer low-cost bank payments with instant confirmation and faster settlement. This feature provides protection from common ACH failures and accelerates checkout. Instant Bank Payments are automatically enabled when Link is turned on, subject to eligibility.
- [Link in different payment integrations | Stripe Documentation](https://docs.stripe.com/payments/link/link-payment-integrations): To use Link, it must be enabled in payment method settings and integrated either as a primary payment method or within a card-specific integration. Link transactions are identified by a PaymentMethod object with the type 'link' and support various funding methods including credit cards, bank payments, and Klarna. All Link transactions confirm immediately.
- [Link with Invoicing | Stripe Documentation](https://docs.stripe.com/payments/link/invoicing): Link can be used with Stripe's Hosted Invoice Page to speed up invoice payments, providing customers with a unique, secure URL to pay without extra implementation. Link is compatible with both Invoices and Subscriptions APIs, allowing customers to autofill payment details for faster invoice settlement. Enabling Link in the Hosted Invoice Page is done through the Dashboard settings.
- [Klarna on Link | Stripe Documentation](https://docs.stripe.com/payments/link/klarna): Link customers in the US can use Klarna's buy now, pay later option through Link. Klarna is automatically enabled when Link is active and supported on Checkout, Payment Links, and the Payment Element. Users can test Klarna on Link in a sandbox environment using specific test card numbers.
- [Link in the Mobile Payment Element | Stripe Documentation](https://docs.stripe.com/payments/link/mobile-payment-element-link): Link can be added to native iOS, Android, and React Native apps using the Mobile Payment Element for faster checkout. It autofills payment information for existing Link users. To enable Link in mobile apps, integrate the Mobile Payment Element, enable Link in payment settings, and use dynamic payment methods.
- [Link in the Payment Element | Stripe Documentation](https://docs.stripe.com/payments/link/payment-element-link): The Link in the Payment Element allows customers to check out faster by autofilling their information if they are logged into Link. This integration option is recommended by Stripe when a customer's email address is available. You can manage Link within the Payment Element through your payment method settings.
- [Link in the Payment Request Button | Stripe Documentation](https://docs.stripe.com/payments/link/payment-request-button-link): Link in the Payment Request Button enables faster checkouts for customers using their saved payment details without manual entry. Stripe no longer recommends using the Payment Request Button for new integrations, suggesting the Link Authentication Element, Express Checkout Element, or Payment Element instead. Link is compatible with other card payment features like subscriptions at no additional cost.
- [Set up future payments using Elements and Link | Stripe Documentation](https://docs.stripe.com/payments/link/save-and-reuse): This guide explains how to set up future payments using Stripe Elements and Link, focusing on the Setup Intents API. It outlines three methods for securing a customer's email address for Link authentication or enrollment: passing it directly, collecting it within the Payment Element, or using the Link Authentication Element. These methods help streamline the process for recurring payments and saved payment details.
- [Machine payments | Stripe Documentation](https://docs.stripe.com/payments/machine): Machine payments enable programmatic payments for resources like API calls or data, allowing agents to pay via crypto directly into a Stripe balance. This feature supports pay-per-use business models for sellers and allows agents to pay on demand without needing API keys, only a crypto wallet. Payments land in the Stripe balance, settle in fiat, and support microtransactions as low as 0.01 USDC.
- [x402 quickstart | Stripe Documentation](https://docs.stripe.com/payments/machine/quickstart): This page serves as a quickstart guide for implementing machine payments using Stripe. It is a part of the broader documentation on enabling machine-to-machine payments, likely detailing the initial steps and setup required.
- [x402 payments | Stripe Documentation](https://docs.stripe.com/payments/machine/x402): x402 payments enable machine-to-machine transactions using an HTTP 402 response protocol, where servers indicate payment is required for resources. Stripe facilitates crypto payments, handling deposit addresses and capturing PaymentIntents upon on-chain settlement. This requires a Stripe account with crypto payins and machine payments enabled, and involves creating an endpoint with payment middleware.
- [Accept in-app payments | Stripe Documentation](https://docs.stripe.com/payments/mobile/accept-payment-embedded): This page details how to accept in-app payments using the customizable Payment Element within iOS, Android, or React Native applications. The Payment Element allows for a unified integration of multiple payment methods, collecting details via bottom sheets. The process involves setting up a server-side integration with the Stripe API and a client-side implementation within the app.
- [Accept in-app payments | Stripe Documentation](https://docs.stripe.com/payments/mobile/accept-payment-embedded?platform=ios): This page explains how to accept in-app payments on iOS using the customizable Payment Element. The Payment Element renders a list of payment methods and collects details through bottom sheets, allowing for a streamlined payment experience. It outlines the server-side and client-side integration steps required for iOS applications.
- [Accept in-app payments | Stripe Documentation](https://docs.stripe.com/payments/mobile/accept-payment-embedded?platform=android): This page guides developers on accepting in-app payments on Android using the Payment Element. It highlights the Payment Element's ability to handle multiple payment methods within a single integration, collecting payment details via bottom sheets. The documentation covers both server-side and client-side setup for Android applications.
- [Accept in-app payments | Stripe Documentation](https://docs.stripe.com/payments/mobile/accept-payment-embedded?platform=react-native): This page provides instructions for accepting in-app payments in React Native applications using the Payment Element. It emphasizes the component's flexibility in handling various payment methods and collecting details through bottom sheets. The guide covers the necessary server-side and client-side configurations for React Native integrations.
- [Accept in-app payments | Stripe Documentation](https://docs.stripe.com/payments/mobile/accept-payment): This page explains how to accept in-app payments using the Payment Sheet in iOS, Android, or React Native apps. The Payment Sheet is a customizable component that displays available payment methods and collects details via a bottom sheet. It supports saving payment details for future purchases and integrates with Stripe's customer management.
- [Accept in-app payments | Stripe Documentation](https://docs.stripe.com/payments/mobile/accept-payment?platform=ios): This page details how to accept in-app payments on iOS using the Payment Sheet. The Payment Sheet is a customizable UI component that presents various payment methods and collects customer details through a bottom sheet. It allows for saving payment methods on the device for future use, integrating with server-side and client-side Stripe APIs.
- [Accept in-app payments | Stripe Documentation](https://docs.stripe.com/payments/mobile/accept-payment?platform=android): This page explains how to accept in-app payments on Android using the Payment Sheet. The Payment Sheet component displays multiple payment methods and collects necessary details within a bottom sheet interface. It covers the integration flow, including server-side setup with Stripe APIs and client-side implementation for Android apps.
- [Accept in-app payments | Stripe Documentation](https://docs.stripe.com/payments/mobile/accept-payment?platform=react-native): This page outlines how to accept in-app payments in React Native applications using the Payment Sheet. The Payment Sheet component provides a customizable interface for displaying and collecting payment information via a bottom sheet. It details the server-side and client-side integration steps required for React Native development.
- [Add custom payment methods | Stripe Documentation](https://docs.stripe.com/payments/mobile/custom-payment-methods): This guide explains how to add custom payment methods to the Mobile Payment Element, allowing for the display of methods not processed by Stripe. These custom methods can be configured in the Stripe Dashboard and recorded for reporting purposes, even though transactions finalize outside of Stripe. This requires additional configuration work for the integration.
- [Add external payment methods | Stripe Documentation](https://docs.stripe.com/payments/mobile/external-payment-methods): This page discusses adding external payment methods to the Mobile Payment Element, recommending the custom payment methods feature instead. External payment methods are handled by the app rather than Stripe, requiring the developer to manage the transaction process and compliance. The guide provides an example of adding Fawry as an external payment method using the Payment Sheet.
- [Migrate from the Basic Integration to the Payment Sheet | Stripe Documentation](https://docs.stripe.com/payments/mobile/migrating-to-mobile-payment-element-from-basic-integration): This document details the migration from Stripe's legacy Basic Integration to the Payment Sheet for mobile SDKs (iOS, Android, React Native) by November 4, 2024. Upgrading to the Payment Sheet provides access to over 100 payment methods, including Link, and allows for customization and saving of payment methods. The guide offers specific integration paths for checkout pages and wallet use cases.
- [Collect physical addresses and phone numbers | Stripe Documentation](https://docs.stripe.com/payments/mobile/collect-addresses): This page explains how to collect customer addresses and phone numbers in mobile apps using the Address Element. The Address Element can also be used to enable address autocomplete and prefill billing information in the Payment Element. Stripe combines the collected address and payment method details to create a PaymentIntent.
- [Provide subscription management on iOS with a customer portal page | Stripe Documentation](https://docs.stripe.com/mobile/digital-goods/customer-portal): This guide explains how to provide subscription management for iOS apps by setting up a customer portal page. Customers can manage their subscriptions and payment methods by being redirected to this external page from the app. The process involves configuring the portal, using universal links for redirection, and monitoring webhooks for status updates.
- [Customize appearance | Stripe Documentation](https://docs.stripe.com/elements/appearance-api/mobile): This page describes how to customize the appearance of mobile payment integrations using the Appearance API. Developers can modify colors, fonts, corner radius, and other visual elements of the Payment Sheet and Payment Element to match their app's design. Code examples are provided for iOS to demonstrate customization of these visual properties.
- [Finalize payments on the server | Stripe Documentation](https://docs.stripe.com/payments/mobile/finalize-payments-on-the-server): This page explains how to finalize payments on the server by confirming a PaymentIntent or SetupIntent after rendering the Mobile Payment Element. It requires server-side endpoints to interact with the Stripe API using official libraries.
- [Display BNPL Messaging | Stripe Documentation](https://docs.stripe.com/payments/mobile/display-bnpl-messaging): This guide details how to use the Payment Method Messaging Element to display promotional messages for buy now, pay later payment options within your app. It covers SDK installation and configuration for iOS.
- [Add custom payment methods | Stripe Documentation](https://docs.stripe.com/payments/mobile/embedded-custom-payment-methods): This document describes how to add custom payment methods to the Payment Element for in-app integrations. It allows displaying payment methods not processed by Stripe and optionally recording these transactions for reporting in your Stripe account.
- [Customize appearance | Stripe Documentation](https://docs.stripe.com/elements/appearance-api/embedded-mobile): This page explains how to customize the appearance of the Payment Element in your in-app integration using the Appearance API. You can modify fonts, colors, shapes, and specific components to match your app's design.
- [Filter card brands | Stripe Documentation](https://docs.stripe.com/payments/mobile/embedded-filter-card-brands): This guide explains how to filter accepted card brands within your Stripe In-app Payments integration for iOS, Android, and React Native. You can specify allowed or disallowed card brands for both the credit card form and Apple Pay.
- [Filter card brands | Stripe Documentation](https://docs.stripe.com/payments/mobile/filter-card-brands): This page details how to filter card brands accepted by your Stripe In-app Payments integration. You can configure the system to either allow only specific card brands or disallow certain brands for payments made through the Payment Sheet.
- [Accept in-app purchases on iOS and Android | Stripe Documentation](https://docs.stripe.com/mobile/digital-goods): This page outlines how to accept in-app purchases for digital goods or subscriptions on iOS and Android using Stripe. It provides options for redirecting to Stripe Checkout or using in-app payment flows for direct processing.
- [Build an in-app payments integration | Stripe Documentation](https://docs.stripe.com/payments/mobile): This overview introduces Stripe's In-app Payments, enabling customized payment integrations and checkout flows for iOS, Android, and React Native apps. It offers three UI integration options: Payment Sheet, Flow Controller, and Payment Element, each with varying levels of code and flexibility.
- [Migrate your basic card integration | Stripe Documentation](https://docs.stripe.com/payments/mobile/upgrade-to-handle-actions): This guide helps migrate your mobile app's basic card integration to handle bank authentication requests. It involves updating server and client code to prompt users for authentication when required, preventing payment declines.
- [Migrate to Confirmation Tokens | Stripe Documentation](https://docs.stripe.com/payments/mobile/migration-confirmation-tokens): This guide explains how to migrate your mobile integration from using PaymentMethod to ConfirmationToken for handling payments. ConfirmationTokens simplify server-side code and automatically include payment context like shipping and mandate data.
- [Address Element | Stripe Documentation](https://docs.stripe.com/payments/mobile/address-element): The Address Element is an embeddable UI component for collecting complete billing and shipping addresses in in-app integrations. It supports global address formats, offers autocomplete, and can be customized to match your app's design.
- [Payment Method Messaging Element | Stripe Documentation](https://docs.stripe.com/payments/mobile/payment-method-messaging-element): The Payment Method Messaging Element is a customizable UI component that informs customers about available buy now, pay later plans. It automatically determines and displays localized descriptions of these payment options within your app.
- [Payment Element | Stripe Documentation](https://docs.stripe.com/payments/mobile/embedded): The Payment Element is a customizable, embeddable component that displays a list of payment methods directly within your app. It supports over 100 global payment methods and allows UI customizations to match your app's design.
- [Payment Sheet | Stripe Documentation](https://docs.stripe.com/payments/mobile/payment-sheet): The Payment Sheet is a prebuilt UI that presents payment methods in a sheet and is Stripe's recommended integration for most apps. It offers access to over 100 global payment methods and allows UI customizations to match your app's look and feel.
- [Save payment details during an in-app payment | Stripe Documentation](https://docs.stripe.com/payments/mobile/save-during-payment): This page describes how to save payment details from a purchase during an in-app payment using the Payment Intents API. This is useful for future purchases, recurring payments, or charging deposits later.
- [Save payment details during an in-app payment | Stripe Documentation](https://docs.stripe.com/payments/mobile/save-during-payment?platform=platform=ios&mobile-ui=payment-element): This page explains how to save payment details during an in-app payment on iOS using the Payment Intents API. This functionality is useful for storing details for future purchases or recurring payments.
- [Save payment details during an in-app payment | Stripe Documentation](https://docs.stripe.com/payments/mobile/save-during-payment?platform=platform=android&mobile-ui=payment-element): This page explains how to save payment details during an in-app payment on Android using the Payment Intents API. This functionality is useful for storing details for future purchases or recurring payments.
- [Save payment details during an in-app payment | Stripe Documentation](https://docs.stripe.com/payments/mobile/save-during-payment?platform=platform=react-native&mobile-ui=payment-element): This page explains how to save payment details during an in-app payment in React Native applications using the Payment Intents API. This allows for storing details for future purchases or recurring payments.
- [Save a card without bank authentication | Stripe Documentation](https://docs.stripe.com/payments/mobile/save-card-without-authentication): This guide explains how to collect card details in your mobile app and charge customers later without requiring immediate bank authentication, primarily for US and Canadian markets. It warns that this method is non-compliant in regions requiring authentication.
- [Set up future payments | Stripe Documentation](https://docs.stripe.com/payments/mobile/set-up-future-payments): This page details how to use the Setup Intents API to save a customer's payment details in your mobile app without an initial payment. This is useful for onboarding customers and charging them later, especially for recurring payments or when the final amount is determined after service delivery.
- [Card payments without bank authentication | Stripe Documentation](https://docs.stripe.com/payments/mobile/without-card-authentication): This page details how to implement card payments in mobile applications without requiring bank authentication, specifically for businesses accepting only US and Canadian cards. It offers a simpler integration but does not support global customer bases or additional payment methods.
- [Charge for shipping | Stripe Documentation](https://docs.stripe.com/payments/no-code/charge-shipping): This page explains how to charge customers for shipping using Stripe's Payment Links. It allows for the creation of different shipping rates and options, which can be configured directly in the Stripe Dashboard or via API for more complex integrations.
- [The Off-Session Payments API | Stripe Documentation](https://docs.stripe.com/payments/off-session-payments): The Off-Session Payments API enables the creation of custom payment flows for recurring and unscheduled payments. It offers features like smart retries for failed payments and the ability to process payments across multiple processors, all managed through a single API request.
- [Older payment APIs | Stripe Documentation](https://docs.stripe.com/payments/older-apis): This documentation provides information on Stripe's older payment APIs, noting that they are no longer actively updated and may have limitations. It strongly recommends migrating to current APIs like Payment Intents and Payment Methods for access to the latest features and ongoing support.
- [Supported Orchestration features | Stripe Documentation](https://docs.stripe.com/payments/orchestration/feature-support): This page outlines the features supported by Stripe's Orchestration for routing payments across multiple processors. It details error protection mechanisms and lists specific supported features like automatic confirmation, capture, refunds, and wallet payments for providers such as Adyen, Braintree, and Worldpay.
- [Orchestration | Stripe Documentation](https://docs.stripe.com/payments/orchestration): Stripe Orchestration is a private preview feature that allows businesses to route payments to multiple payment processors and manage rules for this routing. It supports features like retrying failed payments on alternative processors and monitoring overall payment performance across different providers.
- [Cross-processor retries with Orchestration | Stripe Documentation](https://docs.stripe.com/payments/orchestration/retries): This page describes how to configure cross-processor retries with Stripe Orchestration to automatically reattempt failed payments using a different processor. This feature helps recover revenue by increasing the likelihood of successful payment processing when the initial attempt fails due to various reasons.
- [Route payments to multiple processors | Stripe Documentation](https://docs.stripe.com/payments/orchestration/route-payments): Stripe Orchestration enables businesses to route payments to multiple processors based on custom rules defined in the Dashboard. It supports routing based on conditions like card country, currency, or amount, and includes functionality for setting up retry actions on alternative processors.
- [Manage rules | Stripe Documentation](https://docs.stripe.com/payments/orchestration/rules): This page explains how to manage rules within Stripe Orchestration for routing payments across different processors. Rules are based on payment conditions such as amount, BIN, card country, issuer, type, and currency, with defined actions to determine where the payment is processed.
- [Wallet payments with Orchestration | Stripe Documentation](https://docs.stripe.com/payments/orchestration/wallet-payments): Orchestration supports wallet payments like Apple Pay and Google Pay, allowing businesses to route these transactions to different processors. The setup involves enabling wallet payments on the third-party processor and configuring Stripe, with options to test routing in a sandbox environment.
- [Asynchronous capture | Stripe Documentation](https://docs.stripe.com/payments/payment-intents/asynchronous-capture): Asynchronous Capture is a feature that speeds up PaymentIntent confirmations by performing the capture operation in the background. After the capture request is made, the integration receives an immediate success response, while Stripe handles the actual payment capture on the backend.
- [The Checkout Sessions API | Stripe Documentation](https://docs.stripe.com/payments/checkout-sessions): The Checkout Sessions API is recommended by Stripe for most payment integrations as it provides built-in support for complex checkout tasks. It manages the entire checkout lifecycle, offering features like tax calculation, discounts, subscriptions, shipping, and currency conversion through various UI options.
- [The Payment Intents API | Stripe Documentation](https://docs.stripe.com/payments/payment-intents): The Payment Intents API is used to build integrations that handle complex payment flows, tracking a payment from creation through authentication and completion. It offers advantages such as automatic authentication handling, no double charges, and support for Strong Customer Authentication (SCA).
- [How PaymentIntents and SetupIntents work | Stripe Documentation](https://docs.stripe.com/payments/paymentintents/lifecycle): This page explains the lifecycle of PaymentIntents and SetupIntents, highlighting their core differences. Payment Intents are used to collect payment and charge a customer immediately, while Setup Intents are used to save payment method details for future use without an immediate charge.
- [Migrate to the Payment Intents API | Stripe Documentation](https://docs.stripe.com/payments/payment-intents/migration): This guide details how to migrate existing Stripe integrations from the Charges API to the Payment Intents API. It suggests an incremental approach, starting with updating API versions and client libraries, then migrating code that reads Charge properties, and finally migrating card-saving functionalities.
- [Mail order telephone order (MOTO) | Stripe Documentation](https://docs.stripe.com/payments/payment-intents/moto): This page explains how to handle Mail Order Telephone Order (MOTO) payments, which are out-of-scope for Strong Customer Authentication (SCA) regulations. Integrations must correctly flag these transactions as MOTO, with the cardholder's bank making the final decision on acceptance or rejection.
- [Charges versus Payment Intents APIs | Stripe Documentation](https://docs.stripe.com/payments/payment-intents/migration/charges): This comparison clarifies the differences between Stripe's Charges API and Payment Intents API. The Payment Intents API is the unifying API for all Stripe products and payment methods, supporting SCA and new features, while the Charges API is primarily for US/Canadian card acceptance.
- [Payment status updates | Stripe Documentation](https://docs.stripe.com/payments/payment-intents/verifying-status): This page describes how to monitor and verify the status of a PaymentIntent to respond to successful or failed payments. Integrations can inspect the PaymentIntent's status on the client-side or use the Stripe Dashboard to receive email notifications about payment events.
- [Create an embeddable buy button | Stripe Documentation](https://docs.stripe.com/payment-links/buy-button): This page explains how to create an embeddable buy button using Stripe Payment Links. Businesses can select an existing link or create a new one, then customize the button's design, branding, and call to action to match their website before embedding it.
- [Create a payment link | Stripe Documentation](https://docs.stripe.com/payment-links/create): This guide details how to create a payment link using the Stripe Dashboard without requiring code. These links redirect customers to a Stripe-hosted payment page and can be used to sell products, subscriptions, or collect tips and donations, supporting various languages and payment methods.
- [Customize checkout for Payment Links | Stripe Documentation](https://docs.stripe.com/payment-links/customize): Stripe Payment Links allow customization of the checkout experience, including branding, collecting additional customer information, and setting limits on how many times a link can be paid. You can also configure options like shipping charges, promotion codes, and upsells to enhance the checkout process.
- [Accept payments online without writing code | Stripe Documentation](https://docs.stripe.com/payment-links): Stripe Payment Links enable users to accept payments online without writing code by creating shareable links. These links can be customized with branding, and support various payment methods, local languages, and currencies, facilitating easy online transactions via social media, email, or websites.
- [After a payment link payment | Stripe Documentation](https://docs.stripe.com/payment-links/post-payment): After a payment link transaction, Stripe provides tools to track payments in the Dashboard or via API, and offers options for automatic fulfillment through partners or programmatically. You can also view payment link metrics and manage customer data, including creating guest customers or Customer objects for recurring payments.
- [Promotion codes, upsells, and optional items | Stripe Documentation](https://docs.stripe.com/payment-links/promotions): Stripe Payment Links allow businesses to offer discounts and upsells during checkout using promotion codes and subscription upgrades. Customers can apply promotion codes on the payment page, and businesses can enable subscription upsells for longer-term plans, helping to increase revenue.
- [Share a payment link | Stripe Documentation](https://docs.stripe.com/payment-links/share): Once a Stripe payment link is created, it can be easily shared with customers through various channels like email, text messages, or social media. You can also generate a QR code for the link or embed it as a buy button on your website to facilitate payments without a digital storefront.
- [Track a payment link | Stripe Documentation](https://docs.stripe.com/payment-links/url-parameters): Stripe Payment Links can be tracked using URL parameters and UTM codes to gain insights into customer behavior and marketing campaign effectiveness. By adding parameters like utm_source, utm_medium, and utm_campaign, you can identify traffic sources and optimize marketing strategies for better conversion rates.
- [Payment method configurations | Stripe Documentation](https://docs.stripe.com/payments/payment-method-configurations): Payment method configurations in Stripe allow businesses to dynamically display different sets of payment methods to customers based on specific checkout scenarios. This enables tailoring payment options for particular products, checkout flows (one-time vs. subscription), or connected accounts, optimizing for conversion without requiring code changes.
- [Payment method rules | Stripe Documentation](https://docs.stripe.com/payments/payment-method-rules): Stripe's payment method rules enable businesses to control the availability of payment methods directly from the Dashboard based on specific conditions. Rules can be set for order amounts, buyer countries, or currencies, offering flexibility and potentially improving unit economics and average order value without custom coding.
- [Accept a Canadian pre-authorized debit payment | Stripe Documentation](https://docs.stripe.com/payments/acss-debit/accept-a-payment): Canadian pre-authorized debit (PAD) payments can be accepted through Stripe using either a custom payment form or Stripe Checkout. This process involves creating a payment object, collecting mandate acknowledgement, and submitting the payment for processing, with funds typically taking 5 business days to become available.
- [Custom Canadian pre-authorized debit mandate agreements | Stripe Documentation](https://docs.stripe.com/payments/acss-debit/custom-pad-agreement): Custom Canadian pre-authorized debit mandate agreements are rarely needed, as Stripe.js provides a default solution for collecting and verifying bank account information and mandates. Custom agreements are only necessary for specific scenarios, such as waiving debit notification emails or providing alternative cancellation terms that comply with Payments Canada rules.
- [Pre-authorized debit payments in Canada | Stripe Documentation](https://docs.stripe.com/payments/acss-debit): Stripe enables businesses in Canada and the United States to accept pre-authorized debit payments (PADs) from customers with Canadian bank accounts via the ACSS system. A mandate defining payment terms must be collected before debiting, and Stripe.js can facilitate the collection of bank details and verification, reducing payment failures.
- [Save details for future payments with pre-authorized debit in Canada | Stripe Documentation](https://docs.stripe.com/payments/acss-debit/set-up-payment): Stripe allows saving payment method details for future Canadian pre-authorized debit payments using the Setup Intents API. This is useful for streamlining future purchases, collecting surcharges, or starting free trials, though it's important to select the correct currency (CAD or USD) to avoid payment failures.
- [Accept an Affirm payment | Stripe Documentation](https://docs.stripe.com/payments/affirm/accept-a-payment): Affirm is a buy now, pay later payment method available through Stripe for US and Canadian customers, allowing them to split purchases into installments. Customers authenticate on Affirm's site, and upon acceptance, the full payment is guaranteed to the merchant upfront, with Affirm collecting repayments directly from the customer.
- [Affirm payments | Stripe Documentation](https://docs.stripe.com/payments/affirm): Affirm offers US and Canadian customers flexible financing options, allowing purchases to be paid over time with interest-free or monthly installments. Merchants receive the full payment upfront (minus fees), while Affirm manages the repayment from the customer, supporting various currencies and offering dispute resolution.
- [Display Affirm messaging | Stripe Documentation](https://docs.stripe.com/payments/affirm/site-messaging): This documentation page is deprecated and recommends using the Payment Method Messaging Element instead of the legacy Affirm messaging Element. The Messaging Element dynamically displays buy now, pay later options, calculates installments, and shows information modals to increase conversion by informing customers about Affirm availability.
- [Accept an Afterpay or Clearpay payment | Stripe Documentation](https://docs.stripe.com/payments/afterpay-clearpay/accept-a-payment): Afterpay (Clearpay in the UK) is a payment method integrated with Stripe for US, CA, UK, AU, and NZ customers, enabling installment payments. Customers authenticate on Afterpay's site, and upon successful authorization, the funds are guaranteed to the merchant upfront, with Afterpay handling customer repayments.
- [Afterpay and Clearpay payments | Stripe Documentation](https://docs.stripe.com/payments/afterpay-clearpay): Afterpay (Clearpay) offers customers flexible financing by splitting purchases into interest-free or monthly installments, with merchants receiving full payment upfront. The service is available in multiple regions, and while Afterpay handles customer repayments, Stripe provides dispute support and allows for refunds.
- [Display Afterpay or Clearpay messaging | Stripe Documentation](https://docs.stripe.com/payments/afterpay-clearpay/site-messaging): This documentation page is deprecated and recommends using the Payment Method Messaging Element instead of the legacy Afterpay/Clearpay messaging Element. The Messaging Element dynamically displays relevant buy now, pay later options, calculates installment amounts, and localizes information to inform customers about Afterpay and Clearpay availability.
- [Accept an Alipay payment | Stripe Documentation](https://docs.stripe.com/payments/alipay/accept-a-payment): Alipay is a popular digital wallet payment method, primarily used by customers from China, that can be integrated with Stripe. Payments are authenticated by the customer on Alipay's platform, providing immediate success or failure notifications to the merchant and offering a low dispute rate due to its authentication process.
- [Alipay payments | Stripe Documentation](https://docs.stripe.com/payments/alipay): Alipay, a widely used digital wallet in China, allows for web and mobile payments with strong fraud reduction through credential authentication. Stripe supports Alipay for businesses in various locations, with specific currency and business category restrictions, offering standard payout timing and dispute handling.
- [Accept a payment with Alma | Stripe Documentation](https://docs.stripe.com/payments/alma/accept-a-payment): This page explains how to integrate Alma, a buy-now-pay-later service, into your Stripe Checkout integration. It outlines the conditions for using Alma, such as currency consistency across line items, and guides users through the setup process for accepting installment payments.
- [Alma payments | Stripe Documentation](https://docs.stripe.com/payments/alma): Alma is a buy-now-pay-later payment method available in several European countries, allowing customers to pay in 2, 3, or 4 installments. Stripe facilitates these payments, offering instant payouts to businesses and handling the redirection and authorization process with Alma.
- [Accept a payment with Amazon Pay | Stripe Documentation](https://docs.stripe.com/payments/amazon-pay/accept-a-payment): This guide details how to accept Amazon Pay as a payment method within your Stripe integration. It covers the compatibility requirements for using Amazon Pay with Stripe Checkout, emphasizing currency consistency for all line items.
- [Amazon Pay payments | Stripe Documentation](https://docs.stripe.com/payments/amazon-pay): Amazon Pay is a wallet payment method that allows customers to use their existing Amazon account information for a streamlined checkout experience. Stripe integrates with Amazon Pay, enabling businesses to accept payments globally in various currencies.
- [Set up a subscription with Amazon Pay | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/amazon-pay): This guide explains how to set up recurring subscription payments using Amazon Pay as the payment method within Stripe Billing. It details the process using API calls to set Amazon Pay as a payment method and then create a subscription.
- [Set up a subscription with Amazon Pay | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/amazon-pay?api-integration=setupintents): This guide outlines how to set up subscriptions with Amazon Pay using the Setup Intents API. It involves creating a product and price in Stripe, then using API calls to establish Amazon Pay as a payment method for recurring charges.
- [Set up a subscription with Amazon Pay | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/amazon-pay?api-integration=api): This guide explains how to set up subscriptions with Amazon Pay using direct API integration. It involves using the Setup Intents API to register Amazon Pay as a payment method and then creating a subscription with customer and payment details.
- [Set up a subscription with Amazon Pay | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/amazon-pay?api-integration=checkout): This guide details how to set up subscriptions with Amazon Pay using Stripe's prebuilt Checkout page. It explains how to create a product and price in Stripe, then leverage the Checkout API to manage the subscription creation and payment process.
- [Set up future Amazon Pay payments | Stripe Documentation](https://docs.stripe.com/payments/amazon-pay/set-up-future-payments): This page describes how to save Amazon Pay payment details for future use, enabling recurring payments or subscriptions. It focuses on using Stripe Checkout to obtain customer consent and store payment information securely.
- [Accept an Australia BECS Direct Debit payment | Stripe Documentation](https://docs.stripe.com/payments/au-becs-debit/accept-a-payment): This document provides instructions on how to accept Australia BECS Direct Debit payments through Stripe Checkout. It outlines the conditions for compatibility, such as all line items being in the same currency, and guides users through the integration process.
- [Australia BECS Direct Debit payments | Stripe Documentation](https://docs.stripe.com/payments/au-becs-debit): Australia BECS Direct Debit is a payment method for customers with Australian bank accounts, allowing businesses to debit accounts after collecting a mandate. Payments are reusable but have a delayed notification of success or failure, typically taking up to three business days.
- [Save Australia BECS Direct Debit details for future payments | Stripe Documentation](https://docs.stripe.com/payments/au-becs-debit/set-up-payment): This guide explains how to use the Setup Intents API to save Australia BECS Direct Debit payment details for future transactions. It allows for collecting bank details securely via Stripe Elements and determining payment amounts or dates later, streamlining future purchases or subscriptions.
- [Bacs Direct Debit payments | Stripe Documentation](https://docs.stripe.com/payments/bacs-debit/accept-a-payment): This page details how to accept Bacs Direct Debit payments from customers with UK bank accounts using Stripe Checkout. It covers the necessary server-side setup and the process of creating a Checkout Session for payment collection.
- [Bacs Direct Debit email notification requirements | Stripe Documentation](https://docs.stripe.com/payments/bacs-debit/email-customization): Bacs Direct Debit requires businesses to send specific email notifications to customers regarding payment collection. These include confirmation of signup and advanced notice emails, with specific content requirements and an approval process for custom designs.
- [Bacs Direct Debit payments in the UK | Stripe Documentation](https://docs.stripe.com/payments/payment-methods/bacs-debit): Bacs Direct Debit is a payment method for UK bank accounts, requiring businesses to collect a mandate that includes customer details and authorization to debit. Payments are reusable with delayed confirmation, and have transaction limits, with longer confirmation times when a new mandate is needed.
- [Requirements for online Bacs Direct Debit mandate collection | Stripe Documentation](https://docs.stripe.com/payments/bacs-debit/mandate-collection-requirements): This document outlines the requirements for hosting your own Bacs Direct Debit mandate collection forms. It details the essential information to collect from payers, such as bank account details and explicit agreement, and the information that must be displayed to them.
- [Export Bacs data from Stripe | Stripe Documentation](https://docs.stripe.com/payments/bacs-debit/export-data): This page explains how to export Bacs data from your Stripe account to another payment processor. The process involves submitting a data migration request through Stripe Support and typically takes 6-8 weeks to complete.
- [Save Bacs Direct Debit bank details | Stripe Documentation](https://docs.stripe.com/payments/bacs-debit/save-bank-details): This guide explains how to use Stripe Checkout to save Bacs Direct Debit payment details for future use. This functionality is useful for streamlining future purchases, collecting surcharges, or initiating subscription free trials.
- [Pay with Stripe balance | Stripe Documentation](https://docs.stripe.com/payments/pay-with-balance): This page describes how to use a connected account's Stripe balance to collect subscription payments directly. This feature, available in public preview for Accounts V2, bypasses external payment methods and is specifically for subscription charges initiated by the platform.
- [Accept a Bancontact payment | Stripe Documentation](https://docs.stripe.com/payments/bancontact/accept-a-payment): This guide explains how to accept Bancontact payments, a common method in Belgium, through Stripe Checkout. It outlines compatibility requirements, such as payments being in Euros, and the process of customer authentication via redirection.
- [Bancontact payments | Stripe Documentation](https://docs.stripe.com/payments/bancontact): Bancontact is a popular online payment method in Belgium that redirects customers to their bank's app or website for authorization. Payments are confirmed immediately upon return to your site, and it supports immediate payout timing.
- [Save bank details during a Bancontact payment | Stripe Documentation](https://docs.stripe.com/payments/bancontact/save-during-payment): This guide explains how to save a customer's IBAN details from a Bancontact payment to set up future SEPA Direct Debit payments. This reduces friction for customers by eliminating the need to re-enter their banking information.
- [Use Bancontact to set up future SEPA Direct Debit payments | Stripe Documentation](https://docs.stripe.com/payments/bancontact/set-up-payment): This feature allows you to save bank details from a Bancontact payment to later charge customers using SEPA Direct Debit. Stripe charges a small fee to collect and verify the IBAN, which is then refunded, enabling recurring payments or subscriptions.
- [Bank Debits | Stripe Documentation](https://docs.stripe.com/payments/bank-debits): Bank debits allow you to pull funds directly from a customer's bank account for one-time or recurring payments. This method is suitable for businesses collecting recurring payments or seeking a low-cost alternative to cards for large consumer payments, but it may not be ideal for immediate goods delivery due to confirmation delays.
- [Migrating to new ACH Direct Debit APIs | Stripe Documentation](https://docs.stripe.com/payments/ach-direct-debit/migrating-to-new-apis): Stripe is deprecating legacy ACH Direct Debit integrations and requires migration to the Payment Intents or Checkout Sessions APIs. The new APIs offer enhanced features like improved checkout support, dynamic payment methods, faster settlement, and instant bank account verification.
- [Migrate existing bank accounts | Stripe Documentation](https://docs.stripe.com/payments/ach-direct-debit/migrating-from-charges): This document outlines the process for migrating existing bank accounts from legacy ACH Direct Debit integrations to the Payment Intents or Checkout Sessions APIs. It details requirements for using saved bank accounts with the new APIs, including customer verification and active mandates.
- [Accept a bank transfer | Stripe Documentation](https://docs.stripe.com/payments/bank-transfers/accept-a-payment): This page explains how to accept bank transfer payments using the Payment Intents API. Stripe generates a virtual bank account for the customer upon their first transfer, which is then used for all subsequent payments, simplifying reconciliation and protecting your actual bank details.
- [Bank transfer payments | Stripe Documentation](https://docs.stripe.com/payments/bank-transfers): Bank transfers offer a secure method for customers to send money, with Stripe providing virtual bank account numbers to automate reconciliation and protect your financial information. While generally standard payout timing applies, recurring payments require customer action to ensure sufficient funds.
- [Refund bank transfer payments | Stripe Documentation](https://docs.stripe.com/payments/customer-balance/refunding): Refunds for customer balance payments, including those made via bank transfers, can be processed through the Dashboard or API. Stripe requires customer bank account details to process refunds and will contact the customer if this information is ambiguous or missing.
- [Customer balance | Stripe Documentation](https://docs.stripe.com/payments/customer-balance): A customer balance can hold cash or credit funds. Cash balances accumulate from overpayments or unreconciled bank transfers and can be used for future payments or refunded to the customer's bank account. These balances are not a digital wallet and only serve as a reconciliation layer.
- [Automatic migration to Bank Transfers | Stripe Documentation](https://docs.stripe.com/payments/customer-balance/ach-ct-automigration): Stripe is replacing the ACH Credit Transfers payment method with Bank Transfers, deprecating the Sources API. This migration occurs automatically for accounts processing ACH Credit Transfers through invoices or subscriptions, but may require integration adjustments, particularly for webhook endpoints.
- [Migrate to EUR bank transfers from a Direct Integration using the Sources or Charges API | Stripe Documentation](https://docs.stripe.com/payments/customer-balance/direct-sepa-ct-sources-migration): This guide details migrating a Sources API integration for SEPA Credit Transfers to EUR Bank Transfers. It emphasizes that the Sources API is deprecated and requires migration to the Payment Methods API for continued functionality.
- [Migrate to USD bank transfers from a Direct Integration using the Sources or Charges API | Stripe Documentation](https://docs.stripe.com/payments/customer-balance/direct-sources-migration): This guide explains how to migrate a Sources API integration for ACH Credit Transfers to USD Bank Transfers. It highlights the deprecation of the Sources API and the necessity of moving to the Payment Methods API for ongoing support.
- [Funding instructions | Stripe Documentation](https://docs.stripe.com/payments/customer-balance/funding-instructions): Funding instructions allow you to provide customers with bank account details for making payments before a PaymentIntent is created. This can be done via the Dashboard or API, enabling customers to initiate transfers to a designated virtual bank account, and Stripe can provide account ownership confirmation letters.
- [Migrate to USD bank transfers from ACH Credit Transfers with Invoicing or Billing | Stripe Documentation](https://docs.stripe.com/payments/customer-balance/invoicing-migration): This guide assists in migrating ACH Credit Transfers used with Invoicing or Billing to Stripe USD Bank Transfers. It notes the deprecation of the Sources API and the mandatory shift to the Payment Methods API for continued service.
- [Migrate to EUR bank transfers from SEPA Credit Transfers with Invoicing or Billing | Stripe Documentation](https://docs.stripe.com/payments/customer-balance/invoicing-sepa-ct-migration): This guide explains how to migrate SEPA Credit Transfers used with Invoicing or Billing to Stripe EUR Bank Transfers. It reiterates the deprecation of the Sources API and the requirement to transition to the Payment Methods API.
- [Migrate from Sources-based Credit Transfers | Stripe Documentation](https://docs.stripe.com/payments/customer-balance/migrating-from-sepa-credit-transfer): This document guides the migration of Sources-based SEPA Credit Transfer payment methods to EUR Bank Transfers. It warns that the Sources API is deprecated and requires migration to the Payment Methods API, and notes that new virtual bank account numbers (VBANs) will be issued post-migration.
- [Migrating from Sources-based Credit Transfers | Stripe Documentation](https://docs.stripe.com/payments/customer-balance/migrating-from-sources): This guide covers migrating Sources-based ACH Credit Transfer payment methods to USD Bank Transfers. It stresses the deprecation of the Sources API and the need to migrate to the Payment Methods API, highlighting improvements in the Bank Transfers method.
- [Reconciliation | Stripe Documentation](https://docs.stripe.com/payments/customer-balance/reconciliation): Stripe offers automatic or manual reconciliation for funds in a customer's cash balance, with automatic reconciliation being the default. Reconciliation behavior can be overridden for specific customers through the Dashboard or API, allowing for manual control over how funds are applied.
- [EUR Bank Transfers migration guide for Standard Connect accounts | Stripe Documentation](https://docs.stripe.com/payments/customer-balance/sepa-ct-connect-migration): This guide details migrating SEPA Credit Transfer Standard Connect integrations to EUR Bank Transfers. It warns that the Sources API is deprecated and requires migration to the Payment Methods API, and outlines the impact on connected accounts and their end customers.
- [Migrating your Standard Connect integration to USD Bank Transfers | Stripe Documentation](https://docs.stripe.com/payments/customer-balance/standard-connect-migration): This page guides users on migrating their Standard Connect integration from ACH Credit Transfers to USD Bank Transfers. It highlights the deprecation of the Sources API and the necessity of moving to the Payment Methods API for continued support. The migration offers benefits of updated bank transfer processes.
- [Virtual bank account numbers | Stripe Documentation](https://docs.stripe.com/payments/customer-balance/virtual-bank-account-numbers): Virtual Bank Account Numbers (VBANs) are used for reconciliation in Stripe bank transfers, allowing funds to be automatically allocated to a customer's cash balance. Once assigned, a VBAN is permanent and any subsequent funds sent to it are added to the customer's balance. Understanding VBANs and their best practices is crucial for accurate fund association with PaymentIntents or Invoices.
- [Credit transfers (Sources) | Stripe Documentation](https://docs.stripe.com/payments/sources/credit-transfers): Credit transfers, processed via the deprecated Sources API, allow customers to send money directly from their bank accounts. Stripe advises migrating to the Payment Methods API for bank transfer payments due to the deprecation of the Sources API. This method is suitable for large, one-off payments but may not be ideal for frequent low-value transactions or when precise timing is critical.
- [Mexico bank transfers | Stripe Documentation](https://docs.stripe.com/payments/bank-transfers/acerca-de-transferencias-bancarias): This page details Stripe's bank transfer payment method for Mexico, which uses Citibanamex and the SPEI network. It offers benefits like reduced declines, fraud, and chargebacks, with lower fees than credit cards. The product supports automatic reconciliation, partial/overpayments, and refunds, with payment confirmations typically provided within 30 minutes on business days.
- [Accept a payment with Billie | Stripe Documentation](https://docs.stripe.com/payments/billie/accept-a-payment): This guide explains how to accept payments using Billie, a 'Pay by Invoice' service offering payment terms from 7-120 days. To maximize approval rates, it's recommended to include line item data in your integration. Customers are redirected to Billie to authorize the payment and then return to your site, with immediate notification of success or failure.
- [Billie payments | Stripe Documentation](https://docs.stripe.com/payments/billie): Billie is a Buy Now, Pay Later payment method available in several European countries, allowing customers to pay in 30 days while businesses receive immediate payment. Stripe automatically presents Billie as a payment option if eligible, simplifying integration. The payment flow involves redirecting customers to Billie for authorization.
- [Accept a payment with Bizum | Stripe Documentation](https://docs.stripe.com/payments/bizum/accept-a-payment): This page describes how to accept payments with Bizum, a real-time payment system in Spain. Customers need a Spanish IBAN linked to their mobile number to use Bizum through their banking app. Stripe can automatically present Bizum as a payment option based on customer and transaction parameters.
- [Bizum payments | Stripe Documentation](https://docs.stripe.com/payments/bizum): Bizum is a real-time payment system in Spain where customers authenticate payments within their banking app using their registered phone number. It is available for single-use payments and requires customers to have a Spanish IBAN linked to their mobile number. Stripe can dynamically display Bizum as a payment option.
- [BLIK payments | Stripe Documentation](https://docs.stripe.com/payments/blik/accept-a-payment): This guide explains how to accept BLIK payments, a common method in Poland. Customers request a six-digit code from their banking app and enter it on the payment form, then authorize the payment via a push notification. The BLIK code is valid for 2 minutes, with a 60-second window for authorization.
- [BLIK payments | Stripe Documentation](https://docs.stripe.com/payments/blik): BLIK is a single-use payment method in Poland requiring customers to authenticate via a six-digit code generated in their banking app and a subsequent push notification. Payments are typically approved in under 10 seconds. Stripe supports BLIK for single-use payments and offers integration through Checkout or Elements.
- [Buy now, pay later | Stripe Documentation](https://docs.stripe.com/payments/buy-now-pay-later): Buy Now, Pay Later (BNPL) methods allow customers to pay in installments over time, while merchants receive full payment immediately. These methods are often used for high-value goods or to increase average cart size by offering payment flexibility. Stripe enables BNPL methods dynamically, displaying the most relevant options to customers based on eligibility.
- [Boleto payments | Stripe Documentation](https://docs.stripe.com/payments/boleto/accept-a-payment): This page details how to accept Boleto payments, a common method in Brazil. Boleto is a voucher-based payment that customers complete at ATMs, banks, or online portals before its expiration date. Payment confirmation is received after 1 business day, with funds available for payout 2 business days later.
- [Boleto payments | Stripe Documentation](https://docs.stripe.com/payments/boleto): Boleto is a regulated payment method in Brazil where customers pay using a voucher with a generated number at authorized locations or online portals. Payment confirmation typically occurs within 1 business day, and funds are available for payout 2 business days after confirmation. Boleto can be used for recurring payments and is supported by Stripe Connect.
- [Use Boleto with invoices | Stripe Documentation](https://docs.stripe.com/payments/boleto/set-up-invoices): This guide explains how to use Boleto as a payment method for invoices in Stripe. It covers enabling Boleto emails and choosing between sending an invoice or automatically charging the customer. Boleto is suitable when a customer hasn't defined a preferred payment method or when essential customer information for Boleto is missing.
- [Use Boleto with subscriptions | Stripe Documentation](https://docs.stripe.com/payments/boleto/set-up-subscription): This guide details setting up Boleto for subscriptions in Stripe. It involves enabling Boleto in payment method settings and configuring voucher expiration. Similar to invoices, businesses can choose to send an invoice or automatically charge the customer for subscription payments.
- [Cards | Stripe Documentation](https://docs.stripe.com/payments/cards): Cards are a fundamental payment method linked to bank accounts, enabled by default in Stripe for online payments. Customers enter card details at checkout, potentially undergoing additional security verification. Cards can also serve as the funding source for other Stripe products like Link and digital wallets.
- [Cartes Bancaires (CB) | Stripe Documentation](https://docs.stripe.com/payments/cartes-bancaires): Cartes Bancaires (CB) is France's primary card network, with most cards co-badged with Visa or Mastercard. Stripe allows processing over either network and automatically retries declined charges on alternative networks to improve acceptance rates. Businesses in the EEA must offer customers a choice of network at checkout for compliance.
- [Cash App Pay payments | Stripe Documentation](https://docs.stripe.com/payments/cash-app-pay/accept-a-payment): This page explains how to add Cash App Pay to your Stripe integration, a digital wallet payment method popular in the US. It supports single-use and recurring payments, funded by the customer's balance or linked card. Customers authenticate via redirect to the mobile app or by scanning a QR code on desktop.
- [Set up future Cash App Pay payments | Stripe Documentation](https://docs.stripe.com/payments/cash-app-pay/set-up-payment): This guide covers setting up future Cash App Pay payments by saving payment details, enabling recurring payments and subscriptions. Payment methods are attached to a Stripe Customer object for reuse. This process is facilitated through Stripe's Checkout hosted page.
- [Cash App Pay payments | Stripe Documentation](https://docs.stripe.com/payments/cash-app-pay): Cash App Pay is a digital wallet payment method popular with US customers, allowing single-use and recurring payments. Funds are drawn from the customer's stored balance or linked debit card. Authentication occurs either through a mobile app redirect or by scanning a QR code on a desktop.
- [Set up a subscription with Cash App Pay | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/cash-app-pay): This guide explains how to set up a subscription with Cash App Pay as a payment method. It involves using the Setup Intents API to establish Cash App Pay and then the Subscriptions API to create and confirm the subscription and payment.
- [Accept stablecoin payments | Stripe Documentation](https://docs.stripe.com/payments/accept-stablecoin-payments): This page details how to accept stablecoin payments by enabling the Crypto payment method in your Stripe account. Customers can pay using stablecoins like USDC, and the funds settle in your Stripe balance in USD.
- [Stablecoin payments | Stripe Documentation](https://docs.stripe.com/payments/stablecoin-payments): Stablecoin payments allow customers to pay using their preferred crypto wallet and network, with transactions settling in USD in your Stripe balance. The payment flow involves redirection to a crypto wallet for authentication and confirmation.
- [Deposit mode stablecoin payments | Stripe Documentation](https://docs.stripe.com/payments/deposit-mode-stablecoin-payments): Deposit mode stablecoin payments offer an API-only crypto payment flow where Stripe provides deposit addresses for specific networks. Once funds are sent to the address, Stripe automatically captures the PaymentIntent after on-chain settlement.
- [Custom payment methods | Stripe Documentation](https://docs.stripe.com/payments/payment-methods/custom-payment-methods): Custom payment methods enable extending payment and billing integrations with methods processed outside of Stripe, while still recording transaction details for unified reporting. You can configure these custom types in the Stripe Dashboard, including branding for each.
- [Dynamic payment methods | Stripe Documentation](https://docs.stripe.com/payments/payment-methods/dynamic-payment-methods): Dynamic payment methods simplify payment integration by allowing Stripe to automatically order and display the most relevant payment methods to customers based on various signals. This feature can be managed through the Dashboard without code changes, optimizing conversion rates.
- [eftpos Australia | Stripe Documentation](https://docs.stripe.com/payments/eftpos-australia): Eftpos Australia is a common debit card network in Australia, with most cards co-branded with Visa or Mastercard. Stripe processes these co-branded cards over the eftpos network, adhering to least cost routing requirements.
- [Accept an EPS payment | Stripe Documentation](https://docs.stripe.com/payments/eps/accept-a-payment): This guide explains how to accept EPS payments, an Austrian payment method where customers authenticate via their bank's website. EPS is a single-use payment method compatible with one-time line items in Checkout Sessions.
- [EPS payments | Stripe Documentation](https://docs.stripe.com/payments/eps): EPS is an Austrian online banking payment method that redirects customers to their bank for authentication, providing immediate payment success or failure notifications. It is a customer-authenticated, single-use payment method that cannot be used for recurring payments.
- [Accept an FPX payment | Stripe Documentation](https://docs.stripe.com/payments/fpx/accept-a-payment): This page details how to accept FPX payments, a Malaysian payment method requiring customers to redirect to their bank for payment. FPX is a single-use payment method suitable for one-time line items in Checkout Sessions.
- [FPX payments | Stripe Documentation](https://docs.stripe.com/payments/fpx): FPX (Financial Process Exchange) is a popular Malaysian payment method allowing online transactions via bank credentials, involving a two-step authorization process. Stripe requires a Business Registration Number to process FPX charges and payouts.
- [Accept a giropay payment | Stripe Documentation](https://docs.stripe.com/payments/giropay/accept-a-payment): This page explains how to accept giropay payments, a German online banking method, noting its deprecation after June 30, 2024. Giropay is a single-use payment method requiring customer authentication and is compatible with one-time line items.
- [giropay payments | Stripe Documentation](https://docs.stripe.com/payments/giropay): Giropay is a deprecated German online banking payment method that allows customers to authenticate transactions via their bank, providing immediate payment status. It is a customer-authenticated, single-use payment method not compatible with recurring payments.
- [Accept a GrabPay payment | Stripe Documentation](https://docs.stripe.com/payments/grabpay/accept-a-payment): This guide covers accepting GrabPay payments, a digital wallet popular in Southeast Asia, noting that subscriptions are not currently supported. GrabPay is a single-use payment method where customers authenticate via the GrabPay website.
- [GrabPay payments | Stripe Documentation](https://docs.stripe.com/payments/grabpay): GrabPay is a digital wallet payment method used in Singapore and Malaysia, where customers authenticate transactions via the GrabPay website using a one-time password. It is a customer-initiated, single-use payment method.
- [Accept an iDEAL payment | Stripe Documentation](https://docs.stripe.com/payments/ideal/accept-a-payment): This guide explains how to accept iDEAL payments, a popular Dutch payment method where customers authenticate via their bank. iDEAL is a single-use payment method, and payments must be in Euros.
- [iDEAL payments | Stripe Documentation](https://docs.stripe.com/payments/ideal): iDEAL is a Netherlands-based payment method that allows customers to complete online transactions using their bank credentials, with payments redirecting to their online banking environment. It is being replaced by Wero in 2026-2027.
- [Save bank details during an iDEAL payment | Stripe Documentation](https://docs.stripe.com/payments/ideal/save-during-payment): This page describes how to use iDEAL to save customer IBAN bank details for future SEPA Direct Debit payments. This process involves a small EUR charge to collect and verify bank details, which are then refunded.
- [Use iDEAL to set up future SEPA Direct Debit payments | Stripe Documentation](https://docs.stripe.com/payments/ideal/set-up-payment): This guide explains how to use iDEAL to set up future SEPA Direct Debit payments by collecting customer bank details through a small, refunded EUR transaction. This allows for subsequent payments or subscription setups using the stored SEPA Direct Debit payment method.
- [Payment Methods API | Stripe Documentation](https://docs.stripe.com/payments/payment-methods): The Payment Methods API enables accepting various global payment methods through a single API, using PaymentMethod objects that contain payment details. These can be combined with PaymentIntents for immediate payments or SetupIntents to save details for future use.
- [Installments | Stripe Documentation](https://docs.stripe.com/payments/installments): Installments allow customers to split purchases over multiple billing statements using credit cards. Stripe supports installment payments for Mastercard in Mexico and for Japanese customers, with varying payment structures like fixed payments or revolving credit.
- [Accept installment card payments | Stripe Documentation](https://docs.stripe.com/payments/jp-installments/accept-a-payment): This page explains how to accept installment card payments in Japan, where customers can split purchases over multiple billing statements. Stripe handles the full payment upfront, and the customer's card company manages the installments. Integration is possible via Stripe Checkout, Elements, or the Direct API.
- [Accept installment card payments in Japan | Stripe Documentation](https://docs.stripe.com/payments/jp-installments): Installments in Japan (分割払い) allow customers to divide credit card purchases across several billing cycles, with Stripe receiving the full amount upfront. Stripe Japan accounts can enable this feature using Payment Intents and Payment Methods APIs, and it incurs no additional fees for the merchant.
- [Accept a payment using Kakao Pay in South Korea | Stripe Documentation](https://docs.stripe.com/payments/kakao-pay/accept-a-payment): This guide details how to accept payments via Kakao Pay in South Korea, a popular local payment method. Integrations can be built using Stripe Checkout or the Direct API, requiring payments to be in Korean won (KRW) and adhering to minimum amount requirements.
- [Set up a subscription with Kakao Pay | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/kakao-pay): This page describes how to set up recurring subscriptions using Kakao Pay as a payment method in South Korea. The setup involves using the Intents API and Subscriptions API, or a Stripe-hosted page, to create and confirm subscriptions with Kakao Pay.
- [Set up a subscription with Kakao Pay | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/kakao-pay?api-integration=setupintents): This page provides instructions on setting up subscriptions with Kakao Pay using the Intents API. It outlines the process of creating a product and price in the Stripe Dashboard, and then using API calls to establish the subscription.
- [Set up a subscription with Kakao Pay | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/kakao-pay?api-integration=api): This page explains how to set up subscriptions with Kakao Pay using the API integration. It involves using the Subscriptions API and Payment Intents API to create and confirm subscriptions, and managing products and prices through the Stripe Dashboard.
- [Set up a subscription with Kakao Pay | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/kakao-pay?api-integration=checkout): This guide explains how to set up subscriptions with Kakao Pay using Stripe Checkout. It involves creating a product and price in the Dashboard and then using the Checkout Sessions API to create and confirm the subscription with Kakao Pay.
- [Set up future payments with Kakao Pay | Stripe Documentation](https://docs.stripe.com/payments/kakao-pay/set-up-future-payments): This guide explains how to save Kakao Pay payment details for future use, enabling recurring payments or streamlined on-demand purchases. It covers using Stripe Checkout to save the payment method and obtaining server-side permission to store customer payment details.
- [Accept a Klarna payment | Stripe Documentation](https://docs.stripe.com/payments/klarna/accept-a-payment): This page details how to accept Klarna payments, a global buy now, pay later service, through Stripe. Customers are redirected to Klarna to select a payment option and authenticate, after which Stripe receives the full payment upfront. Integrations can be built using Stripe Checkout or Elements.
- [Comply with Klarna rules | Stripe Documentation](https://docs.stripe.com/payments/klarna/compliance): This guide outlines Klarna's network requirements and compliance rules for merchants. It specifies prohibited business categories and mandates adherence to Klarna's branding guidelines, recommending the use of the Payment Method Messaging Element for automatic compliance.
- [Respond to disputes | Stripe Documentation](https://docs.stripe.com/payments/klarna/disputes): This page explains the dispute process for Klarna payments, noting that customers have up to 180 days to file a dispute. It details how Stripe shares dispute reason codes and outlines the standard dispute resolution pattern, highlighting key differences from card disputes.
- [Klarna payments | Stripe Documentation](https://docs.stripe.com/payments/klarna): Klarna offers customers flexible payment options, allowing them to pay over time while merchants receive full payment upfront from Stripe. Customers are redirected to Klarna to select a payment option, and Klarna assumes the liability for customer repayment issues. It is available in numerous countries and currencies.
- [Migrate Klarna from Sources | Stripe Documentation](https://docs.stripe.com/payments/klarna/migrate): This guide explains how to migrate Klarna integrations from the deprecated Sources API to the Payment Intents API. Key changes include customers selecting their Klarna product on Klarna's redirect page and the removal of SDK inline display support for payments.
- [Optimize Klarna conversion | Stripe Documentation](https://docs.stripe.com/payments/klarna/best-practices): This page provides best practices for optimizing Klarna conversion and increasing cart size. Recommendations include offering express checkout with the Express Checkout Element and promoting buy now, pay later offers using the Payment Method Messaging Element.
- [Set up a subscription with Klarna | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/klarna): This guide explains how to set up subscriptions using Klarna as a payment method, recommending Stripe Checkout for saving Klarna as a payment method. It covers creating products and prices in the Stripe Dashboard and integrating Klarna for recurring payments.
- [Set up future Klarna payments | Stripe Documentation](https://docs.stripe.com/payments/klarna/set-up-future-payments): This guide explains how to save Klarna payment details for future use, supporting automatic subscription payments and streamlined on-demand purchases. It recommends using Stripe Checkout to save the payment method and details how to charge the saved method immediately or later.
- [Klarna supplementary purchase data | Stripe Documentation](https://docs.stripe.com/payments/klarna/supplementary-purchase-data): This page describes how to provide Klarna-specific supplementary purchase data for various industry verticals to improve payment outcomes and customer support. This data can enhance post-purchase transparency, increase acceptance rates, and support fraud assessment.
- [Konbini payments | Stripe Documentation](https://docs.stripe.com/payments/konbini/accept-a-payment): Konbini payments allow customers in Japan to pay for online purchases in cash at convenience stores using payment codes and confirmation numbers. Stripe confirms payment instantly, and funds are available after 4 business days. This method supports one-time payments in JPY and can be integrated via Checkout, Payment Intents, and Payment Methods APIs.
- [Konbini payments | Stripe Documentation](https://docs.stripe.com/payments/konbini): Konbini payments enable customers in Japan to pay for online purchases with cash at convenience stores like FamilyMart and Lawson. After receiving payment codes, customers complete the transaction in-store, and Stripe confirms payment instantly with funds available in about 4 business days. This method is suitable for one-time payments in JPY.
- [Accept a payment using local cards in South Korea | Stripe Documentation](https://docs.stripe.com/payments/kr-card/accept-a-payment): This page explains how to accept payments using locally issued South Korean cards. It details the conditions for a Checkout Session to support these payments, including the requirement for prices to be in Korean won (KRW) and a minimum amount of 100 KRW. Customers are redirected to a local processor to authenticate payments.
- [Set up a subscription with local South Korean cards | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/kr-card): This page outlines how to set up subscriptions using local South Korean cards as a payment method. It describes using the Subscriptions API and SetupIntents API to create and confirm subscriptions. The process involves creating products and prices in the Stripe Dashboard before integration.
- [Set up a subscription with local South Korean cards | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/kr-card?api-integration=setupintents): This page details setting up subscriptions with local South Korean cards, specifically focusing on the SetupIntents API integration. It explains how to create a subscription and PaymentIntent using two API calls, with the PaymentIntent ID then used to confirm the payment. The guide also covers product and price creation within the Stripe Dashboard.
- [Set up a subscription with local South Korean cards | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/kr-card?api-integration=api): This page provides instructions for setting up subscriptions with local South Korean cards using the API integration. It describes creating a subscription and PaymentIntent via the Subscriptions API, then confirming the payment using the Payment Intents API. The process includes defining products and prices in the Stripe Dashboard.
- [Set up a subscription with local South Korean cards | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/kr-card?api-integration=checkout): This page explains how to set up subscriptions using local South Korean cards via the Checkout API integration. It details using a prebuilt checkout page to create and confirm subscriptions, and also covers the initial steps of creating products and prices in the Stripe Dashboard. An example of a monthly subscription for 100,000 KRW is provided.
- [Set up future payments with South Korean cards | Stripe Documentation](https://docs.stripe.com/payments/kr-card/set-up-future-payments): This page guides users on how to save local South Korean card details for future payments. It explains that permission is needed to save payment methods, often through creating an agreement or mandate upfront. The page also mentions that saving payment methods in Checkout can facilitate setting up recurring payments for subscriptions.
- [Accept a payment with Kriya | Stripe Documentation](https://docs.stripe.com/payments/kriya/accept-a-payment): This page describes how to accept payments using Kriya, a payment method offering flexible payment terms for businesses. Kriya allows customers to buy now and pay later, with businesses receiving immediate payment. Compatibility requires all line items in a Checkout Session to be in the same currency.
- [Kriya payments | Stripe Documentation](https://docs.stripe.com/payments/kriya): This page introduces Kriya, a payment solution that provides businesses with flexible payment terms, allowing customers to buy now and pay later while businesses get paid instantly. Kriya is suitable for B2B commerce and supports various payment flows. Businesses can enable Kriya through the Stripe Dashboard and integrate it using Stripe's front-end products like Checkout or Elements.
- [Link | Stripe Documentation](https://docs.stripe.com/payments/wallets/link): This page details Link, Stripe's digital wallet, which allows customers to securely save and reuse payment methods for faster checkout. It supports various payment methods including cards and bank accounts, potentially reducing processing costs. Link confirms transactions immediately and settles them to the Stripe balance similarly to card payments.
- [Enable local payment methods by country | Stripe Documentation](https://docs.stripe.com/payments/local-markets): This page explains how to enable local payment methods by country, focusing on South Korea and Nigeria. It highlights the importance of integrating region-specific options to cater to local preferences and increase conversion rates. The document mentions that Stripe supports accepting wallets and local cards in South Korea without requiring a local entity.
- [Mastercard Installments | Stripe Documentation](https://docs.stripe.com/payments/mastercard-installments): This page describes Mastercard Installments, a feature enabling buy now, pay later options for customers using Mastercard. Businesses are automatically enrolled to accept this payment method, and customers can pay in interest-free installments. Standard Mastercard transaction fees apply, and surcharging is prohibited. This feature does not support recurring payments.
- [MB WAY payments | Stripe Documentation](https://docs.stripe.com/payments/mb-way/accept-a-payment): This page explains how to accept MB WAY payments, a digital wallet payment method popular in Portugal. Customers use their phone number to initiate payments and authenticate them via the MB WAY app, receiving immediate payment success or failure notifications. To support MB WAY, prices must be in Euros (EUR).
- [MB WAY payments | Stripe Documentation](https://docs.stripe.com/payments/mb-way): This page describes MB WAY, a digital wallet payment method used in Portugal where customers pay using their phone number and authenticate through the MB WAY app. Payments are confirmed immediately, and transactions can range from 0.50 EUR to 5,000 EUR. This payment method is family-oriented and does not support recurring payments.
- [Accept meses sin intereses card payments | Stripe Documentation](https://docs.stripe.com/payments/meses-sin-intereses/accept-a-payment): This page details how to accept 'meses sin intereses' (months without interest) card payments in Mexico. This feature allows customers to split purchases over multiple billing statements, while the merchant receives the full payment upfront minus fees. Accepting installment payments incurs an additional fee beyond the standard credit card transaction fee.
- [Mexico installments (meses sin intereses) | Stripe Documentation](https://docs.stripe.com/payments/mx-installments): This page explains 'meses sin intereses' (installments) as a credit card payment method in Mexico, enabling customers to split purchases over time. Merchants receive the full payment minus a fee, with the customer's bank handling the installment collection. Stripe supports this feature across various products like Payment Intents, Checkout, and Invoicing for Stripe Mexico accounts.
- [MobilePay payments | Stripe Documentation](https://docs.stripe.com/payments/mobilepay/accept-a-payment): This page explains how to accept MobilePay payments, a digital wallet payment method used in Denmark and Finland. Customers authenticate and approve payments using the MobilePay app, and Stripe processes this as a card transaction, providing immediate payment success or failure notifications. Compatibility requires prices to be in local currency (DKK, EUR, NOK, SEK).
- [MobilePay payments | Stripe Documentation](https://docs.stripe.com/payments/mobilepay): This page describes MobilePay, a digital wallet payment method prevalent in Denmark and Finland, allowing customers to authenticate payments via its app. Stripe processes MobilePay payments as card transactions, offering immediate confirmation of success or failure. The service supports multiple currencies including DKK, EUR, NOK, and SEK and does not support recurring payments.
- [Accept a payment with Mondu | Stripe Documentation](https://docs.stripe.com/payments/mondu/accept-a-payment): This page describes how to accept payments with Mondu, a payment method offering 30-day net terms for B2B commerce. Customers are redirected to Mondu for a credit check and then return to complete the order, while the business receives immediate payment. To support Mondu, all line items in a Checkout Session must be in the same currency.
- [Mondu payments | Stripe Documentation](https://docs.stripe.com/payments/mondu): This page introduces Mondu, a European payment solution for B2B commerce that provides customers with 30-day net payment terms while ensuring businesses are paid upfront. It involves a redirection to Mondu for a credit check. Mondu supports multiple currencies including EUR, CHF, and GBP and is categorized as a Buy Now, Pay Later service.
- [Accept a Multibanco payment | Stripe Documentation](https://docs.stripe.com/payments/multibanco/accept-a-payment): This page explains how to accept Multibanco payments, a voucher-based method popular in Portugal. Customers receive a voucher with entity and reference numbers to pay via online banking or ATMs, which can lead to delayed payment confirmation. Businesses in Europe or the US can accept Multibanco payments through Stripe Checkout from customers in Portugal.
- [Multibanco payments | Stripe Documentation](https://docs.stripe.com/payments/multibanco): Multibanco is a voucher-based payment method in Portugal that allows customers to pay via online banking or ATM using provided entity and reference numbers. Payment confirmation may be delayed by several days due to bank transfer processing, especially over weekends.
- [Accept a payment using Naver Pay in South Korea | Stripe Documentation](https://docs.stripe.com/payments/naver-pay/accept-a-payment): This page explains how to accept payments using Naver Pay in South Korea. It details the integration process with Stripe Checkout, emphasizing that prices must be in Korean Won (KRW) and meet a minimum amount of 100 KRW.
- [Set up a subscription with Naver Pay | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/naver-pay): This guide outlines how to set up subscriptions with Naver Pay as a payment method using Stripe's Intents API and Subscriptions API. It covers creating products and prices in the Stripe Dashboard and confirming subscriptions via API calls.
- [Set up a subscription with Naver Pay | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/naver-pay?api-integration=setupintents): This page details setting up subscriptions with Naver Pay via the Setup Intents API. It explains the process of creating a subscription and PaymentIntent using two API calls and managing products and prices in the Stripe Dashboard.
- [Set up a subscription with Naver Pay | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/naver-pay?api-integration=api): This guide explains how to set up subscriptions using Naver Pay as a payment method through the Stripe API. It covers creating a subscription and PaymentIntent with two API calls and managing product and price configurations in the Stripe Dashboard.
- [Set up a subscription with Naver Pay | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/naver-pay?api-integration=checkout): This page describes how to set up subscriptions with Naver Pay using the Stripe Checkout API. It explains the process of creating and confirming a subscription with a prebuilt checkout page and setting up products and prices in the Dashboard.
- [Set up future payments with Naver Pay | Stripe Documentation](https://docs.stripe.com/payments/naver-pay/set-up-future-payments): This document explains how to save Naver Pay payment details for future use, enabling recurring payments and subscriptions. It highlights the use of Stripe Checkout and the need to obtain customer permission to save payment methods.
- [Accept a payment through local bank transfers in Nigeria | Stripe Documentation](https://docs.stripe.com/payments/ng-bank-transfer/accept-a-payment): This page details how to accept payments via local bank transfers in Nigeria using Stripe. It covers the redirect-based payment flow where customers are directed to a local provider for authentication and authorization, requiring prices in Nigerian Naira (NGN).
- [Accept a payment using local cards in Nigeria | Stripe Documentation](https://docs.stripe.com/payments/ng-card/accept-a-payment): This guide explains how to accept payments using Nigerian-issued cards (Naira cards) through Stripe. It describes a redirect-based payment flow for authentication and authorization, with prices required in Nigerian Naira (NGN) and specific minimum and maximum transaction amounts.
- [Set up a subscription with Nigerian cards | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/ng-card): This page explains how to set up subscriptions using Naira cards as a payment method in Nigeria with Stripe. It covers creating products and prices in the Stripe Dashboard and using API calls to create and confirm subscriptions.
- [Set up a subscription with Nigerian cards | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/ng-card?api-integration=setupintents): This guide details setting up subscriptions with Nigerian cards via the Setup Intents API. It outlines the process of creating a subscription and PaymentIntent using two API calls and managing product and price configurations in the Stripe Dashboard.
- [Set up a subscription with Nigerian cards | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/ng-card?api-integration=api): This page explains how to set up subscriptions using Naira cards as a payment method through the Stripe API. It covers creating a subscription and PaymentIntent with two API calls and managing product and price configurations in the Stripe Dashboard.
- [Set up a subscription with Nigerian cards | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/ng-card?api-integration=checkout): This page describes how to set up subscriptions using Nigerian cards with the Stripe Checkout API. It explains creating and confirming a subscription with a prebuilt checkout page and setting up products and prices in the Dashboard.
- [Set up future payments with Naira card | Stripe Documentation](https://docs.stripe.com/payments/ng-card/set-up-future-payments): This document explains how to save Naira card payment details for future use, enabling recurring payments and subscriptions. It highlights the use of Stripe Checkout and the necessity of obtaining customer permission to save payment methods.
- [Accept a New Zealand BECS Direct Debit payment | Stripe Documentation](https://docs.stripe.com/payments/nz-bank-account/accept-a-payment): This page explains how to accept New Zealand BECS Direct Debit payments using Stripe. It involves creating a payment object, collecting payment method information and mandate acknowledgement, and submitting the payment for processing.
- [New Zealand BECS Direct Debit payments | Stripe Documentation](https://docs.stripe.com/payments/nz-bank-account): This page provides information on accepting New Zealand BECS Direct Debit payments, which allows direct debits from customer bank accounts. It requires collecting a mandate from the customer and notes that payment notification can take up to two business days.
- [Migrate from another processor | Stripe Documentation](https://docs.stripe.com/payments/nz-bank-account/migrate-from-another-processor): This guide explains how to migrate bank accounts from another payment processor to Stripe for New Zealand BECS Direct Debit. It emphasizes retaining copies of Direct Debit Authorities and informing customers about the migration process.
- [Save details for future payments with New Zealand BECS Direct Debits | Stripe Documentation](https://docs.stripe.com/payments/nz-bank-account/set-up-payment): This page details how to save payment method details for future New Zealand BECS Direct Debit payments. It explains using the Setup Intents API to collect payment details in advance, which is useful for streamlining future purchases and subscriptions.
- [Supported payment methods | Stripe Documentation](https://docs.stripe.com/payments/payment-methods/overview): This page provides an overview of payment method categories supported by Stripe, including Cards, Bank debits, Bank redirects, Bank transfers, Buy now, pay later, Real-time payments, Vouchers, and Wallets. Integrating one payment method within a family allows for easier addition of others.
- [Accept an OXXO payment | Stripe Documentation](https://docs.stripe.com/payments/oxxo/accept-a-payment): This page explains how to accept OXXO payments in Mexico, a voucher-based method where customers pay with cash at an OXXO store. It requires prices to be in the same currency and only supports one-time payments, not recurring subscriptions.
- [OXXO payments | Stripe Documentation](https://docs.stripe.com/payments/oxxo): OXXO is a Mexican convenience store chain that allows customers to pay for online purchases in-store with cash using a voucher. Customers receive a voucher with a transaction reference, which they present at an OXXO store to complete the payment. Payment confirmation is typically received by the next business day.
- [Accept a Przelewy24 payment | Stripe Documentation](https://docs.stripe.com/payments/p24/accept-a-payment): Przelewy24 (P24) is a popular Polish payment method that allows customers to pay online by redirecting to their bank's website for authentication. The integration provides immediate notification of payment success or failure. Compatibility requires all line items to be in the same currency and only supports one-time payments.
- [Przelewy24 payments | Stripe Documentation](https://docs.stripe.com/payments/p24): Przelewy24 is a Polish payment method aggregator enabling online transactions through bank transfers and other methods. Customers are redirected to the Przelewy24 website to authenticate payments, with immediate feedback on success or failure. This method is a single-use authenticated bank debit and does not support recurring payments.
- [Pay by Bank payments | Stripe Documentation](https://docs.stripe.com/payments/pay-by-bank/accept-a-payment): Pay by Bank is a single-use payment method that requires customers to authenticate transactions directly with their bank via a mobile app or web portal. The process redirects customers away from your site for authorization and then returns them, providing immediate payment status. Compatibility requires all line items to be in the same currency and only supports one-time payments.
- [Pay by Bank payments | Stripe Documentation](https://docs.stripe.com/payments/pay-by-bank): Pay by Bank allows customers in the UK and Europe to pay directly from their bank accounts using open banking APIs. Customers select their bank and approve the payment through their bank's app or web portal. The service is available by default for amounts between 0.50 GBP and 10,000 GBP.
- [Accept a payment using PAYCO in South Korea | Stripe Documentation](https://docs.stripe.com/payments/payco/accept-a-payment): Integrating PAYCO in South Korea allows customers to pay using this local payment method, which involves redirecting them to a partner processor for authentication. After authorization, customers are returned to your site with immediate payment status. Compatibility requires all line items to be in Korean Won (KRW).
- [Payment method support for platforms and marketplaces | Stripe Documentation](https://docs.stripe.com/payments/payment-methods/payment-method-connect-support): Platforms and marketplaces using Stripe Connect have varying payment method availability based on country, business type, account type, and charge type. Specific payment methods like ACH Direct Debit require requesting capabilities for connected accounts to be enabled. The charge type of Connect payments can influence default statement descriptors.
- [Register domains for payment methods | Stripe Documentation](https://docs.stripe.com/payments/payment-methods/pmd-registration): Registering web domains is required for certain payment methods like Apple Pay, Google Pay, Klarna, and PayPal when using Elements or Checkout's embeddable payment form. This process ensures the domain is ready for use with these payment methods and any future ones enabled. Domains must be registered for both live and testing environments.
- [Payment method integration options | Stripe Documentation](https://docs.stripe.com/payments/payment-methods/integration-options): The available payment methods depend on currency, country, and Stripe products used, with integration options ranging from no-code to advanced. Stripe Invoicing also allows automatic charging of saved payment methods or emailing invoices without coding. Payment Links, Stripe-hosted pages, embedded forms, and advanced API integrations offer different levels of effort and hosting.
- [Payment method support | Stripe Documentation](https://docs.stripe.com/payments/payment-methods/payment-method-support): Payment method support varies based on currency, country, and API options, with specific requirements and restrictions for each. Users can troubleshoot payment method visibility issues using the Dashboard's troubleshooting tool. Detailed tables provide information on country and currency support, product support, and API support for each payment method.
- [Accept a PayNow payment | Stripe Documentation](https://docs.stripe.com/payments/paynow/accept-a-payment): PayNow is a Singaporean funds transfer service enabling online payments by having customers scan a QR code during checkout using their preferred banking app. Payment confirmation is received instantly from Stripe after the customer completes the transaction. Compatibility requires all line items to be in SGD and only supports one-time payments.
- [PayNow payments | Stripe Documentation](https://docs.stripe.com/payments/paynow): PayNow is a Singapore-based payment method allowing customers to pay via their preferred banking app by scanning a QR code presented at checkout. Instant confirmation is provided by Stripe upon payment completion. This real-time payment method is specific to Singapore and supports only SGD currency.
- [Accept a PayPal payment | Stripe Documentation](https://docs.stripe.com/payments/paypal/accept-a-payment): PayPal is a digital wallet payment method available globally, redirecting customers to PayPal for authentication before returning them to your site with immediate payment status. It supports various funding sources like PayPal balance, linked accounts, or buy now, pay later options. Connect support for PayPal is partial and may require manual approval.
- [Choose settlement preference | Stripe Documentation](https://docs.stripe.com/payments/paypal/choose-settlement-preference): For direct Stripe businesses, settlement preference for PayPal payments can be set by connecting PayPal and Stripe accounts, determining how funds are accessed and managed. If funds settle on Stripe, they are accessible via the Stripe balance according to the payout schedule. Settlement choice impacts reconciliation and fund management.
- [Activate PayPal payments | Stripe Documentation](https://docs.stripe.com/payments/paypal/activate): PayPal can be activated for eligible Stripe accounts in the EU, UK, Norway, Switzerland, and Liechtenstein directly from the Stripe Dashboard. Users select a settlement preference: adding funds to their Stripe balance or keeping them in their PayPal balance, which requires separate management. Connecting Stripe and PayPal accounts is required to complete the activation.
- [Disputed PayPal payments | Stripe Documentation](https://docs.stripe.com/payments/paypal/disputed-payments): PayPal payments carry a low risk of fraud due to mandatory customer authentication, but disputes can arise if goods are not received or do not match descriptions. Disputes can be filed up to 180 days after purchase, and Stripe notifies users via email, the Dashboard, or API events. Settlement choice affects the fund flow for PayPal disputes.
- [Import saved PayPal payment methods | Stripe Documentation](https://docs.stripe.com/payments/paypal/import-saved-payment-method): Existing PayPal billing agreements created outside of Stripe can be imported and reused within a Stripe integration using the billing_agreement_id parameter. This allows charging customers without requiring reauthorization, provided recurring payments are enabled. Only billing agreements created through Stripe generate cancellation webhooks.
- [PayPal payments | Stripe Documentation](https://docs.stripe.com/payments/paypal): PayPal is a global digital wallet payment method that redirects customers to PayPal for authentication, allowing them to use various funding sources. Immediate payment success or failure notifications are provided upon return to the merchant's site. It supports recurring payments and has dispute resolution capabilities.
- [PayPal payout reconciliation | Stripe Documentation](https://docs.stripe.com/payments/paypal/payout-reconciliation): PayPal payout reconciliation is necessary when funds are received on PayPal rather than Stripe, requiring matching of received payments with PayPal orders. Stripe automatically reconciles transactions settling on its platform, but external settlements require using PayPal reporting or sFTP. Using the reference field for order/invoice IDs is the recommended reconciliation method.
- [PayPal Button | Stripe Documentation](https://docs.stripe.com/payments/paypal/paypal-button): The PayPal button simplifies customer payments through Stripe Checkout or the Express Checkout Element, offering an alternative to direct redirects. Stripe determines when to present the button, but its availability can be influenced by integration configurations. Testing with a PayPal Sandbox account is recommended before going live.
- [Set up future PayPal payments | Stripe Documentation](https://docs.stripe.com/payments/paypal/set-up-future-payments): This page explains how to set up future PayPal payments for subscriptions, delayed charges, and streamlined future purchases. It details how Stripe automatically enables recurring payments for most users, but some may need to enable it manually in their Payment methods settings.
- [Accept a payment with PayPay | Stripe Documentation](https://docs.stripe.com/payments/paypay/accept-a-payment): This guide explains how to accept a payment using PayPay, a digital wallet popular in Japan. It covers how Stripe automatically presents payment options and provides instructions for manually configuring PayPay if needed, noting that it's a single-use payment method requiring customer authentication.
- [PayPay payments | Stripe Documentation](https://docs.stripe.com/payments/paypay): This page introduces PayPay as a popular digital payment platform and mobile wallet service in Japan. It outlines PayPay's payment method properties, including its customer locations, presentment currency (JPY), and lack of support for recurring payments. The guide also explains how to enable PayPay through the Stripe Dashboard or by using Stripe's front-end products like Checkout and Elements.
- [PayTo payments | Stripe Documentation](https://docs.stripe.com/payments/payto/accept-a-payment): This document describes how to accept PayTo payments, a real-time payment method in Australia for one-time and recurring payments. Customers authenticate using their mobile banking app, and notification of payment success or failure is delayed. The guide details how to configure PayTo in a Checkout integration, requiring all line items to be in AUD.
- [PayTo payments | Stripe Documentation](https://docs.stripe.com/payments/payto): This page provides an overview of PayTo, a real-time payment method in Australia that supports both one-time and recurring payments. It details PayTo's payment method properties, including its customer locations (Australia), presentment currency (AUD), and support for recurring payments and disputes. The guide also outlines the payment flow and verification requirements for using PayTo.
- [Accept a payment and save a mandate for future PayTo payments | Stripe Documentation](https://docs.stripe.com/payments/payto/save-during-payment): This page explains how to set up future PayTo payments, allowing customers in Australia to authenticate mandates for one-off and recurring payments via their banking apps. Setting up a mandate enables future recurring payments without requiring repeated customer authorization. The guide covers compatibility requirements, including using AUD for all line items in Checkout sessions.
- [Accept subscription payments with PayTo | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/payto): This guide explains how to set up subscription payments using PayTo as the payment method. It details the process of creating a product and price in the Stripe Dashboard, specifying recurring billing and currency (AUD). The guide then directs users to follow quickstarts for Checkout, Elements, or API integrations to implement subscriptions with PayTo.
- [Accept subscription payments with PayTo | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/payto?api-integration=setupintents): This guide details setting up subscription payments with PayTo using the Setup Intents API. It outlines creating products and prices in the Stripe Dashboard and then using two API calls: one with the Setup Intents API to set PayTo as the payment method, and another with the Subscriptions API to create the subscription and confirm payment.
- [Accept subscription payments with PayTo | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/payto?api-integration=api): This guide explains how to set up subscription payments with PayTo using the Checkout API. It covers creating products and prices in the Stripe Dashboard and then using the Checkout API to create and confirm a subscription with a prebuilt checkout page. The process involves recording the price ID for subsequent steps.
- [Accept subscription payments with PayTo | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/payto?api-integration=checkout): This guide explains how to set up subscription payments with PayTo using the Checkout API. It details creating products and prices in the Stripe Dashboard and then using the Checkout API to create and confirm a subscription with a prebuilt checkout page. The process involves recording the price ID for subsequent steps.
- [Set up future PayTo payments | Stripe Documentation](https://docs.stripe.com/payments/payto/set-up-payment): This page explains how to set up future PayTo payments, enabling customers in Australia to authenticate PayTo mandates for one-off and recurring payments through their banking apps. Setting up a mandate allows for future payments without re-authorization, and customers can manage mandates in their banking apps. The guide details how to create a Checkout Session in setup mode to specify mandate terms.
- [Use existing AU BECS customer details to set up PayTo agreements | Stripe Documentation](https://docs.stripe.com/payments/payto/use-au-becs-customer-details-to-set-up-payto-agreements): This guide explains how to use existing Australian BECS customer details to set up PayTo agreements. It emphasizes obtaining customer authorization by sending a new PayTo mandate via Stripe APIs and provides instructions for creating customers and SetupIntents, including options for authorization via bank account details or PayID. Customers receive an authorization request from their bank to approve the mandate.
- [Pix payments | Stripe Documentation](https://docs.stripe.com/payments/pix/accept-a-payment): This page describes how to accept Pix payments, a real-time payment method in Brazil. Customers pay by scanning a QR code or copying a Pix string in their banking apps. To support Pix, all line items in a Checkout Session must be in BRL currency and only one-time payments are supported.
- [Pix payments | Stripe Documentation](https://docs.stripe.com/payments/pix): This page introduces Pix as a real-time payment system in Brazil developed by the Central Bank. Customers authenticate by scanning a QR code or using a Pix string in their banking apps. It outlines Pix's payment method properties, including its customer locations (Brazil), presentment currency (BRL), and support for disputes. The guide also explains how to enable Pix through the Stripe Dashboard or Stripe's front-end products.
- [Accept a PromptPay payment | Stripe Documentation](https://docs.stripe.com/payments/promptpay/accept-a-payment): This guide explains how to accept PromptPay payments, an instant funds transfer service in Thailand. Customers pay by scanning a QR code during checkout, which redirects them back to the merchant's website. To support PromptPay, all line items must be in the same currency, and only one-time payments are supported.
- [PromptPay payments | Stripe Documentation](https://docs.stripe.com/payments/promptpay): This page introduces PromptPay as a popular payment method in Thailand that allows customers to pay using their preferred banking app by scanning a QR code. It details PromptPay's payment method properties, including customer locations (Thailand), presentment currency (THB), and instant payment confirmation. The guide also explains how to enable PromptPay through the Stripe Dashboard or Stripe's front-end products.
- [Real-time payments | Stripe Documentation](https://docs.stripe.com/payments/real-time): This page provides an overview of real-time payments supported by Stripe in countries like Brazil, Singapore, Thailand, Sweden, and India. These methods allow customers to directly transfer funds from their bank accounts or other sources through an authenticating intermediary, potentially increasing conversion rates. The page lists supported Stripe products and API integrations for various real-time payment methods.
- [Payment on invoice | Stripe Documentation](https://docs.stripe.com/payments/rechnung): This page describes 'Payment on Invoice,' a buy now, pay later option primarily for Germany, which allows merchants to get paid upfront. After a risk assessment and approval, Stripe adds the full payment amount to the merchant's balance, and the customer is invoiced to pay within 14 days. The payment method is customer-initiated and provides immediate notification of success or failure.
- [Accept a payment with Revolut Pay | Stripe Documentation](https://docs.stripe.com/payments/revolut-pay/accept-a-payment): This guide explains how to accept payments with Revolut Pay, a reusable digital wallet payment method used in the UK and EU. Customers authenticate through Revolut Pay and are redirected back to the merchant's website, with immediate notification of payment success or failure. The guide covers compatibility requirements, including supporting the same currency for all line items and the support for recurring subscription plans.
- [Revolut Pay payments | Stripe Documentation](https://docs.stripe.com/payments/revolut-pay): This page introduces Revolut Pay, a digital wallet payment method developed by Revolut, used in the UK and EU. It allows customers to pay using their stored balance or cards, with options for non-Revolut customers to save details. The page outlines Revolut Pay's payment method properties, including supported currencies and its support for recurring payments and manual capture. It also details the payment flow where customers are redirected to Revolut Pay for authentication.
- [Set up a subscription with Revolut Pay | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/revolut-pay): This guide explains how to set up a subscription using Revolut Pay as a payment method with Stripe. It involves using the Setup Intents API to set Revolut Pay and then the Subscriptions API to create and confirm the subscription and payment.
- [Set up a subscription with Revolut Pay | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/revolut-pay?api-integration=setupintents): This guide explains how to set up a subscription using Revolut Pay as a payment method with Stripe, specifically detailing the Setup Intents API integration. It outlines the process of using two API calls to set up Revolut Pay and then create and confirm a subscription.
- [Set up a subscription with Revolut Pay | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/revolut-pay?api-integration=api): This guide details setting up a subscription with Revolut Pay as the payment method through Stripe's API integration. It describes a two-step API call process: first using Setup Intents API for Revolut Pay, then Subscriptions API for creating and confirming the subscription.
- [Set up a subscription with Revolut Pay | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/revolut-pay?api-integration=checkout): This guide explains how to set up a subscription with Revolut Pay as a payment method using Stripe's Checkout API. It details a two-step API process involving Setup Intents API and Subscriptions API to create and confirm the subscription and payment.
- [Set up future Revolut Pay payments | Stripe Documentation](https://docs.stripe.com/payments/revolut-pay/set-up-future-payments): This guide explains how to save Revolut Pay payment details for future recurring payments using Stripe's Checkout. It covers obtaining customer permission (mandate) to save payment details for later charges, enabling recurring payments.
- [Accept a payment using Samsung Pay in South Korea | Stripe Documentation](https://docs.stripe.com/payments/samsung-pay/accept-a-payment): This guide explains how to accept payments using Samsung Pay in South Korea through Stripe's Checkout integration. It outlines the conditions for supporting this local payment method, including currency requirements, and details how to enable it.
- [Accept a payment with Satispay | Stripe Documentation](https://docs.stripe.com/payments/satispay/accept-a-payment): This guide explains how to accept payments with Satispay, a single-use payment method where customers authenticate via redirection. It details compatibility requirements for Satispay within a Stripe Checkout Session and how customers complete payments.
- [Satispay payments | Stripe Documentation](https://docs.stripe.com/payments/satispay): This page describes how to accept payments with Satispay, a digital wallet popular in Italy, through Stripe. It outlines Satispay's payment properties, including business and customer locations, currency support, and payment flow, and explains how to enable it via the Stripe Dashboard or hosted UIs.
- [Accept a payment with Scalapay | Stripe Documentation](https://docs.stripe.com/payments/scalapay/accept-a-payment): This guide explains how to accept payments with Scalapay, a buy now, pay later service offering 3 or 4 installment payments. It details compatibility requirements for Scalapay within a Stripe Checkout Session and the customer payment flow involving redirection and authorization.
- [Scalapay payments | Stripe Documentation](https://docs.stripe.com/payments/scalapay): This page describes Scalapay payments, a buy now, pay later option for customers to pay in 3 or 4 installments, available in the EU. It lists payment method properties, including business and customer locations, currency, and payment confirmation, and explains how to enable Scalapay through Stripe.
- [Accept a SEPA Direct Debit payment | Stripe Documentation](https://docs.stripe.com/payments/sepa-debit/accept-a-payment): This guide explains how to accept SEPA Direct Debit payments using Stripe, a common payment method in the EU. It details the process of creating a PaymentIntent to track payments, collecting mandate acknowledgments, and the delayed notification nature of these transactions.
- [SEPA Direct Debit payments | Stripe Documentation](https://docs.stripe.com/payments/sepa-debit): This page details SEPA Direct Debit payments, a common EU payment method for EUR-denominated bank accounts. It explains that Stripe supports the Core scheme, requires customer name and IBAN, and that customers must accept a mandate for authorization.
- [Save SEPA Direct Debit details for future payments | Stripe Documentation](https://docs.stripe.com/payments/sepa-debit/set-up-payment): This guide explains how to save SEPA Direct Debit payment details for future use with Stripe, enabling streamlined future purchases or subscription trials. It emphasizes that saved payment methods must be attached to a Customer object and notes the delayed notification for SEPA Direct Debit.
- [Accept a payment with SeQura | Stripe Documentation](https://docs.stripe.com/payments/sequra/accept-a-payment): This guide explains how to accept payments with SeQura, a payment method offering terms from 7-120 days. It details compatibility requirements for SeQura within a Stripe Checkout Session and the customer payment flow involving redirection and authorization.
- [SeQura payments | Stripe Documentation](https://docs.stripe.com/payments/sequra): This page describes SeQura payments, a buy now, pay later option for customers in Southern Europe to pay in installments. It lists payment method properties, including business and customer locations, currency, and payment confirmation, and explains how to enable SeQura through Stripe.
- [Remove and replace SOFORT in your integration | Stripe Documentation](https://docs.stripe.com/payments/sofort/replace): This guide explains how to remove SOFORT as a payment method from Stripe integrations, as it is discontinued as of March 31, 2025. It provides instructions for removing SOFORT and suggests alternatives like Klarna's 'pay in full' option.
- [Accept a payment with Sunbit | Stripe Documentation](https://docs.stripe.com/payments/sunbit/accept-a-payment): This guide explains how to accept payments with Sunbit, a buy now, pay later service offering 3, 6, or 12 installment payments. It details compatibility requirements for Sunbit within a Stripe Checkout Session and the customer payment flow involving redirection and authorization.
- [Sunbit payments | Stripe Documentation](https://docs.stripe.com/payments/sunbit): This page describes Sunbit payments, a buy now, pay later option available in the US for customers to pay in installments. It lists payment method properties, including business and customer locations, currency, and payment confirmation, and explains how to enable Sunbit through Stripe.
- [Swish payments | Stripe Documentation](https://docs.stripe.com/payments/swish/accept-a-payment): This guide explains how to accept Swish payments, a popular mobile payment method in Sweden, through Stripe's Checkout integration. It outlines the conditions for supporting Swish, including currency requirements, and details the mobile redirect payment flow.
- [Swish payments | Stripe Documentation](https://docs.stripe.com/payments/swish): This page describes Swish payments, a single-use mobile payment method popular in Sweden. It outlines payment method properties, including business and customer locations, currency, and payment confirmation, and details the mobile and desktop payment flows.
- [Migrate to the Payment Intents and Payment Methods APIs | Stripe Documentation](https://docs.stripe.com/payments/payment-methods/transitioning): The Payment Methods API is replacing the older Sources and Tokens APIs for collecting and storing payment information. It integrates with the Payment Intents API to support a wide range of payment methods, and migrating local payment methods from the Sources API is mandatory.
- [TWINT payments | Stripe Documentation](https://docs.stripe.com/payments/twint/accept-a-payment): TWINT is a single-use payment method popular in Switzerland that allows customers to authenticate and approve payments via a mobile app. To accept TWINT payments through Stripe Checkout, all line items must be priced in Swiss Francs (CHF).
- [TWINT payments | Stripe Documentation](https://docs.stripe.com/payments/twint): TWINT is a Swiss payment method allowing mobile app authentication for single-use payments, providing immediate success or failure notifications. Customers can pay via mobile redirect or by scanning a QR code with their TWINT app.
- [UPI payments | Stripe Documentation](https://docs.stripe.com/payments/upi/accept-a-payment): UPI is a common payment method in India that enables real-time fund transfers between bank accounts. To accept UPI payments via Stripe Checkout, all line items must be priced in Indian Rupees (INR), and it supports both one-time and recurring payments through UPI AutoPay.
- [UPI payments | Stripe Documentation](https://docs.stripe.com/payments/upi): UPI is India's real-time payment system for instant bank transfers, allowing customers to authenticate using their preferred banking or wallet app. It supports both one-time and recurring payments via UPI AutoPay, where customers authorize future automatic charges.
- [Set up future UPI payments | Stripe Documentation](https://docs.stripe.com/payments/upi/set-up-future-payments): This guide explains how to save UPI payment details for future use with Stripe Checkout by creating an agreement (mandate) upfront. This allows for saving customer payment details and potentially charging them later, even when not actively using the website or app.
- [UPI AutoPay | Stripe Documentation](https://docs.stripe.com/payments/upi/upi-autopay): UPI AutoPay facilitates recurring payments in India through e-mandates, allowing customers to authorize automatic charges for subscriptions. Stripe handles pre-debit notifications and supports additional security measures like PIN entry for mandate authorization and high-value transactions.
- [Accept an ACH Direct Debit payment | Stripe Documentation](https://docs.stripe.com/payments/ach-direct-debit/accept-a-payment): ACH Direct Debit allows businesses in the US to accept payments from customers with US bank accounts, functioning as a reusable, delayed notification payment method. It requires customer authorization and bank account verification, with a risk of payment failures and disputes.
- [Blocked bank accounts | Stripe Documentation](https://docs.stripe.com/payments/ach-direct-debit/blocked-bank-accounts): Stripe may block bank accounts for reasons like returned debits or failed payouts, requiring review before reinitiating debits as per NACHA rules. Understanding the cause of a block is crucial for unblocking the account and preventing future issues.
- [ACH Direct Debit | Stripe Documentation](https://docs.stripe.com/payments/ach-direct-debit): ACH Direct Debit is a Stripe payment method for US bank debits, offering a reusable and delayed notification system that can take up to 4 business days for confirmation. It carries a risk of failed payments and disputes, requiring customer authorization and bank account verification.
- [Migrating from another processor | Stripe Documentation](https://docs.stripe.com/payments/ach-direct-debit/migrating-from-another-processor): Verified bank accounts used with other processors can be migrated to Stripe for ACH Direct Debit payments through a data migration process with Stripe or a manual migration. Both the business and Stripe share responsibility for maintaining proof of authorization and verification.
- [Nacha compliance for online consumer purchases | Stripe Documentation](https://docs.stripe.com/payments/ach-direct-debit/nacha-purchase-rule): Effective March 20, 2026, Nacha requires e-commerce ACH debit purchases to include 'PURCHASE' in the Company Entry Description. This applies to consumer-authorized online purchases of goods using WEB or TEL SEC codes, and can be configured via the Stripe Dashboard or API.
- [Overview of ACH SEC codes | Stripe Documentation](https://docs.stripe.com/payments/ach-direct-debit/sec-codes): A Standard Entry Class (SEC) code describes how a customer or business authorized an ACH transaction, with businesses responsible for using the correct code to comply with Nacha rules. Stripe supports four SEC codes, defaulting to WEB for consumers and CCD for businesses if no mandate method is specified.
- [Save details for future payments with ACH Direct Debit | Stripe Documentation](https://docs.stripe.com/payments/ach-direct-debit/set-up-payment): Stripe Checkout in setup mode allows collecting payment method details for future ACH Direct Debit payments, with the final amount and date determined later. This is useful for saving payment methods, collecting surcharges, or starting free trials, though ACH Direct Debit payments take up to 4 business days to process.
- [Vipps payments | Stripe Documentation](https://docs.stripe.com/payments/vipps/accept-a-payment): Vipps is a single-use payment method in Norway that uses the Vipps app for customer authentication and payment approval. Stripe processes this as a card transaction, providing immediate notification of success or failure, and it can be integrated into Stripe Checkout.
- [Vipps payments | Stripe Documentation](https://docs.stripe.com/payments/vipps): Vipps is a Norwegian payment method that functions as a single-use card wallet, allowing customers to authorize payments via the Vipps app. Stripe handles the underlying card transaction, providing immediate payment confirmation, and requires a specific API header for integration during its private preview.
- [Vouchers | Stripe Documentation](https://docs.stripe.com/payments/vouchers): Vouchers enable customers to complete online purchases in person at authorized locations by scanning a voucher code, often with cash. This method is suitable for businesses with customers lacking cards or bank accounts, but may not be ideal if immediate goods delivery or easy refunds are required.
- [Wallets | Stripe Documentation](https://docs.stripe.com/payments/wallets): Wallets allow customers to pay online or in person using saved payment credentials or stored balances, with the wallet authenticating the customer and passing payment details securely. Coverage and flow can vary by country and device, and refund/dispute processes may differ from card payments.
- [Accept a WeChat Pay payment | Stripe Documentation](https://docs.stripe.com/payments/wechat-pay/accept-a-payment): WeChat Pay is a popular digital wallet in China that allows customers to pay for goods and services by scanning a QR code during checkout. It is a single-use payment method, and for integration, all line items in a Checkout Session must be in the same currency.
- [WeChat Pay payments | Stripe Documentation](https://docs.stripe.com/payments/wechat-pay): WeChat Pay, used by over 800 million users, is China's leading payment wallet within the WeChat super app. It enables Chinese consumers, overseas Chinese, and travelers to pay for goods and services across various categories on apps and websites.
- [Wero payments | Stripe Documentation](https://docs.stripe.com/payments/wero): Wero is a pan-European payment method allowing secure desktop and mobile transactions by connecting bank accounts to a Wero wallet. It is currently in private preview and supports Germany for EUR payments, with standard payout timing and customer-initiated payment confirmation.
- [Accept a Zip payment | Stripe Documentation](https://docs.stripe.com/payments/zip/accept-a-payment): Zip is a buy now, pay later payment method popular in Australia and the US, enabling customers to split purchases into installments. Customers authenticate on the Zip website, and payment success or failure is immediately notified. To accept Zip payments, your Checkout Session must use Australian Dollar (AUD) or United States Dollar (USD) currency.
- [Zip payments | Stripe Documentation](https://docs.stripe.com/payments/zip): Zip is a buy now, pay later payment method for customers in Australia and the US, allowing them to split purchases into multiple payments. Customers authorize payment plans on the Zip site, and Stripe receives funds upfront while the customer repays Zip over time. The payment method is available in AUD and USD and is customer-authenticated.
- [The Payment Records API | Stripe Documentation](https://docs.stripe.com/payments/payment-records): The Payment Records API helps maintain a unified history of all payments, whether processed through Stripe or third-party processors. It enables reporting off-Stripe payment results to Stripe for features like Subscriptions and Radar, and tracks complex payment flows like multi-capture. Payment Records serve as a system of record, especially when applications handle both on-Stripe and off-Stripe payments.
- [Recurring payments | Stripe Documentation](https://docs.stripe.com/recurring-payments): This guide explores Stripe's options for charging customers on a recurring basis, covering use cases, types of recurring payments, and supporting Stripe products. It helps businesses select the best approach for accepting regular payments, splitting purchases into installments, managing subscriptions, or collecting recurring donations.
- [Secure Remote Commerce program guide | Stripe Documentation](https://docs.stripe.com/secure-remote-commerce): Secure Remote Commerce (SRC) enables secure online payments by protecting payment information and allowing users to add cards from major networks like Visa and Mastercard. Currently, SRC is only available in the US and integrates with existing Stripe integrations by adding a specific script tag to your HTML document.
- [Industry metadata | Stripe Documentation](https://docs.stripe.com/industry-metadata): Industry metadata can be provided for travel and entertainment purchases using the Payment Intents API, especially for specific merchant category codes (MCCs). This feature, available in public preview, is required for compliance with card network rules and may improve authorization rates for certain transactions, including Klarna.
- [Upgrade your integration | Stripe Documentation](https://docs.stripe.com/payments/upgrades): Upgrading your Stripe integration can increase conversion rates and grant access to new features. Recommended upgrades include migrating from the Card Element to the Payment Element for a unified payment method experience and from Legacy Checkout to Checkout or Payment Links for enhanced features like dynamic payment methods.
- [Design a payments integration | Stripe Documentation](https://docs.stripe.com/payments/use-cases/get-started): This guide helps businesses choose the right Stripe payments integration by explaining options like Checkout for pre-built forms, Stripe Elements for customizable forms, and Mobile Elements for in-app payments. It also covers no-code solutions like Payment Links for accepting payments without a website.
- [Customized start of day | Stripe Documentation](https://docs.stripe.com/payouts/customized-start-of-day): Customized start of day allows users to set a specific time in their local timezone for automatic payouts, grouping payments processed within that day. This feature aids in payout reconciliation by aligning payouts with the user's timezone rather than UTC. It is available in several Asia-Pacific countries and can be configured in the Dashboard.
- [Receive payouts | Stripe Documentation](https://docs.stripe.com/payouts): Stripe facilitates receiving funds through payouts to your bank account, with availability timelines varying by industry and country. Initial payouts typically occur 7-14 days after the first payment, with subsequent payouts following your account's schedule. Bank account details can be added or updated in the Dashboard's Payout settings.
- [Institution support for Instant Payouts | Stripe Documentation](https://docs.stripe.com/payouts/instant-payouts-banks): Stripe supports Instant Payouts for eligible users in various countries including the US, Canada, UK, EU, Singapore, Australia, and more, requiring local currency for each transaction. The page provides a dropdown to check which specific institutions within each country support Instant Payouts for debit cards.
- [Instant Payouts with advance funding | Stripe Documentation](https://docs.stripe.com/payouts/instant-payouts-with-advance-funding): Instant Payouts with advance funding allow users to access pending balances through `advance` and `advance_funding` balance transactions. When an instant payout exceeds the available balance, funds are drawn from pending balances across multiple days, creating granular `advance_funding` transactions for accurate bookkeeping.
- [Instant Payouts for Stripe Dashboard users | Stripe Documentation](https://docs.stripe.com/payouts/instant-payouts): Instant Payouts enable Stripe Dashboard users to access their Stripe balance immediately after a successful charge, with funds typically settling within 30 minutes, even on weekends and holidays. This service incurs a fee per payout and is available in numerous countries, with funds from card payments available instantly and ACH debits after settlement.
- [Minimum balances for automatic payouts | Stripe Documentation](https://docs.stripe.com/payouts/minimum-balances-for-automatic-payouts): Minimum balances for automatic payouts allow you to retain a specified amount in your Stripe account to cover potential refunds, disputes, and fees. Automatic payouts will only disburse funds exceeding this minimum balance, helping to manage cash flow and prevent negative balances. This feature is not supported in Brazil, India, and Thailand.
- [Money management | Stripe Documentation](https://docs.stripe.com/manage-money): Stripe's money management features, accessible through the Dashboard, allow users to store funds, send and receive money, convert currencies, and spend from cards directly. The Balances page provides an overview of these capabilities for managing finances in multiple currencies.
- [Multi-currency settlement | Stripe Documentation](https://docs.stripe.com/payouts/multicurrency-settlement): Multi-currency settlement allows you to accept, settle, and pay out funds in multiple currencies without foreign exchange fees by configuring your account in the Dashboard. This feature is available in select locations including the US, EU, Australia, and Hong Kong, requiring a separate bank account for each settlement currency.
- [Next-day settlement | Stripe Documentation](https://docs.stripe.com/payouts/next-day-settlement): Next-day settlement makes funds from domestic Stripe transactions (excluding ACH direct debits) available in your balance on the following business day. If on an automatic daily payout schedule, eligible funds are sent to your bank account the next business day. This feature is currently available only for Stripe Dashboard users in the US.
- [Payout statement descriptors | Stripe Documentation](https://docs.stripe.com/payouts/statement-descriptors): Payout statement descriptors allow you to configure how Stripe payouts appear on bank statements, either at the account level for a consistent descriptor across all payouts or at the payout level for unique descriptors on manual payouts. While Stripe provides these descriptors, their display on bank statements is ultimately up to the beneficiary bank.
- [Payout Trace IDs | Stripe Documentation](https://docs.stripe.com/payouts/trace-id): The Payout Trace ID is a unique identifier generated by banking partners to track missing or delayed payouts. If a payout hasn't arrived within 10 business days, providing this ID to your bank can help locate it. For Connect users, Trace IDs can be accessed via the API to assist connected accounts with self-service investigations.
- [Payout reconciliation | Stripe Documentation](https://docs.stripe.com/payouts/reconciliation): Payout reconciliation in Stripe helps you match transactions to specific payouts by providing tools like the Stripe Dashboard, payout reports, and API access. For manual payouts, you are responsible for reconciling them against your transaction history.
- [Add additional metadata to payments | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/cookbooks/add-additional-metadata): This guide explains how to extend the Stripe module for Adobe Commerce to add custom metadata to each payment. It involves creating a new module and modifying specific configuration files to send additional payment information to Stripe.
- [Add custom events to Stripe webhooks | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/cookbooks/add-custom-events): This guide details how to extend the Stripe module for Adobe Commerce to include custom events in Stripe webhooks. It involves creating a new module and configuring dependency injection to add custom event triggers.
- [Disable specific shipping methods in Express Checkout modals | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/cookbooks/disable-express-checkout-payment-methods): This guide explains how to disable specific shipping methods, such as 'Pick up from store,' in the Express Checkout modal for Adobe Commerce. It involves creating a custom module to prevent unsuitable shipping options from appearing in the payment modal.
- [Enable manual capture | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/cookbooks/enable-manual-capture): This guide shows how to enable manual capture for eligible Stripe payment methods in Adobe Commerce without upgrading the Stripe module. It involves updating the payment method helper file directly by creating a custom module.
- [Add external payment methods to the payment form | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/cookbooks/external-payment-methods): This guide demonstrates how to display non-Stripe payment methods within the Stripe PaymentElement for Adobe Commerce. It covers redirecting customers to external URLs for payment collection and highlights the need for manual reconciliation as these transactions occur outside Stripe.
- [Hide the terms displayed in the PaymentElement form | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/cookbooks/hide-terms): This guide explains how to disable the display of terms text under the Stripe PaymentElement in Adobe Commerce. It involves creating a custom module to hide these terms, using a plugin to modify the PaymentElement's behavior.
- [Adobe Commerce Plugin cookbooks | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/cookbooks): This page lists integration recipes, or cookbooks, for Stripe's Adobe Commerce apps. These resources help users customize their integration with Stripe's payment and tax functionalities, covering various aspects from metadata to styling and testing.
- [Style the payment form at the checkout | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/cookbooks/style-payment-element): This guide explains how to customize the appearance of Stripe's PaymentElement on the Adobe Commerce checkout page using the Appearance API. It details how to modify themes and variables by defining a custom module that overrides these parameters.
- [Integrate a custom fee to the tax calculation | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/cookbooks/tax-additional-fees): This guide explains how to integrate custom fees into the tax calculation process for Adobe Commerce using Stripe Tax. It describes how to provide details of custom fees to the Stripe Tax module so they are included in the tax calculation requests.
- [Test why a specific payment method doesn't appear | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/cookbooks/test-specific-method): This guide demonstrates how to force-enable a specific payment method in Adobe Commerce to test why it might not be appearing at checkout. By making a small adjustment in the Stripe module, an error message will display, explaining the reason for the unavailability.
- [Stripe plugins for Adobe Commerce | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce): Stripe offers two plugins for Adobe Commerce: one for Payments, Billing, and Tax, and a standalone option for Tax. These plugins enable merchants to accept various payment methods, automate tax calculation, and manage reporting within their Adobe Commerce store.
- [Using the Adobe Commerce admin panel | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/payments/admin): This guide explains how to use the Adobe Commerce admin panel to configure the Stripe module, including issuing refunds. It details the process for both 'Authorize Only' and 'Authorize and Capture' payment actions, and how to perform live or offline refunds.
- [Configure the Stripe Plugin for Adobe Commerce | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/payments/configuration): This page provides instructions on configuring the Stripe plugin for Adobe Commerce, including setting up payment methods and API keys. It recommends installing the Adobe Commerce app from the Stripe App Marketplace for enhanced security with restricted keys.
- [Build a custom storefront | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/payments/custom-storefront): This guide explains how to build a custom storefront for Adobe Commerce using its REST or GraphQL APIs, supporting Stripe payment features. It details how to retrieve Stripe API keys and other initialization parameters for front-end integration.
- [Manage fraud and disputes | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/payments/fraud-disputes): This page describes how the Stripe Connector for Adobe Commerce provides fraud protection and dispute management through Stripe Radar. It explains how to leverage Radar for real-time fraud prevention, customize rules, and handle manual review workflows.
- [Stripe Payments, Billing, and Tax plugin for Adobe Commerce | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/payments): This guide introduces the Stripe Payments, Billing, and Tax plugin for Adobe Commerce, enabling merchants to accept online payments. It offers two checkout flows: embedding the Payment Element or redirecting to Stripe Checkout, both optimized for conversion and PCI compliance.
- [Use the Stripe app for Adobe Commerce (Magento 2) | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/payments/install): This guide covers the installation, upgrade, and uninstallation of the Stripe app for Adobe Commerce (Magento 2). It provides instructions for installing via the Adobe Marketplace or command line and setting up the module.
- [Use Stripe Billing to enable subscriptions for Adobe Commerce | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/payments/subscriptions): This guide explains how to use Stripe Billing to enable subscriptions for Adobe Commerce products. It details how to configure the Stripe plugin to turn products into subscriptions, manage recurring payments, and handle renewal orders.
- [Use Stripe Tax to automate tax calculation and reporting for Adobe Commerce | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/payments/tax): This guide explains how to use Stripe Tax with Adobe Commerce to automate tax calculation, collection, and reporting. It highlights Stripe Tax's dynamic nature, simpler configuration compared to the native engine, and continuous updates to tax rules.
- [Troubleshooting for Adobe Commerce | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/payments/troubleshooting): This page provides troubleshooting steps for the Stripe Plugin for Adobe Commerce, addressing common issues like installation errors related to Composer and caching problems after module upgrades. It guides users through resolving Composer package not found errors by ordering the module correctly and clearing cache directories. The documentation also outlines commands to run after clearing the cache to ensure changes are applied.
- [Standalone Tax Plugin for Adobe Commerce | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/adobe-commerce/standalone-tax): The Standalone Tax Plugin for Adobe Commerce by Stripe automates tax calculation, collection, and reporting for payments made through any supported Adobe Commerce payment method. It offers a simpler configuration than the native engine, dynamically updating tax rules without manual reconfiguration. Minimum system requirements include PHP 7.4 and Adobe Commerce 2.3.7 or later.
- [Install and configure the Stripe Tax app | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/bigcommerce/configuration): This guide explains how to install and configure the Stripe Tax app for BigCommerce to automatically calculate and collect sales tax, VAT, and GST. It details the process of installing the app from the BigCommerce marketplace and connecting a Stripe account. Users are then directed to configure tax settings in the Stripe Dashboard, including head office address, tax codes, and registrations.
- [Stripe Tax for BigCommerce | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/bigcommerce): The Stripe Tax app for BigCommerce automatically calculates and collects sales tax, VAT, and GST, applying the correct rates for all transactions. The app's pricing is usage-based, either through PAYG Stripe Tax API pricing or subscription-based options. Instructions are provided for installation, configuration, and testing the app's functionality.
- [Configure the app | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/cegid/configuration): This page details how to configure the Stripe app for Cegid after installation, focusing on setting up a payment method within the Cegid Y2 Back Office application. It outlines the necessary parameters for creating a payment method, including codes, descriptions, and categories, and specifies settings for peripheral registration and accounting. The configuration ensures the Stripe payment provider is correctly recognized and usable at the register.
- [Stripe app for Cegid | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/cegid/overview): The Stripe app for Cegid integrates Stripe Terminal into Cegid POS systems, enabling retailers to accept in-person payments. After setup, users can process on-site payments using Stripe Terminal devices, with all transactions linked directly to their Stripe account. Prerequisites include ordering an internet-connected Terminal device and creating a location for it in the Stripe account.
- [Install the app | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/cegid/installation): This guide provides instructions on how to download and install the Stripe app for Cegid, which facilitates in-person payments using Stripe Terminal. The installation process involves downloading an installer and running it, after which the app completes installation without further user action. Links to configuration and troubleshooting guides are also provided.
- [Troubleshoot the app | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/cegid/troubleshooting): This troubleshooting guide helps resolve issues with the Stripe app for Cegid and its integration. It addresses common problems such as missing SSL libraries by suggesting configuration changes in EPT settings. The guide also explains how to handle payments being reversed when exiting the payments screen and how to prevent duplicate payment references by enabling ReceiptRef.
- [Stripe app for Commercetools Connect | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/commercetools-connect): The Stripe app for Commercetools Connect allows integration of Stripe Payments with Commercetools, offering two app options for different needs: a pre-built checkout app and a custom checkout app. These integrations support features like automatic and manual capture/refunds, saved payment methods, and e-commerce workflows, with SAQ-A eligibility for PCI compliance. The app for Composable Commerce also supports subscriptions.
- [Install and configure the Stripe Payment app for Commercetools Checkout | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/commercetools-connect/install-and-configure-checkout): This document explains how to install and configure the Stripe Payment app for Commercetools Checkout, which provides a pre-built UI for secure payments. It outlines the prerequisites, including Stripe account details and Commercetools instance information, and guides users through selecting the app from the Commercetools Merchant Center. The configuration involves enabling payment methods and entering necessary environment variables and integration keys.
- [Install the app for Composable Commerce from your merchant center | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/commercetools-connect/install-and-configure): This guide details how to install the Stripe Payment Composable Connector for Commercetools from the merchant center to create a custom checkout workflow. It covers prerequisites like identifying the Commercetools organization and project, then guides users through selecting the app from the Connect Marketplace. Configuration involves providing environment variables and setting up a Stripe webhook.
- [Use Stripe Billing to enable subscriptions for Commercetools | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/commercetools-connect/use-subscriptions): This guide explains how to use Stripe Billing to enable subscriptions for Commercetools products via the Composable Commerce app. It covers defining product attributes and variants in the Commercetools merchant center to register recurring payments through Stripe. The system handles subscription management, payment collection, and automatically creates new orders for renewals, recalculating shipping and tax.
- [Stripe Accelerator apps for Guidewire Insurance platform | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/guidewire): Stripe Accelerator apps for Guidewire integrate Stripe's payment processing into Guidewire BillingCenter and ClaimCenter. These apps are available on the Guidewire Marketplace and support modern payment methods and workflows for the insurance platform. System requirements include Guidewire Platform version 10.x or higher and a Stripe account, with installation and configuration involving API keys from the Stripe Dashboard.
- [Use apps from Stripe | Stripe Documentation](https://docs.stripe.com/use-stripe-apps): This page provides an overview of using apps from Stripe to unify business software, connecting Stripe to e-commerce, ERP, POS, or CRM solutions. It highlights various Stripe-built apps for platforms like Adobe Commerce, Commercetools, and Shopify, as well as apps for in-person payments with Oracle Opera and Cegid. Information on partner apps is available through the Stripe App Marketplace.
- [Configure the Mirkal app | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/mirakl/configuration): This guide explains how to configure the Mirakl app for Stripe, which manages business payouts and tax calculations for Mirakl-built marketplaces. It details preparing integration variables in a `.env` file, including general settings like API keys and database URLs, and onboarding settings such as redirect URLs. The configuration ensures secure and efficient marketplace operations.
- [Stripe app for Mirakl | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/mirakl): The Stripe app for Mirakl is designed for Mirakl marketplaces, supporting various payment methods, B2C and B2B transactions, and multi-seller orders with automated payouts. Setting up involves registering for Stripe, implementing payment methods, activating Connect, configuring branding, and installing the app. The process includes onboarding sellers, testing workflows, and going live.
- [Install the Mirakl app | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/mirakl/install): This guide details the installation requirements and process for the Mirakl app for Stripe, which supports PHP 7.3+, PostgreSQL, and a web server with SSL/TLS. It provides instructions for using Docker or Composer, including cloning the app, installing dependencies, configuring the `.env` file, and running database migrations. The guide also covers updating supervisor and the job scheduler for worker processes.
- [Onboard sellers | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/mirakl/onboarding-sellers): This page describes how to onboard sellers using the Stripe Mirakl app, which supports Express or Custom Stripe accounts for the transfers capability. The workflow begins with new shop creation in Mirakl, where the plugin adds an onboarding link for sellers to complete KYC/KYB on Stripe. It also outlines how to initiate onboarding outside of Mirakl using an API request to map Stripe accounts with Mirakl shops.
- [Payments and payouts using the Mirakl app | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/mirakl/payments): This guide covers accepting payments and managing payouts using the Stripe Mirakl app, categorizing payment methods into seven families. It emphasizes using the app for splitting funds based on Mirakl orders and avoiding Connect charge types. The process includes creating payments, handling different payment methods like cards and bank redirects, and setting capture methods for authorization.
- [Mirakl reference | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/mirakl/reference): This reference page details the default settings and commands for Mirakl app events, including onboarding, payment validation, payment splitting, refunds, and payouts. It specifies default and recommended frequencies for scheduled jobs, such as fetching new Mirakl shops for onboarding or validating payments on Stripe. The page also covers alerting for failed operations.
- [Configure taxes with Stripe and NetSuite | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/configure-taxes): This page explains how to configure taxes when using Stripe with NetSuite. It outlines options for tax calculation, including using Stripe Tax automatically, creating custom tax rates, or calculating taxes outside of Stripe. Key considerations involve determining the payment system and tax application based on location.
- [Stripe credit notes and NetSuite credit memos | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/credit-notes-credit-memos): This document details how the Stripe Connector for NetSuite automates the creation of credit memos in NetSuite for Stripe credit notes. It supports handling refunds, discounts, and revenue recognition, allowing for adjustments to invoice amounts. Credit notes can be applied to open or paid invoices to decrease the amount due.
- [Custom payment application | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/custom-payment-application): This page describes how to customize payment recording and application within the Stripe Connector for NetSuite. It allows reconciliation of Stripe payment activity with NetSuite using Stripe metadata, invoices for payments, and connector add-ons. Stripe metadata can link Stripe objects to NetSuite records for accurate representation.
- [NetSuite customer payment page | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/customer-payment-page): This page explains how to use the customer payment page feature of the Stripe Connector for NetSuite. It enables customers to make payments towards their NetSuite balance, which can be applied to multiple invoices. The connector automatically sets the amount due but allows customers to adjust it, with automated payment processing and deposit automation included.
- [Deposit automation | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/deposit-automation): This document covers deposit automation within the Stripe Connector for NetSuite, which streamlines the bank reconciliation process. The connector creates bank deposits in NetSuite for Stripe payouts, automates fee calculation, and manages refunds and disputes. This reduces manual work by consolidating transactions into a single deposit record for matching against bank statements.
- [Troubleshoot the connector | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/error-resolution): This guide provides instructions for troubleshooting errors encountered with the Stripe Connector for NetSuite. It helps identify and resolve issues related to syncing records or loading payment pages. The document includes a table detailing common data errors, their descriptions, and suggested resolutions for syncing records from Stripe to NetSuite.
- [Field mappings | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/field-mappings): This page explains how to use field mappings in the Stripe Connector for NetSuite to customize data synced to NetSuite records. Field mappings allow for additional reporting, categorization, or the inclusion of required fields not present in Stripe. Both field defaults (static values) and dynamic field mappings can be configured within the connector app.
- [Stripe and NetSuite fields and references | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/fields-references): This page outlines the correlation between Stripe records and NetSuite records when using the Stripe Connector for NetSuite. It maps Stripe objects like charges, credit notes, and invoices to their corresponding NetSuite records such as customer payments, credit memos, and invoices. The page also details how NetSuite record IDs and Stripe IDs are stored and referenced, including the use of metadata for identification.
- [Stripe Connector for NetSuite | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/overview): This page provides an overview of the Stripe Connector for NetSuite, which automates accounting workflows and eliminates manual work. It offers an automated testing system for NetSuite features and secure communication via HTTPS. The connector supports various workflow automations, including invoice, customer payment, and deposit automation.
- [Stripe Billing and Invoicing automation | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/invoice-automation): This document describes the invoice automation feature of the Stripe Connector for NetSuite, which syncs Stripe invoices into NetSuite. It includes details like credit notes, discounts, and taxes, allowing for complete accounting workflows within Stripe without manual reconciliation. The process creates or links NetSuite customers and invoices when Stripe invoices are generated.
- [Install the NetSuite connector invoice payment link | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/invoice-payment-link/installation): This page explains how to self-serve onboard and set up the free version of the Stripe Connector for NetSuite to integrate Stripe payment links. This version allows for processing payments from NetSuite invoices via Stripe Checkout without syncing data to NetSuite. It requires a Stripe account, a NetSuite account, and administrative access to both.
- [NetSuite invoice payment link | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/invoice-payment-link/overview): This page details the NetSuite invoice payment link feature of the Stripe Connector for NetSuite. It enables the creation of a payment link for each NetSuite invoice, allowing customers to pay using Stripe Checkout with enabled payment methods. This free, self-serve version processes payments and provides a customizable payment link that can be integrated into customer communications.
- [Set up payment method rules | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/invoice-payment-link/payment-method-rules): This page explains how to set up payment method rules for the Stripe Connector for NetSuite's invoice payment link. These rules control the visibility of payment methods based on order amount or buyer location, excluding cards. Configuration is done within the Stripe Dashboard under Settings > Payments, allowing customization of transaction limits and country/currency restrictions.
- [NetSuite invoice payment page | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/invoice-payment-page): This page describes the NetSuite invoice payment page feature of the Stripe Connector for NetSuite. It generates a payment page for each NetSuite invoice, allowing customers to pay using a Stripe payment flow with enabled methods. The process includes automated payment processing, cash application, and deposit automation, syncing payments back into NetSuite against the invoice.
- [Migrate the SuiteSync NetSuite Auto Pay workflow | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/migration/auto-pay-instructions): This page provides instructions for migrating the SuiteSync NetSuite Auto Pay workflow to the Stripe Connector for NetSuite. It offers guidance for users with active SuiteSync integrations to transition to the new connector. Personalized migration instructions are available by logging into a Stripe account.
- [Configure your Stripe Connector for NetSuite App | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/migration/configure-app): This guide explains how to configure the Stripe Connector for NetSuite App after migrating from SuiteSync. It details setting up SuiteSync configurations within the Connector App in a test environment before moving to a live environment. Assistance is available through Stripe support or implementation partners.
- [Migrate the legacy SuiteSync Customer Portal Link | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/migration/customer-payment-page): This page provides guidance on migrating the legacy SuiteSync Customer Portal Link workflow to the Stripe Connector for NetSuite's Customer Payment Page. It offers instructions for users with active SuiteSync integrations to transition to the new connector. Personalized migration instructions are available by logging into a Stripe account.
- [Migrate the SuiteSync NetSuite-Initiated Refunds workflow | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/migration/netsuite-initiated-refunds): This page details how to migrate the SuiteSync NetSuite-Initiated Refunds workflow to the Stripe Connector for NetSuite. It offers guidance for users with active SuiteSync integrations to transition to the new connector. Personalized migration instructions are available by logging into a Stripe account.
- [Migrate the SuiteSync Paid Out of Band workflow | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/migration/paid-out-of-band): This page provides instructions for migrating the SuiteSync Paid Out of Band workflow to the Stripe Connector for NetSuite. It offers guidance for users with active SuiteSync integrations to transition to the new connector. Personalized migration instructions are available by logging into a Stripe account.
- [Migrate from SuiteSync to the Stripe Connector for NetSuite | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/migration/get-started): This page serves as an introduction to migrating from SuiteSync to the Stripe Connector for NetSuite, explaining that the connector is a "v2" built on Stripe's infrastructure. It outlines the migration process as a re-implementation of existing SuiteSync configurations into the connector environment. The migration is largely self-serve, with guidance and support available.
- [Multiple currencies with Stripe and NetSuite | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/multiple-currencies): The Stripe Connector for NetSuite supports multiple currencies and can automatically reconcile payments requiring currency conversion. You can either use a single Stripe account for multiple currencies or multiple Stripe accounts for different subsidiaries to avoid conversion fees.
- [Multiple NetSuite subsidiaries | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/multiple-subsidiaries): The Stripe Connector for NetSuite accommodates businesses with multiple subsidiaries and various currencies, managing currency conversion and bank reconciliation. It supports configurations like one Stripe account with multiple settlement currencies or multiple Stripe accounts linked to different NetSuite subsidiaries, but a single Stripe account cannot be used with multiple NetSuite subsidiaries.
- [Prepare for onboarding | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/onboarding): To onboard with the Stripe Connector for NetSuite, you must collaborate with an official implementation partner and prepare your Stripe and NetSuite accounts. Key preparation steps include activating your Stripe account, setting up a NetSuite test account, and creating a dedicated NetSuite user for the connector.
- [Migrate the SuiteSync eCommerce and third-party billing workflows | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/migration/payment-linker-instructions): This document provides instructions for migrating SuiteSync eCommerce and third-party billing workflows to the Stripe Connector for NetSuite. It guides users on setting up Payment Linker workflows within the Stripe Connector for NetSuite, particularly for those with active SuiteSync integrations.
- [Revenue recognition | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/revenue-recognition): The Stripe Connector for NetSuite syncs subscription invoice data to NetSuite, enabling revenue recognition calculations by passing subscription period start and end dates. It supports NetSuite Advanced Revenue Management (ARM) and automatically applies revenue recognition rules when creating items and invoices.
- [Stripe charges in NetSuite | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/stripe-charges-netsuite): The Stripe Connector for NetSuite automates the reconciliation of Stripe charges and payments within NetSuite. It creates corresponding payment records in NetSuite, applying them to invoices where applicable, and includes transfer and platform fee details for Stripe Connect charges in the memo field.
- [Stripe Connect in NetSuite | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/stripe-connect-netsuite): The Stripe Connector for NetSuite supports Stripe Connect platforms and connected accounts, automatically reconciling Connect-specific activities like transfers and application fees. It provides visibility into these transactions within NetSuite for both platforms and connected accounts, including details in the memo field for charges, refunds, and disputes.
- [Install and configure the Stripe Connector Add-ons bundle | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/migration/stripe-connector-add-ons): This page details the prerequisite configuration steps for installing and using the Stripe Connector Add-ons bundle. It is intended for users with an active SuiteSync integration who need to migrate workflows requiring the Add-ons bundle.
- [Stripe customers and customer balances in NetSuite | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/stripe-customers-netsuite): The Stripe Connector for NetSuite automatically syncs Stripe customers and their associated balances into NetSuite as customer and invoice records. It offers options to sync new Stripe customers as new NetSuite customers, link them to existing NetSuite customers, or associate all customers with a single global customer record.
- [Stripe disputes in NetSuite | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/stripe-disputes-netsuite): The Stripe Connector for NetSuite automatically creates corresponding NetSuite objects for Stripe disputes (chargebacks) as soon as they occur. It records dispute fees as a cash-back line item, typically posting to the same account as credit card processing fees, and creates a customer refund and a credit memo if the charge was applied to an invoice.
- [Stripe invoices in NetSuite | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/stripe-invoices-netsuite): The Stripe Connector for NetSuite automatically syncs invoices generated from Stripe Billing subscriptions or Stripe Invoicing into NetSuite. It creates NetSuite invoices to represent subscription periods and handles various invoice statuses like paid, unpaid, or refunded by creating corresponding NetSuite customer payments, credit memos, or refunds.
- [Stripe payouts in NetSuite | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/stripe-payouts-netsuite): The Stripe Connector for NetSuite automates the reconciliation of Stripe payouts to NetSuite bank deposits, including fees and currency conversions. Each Stripe transaction results in a NetSuite bank deposit, with fees and reversals recorded as line items, ensuring the deposit amount matches bank statements.
- [Stripe prices and coupons in NetSuite | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/stripe-prices-coupons-netsuite): The Stripe Connector for NetSuite syncs Stripe products, prices, and coupons into NetSuite items, price levels, or one-time items for miscellaneous charges. Users manage item configurations like revenue recognition and reporting in NetSuite, with options for representing each Stripe price as a unique NetSuite item for detailed reporting.
- [Stripe refunds in NetSuite | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/stripe-refunds-netsuite): The Stripe Connector for NetSuite automates the reconciliation of Stripe refunds, syncing them into NetSuite and representing them based on their payment status. It creates credit memos and customer refunds to represent refunds for charges applied to invoices, or directly against customer payments for non-invoice-related charges.
- [Sync Stripe data to NetSuite | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/netsuite/sync-data): The Stripe Connector for NetSuite synchronizes data from Stripe to NetSuite by processing various webhook events. Successful charge events create CustomerPayments and NetSuite invoices, while refunded charges generate CreditMemos and CustomerRefunds, and disputes are noted on the payout record.
- [Configure the app | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/oracle/opera/configuration): This guide explains how to configure the Stripe app for Oracle Opera after installation to integrate with your Stripe Terminal. It details how to edit the appsettings.json file to set parameters such as allowed hosts, listen host, and server certificate paths for secure and proper operation.
- [Stripe app for Oracle Opera | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/oracle/opera/overview): The Stripe app for Oracle Opera integrates Stripe Terminal into Oracle Opera property management systems, enabling hotels to accept in-person payments. After setup, Stripe Terminal devices process payments directly linked to the Stripe account, requiring an internet-connected Terminal device and server-driven integration setup.
- [Install the app | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/oracle/opera/installation): To install the Stripe app for Oracle Opera, download the installer and run the setup wizard, accepting the license agreement and choosing an installation directory. The process involves running the installer and completing the wizard to integrate Stripe Terminal for in-person payment collection.
- [Troubleshoot your installation | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/oracle/opera/troubleshooting): Troubleshooting the Stripe app for Oracle Opera installation involves uninstalling the app, deleting cached data from the installation folder, and then reinstalling it. This process ensures a clean setup to resolve any installation failures.
- [Access the app web interface | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/oracle/opera/web-interface): After configuring the Stripe app for Oracle Opera, access its web interface at https://127.0.0.1:8081 using default admin credentials. It is recommended to change the default admin password and create new super admin users for enhanced security and management of the operating environment.
- [Configure the app | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/oracle/simphony/configuration): This page details how to configure the Stripe app for Oracle Simphony after installation. It guides users through signing into the Simphony Enterprise Management Console, editing payment driver settings, and updating the application.yaml file with the correct host and port information.
- [Install the app | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/oracle/simphony/installation): This page explains the process of downloading and installing the Stripe App for Oracle Simphony. It covers running the setup wizard, accepting the license agreement, selecting installation folders, and completing the installation process.
- [Stripe app for Oracle Simphony | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/oracle/simphony/overview): This page provides an overview of the Stripe app for Oracle Simphony, enabling retailers to accept in-person payments via Stripe Terminal. It outlines key features like processing sales, issuing refunds, and collecting customer information, along with supported card brands and prerequisites for setup.
- [Access the app web interface | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/oracle/simphony/web-interface): This page describes how to access and manage the web interface for the Stripe App for Oracle Simphony. It provides the URL, default login credentials, and instructions for changing the admin password and creating new super admin users to ensure secure access.
- [Install the Oracle Xstore app | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/oracle/xstore/installation): This page outlines the steps to download and install the Stripe App for Oracle Xstore. It details running the setup wizard, accepting the license agreement, choosing installation directories, and completing the installation for integrating Stripe Terminal payments.
- [Stripe app for Oracle Xstore | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/oracle/xstore/overview): This page introduces the Stripe App for Oracle Xstore, which allows retailers to process in-person payments using Stripe Terminal within their Xstore point-of-sale system. It highlights functionalities such as processing transactions, issuing refunds, and supported card brands, along with necessary prerequisites.
- [Access the app web interface | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/oracle/xstore/web-interface): This page explains how to access the web interface for the Stripe App for Oracle Xstore after configuration. It provides the URL, default admin credentials, and guidance on managing users, changing passwords, and creating super admin accounts for security.
- [Install and configure the Stripe module for PrestaShop | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/prestashop/configuration): This page details the installation and configuration of the Stripe module for PrestaShop. It guides users to install the app from the Stripe App Marketplace to obtain secure keys and then configure it within their PrestaShop environment.
- [Stripe module for PrestaShop | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/prestashop): This page provides an overview of the Stripe module for PrestaShop, enabling integration with Stripe Elements to accept over 25 payment methods. It highlights features like built-in conversion logic, global payment support, and the ability to authorize and capture payments separately.
- [Stripe Adapter for SAP Digital Payments add-on | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/sap-digital-payments): This page describes the Stripe Adapter for SAP Digital Payments add-on, which integrates Stripe payment capabilities into SAP. It supports over 40 payment methods, works with SAP S/4 HANA, and simplifies automatic bank reconciliation for online sales and accounts receivable.
- [Stripe Subscriptions for Shopify | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/shopify-subscriptions): This page explains how to install and configure the Stripe Subscriptions app for Shopify to manage recurring payments. It covers creating subscription plans, offering discounts, and allowing customers to manage their subscriptions, with all data accessible via Shopify admin and Stripe Dashboard.
- [Stripe Tax for Shopify | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/shopify): This page details the Stripe Tax for Shopify integration, which automatically syncs Shopify transactions for unified threshold monitoring, reporting, and filing. It calculates tax obligations, assigns product tax codes, and consolidates sales data into Stripe Tax reports.
- [Install and configure the Stripe app for Shopware 6 | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/shopware6/configuration): This page guides users on installing and configuring the Stripe app for Shopware 6 to integrate Stripe Elements for payments. It covers installing the connector from the Shopware Account and adding Stripe as a payment method in the administration panel.
- [Stripe app for Shopware 6 | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/shopware6): This page provides an overview of the Stripe app for Shopware 6, enabling the acceptance of over 25 payment methods through Stripe Elements. It highlights features such as built-in conversion logic, global payment support, and responsive checkout across devices.
- [Use the Shopware 6 app | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/shopware6/user-guide): This page explains how to use the Stripe app for Shopware 6, covering payment management, refunds, and troubleshooting. It details how to view payment information at the order level, cancel uncaptured payments, and process full refunds for orders.
- [Install and configure the Stripe Tax Extension | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/woocommerce/configuration): This page details the installation and configuration of the Stripe Tax Extension for WooCommerce. It guides users to connect their Stripe account, install the extension, and configure tax settings to automatically calculate sales tax, VAT, and GST.
- [Stripe Tax Extension for WooCommerce | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/woocommerce): This page provides an overview of the Stripe Tax Extension for WooCommerce, which automatically calculates and applies sales tax, VAT, and GST. It covers understanding tax registration requirements, automating tax collection, and reconciling transactions for filing.
- [Test the Stripe Tax Extension | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/woocommerce/troubleshooting): This page explains how to test the Stripe Tax Extension for WooCommerce and troubleshoot issues. It provides examples for testing tax calculation through manual order creation and the checkout page, noting that testing incurs fees.
- [Handling customer deletion requests | Stripe Documentation](https://docs.stripe.com/privacy/deletion-requests): This page describes Stripe's tools for handling customer deletion requests, focusing on redaction and deletion capabilities. Redaction permanently removes personal data from view in the Dashboard and API, while deletion is feature-specific.
- [Complete a redaction job | Stripe Documentation](https://docs.stripe.com/privacy/redaction/example): This page provides an example of completing a redaction job using the RedactionJob object to remove a customer's personal data from the Stripe API and Dashboard. It outlines the process of creating a job, validating objects, and the scope of data that is identified for redaction.
- [Redaction API integration guide | Stripe Documentation](https://docs.stripe.com/privacy/redaction-integration): The Redaction API allows users to programmatically redact personal data from Stripe resources to comply with data privacy requests. Redaction is irreversible and replaces personal data with placeholders, making the object unusable for future actions. The process involves identifying objects, calling the /redact API endpoint, and can take up to 7 days to complete.
- [Redact personal data | Stripe Documentation](https://docs.stripe.com/privacy/redaction): Redaction jobs enable the removal of user data from Stripe for consumer deletion requests, redacting objects containing personal information and their related data. This feature is in public preview and requires creating a redaction job with object identifiers, validating it, and then running it. Redacted objects cannot be updated or reused, and will display placeholders for personal data when accessed.
- [Create and send a quote | Stripe Documentation](https://docs.stripe.com/quotes/create): A quote is a tool to present prospective or existing customers with the costs of products and services, either for a one-off invoice or a subscription. In the Stripe Dashboard, users can create a quote by adding a customer, selecting items, setting an expiration date, and then finalizing it. Once finalized, the quote can be downloaded as a PDF and sent to the customer for review.
- [How quotes work | Stripe Documentation](https://docs.stripe.com/quotes): Quotes provide customers with a price estimate for goods or services, combining various line items, discounts, and taxes. Quotes can be converted into recurring subscriptions or one-time invoices upon customer acceptance. The quote lifecycle includes statuses such as draft, open, accepted, and canceled, with specific actions available at each stage.
- [Renegotiate a quote | Stripe Documentation](https://docs.stripe.com/quotes/clone): Finalized quotes can be modified by duplicating them into new drafts, allowing for updates like applying discounts or fees. Open quotes can also be revised directly through the Dashboard or API. Duplicating a quote is possible for draft, open, or accepted states, creating a new draft with the original details for further editing.
- [Customer abuse evaluation | Stripe Documentation](https://docs.stripe.com/radar/customer-abuse): The Customer Account Evaluation API offers risk intelligence for registration and login flows to detect multi-accounting and account sharing. It provides risk scores before payment collection, enabling informed decisions about account access. The process involves creating a Radar Session to capture device metadata, requesting an evaluation, and reporting the outcome to Stripe.
- [Radar | Stripe Documentation](https://docs.stripe.com/radar): Stripe Radar protects businesses against fraud by evaluating transactions in real-time using AI algorithms. It offers customization through Radar for Fraud Teams and protection against transaction and account risk with Radar for Platforms. Radar screens various payment methods and provides features like AI-based fraud detection and custom rules.
- [Lists | Stripe Documentation](https://docs.stripe.com/radar/lists): Stripe Radar for Fraud Teams allows the creation of custom lists of information, such as trusted customer IDs or fraudulent email addresses, to be used in rules for blocking or allowing payments. These lists streamline rule management by grouping similar items, and Stripe provides default lists for various payment methods to aid in initial setup.
- [Radar for local payment methods | Stripe Documentation](https://docs.stripe.com/radar/local-payment-methods): Radar for local payment methods extends Radar's risk evaluation capabilities to a wider range of payment types beyond cards and ACH. This private preview feature offers fraud prevention tools like default block/allow lists, custom rules, backtesting, and analytics across supported payment methods, starting with Klarna. It allows businesses to offer more payment choices while maintaining fraud protection.
- [Optimize fraud signals | Stripe Documentation](https://docs.stripe.com/radar/optimize-fraud-signals): To maximize Stripe Radar's effectiveness, it's recommended to provide relevant data that supports accurate risk assessment without hindering the checkout experience. The completeness of fraud signals depends on the integration type, with integrations like Payment Links and Checkout offering excellent signal completeness. Adding customer and client signals to objects can improve fraud detection when direct API integration is used.
- [How Radar works | Stripe Documentation](https://docs.stripe.com/radar/how-radar-works): Stripe Radar provides real-time fraud protection using AI algorithms to assess transaction risk, with customization options available through Radar for Fraud Teams. Radar for Platforms offers protection against both transaction and account risk. It evaluates various payment attempt types and payment methods, charging a fee per evaluated transaction, with an exception for Stripe Billing users.
- [Fraud alerts | Stripe Documentation](https://docs.stripe.com/radar/analytics/fraud-alerts): Fraud alerts notify users via email and Dashboard notifications when Stripe detects unusual fraud patterns, such as significant shifts in Radar risk scores. These alerts help mitigate risks like lost revenue and increased dispute fees by enabling quick responses. The notifications provide a link to a dedicated investigation page for reviewing details and taking action.
- [Fraud insights | Stripe Documentation](https://docs.stripe.com/radar/analytics/fraud-insights): Fraud insights, available with Radar for Fraud Teams, allow businesses to visualize fraud trends, identify impactful Radar attributes, and inspect high-level patterns. Users can customize the data displayed by selecting time periods and applying filters to tailor their fraud fighting strategy. These insights help in adjusting Radar rules or risk controls based on discovered patterns.
- [Radar analytics center | Stripe Documentation](https://docs.stripe.com/radar/analytics): The Radar analytics center in the Dashboard helps analyze and understand fraud for a business by providing reports on blocked fraud and key metrics over time. Using Fraud Insights, Sigma, or Data Pipeline, users can improve fraud management, identify fraudulent payments, and gain a deeper customer understanding. The center offers enhanced data analysis and comparison to other businesses.
- [Radar scores for multiple payment processors | Stripe Documentation](https://docs.stripe.com/radar/multiprocessor): Radar scores for multiple payment processors allow users to apply Stripe's risk evaluation expertise to externally processed payments by requesting a risk score and recommendation. Prerequisites include creating a tokenized PaymentMethod, a Radar Session token, and collecting customer email. This enables real-time risk evaluation at any point in the payment lifecycle.
- [Radar for Platforms | Stripe Documentation](https://docs.stripe.com/radar/radar-for-platforms): Radar for Platforms provides Connect platforms with tools to reduce buyer and connected account risk, including identifying financial risk with machine learning scores and custom rules. It helps investigate connected accounts, gather additional information, and take action on transactions and accounts. Risk levels range from normal to highest, indicating probability of financial loss due to fraud or credit risk.
- [Provide Radar additional fraud data | Stripe Documentation](https://docs.stripe.com/radar/radar-session): Using Radar Sessions allows for the capture of critical browser metadata and device details to improve Radar's fraud score accuracy, especially when card tokenization is handled externally. This metadata includes IP address, browser, and device information. Preferred Stripe integrations automatically handle secure payment information collection and provide better fraud protection.
- [Review uncaptured payments | Stripe Documentation](https://docs.stripe.com/radar/reviews/auth-and-capture): For integrations using auth and capture, reviews allow for manual inspection of uncaptured payments before funds are transferred. The Dashboard displays a 'Capture' button for approved reviews, and canceling an uncaptured payment releases authorization without creating a Refund object. The API can be used to automatically capture payments not placed in review or to capture approved payments.
- [Review card payments | Stripe Documentation](https://docs.stripe.com/radar/reviews): Reviews supplement Stripe's automated fraud prevention by providing a manual inspection layer for card payments, allowing users to examine transactions with elevated fraud risk, unusual origins, or large amounts. The review queue in Radar for Fraud Teams enables targeted examination of suspicious payments based on specified criteria.
- [Risk insights | Stripe Documentation](https://docs.stripe.com/radar/reviews/risk-insights): Risk insights, available with Stripe Radar for Fraud Teams, offer a view into the signals powering Radar's AI model for determining payment risk scores and levels. This feature includes information about the customer, such as email address success rates and matching cardholder names, as well as geography-based data like billing and IP address locations.
- [Risk evaluations | Stripe Documentation](https://docs.stripe.com/radar/risk-evaluation): Stripe Radar uses an adaptive AI model to evaluate the risk level of each payment in real time, utilizing hundreds of signals and network data to predict fraudulent transactions. This model learns from new patterns and user feedback, but specialized models are used for risk settings and controls to balance authorization and fraud.
- [Risk setting and risk controls | Stripe Documentation](https://docs.stripe.com/radar/risk-settings): Stripe Radar allows businesses to choose a risk setting that automatically adjusts fraud protection thresholds based on their needs and tolerance for risk. These settings use risk controls to block payments likely to result in fraudulent disputes or early fraud warnings, balancing fraud protection with revenue.
- [Dispute resolution rules | Stripe Documentation](https://docs.stripe.com/radar/rules/disputes): Stripe Radar enables automatic resolution of specific disputes by creating dispute resolution rules. These rules evaluate incoming disputes against defined criteria, and if a match is found, the dispute is automatically resolved with a specified action, such as a refund.
- [Fraud prevention rules | Stripe Documentation](https://docs.stripe.com/radar/rules): Fraud prevention rules in Stripe Radar allow businesses to take automated actions when payments meet certain criteria, helping to protect against fraud risk. Businesses can use built-in rules or create custom rules based on specific business logic to request authentication, allow, block, or review payments.
- [Rules reference | Stripe Documentation](https://docs.stripe.com/radar/rules/reference): Stripe Radar processes rules based on their action type: Request 3DS, Allow, Block, or Review, with a specific prioritization order. When a payment matches a rule's criteria, Radar takes the defined action, and rules of the same action type are not ordered.
- [Supported attributes | Stripe Documentation](https://docs.stripe.com/radar/rules/supported-attributes): Stripe Radar supports a variety of attributes for writing rules, including payment method-specific attributes like card BINs and SEPA debit fingerprints, as well as general attributes like 3D Secure status and transaction amounts. These attributes allow for precise criteria to be set for fraud prevention rules.
- [Testing Stripe Radar | Stripe Documentation](https://docs.stripe.com/radar/testing): Stripe Radar provides test credit card numbers to simulate payments with specific risk levels in a sandbox environment, allowing users to test their fraud prevention strategies. Before implementing rules, users can also review historical live payments that match the rule criteria to estimate their impact.
- [Bank reconciliation | Stripe Documentation](https://docs.stripe.com/bank-reconciliation): The Bank reconciliation report in Stripe helps users reconcile Stripe payouts with cash in their bank accounts, tracking funds from Stripe to their bank. This report provides a monthly summary of account activity, helps track realized cash, and tracks payouts and their reconciliation status with bank deposits.
- [Refund and cancel payments | Stripe Documentation](https://docs.stripe.com/refunds): Stripe allows users to cancel payments before completion at no cost or refund all or part of a successful payment, which may incur a fee. Refunds are processed using the available Stripe balance, and successful refunds are reflected on the customer's bank statement.
- [Product release phases | Stripe Documentation](https://docs.stripe.com/release-phases): Stripe uses product release phases—Private preview, Public preview, and General availability (GA)—to describe the availability of features in its API and Dashboard. These phases allow for incremental feature releases and improvements based on user feedback.
- [Integrate an accounting tool | Stripe Documentation](https://docs.stripe.com/accounting-integrations): Stripe facilitates integration with accounting tools like QuickBooks and NetSuite, allowing users to export financial data such as payments, refunds, fees, and payouts. These integrations automate bookkeeping and keep financial data updated, often by creating specific Stripe-prefixed accounts in the accounting software.
- [Fees report | Stripe Documentation](https://docs.stripe.com/reports/all-fees): The Fees report in Stripe provides a detailed list of all fees charged by Stripe, networks, and external partners, impacting your Stripe balance, Fee credits balance, and Financial Accounts. It can be viewed as a summary or an itemized report at the transaction level and is accessible via the Dashboard, Reporting API, or Sigma.
- [How the Reports API works | Stripe Documentation](https://docs.stripe.com/reports/api): The Reports API allows users to access Stripe's financial reports programmatically, enabling automated reconciliation workflows. Reports available in the Dashboard, such as Balance, Payout reconciliation, and Fees reports, can also be retrieved via the API.
- [Balance transaction types | Stripe Documentation](https://docs.stripe.com/reports/balance-transaction-types): Balance transactions represent all types of funds moving into or out of a Stripe account's balance, serving as a recommended starting point for reporting. Each balance transaction includes a source field linking it to the related Stripe object, and the reporting_category field classifies transactions for accounting purposes.
- [Balance summary report | Stripe Documentation](https://docs.stripe.com/reports/balance): The Balance summary report acts like a bank statement, providing an itemized CSV export of your complete transaction history to reconcile your Stripe balance monthly. It details your starting and ending balance, a breakdown of transactions by reporting category (excluding payouts), and information on payouts made.
- [Create custom columns using metadata | Stripe Documentation](https://docs.stripe.com/reports/metadata): Custom columns can be added to Stripe Financial Reports using metadata, which consists of key-value pairs associated with objects or transactions. This allows for storing and retrieving supplementary information, facilitating targeted reporting, reconciliation with internal systems, and advanced data querying.
- [Reports for multiple accounts | Stripe Documentation](https://docs.stripe.com/reports/multiple-accounts): Reports for multiple Stripe accounts can be accessed and downloaded, including a consolidated report for all accounts within an organization. Users can filter these reports by organization, specific accounts, time period, and currency to view aggregated financial data.
- [How report configuration works | Stripe Documentation](https://docs.stripe.com/reports/options): Report configuration options in Stripe allow users to customize financial reports by selecting data filters such as date range, time zone, and connected accounts. Reports are computed daily and typically available within 12 hours, with specific SLAs indicating download availability.
- [Payout reconciliation report | Stripe Documentation](https://docs.stripe.com/reports/payout-reconciliation): The Payout reconciliation report helps users match payouts received in their bank account with the batches of transactions they settle, optimized for automatic payouts. It provides a breakdown of automatic payouts and the transactions grouped by reporting category within those settlement batches.
- [Fees report type | Stripe Documentation](https://docs.stripe.com/reports/report-types/fees): The Fees report type provides a list of all fees taken from your Stripe balance, Fee credits balance, and Financial Accounts, including those from Stripe, networks, and external partners. It can be viewed as a summary or an itemized report at the transaction level and is accessible via the Dashboard or API.
- [Balance report type | Stripe Documentation](https://docs.stripe.com/reports/report-types/balance): The Balance report provides a complete transaction history for reconciliation purposes. It can be run via the API or downloaded as a CSV from the Dashboard, offering detailed breakdowns of balance changes and payouts.
- [Connect report type | Stripe Documentation](https://docs.stripe.com/reports/report-types/connect): Connect platforms can use the Connect report types to view financial activity within their platform account or their connected accounts. These reports allow for retrieving financial data specific to connected accounts via the API.
- [Payout reconciliation report type | Stripe Documentation](https://docs.stripe.com/reports/report-types/payout-reconciliation): The Payout reconciliation report helps match payouts received in your bank account to the transactions they relate to. It provides data on payouts and failed payouts, and can be accessed via API or downloaded from the Dashboard.
- [Tax report type | Stripe Documentation](https://docs.stripe.com/reports/report-types/tax): The Tax report provides data on taxes calculated and charged for transactions, including information on tax codes used. This report can be run via the API and includes details like country codes, currency, and tax amounts.
- [Reporting categories and types | Stripe Documentation](https://docs.stripe.com/reports/reporting-categories): The reporting_category field on Stripe's BalanceTransaction objects offers a more detailed and useful grouping for financial reporting than the 'type' field. It separates adjustments like disputes and reversals into distinct categories and consolidates various transaction types into common groupings.
- [How to select a report | Stripe Documentation](https://docs.stripe.com/reports/select-a-report): Stripe offers various reports to assist with financial workflows, including monthly transaction history, balance reconciliation, and payout details. The Balance report functions like a bank statement for accounting, while the Payout reconciliation report breaks down individual payout transactions.
- [Revenue | Stripe Documentation](https://docs.stripe.com/revenue): Stripe helps manage the entire revenue lifecycle, from customer acquisition to closing books and automating sales taxes. It offers tools for subscriptions, invoicing, tax management, and various reporting options, including prebuilt reports and custom data analysis.
- [Stripe reporting | Stripe Documentation](https://docs.stripe.com/stripe-reports): Stripe reporting provides prebuilt reports for analyzing account activity like payments, payouts, fees, and balance changes, accessible via the Dashboard or CSV download. Advanced tools include Revenue Recognition for accrual accounting and custom report generation with Stripe Sigma.
- [Subscription and cancellation policies | Stripe Documentation](https://docs.stripe.com/billing/subscription-pricing/cancel): Stripe offers annual subscription plans for products like Billing and Tax, requiring a one-year commitment and automatically renewing unless canceled at least 24 hours before the renewal date. These plans provide a set usage entitlement and may offer discounts compared to pay-as-you-go options.
- [Subscription pricing plans | Stripe Documentation](https://docs.stripe.com/billing/subscription-pricing): Stripe subscription plans offer a way to pay for Stripe Billing and Tax with predictable monthly costs and potential discounts. Customers select a monthly product usage entitlement and commit to an annual contract, paying a monthly fee and potential overage fees for usage beyond the entitlement.
- [Revenue Recognition API | Stripe Documentation](https://docs.stripe.com/revenue-recognition/api): Stripe Revenue Recognition allows programmatic access to reports like monthly summaries and revenue waterfalls via the API to automate accrual accounting. It supports six different report types for analyzing debits and credits by various dimensions such as price, product, customer, or invoice.
- [Bulk account mapping | Stripe Documentation](https://docs.stripe.com/revenue-recognition/chart-of-accounts/bulk-account-mappings): The Bulk Account Mapping feature simplifies connecting Stripe's default accounts to your General Ledger (GL) structure by allowing simultaneous upload of multiple mappings via a CSV file. This feature eliminates manual creation, ensures consistency, and reduces repetitive work for large product catalogs.
- [Map to your chart of accounts | Stripe Documentation](https://docs.stripe.com/revenue-recognition/chart-of-accounts): You can customize Stripe Revenue Recognition reports to use your own General Ledger (GL) chart of accounts instead of Stripe's defaults. Mapping rules can be configured by product, shipping region, or invoice metadata, and these custom mappings are applied to downloaded CSV reports and audits.
- [Revenue Recognition for Connect platforms | Stripe Documentation](https://docs.stripe.com/revenue-recognition/connect): Revenue Recognition for Connect platforms supports three methods for collecting application fees: destination charges, direct charges, and separate charges and transfers. Each method impacts how platform fees are recognized as revenue, with specific functionalities available for different charge types.
- [Revenue Recognition for destination charges | Stripe Documentation](https://docs.stripe.com/revenue-recognition/connect/destination-charges): Revenue Recognition for destination charges tracks platform fees as revenue when using the destination charge model in Stripe Connect. It details how platform fees are recognized whether collected via application_fee_amount or by deducting them from the transfer_data[amount].
- [Revenue Recognition for direct charges | Stripe Documentation](https://docs.stripe.com/revenue-recognition/connect/direct-charges): Revenue Recognition for direct charges allows platforms to make charges directly on connected accounts and collect application fees immediately. The platform recognizes the revenue from these fees, and refunds of application fees are booked as contra revenue.
- [Revenue Recognition for separate charges and transfers | Stripe Documentation](https://docs.stripe.com/revenue-recognition/connect/charges-transfers): Revenue Recognition for separate charges and transfers enables platforms to make charges on their account for connected accounts, perform transfers separately, and retain funds. Stripe books separate transfers as contra revenue, and transfer reversals cancel this contra revenue.
- [Revenue Recognition data freshness | Stripe Documentation](https://docs.stripe.com/revenue-recognition/data-freshness): Stripe Revenue Recognition data is accessible through the Product Dashboard, Sigma, and the Reporting API, with new transaction data appearing within approximately 3-4 hours after completion. Data Pipeline syncs with custom data warehouses every 6 hours, with ledger entries appearing within 8-9 hours.
- [Revenue Recognition data import | Stripe Documentation](https://docs.stripe.com/revenue-recognition/data-import): Revenue Recognition data import allows for performing revenue recognition on non-Stripe transactions and adjusting existing Stripe transactions. This includes general imports via CSV, exclusion imports by transaction ID, and journal entry imports to manage all revenue recognition within Stripe.
- [Stripe Connector for the Apple App Store | Stripe Documentation](https://docs.stripe.com/revenue-recognition/data-import/apple-app-store): The Stripe Connector for the Apple App Store automatically imports subscription purchases into Stripe Revenue Recognition for near real-time availability and increased accuracy. It supports daily automated imports, improved refund treatment, and breakdown by subscriber for audits.
- [Error handling for data import | Stripe Documentation](https://docs.stripe.com/revenue-recognition/data-import/error-handling): This page details common errors encountered when importing revenue recognition data into Stripe, such as empty or invalid CSV files. It provides recommendations for resolving these errors, often requiring data re-import with corrected formats and values.
- [Data import examples | Stripe Documentation](https://docs.stripe.com/revenue-recognition/data-import/examples): This page provides practical examples of importing data for Stripe Revenue Recognition, demonstrating how to add service periods to Stripe payments and override or add service periods to invoice line items. These examples illustrate common use cases for integrating external data with Stripe's revenue recognition system.
- [Stripe Connector for Google Play | Stripe Documentation](https://docs.stripe.com/revenue-recognition/data-import/google-play): The Stripe Connector for Google Play automates the import of subscription purchases from Google Play into Stripe Revenue Recognition. This integration offers near real-time data availability, improved refund treatment, and auditability by order. It also provides guidance on migrating from manual data imports to avoid double-counting.
- [Manage imported data | Stripe Documentation](https://docs.stripe.com/revenue-recognition/data-import/manage-imported-data): This page explains how to manage imported data within the Stripe Dashboard after uploading CSV files for revenue recognition. It covers viewing import statuses, identifying import types, and managing transactions, including filtering and viewing split transactions. Successful imports show imported line counts, while errors display specific line numbers.
- [Data reconciliation with Stripe reports | Stripe Documentation](https://docs.stripe.com/revenue-recognition/data-reconciliation): This guide explains how to reconcile Stripe Revenue Recognition data with other financial reports, particularly the Balance Summary report. It details how to adjust for fees, network costs, and other items to accurately compare cash accounts and balance changes. The process involves downloading specific reports and factoring in corrections from the debits and credits report.
- [Revenue Recognition examples | Stripe Documentation](https://docs.stripe.com/revenue-recognition/examples): This page serves as a central hub for various Stripe Revenue Recognition examples, illustrating how the system automates accrual accounting. It categorizes examples into sections like Contra, Credit notes, FX and currency, Subscriptions, Tax, and others, to demonstrate practical applications.
- [Contra examples | Stripe Documentation](https://docs.stripe.com/revenue-recognition/examples/contra): This page presents contra examples for Stripe Revenue Recognition, focusing on scenarios involving customer credit balances. It explains how existing credits are applied to invoices and how negative invoice amounts can credit customer balances, demonstrating adjustments to revenue recognition under specific conditions.
- [Credit note examples | Stripe Documentation](https://docs.stripe.com/revenue-recognition/examples/credit-notes): This page offers examples of credit notes within Stripe Revenue Recognition, illustrating scenarios before and after a payment. It shows how pre-payment credit notes act as upfront discounts, reducing the total invoice amount. It also details how post-payment credit notes, issued via refunds or customer credits, adjust recognized revenue and deferred revenue.
- [FX and currency examples | Stripe Documentation](https://docs.stripe.com/revenue-recognition/examples/currency): This page provides examples of foreign exchange (FX) and currency impacts on Stripe Revenue Recognition. It covers scenarios with multi-currency transactions where presentment and settlement currencies differ, and illustrates how exchange rate fluctuations between invoice finalization and payment can lead to FX gains or losses.
- [Exclusion examples | Stripe Documentation](https://docs.stripe.com/revenue-recognition/examples/exclusion): This page details exclusion examples for Stripe Revenue Recognition, explaining how excluding transactions affects accounting. It differentiates between excluding paid and unpaid transactions, outlining how Stripe debits specific accounts like cash or customer balance and credits exclusion accounts for paid items. Unpaid transactions are treated as if they never occurred.
- [Other examples | Stripe Documentation](https://docs.stripe.com/revenue-recognition/examples/other-examples): This page presents 'Other examples' for Stripe Revenue Recognition, including scenarios with external assets and fees. It explains how manually marking invoices as paid outside Stripe increases the external asset account without affecting the cash account. It also clarifies how Stripe fees are booked on a cash basis starting from a specific date.
- [Subscription examples | Stripe Documentation](https://docs.stripe.com/revenue-recognition/examples/subscriptions): This page provides subscription examples for Stripe Revenue Recognition, illustrating monthly and annual subscriptions, as well as upgrades. It demonstrates how revenue is recognized daily over the service period, showing the breakdown of recognized and deferred revenue at month-end. The examples highlight the system's ability to handle recurring billing models.
- [Tax examples | Stripe Documentation](https://docs.stripe.com/revenue-recognition/examples/tax): This page offers tax examples for Stripe Revenue Recognition, covering tax-exempt customers and tax-inclusive invoice items. It explains how tax exemption statuses affect invoice calculations and demonstrates journal entries for tax-inclusive rates, differentiating between scenarios where the invoice item and accounting period are the same or different.
- [Revenue Recognition | Stripe Documentation](https://docs.stripe.com/revenue-recognition): Stripe Revenue Recognition automates accrual accounting, simplifying revenue recognition processes according to global accounting standards. It offers features like recognized and deferred revenue summaries, downloadable reports, configurable rules, and integration with other Stripe objects for intelligent defaults. The service is crucial for public companies, startups, and subscription-based businesses.
- [Invite your accountant | Stripe Documentation](https://docs.stripe.com/revenue-recognition/invite-accountant): This page explains how to invite accountants to access Stripe Revenue Recognition, providing them with tailored permissions. This access allows accountants to configure accounting logic and settings, such as amortization settings and custom charts of accounts, without having full administrative control over sensitive business data or payouts. It ensures books are audit-ready with a balance of edit and view-only access.
- [How revenue recognition works | Stripe Documentation](https://docs.stripe.com/revenue-recognition/methodology): Stripe Revenue Recognition automates accrual accounting by recognizing revenue when earned, not just when paid, aligning with GAAP. It simplifies processes with features like recognized/deferred revenue summaries, downloadable reports, and configurable rules. Revenue recognition is essential for businesses requiring accurate profitability insights, especially public companies, startups, and subscription-based models.
- [Revenue Recognition with multiple currencies | Stripe Documentation](https://docs.stripe.com/revenue-recognition/methodology/multi-currency): This page details how Stripe Revenue Recognition handles multiple currencies, distinguishing between presentment and settlement currencies. Transactions where presentment and settlement currencies match are processed directly. For unsupported presentment currencies, transactions convert to the account's default settlement currency, using the exchange rate at the time of money movement for recognition.
- [Revenue Recognition with refunds and disputes | Stripe Documentation](https://docs.stripe.com/revenue-recognition/methodology/refunds-and-disputes): This page explains how refunds and disputes impact Stripe Revenue Recognition by offsetting prior recognized revenue with contra revenue in specific accounts. When a refund or dispute occurs, cash is returned, prior revenue is offset, and any un-recognized deferred revenue is cleared. Examples illustrate the accounting entries for one-time payment refunds and subscription disputes.
- [Revenue Recognition with subscriptions and invoicing | Stripe Documentation](https://docs.stripe.com/revenue-recognition/methodology/subscriptions-and-invoicing): This page describes how Stripe Revenue Recognition leverages subscription and invoice data to accurately defer and recognize revenue. Each invoice line item and subscription item is treated as a performance obligation, with revenue amortized daily. Examples illustrate how monthly and annual subscriptions, including upgrades, are processed, showing the recognized and deferred revenue over service periods.
- [Revenue Recognition transaction overrides | Stripe Documentation](https://docs.stripe.com/revenue-recognition/overrides): This page discusses Revenue Recognition transaction overrides in Stripe, noting that the feature is being deprecated in favor of the data import feature. It explains how overrides allow manual corrections to revenue recognition data, supporting invoices and charges. Users can find transaction IDs in the Dashboard or API and select override types like recognition period start and end dates.
- [Revenue Recognition Performance Obligations API | Stripe Documentation](https://docs.stripe.com/revenue-recognition/performance-obligations-api): The Revenue Recognition Performance Obligations API allows businesses to model and track the fulfillment of performance obligations, which is crucial for accurate revenue reporting. It helps in scenarios like the delivery of goods, performance of services, and handling prepayments.
- [Revenue Recognition reports | Stripe Documentation](https://docs.stripe.com/revenue-recognition/reports): Stripe Revenue Recognition automatically generates reports that can be viewed in the Dashboard or exported as CSV files, providing key financial information like revenue and deferred revenue. These reports offer both aggregate and detailed views for analysis and data validation, with requirements for proper business modeling.
- [Activity breakdown | Stripe Documentation](https://docs.stripe.com/revenue-recognition/reports/activity-breakdown): The Activity Breakdown report provides detailed transaction-level data for journal entry activity, aiding in account reconciliation, audit preparation, and customer or product performance analysis. It includes historical trend charts to visualize account activity over time.
- [Accounts receivable aging | Stripe Documentation](https://docs.stripe.com/revenue-recognition/reports/accounts-receivable-aging): The Accounts Receivable Aging report monitors outstanding invoices by grouping them into age ranges, helping businesses understand collections performance and assess credit risk. This report is essential for managing cash flow and credit policies.
- [Audit your numbers | Stripe Documentation](https://docs.stripe.com/revenue-recognition/reports/audit-numbers): The 'Audit your numbers' feature in the Stripe Dashboard allows users to examine detailed accounting numbers from various reports, such as the monthly summary, revenue waterfall, and AR aging summary. Users can drill down by customer or transaction to view specific details.
- [Balance sheet | Stripe Documentation](https://docs.stripe.com/revenue-recognition/reports/balance-sheet): The Balance Sheet report offers a snapshot of a company's financial position at a specific time, listing assets and liabilities to assess financial health and stability. It aligns with other Revenue Recognition reports for consistency and can be analyzed comparatively across periods.
- [Debits and credits | Stripe Documentation](https://docs.stripe.com/revenue-recognition/reports/debits-and-credits): The Debits and Credits report displays every debit and credit entry in the accounting system, facilitating general ledger reconciliation, transaction auditing, and balance verification. It allows filtering by transaction type, including corrections to closed periods.
- [Income statement | Stripe Documentation](https://docs.stripe.com/revenue-recognition/reports/income-statement): The Income Statement report analyzes a company's financial performance over a specified period, detailing revenue, expenses, and net income. It helps assess financial health by tracking contra revenue, expenses, and gains, and reconciles with other financial reports.
- [Custom reports by Sigma and SDP | Stripe Documentation](https://docs.stripe.com/revenue-recognition/reports/sigma-and-sdp): Businesses can build custom reports using Stripe's Sigma and SDP tools by querying revenue recognition data tables. This allows for detailed analysis, such as generating reports on revenue recognized from unpaid invoices.
- [Trial balance | Stripe Documentation](https://docs.stripe.com/revenue-recognition/reports/trial-balance): The Trial Balance report summarizes account balances at a specific point in time, ensuring that total debits equal total credits, which is a key step in closing accounting periods. It details starting balance, net change, and ending balance for each account.
- [Revenue waterfall | Stripe Documentation](https://docs.stripe.com/revenue-recognition/reports/waterfall): The Revenue Waterfall report visualizes monthly revenue, showing booked revenue against recognized revenue over selected periods. It helps track revenue that has been billed, recognized, and remains unrecognized.
- [Revenue Recognition contracts | Stripe Documentation](https://docs.stripe.com/revenue-recognition/revenue-contracts): Revenue Contracts feature allows for the representation of enterprise sales contracts in Stripe, enabling custom revenue schedules decoupled from billing periods. It also facilitates tracking key contract-level metrics and augmenting reports with non-GAAP accounts.
- [Revenue Recognition settings | Stripe Documentation](https://docs.stripe.com/revenue-recognition/revenue-settings): Stripe Revenue Recognition settings allow businesses to customize how revenue is recognized, including configuring accounting periods and amortization granularity. These settings impact all revenue recognition charts and reports within 24 hours.
- [Revenue Recognition accounting period control | Stripe Documentation](https://docs.stripe.com/revenue-recognition/revenue-settings/accounting-period-control): Accounting Period Control lets users manage their accounting calendar, choosing between calendar months or a 4-4-5 structure, and deciding whether to close periods manually or automatically. It also allows for reopening past periods to make retroactive adjustments.
- [Revenue Recognition settings examples | Stripe Documentation](https://docs.stripe.com/revenue-recognition/revenue-settings/examples): Revenue Recognition settings examples demonstrate how different amortization granularities (by second, day, or month) affect revenue recognition and deferred revenue calculations over a subscription period. It also touches on how recovered revenue is recognized as gains by default.
- [Revenue Recognition rules | Stripe Documentation](https://docs.stripe.com/revenue-recognition/rules): Revenue Recognition rules enable businesses to customize how revenue is treated by defining specific rules for categorization, booking, exclusion, amortization, and allocation. These rules are applied to reports and can be managed through the Stripe Dashboard.
- [Create a rule | Stripe Documentation](https://docs.stripe.com/revenue-recognition/rules/create-a-rule): Creating a Revenue Recognition rule involves defining its name, conditions for application, and the revenue treatment and allocation. Rules must meet both condition and effective period requirements to apply, and updates can retroactively affect previous accounting periods.
- [Recognize revenue with Stripe | Stripe Documentation](https://docs.stripe.com/revenue-recognition/get-started): Stripe Revenue Recognition helps businesses automate revenue recognition by importing transaction data, setting up custom rules, and generating reports. Features are available through the Dashboard, with a 30-day free trial offered for exploration.
- [Standalone selling prices | Stripe Documentation](https://docs.stripe.com/revenue-recognition/standalone-selling-price): The Standalone Selling Price (SSP) feature helps allocate revenue for bundled products by allowing customizable allocations based on absolute values or percentages. It enables setting different revenue schedules for bundle components and auditing journal entries at the bundle item level.
- [Stripe app for Salesforce Platform AgnosticInvocable Example | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/stripe-app-for-salesforce/training/code-examples-agnostic): This guide provides code examples for creating Stripe customers and PaymentIntents within Salesforce using custom Apex classes for agnostic API calls. It demonstrates how to abstract the Stripe API for greater flexibility and easier management.
- [Stripe app for Salesforce Platform invocations | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/stripe-app-for-salesforce/training/code-examples-invocations): This guide provides Apex code examples for integrating Stripe with Salesforce, enabling tasks like customer creation and checkout session initiation directly from Salesforce. It's designed for Salesforce administrators and developers seeking seamless payment workflow integrations.
- [Stripe app for Salesforce Platform configure events guide | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/stripe-app-for-salesforce/configure-events): This page explains how to configure Stripe events within the Salesforce app, which automatically creates webhooks in Stripe and sets up listeners in Salesforce. It guides users through selecting Stripe objects to enable events and how these events are captured as records in Salesforce.
- [Stripe app for Salesforce Platform Configuration | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/stripe-app-for-salesforce/configuration): This document details the configuration options for the Stripe app on the Salesforce Platform, offering custom integrations via Flows and Apex, or pre-built billing integrations. It covers connecting Stripe accounts, managing data synchronization, and leveraging subscription management templates.
- [Stripe app for Salesforce Platform | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/stripe-app-for-salesforce/overview): The Stripe app for Salesforce Platform allows users to automate and integrate Stripe API functionalities directly within Salesforce using Flow Builder and Apex. It supports native Stripe Billing data models, offers one-click data synchronization, and facilitates features like opportunity-to-subscription conversion.
- [Stripe app for Salesforce Platform installation | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/stripe-app-for-salesforce/installation-guide): This guide explains how to install the Stripe app for Salesforce Platform, providing separate options for test and production environments via the Salesforce AppExchange. It outlines the installation process, including enabling Lightning Web Security and recommending 'Install for Admins Only'.
- [Stripe app for Salesforce Platform | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/stripe-app-for-salesforce/training): This page offers usage examples and training for the Stripe app on the Salesforce Platform, directing users to a GitHub repository for code examples. It covers syncing objects, creating payment pages, generating invoices, and explains two primary methods for calling Stripe from Salesforce: direct class invocations and an agnostic method.
- [Stripe apps for Salesforce | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/salesforce): This page provides an overview of Stripe apps for Salesforce, highlighting how to leverage Stripe's product suite within Salesforce for streamlined revenue operations. It introduces the Salesforce Billing Extension and the Stripe app for Salesforce B2C Commerce Cloud, enabling payment processing and storefront integrations.
- [Best practices for using Stripe with Salesforce Billing | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/salesforce-billing/bestpractices): This guide details best practices for integrating Stripe with Salesforce Billing, covering data import options for customers and payment methods. It explains how to import data using quick actions, data imports, or custom scripts, ensuring necessary fields are present for successful integration.
- [Salesforce Billing Extension configuration | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/salesforce-billing-extension/configuration): This document outlines the configuration steps for the Salesforce Billing Extension, which integrates with Stripe Payments and Salesforce Payment Center. It details assigning permission sets, updating global value sets for gateway types, and adding payment method buttons to account layouts.
- [Configure Stripe app for Salesforce Billing | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/salesforce-billing/configuration): This guide explains how to configure the Stripe app for Salesforce Billing by assigning necessary permission sets for admin and standard users. It also details how to assign the correct Page Layouts for Opportunity, Account, and Order objects to ensure proper payment processing flows.
- [Salesforce Billing Extension | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/salesforce-billing-extension): The Salesforce Billing Extension is an unmanaged package that enhances the Stripe app for Salesforce Platform, enabling payment processing through Salesforce Payment Gateway using Stripe. It supports UI-based transactions like tokenization, charging, and refunds, as well as API-based transactions for advanced customization.
- [Install the Salesforce Billing Extension | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/salesforce-billing-extension/install): This guide details the installation process for the Salesforce Billing Extension, which requires the Stripe app for Salesforce Platform and Salesforce CPQ to be installed first. It provides links for installing Salesforce CPQ in production or sandbox environments and outlines post-installation configuration steps.
- [Install the Stripe app for Salesforce B2C Commerce Shopfront architecture | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/salesforce-commerce-cloud/component-overview): This page describes the Stripe app for Salesforce B2C Commerce Shopfront architecture, explaining how the Stripe Payment Element securely tokenizes credit card data using Stripe.js. It details the PaymentIntent workflow, ensuring unmasked credit card data is never sent to Commerce Cloud servers.
- [Stripe app for Salesforce B2C Commerce implementation guide | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/salesforce-commerce-cloud/implementation-guide): This implementation guide for the Stripe app for Salesforce B2C Commerce Cloud covers setting up Business Manager, assigning site cartridges, and importing metadata. It details the necessary cartridges and configuration steps to integrate Stripe functionality into your Commerce Cloud storefront.
- [Stripe app for Salesforce B2C Commerce Cloud | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/salesforce-commerce-cloud): The Stripe app for Salesforce B2C Commerce Cloud facilitates payment integration between Commerce Cloud storefronts and Stripe, supporting various payment processing options and saved payment methods. It enables e-commerce workflows, utilizes deferred-based intent logic, and supports bank transfer payments.
- [Stripe app for Salesforce B2C Commerce Cloud Testing integration | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/salesforce-commerce-cloud/testing): This guide explains how to test the Stripe app for Salesforce B2C Commerce Cloud integration, focusing on storefront functionality and checkout processes. It provides instructions on using test credit card numbers and API keys, and outlines the steps for a successful checkout simulation.
- [Use the Stripe app for Salesforce Commerce Cloud | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/salesforce-commerce-cloud/user-guide): This user guide for the Stripe app for Salesforce Commerce Cloud explains its day-to-day functionality after installation and configuration. It covers payment processing, saved payment methods, and data management, including merchant roles, Business Manager jobs, and storefront features for authenticated customers.
- [Stripe app for Salesforce Order Management | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/salesforce-order-management): This page introduces the Stripe app for Salesforce Order Management, a managed package that enables payment capture and refunds for order servicing use cases. It requires a Salesforce B2C Commerce Cloud storefront and an integration between B2C Commerce Cloud and Order Management, detailing core concepts like PaymentIntent and payment authorization.
- [Install the Stripe app for Salesforce Order Management | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/salesforce-order-management/installation): This guide provides instructions for installing and configuring the Stripe app for Salesforce Order Management. It highlights integration limitations, such as supporting only a single B2C storefront and one-time manual capture, and outlines the steps for configuring a Stripe Synchronous Payment Gateway Adapter.
- [About the Stripe app for Salesforce Order Management | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/salesforce-order-management/operations-and-maintenance): This page explains the core concepts of the Stripe app for Salesforce Order Management, including Payment Intents and payment authorization. It details how PaymentIntent IDs are stored in Salesforce Order Management and discusses capture modes (authorize and capture) within the Stripe LINK cartridge for Salesforce B2C Commerce Cloud.
- [How the App for Salesforce Order Management works | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/salesforce-order-management/overview): The Stripe app for Salesforce Order Management integrates Stripe's payment gateway with Salesforce Order Management. Key components include the StripeAPI named credential and Apex classes like StripeAdapter for payment processing. It also utilizes custom settings for authentication and Lightning Pages for authorization.
- [Testing the Stripe app for Salesforce Order Management | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/salesforce-order-management/testing): This guide outlines how to test the Stripe app for Salesforce Order Management integration. It involves toggling Stripe to test mode, raising orders in Salesforce, fulfilling or refunding them, and verifying payment statuses in the Stripe Dashboard. It also covers verifying integration between Salesforce B2C Commerce Cloud and Salesforce Order Management.
- [Stripe Billing flows configuration | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/stripe-billing-flows-extension/configuration): This page details the configuration of the Stripe Billing Flows Extension, which automates subscription management by connecting Salesforce processes with Stripe subscriptions. The extension is an unmanaged package, allowing for customization of flows, object mappings, and pricing structures. It works with Salesforce Orders and Contracts as primary objects and uses a flat-rate recurring pricing model.
- [Stripe Billing Flows Extension | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/stripe-billing-flows-extension): The Stripe Billing Flows Extension is an unmanaged package installed on top of the Stripe app for Salesforce Platform. It automates the creation of subscription schedules based on Salesforce Order activation using pre-built flows. As an unmanaged package, it offers customization of existing flows, Apex code, and default object mappings.
- [Install the Stripe Billing Flows Extension | Stripe Documentation](https://docs.stripe.com/use-stripe-apps/stripe-billing-flows-extension/install): This document provides instructions for installing the Stripe Billing Flows Extension. After installing the Stripe app for Salesforce and its API Extension, users install the Stripe for Salesforce Platform Recipes from the app wizard. The installation process involves granting third-party access and verifying the package installation in Salesforce Setup.
- [Identity verification (redirect) | Stripe Documentation](https://docs.stripe.com/samples/identity/redirect): This is a sample project demonstrating identity verification using a redirect flow with Stripe. It showcases how to implement identity verification where users are redirected to a Stripe-hosted page to complete the process.
- [Browse sample projects | Stripe Documentation](https://docs.stripe.com/samples): This page provides a library of Stripe sample projects for various use cases, including accepting payments with Stripe Checkout, setting up subscriptions with Stripe Billing, and integrating payment forms using Stripe Elements. Projects are available for different platforms and languages, with links to view them in VS Code or GitHub.
- [Create claimable sandboxes | Stripe Documentation](https://docs.stripe.com/sandboxes/claimable-sandboxes): This guide explains how to create anonymous, claimable sandboxes programmatically using the Claimable Sandbox API. Users can claim these sandboxes via a unique URL, which prompts them to associate the sandbox with a new or existing Stripe account. This allows for integration of Stripe's payment features within user applications.
- [Manage access and API keys | Stripe Documentation](https://docs.stripe.com/sandboxes/dashboard/manage-access): This document details how to manage access and API keys for Stripe sandboxes through the Stripe Dashboard. Users can grant specific roles to team members for access to individual sandboxes or organization sandboxes. API keys are used for authenticating requests to sandbox environments and can be revealed, revoked, or created within the Developer Dashboard.
- [Manage sandboxes | Stripe Documentation](https://docs.stripe.com/sandboxes/dashboard/manage): This page describes how to manage Stripe sandboxes within the Dashboard for development and testing purposes. Users can create up to five sandboxes per account, choosing to either copy their existing account's settings or start from scratch. Sandboxes can be used to mirror live mode for staging changes or to isolate testing environments.
- [Manage organization sandboxes | Stripe Documentation](https://docs.stripe.com/sandboxes/dashboard/organizations): This guide explains how to manage organization sandboxes in the Stripe Dashboard, which are useful for testing integrations across multiple sandboxes or mirroring a live organization. Creating an organization sandbox requires specific roles within the live organization. Access to these sandboxes is managed at the live organization level.
- [Sandbox settings | Stripe Documentation](https://docs.stripe.com/sandboxes/dashboard/sandbox-settings): This page covers sandbox settings in Stripe, allowing users to choose a starting configuration when creating a sandbox. Options include copying existing account settings and capabilities to create a similar environment or creating a blank sandbox from scratch. This helps in testing how configuration changes affect integration behavior.
- [Sandboxes | Stripe Documentation](https://docs.stripe.com/sandboxes): Sandboxes provide an isolated test environment for experimenting with Stripe functionality without affecting live integrations. They are used for various scenarios, such as simulating events without real money movement, scaling isolated environments for teams, and inviting external users for collaboration. Sandboxes can be accessed via the Dashboard or the Stripe CLI.
- [Strong Customer Authentication readiness | Stripe Documentation](https://docs.stripe.com/strong-customer-authentication): This page explains the Strong Customer Authentication (SCA) regulation, which requires additional authentication for online payments in Europe, primarily through 3D Secure. Businesses operating in the EEA or serving EEA customers must update their integrations to avoid declined payments. The page guides users on determining SCA impact and choosing SCA-ready products.
- [SCA migration guide for Connect platforms | Stripe Documentation](https://docs.stripe.com/strong-customer-authentication/connect-platforms): This guide helps Stripe Connect platforms update their integrations for Strong Customer Authentication (SCA). It covers scenarios like direct charges, destination charges, and separate charges and transfers that require additional authentication. The guide recommends using Stripe Checkout or the Payment Intents API for SCA compliance.
- [Pricing and cancellation terms for Stripe Foundations, Expansion, and Scale plans | Stripe Documentation](https://docs.stripe.com/bundled-pricing/terms): This document outlines the pricing and cancellation terms for Stripe's subscription-based plans (Foundations, Expansion, and Scale). These plans have a minimum one-month commitment and automatically renew unless canceled at least two business days before the renewal date. After the contract ends, accounts revert to pay-as-you-go pricing.
- [Search | Stripe Documentation](https://docs.stripe.com/search): This page describes how to search for objects within your Stripe data using flexible search API methods, which is faster than pagination. It details the minimum API version required for search (2020-08-27) and notes that data may take up to 1 minute to become searchable after creation or update.
- [Integration security guide | Stripe Documentation](https://docs.stripe.com/security/guide): This guide focuses on ensuring PCI compliance and secure customer-server communications for Stripe integrations. It explains that PCI DSS is a global security standard for handling cardholder data, with Stripe being a PCI Level 1 Service Provider. Businesses must also comply with PCI DSS and can leverage Stripe's tools and documentation for assistance.
- [Python PGP key | Stripe Documentation](https://docs.stripe.com/security/python-client-pgp-key): This page provides the PGP public key for the Stripe Python client library, enabling users to encrypt files. It includes the key ID, type, size, fingerprint, and user ID for verification. Users unfamiliar with PGP are advised to review GPG basics before importing and using the key.
- [Security at Stripe | Stripe Documentation](https://docs.stripe.com/security): This page details Stripe's security posture as a payments infrastructure company, emphasizing their commitment to protecting sensitive data. Stripe is PCI-certified at the highest level and adheres to global financial industry standards. They offer features to automate PCI compliance and regularly undergo SOC 1 and SOC 2 audits.
- [Alipay payments with Sources | Stripe Documentation](https://docs.stripe.com/sources/alipay): The Alipay payment guide explains how to use Stripe Sources to accept payments from customers in China. It details the process of creating a Source object, customer redirection to Alipay for authorization, and completing the payment. Note that the Sources API is deprecated, and migration to the Payment Methods API is recommended.
- [Bancontact payments with Sources | Stripe Documentation](https://docs.stripe.com/sources/bancontact): This guide covers accepting Bancontact payments in Belgium using Stripe Sources. It outlines the process of creating a Source object, redirecting customers to their bank for authorization, and then using the source to complete the charge. The document also warns that the Sources API is deprecated and recommends migrating to the Payment Methods API.
- [Best practices for using Sources | Stripe Documentation](https://docs.stripe.com/sources/best-practices): This document outlines best practices for using the deprecated Stripe Sources API, emphasizing the need to migrate to the Payment Methods API for new integrations and to access the latest features. It explains how different payment methods require different handling, particularly noting that methods involving customer redirects or asynchronous actions necessitate the use of webhooks for status updates.
- [Connect platforms using the Sources API | Stripe Documentation](https://docs.stripe.com/sources/connect): This page discusses considerations for Stripe Connect platforms using the deprecated Sources API to add payment methods. It highlights the deprecation of the Sources API and the recommendation to migrate to the Payment Methods API, especially due to SCA regulations. The document also details how to handle destination and direct charges with alternative payment methods.
- [Sources and customers | Stripe Documentation](https://docs.stripe.com/sources/customers): This guide explains how to manage Stripe Sources with Customer objects, noting the deprecation of the Sources API and recommending migration to the Payment Methods API. It details that reusable sources must be attached to a Customer object before charging to prevent them from being consumed. This allows for easier presentation of previously used payment methods to customers.
- [giropay payments with Sources | Stripe Documentation](https://docs.stripe.com/sources/giropay): The giropay payments guide explains how to accept payments from German customers using Stripe Sources, involving the creation of a Source object and redirection to the customer's bank for authorization. It also warns that the Sources API is deprecated and recommends migrating to the Payment Methods API for current and future integrations.
- [iDEAL payments with Sources | Stripe Documentation](https://docs.stripe.com/sources/ideal): This page details how to accept iDEAL payments from customers in the Netherlands using Stripe Sources. It explains the process of creating a Source object, redirecting the customer to their bank for authorization, and completing the payment. The guide also highlights the deprecation of the Sources API and recommends migrating to the Payment Methods API.
- [The Sources API | Stripe Documentation](https://docs.stripe.com/sources): The Stripe Sources API overview explains its functionality for accepting various payment methods through a single API, with Source objects representing customer payment methods. It strongly advises migrating from the deprecated Sources API to the Payment Methods API for access to new features and local payment methods. The document also mentions SCA regulations impacting European payments.
- [Multibanco payments with Sources | Stripe Documentation](https://docs.stripe.com/sources/multibanco): This guide covers accepting Multibanco payments in Portugal using Stripe Sources, detailing the creation of a Source object and the customer's redirection for authorization, which may take several days. It emphasizes that the Sources API is deprecated and recommends migrating to the Payment Methods API. The process involves the customer sending funds via a receiver outside the checkout flow.
- [Przelewy24 payments with Sources | Stripe Documentation](https://docs.stripe.com/sources/p24): This page explains how to accept Przelewy24 payments in Poland using Stripe Sources, involving customer redirection to their bank for authorization and subsequent charge completion. It notes that the Sources API is deprecated and recommends migrating to the Payment Methods API. The guide also specifies the parameters required for creating a Przelewy24 Source object.
- [SEPA Credit Transfer payments with Sources | Stripe Documentation](https://docs.stripe.com/sources/sepa-credit-transfer): This guide details how to accept SEPA Credit Transfer payments using Stripe Sources, where customers are provided with an IBAN to initiate a transfer from their bank. It highlights that SEPA Credit Transfers are a reusable, push-based payment method that can take a few days to arrive. The document also states that the Sources API is deprecated and recommends migration to the Payment Methods API.
- [SEPA Direct Debit payments with Sources | Stripe Documentation](https://docs.stripe.com/sources/sepa-debit): This page explains how to accept SEPA Direct Debit payments using Stripe Sources, which involves collecting customer bank account information and a mandate for debit authorization. It notes that SEPA Direct Debit is a pull-based, reusable, and asynchronous payment method that can take up to 14 business days to confirm. The document also warns about transaction limits and the deprecation of the Sources API.
- [WeChat Pay payments with Sources | Stripe Documentation](https://docs.stripe.com/sources/wechat-pay): This guide explains how to accept WeChat Pay payments using Stripe Sources, which involves creating a Source object and providing a URL for customers to authorize payments via QR code scanning within the WeChat app. It also warns that the Sources API is deprecated and recommends migrating to the Payment Methods API. WeChat Pay is described as a synchronous payment method with immediate confirmation.
- [Enable autocompletion for the Stripe CLI | Stripe Documentation](https://docs.stripe.com/stripe-cli/autocomplete): This page explains how to enable command autocompletion for the Stripe CLI on macOS and Linux using Zsh or Bash shells. Autocompletion allows users to press the tab key to see available commands and flags, streamlining command-line operations. Windows autocompletion is not currently supported.
- [Stripe CLI | Stripe Documentation](https://docs.stripe.com/stripe-cli): The Stripe CLI page introduces the command-line tool for building, testing, and managing Stripe integrations. It covers installation, usage, enabling autocompletion, and managing CLI keys. The CLI allows users to perform tasks like calling APIs, testing webhooks, and creating applications directly from the terminal.
- [Install the Stripe CLI | Stripe Documentation](https://docs.stripe.com/stripe-cli/install): This guide details how to install the Stripe CLI on macOS, Windows, and Linux using various methods including package managers and direct downloads. The Stripe CLI enables users to manage Stripe resources in a sandbox, stream API requests, and test webhook integrations. It also covers logging into the CLI to authenticate with a Stripe account.
- [Stripe CLI keys and permissions | Stripe Documentation](https://docs.stripe.com/stripe-cli/keys): This page explains Stripe CLI keys and permissions, detailing how the `stripe login` command generates restricted keys for sandbox and live modes, valid for 90 days. It contrasts these with unrestricted API secret keys and explains how to view key permissions and specify API keys using the `--api-key` flag. The CLI stores keys locally and in the Dashboard's Restricted keys section.
- [Trigger webhook events with the Stripe CLI | Stripe Documentation](https://docs.stripe.com/stripe-cli/triggers): This guide explains how to trigger webhook events in a Stripe sandbox using the Stripe CLI. Users can either perform actions that naturally generate events or use the `stripe trigger <EVENT>` command to simulate specific events. The CLI can also customize events using override flags and is used in conjunction with `stripe listen` to test webhook integrations.
- [Upgrade the Stripe CLI | Stripe Documentation](https://docs.stripe.com/stripe-cli/upgrade): This page provides instructions on how to upgrade the Stripe CLI on various operating systems and installation methods, including Homebrew, Scoop, Docker, and manual downloads. Keeping the CLI updated is recommended for access to new features, improvements, and security updates.
- [Use the Stripe CLI | Stripe Documentation](https://docs.stripe.com/stripe-cli/use-cli): This page describes how to use the Stripe CLI to build, test, and manage Stripe integrations from the command line. It covers specifying API versions for requests using flags like `--stripe-version` and `--latest`, streaming API request logs with `stripe logs tail`, and forwarding events to a local webhook endpoint using the `--forward-to` flag.
- [Stripe connector for Apple App Store®* | Stripe Documentation](https://docs.stripe.com/stripe-data/import-external-data/connectors/apple-app-store): The Stripe connector for Apple App Store automates the import of application files into Stripe's data management platform. This process requires an active Apple Developer account, an App Store Connect API key, and specific financial report access. By importing this data, businesses can keep their Stripe products up-to-date.
- [Stripe connector for Google Play Store* | Stripe Documentation](https://docs.stripe.com/stripe-data/import-external-data/connectors/google-play): The Stripe connector for Google Play Store automates the import of application files into Stripe's data management platform. This requires an active Google Cloud and Play Console account, along with specific API enablement and service account configurations. Automating this import helps maintain up-to-date Stripe product information.
- [Import external data into Stripe | Stripe Documentation](https://docs.stripe.com/stripe-data/import-external-data): Stripe's data management platform allows for the automated import of external data from sources like the Apple App Store and Google Play Store using no-code connectors. This feature supports various use cases, including powering Revenue Recognition reports and enabling usage-based billing. Manual file uploads and third-party transaction data imports for Stripe Tax are also supported.
- [Stripe connector for Amazon S3 | Stripe Documentation](https://docs.stripe.com/stripe-data/import-external-data/connectors/s3): The Stripe connector for Amazon S3 enables automated recurring file imports from an S3 bucket into the Stripe Data Management Platform. Prerequisites include an active AWS account and S3 bucket access. The process involves configuring the connection within Stripe and ensuring files meet Stripe's naming and size requirements, supporting CSV, TSV, JSON, and JSONLINE formats.
- [Export data to Amazon S3 | Stripe Documentation](https://docs.stripe.com/stripe-data/access-data-in-warehouse/cloud-storage/aws-s3-storage): Stripe's Data Pipeline can automate recurring data exports from your Stripe account to an Amazon S3 storage bucket. This process requires an active AWS account with permissions to create an S3 bucket and an IAM role for Stripe. Data is delivered as Parquet files, updated every 3 hours, and organized into directories for each table.
- [Export data to Azure Blob Storage | Stripe Documentation](https://docs.stripe.com/stripe-data/access-data-in-warehouse/cloud-storage/azure-blob-storage): This document outlines how to export Stripe data to Azure Blob Storage using the Data Pipeline. It details the prerequisites, including creating an Azure App Registration and Storage Account/Container, and obtaining necessary IDs and secrets. Stripe data is delivered as Parquet files to your Azure Blob Storage account, updated every 3 hours.
- [Export data to cloud storage | Stripe Documentation](https://docs.stripe.com/stripe-data/access-data-in-warehouse/cloud-storage): Stripe's Data Pipeline allows syncing your Stripe account data to cloud storage destinations like Google Cloud Storage, Azure Blob Storage, or Amazon S3. Data is exported as Parquet files and regularly refreshed, with a SUCCESS file indicating successful transfer for each run. This enables integration with data warehouses such as BigQuery and Databricks.
- [Export data to a data warehouse | Stripe Documentation](https://docs.stripe.com/stripe-data/access-data-in-warehouse/data-warehouses): Data Pipeline enables automated data exports from Stripe to data warehouses like Snowflake, Amazon Redshift, and Databricks. After onboarding, core Stripe data becomes accessible within 12 hours and refreshes every 3 hours. Users can connect only one warehouse account to their Stripe account.
- [Cloud storage file organization | Stripe Documentation](https://docs.stripe.com/stripe-data/access-data-in-warehouse/cloud-storage/file-organization): This page explains the file organization for data exported to cloud storage from Stripe. Data is separated into 'livemode' and 'testmode' directories based on its origin. It details the structure of SUCCESS files associated with different datasets, which confirm the successful loading of data with specific freshness and refresh intervals.
- [Export data to Google Cloud Storage | Stripe Documentation](https://docs.stripe.com/stripe-data/access-data-in-warehouse/cloud-storage/google-cloud-storage): This guide explains how to export Stripe data to Google Cloud Storage using Data Pipeline. It requires creating a Google Cloud Storage bucket and a service account with specific roles (Storage Object User, Creator, and Collector Service). Stripe data is delivered as Parquet files to your GCS bucket and updated every 3 hours.
- [How Data Pipeline works | Stripe Documentation](https://docs.stripe.com/stripe-data/access-data-in-warehouse): Data Pipeline is a no-code Stripe product that centralizes your Stripe data by exporting it to various destinations like data warehouses or cloud storage. It automates data exports, eliminating the need for third-party ETL pipelines or custom API integrations. Data is refreshed regularly, with cloud storage destinations receiving updates every 3 hours.
- [Data Pipeline | Stripe Documentation](https://docs.stripe.com/stripe-data/data-pipeline): Data Pipeline is a no-code Stripe product that synchronizes all your Stripe data to various storage destinations, including data warehouses (Snowflake, Amazon Redshift, Databricks) and cloud storage (Google Cloud Storage, Amazon S3, Azure Blob Storage). This allows for centralizing Stripe data with other business data for enhanced insights and reporting. Users can also customize their data exports and delivery options.
- [Diagnose connection issues with cloud storage | Stripe Documentation](https://docs.stripe.com/stripe-data/access-data-in-warehouse/cloud-storage/connection): This guide helps diagnose connection issues with Stripe Data Pipeline to cloud storage by checking common configuration points. It provides specific steps for Google Cloud Storage and Azure, focusing on verifying bucket/project names, container correctness, and required roles/permissions for service accounts.
- [Stripe data | Stripe Documentation](https://docs.stripe.com/stripe-data): Stripe data can be utilized to gauge business performance through tools like Stripe Sigma for custom queries and Data Pipeline for syncing data to warehouses or cloud storage. No-code connectors are available to import external data into Stripe, and data can be exported to data warehouses or cloud storage destinations.
- [Data freshness | Stripe Documentation](https://docs.stripe.com/stripe-data/available-data): Sigma and Data Pipeline provide access to Stripe data for analysis and export, with most transaction data available within one day. Sigma offers a SQL-based interface for custom queries, making most data available within three hours of activity. Data Pipeline enables bulk data exports to various destinations.
- [Query business data | Stripe Documentation](https://docs.stripe.com/stripe-data/query-data): This page details how to query business and product data using Stripe Sigma and Data Pipeline. It covers querying transactional data, billing information, connected account details, and tax data. Information on data freshness and browsing the Stripe schema is also provided to assist in query writing.
- [Query fees data | Stripe Documentation](https://docs.stripe.com/stripe-data/query-all-fees-data): You can query fees data using Sigma or Data Pipeline to obtain a granular breakdown of every fee charged to your Stripe balance. The `itemized_fees` table provides details on the fee amount, tax, currency, and the object that incurred the fee, allowing for comprehensive analysis of fees paid over time.
- [Query billing data | Stripe Documentation](https://docs.stripe.com/stripe-data/query-billing-data): This document explains how to query billing data using Sigma or Data Pipeline, focusing on subscriptions and invoices as primary tables. It highlights that the `customers` table is fundamental for billing-related reporting. An example SQL query demonstrates retrieving unpaid subscriptions with associated customer contact information.
- [Query connected account data | Stripe Documentation](https://docs.stripe.com/stripe-data/query-connect-data): Connect platforms can use Sigma or Data Pipeline to query connected account information, with dedicated Connect-specific tables available in the schema. The `connected_accounts` table provides account-level details such as business name and country. An example query retrieves specific information for individual accounts in the US, detailing required verification data.
- [Query disputes and fraud data | Stripe Documentation](https://docs.stripe.com/stripe-data/query-disputes-and-fraud-data): This page explains how to query disputes and fraud data using Sigma or Data Pipeline. The `disputes` table contains information on all disputes, including evidence submitted. An example query joins the `disputes` and `charges` tables to retrieve details on lost disputes, and mentions the `radar_rules` table for those using Radar for Fraud Teams.
- [Query card issuing data | Stripe Documentation](https://docs.stripe.com/stripe-data/query-issuing-data): Stripe Sigma and Data Pipeline allow you to query card issuing data, including Authorizations, Transactions, Cards, and Cardholders. These tools provide access to detailed information about card usage and associated data, enabling custom reporting and analysis.
- [Query tax data | Stripe Documentation](https://docs.stripe.com/stripe-data/query-tax-data): Stripe Tax data, primarily found in the `tax_transactions` table, enables comprehensive tax liability reporting. Additional tables like `tax_transaction_line_items` and `tax_transaction_shipping_costs` provide further details for automated tax calculations across various Stripe products.
- [Query transactional data | Stripe Documentation](https://docs.stripe.com/stripe-data/query-transactions): Transactional data in Stripe can be queried using tables like `balance_transactions` to report on account balance activity. This table provides a ledger-style record of all incoming and outgoing transactions, including charges, refunds, transfers, and payouts, simplifying financial reporting.
- [Stripe data schema | Stripe Documentation](https://docs.stripe.com/stripe-data/schema): The Stripe data schema outlines the organizational structure of Stripe data available for querying. It serves as a reference for understanding the various tables and their relationships, aiding in the creation of custom reports and data analysis.
- [How Sigma works | Stripe Documentation](https://docs.stripe.com/stripe-data/how-sigma-works): Stripe Sigma offers an interactive SQL environment within the Stripe Dashboard for querying transactional data. It allows users to create custom financial reports, utilize pre-configured templates, and track key metrics, with a free sandbox environment for testing.
- [Sigma | Stripe Documentation](https://docs.stripe.com/stripe-data/sigma): Sigma enables the generation of custom reports for various Stripe data points like charges, refunds, and disputes through an interactive SQL environment in the Stripe Dashboard. It provides access to transactional data for payments, subscriptions, customers, and payouts, allowing for data export and scheduled fetching.
- [Migrate queries | Stripe Documentation](https://docs.stripe.com/stripe-data/migrate-queries): This document guides users on migrating Sigma queries from Presto to Trino, detailing potential issues with invalid time zones, column references, and scientific notation. It provides valid examples to ensure query compatibility with the updated Trino v414 infrastructure.
- [Schedule queries | Stripe Documentation](https://docs.stripe.com/stripe-data/schedule-queries): Sigma queries can be automated to run on a daily, weekly, or monthly basis, with results delivered via email or webhook events. Scheduling allows for recurring data retrieval as soon as the data for the specified period becomes available.
- [Use the Sigma API | Stripe Documentation](https://docs.stripe.com/stripe-data/sigma-api): The Sigma API allows programmatic execution of Sigma queries, enabling advanced use cases such as data retrieval for Jupyter notebooks or internally scheduled data extraction. Users can sign up for access to leverage these extended capabilities beyond the Sigma editor.
- [Query data across accounts belonging to an organization | Stripe Documentation](https://docs.stripe.com/stripe-data/sigma-organizations): Using Sigma with Organizations allows querying data across multiple Stripe accounts within a single organization. This feature provides insights into customers and payments across the entire business, requiring the creation of an organization and enabling Sigma in each included account.
- [Write queries | Stripe Documentation](https://docs.stripe.com/stripe-data/write-queries): The Sigma query editor allows users to compose custom queries using standard ANSI SQL, with assistance from an LLM-based query assistant. The editor provides access to saved queries, team queries, the table schema, and Stripe query templates for building reports.
- [The Stripebot web crawler | Stripe Documentation](https://docs.stripe.com/stripebot-crawler): Stripebot is Stripe's automated web crawler that collects data from user websites to provide services and comply with financial regulations. It identifies itself with a specific user-agent and can be verified through DNS lookups, with access controlled via the RFC 9309 Robots Exclusion Protocol.
- [Elements Appearance API | Stripe Documentation](https://docs.stripe.com/elements/appearance-api): The Elements Appearance API allows customization of the look and feel of Stripe Elements to match a website's design. Users can modify colors, fonts, and borders, choosing from prebuilt themes or fine-tuning individual components for a consistent user experience.
- [React Stripe.js reference | Stripe Documentation](https://docs.stripe.com/sdks/stripejs-react): React Stripe.js is a wrapper for Stripe Elements, enabling the integration of Elements into React applications. It works with the CheckoutProvider to manage Stripe object access and utilizes the Stripe.js loader for script initialization.
- [Stripe.js testing assistant | Stripe Documentation](https://docs.stripe.com/sdks/stripejs-testing-assistant): The Stripe.js testing assistant is a browser-based tool for testing and debugging Stripe Elements integrations in a sandbox environment. It offers autofill shortcuts for payment methods, highlights integration errors and warnings, and simulates customer locations to test payment method display.
- [Account and customer tax IDs with Invoicing | Stripe Documentation](https://docs.stripe.com/tax/invoicing/tax-ids): Stripe allows for the management of account and customer tax IDs, which appear on invoice and credit note PDFs. Account tax IDs can be set as default or specified for individual invoices, and can be added or deleted via the Dashboard or API before an invoice is finalized.
- [Collect taxes for recurring payments | Stripe Documentation](https://docs.stripe.com/tax/subscriptions): Stripe Tax calculates tax amounts on recurring payments when using Stripe Billing, integrating automatically with pricing models, prorations, and discounts. It uses customer location details to estimate tax before subscription creation and handles tax calculations with Stripe Tax enabled.
- [How Tax works | Stripe Documentation](https://docs.stripe.com/tax/how-tax-works): Stripe Tax automates tax compliance by determining tax obligations, calculating and collecting taxes, and assisting with reporting and filing. It accounts for varying taxability and rates based on location, product category, business address, and customer details.
- [Use Stripe Tax with Connect | Stripe Documentation](https://docs.stripe.com/tax/connect): Stripe Tax supports Connect by helping platforms and connected accounts comply with tax obligations, offering transactional reports for filing. The responsibility for tax collection and reporting may lie with the platform or the connected account, depending on the business model and regulations.
- [Countries supported by Stripe Tax | Stripe Documentation](https://docs.stripe.com/tax/supported-countries): Stripe Tax supports tax calculation on sales in various supported countries across Africa, Asia Pacific, Canada, Europe, Latin America, and the United States. Support varies by location and product type, with options for digital products and remote sales.
- [Collect customer addresses | Stripe Documentation](https://docs.stripe.com/tax/customer-locations): Stripe Tax requires your customer's location to calculate tax automatically. The system prioritizes the shipping address, then the billing address, to determine the customer's location for tax calculations. You can review the source of the address used in the Dashboard or via the Customer API object.
- [Collect taxes | Stripe Documentation](https://docs.stripe.com/payments/advanced/tax): Stripe Tax can automatically calculate and collect taxes in custom integrations using Elements. To enable this, pass `automatic_tax[enabled]=true` when creating a Checkout Session and specify a `tax_code` and `tax_behavior` for each line item. This allows Stripe Tax to handle tax calculations based on your configured settings.
- [Tax ticket sales based on event location | Stripe Documentation](https://docs.stripe.com/tax/tax-for-tickets/integration-guide): This guide explains how to integrate Stripe Tax for ticket sales, where taxes are based on the event's location, not the customer's. It outlines integration paths like Payment Intent, Checkout Session, and Custom Tax Calculation API, detailing their advantages and disadvantages for calculating taxes on admission fees and tickets.
- [Tax for ticket sales | Stripe Documentation](https://docs.stripe.com/tax/tax-for-tickets/overview): Stripe Tax assists businesses in managing the complex tax obligations for ticket sales, which are typically determined by the event's performance location. Accurate tax calculation requires providing performance location addresses, and Stripe Tax supports various integration methods for calculating these taxes.
- [File with TaxJar | Stripe Documentation](https://docs.stripe.com/tax/file-with-taxjar): Stripe Tax integrates with TaxJar to automate US sales tax filing, helping businesses file on time and avoid errors. This feature is in public preview and requires a TaxJar Tax Complete subscription, a US-based bank account, and proper setup of Stripe Tax registrations.
- [File with Taxually | Stripe Documentation](https://docs.stripe.com/tax/file-with-taxually): Stripe Tax integrates with Taxually to automate tax filing for businesses outside the US, ensuring timely and error-free submissions. The process involves setting up Stripe Tax, installing the Taxually Stripe app, creating a Taxually account, and selecting jurisdictions for filing.
- [Calculate tax | Stripe Documentation](https://docs.stripe.com/tax/calculating): Stripe calculates indirect taxes like sales tax, VAT, and GST based on factors such as seller and customer location, the activity's location, product type, and reverse charge status. It uses a single address as the customer's location for tax calculations and can also consider a specified performance location.
- [Stripe Tax | Stripe Documentation](https://docs.stripe.com/tax): Stripe Tax offers an end-to-end solution for automating sales tax, VAT, and GST compliance, including obligation monitoring, registrations, calculations, and filings. It supports various integration methods, from simple Payment Links to custom API integrations, to help businesses manage their tax obligations.
- [Automatically collect tax on Checkout sessions | Stripe Documentation](https://docs.stripe.com/tax/checkout): Stripe Tax automatically calculates taxes for all purchases and subscriptions within a Checkout session. The tax rate is determined by the customer's address, which Checkout assesses based on whether they are a new or existing customer and if shipping addresses are collected.
- [Automatically collect tax on invoices | Stripe Documentation](https://docs.stripe.com/tax/invoicing): Stripe Tax automatically calculates sales tax, VAT, and GST on invoices based on your tax settings, the customer's location and settings, and product tax codes. The tax is calculated at the published rate at the time of invoice finalization, and customer location details like country, postal code, or province are required for accurate calculation.
- [Calculate tax in your custom payment flows | Stripe Documentation](https://docs.stripe.com/tax/payment-intent): The Stripe Tax API allows for tax calculation within custom payment flows, integrating with the Payment Intents API to submit tax transactions. Tax calculation typically requires the customer's location, which can be collected using the Address Element, a custom form, or estimated via IP address.
- [Automatically collect tax on Payment Links | Stripe Documentation](https://docs.stripe.com/tax/payment-links): Stripe Tax can be used with Payment Links to automatically calculate and collect taxes on a payment page without writing code. By enabling 'Collect tax automatically' and optionally 'Collect customers' addresses,' businesses can streamline tax collection for their customers.
- [Specify tax codes and behavior on pricing plans | Stripe Documentation](https://docs.stripe.com/tax/subscriptions/pricing-plans-tax-codes-behavior): This feature, currently in private preview, allows adding tax codes and tax behavior to pricing plans to automatically calculate taxes. Assigning a tax code to each product ensures the correct tax rate and rules are applied, with a preset code used if none is explicitly specified.
- [Collect tax on usage-based rate card subscriptions | Stripe Documentation](https://docs.stripe.com/tax/subscriptions/rate-cards): This private preview feature enables Stripe Tax to calculate and collect taxes on usage-based rate card subscriptions. By setting customer location details when creating a rate card subscription, businesses can ensure automatic tax handling when the customer is ready to pay.
- [Specify tax codes and behavior on rate cards | Stripe Documentation](https://docs.stripe.com/tax/subscriptions/rate-card-tax-codes-tax-behavior): This private preview feature allows adding tax codes and tax behavior to rate cards for automatic tax calculation. Assigning a tax code to each product ensures the correct tax rate and rules are applied, with a preset code used if none is explicitly specified.
- [Update existing subscriptions | Stripe Documentation](https://docs.stripe.com/tax/subscriptions/update): When integrating Stripe Tax, existing subscriptions need to be updated to ensure automatic tax calculation. Stripe provides automated tooling to help with this process, removing manual tax rates and applying updates at the start of the next billing cycle.
- [Monitor your obligations | Stripe Documentation](https://docs.stripe.com/tax/monitoring): Stripe Tax provides insights into potential tax registration obligations, known as economic nexus in the US, based on past transactions. It tracks sales against registration thresholds to help businesses understand where they might need to collect and remit tax.
- [Tax for physical goods | Stripe Documentation](https://docs.stripe.com/tax/physical-goods): Stripe Tax supports the sale of physical goods for e-commerce businesses, handling cross-border sales according to regional laws. Businesses can configure product-specific tax codes and shipping settings, and use threshold monitoring to track registration requirements.
- [Specify product tax codes and tax behavior | Stripe Documentation](https://docs.stripe.com/tax/products-prices-tax-codes-tax-behavior): Assigning product tax codes and tax behavior to products and prices enables automatic tax calculation by Stripe Tax. Tax codes are consistent across jurisdictions, but Stripe maintains current taxability information and handles varying local tax treatments.
- [Register for sales tax, VAT, and GST | Stripe Documentation](https://docs.stripe.com/tax/registering): Businesses must identify and register with tax authorities in all applicable jurisdictions where they have tax obligations. Stripe can assist with this process, either by using the Registrations API or by registering on the business's behalf.
- [Use the Registrations API to manage tax registrations | Stripe Documentation](https://docs.stripe.com/tax/registrations-api): The Registrations API allows businesses to programmatically manage tax registrations, enabling tax calculation and collection through Stripe. It supports adding, scheduling, and checking active registrations for both direct usage and platform-managed connected accounts.
- [Set up Stripe Tax | Stripe Documentation](https://docs.stripe.com/tax/set-up): Stripe Tax can be set up automatically by configuring tax settings through the Dashboard or the Tax Settings API. Key setup steps include confirming your head office address and selecting a preset tax code for your products.
- [Use the Settings API to configure Stripe Tax | Stripe Documentation](https://docs.stripe.com/tax/settings-api): The Settings API enables the retrieval and configuration of Stripe Tax settings without using the Dashboard. This API is useful for platforms setting up Stripe Tax for connected accounts and for direct users managing their own tax configurations.
- [Collect taxes | Stripe Documentation](https://docs.stripe.com/tax/custom): Stripe Tax APIs facilitate tax calculation within custom payment flows, allowing integration with any payment processor. Key features include adding registrations, collecting customer addresses, and calculating tax server-side or client-side.
- [Collect tax in Africa | Stripe Documentation](https://docs.stripe.com/tax/supported-countries/africa/collect-tax): This page details how to collect tax in African countries using Stripe Tax, outlining country-specific registration requirements, thresholds, and supported product types. Businesses must register with local tax authorities and add their registrations in Stripe to begin collecting tax.
- [Tax in Africa | Stripe Documentation](https://docs.stripe.com/tax/supported-countries/africa): Stripe Tax supports businesses making sales into various African countries, with registration and transaction requirements varying by nation. Businesses generally need to be remote sellers without a physical presence to collect tax via Stripe, and must register with local authorities.
- [Collect tax in Asia Pacific | Stripe Documentation](https://docs.stripe.com/tax/supported-countries/asia-pacific/collect-tax): This guide explains how to collect tax in Asia Pacific countries using Stripe Tax, detailing country-specific registration thresholds and transaction types. Businesses can collect tax if based in certain countries or act as remote sellers in others.
- [Tax in Asia Pacific | Stripe Documentation](https://docs.stripe.com/tax/supported-countries/asia-pacific): Stripe Tax supports businesses selling into Asia Pacific countries, with varying registration and transaction requirements per country. Businesses based in specific APAC countries can collect tax directly, while others must operate as remote sellers.
- [Collect tax in Canada | Stripe Documentation](https://docs.stripe.com/tax/supported-countries/canada/collect-tax): This page describes how to collect tax in Canadian provinces, covering federal GST/HST and provincial taxes. It details registration thresholds, monitored transaction types, and registration resources for businesses selling into Canada.
- [Tax in Canada | Stripe Documentation](https://docs.stripe.com/tax/supported-countries/canada): Stripe Tax supports tax calculation across Canadian provinces, with varying collection requirements and transaction types. Businesses must register with the Canadian government and add their registrations in Stripe to begin collecting tax.
- [Collect tax in a European country | Stripe Documentation](https://docs.stripe.com/tax/supported-countries/europe/collect-tax): This page outlines how to collect tax in European countries outside the EU using Stripe Tax, detailing registration thresholds and transaction types. Businesses based in specific European countries can collect tax directly, while others must act as remote sellers.
- [Tax in Europe | Stripe Documentation](https://docs.stripe.com/tax/supported-countries/europe): Stripe Tax supports businesses selling into European countries (outside the EU), with registration and transaction rules varying by nation. Businesses based in certain countries can collect tax directly, while others must operate as remote sellers.
- [Collect tax in a country in the European Union | Stripe Documentation](https://docs.stripe.com/tax/supported-countries/european-union/collect-tax): This guide details how to collect tax in European Union countries, explaining that all EU countries follow EU VAT rules but have varying registration requirements. Businesses can find country-specific information on sales, tax types, and registration resources.
- [Tax in the European Union | Stripe Documentation](https://docs.stripe.com/tax/supported-countries/european-union): Stripe Tax supports tax calculation in all European Union countries, where businesses may need to collect VAT regardless of their establishment. Country-specific registration resources and rules are available, and businesses must register and add their registrations in Stripe.
- [Collect tax in Latin America and the Caribbean | Stripe Documentation](https://docs.stripe.com/tax/supported-countries/latin-america-and-caribbean/collect-tax): This page explains how to collect tax in Latin America and the Caribbean using Stripe Tax, detailing country-specific registration thresholds and transaction types. Businesses generally need to be remote sellers, with Mexico being an exception for full support.
- [Tax in Latin America and the Caribbean | Stripe Documentation](https://docs.stripe.com/tax/supported-countries/latin-america-and-caribbean): Stripe Tax supports businesses selling into Latin America and the Caribbean countries, with registration and transaction requirements varying by nation. Businesses based in Mexico are fully supported, while others must operate as remote sellers.
- [Collect tax in the United States | Stripe Documentation](https://docs.stripe.com/tax/supported-countries/united-states/collect-tax): This page details how to collect sales tax in the United States, noting that rates and rules vary by region. It provides information on registration thresholds, supported tax calculations, and registration resources for each state and territory.
- [Collect tax in the United States | Stripe Documentation](https://docs.stripe.com/tax/supported-countries/united-states): Businesses selling goods and services in the US may need to collect sales tax, with rules varying by region based on nexus (physical or economic activity). Stripe can assist with registration with local US tax authorities.
- [Product tax codes | Stripe Documentation](https://docs.stripe.com/tax/tax-codes): Product tax codes (PTCs) are used by Stripe Tax to associate products with specific tax rates, ensuring correct tax application. Businesses can set a preset tax code in their settings or assign individual PTCs to each product.
- [Tax customizations | Stripe Documentation](https://docs.stripe.com/tax/tax-customizations): Tax customizations allow businesses to define rules that alter tax behavior for specific product tax codes in any supported location. These customizations help align Stripe Tax calculations with unique business needs and local tax regulations.
- [File and remit | Stripe Documentation](https://docs.stripe.com/tax/filing): Stripe Tax requires businesses to file and remit collected taxes for every location where they are registered, with varying rules for reporting and payment frequency. Stripe Tax partners can help automate much of this process.
- [Tax for marketplaces | Stripe Documentation](https://docs.stripe.com/tax/tax-for-marketplaces): Marketplace operators may be required to collect sales tax and VAT on facilitated sales in many countries and US states. Stripe Tax can be enabled for marketplaces to calculate, collect, file, and report indirect taxes if the platform is responsible for these obligations.
- [Tax for software platforms | Stripe Documentation](https://docs.stripe.com/tax/tax-for-platforms): Software platforms can use Stripe Tax to offer pre-integrated tax compliance to their connected accounts, enabling them to calculate, collect, and report indirect taxes. Platforms must ensure connected accounts have their tax settings and registrations configured before enabling tax calculations.
- [Tax reporting | Stripe Documentation](https://docs.stripe.com/tax/reports): Stripe Tax provides itemized, summarized, and location-based reports of completed transactions to help businesses manage tax reporting. These reports can be accessed through the Dashboard and detail tax breakdowns or aggregated transaction views.
- [Testing Stripe Tax | Stripe Documentation](https://docs.stripe.com/tax/testing): Stripe Tax can be tested in a sandbox environment to preview tax calculation behavior and validate integration accuracy before going live. This involves configuring separate sandbox tax settings and adding registrations in jurisdictions to test tax collection.
- [Third-party tax apps | Stripe Documentation](https://docs.stripe.com/tax/third-party-apps): Businesses can integrate with third-party tax providers through the Stripe App Marketplace to handle tax calculations. This integration allows users to select and enable a preferred third-party tax app within Stripe's Tax settings.
- [Zero tax amounts and reverse charges | Stripe Documentation](https://docs.stripe.com/tax/zero-tax): Stripe Tax returns a zero tax amount in specific situations, such as when a business is not registered in a jurisdiction, a sale is treated as non-taxable, or a product is exempt. The `taxability_reason` field in the API response clarifies why tax was not collected.
- [Use Stripe to register for sales tax | Stripe Documentation](https://docs.stripe.com/tax/use-stripe-to-register): Stripe can register remote sellers with local tax authorities in the United States for sales and use tax collection, provided certain eligibility requirements are met. Users can initiate this registration process through the Tax page in their Stripe Dashboard.
- [Register outside the US with Taxually | Stripe Documentation](https://docs.stripe.com/tax/use-taxually-to-register): Stripe partners with Taxually to facilitate tax registrations with local authorities outside the United States. This process involves installing the Taxually app, creating a Taxually account, and providing necessary business and location information.
- [Collect card payments while offline | Stripe Documentation](https://docs.stripe.com/terminal/features/operate-offline/collect-card-payments): Stripe Terminal allows for collecting card payments even without an internet connection, storing payment information locally and attempting authorization once connectivity is restored. Users assume risks associated with offline transactions, such as potential declines or fraud.
- [Design a custom POS integration | Stripe Documentation](https://docs.stripe.com/terminal/designing-integration): Designing a custom Point of Sale (POS) integration with Stripe Terminal involves selecting a country, reader, and architecture type (server-driven or reader-driven). The server-driven approach allows POS applications to run on any device and communicate with readers via the Stripe API.
- [Example applications | Stripe Documentation](https://docs.stripe.com/terminal/example-applications): Stripe Terminal offers example applications and simulated readers to help developers test and understand their integration. These examples demonstrate the interactions between the Terminal SDK, reader, POS application, and backend.
- [Prepare for app review | Stripe Documentation](https://docs.stripe.com/terminal/features/apps-on-devices/app-review): Apps intended for Stripe readers, particularly those using Point-to-Point Encryption (P2PE) or Verifone devices, require a review process. Apps used only for development on a DevKit or on Stripe readers without P2PE may qualify for automated approval.
- [Build and test your app | Stripe Documentation](https://docs.stripe.com/terminal/features/apps-on-devices/build): Developers can build and test their applications using a SmartPOS DevKit device without needing to go through the full deployment and review process. This allows for iterative development and testing of custom POS applications for Stripe readers.
- [Deploy your app with the API | Stripe Documentation](https://docs.stripe.com/terminal/features/apps-on-devices/deploy-with-API): After app approval, Android apps can be deployed to Stripe Terminal devices via a webhook notification. Deployment involves creating a device deploy group and associating it with a location, enabling automatic updates and installations.
- [Deploy your app in the Dashboard | Stripe Documentation](https://docs.stripe.com/terminal/features/apps-on-devices/deploy-in-Dashboard): Android apps for Stripe Terminal devices can be deployed directly through the Stripe Dashboard after approval. This process involves adding or editing a deploy group, which then pushes the app to selected devices, initiating an automatic reboot for installation.
- [Monitor your deployment | Stripe Documentation](https://docs.stripe.com/terminal/features/apps-on-devices/monitor): The deployment progress of Android apps on Stripe smart readers can be monitored in the Stripe Dashboard under Terminal > Software. This allows users to view the status of deployed apps, identify issues, and check the number of readers in various deployment states.
- [Apps on Devices | Stripe Documentation](https://docs.stripe.com/terminal/features/apps-on-devices/overview): Apps on Devices allows for running custom point-of-sale (POS) applications and other apps directly on Stripe smart readers. This feature supports the full app lifecycle, from building and testing to deployment and monitoring, with the Terminal SDK handling payments and compliance.
- [Submit your app | Stripe Documentation](https://docs.stripe.com/terminal/features/apps-on-devices/submit): After finalizing an Android app for Stripe readers, it must be submitted via the Stripe Dashboard. Apps requiring a review must follow specific guidelines to ensure a timely and successful review process.
- [Troubleshoot apps on devices | Stripe Documentation](https://docs.stripe.com/terminal/features/apps-on-devices/troubleshooting): Troubleshooting apps on devices involves resolving issues such as APK upload timeouts due to large file sizes or slow internet speeds. Uploading the APK to a faster server before sending it to Stripe can help overcome these limitations.
- [Display cart details | Stripe Documentation](https://docs.stripe.com/terminal/features/display): Stripe Terminal allows you to display line items and the total transaction amount on the reader's screen using the setReaderDisplay method. Your application must calculate tax and totals before passing them to this method for display purposes only.
- [Collect swiped data | Stripe Documentation](https://docs.stripe.com/terminal/features/collect-data): Stripe Terminal's private preview feature enables collecting non-PCI data, such as gift card information, using the reader's hardware interfaces like the magnetic stripe reader. The SDK provides a tokenized data object after swiping, which can be used to securely retrieve the cleartext track data on your backend.
- [Collect on-screen inputs | Stripe Documentation](https://docs.stripe.com/terminal/features/collect-inputs): Stripe Terminal smart readers can display input forms to collect various types of customer information, including phone numbers, emails, signatures, selections, and text. These forms can be presented before, after, or outside of a payment cycle, but should not be used for sensitive data.
- [Collect tapped data for NFC instruments | Stripe Documentation](https://docs.stripe.com/terminal/features/collect-nfc-data): This Stripe Terminal feature, currently in private preview, allows the collection of NFC instrument unique identifiers (UIDs) using the reader's contactless interface, even offline. The Terminal SDK provides a data object with the NFC UID after a tap, but this cannot be used for collecting card payments.
- [Use Terminal with Connect | Stripe Documentation](https://docs.stripe.com/terminal/features/connect): Stripe Terminal integrates with Connect platforms, enabling both the platform and connected accounts to accept in-person payments. The integration method depends on how the platform processes payments, whether through direct charges, destination charges, or separate charges and transfers, utilizing specific API keys and headers for identification.
- [Extended authorizations | Stripe Documentation](https://docs.stripe.com/terminal/features/extended-authorizations): Extended authorizations in Stripe Terminal allow capturing a confirmed PaymentIntent up to 30 days later, which is useful for businesses with longer fulfillment periods like hotels. This feature is available for major card brands but not for single-message payment methods.
- [Incremental authorizations | Stripe Documentation](https://docs.stripe.com/terminal/features/incremental-authorizations): Incremental authorizations in Stripe Terminal permit increasing the authorized amount of a PaymentIntent before capture, accommodating changes in total price or added items. This functionality is available for specific card brands and requires the transaction to be made with a POS and reader.
- [Mail order and telephone order (MOTO) payments | Stripe Documentation](https://docs.stripe.com/terminal/features/mail-telephone-orders/overview): Mail order and telephone order (MOTO) payments can be processed using Stripe Terminal by entering card details directly on supported readers like the Stripe Reader S700/S710 or BBPOS WisePOS E. Contact Stripe support to enable this feature, which prompts for card number, CVC, expiration date, and postal code.
- [Collect on-reader tips | Stripe Documentation](https://docs.stripe.com/terminal/features/collecting-tips/on-reader): On-reader tipping allows Stripe Terminal readers to display suggested tip amounts to customers before payment, with the selected tip being included in the confirmed PaymentIntent. This feature is available on specific readers like the Stripe Reader S700/S710 and BBPOS WisePOS E.
- [Collect on-receipt tips | Stripe Documentation](https://docs.stripe.com/terminal/features/collecting-tips/on-receipt): On-receipt tipping enables customers to add a tip after authorizing a card, typically used in dining and hospitality settings within the US. This is achieved through overcapture, where the captured amount exceeds the authorized amount, and requires the PaymentIntent to have a manual capture method.
- [Accept offline payments | Stripe Documentation](https://docs.stripe.com/terminal/features/operate-offline/overview): Stripe Terminal allows accepting payments offline by storing them locally on the POS device or smart reader, automatically forwarding them to Stripe once a network connection is restored. The payment collection process remains similar to online operations, with the SDK providing callbacks for offline events.
- [Print content on a reader | Stripe Documentation](https://docs.stripe.com/terminal/features/print-content): The Verifone V660p reader, equipped with an embedded printer, can print custom content like receipts or tickets directly from Stripe Terminal integrations. Your integration must generate the content as a black and white image file, adhering to specific size and clarity guidelines.
- [Provide receipts | Stripe Documentation](https://docs.stripe.com/terminal/features/receipts): Stripe Terminal facilitates providing compliant physical or email receipts to customers, meeting card network rules for in-person payments. You can use Stripe's prebuilt email receipts or generate custom receipts using API data, ensuring all required fields are included.
- [Refund transactions | Stripe Documentation](https://docs.stripe.com/terminal/features/refunds): Stripe Terminal supports canceling authorized but uncaptured payments, or refunding captured payments via the refunds API or Dashboard. This feature is available for most major card brands, with automatic capture and refunding for single-message payment methods.
- [Save payment details after payment | Stripe Documentation](https://docs.stripe.com/terminal/features/saving-payment-details/save-after-payment): Stripe Terminal enables saving payment details from an in-store purchase for future customer-not-present use, such as recurring subscriptions or online orders. A successful card_present payment generates a reusable card PaymentMethod in the generated_card attribute.
- [Save directly without charging | Stripe Documentation](https://docs.stripe.com/terminal/features/saving-payment-details/save-directly): Use SetupIntents with Stripe Terminal to collect and save card or mobile wallet details without charging the card, creating a reusable generated_card PaymentMethod for online use. Note that charges using this method are card-not-present (CNP) and do not qualify for associated benefits.
- [Collect and save payment details for future use | Stripe Documentation](https://docs.stripe.com/terminal/features/saving-payment-details/overview): Stripe Terminal allows collecting and saving payment methods, including NFC-based mobile wallets, for online reuse with returning customers. This can be done directly without charging, or after a payment, enabling online subscriptions or deferred payments.
- [Collect tips | Stripe Documentation](https://docs.stripe.com/terminal/features/collecting-tips/overview): Stripe Terminal offers two methods for collecting voluntary tips: on-receipt tipping (collected during capture) and on-reader tipping (suggested before payment). Mandatory tips must be included in the original PaymentIntent amount.
- [Configure the admin menu passcode | Stripe Documentation](https://docs.stripe.com/terminal/fleet/admin-menu-passcode): The admin menu on Stripe Terminal smart readers provides access to settings like Wi-Fi, appearance, and diagnostics, with a default passcode of 07139. For security, it's recommended to set a custom 5-digit passcode at the account or location level.
- [Configure the cellular network | Stripe Documentation](https://docs.stripe.com/terminal/fleet/cellular): The Stripe Reader S710 supports cellular connectivity, allowing it to automatically connect via cellular when Wi-Fi is unavailable. Cellular functionality is enabled by configuring locations in the Dashboard or via the Configuration API, and usage incurs monthly fees.
- [Terminal configurations | Stripe Documentation](https://docs.stripe.com/terminal/fleet/configurations-overview): Stripe Terminal Configurations allow you to apply settings like splash screens and tipping options to your readers. These configurations can be set at the account level for all readers or at the individual location level, with location-specific settings overriding account-level ones.
- [Manage locations | Stripe Documentation](https://docs.stripe.com/terminal/fleet/locations-and-zones): Locations and zones in Stripe Terminal help group and manage readers by physical site. Locations allow for reader monitoring and location-based settings, while zones offer an optional way to categorize broader groups of locations or readers.
- [Monitor readers | Stripe Documentation](https://docs.stripe.com/terminal/fleet/monitor-readers): The Stripe Dashboard provides tools to monitor the performance and operational data of your Stripe Terminal devices. You can view a list of all registered readers, apply filters, and access detailed information for each individual reader.
- [Configure offline mode | Stripe Documentation](https://docs.stripe.com/terminal/fleet/offline-mode): Stripe Terminal's offline mode allows your POS device to store payments locally when network connectivity is intermittent or unavailable. Once a connection is restored, the SDK automatically forwards these stored payments to Stripe.
- [Configure the reboot time window | Stripe Documentation](https://docs.stripe.com/terminal/fleet/reboot-time): You can customize the reboot time window for your Stripe Terminal readers to avoid interruptions during business hours. Readers will reboot randomly within the configured time period for their registered location's local time, rather than all at once.
- [Register readers | Stripe Documentation](https://docs.stripe.com/terminal/fleet/register-readers): Registering your Stripe Terminal reader to a location is mandatory for accepting payments. The registration process differs for smart readers and mobile readers, with smart readers offering registration via a code, serial number, or order number.
- [Configure readers with a custom splash screen | Stripe Documentation](https://docs.stripe.com/terminal/fleet/splash-screen): You can set a custom splash screen for your Stripe Terminal readers, which appears when the reader is ready to accept payments. This can be configured as an account-wide default or customized for individual locations, overriding the account default.
- [Configure on-reader tips | Stripe Documentation](https://docs.stripe.com/terminal/fleet/tipping): Stripe Terminal allows you to configure on-reader tipping options, displaying suggested tip amounts or percentages before customers present their payment method. These tipping settings can be customized per location.
- [Configure the WiFi network | Stripe Documentation](https://docs.stripe.com/terminal/fleet/wifi): Stripe Terminal enables remote configuration and management of WiFi networks for sPOS readers, supporting various security types like WPA/WPA2 Personal and Enterprise. Once configured, readers can connect automatically without user intervention.
- [Terminal | Stripe Documentation](https://docs.stripe.com/terminal): Stripe Terminal allows businesses to accept in-person card payments using card readers, unifying online and in-person payment management within the Stripe Dashboard. It offers flexible SDKs for integration into existing or custom POS systems.
- [Place hardware orders | Stripe Documentation](https://docs.stripe.com/terminal/fleet/order-and-return-readers): You can order pre-certified reader hardware and accessories compatible with Stripe Terminal directly from the Stripe Dashboard or via the Stripe API. Ordering directly from Stripe ensures readers are pre-loaded with payment applications and encryption keys.
- [Submit a warranty claim | Stripe Documentation](https://docs.stripe.com/terminal/fleet/submitting-warranty-claim): Submit warranty claims for defective Stripe Terminal readers through the Stripe Dashboard by providing the reader's serial number. Stripe provides a one-year limited warranty against defects in materials and workmanship for Terminal products.
- [Process MOTO payments | Stripe Documentation](https://docs.stripe.com/terminal/features/mail-telephone-orders/payments): Stripe Terminal supports processing Mail Order and Telephone Order (MOTO) payments, requiring access to be requested from Stripe support. This involves creating a PaymentIntent, processing the payment, and verifying the reader state.
- [Save a card with MOTO for future payments | Stripe Documentation](https://docs.stripe.com/terminal/features/mail-telephone-orders/save-directly): You can save card details from Mail Order and Telephone Order (MOTO) payments for future use with Stripe Terminal. This requires creating or retrieving a Customer, creating a SetupIntent, and then charging the saved PaymentMethod.
- [Accept in-person payments with Terminal | Stripe Documentation](https://docs.stripe.com/terminal/overview): Stripe Terminal integrates Stripe payments into in-person checkout flows and mobile/web applications, offering SDKs, Tap to Pay capabilities, and reader management tools. It unifies online and in-person payments and can be integrated with Connect platforms.
- [Additional payment methods | Stripe Documentation](https://docs.stripe.com/terminal/payments/additional-payment-methods): Stripe Terminal supports additional QR code-based payment methods like WeChat Pay, Affirm, and PayNow, in addition to cards. Customers scan a QR code displayed on smart or Tap to Pay readers to complete checkout on their mobile devices.
- [Collect card payments | Stripe Documentation](https://docs.stripe.com/terminal/payments/collect-card-payment): To collect card payments with Stripe Terminal, you prepare your application and backend to create and update a PaymentIntent, which represents a payment session. For certain readers, a server-side integration using the Stripe API is recommended over an SDK.
- [Connect to a reader | Stripe Documentation](https://docs.stripe.com/terminal/payments/connect-reader): You can connect your application to a Stripe Terminal reader using simulated readers for development and testing without physical hardware. Simulated readers are created using specific registration codes and function only in a sandbox environment.
- [Regional considerations | Stripe Documentation](https://docs.stripe.com/terminal/payments/regional): While Stripe Terminal integrations are largely consistent across countries, regional considerations and local regulations may apply. Both the Stripe account and the reader's location must be in the same country and accept local currency only.
- [Stripe Reader S700/S710 accessories | Stripe Documentation](https://docs.stripe.com/terminal/payments/stripe-reader-s700-s710/accessories): Stripe offers accessories for the Stripe Reader S700/S710, including protective cases and hubs for expanded I/O. These accessories are designed to enhance the functionality and durability of the readers.
- [Set up BBPOS Chipper 2X BT | Stripe Documentation](https://docs.stripe.com/terminal/payments/setup-reader/bbpos-chipper2xbt): The BBPOS Chipper 2X BT is a handheld reader for mobile applications that connects via Bluetooth Low Energy or USB. It is compatible with iOS, Android, and React Native SDKs, but is no longer available for purchase and is not recommended for new integrations.
- [Set up Stripe Reader M2 | Stripe Documentation](https://docs.stripe.com/terminal/payments/setup-reader/stripe-m2): The Stripe Reader M2 is a compact reader designed for mobile applications, connecting via Bluetooth Low Energy or USB (Android only). It supports iOS, Android, and React Native SDKs. Users are advised to keep the reader dry as it is not liquid-proof.
- [Verifone M425 reader | Stripe Documentation](https://docs.stripe.com/terminal/payments/setup-reader/m425): The Verifone M425 is an Android-based smart reader for countertop use, connecting to the Stripe Terminal SDK over the internet or LAN. It supports JavaScript, iOS, Android, and React Native SDKs, with a recommendation for server-driven integration. Support is in public preview for the US and CA.
- [Set up Verifone P400 | Stripe Documentation](https://docs.stripe.com/terminal/payments/setup-reader/verifone-p400): The Verifone P400 is a countertop reader for Stripe Terminal apps that connects via the internet. It is compatible with JavaScript, iOS, Android, and React Native SDKs, but is no longer available for purchase and not recommended for new integrations.
- [Verifone P630 reader | Stripe Documentation](https://docs.stripe.com/terminal/payments/setup-reader/p630): The Verifone P630 is an Android-based smart reader for countertop use, connecting via the internet or LAN. It supports various SDKs and recommends a server-driven integration. Support is in public preview for the US and CA, and private preview for Ireland, the UK, and Singapore.
- [Set up Stripe Reader S700/S710 | Stripe Documentation](https://docs.stripe.com/terminal/payments/setup-reader/stripe-reader-s700-s710): The Stripe Reader S700/S710 is an Android-based smart reader suitable for countertop and handheld use, offering customizable on-reader UI. It connects via internet, LAN, or handoff mode and supports multiple SDKs, with a recommendation for server-driven integration.
- [Select your reader | Stripe Documentation](https://docs.stripe.com/terminal/payments/setup-reader): This page provides an overview of Stripe's pre-certified card readers and Tap to Pay, guiding users to select the best reader for their application and sales environment. It also details how to order readers from the Dashboard.
- [Tap to Pay | Stripe Documentation](https://docs.stripe.com/terminal/payments/setup-reader/tap-to-pay): Tap to Pay enables contactless payments on compatible iPhone or Android devices, supporting various cards and mobile wallets. It is integrated into the Terminal iOS and React Native SDKs for direct payment processing.
- [Verifone UX700 reader | Stripe Documentation](https://docs.stripe.com/terminal/payments/setup-reader/ux700): The Verifone UX700 is a smart reader for countertop use, connecting via internet, LAN, or handoff mode. It supports multiple SDKs and recommends a server-driven integration. Support is in public preview for the US and CA, and private preview for Ireland and the UK.
- [Verifone V660p reader | Stripe Documentation](https://docs.stripe.com/terminal/payments/setup-reader/v660p): The Verifone V660p is a smart reader connecting via internet, LAN, or handoff mode, supporting various SDKs and recommending server-driven integration. Support is in public preview for the US and CA, and private preview for Ireland, the UK, and Singapore.
- [Set up Verifone readers | Stripe Documentation](https://docs.stripe.com/terminal/payments/setup-reader/verifone): This page details the setup for Verifone readers compatible with Stripe Terminal, noting that support is in public preview for the US and Canada, with some readers in private preview for other regions. It highlights that different Verifone models have unique strengths and availability varies by country.
- [Set up BBPOS WisePad 3 | Stripe Documentation](https://docs.stripe.com/terminal/payments/setup-reader/bbpos-wisepad3): The BBPOS WisePad 3 is a handheld reader for mobile applications, connecting via Bluetooth Low Energy or USB (Android only). It features a display and PIN pad, making it suitable for regions where PIN authentication is common, and is compatible with iOS, Android, and React Native SDKs.
- [Set up BBPOS WisePOS E | Stripe Documentation](https://docs.stripe.com/terminal/payments/setup-reader/bbpos-wisepos-e): The BBPOS WisePOS E is a countertop reader for Stripe Terminal apps that connects via the internet or LAN. It supports multiple SDKs and recommends a server-driven integration. Users are advised to keep the reader dry as it is not liquid-proof.
- [Set up your integration | Stripe Documentation](https://docs.stripe.com/terminal/payments/setup-integration): This guide helps set up Stripe Terminal integrations, supporting either the Terminal SDK or a server-driven approach for in-person payments. Server-driven integrations utilize the Stripe API and are recommended for smart readers like WisePOS E and S700/S710, offering greater flexibility.
- [Stripe Terminal global availability | Stripe Documentation](https://docs.stripe.com/terminal/payments/collect-card-payment/supported-card-brands): Stripe Terminal is available in numerous countries, with specific regions offering only Tap to Pay functionality. The page details supported payment methods, including cards and NFC-based mobile wallets, and notes that transactions must be processed in the local currency.
- [Verifone accessories | Stripe Documentation](https://docs.stripe.com/terminal/payments/verifone/accessories): This page lists accessories available for Stripe-supported Verifone readers, including power supplies and cables for the V660p and UX700 models. It notes that Verifone reader support is in public preview for the US and Canada, with some readers in private preview for other regions.
- [Deployment checklist | Stripe Documentation](https://docs.stripe.com/terminal/references/checklist): This checklist ensures a smooth deployment of Stripe Terminal by covering critical hardware and software integration steps. It emphasizes correctly setting up the ConnectionToken endpoint on your backend to manage reader access and avoid hard-coding tokens.
- [JavaScript API reference | Stripe Documentation](https://docs.stripe.com/terminal/references/api/js-sdk): This page provides the API reference for the Stripe Terminal JavaScript SDK, detailing methods for creating a terminal instance, discovering and connecting readers, and processing payments. It outlines options for configuring the SDK, such as handling connection tokens and unexpected reader disconnections.
- [Terminal network requirements | Stripe Documentation](https://docs.stripe.com/terminal/network-requirements): Terminal network requirements vary based on the readers and integration method used. Mobile readers need internet connectivity for the point-of-sale device, while smart readers, especially with server-driven integrations, are recommended to minimize network issues.
- [Stripe Terminal reader product sheets | Stripe Documentation](https://docs.stripe.com/terminal/readers/product-sheets): This page provides access to Stripe Terminal reader product sheets, containing hardware specifications, operating information, and manufacturer disclosures. It lists available readers like the S700/S710, M2, BBPOS Chipper 2X BT, WisePad 3, WisePOS E, and various Verifone models.
- [BBPOS Chipper 2X BT | Stripe Documentation](https://docs.stripe.com/terminal/readers/bbpos-chipper2xbt): The BBPOS Chipper 2X BT is a handheld reader for Stripe Terminal that connects via Bluetooth LE or USB to mobile devices. It is no longer available for purchase, and users are directed to current supported reader offerings.
- [BBPOS WisePad 3 | Stripe Documentation](https://docs.stripe.com/terminal/readers/bbpos-wisepad3): The BBPOS WisePad 3 is a handheld reader for Stripe Terminal that connects via Bluetooth LE or USB to mobile devices. It features a display and PIN pad, making it suitable for regions where PIN authentication is common.
- [BBPOS WisePOS E | Stripe Documentation](https://docs.stripe.com/terminal/readers/bbpos-wisepos-e): The BBPOS WisePOS E is a countertop reader for Stripe Terminal that connects to the SDKs over the internet. It is recommended for server-driven integrations and is compatible with JavaScript, iOS, Android, and React Native SDKs.
- [Stripe Terminal mobile readers | Stripe Documentation](https://docs.stripe.com/terminal/mobile-readers): Stripe Terminal mobile readers, including the Stripe Reader M2, BBPOS Chipper 2X BT, and BBPOS WisePad 3, connect to iOS, Android, and React Native SDKs via Bluetooth LE or USB. These readers update automatically, but applications must support these updates to ensure continued payment processing.
- [Stripe Terminal smart readers | Stripe Documentation](https://docs.stripe.com/terminal/smart-readers): Stripe Terminal smart readers, such as the Stripe Reader S700/S710 and BBPOS WisePOS E, are compatible with various SDKs and connect over the internet. These readers receive automatic software updates from Stripe when connected to power.
- [Troubleshoot M425 | Stripe Documentation](https://docs.stripe.com/terminal/readers/reference/m425): This page provides troubleshooting steps for the Verifone M425 reader, an Android-based smart reader for Stripe Terminal. It covers network requirements, common issues, and how to run built-in diagnostics for connectivity and configuration problems.
- [Troubleshoot P630 | Stripe Documentation](https://docs.stripe.com/terminal/readers/reference/p630): This document offers troubleshooting guidance for the Verifone P630 reader, an Android-based smart reader for Stripe Terminal. It details network requirements, common troubleshooting scenarios, and the use of built-in diagnostics for connectivity and configuration issues.
- [Stripe Reader M2 | Stripe Documentation](https://docs.stripe.com/terminal/readers/stripe-m2): The Stripe Reader M2 is a compact, durable reader for mobile applications, connecting via Bluetooth LE or USB to the Stripe Terminal SDK. It is compatible with iOS, Android, and React Native SDKs, and its LEDs indicate battery and charging status.
- [Stripe Reader S700/S710 | Stripe Documentation](https://docs.stripe.com/terminal/readers/stripe-reader-s700-s710): The Stripe Reader S700/S710 is an Android-based smart reader for Stripe Terminal, usable in countertop and handheld configurations. It connects via internet, LAN, or handoff mode and supports various SDKs, with a recommendation for server-driven integration for systems without offline payment needs.
- [Stripe Terminal Tap to Pay readers | Stripe Documentation](https://docs.stripe.com/terminal/tap-to-pay-readers): Stripe Terminal's Tap to Pay readers, including Tap to Pay on iPhone and Android, are compatible with iOS, Android, and React Native SDKs. These readers often initiate automatic software updates, which applications must support to maintain payment processing functionality.
- [Troubleshoot UX700 | Stripe Documentation](https://docs.stripe.com/terminal/readers/reference/ux700): This page provides troubleshooting information for the Verifone UX700 reader, an Android-based smart reader for Stripe Terminal. It covers network requirements, common issues, and how to access built-in diagnostics to identify connectivity and configuration problems.
- [Troubleshoot V660p | Stripe Documentation](https://docs.stripe.com/terminal/readers/reference/v660p): This document details troubleshooting for the Verifone V660p reader, an Android-based smart reader for Stripe Terminal. It outlines network requirements, common troubleshooting scenarios, and the procedure for running built-in diagnostics to resolve connectivity and configuration issues.
- [Verifone P400 | Stripe Documentation](https://docs.stripe.com/terminal/readers/verifone-p400): The Verifone P400 is a countertop reader for Stripe Terminal that connects over the internet and is compatible with various SDKs. This reader is no longer available for purchase, and users are advised to explore current supported reader options.
- [Terminal SDK migration guide | Stripe Documentation](https://docs.stripe.com/terminal/references/sdk-migration-guide): This guide details the changes and steps required to migrate to version 5.0.0 of the Stripe Terminal SDK for iOS and Android. It addresses breaking changes in APIs and behavior to help developers update their integrations for improved consistency and simplified logic.
- [Terminal SDK V3 migration guide | Stripe Documentation](https://docs.stripe.com/terminal/references/sdk-v3-migration-guide): This guide outlines the necessary steps to migrate to version 3.0.0 of the Stripe Terminal SDK for iOS and Android. It covers breaking changes in APIs and behavior, aiming to simplify application logic and integration by improving SDK consistency.
- [Terminal SDK V4 migration guide | Stripe Documentation](https://docs.stripe.com/terminal/references/sdk-v4-migration-guide): This guide explains how to migrate to version 4.0.0 of the Stripe Terminal SDK for iOS and Android, detailing breaking API and behavior changes. The updates aim to enhance SDK consistency and simplify integration logic for developers.
- [Test Stripe Terminal | Stripe Documentation](https://docs.stripe.com/terminal/references/testing): This page explains how to effectively test Stripe Terminal integrations, recommending the use of a reader simulator and physical test cards. It notes that Stripe Terminal cannot be used with mobile wallets in test mode, similar to online Stripe payments.
- [Terraform | Stripe Documentation](https://docs.stripe.com/terraform): The Stripe Terraform provider allows management of Stripe resources through infrastructure as code, enabling declarative configuration of products, prices, and billing. It supports various resources and workflows for reproducible and auditable Stripe infrastructure management.
- [Install the Stripe Terraform provider | Stripe Documentation](https://docs.stripe.com/terraform/install): This guide details how to install and configure the Stripe Terraform provider for local development, enabling infrastructure as code for managing Stripe resources. It includes sample workflows for creating products, prices, and webhook endpoints, along with a list of supported resources.
- [Supported resources | Stripe Documentation](https://docs.stripe.com/terraform/resources): This page lists and describes the supported resources for the Stripe Terraform provider, including billing meters. Each resource example includes a brief description and a link to the relevant Stripe API reference for detailed information.
- [Test your integration | Stripe Documentation](https://docs.stripe.com/testing/overview): This page provides an overview of Stripe's testing tools and environments, including sandboxes and test values, to help developers simulate transactions and verify integrations before going live. It emphasizes the importance of testing to ensure functionality and identify potential issues in a safe, non-production environment.
- [Testing use cases | Stripe Documentation](https://docs.stripe.com/testing-use-cases): This document details Stripe's testing use cases, highlighting the use of test mode and Sandboxes to simulate transactions without real charges. It recommends Sandboxes for their advanced functionality and suggests using QA testing scenarios and Postman collections for a comprehensive testing process.
- [Test card numbers | Stripe Documentation](https://docs.stripe.com/testing): This page explains how to use test card numbers and other test values within Stripe's sandbox environment to simulate various payment scenarios and errors. It stresses the importance of using test API keys and not real card details to ensure secure and effective integration testing.
- [Test Apple and Google wallet rendering | Stripe Documentation](https://docs.stripe.com/testing/wallets): This page guides users on testing the rendering of Apple Pay and Google Pay integrations with Stripe. It provides a demo to visually compare wallet displays and offers troubleshooting steps if the wallets do not appear as expected in the integration.
- [TLS Certificates | Stripe Documentation](https://docs.stripe.com/tls-certificates): This document explains how Stripe uses Transport Layer Security (TLS) certificates to ensure secure API communication over HTTPS. It details the function of TLS certificates in verifying server identity and advises against certificate pinning to avoid integration issues during certificate updates.
- [Tour of the API | Stripe Documentation](https://docs.stripe.com/payments-api/tour): This API tour provides an in-depth look at Stripe's API objects and their interactions, explaining core concepts and best practices for building integrations. It helps developers understand the lifecycle of objects and how to manage complex payment processes beyond basic tutorials.
- [Transfer Payout Split: Stripe-Version 2017-04-06 | Stripe Documentation](https://docs.stripe.com/transfer-payout-split): This page details a Stripe API version change from April 6, 2017, that split the `/v1/transfers` resource into `/v1/transfers` for Connect-related money movement and `/v1/payouts` for moving money out of Stripe. This change aimed to clarify fund flows and improve API structure without requiring immediate changes to existing integrations.
- [Get started with API access to Financial Accounts for platforms | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/access): This guide helps platforms get started with API access to Financial Accounts for platforms, emphasizing the use of sandbox environments for testing before live integration. It outlines steps to enable Issuing and Financial Accounts capabilities on connected accounts within a sandbox.
- [Accounts structure | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/account-management/accounts-structure): This page explains the account structure for Financial Accounts for platforms, noting the requirement for Stripe Connect and differentiating between platform and connected accounts as Account objects. It clarifies that Accounts v2 API is not compatible and specifies that only Custom connected accounts are supported.
- [Financial account features | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/account-management/financial-account-features): This document outlines the features available for financial accounts within Stripe's platform, including capabilities for moving money and attaching payment cards. It highlights that certain features require specific capabilities to be active on the connected account, such as card_issuing.
- [Working with Stripe Issuing cards | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/account-management/issuing-cards): This guide explains how to integrate Stripe Issuing cards with Financial Accounts for platforms, detailing the process of enabling the card_issuing capability on connected accounts. It provides code examples for requesting necessary account and financial account features.
- [Platform financial accounts | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/account-management/platform-financial-account): This page describes the platform financial account automatically provisioned by Stripe when API access to Financial Accounts for platforms is granted. It explains that this test account in sandbox environments allows for integration testing without affecting live accounts and that the live account serves as working capital.
- [Financial Accounts for platforms supportability for connected accounts | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/account-management/supportability): This document details the requirements for connected accounts to be supported by Financial Accounts for platforms, including business eligibility and compliance with bank policies. It explains how Stripe reviews accounts for supportability and how to check for outstanding requirements via the API.
- [Working with balances and transactions | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/account-management/working-with-balances-and-transactions): This page explains how financial accounts have separate balances from their associated platform or connected accounts, detailing the components of these balances: cash, inbound_pending, and outbound_pending. It describes how Transaction and TransactionEntry objects affect these balances.
- [Working with connected accounts | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/account-management/connected-accounts): This guide outlines how platforms manage connected accounts for Financial Accounts for platforms, emphasizing the need for a Stripe Connect integration and specific account types (Custom connected accounts). It details the platform's responsibility for requirements collection and loss liability.
- [Working with financial accounts | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/account-management/financial-accounts): This page explains how to work with financial accounts, which store, send, and receive funds, and have balances separate from their linked accounts. It clarifies that API access enables provisioning financial accounts for connected accounts, with distinct balances for each.
- [Integrate with Fifth Third Bank | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/fifth-third): This document introduces Fifth Third Bank as a new bank partner for Stripe's Financial Accounts for platforms product. It explains how this integration works with existing Financial Accounts for platforms setups and directs new users to a separate getting started guide.
- [Build a new Financial Accounts for platforms integration with Fifth Third Bank | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/fifth-third-get-started): This guide provides instructions for building a new Financial Accounts for platforms integration using Fifth Third Bank, emphasizing the use of sandbox environments for testing. It covers enabling features in sandboxes and the steps required for live mode compliance reviews.
- [Financial Accounts for platforms product marketing, design, and compliance guidelines | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/compliance): This document outlines marketing and compliance guidelines for using Stripe Financial Accounts for platforms and Issuing products. It stresses the importance of adhering to financial regulations, providing necessary disclosures, and ensuring compliant customer communications and user interfaces.
- [Handling complaints | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/handling-complaints): This page details the mandatory process for handling complaints related to Stripe Financial Accounts for platforms or Issuing. It requires platforms to provide accessible complaint submission methods, acknowledge complaints within 5 business days, and resolve them within 15 business days, while maintaining records.
- [Marketing Financial Accounts for platforms | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/marketing-financial-accounts): This page provides guidelines for marketing financial accounts to platforms, emphasizing the use of compliant terminology to avoid regulatory scrutiny. It offers recommended terms for describing these accounts and services, such as 'money management account' or 'cash management solution,' and lists terms to avoid.
- [Regulatory receipts | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/moving-money/regulatory-receipts): Platforms must provide regulatory transaction receipts to customers involved in regulated transactions facilitated by Stripe's money movement resources. Stripe hosts these receipts, which include transaction details and disclosures, and provides a URL for platforms to access and present them to their connected accounts.
- [Use Financial Accounts for platforms and Issuing to set up financial accounts and cards | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/examples/financial-accounts): This guide demonstrates how a platform can integrate Stripe Financial Accounts and Issuing to set up financial accounts and create payment cards for its users. It outlines the platform onboarding process and highlights the use of Accounts v1 for managing treasury and card-issuing capabilities when using the Accounts v2 API.
- [Using Financial Accounts for platforms to move money | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/examples/moving-money): This page explains how to use Stripe Financial Accounts for platforms to move money between connected accounts, external bank accounts, and financial accounts. It details the use of API endpoints like InboundTransfer and OutboundTransfer to facilitate these money movements.
- [Financial Accounts for platforms connected account onboarding guide | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/examples/onboarding-guide): This guide focuses on the connected account onboarding process when using Stripe Financial Accounts for platforms, emphasizing fraud prevention and regulatory compliance. It stresses the importance of collecting Know Your Customer (KYC) and Know Your Business (KYB) information upfront, recommending against incremental onboarding.
- [Financial Accounts for platforms fraud guide | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/examples/fraud-guide): This page provides a guide to managing fraud within Stripe Financial Accounts for platforms, outlining common fraud types like business fraud, transaction fraud, and account takeover fraud. It explains how Financial Accounts for platforms, an embedded finance API, allows platforms to offer financial services like stored-value accounts and card spending.
- [Issuing and Financial Accounts for platforms sample app | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/examples/sample-app): This document introduces a Next.js sample app that helps developers integrate Stripe Issuing and Financial Accounts for platforms. The sample app provides practical examples for features like onboarding connected accounts, displaying account information and transactions, and simulating money transfers.
- [Webhooks for Stripe Issuing and Financial Accounts for platforms | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/examples/webhooks): This page explains how Stripe uses webhooks to notify applications about events related to Issuing and Financial Accounts for platforms, such as the creation of an authorization or an ACH transfer. It notes that Connect webhooks encompass all events on a connected account, including those generated by Financial Accounts for platforms and Issuing integrations.
- [How Financial Accounts for platforms works | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/how-financial-accounts-for-platforms-works): Financial Accounts for platforms is a suite of APIs enabling Stripe Connect platforms to embed financial services for their connected accounts. It allows accounts to hold funds, pay bills, and manage cash flow through modular components, with Stripe providing the infrastructure in partnership with banks.
- [Moving money using CreditReversal objects | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/moving-money/into/credit-reversals): This page details how to use CreditReversal objects to return funds from received credits that have added money to a financial account. It explains the conditions under which a ReceivedCredit can be reversed, depending on the network and source flow, and provides details on restricted reasons and deadlines.
- [Moving money with using InboundTransfer objects | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/moving-money/into/inbound-transfers): This page describes how to use InboundTransfer objects to move money from an external US bank account into a financial account via the ACH network. It specifies that these transfers are initiated with InboundTransfer objects and typically take 2-4 business days to complete, excluding same-day ACH.
- [Moving money using ReceivedCredit objects | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/moving-money/into/received-credits): This page explains that when funds enter a financial account, Stripe generates a ReceivedCredit object containing details about the transfer source. It covers how to send funds using account and routing numbers for ACH and wire transfers, or a financial account ID for internal transfers.
- [Money movement timelines | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/money-movement/timelines): This page outlines the timelines for various money movement operations within Financial Accounts for platforms, considering the processing and cutoff times of banking partners and payment networks. It details the expected arrival times for ACH, domestic wire, and Stripe network transfers.
- [Moving money into financial accounts | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/moving-money/moving-money-into-financial-accounts): This page covers the available requests for moving money into financial accounts using InboundTransfer and ReceivedCredit objects, including the reversal of ReceivedCredits via CreditReversal objects. It also mentions test objects provided by Stripe to facilitate testing money flows and business logic.
- [Moving money out of Financial Accounts for platforms | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/moving-money/moving-money-out): This page details methods for moving funds out of a financial account, including OutboundPayment, OutboundTransfer, and card transactions via Stripe Issuing. It also covers ReceivedDebit objects, which are initiated by external account holders to pull funds from a financial account.
- [ACH NOC and SEC handling | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/moving-money/noc-sec-handling): This page explains how Stripe handles ACH Notifications of Change (NOC) and SEC codes, which provide updated external account information. When an ACH transaction returns an NOC, Stripe automatically updates the relevant PaymentMethod or BankAccount object and notifies the platform via webhook.
- [Moving money using DebitReversal objects | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/moving-money/out-of/debit-reversals): This page explains how DebitReversal objects are used to retrieve funds previously debited from a financial account to an external account. It details the scenarios and conditions under which funds from a ReceivedDebit can be returned, based on the network and source flow, including deadlines and restrictions.
- [Moving money using OutboundPayment objects | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/moving-money/out-of/outbound-payments): This page describes how to use OutboundPayment objects to create push-based transfers from a financial account to third-party external accounts or other financial accounts via ACH, wire transfer, or the Stripe network. It outlines the typical transfer times, ranging from minutes to 1-2 business days.
- [Moving money using OutboundTransfer objects | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/moving-money/out-of/outbound-transfers): This page explains how OutboundTransfer objects facilitate money movement from a financial account to an external bank account owned by a connected account using ACH or domestic wire transfers. It also notes that in the Multi FA beta, OutboundTransfer can be used for near-instantaneous transfers between financial accounts on the same platform.
- [Moving money using ReceivedDebit objects | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/moving-money/out-of/received-debits): This page explains that ReceivedDebit objects are created when money is pulled from a financial account, such as through Stripe Issuing card spending or ACH debits to external accounts. Platforms observe these object creations via webhooks, as they are not directly created by the platform.
- [Payouts and top-ups from Stripe Payments | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/moving-money/payouts): This page explains how to move money between Stripe Payments and Financial Accounts for platforms using payouts and top-ups. It details setting up financial accounts as external bank accounts and the necessary API configurations for connected and platform accounts.
- [Working with SetupIntents, PaymentMethods, and BankAccounts | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/moving-money/working-with-bankaccount-objects): This document outlines how to use PaymentMethod objects to manage US-based bank account credentials for saving and reusing funds movement. It explains attaching PaymentMethods to Customer or Stripe accounts depending on whether the transfer is outbound to a third party or inbound/outbound for the platform.
- [Financial Accounts for platforms | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect): Financial Accounts for platforms provides Stripe Connect platforms with APIs to embed financial services, enabling connected accounts to hold funds, pay bills, and manage cash flow. It is available for testing in sandbox environments for US-based commercial businesses and requires review for other businesses.
- [Financial Accounts for platforms requirements | Stripe Documentation](https://docs.stripe.com/financial-accounts/connect/requirements): This page details the compliance requirements and restrictions for using Stripe Financial Accounts for platforms, which apply to both the platform and its connected accounts. Key requirements include maintaining a fraud risk management process and offering services only to eligible businesses.
- [Forward card details to third-party API endpoints | Stripe Documentation](https://docs.stripe.com/payments/vault-and-forward): The Vault and Forward API allows tokenizing and securely storing card details in Stripe's PCI-compliant vault to route data to supported processors or endpoints. This enables using the Payment Element across multiple processors and routing card details to your own PCI-compliant token vault.
- [Stripe Verified for platforms | Stripe Documentation](https://docs.stripe.com/verified/verified-for-platforms): Stripe Verified for platforms offers specialized risk and compliance controls, along with benefits for connected accounts like fewer paused capabilities and higher ACH limits. It also provides benefits for the platform account, including personalized monitoring and enhanced protections.
- [Stripe Verified | Stripe Documentation](https://docs.stripe.com/verified): Stripe Verified helps navigate global payment processing and financial service requirements by offering personalized monitoring, enhanced protections, and expert assistance. It aims to minimize business disruptions and resolve issues, with a current private preview and a future monthly fee.
- [Stripe payments with Visa Checkout | Stripe Documentation](https://docs.stripe.com/visa-checkout): This page discusses the deprecated Visa Checkout integration, recommending migration to Secure Remote Commerce for unified online checkout. It explains how Visa Checkout previously allowed users to streamline payments by using stored information via a unique ID.
- [Handle webhook event generation failures | Stripe Documentation](https://docs.stripe.com/webhooks/handle-irrecoverable-events): This guide explains how to handle rare instances where Stripe fails to generate a webhook Event object, resulting in an irrecoverable event. Stripe sends a v2.core.health.event_generation_failure.resolved event to inform you of the failure and provide details for recovery.
- [Migrate from snapshot events to thin events | Stripe Documentation](https://docs.stripe.com/webhooks/migrate-snapshot-to-thin-events): This document guides users on migrating from snapshot events to thin events for API v1 resources, offering a lightweight and version-stable alternative. Thin events provide compact notifications, reducing the need to update webhook handlers during API version upgrades.
- [Process undelivered webhook events | Stripe Documentation](https://docs.stripe.com/webhooks/process-undelivered-events): This guide explains how to manually process undelivered webhook events to speed up delivery when your endpoint is temporarily unavailable. It details using the List Events API with parameters like `ending_before` and `delivery_success=false` to retrieve and process missed events.
- [Resolve webhook signature verification errors | Stripe Documentation](https://docs.stripe.com/webhooks/signature): This page explains how to resolve webhook signature verification errors by ensuring the correct parameters are used with the `constructEvent()` function. The most common error involves using the wrong endpoint secret, which can be found in the Stripe Dashboard or Stripe CLI.
- [Handle webhook versioning | Stripe Documentation](https://docs.stripe.com/webhooks/versioning): This guide explains how to upgrade webhook endpoints to newer API versions, especially those with breaking changes, using a safe process. It highlights that API versions prior to 2024-09-30.acacia contain breaking changes, while subsequent monthly releases are backward-compatible.
- [Manage event destinations | Stripe Documentation](https://docs.stripe.com/workbench/event-destinations): This guide details how to set up and manage event destinations using Workbench, allowing you to configure webhook endpoints and AWS EventBridge destinations. You can select API versions, event types, and view delivery statuses for your configured destinations.
- [Use cases | Stripe Documentation](https://docs.stripe.com/workbench/guides): Workbench provides tools to help developers debug, manage, and grow Stripe integrations, including viewing API versions used, recent integration errors, and API request logs. It offers filtering options by HTTP method, status, or source.
- [Health alerts and insights | Stripe Documentation](https://docs.stripe.com/workbench/health): The Health tab in Workbench provides a consolidated view of critical and non-critical alerts affecting Stripe payment processing, with a 30-day history and actionable insights. It helps proactively improve API integration health by identifying root causes of issues.
- [Workbench | Stripe Documentation](https://docs.stripe.com/workbench): Workbench offers tools to build, test, and debug Stripe integrations, including a Shell and API Explorer for interacting with APIs, managing event destinations, and gaining health insights. It replaces the Developers Dashboard and is enabled by default for new accounts.
- [How Workbench works | Stripe Documentation](https://docs.stripe.com/workbench/overview): Workbench provides developer tools to debug, manage, and grow Stripe integrations, allowing users to review errors, inspect API objects, manage event destinations, and run API requests via the Shell and API Explorer. It replaces the Developers Dashboard and is enabled by default for new accounts.
- [Shell and API Explorer | Stripe Documentation](https://docs.stripe.com/workbench/shell): Shell, a command-line interface within Workbench, offers Stripe CLI-like commands for managing and debugging integrations, including autocompletion and an API Explorer. It runs in the browser and is read-only in live mode, requiring a sandbox environment for modifications.
- [Workflows | Stripe Documentation](https://docs.stripe.com/workflows): Stripe Workflows is a no-code product within the Stripe Dashboard that automates tasks and creates custom flows for multi-step processes. It uses a visual builder with triggers and steps, conditional logic, and sequencing to build efficient and dynamic workflows.
- [Set up workflows | Stripe Documentation](https://docs.stripe.com/workflows/set-up): Workflows allow you to automate tasks in response to Stripe events. You can create workflows in the Stripe Dashboard by defining a trigger and a series of actions or conditions. A sandbox environment is available for testing workflow creation and execution.
- [Workflows use cases | Stripe Documentation](https://docs.stripe.com/workflows/use-cases): Workflows can be used to automate various business scenarios, such as personalizing customer orders. An example demonstrates how to trigger an email to a team member for a handwritten note when a purchase exceeds a certain amount. This workflow can be set up and customized within the Stripe Dashboard.
- [How Workflows work | Stripe Documentation](https://docs.stripe.com/workflows/define-workflows): Workflows are built using a visual builder in the Stripe Dashboard to automate multi-step processes. Each workflow consists of a single trigger event and a series of up to 12 steps, which can be actions or conditions. This enables streamlining processes, enforcing business rules, and reducing manual effort.
- [Localization | Stripe Documentation](https://docs.stripe.com/localization): Localization allows you to provide translated content for Stripe APIs to display information in users' preferred languages. Stripe provides translatable fields in XLIFF 2.0 format, which you download and translate for your target languages. Your application then serves these translations based on user location.
- [Bill customers in advance | Stripe Documentation](https://docs.stripe.com/billing/subscriptions/prebilling): Prebilling enables you to bill customers in advance for future service periods or upcoming renewals, rather than just the current cycle. This feature can be enabled when creating or updating a subscription and applies at the item level. Example use cases include prebilling for a set number of days or for upcoming renewal periods.
- [Acacia | Stripe Documentation](https://docs.stripe.com/changelog/acacia): The Acacia release (2024-09-30) introduces a new API versioning model with breaking changes and new features. Subsequent Acacia versions will include only additive changes. Key updates include more granular control of credit grants, scheduled debit payments, and the ability to restrict card brands for Checkout Sessions.
- [Basil | Stripe Documentation](https://docs.stripe.com/changelog/basil): The Basil release (2025-03-31) is the second in the new API versioning model, introducing breaking changes and new features, with subsequent versions being additive. Recent updates include payouts to Financial Accounts v2, support for third-party tax apps with subscriptions, and flexible billing mode becoming the default.
- [2011-06-21 release | Stripe Documentation](https://docs.stripe.com/changelog/2011-06-21): The June 21, 2011 release introduced a breaking change where errors now produce exceptions for unrecognized API parameters across all products. This change impacts how developers should handle unexpected API inputs.
- [2011-06-28 release | Stripe Documentation](https://docs.stripe.com/changelog/2011-06-28): The June 28, 2011 release included a breaking change in the Billing product, where plans no longer include the identifier field. This change affects how plan identifiers are accessed or managed.
- [2011-08-01 release | Stripe Documentation](https://docs.stripe.com/changelog/2011-08-01): The August 1, 2011 release introduced a breaking change where lists now provide a total count of items and a data field, affecting all products. This change impacts how paginated data is retrieved and processed.
- [2011-09-15 release | Stripe Documentation](https://docs.stripe.com/changelog/2011-09-15): The September 15, 2011 release introduced a breaking change in how cards are validated when creating tokens, affecting Elements and one other area. This change requires adjustments in tokenization processes.
- [2012-02-23 release | Stripe Documentation](https://docs.stripe.com/changelog/2012-02-23): The February 23, 2012 release introduced a breaking change where fields with null values are now included in API responses across all products. This ensures more complete data is returned in API calls.
- [2012-03-25 release | Stripe Documentation](https://docs.stripe.com/changelog/2012-03-25): The March 25, 2012 release included a breaking change in the Billing product, where customers no longer include a next_recurring_charge field. This change affects how recurring charge information is accessed for customer objects.
- [2012-06-18 release | Stripe Documentation](https://docs.stripe.com/changelog/2012-06-18): The June 18, 2012 release introduced a breaking change where tokens no longer include the amount and currency properties, affecting Elements and one other area. This change impacts how token data is interpreted.
- [2012-07-09 release | Stripe Documentation](https://docs.stripe.com/changelog/2012-07-09): The July 9, 2012 release included a breaking change in the Payments product, where customers no longer include the uncaptured field. This change affects how payment capture status is determined for customer objects.
- [2012-09-24 release | Stripe Documentation](https://docs.stripe.com/changelog/2012-09-24): The September 24, 2012 release included a breaking change in the Billing product, where discounts no longer include an extraneous id field. This change impacts how discount objects are structured.
- [2012-10-26 release | Stripe Documentation](https://docs.stripe.com/changelog/2012-10-26): The October 26, 2012 release introduced a breaking change in the Billing product, where invoices now include a sublist of invoice line items. This change affects how invoice details are accessed.
- [2012-11-07 release | Stripe Documentation](https://docs.stripe.com/changelog/2012-11-07): The November 7, 2012 release introduced a breaking change in the Payments product, renaming the disputed field for Charges to dispute. This change impacts how charge disputes are referenced.
- [2013-02-11 release | Stripe Documentation](https://docs.stripe.com/changelog/2013-02-11): The February 11, 2013 release introduced a breaking change where failed invoice payments now return an HTTP error in the Invoicing product. This change impacts error handling for failed payments.
- [2013-02-13 release | Stripe Documentation](https://docs.stripe.com/changelog/2013-02-13): The February 13, 2013 release introduced a breaking change where disputes on charges are now tracked through the stripe_fee field and included in the fee total within the Payments product. This change affects how dispute costs are accounted for.
- [2013-07-05 release | Stripe Documentation](https://docs.stripe.com/changelog/2013-07-05): The 2013-07-05 release introduces a 'cards' sublist and 'default_card' field to customer objects. This update enhances customer data management by providing more detailed information about their associated payment methods.
- [2013-08-12 release | Stripe Documentation](https://docs.stripe.com/changelog/2013-08-12): The 2013-08-12 release allows the 'description' and 'email' fields to be null across several objects. This change offers greater flexibility in data input for these specific fields.
- [2013-08-13 release | Stripe Documentation](https://docs.stripe.com/changelog/2013-08-13): The 2013-08-13 release moves fee details from charges and transfers to their respective balance transactions. This consolidates financial reporting and simplifies access to fee information.
- [2013-10-29 release | Stripe Documentation](https://docs.stripe.com/changelog/2013-10-29): The 2013-10-29 release updates invoicing logic so that coupons only apply to an invoice's total balance. This change prevents coupons from being applied to zero-cost invoices.
- [2013-12-03 release | Stripe Documentation](https://docs.stripe.com/changelog/2013-12-03): The 2013-12-03 release introduces an expandable 'account' field for application fees, allowing retrieval of user details. Additionally, application fee refunds are now proportional to the charged amount.
- [2014-01-31 release | Stripe Documentation](https://docs.stripe.com/changelog/2014-01-31): The 2014-01-31 release updates billing functionality by allowing customers to have multiple subscriptions. It also changes how trial end dates are handled for canceled subscriptions, no longer computing them.
- [2014-03-13 release | Stripe Documentation](https://docs.stripe.com/changelog/2014-03-13): The 2014-03-13 release renames the 'statement descriptor' field within the Connect API. This change standardizes naming conventions for descriptive elements in financial transactions.
- [2014-03-28 release | Stripe Documentation](https://docs.stripe.com/changelog/2014-03-28): The 2014-03-28 release removes the 'count' field from all lists across products. This streamlines API responses by eliminating redundant information.
- [2014-05-19 release | Stripe Documentation](https://docs.stripe.com/changelog/2014-05-19): The 2014-05-19 release replaces the 'account' field on transfers with a new field for Connect. This update enhances the way transfer-related account information is accessed and managed.
- [2014-06-13 release | Stripe Documentation](https://docs.stripe.com/changelog/2014-06-13): The 2014-06-13 release renames the 'type' field on cards to 'brand'. This change provides a more specific and intuitive name for card issuer information.
- [2014-06-17 release | Stripe Documentation](https://docs.stripe.com/changelog/2014-06-17): The 2014-06-17 release adds a 'refunds' sublist to invoices, providing direct access to refund information. This enhances the ability to track and manage invoice-related refunds.
- [2014-07-22 release | Stripe Documentation](https://docs.stripe.com/changelog/2014-07-22): The 2014-07-22 release updates invoice line items to include subscription plans and quantities. This provides more detailed information within each invoice line item.
- [2014-07-26 release | Stripe Documentation](https://docs.stripe.com/changelog/2014-07-26): The 2014-07-26 release adds a 'refunds' sublist to application fees, allowing direct access to refund data. This improves the tracking and management of refunds associated with application fees.
- [2014-08-04 release | Stripe Documentation](https://docs.stripe.com/changelog/2014-08-04): The 2014-08-04 release enables retrieval of balance histories directly, rather than relying on Transfer fields. This change provides a more direct and comprehensive way to access balance transaction data.
- [2014-08-20 release | Stripe Documentation](https://docs.stripe.com/changelog/2014-08-20): The 2014-08-20 release introduces new statuses for disputes and includes multiple balance transactions within dispute objects. These updates provide more granular information and better tracking for payment disputes.
- [2014-09-08 release | Stripe Documentation](https://docs.stripe.com/changelog/2014-09-08): The 2014-09-08 release updates bank accounts to include a 'status' enum that replaces multiple previous fields. This simplifies the representation of bank account status.
- [2014-10-07 release | Stripe Documentation](https://docs.stripe.com/changelog/2014-10-07): The 2014-10-07 release prevents the retrieval of tokens using publishable keys and omits fingerprints from API responses when creating cards or bank accounts with a publishable key. These changes enhance security by limiting the sensitive data exposed through client-side operations.
- [2014-11-05 release | Stripe Documentation](https://docs.stripe.com/changelog/2014-11-05): The 2014-11-05 release updates the terms for account activation status related to payments and transfers. This clarifies the conditions under which accounts are considered active for these operations.
- [2014-11-20 release | Stripe Documentation](https://docs.stripe.com/changelog/2014-11-20): The 2014-11-20 release updates dispute reporting to indicate disputes as won even if the charge is refunded. It also changes invoice items to reflect metadata for their associated subscription instead of the plan. These changes refine how disputes and invoice items are represented.
- [2014-12-08 release | Stripe Documentation](https://docs.stripe.com/changelog/2014-12-08): The 2014-12-08 release adds an 'evidence_details' object to disputes for improved evidence documentation. This enhances the process of managing and reviewing dispute evidence.
- [2014-12-17 release | Stripe Documentation](https://docs.stripe.com/changelog/2014-12-17): The December 17, 2014 release introduces the statement_description field for charges, invoices, plans, and transfers. Creating accounts via the API now requires version 2014-12-17 or newer.
- [2014-12-22 release | Stripe Documentation](https://docs.stripe.com/changelog/2014-12-22): The December 22, 2014 release updates how card checks are described, using both unchecked and unavailable values for address and CVC checks. It also removes the customer field from tokens with cards.
- [2015-01-11 release | Stripe Documentation](https://docs.stripe.com/changelog/2015-01-11): The January 11, 2015 release simplifies file type descriptions with the 'type' field and format. This change affects all products related to file uploads.
- [2015-01-26 release | Stripe Documentation](https://docs.stripe.com/changelog/2015-01-26): The January 26, 2015 release modifies how events with previous_attributes are rendered, showing only differences in object updates. Subscriptions now only report the timestamp for API or invoice payment failures in the canceled_at field.
- [2015-02-10 release | Stripe Documentation](https://docs.stripe.com/changelog/2015-02-10): The February 10, 2015 release introduces a 'warning_closed' status for disputes. Transfers in test mode now require a sufficient account balance to better simulate live conditions.
- [2015-02-16 release | Stripe Documentation](https://docs.stripe.com/changelog/2015-02-16): The February 16, 2015 release renames the transfer.canceled event type to transfer.reversed.
- [2015-02-18 release | Stripe Documentation](https://docs.stripe.com/changelog/2015-02-18): The February 18, 2015 release adds a 'succeeded' status for charges and introduces a 'source' field for charges and customers that accepts a source or card. Related event types are also updated.
- [2015-03-24 release | Stripe Documentation](https://docs.stripe.com/changelog/2015-03-24): The March 24, 2015 release updates how ending periods are calculated for prorated invoice line items and changes the sorting order of lines for invoices.
- [2015-04-07 release | Stripe Documentation](https://docs.stripe.com/changelog/2015-04-07): The April 7, 2015 release updates the calculation of ending periods for prorated invoice line items and modifies the sorting order of lines on invoices.
- [2015-06-15 release | Stripe Documentation](https://docs.stripe.com/changelog/2015-06-15): The June 15, 2015 release introduces a new error for accounts on manual payout schedules when they attempt to perform certain actions. This change primarily affects Connect features.
- [2015-07-07 release | Stripe Documentation](https://docs.stripe.com/changelog/2015-07-07): The July 7, 2015 release adds an 'in_transit' status for transfers that have been submitted to the bank but have not yet arrived. This provides more detailed tracking for Connect features.
- [2015-07-13 release | Stripe Documentation](https://docs.stripe.com/changelog/2015-07-13): The July 13, 2015 release adds the verification[disabled_reason] field to accounts, indicating why an account cannot make transfers or charges. This impacts Connect functionality.
- [2015-07-28 release | Stripe Documentation](https://docs.stripe.com/changelog/2015-07-28): The July 28, 2015 release triggers the balance.available event for transfers that are immediately processed. This change provides real-time updates for Connect users.
- [2015-08-07 release | Stripe Documentation](https://docs.stripe.com/changelog/2015-08-07): The August 7, 2015 release ensures that the tos_acceptance[date] field on accounts is always a valid timestamp. This improves data integrity for Connect accounts.
- [2015-08-19 release | Stripe Documentation](https://docs.stripe.com/changelog/2015-08-19): The August 19, 2015 release updates balance transactions, specifying the corresponding ID in the source field for refunds or disputes. This enhances transaction tracking for payments.
- [2015-09-03 release | Stripe Documentation](https://docs.stripe.com/changelog/2015-09-03): The September 3, 2015 release introduces an error for requests that reuse idempotency tokens but alter request parameters. This change affects all products by enforcing stricter request validation.
- [2015-09-08 release | Stripe Documentation](https://docs.stripe.com/changelog/2015-09-08): The September 8, 2015 release changes rate-limited requests to return an HTTP 429 error, removing the rate_limit field. This simplifies error handling for API interactions.
- [2015-09-23 release | Stripe Documentation](https://docs.stripe.com/changelog/2015-09-23): The September 23, 2015 release makes several changes to invoices and charges. The charge field now always reflects the latest charge on invoices, and invoices no longer include the payment property. Listing all charges now includes payments from all funding sources, and charges only support an offset for list pagination when filtering by source.
- [2015-10-01 release | Stripe Documentation](https://docs.stripe.com/changelog/2015-10-01): The October 1, 2015 release renames bank account information to external accounts on user profiles. Accounts now include an external_accounts field, impacting Connect features.
- [2015-10-12 release | Stripe Documentation](https://docs.stripe.com/changelog/2015-10-12): The October 12, 2015 release updates error handling for creating cards or bank accounts using invalid parameters. Such requests now throw an HTTP 400 error, improving API robustness for Payments and Connect.
- [2015-10-16 release | Stripe Documentation](https://docs.stripe.com/changelog/2015-10-16): This release notes page from October 16, 2015, indicates a breaking change in Stripe's API. Creating or updating customers now requires a plan to be specified if a tax percentage is also provided.
- [2016-02-03 release | Stripe Documentation](https://docs.stripe.com/changelog/2016-02-03): The Stripe release notes for February 3, 2016, detail a change in the Connect API. Accounts now only display country-specific subfields for the legal_entity field.
- [2016-02-19 release | Stripe Documentation](https://docs.stripe.com/changelog/2016-02-19): This Stripe release from February 19, 2016, announces a change in the Bank Accounts API. The name field for Bank Accounts is renamed to account_holder_name.
- [2016-02-22 release | Stripe Documentation](https://docs.stripe.com/changelog/2016-02-22): The Stripe release notes for February 22, 2016, introduce a limit on invoice items. You can no longer add more than 250 invoice items to a single invoice.
- [2016-02-23 release | Stripe Documentation](https://docs.stripe.com/changelog/2016-02-23): According to the Stripe release notes from February 23, 2016, orders that are paid or fulfilled and then become canceled or returned will now automatically refund associated charges.
- [2016-02-29 release | Stripe Documentation](https://docs.stripe.com/changelog/2016-02-29): This Stripe release from February 29, 2016, impacts the Connect API. When creating or updating an account, the postal code for its legal entity is now validated.
- [2016-03-07 release | Stripe Documentation](https://docs.stripe.com/changelog/2016-03-07): The Stripe release notes for March 7, 2016, state that supported currencies are now defined on the country spec for an account's country.
- [2016-06-15 release | Stripe Documentation](https://docs.stripe.com/changelog/2016-06-15): This Stripe release from June 15, 2016, changes how products and SKUs are managed. Deactivating a product no longer automatically deactivates its associated SKUs.
- [2016-07-06 release | Stripe Documentation](https://docs.stripe.com/changelog/2016-07-06): The Stripe release notes for July 6, 2016, introduce a new filtering capability for subscriptions. You can now filter lists of subscriptions to view only canceled subscriptions.
- [2016-10-19 release | Stripe Documentation](https://docs.stripe.com/changelog/2016-10-19): This Stripe release from October 19, 2016, addresses API request handling. Using insufficient permissions to make API requests now results in an HTTP 403 error across all products.
- [2017-01-27 release | Stripe Documentation](https://docs.stripe.com/changelog/2017-01-27): The Stripe release notes for January 27, 2017, indicate a change in the Payments API. Balance transactions no longer include the sourced_transfers field.
- [2017-02-14 release | Stripe Documentation](https://docs.stripe.com/changelog/2017-02-14): This Stripe release from February 14, 2017, enhances transaction data. Charges now specify the ID for the rule blocking a transaction and the ID for any associated dispute, both of which can be expanded.
- [2017-04-06 release | Stripe Documentation](https://docs.stripe.com/changelog/2017-04-06): The Stripe release notes for April 6, 2017, update the Connect API. Transfers are now split into distinct 'payouts' and 'transfers' categories.
- [2017-05-25 release | Stripe Documentation](https://docs.stripe.com/changelog/2017-05-25): This Stripe release from May 25, 2017, introduces several updates. Events for Connect now specify the originating connected account, the Events object's request field includes both request ID and idempotency key, and events with previous_attributes render the complete affected sub-array. Additionally, accounts must now specify one of three types: Standard, Express, or Custom.
- [2017-06-05 release | Stripe Documentation](https://docs.stripe.com/changelog/2017-06-05): The Stripe release notes for June 5, 2017, add a new field for account status. Accounts can now specify the reason why an account is not enabled using the new 'reason' field under_review.
- [2017-08-15 release | Stripe Documentation](https://docs.stripe.com/changelog/2017-08-15): This Stripe release from August 15, 2017, updates the Payments API. Sources can now specify that an authentication redirect is not required.
- [2017-12-14 release | Stripe Documentation](https://docs.stripe.com/changelog/2017-12-14): The Stripe release notes for December 14, 2017, bring changes to invoicing. Invoice line items must now always include a description, and invoice payment failures return a card_error when a charge is declined.
- [2018-01-23 release | Stripe Documentation](https://docs.stripe.com/changelog/2018-01-23): This Stripe release from January 23, 2018, enhances the Connect API. Connect platforms can now identify reused card or bank accounts across connected accounts, as they will share the same fingerprint.
- [2018-02-05 release | Stripe Documentation](https://docs.stripe.com/changelog/2018-02-05): The Stripe release notes for February 5, 2018, introduce significant changes to billing and plans. Free plans with prorations now generate zero-dollar invoices, subscriptions can delay their first full invoice, and plans now link to individual products with several fields moving to the product resource. Products also now require a type field.
- [2018-02-06 release | Stripe Documentation](https://docs.stripe.com/changelog/2018-02-06): This Stripe release from February 6, 2018, updates the Payments API. Sources now provide a recommended value when the issuer advises using 3D Secure for authentication.
- [2018-02-28 release | Stripe Documentation](https://docs.stripe.com/changelog/2018-02-28): The 2018-02-28 Stripe release includes a breaking change where updating a canceled subscription on a future date no longer resets its status.
- [2018-05-21 release | Stripe Documentation](https://docs.stripe.com/changelog/2018-05-21): The 2018-05-21 Stripe release introduces several breaking changes. Products no longer embed lists of SKUs, and invoice line items now have unique IDs. Additionally, coupons, SKUs, customers, products, and plans have stricter ID character validation.
- [2018-07-27 release | Stripe Documentation](https://docs.stripe.com/changelog/2018-07-27): The 2018-07-27 Stripe release brings changes to subscriptions, coupons, and customer data handling. Subscriptions no longer support direct modification of the source parameter, and trial periods are handled differently. Coupons use floats for percent_off, and email addresses are validated for customers.
- [2018-08-23 release | Stripe Documentation](https://docs.stripe.com/changelog/2018-08-23): The 2018-08-23 Stripe release impacts subscriptions, customer tax information, and plan tier pricing. The ending period of a subscription cannot be configured during cancellation. Customers now provide a tax_info object for tax IDs, and the amount field for plan tiers is renamed to unit_amount.
- [2018-09-06 release | Stripe Documentation](https://docs.stripe.com/changelog/2018-09-06): The 2018-09-06 Stripe release updates SKU handling for Checkout. SKU values no longer need to be unique, simplifying product management within Checkout.
- [2018-09-24 release | Stripe Documentation](https://docs.stripe.com/changelog/2018-09-24): The 2018-09-24 Stripe release renames the FileUpload object to Files and requires secret keys for downloading. This change affects how files are managed and accessed.
- [2018-10-31 release | Stripe Documentation](https://docs.stripe.com/changelog/2018-10-31): The 2018-10-31 Stripe release introduces character limits for descriptions of customers, products, and invoice line items. The billing_reason for the first subscription invoice is now subscription_create.
- [2018-11-08 release | Stripe Documentation](https://docs.stripe.com/changelog/2018-11-08): The 2018-11-08 Stripe release brings significant changes to invoicing and the Payment Intents API. Invoices now use an auto_advance field for automatic collection behavior and a new uncollectible status replaces the forgiven field. The Payment Intents API sees several updates for its private beta users.
- [2019-02-11 release | Stripe Documentation](https://docs.stripe.com/changelog/2019-02-11): The 2019-02-11 Stripe release focuses on renaming fields within the Payment Intents and Sources APIs. This includes changes to statuses, saving payment methods, and redirect URLs for payment authorization.
- [2019-02-19 release | Stripe Documentation](https://docs.stripe.com/changelog/2019-02-19): The 2019-02-19 Stripe release updates behaviors for card payments and refactors account-related fields. Statement descriptor behaviors for charges are changed, and account fields related to business details, verification, and capabilities are reorganized.
- [2019-03-14 release | Stripe Documentation](https://docs.stripe.com/changelog/2019-03-14): The 2019-03-14 Stripe release introduces changes to invoice and subscription management. Invoice line item application fees are renamed, and subscriptions can now be created even if the initial payment fails. Timestamps for invoice state transitions are provided, and the invoice date field is renamed to created.
- [2019-05-16 release | Stripe Documentation](https://docs.stripe.com/changelog/2019-05-16): The 2019-05-16 Stripe release includes a breaking change for bank pull payments. These payments no longer expose internal system refunds upon failure.
- [2019-08-14 release | Stripe Documentation](https://docs.stripe.com/changelog/2019-08-14): The 2019-08-14 Stripe release modifies account capabilities and person configurations. The platform_payments capability is renamed to card_payments, requiring explicit specification of the added transfers capability. Configuring a person as an account opener no longer automatically designates them as an executive.
- [2019-09-09 release | Stripe Documentation](https://docs.stripe.com/changelog/2019-09-09): The 2019-09-09 Stripe release updates account creation requirements and person document verification. Accounts in many countries now necessitate specifying capabilities during creation. New details_code values are added for person document verification.
- [2019-10-08 release | Stripe Documentation](https://docs.stripe.com/changelog/2019-10-08): The 2019-10-08 Stripe release renames an attribute within the Person object related to relationships. This change affects how person object relationships are referenced in the API.
- [2019-10-17 release | Stripe Documentation](https://docs.stripe.com/changelog/2019-10-17): The 2019-10-17 Stripe release brings several updates to subscription and invoice properties. Subscription schedule renewal properties are renamed and updated, and the subscription start field is replaced with start_date. The billing field is renamed to collection_method across invoices, subscriptions, and subscription schedules.
- [2019-11-05 release | Stripe Documentation](https://docs.stripe.com/changelog/2019-11-05): The 2019-11-05 Stripe release introduces new requirements for custom account creation and updates subscription settings. Custom account creation now requires specifying requested_capabilities. Nested subscription schedule settings are now organized under default_settings.
- [2019-12-03 release | Stripe Documentation](https://docs.stripe.com/changelog/2019-12-03): The 2019-12-03 Stripe release standardizes invoice line item IDs and introduces new requirements for credit notes. Customer balances are now returned when invoices are voided, and deprecated tax information fields are removed from the Customer object.
- [2020-03-02 release | Stripe Documentation](https://docs.stripe.com/changelog/2020-03-02): The 2020-03-02 Stripe release enables sequential numbering for invoices across an account. This change provides a more organized and consistent invoicing system.
- [2020-08-27 release | Stripe Documentation](https://docs.stripe.com/changelog/2020-08-27): The 2020-08-27 Stripe release includes several breaking changes across Payments, Billing, and Checkout. The tax_percent attribute is removed from Checkout, and subscription schedule phases attributes are renamed. Auto-expansion of certain objects like customer sources and plan tiers is also deprecated.
- [2022-08-01 release | Stripe Documentation](https://docs.stripe.com/changelog/2022-08-01): The 2022-08-01 Stripe release notes detail several breaking changes across various products. Key updates include modifications to invoice creation, Checkout Session parameters, and the removal of the default_currency attribute from the Customer object.
- [2022-11-15 release | Stripe Documentation](https://docs.stripe.com/changelog/2022-11-15): The 2022-11-15 Stripe release introduces changes to how refunds are handled for Charges and updates the PaymentIntent and SetupIntent APIs with new decline codes. It also adds new error codes for the Accounts API in Connect.
- [2023-08-16 release | Stripe Documentation](https://docs.stripe.com/changelog/2023-08-16): The 2023-08-16 Stripe release enables automatic payment methods by default for PaymentIntents and SetupIntents. It also introduces platform-scope rendering for PaymentMethod fingerprints in Connect and adds specific error codes for failed Klarna payments.
- [2023-10-16 release | Stripe Documentation](https://docs.stripe.com/changelog/2023-10-16): The 2023-10-16 Stripe release adds new account requirement error codes to the Accounts API for Connect. It also auto-populates the statement descriptor and prefix within the Accounts API.
- [2024-04-10 release | Stripe Documentation](https://docs.stripe.com/changelog/2024-04-10): The 2024-04-10 Stripe release makes automatic sync the default capture method for PaymentIntents when not specified. It also renames the rendering_options attribute for invoices to rendering and the features attribute of the Product object.
- [2024-06-20 release | Stripe Documentation](https://docs.stripe.com/changelog/2024-06-20): The 2024-06-20 Stripe release includes several renames and deprecations for Issuing objects and Connect capabilities. It renames attributes like fuel and purchase_details for Issuing objects and deprecates the bank_transfer_payments capability type in favor of newer ones in Connect.
- [Customize your data exports | Stripe Documentation](https://docs.stripe.com/stripe-data/export-customizations): This page explains how to customize data exports using Stripe's Data Pipeline. Users can pause table syncing, set custom delivery schedules, pause the entire pipeline, and automatically deliver standard dashboard reports to data warehouses.
- [Stripe API Reference](https://docs.stripe.com/api): This page provides an overview of the Stripe API, detailing its RESTful structure, authentication methods, and core resources. It highlights that the API supports test mode and does not allow bulk updates, with different accounts potentially having tailored functionality.
- [Authentication | Stripe API Reference](https://docs.stripe.com/api/authentication): This page details how to authenticate Stripe API requests using API keys, differentiating between test and live mode keys. It emphasizes the importance of keeping secret keys secure and making all API requests over HTTPS.
- [Errors | Stripe API Reference](https://docs.stripe.com/api/errors): This page outlines Stripe's error handling conventions, using HTTP response codes to indicate success (2xx) or failure (4xx, 5xx). It details attributes like code, decline_code, and message that provide specific error information, especially for card errors.
- [Handling errors | Stripe API Reference](https://docs.stripe.com/api/errors/handling): This page explains how Stripe's client libraries raise exceptions for various API errors and recommends implementing graceful handling. It also introduces the concept of expanding responses using the 'expand' parameter to retrieve additional related object information.
- [Expanding Responses | Stripe API Reference](https://docs.stripe.com/api/expanding_objects): This page describes how to use the 'expand' request parameter to retrieve additional information within API responses. It allows for expanding related object IDs or specific fields not included by default, and supports recursive expansion.
- [Idempotent requests | Stripe API Reference](https://docs.stripe.com/api/idempotent_requests): This page explains how to use idempotency keys for safely retrying API requests without duplication. By providing a unique key, Stripe recognizes subsequent retries and returns the same result, preventing accidental duplicate operations.
- [Include-dependent response values (API v2) | Stripe API Reference](https://docs.stripe.com/api/include_dependent_response_values): This page details how to use the 'include' parameter in API v2 requests to retrieve null values for certain response properties. By specifying properties in the 'include' array, users can retrieve their actual values, reducing payload size by default.
- [Metadata | Stripe API Reference](https://docs.stripe.com/api/metadata): This page explains the metadata parameter available on updateable Stripe objects, allowing users to attach key-value string data. It outlines the limits for keys and values and notes that Stripe does not use metadata for processing or display to users.
- [Pagination | Stripe API Reference](https://docs.stripe.com/api/pagination): This page describes Stripe's cursor-based pagination for list API methods using 'starting_after' and 'ending_before' parameters. It also mentions the 'limit' parameter and introduces auto-pagination helpers in client libraries for traversing all pages.
- [Search | Stripe API Reference](https://docs.stripe.com/api/pagination/search): This page details Stripe's search API methods, which utilize cursor-based pagination via the 'page' and 'next_page' parameters. It explains the search request format, including the required 'query' and optional 'limit', and the structure of search responses.
- [Auto-pagination | Stripe API Reference](https://docs.stripe.com/api/pagination/auto): This page highlights Stripe's auto-pagination feature, available in client libraries, which simplifies iterating through large lists of resources. It allows developers to traverse all pages of results without manual request management.
- [Request IDs | Stripe API Reference](https://docs.stripe.com/api/request_ids): This page explains that each Stripe API request has a unique Request ID found in the response headers or Dashboard logs. Providing this ID expedites issue resolution when contacting Stripe support.
- [Connected Accounts | Stripe API Reference](https://docs.stripe.com/api/connected-accounts): This page describes how to issue requests on behalf of connected accounts using Stripe Connect by including the 'Stripe-Account' header with the connected account ID. It also touches upon API versioning and upgrading.
- [Versioning | Stripe API Reference](https://docs.stripe.com/api/versioning): Stripe API versioning allows for major releases with backward-incompatible changes and monthly releases with backward-compatible changes. The current API version is 2026-02-25. The API version can be updated in Workbench, and versioning is recommended for testing before committing to an upgrade.
- [Accounts | Stripe API Reference](https://docs.stripe.com/api/v2/core/accounts): The Account v2 object represents an entity interacting with Stripe, storing identifying information and behavior-controlling properties. It can have configurations enabling features like acting as a merchant or customer. The Accounts v2 API is generally available for Connect and supports Global Payouts.
- [The Account object | Stripe API Reference](https://docs.stripe.com/api/v2/core/accounts/object): The Account object v2 stores identity information and configurations that enable product-specific capabilities for companies, individuals, or other entities. These configurations can be assigned at creation or added later, allowing the Account to function as a customer, merchant, or recipient.
- [Create an Account | Stripe API Reference](https://docs.stripe.com/api/v2/core/accounts/create): Creating an Account involves representing an entity with identifying information and feature configurations. An Account can be configured as a customer, merchant, and/or recipient, with parameters for contact details, dashboard access, and display name.
- [Update an Account | Stripe API Reference](https://docs.stripe.com/api/v2/core/accounts/update): This API updates the details of an existing Account, allowing modification of its configurations, contact information, and dashboard access. Parameters include the Account ID, account token, configuration details, and optional fields to include in the response.
- [Retrieve an Account | Stripe API Reference](https://docs.stripe.com/api/v2/core/accounts/retrieve): This API retrieves the details of a specific Account, including its ID, object type, applied configurations, and closure status. Optional parameters allow for including additional fields like defaults, future requirements, identity, and specific configurations.
- [List Accounts | Stripe API Reference](https://docs.stripe.com/api/v2/core/accounts/list): This API returns a list of Accounts, with options to filter by applied configurations, closure status, and to limit the number of results. Pagination is supported to navigate through multiple pages of accounts.
- [Close an Account | Stripe API Reference](https://docs.stripe.com/api/v2/core/accounts/close): Closing an Account removes access to it and its associated resources, making it inoperable. While limited information can still be retrieved for historical tracking, all applied configurations must be passed to successfully close the account.
- [Account event types | Stripe API Reference](https://docs.stripe.com/api/v2/core/accounts/event-types): This page lists all public thin events for Account updates, noting that the payload is unversioned. During processing, it's necessary to fetch the versioned event from the API or retrieve the resource's current state.
- [Account Links | Stripe API Reference](https://docs.stripe.com/api/v2/core/account-links): Account Links create a temporary, single-use URL for a Stripe-hosted flow to collect or update required information from an account. The Account Link object includes details like the account ID, creation and expiration timestamps, and the unique URL.
- [The Account Link object | Stripe API Reference](https://docs.stripe.com/api/v2/core/account-links/object): The Account Link object v2 represents a temporary, single-use URL for Stripe-hosted flows to collect or update account information. It includes the account ID, creation and expiration timestamps, live mode status, and the URL for accessing the flow, along with use case details.
- [Create an Account Link | Stripe API Reference](https://docs.stripe.com/api/v2/core/account-links/create): This API creates an AccountLink object, providing a single-use URL for accounts to access Stripe-hosted flows for information collection or updates. Parameters include the account ID and the use case for the link, such as account onboarding.
- [Account Tokens | Stripe API Reference](https://docs.stripe.com/api/v2/core/account-tokens): Account tokens are single-use tokens that represent company, individual, or business information and are used for creating or updating Accounts. The Account Token object includes an ID, creation and expiration timestamps, live mode status, and a used status.
- [The Account Token object | Stripe API Reference](https://docs.stripe.com/api/v2/core/account-tokens/object): The Account Token object v2 is a single-use token used to tokenize entity information for creating or updating Stripe Accounts. It contains a unique ID, creation and expiration timestamps, live mode status, and a flag indicating if the token has been used.
- [Create an Account Token | Stripe API Reference](https://docs.stripe.com/api/v2/core/account-tokens/create): This API creates an Account Token, which is a single-use token used to tokenize entity information for creating or updating a Stripe Account. Parameters include contact email, phone, display name, and identity information.
- [Retrieve an Account Token | Stripe API Reference](https://docs.stripe.com/api/v2/core/account-tokens/retrieve): This API retrieves an Account Token using its ID. The response includes the token's ID, creation and expiration timestamps, live mode status, and whether the token has been used.
- [Balance | Stripe API Reference](https://docs.stripe.com/api/balance): The Balance object represents the Stripe balance, detailing available and pending funds. It provides a breakdown of funds by currency and source type, including connect-reserved and instant-available amounts.
- [The Balance object | Stripe API Reference](https://docs.stripe.com/api/balance/balance_object): The Balance object details available and pending funds in a Stripe account, broken down by currency and source type. It also includes connect-reserved and instant-available funds, along with live mode status.
- [Retrieve balance | Stripe API Reference](https://docs.stripe.com/api/balance/balance_retrieve): This API retrieves the current account balance, returning a balance object that details available and pending funds. The balance is based on the authentication used for the request.
- [Balance Transactions | Stripe API Reference](https://docs.stripe.com/api/balance_transactions): Balance transactions represent all fund movements within a Stripe account, created for every transaction that enters or leaves the balance. Key attributes include the transaction ID, gross amount, currency, fees, net impact, source, status, and type.
- [The Balance Transaction object | Stripe API Reference](https://docs.stripe.com/api/balance_transactions/object): The Balance Transaction object details financial events impacting a Stripe account balance. It includes attributes like ID, amount, currency, fees, net impact, status, and type, providing a comprehensive record of monetary movements.
- [Retrieve a balance transaction | Stripe API Reference](https://docs.stripe.com/api/balance_transactions/retrieve): This API retrieves a specific balance transaction using its unique ID. It's a direct lookup to get detailed information about a particular financial event within the Stripe account.
- [List all balance transactions | Stripe API Reference](https://docs.stripe.com/api/balance_transactions/list): This API returns a list of transactions that have affected the Stripe account balance, such as charges and transfers, sorted by recency. It allows filtering by payout or transaction type for more specific results.
- [Charges | Stripe API Reference](https://docs.stripe.com/api/charges): The Charge object represents an attempt to move money into a Stripe account, often created through PaymentIntent confirmation. It includes details like the amount, currency, customer, and billing information, and can be captured, updated, or searched.
- [The Charge object | Stripe API Reference](https://docs.stripe.com/api/charges/object): The Charge object represents a single attempt to collect funds into a Stripe account. Key attributes include its unique ID, amount, currency, and associated customer or payment details, along with its dispute status.
- [Create a charge | Stripe API Reference](https://docs.stripe.com/api/charges/create): This endpoint is used to create a charge, although it is now deprecated in favor of the Payment Intents API. It requires the amount and currency, and can optionally include customer and description details.
- [Update a charge | Stripe API Reference](https://docs.stripe.com/api/charges/update): This API allows updating an existing charge by modifying its parameters, such as the associated customer, description, or receipt email. Any parameters not provided remain unchanged.
- [Retrieve a charge | Stripe API Reference](https://docs.stripe.com/api/charges/retrieve): This API retrieves the details of a previously created charge using its unique ID. It returns all information associated with the charge, including its status, amount, and payment method details.
- [List all charges | Stripe API Reference](https://docs.stripe.com/api/charges/list): This API returns a list of previously created charges, sorted by creation date with the most recent first. It supports filtering by customer ID, payment intent, and other parameters.
- [Capture a charge | Stripe API Reference](https://docs.stripe.com/api/charges/capture): This API captures the payment of an existing, uncaptured charge. It is used when a charge was created with the capture option set to false and must be used before the uncaptured payment expires.
- [Search charges | Stripe API Reference](https://docs.stripe.com/api/charges/search): This API allows searching for previously created charges using Stripe’s Search Query Language. It enables filtering charges based on various criteria like amount and metadata.
- [Customers | Stripe API Reference](https://docs.stripe.com/api/customers): The Customer object represents a customer of a business, used for managing recurring charges, saving payment information, and tracking payments. It includes attributes such as ID, email, address, and payment details.
- [The Customer object | Stripe API Reference](https://docs.stripe.com/api/customers/object): The Customer object stores information about a business's customer, including their ID, contact details like email and phone, address, and payment information. It facilitates recurring payments and tracks customer transactions.
- [Create a customer | Stripe API Reference](https://docs.stripe.com/api/customers/create): This API creates a new customer object, storing their details such as name, email, address, and phone number. It can also associate a payment method and shipping information during creation.
- [Update a customer | Stripe API Reference](https://docs.stripe.com/api/customers/update): This API updates an existing customer's information, allowing modifications to their address, email, description, and other details. Changes to the default source can trigger retries for past-due subscriptions.
- [Retrieve a customer | Stripe API Reference](https://docs.stripe.com/api/customers/retrieve): This API retrieves a Customer object using its unique identifier. It returns the customer's details, and if the customer has been deleted, it includes a 'deleted' property set to true.
- [List all customers | Stripe API Reference](https://docs.stripe.com/api/customers/list): This API returns a list of customers, sorted by creation date with the most recent first. It supports filtering by email address for targeted retrieval of customer data.
- [Delete a customer | Stripe API Reference](https://docs.stripe.com/api/customers/delete): This API permanently deletes a customer and cancels any active subscriptions associated with them. Deleted customers can still be retrieved for historical tracking, but further operations are prevented.
- [Search customers | Stripe API Reference](https://docs.stripe.com/api/customers/search): This API allows searching for previously created customers using Stripe’s Search Query Language. It enables filtering customers based on various criteria like name and metadata.
- [Customer Session | Stripe API Reference](https://docs.stripe.com/api/customer_sessions): This API creates a Customer Session, generating a client secret for secure client-side access to a Customer object. This is used to integrate Stripe's frontend SDKs with customer data for payment elements or other features.
- [The Customer Session object | Stripe API Reference](https://docs.stripe.com/api/customer_sessions/object): The Customer Session object provides a single-use client secret for secure client-side access to customer resources. It includes attributes like client_secret, customer ID, and expiration time, along with component configurations for features like buy buttons or pricing tables.
- [Create a Customer Session | Stripe API Reference](https://docs.stripe.com/api/customer_sessions/create): This page details how to create a Customer Session object using the Stripe API. It requires specifying the customer ID and configuring enabled components, returning a Customer Session object with a client secret for frontend use.
- [Disputes | Stripe API Reference](https://docs.stripe.com/api/disputes): Disputes arise when a customer questions a charge with their card issuer, providing an opportunity to respond with evidence. The API allows for retrieving, listing, updating, and closing disputes, with various statuses indicating the dispute's progress.
- [The Dispute object | Stripe API Reference](https://docs.stripe.com/api/disputes/object): The Dispute object in Stripe represents a customer's challenge to a charge, including its ID, amount, currency, and associated charge or payment intent. It details the reason for the dispute and its current status, such as 'needs_response' or 'lost'.
- [Update a dispute | Stripe API Reference](https://docs.stripe.com/api/disputes/update): This API endpoint allows for updating a dispute by submitting evidence to help resolve it in your favor. You can provide various evidence fields depending on the dispute type and optionally submit the evidence immediately or stage it for later.
- [Retrieve a dispute | Stripe API Reference](https://docs.stripe.com/api/disputes/retrieve): The Retrieve a dispute API endpoint fetches the details of a specific dispute using its ID. If a valid dispute ID is provided, it returns the dispute object; otherwise, it raises an error.
- [List all disputes | Stripe API Reference](https://docs.stripe.com/api/disputes/list): This API endpoint allows you to retrieve a list of your disputes, with options to filter by charge ID or PaymentIntent ID. It returns an array of dispute objects, each containing details about the dispute.
- [Close a dispute | Stripe API Reference](https://docs.stripe.com/api/disputes/close): Closing a dispute via the API signifies that you have no evidence to submit and are acknowledging the dispute as lost. This action irreversibly changes the dispute's status to 'lost' and cannot be undone.
- [Events | Stripe API Reference](https://docs.stripe.com/api/events): Stripe Events track and notify about changes to API resources, containing relevant information about the action and the affected resource. Events can be retrieved individually or as a list, and can be configured to be sent to specific destinations.
- [The Event object | Stripe API Reference](https://docs.stripe.com/api/events/object): The Event object stores details about changes to Stripe resources, including a unique ID, API version, creation timestamp, and the type of event. The 'data' attribute contains the affected API resource, and 'request' provides information about the triggering API call.
- [Retrieve an event | Stripe API Reference](https://docs.stripe.com/api/events/retrieve): This API retrieves the details of an event created within the last 30 days using its unique identifier, often received via webhook. The returned event object includes the affected resource's data, which mirrors direct API retrieval.
- [List all events | Stripe API Reference](https://docs.stripe.com/api/events/list): This API allows listing events from the past 30 days, with options to filter by event type, creation date, and delivery success. It returns an array of event objects, each containing details about the specific event.
- [Types of events | Stripe API Reference](https://docs.stripe.com/api/events/types): This page lists all public snapshot event types used by Stripe resources, following a 'resource.event' naming convention. Events are generated for resource state changes, and some types are only created when webhooks are configured to listen for them.
- [Events | Stripe API Reference](https://docs.stripe.com/api/v2/core/events): Events in the /v2 namespace are generated to inform businesses of account activity, providing thin events with small, unversioned payloads that reference the changed object's ID. The Events v2 API returns these events, requiring retrieval of the event object for additional data.
- [The Event object | Stripe API Reference](https://docs.stripe.com/api/v2/core/events/object): The Event object v2 represents changes in Stripe, including a unique ID, creation timestamp, and type. It contains 'changes' detailing before and after states, 'context', and 'data' about the event, with 'related_object' referencing the associated API resource.
- [Retrieve an Event | Stripe API Reference](https://docs.stripe.com/api/v2/core/events/retrieve): This API retrieves the details of an event using its unique identifier. The response includes the event's ID, type, creation timestamp, and related object information, along with potential changes and context.
- [List Events | Stripe API Reference](https://docs.stripe.com/api/v2/core/events/list): This API lists events, going back up to 30 days, with parameters to filter by object ID, creation date range, and event types. It returns a paginated list of event objects, including URLs for navigating to the next or previous pages.
- [Ping an Event Destination | Stripe API Reference](https://docs.stripe.com/api/v2/core/events/ping): This API sends a ping event to a specified event destination to test connectivity. It requires the event destination's identifier and returns an event object representing the ping action.
- [Types of events | Stripe API Reference](https://docs.stripe.com/api/v2/core/events/event-types): This page lists all public thin event types used by Stripe for /v1 and /v2 resources, noting that their payloads are unversioned. When processing these events, you must fetch the versioned event or the resource's current state from the API.
- [Event Destinations | Stripe API Reference](https://docs.stripe.com/api/v2/core/event-destinations): Event Destinations allow setting up webhook endpoints or Amazon EventBridge to receive Stripe events, supporting both thin and snapshot event types. You can create, update, retrieve, list, delete, enable, or disable these destinations.
- [The Event Destination object | Stripe API Reference](https://docs.stripe.com/api/v2/core/event-destinations/object): The Event Destination object in Stripe's API v2 allows for configuring where events are sent. It includes attributes like ID, creation timestamp, description, enabled events, payload type, status, and type (Amazon EventBridge or webhook endpoint).
- [Create an Event Destination | Stripe API Reference](https://docs.stripe.com/api/v2/core/event-destinations/create): This Stripe API v2 endpoint allows you to create a new event destination. You must provide the enabled events, event payload type, name, and destination type (Amazon EventBridge or webhook). Optional parameters include description and where events should be routed from.
- [Update an Event Destination | Stripe API Reference](https://docs.stripe.com/api/v2/core/event-destinations/update): The Update an Event Destination API v2 endpoint allows modification of an existing event destination's details. You can update the description, enabled events, name, and webhook endpoint configuration using the event destination's ID. Optional fields can be included in the response.
- [Retrieve an Event Destination | Stripe API Reference](https://docs.stripe.com/api/v2/core/event-destinations/retrieve): This Stripe API v2 endpoint retrieves the details of a specific event destination using its unique identifier. You can optionally include related fields such as the webhook endpoint URL in the response. The returned object contains all configuration details for the event destination.
- [List Event Destinations | Stripe API Reference](https://docs.stripe.com/api/v2/core/event-destinations/list): The List Event Destinations API v2 endpoint returns a list of all accessible event destinations for your account. You can optionally include webhook endpoint URLs and control the number of results per page. The response includes a data array of event destination objects and pagination URLs.
- [Delete an Event Destination | Stripe API Reference](https://docs.stripe.com/api/v2/core/event-destinations/delete): The Delete an Event Destination API v2 endpoint permanently removes an event destination. You must provide the unique identifier of the event destination to be deleted. The response confirms the deletion with the ID and object type of the removed resource.
- [Disable an Event Destination | Stripe API Reference](https://docs.stripe.com/api/v2/core/event-destinations/disable): This Stripe API v2 endpoint disables an event destination, preventing it from receiving events. You need to provide the identifier of the event destination to be disabled. The response returns the updated event destination object, including its status.
- [Enable an Event Destination | Stripe API Reference](https://docs.stripe.com/api/v2/core/event-destinations/enable): The Enable an Event Destination API v2 endpoint reactivates a disabled event destination. You must provide the unique identifier of the event destination you wish to enable. The response returns the updated event destination object, reflecting its enabled status.
- [Event Destination event types | Stripe API Reference](https://docs.stripe.com/api/v2/core/event-destinations/event-types): This page lists all public 'thin' events currently supported for updates to Stripe Event Destinations. These events are unversioned, meaning you need to fetch the versioned event or resource state separately during processing. The list is subject to ongoing evolution and expansion.
- [Files | Stripe API Reference](https://docs.stripe.com/api/files): The File object in Stripe represents files hosted on their servers, which can be uploaded by users (e.g., dispute evidence) or created by Stripe (e.g., Sigma query results). Key attributes include ID, purpose, type, creation timestamp, and a URL for accessing the file content.
- [The File object | Stripe API Reference](https://docs.stripe.com/api/files/object): The File object details include its unique identifier, purpose (e.g., dispute_evidence, identity_document), type (e.g., pdf, png), creation timestamp, and an optional expiration timestamp. It also contains links to access the file's content or related resources.
- [Create a file | Stripe API Reference](https://docs.stripe.com/api/files/create): This Stripe API endpoint allows you to upload a file using a multipart/form-data request. You must provide the file itself and specify its purpose, such as 'dispute_evidence' or 'identity_document'. The API returns the created File object upon successful upload.
- [Retrieve a file | Stripe API Reference](https://docs.stripe.com/api/files/retrieve): The Retrieve a file endpoint allows you to fetch the details of an existing file object using its unique ID. If the ID is valid, Stripe returns the corresponding file object, including its metadata and URL. Otherwise, an error is raised.
- [List all files | Stripe API Reference](https://docs.stripe.com/api/files/list): This Stripe API endpoint lists all files accessible to your account, sorted by creation date with the most recent first. You can filter the results by file purpose and use parameters like 'limit', 'starting_after', and 'ending_before' for pagination. The response includes an array of file objects and pagination links.
- [File Links | Stripe API Reference](https://docs.stripe.com/api/file_links): File Links in Stripe allow sharing of File objects with non-authenticated users via a unique URL. A File Link object contains an ID, expiration timestamp, the associated file, and a public URL for accessing the file's content. It can also store custom metadata.
- [The File Link object | Stripe API Reference](https://docs.stripe.com/api/file_links/object): The File Link object includes attributes such as ID, creation timestamp, expiration status, and an optional expiration timestamp. It references a specific file and provides a unique, publicly accessible URL for downloading the file's content without authentication.
- [Create a file link | Stripe API Reference](https://docs.stripe.com/api/file_links/create): This Stripe API endpoint creates a new file link, enabling you to share a file via a URL. You must provide the ID of the file and can optionally set an expiration timestamp and metadata. The API returns the created File Link object upon success.
- [Update a file link | Stripe API Reference](https://docs.stripe.com/api/file_links/update): The Update a file link API allows modification of an existing file link's expiration timestamp and metadata. Expired links cannot be updated. You can also set the link to expire immediately by providing 'now' as the timestamp. The updated file link object is returned upon success.
- [Retrieve a file link | Stripe API Reference](https://docs.stripe.com/api/file_links/retrieve): This Stripe API endpoint retrieves a specific file link using its ID. If the provided ID is valid, the corresponding file link object is returned, containing details like the URL and expiration status. An error is raised for invalid IDs.
- [List all file links | Stripe API Reference](https://docs.stripe.com/api/file_links/list): The List all file links endpoint returns a list of file links associated with your account. You can filter these links by file, expiration status, and creation date, and use pagination parameters like 'limit' and 'starting_after'. The response provides an array of file link objects.
- [Mandates | Stripe API Reference](https://docs.stripe.com/api/mandates): The Mandate object represents a customer's permission to debit their payment method. It includes details about customer acceptance, the associated payment method, and its status (active, inactive, pending). Mandates can be of type multi_use or single_use.
- [The Mandate object | Stripe API Reference](https://docs.stripe.com/api/mandates/object): This page details the attributes of the Mandate object, including its unique ID, customer acceptance information, and payment method details. It outlines the possible statuses (active, inactive, pending) and types (multi_use, single_use) of a mandate. The object also includes live mode status and optional fields for multi_use and single_use configurations.
- [Retrieve a Mandate | Stripe API Reference](https://docs.stripe.com/api/mandates/retrieve): This API endpoint retrieves a specific Mandate object using its ID. It does not require any parameters for the retrieval itself. The response returns the full Mandate object, providing details about the customer's permission to debit their payment method.
- [Payment Intents | Stripe API Reference](https://docs.stripe.com/api/payment_intents): A PaymentIntent guides the process of collecting a payment from a customer, with one PaymentIntent typically corresponding to one order or customer session. It transitions through various statuses as it interacts with Stripe.js for authentication and ultimately results in at most one successful charge. Key attributes include amount, currency, and payment method configurations.
- [The PaymentIntent object | Stripe API Reference](https://docs.stripe.com/api/payment_intents/object): This page describes the PaymentIntent object, which is a unique identifier for a payment collection process. It includes essential details such as the amount, currency, and customer information. The object also contains a client_secret for client-side retrieval and settings for automatic payment methods.
- [Create a PaymentIntent | Stripe API Reference](https://docs.stripe.com/api/payment_intents/create): This API endpoint creates a PaymentIntent object, which represents a customer's intent to pay. After creation, a payment method must be attached and confirmed to complete the payment. The `confirm=true` parameter allows for immediate creation and confirmation in a single call.
- [Update a PaymentIntent | Stripe API Reference](https://docs.stripe.com/api/payment_intents/update): This API endpoint updates properties of a PaymentIntent object without confirming the payment. Changes to certain properties, like the payment method, may require re-confirmation. For simultaneous updates and confirmations, it's recommended to use the confirm API.
- [Retrieve a PaymentIntent | Stripe API Reference](https://docs.stripe.com/api/payment_intents/retrieve): This API endpoint retrieves the details of a previously created PaymentIntent. It can be used client-side with a publishable key and the `client_secret`, though this only returns a subset of properties. The endpoint requires a valid PaymentIntent identifier or client secret for retrieval.
- [List all PaymentIntent LineItems | Stripe API Reference](https://docs.stripe.com/api/payment_intents/amount_details_line_items): This API endpoint lists all LineItems associated with a given PaymentIntent. It allows for pagination using `ending_before` and `starting_after` parameters. The response contains an array of line item objects, each detailing product information, quantity, and costs.
- [List all PaymentIntents | Stripe API Reference](https://docs.stripe.com/api/payment_intents/list): This API endpoint returns a list of PaymentIntents, with options to filter by customer. It supports pagination and can retrieve a specified number of PaymentIntents using the `limit` parameter. The response includes an array of PaymentIntent objects or an empty array if none match.
- [Cancel a PaymentIntent | Stripe API Reference](https://docs.stripe.com/api/payment_intents/cancel): This API endpoint allows for the cancellation of a PaymentIntent object when it is in specific statuses like `requires_payment_method` or `requires_capture`. Cancellation prevents further charges and automatically refunds any capturable amount for `requires_capture` statuses. A `cancellation_reason` can optionally be provided.
- [Capture a PaymentIntent | Stripe API Reference](https://docs.stripe.com/api/payment_intents/capture): This API endpoint captures funds from an existing, uncaptured PaymentIntent that is in the `requires_capture` status. The capture can be for the full amount or a partial amount up to the `amount_capturable`. Uncaptured PaymentIntents are automatically canceled after a set period if not captured.
- [Confirm a PaymentIntent | Stripe API Reference](https://docs.stripe.com/api/payment_intents/confirm): This API endpoint confirms a customer's intent to pay with a specific payment method, initiating the payment process. If additional authentication is needed, the PaymentIntent status changes to `requires_action`. Successful confirmation leads to a `succeeded` or `requires_capture` status, while failure results in `requires_payment_method` or `canceled`.
- [Increment an authorization | Stripe API Reference](https://docs.stripe.com/api/payment_intents/increment_authorization): This API endpoint performs an incremental authorization on an eligible PaymentIntent, allowing an increase to the initially authorized amount. The PaymentIntent must be in the `requires_capture` status and support incremental authorizations. A PaymentIntent can undergo multiple incremental authorization attempts, up to a maximum of 10.
- [Reconcile a customer_balance PaymentIntent | Stripe API Reference](https://docs.stripe.com/api/payment_intents/apply_customer_balance): This API endpoint manually reconciles the remaining amount for a `customer_balance` PaymentIntent using funds from the customer's cash balance. If the PaymentIntent was created by an Invoice, the full amount is applied. When the `amount` parameter is omitted, it defaults to the remaining requested amount.
- [Search PaymentIntents | Stripe API Reference](https://docs.stripe.com/api/payment_intents/search): This API endpoint allows searching for previously created PaymentIntents using Stripe’s Search Query Language. It's important to note that search is not suitable for strict read-after-write consistency flows. Data is typically searchable within a minute, but can take up to an hour during outages. Search is not available to merchants in India.
- [Verify microdeposits on a PaymentIntent | Stripe API Reference](https://docs.stripe.com/api/payment_intents/verify_microdeposits): This API endpoint verifies microdeposits made to a bank account associated with a PaymentIntent. It requires two integer amounts representing the microdeposit values and an optional `descriptor_code`. Upon successful verification, the PaymentIntent object is returned.
- [Persons | Stripe API Reference](https://docs.stripe.com/api/v2/core/persons): The Person object v2 represents an individual associated with an Account's identity for verification and compliance purposes. It includes attributes such as ID, account association, addresses, names, date of birth, and identification numbers. This object is used to provide and update identity information.
- [The Person object | Stripe API Reference](https://docs.stripe.com/api/v2/core/persons/object): This page details the attributes of the Person object v2, including its unique ID, account association, and various personal details like addresses, names, date of birth, and email. It also includes fields for identification numbers, gender, live mode status, and metadata. This object is crucial for identity verification and compliance.
- [Create a person | Stripe API Reference](https://docs.stripe.com/api/v2/core/persons/create): This API endpoint creates a Person object, associating an individual with an Account's identity. It allows for the inclusion of relationship attributes and identity information such as addresses, date of birth, and identification numbers. The `account_id` is a required parameter for this operation.
- [Update a person | Stripe API Reference](https://docs.stripe.com/api/v2/core/persons/update): This page details how to update a Person object associated with a Stripe Account using the API. It outlines the required parameters such as account ID and person ID, and lists various optional fields for updating additional information like addresses, names, and documents.
- [Retrieve a Person | Stripe API Reference](https://docs.stripe.com/api/v2/core/persons/retrieve): This page explains how to retrieve a specific Person object associated with a Stripe Account via the API. It details the required parameters (account ID and person ID) and lists the attributes returned, including the person's ID, account, address, and creation timestamp.
- [List Persons | Stripe API Reference](https://docs.stripe.com/api/v2/core/persons/list): This page describes how to list all Person objects associated with a Stripe Account using the API. It specifies the required account ID parameter and optional limit and page parameters for pagination. The response includes a list of Person objects and URLs for navigating through pages.
- [Delete a Person | Stripe API Reference](https://docs.stripe.com/api/v2/core/persons/delete): This page provides instructions for deleting a Person object associated with a Stripe Account via the API. It requires the account ID and the person's ID as parameters. The response confirms the deletion with the person's ID and a boolean indicating deletion status.
- [Person event types | Stripe API Reference](https://docs.stripe.com/api/v2/core/persons/event-types): This page lists the available public thin event types for updates to Person objects in the Stripe API. It notes that these events are continually evolving and that the payload is unversioned, requiring fetching the resource's current state or versioned event during processing.
- [Person Tokens | Stripe API Reference](https://docs.stripe.com/api/v2/core/person-tokens): This page introduces Person Tokens, which are single-use tokens used to tokenize person information for creating or updating a Person object via the Stripe API. It details the available endpoints for creating and retrieving Person Tokens and describes the attributes of the Person Token object.
- [The Person Token object | Stripe API Reference](https://docs.stripe.com/api/v2/core/person-tokens/object): This page details the attributes of the Person Token object in the Stripe API, including its unique identifier, creation and expiration timestamps, live mode status, and whether it has been used. It also describes the process of creating a Person Token, which involves associating it with an Account and providing person details.
- [Create a Person Token | Stripe API Reference](https://docs.stripe.com/api/v2/core/person-tokens/create): This page explains how to create a Person Token associated with a Stripe Account using the API. It lists the required account ID and various optional parameters for including person details such as addresses, names, date of birth, and identification numbers.
- [Retrieve a Person Token | Stripe API Reference](https://docs.stripe.com/api/v2/core/person-tokens/retrieve): This page describes how to retrieve a Person Token associated with a Stripe Account using the API. It requires both the account ID and the token ID as parameters. The response includes details about the token, such as its ID, creation and expiration times, and usage status.
- [Setup Intents | Stripe API Reference](https://docs.stripe.com/api/setup_intents): This page introduces SetupIntents, which guide users through saving customer payment credentials for future use without immediate payment. It explains that SetupIntents transition through various statuses and result in optimized payment credentials, recommending their use to reduce customer friction.
- [The SetupIntent object | Stripe API Reference](https://docs.stripe.com/api/setup_intents/object): This page details the attributes of the SetupIntent object in the Stripe API. It includes properties like ID, client secret, customer and account associations, description, and the status of the setup process. The object also contains information about the last setup error and metadata.
- [Create a SetupIntent | Stripe API Reference](https://docs.stripe.com/api/setup_intents/create): This page explains how to create a SetupIntent object using the Stripe API, which is used to set up and save a customer's payment credentials. Parameters include options for automatic payment methods, confirmation, customer or account association, and description.
- [Update a SetupIntent | Stripe API Reference](https://docs.stripe.com/api/setup_intents/update): This page describes how to update a SetupIntent object via the Stripe API. It allows modification of parameters such as customer or account association, description, metadata, and the payment method. The update operation returns the modified SetupIntent object.
- [Retrieve a SetupIntent | Stripe API Reference](https://docs.stripe.com/api/setup_intents/retrieve): This page details how to retrieve a SetupIntent using the Stripe API, allowing access to its details. It explains that retrieval with a publishable key requires a client secret and returns a subset of properties. The API call returns the SetupIntent object if a valid identifier is provided.
- [List all SetupIntents | Stripe API Reference](https://docs.stripe.com/api/setup_intents/list): This page explains how to list all SetupIntents using the Stripe API, with options to filter by customer, customer account, or payment method. The response provides a list of SetupIntent objects, including URLs for navigating to the next or previous pages.
- [Cancel a SetupIntent | Stripe API Reference](https://docs.stripe.com/api/setup_intents/cancel): This page describes how to cancel a SetupIntent object using the Stripe API, which can be done when the intent is in specific statuses like requires_payment_method. Cancellation abandons the setup process, and the API returns the updated SetupIntent object, indicating its canceled status.
- [Confirm a SetupIntent | Stripe API Reference](https://docs.stripe.com/api/setup_intents/confirm): This page explains how to confirm a SetupIntent using the Stripe API, which signifies the customer's intent to set up a payment method for future use. The confirmation process transitions the SetupIntent through various statuses, potentially requiring additional customer actions or resulting in success or failure.
- [Verify microdeposits on a SetupIntent | Stripe API Reference](https://docs.stripe.com/api/setup_intents/verify_microdeposits): This page details how to verify microdeposits on a SetupIntent using the Stripe API. It requires providing the amounts of the microdeposits and a descriptor code. Upon successful verification, the API returns the updated SetupIntent object, often indicating a succeeded status.
- [Setup Attempts | Stripe API Reference](https://docs.stripe.com/api/setup_attempts): This page introduces SetupAttempts, which describe individual attempts to confirm a SetupIntent, whether successful or not. They allow inspection of details related to a specific attempt at setting up a payment method. The page also lists attributes of the SetupAttempt object.
- [The SetupAttempt object | Stripe API Reference](https://docs.stripe.com/api/setup_attempts/object): This page details the attributes of the SetupAttempt object in the Stripe API, which represents an attempt to confirm a SetupIntent. It includes properties such as ID, creation timestamp, and associations with application, customer, and customer account. The object also indicates flow directions for money movement.
- [List all SetupAttempts | Stripe API Reference](https://docs.stripe.com/api/setup_attempts/list): This page details how to list all SetupAttempts associated with a given SetupIntent. It provides the API endpoint and explains the parameters for filtering and pagination, along with an example response.
- [Payouts | Stripe API Reference](https://docs.stripe.com/api/payouts): This page introduces the Stripe Payout object, explaining that payouts are funds transferred to bank accounts or debit cards. It covers the creation, updating, retrieval, listing, cancellation, and reversal of payouts, noting that payout schedules vary by region.
- [The Payout object | Stripe API Reference](https://docs.stripe.com/api/payouts/object): This section describes the attributes of the Stripe Payout object, including its ID, amount, currency, status (paid, pending, in_transit, canceled, failed), and arrival date. It also details optional fields like description, metadata, and statement descriptor.
- [Create a payout | Stripe API Reference](https://docs.stripe.com/api/payouts/create): This page explains how to create a new payout object in Stripe to send funds to a bank account. It requires the payout amount and currency, and notes that the Stripe balance must cover the payout. Test mode operations mimic live mode actions without actual fund transfer.
- [Update a payout | Stripe API Reference](https://docs.stripe.com/api/payouts/update): This page describes how to update an existing Stripe payout, noting that only the metadata parameter can be modified. The request returns the updated payout object or an error if the parameters are invalid.
- [Retrieve a payout | Stripe API Reference](https://docs.stripe.com/api/payouts/retrieve): This page details how to retrieve the details of an existing Stripe payout by providing its unique ID. It returns the corresponding payout information or an error if the ID is invalid.
- [List all payouts | Stripe API Reference](https://docs.stripe.com/api/payouts/list): This page explains how to list all Stripe payouts, which are funds sent to bank accounts or debit cards. It allows filtering by status (pending, paid, failed, canceled) and provides parameters for pagination.
- [Cancel a payout | Stripe API Reference](https://docs.stripe.com/api/payouts/cancel): This page describes how to cancel a pending Stripe payout, which refunds the funds to your available balance. Automatic Stripe payouts cannot be canceled, and the endpoint returns the payout object upon successful cancellation or an error if it cannot be canceled.
- [Reverse a payout | Stripe API Reference](https://docs.stripe.com/api/payouts/reverse): This page details how to reverse a Stripe payout by debiting the destination bank account, applicable only to connected accounts with US and Canadian bank accounts. It confirms that the user authorizes the debit and returns the reversing payout object or an error.
- [Refunds | Stripe API Reference](https://docs.stripe.com/api/refunds): This page introduces Stripe refunds, which allow refunding previously created charges to the original payment method. It covers creating, updating, retrieving, listing, and canceling refunds, detailing the Refund object's attributes like amount, charge, currency, and status.
- [The Refund object | Stripe API Reference](https://docs.stripe.com/api/refunds/object): This section describes the attributes of the Stripe Refund object, including its ID, amount, currency, and status (pending, succeeded, failed, canceled). It also details associated charge or PaymentIntent IDs, reason for the refund, and metadata.
- [Create a refund | Stripe API Reference](https://docs.stripe.com/api/refunds/create): This page explains how to create a refund in Stripe, which requires specifying a Charge or PaymentIntent object. Partial refunds are supported up to the unrefunded amount of the charge, and a charge cannot be refunded multiple times.
- [Update a refund | Stripe API Reference](https://docs.stripe.com/api/refunds/update): This page details how to update a Stripe refund, allowing modification of parameters like metadata. Any parameters not provided remain unchanged, and the request returns the updated refund object or an error for invalid parameters.
- [Retrieve a refund | Stripe API Reference](https://docs.stripe.com/api/refunds/retrieve): This page explains how to retrieve the details of an existing Stripe refund using its unique ID. It returns the refund object if the ID is valid, otherwise, it raises an error.
- [List all refunds | Stripe API Reference](https://docs.stripe.com/api/refunds/list): This page describes how to list all Stripe refunds, ordered by most recent. It allows filtering refunds by a specific Charge ID or PaymentIntent ID and provides parameters for pagination.
- [Cancel a refund | Stripe API Reference](https://docs.stripe.com/api/refunds/cancel): This page explains that a refund can be canceled only if its status is 'requires_action', which applies to refunds for payment methods needing customer action. The endpoint returns the refund object upon successful cancellation or an error if it cannot be canceled.
- [Confirmation Token | Stripe API Reference](https://docs.stripe.com/api/confirmation_tokens): This page introduces Stripe Confirmation Tokens, which securely transport client-side data to the server for confirming PaymentIntents or SetupIntents. It details the attributes of the Confirmation Token object, including its ID, creation time, expiration, and associated payment details.
- [The Confirmation Token object | Stripe API Reference](https://docs.stripe.com/api/confirmation_tokens/object): This section describes the attributes of the Stripe Confirmation Token object, including its unique ID, creation timestamp, expiration time, and live mode status. It also covers associated data like mandate details, payment intent, and return URL.
- [Retrieve a ConfirmationToken | Stripe API Reference](https://docs.stripe.com/api/confirmation_tokens/retrieve): This page explains how to retrieve an existing Stripe ConfirmationToken object using its ID. It returns the specified ConfirmationToken, which is used to confirm PaymentIntents or SetupIntents.
- [Create a test Confirmation Token | Stripe API Reference](https://docs.stripe.com/api/confirmation_tokens/test_create): This page describes how to create a test mode Confirmation Token on the server-side for integration testing. It allows specifying a PaymentMethod ID or providing payment method data, along with a return URL and setup future usage preference.
- [Tokens | Stripe API Reference](https://docs.stripe.com/api/tokens): Stripe's Token API facilitates the secure collection of sensitive payment and personal information directly from customers. It generates single-use tokens representing this data, which are then used in API requests, ensuring sensitive data never touches your server when client-side tokenization is used. The API supports creating tokens for bank accounts, cards, CVC updates, persons, PII, and accounts.
- [The Token object | Stripe API Reference](https://docs.stripe.com/api/tokens/object): The Token object in Stripe's API represents sensitive customer information like card or bank account details, or PII, that has been tokenized for secure use. It includes attributes such as a unique ID, creation timestamp, type (e.g., 'card', 'bank_account'), and a boolean indicating if it has been used. The object can contain nested details about the card or bank account it represents.
- [Create a bank account token | Stripe API Reference](https://docs.stripe.com/api/tokens/create_bank_account): This Stripe API endpoint creates a single-use token representing bank account details. This token can be used in place of a full bank account dictionary in API v1 methods, particularly for connected accounts. The token is single-use and requires specific bank account parameters like country, currency, account holder name, routing number, and account number.
- [Create a card token | Stripe API Reference](https://docs.stripe.com/api/tokens/create_card): This Stripe API endpoint creates a single-use token for credit card details. The token can be used in place of a credit card dictionary in any v1 API method and can be used once to create a new Charge or attach to a Customer. API access to raw card data must be enabled, and using Stripe's recommended payment integrations is generally preferred over direct API use.
- [Create a CVC update token | Stripe API Reference](https://docs.stripe.com/api/tokens/create_cvc_update): This Stripe API endpoint generates a single-use token for an updated CVC value. It is used for CVC re-collection, specifically when confirming a card payment or using a saved card with a PaymentIntent that has `confirmation_method: manual`. For automatic confirmation methods or general use, Stripe's JavaScript library or recommended payment integrations are advised over direct API tokenization of the CVC.
- [Create a person token | Stripe API Reference](https://docs.stripe.com/api/tokens/create_person): This Stripe API endpoint creates a single-use token representing a person's details, used for creating or updating persons associated with a Connect account. Token creation has specific key requirements: in live mode, only the publishable key can be used, while in test mode, either the secret or publishable key is acceptable. The token encapsulates personal information required for account verification.
- [Create a PII token | Stripe API Reference](https://docs.stripe.com/api/tokens/create_pii): This Stripe API endpoint creates a single-use token for personally identifiable information (PII). The token can substitute for `id_number` or `id_number_secondary` in Account or Person Update API methods. PII tokens are single-use and are designed to securely transmit sensitive identification details.
- [Create an account token | Stripe API Reference](https://docs.stripe.com/api/tokens/create_account): This Stripe API endpoint creates a single-use token that encapsulates a user's legal entity information, primarily for creating or updating Connect accounts. In live mode, this token can only be created using the application's publishable key, whereas in test mode, either the secret or publishable key can be used. The token simplifies the process of providing account-related legal entity data.
- [Retrieve a token | Stripe API Reference](https://docs.stripe.com/api/tokens/retrieve): This Stripe API endpoint retrieves a token using its unique ID. If a valid token ID is provided, the API returns the corresponding token object; otherwise, it raises an error. This is useful for inspecting token details after creation or for verification purposes.
- [Payment Methods | Stripe API Reference](https://docs.stripe.com/api/payment_methods): Stripe's PaymentMethod objects represent customer payment instruments, which can be used with PaymentIntents for collecting payments or saved to Customer objects for future use. The API provides endpoints to create, update, retrieve, list, attach, and detach PaymentMethods. PaymentMethods can be of various types, such as cards, bank accounts, or digital wallets, each with specific attributes.
- [The PaymentMethod object | Stripe API Reference](https://docs.stripe.com/api/payment_methods/object): The PaymentMethod object in Stripe's API details a customer's payment instrument, including its unique ID, billing information, associated customer ID (if saved), and type. The 'type' attribute determines which additional hash is included, containing specific details for that payment method (e.g., card details, bank account information). This object is fundamental for managing and processing customer payments.
- [Create a PaymentMethod | Stripe API Reference](https://docs.stripe.com/api/payment_methods/create): This Stripe API endpoint creates a PaymentMethod object, representing a customer's payment instrument. While direct creation is possible, Stripe recommends using the PaymentIntents API for immediate payments or the SetupIntent API for collecting future payment details. The 'type' parameter is required and specifies the kind of payment method being created, such as 'card' or 'us_bank_account'.
- [Update a PaymentMethod | Stripe API Reference](https://docs.stripe.com/api/payment_methods/update): This Stripe API endpoint updates an existing PaymentMethod object, which must be attached to a customer. Updates can include modifying billing details and metadata. Specific payment method types like 'card', 'payto', or 'us_bank_account' can also be updated with relevant parameters. The endpoint returns the updated PaymentMethod object upon success.
- [Retrieve a Customer's PaymentMethod | Stripe API Reference](https://docs.stripe.com/api/payment_methods/customer): This Stripe API endpoint retrieves a specific PaymentMethod object associated with a given Customer. It requires both the customer ID and the PaymentMethod ID. The response includes details about the payment method, such as its type, card information (if applicable), and its association with the customer.
- [Retrieve a PaymentMethod | Stripe API Reference](https://docs.stripe.com/api/payment_methods/retrieve): This Stripe API endpoint retrieves a PaymentMethod object attached to a Stripe Account. To retrieve a PaymentMethod linked to a Customer, the 'Retrieve a Customer's PaymentMethods' endpoint should be used instead. The endpoint returns the PaymentMethod object if the ID is valid.
- [List a Customer's PaymentMethods | Stripe API Reference](https://docs.stripe.com/api/payment_methods/customer_list): This Stripe API endpoint returns a list of PaymentMethods for a specified Customer. An optional `type` parameter can filter the results to include only specific payment method types, reducing payload size. The response contains an array of PaymentMethod objects, with options to control the number of results and pagination.
- [List PaymentMethods | Stripe API Reference](https://docs.stripe.com/api/payment_methods/list): This Stripe API endpoint returns a list of all PaymentMethods. The list can be filtered by `type` to include only specific payment method types, excluding custom ones by default. Parameters allow for filtering by customer, customer account, and pagination controls, returning an array of PaymentMethod objects.
- [Attach a PaymentMethod to a Customer | Stripe API Reference](https://docs.stripe.com/api/payment_methods/attach): This Stripe API endpoint attaches a PaymentMethod object to a Customer, making it available for future use. For optimal future payment processing, it's recommended to use a SetupIntent or PaymentIntent with `setup_future_usage` before attaching. This action can also set the PaymentMethod as the default for invoices or subscriptions by updating the customer's `invoice_settings.default_payment_method`.
- [Detach a PaymentMethod from a Customer | Stripe API Reference](https://docs.stripe.com/api/payment_methods/detach): This Stripe API endpoint detaches a PaymentMethod object from a Customer. Once detached, the PaymentMethod can no longer be used for payments or re-attached to any customer. The endpoint returns the detached PaymentMethod object upon successful execution.
- [Payment Method Configurations | Stripe API Reference](https://docs.stripe.com/api/payment_method_configurations): PaymentMethodConfigurations control which payment methods are presented to customers when specific types are not explicitly defined. Configurations can be direct (for payments on your account) or child (for payments on connected accounts), with child configurations inheriting settings from a parent. These configurations allow for dynamic display of payment options based on context and can be managed via the API or dashboard.
- [The Payment Method Configuration object | Stripe API Reference](https://docs.stripe.com/api/payment_method_configurations/object): The Payment Method Configuration object defines settings for how payment methods are presented and managed within Stripe. It includes attributes like activation status, default settings, and specific configurations for various payment methods such as cards, Apple Pay, and Google Pay.
- [Create a payment method configuration | Stripe API Reference](https://docs.stripe.com/api/payment_method_configurations/create): This page details how to create a Payment Method Configuration object using the Stripe API. It outlines the required parameters, such as 'name' or 'parent', and lists the various payment methods that can be configured, including their display preferences.
- [Update payment method configuration | Stripe API Reference](https://docs.stripe.com/api/payment_method_configurations/update): This documentation explains how to update an existing Payment Method Configuration object via the Stripe API. You can modify the 'active' status and 'name' of a configuration, along with specific settings for individual payment methods.
- [Retrieve payment method configuration | Stripe API Reference](https://docs.stripe.com/api/payment_method_configurations/retrieve): This page describes how to retrieve a specific Payment Method Configuration object using its ID via the Stripe API. It details the parameters required and the structure of the returned payment method configuration object.
- [List payment method configurations | Stripe API Reference](https://docs.stripe.com/api/payment_method_configurations/list): This page explains how to list all existing Payment Method Configuration objects using the Stripe API. It details the available parameters for filtering and pagination, and the structure of the returned list.
- [Payment Method Domains | Stripe API Reference](https://docs.stripe.com/api/payment_method_domains): A Payment Method Domain object represents a registered web domain with Stripe, used to control the display of specific payment methods in Stripe Elements. The page outlines the attributes of this object, such as domain name and enabled status, and lists endpoints for managing these domains.
- [The PaymentMethodDomain object | Stripe API Reference](https://docs.stripe.com/api/payment_method_domains/object): The PaymentMethodDomain object represents a registered web domain with Stripe that controls the visibility of payment methods in Stripe Elements. Key attributes include the domain name, its enabled status, and specific statuses for integrated payment methods like Apple Pay and Google Pay.
- [Create a payment method domain | Stripe API Reference](https://docs.stripe.com/api/payment_method_domains/create): This page details how to create a Payment Method Domain object using the Stripe API. It requires the domain name and an 'enabled' status, and returns the created domain object, which links web domains to payment method availability.
- [Update a payment method domain | Stripe API Reference](https://docs.stripe.com/api/payment_method_domains/update): This documentation describes how to update an existing Payment Method Domain object via the Stripe API, primarily by toggling its 'enabled' status. This action affects whether payment methods requiring domain registration will appear in Elements or Embedded Checkout.
- [Retrieve a payment method domain | Stripe API Reference](https://docs.stripe.com/api/payment_method_domains/retrieve): This page explains how to retrieve a specific Payment Method Domain object using its ID via the Stripe API. It outlines the parameters required and the structure of the returned payment method domain object, including its associated payment methods.
- [List payment method domains | Stripe API Reference](https://docs.stripe.com/api/payment_method_domains/list): This page details how to list existing Payment Method Domain objects using the Stripe API. It describes the available parameters for filtering and pagination, and the structure of the returned list of payment method domains.
- [Validate an existing payment method domain | Stripe API Reference](https://docs.stripe.com/api/payment_method_domains/validate): This endpoint allows for validating a payment method domain, which is necessary for certain payment methods if their registration requirements were not met during creation. Validation ensures the payment method becomes active and appears in Elements or Embedded Checkout for that domain.
- [Bank Accounts | Stripe API Reference](https://docs.stripe.com/api/customer_bank_accounts): Bank accounts are presented as payment methods on Customer objects within Stripe. This section details the attributes of the Bank Account object, such as account holder information, bank name, country, and currency, and lists the available API endpoints for managing them.
- [The Bank Account object | Stripe API Reference](https://docs.stripe.com/api/customer_bank_accounts/object): The Bank Account object in Stripe represents a customer's bank account used as a payment method. It includes details like the account holder's name and type, bank name, country, currency, and the last four digits of the account number. It also contains status information and can be linked to a customer.
- [Create a bank account | Stripe API Reference](https://docs.stripe.com/api/customer_bank_accounts/create): This page describes how to create a bank account as a payment method for a Customer using the Stripe API. It requires a source (like a token or bank details) and returns the created bank account object, including its status and associated customer ID.
- [Update a bank account | Stripe API Reference](https://docs.stripe.com/api/customer_bank_accounts/update): This documentation explains how to update a customer's bank account details via the Stripe API. Specifically, you can modify the account holder's name, account holder type, and metadata; other bank account details are not editable.
- [Retrieve a bank account | Stripe API Reference](https://docs.stripe.com/api/customer_bank_accounts/retrieve): This page details how to retrieve a specific bank account object associated with a customer using the Stripe API. It outlines the endpoint and the structure of the returned bank account object, including its status and associated customer ID.
- [List all bank accounts | Stripe API Reference](https://docs.stripe.com/api/customer_bank_accounts/list): This page explains how to list all bank accounts associated with a specific customer using the Stripe API. It allows for pagination using 'limit' and 'starting_after' parameters to retrieve more than the default 10 most recent sources.
- [Delete a bank account | Stripe API Reference](https://docs.stripe.com/api/customer_bank_accounts/delete): This documentation describes how to delete a bank account from a customer's payment methods using the Stripe API. The endpoint and the response indicating the deleted status are provided.
- [Verify a bank account | Stripe API Reference](https://docs.stripe.com/api/customer_bank_accounts/verify): This page explains how to verify a customer's bank account using microdeposits via the Stripe API. It details the required 'amounts' parameter, which consists of two positive integers representing the microdeposit values.
- [Cash Balance | Stripe API Reference](https://docs.stripe.com/api/cash_balance): The Cash balance object represents real funds a customer can add via bank transfer, which can then be used for payments or payouts. This page details the API endpoints for retrieving and updating a customer's cash balance settings.
- [The Cash balance object | Stripe API Reference](https://docs.stripe.com/api/cash_balance/object): This page describes the attributes of the Stripe Cash balance object, including its available funds, associated customer, live mode status, and settings. It also provides details on how to update these settings and retrieve the cash balance.
- [Update a cash balance's settings | Stripe API Reference](https://docs.stripe.com/api/cash_balance/update): This page explains how to update the settings for a customer's cash balance, specifically focusing on parameters like reconciliation mode. It provides the API endpoint and example request/response for modifying these settings.
- [Retrieve a cash balance | Stripe API Reference](https://docs.stripe.com/api/cash_balance/retrieve): This page details how to retrieve a customer's cash balance using the Stripe API. It outlines the endpoint and provides an example of the expected response, which includes the available balance and settings.
- [Cash Balance Transaction | Stripe API Reference](https://docs.stripe.com/api/cash_balance_transactions): Cash Balance Transactions represent the movement of funds into or out of a customer's cash balance, such as funding, allocation to payments, or refunds. This page lists the API endpoints for creating funding instructions, retrieving, listing, and funding test mode cash balances.
- [The Cash Balance Transaction object | Stripe API Reference](https://docs.stripe.com/api/cash_balance_transactions/object): This page details the attributes of a Cash Balance Transaction object, including its ID, creation timestamp, currency, and associated customer. It also describes properties related to overdraft adjustments, payment applications, funding details, and the net amount of the transaction.
- [Create or retrieve funding instructions for a customer cash balance | Stripe API Reference](https://docs.stripe.com/api/cash_balance_transactions/create_or_retrieve_funding_instructions): This page describes how to create or retrieve funding instructions for a customer's cash balance, specifically for bank transfers. It outlines the required parameters such as currency and funding type, and provides an example response showing bank transfer details.
- [Retrieve a cash balance transaction | Stripe API Reference](https://docs.stripe.com/api/cash_balance_transactions/retrieve): This page explains how to retrieve a specific cash balance transaction that modified a customer's balance. It provides the API endpoint for this action and includes example requests and responses, detailing transaction information like type, amount, and funding source.
- [List cash balance transactions | Stripe API Reference](https://docs.stripe.com/api/cash_balance_transactions/list): This page details how to list transactions that have modified a customer's cash balance. It provides the API endpoint and parameters for pagination, along with an example response showing a list of cash balance transaction objects.
- [Fund a test mode cash balance | Stripe API Reference](https://docs.stripe.com/api/cash_balance_transactions/fund_cash_balance): This page describes the test helper endpoint to fund a customer's cash balance in test mode. It outlines the required parameters like amount and currency, and provides an example request and response for creating a test cash balance transaction.
- [Cards | Stripe API Reference](https://docs.stripe.com/api/cards): This page details the Stripe API for managing card objects, which represent customer payment instruments. It outlines endpoints for creating, updating, retrieving, listing, and deleting cards associated with customers or recipients.
- [The Card object | Stripe API Reference](https://docs.stripe.com/api/cards/object): This page describes the attributes of the Stripe Card object, including its ID, address details, brand, country, and expiration date. It also includes information about the associated customer, CVC check results, and fingerprint.
- [Create a card | Stripe API Reference](https://docs.stripe.com/api/cards/create): This page explains how to create a new card for a customer or recipient using the Stripe API. It details the required parameters, such as the source token or card details, and provides an example of the created Card object response.
- [Update a card | Stripe API Reference](https://docs.stripe.com/api/cards/update): This page describes how to update an existing card for a customer using the Stripe API. It lists the available parameters for modifying card details like address, expiration date, and metadata, and provides an example API call and response.
- [Retrieve a card | Stripe API Reference](https://docs.stripe.com/api/cards/retrieve): This page details how to retrieve specific card details for a customer using the Stripe API. It provides the endpoint for retrieving a single card and an example response containing the card's attributes.
- [List all cards | Stripe API Reference](https://docs.stripe.com/api/cards/list): This page explains how to list all cards associated with a customer using the Stripe API. It provides the endpoint and parameters for pagination, along with an example response showing a list of card objects.
- [Delete a card | Stripe API Reference](https://docs.stripe.com/api/cards/delete): This page describes how to delete a card from a customer or recipient using the Stripe API. It outlines the API endpoint and provides an example of the response, indicating that the card object has been deleted.
- [Sources | Stripe API Reference](https://docs.stripe.com/api/sources): The Sources API allows for accepting various payment methods by representing a customer's payment instrument. It provides endpoints for creating, updating, retrieving, attaching, and detaching sources, though the PaymentMethods API is now recommended.
- [The Source object | Stripe API Reference](https://docs.stripe.com/api/sources/object): This page details the attributes of the deprecated Stripe Source object, including its ID, amount, currency, and associated customer. It also covers metadata, owner information, redirect details, statement descriptor, and status.
- [Create a source | Stripe API Reference](https://docs.stripe.com/api/sources/create): This page explains how to create a new source object using the Stripe API, specifying the type of source and optionally an amount, currency, metadata, owner, or redirect parameters. It provides an example API call and response for creating a source.
- [Update a source | Stripe API Reference](https://docs.stripe.com/api/sources/update): This page details how to update an existing source object in Stripe. You can modify parameters like amount, metadata, and owner information. It also allows for type-specific updates for certain payment methods.
- [Retrieve a source | Stripe API Reference](https://docs.stripe.com/api/sources/retrieve): This page explains how to retrieve details of an existing source object using its unique ID. The API returns the most up-to-date information for the specified source.
- [Attach a source | Stripe API Reference](https://docs.stripe.com/api/sources/attach): This page describes how to attach a Stripe Source object to a Customer. The source must be in a chargeable or pending state to be attached, and metadata can be included.
- [Detach a source | Stripe API Reference](https://docs.stripe.com/api/sources/detach): This page details how to detach a Stripe Source object from a Customer. Once detached, the source's status changes to 'consumed' and it can no longer be used for charges.
- [Products | Stripe API Reference](https://docs.stripe.com/api/products): This page introduces Stripe Products, which represent goods or services offered to customers. Products can be used with Prices to configure payment terms for various Stripe features like Checkout and Subscriptions.
- [The Product object | Stripe API Reference](https://docs.stripe.com/api/products/object): This page describes the Stripe Product object, outlining its attributes such as ID, name, description, and status. It details fields like active, metadata, and tax code, which define a product's characteristics.
- [Create a product | Stripe API Reference](https://docs.stripe.com/api/products/create): This page explains how to create a new Stripe Product object. Key parameters include name, active status, description, and optional custom ID or metadata.
- [Update a product | Stripe API Reference](https://docs.stripe.com/api/products/update): This page details how to update an existing Stripe Product object. You can modify parameters like active status, name, description, and metadata, with any omitted parameters remaining unchanged.
- [Retrieve a product | Stripe API Reference](https://docs.stripe.com/api/products/retrieve): This page explains how to retrieve the details of an existing Stripe Product using its unique ID. The API returns the corresponding product information, including its attributes and status.
- [List all products | Stripe API Reference](https://docs.stripe.com/api/products/list): This page describes how to list all of your Stripe products. Results can be filtered by active status and sorted by creation date, with options for pagination.
- [Delete a product | Stripe API Reference](https://docs.stripe.com/api/products/delete): This page details how to delete a Stripe Product. Deletion is only possible if the product has no associated prices or, for 'good' type products, no associated SKUs.
- [Search products | Stripe API Reference](https://docs.stripe.com/api/products/search): This page explains how to search for Stripe products using Stripe's Search Query Language. It allows filtering based on various product attributes and provides options for limiting and paginating results.
- [Prices | Stripe API Reference](https://docs.stripe.com/api/prices): This page introduces Stripe Prices, which define the cost, currency, and billing cycle for products. Prices are used in conjunction with Products to manage payment terms for one-time or recurring purchases.
- [The Price object | Stripe API Reference](https://docs.stripe.com/api/prices/object): This page describes the Stripe Price object, outlining its attributes such as ID, active status, currency, and associated product. It details recurring components, billing schemes, and unit amounts.
- [Create a price | Stripe API Reference](https://docs.stripe.com/api/prices/create): This page explains how to create a new Stripe Price for an existing Product. Prices can be configured as recurring or one-time, with required parameters including currency and either unit amount or recurring details.
- [Update a price | Stripe API Reference](https://docs.stripe.com/api/prices/update): This page details how to update an existing Stripe Price object. You can modify parameters like active status, nickname, and tax behavior, with any omitted parameters remaining unchanged.
- [Retrieve a price | Stripe API Reference](https://docs.stripe.com/api/prices/retrieve): This page explains how to retrieve a specific Stripe Price using its ID. The API returns the price object if a valid ID is provided, otherwise, it raises an error.
- [List all prices | Stripe API Reference](https://docs.stripe.com/api/prices/list): This page describes how to list your Stripe prices. Results can be filtered by active status, currency, product, and type (recurring or one-time), with options for pagination.
- [Search prices | Stripe API Reference](https://docs.stripe.com/api/prices/search): This page explains how to search for Stripe prices using Stripe's Search Query Language. It allows filtering based on various price attributes and provides options for limiting and paginating results.
- [Coupons | Stripe API Reference](https://docs.stripe.com/api/coupons): This page introduces Stripe Coupons, which define percent-off or amount-off discounts applicable to subscriptions, invoices, and other Stripe features. Coupons are not compatible with conventional one-off charges.
- [The Coupon object | Stripe API Reference](https://docs.stripe.com/api/coupons/object): The Coupon object in Stripe represents a discount that can be applied to customer invoices. It can be configured with a fixed amount off or a percentage off, and has options for duration (forever, once, repeating) and currency. Key attributes include its unique ID, name, and redemption details.
- [Create a coupon | Stripe API Reference](https://docs.stripe.com/api/coupons/create): This page details how to create a coupon using the Stripe API, which can be done programmatically or through the Stripe dashboard. Coupons are defined by either a fixed amount off or a percentage off, and can be configured with a specific duration for subscriptions. The creation process requires specifying the discount amount or percentage and currency if applicable.
- [Update a coupon | Stripe API Reference](https://docs.stripe.com/api/coupons/update): This documentation explains how to update a coupon via the Stripe API, noting that core details like currency and duration are not editable. Updates primarily involve modifying the coupon's metadata and its display name. The API endpoint for updating a coupon requires the coupon's ID and accepts new metadata or name values.
- [Retrieve a coupon | Stripe API Reference](https://docs.stripe.com/api/coupons/retrieve): This page describes how to retrieve a specific coupon using its unique ID via the Stripe API. The retrieval process does not require any parameters beyond the coupon's ID. A successful request returns the coupon object, while an invalid ID will result in an error.
- [List all coupons | Stripe API Reference](https://docs.stripe.com/api/coupons/list): This documentation covers listing all available coupons using the Stripe API. The API call can accept parameters to filter the results, such as specifying a starting or ending point, or setting a limit on the number of coupons returned. The response includes a list of coupon objects, each containing details about the coupon.
- [Delete a coupon | Stripe API Reference](https://docs.stripe.com/api/coupons/delete): This page explains how to delete a coupon using the Stripe API. Deleting a coupon prevents new customers from using it but does not affect customers who have already applied it. The API call requires the coupon's ID and returns a confirmation of deletion upon success.
- [Promotion Code | Stripe API Reference](https://docs.stripe.com/api/promotion_codes): A Promotion Code in Stripe is a customer-redeemable code linked to an underlying promotion, allowing for multiple codes per promotion. These codes can be redeemed by customers in the customer portal or via the API. Promotion codes can be restricted by customer, redemption limit, and expiration date.
- [The Promotion Code object | Stripe API Reference](https://docs.stripe.com/api/promotion_codes/object): The Promotion Code object in Stripe represents a customer-facing code that grants access to a promotion. Key attributes include a unique ID, the customer-facing code itself, and details about the associated promotion. It also tracks activation status, redemption limits, and expiration dates.
- [Create a promotion code | Stripe API Reference](https://docs.stripe.com/api/promotion_codes/create): This page details how to create a promotion code using the Stripe API, which can be used to grant discounts or other promotions. A promotion code must be linked to an existing promotion (like a coupon) and can be optionally restricted by customer, redemption limit, and expiration date. The API allows for automatic generation of the code if not provided.
- [Update a promotion code | Stripe API Reference](https://docs.stripe.com/api/promotion_codes/update): This documentation covers updating a promotion code via the Stripe API, primarily allowing modification of its metadata and active status. Most other fields, such as the code itself or the associated promotion, are not editable after creation. The API endpoint requires the promotion code's ID and accepts parameters for fields that can be updated.
- [Retrieve a promotion code | Stripe API Reference](https://docs.stripe.com/api/promotion_codes/retrieve): This page describes how to retrieve a specific promotion code using its unique ID via the Stripe API. To find a promotion code by its customer-facing code, the list API should be used with appropriate filters. A successful retrieval returns the promotion code object, while an invalid ID results in an error.
- [List all promotion codes | Stripe API Reference](https://docs.stripe.com/api/promotion_codes/list): This documentation explains how to list all promotion codes using the Stripe API. The API allows for filtering results by various parameters, including active status, associated coupon, customer, and date ranges. The response provides an array of promotion code objects, each containing details about the code and its restrictions.
- [Discounts | Stripe API Reference](https://docs.stripe.com/api/discounts): A discount in Stripe represents the application of a coupon or promotion code to a customer or subscription. It includes information about the start and end dates of the discount, and its source (coupon or promotion code). Discounts can be applied to customers, subscriptions, invoices, or specific invoice items.
- [The Discount object | Stripe API Reference](https://docs.stripe.com/api/discounts/object): The Discount object in Stripe details the application of a coupon or promotion code. It includes the ID of the associated customer or subscription, the start date, and potentially an end date if the discount is repeating. The source of the discount, whether a coupon or promotion code, is also specified.
- [Delete a customer discount | Stripe API Reference](https://docs.stripe.com/api/discounts/delete): This page explains how to delete a customer discount via the Stripe API. Removing a discount from a customer means they will no longer receive that specific discount on future charges. The API call requires the customer's ID and returns a success confirmation if a discount was present and removed.
- [Delete a subscription discount | Stripe API Reference](https://docs.stripe.com/api/discounts/subscription_delete): This documentation describes how to delete a subscription discount using the Stripe API. This action removes the applied discount from a specific subscription, affecting future charges for that subscription. The API call requires the subscription's ID and confirms the deletion upon successful execution.
- [Tax Code | Stripe API Reference](https://docs.stripe.com/api/tax_codes): Tax codes in Stripe are used to classify goods and services for tax calculation purposes. Each tax code has a unique ID, a name, and a description detailing the types of products it represents. These codes are essential for accurate tax reporting and compliance across different jurisdictions.
- [The Tax Code object | Stripe API Reference](https://docs.stripe.com/api/tax_codes/object): The Tax Code object in Stripe provides details for classifying goods and services for tax purposes. It includes a unique identifier, a name, and a description that specifies the product types the code applies to. This object is used to ensure correct tax calculations and reporting.
- [Retrieve a tax code | Stripe API Reference](https://docs.stripe.com/api/tax_codes/retrieve): This page explains how to retrieve a specific tax code using its unique ID via the Stripe API. Supplying a valid tax code ID returns the corresponding tax code object, which includes its description and name. This function is useful for looking up details about specific tax classifications.
- [List all tax codes | Stripe API Reference](https://docs.stripe.com/api/tax_codes/list): This documentation covers listing all available tax codes in Stripe, which are used for product classification in tax calculations. The API response includes an array of tax code objects, each containing an ID, name, and description. This list is useful for understanding the available tax classifications for products.
- [Tax Rate | Stripe API Reference](https://docs.stripe.com/api/tax_rates): This page details the Stripe API for Tax Rates, outlining how to create, update, retrieve, and list tax rates. It describes the attributes of a Tax Rate object, including its ID, active status, country, display name, and percentage.
- [The Tax Rate object | Stripe API Reference](https://docs.stripe.com/api/tax_rates/object): This page provides a detailed description of the Stripe Tax Rate object, enumerating its attributes such as ID, active status, country, description, display name, inclusivity, jurisdiction, metadata, and percentage. It also lists additional attributes like created timestamp, effective percentage, and tax type.
- [Create a tax rate | Stripe API Reference](https://docs.stripe.com/api/tax_rates/create): This page explains how to create a new tax rate using the Stripe API. It specifies the required parameters: display name, inclusivity, and percentage, along with optional parameters like active status, country, description, jurisdiction, and metadata.
- [Update a tax rate | Stripe API Reference](https://docs.stripe.com/api/tax_rates/update): This page describes how to update an existing tax rate via the Stripe API. It lists parameters that can be modified, including active status, country, description, display name, jurisdiction, and metadata. The endpoint for updating a tax rate is also provided.
- [Retrieve a tax rate | Stripe API Reference](https://docs.stripe.com/api/tax_rates/retrieve): This page covers the Stripe API endpoints for retrieving and listing tax rates. It details how to retrieve a specific tax rate by its ID and how to list all tax rates, with options to filter by active status and sort by creation date. The structure of the returned tax rate objects is also described.
- [List all tax rates | Stripe API Reference](https://docs.stripe.com/api/tax_rates/list): This page details the Stripe API for listing tax rates, explaining how to retrieve a list of existing tax rates. It outlines parameters for filtering and pagination, such as 'active', 'ending_before', 'limit', and 'starting_after'. The response format includes a data property containing an array of tax rate objects.
- [Shipping Rates | Stripe API Reference](https://docs.stripe.com/api/shipping_rates): This page introduces Stripe's Shipping Rates API, which describes the price of shipping presented to customers and applied to purchases. It lists the available endpoints for creating, updating, retrieving, and listing shipping rates, and begins to describe the Shipping Rate object's attributes.
- [The Shipping Rate object | Stripe API Reference](https://docs.stripe.com/api/shipping_rates/object): This page details the Stripe Shipping Rate object, outlining its attributes such as ID, active status, display name, fixed amount, metadata, tax behavior, and type. It also lists additional attributes like creation timestamp and delivery estimate.
- [Create a shipping rate | Stripe API Reference](https://docs.stripe.com/api/shipping_rates/create): This page explains how to create a new shipping rate using the Stripe API. It specifies required parameters like display name and type, along with optional parameters such as fixed amount details, metadata, tax behavior, and tax code. The endpoint and example request for creating a shipping rate are provided.
- [Update a shipping rate | Stripe API Reference](https://docs.stripe.com/api/shipping_rates/update): This page describes how to update an existing shipping rate via the Stripe API. It lists modifiable parameters including active status, fixed amount, metadata, tax behavior, and tax code. The endpoint for updating a shipping rate and an example response are also included.
- [Retrieve a shipping rate | Stripe API Reference](https://docs.stripe.com/api/shipping_rates/retrieve): This page covers the Stripe API endpoints for retrieving and listing shipping rates. It details how to retrieve a specific shipping rate by its ID and how to list all shipping rates with filtering and pagination options. The structure of the returned shipping rate objects is also described.
- [List all shipping rates | Stripe API Reference](https://docs.stripe.com/api/shipping_rates/list): This page details the Stripe API for listing shipping rates, explaining how to retrieve a list of existing shipping rates. It outlines parameters for filtering and pagination, such as 'active', 'created', 'currency', 'ending_before', 'limit', and 'starting_after'. The response format includes a data property containing an array of shipping rate objects.
- [Checkout Sessions | Stripe API Reference](https://docs.stripe.com/api/checkout/sessions): This page introduces the Stripe API for Checkout Sessions, which represent a customer's session during payment for one-time purchases or subscriptions. It outlines endpoints for creating, updating, retrieving, listing, and expiring sessions, and begins to describe the Checkout Session object's attributes.
- [The Checkout Session object | Stripe API Reference](https://docs.stripe.com/api/checkout/sessions/object): This page details the Stripe Checkout Session object, enumerating its attributes such as ID, automatic tax status, client reference ID, currency, customer, customer email, and line items. It also includes details on automatic tax calculation, customer creation, and payment method options.
- [Create a Checkout Session | Stripe API Reference](https://docs.stripe.com/api/checkout/sessions/create): This page explains how to create a Checkout Session using the Stripe API. It details parameters for configuring automatic tax, customer references, customer IDs, line items, metadata, and more. The endpoint and example request for creating a Checkout Session are provided.
- [Update a Checkout Session | Stripe API Reference](https://docs.stripe.com/api/checkout/sessions/update): This page describes how to update a Checkout Session using the Stripe API, focusing on modifying line items, metadata, shipping options, and collected information. It specifies that the entire array of line items must be retransmitted when updating them. The endpoint for updating a Checkout Session is also provided.
- [Retrieve a Checkout Session | Stripe API Reference](https://docs.stripe.com/api/checkout/sessions/retrieve): This page covers the Stripe API endpoints for retrieving a Checkout Session and its line items. It explains how to retrieve a specific Checkout Session by its ID and how to fetch its associated line items, including parameters for pagination. The structure of the returned Checkout Session and line item objects is also described.
- [Retrieve a Checkout Session's line items | Stripe API Reference](https://docs.stripe.com/api/checkout/sessions/line_items): This page details how to retrieve line items associated with a Stripe Checkout Session. It explains that the `line_items` property is includable when retrieving a session and provides a URL to fetch the full, paginated list of line items. Parameters for pagination are also listed.
- [List all Checkout Sessions | Stripe API Reference](https://docs.stripe.com/api/checkout/sessions/list): This page details the Stripe API for listing Checkout Sessions, explaining how to retrieve a list of existing Checkout Sessions. It outlines various parameters for filtering and pagination, such as 'payment_intent', 'subscription', 'customer', 'created', 'ending_before', 'limit', and 'starting_after'. The response format includes a data property containing an array of Checkout Session objects.
- [Expire a Checkout Session | Stripe API Reference](https://docs.stripe.com/api/checkout/sessions/expire): This page explains how to expire an open Stripe Checkout Session using the API. It states that once expired, customers cannot complete the session and will see an expiration message. The endpoint for expiring a Checkout Session and an example response are provided.
- [Payment Link | Stripe API Reference](https://docs.stripe.com/api/payment-link): Stripe's Payment Links API allows you to create shareable URLs that direct customers to a hosted payment page. Each link generates a new checkout session for a customer and can be used multiple times. The API provides endpoints to create, retrieve, update, and list payment links, along with details about the Payment Link object itself.
- [The Payment Link object | Stripe API Reference](https://docs.stripe.com/api/payment-link/object): The Payment Link object in Stripe represents a shareable URL for customer payments. It contains attributes such as a unique ID, active status, line items, metadata, and the public URL. Additional configurations include options for promotions, application fees, tax collection, and customer details.
- [Create a payment link | Stripe API Reference](https://docs.stripe.com/api/payment-link/create): This Stripe API documentation describes how to create a payment link. The process requires specifying line items, which represent the products or services being sold. Optional parameters allow for customization of the post-payment experience, promotion codes, and customer-specific details.
- [Update a payment link | Stripe API Reference](https://docs.stripe.com/api/payment-link/update): The Stripe API allows you to update an existing payment link. You can modify its active status, line items, and metadata. This endpoint enables adjustments to payment link configurations after creation, affecting how customers interact with the payment page.
- [Retrieve a payment link's line items | Stripe API Reference](https://docs.stripe.com/api/payment-link/retrieve-line-items): This Stripe API documentation explains how to retrieve line items associated with a payment link. While the payment link object itself includes a summary of line items, a separate URL is provided to fetch the complete, paginated list. This allows for detailed examination of all items included in a payment link.
- [Retrieve payment link | Stripe API Reference](https://docs.stripe.com/api/payment-link/retrieve): The Stripe API provides an endpoint to retrieve a specific payment link by its ID. This function returns the complete details of the payment link, including its unique identifier, active status, associated line items, and the public URL. It's a key operation for fetching existing payment link configurations.
- [List all payment links | Stripe API Reference](https://docs.stripe.com/api/payment-link/list): This Stripe API documentation covers how to list all payment links. You can filter the results by the active status of the payment links. The response provides an array of payment link objects, allowing you to retrieve and manage multiple payment links efficiently.
- [Credit Balance Summary | Stripe API Reference](https://docs.stripe.com/api/billing/credit-balance-summary): The Stripe Credit Balance Summary object indicates a customer's billing credit balance. It details available and ledger balances across different currencies granted to a customer. This summary is accessible via an API endpoint that retrieves the balance information for a specific customer or account.
- [The Credit Balance Summary object | Stripe API Reference](https://docs.stripe.com/api/billing/credit-balance-summary/object): The Credit Balance Summary object in Stripe details a customer's billing credits, including available and ledger balances per currency. It contains attributes like the object type, balances, customer ID, and live mode status. This object is retrieved using an API call that can filter by customer or account.
- [Retrieve the credit balance summary for a customer | Stripe API Reference](https://docs.stripe.com/api/billing/credit-balance-summary/retrieve): This Stripe API documentation describes how to retrieve the credit balance summary for a customer. The process involves specifying filter criteria, such as the customer ID. The API returns the credit balance summary, providing details on available and ledger balances for that customer.
- [Credit Balance Transaction | Stripe API Reference](https://docs.stripe.com/api/billing/credit-balance-transaction): A Stripe credit balance transaction represents a credit or debit against an existing credit grant. These transactions are linked to specific credit grants and can be of type 'credit' or 'debit'. The API allows retrieval of individual transactions or a list of transactions for a given credit grant or customer.
- [The Credit Balance Transaction object | Stripe API Reference](https://docs.stripe.com/api/billing/credit-balance-transaction/object): The Credit Balance Transaction object in Stripe details a single credit or debit transaction against a credit grant. It includes attributes like ID, type (credit/debit), creation time, and effective time. Debit transactions specify applied credits, while credit transactions detail the granted credits.
- [Retrieve a credit balance transaction | Stripe API Reference](https://docs.stripe.com/api/billing/credit-balance-transaction/retrieve): This Stripe API documentation explains how to retrieve a specific credit balance transaction using its unique ID. The API returns the details of the transaction, including its type, associated credit grant, and any debit or credit information. It's used to inspect individual credit balance movements.
- [List credit balance transactions | Stripe API Reference](https://docs.stripe.com/api/billing/credit-balance-transaction/list): The Stripe API allows you to retrieve a list of credit balance transactions. You can filter these transactions by customer, customer account, or a specific credit grant. The response provides an array of credit balance transaction objects, detailing credits and debits against credit grants.
- [Credit Grant | Stripe API Reference](https://docs.stripe.com/api/billing/credit-grant): A Stripe credit grant is an API resource that documents the allocation of billing credits to a customer. These grants can be purchased or promotional and have associated amounts, categories, and applicability configurations. The API provides endpoints to create, retrieve, update, list, expire, and void credit grants.
- [The Credit Grant object | Stripe API Reference](https://docs.stripe.com/api/billing/credit-grant/object): The Credit Grant object in Stripe represents an allocation of billing credits to a customer. Key attributes include a unique ID, amount, category (paid/promotional), customer ID, and effective/expiration times. It also contains applicability configuration for metered prices and optional metadata.
- [Create a credit grant | Stripe API Reference](https://docs.stripe.com/api/billing/credit-grant/create): This Stripe API documentation details how to create a credit grant. It requires specifying the amount and applicability configuration for the credits, along with the customer ID. Optional parameters include category, effective and expiration times, metadata, name, and priority.
- [Update a credit grant | Stripe API Reference](https://docs.stripe.com/api/billing/credit-grant/update): The Stripe API allows you to update an existing credit grant. You can modify the expiration time of the credits and attach additional metadata. This operation returns the updated credit grant object with the applied changes.
- [Retrieve a credit grant | Stripe API Reference](https://docs.stripe.com/api/billing/credit-grant/retrieve): This Stripe API documentation explains how to retrieve a specific credit grant using its ID. The API returns the details of the credit grant, including its amount, customer, effective and expiration dates, and category. It's used to fetch information about a particular credit allocation.
- [List credit grants | Stripe API Reference](https://docs.stripe.com/api/billing/credit-grant/list): The Stripe API provides an endpoint to list all credit grants. You can filter the results by customer or customer account. The response returns an array of credit grant objects, allowing you to view and manage all credit allocations for your customers.
- [Expire a credit grant | Stripe API Reference](https://docs.stripe.com/api/billing/credit-grant/expire): This page details how to expire a credit grant using the Stripe API. It provides the endpoint POST /v1/billing/credit_grants/:id/expire and describes the request and response objects. Expiring a credit grant effectively invalidates it, preventing its future use.
- [Void a credit grant | Stripe API Reference](https://docs.stripe.com/api/billing/credit-grant/void): This page explains how to void a credit grant via the Stripe API. It specifies the POST /v1/billing/credit_grants/:id/void endpoint and outlines the parameters and response. Voiding a credit grant permanently cancels it.
- [Credit Note | Stripe API Reference](https://docs.stripe.com/api/credit_notes): This page describes the Stripe API's Credit Note object, which is used to adjust an invoice's amount after finalization. It details the attributes of a credit note, including its ID, amount, customer, invoice, line items, reason, and status (issued or void). The page also lists endpoints for creating, updating, retrieving, and voiding credit notes.
- [The Credit Note object | Stripe API Reference](https://docs.stripe.com/api/credit_notes/object): This page provides a detailed schema for the Stripe Credit Note object. It lists all available attributes such as ID, currency, invoice, line items, memo, metadata, reason, and status. The object represents a credit issued to a customer to adjust an invoice amount.
- [Credit Note Line Item | Stripe API Reference](https://docs.stripe.com/api/credit_notes/line_item): This page details the Stripe API's Credit Note Line Item object. It outlines the attributes of individual line items within a credit note, including ID, amount, description, and quantity. This object represents a specific item being credited on a credit note.
- [Create a credit note | Stripe API Reference](https://docs.stripe.com/api/credit_notes/create): This page explains how to create a credit note using the Stripe API to adjust a finalized invoice's amount. It details the parameters required, such as the invoice ID and line items, and describes how the credit note can result in refunds, customer balance credits, or outside-of-Stripe credits. Multiple credit notes can be issued for a single invoice.
- [Update a credit note | Stripe API Reference](https://docs.stripe.com/api/credit_notes/update): This page describes how to update an existing credit note using the Stripe API. It specifies the POST /v1/credit_notes/:id endpoint and details the updatable fields, primarily memo and metadata. The call returns the updated credit note object upon success.
- [Retrieve a credit note | Stripe API Reference](https://docs.stripe.com/api/credit_notes/retrieve): This page details how to retrieve a specific credit note using its identifier via the Stripe API. It provides the GET /v1/credit_notes/:id endpoint and describes the expected response, which is the credit note object itself. It also mentions how to retrieve a paginated list of line items for a credit note preview.
- [Retrieve a credit note preview's line items | Stripe API Reference](https://docs.stripe.com/api/credit_notes/preview_lines): This page explains how to retrieve the line items for a credit note preview using the Stripe API. It specifies the GET /v1/credit_notes/preview/lines endpoint and details the parameters like invoice ID and line item details. This allows for fetching a paginated list of line items associated with a credit note preview.
- [Retrieve a credit note's line items | Stripe API Reference](https://docs.stripe.com/api/credit_notes/lines): This page describes how to retrieve a credit note's line items using the Stripe API. It provides the GET /v1/credit_notes/:id/lines endpoint and explains that a credit note object includes a 'lines' property with a URL to fetch the full, paginated list of line items. It also details parameters for listing credit notes.
- [List all credit notes | Stripe API Reference](https://docs.stripe.com/api/credit_notes/list): This page explains how to list all credit notes using the Stripe API. It provides the GET /v1/credit_notes endpoint and details available parameters for filtering the list, such as by invoice, customer, or date range. The response includes a data property containing an array of credit note objects.
- [Preview a credit note | Stripe API Reference](https://docs.stripe.com/api/credit_notes/preview): This page details how to preview a credit note without creating it using the Stripe API. It provides the GET /v1/credit_notes/preview endpoint and lists the required parameters like invoice ID and line items. The response returns a credit note object representing the preview.
- [Void a credit note | Stripe API Reference](https://docs.stripe.com/api/credit_notes/void): This page explains how to void a credit note using the Stripe API. It specifies the POST /v1/credit_notes/:id/void endpoint and notes that this action marks the credit note as void. The response returns the voided credit note object.
- [Customer Balance Transaction | Stripe API Reference](https://docs.stripe.com/api/customer_balance_transactions): This page introduces Customer Balance Transactions in Stripe, which are used to modify a customer's balance that is automatically applied to their next invoice. It explains that balances can be updated directly or by creating a transaction, and lists the relevant API endpoints. A negative transaction amount credits the customer's balance, while a positive amount debits it.
- [The Customer Balance Transaction object | Stripe API Reference](https://docs.stripe.com/api/customer_balance_transactions/object): This page details the Stripe API's Customer Balance Transaction object, which represents adjustments to a customer's balance. It outlines attributes such as ID, amount, currency, customer, and the resulting ending balance. The object also includes a 'type' attribute indicating the transaction's purpose.
- [Create a customer balance transaction | Stripe API Reference](https://docs.stripe.com/api/customer_balance_transactions/create): This page describes how to create a customer balance transaction using the Stripe API to update a customer's credit balance. It specifies the POST /v1/customers/:id/balance_transactions endpoint and details required parameters like amount and currency. The call returns the created transaction object.
- [Update a customer credit balance transaction | Stripe API Reference](https://docs.stripe.com/api/customer_balance_transactions/update): This page explains how to update a customer balance transaction using the Stripe API. It notes that most fields are immutable, but the description and metadata can be modified via the POST /v1/customers/:id/balance_transactions/:id endpoint. The updated transaction object is returned upon success.
- [Retrieve a customer balance transaction | Stripe API Reference](https://docs.stripe.com/api/customer_balance_transactions/retrieve): This page details how to retrieve a specific customer balance transaction using its ID via the Stripe API. It provides the GET /v1/customers/:id/balance_transactions/:id endpoint and describes the returned customer balance transaction object. It also mentions how to list customer balance transactions.
- [List customer balance transactions | Stripe API Reference](https://docs.stripe.com/api/customer_balance_transactions/list): This page explains how to list customer balance transactions using the Stripe API. It provides the GET /v1/customers/:id/balance_transactions endpoint and details parameters for filtering and pagination. The response returns an array of customer balance transaction objects.
- [Customer Portal Configuration | Stripe API Reference](https://docs.stripe.com/api/customer_portal/configurations): This page describes the Stripe API's Customer Portal Configuration object, which defines the functionality and appearance of a customer portal session. It lists attributes such as ID, active status, business profile details, default return URL, and features. This configuration can be set as the default or overridden when creating a portal session.
- [The Customer portal configuration object | Stripe API Reference](https://docs.stripe.com/api/customer_portal/configurations/object): The Customer portal configuration object defines the settings and features available in the Stripe customer portal. It includes attributes like active status, business profile information, default return URL, and feature enablement for customer updates and invoice history. This object is used to customize the portal's appearance and functionality.
- [Create a portal configuration | Stripe API Reference](https://docs.stripe.com/api/customer_portal/configurations/create): This page details how to create a customer portal configuration using the Stripe API. It outlines the required parameters, such as features, business profile, and default return URL, that define the portal's behavior. The process involves making a POST request to the /v1/billing_portal/configurations endpoint.
- [Update a portal configuration | Stripe API Reference](https://docs.stripe.com/api/customer_portal/configurations/update): The Update a portal configuration API allows modification of existing customer portal configurations. You can change settings like the active status, business profile details, default return URL, and feature enablement. Updates are made by sending a POST request to the specific configuration's endpoint.
- [Retrieve a portal configuration | Stripe API Reference](https://docs.stripe.com/api/customer_portal/configurations/retrieve): This documentation explains how to retrieve a specific customer portal configuration using its ID via the Stripe API. The Retrieve a portal configuration endpoint allows fetching the details of a configuration, including its active status, features, and business information. Additionally, it covers listing all available portal configurations with options to filter by active status or default setting.
- [List portal configurations | Stripe API Reference](https://docs.stripe.com/api/customer_portal/configurations/list): The List portal configurations API endpoint allows retrieval of multiple customer portal configurations. You can filter the results by active status or whether the configuration is the default one. This endpoint provides a way to manage and view all available portal configurations.
- [Customer Portal Session | Stripe API Reference](https://docs.stripe.com/api/customer_portal/sessions): The Customer Portal Session object represents an instance of the Stripe customer portal for a specific customer. It links to a customer and a portal configuration, defining the features available during that session. Sessions are short-lived and are created on-demand when a customer intends to manage their billing and subscriptions.
- [The Customer Portal Session object | Stripe API Reference](https://docs.stripe.com/api/customer_portal/sessions/object): This page describes the attributes of the Customer Portal Session object in the Stripe API. Key details include the session ID, the associated customer and configuration IDs, creation timestamp, and live mode status. It also mentions optional fields like locale and on-behalf-of for Connect applications.
- [Create a portal session | Stripe API Reference](https://docs.stripe.com/api/customer_portal/sessions/create): The Create a portal session API allows generating a unique, short-lived URL for a customer to access the Stripe customer portal. You must provide a customer ID and can optionally specify a configuration ID, return URL, locale, or flow data. The response includes the session details and the URL to access the portal.
- [Invoices | Stripe API Reference](https://docs.stripe.com/api/invoices): Invoices in Stripe are statements of amounts owed by customers, generated either one-off or from subscriptions. They include invoice items and proration adjustments, and can be automatically finalized and paid by Stripe or emailed to the customer. Stripe applies customer credits before determining the final amount due.
- [The Invoice object | Stripe API Reference](https://docs.stripe.com/api/invoices/object): The Invoice object in Stripe represents a statement of amounts owed by a customer. It details charges, payment collection methods (automatic or manual via email), currency, customer information, and status. The object also includes subtotal and total amounts, and information about the next payment attempt.
- [Create a preview invoice | Stripe API Reference](https://docs.stripe.com/api/invoices/create_preview): This API endpoint allows you to preview an upcoming invoice for a subscription or subscription schedule without creating it. It shows pending charges, renewal fees, and applicable discounts. You can also preview the effects of creating or updating subscriptions, including prorations, but these previews cannot be paid or edited.
- [Create an invoice | Stripe API Reference](https://docs.stripe.com/api/invoices/create): The Create an invoice API endpoint allows you to create a draft invoice for a customer. The invoice remains a draft until finalized, after which it can be paid or sent. You can specify parameters like collection method, customer ID, and automatic tax settings. The `auto_advance` parameter controls whether Stripe automatically collects payment.
- [Update an invoice | Stripe API Reference](https://docs.stripe.com/api/invoices/update): The Update an invoice API allows editing draft invoices, but monetary values and collection methods become uneditable once finalized. You can modify parameters like `auto_advance`, `collection_method`, description, and metadata. Updates to finalized invoices are restricted, and draft invoices must be finalized before certain actions can be taken.
- [Retrieve an invoice | Stripe API Reference](https://docs.stripe.com/api/invoices/retrieve): The Retrieve an invoice API allows fetching a specific invoice by its ID. The returned invoice object contains detailed information, including line items, subscription details, prorations, subtotal, total, and the next payment attempt. It provides a comprehensive view of the invoice's financial details.
- [List all invoices | Stripe API Reference](https://docs.stripe.com/api/invoices/list): The List all invoices API endpoint allows retrieval of all invoices or invoices for a specific customer. Invoices are returned sorted by creation date, with options to filter by customer, status, or subscription. Parameters like `limit` and `ending_before` can be used for pagination.
- [Delete a draft invoice | Stripe API Reference](https://docs.stripe.com/api/invoices/delete): The Delete a draft invoice API permanently removes a one-off invoice draft that has not yet been finalized. This action cannot be undone. Invoices that are no longer in a draft state, or are associated with subscriptions, cannot be deleted and must be voided instead.
- [Attach a payment to an Invoice | Stripe API Reference](https://docs.stripe.com/api/invoices/attach_payment): The Attach a payment to an Invoice API allows associating a PaymentIntent or Out of Band Payment with an invoice. When the PaymentIntent succeeds, the payment is credited to the invoice, increasing the `amount_paid`. This process updates the invoice's status once it is fully paid.
- [Finalize an invoice | Stripe API Reference](https://docs.stripe.com/api/invoices/finalize): The Finalize an invoice API allows you to manually finalize a draft invoice, changing its status to 'open'. Stripe typically finalizes invoices automatically before attempting payment. This endpoint can also control whether Stripe automatically advances the invoice's collection state using the `auto_advance` parameter.
- [Mark an invoice as uncollectible | Stripe API Reference](https://docs.stripe.com/api/invoices/mark_uncollectible): Marking an invoice as uncollectible is used for accounting purposes to track bad debts. This action changes the invoice's status to uncollectible, indicating it will not be paid. The API call returns the updated invoice object.
- [Pay an invoice | Stripe API Reference](https://docs.stripe.com/api/invoices/pay): The Pay an invoice API allows you to manually attempt payment collection for an invoice outside the normal schedule. This is useful for various scenarios where immediate payment processing is needed. The API call returns the updated invoice object after the payment attempt.
- [Search invoices | Stripe API Reference](https://docs.stripe.com/api/invoices/search): The Stripe API allows searching for invoices using the Search Query Language. You can specify parameters like 'query', 'limit', and 'page' to filter and paginate results. The API returns a dictionary containing an array of invoice objects that match the search criteria.
- [Send an invoice for manual payment | Stripe API Reference](https://docs.stripe.com/api/invoices/send): This Stripe API endpoint enables manually sending an invoice to a customer outside of the regular subscription schedule. When sending an invoice that has already been paid, the payment will not be referenced in the email. In test mode, no emails are sent.
- [Void an invoice | Stripe API Reference](https://docs.stripe.com/api/invoices/void): This Stripe API endpoint allows marking a finalized invoice as void, which is an irreversible action. Voiding an invoice is similar to deletion but maintains a record for auditing purposes. It's recommended to consult local regulations and legal counsel regarding invoice amendments, cancellations, or voiding.
- [Invoice Items | Stripe API Reference](https://docs.stripe.com/api/invoiceitems): Invoice Items represent individual lines on an invoice and can be created before an invoice is sent, useful for batching charges or credits. They can be attached to a specific invoice or will be added to the next invoice created for a customer. This API covers creating, updating, retrieving, listing, and deleting invoice items.
- [The Invoice Item object | Stripe API Reference](https://docs.stripe.com/api/invoiceitems/object): The Invoice Item object in the Stripe API details attributes such as ID, amount, currency, customer, description, and metadata. It also includes information about the parent object, the period it covers, and pricing details. Additional attributes like quantity and tax rates are also part of this object.
- [Create an invoice item | Stripe API Reference](https://docs.stripe.com/api/invoiceitems/create): This Stripe API endpoint creates an invoice item that can be added to a draft invoice or the next invoice for a customer. You can specify the amount, currency, customer, and description for the item. Optional parameters include metadata and a period for the item.
- [Update an invoice item | Stripe API Reference](https://docs.stripe.com/api/invoiceitems/update): The Stripe API allows updating an invoice item's amount or description, but only before the associated invoice is closed. This endpoint can also update metadata and the period for the invoice item. Updates to fields like 'amount' on the invoice line item will propagate to the invoice item.
- [Retrieve an invoice item | Stripe API Reference](https://docs.stripe.com/api/invoiceitems/retrieve): This Stripe API endpoint retrieves a specific invoice item using its ID. If a valid ID is provided, it returns the invoice item object; otherwise, it raises an error. The response includes details like amount, currency, customer, and description.
- [List all invoice items | Stripe API Reference](https://docs.stripe.com/api/invoiceitems/list): The Stripe API provides an endpoint to list all invoice items, sorted by creation date. You can filter these items by customer or customer account, and use parameters like 'limit', 'ending_before', and 'starting_after' for pagination. The response includes a data property containing an array of invoice item objects.
- [Delete an invoice item | Stripe API Reference](https://docs.stripe.com/api/invoiceitems/delete): This Stripe API endpoint deletes an invoice item, removing it from an invoice. Deletion is only permitted if the invoice item is not attached to a finalized invoice or if it's attached to a draft invoice. The response confirms the deletion with the item's ID and a 'deleted' flag.
- [Invoice Line Item | Stripe API Reference](https://docs.stripe.com/api/invoice-line-item): Invoice Line Items represent the individual lines within an invoice and are backed by either invoice items or subscription items. They exist only within the context of an invoice. The API provides endpoints for updating, retrieving, and performing bulk operations (add, remove, update) on invoice line items.
- [The Invoice Line Item object | Stripe API Reference](https://docs.stripe.com/api/invoice-line-item/object): The Invoice Line Item object in the Stripe API details attributes like ID, amount, currency, and description. It includes the associated invoice ID, metadata, and parent object information. The period covered by the line item and pricing details are also provided.
- [Update an invoice's line item | Stripe API Reference](https://docs.stripe.com/api/invoice-line-item/update): This Stripe API endpoint allows updating an invoice's line item, which is only possible before the invoice is finalized. Fields like tax amounts can only be updated here, while others like 'amount' will propagate to the associated invoice item. Parameters include the invoice ID, line item ID, and optional fields like description and metadata.
- [Retrieve an invoice's line items | Stripe API Reference](https://docs.stripe.com/api/invoice-line-item/retrieve): When retrieving an invoice, the 'lines' property provides a count and a sample of line items. To get the full list, a separate URL is provided for paginated retrieval. This endpoint allows fetching all line items associated with a specific invoice.
- [Bulk add invoice line items | Stripe API Reference](https://docs.stripe.com/api/invoice-line-item/bulk): This Stripe API endpoint adds multiple line items to a draft invoice. You can specify the line items to add, including their amount and description, or reference existing invoice items. The updated invoice with the added line items is returned upon success.
- [Bulk remove invoice line items | Stripe API Reference](https://docs.stripe.com/api/invoice-line-item/invoices/remove-lines/bulk): The Stripe API allows removing multiple line items from a draft invoice. You specify the line items to remove by their ID and can choose a 'delete' or 'unassign' behavior. The updated invoice, without the removed line items, is returned upon successful execution.
- [Bulk update invoice line items | Stripe API Reference](https://docs.stripe.com/api/invoice-line-item/invoices/update-lines/bulk): This Stripe API endpoint updates multiple line items on a draft invoice. You can modify fields such as the description for each line item. For subscription-based line items, incoming metadata directly sets the value, while for invoice items, it merges with existing metadata.
- [Invoice Payment | Stripe API Reference](https://docs.stripe.com/api/invoice-payment): Invoice Payments represent payments made against invoices and can be accessed by expanding the 'payments' field on an Invoice resource or using dedicated retrieve and list endpoints. This resource maps payment objects like Payment Intents to invoices, allowing tracking of payment associations and allocation details.
- [The Invoice Payment object | Stripe API Reference](https://docs.stripe.com/api/invoice-payment/object): The Invoice Payment object in the Stripe API includes attributes like ID, amount paid, amount requested, and the associated invoice. It also details the payment type (e.g., Payment Intent) and the payment status (open, paid, canceled). Stripe automatically creates a default InvoicePayment when an invoice is finalized.
- [Retrieve an InvoicePayment | Stripe API Reference](https://docs.stripe.com/api/invoice-payment/retrieve): This Stripe API endpoint retrieves a specific invoice payment using its ID. If a valid ID is provided, it returns the invoice payment object, including details like amount paid, requested amount, currency, and status. Otherwise, an error is raised.
- [List all payments for an invoice | Stripe API Reference](https://docs.stripe.com/api/invoice-payment/list): This page details how to list all payments associated with a specific invoice using the Stripe API. It explains the available parameters for filtering payments by status and provides an example of the API request and response structure.
- [Invoice Rendering Templates | Stripe API Reference](https://docs.stripe.com/api/invoice-rendering-template): This page introduces Invoice Rendering Templates, which are used to configure how invoices appear in formats like PDFs. Templates can be created via the Stripe Dashboard or the API, and this section outlines the available endpoints for managing them.
- [The Invoice Rendering Template object | Stripe API Reference](https://docs.stripe.com/api/invoice-rendering-template/object): This page describes the attributes of the Stripe Invoice Rendering Template object. It covers details such as the template's ID, creation timestamp, live mode status, nickname, and current status (active or archived).
- [Retrieve an invoice rendering template | Stripe API Reference](https://docs.stripe.com/api/invoice-rendering-template/retrieve): This page explains how to retrieve a specific invoice rendering template by its ID using the Stripe API. It also mentions the possibility of retrieving older versions of a template and provides an example of the API call and its response.
- [List all invoice rendering templates | Stripe API Reference](https://docs.stripe.com/api/invoice-rendering-template/list): This page details how to list all available invoice rendering templates via the Stripe API. It explains that templates are listed in order of creation date and provides parameters for pagination and filtering, along with an example API response.
- [Archive an invoice rendering template | Stripe API Reference](https://docs.stripe.com/api/invoice-rendering-template/archive): This page describes how to archive an invoice rendering template using the Stripe API. Archiving a template prevents it from being referenced by new Stripe objects and stops further updates, though it remains active on existing objects.
- [Unarchive an invoice rendering template | Stripe API Reference](https://docs.stripe.com/api/invoice-rendering-template/unarchive): This page explains how to unarchive an invoice rendering template using the Stripe API. Unarchiving a template allows it to be referenced by new Stripe objects again. It provides the API endpoint and an example response.
- [Meters | Stripe API Reference](https://docs.stripe.com/api/billing/meter): This page introduces Stripe's Meters, which are used to aggregate meter events over a billing period for usage-based billing. Meters are attached to prices and define how customer actions (meter events) are aggregated into billable charges. It lists the available API endpoints for managing meters.
- [The Meter object | Stripe API Reference](https://docs.stripe.com/api/billing/meter/object): This page details the attributes of the Stripe Meter object, which is used for usage-based billing. It includes information on the meter's ID, display name, event name, aggregation settings, status (active/inactive), and how meter events are mapped to customers.
- [Create a billing meter | Stripe API Reference](https://docs.stripe.com/api/billing/meter/create): This page explains how to create a new billing meter using the Stripe API. It outlines the required parameters such as display name, event name, and default aggregation settings, and provides an example API request and the resulting meter object.
- [Update a billing meter | Stripe API Reference](https://docs.stripe.com/api/billing/meter/update): This page describes how to update an existing billing meter via the Stripe API. It details the parameters that can be modified, such as the display name, and provides an example API request and the updated meter object in the response.
- [Retrieve a billing meter | Stripe API Reference](https://docs.stripe.com/api/billing/meter/retrieve): This page explains how to retrieve a specific billing meter by its ID using the Stripe API. It provides the API endpoint and an example of the request and the returned meter object, including its configuration and status.
- [List billing meters | Stripe API Reference](https://docs.stripe.com/api/billing/meter/list): This page details how to list all billing meters using the Stripe API. It explains that results can be filtered by status and provides parameters for pagination. An example API response containing a list of meter objects is included.
- [Deactivate a billing meter | Stripe API Reference](https://docs.stripe.com/api/billing/meter/deactivate): This page describes how to deactivate a billing meter using the Stripe API. Deactivating a meter prevents it from accepting new events and from being attached to a price. The API endpoint and an example response are provided.
- [Reactivate a billing meter | Stripe API Reference](https://docs.stripe.com/api/billing/meter/reactivate): This page explains how to reactivate a billing meter using the Stripe API. Reactivating a meter allows it to accept new events and be attached to a price. The API endpoint and an example response are shown.
- [Meter Events | Stripe API Reference](https://docs.stripe.com/api/billing/meter-event): This page introduces Stripe's Meter Events, which represent customer actions used for usage-based billing. Meter events are linked to billing meters that define how these actions are aggregated into charges. It outlines the API endpoint for creating meter events.
- [The Meter Event object | Stripe API Reference](https://docs.stripe.com/api/billing/meter-event/object): This page details the attributes of the Stripe Meter Event object. It includes information such as the event's name, a unique identifier, payload data, and timestamp, which are used to track customer usage for billing purposes.
- [Create a billing meter event | Stripe API Reference](https://docs.stripe.com/api/billing/meter-event/create): This page explains how to create a billing meter event using the Stripe API. It specifies the required parameters like event name and payload, and an optional unique identifier and timestamp. An example API request and response are provided.
- [Meter Event Adjustment | Stripe API Reference](https://docs.stripe.com/api/billing/meter-event-adjustment): This page introduces the Stripe Meter Event Adjustment resource, which allows for the cancellation of previously created meter events. It explains the purpose of adjustments, such as correcting errors, and details the available API endpoint.
- [The Meter Event Adjustment object | Stripe API Reference](https://docs.stripe.com/api/billing/meter-event-adjustment/object): This page describes the attributes of the Stripe Meter Event Adjustment object. It includes the adjustment's status (complete or pending), the type of adjustment (e.g., cancel), and details about the event being adjusted.
- [Create a billing meter event adjustment | Stripe API Reference](https://docs.stripe.com/api/billing/meter-event-adjustment/create): This page describes how to create a billing meter event adjustment using the Stripe API. It details the parameters required, such as event name and type, and provides an example of the API request and response.
- [Meter Event Adjustments | Stripe API Reference](https://docs.stripe.com/api/v2/billing/meter-event-adjustments): This page details the Meter Event Adjustments resource in Stripe API v2, explaining its purpose for canceling meter events. It outlines the available attributes of the Meter Event Adjustment object and lists the relevant API endpoint for managing these adjustments.
- [The Meter Event Adjustment object | Stripe API Reference](https://docs.stripe.com/api/v2/billing/meter-event-adjustments/object): This page describes the Meter Event Adjustment object in Stripe API v2, detailing its attributes like ID, creation timestamp, event name, and status. It also includes information on how to create a Meter Event Adjustment to cancel a previously sent meter event.
- [Create a Meter Event Adjustment | Stripe API Reference](https://docs.stripe.com/api/v2/billing/meter-event-adjustments/create): This page explains how to create a meter event adjustment using Stripe API v2 to cancel a previously sent meter event. It lists the required parameters, such as the cancellation details and event name, and outlines the response attributes.
- [Meter Event Streams | Stripe API Reference](https://docs.stripe.com/api/v2/meter-event-streams): This page introduces Stripe's Meter Event Streams for higher-throughput meter event submission. It explains the need to create a meter event session with a short-lived token for authentication when using the meter event stream endpoint.
- [The Meter Event Session object | Stripe API Reference](https://docs.stripe.com/api/v2/meter-event-streams/meter-event-sessions/object): This page details the Meter Event Session object in Stripe API v2, which is used for authenticating high-throughput meter event submissions. It lists the object's attributes, including the session ID, authentication token, and expiration time, and provides an example of the object's structure.
- [Create a Meter Event Stream Authentication Session | Stripe API Reference](https://docs.stripe.com/api/v2/meter-event-streams/meter-event-sessions/create): This page describes how to create a meter event session for the high-throughput meter event stream in Stripe API v2. It notes that authentication tokens are valid for 15 minutes and provides the API endpoint and example response for creating a session.
- [Create a Meter Event with asynchronous validation | Stripe API Reference](https://docs.stripe.com/api/v2/billing/meter-event-sessions/create-async): This page explains how to create meter events using Stripe API v2 with asynchronous validation, which is suitable for high-throughput scenarios. It requires a meter event session for authentication and supports up to 10,000 requests per second in live mode.
- [Meter Event Summary | Stripe API Reference](https://docs.stripe.com/api/billing/meter-event-summary): This page describes the Stripe Meter Event Summary, which provides an aggregated view of a customer's billing meter events over a specific timeframe. It notes that summaries are eventually consistent due to asynchronous aggregation and details the attributes of the Meter Event Summary object.
- [The Meter Event Summary object | Stripe API Reference](https://docs.stripe.com/api/billing/meter-event-summary/object): This page details the attributes of the Meter Event Summary object in Stripe, including its ID, aggregated value, and timestamps. It also explains how to retrieve a list of meter event summaries for a customer within a specified time range.
- [List billing meter event summaries | Stripe API Reference](https://docs.stripe.com/api/billing/meter-event-summary/list): This page explains how to retrieve a list of billing meter event summaries in Stripe, detailing the required parameters such as customer ID, start, and end times. It also outlines optional parameters for filtering and grouping the summaries by hour or day.
- [Meter Events | Stripe API Reference](https://docs.stripe.com/api/v2/meter-events): This page describes Stripe's Meter Events, which are used to report customer usage associated with billing meters. It explains that meter events are processed asynchronously and details the attributes of the Meter Event object, including its name, identifier, payload, and timestamp.
- [The Meter Event object | Stripe API Reference](https://docs.stripe.com/api/v2/billing/meter-events/object): This page details the Meter Event object in Stripe API v2, outlining its attributes such as object type, creation timestamp, event name, identifier, live mode status, payload, and event time. It also provides an example of the Meter Event object's structure.
- [Create a Meter Event with synchronous validation | Stripe API Reference](https://docs.stripe.com/api/v2/billing/meter-events/create): This page explains how to create a meter event with synchronous validation in Stripe API v2, noting that events are processed asynchronously. It lists the required parameters, including event name and payload, and specifies the API endpoint for this operation.
- [Plans | Stripe API Reference](https://docs.stripe.com/api/plans): This page introduces Stripe's Plans API, which defines recurring pricing for products, and notes its replacement by the Prices API. It explains that plans specify the base price, currency, and billing cycle, and provides examples of how products and plans can be structured.
- [The Plan object | Stripe API Reference](https://docs.stripe.com/api/plans/object): This page details the attributes of the Stripe Plan object, including its ID, active status, amount, currency, and interval. It also lists additional attributes like nickname, product association, and usage type, and provides an example of a Plan object.
- [Create a plan | Stripe API Reference](https://docs.stripe.com/api/plans/create): This page explains how to create a new plan in Stripe, noting that the Prices API is now recommended for more flexible subscription modeling. It lists the required parameters such as currency, interval, and product, along with optional parameters for customization.
- [Update a plan | Stripe API Reference](https://docs.stripe.com/api/plans/update): This page describes how to update an existing plan in Stripe, specifying that parameters like ID, amount, currency, and billing cycle cannot be changed. It outlines the available parameters for updating a plan, such as active status, metadata, and nickname.
- [Retrieve a plan | Stripe API Reference](https://docs.stripe.com/api/plans/retrieve): This page explains how to retrieve a specific plan using its ID in Stripe. It states that a valid plan ID must be provided for the retrieval to succeed, otherwise an error will be raised.
- [List all plans | Stripe API Reference](https://docs.stripe.com/api/plans/list): This page details how to list all plans in Stripe, including optional parameters to filter by active status or product. It specifies the API endpoint and provides an example of the response, which includes a list of plan objects.
- [Delete a plan | Stripe API Reference](https://docs.stripe.com/api/plans/delete): This page details how to delete a plan in Stripe. Deleting a plan prevents new subscribers from being added, but existing subscribers are unaffected. The API call returns the deleted plan's ID and a deleted flag upon success.
- [Quote | Stripe API Reference](https://docs.stripe.com/api/quotes): This page introduces Stripe's Quote object, which models prices for customers. Once accepted, a quote automatically creates an invoice, subscription, or subscription schedule. It outlines various endpoints for managing quotes, including creation, retrieval, acceptance, and cancellation.
- [The Quote object | Stripe API Reference](https://docs.stripe.com/api/quotes/object): This page provides a detailed description of the Stripe Quote object's attributes. It covers essential fields such as ID, line items, metadata, amounts, customer information, status, and timestamps. The page also includes an example JSON response for a quote object.
- [Create a quote | Stripe API Reference](https://docs.stripe.com/api/quotes/create): This page explains how to create a quote in Stripe, which models prices and services for a customer. It details the required `line_items` parameter and other optional parameters like `metadata`, `expires_at`, and `description`. The page also provides an example API request and response for creating a quote.
- [Update a quote | Stripe API Reference](https://docs.stripe.com/api/quotes/update): This page describes how to update an existing quote in Stripe. It allows modification of parameters such as line items and metadata. The API call returns the updated quote object.
- [Retrieve a quote | Stripe API Reference](https://docs.stripe.com/api/quotes/retrieve): This page details how to retrieve a specific quote in Stripe using its ID. It explains that the API returns the quote object if a valid ID is provided, otherwise it raises an error. The page also mentions that line items can be included when retrieving a quote.
- [Retrieve a quote's line items | Stripe API Reference](https://docs.stripe.com/api/quotes/line_items/list): This page explains how to retrieve the line items associated with a Stripe quote. It notes that a limited number of line items are included by default, but a separate URL allows retrieval of the full, paginated list. The API returns an array of line item objects.
- [Retrieve a quote's upfront line items | Stripe API Reference](https://docs.stripe.com/api/quotes/line_items/upfront/list): This page describes how to retrieve the upfront line items for a Stripe quote. It mentions an includable `computed.upfront.line_items` property and provides a URL for fetching the full, paginated list. The API returns an array of upfront line item objects.
- [List all quotes | Stripe API Reference](https://docs.stripe.com/api/quotes/list): This page explains how to list all quotes in Stripe, with options to filter by customer, customer account, or status. By default, it returns active quotes, but canceled or ended subscriptions can also be retrieved. The API response includes a list of quote objects.
- [Accept a quote | Stripe API Reference](https://docs.stripe.com/api/quotes/accept): This page details how to accept a quote in Stripe, which creates an invoice, subscription, or subscription schedule. The API call returns the accepted quote object with an updated status. It also covers how to cancel a quote, returning a canceled quote object.
- [Cancel a quote | Stripe API Reference](https://docs.stripe.com/api/quotes/cancel): This page explains how to cancel a quote in Stripe, returning a canceled quote object with an updated status. It also covers downloading the PDF for a finalized quote and finalizing an open quote. The finalize action can optionally update the expiration timestamp.
- [Download quote PDF | Stripe API Reference](https://docs.stripe.com/api/quotes/pdf): This page describes how to download the PDF for a finalized Stripe quote. It also covers how to finalize an open quote, which can optionally update the expiration timestamp. The finalize action returns the quote object with an updated status.
- [Finalize a quote | Stripe API Reference](https://docs.stripe.com/api/quotes/finalize): This page explains how to finalize a quote in Stripe, returning an open quote object with an updated status. It also covers downloading the PDF for a finalized quote and canceling a quote. The finalize action can optionally update the expiration timestamp.
- [Subscriptions | Stripe API Reference](https://docs.stripe.com/api/subscriptions): This page introduces Stripe Subscriptions, which allow charging customers on a recurring basis. It outlines the available API endpoints for managing subscriptions, including creating, updating, retrieving, listing, and canceling them. The page also describes the core attributes of the Subscription object.
- [The Subscription object | Stripe API Reference](https://docs.stripe.com/api/subscriptions/object): This page provides a detailed description of the Stripe Subscription object's attributes. It covers key fields such as ID, currency, customer, default payment method, items, and metadata. The page also includes an example JSON response for a subscription object.
- [Create a subscription | Stripe API Reference](https://docs.stripe.com/api/subscriptions/create): This page explains how to create a new subscription for an existing customer in Stripe. It highlights that customers can have up to 500 subscriptions and details parameters like `customer`, `currency`, and `items`. The API call finalizes the first invoice upon creation if `collection_method` is set to `charge_automatically`.
- [Update a subscription | Stripe API Reference](https://docs.stripe.com/api/subscriptions/update): This page describes how to update an existing subscription in Stripe, with options to prorate price changes for the next billing cycle. It explains how proration works for upgrades and downgrades, and when billing dates might change. The API returns the updated subscription object.
- [Retrieve a subscription | Stripe API Reference](https://docs.stripe.com/api/subscriptions/retrieve): This page details how to retrieve a specific subscription in Stripe using its ID. The API call returns the subscription object, including details about its items, billing cycle, and customer. It also mentions related endpoints for listing, creating, updating, and canceling subscriptions.
- [List subscriptions | Stripe API Reference](https://docs.stripe.com/api/subscriptions/list): This page explains how to list subscriptions in Stripe, with options to filter by customer, price, or status. It can return active, canceled, or ended subscriptions. The API response includes a list of subscription objects and details about pagination.
- [Cancel a subscription | Stripe API Reference](https://docs.stripe.com/api/subscriptions/cancel): This page describes how to cancel a customer's subscription in Stripe immediately. Upon cancellation, the customer is no longer charged and the subscription cannot be updated. It details parameters for handling pending invoices and prorations, and the API returns the canceled Subscription object.
- [Migrate a subscription | Stripe API Reference](https://docs.stripe.com/api/subscriptions/migrate): This page details how to migrate an existing Stripe subscription to a different billing mode, such as flexible or per_unit. It outlines the API endpoint and parameters required to perform this migration, along with a response example.
- [Resume a subscription | Stripe API Reference](https://docs.stripe.com/api/subscriptions/resume): This page explains how to resume a paused Stripe subscription. It covers the API parameters for optionally resetting the billing cycle anchor and handling prorations. The process can result in an immediate activation or require invoice payment depending on proration settings.
- [Search subscriptions | Stripe API Reference](https://docs.stripe.com/api/subscriptions/search): This page describes how to search for Stripe subscriptions using Stripe's Search Query Language. It provides the API endpoint and parameters like 'query', 'limit', and 'page' for efficient searching. The content also notes that search functionality is not available to merchants in India and that data may take up to an hour to become searchable.
- [Subscription Items | Stripe API Reference](https://docs.stripe.com/api/subscription_items): This page introduces Stripe's subscription items, which allow for multiple plans within a single customer subscription to manage complex billing relationships. It lists the available API endpoints for creating, retrieving, updating, and deleting subscription items. The page also details the attributes of the Subscription Item object.
- [The Subscription Item object | Stripe API Reference](https://docs.stripe.com/api/subscription_items/object): This page provides a detailed description of the Stripe Subscription Item object, outlining its attributes such as ID, metadata, price, and quantity. It explains how subscription items enable multiple plans per subscription and details the parameters for creating a new subscription item.
- [Create a subscription item | Stripe API Reference](https://docs.stripe.com/api/subscription_items/create): This page explains how to add a new item to an existing Stripe subscription using the 'Create a subscription item' API. It details the required 'subscription' parameter and optional parameters like 'metadata' and 'payment_behavior'. The process does not alter existing items on the subscription.
- [Update a subscription item | Stripe API Reference](https://docs.stripe.com/api/subscription_items/update): This page describes how to update a subscription item on a Stripe subscription, allowing changes to the plan or quantity. It details the available parameters, including metadata and payment behavior options, and explains how these updates affect the subscription's billing status.
- [Retrieve a subscription item | Stripe API Reference](https://docs.stripe.com/api/subscription_items/retrieve): This page covers the retrieval of a specific subscription item by its ID using the Stripe API. It also details how to list all subscription items associated with a given subscription, including parameters for pagination and filtering.
- [List all subscription items | Stripe API Reference](https://docs.stripe.com/api/subscription_items/list): This page explains how to retrieve a list of all subscription items for a specific Stripe subscription. It details the required 'subscription' parameter and optional parameters for pagination, such as 'limit', 'ending_before', and 'starting_after'. The response format includes an array of subscription item objects.
- [Delete a subscription item | Stripe API Reference](https://docs.stripe.com/api/subscription_items/delete): This page details the process of deleting a subscription item from a Stripe subscription. It clarifies that removing an item does not cancel the entire subscription and outlines the 'payment_behavior' parameter options for handling potential invoice issues.
- [Subscription Schedule | Stripe API Reference](https://docs.stripe.com/api/subscription_schedules): This page introduces Stripe's Subscription Schedule object, which allows for predefined changes to a subscription's lifecycle. It lists the API endpoints for creating, updating, retrieving, listing, canceling, and releasing schedules. The page also describes the attributes of the Subscription Schedule object, including its status and phases.
- [The Subscription Schedule object | Stripe API Reference](https://docs.stripe.com/api/subscription_schedules/object): This page provides a comprehensive overview of the Stripe Subscription Schedule object, detailing its attributes like ID, customer, phases, and status. It explains how subscription schedules manage the lifecycle of subscriptions with predefined changes and lists the parameters for creating a new schedule.
- [Create a schedule | Stripe API Reference](https://docs.stripe.com/api/subscription_schedules/create): This page explains how to create a new subscription schedule in Stripe, which allows for managing a subscription's lifecycle with predefined changes. It details the required 'customer' parameter and optional parameters like 'metadata', 'phases', and 'start_date'. The API allows up to 500 active or scheduled subscriptions per customer.
- [Update a schedule | Stripe API Reference](https://docs.stripe.com/api/subscription_schedules/update): This page describes how to update an existing Stripe subscription schedule. It details parameters such as metadata and phases, and importantly, the 'proration_behavior' which dictates how changes to the billing configuration are handled. The API returns the updated subscription schedule object upon success.
- [Retrieve a schedule | Stripe API Reference](https://docs.stripe.com/api/subscription_schedules/retrieve): This page explains how to retrieve the details of an existing Stripe subscription schedule using its unique identifier. It outlines the API endpoint and notes that no additional parameters are required beyond the schedule ID. The response includes the full subscription schedule object if the ID is valid.
- [List all schedules | Stripe API Reference](https://docs.stripe.com/api/subscription_schedules/list): This page details how to list Stripe subscription schedules, with options to filter by customer. It specifies the API endpoint and available parameters for pagination and filtering, such as 'limit', 'ending_before', and 'starting_after'. The response contains an array of subscription schedule objects.
- [Cancel a schedule | Stripe API Reference](https://docs.stripe.com/api/subscription_schedules/cancel): This page explains how to cancel a Stripe subscription schedule and its associated active subscription. It details the API endpoint and parameters like 'invoice_now' and 'prorate' to control final invoicing and prorations. The status of the canceled schedule becomes 'canceled', and 'canceled_at' is set.
- [Release a schedule | Stripe API Reference](https://docs.stripe.com/api/subscription_schedules/release): This page describes how to release a Stripe subscription schedule, which immediately stops future phase scheduling but leaves the existing subscription active. It details the API endpoint and the 'preserve_cancel_date' parameter. The released schedule's status becomes 'released', and it will no longer be associated with the subscription.
- [Tax IDs | Stripe API Reference](https://docs.stripe.com/api/tax_ids): This page details Stripe's Tax ID functionality, allowing the addition of tax identification numbers to customers or accounts. These IDs are displayed on related invoices and credit notes. The page lists the API endpoints for creating, retrieving, listing, and deleting tax IDs.
- [The Tax ID object | Stripe API Reference](https://docs.stripe.com/api/tax_ids/object): This page provides a detailed description of the Stripe Tax ID object, outlining its attributes such as ID, country, type, and value. It explains the various types of tax IDs supported and lists additional attributes like creation timestamp and owner information.
- [Create a Customer tax ID | Stripe API Reference](https://docs.stripe.com/api/tax_ids/customer_create): This page details how to create a tax ID for a customer using the Stripe API. It outlines the required parameters, such as the type and value of the tax ID, and provides an example of the API request and response.
- [Create a tax ID | Stripe API Reference](https://docs.stripe.com/api/tax_ids/create): This page explains how to create a tax ID object for either an account or a customer via the Stripe API. It lists the various types of tax IDs supported and shows the structure of the API request and the resulting tax ID object.
- [Retrieve a Customer tax ID | Stripe API Reference](https://docs.stripe.com/api/tax_ids/customer_retrieve): This page describes how to retrieve a specific customer's tax ID using its identifier via the Stripe API. It details the API endpoint and provides an example of a successful response, which includes the tax ID's details.
- [Retrieve a tax ID | Stripe API Reference](https://docs.stripe.com/api/tax_ids/retrieve): This page covers retrieving an account or customer tax ID object using its unique identifier through the Stripe API. It specifies the GET request endpoint and shows a sample response containing the tax ID's attributes.
- [List all Customer tax IDs | Stripe API Reference](https://docs.stripe.com/api/tax_ids/customer_list): This page explains how to list all tax IDs associated with a specific customer using the Stripe API. It details the available parameters for filtering and pagination, and provides an example of the API response, which returns an array of tax ID objects.
- [List all tax IDs | Stripe API Reference](https://docs.stripe.com/api/tax_ids/list): This page describes how to list all tax IDs, either for accounts or customers, using the Stripe API. It outlines the parameters for filtering by owner and pagination, and shows an example of the API response containing a list of tax ID objects.
- [Delete a Customer tax ID | Stripe API Reference](https://docs.stripe.com/api/tax_ids/customer_delete): This page details how to delete a customer's tax ID using the Stripe API. It specifies the DELETE request endpoint and provides an example of the response, which confirms the deletion with a 'deleted: true' status.
- [Delete a tax ID | Stripe API Reference](https://docs.stripe.com/api/tax_ids/delete): This page explains how to delete an existing account or customer tax ID object via the Stripe API. It provides the DELETE endpoint and an example response confirming the successful deletion of the tax ID.
- [Test Clocks | Stripe API Reference](https://docs.stripe.com/api/test_clocks): This page introduces Stripe's Test Clocks, a feature that allows for deterministic control over objects in test mode. Test Clocks enable creating objects at specific past or future times and advancing time to observe webhooks and state changes for testing scenarios.
- [The Test Clock object | Stripe API Reference](https://docs.stripe.com/api/test_clocks/object): This page describes the attributes of the Stripe Test Clock object, including its ID, creation timestamp, frozen time, live mode status, name, and current status (e.g., 'advancing', 'ready'). It also details the possible enum values for the status and status details.
- [Create a test clock | Stripe API Reference](https://docs.stripe.com/api/test_clocks/create): This page explains how to create a new test clock in Stripe, which can be attached to customers and quotes for testing purposes. It requires specifying the initial frozen time and an optional name for the test clock, returning the newly created TestClock object upon success.
- [Retrieve a test clock | Stripe API Reference](https://docs.stripe.com/api/test_clocks/retrieve): This page details how to retrieve a specific test clock using its ID via the Stripe API. It provides the GET endpoint and an example response that includes the test clock's details such as ID, creation time, frozen time, and status.
- [List all test clocks | Stripe API Reference](https://docs.stripe.com/api/test_clocks/list): This page explains how to list all available test clocks in Stripe. It outlines parameters for pagination and provides an example API response containing a list of test clock objects, each with its relevant attributes.
- [Delete a test clock | Stripe API Reference](https://docs.stripe.com/api/test_clocks/delete): This page describes how to delete a test clock using the Stripe API. It specifies the DELETE endpoint and provides an example response confirming the successful deletion of the test clock.
- [Advance a test clock | Stripe API Reference](https://docs.stripe.com/api/test_clocks/advance): This page explains how to advance a Stripe test clock to a specified future time, allowing for the observation of webhooks and state changes. The advancement process is initiated via a POST request and completes when the clock's status changes to 'Ready'.
- [Financing Offer | Stripe API Reference](https://docs.stripe.com/api/capital/financing_offers): This page introduces the Stripe Financing Offer object, which represents an offer of financing from Stripe Capital to a Connect subaccount. It details the attributes of the financing offer, including its ID, account, creation date, expiration, financing type, and offered terms.
- [The Financing offer object | Stripe API Reference](https://docs.stripe.com/api/capital/connect_financing_object): This page details the attributes of the Stripe Financing Offer object, used for capital financing for Connect subaccounts. It lists properties such as ID, account, creation timestamp, expiration, financing type, and offered terms including advance amount, currency, and fees.
- [Retrieve a given financing offer | Stripe API Reference](https://docs.stripe.com/api/capital/financing_offers/retrieve): This page explains how to retrieve the details of a specific Stripe financing offer using its ID. It provides the GET API endpoint and an example response that includes all information about the financing offer, such as its status and offered terms.
- [List financing offers | Stripe API Reference](https://docs.stripe.com/api/capital/financing_offers/list): This page describes how to list financing offers available for Connected accounts on a Stripe platform. It outlines parameters for filtering by connected account, creation date, and status, and provides an example API response containing a list of financing offer objects.
- [Mark that a financing offer has been delivered | Stripe API Reference](https://docs.stripe.com/api/capital/financing_offers/mark_delivered): This page explains how to acknowledge the delivery of a Stripe financing offer to a merchant recipient. It specifies the POST API endpoint for marking an offer as delivered and provides an example response confirming the status update.
- [Financing Summary | Stripe API Reference](https://docs.stripe.com/api/capital/financing_summary): The Financing Summary object provides real-time financing status for a connected Stripe account, indicating if an offer is accepted, delivered, or none. It includes details like currency, advance amount, fees, and repayment status. The API allows retrieving this summary for a specific account.
- [The Financing Summary object | Stripe API Reference](https://docs.stripe.com/api/capital/financing_summary_object): The Financing Summary object in Stripe's API details a connected account's real-time financing status, such as 'accepted', 'delivered', or 'none'. It contains financial information like advance amount, fees, and remaining balance. This object is crucial for understanding the financial standing of connected accounts.
- [Retrieve financing summary | Stripe API Reference](https://docs.stripe.com/api/capital/financing_summary/retrieve): This API endpoint allows you to retrieve the financing summary object for a connected Stripe account. The response provides details about the account's current financing status, including financial metrics and the associated financing offer. It's a key tool for monitoring connected account finances.
- [Accounts | Stripe API Reference](https://docs.stripe.com/api/accounts): The Account object represents a Stripe account and contains information like its ID, business type, and capabilities. It details whether the account is enabled for live charges or payouts, and includes requirements for onboarding. This object is fundamental for managing connected accounts via Stripe Connect.
- [The Account object | Stripe API Reference](https://docs.stripe.com/api/accounts/object): The Account object in Stripe's API represents a connected account, detailing its unique identifier, business type, and capabilities. It also includes information about the account's status regarding charges and payouts, and any pending requirements for onboarding. This object is essential for managing and understanding connected accounts.
- [Create an account | Stripe API Reference](https://docs.stripe.com/api/accounts/create): This API allows you to create a new Stripe account for a user via Connect. You can prefill information during creation to streamline the Connect Onboarding process for the connected account. Parameters include the business type and conditionally required capabilities.
- [Update an account | Stripe API Reference](https://docs.stripe.com/api/accounts/update): The Update Account API allows modification of connected account details. Parameters not provided remain unchanged. For Custom accounts, all information can be updated, while for Standard and Express accounts, updates are restricted after Connect Onboarding begins. Use the Dashboard for updating your own account.
- [Retrieve account | Stripe API Reference](https://docs.stripe.com/api/accounts/retrieve): The Retrieve Account API fetches the details of a specific Stripe account using its ID. If the account exists, it returns the Account object containing information like business profile, capabilities, and requirements. An error is raised if the account ID is not found.
- [List all connected accounts | Stripe API Reference](https://docs.stripe.com/api/accounts/list): This API endpoint returns a list of accounts connected to your platform via Stripe Connect. If you are not a platform, the list will be empty. The response includes an array of Account objects, each containing details about a connected account.
- [Delete an account | Stripe API Reference](https://docs.stripe.com/api/accounts/delete): The Delete Account API allows you to delete connected Stripe accounts. Test-mode accounts can be deleted anytime, while live-mode accounts have restrictions based on Stripe's liability for negative balances and zero balances. Your own account must be deleted via account settings.
- [Reject an account | Stripe API Reference](https://docs.stripe.com/api/account/reject): The Reject Account API allows you to reject suspicious connected accounts. This action is only applicable to accounts where your platform is liable for negative balances, such as Custom and Express accounts. Test-mode accounts can be rejected immediately, while live-mode accounts require zero balances.
- [Login Links | Stripe API Reference](https://docs.stripe.com/api/accounts/login_link): Login Links are single-use URLs that direct an Express account to their Stripe dashboard. These links are specifically for Express accounts connected to your platform and differ from Account Links. The API allows you to create a login link for a given account ID.
- [The Login Link object | Stripe API Reference](https://docs.stripe.com/api/accounts/login_link/object): The Login Link object contains a URL that provides single-use access to an Express account's Stripe dashboard. It is generated via an API call and is intended for use with Express accounts connected to your platform. The object includes the URL and creation timestamp.
- [Create a login link | Stripe API Reference](https://docs.stripe.com/api/accounts/login_link/create): This API endpoint creates a login link for a connected account to access their Express Dashboard. It is exclusively for accounts using the Express Dashboard and connected to your platform. The API returns a login link object upon successful creation.
- [Account Links | Stripe API Reference](https://docs.stripe.com/api/account_links): Account Links are used by Connect platforms to grant connected accounts access to Stripe-hosted applications like Connect Onboarding. The API creates an AccountLink object which includes a single-use URL for redirecting users to complete onboarding or update their information. Parameters specify the account and the type of link.
- [The Account Link object | Stripe API Reference](https://docs.stripe.com/api/account_links/object): The Account Link object contains a single-use URL that directs users to Stripe-hosted applications for Connect Onboarding or account updates. It includes an expiration timestamp and the URL itself. This object is generated via an API call and is used for user redirection.
- [Create an account link | Stripe API Reference](https://docs.stripe.com/api/account_links/create): This API endpoint creates an AccountLink object, providing a single-use Stripe URL for users to complete Connect Onboarding or update their account information. Required parameters include the account ID and the type of link ('account_onboarding' or 'account_update'). A refresh URL is also required.
- [Account Session | Stripe API Reference](https://docs.stripe.com/api/account_sessions): An AccountSession allows a Connect platform to grant client-side access to a connected account for embedded components. It generates a client secret for secure access and specifies enabled embedded components. AccountSessions are single-use and expire quickly, so they should not be stored.
- [The Account Session object | Stripe API Reference](https://docs.stripe.com/api/account_sessions/object): The Account Session object provides the necessary details for a Connect platform to grant client-side access to a connected account within embedded components. It includes the account ID, a client secret for secure access, and information about enabled components. This object is temporary and should not be persisted.
- [Create an Account Session | Stripe API Reference](https://docs.stripe.com/api/account_sessions/create): This API endpoint creates an AccountSession object, which includes a single-use token for granting client-side API access to a connected account. It requires the account ID and a configuration object specifying which embedded components are enabled. The API returns the created Account Session object.
- [Application Fees | Stripe API Reference](https://docs.stripe.com/api/application_fees): This page details the Application Fee object in Stripe, which is created when a transaction fee is collected on top of a charge for a user via Connect. It outlines the attributes of the Application Fee object and provides examples of its structure. The page also lists the relevant API endpoints for retrieving and listing application fees.
- [The Application Fee object | Stripe API Reference](https://docs.stripe.com/api/application_fees/object): This page describes the Application Fee object in Stripe's API, detailing its attributes such as ID, account, amount, currency, and refund status. It provides a JSON example of the object and links to related API endpoints for retrieving, listing, and refunding application fees. The information is crucial for understanding how application fees are structured and managed.
- [Retrieve an application fee | Stripe API Reference](https://docs.stripe.com/api/application_fees/retrieve): This page explains how to retrieve a specific application fee using the Stripe API. It details the endpoint and provides an example of the API request and response. The function allows users to fetch the details of a collected application fee, which is useful for managing transactions and refunds.
- [List all application fees | Stripe API Reference](https://docs.stripe.com/api/application_fees/list): This page covers the Stripe API endpoint for listing all collected application fees. It explains that the fees are returned in sorted order by creation date and details the available parameters for filtering the results, such as by charge ID or date range. An example API request and response are provided.
- [Application Fee Refunds | Stripe API Reference](https://docs.stripe.com/api/fee_refunds): This page introduces the Application Fee Refund object in Stripe, which allows for refunding previously created application fees. It explains that funds are returned to the Stripe account from which the fee was originally collected and details the endpoints for creating, updating, retrieving, and listing fee refunds. The page also describes the attributes of the Application Fee Refund object.
- [The Application Fee Refund object | Stripe API Reference](https://docs.stripe.com/api/fee_refunds/object): This page details the Application Fee Refund object within the Stripe API, outlining its attributes such as ID, amount, currency, and the associated fee. It provides a JSON example of the refund object and links to related API endpoints for creating, updating, retrieving, and listing fee refunds. This information is essential for managing the refund process for application fees.
- [Create an application fee refund | Stripe API Reference](https://docs.stripe.com/api/fee_refunds/create): This page describes the Stripe API method for creating an application fee refund. It explains that you can refund all or part of an application fee, and this can be done multiple times until the entire fee is refunded. The page details the parameters for the request, including amount and metadata, and the expected response.
- [Update an application fee refund | Stripe API Reference](https://docs.stripe.com/api/fee_refunds/update): This page explains how to update an application fee refund in Stripe, primarily allowing for modifications to the metadata associated with the refund. It details the API endpoint, parameters, and the expected response, which includes the updated application fee refund object. This functionality is useful for adding or modifying contextual information for a refund.
- [Retrieve an application fee refund | Stripe API Reference](https://docs.stripe.com/api/fee_refunds/retrieve): This page details how to retrieve a specific application fee refund using the Stripe API. It explains that while recent refunds are available on the application fee object, this endpoint allows retrieval of details for a specific refund. The page provides the API endpoint and an example of the request and response.
- [List all application fee refunds | Stripe API Reference](https://docs.stripe.com/api/fee_refunds/list): This page describes the Stripe API endpoint for listing all application fee refunds associated with a specific application fee. It notes that the 10 most recent refunds are available by default on the application fee object, but this endpoint allows for paginating through additional refunds using limit and starting_after parameters. The page includes the API endpoint and an example response.
- [Capabilities | Stripe API Reference](https://docs.stripe.com/api/capabilities): This page introduces the Capability object in Stripe, representing a specific functionality enabled for a Stripe account. It details the attributes of a capability, such as its ID, status, and requirements for activation. The page also lists the relevant API endpoints for updating, retrieving, and listing account capabilities.
- [The Capability object | Stripe API Reference](https://docs.stripe.com/api/capabilities/object): This page describes the Stripe Capability object, detailing its attributes like ID, account, requested status, and requirements for activation. It provides a JSON example of a capability object, illustrating its structure and the information it contains. The page also links to API endpoints for managing account capabilities.
- [Update an Account Capability | Stripe API Reference](https://docs.stripe.com/api/capabilities/update): This page explains how to update an Account Capability in Stripe, allowing users to request or remove capabilities for an account by modifying the 'requested' parameter. It details the API endpoint, parameters, and the expected response, which includes the updated capability object. This is used to enable or disable specific functionalities for an account.
- [Retrieve an Account Capability | Stripe API Reference](https://docs.stripe.com/api/capabilities/retrieve): This page describes how to retrieve information about a specific Account Capability using the Stripe API. It details the API endpoint and provides an example of the request and response, which returns the Capability object. This function is used to check the status and requirements of a particular capability for an account.
- [List all account capabilities | Stripe API Reference](https://docs.stripe.com/api/capabilities/list): This page covers the Stripe API endpoint for listing all capabilities associated with an account. It explains that capabilities are returned sorted by creation date and provides the API endpoint and an example response. This allows users to view all enabled or requested functionalities for a given account.
- [Country Specs | Stripe API Reference](https://docs.stripe.com/api/country_specs): This page introduces the Country Spec object in Stripe, which provides information about country-specific requirements for Stripe accounts. It details attributes like the default currency, supported currencies and payment methods, and verification fields. The page also lists the API endpoints for retrieving and listing country specifications.
- [The Country Spec object | Stripe API Reference](https://docs.stripe.com/api/country_specs/object): This page describes the Stripe Country Spec object, detailing its attributes such as country ID, default currency, supported currencies and payment methods, and verification requirements. It provides a JSON example of the object and links to API endpoints for retrieving and listing country specifications. This object is crucial for understanding regional compliance and feature availability.
- [Retrieve a Country Spec | Stripe API Reference](https://docs.stripe.com/api/country_specs/retrieve): This page explains how to retrieve a specific Country Spec using the Stripe API by providing a country code. It details the API endpoint and provides an example of the request and response, which returns the Country Spec object. This is used to get information about a country's supported currencies, payment methods, and verification requirements.
- [List Country Specs | Stripe API Reference](https://docs.stripe.com/api/country_specs/list): This page covers the Stripe API endpoint for listing all available Country Spec objects. It explains that the objects represent country-specific rules and information relevant to Stripe accounts. The page provides the API endpoint and an example response, allowing users to retrieve a list of all country specifications.
- [Balance Settings | Stripe API Reference](https://docs.stripe.com/api/balance-settings): This page introduces the Balance Settings object in Stripe, which allows for customization of account balances and payout settings for connected accounts on a Stripe platform. It details the attributes of the Balance Setting object, focusing on payments and payouts, and lists the API endpoints for updating and retrieving these settings. This is used to configure how funds are managed and disbursed.
- [The Balance Setting object | Stripe API Reference](https://docs.stripe.com/api/balance-settings/object): The Balance Setting object in the Stripe API defines configurations for a connected account's balance, including settings for payments, payouts, and settlement timing. It allows for updating and retrieving these balance-related settings through specific API endpoints.
- [Update balance settings | Stripe API Reference](https://docs.stripe.com/api/balance-settings/update): The 'Update balance settings' endpoint allows modification of a connected account's balance settings, specifically for payments and payouts. This includes configuring payout schedules, minimum balance requirements by currency, and settlement timing delays.
- [Retrieve balance settings | Stripe API Reference](https://docs.stripe.com/api/balance-settings/retrieve): The 'Retrieve balance settings' endpoint fetches the current balance settings for a connected account. This allows developers to view configurations related to payments and payouts, such as settlement timing and payout schedules.
- [External Bank Accounts | Stripe API Reference](https://docs.stripe.com/api/external_accounts): External bank accounts are financial accounts linked to Stripe platform connected accounts for fund transfers. The API provides endpoints to create, update, retrieve, list, and delete these bank accounts, which are essential for managing payouts and deposits.
- [The External Bank Account object | Stripe API Reference](https://docs.stripe.com/api/external_account_bank_accounts/object): The External Bank Account object in the Stripe API represents a bank account linked to a connected account for fund transfers. It includes attributes like account details, country, currency, and status, and is managed through various API endpoints.
- [Create a bank account | Stripe API Reference](https://docs.stripe.com/api/external_account_bank_accounts/create): The 'Create a bank account' endpoint allows for the addition of a new bank account to a connected account. This process requires specifying the connected account and can optionally set the new bank account as the default for its currency.
- [Update a bank account | Stripe API Reference](https://docs.stripe.com/api/external_account_bank_accounts/update): The 'Update a bank account' endpoint enables modifications to a connected account's bank account details, such as metadata and account holder information. It also allows setting a bank account as the default for its currency, but other core details are not editable.
- [Retrieve a bank account | Stripe API Reference](https://docs.stripe.com/api/external_account_bank_accounts/retrieve): The 'Retrieve a bank account' endpoint fetches details for a specific external bank account associated with a connected account. It allows access to information like the bank name, last four digits, and status.
- [List all bank accounts | Stripe API Reference](https://docs.stripe.com/api/external_account_bank_accounts/list): The 'List all bank accounts' endpoint retrieves a list of all bank accounts associated with a connected account. This is useful for managing multiple external accounts and can be used with parameters to paginate through results beyond the default ten.
- [Delete a bank account | Stripe API Reference](https://docs.stripe.com/api/external_account_bank_accounts/delete): The 'Delete a bank account' endpoint removes a destination bank account from a connected account. Restrictions apply, particularly if the bank account is set as the default for its currency, requiring a replacement before deletion.
- [External Account Cards | Stripe API Reference](https://docs.stripe.com/api/external_account_cards): External account cards are debit cards linked to Stripe platform connected accounts for fund transfers. The API provides endpoints to manage these cards, including creating, updating, retrieving, listing, and deleting them.
- [The External Account Card object | Stripe API Reference](https://docs.stripe.com/api/external_account_cards/object): The External Account Card object in the Stripe API represents a debit card linked to a connected account for fund transfers. It stores details like card brand, country, expiration date, and billing address information.
- [Create a card | Stripe API Reference](https://docs.stripe.com/api/external_account_cards/create): The 'Create a card' endpoint allows adding a new debit card to a connected account, which can then be used for fund transfers. This process can optionally designate the new card as the default for its currency.
- [Update a card | Stripe API Reference](https://docs.stripe.com/api/external_account_cards/update): The 'Update a card' endpoint allows for modifying specific details of a card associated with a connected account, such as billing address or expiration date, without requiring re-entry of full card details. It can also set the card as the default for its currency.
- [Retrieve a card | Stripe API Reference](https://docs.stripe.com/api/external_account_cards/retrieve): The 'Retrieve a card' endpoint fetches details for a specific external card associated with a connected account. This allows viewing information such as the card's brand, last four digits, and expiration date.
- [List all cards | Stripe API Reference](https://docs.stripe.com/api/external_account_cards/list): The 'List all cards' endpoint retrieves a list of all external cards associated with a connected account. This functionality is useful for managing multiple cards and can be paginated to retrieve more than the default ten.
- [Delete a card | Stripe API Reference](https://docs.stripe.com/api/external_account_cards/delete): The 'Delete a card' endpoint removes a card from a connected account. Similar to bank accounts, restrictions apply if the card is the default for its currency, requiring a replacement before deletion.
- [Person | Stripe API Reference](https://docs.stripe.com/api/persons): The Person object in the Stripe API represents an individual associated with a Stripe account, often required for identity verification and compliance. Platforms can access a subset of this data for accounts undergoing onboarding.
- [The Person object | Stripe API Reference](https://docs.stripe.com/api/persons/object): The Person object in the Stripe API details an individual associated with a Stripe account, including their name, address, date of birth, and relationship to the account. It also contains information regarding verification requirements.
- [Create a person | Stripe API Reference](https://docs.stripe.com/api/persons/create): The 'Create a person' endpoint allows for the creation of a new person object associated with a connected account. This is a crucial step for identity verification and compliance, requiring details such as name, address, date of birth, and potentially an ID number.
- [Update a person | Stripe API Reference](https://docs.stripe.com/api/persons/update): This page details how to update an existing person's information within your Stripe account. You can modify various attributes such as address, date of birth, name, and contact details.
- [Retrieve a person | Stripe API Reference](https://docs.stripe.com/api/persons/retrieve): This page explains how to retrieve the details of a specific person associated with your Stripe account. It requires the person's ID to fetch their information.
- [List all persons | Stripe API Reference](https://docs.stripe.com/api/persons/list): This page describes how to list all persons associated with your Stripe account's legal entity. You can filter the list based on the person's relationship to the company.
- [Delete a person | Stripe API Reference](https://docs.stripe.com/api/persons/delete): This page outlines the process of deleting a person's relationship to an account's legal entity in Stripe. This action can be performed via the API, with specific exceptions for account openers and verified executives.
- [Top-ups | Stripe API Reference](https://docs.stripe.com/api/topups): This page introduces the concept of top-ups in Stripe, which are used to add funds to your Stripe balance. It covers creating, updating, retrieving, listing, and canceling top-ups.
- [The Top-up object | Stripe API Reference](https://docs.stripe.com/api/topups/object): This page details the attributes of the Stripe Top-up object, including its ID, amount, currency, description, and status. It also provides an example of a top-up object.
- [Create a top-up | Stripe API Reference](https://docs.stripe.com/api/topups/create): This page explains how to create a top-up to add funds to your Stripe balance. It requires specifying the amount, currency, and optionally a description and metadata.
- [Update a top-up | Stripe API Reference](https://docs.stripe.com/api/topups/update): This page describes how to update the metadata of an existing Stripe top-up. Other details of a top-up cannot be edited after creation.
- [Retrieve a top-up | Stripe API Reference](https://docs.stripe.com/api/topups/retrieve): This page details how to retrieve the information for a specific Stripe top-up using its unique ID. It returns the top-up object if the ID is valid.
- [List all top-ups | Stripe API Reference](https://docs.stripe.com/api/topups/list): This page explains how to list all top-ups associated with your Stripe account. You can filter the list by status and sort the results.
- [Cancel a top-up | Stripe API Reference](https://docs.stripe.com/api/topups/cancel): This page describes how to cancel a pending top-up in Stripe. Only top-ups with a 'pending' status can be canceled.
- [Transfers | Stripe API Reference](https://docs.stripe.com/api/transfers): This page introduces Stripe Transfers, used for moving funds between Stripe accounts within Connect. It distinguishes them from Payouts, which move funds to external bank accounts or cards.
- [The Transfer object | Stripe API Reference](https://docs.stripe.com/api/transfers/object): This page details the attributes of the Stripe Transfer object, including its ID, amount, currency, destination, and metadata. It also provides an example of a transfer object.
- [Create a transfer | Stripe API Reference](https://docs.stripe.com/api/transfers/create): This page explains how to create a transfer to send funds from your Stripe account to a connected account. It requires specifying the amount, currency, and destination account ID.
- [Update a transfer | Stripe API Reference](https://docs.stripe.com/api/transfers/update): This page describes how to update a Stripe transfer, primarily by modifying its metadata or description. Other transfer details cannot be changed after creation.
- [Retrieve a transfer | Stripe API Reference](https://docs.stripe.com/api/transfers/retrieve): This page explains how to retrieve the details of an existing Stripe transfer using its unique ID. It returns the transfer information if a valid ID is provided.
- [List all transfers | Stripe API Reference](https://docs.stripe.com/api/transfers/list): This page describes how to list all transfers sent to connected accounts. You can filter transfers by destination account and sort the results.
- [Transfer Reversals | Stripe API Reference](https://docs.stripe.com/api/transfer_reversals): This page introduces Stripe Transfer Reversals, allowing Connect platforms to reverse transfers made to connected accounts. Reversals affect both the platform's and the destination account's balances.
- [The Transfer Reversal object | Stripe API Reference](https://docs.stripe.com/api/transfer_reversals/object): This page details the attributes of the Stripe Transfer Reversal object, including its ID, amount, currency, and the associated transfer ID. It also provides an example of a transfer reversal object.
- [Create a transfer reversal | Stripe API Reference](https://docs.stripe.com/api/transfer_reversals/create): This page explains how to create a transfer reversal, either partially or fully, for a given transfer. This action is only allowed for transfers to Stripe Accounts and cannot exceed the unreversed amount.
- [Update a reversal | Stripe API Reference](https://docs.stripe.com/api/transfer_reversals/update): This page details how to update a transfer reversal using the Stripe API. You can modify the metadata and description of an existing reversal. The request only accepts these specific arguments for updates.
- [Retrieve a reversal | Stripe API Reference](https://docs.stripe.com/api/transfer_reversals/retrieve): This page explains how to retrieve a specific transfer reversal using the Stripe API. By default, the 10 most recent reversals are available on the transfer object, but this endpoint allows access to details of a particular reversal.
- [List all reversals | Stripe API Reference](https://docs.stripe.com/api/transfer_reversals/list): This page describes how to list all reversals associated with a specific transfer via the Stripe API. It allows for pagination to retrieve more than the default 10 most recent reversals using `limit` and `starting_after` parameters.
- [Secrets | Stripe API Reference](https://docs.stripe.com/api/secret_management): This page introduces Stripe's Secret Store API, designed for securely persisting secrets for Stripe Apps developers. It explains the concept of secrets, their scoping (account-level and user-level), and lists the available endpoints for managing them.
- [Secrets | Stripe API Reference](https://docs.stripe.com/api/apps/secret_store/secret_resource): This page details the structure and attributes of the Secret object within Stripe's API. It outlines properties such as ID, creation timestamp, expiration, live mode status, name, and payload. The page also covers listing secrets by scope.
- [List secrets | Stripe API Reference](https://docs.stripe.com/api/apps/secret_store/list): This page explains how to list all secrets stored within a given scope using the Stripe API. It details the parameters, including the required `scope` object, and describes the structure of the returned list of Secret objects.
- [Delete a Secret | Stripe API Reference](https://docs.stripe.com/api/apps/secret_store/delete): This page describes how to delete a secret from the Stripe Secret Store using the API. It requires the secret's name and scope for identification and returns the deleted secret object upon successful deletion.
- [Find a Secret | Stripe API Reference](https://docs.stripe.com/api/apps/secret_store/find): This page explains how to find a specific secret within the Stripe Secret Store using its name and scope. It details the parameters required for the search and the structure of the returned secret object.
- [Set a Secret | Stripe API Reference](https://docs.stripe.com/api/apps/secret_store/set): This page describes how to create or replace a secret in the Stripe Secret Store using the API. It outlines the required parameters: name, payload, and scope, along with an optional expiration time. The endpoint returns the created or updated secret object.
- [Overview | Stripe API Reference](https://docs.stripe.com/api/reserves): This page provides an overview of Stripe's Reserves feature, which allows Connect platforms to hold a portion of a connected account's funds. This is used to cover potential negative balances from refunds and disputes, thereby reducing loss exposure. The feature is part of Radar for Platforms and may require early access.
- [Reserve Holds | Stripe API Reference](https://docs.stripe.com/api/reserve/hold): This page introduces ReserveHolds, a feature for placing temporary holds on a merchant's funds via the Stripe API. It lists the available endpoints for creating, retrieving, and updating ReserveHolds, and describes the attributes of the ReserveHold object.
- [The ReserveHold object | Stripe API Reference](https://docs.stripe.com/api/reserve/hold/object): This page details the attributes of the ReserveHold object in Stripe's API, including its ID, amount, currency, and release schedule. It also covers related information such as `amount_releasable`, `created_by`, and `livemode` status.
- [Create a ReserveHold | Stripe API Reference](https://docs.stripe.com/api/reserve/hold/create): This page explains how to create a ReserveHold using the Stripe API, which involves placing a temporary hold on a merchant's funds. It details the required parameters such as amount, currency, and release schedule, and specifies the endpoint for this operation.
- [Update a ReserveHold | Stripe API Reference](https://docs.stripe.com/api/reserve/hold/update): This page describes how to update a ReserveHold's release schedule or metadata using the Stripe API. It requires the ReserveHold's ID and allows modification of associated metadata and release timing. The endpoint returns the updated ReserveHold object.
- [Retrieve a ReserveHold | Stripe API Reference](https://docs.stripe.com/api/reserve/hold/retrieve): This page explains how to retrieve a specific ReserveHold using its ID via the Stripe API. It details the required `id` parameter and describes the structure of the returned ReserveHold object, including its amount, currency, and release schedule.
- [List ReserveHolds | Stripe API Reference](https://docs.stripe.com/api/reserve/hold/list): This page describes how to list ReserveHolds using the Stripe API, returning them in sorted order with the most recent first. It details various filtering parameters such as currency, releasability, and source charge, as well as pagination options.
- [Reserve Plans | Stripe API Reference](https://docs.stripe.com/api/reserve/plan): This page introduces ReservePlans, a Stripe API feature for automatically placing holds on a merchant's funds until the plan expires. It outlines the different types of ReservePlans (fixed and rolling release) and lists the available endpoints for managing them.
- [The ReservePlan object | Stripe API Reference](https://docs.stripe.com/api/reserve/plan/object): This page details the attributes of the ReservePlan object in Stripe's API, including its ID, percentage of charges to reserve, and release schedule type (fixed or rolling). It also covers status, currency, and metadata associated with the plan.
- [Create a ReservePlan | Stripe API Reference](https://docs.stripe.com/api/reserve/plan/create): This page explains how to create a ReservePlan using the Stripe API, which automatically reserves a percentage of charges. It details the required parameters such as percentage, type (fixed or rolling release), and optional currency. The endpoint returns the created ReservePlan object.
- [Update a ReservePlan | Stripe API Reference](https://docs.stripe.com/api/reserve/plan/update): This page describes how to update a ReservePlan's configuration, percentage, or metadata using the Stripe API. It requires the ReservePlan's ID and allows modifications to its release schedule, percentage, and associated metadata. The endpoint returns the updated ReservePlan object.
- [Retrieve a ReservePlan | Stripe API Reference](https://docs.stripe.com/api/reserve/plan/retrieve): This page details how to retrieve a specific ReservePlan using its ID via the Stripe API. It outlines the request parameters, the expected ReservePlan object in the response, and provides example cURL commands for both retrieving a single plan and listing multiple plans.
- [List ReservePlans | Stripe API Reference](https://docs.stripe.com/api/reserve/plan/list): This page explains how to list existing ReservePlans using the Stripe API. It details the available parameters for filtering and pagination, and provides example cURL commands and response structures for retrieving a list of ReservePlans.
- [Disable a ReservePlan | Stripe API Reference](https://docs.stripe.com/api/reserve/plan/disable): This page describes how to disable a ReservePlan using its ID via the Stripe API. Disabling a ReservePlan is an irreversible action that will asynchronously release all associated ReserveHolds. The API call returns the updated ReservePlan object.
- [Reserve Releases | Stripe API Reference](https://docs.stripe.com/api/reserve/release): This section introduces ReserveReleases, which represent the release of funds from a ReserveHold. It details the available endpoints for creating, retrieving, and listing ReserveReleases, and describes the attributes of a ReserveRelease object, including its ID, amount, currency, reason for release, and associated ReserveHold.
- [The ReserveRelease object | Stripe API Reference](https://docs.stripe.com/api/reserve/release/object): This page provides a detailed description of the ReserveRelease object in the Stripe API. It outlines the attributes of a ReserveRelease, such as its ID, amount, currency, reason for release, and the associated ReserveHold and ReservePlan. It also includes information on creating a ReserveRelease.
- [Create a ReserveRelease | Stripe API Reference](https://docs.stripe.com/api/reserve/release/create): This page details how to create a ReserveRelease using the Stripe API to manually release funds from a ReserveHold. It specifies the required parameters such as `reserve_hold` and `amount`, and optional parameters like `currency` and `metadata`. The API returns the created ReserveRelease object.
- [Update a ReserveRelease | Stripe API Reference](https://docs.stripe.com/api/reserve/release/update): This page explains how to update the metadata of an existing ReserveRelease using its ID via the Stripe API. It details the required `metadata` parameter and specifies that the API returns the updated ReserveRelease object.
- [Retrieve a ReserveRelease | Stripe API Reference](https://docs.stripe.com/api/reserve/release/retrieve): This page describes how to retrieve a specific ReserveRelease using its ID via the Stripe API. It outlines the request parameters and the structure of the returned ReserveRelease object. It also provides information on listing ReserveReleases with various filter and pagination options.
- [List ReserveReleases | Stripe API Reference](https://docs.stripe.com/api/reserve/release/list): This page details how to list ReserveReleases using the Stripe API, allowing filtering by currency, reserve_hold, or reserve_plan, and supporting pagination. It provides example cURL commands and describes the structure of the returned list of ReserveRelease objects.
- [Early Fraud Warning | Stripe API Reference](https://docs.stripe.com/api/radar/early_fraud_warnings): This page introduces Early Fraud Warnings (EFWs) in Stripe, which indicate potential fraud reported by card issuers. It describes the EFW object's attributes, such as its ID, actionable status, associated charge, and fraud type. The page also covers endpoints for retrieving and listing EFWs.
- [The Early Fraud Warning object | Stripe API Reference](https://docs.stripe.com/api/radar/early_fraud_warnings/object): This page details the Stripe Early Fraud Warning (EFW) object, including its attributes like ID, actionable status, associated charge, and fraud type. It explains that an EFW is actionable if no dispute has been received and the charge has not been fully refunded. The page also covers how to retrieve a specific EFW.
- [Retrieve an early fraud warning | Stripe API Reference](https://docs.stripe.com/api/radar/early_fraud_warnings/retrieve): This page explains how to retrieve a specific Early Fraud Warning (EFW) using its ID via the Stripe API. It also details how to list all early fraud warnings, with options to filter by charge, creation date, or PaymentIntent. Example cURL commands and response structures are provided.
- [List all early fraud warnings | Stripe API Reference](https://docs.stripe.com/api/radar/early_fraud_warnings/list): This page describes how to list all early fraud warnings using the Stripe API, with options to filter by charge, creation date, or PaymentIntent. It provides example cURL commands and details the structure of the returned list of EarlyFraudWarning objects.
- [Reviews | Stripe API Reference](https://docs.stripe.com/api/radar/reviews): This page introduces Stripe Reviews, which are used to supplement automated fraud detection with human expertise. It describes the Review object's attributes, such as its ID, associated charge, open status, and reason. Endpoints for retrieving, listing, and approving reviews are also covered.
- [The Review object | Stripe API Reference](https://docs.stripe.com/api/radar/reviews/object): This page details the Stripe Review object, including its attributes like ID, associated charge, open status, and reason for being open or closed. It explains that reviews can be used to enhance fraud detection and covers endpoints for retrieving and approving reviews.
- [Retrieve a review | Stripe API Reference](https://docs.stripe.com/api/radar/reviews/retrieve): This page explains how to retrieve a specific review using its ID via the Stripe API and how to list all open reviews. It provides example cURL commands and details the structure of the returned Review objects and the list response.
- [List all open reviews | Stripe API Reference](https://docs.stripe.com/api/radar/reviews/list): This page details how to list all open reviews using the Stripe API, sorted by creation date. It provides example cURL commands and describes the structure of the returned list of Review objects. It also covers the endpoint for approving a review.
- [Approve a review | Stripe API Reference](https://docs.stripe.com/api/radar/reviews/approve): This page explains how to approve a review using its ID via the Stripe API, which closes the review and removes it from the list. The API call returns the approved Review object. Example cURL commands are provided.
- [Value Lists | Stripe API Reference](https://docs.stripe.com/api/radar/value_lists): This page introduces Stripe Value Lists, which allow grouping values for use in rules to enhance fraud detection. It describes the Value List object's attributes, such as ID, alias, item type, and name. Endpoints for creating, retrieving, and deleting value lists are also covered.
- [The Value List object | Stripe API Reference](https://docs.stripe.com/api/radar/value_lists/object): This page details the Stripe Value List object, including its attributes like ID, alias, item type, and name. It explains that value lists are used to group values that can be referenced in rules for fraud detection. The page also covers creating a new value list.
- [Create a value list | Stripe API Reference](https://docs.stripe.com/api/radar/value_lists/create): This page details how to create a Stripe ValueList object using the API. A ValueList is used to store collections of items like IP addresses or card fingerprints that can be referenced in Radar rules. The process involves specifying a name, alias, and the type of items the list will contain.
- [Update a value list | Stripe API Reference](https://docs.stripe.com/api/radar/value_lists/update): This page explains how to update an existing Stripe ValueList object via the API. You can modify the name and alias of a ValueList, but the item_type is immutable once created. Metadata can also be updated or cleared.
- [Retrieve a value list | Stripe API Reference](https://docs.stripe.com/api/radar/value_lists/retrieve): This page describes how to retrieve a specific Stripe ValueList object using its ID via the API. It returns the details of the ValueList, including its ID, name, alias, item type, and creation information.
- [List all value lists | Stripe API Reference](https://docs.stripe.com/api/radar/value_lists/list): This page outlines how to list all Stripe ValueList objects using the API. The results can be filtered by alias and sorted by creation date, with options to control the number of returned lists. It provides a way to view existing value lists.
- [Delete a value list | Stripe API Reference](https://docs.stripe.com/api/radar/value_lists/delete): This page details the process of deleting a Stripe ValueList object and its associated items using the API. A value list must not be referenced in any rules before it can be deleted. The API returns confirmation of the deletion.
- [Value List Items | Stripe API Reference](https://docs.stripe.com/api/radar/value_list_items): This page introduces Value List Items, which are individual values added to a Stripe Radar ValueList. These items can be of various types (e.g., IP address, email, card fingerprint) and are used in Radar rules. The page lists the available API endpoints for managing these items.
- [The Value List Item object | Stripe API Reference](https://docs.stripe.com/api/radar/value_list_items/object): This page describes the structure and attributes of the Stripe ValueListItem object. It includes the item's unique ID, its value, and the identifier of the parent ValueList it belongs to. The page also provides an example of a ValueListItem object.
- [Create a value list item | Stripe API Reference](https://docs.stripe.com/api/radar/value_list_items/create): This page explains how to create a new Stripe ValueListItem object and add it to a specified parent ValueList. The process requires providing the value of the item and the ID of the ValueList it should be added to. The API returns the newly created ValueListItem object.
- [Retrieve a value list item | Stripe API Reference](https://docs.stripe.com/api/radar/value_list_items/retrieve): This page details how to retrieve a specific Stripe ValueListItem object using its ID via the API. It returns the details of the ValueListItem, including its ID, value, and the associated ValueList ID. An example response is provided.
- [List all value list items | Stripe API Reference](https://docs.stripe.com/api/radar/value_list_items/list): This page explains how to list all Stripe ValueListItem objects, optionally filtering by the parent ValueList or a specific value. The items are sorted by creation date in descending order. The API returns a list of ValueListItem objects or an empty array if none are found.
- [Delete a value list item | Stripe API Reference](https://docs.stripe.com/api/radar/value_list_items/delete): This page describes how to delete a Stripe ValueListItem object using its ID via the API. Deleting an item removes it from its parent ValueList. The API confirms the deletion by returning the item's ID and a deleted status.
- [Authorizations | Stripe API Reference](https://docs.stripe.com/api/issuing/authorizations): This page introduces Stripe Issuing Authorizations, which are created when an issued card is used for a purchase. Authorizations must be approved for a purchase to complete. The page lists the available API endpoints for managing authorizations, including approving, declining, and retrieving them.
- [The Authorization object | Stripe API Reference](https://docs.stripe.com/api/issuing/authorizations/object): This page details the attributes of the Stripe Authorization object. It includes information such as the authorization ID, amount, approval status, card details, currency, and current status (pending, closed, expired, reversed). Examples of the object's structure are provided.
- [Update an authorization | Stripe API Reference](https://docs.stripe.com/api/issuing/authorizations/update): This page explains how to update an existing Stripe Issuing Authorization object via the API. Currently, only the metadata of an authorization can be updated. The API returns the modified Authorization object upon successful update.
- [Retrieve an authorization | Stripe API Reference](https://docs.stripe.com/api/issuing/authorizations/retrieve): This page describes how to retrieve a specific Stripe Issuing Authorization object using its ID via the API. It returns the full details of the authorization, including its amount, status, cardholder information, and merchant data. An example response is provided.
- [List all authorizations | Stripe API Reference](https://docs.stripe.com/api/issuing/authorizations/list): This page explains how to list all Stripe Issuing Authorization objects. The results can be filtered by card, cardholder, or status (pending, closed, reversed) and sorted by creation date. The API returns a list of Authorization objects or an empty array.
- [Approve an authorization | Stripe API Reference](https://docs.stripe.com/api/issuing/authorizations/approve): This page describes how to approve a pending Stripe Issuing Authorization object via the API. While deprecated in favor of webhook responses, this method allows specifying an amount and metadata for approval. It returns the approved Authorization object.
- [Decline an authorization | Stripe API Reference](https://docs.stripe.com/api/issuing/authorizations/decline): This page details how to decline a pending Stripe Issuing Authorization object via the API. Although deprecated in favor of webhook responses, this method allows adding metadata to the decline action. It returns the declined Authorization object.
- [Create a test-mode authorization | Stripe API Reference](https://docs.stripe.com/api/issuing/authorizations/test_mode_create): This page explains how to create a test-mode Stripe Issuing Authorization using the API. This is useful for testing authorization flows without affecting live data. Parameters include the card, amount, and currency, and it returns a created Authorization object.
- [Capture a test-mode authorization | Stripe API Reference](https://docs.stripe.com/api/issuing/authorizations/test_mode_capture): This page describes how to capture a test-mode Stripe Issuing Authorization using the API. You can specify the capture amount and whether to close the authorization after capture. It returns the updated Authorization object.
- [Expire a test-mode authorization | Stripe API Reference](https://docs.stripe.com/api/issuing/authorizations/test_mode_expire): This page describes how to expire a test-mode authorization using the Stripe API. It provides the endpoint and expected response for this operation.
- [Finalize a test-mode authorization's amount | Stripe API Reference](https://docs.stripe.com/api/issuing/authorizations/test_mode_finalize_amount): This page explains how to finalize the amount of a test-mode authorization before capture using the Stripe API. It details the required 'final_amount' parameter and the structure of the returned Authorization object.
- [Increment a test-mode authorization | Stripe API Reference](https://docs.stripe.com/api/issuing/authorizations/test_mode_increment): This page details how to increment a test-mode authorization's amount using the Stripe API. It specifies the 'increment_amount' parameter and the optional 'is_amount_controllable' flag, along with the returned Authorization object.
- [Respond to fraud challenge | Stripe API Reference](https://docs.stripe.com/api/issuing/authorizations/respond_to_fraud_challenges): This page describes how to respond to a fraud challenge for a test-mode Issuing authorization via the Stripe API. It explains the 'confirmed' parameter, which simulates either a legitimate transaction or a fraudulent one, and the returned Authorization object.
- [Reverse a test-mode authorization | Stripe API Reference](https://docs.stripe.com/api/issuing/authorizations/test_mode_reverse): This page explains how to reverse a test-mode authorization using the Stripe API. It details the optional 'reverse_amount' parameter and the structure of the returned Authorization object.
- [Cardholders | Stripe API Reference](https://docs.stripe.com/api/issuing/cardholders): This page introduces the Stripe Issuing Cardholder object, which represents an individual or business entity issued cards. It outlines the available endpoints for managing cardholders, including creating, retrieving, updating, and listing them, and describes the key attributes of the Cardholder object.
- [The Cardholder object | Stripe API Reference](https://docs.stripe.com/api/issuing/cardholders/object): This page provides a detailed description of the Stripe Issuing Cardholder object's attributes. It covers identifiers, billing information, contact details, metadata, and status, along with examples of its structure.
- [Create a cardholder | Stripe API Reference](https://docs.stripe.com/api/issuing/cardholders/create): This page describes how to create a new Issuing Cardholder object using the Stripe API. It details the required parameters such as 'billing' and 'type', and optional parameters like 'email' and 'phone_number', along with the structure of the returned Cardholder object.
- [Update a cardholder | Stripe API Reference](https://docs.stripe.com/api/issuing/cardholders/update): This page explains how to update an existing Issuing Cardholder object via the Stripe API. It lists the updatable parameters such as billing information, email, and metadata, and describes the returned updated Cardholder object.
- [Retrieve a cardholder | Stripe API Reference](https://docs.stripe.com/api/issuing/cardholders/retrieve): This page describes how to retrieve a specific Issuing Cardholder object using its ID via the Stripe API. It outlines the parameters and the structure of the returned Cardholder object, including information about deleted cards.
- [List all cardholders | Stripe API Reference](https://docs.stripe.com/api/issuing/cardholders/list): This page details how to list all Issuing Cardholder objects using the Stripe API. It explains the available filtering parameters such as 'cardholder', 'type', and 'status', and the structure of the returned list of Cardholder objects.
- [Cards | Stripe API Reference](https://docs.stripe.com/api/issuing/cards): This page introduces the Stripe Issuing Card object, which can be physical or virtual and is issued to cardholders. It outlines the endpoints for managing cards, including creation, retrieval, updates, and shipping test helpers, and describes the key attributes of the Card object.
- [The Card object | Stripe API Reference](https://docs.stripe.com/api/issuing/cards/object): This page provides a detailed description of the Stripe Issuing Card object's attributes. It covers identifiers, cancellation reasons, cardholder information, currency, expiration details, last four digits, metadata, status, and card type, along with examples of its structure.
- [Create a card | Stripe API Reference](https://docs.stripe.com/api/issuing/cards/create): This page describes how to create an Issuing Card object (physical or virtual) using the Stripe API. It details the required parameters like 'currency', 'type', and 'cardholder', and optional parameters such as expiration date and metadata. The response includes the created Card object.
- [Update a card | Stripe API Reference](https://docs.stripe.com/api/issuing/cards/update): This page explains how to update an Issuing Card object using the Stripe API. It details parameters for updating the card's status, cancellation reason, metadata, and other settings, and describes the returned updated Card object.
- [Retrieve a card | Stripe API Reference](https://docs.stripe.com/api/issuing/cards/retrieve): This page describes how to retrieve a specific Issuing Card object using its ID via the Stripe API. It outlines the parameters and the structure of the returned Card object, including information about deleted cards.
- [List all cards | Stripe API Reference](https://docs.stripe.com/api/issuing/cards/list): This page details how to list all Issuing Card objects using the Stripe API. It explains the available filtering parameters such as 'cardholder', 'type', and 'status', and the structure of the returned list of Card objects.
- [Deliver a testmode card | Stripe API Reference](https://docs.stripe.com/api/issuing/cards/test_mode_deliver): This page describes how to update a test-mode Issuing Card object to a 'delivered' shipping status using the Stripe API. It provides the endpoint and expected response, which is the updated Card object.
- [Fail a testmode card | Stripe API Reference](https://docs.stripe.com/api/issuing/cards/test_mode_fail): This page explains how to update a test-mode Issuing Card object to a 'failed' shipping status using the Stripe API. It provides the endpoint and the expected response, which is the updated Card object.
- [Return a testmode card | Stripe API Reference](https://docs.stripe.com/api/issuing/cards/test_mode_return): This page describes how to update a test-mode Issuing Card object to a 'returned' shipping status using the Stripe API. It provides the endpoint and the expected response, which is the updated Card object.
- [Ship a testmode card | Stripe API Reference](https://docs.stripe.com/api/issuing/cards/test_mode_ship): This page describes how to ship a testmode Issuing Card using the Stripe API. It provides the endpoint and example for updating the shipping status of a card to 'shipped'.
- [Disputes | Stripe API Reference](https://docs.stripe.com/api/issuing/disputes): This page introduces the Stripe API for Issuing Disputes, allowing card issuers to dispute transactions. It lists relevant endpoints and details the attributes of the Dispute object, including its ID, amount, currency, evidence, status, and associated transaction.
- [The Dispute object | Stripe API Reference](https://docs.stripe.com/api/issuing/disputes/object): This page details the Stripe Issuing Dispute object, outlining its attributes such as ID, amount, currency, evidence, and status. It also explains how to create a dispute, noting that individual evidence fields are optional during creation but required during submission.
- [Create a dispute | Stripe API Reference](https://docs.stripe.com/api/issuing/disputes/create): This page explains how to create an Issuing Dispute object using the Stripe API. It details the required 'transaction' parameter and optional 'evidence' and 'metadata' parameters. The endpoint and an example request/response are provided for creating a dispute in an 'unsubmitted' status.
- [Update a dispute | Stripe API Reference](https://docs.stripe.com/api/issuing/disputes/update): This page describes how to update an existing Issuing Dispute object via the Stripe API. It explains that any parameters not provided will remain unchanged and that properties on the 'evidence' object can be unset by passing an empty string. The endpoint and an example for updating dispute evidence are shown.
- [Retrieve a dispute | Stripe API Reference](https://docs.stripe.com/api/issuing/disputes/retrieve): This page details how to retrieve a specific Issuing Dispute object using its ID via the Stripe API. It also explains how to list all Issuing Disputes, sorted by creation date, with options to filter by transaction, creation date range, and status. Example requests and responses are provided for both operations.
- [List all disputes | Stripe API Reference](https://docs.stripe.com/api/issuing/disputes/list): This page explains how to retrieve a list of Issuing Dispute objects using the Stripe API, sorted by creation date. It details available parameters for filtering disputes by transaction, date range, and status. Example requests and responses are provided for listing disputes and submitting a dispute.
- [Submit a dispute | Stripe API Reference](https://docs.stripe.com/api/issuing/dispute/submit): This page describes how to submit an Issuing Dispute to the card network using the Stripe API. It confirms that Stripe validates required evidence fields during submission and provides the endpoint and an example for submitting a dispute, which changes its status to 'submitted'.
- [Funding Instructions | Stripe API Reference](https://docs.stripe.com/api/issuing/funding_instructions): This page introduces Funding Instructions for Stripe Issuing, which contain reusable bank account and routing information for topping up Issuing Balances via bank transfer. It lists endpoints for creating and retrieving funding instructions, and describes the Funding Instruction object's attributes.
- [The Funding Instruction object | Stripe API Reference](https://docs.stripe.com/api/issuing/funding_instructions/object): This page details the Stripe Issuing Funding Instruction object, outlining its attributes such as bank transfer details, currency, and funding type. It also explains how to create or retrieve funding instructions for an Issuing balance, returning existing instructions if they already exist.
- [Create funding instructions | Stripe API Reference](https://docs.stripe.com/api/issuing/funding_instructions/create): This page explains how to create or retrieve funding instructions for a Stripe Issuing balance using the API. It details the required parameters for bank transfer types and currency. The endpoint and an example response for creating funding instructions are provided.
- [List all funding instructions | Stripe API Reference](https://docs.stripe.com/api/issuing/funding_instructions/list): This page describes how to retrieve all applicable funding instructions for a Stripe Issuing balance. It provides the API endpoint and an example response, detailing parameters for filtering the list by limit and pagination. It also introduces the test helper to simulate a top-up.
- [Simulate a top up | Stripe API Reference](https://docs.stripe.com/api/issuing/funding_instructions/fund): This page explains how to simulate a top-up for a Stripe Issuing balance in test mode using the API. It details the required 'amount' and 'currency' parameters for the simulated bank transfer. The endpoint and an example response are provided.
- [Personalization Designs | Stripe API Reference](https://docs.stripe.com/api/issuing/personalization_designs): This page introduces Personalization Designs in Stripe Issuing, which logically group physical bundles, card logos, and carrier text to represent product lines. It lists endpoints for creating, retrieving, updating, and managing the status of personalization designs. The Personalization Design object's attributes are also described.
- [The Personalization Design object | Stripe API Reference](https://docs.stripe.com/api/issuing/personalization_designs/object): This page details the Stripe Issuing Personalization Design object, outlining its attributes such as ID, card logo, carrier text, lookup key, and status. It describes how this object represents a product line by grouping physical card elements and provides an example of the object's structure.
- [Create a personalization design | Stripe API Reference](https://docs.stripe.com/api/issuing/personalization_designs/create): This page explains how to create a Personalization Design object using the Stripe API. It details the required 'physical_bundle' parameter and other optional parameters like 'card_logo', 'carrier_text', 'lookup_key', 'name', and 'preferences'. The endpoint and an example response for creating a design are provided.
- [Update a personalization design | Stripe API Reference](https://docs.stripe.com/api/issuing/personalization_designs/update): This page describes how to update a Stripe Issuing Personalization Design object via the API. It lists the parameters that can be modified, including card logo, carrier text, lookup key, name, physical bundle, and preferences. The endpoint and an example response for updating a design are provided.
- [Retrieve a personalization design | Stripe API Reference](https://docs.stripe.com/api/issuing/personalization_designs/retrieve): This page explains how to retrieve a specific Personalization Design object using its ID via the Stripe API. It also details how to list all Personalization Designs, with options to filter by lookup keys, preferences, and status. Example requests and responses are provided for both operations.
- [List all personalization designs | Stripe API Reference](https://docs.stripe.com/api/issuing/personalization_designs/list): This page explains how to retrieve a list of Personalization Design objects using the Stripe API, sorted by creation date. It details available parameters for filtering designs by lookup keys, preferences, and status. Example requests and responses are provided for listing designs.
- [Activate a testmode personalization design | Stripe API Reference](https://docs.stripe.com/api/issuing/personalization_designs/activate_testmode): This page describes how to activate, deactivate, or reject a testmode Personalization Design object using Stripe's test helper endpoints. It provides the specific API calls and example responses for changing the status of a personalization design to 'active', 'inactive', or 'rejected'.
- [Deactivate a testmode personalization design | Stripe API Reference](https://docs.stripe.com/api/issuing/personalization_designs/deactivate_testmode): This API endpoint deactivates a testmode personalization design, updating its status to inactive. It requires the ID of the personalization design to be specified in the URL.
- [Reject a testmode personalization design | Stripe API Reference](https://docs.stripe.com/api/issuing/personalization_designs/reject_testmode): This API endpoint rejects a testmode personalization design, updating its status to rejected. It requires the ID of the personalization design and a rejection reason.
- [Physical Bundles | Stripe API Reference](https://docs.stripe.com/api/issuing/physical_bundles): A Physical Bundle represents the physical items shipped with a card, including card stock, carrier letter, and envelope. It has attributes such as ID, name, status (active, inactive, review), and type (custom, standard).
- [The Physical Bundle object | Stripe API Reference](https://docs.stripe.com/api/issuing/physical_bundles/object): The Physical Bundle object details the components of a physical card shipment, including its ID, name, features like card logo requirements, and its status (active, inactive, review). It can be either a standard Stripe offering or custom-made.
- [Retrieve a physical bundle | Stripe API Reference](https://docs.stripe.com/api/issuing/physical_bundles/retrieve): This API endpoint retrieves a specific physical bundle object using its ID. It also provides an endpoint to list all physical bundles, with options to filter by status and type.
- [List all physical bundles | Stripe API Reference](https://docs.stripe.com/api/issuing/physical_bundles/list): This API endpoint returns a list of physical bundle objects, sorted by creation date. You can filter the results by status (active, inactive, review) and type (custom, standard).
- [Tokens | Stripe API Reference](https://docs.stripe.com/api/issuing/tokens): An issuing token object is created when an issued card is added to a digital wallet. Stripe allows card issuers to view and manage these tokens, which include details like the associated card, creation time, and network.
- [The Token object | Stripe API Reference](https://docs.stripe.com/api/issuing/tokens/object): The Token object represents a digital wallet token for an issued card, containing its ID, associated card, creation timestamp, and network information. It also includes the token's status (active, deleted, suspended) and potentially device-specific data.
- [Update a token status | Stripe API Reference](https://docs.stripe.com/api/issuing/tokens/update): This API endpoint updates the status of an Issuing Token object to active, deleted, or suspended. It requires the token's ID and the desired new status. The endpoint returns the updated token object.
- [Retrieve an issuing token | Stripe API Reference](https://docs.stripe.com/api/issuing/tokens/retrieve): This API endpoint retrieves a specific Issuing Token object using its ID. It returns details about the token, including its status, associated card, and network information.
- [List all issuing tokens for card | Stripe API Reference](https://docs.stripe.com/api/issuing/tokens/list): This API endpoint lists all Issuing Token objects for a given card. You can filter tokens by their status (active, deleted, requested, suspended) and creation date. The response includes a list of token objects.
- [Transactions | Stripe API Reference](https://docs.stripe.com/api/issuing/transactions): An Issuing Transaction object represents any use of an issued card that results in funds moving in or out of your Stripe account, such as purchases or refunds. These transactions include details like amount, currency, and type (capture or refund).
- [The Transaction object | Stripe API Reference](https://docs.stripe.com/api/issuing/transactions/object): The Transaction object details financial activities related to issued cards, including the transaction ID, amount, currency, and type (capture or refund). It can be linked to an authorization, card, and cardholder, and may include merchant data.
- [Update a transaction | Stripe API Reference](https://docs.stripe.com/api/issuing/transactions/update): This API endpoint updates an existing Issuing Transaction object by setting specified parameters, such as metadata. Any parameters not provided remain unchanged. The endpoint returns the updated transaction object.
- [Retrieve a transaction | Stripe API Reference](https://docs.stripe.com/api/issuing/transactions/retrieve): This API endpoint retrieves a specific Issuing Transaction object using its ID. It returns detailed information about the transaction, including amount, currency, type, and associated cardholder data.
- [List all transactions | Stripe API Reference](https://docs.stripe.com/api/issuing/transactions/list): This API endpoint returns a list of Issuing Transaction objects, sorted by creation date. You can filter transactions by card, cardholder, creation date, and type (capture or refund).
- [Create a test-mode force capture | Stripe API Reference](https://docs.stripe.com/api/issuing/transactions/test_mode_create_force_capture): This test helper allows the creation of a forced capture transaction for an arbitrary amount. It requires the amount and the associated card, and optionally accepts currency and merchant data.
- [Create a test-mode unlinked refund | Stripe API Reference](https://docs.stripe.com/api/issuing/transactions/test_mode_create_unlinked_refund): This test helper enables the creation of an unlinked refund transaction for an arbitrary amount. It requires the amount and the associated card, and optionally accepts currency and merchant data.
- [Refund a test-mode transaction | Stripe API Reference](https://docs.stripe.com/api/issuing/transactions/test_mode_refund): This test helper allows refunding a test-mode Issuing Transaction. It requires the ID of the transaction to be refunded and the refund amount. The API returns the original transaction object.
- [Connection Token | Stripe API Reference](https://docs.stripe.com/api/terminal/connection_tokens): A Connection Token is used by the Stripe Terminal SDK to connect to a reader. Your backend creates and returns a short-lived connection token, which can be scoped to a specific location for enhanced security.
- [The Connection Token object | Stripe API Reference](https://docs.stripe.com/api/terminal/connection_tokens/object): The Connection Token object represents a short-lived token required by the Stripe Terminal SDK to connect to a reader. It includes a secret for your application to pass to the SDK and an optional location ID for scoping. A connection token is created on your backend server by making a POST request to the Stripe API.
- [Create a Connection Token | Stripe API Reference](https://docs.stripe.com/api/terminal/connection_tokens/create): This page details how to create a connection token for Stripe Terminal. A connection token is a short-lived credential that your server provides to the Stripe Terminal SDK, enabling it to connect to a reader. The API endpoint POST /v1/terminal/connection_tokens is used for this purpose, optionally accepting a location ID.
- [Location | Stripe API Reference](https://docs.stripe.com/api/terminal/locations): A Location in Stripe Terminal represents a physical place where readers are deployed, serving as a grouping mechanism for readers. The API allows for creating, retrieving, updating, listing, and deleting Location objects. Each location has an ID, address, display name, and can store metadata.
- [The Location object | Stripe API Reference](https://docs.stripe.com/api/terminal/locations/object): The Location object in Stripe Terminal defines a physical place and groups readers. It includes attributes like a unique ID, address, display name, and metadata. Locations are essential for organizing and managing readers within your Stripe Terminal setup.
- [Create a Location | Stripe API Reference](https://docs.stripe.com/api/terminal/locations/create): This page describes how to create a new Location object for Stripe Terminal. A location is a grouping of readers and requires an address and a display name. The API endpoint POST /v1/terminal/locations is used, and the creation can optionally include metadata.
- [Update a Location | Stripe API Reference](https://docs.stripe.com/api/terminal/locations/update): This section explains how to update an existing Stripe Terminal Location object. You can modify parameters such as the display name and address, though the country cannot be changed. The API endpoint POST /v1/terminal/locations/:id is used for updates, and it returns the updated Location object.
- [Retrieve a Location | Stripe API Reference](https://docs.stripe.com/api/terminal/locations/retrieve): This page details how to retrieve a specific Stripe Terminal Location object using its ID. The GET /v1/terminal/locations/:id endpoint is used for this purpose. The request returns the full Location object if a valid identifier is provided.
- [List all Locations | Stripe API Reference](https://docs.stripe.com/api/terminal/locations/list): This page describes how to list all Stripe Terminal Location objects. The GET /v1/terminal/locations endpoint returns a list of locations, with options to limit the number of results or paginate using `ending_before` and `starting_after` parameters. The response includes a data array containing Location objects.
- [Delete a Location | Stripe API Reference](https://docs.stripe.com/api/terminal/locations/delete): This page explains how to delete a Stripe Terminal Location object using its ID. The DELETE /v1/terminal/locations/:id endpoint is used for this operation. Upon successful deletion, the API returns the deleted Location object, indicating its deletion status.
- [Reader | Stripe API Reference](https://docs.stripe.com/api/terminal/readers): A Reader in Stripe Terminal represents a physical device used for accepting payment details. The API provides endpoints for creating, retrieving, updating, listing, and deleting readers, as well as for managing reader actions like canceling, collecting input, and processing payments. Readers have attributes such as ID, device type, label, serial number, and status.
- [The Reader object | Stripe API Reference](https://docs.stripe.com/api/terminal/readers/object): The Reader object in Stripe Terminal represents a physical payment device. Key attributes include its unique ID, device type (e.g., Stripe M2, BBPOS WisePad 3), a custom label, associated location ID, serial number, and current status (online/offline). This object is central to managing and interacting with your Stripe payment terminals.
- [Create a Reader | Stripe API Reference](https://docs.stripe.com/api/terminal/readers/create): This page describes how to create a new Stripe Terminal Reader object. A reader is registered using a code provided by the device and is associated with a specific location. You can also assign a custom label and metadata to the reader during creation via the POST /v1/terminal/readers endpoint.
- [Update a Reader | Stripe API Reference](https://docs.stripe.com/api/terminal/readers/update): This section details how to update an existing Stripe Terminal Reader object. You can modify the reader's label and metadata through the POST /v1/terminal/readers/:id endpoint. Any parameters not provided in the update request remain unchanged.
- [Retrieve a Reader | Stripe API Reference](https://docs.stripe.com/api/terminal/readers/retrieve): This page explains how to retrieve a specific Stripe Terminal Reader object using its ID. The GET /v1/terminal/readers/:id endpoint fetches the reader's details, including its ID, device type, label, location, status, and more. The response returns the Reader object if the identifier is valid.
- [List all Readers | Stripe API Reference](https://docs.stripe.com/api/terminal/readers/list): This page describes how to list all Stripe Terminal Reader objects. You can filter the list by device type, location, serial number, or status (online/offline) using query parameters. The GET /v1/terminal/readers endpoint returns a paginated list of Reader objects.
- [Delete a Reader | Stripe API Reference](https://docs.stripe.com/api/terminal/readers/delete): This page explains how to delete a Stripe Terminal Reader object using its ID. The DELETE /v1/terminal/readers/:id endpoint removes the reader from your account. The API returns the deleted Reader object upon successful deletion.
- [Cancel the current reader action | Stripe API Reference](https://docs.stripe.com/api/terminal/readers/cancel_action): This page describes how to cancel the current action being performed by a Stripe Terminal reader. The POST /v1/terminal/readers/:id/cancel_action endpoint can be used to halt ongoing operations. This is useful for programmatic cancellation and returns an updated Reader resource.
- [Collect inputs using a Reader | Stripe API Reference](https://docs.stripe.com/api/terminal/readers/collect_inputs): This page details how to initiate an input collection flow on a Stripe Terminal reader. The POST /v1/terminal/readers/:id/collect_inputs endpoint allows you to display forms for customers to provide information, such as signatures or selections. You can specify multiple inputs, their types, and associated custom text or options.
- [Confirm a PaymentIntent on the Reader | Stripe API Reference](https://docs.stripe.com/api/terminal/readers/confirm_payment_intent): This page explains how to confirm a PaymentIntent on a Stripe Terminal reader. The POST /v1/terminal/readers/:id/confirm_payment_intent endpoint finalizes a payment after card details have been collected. It requires the PaymentIntent ID and returns an updated Reader resource.
- [Hand off a PaymentIntent to a Reader and collect card details | Stripe API Reference](https://docs.stripe.com/api/terminal/readers/collect_payment_method): This page describes how to hand off a PaymentIntent to a Stripe Terminal reader to collect card details. The POST /v1/terminal/readers/:id/collect_payment_method endpoint initiates the payment flow on the reader. The PaymentIntent is updated with card details before manual confirmation, and the API returns an updated Reader resource.
- [Hand-off a PaymentIntent to a Reader | Stripe API Reference](https://docs.stripe.com/api/terminal/readers/process_payment_intent): This page describes how to initiate a payment flow on a Stripe Terminal Reader by processing a PaymentIntent. It details the required `payment_intent` parameter and provides an example API request and response.
- [Hand-off a SetupIntent to a Reader | Stripe API Reference](https://docs.stripe.com/api/terminal/readers/process_setup_intent): This page explains how to initiate a SetupIntent flow on a Stripe Terminal Reader, allowing for saving payment methods without immediate charging. It outlines the `allow_redisplay` and `setup_intent` parameters and includes an example API request and response.
- [Refund a Charge or a PaymentIntent in-person | Stripe API Reference](https://docs.stripe.com/api/terminal/readers/refund_payment): This page details how to initiate an in-person refund for a Charge or PaymentIntent using a Stripe Terminal Reader. It specifies parameters such as `amount`, `charge`, `payment_intent`, and options for refunding application fees or reversing transfers, along with an example API request.
- [Set reader display | Stripe API Reference](https://docs.stripe.com/api/terminal/readers/set_reader_display): This page describes how to set the display on a Stripe Terminal Reader to show cart details, including line items, amounts, and currency. It specifies the `type` parameter as 'cart' and provides an example API request and response.
- [Simulate a successful input collection | Stripe API Reference](https://docs.stripe.com/api/terminal/readers/succeed_input_collection): This page explains how to use a test helper endpoint to simulate a successful input collection on a simulated Stripe Terminal Reader. It details the `skip_non_required_inputs` parameter and provides an example API request and response.
- [Simulate an input collection timeout | Stripe API Reference](https://docs.stripe.com/api/terminal/readers/timeout_input_collection): This page describes how to use a test helper endpoint to simulate an input collection timeout error on a simulated Stripe Terminal Reader. It provides an example API request and response, showing the failure code and message.
- [Simulate presenting a payment method | Stripe API Reference](https://docs.stripe.com/api/terminal/readers/present_payment_method): This page explains how to use a test helper endpoint to simulate presenting a payment method on a simulated Stripe Terminal Reader. This can be used to test scenarios like accepting a payment, saving a card, or refunding a transaction, with examples for different payment types.
- [Terminal Hardware Order | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_orders): This page introduces the TerminalHardwareOrder object, which represents an order for Stripe Terminal hardware. It details the attributes of the object, including its ID, amount, currency, items, payment type, shipping information, and status. The page also lists available endpoints for managing hardware orders.
- [The TerminalHardwareOrder object | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_orders/object): This page provides a detailed description of the TerminalHardwareOrder object in Stripe's API. It lists attributes such as ID, amount, currency, hardware order items, metadata, payment type, shipping details, and status, along with possible values for the status enum.
- [Create a Terminal Hardware Order | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_orders/create): This page describes how to create a new TerminalHardwareOrder object using the Stripe API. It outlines the required parameters, including `hardware_order_items`, `payment_type`, `shipping` address, and `shipping_method`, and provides an example API request and response.
- [Retrieve a Terminal Hardware Order | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_orders/retrieve): This page explains how to retrieve a specific TerminalHardwareOrder object using its ID via the Stripe API. It details the parameters and the expected response, which includes the full details of the requested hardware order.
- [List all Terminal Hardware Orders | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_orders/list): This page describes how to list all TerminalHardwareOrder objects using the Stripe API. It details the available parameters, such as filtering by `status`, and explains the structure of the response, which contains an array of order objects.
- [Cancel a Terminal Hardware Order | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_orders/cancel): This page explains how to cancel a pending Terminal Hardware Order by setting its status to 'canceled' using the Stripe API. It provides the API endpoint and an example request and response showing the updated order status.
- [Preview a Terminal Hardware Order | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_orders/preview): This page describes how to get a preview of a TerminalHardwareOrder without actually creating it, using the Stripe API. It outlines the required parameters, which are similar to the creation endpoint, and explains the response format.
- [Test mode: Mark a Terminal Hardware Order as Delivered | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_orders/test_mode_deliver): This page details how to use a test helper endpoint to mark a test mode TerminalHardwareOrder as 'delivered'. It provides the API endpoint and an example response showing the updated order status.
- [Test mode: Mark a Terminal Hardware Order as Ready To Ship | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_orders/test_mode_mark_ready_to_ship): This page explains how to use a test helper endpoint to update a test mode TerminalHardwareOrder's status to 'ready_to_ship'. It provides the API endpoint and an example response reflecting the status change.
- [Test mode: Mark a Terminal Hardware Order as Shipped | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_orders/test_mode_ship): This page describes how to use a test helper endpoint to mark a test mode TerminalHardwareOrder as 'shipped'. It provides the API endpoint and an example response showing the updated order status.
- [Test mode: Mark a Terminal Hardware Order as Undeliverable | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_orders/test_mode_mark_undeliverable): This page details how to use a test helper endpoint to mark a test mode TerminalHardwareOrder as 'undeliverable'. It provides the API endpoint and an example response showing the updated order status.
- [Terminal Hardware Product | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_products): This page introduces the TerminalHardwareProduct object, representing a category of hardware devices. It describes the object's attributes, including ID, status, type, and when it becomes unavailable, and lists endpoints for retrieving and listing products.
- [The TerminalHardwareProduct object | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_products/object): This page provides a detailed description of the TerminalHardwareProduct object in Stripe's API. It lists attributes such as ID, object type, status, product type, and the `unavailable_after` timestamp, along with examples for retrieving and listing products.
- [Retrieve a Terminal Hardware Product | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_products/retrieve): This page provides details on how to retrieve a specific Terminal Hardware Product using its ID via the Stripe API. It also outlines the parameters and response structure for listing all available Terminal Hardware Products, including filtering by status.
- [List all Terminal Hardware Products | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_products/list): This page explains how to list all Terminal Hardware Products available through the Stripe API. It details the available parameters for filtering the results, such as by product status, and provides an example of the API response.
- [Terminal Hardware SKU | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_skus): This page introduces the TerminalHardwareSKU object in the Stripe API, which represents a Stock Keeping Unit for terminal hardware. It describes the attributes of a SKU, including its ID, price, currency, and status, and provides endpoints for retrieving and listing SKUs.
- [The TerminalHardwareSKU object | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_skus/object): This page details the attributes of the TerminalHardwareSKU object within the Stripe API. It explains each attribute, such as id, amount, currency, country, and status, and provides an example of a SKU object and its associated API endpoints.
- [Retrieve an available Terminal Hardware SKU | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_skus/retrieve): This page describes how to retrieve a specific Terminal Hardware SKU object using its ID via the Stripe API. It outlines the parameters and response structure for this operation and also includes information on listing all Terminal Hardware SKUs.
- [List all Terminal Hardware SKUs | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_skus/list): This page details how to list all Terminal Hardware SKU objects using the Stripe API. It specifies the required 'country' parameter for filtering and lists optional parameters like 'product', 'provider', and 'status', along with an example response.
- [Terminal Hardware Shipping Method | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_shipping_methods): This page introduces the Terminal Hardware Shipping Method object in the Stripe API, representing country-specific shipping options for terminal hardware. It describes the object's attributes, such as ID, country, estimated delivery window, and name, and provides endpoints for retrieving and listing shipping methods.
- [The Terminal Hardware Shipping Method object | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_shipping_methods/object): This page details the attributes of the Terminal Hardware Shipping Method object in the Stripe API. It explains each attribute, including id, country, estimated_delivery_window, and name, and provides an example of a shipping method object along with its associated API endpoints.
- [Retrieve a Terminal Hardware Shipping Method | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_shipping_methods/retrieve): This page explains how to retrieve a specific Terminal Hardware Shipping Method object using its ID via the Stripe API. It also provides details on listing all Terminal Hardware Shipping Methods, including filtering by country, name, and status.
- [List all Terminal Hardware Shipping Methods | Stripe API Reference](https://docs.stripe.com/api/terminal/hardware_shipping_methods/list): This page details how to list all Terminal Hardware Shipping Methods using the Stripe API. It specifies the required 'country' parameter and optional filters like 'name' and 'status', providing an example of the API request and response.
- [Configuration | Stripe API Reference](https://docs.stripe.com/api/terminal/configuration): This page describes the Configuration object in the Stripe API, which is used to define settings for terminal readers. It outlines the attributes of a Configuration object, including device-specific settings and tipping options, and provides endpoints for creating, retrieving, updating, and deleting configurations.
- [The Configuration object | Stripe API Reference](https://docs.stripe.com/api/terminal/configuration/object): This page details the attributes of the Configuration object in the Stripe API, which manages settings for terminal readers. It explains each attribute, such as id, device-specific configurations, tipping settings, and livemode status, and provides an example of a Configuration object and its associated API endpoints.
- [Create a Configuration | Stripe API Reference](https://docs.stripe.com/api/terminal/configuration/create): This page explains how to create and update Configuration objects for Stripe terminal readers via the API. It details the parameters for specifying device-specific settings and other configurations, and provides example API requests and responses for both creation and updates.
- [Update a Configuration | Stripe API Reference](https://docs.stripe.com/api/terminal/configuration/update): This page details how to update a Stripe Terminal Configuration object using its ID. It outlines the parameters for modifying device-specific settings and other configuration options, and provides example API requests and responses for updating a configuration.
- [Retrieve a Configuration | Stripe API Reference](https://docs.stripe.com/api/terminal/configuration/retrieve): This page explains how to retrieve a specific Configuration object for Stripe terminal readers using its ID. It also provides details on listing all configurations, filtering them by account default status, and deleting a configuration object via the API.
- [List all Configurations | Stripe API Reference](https://docs.stripe.com/api/terminal/configuration/list): This page describes how to list all Configuration objects for Stripe terminal readers via the API. It details the available parameters for filtering the results, such as by account default status, and provides an example of the API request and response.
- [Delete a Configuration | Stripe API Reference](https://docs.stripe.com/api/terminal/configuration/delete): This page explains how to delete a Configuration object for Stripe terminal readers using its ID. It outlines the API endpoint and provides an example of the request and the response, which confirms the deletion of the object.
- [Financial Accounts | Stripe API Reference](https://docs.stripe.com/api/treasury/financial_accounts): This page introduces Stripe Treasury's Financial Accounts, which serve as containers for money separate from the Payments balance. It describes the purpose of Financial Accounts as sources and destinations for money movement APIs and lists the available endpoints for managing them.
- [The FinancialAccount object | Stripe API Reference](https://docs.stripe.com/api/treasury/financial_accounts/object): This page details the attributes of the FinancialAccount object within Stripe Treasury. It explains properties such as id, balance, country, features, and status, and provides an example of a FinancialAccount object and its associated API endpoints.
- [Create a FinancialAccount | Stripe API Reference](https://docs.stripe.com/api/treasury/financial_accounts/create): This page explains how to create a new FinancialAccount using the Stripe API, which is part of Stripe Treasury. It details the required 'supported_currencies' parameter and optional parameters for features, metadata, and restrictions, along with an example API request and response.
- [Update a FinancialAccount | Stripe API Reference](https://docs.stripe.com/api/treasury/financial_accounts/update): This page describes how to update a FinancialAccount using the Stripe API. You can modify features, forwarding settings, metadata, nickname, and platform restrictions for a given FinancialAccount.
- [Retrieve a FinancialAccount | Stripe API Reference](https://docs.stripe.com/api/treasury/financial_accounts/retrieve): This page details how to retrieve a FinancialAccount's details using its ID via the Stripe API. It returns the complete FinancialAccount object, including its balance, country, and active features.
- [List all FinancialAccounts | Stripe API Reference](https://docs.stripe.com/api/treasury/financial_accounts/list): This page explains how to list all FinancialAccounts associated with your Stripe account using the API. You can filter the results by creation date and retrieve them in a paginated format.
- [Financial Account Features | Stripe API Reference](https://docs.stripe.com/api/treasury/financial_account_features): This page describes the FinancialAccount Features object in the Stripe API, which encodes a FinancialAccount's access to various features. It outlines the endpoints for updating and retrieving these features, detailing attributes like card issuing, deposit insurance, and transfer capabilities.
- [The FinancialAccount Feature object | Stripe API Reference](https://docs.stripe.com/api/treasury/financial_account_features/object): This page details the attributes of the FinancialAccount Feature object within the Stripe API. It describes various features such as card issuing, deposit insurance, financial addresses, inbound/outbound transfers, and intra-Stripe flows, along with their requested status and associated details.
- [Update FinancialAccount Features | Stripe API Reference](https://docs.stripe.com/api/treasury/financial_account_features/update): This page explains how to update the Features associated with a FinancialAccount using the Stripe API. You can modify settings for features like card issuing, deposit insurance, financial addresses, and various transfer types.
- [Retrieve FinancialAccount Features | Stripe API Reference](https://docs.stripe.com/api/treasury/financial_account_features/retrieve): This page describes how to retrieve the Features information for a specific FinancialAccount using the Stripe API. It returns a dictionary of features, detailing their requested status and any associated status details.
- [Transactions | Stripe API Reference](https://docs.stripe.com/api/treasury/transactions): This page introduces Transactions in the Stripe API, which represent changes to a FinancialAccount's balance. It outlines the endpoints for retrieving single transactions or a list of transactions, and describes the attributes of the Transaction object, including amount, currency, and flow type.
- [The Transaction object | Stripe API Reference](https://docs.stripe.com/api/treasury/transactions/object): This page details the attributes of the Transaction object in the Stripe API. It includes information such as the transaction ID, amount, currency, description, associated financial account, and the type of flow that generated the transaction.
- [Retrieve a Transaction | Stripe API Reference](https://docs.stripe.com/api/treasury/transactions/retrieve): This page explains how to retrieve the details of a specific Transaction using its ID via the Stripe API. It returns a Transaction object, providing information about the amount, balance impact, currency, and associated financial account.
- [List all Transactions | Stripe API Reference](https://docs.stripe.com/api/treasury/transactions/list): This page describes how to list all Transactions for a FinancialAccount using the Stripe API. You can filter transactions by financial account, creation date, and status, and sort them by creation or posted date.
- [Transaction Entries | Stripe API Reference](https://docs.stripe.com/api/treasury/transaction_entries): This page introduces TransactionEntries in the Stripe API, representing individual money movements within a Transaction. It details the endpoints for retrieving single or multiple TransactionEntries and describes the attributes of the TransactionEntry object, including balance impact, currency, and type.
- [The TransactionEntry object | Stripe API Reference](https://docs.stripe.com/api/treasury/transaction_entries/object): This page details the attributes of the TransactionEntry object in the Stripe API. It includes information such as the entry ID, balance impact, currency, effective date, associated financial account, and the specific money movement type that generated the entry.
- [Retrieve a TransactionEntry | Stripe API Reference](https://docs.stripe.com/api/treasury/transaction_entries/retrieve): This page explains how to retrieve a specific TransactionEntry using its ID via the Stripe API. It returns the TransactionEntry object, providing details on its balance impact, currency, effective date, and the associated transaction.
- [List all TransactionEntries | Stripe API Reference](https://docs.stripe.com/api/treasury/transaction_entries/list): This page describes how to list all TransactionEntries associated with a FinancialAccount or a specific Transaction using the Stripe API. You can filter by creation date and order the results by creation or effective date.
- [Outbound Transfers | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_transfers): This page explains how to use OutboundTransfers to move funds from a FinancialAccount to a PaymentMethod belonging to the same entity via ACH or domestic wire. It outlines the API endpoints for creating, retrieving, canceling, and simulating state changes for OutboundTransfers.
- [The OutboundTransfer object | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_transfers/object): This page details the attributes of the OutboundTransfer object in the Stripe API. It includes information such as the transfer amount, currency, description, destination payment method, expected arrival date, and the status of the transfer.
- [Create an OutboundTransfer | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_transfers/create): This page describes how to create an OutboundTransfer using the Stripe API, which moves funds from a FinancialAccount to a specified PaymentMethod. It details the required parameters like amount, currency, and financial account, and optional parameters for description and metadata.
- [Retrieve an OutboundTransfer | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_transfers/retrieve): This page explains how to retrieve the details of an existing OutboundTransfer using its unique ID via the Stripe API. It returns the OutboundTransfer object, providing information on its status, amount, destination, and expected arrival date.
- [List all OutboundTransfers | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_transfers/list): This page describes how to list OutboundTransfers sent from a specified FinancialAccount using the Stripe API. You can filter the results by the status of the transfer (e.g., processing, posted, failed) and retrieve them in a paginated format.
- [Cancel an OutboundTransfer | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_transfers/cancel): This page details how to cancel an OutboundTransfer via the Stripe API, which is possible only if the funds have not yet been paid out. It outlines the API endpoint and provides an example response. The page also briefly mentions how to transition a test mode OutboundTransfer to a failed state.
- [Test mode: Fail an OutboundTransfer | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_transfers/test_mode_fail): This document explains how to transition a test mode OutboundTransfer to a 'failed' status using the Stripe API. It specifies that the OutboundTransfer must be in the processing state and cannot already be failed or un-failiable. The page includes the relevant API endpoint and an example response.
- [Test mode: Post an OutboundTransfer | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_transfers/test_mode_post): This page describes how to transition a test mode OutboundTransfer to a 'posted' status using the Stripe API. The OutboundTransfer must be in a processable state and not already posted or un-postable. The documentation provides the API endpoint and a sample response for this operation.
- [Test mode: Return an OutboundTransfer | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_transfers/test_mode_return): This Stripe API documentation explains how to transition a test mode OutboundTransfer to a 'returned' status. The transfer must be in a processable state and not already returned or un-returnable. The page details the API endpoint and includes an example response, noting that `returned_details` can be provided.
- [Test mode: Update an OutboundTransfer | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_transfers/test_mode_update): This page details how to update a test mode OutboundTransfer with tracking information using the Stripe API. The OutboundTransfer must not be cancelable and cannot be in a canceled or failed state. The documentation provides the API endpoint and an example of a successful response with added tracking details.
- [Outbound Payments | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_payments): This page introduces Stripe's OutboundPayments API, used to send funds to external bank accounts or other FinancialAccounts, differentiating it from OutboundTransfers which are for same-user accounts. It lists available endpoints for managing OutboundPayments, including creation, retrieval, cancellation, and test helper functions for state transitions. Key attributes of the OutboundPayment object are also described.
- [The Outbound Payment object | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_payments/object): This document details the attributes of the Stripe OutboundPayment object, including its ID, amount, currency, and status. It explains fields like `destination_payment_method_details`, `end_user_details`, and `returned_details`. The object's attributes provide comprehensive information about outbound payment transactions.
- [Create an OutboundPayment | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_payments/create): This page describes how to create an OutboundPayment using the Stripe API, specifying required parameters like amount, currency, and financial account. It details optional parameters such as customer, description, and payment method details, and outlines the expected response upon successful creation. The endpoint for creating OutboundPayments is also provided.
- [Retrieve an OutboundPayment | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_payments/retrieve): This Stripe API documentation explains how to retrieve an existing OutboundPayment by its ID. It provides the GET endpoint and an example response showing the details of a processing OutboundPayment. The page also describes how to list all OutboundPayments, detailing available filter parameters like financial account, customer, and status.
- [List all OutboundPayments | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_payments/list): This page details how to list all OutboundPayments associated with a specific FinancialAccount using the Stripe API. It outlines the available query parameters for filtering results by financial account, creation date, customer, and status. An example API call and its response are provided, showing a list of OutboundPayments.
- [Cancel an OutboundPayment | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_payments/cancel): This document explains how to cancel an OutboundPayment using the Stripe API, which can only be done if the payment is not yet canceled or cannot be canceled. It provides the API endpoint and an example response showing a successfully canceled OutboundPayment. The page also briefly covers test mode operations for failing an OutboundPayment.
- [Test mode: Fail an OutboundPayment | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_payments/test_mode_fail): This page details how to transition a test mode OutboundPayment to a 'failed' status using the Stripe API. The OutboundPayment must be in the processing state and not already failed or un-failiable. The documentation includes the relevant API endpoint and an example response for this test helper operation.
- [Test mode: Post an OutboundPayment | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_payments/test_mode_post): This Stripe API documentation explains how to transition a test mode OutboundPayment to a 'posted' status. The OutboundPayment must be in the processing state and not already posted or un-postable. The page provides the API endpoint and an example response demonstrating a successful transition to the posted state.
- [Test mode: Return an OutboundPayment | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_payments/test_mode_return): This page describes how to transition a test mode OutboundPayment to a 'returned' status using the Stripe API. The OutboundPayment must be in the processing state and not already returned or un-returnable. The documentation includes the API endpoint and an example response, noting the optional `returned_details` parameter.
- [Test mode: Update an OutboundPayment | Stripe API Reference](https://docs.stripe.com/api/treasury/outbound_payments/test_mode_update): This page details how to update a test mode OutboundPayment with tracking information using the Stripe API. The OutboundPayment must not be cancelable and cannot be in a canceled or failed state. The documentation provides the API endpoint and an example response showing a successfully updated OutboundPayment with tracking details.
- [Inbound Transfers | Stripe API Reference](https://docs.stripe.com/api/treasury/inbound_transfers): This page introduces Stripe's InboundTransfers API, used to add funds to a FinancialAccount from a PaymentMethod owned by the user, typically via ACH debit. It lists endpoints for managing InboundTransfers, including creation, retrieval, cancellation, and test helper functions for state transitions. Key attributes of the InboundTransfer object are also described.
- [The InboundTransfer object | Stripe API Reference](https://docs.stripe.com/api/treasury/inbound_transfers/object): This document details the attributes of the Stripe InboundTransfer object, such as ID, amount, currency, and status. It explains fields like `failure_details`, `financial_account`, and `origin_payment_method_details`. The object's attributes provide comprehensive information about inbound transfer transactions.
- [Create an InboundTransfer | Stripe API Reference](https://docs.stripe.com/api/treasury/inbound_transfers/create): This page explains how to create an InboundTransfer using the Stripe API, requiring parameters like amount, currency, financial account, and origin payment method. It details optional parameters such as description and metadata, and outlines the expected response upon successful creation, which will have a 'processing' status. The API endpoint for creating InboundTransfers is provided.
- [Retrieve an InboundTransfer | Stripe API Reference](https://docs.stripe.com/api/treasury/inbound_transfers/retrieve): This Stripe API documentation explains how to retrieve an existing InboundTransfer by its ID. It provides the GET endpoint and an example response showing the details of a processing InboundTransfer. The page also describes how to list all InboundTransfers, detailing available filter parameters like financial account and status.
- [List all InboundTransfers | Stripe API Reference](https://docs.stripe.com/api/treasury/inbound_transfers/list): This page details how to list all InboundTransfers associated with a specific FinancialAccount using the Stripe API. It outlines the available query parameters for filtering results by financial account and status. An example API call and its response are provided, showing a list of InboundTransfers currently in a processing state.
- [Cancel an InboundTransfer | Stripe API Reference](https://docs.stripe.com/api/treasury/inbound_transfers/cancel): This page details how to cancel an InboundTransfer using the Stripe API. It provides the endpoint and example request/response for canceling an existing InboundTransfer.
- [Test mode: Fail an InboundTransfer | Stripe API Reference](https://docs.stripe.com/api/treasury/inbound_transfers/test_mode_fail): This page explains how to transition a test mode InboundTransfer to a 'failed' status using the Stripe API. It specifies the required parameters and provides an example of the API call and its response.
- [Test mode: Return an InboundTransfer | Stripe API Reference](https://docs.stripe.com/api/treasury/inbound_transfers/test_mode_return): This page describes how to mark a test mode InboundTransfer as 'returned' via the Stripe API. It outlines the endpoint and provides an example of the request and response for this operation.
- [Test mode: Succeed an InboundTransfer | Stripe API Reference](https://docs.stripe.com/api/treasury/inbound_transfers/test_mode_succeed): This page details the process of transitioning a test mode InboundTransfer to a 'succeeded' status using the Stripe API. It includes the relevant endpoint, parameters, and an example of the API call and its response.
- [Received Credits | Stripe API Reference](https://docs.stripe.com/api/treasury/received_credits): This page introduces ReceivedCredits in Stripe, which represent funds sent to a FinancialAccount not initiated by the account itself. It lists available endpoints for retrieving and creating ReceivedCredits, and details the attributes of the ReceivedCredit object.
- [The ReceivedCredit object | Stripe API Reference](https://docs.stripe.com/api/treasury/received_credits/object): This page provides a detailed description of the Stripe ReceivedCredit object, outlining its attributes such as ID, amount, currency, and status. It explains possible failure codes and details about the initiating payment method and linked flows.
- [Retrieve a ReceivedCredit | Stripe API Reference](https://docs.stripe.com/api/treasury/received_credits/retrieve): This page explains how to retrieve a specific ReceivedCredit using its ID via the Stripe API. It also details how to list all ReceivedCredits, with options to filter by financial account, linked flows, and status.
- [List all ReceivedCredits | Stripe API Reference](https://docs.stripe.com/api/treasury/received_credits/list): This page describes how to list all ReceivedCredits in Stripe, with options to filter by financial account, linked flows, and status. It provides the API endpoint and an example of the request and response.
- [Test mode: Create a ReceivedCredit | Stripe API Reference](https://docs.stripe.com/api/treasury/received_credits/test_mode_create): This page details how to simulate a test mode ReceivedCredit using the Stripe API. It outlines the required parameters such as amount, currency, and financial account, and provides an example of the API call and its response.
- [Received Debits | Stripe API Reference](https://docs.stripe.com/api/treasury/received_debits): This page introduces Stripe ReceivedDebits, which represent funds pulled from a FinancialAccount. It lists endpoints for retrieving and creating ReceivedDebits and details the attributes of the ReceivedDebit object.
- [The ReceivedDebit object | Stripe API Reference](https://docs.stripe.com/api/treasury/received_debits/object): This page provides a detailed description of the Stripe ReceivedDebit object, including its attributes like ID, amount, currency, and status. It explains possible failure codes and details about the initiating payment method and linked flows.
- [Retrieve a ReceivedDebit | Stripe API Reference](https://docs.stripe.com/api/treasury/received_debits/retrieve): This page explains how to retrieve a specific ReceivedDebit using its ID via the Stripe API. It also details how to list all ReceivedDebits, with options to filter by financial account and status.
- [List all ReceivedDebits | Stripe API Reference](https://docs.stripe.com/api/treasury/received_debits/list): This page describes how to list all ReceivedDebits in Stripe, with options to filter by financial account and status. It provides the API endpoint and an example of the request and response.
- [Test mode: Create a ReceivedDebit | Stripe API Reference](https://docs.stripe.com/api/treasury/received_debits/test_mode_create): This page details how to simulate a test mode ReceivedDebit using the Stripe API. It outlines the required parameters such as amount, currency, and financial account, and provides an example of the API call and its response.
- [Credit Reversals | Stripe API Reference](https://docs.stripe.com/api/treasury/credit_reversals): This page introduces CreditReversals in Stripe, which are used to reverse certain ReceivedCredits. It lists endpoints for creating and retrieving CreditReversals and details the attributes of the CreditReversal object.
- [The CreditReversal object | Stripe API Reference](https://docs.stripe.com/api/treasury/credit_reversals/object): This page provides a detailed description of the Stripe CreditReversal object, including its attributes such as ID, amount, currency, and status. It explains the different statuses a CreditReversal can have and related transactions.
- [Create a CreditReversal | Stripe API Reference](https://docs.stripe.com/api/treasury/credit_reversals/create): This page explains how to create a CreditReversal to reverse a ReceivedCredit using the Stripe API. It specifies the required 'received_credit' parameter and provides an example of the API call and its response.
- [Retrieve a CreditReversal | Stripe API Reference](https://docs.stripe.com/api/treasury/credit_reversals/retrieve): This page explains how to retrieve a specific CreditReversal using its ID via the Stripe API. It also details how to list all CreditReversals, with options to filter by financial account, received credit, and status.
- [List all CreditReversals | Stripe API Reference](https://docs.stripe.com/api/treasury/credit_reversals/list): This page describes how to list all CreditReversals in Stripe, with options to filter by financial account, received credit, and status. It provides the API endpoint and an example of the request and response.
- [Debit Reversals | Stripe API Reference](https://docs.stripe.com/api/treasury/debit_reversals): This page introduces DebitReversals in Stripe, which are used to reverse certain ReceivedDebits. It lists endpoints for creating and retrieving DebitReversals and details the attributes of the DebitReversal object.
- [The DebitReversal object | Stripe API Reference](https://docs.stripe.com/api/treasury/debit_reversals/object): The DebitReversal object in Stripe represents a reversal of a ReceivedDebit, allowing funds to be moved back. It includes details such as the amount, currency, status (processing, succeeded, failed), and associated financial accounts and transactions. The object also tracks network used and timestamps for status transitions.
- [Create a DebitReversal | Stripe API Reference](https://docs.stripe.com/api/treasury/debit_reversals/create): This Stripe API endpoint allows for the creation of a DebitReversal object, which reverses a previously received debit. It requires the ID of the ReceivedDebit to be reversed and optionally accepts metadata. The API returns the newly created DebitReversal object upon successful creation.
- [Retrieve a DebitReversal | Stripe API Reference](https://docs.stripe.com/api/treasury/debit_reversals/retrieve): This Stripe API endpoint retrieves a specific DebitReversal object using its unique ID. It returns the details of the DebitReversal, including its ID, amount, currency, status, and associated financial account and transaction information. No parameters are required for this retrieval operation.
- [List all DebitReversals | Stripe API Reference](https://docs.stripe.com/api/treasury/debit_reversals/list): This Stripe API endpoint lists all DebitReversals, with options to filter by financial account or a specific ReceivedDebit. You can also filter by resolution status (lost or won) and the overall status (canceled, completed, processing). Pagination parameters like `ending_before` and `starting_after` are available for managing large result sets.
- [Payment Records | Stripe API Reference](https://docs.stripe.com/api/payment-record): A Payment Record in Stripe represents payments that occur either on or off the Stripe platform, enabling the modeling of external payments to update Invoices or Subscriptions. It comprises one or more Payment Attempt Records, detailing individual payment network interactions. The Payment Record object includes attributes like ID, amount details (requested, authorized, failed, guaranteed, refunded, canceled), customer information, and payment method details.
- [The Payment Record object | Stripe API Reference](https://docs.stripe.com/api/payment-record/object): The Payment Record object in Stripe details various aspects of a payment, including its ID, requested, authorized, guaranteed, failed, and refunded amounts. It also captures customer and payment method specifics, shipping details, and a description. The object can store custom metadata and indicates whether the customer was present during the transaction.
- [Retrieve a Payment Record | Stripe API Reference](https://docs.stripe.com/api/payment-record/retrieve): This Stripe API endpoint retrieves a specific Payment Record using its unique ID. It returns a detailed Payment Record object, including amounts, customer details, payment method information, and shipping details. This is useful for checking the status and details of a payment that has been reported.
- [Report a payment | Stripe API Reference](https://docs.stripe.com/api/payment-record/report): The 'Report a payment' endpoint in Stripe allows for the creation of a new Payment Record or updating an existing one with terminal states. It requires essential details such as the requested amount, initiation time, payment method, and processor information. Optional parameters include customer details, description, and outcome (failed, guaranteed).
- [Report a payment attempt | Stripe API Reference](https://docs.stripe.com/api/payment-record/report-payment-attempt/report): This Stripe API endpoint reports a new payment attempt on a specified Payment Record. It requires the Payment Record ID and the initiation time of the payment attempt. You can also provide details about failures, guarantees, payment methods, and shipping. This endpoint is used to update the status of a payment attempt.
- [Report a refund | Stripe API Reference](https://docs.stripe.com/api/payment-record/report-refund/report): The 'Report a refund' endpoint in Stripe allows you to record that a refund has occurred for a specific Payment Record. You must provide the Payment Record ID and specify the refund outcome as 'refunded'. Details about the refunded amount and initiation time can also be included, along with processor-specific information.
- [Report payment attempt canceled | Stripe API Reference](https://docs.stripe.com/api/payment-record/report-payment-attempt-canceled/report): This Stripe API endpoint reports that the most recent payment attempt on a Payment Record has been canceled. It requires the Payment Record ID and the timestamp when the cancellation occurred. This action updates the Payment Record to reflect the canceled attempt, provided it hasn't already been guaranteed.
- [Report payment attempt failed | Stripe API Reference](https://docs.stripe.com/api/payment-record/report-payment-attempt-failed/report): This Stripe API endpoint reports that the most recent payment attempt on a Payment Record has failed or encountered an error. It requires the Payment Record ID and the timestamp of the failure. This updates the Payment Record to reflect the failed attempt, unless the attempt has already been guaranteed.
- [Report payment attempt guaranteed | Stripe API Reference](https://docs.stripe.com/api/payment-record/report-payment-attempt-guaranteed/report): This Stripe API endpoint reports that the most recent payment attempt on a Payment Record has been guaranteed. It requires the Payment Record ID and the timestamp when the guarantee occurred. This updates the Payment Record to reflect the guaranteed status, preventing further modifications to that specific attempt.
- [Report payment attempt informational | Stripe API Reference](https://docs.stripe.com/api/payment-record/report-payment-attempt-informational/report): This Stripe API endpoint allows reporting informational updates for a Payment Record. You can provide new customer details, a description, shipping information, and metadata. This is useful for adding context or updating non-financial details about a payment without changing its core financial status.
- [Payment Attempt Records | Stripe API Reference](https://docs.stripe.com/api/payment-attempt-record): A Payment Attempt Record in Stripe represents a single attempt to process a payment, linked to a Payment Record. It details the amount intended for collection and tracks various states like authorized, guaranteed, failed, canceled, and refunded. Each Payment Attempt Record includes customer and payment method information, as well as processor-specific details.
- [The Payment Attempt Record object | Stripe API Reference](https://docs.stripe.com/api/payment-attempt-record/object): The Payment Attempt Record object in Stripe uniquely identifies an individual payment attempt, including its ID and associated Payment Record. It captures details on amounts requested, authorized, guaranteed, failed, canceled, and refunded. The object also stores customer and payment method specifics, along with processor and shipping information.
- [Retrieve a Payment Attempt Record | Stripe API Reference](https://docs.stripe.com/api/payment-attempt-record/retrieve): This Stripe API endpoint retrieves a specific Payment Attempt Record using its unique ID. It returns a detailed object containing information about the payment attempt, such as amounts, timestamps, customer details, and payment method specifics. This is useful for inspecting the status and details of individual payment attempts.
- [List Payment Attempt Records | Stripe API Reference](https://docs.stripe.com/api/payment-attempt-record/list): This Stripe API endpoint lists all Payment Attempt Records associated with a specific Payment Record. It requires the Payment Record ID and allows for pagination using `limit` and `starting_after` parameters. The response includes an array of Payment Attempt Record objects.
- [Feature | Stripe API Reference](https://docs.stripe.com/api/entitlements/feature): A feature in Stripe represents a monetizable capability or functionality that can be assigned to products. When a product with an assigned feature is purchased, Stripe creates an entitlement for the customer to use that feature. The Feature object includes a unique ID, a lookup key, a name, and metadata.
- [The Feature object | Stripe API Reference](https://docs.stripe.com/api/entitlements/feature/object): The Feature object in Stripe defines a monetizable aspect of a product, identified by a unique ID, lookup key, and name. It can be marked as active or inactive and may include custom metadata. This object is fundamental for managing entitlements when products are purchased.
- [Create a feature | Stripe API Reference](https://docs.stripe.com/api/entitlements/feature/create): This page details how to create a feature using the Stripe API. It outlines the required parameters, such as a unique lookup key and a name for the feature. The response includes the newly created feature object with its ID and other attributes.
- [List all features | Stripe API Reference](https://docs.stripe.com/api/entitlements/feature/list): This page explains how to list all features available in your Stripe account via the API. You can filter the list by archived status or a specific lookup key. The response returns a list of feature objects, each containing details like ID, name, and metadata.
- [Updates a feature | Stripe API Reference](https://docs.stripe.com/api/entitlements/feature/updates): This page describes how to update an existing feature in Stripe using the API. You can modify the feature's metadata or its active status. The API call returns the updated feature object, reflecting the changes made.
- [Product Feature | Stripe API Reference](https://docs.stripe.com/api/product-feature): This page introduces the Product Feature object, which links a feature to a product in Stripe. When a product with an attached feature is purchased, Stripe automatically creates an entitlement for the customer. It covers endpoints for listing, attaching, and detaching features from products.
- [The ProductFeature object | Stripe API Reference](https://docs.stripe.com/api/product-feature/object): This page details the Product Feature object in Stripe, representing the association between a product and a feature. It outlines the object's attributes, such as its unique ID and the attached entitlement feature. The page also provides information on listing, attaching, and detaching features from products.
- [List all features attached to a product | Stripe API Reference](https://docs.stripe.com/api/product-feature/list): This page explains how to retrieve a list of all features attached to a specific product using the Stripe API. It covers the endpoint for this operation and provides an example of the response, which includes a list of product feature objects. The page also details how to attach and detach features from products.
- [Attach a feature to a product | Stripe API Reference](https://docs.stripe.com/api/product-feature/attach): This page describes how to attach a feature to a product using the Stripe API. This action creates a product_feature object, linking the specified feature to the product. The API call requires the feature's ID and returns the created product_feature object.
- [Remove a feature from a product | Stripe API Reference](https://docs.stripe.com/api/product-feature/remove): This page explains how to remove a feature from a product using the Stripe API. This action deletes the product_feature object that links the feature to the product. The API call returns an object confirming the deletion if successful.
- [Active Entitlement | Stripe API Reference](https://docs.stripe.com/api/entitlements/active-entitlement): This page defines an active entitlement as a customer's access to a specific feature within Stripe. It covers the API endpoints for retrieving a single active entitlement by its ID or listing all active entitlements for a given customer. The Active Entitlement object includes the feature's ID and lookup key.
- [The Active Entitlement object | Stripe API Reference](https://docs.stripe.com/api/entitlements/active-entitlement/object): This page details the Active Entitlement object in Stripe, which represents a customer's access to a feature. It lists the object's attributes, including its ID, the associated feature, and its lookup key. The page also provides information on retrieving and listing active entitlements.
- [Retrieve an active entitlement | Stripe API Reference](https://docs.stripe.com/api/entitlements/active-entitlement/retrieve): This page explains how to retrieve a specific active entitlement for a customer using the Stripe API. It details the required `id` parameter for the entitlement and shows an example of the API response. The page also covers listing all active entitlements for a customer.
- [List all active entitlements | Stripe API Reference](https://docs.stripe.com/api/entitlements/active-entitlement/list): This page describes how to list all active entitlements for a specific customer using the Stripe API. It outlines the required `customer` parameter and provides an example of the API response, which is a list of active entitlement objects. The page also details how to retrieve a single active entitlement.
- [Scheduled Queries | Stripe API Reference](https://docs.stripe.com/api/sigma/scheduled_queries): This page introduces Stripe Sigma's Scheduled Queries, which allow users to run custom SQL queries against their Stripe data. It explains that a `sigma.scheduled_query_run.created` webhook is sent upon query completion, containing a Scheduled Query object with results. The page covers endpoints for retrieving individual and all scheduled query runs.
- [The Scheduled Query object | Stripe API Reference](https://docs.stripe.com/api/sigma/scheduled_queries/object): This page details the Scheduled Query object in Stripe Sigma, representing the result of a scheduled SQL query. It outlines the object's attributes, including its ID, the SQL query used, its status (completed, failed, etc.), and a link to the file containing the results. The page also covers retrieving scheduled query runs.
- [Retrieve a scheduled query run | Stripe API Reference](https://docs.stripe.com/api/sigma/scheduled_queries/retrieve): This page explains how to retrieve a specific scheduled query run from Stripe Sigma using its ID. It details the API endpoint and provides an example of the response, which includes the query's SQL, status, and a link to the result file. The page also covers listing all scheduled query runs.
- [List all scheduled query runs | Stripe API Reference](https://docs.stripe.com/api/sigma/scheduled_queries/list): This page describes how to list all scheduled query runs in Stripe Sigma. It provides the API endpoint for this operation and an example response containing a list of scheduled query run objects. Each object includes details like the query's status and a link to its results file.
- [Report Runs | Stripe API Reference](https://docs.stripe.com/api/reporting/report_run): This page introduces the Stripe Report Run object, which represents an instance of a generated report with specific parameters. Once created, Stripe processes the report and provides a file reference for the results upon completion. It covers endpoints for creating, retrieving, and listing report runs.
- [The Report Run object | Stripe API Reference](https://docs.stripe.com/api/reporting/report_run/object): This page details the Stripe Report Run object, which represents a generated report instance. It outlines the object's attributes, including its ID, the report type, status (pending, succeeded, failed), and parameters used. The page also covers creating, retrieving, and listing report runs.
- [Create a Report Run | Stripe API Reference](https://docs.stripe.com/api/reporting/report_run/create): This page explains how to create a new report run using the Stripe API. This action initiates the generation of a report based on the specified `report_type` and parameters. The API call returns the newly created ReportRun object, which includes its status and other details.
- [Retrieve a Report Run | Stripe API Reference](https://docs.stripe.com/api/reporting/report_run/retrieve): This page describes how to retrieve details of an existing Stripe Report Run using its ID. It provides the API endpoint and an example of the response, which includes the report's status, parameters, and a link to the result file if successful. The page also covers creating and listing report runs.
- [List all Report Runs | Stripe API Reference](https://docs.stripe.com/api/reporting/report_run/list): This API endpoint allows you to list all report runs, ordered by most recent first. You can filter these reports by creation date and specify limits for the number of results returned. The response includes an array of ReportRun objects, each containing details about a specific report execution.
- [Report Types | Stripe API Reference](https://docs.stripe.com/api/reporting/report_type): This page describes the Report Type resource, which represents a specific kind of report like 'Activity summary' or 'Itemized payouts'. Report Types are identified by an ID and have associated parameters, some of which may require a live-mode API key. The response provides details such as the report type ID, availability dates, default columns, and version.
- [The Report Type object | Stripe API Reference](https://docs.stripe.com/api/reporting/report_type/object): This page details the attributes of the Report Type object, including its ID, human-readable name, and data availability windows. It also specifies default columns and live mode status. An example JSON object illustrates the structure of a Report Type, such as 'Balance summary'.
- [Retrieve a Report Type | Stripe API Reference](https://docs.stripe.com/api/reporting/report_type/retrieve): This API endpoint retrieves the details of a specific Report Type, identified by its ID. It's noted that some report types require a live-mode API key for access. The endpoint returns the ReportType object if found, otherwise it raises an error.
- [List all Report Types | Stripe API Reference](https://docs.stripe.com/api/reporting/report_type/list): This API endpoint returns a full list of available Report Types. Each Report Type object in the response includes its ID, name, data availability, default columns, and live mode status. The response is structured as a list with a 'data' property containing the ReportType objects.
- [Accounts | Stripe API Reference](https://docs.stripe.com/api/financial_connections/accounts): A Financial Connections Account represents an external account to which you have been granted access. This page outlines the available endpoints for managing these accounts, including retrieving, disconnecting, refreshing, and subscribing to data updates. The Account object attributes are detailed, such as ID, category, institution name, and balance information.
- [The Account object | Stripe API Reference](https://docs.stripe.com/api/financial_connections/accounts/object): This page describes the attributes of the Financial Connections Account object. Key details include the account's ID, holder information, balance, category (cash, credit, investment, other), and institution name. It also covers status, permissions, and supported payment method types.
- [Retrieve an Account | Stripe API Reference](https://docs.stripe.com/api/financial_connections/accounts/retrieve): This API endpoint retrieves the details of a specific Financial Connections Account using its ID. The response includes comprehensive information about the account, such as its holder, balance, category, and institution. The page also provides details on how to list all Financial Connections Accounts.
- [List Accounts | Stripe API Reference](https://docs.stripe.com/api/financial_connections/accounts/list): This API endpoint returns a list of Financial Connections Account objects. You can filter accounts by the account holder or a specific session. The response is a dictionary containing a 'data' property, which is an array of Account objects, along with pagination information.
- [Disconnect an Account | Stripe API Reference](https://docs.stripe.com/api/financial_connections/accounts/disconnect): This API endpoint allows you to disconnect a Financial Connections Account, disabling access to its data like balances and transactions. The response returns the updated Account object with its status changed to 'disconnected'. The page also describes how to refresh account data.
- [Refresh Account data | Stripe API Reference](https://docs.stripe.com/api/financial_connections/accounts/refresh): This API endpoint refreshes data associated with a Financial Connections Account, allowing you to specify which features (balance, ownership, transactions) to update. The response returns the Account object with updated balance or transaction refresh status. The page also covers subscribing and unsubscribing from data refreshes.
- [Subscribe to data refreshes for an Account | Stripe API Reference](https://docs.stripe.com/api/financial_connections/accounts/subscribe): This API endpoint subscribes to periodic refreshes of data for a Financial Connections Account, typically daily for active accounts. You specify the features (e.g., transactions) to subscribe to. The response returns the Account object, indicating the active subscriptions for data refreshes.
- [Unsubscribe from data refreshes for an Account | Stripe API Reference](https://docs.stripe.com/api/financial_connections/accounts/unsubscribe): This API endpoint allows you to unsubscribe from periodic data refreshes for a Financial Connections Account. You specify the features you wish to stop receiving updates for, such as transactions. The response returns the Account object with updated subscription status.
- [Account Owner | Stripe API Reference](https://docs.stripe.com/api/financial_connections/ownership): This page describes the Account Owner object, which represents an individual owner of a Financial Connections Account. Attributes include the owner's ID, name, email, and phone number. It also details the Account Ownership object, which groups owners for a specific account, and provides an endpoint to list all owners for an account.
- [The Account Owner object | Stripe API Reference](https://docs.stripe.com/api/financial_connections/ownership/owner-object): This page details the attributes of the Account Owner object, including its unique ID, email, name, and phone number. It also describes the Account Ownership object, which contains a list of owners associated with an account. An example JSON for both objects is provided.
- [The Account Ownership object | Stripe API Reference](https://docs.stripe.com/api/financial_connections/ownership/object): This API endpoint lists all owners for a given Financial Connections Account Ownership object, identified by its ID. The response is a dictionary containing a 'data' property, which is an array of owner objects. Pagination parameters can be used to control the number of results returned.
- [List Account Owners | Stripe API Reference](https://docs.stripe.com/api/financial_connections/ownership/list): This API endpoint lists all owners associated with a specific Financial Connections Account Ownership object. The response provides an array of owner objects, each containing details like ID, name, and email. Pagination parameters are available to manage the results.
- [Session | Stripe API Reference](https://docs.stripe.com/api/financial_connections/sessions): A Financial Connections Session is used to securely launch the client-side Stripe.js modal, enabling users to link their external accounts. This page outlines the Session object's attributes, such as ID, account holder details, requested permissions (balances, ownership, transactions), and filters. It also describes endpoints for creating and retrieving sessions.
- [The Session object | Stripe API Reference](https://docs.stripe.com/api/financial_connections/sessions/object): This page details the attributes of the Financial Connections Session object. Key information includes the session ID, client secret for launching the flow, account holder, collected accounts, requested permissions, and filters. It also mentions prefetch options for data features upon account creation.
- [Create a Session | Stripe API Reference](https://docs.stripe.com/api/financial_connections/sessions/create): This API endpoint creates a Session to launch the Financial Connections authorization flow, returning a Session object with a client_secret for use with Stripe.js. You must specify the account holder and the requested permissions for data access. Filters can be applied to restrict the types of accounts collected, and prefetch options can be set for data features.
- [Retrieve a Session | Stripe API Reference](https://docs.stripe.com/api/financial_connections/sessions/retrieve): This page describes how to retrieve details of a Financial Connections Session using its ID. It outlines the GET request format and provides an example of the expected Session object response.
- [Transactions | Stripe API Reference](https://docs.stripe.com/api/financial_connections/transactions): This page details the Transaction object within Stripe's Financial Connections API. It explains that a Transaction represents a real financial event affecting an account balance and lists its attributes, including ID, amount, currency, description, and status.
- [The Transaction object | Stripe API Reference](https://docs.stripe.com/api/financial_connections/transactions/object): This page provides a comprehensive description of the Stripe Financial Connections Transaction object. It details the attributes such as ID, account, amount, currency, description, status, and timestamps related to transaction updates.
- [Retrieve a Transaction | Stripe API Reference](https://docs.stripe.com/api/financial-connections/transaction/retrieve): This page explains how to retrieve a specific Financial Connections Transaction using its ID via the Stripe API. It includes the GET request endpoint and an example response object detailing the transaction's properties.
- [List Transactions | Stripe API Reference](https://docs.stripe.com/api/financial_connections/transactions/list): This page describes how to list Financial Connections Transactions for a given account using the Stripe API. It outlines the required 'account' parameter and optional filters like 'transacted_at' and 'limit', along with an example API request and response.
- [Tax Calculations | Stripe API Reference](https://docs.stripe.com/api/tax/calculations): This page introduces Stripe's Tax Calculations API, which allows for the calculation of taxes to be collected from customers. It details the available endpoints for creating calculations, retrieving line items, and retrieving calculation objects, along with the attributes of a Tax Calculation object.
- [The Tax Calculation object | Stripe API Reference](https://docs.stripe.com/api/tax/calculations/object): This page details the Stripe Tax Calculation object, outlining its attributes such as ID, total amount, currency, customer details, expiration time, and tax amounts. It also describes the nested objects for line items, shipping costs, and tax breakdown.
- [Create a Tax Calculation | Stripe API Reference](https://docs.stripe.com/api/tax/calculations/create): This page explains how to create a Tax Calculation using the Stripe API, which determines the tax to be collected from a customer. It lists the required parameters like currency, line items, and customer details, and provides an example POST request and the resulting Tax Calculation object.
- [Retrieve a calculation's line items | Stripe API Reference](https://docs.stripe.com/api/tax/calculations/line_items): This page describes how to retrieve the line items associated with a specific tax calculation using the Stripe API. It details the GET request endpoint, available pagination parameters (ending_before, limit, starting_after), and the structure of the returned list of Line Item objects.
- [Retrieve a Tax Calculation | Stripe API Reference](https://docs.stripe.com/api/tax/calculations/retrieve): This page explains how to retrieve a specific Tax Calculation object using its ID via the Stripe API. It details the GET request endpoint and provides an example response object, noting that calculations expire and cannot be retrieved after expiration.
- [Tax Registrations | Stripe API Reference](https://docs.stripe.com/api/tax/registrations): This page introduces Stripe's Tax Registrations API, which allows businesses to register for tax collection in specific regions. It explains the purpose of a Tax Registration object and lists the available endpoints for creating, retrieving, and updating registrations, along with the attributes of the Tax Registration object.
- [The Tax Registration object | Stripe API Reference](https://docs.stripe.com/api/tax/registrations/object): This page details the Stripe Tax Registration object, outlining its attributes such as ID, active status, country, and expiration date. It also describes the country-specific options and the different possible statuses for a registration.
- [Create a registration | Stripe API Reference](https://docs.stripe.com/api/tax/registrations/create): This page describes how to create a new Tax Registration object using the Stripe API. It specifies the required parameters, including the start date, country, and country-specific options, and provides an example POST request and the resulting Tax Registration object.
- [Update a registration | Stripe API Reference](https://docs.stripe.com/api/tax/registrations/update): This page explains how to update an existing Tax Registration object via the Stripe API. It details the parameters for modifying the active start and expiration dates and provides an example POST request for updating a registration, noting that registrations cannot be deleted but can be expired.
- [Retrieve a registration | Stripe API Reference](https://docs.stripe.com/api/tax/registrations/retrieve): This page describes how to retrieve a specific Tax Registration object using its ID via the Stripe API. It provides the GET request endpoint and an example response object, detailing the registration's active status, country, and associated options.
- [List registrations | Stripe API Reference](https://docs.stripe.com/api/tax/registrations/all): This page details how to list Tax Registrations using the Stripe API, allowing retrieval of active, expired, scheduled, or all registrations. It outlines the available parameters for filtering by status and for pagination, along with an example API request and response.
- [Tax Transactions | Stripe API Reference](https://docs.stripe.com/api/tax/transactions): This page introduces Stripe's Tax Transactions API, which records tax collected from or refunded to customers. It lists endpoints for creating reversals, creating from calculations, retrieving transactions, and retrieving transaction line items, and describes the attributes of a Tax Transaction object.
- [The Tax Transaction object | Stripe API Reference](https://docs.stripe.com/api/tax/transactions/object): This page provides a detailed description of the Stripe Tax Transaction object. It outlines the attributes such as ID, currency, customer details, line items, reference, and type (transaction or reversal), along with timestamps and other related information.
- [Create a reversal transaction | Stripe API Reference](https://docs.stripe.com/api/tax/transactions/create_reversal): This page explains how to create a reversal for a previously created tax transaction using the Stripe API. It details the 'mode' parameter (full or partial), the required 'original_transaction' ID, and options for specifying amounts or line items to reverse, returning a new Tax Transaction object representing the reversal.
- [Create a transaction from a calculation | Stripe API Reference](https://docs.stripe.com/api/tax/transactions/create_from_calculation): This page describes how to create a Tax Transaction from a prior Tax Calculation using the Stripe API. It specifies the required 'calculation' ID and 'reference' for the transaction, and provides an example POST request and the resulting Tax Transaction object, noting that calculations expire after 90 days.
- [Retrieve a transaction | Stripe API Reference](https://docs.stripe.com/api/tax/transactions/retrieve): This page describes how to retrieve a specific Tax Transaction object using its ID. It outlines the parameters (none required) and the structure of the returned Tax Transaction object, including details like currency, customer information, and line items.
- [Retrieve a transaction's line items | Stripe API Reference](https://docs.stripe.com/api/tax/transactions/line_items): This page explains how to retrieve the line items associated with a committed standalone tax transaction. It details the available parameters for pagination and limiting results, and describes the structure of the returned list of Line Item objects.
- [Tax Settings | Stripe API Reference](https://docs.stripe.com/api/tax/settings): This page covers Stripe Tax Settings, which manage configurations for tax calculations. It details the endpoints for retrieving and updating these settings, including attributes like head office location and tax behavior defaults. The status of the settings, whether active or pending, is also explained.
- [The Tax Setting object | Stripe API Reference](https://docs.stripe.com/api/tax/settings/object): This page describes the Stripe Tax Setting object, which holds configurations for tax calculations. It details attributes such as the object type, default tax behavior and codes, head office location, and live mode status. The page also explains how to update these settings.
- [Update settings | Stripe API Reference](https://docs.stripe.com/api/tax/settings/update): This page details how to update Stripe Tax Settings, which are used for tax calculations. It explains that all parameters are editable and describes the parameters for default configurations and head office location. The page also includes the endpoint for updating settings and an example response.
- [Retrieve settings | Stripe API Reference](https://docs.stripe.com/api/tax/settings/retrieve): This page explains how to retrieve the merchant's Tax Settings using the Stripe API. It details the endpoint and provides an example response showing the structure of the Tax Settings object, including defaults and head office information.
- [Tax Association | Stripe API Reference](https://docs.stripe.com/api/tax/associations): This page introduces the Tax Association, which links Tax Transactions to PaymentIntents. It describes the attributes of the Tax Association object, such as its ID, calculation, and payment intent, as well as the attempts made to create tax transactions. The page also details how to find a tax association using a PaymentIntent ID.
- [The Tax Association object | Stripe API Reference](https://docs.stripe.com/api/tax/associations/object): This page describes the Stripe Tax Association object, which connects Tax Transactions to PaymentIntents. It details attributes like ID, calculation, and payment intent, and lists tax transaction attempts. The page also explains how to find a tax association by providing a PaymentIntent ID.
- [Find a Tax Association | Stripe API Reference](https://docs.stripe.com/api/tax/associations/find): This page describes how to find a tax association object using a PaymentIntent ID. It details the required 'payment_intent' parameter and the structure of the returned Tax Association object, which includes the calculation ID and associated tax transaction attempts.
- [Verification Session | Stripe API Reference](https://docs.stripe.com/api/identity/verification_sessions): This page introduces the VerificationSession, a tool for collecting and verifying user identities. It explains that a VerificationSession guides the verification process, contains details about the checks performed, and transitions through various statuses. The page also lists the available endpoints for managing VerificationSessions.
- [The VerificationSession object | Stripe API Reference](https://docs.stripe.com/api/identity/verification_sessions/object): This page details the attributes of the Stripe VerificationSession object. It includes the session ID, client reference ID, client secret for Stripe.js integration, creation timestamp, and status. The object also contains information about the last error, last verification report, and live mode status.
- [Create a VerificationSession | Stripe API Reference](https://docs.stripe.com/api/identity/verification_sessions/create): This page explains how to create a VerificationSession to collect and verify user identities. It describes the parameters for creating a session, such as client reference ID, metadata, options for verification checks, and the return URL. The page also notes that test mode verification checks are not processed.
- [Update a VerificationSession | Stripe API Reference](https://docs.stripe.com/api/identity/verification_sessions/update): This page describes how to update a VerificationSession, particularly when its status is 'requires_input'. It details the parameters that can be updated, including metadata, options for verification checks, and the type of check. The page also covers retrieving a VerificationSession and provides an example of updating a session.
- [Retrieve a VerificationSession | Stripe API Reference](https://docs.stripe.com/api/identity/verification_sessions/retrieve): This page explains how to retrieve details of a previously created VerificationSession. It is useful when the session status is 'requires_input' to obtain a valid client_secret or URL for re-submission. The page also details how to list all VerificationSessions with various filtering options.
- [List VerificationSessions | Stripe API Reference](https://docs.stripe.com/api/identity/verification_sessions/list): This page describes how to list VerificationSessions with filtering capabilities. It details parameters such as client_reference_id, creation date, related customer, and status. The response includes a list of VerificationSession objects matching the specified criteria.
- [Cancel a VerificationSession | Stripe API Reference](https://docs.stripe.com/api/identity/verification_sessions/cancel): This page explains how to cancel a VerificationSession when it is in the 'requires_input' status. Once canceled, future submission attempts are disabled and this action cannot be undone. The page provides the endpoint for cancellation and an example of the response.
- [Redact a VerificationSession | Stripe API Reference](https://docs.stripe.com/api/identity/verification_sessions/redact): This page describes how to redact a VerificationSession to remove all collected personal information from Stripe. Redaction can be performed on sessions in 'requires_input' or 'verified' status and is irreversible. The process can take up to four days, and redacted objects are marked with placeholders.
- [Verification Report | Stripe API Reference](https://docs.stripe.com/api/identity/verification_reports): This page introduces the VerificationReport, which is the result of an attempt to collect and verify user data. It explains that the report contains the outcome of specific verification checks (document, id_number, selfie) and includes collected data and reference IDs. To configure and create reports, use the VerificationSession API.
- [The VerificationReport object | Stripe API Reference](https://docs.stripe.com/api/identity/verification_reports/object): This page details the attributes of the Stripe VerificationReport object, including its ID, creation timestamp, and status. It outlines the results of various checks such as document, email, ID number, phone, and selfie verification. The page also specifies the type of report and the associated VerificationSession.
- [Retrieve a VerificationReport | Stripe API Reference](https://docs.stripe.com/api/identity/verification_reports/retrieve): This page explains how to retrieve an existing VerificationReport using its ID. It also details how to list all verification reports with options to filter by client reference ID, creation date, type, or the associated VerificationSession. The response includes a list of VerificationReport objects.
- [List VerificationReports | Stripe API Reference](https://docs.stripe.com/api/identity/verification_reports/list): This page describes how to list verification reports using the Stripe API. It details the available parameters for filtering reports, such as client reference ID, creation date, type, and verification session ID. The response format includes a list of verification report objects.
- [Climate Order | Stripe API Reference](https://docs.stripe.com/api/climate/order): This page introduces the Stripe Climate Order object, which represents an intent to purchase a specific Climate product. Creating an order deducts payment from the merchant's balance and provides details about the order, including amounts, beneficiary, and timestamps for creation, confirmation, and cancellation.
- [The Climate order object | Stripe API Reference](https://docs.stripe.com/api/climate/order/object): This page details the attributes of the Stripe Climate order object. It covers identifiers, amounts (fees, subtotal, total), beneficiary information, and timestamps for various order states like cancellation and confirmation. It also includes details on delivery and product information.
- [Create an order | Stripe API Reference](https://docs.stripe.com/api/climate/order/create): This page explains how to create a Stripe Climate order, which represents an intent to purchase carbon removal. Orders are processed immediately, and payment is deducted from your Stripe balance. Key parameters include the product ID, amount or metric tons, currency, and optional metadata.
- [Update an order | Stripe API Reference](https://docs.stripe.com/api/climate/order/update): This page describes how to update an existing Stripe Climate order. Updates can be made to parameters like the beneficiary and metadata. The endpoint allows for modification of specific order details after its initial creation.
- [Retrieve an order | Stripe API Reference](https://docs.stripe.com/api/climate/order/retrieve): This page details how to retrieve a specific Climate order object by its ID using the Stripe API. It also covers listing all Climate orders, which are returned sorted by creation date. Parameters for listing include pagination options like `ending_before` and `starting_after`.
- [List orders | Stripe API Reference](https://docs.stripe.com/api/climate/order/list): This page explains how to list all Climate order objects using the Stripe API, sorted by creation date. It also details how to cancel a Climate order, noting that cancellations are possible within 24 hours of creation and may result in partial refunds. Frontier may also cancel orders with advance notice.
- [Cancel an order | Stripe API Reference](https://docs.stripe.com/api/climate/order/cancel): This page describes how to cancel a Stripe Climate order, which can be done within 24 hours of creation. User-initiated cancellations refund the subtotal but not the fees, while Frontier-initiated cancellations due to supplier failure refund the total amount with advance notice.
- [Climate Product | Stripe API Reference](https://docs.stripe.com/api/climate/product): This page introduces the Stripe Climate Product object, representing a type of carbon removal unit. It details how to retrieve a specific product or list all available products to check current pricing and availability. The product object includes information on its ID, name, pricing, delivery year, and suppliers.
- [The Climate product object | Stripe API Reference](https://docs.stripe.com/api/climate/product/object): This page details the attributes of the Stripe Climate Product object. It includes the product's unique ID, name, creation timestamp, current pricing per metric ton (including fees and subtotals), expected delivery year, available metric tons, and associated suppliers.
- [Retrieve a product | Stripe API Reference](https://docs.stripe.com/api/climate/product/retrieve): This page explains how to retrieve a specific Climate product object by its ID using the Stripe API. It also covers listing all available Climate product objects, which can be filtered using pagination parameters. Each product object provides details on pricing, availability, and suppliers.
- [List products | Stripe API Reference](https://docs.stripe.com/api/climate/product/list): This page details how to list all available Climate product objects using the Stripe API. It also covers retrieving a specific Climate product by its ID. The product object provides information such as its ID, name, current pricing, delivery year, available quantity, and the suppliers involved.
- [Climate Supplier | Stripe API Reference](https://docs.stripe.com/api/climate/supplier): This page introduces the Stripe Climate Supplier object, which represents a provider of carbon removal services. It outlines how to retrieve a specific supplier or list all suppliers to view details about their operations. The supplier object includes an ID, name, information URL, operational locations, and the removal pathway.
- [The Climate supplier object | Stripe API Reference](https://docs.stripe.com/api/climate/supplier/object): This page details the attributes of the Stripe Climate Supplier object. It includes the supplier's unique ID, name, a URL for more information, and details about their operational locations and the specific carbon removal pathway they utilize. The object also indicates whether it is in live or test mode.
- [Retrieve a supplier | Stripe API Reference](https://docs.stripe.com/api/climate/supplier/retrieve): This page explains how to retrieve a specific Climate supplier object by its ID using the Stripe API. It also covers listing all available Climate supplier objects. Each supplier object provides information such as its ID, name, contact URL, operational locations, and the carbon removal method used.
- [List suppliers | Stripe API Reference](https://docs.stripe.com/api/climate/supplier/list): This page details how to list all available Climate supplier objects using the Stripe API. It also covers retrieving a specific supplier by its ID. The supplier object provides information on its ID, name, contact URL, operational locations, and the carbon removal pathway.
- [Forwarding Request | Stripe API Reference](https://docs.stripe.com/api/forwarding/request): This page describes the Stripe Forwarding Request object, which allows Stripe to make a request on your behalf to a destination URL using your credentials. Stripe redacts sensitive information before storing the request and response data for 30 days. It supports synchronous requests and requires specific configurations for the destination URL.
- [The ForwardingRequest object | Stripe API Reference](https://docs.stripe.com/api/forwarding/request/object): This page details the attributes of the Stripe ForwardingRequest object. It includes the request's ID, creation timestamp, live mode status, metadata, the payment method used, and details about the request itself (body, headers, URL). It also contains information about the request context and the redacted response received.
- [Create a ForwardingRequest | Stripe API Reference](https://docs.stripe.com/api/forwarding/forwarding_requests/create): This page explains how to create a Stripe ForwardingRequest object. This allows Stripe to make a request to a specified destination URL using provided payment method details and request parameters. Key parameters include the payment method, fields to replace (like card number), the request body and headers, and the destination URL.
- [Retrieve a ForwardingRequest | Stripe API Reference](https://docs.stripe.com/api/forwarding/forwarding_requests/retrieve): This page details how to retrieve a specific ForwardingRequest object by its ID using the Stripe API. It also covers listing all ForwardingRequest objects, which can be filtered by creation date and paginated. The ForwardingRequest object contains information about the forwarded request, its context, and the redacted response.
- [List all ForwardingRequests | Stripe API Reference](https://docs.stripe.com/api/forwarding/forwarding_requests/list): This page details how to list all ForwardingRequest objects using the Stripe API. It outlines the available parameters for filtering and pagination, such as created timestamp, starting_after, and limit. The response format includes a list of ForwardingRequest objects with their details.
- [Redaction Job | Stripe API Reference](https://docs.stripe.com/api/privacy/redaction-job): This page introduces the Redaction Job object in Stripe, which is used to permanently remove personal information from selected objects. It lists the available API endpoints for managing redaction jobs, including creating, canceling, running, and validating them. The page also describes the attributes and possible statuses of a Redaction Job.
- [The Redaction Job object | Stripe API Reference](https://docs.stripe.com/api/privacy/redaction-job/object): This page provides a detailed description of the Redaction Job object in the Stripe API. It outlines the object's attributes such as ID, creation timestamp, live mode status, and the status of the redaction process. The page also explains the 'objects' attribute for specifying items to redact and the 'validation_behavior' for handling redaction eligibility.
- [Create a redaction job | Stripe API Reference](https://docs.stripe.com/api/privacy/redaction-job/create): This page explains how to create a redaction job using the Stripe API to remove personal information from specified objects. It details the required 'objects' parameter and the optional 'validation_behavior' parameter, which can be set to 'error' or 'fix'. The response includes the newly created RedactionJob object with its initial status.
- [Update a redaction job | Stripe API Reference](https://docs.stripe.com/api/privacy/redaction-job/update): This page describes how to update a redaction job in Stripe without running or canceling it. It details the parameters available for updating, including the redaction job's ID and its validation behavior. The page also covers retrieving and listing redaction jobs, and notes that failed jobs may require re-validation after updates.
- [Retrieve a redaction job | Stripe API Reference](https://docs.stripe.com/api/privacy/redaction-job/retrieve): This page explains how to retrieve the details of a specific redaction job using its ID via the Stripe API. It also details how to list all redaction jobs with options for pagination. Additionally, it describes how to cancel a redaction job that is in a 'ready' or 'failed' status, and how to run a job that is in a 'ready' status.
- [List all redaction jobs | Stripe API Reference](https://docs.stripe.com/api/privacy/redaction-job/list): This page provides information on how to list all redaction jobs in Stripe, including parameters for pagination like 'ending_before' and 'starting_after'. It also details the process of canceling a redaction job, which abandons the redaction of configured objects and cannot be undone. Furthermore, it explains how to run a redaction job, which initiates an irreversible asynchronous redaction process.
- [Cancel a redaction job | Stripe API Reference](https://docs.stripe.com/api/privacy/redaction-job/cancel): This page details how to cancel a Stripe redaction job, which can be done when the job is in a 'ready' or 'failed' status. Canceling abandons the redaction process and makes the job unusable. It also describes how to run a redaction job, initiating an irreversible asynchronous redaction process that changes the job's status to 'redacting' and eventually 'succeeded'. The page also mentions the ability to validate a redaction job.
- [Run a redaction job | Stripe API Reference](https://docs.stripe.com/api/privacy/redaction-job/run): This page explains how to run a Stripe redaction job, which redacts configured objects asynchronously and irreversibly. When run, the job status changes to 'redacting' and then 'succeeded' upon completion, with potential automatic fixes applied if 'validation_behavior' is set to 'fix'. It also covers validating a redaction job, which checks objects for redaction eligibility and can change the job status to 'validating', 'ready', or 'failed'.
- [Validate a redaction job | Stripe API Reference](https://docs.stripe.com/api/privacy/redaction-job/validate): This page describes how to validate a Stripe redaction job, which is automatically initiated upon creation and can be re-triggered if the job is in a 'failed' status or if the 'validation_behavior' changes. The validation process updates the job's status to 'validating', and upon completion, it becomes 'ready' if successful or 'failed' if errors persist. This validation ensures objects are eligible for redaction.
- [Redaction Job Validation Error | Stripe API Reference](https://docs.stripe.com/api/privacy/redaction-job-validation-error): This page introduces the Redaction Job Validation Error object in Stripe, which provides details about errors preventing object redaction. It lists the API endpoint for retrieving these errors and describes the attributes of a validation error, including a unique ID, error code, the specific object causing the error, and a human-readable message.
- [The Redaction Job Validation Error object | Stripe API Reference](https://docs.stripe.com/api/privacy/redaction-job-validation-error/object): This page details the attributes of the Redaction Job Validation Error object in the Stripe API. It includes the error's ID, type, a code indicating the reason for the error (e.g., 'invalid_state', 'locked_by_other_job'), an optional reference to the object causing the error, and a descriptive message. This information helps in resolving issues that prevent redaction.
- [List all validation errors | Stripe API Reference](https://docs.stripe.com/api/privacy/redaction-job-validation-error/list): This page explains how to list all validation errors for a specific Stripe redaction job using its ID. It details the parameters available for pagination, such as 'ending_before' and 'starting_after'. The response provides a list of Redaction Job validation error objects, each containing details about the specific error encountered.
- [Webhook Endpoints | Stripe API Reference](https://docs.stripe.com/api/webhook_endpoints): This page describes Stripe's Webhook Endpoints API, allowing users to configure endpoints to receive notifications about events. While most users set up webhooks via the dashboard, the API provides programmatic control. It lists the available endpoints for managing webhook endpoints, including creating, retrieving, updating, and deleting them.
- [The Webhook Endpoint object | Stripe API Reference](https://docs.stripe.com/api/webhook_endpoints/object): This page details the attributes of the Webhook Endpoint object in the Stripe API. It includes identifiers, API version, description, enabled events, metadata, secret (for signature generation), status, and URL. The object also contains information about the associated application and creation timestamp.
- [Create a webhook endpoint | Stripe API Reference](https://docs.stripe.com/api/webhook_endpoints/create): This page explains how to create a webhook endpoint using the Stripe API. A URL and a list of enabled events are required, with an option to specify a 'connect' parameter for handling events from connected accounts. The page lists various events that can be enabled, such as 'charge.succeeded' and 'account.updated'.
- [Update a webhook endpoint | Stripe API Reference](https://docs.stripe.com/api/webhook_endpoints/update): This page describes how to update an existing webhook endpoint via the Stripe API. Users can modify the endpoint's URL, the list of enabled events, and its status. Optional parameters like description and metadata can also be updated. The page lists numerous available events that can be configured for the endpoint.
- [Retrieve a webhook endpoint | Stripe API Reference](https://docs.stripe.com/api/webhook_endpoints/retrieve): This page explains how to retrieve a specific webhook endpoint by its ID using the Stripe API. It also details how to list all webhook endpoints associated with an account, with options for pagination. The response for listing endpoints includes an array of webhook endpoint objects, each containing details like ID, URL, and enabled events.
- [List all webhook endpoints | Stripe API Reference](https://docs.stripe.com/api/webhook_endpoints/list): This page describes how to list all webhook endpoints for a Stripe account, including parameters for pagination like 'limit' and 'starting_after'. It also covers deleting a webhook endpoint using its ID via the API or the Stripe dashboard. The deletion process returns an object confirming the deleted endpoint's ID.
- [Delete a webhook endpoint | Stripe API Reference](https://docs.stripe.com/api/webhook_endpoints/delete): This page details how to delete a webhook endpoint using its ID via the Stripe API. The deletion can also be performed through the Stripe dashboard. Upon successful deletion, the API returns an object confirming the deleted webhook endpoint's ID. This action is irreversible.
- [Stripe CLI Reference](https://docs.stripe.com/cli): The Stripe CLI provides a command-line interface for interacting with Stripe. It allows developers to manage their Stripe account, test integrations, and automate workflows directly from their terminal. This reference covers various commands and functionalities available through the CLI.
- [Stripe CLI Reference](https://docs.stripe.com/cli/login): The `stripe login` command authenticates your Stripe CLI with your Stripe account. This is a necessary first step to use most other CLI commands that interact with your Stripe data. It securely links your local environment to your Stripe dashboard.
- [Stripe CLI Reference](https://docs.stripe.com/cli/api_keys): This section of the Stripe CLI reference details how to manage API keys. It explains how to view, create, and revoke API keys directly from the command line. Proper management of API keys is crucial for securing your Stripe integration.
- [Stripe CLI Reference](https://docs.stripe.com/cli/config): The `stripe config` command allows you to view and set configuration options for the Stripe CLI. You can manage settings such as the default Stripe account and output formats. This helps tailor the CLI experience to your specific needs.
- [Stripe CLI Reference](https://docs.stripe.com/cli/completion): This page explains how to set up shell command completion for the Stripe CLI. Enabling completion significantly speeds up command entry by offering suggestions as you type. It supports various shells like Bash, Zsh, and Fish.
- [Stripe CLI Reference](https://docs.stripe.com/cli/flags): The Stripe CLI reference on flags covers global and command-specific options that modify command behavior. Flags allow for fine-grained control over CLI operations, such as specifying output formats or targeting specific Stripe resources. Understanding flags is key to efficient CLI usage.
- [Stripe CLI Reference](https://docs.stripe.com/cli/intro_stripe): This introductory guide to Stripe within the CLI explains its core purpose and benefits. It highlights how the CLI simplifies common Stripe-related tasks for developers. The CLI acts as a powerful tool for managing and testing Stripe integrations.
- [Stripe CLI Reference](https://docs.stripe.com/cli/logs/tail): The `stripe logs tail` command streams your Stripe logs in real-time to your terminal. This is invaluable for debugging webhook events and monitoring API activity as it happens. It provides immediate feedback on incoming requests and responses.
- [Stripe CLI Reference](https://docs.stripe.com/cli/open): The `stripe open` command provides a quick way to open specific Stripe resources in your web browser. You can use it to open your Stripe dashboard, specific API resources, or even documentation pages. This streamlines navigation between your local development and the Stripe dashboard.
- [Stripe CLI Reference](https://docs.stripe.com/cli/intro_webhooks): This introduction to Stripe webhooks via the CLI explains how to receive and inspect webhook events locally. It demonstrates how the CLI can simulate webhook delivery, making it easier to test your webhook handlers. This simplifies the development and testing of event-driven Stripe features.
- [Stripe CLI Reference](https://docs.stripe.com/cli/listen): The `stripe listen` command forwards events from Stripe to your local development environment. It allows you to test webhook endpoints without deploying your application. This is essential for developing and debugging integrations that rely on Stripe events.
- [Stripe CLI Reference](https://docs.stripe.com/cli/trigger): The `stripe trigger` command allows you to manually trigger Stripe events from the command line. This is useful for testing specific event flows and ensuring your application responds correctly. It provides a way to simulate various scenarios without requiring actual user actions.
- [Stripe CLI Reference](https://docs.stripe.com/cli/events/resend): The `stripe events resend` command enables you to resend specific Stripe events. This is helpful for replaying events during testing or recovery scenarios. It ensures that your application can handle events even if there were temporary processing issues.
- [Stripe CLI Reference](https://docs.stripe.com/cli/intro_resources_http): This section introduces how to interact with Stripe resources using HTTP methods via the CLI. It covers basic operations like GET, POST, DELETE, and PATCH for managing Stripe objects. This provides a low-level way to interact with the Stripe API directly.
- [Stripe CLI Reference](https://docs.stripe.com/cli/resources): The `stripe resources` command provides general information and commands related to Stripe resources. It acts as a gateway to managing various Stripe objects through the CLI. This section offers an overview of how to work with different Stripe entities.
- [Stripe CLI Reference](https://docs.stripe.com/cli/get): The `stripe get` command retrieves specific Stripe resources or lists of resources. It allows you to fetch data about customers, payments, and other objects from your Stripe account. This is a fundamental command for inspecting your Stripe data.
- [Stripe CLI Reference](https://docs.stripe.com/cli/post): The `stripe post` command sends POST requests to the Stripe API, typically used for creating new resources. You can use it to create customers, charges, and other objects. This command is essential for adding data to your Stripe account programmatically.
- [Stripe CLI Reference](https://docs.stripe.com/cli/delete): The `stripe delete` command removes Stripe resources from your account. Use this command with caution to delete objects like customers or subscriptions. It provides a direct way to clean up or remove data via the CLI.
- [Stripe CLI Reference](https://docs.stripe.com/cli/fixtures): The `stripe fixtures` command helps you create sample data within your Stripe account. It allows you to populate your Stripe environment with test customers, products, and other resources. This is invaluable for setting up consistent testing environments.
- [Stripe CLI Reference](https://docs.stripe.com/cli/intro_stripe_samples): This introduction to Stripe samples within the CLI explains how to use the command-line tool to work with sample Stripe integrations. It demonstrates how to download, run, and customize official Stripe code samples. This helps developers quickly get started with common Stripe use cases.
- [Stripe CLI Reference](https://docs.stripe.com/cli/samples/create): The Stripe CLI's 'samples create' command generates sample Stripe integrations. It helps developers quickly set up and test different payment flows and features.
- [Stripe CLI Reference](https://docs.stripe.com/cli/samples/list): The Stripe CLI's 'samples list' command displays available sample Stripe integrations. Developers can use this to discover and choose which samples to download or use.
- [Stripe CLI Reference](https://docs.stripe.com/cli/serve): The Stripe CLI's 'serve' command runs a local development server. It allows developers to test webhooks and other server-side logic without deploying to a live environment.
- [Stripe CLI Reference](https://docs.stripe.com/cli/intro_additional_commands): This section of the Stripe CLI reference covers additional commands beyond the core functionality. It provides details on less common but useful CLI operations.
- [Stripe CLI Reference](https://docs.stripe.com/cli/terminal/quickstart): This Stripe CLI quickstart guide focuses on integrating Stripe Terminal. It provides step-by-step instructions for setting up and using the Terminal SDK in a development environment.
- [Stripe CLI Reference](https://docs.stripe.com/cli/logout): The Stripe CLI's 'logout' command revokes authentication for the CLI. This is useful for switching accounts or securing your development environment.
- [Stripe CLI Reference](https://docs.stripe.com/cli/feedback): The Stripe CLI's 'feedback' command allows users to send feedback directly to Stripe. It's a channel for reporting issues or suggesting improvements for the CLI tool.
- [Stripe CLI Reference](https://docs.stripe.com/cli/help): The Stripe CLI's 'help' command provides documentation and usage information for all available commands. It's the primary resource for understanding how to use the CLI.
- [Stripe CLI Reference](https://docs.stripe.com/cli/version): The Stripe CLI's 'version' command displays the currently installed version of the Stripe CLI. This is helpful for troubleshooting and ensuring compatibility.
- [Stripe CLI Reference](https://docs.stripe.com/cli/intro_further_information): This section of the Stripe CLI reference provides further information and resources. It guides users on where to find additional help and advanced topics related to the CLI.
- [Stripe CLI Reference](https://docs.stripe.com/cli/docker): This Stripe CLI documentation covers using Docker with the CLI. It explains how to run the Stripe CLI within a Docker container for consistent development environments.
- [Stripe CLI Reference](https://docs.stripe.com/cli/telemetry): The Stripe CLI's 'telemetry' command manages data collection settings. It allows users to enable or disable sending usage data to Stripe for product improvement.
- [Stripe CLI Reference](https://docs.stripe.com/cli/license): The Stripe CLI's 'license' command displays the software license. It outlines the terms and conditions for using the Stripe Command Line Interface.
- [Stripe JS Reference](https://docs.stripe.com/js): This Stripe JS reference provides an overview of the Stripe JavaScript library. It enables developers to securely collect payment information and integrate Stripe payments directly into web applications.
- [Stripe JS Reference](https://docs.stripe.com/js/including): This Stripe JS documentation explains how to include the Stripe.js library in your web project. It covers different methods for adding the script to your HTML or JavaScript files.
- [Stripe JS Reference](https://docs.stripe.com/js/initializing): This Stripe JS reference details how to initialize Stripe.js in your application. It covers setting up the Stripe object with your publishable key to enable Stripe functionality.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object): This Stripe JS documentation describes the Elements object. It is a core component for building customizable and secure payment forms within your web application.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/create): This Stripe JS reference explains how to create Elements instances using the Elements object. It details the process of generating UI components for payment collection.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/create_without_intent): This Stripe JS documentation covers creating Elements without a PaymentIntent. It provides guidance on setting up payment UI components when a PaymentIntent is not immediately available.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/update): This Stripe JS reference details how to update Elements instances. It explains how to modify the appearance and behavior of payment UI components after they have been created.
- [Stripe JS Reference](https://docs.stripe.com/js/element/events/on_update_end): This page details how to listen for and handle the 'update:end' event on Stripe Elements. This event fires after an Element has finished updating its internal state, providing a way to react to changes in real-time.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/fetch_updates): This page explains how to fetch updates for Stripe Elements using the Elements object. It covers the methods and parameters required to retrieve the latest information or state changes for your payment elements.
- [Stripe JS Reference](https://docs.stripe.com/js/elements/submit): This page describes the process of submitting Stripe Elements. It outlines the necessary JavaScript functions and considerations for securely sending payment details to Stripe for processing.
- [Stripe JS Reference](https://docs.stripe.com/js/element): This page serves as a general reference for Stripe Elements. It provides an overview of what Elements are, their purpose in collecting payment information, and how they integrate into your payment flow.
- [Stripe JS Reference](https://docs.stripe.com/js/element/payment_element): This page focuses on the Payment Element, a pre-built UI component from Stripe. It explains how the Payment Element simplifies the checkout process by offering multiple payment methods in a single integration.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/create_payment_element): This page details how to create a Payment Element using the Stripe Elements object. It outlines the JavaScript code required to instantiate and mount the Payment Element on your webpage.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/get_payment_element): This page explains how to retrieve an existing Payment Element instance from the Stripe Elements object. This is useful for interacting with a Payment Element that has already been created.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/update_payment_element): This page describes how to update the configuration or appearance of a Stripe Payment Element after it has been created. It covers the methods available for dynamically modifying the element's behavior or presentation.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/collapse_payment_element): This page details how to collapse a Stripe Payment Element. This functionality allows you to hide or minimize the Payment Element, often used in responsive designs or after certain actions are completed.
- [Stripe JS Reference](https://docs.stripe.com/js/element/express_checkout_element): This page introduces the Express Checkout Element, a Stripe UI component designed for faster, more streamlined checkouts. It simplifies the integration of express payment methods like Shop Pay.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/create_express_checkout_element): This page explains how to create an Express Checkout Element using the Stripe Elements object. It provides the JavaScript code necessary to integrate this element into your site for quick payment processing.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/get_express_checkout_element): This page describes how to get a reference to an already created Express Checkout Element. This allows you to interact with the element programmatically after its initial setup.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/update_express_checkout_element): This page details how to update the Express Checkout Element. It covers the methods for modifying its properties or appearance dynamically after it has been rendered on the page.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/express_checkout_element_click_event): This page explains the 'click' event for the Stripe Express Checkout Element. It covers how to listen for and respond when a user clicks on the Express Checkout Element, enabling custom interactions.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/express_checkout_element_confirm_event): This page details the 'confirm' event for the Stripe Express Checkout Element. This event signifies that a payment confirmation has been initiated or completed, allowing you to handle post-confirmation logic.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/express_checkout_element_cancel_event): This page describes the 'cancel' event for the Stripe Express Checkout Element. It explains how to detect when a user cancels the express checkout flow and implement appropriate actions.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/express_checkout_element_shippingaddresschange_event): This page focuses on the 'shippingaddresschange' event for the Stripe Express Checkout Element. It explains how to capture changes in the shipping address provided by the user and update the order accordingly.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/express_checkout_element_shippingratechange_event): This page details the 'shippingratechange' event for the Stripe Express Checkout Element. It covers how to detect when a user selects a different shipping rate and update the total order cost.
- [Stripe JS Reference](https://docs.stripe.com/js/element/link_authentication_element): This page introduces the Link Authentication Element, a Stripe UI component for collecting user authentication details. It simplifies the process of verifying customer identities for payments.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/create_link_authentication_element): This page explains how to create a Link Authentication Element using the Stripe Elements object. It provides the JavaScript code to integrate this element for secure user authentication during checkout.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/get_link_authentication_element): This page provides documentation for the Stripe JS `getLinkAuthenticationElement` method. It explains how to retrieve an existing Link Authentication Element instance from the Elements API. This is useful for interacting with a pre-rendered Link Authentication Element.
- [Stripe JS Reference](https://docs.stripe.com/js/element/address_element): This page details the Stripe JS `AddressElement`. It describes how to create and use an Address Element, which is a pre-built UI component for collecting customer addresses. The element simplifies address collection and supports various customization options.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/create_address_element): This page covers the Stripe JS `createAddressElement` method. It explains how to programmatically create an instance of the Address Element, a pre-built UI component for collecting customer addresses. This method allows for customization of the element's appearance and behavior.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/get_address_element): This page documents the Stripe JS `getAddressElement` method. It explains how to retrieve an existing Address Element instance from the Elements API. This is useful for interacting with a pre-rendered Address Element.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/update_address_element): This page describes the Stripe JS `updateAddressElement` method. It details how to update the properties of an existing Address Element instance. This allows for dynamic changes to the address form's configuration after it has been created.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/get_value_address_element): This page explains the Stripe JS `getValue` method for the Address Element. It shows how to retrieve the current value or data entered into the Address Element. This is essential for accessing the collected address information for further processing.
- [Stripe JS Reference](https://docs.stripe.com/js/element/tax_id_element): This page details the Stripe JS `TaxIdElement`. It describes how to create and use a Tax ID Element, a pre-built UI component for collecting customer tax identification numbers. The element supports various tax ID types and countries.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/create_tax_id_element): This page covers the Stripe JS `createTaxIdElement` method. It explains how to programmatically create an instance of the Tax ID Element, a pre-built UI component for collecting customer tax identification numbers. This method allows for customization of the element's configuration.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/get_tax_id_element): This page documents the Stripe JS `getTaxIdElement` method. It explains how to retrieve an existing Tax ID Element instance from the Elements API. This is useful for interacting with a pre-rendered Tax ID Element.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/get_value_tax_id_element): This page explains the Stripe JS `getValue` method for the Tax ID Element. It shows how to retrieve the current value or data entered into the Tax ID Element. This is essential for accessing the collected tax ID information.
- [Stripe JS Reference](https://docs.stripe.com/js/element/issuing): This page provides an overview of Stripe's Issuing Elements for Stripe.js. It introduces pre-built UI components designed for managing Issuing cards within your application. These elements simplify the process of displaying card details and handling card actions.
- [Stripe JS Reference](https://docs.stripe.com/js/issuing_elements/create): This page details the Stripe JS `create` method for Issuing Elements. It explains how to programmatically create instances of Issuing Elements, which are pre-built UI components for displaying and managing Issuing card information. This method allows for customization of the element's appearance and functionality.
- [Stripe JS Reference](https://docs.stripe.com/js/element/other_element): This page covers the Stripe JS `OtherElement`. It describes a generic element type within Stripe.js that can be used for various custom UI integrations. This element provides a flexible way to embed Stripe-related UI components.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/create_element): This page details the Stripe JS `createElement` method. It explains how to create various types of Stripe Elements, which are pre-built UI components for collecting payment or other sensitive information. This is a fundamental method for integrating Stripe's UI components into your application.
- [Stripe JS Reference](https://docs.stripe.com/js/elements_object/get_element): This page documents the Stripe JS `getElement` method. It explains how to retrieve an existing Stripe Element instance from the Elements API using its ID. This is useful for interacting with pre-rendered elements or managing their state.
- [Stripe JS Reference](https://docs.stripe.com/js/element/other_methods/update): This page describes the Stripe JS `update` method for Elements. It explains how to modify the properties or appearance of an existing Stripe Element instance after it has been created. This allows for dynamic updates to the UI components.
- [Stripe JS Reference](https://docs.stripe.com/js/element/the_element_container): This page discusses the Element container in Stripe.js. It explains how Stripe Elements are rendered within a specified DOM element. This documentation covers how to mount and manage the container for your Stripe UI components.
- [Stripe JS Reference](https://docs.stripe.com/js/element/input_validation): This page details input validation for Stripe Elements. It explains how Stripe.js handles and displays validation errors for user input within Elements. This ensures that users receive feedback on incorrect or missing information.
- [Stripe JS Reference](https://docs.stripe.com/js/element/postal_code_formatting): This page covers postal code formatting within Stripe Elements. It explains how Stripe.js automatically formats postal codes based on the selected country. This feature helps ensure accurate address data collection.
- [Stripe JS Reference](https://docs.stripe.com/js/element/mount): This page describes the Stripe JS `mount` method. It explains how to attach a Stripe Element to a specific DOM element on your webpage. This action renders the UI component and makes it interactive for the user.
- [Stripe JS Reference](https://docs.stripe.com/js/element/other_methods): This page provides a reference for various methods available for Stripe Elements. It details functions for managing the lifecycle and behavior of elements, such as blurring, clearing, destroying, focusing, and unmounting.
- [Stripe JS Reference](https://docs.stripe.com/js/element/other_methods/blur): This page documents the `blur()` method for Stripe Elements. It explains how to programmatically remove focus from an Element, which can be useful for controlling user interaction within forms.
- [Stripe JS Reference](https://docs.stripe.com/js/element/other_methods/clear): This section details the `clear()` method for Stripe Elements. This method allows you to clear the value and reset the state of an input Element, useful for form resets or correcting user input.
- [Stripe JS Reference](https://docs.stripe.com/js/element/other_methods/destroy): This page describes the `destroy()` method for Stripe Elements. It explains how to permanently remove an Element from the DOM and release associated resources, essential for cleanup when an Element is no longer needed.
- [Stripe JS Reference](https://docs.stripe.com/js/element/other_methods/focus): This documentation covers the `focus()` method for Stripe Elements. It explains how to programmatically set focus to an Element, improving user experience by guiding input to specific fields.
- [Stripe JS Reference](https://docs.stripe.com/js/element/other_methods/unmount): This page details the `unmount()` method for Stripe Elements. It explains how to remove an Element from its container without destroying it, allowing for re-mounting later if needed.
- [Stripe JS Reference](https://docs.stripe.com/js/element/events): This page serves as a reference for events that can be handled by Stripe Elements. It outlines the various events that Elements can emit, allowing developers to react to user interactions and Element state changes.
- [Stripe JS Reference](https://docs.stripe.com/js/element/events/on_change): This documentation covers the `onChange` event for Stripe Elements. It explains how to listen for changes in an Element's value or state, enabling real-time validation and updates.
- [Stripe JS Reference](https://docs.stripe.com/js/element/events/on_ready): This page details the `onReady` event for Stripe Elements. It explains how to detect when an Element has finished loading and is ready to be interacted with, ensuring a smooth user experience.
- [Stripe JS Reference](https://docs.stripe.com/js/element/events/on_focus): This documentation covers the `onFocus` event for Stripe Elements. It explains how to listen for when an Element receives focus, allowing for visual feedback or specific input handling.
- [Stripe JS Reference](https://docs.stripe.com/js/element/events/on_blur): This page details the `onBlur` event for Stripe Elements. It explains how to listen for when an Element loses focus, useful for triggering validation or updating UI states.
- [Stripe JS Reference](https://docs.stripe.com/js/element/events/on_escape): This documentation covers the `onEscape` event for Stripe Elements. It explains how to handle the Escape key press within an Element, often used for closing modals or canceling input.
- [Stripe JS Reference](https://docs.stripe.com/js/element/events/on_click): This page details the `onClick` event for Stripe Elements. It explains how to listen for click events on an Element, enabling custom interactions or triggering actions.
- [Stripe JS Reference](https://docs.stripe.com/js/element/events/on_loaderror): This documentation covers the `onLoadError` event for Stripe Elements. It explains how to handle errors that occur during the loading of an Element, allowing for graceful error display to the user.
- [Stripe JS Reference](https://docs.stripe.com/js/element/events/on_loaderstart): This page details the `onLoaderStart` event for Stripe Elements. It explains how to detect when the loading indicator for an Element begins to display, useful for managing UI states during loading.
- [Stripe JS Reference](https://docs.stripe.com/js/element/events/on_networkschange): This documentation covers the `onNetworksChange` event for Stripe Elements. It explains how to listen for changes in detected card networks, which can be used for displaying relevant branding or applying specific logic.
- [Stripe JS Reference](https://docs.stripe.com/js/embedded_checkout): This page provides a reference for Stripe's Embedded Checkout functionality. It outlines the core concepts and methods for integrating a pre-built checkout flow directly into your application.
- [Stripe JS Reference](https://docs.stripe.com/js/embedded_checkout/init): This documentation covers the `init()` method for Stripe's Embedded Checkout. It explains how to initialize the Embedded Checkout component, setting up the necessary parameters and configurations to display the checkout flow.
- [Stripe JS Reference](https://docs.stripe.com/js/embedded_checkout/mount): This page details the `mount()` method for Stripe's Embedded Checkout. It explains how to attach the Embedded Checkout component to a specific DOM element on your page, making the checkout flow visible to the user.
- [Stripe JS Reference](https://docs.stripe.com/js/embedded_checkout/unmount): This documentation covers the `unmount()` method for Stripe's Embedded Checkout. It explains how to remove the Embedded Checkout component from the DOM, effectively closing the checkout flow and releasing resources.
- [Stripe JS Reference](https://docs.stripe.com/js/embedded_checkout/destroy): This page details the `destroy` method for Stripe's Embedded Checkout. It explains how to cleanly unmount the checkout instance from the DOM, releasing resources and preventing memory leaks. Proper use of this method ensures a smooth user experience when the checkout is no longer needed.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout): This page serves as an introduction to Stripe's Custom Checkout. It outlines the core concepts and the overall workflow for integrating a customizable checkout experience into your application. The documentation guides developers on how to leverage Stripe.js for building tailored payment flows.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/init): This page explains how to initialize Stripe's Custom Checkout using the `init` function. It covers the necessary parameters and configurations required to set up the checkout instance within your application. Proper initialization is crucial for enabling all Custom Checkout features.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/checkout_object): This page describes the `checkout_object` in Stripe's Custom Checkout. It details the structure and properties of this object, which represents the active checkout session. Understanding the `checkout_object` is key to interacting with and managing the checkout state.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/session): This page focuses on the `session` object within Stripe's Custom Checkout. It explains how to retrieve and interact with the session data, which includes details about the order, customer, and payment status. This object is fundamental for managing the checkout process dynamically.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/apply_promotion_code): This page details the `apply_promotion_code` method for Stripe's Custom Checkout. It describes how to apply a promotion code to the checkout session, which can automatically adjust line items and totals. This functionality allows for flexible discount application during the payment process.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/remove_promotion_code): This page explains the `remove_promotion_code` method in Stripe's Custom Checkout. It covers how to remove an already applied promotion code from the checkout session. This is useful for scenarios where a user changes their mind or a promotion is no longer valid.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/update_shipping_address): This page describes the `update_shipping_address` method for Stripe's Custom Checkout. It allows developers to programmatically update the shipping address for the checkout session. This is essential for recalculating shipping costs and taxes based on the new address.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/update_billing_address): This page details the `update_billing_address` method within Stripe's Custom Checkout. It explains how to update the billing address associated with the checkout session. This is important for payment processing and tax compliance.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/update_email): This page covers the `update_email` method for Stripe's Custom Checkout. It describes how to update the customer's email address within the checkout session. This is useful for ensuring accurate order confirmation and communication.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/update_phone_number): This page explains the `update_phone_number` method in Stripe's Custom Checkout. It details how to update the customer's phone number for the checkout session. This information is often used for delivery notifications or customer support.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/update_tax_id_info): This page describes the `update_tax_id_info` method for Stripe's Custom Checkout. It explains how to update tax identification information for the checkout session, which is crucial for businesses operating in different tax jurisdictions. This ensures accurate tax calculation and compliance.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/update_line_item_quantity): This page details the `update_line_item_quantity` method in Stripe's Custom Checkout. It allows developers to modify the quantity of specific items within the checkout session. This is a core feature for enabling dynamic cart adjustments before payment.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/update_shipping_option): This page explains the `update_shipping_option` method for Stripe's Custom Checkout. It describes how to allow customers to select different shipping methods, which then updates the total cost of the order. This provides flexibility in delivery choices.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/confirm): This page focuses on the `confirm` method within Stripe's Custom Checkout. It explains how to finalize the checkout process and initiate payment collection after all details have been entered. This is the final step before the transaction is processed by Stripe.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/run_server_update): This page details the `run_server_update` method for Stripe's Custom Checkout. It explains how to trigger server-side updates for the checkout session, which might be necessary for complex business logic or inventory management. This ensures data consistency between the client and server.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/session_object): This page describes the `session_object` in Stripe's Custom Checkout documentation. It provides an in-depth look at the structure and properties of the session object, which holds all relevant information about the checkout. Understanding this object is vital for managing and manipulating the checkout flow.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/events): This page covers the events system for Stripe's Custom Checkout. It explains how to listen for and respond to various events that occur during the checkout process, such as updates to the session or completion of payment. This enables dynamic UI updates and custom logic.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/change_event): This page details the `change_event` object in Stripe's Custom Checkout. It describes the structure of event objects that are dispatched when changes occur within the checkout session. Understanding these events allows for real-time feedback and interaction with the checkout flow.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/custom_checkout_elements): This page introduces `custom_checkout_elements` within Stripe's JS library. It explains how these elements are used to build the user interface for a customizable checkout experience. Developers can leverage these components to create a branded and tailored payment flow.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/create_payment_element): This page details how to create a Payment Element using Stripe.js, which is a pre-built, customizable UI component for collecting payment details. It simplifies the integration of various payment methods into your application.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/create_billing_address_element): This page explains how to create a Billing Address Element using Stripe.js. This element allows customers to enter their billing address, which can be used for payment processing and verification.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/create_shipping_address_element): This page describes the creation of a Shipping Address Element with Stripe.js. This component enables users to input their shipping address, facilitating order fulfillment and delivery processes.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/create_express_checkout_element): This page covers the creation of an Express Checkout Element using Stripe.js. This element integrates with express payment methods, offering a streamlined checkout experience for customers.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/create_currency_selector_element): This page details how to create a Currency Selector Element using Stripe.js. This component allows users to select their preferred currency, which can be useful for internationalization.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/create_tax_id_element): This page explains the process of creating a Tax ID Element with Stripe.js. This element is used to collect tax identification numbers from customers, essential for business transactions.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/get_payment_element): This page provides instructions on how to retrieve an existing Payment Element instance using Stripe.js. This is useful for managing and interacting with a previously rendered payment form.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/get_billing_address_element): This page describes how to get a Billing Address Element instance using Stripe.js. This allows you to access and manipulate a billing address form that has already been mounted.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/get_shipping_address_element): This page explains how to retrieve a Shipping Address Element instance using Stripe.js. This enables you to interact with a shipping address form that has been previously created and displayed.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/get_express_checkout_element): This page details how to access an Express Checkout Element instance via Stripe.js. This allows for programmatic control over the express checkout component after it has been initialized.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/get_currency_selector_element): This page covers how to retrieve a Currency Selector Element instance using Stripe.js. This enables you to interact with the currency selection component programmatically.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/change_appearance): This page explains how to change the appearance of Stripe Elements using Stripe.js. It allows for customization of styles to match your brand's look and feel.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/load_fonts): This page details how to load custom fonts for Stripe Elements using Stripe.js. This enables you to use specific fonts to enhance the visual design of your checkout forms.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/element_events): This page provides an overview of the events that Stripe Elements can emit using Stripe.js. Understanding these events is crucial for responding to user interactions and element states.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/element_events/on_change): This page focuses on the 'change' event emitted by Stripe Elements via Stripe.js. This event fires when the user modifies input within an element, allowing you to react to data updates.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/element_events/on_ready): This page describes the 'ready' event for Stripe Elements using Stripe.js. This event is triggered once an element has finished loading and is ready to be interacted with.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/element_events/on_focus): This page explains the 'focus' event for Stripe Elements using Stripe.js. This event fires when a user focuses on an input field within an element, indicating user interaction.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/element_events/on_blur): This page details the 'blur' event for Stripe Elements using Stripe.js. This event is triggered when a user moves focus away from an input field within an element.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/element_events/on_escape): This page covers the 'escape' event for Stripe Elements using Stripe.js. This event fires when the user presses the Escape key while an element is focused, often used for closing modals.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/element_events/on_loaderror): This page explains the 'loaderror' event for Stripe Elements using Stripe.js. This event is triggered if an element fails to load correctly, allowing you to handle potential errors.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/element_events/on_loaderstart): This page documents the `onLoaderStart` event for Stripe's custom checkout elements. It explains when this event fires, typically before the element's loader starts, and provides details on the event object that is passed to the handler.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/element_events/on_confirm): This page details the `onConfirm` event for Stripe's custom checkout elements. It describes the conditions under which this event is triggered, usually after a payment confirmation attempt, and outlines the properties available in the event object for handling confirmation outcomes.
- [Stripe JS Reference](https://docs.stripe.com/js/custom_checkout/element_events/on_cancel): This page covers the `onCancel` event for Stripe's custom checkout elements. It explains that this event occurs when a checkout process is canceled by the user or the system. The documentation details the event object associated with cancellation, allowing developers to manage canceled checkout flows.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js): This page serves as a reference for Stripe's React library, `react-stripe-js`. It provides an overview of how to integrate Stripe payments into React applications using this library. The documentation covers setup, core components, and hooks for managing Stripe elements and checkout flows.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout): This page focuses on the `Checkout` component within Stripe's `react-stripe-js` library. It explains how to use this component to create and manage a Stripe checkout experience in a React application. Key features and configuration options for the `Checkout` component are detailed.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout/checkout_provider): This page describes the `CheckoutProvider` component from Stripe's `react-stripe-js` library. It explains that `CheckoutProvider` is used to wrap parts of your React application that need access to checkout-related context and functionality. This allows nested components to easily interact with Stripe's checkout services.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout/use_checkout): This page documents the `useCheckout` hook provided by Stripe's `react-stripe-js` library. It explains how to use this hook within functional React components to access checkout state and functions. The hook simplifies managing the checkout process and interacting with Stripe's checkout APIs.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout/apply_promotion_code): This page details the `applyPromotionCode` function available through Stripe's `react-stripe-js` library. It explains how to use this function to apply a promotion code to an active checkout session. The documentation covers the parameters required and the expected return values or side effects.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout/remove_promotion_code): This page describes the `removePromotionCode` function in Stripe's `react-stripe-js` library. It guides developers on how to remove an applied promotion code from a checkout session. The documentation outlines the function's signature and its role in updating the checkout total.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout/update_shipping_address): This page covers the `updateShippingAddress` function within Stripe's `react-stripe-js` library. It explains how to programmatically update the shipping address for a checkout session. This is useful for scenarios where the customer provides or changes their shipping details during the checkout flow.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout/update_billing_address): This page documents the `updateBillingAddress` function from Stripe's `react-stripe-js` library. It details how to update the billing address associated with a checkout session. This function is crucial for ensuring accurate billing information is captured and processed by Stripe.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout/update_email): This page focuses on the `updateEmail` function provided by Stripe's `react-stripe-js` library. It explains how to update the customer's email address within an ongoing checkout session. This is important for communication and order confirmation purposes.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout/update_phone_number): This page describes the `updatePhoneNumber` function in Stripe's `react-stripe-js` library. It guides developers on how to update the customer's phone number during the checkout process. This function helps maintain accurate contact information for the order.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout/update_tax_id_info): This page details the `updateTaxIdInfo` function from Stripe's `react-stripe-js` library. It explains how to update tax identification information for a checkout session, which is particularly relevant for business transactions or specific tax requirements. The documentation covers the function's parameters for tax ID and type.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout/update_line_item_quantity): This page covers the `updateLineItemQuantity` function within Stripe's `react-stripe-js` library. It explains how to modify the quantity of specific items in a customer's shopping cart during checkout. This function is essential for allowing customers to adjust their order before payment.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout/update_shipping_option): This page documents the `updateShippingOption` function provided by Stripe's `react-stripe-js` library. It explains how to update the selected shipping method for a checkout session. This allows customers to choose different delivery speeds or carriers, affecting the total cost.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout/confirm): This page focuses on the `confirm` function within Stripe's `react-stripe-js` library. It describes how to use this function to finalize the payment process for a checkout session. The documentation outlines the necessary parameters and the outcomes of calling `confirm`, such as successful payment or errors.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout/run_server_update): This page details the `runServerUpdate` function from Stripe's `react-stripe-js` library. It explains how to trigger a server-side update for a checkout session from the client-side. This function is useful for complex scenarios requiring backend logic to modify the checkout state before completion.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout/payment_element): This page describes the `PaymentElement` component in Stripe's `react-stripe-js` library. It explains how this versatile component can be used to collect payment details for various payment methods within a React application. The documentation covers its integration and customization options.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout/express_checkout_element): This page focuses on the `ExpressCheckoutElement` component from Stripe's `react-stripe-js` library. It explains how this element facilitates express checkout flows, allowing customers to pay quickly using stored payment information. The documentation details its implementation and benefits for a streamlined user experience.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout/billing_address_element): The Billing Address Element allows customers to enter their billing address directly within your Stripe checkout flow. It provides a pre-built UI component that collects necessary address details, validating them in real-time to ensure accuracy.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout/shipping_address_element): The Shipping Address Element enables customers to input their shipping address during checkout. This component simplifies address collection and validation, ensuring that accurate shipping information is captured for orders.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout/currency_selector_element): The Currency Selector Element provides a user interface for customers to choose their preferred currency during checkout. This enhances the customer experience by allowing them to view prices and complete transactions in their local currency.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/checkout/tax_id_element): The Tax ID Element allows customers to enter their tax identification number, which is crucial for businesses that need to collect this information for tax compliance. It integrates seamlessly into the checkout process, ensuring accurate tax handling.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/elements): This page serves as a central reference for Stripe's React Elements, which are pre-built UI components for collecting payment and other customer information. It outlines how to integrate these elements into your React application for a streamlined checkout experience.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/elements/elements_provider): The ElementsProvider component is essential for setting up Stripe Elements in your React application when you have a Stripe PaymentIntent. It makes the Stripe API available to all child components, enabling them to interact with Stripe's services.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/elements/elements_provider_without_intent): The ElementsProviderWithoutIntent is used to set up Stripe Elements when you do not have a Stripe PaymentIntent readily available. It provides the necessary context for Stripe Elements to function, allowing for flexible integration scenarios.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/elements/use_stripe): The `useStripe` hook provides access to the Stripe object, which is the main entry point for interacting with Stripe.js in your React application. It allows you to create Elements, confirm payments, and perform other Stripe-related actions.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/elements/use_elements): The `useElements` hook returns an instance of the Elements API, which provides access to all the Stripe Elements you have mounted in your application. This hook is crucial for retrieving element instances to perform actions like retrieving element values or validating input.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/elements/elements_consumer): The ElementsConsumer component allows you to access the Stripe object and the Elements API through render props. This is useful for components that need to interact with Stripe but are not direct children of the ElementsProvider.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/elements/payment_element): The Payment Element is a pre-built, customizable UI component that collects all the necessary payment details from your customers. It dynamically displays the most relevant fields based on the payment method, simplifying the checkout process.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/elements/express_checkout_element): The Express Checkout Element offers a streamlined checkout experience by integrating with services like Shop Pay. It simplifies the process for customers to complete their purchases quickly and securely.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/elements/address_element): The Address Element is a versatile component that collects complete address information, supporting both billing and shipping addresses. It offers a unified interface for address input and validation, reducing integration complexity.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/elements/link_authentication_element): The Link Authentication Element is used to collect customer email addresses for identity verification and authentication purposes. It integrates with Stripe's Link service to provide a fast and secure way to authenticate users.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/elements/tax_id_element): The Tax ID Element allows customers to enter their tax identification number, which is crucial for businesses that need to collect this information for tax compliance. It integrates seamlessly into the checkout process, ensuring accurate tax handling.
- [Stripe JS Reference](https://docs.stripe.com/js/react_stripe_js/elements/other): This page covers miscellaneous Stripe.js React components and functionalities not categorized elsewhere. It provides guidance on integrating additional features and handling specific use cases within your React applications.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents): This page provides a reference for Stripe JS, focusing on the Payment Intents API. It details how to manage and interact with payment intents using JavaScript. Key functionalities include creating, confirming, and retrieving payment intents.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_payment): This section of the Stripe JS Reference details the `confirmPayment` method for Payment Intents. It explains how to use this method to confirm a Payment Intent with a given PaymentMethod. This is a crucial step in completing a payment flow.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/payment_method): This page in the Stripe JS Reference focuses on the `paymentMethod` object within the context of Payment Intents. It describes the properties and structure of a PaymentMethod, which represents the payment details used to confirm a Payment Intent. Understanding this object is key to handling various payment types.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_card_payment): This page provides the Stripe JS reference for confirming card payments using Payment Intents. It details the `confirmCardPayment` method, which allows you to securely confirm a Payment Intent with card details. This method handles the necessary steps for processing card transactions.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_us_bank_account_payment): This Stripe JS Reference page explains how to confirm US bank account payments with Payment Intents. It covers the `confirmUSBankAccountPayment` method, enabling users to securely authenticate and complete payments using their US bank accounts. This method is essential for ACH direct debit transactions.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_acss_debit_payment): This page details the Stripe JS method `confirmAcssDebitPayment` for confirming Canadian payments via ACSS Direct Debit. It guides developers on how to integrate this specific payment method into their checkout flow using Stripe.js. This ensures secure and compliant processing of Canadian debit payments.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_affirm_payment): This Stripe JS Reference page describes the `confirmAffirmPayment` method for integrating Affirm payments. It outlines how to use this method to confirm a PaymentIntent, allowing customers to complete their purchase using Affirm's buy now, pay later service. This facilitates flexible payment options for users.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_afterpay_clearpay_payment): This page provides the Stripe JS reference for confirming Afterpay/Clearpay payments. It details the `confirmAfterpayClearpayPayment` method, enabling customers to complete payments using Afterpay or Clearpay. This integration allows for flexible payment options at checkout.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_alipay_payment): This Stripe JS Reference page focuses on the `confirmAlipayPayment` method for integrating Alipay. It explains how to use this method to confirm a PaymentIntent, allowing customers to pay using their Alipay accounts. This method is crucial for reaching customers in markets where Alipay is popular.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_au_becs_debit_payment): This page provides the Stripe JS reference for confirming AU BECS Direct Debit payments. It details the `confirmAuBecsDebitPayment` method, which allows customers to authorize payments directly from their Australian bank accounts. This is essential for businesses accepting recurring or one-time debits in Australia.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_bancontact_payment): This Stripe JS Reference page explains the `confirmBancontactPayment` method for processing Bancontact payments. It guides developers on how to integrate this popular Belgian payment method into their Stripe.js checkout flow. This ensures a seamless payment experience for Belgian customers.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_blik_payment): This page provides the Stripe JS reference for confirming BLIK payments. It details the `confirmBlikPayment` method, which enables customers in Poland to pay quickly and securely using the BLIK mobile payment system. This integration expands payment options for a key European market.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_boleto_payment): This Stripe JS Reference page focuses on the `confirmBoletoPayment` method for integrating Boleto Bancário payments in Brazil. It explains how to use this method to confirm a PaymentIntent, allowing customers to pay via this widely used Brazilian payment voucher. This is vital for serving the Brazilian market.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_customer_balance_payment): This page provides the Stripe JS reference for confirming Customer Balance payments. It details the `confirmCustomerBalancePayment` method, allowing customers to pay using funds available in their Stripe Customer Balance. This offers a flexible payment option for users with existing balances.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_cashapp_payment): This Stripe JS Reference page explains the `confirmCashappPayment` method for integrating Cash App Pay. It guides developers on how to use this method to confirm a PaymentIntent, enabling customers to pay using their Cash App accounts. This provides a popular mobile payment option.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_eps_payment): This page provides the Stripe JS reference for confirming EPS (Electronic Payment Standard) payments. It details the `confirmEpsPayment` method, allowing customers in Austria to pay directly from their bank accounts. This integration supports a common payment method in the Austrian market.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_fpx_payment): This page details how to confirm a PaymentIntent with FPX using Stripe.js. It outlines the necessary parameters and steps to integrate FPX payments into your application.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_giropay_payment): This page explains the process of confirming a PaymentIntent with Giropay using Stripe.js. It provides guidance on the required parameters and implementation for Giropay transactions.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_grabpay_payment): This page covers confirming a PaymentIntent with GrabPay via Stripe.js. It details the parameters and integration steps for enabling GrabPay payments.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_ideal_payment): This page describes how to confirm a PaymentIntent using iDEAL with Stripe.js. It lists the required parameters and provides instructions for integrating iDEAL payments.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_klarna_payment): This page outlines the process of confirming a PaymentIntent with Klarna using Stripe.js. It specifies the parameters and implementation details for Klarna payment integration.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_konbini_payment): This page details how to confirm a PaymentIntent for Konbini payments using Stripe.js. It provides the necessary parameters and steps for integrating this payment method.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_mb_way_payment): This page explains how to confirm a PaymentIntent with MB WAY using Stripe.js. It covers the required parameters and integration steps for MB WAY transactions.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_mobilepay_payment): This page describes confirming a PaymentIntent with MobilePay using Stripe.js. It lists the parameters and provides guidance for integrating MobilePay payments.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_multibanco_payment): This page details the confirmation of a PaymentIntent for Multibanco payments using Stripe.js. It outlines the required parameters and integration steps for this payment method.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_oxxo_payment): This page explains how to confirm a PaymentIntent with OXXO using Stripe.js. It provides the necessary parameters and implementation details for OXXO payment integration.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_p24_payment): This page covers confirming a PaymentIntent with P24 (Przelewy24) using Stripe.js. It details the required parameters and steps for integrating P24 payments.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_pay_by_bank_payment): This page describes the process of confirming a PaymentIntent with Pay by Bank using Stripe.js. It outlines the parameters and integration steps for Pay by Bank transactions.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_paynow_payment): This page details how to confirm a PaymentIntent with PayNow using Stripe.js. It provides the necessary parameters and implementation guidance for PayNow payments.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_paypal_payment): This page explains how to confirm a PaymentIntent with PayPal using Stripe.js. It lists the required parameters and provides instructions for integrating PayPal payments.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_payto_payment): This page covers confirming a PaymentIntent with PayTo using Stripe.js. It details the parameters and integration steps for enabling PayTo payments.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_pix_payment): This page outlines the process of confirming a PaymentIntent with Pix using Stripe.js. It specifies the parameters and implementation details for Pix payment integration.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_promptpay_payment): This page describes how to confirm a PaymentIntent with PromptPay using Stripe.js. It provides the necessary parameters and integration steps for PromptPay transactions.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_sepa_debit_payment): This page details how to confirm a PaymentIntent with SEPA Direct Debit using Stripe.js. It outlines the required parameters and integration steps for SEPA Direct Debit payments.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_sofort_payment): This page explains how to confirm a PaymentIntent with Sofort using Stripe.js. It lists the parameters and provides guidance for integrating Sofort payments.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_twint_payment): This page covers confirming a PaymentIntent with TWINT using Stripe.js. It details the parameters and integration steps for enabling TWINT payments.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_upi_payment): This page provides documentation for confirming UPI payments using Stripe JS. It details the necessary steps and parameters for integrating UPI payment confirmation into your application.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_wechat_pay_payment): This documentation covers the process of confirming WeChat Pay payments through Stripe JS. It outlines the API calls and requirements for enabling WeChat Pay as a payment method.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/confirm_zip_payment): This page explains how to confirm Zip payments using Stripe JS. It provides guidance on integrating Zip as a payment option and handling the confirmation flow.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/retrieve_payment_intent): This documentation details how to retrieve the status and details of a PaymentIntent using Stripe JS. It explains the API endpoint and parameters for fetching PaymentIntent information.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/verify_microdeposits_for_payment): This page describes the process of verifying microdeposits for a PaymentIntent with Stripe JS. It outlines the steps required to confirm microdeposit amounts for bank account verification.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/create_radar_session): This documentation explains how to create a Radar session using Stripe JS. It covers the API for initiating a session to apply Radar rules and fraud detection.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/handle_next_action): This page provides instructions on handling next actions for a PaymentIntent using Stripe JS. It details how to manage asynchronous payment flows that require additional user interaction.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/handle_card_action): This documentation covers handling card actions for a PaymentIntent with Stripe JS. It explains how to manage authentication and authorization steps for card payments.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_intents/collect_bank_account_for_payment): This page describes how to collect bank account details for a payment using Stripe JS. It outlines the necessary steps and components for securely gathering bank account information.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents): This documentation introduces Stripe SetupIntents, which are used to save payment method details for future use. It explains their purpose in securely storing customer payment information.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents/confirm_setup): This page details how to confirm a SetupIntent using Stripe JS. It outlines the process for securely saving a customer's payment method for later transactions.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents/payment_method): This documentation explains how to attach a payment method to a SetupIntent using Stripe JS. It covers the API calls for associating a specific payment method with a SetupIntent.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents/confirm_card_setup): This page describes how to confirm a card setup for a SetupIntent using Stripe JS. It details the process for securely saving card details for future use.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents/confirm_us_bank_account_setup): This documentation explains how to confirm a US bank account setup for a SetupIntent using Stripe JS. It outlines the steps for securely saving US bank account details.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents/confirm_acss_debit_setup): This page details how to confirm an ACSS Direct Debit setup for a SetupIntent using Stripe JS. It provides guidance on securely saving Canadian bank account details for recurring payments.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents/confirm_au_becs_debit_setup): This documentation covers confirming an AU BECS Direct Debit setup for a SetupIntent using Stripe JS. It outlines the process for securely saving Australian bank account details.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents/confirm_bacs_debit_setup): This page explains how to confirm a Bacs Direct Debit setup for a SetupIntent using Stripe JS. It details the steps for securely saving UK bank account details.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents/confirm_bancontact_setup): This documentation covers confirming a Bancontact setup for a SetupIntent using Stripe JS. It outlines the process for securely saving Bancontact payment details.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents/confirm_cashapp_setup): This page details how to confirm a Cash App Pay setup for a SetupIntent using Stripe JS. It provides guidance on securely saving Cash App Pay payment information.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents/confirm_ideal_setup): This documentation explains how to confirm an iDEAL setup for a SetupIntent using Stripe JS. It outlines the process for securely saving iDEAL payment details.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents/confirm_klarna_setup): This page details how to confirm a SetupIntent with Klarna using Stripe.js. It outlines the necessary parameters and steps to complete the Klarna setup process for recurring payments.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents/confirm_paypal_setup): This page explains how to confirm a SetupIntent with PayPal using Stripe.js. It covers the parameters required to finalize PayPal account setup for future transactions.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents/confirm_payto_setup): This page provides guidance on confirming a SetupIntent with PayTo using Stripe.js. It details the process and parameters for setting up PayTo for recurring payments.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents/confirm_sepa_debit_setup): This page describes how to confirm a SetupIntent with SEPA Direct Debit using Stripe.js. It outlines the steps and information needed to set up SEPA Direct Debit for recurring payments.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents/confirm_sofort_setup): This page explains how to confirm a SetupIntent with Sofort using Stripe.js. It details the parameters and process for completing the Sofort setup for recurring payments.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents/retrieve_setup_intent): This page covers retrieving a SetupIntent object using Stripe.js. It explains how to fetch the details of a SetupIntent, which is used to set up recurring payments.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents/verify_microdeposits_for_setup): This page details how to verify microdeposits for a SetupIntent using Stripe.js. It guides through the process of confirming bank account details for recurring payments.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents/handle_next_action): This page explains how to handle the next action required for a SetupIntent using Stripe.js. It covers scenarios where additional user interaction is needed to complete the setup.
- [Stripe JS Reference](https://docs.stripe.com/js/setup_intents/collect_bank_account_for_setup): This page describes how to collect bank account details for a SetupIntent using Stripe.js. It outlines the process for securely gathering customer bank information for recurring payments.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_request): This page introduces the Payment Request API in Stripe.js. This API provides a standardized way to collect payment and shipping information from customers.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_request/create): This page explains how to create a Payment Request object using Stripe.js. It details the parameters and options for initiating a payment request.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_request/can_make_payment): This page covers how to check if a browser can make payments using the Payment Request API with Stripe.js. It determines browser and device support for payment requests.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_request/show): This page details how to display the Payment Request interface to the user using Stripe.js. It outlines the process of showing the payment sheet for collecting details.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_request/update): This page explains how to update a Payment Request with new information using Stripe.js. It covers modifying details like shipping options or line items after the request is shown.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_request/events): This page describes the various events that can occur with the Payment Request API in Stripe.js. It covers the lifecycle of a payment request and potential user interactions.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_request/events/on_token): This page details the `on_token` event for the Payment Request API in Stripe.js. It explains how to handle the token generated when a payment method is selected.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_request/events/on_paymentmethod): This page explains the `on_paymentmethod` event for the Payment Request API in Stripe.js. It covers how to access the PaymentMethod object when a customer selects a payment method.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_request/events/on_source): This page details the `on_source` event for the Payment Request API in Stripe.js. It explains how to handle the Source object when a customer completes the payment flow.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_request/events/on_cancel): This page describes the `on_cancel` event for the Payment Request API in Stripe.js. It covers how to respond when a customer cancels the payment request.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_request/events/on_shipping_address_change): This page explains the `on_shipping_address_change` event for the Payment Request API in Stripe.js. It details how to handle updates when a customer changes their shipping address.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_request/events/on_shipping_option_change): This page details the `onShippingOptionChange` event in Stripe JS, which is triggered when a customer selects a shipping option. It allows you to update the total amount and line items of a Stripe Payment Request based on the chosen shipping method.
- [Stripe JS Reference](https://docs.stripe.com/js/confirmation_tokens): This page serves as a reference for Stripe JS Confirmation Tokens. These tokens are used to confirm payment methods and complete payments after initial authorization.
- [Stripe JS Reference](https://docs.stripe.com/js/confirmation_tokens/create_confirmation_token): This page explains how to create a Stripe JS Confirmation Token. This token is essential for securely confirming a payment method and finalizing a transaction within the Stripe ecosystem.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_methods): This page provides documentation for Stripe JS Payment Methods. It covers various methods customers can use to pay, including cards, bank accounts, and digital wallets.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_methods/create_payment_method): This page details the process of creating a PaymentMethod object using Stripe JS. It enables you to collect payment details from customers and represent them as a Stripe PaymentMethod for future use.
- [Stripe JS Reference](https://docs.stripe.com/js/payment_methods/create_payment_method_elements): This page describes how to create a PaymentMethod using Stripe Elements with Stripe JS. Elements provide pre-built UI components for securely collecting sensitive payment information directly on your site.
- [Stripe JS Reference](https://docs.stripe.com/js/tokens): This page is a reference for Stripe JS Tokens. Tokens are secure, single-use representations of sensitive payment information that can be used in place of the actual details.
- [Stripe JS Reference](https://docs.stripe.com/js/tokens/create_token): This page explains how to create a Stripe JS Token from card details. This token can then be used to securely process payments without directly handling sensitive card information.
- [Stripe JS Reference](https://docs.stripe.com/js/identity/modal): This page documents the Stripe JS Identity Modal. It provides a user-friendly interface for identity verification flows, allowing customers to verify their identity directly within your application.
- [Stripe JS Reference](https://docs.stripe.com/js/issuing/create_ephemeral_key_nonce): This page details how to use Stripe JS to create an ephemeral key nonce for Issuing. This nonce is used in the process of securely creating ephemeral keys for Issuing card operations.
- [Stripe JS Reference](https://docs.stripe.com/js/issuing/retrieve_issuing_card): This page provides documentation on how to retrieve an Issuing Card object using Stripe JS. This allows you to fetch details about a specific Issuing card for use in your application.
- [Stripe JS Reference](https://docs.stripe.com/js/financial_connections): This page introduces Stripe JS Financial Connections. This feature enables you to securely connect to customers' financial institutions to retrieve account and transaction data.
- [Stripe JS Reference](https://docs.stripe.com/js/financial_connections/collect_financial_connections_accounts): This page explains how to use Stripe JS to collect financial account information. It guides you through the process of gathering necessary details about a customer's financial accounts for verification or data retrieval.
- [Stripe JS Reference](https://docs.stripe.com/js/financial_connections/collect_bank_account_token): This page details how to collect a bank account token using Stripe JS. This token represents a customer's bank account and can be used for various payment and verification purposes.
- [Stripe JS Reference](https://docs.stripe.com/js/retrieve_card_networks/intro): This page introduces the functionality for retrieving card networks supported by Stripe JS. It explains how to determine which card networks are compatible with a given card or payment method.
- [Stripe JS Reference](https://docs.stripe.com/js/retrieve_card_networks): This page provides the Stripe JS method for retrieving supported card networks. This function helps you identify the specific card networks (e.g., Visa, Mastercard) associated with a payment method.
- [Stripe JS Reference](https://docs.stripe.com/js/appendix/css_font_source_object): This page documents the CSS font source object in Stripe JS. It defines the structure and properties for specifying custom font sources for styling Stripe elements.
- [Stripe JS Reference](https://docs.stripe.com/js/appendix/custom_font_source_object): This page details the custom font source object within Stripe JS. It outlines how to configure and provide custom fonts to be used for styling Stripe's UI components.
- [Stripe JS Reference](https://docs.stripe.com/js/appendix/contact_object): This page describes the Contact object in Stripe JS. This object is used to represent contact information, such as billing or shipping addresses, within Stripe's payment flows.
- [Stripe JS Reference](https://docs.stripe.com/js/appendix/payment_item_object): This page documents the Payment Item object in Stripe JS. This object represents an individual item within a customer's order, including its description, quantity, and price.
- [Stripe JS Reference](https://docs.stripe.com/js/appendix/payment_response): This page details the structure of the payment response object returned by Stripe.js. It outlines the various fields available, such as payment intent status, client secret, and error information, which are crucial for handling payment outcomes in your application.
- [Stripe JS Reference](https://docs.stripe.com/js/appendix/shipping_option): This section of the Stripe.js reference describes the shipping option object. It explains the properties available for defining shipping methods, including their IDs, labels, and costs, enabling customization of shipping choices for customers.
- [Stripe JS Reference](https://docs.stripe.com/js/appendix/shipping_address): This page covers the shipping address object within the Stripe.js documentation. It details the fields that represent a customer's shipping address, such as name, street, city, and postal code, facilitating the collection and processing of shipping information.
- [Stripe JS Reference](https://docs.stripe.com/js/appendix/style): This Stripe.js reference page explains the styling options available for Stripe Elements. It provides guidance on customizing the appearance of UI components, allowing developers to match the look and feel of their website or application.
- [Stripe JS Reference](https://docs.stripe.com/js/appendix/update_details): This document outlines the functionality for updating details using Stripe.js. It describes how to modify customer or payment information after initial submission, offering flexibility in managing transaction data.
- [Stripe JS Reference](https://docs.stripe.com/js/appendix/supported_browsers): This page lists the browsers officially supported by Stripe.js. It ensures developers are aware of the compatible environments for integrating Stripe's payment solutions, promoting a stable user experience.
- [Stripe JS Reference](https://docs.stripe.com/js/appendix/cross_origin_isolation): This section of the Stripe.js reference discusses cross-origin isolation requirements. It explains the necessary HTTP headers for enabling secure cross-origin communication, which is important for certain advanced features.
- [Stripe JS Reference](https://docs.stripe.com/js/appendix/supported_locales): This page provides a list of supported locales for Stripe.js. It details the languages and regions for which Stripe.js offers localized elements and messages, aiding in the creation of internationalized payment experiences.
- [Stripe JS Reference](https://docs.stripe.com/js/appendix/cookies): This document addresses the use of cookies by Stripe.js. It explains how cookies are utilized for essential functionalities, security, and analytics, providing transparency on data handling practices.
- [Stripe JS Reference](https://docs.stripe.com/js/appendix/viewport_meta_requirements): This page outlines the viewport meta requirements for Stripe.js. It specifies the necessary configurations for the viewport meta tag to ensure proper rendering and responsiveness of Stripe Elements on mobile devices.
- [Stripe JS Reference](https://docs.stripe.com/js/deprecated/handle_card_payment_element): This page details the deprecated `handleCardPaymentElement` method in Stripe.js. It explains the functionality it previously offered for handling card payments within a Payment Element and advises on its replacement.
- [Stripe JS Reference](https://docs.stripe.com/js/deprecated/handle_card_payment): This document covers the deprecated `handleCardPayment` method in Stripe.js. It describes the previous approach to handling card payments directly and points to the current recommended methods for payment processing.
- [Stripe JS Reference](https://docs.stripe.com/js/deprecated/confirm_payment_intent_element): This page discusses the deprecated `confirmPaymentIntentElement` method for Stripe.js. It explains its former role in confirming Payment Intents using a Payment Element and directs users to updated alternatives.
- [Stripe JS Reference](https://docs.stripe.com/js/deprecated/confirm_payment_intent): This document addresses the deprecated `confirmPaymentIntent` method in Stripe.js. It outlines the previous way to confirm Payment Intents and guides developers toward the current, recommended Stripe.js APIs.
- [Stripe JS Reference](https://docs.stripe.com/js/deprecated/handle_card_setup_element): This page describes the deprecated `handleCardSetupElement` method in Stripe.js. It explains its historical use for handling card setup within a Payment Element and indicates the modern approach.
- [Stripe JS Reference](https://docs.stripe.com/js/deprecated/handle_card_setup): This document covers the deprecated `handleCardSetup` method in Stripe.js. It details the past functionality for setting up card details and directs users to the current, preferred methods for card tokenization and setup.
- [Stripe JS Reference](https://docs.stripe.com/js/deprecated/confirm_setup_intent_element): This page discusses the deprecated `confirmSetupIntentElement` method in Stripe.js. It explains its former function in confirming Setup Intents with a Payment Element and provides information on newer, supported methods.
- [Stripe JS Reference](https://docs.stripe.com/js/deprecated/confirm_setup_intent): This document addresses the deprecated `confirmSetupIntent` method in Stripe.js. It outlines the previous process for confirming Setup Intents and guides developers to the current, recommended Stripe.js APIs for this purpose.
- [Stripe JS Reference](https://docs.stripe.com/js/deprecated/handle_fpx_payment): This page details the deprecated `handleFpxPayment` method in Stripe.js. It explains the former process for initiating FPX payments and advises on the current methods for integrating this payment method.
- [Stripe JS Reference](https://docs.stripe.com/js/deprecated/sources): This document covers the deprecated `sources` API in Stripe.js. It explains the historical functionality for creating and managing payment sources and directs users to the current recommended APIs for managing payment methods.
- [Stripe JS Reference](https://docs.stripe.com/js/deprecated/sources/create_source): This page documents the Stripe JS `create_source` function, which is deprecated. It was used to create a Source object with a given type and optional data.
- [Stripe JS Reference](https://docs.stripe.com/js/deprecated/sources/create_source_data): This page documents the deprecated Stripe JS `create_source_data` function. This function was used to create a Source object from provided data, likely for specific payment methods.
- [Stripe JS Reference](https://docs.stripe.com/js/deprecated/sources/retrieve_source): This page details the deprecated Stripe JS `retrieve_source` function. It was used to fetch the details of a specific Source object using its unique ID.
- [Untitled](https://docs.stripe.com/cli.md): This document introduces the Stripe CLI, a command-line tool for managing Stripe integrations. It covers creating, retrieving, updating, and deleting API objects, tailing logs in real-time, and securely testing webhooks.
- [Untitled](https://docs.stripe.com/cli/login.md): This page explains how to connect the Stripe CLI to your Stripe account using the `stripe login` command. It details the process of authentication via the Dashboard and the storage of configuration files.
- [Untitled](https://docs.stripe.com/cli/api_keys.md): This page outlines various methods for using Stripe API keys with the Stripe CLI, including `stripe login`, `stripe config`, the `--api-key` flag, and environment variables. `stripe login` is recommended for ease of use.
- [Untitled](https://docs.stripe.com/cli/config.md): This document describes the `stripe config` command, which allows manual configuration of Stripe CLI options. It supports setting, unsetting, listing, and editing configuration settings, with options for project-specific configurations.
- [Untitled](https://docs.stripe.com/cli/completion.md): This page explains how to set up shell autocompletion for the Stripe CLI on macOS and Linux using the `stripe completion` command. It provides instructions for Bash and Zsh shells.
- [Untitled](https://docs.stripe.com/cli/flags.md): This page lists and describes the global flags available for all Stripe CLI commands. These flags control aspects like API key usage, color output, configuration file paths, and device names.
- [Untitled](https://docs.stripe.com/cli/intro_stripe.md): This page provides a brief overview of Stripe CLI commands related to inspecting Stripe integration details, logs, and service availability.
- [Untitled](https://docs.stripe.com/cli/logs/tail.md): This document details the `stripe logs tail` command, which streams test mode Stripe API request logs in real-time directly to your terminal. It supports various filters to narrow down the displayed logs.
- [Untitled](https://docs.stripe.com/cli/open.md): This page describes the `stripe open` command, a shortcut for opening Stripe documentation or the Dashboard in your browser. It supports various shortcuts and can open live mode Dashboard pages with a flag.
- [Untitled](https://docs.stripe.com/cli/intro_webhooks.md): This page introduces Stripe CLI commands for managing webhook events. These commands allow users to listen for, trigger, and resend webhook events for local testing.
- [Untitled](https://docs.stripe.com/cli/listen.md): This document explains the `stripe listen` command, which receives webhook events from Stripe on your local machine. It can forward events to a local application and filter events by type.
- [Untitled](https://docs.stripe.com/cli/trigger.md): This page details the `stripe trigger` command, used to simulate webhook events for local testing. These simulated events are based on real API objects and can trigger other related events.
- [Untitled](https://docs.stripe.com/cli/events/resend.md): This page describes the `stripe events resend` command, which resends a specific event to a local webhook endpoint. It can only resend events created within the last 30 days and requires a webhook endpoint ID.
- [Untitled](https://docs.stripe.com/cli/intro_resources_http.md): This page introduces the Stripe CLI's resource and HTTP commands for managing API objects. Resource commands offer specific operations for each API resource, while HTTP commands provide shorthand for direct API requests.
- [Untitled](https://docs.stripe.com/cli/resources.md): This document details the Stripe CLI's resource commands, which allow interaction with all Stripe API resources. It explains how to perform operations like create, delete, list, and retrieve resources with various parameters and flags.
- [Untitled](https://docs.stripe.com/cli/get.md): This page describes the `stripe get` command, used to make GET HTTP requests to retrieve API objects. It supports pagination, expanding response attributes, and piping output to other tools like `jq`.
- [Untitled](https://docs.stripe.com/cli/post.md): This page explains the `stripe post` command for making POST HTTP requests to the Stripe API. It supports features like idempotency keys, expandable objects, and sending additional data for creating or updating resources.
- [Untitled](https://docs.stripe.com/cli/delete.md): The `stripe delete` command makes DELETE HTTP requests to the Stripe API. It allows you to delete API objects by providing the URL path and supports various flags for confirmation, data inclusion, and live mode requests.
- [Untitled](https://docs.stripe.com/cli/fixtures.md): The `stripe fixtures` command executes a series of API requests defined in a JSON file. It enables referencing responses from previous requests to build complex data flows or test API behavior, supporting environment variables and nested data access.
- [Untitled](https://docs.stripe.com/cli/intro_stripe_samples.md): Stripe Samples are complete examples that simplify getting started with Stripe integrations. The Stripe CLI allows you to download, build, and serve these samples directly from your command line.
- [Untitled](https://docs.stripe.com/cli/samples/create.md): The `stripe samples create` command creates a local copy of a chosen Stripe Sample. You can specify the sample name and a destination path, with an option to force a refresh of the cached sample list.
- [Untitled](https://docs.stripe.com/cli/samples/list.md): The `stripe samples list` command displays a list of available Stripe Samples that can be created and bootstrapped using the CLI. It provides a brief description and the repository link for each sample.
- [Untitled](https://docs.stripe.com/cli/serve.md): The `stripe serve` command starts an HTTP server to serve static files, defaulting to the current directory. This command is useful for serving files from local Stripe Sample copies.
- [Untitled](https://docs.stripe.com/cli/intro_additional_commands.md): This page indicates that there are additional commands available within the Stripe CLI that offer further functionality.
- [Untitled](https://docs.stripe.com/cli/terminal/quickstart.md): The `stripe terminal quickstart` command helps you quickly set up Stripe Terminal with the Verifone P400 reader. It primarily supports the `--api-key` flag for configuration.
- [Untitled](https://docs.stripe.com/cli/logout.md): The `stripe logout` command removes credentials connecting the CLI to your Stripe account. You can log out of the default project, a specific project using `--project-name`, or all projects with the `--all` flag.
- [Untitled](https://docs.stripe.com/cli/feedback.md): The `stripe feedback` command provides instructions on how to offer feedback for the Stripe CLI. It directs users to GitHub issues for bug reports and a dedicated form for feature suggestions.
- [Untitled](https://docs.stripe.com/cli/help.md): The `stripe help` command provides assistance for any command within the Stripe CLI. You can get help for a specific command by appending its path, or use the `-h` or `--help` flag for any command.
- [Untitled](https://docs.stripe.com/cli/version.md): The `stripe version` command displays the current version of the Stripe CLI. It also checks for and reports if a newer version of the software is available.
- [Untitled](https://docs.stripe.com/cli/intro_further_information.md): This page directs users to further information regarding the operational aspects of the Stripe CLI.
- [Untitled](https://docs.stripe.com/cli/docker.md): The Stripe CLI can be run within a Docker container using its official Docker image. Environment variables like `STRIPE_API_KEY` and `STRIPE_DEVICE_NAME` can be set, and `--api-key` should be used instead of `stripe-cli login` due to container ephemerality.
- [Untitled](https://docs.stripe.com/cli/telemetry.md): The Stripe CLI includes an opt-in telemetry feature that collects usage data to improve the developer experience. This data includes command usage, errors, and performance metrics, but excludes sensitive information like API keys or personal data. Telemetry can be disabled by setting the `STRIPE_CLI_TELEMETRY_OPTOUT` environment variable.
- [Untitled](https://docs.stripe.com/cli/license.md): The Stripe CLI is licensed under the Apache License 2.0. Ownership of the project is verified on GitHub as belonging to Stripe.