From Halal Wallet to Programmable Finance: MRHB's Evolving Position

From Halal Wallet to Programmable Finance: MRHB's Evolving Position

Important: This article explains MRHB’s public positioning. It is not a fatwa, personal financial advice or proof that every product, asset or transaction is Shariah-compliant, safe, available or suitable. Product scope and availability can change by country, network, provider and time.

Quick answer

Sahal Wallet was an easy way to explain what users could do with MRHB. As the company began talking about more uses for its network, it adopted a broader term, programmable finance.

That means building financial tools around rules people agree to in advance. For example, software could release a payment after a specified condition is met. At MRHB this describes a direction for work across payments, asset screening, giving and business infrastructure. Check each product’s documentation for what you can use today.

Key takeaways

  • Sahal Wallet remains a user-facing self-custodial product within the wider MRHB network.
  • Programmable finance is broader than a wallet because it concerns what financial tools can do, connect and automate—not only where assets are held.
  • Programmable payments and programmable money are not identical concepts.
  • Code can execute a rule, but it cannot decide by itself whether the rule is fair, lawful, secure or Shariah-compliant.
  • MRHB’s positioning should be tested against current product documentation, governance evidence and availability—not marketing language alone.

Why the wallet label became too narrow

A wallet has a specific job. It lets a user control access to supported digital assets and authorise transactions. The Sahal Wallet explainer covers that product, its self-custody model and the checks users should complete before moving assets.

MRHB’s wider public narrative now describes more than wallet functions. The MRHB Network ecosystem includes journeys related to screening, spending, tokenized assets, giving and business infrastructure. Those journeys may connect to a wallet, but they are not all wallet features.

The change in language is therefore a change in scope:

Wallet-first descriptionProgrammable-finance description
Focuses on a user applicationDescribes a wider network of products and infrastructure
Emphasises holding and moving supported assetsIncludes decisions, conditions, workflows and integrations
Speaks mainly to individual usersCan also address businesses, builders and partners
Explains an access pointExplains how different financial actions may connect

This does not make the wallet unimportant. It places the wallet inside a larger map.

What does programmable finance mean?

There is no single universally adopted definition of programmable finance. Related institutions often use more precise terms.

The Bank for International Settlements defines programmable payments as payments that execute automatically when preset criteria are met. The Bank of England also distinguishes user-initiated programmable payments from the more controversial idea of an authority programming how money itself may be used.

That distinction matters:

  • Programmable payment: a user or business authorises a payment to happen when a defined condition is met.
  • Smart contract: software that carries out specified actions when its coded conditions are satisfied.
  • Programmable money: a broader and contested idea in which rules may be attached to the money or unit of value itself.
  • Programmable finance: a wider descriptive phrase for financial products and infrastructure that use software rules, conditional actions and connected data.

MRHB’s use of “programmable finance” is best read in that fourth sense. It describes an intended system of connected, values-aligned financial journeys. It should not be read as a claim that MRHB restricts how a person may spend money or that every action must happen on a blockchain.

What does the positioning mean for MRHB?

It helps to separate what a person sees in the wallet, what services they can use and what infrastructure businesses might connect to.

1. A user-controlled access layer

Sahal Wallet is the user-facing access point. Its self-custodial model means the user controls the recovery phrase and authorises wallet transactions. That control also creates responsibility: MRHB may be unable to restore a lost phrase or reverse an incorrectly authorised blockchain transaction.

2. Decision and utility journeys

MRHB’s current public ecosystem describes tools for activities such as screening, spending, exploring tokenized assets and giving. Software can help connect information and actions across these journeys.

The exact tool still needs its own review. A screening result is not a profit or safety guarantee. A tokenized asset requires evidence about custody, legal rights and redemption. A spending or giving flow requires current information about fees, recipients, providers and availability.

3. Business and infrastructure journeys

MRHB also presents a business-facing proposition. A business may explore payments, digital-asset utility or values-aligned financial infrastructure through the current MRHB business information.

That is a starting point for due diligence, not proof that a particular integration is ready or appropriate. Businesses should confirm the exact service, legal entities, jurisdictions, custody model, technical responsibilities, security controls, fees, service levels and Shariah-review scope before relying on it.

