QR Halal Ecosystem · A trust fabric for halal trade

Scan any product.
See its halal proof in seconds.

An OIC-aligned trust fabric that complements national halal authorities — SiHalal · JAKIM · ESMA · SFDA · MUIS · AFIC. Two PNBP services are live today (Halal Passport per-SKU, Halal Shipment Certificate per-batch); more PNBP and B2B modules are on the roadmap. Every credential resolves through a single QR.

301
Passports anchored
5
Shipment certificates
10
Origin countries
4
Destination markets
Why this matters now

Two structural problems Indonesia must solve before October 2026

500,000+ imported SKUs need BPJPH registration

PP 42/2024 mandates that every halal-labelled import SKU be registered with BPJPH by October 2026. The paper process cannot carry that load — it would take BPJPH staff decades to clear manually.

USD 225–300M per year leaks to foreign halal cert bodies

Indonesian exporters pay SGS, Intertek, and the commercial arms of foreign LHLNs for per-shipment certificates BPJPH should be issuing. HaraShield closes that gap at Rp 200K per batch, < 4-hour turnaround.

Two principal interfaces

The data side and the money side, one trust fabric

Halal Passport carries the credential data and resolves the QR. Halal Payment Gateway carries the money — collection, split, NTPN, audit. Every cert is paid through HPG; every Rupiah HPG collects produces a verifiable cert. The two surfaces are inseparable by design.

PNBP-01 · PNBP-02
Halal Passport · data layer

Per-SKU credential bound to a national halal cert, with 4-role attestations (certification · inspection · lab · trade), Polygon anchor, and a QR that resolves in any country.

Platform · payment substrate
Halal Payment Gateway · money layer

Orchestration + audit + reconciliation API on top of BI-licensed PSPs (DANA MPN G3 today). Splits Kas Negara PNBP from HARA platform fees in T+1. Daily Merkle root anchored on Polygon.

Target architecture

Four service clusters on one HARA Trust OS

Clients and PJAH reach the BPJPH core only through API/SDK; the core reaches the OS the same way. Identity is two-plane — Numira = who acts (subject DIDs), Atlas = what is certified (object DIDs), Registry = the ledger.

Tier 3 · Clients
consume the core via API/SDK
Requester Console — exporter · importer · LPH · LHLNHalal Value Services — lab · logisticsPublic PWA Verifier
API / SDK
Tier 2 · PJAH services
commercial operator
PJAH Operator ConsoleHalal Payment GatewayChannel-partner / resellerThird-party paying API· soon
operates under licence to BPJPH
Tier 1a · BPJPH core extended services
Digital Halal CertificateHalal PassportRSHLNHalal Shipment CertPre-border inspection appBPJPH Console (+ INSW coord.)
Tier 1b · Halal Consortium core services
Consortium ConsoleSchema · recognition · accreditationConsortium API· soon
SDK / API
Tier 0 · HARA Trust OS — trust infrastructure
owned by HARA
Registry — ledger / anchors / NFTNumira — subject DIDAtlas — object DID· soon

Ownership: OS = HARA · BPJPH core operated by PJAH under licence to BPJPH (for now) · consortium governs the shared schema. Topology + migration: docs/architecture/target-architecture-and-migration.md.

Section 1 · PNBP services (data layer)

Digital credentials issued under Indonesia's PNBP framework

2 live · more on the roadmap

Each PNBP service is a paid government credential issued by BPJPH, anchored on Polygon for public verifiability. Halal Passport sits at the SKU layer (one per product). Halal Shipment Certificate (HaraShield) sits at the consignment layer (one per shipment, referencing one or more passports or LHLN certs). Every payment for these services routes through Halal Payment Gateway — see Section 2 below.

PNBP-01Halal Digital Passport · HaraPass

One verifiable identity per halal SKU

Per-product digital credential bound to the underlying BPJPH halal certificate, with 4-role attestations (certification, inspection, lab, trade), Polygon anchor, and a QR that resolves in any country. Tariff: Rp 50,000–100,000 per SKU, valid 2 years.

Try a live passport
Browse all 300 halal passports
Flagship · import side
  • · import-passport-flowBerkah verifies a foreign supplier, delta panel, recall feed (~85s)
Supporting scenarios
  • · consumer-scan — QR scan → live verification (~64s)
  • · recognition-delta — field-level ADR 0001 wedge (~75s)
  • · importer-equivalency — pre-shipment recognition check (~70s)
  • · exporter-submission — submit new passport to BPJPH queue (~75s)
  • · authority-approval — review → seal → Polygon anchor (~80s)
  • · consortium-edit — schema governance + audit chain (~75s)
  • · recall-cascade — SiHalal webhook → consumer verdict flips (~90s)
PNBP-02Halal Shipment Certificate · HaraShield

Per-batch halal proof for export consignments

Per-shipment certificate that closes Indonesia's biggest export gap. Exporters pay USD 50–300 to SGS/Intertek today. HaraShield replaces that at Rp 200,000 per batch, < 4-hour turnaround, recognised under bilateral MRAs, anchored to Polygon, and emitted as a W3C Verifiable Credential.

Live shipment certificates
Flagship · import side
  • · import-shipment-flowbulk RSHLN, NTPN, Bea Cukai clearance, money trail (~95s)
Supporting scenarios
  • · harashield-flow — exporter request → BPJPH approve → Polygon anchor → SFDA verifier (~75s)
More scenarios planned: CEISA-embedded request, recall-cascade-to-shipment, freight-forwarder bulk verify.
Section 2 · Halal Payment Gateway

