Riba in the Qur’an and the Contemporary Banking System
Volume Three: Banking, Sovereign Debt, and the Structural Audit of Financial Products
I. The Global Knowledge Manifesto
Knowledge is a universal right. The author firmly believes that wisdom should not be locked behind paywalls or language barriers.
Global Access Policy. All books in this library are available for free in multiple digital formats (PDF, HTML, DOCX, TXT).
The Digital Library. As of early 2026, the collection hosts 236 volumes (118 in Arabic and 118 in English), fully optimized for AI-assisted research and digital archiving.
Official Platforms. Main Website: nasserhabitat.github.io/nasser-books/
GitHub: nasserhabitat/nasser-books
This manifesto is reproduced here as supplied by the author for this condensed edition.
II. Translator’s Note: The Bridge of Meaning
This English edition is a condensed conceptual adaptation. It is not a word-for-word translation, but rather an “extraction of essence.” It presents the core philosophical framework in accessible English, omitting the exhaustive linguistic debates and classical references found in the original Arabic text.
For the academic researcher, the original Arabic version remains the primary source for comprehensive linguistic analysis, detailed exegesis (tafsir), and the complete bibliography.
This adaptation also preserves the methodological status of the Arabic edition. A claim marked OPEN remains open; a CANDIDATE remains a candidate; a RESISTED or STRONGLY RESISTED claim is not revived through simplification; and a CLOSED result remains closed only within its declared scope. The aim is clarity without scientific inflation.
Key Qur’anic terms are sometimes retained in transliteration—such as nafs, tawaffī, barzakh, and baʿth—when a single English equivalent would prematurely narrow the field under study.
Scope of this volume
Volume Three covers Chapters 66–86: a functional account of banking, case-level comparisons of conventional and Islamic banking, a macro-level sovereign-debt application, and the first eleven product audits. It begins the product laboratory that continues in Volume Four. The summaries below condense the argument and its method; they do not reproduce the original’s complete evidence, tables, claim cards, or references.
Methodological boundary
The Qur’anic corpus remains the source for investigating the meaning of riba. Contemporary bank documents and financial records describe applications; they do not define the Qur’anic term. This volume applies the audit frame developed earlier to banks, public debt, and financial products, while preserving the distinction between a textual result and an application-level observation.
The principal unit of analysis is a specific transaction or linked sequence of transactions. An institution, a product family, a contract label, a macroeconomic outcome, or an accounting category cannot replace case-level evidence. The audit asks what was transferred, who owned it, what claim arose, on what ground, when it arose, and how rights and risks were allocated. Missing evidence remains missing; it is not supplied by a label or presumed from an institution’s identity.
The final definition of riba remains NOT SEALED, and classification readiness remains OPEN / NOT PASSED. E*-R2 remains an open candidate. RIBA-QTAM v0.1 is a structural audit model, not an automatic classifier. These limits govern every chapter that follows.
Part VIII — Conventional and Islamic banks as audit laboratories (Chapters 66–75)
Chapter 66 — What is a bank? Decompose functions before names
The chapter treats a bank as a collection of functions rather than as a single transaction or a self-explanatory category. Deposit-taking, credit provision, intermediation, maturity transformation, liquidity provision, payments, credit assessment, and risk management may coexist in one institution, but each function can produce different claims and structures.
The functional map is descriptive. “Intermediation,” “liquidity,” or “banking function” is not presented as a Qur’anic ground of entitlement. A bank balance sheet can help map claims and obligations, but it is an accounting description, not a Qur’anic model. The chapter therefore moves from institution to product and then to the individual case, using the same audit questions without turning the bank’s name into a verdict.
Chapter 67 — Deposits, credit, and financing
This chapter separates deposit-taking, credit, and financing because they describe different directions and functions. A deposit account may create an obligation owed by the bank; credit may create a claim owed by a customer; financing may involve a more complex sequence than a single loan. A customer’s “account” is not necessarily one uniform structure, and the word deposit alone does not settle whether a particular arrangement functions as storage, a debt, or another claim.
The chapter tracks money flows and claim directions, distinguishing the economic function from the type of claim. Deposit returns, credit charges, financing margins, service fees, insurance, guarantees, and commercial financing should not be collapsed into one category. The multi-claim rule remains useful: identify each claim separately and trace its ground. None of these distinctions, by itself, establishes a Qur’anic classification.
Chapter 68 — The bank loan as a structural case template
The bank loan is introduced as a template for examining an individual case, not as a product-level ruling. The audit identifies the parties, the initial provision of money, the creation of the debt, principal, interest, fees, other charges, term, rate, annual percentage rate, fixed or variable terms, and repayment schedule. It then maps when each obligation arises and who holds each claim.
The chapter does not simply equate the English banking term interest with Qur’anic riba, nor does it deny that the two may relate. Labels and numerical differences are prompts for investigation. The case template is designed to expose the grounds, timing, and boundaries of claims; without the executed contract and event-level records, a complete audit cannot be claimed.
Chapter 69 — Auditing a conventional bank from institution to case
This chapter applies the functional and case-level method to a conventional bank. It uses current institutional product information to illustrate the range of functions and products, then distinguishes that descriptive evidence from an audit of a particular executed transaction. A conventional bank is not one claim or one contract; it is a container for multiple functions, products, and cases.
The institution’s product pages support only the description of selected offerings at the time reviewed. They do not establish a Qur’anic classification of the bank or its products. A conclusion reached for one personal loan cannot be transferred to a different product, every customer, or the institution as a whole. The chapter’s governing rule is that each upward move—from case to product, then from product to institution—requires separate evidence.
Chapter 70 — Auditing an Islamic bank under the same model
The chapter applies the same audit method to an Islamic bank. Institutional descriptions such as “Sharia-compliant,” murabaha, or mudaraba are reported as the institution’s own product and contract descriptions; they are not treated as independent proof of the actual transaction structure.
Methodological equality does not require identical results. The same questions are applied to each case, while the conclusion follows the documents and events established in that case. The name “conventional” is not a verdict in advance, and the name “Islamic” is not an endorsement in advance. Product pages can support initial structural reconstruction; executed contracts, terms, ownership events, fee schedules, and default procedures are needed for a real case audit.
Chapter 71 — Does changing a contract’s name change its structure?
The chapter tests substitution of a label for structural analysis. Renaming an arrangement does not by itself change who transferred what, who owned an asset, what obligation arose, or how an additional claim was justified. At the same time, a similar label does not prove that two transactions have the same structure.
Names may help locate documents and identify the parties’ description of a product. They cannot substitute for reconstructing the sequence of events and claims. The chapter’s result is a methodological firewall: classify only after examining structure, and do not treat either a religious or conventional label as conclusive.
Chapter 72 — Similar form and different structure: a comparative matrix
This chapter compares financial arrangements across formal features and underlying structures. It asks which dimensions match and which differ—such as ownership, asset transfer, timing, claim basis, risk, and execution. Formal resemblance may coexist with a material difference, while different legal forms may share some structural elements.
The comparison matrix is an application device. A shared feature does not prove legal, economic, or Qur’anic equivalence, and a difference in form does not prove that the underlying structures differ in every relevant respect. Comparison must state the dimension, evidence, and scope of each finding.
Chapter 73 — When two transactions with the same label differ
The chapter examines same-label cases to show why a product name cannot guarantee structural identity. Two transactions described by one label may differ in asset ownership, transfer sequence, conditions, payment claims, risk allocation, or actual performance. Similar end outcomes also do not prove that the path to those outcomes was the same.
The audit therefore compares event-level records, not labels alone. A case result cannot be generalized across all products bearing the same name unless the required structural evidence supports that broader inference. The chapter does not claim that same-label products are always different; it shows that the label is insufficient evidence of sameness.
Chapter 74 — When differently named transactions have partial structural similarity
This chapter reverses the comparison. Transactions with different names may share some structural features, but partial similarity is not identity. The comparison is limited to the features documented and the purpose for which the comparison is made.
The chapter introduces an application-level structural similarity rank, S-rank, as a comparison device created for this book. It does not alter the Qur’anic claim-rank system and is not a riba classifier. Product pages support published product features only; executed contracts and event-level records are needed for a real case audit. The door’s conclusion is bounded: names neither prove nor disprove structural similarity.
Chapter 75 — Sovereign debt and macro-level extraction
Chapter 75 extends the audit from individual banking cases to public debt and national-scale claims. Its stated type is a contemporary macro-application and sovereign-case laboratory, with no semantic sealing of the definition of riba. It expressly distinguishes a sovereign state from a single transaction and a public budget from a single contract. A sovereign bond or loan label does not automatically yield a Qur’anic classification; macroeconomic collapse is presented as an application outcome, not a standalone lexical definition.
The chapter’s analytical frame follows the movement of public claims: debt issuance, rollover and capitalization, debt service, fiscal adjustment, and possible changes in ownership or control of public assets. It asks who signs for a public obligation and who ultimately bears repayment, how additional claims are treated when rolled into new principal, and whether enforcement measures alter the distribution of rights. Privatization and austerity are treated as enforcement and execution layers in the author’s model, not as direct definitions of riba.
The author presents a historical sequence and a French sovereign-debt case study, SOV-CASE-FR-01, covering 1974–2026. The chapter also advances broader causal and political interpretations about creditor power, public assets, social conflict, and identity-based diversion. In this condensed edition these are identified as the chapter’s application claims and hypotheses. The volatile economic figures and causal claims in the source require independent, date-specific verification before reuse as established facts; this adaptation does not validate them.
The chapter’s own governing statuses constrain its conclusion: debt sufficiency, time or term sufficiency, and increase sufficiency are RESISTED as standalone explanations; rollover and capitalization are analyzed as a role transformation from Δ into new principal; classification readiness remains OPEN / NOT PASSED; and the final definition remains NOT SEALED. QTAM is used to structure the macro audit, not to issue an automatic ruling. Chapter 75 adds an application layer, not a new Qur’anic corpus or a semantic closure.
Part IX — The Islamic financial product laboratory (Chapters 76–86)
Chapter 76 — Bank murabaha
The chapter opens the product laboratory with bank murabaha. The audit reconstructs the stated product and its actual sequence: the asset, its seller and buyer, the institution’s ownership or control, the sale to the customer, the deferred price, and the grounds for each part of the claim. It separates the product’s declared form from event-level evidence.
The chapter’s closing question is structural: what was acquired, by whom, when was it owned and sold, how did the deferred price arise, why was each component of the claim due, and what bounded that right? Calling an amount a margin or an arrangement murabaha does not answer those questions. The case findings apply only to the evidence and version examined and do not reopen or override claims that earlier tests resisted.
Chapter 77 — Murabaha for a purchase orderer
This chapter follows the sequence commonly described as a promise, acquisition, and sale. It asks whether the institution acquired the asset before selling it, how the customer’s promise functioned, when ownership and risk changed, and whether the documented events match the product description.
The sequence is analyzed as a transaction path, not inferred from the product name. The chapter distinguishes application findings from Qur’anic findings and does not claim that a particular promise or acquisition pattern alone settles the classification. Executed records are necessary to determine what happened in a specific case.
Chapter 78 — Ijara and the right of use
The chapter analyzes ijara through the right to use an asset. It asks who owns the asset during the lease, what use-right was granted, how rent is grounded, who bears responsibilities associated with ownership and use, and what happens if the asset is damaged or unavailable.
The audit distinguishes a use-right from ownership and from a debt claim, while recognizing that one arrangement may contain multiple connected obligations. The product’s name does not establish that the described asset, rights, and risks were actually transferred as stated. The chapter provides a structural audit, not a universal verdict on every lease.
Chapter 79 — Lease, promise, and transfer of ownership
This chapter examines ijara muntahia bi al-tamlik, focusing on the lease, any promise, and the later transfer of ownership. It tracks whether the transfer is a separate event, how the parties’ rights change over time, and which obligations relate to use, ownership, or acquisition.
The same end result—customer ownership—can arise through different event sequences. Similar outcomes do not prove that the underlying paths are identical. The case analysis therefore depends on the actual documents and ownership events, and does not treat the product label as sufficient evidence.
Chapter 80 — Musharaka: capital, ownership, profit, and loss
The chapter audits musharaka by tracing each party’s capital contribution, ownership share, management role, profit allocation, and exposure to loss. It asks whether the arrangement described as partnership is reflected in the rights and obligations that actually operate.
Profit and loss are examined in relation to capital and ownership rather than treated as labels. The chapter does not assume every profit-bearing arrangement is a partnership or that a partnership name proves shared ownership and risk. Case-level evidence sets the scope of any finding.
Chapter 81 — Diminishing musharaka and gradual transfer of ownership
This chapter follows a diminishing partnership in which ownership interests may change over time. The audit tracks the parties’ initial shares, each transfer or purchase of a share, the use of the asset, payment flows, and how responsibilities and risk change as ownership shifts.
The gradual transfer must be documented as a sequence rather than compressed into a single product description. Payment amounts may relate to different claims and therefore require separate tracing. The chapter’s structural result is bounded by the arrangement and records examined; it is not a blanket ruling on every diminishing partnership.
Chapter 82 — Mudaraba: capital, management, profit, and loss
The chapter examines the allocation of capital, management, profit, and loss in mudaraba. It asks who provides capital, who manages the activity, how a profit share is calculated, how loss is allocated, and what obligations arise if the manager’s conduct or the project’s performance is disputed.
The audit tests whether the actual rights and responsibilities correspond to the stated structure. A name does not prove how risk is borne or how a claim arose. The chapter keeps the product analysis separate from the Qur’anic semantic question.
Chapter 83 — Salam: prepaid price and deferred delivery
This chapter examines a transaction in which the price is paid in advance and delivery is deferred. It records the subject of the sale, payment timing, delivery obligation, specifications, and the consequences of failure or delay. The key structural distinction is between advance payment and later performance, with each claim and obligation traced separately.
The application analysis does not turn the product category into a Qur’anic classifier. A specific case requires documents showing what was agreed and what was performed. The chapter’s findings remain limited to the tested structure and evidence.
Chapter 84 — Istisna: manufacturing and construction obligation
The chapter audits istisna as an arrangement involving manufacturing or construction. It asks what is to be produced, who undertakes production, when and how payment occurs, how specifications and delivery are governed, and how responsibility is allocated if performance fails.
The obligation to produce or construct is distinguished from a simple transfer of an existing asset. The audit maps the sequence and claims without assuming that a label answers how the transaction operated. Any conclusion is application-specific and evidence-bound.
Chapter 85 — Tawarruq: commodity path and liquidity
The chapter follows the commodity path used in a tawarruq arrangement and asks how it relates to the customer’s liquidity outcome. It maps the commodity, successive buyers and sellers, ownership or control at each stage, the direction of payments, and whether the customer could take delivery or choose how to use the asset.
An initial cash outcome does not alone prove that every case follows the same structure. The audit separates commodity transfers from the resulting claim and records whether the steps were real, documented, and independently chosen. The chapter does not declare a universal classification from the name or the cash-flow result.
Chapter 86 — Organized tawarruq: pre-arrangement, agency, and linkage
The final chapter in this volume examines organized tawarruq, focusing on prior arrangement, agency, and links among contracts. It asks whether a platform or institution coordinates the sequence, whether the parties act through agents, whether settlements are linked or netted, and whether the customer retains a meaningful delivery option.
The chapter proposes an organizational profile—such as low, moderate, high, fully pre-arranged, or unknown—to describe the degree of linkage. This is an application-level structural profile, not a legal or Qur’anic rank and not a riba verdict. The profile records the evidence about organization; it does not independently establish the classification.
Consolidated status and limits
The volume’s results must be read at the level they concern:
• Semantic inquiry: the final definition of riba remains NOT SEALED; classification readiness remains OPEN / NOT PASSED; E*-R2 remains an OPEN candidate.
• Resisted sufficiency claims: debt alone, time or term alone, and increase alone remain RESISTED as standalone explanations in the sovereign-debt audit.
• Application method: QTAM v0.1 organizes transaction and institutional evidence; it does not automatically classify products, institutions, or states.
• Comparative devices: S-rank and the organized-tawarruq profile describe application-level structural similarities or linkages. Neither changes the Qur’anic claim-rank system.
• Evidence boundary: product pages support published product descriptions. An actual case audit requires executed contracts and event-level evidence. Contemporary terms and figures must be checked for the date and case in question.
The word RESISTED applies to the claim and test specified; it does not erase every role of debt, time, increase, or risk in a transaction. Likewise, an application profile or observed macro outcome does not become a Qur’anic definition. The volume extends the audit to new scales and products while retaining the unresolved semantic question.
Closing
Volume Three moves from the bank as a bundle of functions to individual cases, institutional comparisons, sovereign debt, and a series of product structures. Its common discipline is to test actual rights, transfers, claims, timing, ownership, and risk while keeping names and institutional descriptions in their evidentiary place. The work opens applications and comparison, not a final definition. The product audits continue in Volume Four.
Volume Three  •  1