Six concrete use cases.

Existing core (Temenos / Finastra / Mambu) cannot natively accommodate AAOIFI contract structures. Bolt-on Shariah layer means audit gaps + slow product velocity.

IOF runs alongside the core as the Shariah-native API layer. The core stays. New Islamic products ship through IOF rails with AAOIFI compliance enforced at the type level.

Manual surplus calculation, paper-based claims, no real-time pool fund visibility, gharar / maysir review is reactive not proactive.

Takaful rails carry the pool ledger, claims pipeline, surplus distribution, and re-takaful cession. Every contract pre-screened against AAOIFI SS-26 §4.

Sukuk issuance traditionally needs 3-6 vendors (asset originator, SPV admin, paying agent, registrar). Coordination is brittle, audit-trail is fragmented.

Sukuk rails handle issuance prep + coupon scheduling + redemption + annual Shariah audit on a single deterministic ledger. SPV asset uniqueness enforced via KYA Rail.

Want to ship halal payments + halal BNPL inside an existing fintech app, but no licence to operate as a payment institution + no Shariah board on payroll.

Embedded Finance rail provides white-label accounts, cards, lending, payments. IOF holds the licence + Shariah board. Fintech embeds via SDK.

Spreadsheet operations, no real-time impact reporting to donors, Zakat distribution audit-trail patchy, beneficiaries can't be verified across institutions.

Microfinance rails carry Qard Hasan, group lending, Waqf endowments, Zakat distribution to the eight Quranic categories. Every disbursement carries an evidence pack.

Regulatory reporting is monthly / quarterly. Aggregation bias, late detection of stress, no cross-bank visibility into Shariah compliance posture.

IOF emits regulator-shaped evidence packs per transaction (not per quarter). Regulator portal sees aggregated tenant posture in real time. Cross-bank Shariah compliance comparable.