Adds support for setting up future usage of Naver Pay in Checkout Sessions
What’s new
Adds the ability to pass setup_future_usage as a payment method option for Naver Pay payments when creating Checkout Sessions.
Impact
You can now save payment details for Naver Pay for use in future payments.
Changes
| Parameter | Change | Resources or endpoints |
|---|---|---|
| setup_future_usage | Added | Checkout. Session. payment_method_options. naver_pay |
| Fields | Change | From → to |
| ConfirmationToken. payment_method_preview. naver_pay. buyer_id PaymentMethod. naver_pay. buyer_id | Changed | optional → required |
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-05-28. 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
- Adds South Korean payment methods to the Payment Method Configurations API
- Adds account capability for the Pix payment method for US-based sellers
- Adds option to Checkout Sessions to let customers remove saved payment methods
- Adds capture method option to Satispay payments
- Adds support for WeChat Pay for Setup Intents
- Adds network decline codes for PayPal refunds