Breaking changes
Lets the description and email fields be null on several objects Breaking changes
What’s new
Allows the description property on Customer, Charge, InvoiceItem, and Recipient objects, and the email property on Customer and Recipient objects, to be set to null by providing empty string values in POST requests.
Impact
Allows setting description and email to null on various objects, providing more flexibility in how you manage data.
Changes
| Fields | Change | From → to |
|---|---|---|
| Customer. description | Changed | string → nullable(string) |
| Charge. description | Changed | string → nullable(string) |
| InvoiceItem. description | Changed | string → nullable(string) |
| Recipient. description | Changed | string → nullable(string) |
| Customer. email | Changed | string → nullable(string) |
| Recipient. email | Changed | string → nullable(string) |
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: 2013-08-12
- 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.