CDP-архитектура для банка

Зачем банку CDP

Banking core (АБС) хранит accounts, не customers. Карточный процессинг, кредитный pipeline, ВЭД, ипотека — каждое со своей customer record. Cross-product view отсутствует.

CDP — слой, который resolves identity между systems и provides unified profile downstream channels (mobile app, contact center, marketing, advisory).

Структурные элементы

Identity resolution. Связывание records по паспорту, ИНН, телефону, email. В банке specifically — сложно из-за КYC variations, joint accounts, corporate hierarchies.

Profile store. Денормализованный single profile с current state (products, balances, segments) + rolling aggregates (LTV, churn risk, propensity).

Event ingestion. Streaming events из АБС, card processor, app, branch, contact center.

Consent layer. Каждый attribute профиля привязан к customer consent. Per-purpose (marketing, scoring, partner sharing).

Channel APIs. Unified API для downstream — каналы видят consistent view.

Audience builder. Segments для marketing на 360 view, не на product-specific data.

Где банк-specific сложнее, чем telecom

Joint accounts — multi-owner records.

Corporate hierarchies — холдинг → дочки → счета.

Regulatory restrictions на cross-product profiling — некоторые jurisdictions требуют explicit consent.

KYC refresh cycles — profile должен reflect current verification status.

Beneficial ownership — для AML profile должен включать UBO links.

Operating model

Owner — CDO с tech mandate. Не маркетинг, не IT инфра.

Stewardship per source domain (АБС, cards, lending).

Consent steward (compliance / DPO).

Channel integration leads.

Связанное

• /solutions/banking-customer-360-platform/ — customer 360
• /architecture/banking-master-data-management/ — MDM
• /architecture/banking-event-bus-architecture/ — event bus
• /architecture/banking-consent-architecture/ — consent