Pakistan reviewing tokenisation of its existing Eurobond debt; Cabinet approval needed before RFP

The Government of Pakistan is reviewing the possibility of tokenising its existing Eurobond debt — that is, re-representing an obligation already issued as digital tokens on a distributed ledger. The information emerged at a dialogue event attended by representatives of the Ministry of Finance, the Pakistan Banks' Association and the Lahore University of Management Sciences (LUMS). Federal Finance Minister Muhammad Aurangzeb made clear at the forum that the initiative remains at the discussion stage and that approval from the federal Cabinet is mandatory before a Request for Proposals (RFP) is issued. In other words, no new security is being issued at present; what has been announced is an intention. The format of the event itself suggests this is pre-policy dialogue rather than the launch of a funded programme. It was held at a joint forum of a banking-industry body and an academic institution rather than at a ministry press conference, and the principal audience was industry practitioners and future professionals rather than international investors. In his address, the Finance Minister appealed directly to banks to invest in expertise in this area and to secure support at their board level. The meaning of tokenisation needs to be understood clearly here. According to the report, the subject is 'existing Eurobond debt' — a commitment that has already been issued and is now to be re-presented on a distributed ledger. This is not a new borrowing operation. The distinction matters, because tokenisation on the liability side is fundamentally an exercise in settlement, operations and investor access, not a transformation of the balance sheet. Reading it as 'Pakistan monetising its assets' would be a misreading. The government has described the aim as improved sovereign debt management and the opening of new distribution channels through digital means. A parallel track is also under way, covering the tokenisation of real estate and other investment assets. Seen together, this indicates an effort to build a broad domestic digital-asset agenda rather than a single debt-market experiment — with the Eurobond component as the flagship element. The regulatory architecture looks considerably more concrete than the transaction itself. According to the report, a dedicated statute for virtual assets exists — the Virtual Assets Act, referred to as the '2026' Act — and PVARA (Pakistan Virtual Assets Regulatory Authority) has been empowered to license and supervise. The sequencing is notable: statute and regulator first, then a limited access pathway for banks, and only then a financial product. Many emerging markets have followed the reverse order, in which the product arrives first and regulation follows. The State Bank of Pakistan has laid down a conditional pathway for banks. Under it, banks may provide services to licensed businesses, subject to requirements such as proper due diligence and client-fund segregation. Client-fund segregation means customer money is held separately from the bank's own money, so that it is protected if the bank fails. But the same framework contains a limit that calls the commercial logic of the entire plan into question: banks are not permitted to invest, trade or hold virtual assets using their own funds or customer deposits. This prohibition is not a compliance footnote but the central design parameter. Its direct implication is that the banks' role narrows to custody, servicing and distribution fees — a thin revenue line against a heavy cost of building compliance and technological capability. This is precisely why the Finance Minister's appeal matters, in which he asked banks to invest in customer relationships, operational experience and risk management capabilities. He also asked banks to work with the relevant regulators to determine which activities are permitted within their mandates. In other words, banks are being expected to co-author their own rulebook — a signal that the permitted-activity perimeter has not yet been finally settled. Analytically, this is a familiar 'capability-gap' framing: the mandate sits with the government, but execution capacity sits with private banks. The government says it will make the rules, but the actual technical and operational capability will be built by the banks, and the risk will land with them too. Since the revenue-generating activities are restricted, this creates a classic principal-agent incentive mismatch. From an information standpoint the report is thin. No ISIN, maturity date, size, currency or governing law is given for any affected bond. No cost-saving figure is provided. There is no mention of a platform, a settlement venue or a legal-finality mechanism. No timetable has been announced. In the absence of all this, treating the initiative as a funded, defined programme would be premature; on the available information it reads at least as much as exploratory signalling as a planned project. Procedurally, the plan must pass through several gates — first Cabinet approval, then publication of the RFP, then vendor selection. Each gate takes time and each carries a risk of stalling. Historically, sovereign fintech initiatives have rarely reached live issuance within twelve months, so schedule risk should be treated as high. One further point was raised by the minister himself: cybersecurity. He said the threat is continuous, around the clock and every day, and involves both state and non-state actors. That acknowledgement matters, because it turns security architecture into a precondition rather than a supporting workstream. In practice, cybersecurity should be made part of the RFP's selection criteria rather than a condition added later. The biggest omission concerns cross-border and anti-money-laundering issues. A Eurobond is typically governed by foreign law and settles through international securities settlement systems. How the domestic PVARA regime will interact with offshore settlement, securities law and AML standards is not addressed at all in the report. This gap may prove the most decisive factor in determining feasibility. Caution is also warranted on the statutory dating — the law is referred to as the '2026' Act while the report's own date is unclear; this should be verified against the primary legal text. What to watch next is clear. First, the Cabinet decision — approval would move the initiative from 'intention' to 'procurement'. Second, publication of the RFP — that will reveal scope, instrument, platform and budget. Third, PVARA's rulebook — banks will be able to build viable products only once permitted activities are defined. Fourth, the State Bank's posture — any relaxation of the own-fund prohibition would materially improve the commercial case. Finally, a clear caveat. The language of the entire exercise is cautious — 'reviewing', 'in discussions', 'awaiting Cabinet approval before issuing the RFP'. This is a pre-decisional state. Presenting it as a live issuance programme, or saying that Pakistan 'is tokenising' its Eurobonds, would go beyond the facts. The correct conclusion is that Pakistan is exploring tokenisation, and the most solid part of that exploration is not the financial instrument but the regulatory architecture being built around it.