Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Revenue
Platforms and marketplaces
Money management
Developer resources
Overview
Versioning
Changelog
    Overview
    Clover
    Basil
    Acacia
    Previous versions
Upgrade your API version
Upgrade your SDK version
Essentials
SDKs
API
Testing
Stripe CLI
Sample projects
Tools
Stripe Dashboard
Workbench
Developers Dashboard
Stripe Shell
Stripe for Visual Studio Code
Features
Workflows
Event Destinations
Stripe health alertsFile uploads
AI solutions
Agent toolkit
Model Context ProtocolBuild agentic AI SaaS Billing workflows
Security and privacy
Security
Stripebot web crawler
Privacy
Extend Stripe
Build Stripe apps
Use apps from Stripe
Partners
Partner ecosystem
Partner certification
HomeDeveloper resourcesChangelogClover2025-09-30.clover

Adds additional enum values for Radar manual reviewsBreaking changes

What’s new

Adds the following values to the closed_reason enum:

  • acknowledged: The review was acknowledged and then closed.
  • payment_never_settled: The review was closed because the payment never settled.

Why is this a breaking change?

If your integration handles the closed_reason enum to expect only the previous set of values, this change might break it.

Impact

We added these enum values to support manual reviews for Radar on bank debits because the previous set of enum values didn’t account for all states that might occur in asynchronous bank debit flows. You can use the new values for states where:

  • The review was acknowledged and then closed (acknowledged).
  • The review was closed because the payment never settled (payment_never_settled).

Update your integration to make sure any code that handles the closed_reason response expects these new values.

Changes

ValuesChangeEnum
acknowledgedpayment_never_settledAdded
Review.closed_reason

Upgrade

  1. View your current API version in Workbench.
  2. If you use an SDK, upgrade to the corresponding SDK version for this API version.
    • If you don’t use an SDK, update your API requests to include Stripe-Version: 2025-09-30.clover
  3. Upgrade the API version used for webhook endpoints.
  4. Test your integration against the new version.
  5. If you use Connect, test your Connect integration.
  6. In Workbench, perform the upgrade. You can roll back the version for 72 hours.

Learn more about Stripe API upgrades.

Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Join our early access programme.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc