← Alle überwachten APIs
Stripe // api-changelog

Stripe API-Changelog

Wir prüfen täglich den Changelog und die OpenAPI-Spezifikation von Stripe, weil wir produktive Integrationen auf der Stripe API betreiben. Diese Seite listet die 84 Änderungen, die wir seit Beginn der Überwachung am 27. März 2026 erfasst haben, die neuesten zuerst.

Die Einträge geben die englischsprachigen Changelogs der Anbieter wieder und stehen deshalb auf Englisch.

Die letzte erfolgreiche Prüfung war am 30. September 2026. Wir kümmern uns darum; bis dahin fehlen hier eventuell die neuesten Änderungen.

Kurz gesagt

Keine Breaking Changes oder Deprecations in der Stripe API in den letzten 90 Tagen.

Letzte Erkennung, 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.

0 Breaking, 90 Tage
0 Deprecations, 90 Tage
84 Erfasste Änderungen
Zuletzt geprüft

Änderungen an der Stripe API

Die Einordnung erfolgt automatisch. Prüfen Sie die Notiz des Anbieters, bevor Sie Aufwand einplanen.

Juli 2026

  1. Payment Intents and Setup Intents - Allowed payment method types parameter

    Adds parameter for allowed payment method types to Payment Intents and Setup Intents.

  2. Payment Links - Update endpoint with new parameters

    Adds ability to update shipping options, consent collection, and future usage support on Payment Links.

  3. Refunds API - Customer and payment method details

    Adds customer and payment method details to the Refunds API.

  4. Samsung Pay and PAYCO - Setup future usage none only

    Adds ability to specify that Samsung Pay and PAYCO payment methods should not be reused.

Mai 2026

  1. Elements - Link Authentication Element renamed to Contact Details Element

    Renames Link Authentication Element to Contact Details Element.

April 2026

  1. Account as new item type in Radar value lists

    Adds Account as a new item type for Radar value lists.

  2. Amount confirmation parameter for Payment Intent API

    Adds an amount confirmation parameter to the Payment Intent API.

  3. App Distribution - Remove mandatory KYC onboarding

    Removes the mandatory KYC onboarding requirement for app distribution payments for Stripe Apps.

  4. Azure Event Grid event destination support

    Adds support for Azure Event Grid as an event destination.

  5. Card presence spending control for Issuing

    Adds a card presence spending control capability for Issuing.

  6. Embedded components for balance and payout reconciliation reports

    Adds embedded components for balance report and payout reconciliation report to the Account Session API.

  7. Expandable tax rate property in tax rate details

    Adds an expandable tax rate property to tax rate details in the Invoicing product.

  8. Fulfillment error for Issuing card cancellation

    Adds a fulfillment error reason to Issuing card cancellation and replacement reasons.

  9. Klarna QR code support with Terminal readers

    Adds QR code support for Klarna payments when using Terminal readers.

  10. Managed Payments - New merchant of record solution

    Adds support for Managed Payments, Stripe's merchant of record solution.

  11. MOTO property for card setup attempts

    Adds MOTO (mail order/telephone order) property to payment method details for card setup attempts.

  12. New balance transaction types for inbound transfers

    Adds new balance transaction types for inbound transfers and reversals in Treasury.

  13. New tax ID types for multiple countries

    Adds tax ID types for Faroe Islands, Gibraltar, Italy, and Paraguay to capture and store tax identification data.

  14. Phantom Cash and USDT stablecoin support

    Adds support for Phantom Cash and USDT in stablecoin payments.

  15. Pix recurring payments support

    Adds support for recurring payments using Pix payment method.

  16. Product Catalog Import API v2

    Introduces the Product Catalog Import API v2.

