detektu
Supported APIs

Vendor coverage

Stripe API changes & breaking changes

Review changes to Stripe's published API contracts before updating your payments integration. Inspect the changed operation and field, check the API version and preview channel, then monitor the operations your services use.

Last checked Oct 20, 2026, 2:38 PMLast change detected Oct 15, 2026, 1:26 AM

1 catalog dependency on Free · Email digests · No card required.

Detected changes

Latest Stripe API changes

Inspect each finding's source, channel, and before-and-after evidence. API and documentation changes appear first within each page; SDK activity is listed separately.

API and documentation changes

  1. Info
    SDK release 23.1.0-alpha.3sdk:npm/stripe@23.1.0-alpha.3
    Stripe API
  2. Info
    SDK release 23.1.0-alpha.3sdk:npm/stripe@23.1.0-alpha.3
    Stripe API
  3. Info
    SDK release 23.1.0-alpha.2sdk:npm/stripe@23.1.0-alpha.2
    Stripe API
  4. Info
    SDK release 23.1.0-alpha.2sdk:npm/stripe@23.1.0-alpha.2
    Stripe API
  5. Info
    SDK release 23.1.0-beta.1sdk:npm/stripe@23.1.0-beta.1
    Stripe API
  6. Info
    SDK release 23.1.0-alpha.1sdk:npm/stripe@23.1.0-alpha.1
    Stripe API
  7. Info
    SDK release 23.1.0-beta.1sdk:npm/stripe@23.1.0-beta.1
    Stripe API
  8. Info
    SDK release 23.1.0-alpha.1sdk:npm/stripe@23.1.0-alpha.1
    Stripe API
  9. Info
    Response property any of added: payment_method_detailsopenapi:POST /v1/radar/payment_evaluations::response.200.application.json.payment_details.payment_method_details
    Stripe API
  10. Info
    Response optional property added: snapshot_eventopenapi:GET /v2/core/events/{}::response.200.application.json.snapshot_event
    Stripe API

Review checklist

Review a Stripe API change

Use the evidence to decide what needs testing in your integration.

  1. Check request and webhook versions

    Look up recent requests in Stripe Workbench and check any Stripe-Version override. Review webhook endpoint versions separately before changing your account default.

  2. Inspect the payment operation

    Open a finding's before-and-after evidence and compare the changed request or response with your integration. Check the official changelog for the release and migration guidance.

  3. Test the upgrade and keep monitoring

    Test payment flows and webhook handling against the intended version. In Detektu, select the operations and fields your services use to match future findings to declared usage.

Coverage

What Detektu monitors

Catalog contracts configured for monitoring. Check each source link for its version and channel.

Change model

How Stripe ships changes

The release patterns that shape your integration risk.

Stripe groups breaking API changes into named major releases. Monthly releases within the same release family are backward-compatible. Your request and webhook versions determine which behavior you receive, so a change in the latest published contract needs to be checked against your integration's version.

Detektu monitors Stripe's latest GA and public preview OpenAPI contracts separately. Findings describe observed source changes; they do not establish that your pinned API version or application has changed. SDK releases have their own history and should be reviewed alongside the API changelog.

Official Stripe references

Versioning guidance reviewed . Check the official references for current policy and dates.

Monitored for you

Do Stripe's changes affect your integration?

Choose the operations and fields your services use. Detektu matches Stripe findings to that declared usage so your team can review the relevant evidence. No agent or repository access required.