Operating
JaalleID — sign-in and verification for your service
- What
- Let people sign in to your service with JaalleID, and know they have been verified.
- For
- Services that want to offer sign-in with JaalleID.
- Industry-standard sign-in
- Verified people
What working with Maysara Group looks like.
This page is for banks, ministries, telecoms operators and development finance institutions — anyone weighing an actual working relationship, not just reading about one.
What you can use from us
Four services an institution can take up.
Each one carries its real status — operating, in pilot or still in build — exactly as the portfolio page does.
In build
JaallePay — collection
- What
- In build: collection of fees and payments, with a receipt for each payment.
- For
- Institutions and businesses that collect money from the public.
- A receipt for each payment
- Android · iOS · Web
In build
Dakhli — for councils
- What
- District revenue with a verifiable receipt for every payment — and the council sees every payment.
- For
- District councils and state finance ministries.
- Verifiable receipts
- The council sees every payment
In build
Land Registry — for local government
- What
- Every parcel with clear boundaries and a recorded chain of ownership.
- For
- Local-government land offices, and banks that lend against land.
- Mapped parcels
- Chain of ownership
Controls
How we protect data.
These describe how the systems are built; they are not certificates. Each one can be shown during the technical review.
Encrypted in transit and at rest
Data is encrypted as it travels over the network and where it is stored.
Need-to-know access
Each record can be seen or changed only by the people who need to.
A receipt that can be verified
In Dakhli, every receipt can be checked as genuine.
Somali and English
People read what they are agreeing to in their own language.
What we bring
What we put on the table.
A route to customers
The group’s apps are built to reach people on the phone in their hand, in their own language. A partner’s service could meet people where they are.
Verified identity
JaalleID verifies who a person is. A partner can offer sign-in with JaalleID.
Software already built
Ten platforms are built or in build — marketplace, identity, mobility, hospitality, district revenue and the land register among them — so a pilot can start from software that exists.
Systems for merchants
Systems built for hotels, restaurants and car-rental firms to run their orders and their books, with the first operators in pilot.
What we look for
What we need from a partner.
We state the ask plainly, so the first meeting is not spent discovering it.
A licensed payments partner
A licensed institution to provide the regulated side of any payment service the group builds.
Card issuing and acceptance
Visa and Mastercard accepted across the group’s surfaces — online, in store and in the apps.
Growth capital
Capital to take the products now in pilot to a public launch.
Pilot partners in government
A district council for the first Dakhli pilot, and a land office for the land register.
The process
Four steps, on a known clock.
There is no hidden step, and nothing is signed on day one.
- 01
One hour
Introduction call
Each side states what it has and what it needs. Nothing is signed that day.
- 02
2 – 4 weeks
Technical and compliance review
Architecture, data protection and anti-money-laundering obligations are all walked through, under a non-disclosure agreement.
- 03
8 – 12 weeks
A bounded pilot
A fixed number of customers, one service, and an end date written down in advance.
- 04
Then
Commercial agreement
Once the pilot shows it works, the agreement is written and the service opens to the public.
Certifications
What we are working towards — and do not yet hold.
The group holds no ISO certificate today. These are planned; neither will be claimed anywhere until the certificate actually exists.
ISO 9001Planned · Not yet held
Quality management
How we build, test and release our services.
ISO/IEC 27001Planned · Not yet held
Information security
How data and systems are protected, managed and checked.
The limits
What we will not do.
A regulated counterparty reads this part first, which is why it is written down.
- We do not publish a partner’s name before the agreement is signed.
- We do not claim a certification or a permission we do not hold.
- We do not call a pilot a launch, or describe something as public before it is.
Our commitment
Two working days. A reference number.
We reply to institutional enquiries within two working days, with a reference number (MG-…) you can quote back to us.
Start with the first call.
Choose “Partnerships” on the form and tell us what your institution has and what you want from us. We reply within two working days, with a reference number (MG-…).
Contact the group