Branch review comes first
Visitor and member requests are reviewed through the branch workflow so identity, documentation, and purpose can be checked properly.
Rules
Operational rules matter because financial trust depends on them.
The platform is being designed so important actions follow review, approval, documentation, and traceable account movement rather than informal shortcuts.
Approvals create controlled access
Accounts are not treated as open-ended shortcuts. The right accounts are created at the right stage of the approval flow.
Current accounts handle settlement
Approved disbursements and controlled payouts move through the member current account so money movement remains traceable.
Deposits follow lock and release rules
Deposit amounts can stay locked for defined periods, then become available only under the proper release conditions.
Documents remain auditable
Digital uploads and physical paper bundles are meant to be traceable, not left to informal filing or memory.
Notifications should not slow service
Slow external tasks like SMS and email are designed around queue workers so the platform stays responsive during real branch use.
FAQ
Common questions
Does someone need to be a member before requesting Qard Hasana?
No. A visitor can start the Qard Hasana process first. Membership and current-account creation can happen at the approval stage when needed.
Can one deposit account receive multiple deposits later?
Yes. A deposit account can stay open while additional deposits are posted later, each with its own lock timing.
Why is a current account important in the system?
It keeps approved payouts and settlement activity controlled, visible, and easier to audit inside the platform.