Interactive examples

Every widget on this page is built from IslamicOpenFinance™'s own scenarios: notifications, murabaha, Shariah review, takaful, zakat and the market calendar. Pick an audience. All institutions, people and amounts are fictional demonstration data; nothing here is a Shariah ruling.

Customer notifications

One event, the right route: consent, quiet hours, the market calendar and a fallback channel.

Notification centre

Eight events from the platform, each routed by its own rules; act on them as the recipient would.

For: Islamic banks and windows Fintechs and developers Treasury and operations

Eight events, as each recipient gets them

Demo data

You learn: How each event reaches the right person on the right channel, and what they can do with it. You can: Replay the feed and act on a notification as its recipient.

  1. IslamicOpenFinance™ notifications Layla H.murabaha.instalment.due

    Your instalment is due tomorrow

    SAR 527.50, 2 October 2026. Pay with one tap.

    App push fails, falls backSMSIn-appWebhook

    • Customer consent to notifications
    • Preferred channel: app push
    • Quiet hours 22:00 to 08:00 respected
    • Business day per the market calendar
    • Fallback channel: SMS after 2 minutes
  2. IslamicOpenFinance™ notifications Bawsala Electronicspayment.settled

    Funds arrived in your account

    SAR 6,000.00 for invoice INV-BW-07, the bank's asset purchase, via Bayyin Pay.

    App pushIn-appWebhookEmail

    • Consent to transaction notifications
    • Preferred channel: app push
    • No quiet hours for payments
    • Machine copy for accounting: webhook
  3. IslamicOpenFinance™ notifications Layla H.takaful.claim.paid

    Your takaful claim was paid

    AED 3,200.00 from the participants' risk fund, claim CLM-5521.

    App pushEmail

    • Customer consent to notifications
    • Preferred channel: app push
    • Quiet hours 22:00 to 08:00 respected
    • Credited on the next business day
  4. IslamicOpenFinance™ notifications Head of treasuryagent.action.requested

    The treasury agent asks for approval

    Placement of SAR 4.8 M, Qantara → Sahel. Above the SAR 2 M limit.

    App pushIn-appMessenger

    • Recipient role: head of treasury
    • Policy: human approval above SAR 2 M
    • Response window: 4 hours, then escalation
    • Channels: app push and in-app
  5. IslamicOpenFinance™ notifications Layla H.consent.expiring

    Account access consent is ending

    The budgeting app's access to your Sahel account 4 October 2026 ends.

    App pushEmailIn-app

    • Three days before expiry
    • Preferred channel: app push
    • Quiet hours 22:00 to 08:00 respected
    • Second channel: email
  6. IslamicOpenFinance™ notifications Product team, Qantarashariah.resolution.issued

    Resolution issued for a product

    The Shariah board issued SSB-QNT-2026-014 with two conditions.

    App pushSMSIn-app

    • Recorded against the product before launch
    • App push and email together
    • Launch stays locked until conditions are met
    • Business day per the market calendar
  7. IslamicOpenFinance™ notifications Company treasurybalance.low

    The operating account is low

    SAR 28 M; below the SAR 30 M minimum. Suggested: move funds from Qantara.

    App pushMessengerWebhook

    • Threshold: SAR 30 M
    • Recipient: treasury team
    • Channels: team messenger and app push
    • Business day per the market calendar
  8. IslamicOpenFinance™ notifications Investorsukuk.subscription.closing

    Sukuk subscription closes tomorrow

    Ijarah sukuk SK-2031 is 63% subscribed.

    EmailApp push

    • Consent to investment offers
    • Preferred channel: email
    • Quiet hours 22:00 to 08:00 respected
    • Business day per the capital-market calendar
How this widget is built
Demonstrates
Customer notifications
Components
  • Notification rules: consent, quiet hours, market calendar
  • Channels: app push, SMS, email, messenger, in-app, webhook
  • Fallback channel
Flow
An event is matched to its recipient and rules, then sent on the allowed channels; a failed channel falls back. Architecture diagram
Used on
  • /examples/: On the interactive examples page, with the rest of its scenario.
  • /terminal/: The terminal's notify view routes each of these events across channels on a phone mock (data.notify, exported by kit widgets build).

Murabaha

Own, then sell

MUR-84722, Layla Haddad