What programmable finance does not mean

The new positioning should not be used to make claims that the available evidence cannot support.

It does not automatically mean:

  • every MRHB product or roadmap item is live;
  • every feature is available in every country or network;
  • code can issue a Shariah ruling;
  • all financial risk, riba, gharar or prohibited activity is removed by automation;
  • asset backing, custody or redemption is proven merely because a record is on-chain;
  • software cannot contain errors or be exploited;
  • a user will earn a return or avoid loss;
  • regulators, scholars or institutions universally accept the same structure; or
  • MRHB is the only organisation exploring programmable, Islamic or values-aligned finance.

Programmability describes capability. Good governance determines how that capability is designed, reviewed, monitored and corrected.

How Shariah-guided design fits

The beginner guide to what halal fintech means explains why a religious or ethical assessment must look beneath the interface. Purpose, contracts, money flows, assets, fees, risks and governance still matter.

Software may help apply an approved rule consistently. For example, it can display screening information or execute a condition selected by a user. But code cannot determine its own religious validity. People decide which rule to encode, what evidence supports it, how exceptions are handled and when it must be reviewed again.

For any Shariah-related claim, ask:

  1. What exact product, contract or activity was reviewed?
  2. Who performed the review?
  3. Which methodology and evidence were used?
  4. What product version and date did the review cover?
  5. How are changes, exceptions and ongoing monitoring handled?

“Designed with Shariah principles in mind” is a statement about process and intent. It is not a universal ruling for every user action.

What the change means for different readers

For existing Sahal users

The wallet’s basic self-custody responsibility does not disappear because the company uses broader language. Verify the app, protect the recovery phrase, check the network and transaction, and review each connected service separately.

For prospective users

Do not assume the whole ecosystem is required. Start with the exact task you need to complete and read the current product documentation, terms, fees and risk information before acting.

For builders and businesses

Treat programmable-finance language as an architecture and partnership proposition that requires technical and commercial validation. Ask for current documentation rather than inferring an API, integration, certification or launch status from a blog post.

For researchers and journalists

Separate MRHB’s own positioning from independently verified market facts. Attribute category, product and roadmap descriptions to MRHB, and date every time-sensitive claim.

A practical verification checklist

Before relying on a programmable-finance claim, confirm:

  • the exact product or workflow being discussed;
  • whether it is live, limited, in testing or planned;
  • the countries, networks and users it supports;
  • who controls funds and private keys;
  • the contracts, fees and third parties involved;
  • what the code actually automates;
  • the source, scope and date of any Shariah review;
  • security, privacy, operational and legal responsibilities; and
  • what happens when a transaction, integration or rule fails.

If a material answer is missing, describe the feature as unverified or planned rather than filling the gap with an assumption.

Frequently asked questions

Is MRHB still connected to Sahal Wallet?

Yes. Sahal Wallet remains a user-facing product within MRHB’s wider public ecosystem. The broader positioning does not replace the wallet; it explains that the company now describes more than one product journey.

Is programmable finance the same as DeFi?

No. DeFi usually refers to financial applications built on decentralised networks and smart contracts. Programmable finance is a broader phrase and can include conditional payments, software-enabled workflows and infrastructure that may or may not be decentralised.

Does programmable mean MRHB controls where users spend money?

That is not the meaning used in this article. The focus is on user- or business-authorised rules and connected financial workflows. Any feature that limits use of funds would require clear consent, terms, technical explanation and legal review.

Can code guarantee Shariah compliance?

No. Code can execute a defined rule. Qualified people must establish, document and review the rule, its scope and its implementation. Product changes can also require reassessment.

Are all MRHB ecosystem products available now?

Do not assume so from a positioning article. Check the current official product page and confirm availability, supported regions, terms and status for the exact service.

Why keep “halal wallet” in the article at all?

It explains the starting point of MRHB’s positioning and helps existing users understand the transition. The dedicated Sahal Wallet article remains the owner of wallet-product education.

Final takeaway

Sahal gives individuals a way into the MRHB network. Programmable finance describes the broader work of connecting services and setting rules for particular actions. For any service you plan to use, check its documentation, who controls the process and what happens if it fails.