Payments Business Data Model: AI-Ready Edition | Capstera

The Payments Business Data Model: AI-Ready Edition is for business and enterprise architects who need to know what information payments work runs on before an AI agent touches it. It covers 14 subject areas, 82 entities, 577 key attributes and 262 relationships. Every entity and key attribute is classified for sensitivity, with the AI uses and data-quality requirements an agent depends on. It holds the 73 entities every bank and payments company shares and the 9 specific to payments companies, from Business Architecture for Banking and Payments: AI Transformation Blueprint.

What's Inside

The same model comes in three files: the full model in Word, a workbook to filter and extend, and a guide to the scales and the license.

• 14 subject areas and 82 entities, each with a definition, its typical system of record, sensitivity class, AI uses and data-quality requirements
• 577 key attributes with sensitivity and AI relevance, and 262 relationships with cardinality
• Under each entity, the capabilities that need it and the agents that read it, by name and ID
• The Business Data Model (Word): every subject area and entity in full
• The workbook (Excel): subject areas, entities, attributes and relationships in sheets you can filter and extend
• The guide (Word): the scales the model refers to, the data foundation, and the license
• Free corrections, and new versions free for 180 days

Every file names your organization and carries your license ID.

The 14 Subject Areas

The 82 entities are grouped into 14 subject areas. The list gives what each holds and how many entities it has.

• Client Due Diligence and Reference Data (5 entities): Who each client is, who owns and controls it, its financial crime risk rating and reviews, and the classifications and settlement instructions every product uses.
• Financial Accounts and Client Communications (5 entities): The accounts clients hold, who may operate them, and the statements, confirmations and notices clients receive.
• Payments and Settlement (5 entities): Payment instructions from receipt to settlement, the submissions to schemes, the organization's settlement positions and accounts, and returns.
• Payment Exceptions and Disputes (5 entities): Payments that need repair or investigation, recalls between banks, and clients' disputes of transactions.
• Financial Crime (7 entities): The financial crime risk assessment, the screening lists and monitoring scenarios, the alerts they raise, the cases investigated and the reports decided.
• Fraud (4 entities): Fraud alerts and rules, clients' fraud and scam claims, and fraud losses and recoveries.
• Credit Policy, Applications and Decisions (6 entities): The credit policy and delegated authorities, credit applications, risk ratings, decisions and the facilities granted.
• Collateral, Limits and Exposure (6 entities): Collateral and its valuations, the security documents behind it, credit limits and their excesses, and exposure to each counterparty.
• Credit Monitoring and Loss (5 entities): Covenants and their tests, the watchlist and early warning signals, and the expected loss, staging and write-off inputs Finance receives.
• Balance Sheet and Liquidity (8 entities): The balance sheet plan, interest rate risk in the banking book, funds transfer prices, liquidity positions and stresses, the funding plan, the contingency funding plan and the liquidity buffer.
• Capital, Safeguarding and Supervisory Reporting (5 entities): The capital plan and risk-weighted exposure, the safeguarding of client money, and the supervisory returns.
• Financial Products and Pricing (6 entities): Financial products and their approval and review, interest rate and fee schedules, pricing exceptions and product documents.
• Banking Operations Control and Models (6 entities): The end-of-day ledger feeds, suspense items, reconciliation breaks, operational loss events, and the inventory and validation of quantitative models.
• Payments (9 entities): Merchants and their agreements, settlements and reserves, authorizations, payment tokens, wallets and stored value, card programs and network fees.

Who Uses It

Data owners and stewards, data architects, and AI and analytics engineers who need to know what an agent may read, how sensitive it is and how good it must be first; and business architects who link capabilities to data.

How It Fits With the Other Products

The capabilities named under each entity are defined in the Banking and Payments Capability Model: AI-Ready Edition. The agents are specified in Business Architecture for Banking and Payments: AI Transformation Blueprint, which contains this data model and adds the value streams, use cases, controls, an operating model and a roadmap. The Payments Value Streams are sold on their own too.