The operation
Recurring giving had no single operational record.
Enrollment, contribution history, UPI references, reminders, and gratitude material can drift across spreadsheets and WhatsApp conversations. Hibah gives both donors and teams one understandable path.
The useful path
From donor intent to a verified ledger entry.
Personal access without another account
Each donor receives a private passwordless link with their contribution history and payment actions.
Payments remain direct
The donor uses the organization’s UPI details. Hibah does not act as the payment gateway.
Reference numbers become reviewable state
Teams verify submitted UPI transaction references and keep a chronological operational trail.
Reminder and gratitude stay connected
Pending contributions can open pre-filled WhatsApp reminders, while verified contributions can produce branded gratitude material.
Engineering concerns
The backend has to preserve trust without entering the money flow.
Model payment evidence, not bank credentials.
Public product behavior is centered on submitted UPI references and organization-side verification. Hibah states that it does not record bank credentials or UPI PINs.
Keep each organization’s operation separate.
Organizations receive isolated workspaces with roles for owners, administrators, and operators. The product language makes tenant separation part of the trust model.
Implementation note: database design, service boundaries, and deployment architecture are not described here because those details have not yet been confirmed for publication.
Inspect
The product is live in beta.
The public site documents the donor portal, UPI verification workflow, team roles, reminder path, branded output, and organization-level customization.