- Allow removal of a reconcilation line for only 8 minutes
- This was previously 2 hours, but was changes as it otherwise caused sync problems with BI and Finance
- Be able to block users based on invoice payment status
- New
ErrorCode 636 for AbelSecureService/BookTrip to indicate that a user cannot book new trips, as he/she has not paid all his invoices. Will only be triggered if (un)block based on invoice payment status has been checked in the admin panel
- Customers can again be enabled and disabled manually in the admin panel, independent of the
bookTrip-block based on payment status. Customers that are disabled in the admin panel cannot login at all.
- Once a blocked customer has repaid all his invoices, he will automatically be enabled and informed by email (if (un)block based on invoice payment status has been checked in the admin panel). The email can be defined with the “Account unblocked” template
- Simplified response structure of secure tripTariff
- For Api version >= 20170121, the response of a secured
tripTariff call will contain payment methods under ['result']['FeasiblePaymentMethods'] instead of ['result']['FeasiblePaymentMethods']['PaymentMethods']].