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
- A subscriber number with a check digit (8 digits, Luhn): a typo is rejected at the cash desk instead of paying for another flat.
- Signed requests both ways, following the ePay billing protocol: ePay asks what is owed, then reports what was paid.
- Exactly once: a repeated or concurrent notification for the same payment is recognised and ignored, and the payment is recorded once.
- Into the books immediately: a receipt numbered per year, the oldest debt covered first, and anything extra kept as an advance.
- Safe to try: a built-in simulator plays ePay's role, and test payments are labelled TEST everywhere and cancelled from the real books.
- Payments are never deleted; a wrong one is cancelled with a reason.


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
- Published: 2026-11-03
- Project: domsavet.eu — Condominium Management