Building payments that can't go wrong

Paying online or at EasyPay with a subscriber number is common; doing it safely is not. A check digit stops typos, every notice is signed, repeated ones are ignored, and each payment becomes a numbered receipt.

The problem

Several services already let a building collect fees through ePay.bg and EasyPay. The trouble starts when something unusual happens: a resident types the neighbour's number, the payment system sends the same notification twice, two payments arrive at the same second, or someone tests the setup with real money.

How domsavet.eu solves it

Payment settings and the built-in simulator

What each flat owes and when it last paid

The result

Residents pay at any EasyPay desk or online, and the manager never has to untangle a double payment or a payment for the wrong flat. See it in the demo at domsavet.eu.

Technologies

Java, Spring Boot, ePay.bg, EasyPay, Payments