Single checkout, dual-stream disbursement, real-time audit trail

live · in production

HPG sits underneath every PNBP and B2B service in the ecosystem. One payer-facing intent → one DANA checkout → automatic T+1 disbursement to MPN G3 (Kas Negara) and HARA Principal in parallel. NTPN issued immediately. Three-way reconciliation runs nightly: HPG ledger ↔ DANA statement ↔ MPN G3 receipts.

HPGHalal Payment Gateway · HPG

Three primitives that make every payment auditable end-to-end

Single checkout

PNBP + B2B in one transaction. Caller passes line items by code, never by amount — HPG looks up the canonical tariff server-side.

Dual-stream split

PSP performs two disbursements: PNBP to MPN G3 (Kas Negara), B2B fees to HARA Principal. HPG owns the split logic; the PSP just moves money.

Hash-chained audit

Every intent, settlement, NTPN, and disbursement is hash-chained. Daily Merkle root anchored on Polygon. BPK / BPKP can verify independently without trusting the database.

Try it live
Specifications
API · GET /api/v1/hpg/intents
HPG specification: docs/hpg-mvp-spec.md
Flagship · import side
  • · import-shipment-flow — end-to-end HPG loop: bulk pay → NTPN → 60 RSHLNs auto-issue → Bea Cukai clears → Ops sees money trail (~95s)
PSP & settlement
  • · DANA — primary PSP (BI-licensed, SNAP-BI / MPN G3-connected)
  • · DOKU / Xendit / Midtrans — multi-PSP swap-ready (one routing change)
  • · T+1 disbursement — PNBP → Kas Negara, B2B fee → HARA Principal
  • · Daily 3-way recon — HPG ledger ↔ DANA statement ↔ MPN G3 NTPN
See docs/demo-01-import-streamline.md for the full live-demo script (LHLN onboard → importer bulk-pay → certs auto-issue → Bea Cukai clearance).
PNBP-03 · roadmap
Halal Slaughterhouse Registry

Per-facility credential for ruminant + poultry abattoirs. Bilateral with SFDA + UAE supply chains.

PNBP-04 · roadmap
Halal Logistics Certificate

MS 2400-aligned per-route credential for cold-chain and bulk transport of halal goods.

B2B-01 · roadmap
Hara Numira for SMEs

Identity primitive for smaller exporters that don't need full HaraPass but need verifiable provenance.

More PNBP and B2B modules are planned. Each reuses the same Hara Numira identity graph + Hara Registry anchor — no platform fragmentation.

The surfaces

Consoles & apps, by service cluster

six role-gated + one public

Each surface belongs to one tier and reaches the BPJPH core through API/SDK. The four requester portals consolidate into one role-aware Requester Console (see the architecture above).

Clients · Requester Console

· exporter · importer · LPH · LHLN (role-aware, consolidating)

Clients · Halal Value Services

· lab · logistics

Clients · Public PWA Verifier

· auth-free scan-to-verify

BPJPH core extended services

· operated by PJAH under licence to BPJPH

Halal Consortium core services

· shared-schema governance · API later

PJAH services

· commercial operator
Governance & standards

Who decides what a halal passport must contain

Operator and standards body are deliberately separate so no single party can rewrite the rules unilaterally. Member authorities keep sovereignty over their own jurisdiction.

HARA / Dattabot — operator

Builds and runs the platform. Holds the audit chain and anchors to Polygon. Cannot edit halal requirements.

Halal Passport Consortium

Governs the Core schema + HS-code dictionary. Founding sole member: BPJPH. Open to other national halal authorities.

Consortium console
Member authorities

Own their National + Category overlays. Issue and revoke passports. BPJPH today; JAKIM, ESMA/MoIAT, SFDA, MUIS, AFIC as they accede.

The three-layer requirements model

Core
Consortium-governed

Universal floor seeded from SMIIC 1 + Codex CAC/GL 24-1997. Identity, applicant, manufacturer, ingredient list, 4-role credentials.

National
Per authority

BPJPH SJPH layer (penyelia halal, KBLI); JAKIM MS-1500 layer when MY joins; SFDA-FD 2172 layer for SA; and so on.

Category
Per category, per authority

Slaughter method for meat, alcohol type for cosmetics, gelatin source for pharma. Conditional rules — irrelevant fields don't escalate.

HS-code dictionary → internal category → requirement set append-only · sealed passports keep their pinned schema version

What every Halal Passport tells you

Verified by a real authority

See the certifying body (BPJPH, JAKIM, ESMA, SFDA, MUIS, AFIC) and the original cert number. Tap the halal mark to view the actual certificate document.

Where it can be sold

A live recognition matrix shows which countries accept this passport — and which need extra paperwork.

Why it's halal

Plain-language summary built from the real credentials. Madhab acceptance row. Ingredient flags for gelatin, alcohol residue, emulsifiers.

Recall protection

If the certifying authority ever revokes the cert, every consumer who scanned it sees a recall banner instantly.

How it works

  1. 1
    National authority issues the cert

    BPJPH, JAKIM, ESMA, SFDA, MUIS or AFIC certifies the product through their existing system. That remains the legal source of truth.

  2. 2
    Halal Passport mirrors and anchors it

    The cert hash, all 5 credentials and the supply-chain journey are anchored on Polygon, mintable as an NFT for cross-border use.

  3. 3
    Anyone can verify in seconds

    Consumers scan the QR. Importers run pre-shipment checks. Customs agents confirm acceptance. All from one passport.