Discussion Draft · September 2026

Building the digital wallet for the sacred journey.

A proposal for a Road2Haramain-branded e-money ecosystem powered by the MobilityOne / MiPAY platform. Built for pilgrims, travel partners and the wider service economy.

BNM-licensed foundation
8 partner services
~3-month app build target
01 · The Foundation

Built on the MiPAY foundation.

Road2Haramain is a white-label proposition layered on a regulated, BNM-licensed e-money platform. We do not recreate payment infrastructure from zero — we reskin and orchestrate on top of an already-operating one.

BNM-Licensed e-Money

MobilityOne operates the e-money layer with Bank Negara Malaysia licensing and the regulatory controls that come with it.

Prepaid Mastercard

Optional open-loop card programme subject to commercial scope, programme approval and card production readiness.

QR & DuitNow Payments

Merchant payment acceptance including DuitNow QR where supported by the platform and merchant environment.

Wallet Management

Balance, transaction history, account controls and user servicing inside a branded mobile experience.

Funds Movement

P2P, cash-out and remittance capabilities where enabled by the underlying platform and regulatory scope.

White-Label Reskin

Partner branding, app identity, splash screen and UI treatment under the Road2Haramain brand.

02 · The Proposition

From a pilgrim mini-app to a branded wallet ecosystem.

The current Road2Haramain already provides the pilgrim-facing service layer. The proposed model gives it a stronger branded front door — while retaining MiPAY as the regulated payment backbone.

01

Brand ownership

A dedicated Road2Haramain-branded wallet and app experience — instead of relying only on a host mini-app.

02

Integrated payments

Travel bookings, merchant payments and partner services connect to one approved payment layer.

03

Service orchestration

R2H owns the user-facing journey while specialist providers retain ownership of their services and fulfilment.

04

Scalable ecosystem

New travel, health, faith-tech, education and other partner services can be added progressively.

Proposed positioning

"Road2Haramain becomes the branded pilgrim wallet and service ecosystem. MobilityOne / MiPAY remains the payment infrastructure and regulatory layer."

03 · Product Description

What the white-label solution delivers.

A branded digital wallet combining payment capability with the existing Road2Haramain pilgrimage service journey. Six core capabilities, each owned and operated by the right party.

01

R2H-Branded Mobile App

Logo, visual identity, app listing and user-facing experience under the Road2Haramain brand.

02

MiPAY Wallet Account

eKYC, wallet creation, balance, transaction history and payment services powered by MiPAY.

03

Pilgrimage Service Layer

Umrah and Hajj package discovery, agency selection, booking, status and approved partner-service journeys.

04

Merchant Payments

QR and merchant payment acceptance where supported by the MiPAY ecosystem and scheme scope.

05

Optional Prepaid Mastercard

Road2Haramain-branded card programme subject to approvals, commercial model and programme setup.

06

Partner Service Integration

Deep link, referral, API or SDK integration based on each partner's confirmed interface.

04 · Operational Model

The end-to-end operating process.

R2H owns the pilgrim-facing journey. MiPAY owns the regulated wallet and payment layer. Each partner keeps ownership of its specialist service and operational responsibilities.

STAGE 01

Onboarding

User registers, completes required eKYC and activates the Road2Haramain wallet through the MiPAY platform.

STAGE 02

Discover & book

User browses Hajj and Umrah packages or partner services inside the R2H experience.

STAGE 03

Pay

Payment is initiated through the MiPAY wallet or other approved payment rails.

STAGE 04

Process & settle

MobilityOne processes the transaction and settlement follows the agreed merchant and partner model.

STAGE 05

Track & support

R2H surfaces booking and service status and routes customer support appropriately.

STAGE 06

Monitor & report

Transaction, service and operational reporting is available to authorised stakeholders.

05 · Architecture

A clear layered architecture.

Management-level view of the white-label architecture. Exact interfaces should be validated with MobilityOne / MiPAY and each service provider during scoping.

