In payment processing, arithmetic validation ensures that the sum of individual line items perfectly matches the total transaction amount. While this strict validation is useful, it can sometimes cause friction during the payment capture process.

PayPack provides merchants with the flexibility to enable or disable enforcing arithmetic validation at the time of capture, ensuring that your payment workflows remain seamless even when data discrepancies occur.

Why Disable Arithmetic Validation?

It is a common scenario for merchants to use Stripe integrations outside of NetSuite (e.g. BigCommerce, WooCommerce, Magento/Adobe Commerce, etc.) that pass specific line item data during the initial payment authorization. However, when it is time to capture that Payment Intent, NetSuite might not have the exact same line item data constructed within the ERP.

If strict arithmetic validation is forced at the time of capture, these line item data mismatches will cause the capture to fail.

By unchecking this setting, PayPack  tells Stripe to loosen the arithmetic requirements. This gives you the flexibility to authorize with one set of line items and capture with another (or without perfectly matching ERP data), ensuring your payments are successfully processed without unnecessary bottlenecks.

How to Configure the Setting

You can easily toggle this setting on or off depending on your business needs.

1. Navigate to PayPack Configuration.
2. Click on the General tab.
3. Scroll down to the Interchange section.
4. Locate the Arithmetic Validation checkbox:
   • Check the box to enable strict arithmetic validation (line items must match the capture total exactly).
   • Uncheck the box to disable it (loosens the validation so captures can proceed despite line item discrepancies).
5. Save your configuration changes.

Additional Resources

This PayPack configuration leverages Stripe’s flexible capture capabilities. If you want to learn more about how Stripe handles loosened arithmetic validation and Payment Intent captures on the backend, you can review Stripe Docs: Loosen arithmetic validation.