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 a processing status to submitted stablecoin paymentsBreaking changes

What’s new

PaymentIntents confirmed with the crypto payment method for stablecoin payments now have a status of processing when a user submits a transaction to the blockchain for processing. Users only redirect back to your integration when a payment is finalized.

Impact

If you use the crypto payment method and retrieve the PaymentIntent status while customers wait for transaction confirmation, you will see a processing status field. Previously, the PaymentIntent transitioned from requires_action to succeeded or requires_payment_method for success and failure.

If you attempt to cancel a PaymentIntent confirmed with crypto in the processing state, the request will fail with error payment_intent_invalid_cancellation_state.

You can optionally set up your webhooks to listen for a new payment_intent.processing event if you want to be notified when the PaymentIntent transitions to the processing status.

The customer won’t be redirected while the PaymentIntent has the processing status, so your integration doesn’t change.

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.

Related changes

  • Changes the set of decline codes used for Alma, Amazon Pay, Billie, Satispay, and South Korean payment methods
  • Adds a documented reason for Klarna chargeback losses to Disputes API
  • Adds support for the MB WAY payment method
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