← AHMAD BILAL / INDEX OTHER WORK · PVARA · 2025
GOV · REGULATIONFOUNDATION WORK

PVARA: groundwork for Pakistan's virtual-asset regulator

Before the Pakistan Virtual Assets Regulatory Authority had a public face, I did the foundation research and design for one: the benchmark analysis, the service experience, and the citizen-facing tools. The live site at pvara.gov.pk has evolved since. The groundwork is this.

Ahmad Bilal, Product Design Engineer & ResearcherFoundation research & design
ROLE
Research & Design
CLIENT
PVARA
TYPE
Government Service Design
TIMELINE
Late 2025
FIG.01ENLARGE ↗ The landing design. One promise up top, then the fork that shapes everything: consumers who need to invest safely, and VASPs who need to get licensed
FIG.01. The landing design. One promise up top, then the fork that shapes everything: consumers who need to invest safely, and VASPs who need to get licensed. // click to enlarge

Overview

A new federal regulator has a strange design problem. Nobody knows it exists, half its audience is scared of the thing it regulates, and the other half wants a licence yesterday. In late 2025 I took that problem on for PVARA: a full analysis of what the authority's web presence needed, benchmarked against the regulators that got there first, and a designed answer.

The work was research first. I studied VARA in Dubai and ADGM in Abu Dhabi, the two most mature virtual-asset regulators in the region, and mapped what their digital services do well and where citizens still get lost. The design decisions below came out of that benchmark, and I can defend every one of them.

Two audiences, one front door

The core call was structural: a regulator's site serves two publics with almost nothing in common. Consumers need safety, plain language, and a way to check whether a platform is licensed before they hand it money. VASPs and fintechs need the ordinance, the licensing regime, and a register they can be found in. So the experience forks immediately: invest safely on one path, get licensed on the other, with the VASP directory as the shared trust anchor between them.

Three service pillars carried the positioning: remittances and inclusion (regulated channels that let families keep more of what they send home), the regulatory sandbox (test with real users under supervision before scaling), and the Shariah-compliant framework (a dedicated advisory committee, so alignment with Islamic finance principles is a design feature, never a footnote).

FIG.02ENLARGE ↗ The service pillars and the hub model: investors, VASPs, the Shariah board, and the regulator, with verification, licensing, compliance audit, and enforcement as the connecting flows
FIG.02. The service pillars and the hub model: investors, VASPs, the Shariah board, and the regulator, with verification, licensing, compliance audit, and enforcement as the connecting flows. // click to enlarge

Making the market legible

Trust in a regulator starts with legibility, so the design leads with the numbers that make the market real: adoption, assets under regulatory oversight, licensed providers. The same instinct that runs through my other work applies here: claims you can check beat adjectives every time.

FIG.03ENLARGE ↗ The key-indicators strip, designed to make the regulated market legible at a glance
FIG.03. The key-indicators strip, designed to make the regulated market legible at a glance. // click to enlarge

The deepest piece of the citizen-facing work was a remittance-savings calculator, specified end to end: real corridor cost data, the comparison logic, and the interface for a family to see what a regulated channel saves them against informal ones. Remittances are where virtual-asset policy touches ordinary households, and the calculator was designed to make that concrete.

Where it stands

PVARA launched, and pvara.gov.pk has grown well beyond this foundation: licensing regulations, advisories, a complaints channel. Some foundation elements are still ahead of the live site, the public register as shared trust anchor among them; others were iterated away by PVARA's own team as the service found its shape. Both are normal fates for groundwork. This page is the record of where it started, not a claim on what stands today. verify ↗

The full PVARA thread on this site: the essay on designing a regulator people can trust and the sourced PVARA encyclopedia for its actual audiences.

For the thinking behind how I approach institutional trust surfaces, read Auditable AI research, or see the GovX 2030 work for the earlier government thread.