März 2026

  1. Adds crypto fingerprint support to Radar value list items

    Adds crypto fingerprint support to Radar value list items for enhanced fraud detection.

  2. Adds decimal quantity support for Invoice Items and Invoice Line Items

    Adds support for decimal quantities in invoicing for more precise billing.

  3. Adds integration identifier parameter to Checkout Sessions

    Adds integration identifier parameter to Checkout Sessions for better tracking and integration management.

  4. Adds marine carbon removal as a new Climate Orders pathway

    Adds marine carbon removal pathway to Climate Orders for expanded sustainability options.

  5. Adds metadata property to credit note line items

    Adds metadata property to credit note line items for enhanced tracking.

  6. Adds payment method-level support for configuring future usage of crypto payment methods in Checkout Sessions

    Adds granular control for crypto payment method future usage configuration in Checkout Sessions.

  7. Adds presentment details for Adaptive Pricing Subscriptions

    Adds presentment details for Adaptive Pricing Subscriptions to improve pricing transparency.

  8. Adds retention policy cancellation reason to Subscriptions

    Adds retention policy cancellation reason to Subscriptions for improved subscription tracking.

  9. Adds risk requirements to the Capabilities API

    Adds risk requirements to Capabilities API for Connect enhancements.

  10. Adds support for limiting the number of allowed payments for Issuing cards

    Adds payment limit controls for Issuing cards for enhanced card lifecycle management.

  11. Adds Tempo network support for crypto payments

    Adds Tempo network as a supported blockchain for crypto payments.

  12. Changes the Address Element state field to default to Latin-formatted characters

    Changes the Address Element state field default formatting to Latin characters, affecting existing integrations with non-Latin character handling.

  13. Checkout Session UI mode enum values updated

    Updates Checkout Session UI mode enum values.

  14. elements.update() returns Promise

    Updates elements.update() method to return a Promise.

  15. External account collection requirement relaxed

    Removes the requirement for certain connected accounts to collect external account information in the Account Sessions API.

  16. Legacy Stripe.js methods removed

    Removes deprecated Payment Intents, Setup Intents, and Sources methods from Stripe.js.

  17. Removes support for boolean values in options.layout.radios

    Removes support for boolean values in options.layout.radios for Elements, breaking integrations that use this configuration.

  18. Renames Checkout initialization method

    Renames the Checkout initialization method.

  19. Updates card property requirements and adds 3D Secure authentication properties to PaymentRecordPayments

    Updates card property requirements for PaymentRecords, which may affect existing payment record implementations.

  20. Updates the events_from parameter on event destinations to accept string values

    Updates events_from parameter on event destinations to accept string values for greater flexibility.

  21. Updates the Issuing Token card reference ID for Visa to be optional

    Makes Visa card reference ID optional in Issuing Token, reducing required fields.

  22. Updates the process for configuring future usage in the Payment Element

    Updates the process for configuring future usage in the Payment Element, requiring integration updates.

  23. UPI payment method support

    Adds support for UPI payment method.

Februar 2026

  1. Adds display name and service user number to Bacs Direct Debit mandates

    Adds display name and service user number fields to Bacs Direct Debit mandates for improved payment method details.

  2. Adds events for reserve holds, releases, and plans

    Adds webhook events for reserve hold, release, and plan operations in payments.

  3. Adds Pay by Bank to the Billing API

    Adds Pay by Bank as a supported payment method in Billing API.

  4. Adds payment behavior control for subscription item deletion

    Adds payment behavior control options when deleting subscription items.

  5. Adds settlement type to Application Fee objects

    Adds settlement type field to Application Fee objects.

  6. Adds support for Sri Lanka VAT numbers

    Adds Sri Lanka VAT number support for tax identification.

  7. Adds support for uploading Terminal Wi-Fi certificates and private keys

    Adds ability to upload and manage Wi-Fi certificates and private keys for Terminal readers.

  8. Adds the ability to manage cellular connectivity settings for Terminal readers

    Adds support for managing cellular connectivity configuration on Terminal readers.

  9. Adds transaction purpose to PaymentIntents for US bank account payments

    Adds transaction purpose field to PaymentIntents for US bank account payments.

  10. Makes Boleto tax ID nullable in payment method details for Payment Records

    Makes Boleto tax ID nullable in payment method details, affecting payment record validation.

  11. Stripe Reader S710 support

    Adds support for Stripe Reader S710 terminal device.

  12. Terminal reader and location in payment method details

    Adds Terminal reader and location information to payment method details.

Januar 2026

  1. Adds adjustable quantity to the line items response

    Adds adjustable quantity field to Checkout line items response.

  2. Adds Adyen as an issuer for iDEAL payments

    Adds Adyen as a supported iDEAL issuer for payment processing.

  3. Adds OpenAPI artifacts containing v2 API endpoints

    Provides OpenAPI specification artifacts for v2 API endpoints.

  4. Adds support for 3D Secure versions 2.3.0 and 2.3.1

    Adds support for newer 3D Secure protocol versions for enhanced authentication.

  5. Adds support for Polish NIP tax ID type

    Adds Polish NIP tax ID type support.

  6. Adds the ability to opt out of strict arithmetic validation for Payment Line Items

    Adds option to disable strict arithmetic validation on Payment Line Items.

  7. Adds the ability to specify a company's registration date on Accounts v2 objects

    Adds company registration date field to Accounts v2 objects.

  8. Adds the contact phone parameter to the Accounts API

    Adds contact phone parameter to Accounts API.

  9. Adds the top-up field to Treasury ReceivedDebit linked flows

    Adds top-up field to Treasury ReceivedDebit linked flows.

  10. Changes currency mapping for Bulgaria from BGN to EUR

    Updates Terminal currency mapping for Bulgaria from BGN to EUR.

  11. Reintroduces the ability to set an amount-off coupon's duration to forever

    Restores support for setting amount-off coupon duration to forever.

  12. Reserve activity monitoring on Balance Transactions

    Adds the ability to monitor reserve activity on Balance Transactions and reconcile Risk Reserved balance changes.