The sale stays locked until the bank owns the asset.

For: Islamic banks and windows Fintechs and developers

Own, then sell

Demo data

You learn: Why the sale stays locked until the bank owns the asset. You can: Step through the sale.

  1. Step 1 of 5

    Layla Haddad (demo) Financier

    Request

    Requested

  2. Step 2 of 5

    Financier Bawsala Electronics (demo)

    Asset purchase

    The bank bought the asset (invoice)

  3. Step 3 of 5

    FinancierNeeds approval

    Ownership check

    Possession recorded

    The sale stays locked until the bank owns the asset.

  4. Step 4 of 5

    Financier Layla Haddad (demo)Allowed

    Murabaha sale

    Cost and profit disclosed

    Sold at SAR 6,330.00 (cost SAR 6,000.00 + disclosed profit SAR 330.00); 12 instalments scheduled on business days.

  5. Step 5 of 5

    Layla Haddad (demo) Financier

    Instalments

    Business day per the market calendar

Expected outcome
  • Before the sale The sale stays locked until the bank owns the asset.
How this widget is built
Demonstrates
Murabaha financing
Components
  • Ownership record (invoice, possession)
  • Sale lock until ownership
  • Instalment schedule on business days
Flow
Request, asset purchase, ownership check, sale at disclosed cost plus profit, instalments. Architecture diagram
Used on
  • /examples/: On the interactive examples page, with the rest of its scenario.

Murabaha price and instalments

Demo data

You learn: How the sale price and each instalment follow from the cost and the disclosed profit. You can: Change the cost, the profit and the number of instalments.

Inputs
Results

Sale price 6,330.00 SAR

Each instalment 527.50 SAR

Expected outcome
  • Before the sale The sale stays locked until the bank owns the asset.
How this widget is built
Demonstrates
Murabaha financing
Components
  • Cost price
  • Disclosed profit
  • Instalments
Flow
Cost plus the disclosed profit gives the sale price; it is split into equal instalments. Architecture diagram
Used on
  • /examples/: On the interactive examples page, with the rest of its scenario.

Shariah review

Request to resolution

Murabaha appliances product

Resolution SSB-QNT-2026-014 recorded

For: Shariah boards and compliance Islamic banks and windows

Chain of approval, request to launch

Demo data

You learn: Which link in the chain approves a product, and what keeps the launch locked. You can: Walk the chain from request to launch gate.

Expected outcome
  • Statuses Approved, approved with conditions, returned, rejected
How this widget is built
Demonstrates
Shariah governance workflow
Components
  • Product request
  • Conflict declarations
  • Shariah Supervisory Board decision
  • Resolution registry
  • Launch gate
Flow
Request to resolution: the board decides with quorum and no conflicts; the resolution and its conditions gate the launch. Architecture diagram
Used on
  • /examples/: On the interactive examples page, with the rest of its scenario.

Takaful

Contribution to claim to surplus

A motor claim paid from the participants' risk fund

The risk fund belongs to the participants; the shareholders' fund is the operator's and stays separate.

For: Takaful operators

Contribution to claim to surplus

Demo data

You learn: A takaful claim is paid from the participants' fund, not the operator's. You can: Run the claim through its stages.

  1. Notified

    Omar Siddiqui (demo)

    AED 3,200.00

  2. Documents

    Omar Siddiqui (demo)

  3. Assessment

    Takaful operator

    Retakaful cession above AED 250,000 per claim (treaty, demo).

  4. Approved

    Takaful operator

  5. Paid from the risk fund

    Participants' risk fund

    AED 3,200.00

Expected outcome
  • Funds If the risk fund ran short, the operator would lend to it as qard, repaid from future surpluses.
  • Surplus Surplus at year end is distributed only as the fund's rules and its Shariah board allow; it is never guaranteed.
How this widget is built
Demonstrates
Takaful claims
Components
  • Participants' risk fund
  • Operator (wakalah fee)
  • Retakaful treaty
Flow
Notified, documents, assessment, approved, paid from the participants' risk fund. Architecture diagram
Used on
  • /examples/: On the interactive examples page, with the rest of its scenario.

Who holds what

Demo data

You learn: Who holds what in a takaful model. You can: Switch between the participant, the operator and the fund.

Omar Siddiqui (demo)

Participant

Does

  • Notified
  • Documents
