At a glance
Holds customers, accounts, contacts, addresses and identity status.
Key data
Receives from
- Channels
- KYC providers
Sends to
- Order capture
- Billing
- CRM
- IAM
How it works
The main steps, end to end.
- 1Capture customer details
- 2Verify identity (KYC)
- 3Create accounts and hierarchy
- 4Maintain addresses, contacts and payment tokens
- 5Share a single customer record with all systems
Core Capabilities
What Party Management provides across all subscriber lifecycle operations
Account Management
- Creates and manages subscriber accounts across all channels
- Stores personal details: name, date of birth, gender, addresses
- Manages account status lifecycle: Active, Suspended, Inactive, Former
- Supports account type segmentation: individual, business, MVNO
- Links multiple service lines and billing accounts per subscriber
Identity & KYC
- Manages KYC status per subscriber: Not Performed, In Progress, Approved, Rejected
- Supports multiple KYC types: document image, IC chip, in-person
- Tracks KYC method and verification outcome per account
- Generates and manages encrypted identity containers for IC chip verification
- Stores verification status for regulatory compliance
Address Management
- Stores shipping, billing and service addresses per account
- Validates address formats for domestic and international addresses
- Supports multiple addresses per account with labelling
- Used for shipment routing and service area validation
Payment Method
- Stores tokenised payment method reference per account
- Supports credit card, direct debit and other payment channels
- Payment credential tokenised externally — no raw data stored
- Links payment method to billing account for invoice collection
Relationships
- Manages account relationships: parent/child, family group, MVNO tenant
- Creates and updates relationship links between accounts
- Used for family plan grouping, business account hierarchies
- Validates relationship eligibility before linking
Fraud & Risk
- Fraud status checking during account creation and order flows
- Integrates with fraud management service for real-time checks
- Tracks fraud indicators per account for risk assessment
- Blocks high-risk accounts from proceeding with service orders
Storage & Persistence
How and where PartyManagement stores its data
Document Data Store
- Customer account documents: personal details, status, addresses
- KYC status and verification records
- Payment method tokens — no raw credentials
- Relationship documents: family groups, parent/child links
- Fraud status flags per account
Search Index
- Full-text search across account attributes
- Search by MSISDN, email, IMEI, ICCID, order ID
- Used by CRM and Order Capture for eligibility checks
Async Event Bus
- Account created / updated events
- KYC status change events
- Payment method update notifications
Design Principles
Key architectural decisions behind Party Management
Single Account of Truth
All channels, services and downstream systems resolve subscriber identity through Party Management. Account number, KYC status, address and payment method are always read from this single source — preventing inconsistency across the platform.
KYC as a Lifecycle State
KYC is not a one-time event — it is a persistent account attribute with a status that can be updated, reset and re-verified. Party Management owns this state and exposes it to Order Capture, billing and care services for eligibility checks.
Zero Raw Payment Storage
Party Management stores only a payment method token — never raw card numbers or bank account details. The tokenisation service owns credential resolution, keeping sensitive payment data outside the core account system.
AI-assisted document and face checks for faster, safer onboarding.
Find duplicate customer records despite spelling and address differences.
More in 30 AI & ML use cases and AIOps for BSS.