Breaking changes
Updates the Vault and Forward API to return a 402 status code for upstream request timeouts Breaking changes
What’s new
The Vault and Forward API now returns a 402 error instead of 502 and 504 errors for specific scenarios.
Why is this a breaking change?
Some users might expect either 502 or 504 statuses for upstream errors. Update your code to expect 402 statuses as well.
Impact
Previously, the Vault and Forward API returned a 502 or 504 error for any errors with the upstream destination endpoint, regardless of connection status. Now, you receive a 402 error if a request times out before Stripe establishes a connection with the upstream, allowing for safe retries. Stripe continues returning 502 or 504 errors for all other upstream errors.
Upgrade
- View your current API version in Workbench.
- 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-03-31. basil
- Upgrade the API version used for webhook endpoints .
- Test your integration against the new version.
- If you use Connect, test your Connect integration .
- In Workbench, perform the upgrade . You can roll back the version for 72 hours.
Learn more about Stripe API upgrades.
Related changes
- Removes manual capture method for Interac cards
- Payment Methods won’t allow modifying fields for Naver Pay after the object is first created
- Partially capturing or canceling payments no longer creates a Refund
- Adds support for Klarna in the hosted invoice page
- Adds ability to configure saved payment methods for one-time payments on the hosted invoice page
- Adds support for saving and reusing Naver Pay payment methods
- Adds support for the Billie local payment method
- Adds support for the Satispay local payment method
- Makes the client parameter optional for WeChat Pay until confirmation
- Adds support for the New Zealand the related setting Direct Debit local payment method