Version 2026.01

Invoice as a payment method

Facilities can now offer invoice as a payment option. This makes it easier for businesses, teams and associations to book without having to use a card or Vipps straight away.

The invoice module has two modes:

Invoice: A traditional invoice with a payment deadline
Deferred payment: The booking goes through, but payment can be made later

You can configure who has access to pay by invoice (e.g. administrators only, or all users), which product types can be paid by invoice, and whether there should be limits on the number of unpaid invoices.

You will find the invoice configuration under admin > payment.

The admin menu also has a new page for viewing and managing invoices.

Custom confirmation text

After a successful booking, a confirmation dialog is shown to the customer. This text can now be customised under admin > facility.

You can choose between four modes:

System text only: The system generates text based on what was booked (default)
Custom text first: Your text is shown before the system text
Custom text last: Your text is shown after the system text
Custom text only: Only your custom text is shown

The custom text supports markdown, so you can use bold text for emphasis.

Hiding names on tickets

It is now possible to hide who has booked a slot from other users. Showing a public name on tickets is handy for clubs where you want to make sure you book a place on the right slot - but it can be unwanted in other contexts.

You will find the setting under admin > facility > settings.

Better error handling when booking

If something goes wrong during the payment process, the system now gives clearer feedback about what has happened. In addition, the system automatically checks the payment status and shows a dialog if the payment is taking a long time.

This makes the experience more robust, especially on an unstable network connection or when the payment provider is slow.

Stability

This version contains a major rewrite of the backend code for payments and bookings. This gives better traceability and error handling, and should solve some sporadic problems that have been observed:

Vipps Checkout: The implementation introduced in the previous version had some bugs that have now been fixed. Vipps Checkout should now work as expected.
Punch cards and season cards: Better handling of punch cards when booking, especially in cases where several bookings happen at the same time or where the network is unstable.
Payment flow: Improved handling of interrupted payments and cases where the payment takes a long time to complete.

Other improvements

Upgraded to React 19, which gives better performance and stability
Improved email sending with more robust error handling
Better handling of coupon codes when booking
Various bug fixes for events and sign-ups