Skip to main content

Changelog

Follow new updates and improvements to Zemtu.

Backend 6.8.6-14

These nine ✋ releases once again bring several improvements under the hood. Highlight definitely is the signup bot protection, which we have polished in multiple releases. It’s now ready to be used by organization admins.

New 🌟

Signup rules

As bot protection, we have added ALTCHA in August. Some of the bots still get through the ALTCHA protection and for this we have implemented signup rules. This is about an additional email address check and setting up the rules your organization requires.

https://help.zemtu.com/articles/1903894-signup-email-rules

Payment toolbox

In a several months effort, we implemented a 🆕 payment toolbox with additional capabilities to serve the needs of our customers. This toolbox now cover cases like expired authorization and more.

In the following help article, the differences are explained in detail:

https://help.zemtu.com/articles/2752970-payment-toolbox

First Zemtu customers are already using the new toolbox by default and we plan to roll it out to all customers until the end of 2027.

Improved ✨

  • Improve performance of invoice item sorting. This makes processing payments and sending invoices quicker.

Fixed 😎

  • Only allow impersonation of active users.

  • Improve stability of the task workers to prevent outages.

Backend 6.8.1-5

These five ✋ summer ☀️ releases bring several improvements under the hood. Besides these updates, we put our efforts into improving the user interface in order to move the user experience to the next level.

New 🌟

Quick filters

With the 🆕 quick filters concept, we bring the most important filters to the front. As a start, for users and payments. Stay tuned for more.

Users view: quick filters.

Retry authorization on the reservation status page

Admins can now easily retry authorization payments on the central reservation status page.

Reservation status: retry authorization.
Detail view for retrying payment.

Enforced rate limits 👩‍🔧

To ensure fair service use, we now enforce rate limits throughout the Zemtu backend. If you ever encounter “429 Too Many Requests” responses, you’re requesting too fast. Don’t worry, the service just wants you to wait a little bit. When using Zemtu’s APIs, simply add exponential back-off to your requests.

Improved ✨

User overview: display godfather package payments

On the user overview, package payments paid by another payer are now being displayed.

Display of package assignments paid by someone else.

Restyle package assignments

By combining data into sections, we strive to improve readability.

Restyled package assignments view.

Fixed 😎

  • Fix sidebar not appearing on 1280 pixel screens.

Backend 6.8.0

This release brings the settings into the sidebar for quicker access, a clearer user overview, and several improvements around payments and invoicing — plus a handful of fixes to make everyday admin work smoother.

New 🌟

Settings moved to the sidebar

To make Organization, Site Configurations, and the Invoicing Party more accessible, they now live in the left sidebar. We also added the tabs Organization, Site Configurations, and Invoicing Party, so you as an admin can switch between these settings with a single click.

Settings moved to toolbar.

Reordered user overview

The user overview now follows a clearer order: Reservations, Meta payments, then Invoices.

New ordering of sections in user overview.

Payers tab

Invoices and Invoice runs now have a dedicated Payers tab.

Added Payers tab.

Zero-amount invoices marked as paid automatically

When you use the Book & Send action, invoices with a total of zero are now automatically marked as paid.

Improved ✨

  • Faster payments list
    The admin list of meta payments now loads noticeably faster.

  • Polished user overview cards
    Improved layout, filters and links across the overview table cards.

Fixed 😎

  • Edit processing date for approved payments
    Admins can now edit the processing date of approved payments, so a final capture can be rescheduled — for example, timed earlier.

Earlier updates