Breaking changes
Customers no longer include a next_recurring_charge field Breaking changes
What’s new
Removes the next_recurring_charge property from the Customer object. Use the upcoming invoice call instead.
Impact
The removal of the next_recurring_charge property from the Customer object encourages use of more accurate upcoming invoice call.
Changes
| Parameter | Change | Resources or endpoints |
|---|---|---|
| next_recurring_charge | Removed | Customer |
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: 2012-03-25
- 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.
