1The HPZ investigation, frozen amounts and PayU’s answer
analysisIn January 2025, reporting linked virtual accounts at eight Indian payment gateways to the Enforcement Directorate’s HPZ Token investigation. The roughly Rs500 crore frozen across the gateways was an aggregate figure; the report attributed about Rs130 crore to accounts at PayU. It described an alleged investment scheme and scrutiny of payment handling, rather than a judgment finding PayU itself guilty of operating the scheme. 1 2
- qualification
- Funds held in payment accounts are not automatically the payment company’s own corporate assets. Allegations or proceedings concerning the scheme’s promoters are not convictions of PayU, Prosus or Naspers.
- response
- A PayU spokesperson told the newspaper the following day that the reports concerned events in 2022 and that PayU had fully cooperated with the Enforcement Directorate. Other gateways’ separate denials are not attributed to PayU.
- outcome
- The retained material establishes reporting of freezes and an investigation, together with PayU’s response; it does not establish a final adverse judgment against PayU in this matter.
2India authorisation, remaining losses and the separate European sale
analysisPayU’s regulatory and disposal history should be read alongside the HPZ reporting. A January 2023 instruction to reapply for an Indian payment-aggregator licence preceded a later final online approval. The FY26 company report says PayU had obtained online, offline and cross-border aggregator approvals. These permissions concern defined services and entities, not immunity from unrelated investigations. 3 4
- qualification
- The sale of Global Payments Organisation activities did not mean the sale of PayU’s Indian business. The latest financial report records completion of the European GPO disposal in November 2025. Earlier transaction announcements describe a broader agreed business perimeter and must retain their own date and scope.
- outcome
- FY26 India revenue reached US$781 million and adjusted EBITDA was positive at US$18 million, while adjusted EBIT remained a US$10 million loss. The credit business improved to US$6 million adjusted EBITDA, retaining both the favorable trend and the remaining operating loss.
Sources (4)
- Media source · s-d219 identified by category only · Media
- Media source · s-supp-payu-response identified by category only · Media
- Company statement source · s-d17 identified by category only · Company statement
- Media source · s-d99 identified by category only · Media
Recorded connections
- Naspers Limited to PayU (group brand; legal entities distinguished)Group business in South Africa; direct chain not impliedreported · Source recorded 2026-06-29; underlying appointment or transaction date and later status are not inferred from retrieval · current or historical not established
- Laurent Le Moal to PayU (group brand; legal entities distinguished)PayU chief executivereported · PayU CEO in 2021 SEC disclosure; no right to vote or dispose of the disclosed Remitly holding · current or historical not established
- Naspers Limited to PayU (group brand; legal entities distinguished)Group payments business; exact direct chain variesreported · Source recorded 2026-09; underlying appointment or transaction date and later status are not inferred from retrieval · current or historical not established
- Prosus N.V. to PayU (group brand; legal entities distinguished)Parent of PayU groupreported · Source recorded 2025-05-13; underlying appointment or transaction date and later status are not inferred from retrieval · current or historical not established
- PayU (group brand; legal entities distinguished) to RapydSeller of GPO operations to Rapyd; India excludedreported · Source recorded 2025-05-13; underlying appointment or transaction date and later status are not inferred from retrieval · current or historical not established
- PayU (group brand; legal entities distinguished) to Enforcement DirectoratePayment gateway named in HPZ investigation reporting; no conviction establishedreported · Source recorded 2025-01-24; underlying appointment or transaction date and later status are not inferred from retrieval · current or historical not established