- Breaking changes
- Public preview
Adds validation for billing meter event values with more than 15 digits Breaking changes Public preview
What’s new
Introduces validation that rejects billing meter event values with more than 15 significant digits. For the synchronous API, requests with such values now return a 400 error. For async meter events, Stripe reports the rejection through the v1.billing.meter.error_report_triggered event with the new meter_event_value_too_many_digits error code.
The error message provides specific details about the validation failure: “The value in the event payload can have at most max_digits digits. Received value.”
Why is this a breaking change?
This change is breaking because it introduces new validation that can cause API requests to fail. If your integration currently sends usage values with more than 15 significant digits, those requests now return a 400 error instead of being processed. You must update your code to make sure all usage values contain 15 or fewer significant digits before sending them to the Meter Events API.
Impact
If your integration sends usage values with more than 15 significant digits, modify your code to validate and truncate or round these values before making API requests. This prevents data corruption that can occur due to double precision loss in the usage aggregation pipeline.
You can now also handle the new meter_event_value_too_many_digits error code in your error handling logic to provide appropriate feedback when validation fails.
Changes
| Value | Change | Enums |
|---|---|---|
| meter_event_value_too_many_digits | Added | EventsV1BillingMeterErrorReportTriggeredEvent. reason. error_types[] EventsV1BillingMeterNoMeterFoundEvent. reason. error_types[] |
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: 2026-04-22. preview
- 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.