HomeGuidesAPI ReferenceChangelog
Terms of Use
Changelog

3.196.0 release notes

  1. New features
    1. Added the optional paymentTerms field to Operator responses on GET /public-api/resources/operators/v1.0 and GET /public-api/resources/operators/v1.0/{operator}. When configured, this field returns the operator's payment terms value.
  2. 🔧 Improvements
    1. Added explicit validation bounds to the totalAmount and authorizedAmount request fields on POST /public-api/resources/transactions/v1.0 and PATCH /public-api/resources/transactions/v1.0/{transaction}. totalAmount now requires a minimum value of 0.00, and both fields enforce a maximum of 10000000000000.00.
    2. The name, city, address, and bank detail text fields on Operator and Partner responses now return the canonical locale-independent translation value. This ensures consistent output in multi-language configurations where these values are managed as translations rather than scalar columns.
    3. The name and region/state filters on the Sub-Operator listing endpoint now match against translatable field values, and the search filter on the Partner listing endpoint is now locale-aware. Results are more accurate in multi-language configurations where names and regions are stored as translations.