Merit · Product · Internal Explainer
One verified identity, connected to everything of value a person holds, and an agent that uses it on their behalf. That is Merit ID. The B2C Super App is one of eight surfaces standing on it, and it is not the point of it. Merit ID is an identity, not a wallet: it carries programmes rather than holding funds, which keeps it outside payment regulation. Every Merit commercial opportunity, including enterprise white-labels hidden behind a client's own brand, runs on this one identity layer. Eight sections carry the argument: the problem, the vision, the moment a consumer feels it, the architecture, the ecosystem, what exists today, the twelve-month roadmap and the network economics. Pricing, the on-chain concept, the regulatory position, the glossary and the detailed flows sit in the appendix, because each of them still needs validation or sign-off.
“Anytime we have a new project, we push everything to Merit ID. At the end of the day, link everything to the Merit ID.”
Julie Barbier, Chief Product OfficerFragmented identity, fragmented value, and a consumer who cannot use either.
Identity does not travel, so value cannot travel either. Both problems have the same root.
Julie shops at Carrefour. She works at Merit and holds Peoppl points. She banks with SAIB and with Al Rajhi. She is Al Fursan Gold and an Optimoji member. She asked one question about all of it: what does that actually give me? She could not answer it, and she runs product for a loyalty company.
One person, six programs, no answer
Each program knows a different part of her. None knows the whole person.
Loyalty points expiring unused in KSA alone. The value is real, it belongs to the consumer, and it is unreachable.
The average Gulf consumer. Every unused card is a program that paid to acquire someone who never came back.
Of e-commerce checkout conversion, lost to identity and login friction alone, before anyone considers price.
Merit has the same problem from the other side.
Ten clients, ten stacks. Or ten clients, one layer.
Six logins to her. A build cost that repeats with every client, to Merit.
Her diagnosis is sharper than the numbers. People do not use loyalty because they do not understand how it works. Julie can fly a family to Bali on points. That takes industry knowledge. A consumer should not need it.
One Merit ID connects a person to everything they hold and everything they are entitled to, and an agent uses it on their behalf.
Identity does not travel, so value cannot travel. Merit ID makes identity travel.
Merit ID is the universal identity and value layer of the Merit ecosystem. One bank-grade, KYC-verified identity, connected to everything of value a person holds: points, memberships, status, benefits, discounts, credentials, payment instruments, tickets and access, and corporate entitlements. Loyalty is the first use case, not the scope. The consumer verifies once. The partner never re-verifies. Every Merit product plugs into the same spine instead of rebuilding it.
It answers eight questions about a person. Only the first is an authentication question.
That last one already has clients. Kantar and Nielsen are survey companies, and both run Merit storefronts today. Merit also runs bulk redemption for Nielsen. The mechanic is direct: a member answers a survey with their Merit ID and unlocks value for it. No panel to join, and no middleman holding the profile. Consent makes data a trade the member is paid for, priced per person instead of sold in bulk. Flow 1 of the app demo shows the screens: survey, consent, 250 points credited instantly.
“Imagine you could directly answer a survey using your Merit ID and unlock additional value. Your data becomes your new wealth, and you can monetise data at individual level.”
Julie Barbier · Merit ID threadEverything links to Merit ID. Nothing gets its own stack.
A product directive, not a preference. A new project attaches to the layer instead of getting a parallel build.
Wallets and aggregators already do that. The differentiated claim is the opposite. You should not have to understand loyalty at all. Merit knows what value you can reach, and uses it for you.
Identity, not a wallet.
Merit ID carries programmes on a person's behalf. It does not hold funds, and it is not a payment instrument. That distinction keeps it outside payment regulation, and it is the reason Merit ID can sit underneath a bank's app, an airline's app or a marketplace without becoming a licensed money product itself.
Every Merit commercial opportunity runs on Merit ID, including enterprise white-labels, where the layer sits behind a client's own brand and a consumer never sees the Merit name. Merit defines one solution per client rather than offering a menu of options, so the client gets a fitted answer instead of a set of choices to configure.
Enterprise employee rewards is a use case, not a different product.
A large employer can run an employee rewards programme on Merit ID. Employees carry a Merit ID employee badge, and the employer runs its own onboarding dashboard first, with the Merit ID layer underneath it. Some employers, the Public Investment Fund among them as an example rather than a commitment, expect on-premises hosting for this kind of deployment.
This is the same identity and value layer used everywhere else in this document, wearing a different front end for a different buyer.
Licensing: the seller is merchant of record.
In the Super App's third-party seller model, the seller is the merchant of record for the sale, and Merit acts as agent. Merit ID is the identity the buyer and seller both trust, not the party taking title to the goods.
A SAR 400 basket, and Merit finds SAR 91 of value the consumer had forgotten.
Everything else on this page is infrastructure. This is the part a consumer feels, and it is the part that is worth building the infrastructure for. A basket comes to SAR 400. Merit finds points across programs, a coupon she forgot, an entitlement she never claimed and a membership discount, and applies all four in one pass.
Only one identity can do this. To the consumer, those programs are separate companies.
This is also the part investors ask about. It puts Merit ID inside the agentic direction of the market. The agent has to know who you are and what you can reach, and Merit ID is that context.
What the consumer actually sees
One tap at checkout. The agent has already found the value, and the consumer does not have to know where any of it came from.
A wallet holds value. A marketplace takes payment. Nothing decides.
Julie's framing. The gap between the two halves is where the agent lives, and nobody owns it today.
The same person, the same points, two different apps
A balance screen hands the work back. Coaching does the work and asks for one decision.
No build has been sized for this yet. The three-month figure discussed in the session came from external contacts describing what they want to see, which is a signal about timing pressure.
Merit ID as the common spine underneath every Merit product, and what that spine actually holds.
Everything links to Merit ID. Nothing gets its own stack.
Nusuk, NCNP, SAIB, a client marketplace: each one attaches to the identity layer. The reason is not tidiness. It is that the tenth client is then cheaper than the first.
SAIB asked for their own marketplace. The answer is a branded link into the same one. Duplicating it buys a migration later, and an internal fight with it.
Identity screening: two populations, two data owners.
Merit ID integrates LSEG World-Check, the Verify product, for sanctions and PEP screening. Two populations sit on the layer: Merit ID members, where Merit owns the data, and partner-programme members, where the partner owns the data. Merit already screens sellers for KYB, PEP and sanctions through Themis, so this extends a control that already exists rather than introducing a new one.
Open design question: whether Merit ID collects the attributes a screening check needs, such as name, date of birth and government ID number, is not yet decided. It sits with whoever owns the population's data, and it is a design choice, not a settled position.
Five layers, and only one of them holds value
Merit ID is not a ledger of other people's points. It is identity, consent and orchestration over value that stays where it is.
The whole thing in one picture
Issuers and identity sources on the left, verified once. On the right, eight surfaces that consume the layer and none that own it. The B2C Super App is one box among eight.
What it buys, one stakeholder at a time
Seven parties, and every one of them is on the network for a different reason. The strip moves on its own. Click a dot to jump straight to one.
Issuers, identity sources, merchants and Merit products, and the one primitive that connects them.
Four sides, one layer between them
Each side hands the network something it already owns. Each side gets back something it cannot build on its own. Merit ID is what stands in the middle.
Issuer connection status
The technical connection, not the commercial relationship. A pill marks a build state, not a deal stage.
| Issuer | Type | Connection | Role |
|---|---|---|---|
| Peoppl | Merit's own points | LIVE IN APP | The only issuer a user can actually see today. |
| BSF | Bank | CONNECTED | Technical connection established, not yet consumer-visible. |
| Al Rajhi | Bank | CONNECTED | Technical connection established, not yet consumer-visible. |
| ANB | Bank | CONNECTED | Technical connection established, not yet consumer-visible. |
| STC Qitaf | Telco | SIGNED HANDOFF | The connection pattern the rest of the network reuses. |
| SAIB | Bank | IN PROGRESS | A bank-level connection, and a candidate for the deeper embedded-finance optionality in appendix A3. |
| Airlines | Airline | NOT STARTED | The hardest counterparty type to open with, so integration starts later by design. |
No merchant refuses Jahez. As its checkout fills up with loyalty options, Merit ID becomes the obvious way to simplify it, and the rest of the network follows the traffic.
Approaching an issuer as a Merit B2C product invites a negotiation. Approaching under a national initiative such as NCNP or Nusuk does not. It is very hard for a merchant to refuse a public-sector programme.
Accept a weak commercial deal to get connected. Per-deal margin is recoverable later; a competitor getting there first is not.
The starting position, stated plainly, because a vision that overstates the present tense stops being useful the first time somebody checks.
The legacy platform already connects dozens of programs. That estate is real revenue and real relationships. What is new is one identity layer under all of them. Only Peoppl is visible on that new layer today. The table shows the new layer only.
| Capability | State | Detail |
|---|---|---|
| Identity system of record | LIVE | Off-chain. Auth, KYC tiers, sessions and security all built. |
| Merit ID app | LIVE, UNTESTED | In the KSA and UAE App Stores. Deliberately not promoted, still in final testing. |
| Issuer connection journey | BUILT | Permission, OTP, token, live balance reads. Working end to end. |
| Connected issuers visible in app | ONE | Peoppl only. The multi-issuer experience is not yet visible to any user. |
| Bulk identity creation | BUILT | Proven on the Gift Global migration, 1,341 users. |
| In-app marketplace | INCOMPLETE | Cannot yet replace Gift Global, which is what gates decommissioning it. |
| mTrust Score | IN BUILD | General availability not yet scheduled. |
| Membership feature | BRD DRAFT | v0.1, awaiting decisions on tiers, pricing and first program. |
| AI agent at checkout | CONCEPT | No build sized yet. The urgency is an external expectation, not an internal commitment. |
| On-chain credential | CONCEPT | A concept, with nothing built and nothing committed. The closed-loop position is a design intent awaiting external counsel, per jurisdiction. |
Gift Global is a known security exposure and stays live until the Merit ID marketplace can replace it. And the app is region-locked to the KSA and UAE stores. Colleagues elsewhere cannot install it. The CPO in France is one of them. Neither is fatal. Both are embarrassing to discover in front of a partner.
Now, connect, orchestrate, intelligence. Each stage is useful on its own, and each one is visible to a consumer.
Twelve months, and what a consumer can see at each step
Every stage ships something visible. A stage that a consumer cannot see is a stage that cannot be checked.
Merit builds things and then stops enhancing them. That habit turns a platform into a collection of finished projects. The answer is a cadence, not a date. Ship something new every month.
Every new connection makes every existing one worth more. That is the reason to build it, and the reason the window matters.
Six layers to earn on, and one of them compounds. Identity and API fees, partner integration, transaction and orchestration economics, Point Exchange economics, mTrust, premium capabilities.
Willingness to pay is not validated. The indicative price bands sit in appendix A1 and are not a commitment.
Adding the eighth issuer is worth more than adding the second
Seats grow one at a time. Connections grow with the square of the network. That gap is the moat.
Sanabil is working on something in the same space. Merit's advantage is Jahez, and that advantage is fresh rather than permanent.
It has to be discussed for investment reasons, which means the idea is in the open while it is unbuilt. An idea described but not shipped is one somebody else can ship.
Contacts across Visa, Google Pay and Apple Pay in the US described this as the next thing they want to see. That is who is applying the timing pressure.
Behaves like pure SaaS. Cost of goods is auth infrastructure, scoring compute and observability.
Lower, because onboarding services and data mapping are bundled in. Productising the onboarding lifts it.
High margin, and it grows with network density rather than with seat count. This is the only line that gets structurally better the longer the network runs.
Per-seat revenue scales with customers. Settlement spread scales with the connections between them. That is a much steeper curve.
Everything from here waits on validation or sign-off. Do not quote any of it as a Merit position.
A1 pricing, pending commercial sign-off. A2 the on-chain concept, pending counsel. A3 embedded finance, as optionality. A4 roles and definitions. A5 glossary. A6 the issuer connection flow.
Six monetisation layers, and an indicative band that has not been tested with a single issuer.
Merit ID sells to partners on verification cost avoided and conversion recovered. There are six monetisation layers to work with: identity and API fees, partner integration, transaction and orchestration economics, Point Exchange economics, mTrust, and premium capabilities. The pricing principle is deliberate. Set the per-identity fee below what the partner already spends re-verifying and re-acquiring that user. Merit ID then reads as a saving, not a new line item.
Willingness to pay has not been tested with a single issuer. Anchoring a price before that test sets the ceiling for everyone who reads it, so these numbers stay internal, stay indicative, and need commercial sign-off before any external use. Validate with two or three issuers first, then set the bands.
Indicative price per active Merit ID, per month
Volume bands. One measure on one scale, so one hue darkening with volume.
Subject to technical, regulatory and legal validation. Nothing here is built and nothing is committed.
Three phases
Phase 3 is the one that changes the character of the thing, and it is a phase Merit can schedule on its own engineering timeline.
The design intent is that Merit operates as a Technology Service Provider, not a Virtual Asset Service Provider. That is a design intent, not a legal conclusion. External counsel has not signed off these propositions in each relevant jurisdiction. Until they do, present none of this as settled. $MERIT would be a closed-loop utility token. It would not be withdrawable to an external wallet, would not trade on a public exchange, and would be spendable only inside the Merit merchant network. The interface would expose no fiat off-ramp, and a user who wants fiat would be handed to a licensed VASP partner. Nothing of this is built. The precedent people cite is airline miles and Starbucks Stars: real value, not money transmission, because it is restricted to a defined ecosystem. A precedent is not an opinion from counsel, and blockchain only gets built here if it demonstrably improves interoperability, verification or settlement.
The token would have to be transfer-restricted at token level. A freely transferable token can reach a public exchange, which forms a de-facto off-ramp Merit does not control. Closed-loop has to be engineered in, not assumed. Mainnet is public, so the Merit ID to wallet mapping stays off-chain and encrypted.
Interesting future use cases. None of them is an established Merit ID capability today.
Optionality, not a capability. If Merit ID can see what a member holds, a lender could in principle advance against it. Untested, unbuilt and regulated. It is one reason SAIB wants equity, and the aggregation is what gets built first.
Also optionality. Points are a liability on an issuer's balance sheet, and liquidity against them would turn loyalty into a financial product. Merit does not have to become a financial institution to have an enormous opportunity.
The 1 to 100 trust score exists for Merit's own risk decisions, but it sells standalone to issuers and financial institutions as a risk-signal API. General availability is not yet scheduled.
The premium membership shaped for Riyadah was originally going to be a standalone microsite. Julie's direction was that it should not be. Membership is a layer of status, entitlements and a digital credential sitting on top of an identity, and Merit ID already owns the identity. So Membership became a native Merit ID feature: tiers, a digital card in Apple and Google Wallet, and a benefits engine that any program can configure. Riyadah is the first tenant, not the only one. It is also what makes the tennis federation discount in section 03 mechanically possible.
The government identity source separates this from an auth product. The issuer separates it from a loyalty engine.
Merit ID separates two things. A Member is a retail consumer who holds a Merit ID. A User is a merchant or corporate admin on normal corporate auth. Only Members have a Merit ID. In a spec the two can look interchangeable. They are not.
Terms that appear across the Merit ID specs and mean something specific.
@brian, mapped to a verified phone, email and KYC
status. The identity itself, not the app that surfaces it.The flow behind section 05. It is already built and working, and it is the primitive the whole network is made of.
Permission, then token, then live balance
Four steps. After the first three, every later transaction is frictionless, because Merit holds a token rather than asking again.
Merit already holds contracts with many of these partners from the B2B side of the business. In several cases the remaining work is asking an existing partner to connect, not selling a stranger on the idea. Airlines were deliberately left until later as the hardest counterparties to start with.