Takaful operator

Operator wakalah fee

Does

  • Assessment
  • Approved
Participants' risk fund

Funds

Does

  • Paid from the risk fund
How this widget is built
Demonstrates
Takaful claims
Components
  • Participant
  • Operator
  • Participants' risk fund
Flow
Who files, who assesses, which fund pays. Architecture diagram
Used on
  • /examples/: On the interactive examples page, with the rest of its scenario.

Zakat

Illustrative estimate

Zakat estimate (illustrative)

Illustrative only, not a fatwa. The payer or the zakat authority decides the nisab, the method and what counts; ask your scholar.

For: Zakat and social finance

Calculator

Demo data

You learn: How an illustrative zakat estimate is built, and that the nisab and method are the payer's or the zakat body's to decide. You can: Enter holdings, debts and the nisab your zakat body publishes.

Inputs
Results

Net zakatable wealth 43,000.00 MYR

Estimated zakat 1,075.00 MYR

Expected outcome
  • Nisab Set by the payer or the zakat authority
How this widget is built
Demonstrates
Zakat (illustrative)
Components
  • Zakatable holdings
  • Nisab from the payer or the zakat body
  • Rate set by the fund
Flow
Holdings less debts due give net wealth; above the nisab, the rate applies. Architecture diagram
Used on
  • /examples/: On the interactive examples page, with the rest of its scenario.

Market calendar

Hijri (Umm al-Qura) and Gregorian dates, holidays and business days per market, from the same engine as the public API.

Upcoming market holidays

The next public holidays across three markets, as the calendar API answers them on the build date.

For: Treasury and operations Fintechs and developers Islamic banks and windows

Holidays ahead

Calendar engine

You learn: Which market holidays come next across the Gulf and Malaysia. You can: Read the dates in order; they are the engine's answers.

As of 1 October 2026

  1. National Day

    22 Jumada al-Akhirah 1448 AH

    Calendar engine

  2. National Day

    23 Jumada al-Akhirah 1448 AH

    Calendar engine

  3. Christmas Day

    16 Rajab 1448 AH

    Calendar engine

  4. New Year's Day

    23 Rajab 1448 AH

    Calendar engine

How this widget is built
Demonstrates
Market calendar
Components
  • The kit's market calendar engine
  • Holiday rules per market with sources
  • Umm al-Qura Hijri dates
Flow
The engine answers holidays per market on the build date; predicted Islamic holidays stay marked until announced. Architecture diagram
Used on
  • /examples/: On the interactive examples page, with the rest of its scenario.

Calendar API

Calendar engine

You learn: What the calendar API's holidays and markets endpoints return. You can: Pick a request and send it.

Treasury desk · Holidays of a market in a year

Request
GET /api/calendar/holidays?year=2026&market=sa
Response 200
{
  "holidays": [
    {
      "hijri": "5 Ramadan 1447 AH",
      "iso": "2026-02-22",
      "market": "sa",
      "predicted": false,
      "source": "https://saudipedia.com/en/official-holidays-in-saudi-arabia",
      "title": "Founding Day"
    },
    {
      "hijri": "1 Shawwal 1447 AH",
      "iso": "2026-03-20",
      "market": "sa",
      "predicted": true,
      "source": "https://saudipedia.com/en/official-holidays-in-saudi-arabia",
      "title": "Eid al-Fitr"
    },
    {
      "hijri": "10 Dhu al-Hijjah 1447 AH",
      "iso": "2026-05-27",
      "market": "sa",
      "predicted": true,
      "source": "https://saudipedia.com/en/official-holidays-in-saudi-arabia",
      "title": "Eid al-Adha"
    },
    {
      "hijri": "12 Rabi al-Thani 1448 AH",
      "iso": "2026-09-23",
      "market": "sa",
      "predicted": false,
      "source": "https://saudipedia.com/en/official-holidays-in-saudi-arabia",
      "title": "Saudi National Day"
    }
  ],
  "year": 2026
}
How this widget is built
Demonstrates
Calendar API
Components
  • /api/calendar (public, read-only)
  • OpenAPI 3.1 contract
Flow
Requests come from the API's OpenAPI document; each response shown is the data field of the engine's answer on the build date. Architecture diagram
Used on
  • /examples/: On the interactive examples page, with the rest of its scenario.