Table of contents:

1. 🤑 Testing Bulk Payments
2. 💅 Updated filenames for downloaded receipts
3. 📝 A new Communication card solution (WIP)
4. 🧾 Offboarding receipts in admin
5. 🗿 Stable tests
6. 🐛 Distorted pdfs
7. 🪲 Bug fixes
8. 🔀 Webteam split

🤑 Testing Bulk Payments

Right now we’re approaching the final steps for the bulk payments MVP. And we’re happy to announce that we’re currently in the testing phase when it comes this feature.

💅 Updated filenames for downloaded receipts

Before this we had a pretty non-descriptive name when a user downloaded a receipt on the web. But now we instead name the file something like “ICA Fridhemsplan 2022-11-20” when it’s been downloaded.

📝 A new Communication card solution (WIP)

We’re collaborating with the data team on a joint solution where we’ll bring more flexibility for showing cards for specific segments, as well as a CMS setup where you’ll be able to create the actual content for a communication card. This project has taken its first baby steps and we’ll keep you updated on the progress.

🧾 Offboarding receipts in admin

After a request from the support team we’ve helped out by adding the possibility to offboard receipts in admin. This allows the support to offboard users themselves, instead of having to rely on guiding users through the user facing flow.

🗿 Stable tests

This sprint we have made sure that the tests in inbox is stable and you should never be blocked by a flaky test!

🐛 Distorted pdfs

We still have an issue where pdfs on the web inbox gets distorted. It can be hard to read the pdf when this happens. We are working hard on fixing this but since we are not able to reproduce this it is really hard to debug. But we will continue searching for a solution and we have a few possible options.

🪲 Bug fixes and improvements

• Update copy on accounts
• Update copy on company settings
• Should not be possible to delete shared content
• Show feedback when there is no search result for senders in settings (thanks iOS-team for reporting this)
• Making the test run faster in CI by running them in parallel

🔀 Webteam split

Almost three years ago, we decided to improve the web client here at Kivra. At the time the web client consists of a lot of legacy code. The tests had not been passed for years. Our dependencies were outdated by years and did contain a lot of known security issues. Since that time, we have rewritten everything. We have:

• Created a new login and registration portal, including company registration, registration for minors, completion and more.
• Total rewrite the settings portal used on both web and (now partly) native apps.
• Total rewrite of company settings
• Total rewrite of the web inbox
• Creating of a mock server that mimics the behavior of Kivra core and other backend services
• A BFF service
• Creating a lot of new features like receipts on the web, strip payments, tink payments, new TSM backend, just to mention a few examples
• A shard component library
• Shared web sdk

And so much more!

It has been a good and productive ride and it would only be possible with the perfect team working on all these features together.

However, when we started as a web team, there was only one product team, and it was easy to sync with the product owner. Since then, we have seven teams to sync with, and it has become hard to help out with the common goals. That’s why we now will work even closer with the product teams by also being a part of the teams. This is the first step, and we will need to iterate this, especially when we are going from something that has been working so well. If you have any questions about details, please get in touch with Oskar on slack or any web developer.