Makes the client parameter optional for WeChat Pay until confirmation
What’s new
We’ve made the client parameter optional until confirmation time for WeChat Pay payment method options. The parameter is still required at confirmation time, so you must provide the client before you confirm the payment.
Impact
When you create or update a Payment Intent that supports WeChat Pay, but don’t provide a value for the client parameter, you no longer receive a missing parameter error.
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
- Payment Methods won’t allow modifying fields for Naver Pay once 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
- Adds support for the New Zealand BECS Direct Debit local payment method