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
| Fields | Change | From → to |
|---|---|---|
| PaymentIntent#confirm. payment_method_options. wechat_pay. client PaymentIntent#create. payment_method_options. wechat_pay. client PaymentIntent#update. payment_method_options. wechat_pay. client | Changed | required → optional |
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
- 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
- Adds support for the New Zealand the related setting Direct Debit local payment method