Deprecating:
- Agreement and Payment property:
"paymentRequired" - Agreement property:
"defaultQuanity" - Subscription and AddOn property:
"quantity"
During 2026 we will implement a series of backward-compatible optimisations in the Payment API. These improvements aim to simplify maintenance of the source code, ensure stability, and make it easier for new integrators to work with the Payment API.
Payment Required
We found that the property “paymentRequired” caused unnecessary confusion and chose to phase it out from various user interfaces during 2024, reducing its usage intentionally. With this update we also ignore the property, should it be provided by integrators.
The original intention behind “paymentRequired” was to address arrears on an unpaid subscription – for example, when a payment card expired, and the subscription required payment for its service.
This made sense for commercial products, but not for donations, and thus created unnecessary confusion and complexity in the overall solution.
Quantity
Similarly, variations of “quantity” are suited for subscriptions of physical goods, but not for donations, which furthermore added unnecessary confusion.
With this update we ignore the above mentioned properties should they be provided by integrators.