Adds ability to configure saved payment methods for one-time payments on the hosted invoice page
What’s new
You can now specify whether the hosted invoice page saves payment methods for reuse after a customer makes a one-time invoice payment.
Impact
With this update, you can control whether customer payment methods are saved for future use when customers make one-time invoice payments through the hosted invoice page. This can help increase conversion rates by allowing customers to save their payment method for future payments.
Changes
| Parameters | Change | Resources or endpoints |
|---|---|---|
| hosted_payment_method_save | Added | Account#update. settings. invoices Account. settings. invoices |
| invoices | Added | Account#create. settings |
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 .
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 cancelling payments no longer creates a Refund
- Adds support for Klarna in 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