Updates the Vault and Forward API to return a 402 status code for upstream request timeouts
The Vault and Forward API now returns a 402 error instead of 502 and 504 errors for specific scenarios. Some users might expect either 502 or 504 statuses for upstream errors. Update your code to expect 402 statuses as well.
docs.stripe.comquote checked- behaviour change
- Your codeby hand
Nemotron fixes
In its own wordsmatches the page ✓
| [Updates the Vault and Forward API to return a 402 status code for upstream request timeouts](https://docs.stripe.com/changelog/basil/2025-03-31/vault-forward-api-returns-402.md) | Payments | Breaking | api |
Also readmatches the page ✓
Some users might expect either `502` or `504` statuses for upstream errors. Update your code to expect `402` statuses as well.
- 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.
What Teire looks for in your code
nothing to search for: checked by hand
Does it reach your code?