Building halal, Riba-free banking is a product problem before it's a compliance one. This is how Nuqsaf models accounts, settlements, and yield to make ethics auditable, and why we treat Shariah compliance as engineering, not marketing.
There are roughly two billion Muslims globally, a significant portion of whom either avoid conventional banking or use it grudgingly because interest-bearing instruments conflict with their beliefs. Nuqsaf exists to give that user a banking product that doesn't require compromise.
#The thesis: ethics as code
Most fintech treats compliance as a checklist applied after the product is built. We invert that. The product is the compliance, every account, every flow, every settlement is shaped by the constraint that Riba (interest) is not allowed and that contracts must reflect actual underlying economic activity.
This is closer to how protocols are designed than how apps are designed. The rules live in the schema, not in the marketing page.
#The account model
A Nuqsaf account is modeled as a Wakalah (agency) or Mudarabah (profit-sharing partnership) depending on intent. We do not model accounts as deposits earning fixed interest. The account record carries an explicit contract type, a profit-distribution policy, and a settlement frequency.
- Wakalah accounts, Nuqsaf acts as agent; fees are explicit and known
- Mudarabah accounts, profit sharing on a declared ratio (rabbul-mal / mudarib)
- Qard accounts, interest-free safekeeping for users who want zero risk and zero return
- All balances are recorded against an explicit contract row, never a generic 'deposit' type
#Yield without interest
Yield comes from real underlying activity, primarily Shariah-screened equities, Sukuk (Islamic bonds), and partnerships with halal-screened businesses. The technical challenge is making the link between a customer's yield and the underlying activity provable and traceable, so that any auditor (internal, external, or Shariah board) can follow the chain.
#Making the audit trail provable
Every transaction emits a typed event with a contract reference, an underlying activity hash, and a Shariah-board approval ID. The event log is append-only. Reconstructing why a user earned what they earned is a query, not a forensics project.
Halal isn't a badge we earn at launch. It's an invariant we maintain every commit. The schema enforces it before any human review does.
#Why this matters for the diaspora
The Muslim diaspora in the US, UK, Canada, and Europe largely uses conventional banking because nothing better exists at scale. Existing Islamic banks are regional, paper-heavy, and often have worse user experience than the conventional alternative. The opportunity is to build something that is both halal and feels like the best modern fintech. That's the job.
If you want to read the broader Nexobe philosophy on building ethical products, the operating model post goes deeper. If you want to follow Nuqsaf specifically, the product site has waitlist details.