Customer 360: telco plus fintech signals under PDP risk
صارف کا مکمل تصور: PDP خطرے میں telco اور fintech کا میل
36 min read
Three ways to see it
Customer 360 is the practice of unifying every record about one customer across every system the company runs, and using that unified view to drive personalisation, support, and risk decisions. In Pakistani telco-fintech groups like Jazz with JazzCash and Telenor with EasyPaisa (now Telenor Microfinance Bank), the value of joining the two halves is enormous, but the regulatory regime is shifting under the PDP Act 2025 and SBP guidance for branchless banking.
Way one to think about it: identity is the hard part. Tying a JazzCash CNIC to a Jazz mobile MSISDN sounds easy because both are KYC verified. In practice, families share CNICs informally, agents register accounts on behalf of customers, and a single household has multiple SIMs registered to one elder. A naive join over CNIC creates a synthetic super-user that is actually three real humans. The right approach uses probabilistic linkage with explicit confidence and lets the data product reflect that uncertainty.
Way two: the value pockets are uneven. Cross-sell of a microloan to a JazzCash user with steady recharge income is a high-value, well-defined use case. Cross-sell of a Tamasha premium subscription to a heavy data user is medium value. Using location grids from BSS to suggest merchants in a JazzCash user's neighbourhood is low value but high creep risk. Customer 360 leadership must triage by value-per-creep, not just value, or the whole programme stalls under regulatory and customer-trust drag.
Quick check
Quick check: what makes modern AI different from a rule-based program?
The why-tree
Why-tree level one: why is consent more honest as a UX flow than a single signup checkbox? Because customers do not read terms of service. They do read 'allow Jazz to use your JazzCash data to suggest microloans' as a single screen with a yes and no button. Granular, in-context consent is what survives audit and customer trust.
Try this with Claude
AI-edge prompt: 'I am the data leader at a Pakistani telco-fintech group. Design a Customer 360 architecture that joins BSS, JazzCash-style wallet, and content-app data under PDP Act 2025. Cover (1) probabilistic identity resolution with confidence scores, (2) granular purpose-bound consent UX strings in Urdu and English, (3) data minimisation principles per use case, (4) model retraining and right-to-be-forgotten workflow, (5) the three SBP and PTA notifications I will need to file before launch.'
Sources
Sources and further reading. Pakistan Personal Data Protection Act 2025 final text. SBP Branchless Banking Regulations and Mobile Wallet rules. PTA SIM Information System guidelines. GSMA Mobile Money Privacy Toolkit. EU GDPR as a comparison reference. Probabilistic record linkage: Splink, Zingg open-source tools. Customer Data Platforms: mParticle, Segment architecture papers. Operator case studies: Safaricom M-Pesa unified customer view, Vodacom South Africa data ethics framework. JazzCash and EasyPaisa public annual reports.