Layer 1 · Pilgrim-facing
Road2Haramain App
Branded user experience · Pilgrim identity + service access
Layer 2 · Regulated
MiPAY e-Money Layer
Wallet · QR · payment · Card / transfer where enabled
Layer 3 · Orchestration
R2H Service Hub
Travel booking · status · Partner-service orchestration
Layer 4 · Specialists
Service Providers
Travel agencies · merchants · M² · Moddakir · future partners
06 · Target Market

Who the ecosystem is designed to serve.

The solution connects pilgrims, travel operators and service merchants through one branded digital journey. Primary initial focus: Malaysian Hajj and Umrah users and participating travel / service partners.

Hajj & Umrah Pilgrims

Individuals seeking travel booking, payment, journey support and additional digital services — the core initial user base.

Travel Agencies / Operators

Licensed travel partners supplying packages, inventory, booking fulfilment and pilgrim support.

Pilgrim-Service Merchants

Transport, accommodation, retail, health, education and other approved service providers.

Strategic Ecosystem Partners

Technology, faith-tech, education and other partners integrated through the R2H ecosystem.

07 · Roles & Governance

Clear ownership across platform, experience and delivery.

A white-label programme works only when operational and regulatory responsibility is explicit. Each party owns a defined scope and an agreed set of obligations.

Infrastructure

MobilityOne / MiPAY

Payment infrastructure & platform operations

  • ●Operate the e-money and payment infrastructure
  • ●Wallet and optional card programme operations
  • ●Transaction processing and settlement
  • ●Security, AML/CFT, fraud and platform controls
  • ●Regulatory and audit support within agreed scope
  • ●Technical platform support
Brand & Journey

Road2Haramain / M1 Merchant

Brand, user journey & partner orchestration

  • ●Own the Road2Haramain brand and user journey
  • ●Define product and service catalogue
  • ●Manage travel and service-partner relationships
  • ●Manage customer-facing content and business rules
  • ●Coordinate booking and service support
  • ●Own commercial proposition and programme outcomes
Delivery

Travel & Service Partners

Specialist delivery and fulfilment

  • ●Provide products, services and fulfilment
  • ●Maintain inventory, pricing and service information
  • ●Meet onboarding and compliance requirements
  • ●Provide specialist support and warranty where relevant
  • ●Share agreed status and reporting data
  • ●Follow settlement and service-level arrangements
08 · Governance & Compliance

Controls required before launch.

The white-label proposition places significant emphasis on regulatory readiness, security and formal sign-off. Exact requirements depend on the final model and approvals.

eKYC & Identity

Customer onboarding and identity verification aligned with the approved wallet model.

AML/CFT & Fraud

Transaction monitoring, sanctions and risk controls, and fraud handling under the platform framework.

Data & Cybersecurity

Secure hosting, access controls, privacy handling, logging and security testing / VAPT where required.

Regulatory Submission

BNM, scheme and programme submissions and approvals where applicable to the selected model.

UAT & Acceptance

Defined UAT scope, issue handling and formal sign-off before production deployment.

Operational Support

Clear support ownership, incident escalation, settlement and reporting responsibilities.

09 · Implementation

Proposed implementation path.

From scope confirmation to production go-live, in six phases. Indicative timeline: ~3 months for the mobile app implementation, with an additional 1–2 months for prepaid Mastercard implementation where included.

Scope & requirements

Confirm white-label model, service scope, app identity and ownership.

UI/UX & architecture

Approve reskin, R2H journey and technical integration design.

Build & integration

Configure and develop the app, wallet journeys and service connections.

UAT sign-off

Obtain MiPAY UAT access, test end-to-end flows and close critical issues.

Regulatory readiness

Complete required BNM, VAPT and programme approvals where applicable.

Production go-live

Deploy, monitor and enter warranty and post-go-live support.

Timeline note: Indicative only and remains subject to scope, dependencies and regulatory approval. Prepaid Mastercard scope is additional and conditional on programme readiness.
Proposal under discussion

Ready to scope your integration?

Talk to the MobilityOne team about partnering on the Road2Haramain white-label e-money proposition, or explore the platform further on your own.