Shariah-compliant banking software is a product whose rules refuse interest, require an asset or a partnership, and block a prohibited posting. Buyers also search it as sharia-compliant banking software. The reader of this page is a bank, an Islamic window, or a fintech company that wants that product built. It is not a guide for a person moving a personal deposit.
Shakuro builds that product layer to order. The work is the contract states, the screens that show them, and the check that stops a forbidden posting. That build is fintech web development. The customer-facing channel, cards and transfers and statements, is a different order: digital banking software. The ledger and the account engine are a different order: a core banking platform. If the contract list already exists and your own advisor has marked what a forbidden posting looks like, get in touch before a team prices a platform.
An earlier edition of this page was recorded as a podcast episode. The recording is not this revision. This page does not publish a rate card, a build duration, a fatwa, a Shariah certificate, or a banking license.
What does this software have to enforce?
The product is the rule that decides whether a posting is allowed. A label on an existing interest module does not do that job. If the client’s advisor treats an interest posting as a failed contract, the software has to be able to refuse it before it is stored.
Three checks show up in almost every brief. Money is not booked as a rented commodity: there is no field that accrues a stipulated extra on a loan. Profit comes from a recorded asset or from a recorded partnership, and the share can move. A prohibited sector or counterparty is a block on the posting, not a sentence on the marketing page.
The catalog buyers usually hand over is the AAOIFI Shari’ah standards list. Titles on that list that change a build include SS 8 Murabahah, SS 9 Ijarah and Ijarah Muntahia Bittamleek, SS 12 Sharikah (Musharakah) and Modern Corporations, SS 13 Mudarabah, SS 19 Loan (Qard), SS 28 Banking Services in Islamic Banks, SS 29 Stipulations and Ethics of Fatwa in the Institutional Framework, SS 31 Controls on Gharar in Financial Transactions, and SS 40 Distribution of Profit in Mudarabah-Based Investment Accounts. Those are names of standards. They are not a certificate that a vendor can issue.
Adoption is not one switch. AAOIFI states that its Shari’ah standards have been made part of mandatory regulatory requirement in jurisdictions such as Bahrain, Oman, Pakistan, Sudan, and Syria, have been used as the basis of national Shari’ah guidelines in jurisdictions such as Indonesia and Malaysia, and have been used voluntarily as internal guidelines by institutions in other places, including Kuwait, Saudi Arabia, Qatar, the United Arab Emirates, and the United Kingdom. The page is AAOIFI’s note on where the standards are used. A rule set copied from one country into the next is the wrong default.
Governance is a function the client already has, or has to appoint. AAOIFI’s issued standards include GS 1 (Revised 2024) Shari’ah Governance Framework and GS 9 Shari’ah Compliance Function. The software can store the approval, the version of the rule, and the audit trail a reviewer will read. It does not replace that function, and Shakuro does not sit as the board that issues the ruling.
Dinar app by Shakuro
A screen can show an obligation the product calculates, such as a zakah figure the advisor’s rule defines. The frame above is a design credit. It is not a published case of a zakah engine, and it is not evidence of a ruling.
Which contracts change the build?
Each contract is a set of states the software must record. A fixed-rate field cannot stand in for them. The ruling for a market is the advisor’s. The titles below are the catalog, linked above, not a fatwa.
| Contract | What the software records | What a fixed-interest field cannot do |
| Murabahah (SS 8) | Cost, the disclosed markup, and that ownership passed before the second sale | Book profit before the asset is owned |
| Ijara (SS 9) | The lease term, who holds the asset, and a separate transfer if the rule includes one | Treat the lease as a loan with a rate |
| Mudarabah (SS 13) and Musharakah (SS 12) | A variable profit share, and the loss rule the advisor wrote. SS 40 is the distribution standard for mudarabah investment accounts | Store a guaranteed coupon |
| Screening | A block on a prohibited sector or counterparty, with the list version and the date | Leave a badge on the marketing page and still book the trade |
Gharar is on the same list as SS 31, Controls on Gharar in Financial Transactions. The engineering question is whether a contract with an undefined price or an undefined asset can be booked. The advisor answers it. The software should refuse the posting until that answer is stored.
If the contract requires a purchase of a real asset before the financing sale, that purchase is a state: what was bought, from whom, and when ownership passed. The broker is the client’s contract. This page does not name one.
A late amount is the same kind of decision. The advisor decides where it is posted. The software must not drop it into income because a conventional penalty module would.
Finance Management Mobile App Design by Shakuro
The screens that show those states, cost and markup on one step, ownership on the next, are fintech web design. The rules behind the screens are the web build. A concept frame is not a shipped financing book.
What is a different job from this product layer?
This page owns the product rules. Two neighboring builds are easy to mix into the same proposal, and they should stay separate.
The app a customer uses for balances, cards, transfers, and statements is digital banking software. If that channel is the brief, the work starts on that page, not here. A phone skin on top of an interest ledger does not become this product because the colors changed.
Fintech Mobile Banking App by Conceptzilla
The ledger, the chart of accounts, and the engine that posts every product are a core banking platform. Adapting a conventional ledger is that page’s question. Even when the ledger stays, this product still needs a rule that can refuse an interest posting. Renaming the rate field to “profit” does not do it.
A person who wants to move a savings account is not the buyer of this software. SS 6 is titled Conversion of a Conventional Bank to an Islamic Bank. That is an institution changing its book, not a set of steps for a household deposit. This page does not explain how to switch an account.
Mobile Banking App by Coneptzilla
Can a low-code tool hold the contract rules?
A low-code tool can sketch a form for Islamic banking. It does not, by itself, hold sharia-compliant product modeling: two sales in a murabahah, a profit share that changes, or a block on a prohibited sector.
Use it when the question is whether a clerk can see the steps. Stop using it as the product when it cannot refuse a posting the advisor marked forbidden. That refusal is a rules layer, with a stored version of the rule and a record of who approved it. A form that always saves is a prototype.
What do you write down before a price?
A price without this packet is a guess. Five lines are enough to start.
- Which contracts, and which market. One contract in one market is a first release. A second country is a second rule set.
- Who on your side approves a rule before it can go live. Name the role. A development company does not issue that approval.
- Two or three examples of a forbidden posting, written by that advisor, not by the vendor.
- Which outside systems the contract needs, such as a screening list or a commodity purchase, and who already holds that contract.
- What the first release will not do: no customer channel, no new ledger, no second market, unless that is actually the brief.
Shakuro does not invent the ruling, the certificate, or the license that a market may require. Those stay with the client and the advisors the client appoints. The build starts when the packet is specific enough to test a posting against.
What changes the estimate?
There is no rate card on this page. The estimate moves with the packet, not with a slogan about an enterprise platform. Bring the five lines above and get in touch for a figure that matches them.
| Write this down | First release | What moves the estimate |
| Contracts | One contract, one market, with the advisor’s forbidden postings | Each extra contract, and each extra market’s rule set |
| Ledger | The posting goes to a system you already run | A new ledger is the core banking platform, a separate build |
| Channel | Admin screens and the contract steps | A customer app is digital banking software, a separate build |
| Outside systems | One screening list, or one asset-purchase step, if the contract needs it | Each extra provider, and a contract you do not hold yet |
| Review trail | Who approved the rule, and which version booked the posting | A second reviewer, a second language, a report the board will read |
The calculator below is a scope sketch. It is not a quote, and it does not know your advisor’s rule set.
Where does the model usually break?
The failures are specific. They are not a mood about ethics.
- The rate field is renamed “profit” and still accrues a stipulated extra. The advisor’s examples of a forbidden posting would have caught it, if anyone tested them.
- A late amount lands in income because that is where the old penalty module posts. The destination has to be the one the advisor wrote down.
- Screening is a badge. The trade still books. A block stores the list version and the date, and it refuses the posting.
- One country’s rule set is pasted into the next. The adoption note above is why that fails: mandatory, national guideline, and voluntary internal use are not the same instruction.
- The asset purchase exists in a PDF and not as a state. If the contract requires it, the software has to record what was bought and when ownership passed.
A team that cannot show those five failures in a test case is not ready to price the product. Security controls, a banking license, and a market’s reporting duties are agreed with the client’s own specialists. They are not a certificate attached to a proposal.
What has Shakuro published in this area?
ZAD is published as mobile app UX/UI design for a Kuwaiti investment platform. The case describes a Shariah-compliant product that combines a robo-advisor and trading, and interface work so people can trade stocks and ETFs. It describes risk profiling, portfolio views, watchlists, and order screens. It does not document a deposit ledger, a financing book, a fatwa, or a banking license.
Product rules for a banking contract belong on this page, not in that case. The published work sits in fintech app development as interface design. A banking product whose postings have to follow an advisor’s rule is the web build named above.
ZAD app by Shakuro
Silent authentication for ZAD app by Shakuro
The frames are design credits from that project. The case page describes the interface. It does not describe a certified security control, and this page does not add one.
How do you choose a team?
Ask for the contract states, not for a theme. A useful answer names murabahah as two sales with ownership recorded between them, or says the team will not invent that sequence. Ask whether a posting the advisor marked forbidden can be refused, and where the approval is stored. Ask which part of the brief is this product layer, which part is digital banking software, and which part is a core banking platform.
A team that answers with a certificate, a fatwa, or a license it will obtain for you is selling a document it does not have. Shakuro will not do that. If the packet is ready, get in touch and send the contract list.
FAQ
How much does Islamic banking software development cost?
This page does not publish a price. The estimate moves with the number of contracts, the number of markets, whether the ledger already exists, and whether a customer app is in the same brief. Send the packet and ask for a figure.
How long does Islamic banking software development take?
This page does not publish a duration. A first release of one contract against an existing ledger is a different job from a new ledger plus a customer channel plus a second market. The packet is what makes a duration discussable.
What should an Islamic banking software MVP include?
One contract, one market, the states that contract requires, and a refusal of the postings the advisor marked forbidden. It does not need every product, every country, or a new ledger.
Can a conventional core banking system be adapted for Islamic banking?
The ledger question belongs on the core banking platform page. A rename of the interest field is not an adaptation. This product still needs a rule that can refuse a forbidden posting, whether the ledger is old or new.
How is Shariah compliance verified in Islamic banking software?
The client’s advisor, or the compliance function the client appoints, approves the rule. The software stores that approval and can be tested against the forbidden postings the advisor wrote. Shakuro does not issue a fatwa, a Shariah certificate, or a banking license.
How do I choose a development partner for Islamic banking software?
Ask for the contract states and for a test that refuses a forbidden posting. Discard a proposal that offers a certificate, a fatwa, or a license as the deliverable.
Is this page about switching my savings account?
No. It is for a company building the product. It does not explain how to move a personal deposit or a personal account.
What to send before you write
Send the contract, the market, the role that approves a rule, and two forbidden postings. Say whether the ledger already exists, and whether a customer app is in scope. That is enough to tell this product layer from digital banking software and from a core banking platform.
Then get in touch. The conversation is the contract list, not a request for a ruling.
Sources: AAOIFI Shari’ah standards list (titles SS 6, SS 8, SS 9, SS 12, SS 13, SS 19, SS 28, SS 29, SS 31, SS 40); where those standards are used; issued governance standards (GS 1, GS 9). Standard titles are a catalog. They are not a ruling on a client’s product.
Mobile Banking Application Design by Shakuro