Skip to content
Create account or Sign in
The Stripe Docs logo
/
Ask AI
Create accountSign in
Get started
Payments
Revenue
Platforms and marketplaces
Money management
Developer resources
APIs & SDKsHelp
Overview
Versioning
Changelog
    Overview
    Clover
    Basil
    Acacia
    Previous versions
Upgrade your API version
Upgrade your SDK version
Essentials
SDKs
API
Testing
Stripe CLI
Sample projects
Tools
Stripe Dashboard
Workbench
Developers Dashboard
Stripe Shell
Stripe for Visual Studio Code
Terraform
Features
Workflows
Event destinations
Stripe health alertsFile uploads
AI solutions
Agent toolkit
Model Context ProtocolBuild agentic AI SaaS Billing workflows
Security and privacy
Security
Stripebot web crawler
Extend Stripe
Build Stripe apps
Use apps from Stripe
Partners
Partner ecosystem
Partner certification
United States
English (United States)
HomeDeveloper resourcesChangelogClover2026-01-28.clover

Adds the ability to opt out of strict arithmetic validation for Payment Line Items

What’s new

You can now opt out of strict arithmetic validation for Payment Line Items on a per-request basis by using the amount_details.enforce_arithmetic_validation parameter.

Impact

By default, Stripe validates that your line item data passed as part of the Payment Line Items feature adds up correctly. When the sum of line items doesn’t match the total amount, Stripe returns a 400 error so you can correct discrepancies before processing the payment.

You can now opt out of this strict validation on a per-request basis by setting amount_details.enforce_arithmetic_validation to false. When you do this:

  • The request proceeds even if line item amounts don’t match the total.
  • Stripe returns validation error details in the amount_details.error field in the response.
  • For card payments, Stripe doesn’t send line item data with arithmetic errors to card networks, preventing the transaction from qualifying for L2/L3 interchange savings.

Changes

ParametersChangeResources or endpoints
enforce_arithmetic_validationAdded
PaymentIntent#capture.amount_detailsPaymentIntent#confirm.amount_detailsPaymentIntent#create.amount_details
 + 2 more
PaymentIntent#increment_authorization.amount_detailsPaymentIntent#update.amount_details
errorAdded
PaymentIntent.amount_details

Upgrade

  1. View your current API version in Workbench.
  2. 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-01-28.clover
  3. Upgrade the API version used for webhook endpoints.
  4. Test your integration against the new version.
  5. If you use Connect, test your Connect integration.
  6. In Workbench, perform the upgrade. You can roll back the version for 72 hours.

Learn more about Stripe API upgrades.

Related changes

  • Adds support for 3D Secure versions 2.3.0 and 2.3.1
  • Adds the ability to monitor reserve activity on Balance Transactions and reconcile Risk Reserved balance changes
  • Adds Adyen as an issuer for iDEAL payments
  • Adds adjustable quantity to the line items response
Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc