Breaking changes
Payment Methods won't allow modifying fields for Naver Pay after the object is first created Breaking changes
What’s new
Removes the ability to update Naver Pay parameters on a PaymentMethod object. You can only set them when first creating a PaymentMethod.
Why is this a breaking change?
This change removes the ability to update Naver Pay parameters when you update a PaymentMethod.
Impact
You can no longer use POST /v1/payment_methods/:id to update Naver Pay parameters. You can only set them when creating a PaymentMethod.
Changes
| Parameter | Change | Resources or endpoints |
|---|---|---|
| naver_pay | Removed | PaymentMethod#update |
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
- Updates the Vault and Forward API to return a 402 status code for upstream request timeouts
- Removes manual capture method for Interac cards
- 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