💡 New
Confirmation required to change a customer's email address
To better protect customer accounts, changing a customer's email address now requires an additional confirmation. Customers confirm the change either with their current password or with a verification code sent to their current email address (or by SMS, if your SSO is set up to send codes by SMS). Customers without a known password, for example those who registered via Google, can use the code.
The customer API endpoint for changing the email address now expects either the current password or a verification code from the current address. Requests without one of these confirmations are rejected.
A new customer API endpoint sends the verification code to the customer's current email address.
A wrong password or code is rejected before the new address is checked, and the email address remains unchanged.
In the Self Service, the change email form now includes a password field and the option to confirm with a code instead. If the SSO module is not active, only the code option is offered.
If you change customer email addresses through the customer API from your own applications, please update your integration accordingly.
🔧 Change
Failing callback identified in warning emails
The warning emails sent when a callback keeps failing or has been deactivated now include the callback ID, the company ID and the callback URL. This makes it easier to identify and fix the affected callback before it is deactivated.
No unnecessary warning for cancellations at the end of an invoiced period
When a subscription was cancelled exactly to the end of a period that had already been invoiced, an unnecessary warning was logged in the system monitoring. This warning no longer appears. Whether an invoice correction is created remains unchanged.