Payment Methods won't allow modifying fields for Naver Pay once the object is first createdBreaking 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_ to update Naver Pay parameters. You can only set them when creating a PaymentMethod.
Changes
Upgrade
Related changes
- Updates the Vault and Forward API to return a 402 status code for upstream request timeouts
- Deprecates 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 BECS Direct Debit local payment method