Albusyra2u

A mosque portal is usually a noticeboard: prayer times, a few announcements, a phone number. Al-Busyra needed it to also handle money.

Infak and donations were collected in cash or by manual transfer and written up afterwards. That is workable at a small scale and stops being workable the moment a campaign runs — someone transfers on a Friday night, nobody sees it until Monday, and the donor has no receipt in between.

The technical problem was not any single feature. It was the combination: reference content that has to be correct and cannot be wrong, other people's money that has to land in the right place, and traffic that arrives in bursts — prayer times, Ramadan, Friday nights.

Online infak decided the whole architecture.

Every transaction has to be verifiable after the fact. A donor closes the browser mid-payment, the bank times out, or the callback never arrives — and in each of those cases the system has to know the transaction's real state rather than assume it succeeded. That is why a payment record stores its status explicitly and is reconciled against the gateway, instead of being marked paid on the way out.

Reference content is the opposite problem. Quran and hadith text is stored as local data rather than pulled from an outside service, because an outside service going down on a night in Ramadan is not a failure anyone would accept.