RFID-based transaction processor proof of concept

Scroll to the bottom for instructions on how to set up the local development environment

The app consists of two main parts

• The first and probably most important is the Terminal UI, where the transactions happen. This part needs to have access to the Web NFC api to process transactions because it's designed to work with RFID-based chips
• The second part is the admin panel, where you can see the full audit log, add, delete, edit, enable and disable resources.

When you visit the application's domain by default (on the root route) you are presented with the terminal UI after login. It has the following features:

• Only one card can be assigned to each customer
• Conflicts are handled gracefully, it is allowed to reassign a card to a different customer

You are able to create custom items too if something is not in the list. Before charging a customer, you can confirm the order.

You can provide aliases and fuzzy find items all throughout the application

Principal accounts with admin permission can access the admin panel on the /admin route

You are presented with some high level analytics and the complete audit log

You can import, export, create, enable/disable, delete and modify principals You can also manage permissions when modifying terminals or promote them to administrator

You can import, export, create, enable/disable, delete and modify accounts

You can import, export, create, enable/disable, delete and modify accounts

You can view and export the order history

You can import, export, gift and revoke vouchers

You can view and export the full transaction log

Copy the .env.example file to .env and fill it with the required data.

You need to have Docker installed on your machine. Run the following commands in the root directory of the project:

docker-compose up -d

There is a Helm chart provided in this repo to get the backend up and running in a Kubernetes cluster

• Install Kubectl
• Install Helm

• Add bitnami/postgresql repo by running helm repo add postgresql https://charts.bitnami.com/bitnami
• Run helm dependency build ./helm/kir-pay to build Helm chart dependencies
• Create a copy of helm/kir-pay/values.yaml and modify the values for your needs; you can delete the properties you don't modify to make the config cleaner
• Select the correct Kubernetes context: kubectl config use-context <context>
• Run helm upgrade --install kir-pay --values <path-to-your-values.yaml> ./helm/kir-pay to install the chart or to make modifications to an existing deployment

The frontend is a Vite.js + React single page application. We usually deploy it to Vercel, but it should work with any static site hosting service or even with nginx too. (Remember to set the VITE_BACKEND_URL env var on Vercel too when building the application.)

You need a PostgreSQL instance to run the application, preferably on your local machine. Possibly the easiest way to do this is to run it via Docker. This command starts an instance that works with the default backend configuration:

docker run -p5432:5432 -e POSTGRES_USER=kirpay -e POSTGRES_PASSWORD=password -e POSTGRES_DB=kir-pay postgres:17-alpine

Open the monorepo in Intellij and run KirPayApplication. You can seed the database by editing the run configuration of KirPayApplication and adding development to the active profiles.

You can run the application manually through the CLI, but you miss out on a lot of features that ease development. You can also seed the database with some test data by setting the active Spring profile to development Just simply open a terminal in the backend folder and run

./gradlew bootRun --args='--spring.profiles.active=development'

Copy the .env.example file to .env and fill it with the required data. You can leave the defaults for local development.

Open a terminal in the frontend folder and pull the packages

yarn

then start the frontend development server

yarn start