The silence of a missing transaction trail is suddenly deafening for Kenya’s vibrant informal economy. For thousands of street vendors, kiosk owners, and digital marketplace traders, the M-Pesa confirmation SMS was once a source of absolute certainty—a digital handshake providing the sender’s full name and mobile number. As of late March 2026, that certainty has been replaced by a partially masked string of digits, forcing merchants to navigate a new, complex administrative hurdle to identify their customers.

This shift represents a significant pivot in Safaricom’s data strategy, effectively prioritizing data minimization and user privacy over the convenience of immediate, transparent transaction logs. While the telecommunications giant asserts that the masking of phone numbers is a critical defensive measure against rampant social engineering, the implementation has sparked an immediate outcry from business operators who rely on transaction traceability to resolve payment disputes, track inventory, and manage daily accounts.

The Anatomy of a Digital Shield

The core of the change lies in the modification of the ubiquitous M-Pesa transaction SMS. Under the new protocol, while the sender’s first and last names remain visible, the middle digits of the phone number are redacted—a measure designed to prevent the unauthorized harvesting of personal contact data. For the millions of Kenyans who process transactions totaling billions of shillings daily, this represents the most consequential privacy update to the platform since its inception in 2007.

Safaricom has introduced a secondary validation layer to bridge the gap created by this privacy shield. When a merchant or recipient needs to identify a sender, they are now required to forward the M-Pesa confirmation message to the shortcode 334. This action initiates a request for the sender to authorize the disclosure of their full identity. The sender must then manually approve the sharing of their contact details, a process that Safaricom claims is essential for maintaining compliance with the Data Protection Act.

• New Transaction Format: Sender’s phone number now appears masked (e.g., 0722***000), while the amount, transaction code, and timestamp remain visible.
• Verification Window: Verification requests via the 334 shortcode must be initiated within 24 hours of the original transaction.
• Opt-In Requirement: Full sender details are only released if the sender actively approves the request, creating a two-step verification cycle.
• Security Rationale: The update directly combats social engineering tactics where scammers use visible numbers to impersonate customer care agents or fake clients.

The Paradox of Privacy and Utility

For the average consumer, this update is a welcome deterrent against the growing tide of mobile-based fraud. Reports from cybersecurity firms indicate that nearly 46 percent of Kenyan mobile users have been targeted by fraudulent communication in the past year alone. By obscuring the sender’s number, Safaricom effectively creates a hurdle for bad actors who build databases of victims based on transaction logs. Yet, the policy creates a significant friction point for the informal sector.

Small-scale traders, who often conduct hundreds of transactions a day, are reporting that the manual verification process is fundamentally unscalable. An operator selling perishable goods in a busy market cannot pause a transaction to wait for a customer to verify their identity via USSD prompts. The result is a potential loss of reconciliation power, where businesses are unable to account for incorrect payments or verify the legitimacy of high-value transfers in real-time.

The Broader Context of Data Protection

This initiative follows a pattern of regulatory alignment that has been sweeping across the East African financial sector. The Central Bank of Kenya has increasingly emphasized the need for stringent data governance, pushing financial institutions to adopt privacy-by-design frameworks. While the move is consistent with global data protection standards—akin to the European Union’s General Data Protection Regulation—the local implementation must balance these standards against the unique reliance of the Kenyan economy on mobile money as its primary transaction medium.

Financial analysts argue that while the 334 verification workaround may seem cumbersome, it forces a shift in how Kenyan businesses integrate their payment systems. Larger enterprises with integrated PayBill or Till number APIs have largely been using masked data for some time this update effectively forces the smallest of vendors to modernize their back-office systems. The tension, however, remains palpable. Safaricom faces the dual challenge of acting as both a custodian of sensitive consumer data and the operator of the nation’s most vital commercial plumbing.

A Future Built on Verification

As the dust settles on this transition, the long-term impact on transaction volume and user confidence remains to be seen. Safaricom has committed to refining the user experience, but the fundamental change in how trust is brokered on the M-Pesa network is unlikely to be reversed. The era of the "open" transaction log, where every sender’s details were laid bare to the recipient, is effectively over.

Whether this shift will result in a measurable decrease in mobile money fraud, or merely shift the burden of verification onto the shoulders of the merchant, will be the true test of this policy. For now, the Kenyan digital economy remains in a state of adjustment, moving from a culture of unchecked transparency toward a more regulated, albeit more complex, framework of digital privacy.