Web releases

The latest and greatest on the web

Demo 2022-04-21

21 April 2022

Table of contents:

  1. πŸ“œ Receipts live on the web
  2. ❌ K4B churn survey
  3. πŸ“ƒ Tink terms dialog
  4. 🐒 Using the BFF in production

πŸ“œ Receipts live on the web

Receipts are now live in production! 🐢

Small fixes after release:

  • Fixed bug on the chainlist which showed receipts from other chains other than the one you were currently on.
  • Fixed bug where the header which states the month on the receipt list was not translated.
  • Fixed bug where date was formatted wrong on receipts.
  • Fixed bug where URI’s got too long when fetching tenant details.
  • Added fallback for receipts where the total paid was missing.
  • Added fallback logo to stores and chains.
  • Added print action.

❌ K4B churn survey

We implemented a churn survey for when users cancels their K4B account. This is ofcourse to gather valuable information about why the user wants to cancel their company or sports mailbox. This will be released this week.

churn survey k4b

πŸ“ƒ Tink terms dialog

The Tink terms dialog that was shown to users paying with Tink for the first time has been removed. Instead we now show an agreement text and link to Kivra’s terms of use, which states that the user - by continuing, agrees to the terms.

agree to terms

🐒 Using the BFF in production

The BFF is right now being used in production by the web inbox and by the Android BETA (for testing out the new Home view). Our idea is that we try it out on a smaller scale, so that we have the resources to fix any issues that might arise (peppar, peppar) before letting more users on.

In order to get the BFF production ready we have done a few things such as:

  • Added more logs to Splunk which gives us enough information so that we can follow an incoming GraphQL request, see what resources it calls and if any error occurs. We’ve also added data so that we can connect Sentry errors with logs from Splunk by a request id.
  • Added uptime checks so that we (with the help of the Infra team) now have alarms set up for when the BFF is down.
  • Added alert in Splunk if we have slow response times over a period.
  • Added a Splunk dashboard to see how our request latencies look like.

We would also really like to send a huge thanks to the Infra team for helping us along the way with the things above. πŸ™