November 2025

  1. Financial Connections - Client secret now optional

    Makes the client secret parameter optional for Financial Connections sessions.

September 2025

  1. Billing mode - Flexible billing now default for new subscriptions

    Makes flexible billing mode the standard for new subscriptions.

  2. Checkout - initCheckout now executes synchronously

    Updates initCheckout to execute synchronously instead of asynchronously.

  3. Checkout - Remove postal code for card payments

    Removes the postal code requirement for card payments in certain regions in Checkout and Payment Element.

  4. Checkout - Remove redirectToCheckout method support

    Removes support for the redirectToCheckout method.

  5. Discounts - Add discount source and remove discount coupon property

    Adds discount_source property and removes discount_coupon property from discount objects.

  6. Elements - Remove deprecated Bank Elements

    Removes deprecated Bank Elements and replaces them with newer implementations.

  7. Subscription Plans - Remove iterations parameter

    Removes the iterations parameter for subscription plans.

Juni 2024

  1. Alphanumeric ID deprecated for Issuing Authorization

    Deprecates alphanumeric_id for Issuing Authorization with future removal planned.

  2. Bank transfer payments capability type deprecated

    Deprecates the bank_transfer_payments capability type in favor of newer capability types.

  3. Fuel unit enum values added to Issuing

    Adds enum values for fuel units in the Issuing API.

  4. New request history reason enum values for Issuing

    Adds new enum values for request history reasons in the Issuing API.

  5. Purchase details attribute renamed in Transaction object

    Renames a purchase_details attribute of the Transaction object in the Issuing API.

  6. Undocumented fleet fields removed from Issuing

    Removes undocumented fleet fields from Issuing API.

April 2024

  1. Automatic sync as default capture method for PaymentIntents

    Makes automatic sync the default capture method for PaymentIntents when not specified.

  2. Product features attribute renamed

    Renames the features attribute of the Product object.

Änderungen an der OpenAPI-Spezifikation

Unterschiede zwischen aufeinanderfolgenden Versionen der veröffentlichten OpenAPI-Spezifikation von Stripe, ermittelt mit oasdiff. Aufgeführt sind nur Änderungen, die bestehende Clients brechen oder brechen können.

  1. 234 potenziell brechende Änderungen
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • Potenziell brechend 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'
    • und 209 weitere

Häufige Fragen

Gab es zuletzt Breaking Changes in der Stripe API?
Nicht in den letzten 90 Tagen, soweit der Changelog von Stripe und unsere täglichen Prüfungen zeigen.
Wie oft ändert sich die Stripe API?
Im erfassten Zeitraum hat Stripe rund 3 Changelog-Einträge pro Monat veröffentlicht. Die meisten sind Erweiterungen; einplanen sollte man vor allem die Breaking Changes und Deprecations.
Wo finde ich den offiziellen Changelog der Stripe API?
Stripe veröffentlicht ihn unter https://docs.stripe.com/changelog. Diese Seite verfolgt ihn täglich und datiert jeden Eintrag.
Wie erfahre ich von Änderungen an der Stripe API?
Abonnieren Sie den RSS-Feed dieser Seite (https://seamless.engineering/api-changelog/stripe/rss.xml). Soll sich lieber jemand darum kümmern: Wir betreiben Stripe-Integrationen und fangen solche Änderungen ab, bevor sie in Produktion ankommen.

Weitere überwachte APIs

// anfrage

Wir beobachten Stripe, weil wir Integrationen darauf betreiben. Hängt eine Ihrer Integrationen an Stripe, übernehmen wir sie: sauber gebaut, dauerhaft betrieben und angepasst, wenn Stripe etwas ändert, bevor Ihre Daten betroffen sind. Festpreisangebot innerhalb von 48 Stunden.

Wir melden uns innerhalb eines Werktags. Kein Newsletter, keine Vertriebsstrecke.