We check Stripe's changelog and OpenAPI spec every day, because we run production integrations on the Stripe API. This page lists the 84 changes we have recorded since monitoring started on 27 March 2026, newest first.
Our last successful check was on 30 September 2026. We are on it; until then this page may miss the newest changes.
No breaking changes or deprecations in the Stripe API in the last 90 days.
Latest detection, 30 September 2026 Stripe added the `first_payment_failure` and `final_payment_failure` enum values to the response field `status_details.paused.subscription.type` across endpoints including `/v1/billing/alerts`, `/v1/checkout/sessions`, `/v1/credit_notes`, and `/v1/customers`. Update response parsing to accept these values (and avoid assuming the enum is closed); no deadline is specified.
Labels are assigned automatically. Check the vendor's note before planning work around an entry.
Adds parameter for allowed payment method types to Payment Intents and Setup Intents.
Adds ability to update shipping options, consent collection, and future usage support on Payment Links.
Adds customer and payment method details to the Refunds API.
Adds ability to specify that Samsung Pay and PAYCO payment methods should not be reused.
Renames Link Authentication Element to Contact Details Element.
Adds Account as a new item type for Radar value lists.
Adds an amount confirmation parameter to the Payment Intent API.
Removes the mandatory KYC onboarding requirement for app distribution payments for Stripe Apps.
Adds support for Azure Event Grid as an event destination.
Adds a card presence spending control capability for Issuing.
Adds embedded components for balance report and payout reconciliation report to the Account Session API.
Adds an expandable tax rate property to tax rate details in the Invoicing product.
Adds a fulfillment error reason to Issuing card cancellation and replacement reasons.
Adds QR code support for Klarna payments when using Terminal readers.
Adds support for Managed Payments, Stripe's merchant of record solution.
Adds MOTO (mail order/telephone order) property to payment method details for card setup attempts.
Adds new balance transaction types for inbound transfers and reversals in Treasury.
Adds tax ID types for Faroe Islands, Gibraltar, Italy, and Paraguay to capture and store tax identification data.
Adds support for Phantom Cash and USDT in stablecoin payments.
Adds support for recurring payments using Pix payment method.
Introduces the Product Catalog Import API v2.
Adds crypto fingerprint support to Radar value list items for enhanced fraud detection.
Adds support for decimal quantities in invoicing for more precise billing.
Adds integration identifier parameter to Checkout Sessions for better tracking and integration management.
Adds marine carbon removal pathway to Climate Orders for expanded sustainability options.
Adds metadata property to credit note line items for enhanced tracking.
Adds granular control for crypto payment method future usage configuration in Checkout Sessions.
Adds presentment details for Adaptive Pricing Subscriptions to improve pricing transparency.
Adds retention policy cancellation reason to Subscriptions for improved subscription tracking.
Adds risk requirements to Capabilities API for Connect enhancements.
Adds payment limit controls for Issuing cards for enhanced card lifecycle management.
Adds Tempo network as a supported blockchain for crypto payments.
Changes the Address Element state field default formatting to Latin characters, affecting existing integrations with non-Latin character handling.
Updates Checkout Session UI mode enum values.
Updates elements.update() method to return a Promise.
Removes the requirement for certain connected accounts to collect external account information in the Account Sessions API.
Removes deprecated Payment Intents, Setup Intents, and Sources methods from Stripe.js.
Removes support for boolean values in options.layout.radios for Elements, breaking integrations that use this configuration.
Renames the Checkout initialization method.
Updates card property requirements for PaymentRecords, which may affect existing payment record implementations.
Updates events_from parameter on event destinations to accept string values for greater flexibility.
Makes Visa card reference ID optional in Issuing Token, reducing required fields.
Updates the process for configuring future usage in the Payment Element, requiring integration updates.
Adds support for UPI payment method.
Adds display name and service user number fields to Bacs Direct Debit mandates for improved payment method details.
Adds webhook events for reserve hold, release, and plan operations in payments.
Adds Pay by Bank as a supported payment method in Billing API.
Adds payment behavior control options when deleting subscription items.
Adds settlement type field to Application Fee objects.
Adds Sri Lanka VAT number support for tax identification.
Adds ability to upload and manage Wi-Fi certificates and private keys for Terminal readers.
Adds support for managing cellular connectivity configuration on Terminal readers.
Adds transaction purpose field to PaymentIntents for US bank account payments.
Makes Boleto tax ID nullable in payment method details, affecting payment record validation.
Adds support for Stripe Reader S710 terminal device.
Adds Terminal reader and location information to payment method details.
Adds adjustable quantity field to Checkout line items response.
Adds Adyen as a supported iDEAL issuer for payment processing.
Provides OpenAPI specification artifacts for v2 API endpoints.
Adds support for newer 3D Secure protocol versions for enhanced authentication.
Adds Polish NIP tax ID type support.
Adds option to disable strict arithmetic validation on Payment Line Items.
Adds company registration date field to Accounts v2 objects.
Adds contact phone parameter to Accounts API.
Adds top-up field to Treasury ReceivedDebit linked flows.
Updates Terminal currency mapping for Bulgaria from BGN to EUR.
Restores support for setting amount-off coupon duration to forever.
Adds the ability to monitor reserve activity on Balance Transactions and reconcile Risk Reserved balance changes.
Makes the client secret parameter optional for Financial Connections sessions.
Makes flexible billing mode the standard for new subscriptions.
Updates initCheckout to execute synchronously instead of asynchronously.
Removes the postal code requirement for card payments in certain regions in Checkout and Payment Element.
Removes support for the redirectToCheckout method.
Adds discount_source property and removes discount_coupon property from discount objects.
Removes deprecated Bank Elements and replaces them with newer implementations.
Removes the iterations parameter for subscription plans.
Deprecates alphanumeric_id for Issuing Authorization with future removal planned.
Deprecates the bank_transfer_payments capability type in favor of newer capability types.
Adds enum values for fuel units in the Issuing API.
Adds new enum values for request history reasons in the Issuing API.
Renames a purchase_details attribute of the Transaction object in the Issuing API.
Removes undocumented fleet fields from Issuing API.
Makes automatic sync the default capture method for PaymentIntents when not specified.
Renames the features attribute of the Product object.
Differences between consecutive versions of Stripe's published OpenAPI spec, as reported by oasdiff. Only changes that break or may break existing clients are listed.
GET /v1/billing/alerts added the new 'final_payment_failure' enum value to the 'data/items/usage_threshold/anyOf[subschema #1: Usage threshold alert configuration]/filters/items/customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' GET /v1/billing/alerts added the new 'first_payment_failure' enum value to the 'data/items/usage_threshold/anyOf[subschema #1: Usage threshold alert configuration]/filters/items/customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' POST /v1/billing/alerts added the new 'final_payment_failure' enum value to the 'usage_threshold/anyOf[subschema #1: Usage threshold alert configuration]/filters/items/customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' POST /v1/billing/alerts added the new 'first_payment_failure' enum value to the 'usage_threshold/anyOf[subschema #1: Usage threshold alert configuration]/filters/items/customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' GET /v1/billing/alerts/{id} added the new 'final_payment_failure' enum value to the 'usage_threshold/anyOf[subschema #1: Usage threshold alert configuration]/filters/items/customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' GET /v1/billing/alerts/{id} added the new 'first_payment_failure' enum value to the 'usage_threshold/anyOf[subschema #1: Usage threshold alert configuration]/filters/items/customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' POST /v1/billing/alerts/{id}/activate added the new 'final_payment_failure' enum value to the 'usage_threshold/anyOf[subschema #1: Usage threshold alert configuration]/filters/items/customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' POST /v1/billing/alerts/{id}/activate added the new 'first_payment_failure' enum value to the 'usage_threshold/anyOf[subschema #1: Usage threshold alert configuration]/filters/items/customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' POST /v1/billing/alerts/{id}/archive added the new 'final_payment_failure' enum value to the 'usage_threshold/anyOf[subschema #1: Usage threshold alert configuration]/filters/items/customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' POST /v1/billing/alerts/{id}/archive added the new 'first_payment_failure' enum value to the 'usage_threshold/anyOf[subschema #1: Usage threshold alert configuration]/filters/items/customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' POST /v1/billing/alerts/{id}/deactivate added the new 'final_payment_failure' enum value to the 'usage_threshold/anyOf[subschema #1: Usage threshold alert configuration]/filters/items/customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' POST /v1/billing/alerts/{id}/deactivate added the new 'first_payment_failure' enum value to the 'usage_threshold/anyOf[subschema #1: Usage threshold alert configuration]/filters/items/customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' GET /v1/billing/credit_balance_summary added the new 'final_payment_failure' enum value to the 'customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' GET /v1/billing/credit_balance_summary added the new 'first_payment_failure' enum value to the 'customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' GET /v1/billing/credit_grants added the new 'final_payment_failure' enum value to the 'data/items/customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' GET /v1/billing/credit_grants added the new 'first_payment_failure' enum value to the 'data/items/customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' POST /v1/billing/credit_grants added the new 'final_payment_failure' enum value to the 'customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' POST /v1/billing/credit_grants added the new 'first_payment_failure' enum value to the 'customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' GET /v1/billing/credit_grants/{id} added the new 'final_payment_failure' enum value to the 'customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' GET /v1/billing/credit_grants/{id} added the new 'first_payment_failure' enum value to the 'customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' POST /v1/billing/credit_grants/{id} added the new 'final_payment_failure' enum value to the 'customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' POST /v1/billing/credit_grants/{id} added the new 'first_payment_failure' enum value to the 'customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' POST /v1/billing/credit_grants/{id}/expire added the new 'final_payment_failure' enum value to the 'customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' POST /v1/billing/credit_grants/{id}/expire added the new 'first_payment_failure' enum value to the 'customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' POST /v1/billing/credit_grants/{id}/void added the new 'final_payment_failure' enum value to the 'customer/anyOf[subschema #2: Customer]/subscriptions/data/items/status_details/paused/subscription/type' response property for the response status '200' We watch Stripe because we run integrations on it. If one of yours depends on Stripe, we can take it over: build it properly, operate it, and fix it when Stripe changes, before your data is affected. Fixed-price scoping quote within 48 hours.