Industry Vocabulary Reference

Banking & Financial Services

Comprehensive enumeration library for the Banking and Financial Services vertical. Covers every subdomain where agentic AI is actively deployed as of March 2026: payments, lending, fraud and financial crime, treasury and capital markets, customer lifecycle, model risk, regulatory capital, and digital assets. Designed for use as OTel span attributes in an agentic AI SDK and as policy vocabulary in an OPA Rego GRC portal.

Back to industry coverage library

How to use this reference

1. Start with the core file if you need the cross-industry governance baseline.
2. Then move into the vertical file to see the regulated workflow vocabulary, policy surfaces, and implementation pressure unique to this market.
3. Use the OTel attributes and policy paths here as the common language across SDK instrumentation, governance review, and evidence export.

March 2026 deployment context

As of March 2026, agentic AI in banking is deployed across: real-time payment fraud scoring, autonomous AML alert triage, AI-assisted loan underwriting, autonomous treasury liquidity management, customer onboarding KYC/KYB automation, AI-driven trade surveillance, autonomous regulatory report generation (DORA, Basel, HMDA), and AI-assisted credit risk model validation. Each subdomain carries distinct regulatory obligations that must be traceable through OTel spans to OPA policy decisions.

Loading Model

• Mirrored file: 01_vertical_banking_financial_services.json
• Kind: vertical

OTel Namespaces

Primary Standards

• BIAN v13 / v14 (Banking Industry Architecture Network)
• ISO 20022 — Universal financial industry message scheme
• Basel III / Basel III Endgame (BCBS 2017 finalisation, US phase-in through 2028)
• EU DORA — Digital Operational Resilience Act (2022/2554, effective Jan 2025)
• Federal Reserve SR 11-7 — Supervisory Guidance on Model Risk Management (2011)
• FATF Recommendations — AML/CFT (updated 2023)
• EU 6AMLD — Sixth Anti-Money Laundering Directive
• FinCEN / BSA — Bank Secrecy Act SAR requirements
• PCI DSS v4.0 — Payment Card Industry Data Security Standard
• SWIFT CBPR+ — Cross-Border Payments and Reporting Plus (coexistence ended Nov 2025)
• FedNow — Federal Reserve real-time payment service ISO 20022 profile
• SEPA — Single Euro Payments Area rulebooks

Source URLs

• https://bian.org/deliverables/bian-standards/
• https://www.iso20022.org/iso-20022-message-definitions
• https://www.bis.org/bcbs/publ/d424_hlsummary.pdf
• https://www.eba.europa.eu/regulation-and-policy/operational-resilience/digital-operational-resilience-act-dora
• https://www.federalreserve.gov/supervisionreg/srletters/sr1107.htm
• https://explore.fednow.org/resources/readiness-guide-iso-20022.pdf
• https://www.swift.com/standards/iso-20022/iso-20022-financial-institutions-focus-payments-instructions

Subdomains

Implementation examples

• Payments & Funds Transfer: Payment Rail Type. OPA rule: require enhanced OFAC/sanctions screening for swift_cbpr_plus, sepa_credit_transfer, and sepa_instant rails. Require 24/7 HITL coverage for fednow and rtp_tcf rails above configurable threshold. (Fednow: Federal Reserve FedNow Service Operating Procedures)
• Payments & Funds Transfer: Payment Agent Action Type. OPA rule: classify initiate_credit_transfer, initiate_direct_debit, and apply_fx_conversion as irreversible_high_impact, requiring HITL approval above configurable amount threshold. (Psd2: PSD2 Article 64 — Liability for unauthorized payment transactions)
• Payments & Funds Transfer: Sanctions Screening Outcome. OPA rule: deny any payment agent tool call for payment rail execution when sanctions_screening_outcome is potential_hit or confirmed_hit; require HITL escalation. (Ofac: OFAC 31 CFR Part 501 — Reporting and procedures for blocked transactions)
• Fraud Detection & Financial Crime: AMLAlert Status. OPA rule: require HITL with compliance_officer role for sar_decision_pending state. Block automated sar_filed or sar_declined_documented transitions — these must be human-authorised. (Bsa 31 Usc 5318: BSA 31 USC 5318(g) — Suspicious Activity Report filing obligation)

Illustrative policy patterns

package banking.payments

blocking_sanctions_outcomes := {"potential_hit", "confirmed_hit", "escalated_to_compliance"}

deny[msg] {
  input.banking_payment_agent_action in {
    "initiate_credit_transfer",
    "initiate_direct_debit",
    "apply_fx_conversion"
  }
  input.banking_sanctions_screening_outcome in blocking_sanctions_outcomes
  msg := sprintf("Payment blocked: sanctions screening outcome '%v' requires compliance officer review before execution", [input.banking_sanctions_screening_outcome])
}

package banking.aml

reserved_aml_decisions := {"sar_filed", "sar_declined_documented", "blocked_and_frozen"}

deny[msg] {
  input.banking_aml_alert_status in reserved_aml_decisions
  input.gen_ai_agent_autonomy_level in {"supervised_autonomous", "fully_autonomous"}
  input.gen_ai_hitl_decision != "approved"
  msg := "SAR filing and SAR declination decisions require documented compliance officer approval per BSA 31 USC 5318(g)"
}

From enum to evidence

The same vocabulary should carry from instrumentation through review. The OTel attribute names here become emitted metadata, those attributes become policy inputs, and those same labels should still be intelligible when a reviewer opens the decision record later.

import { VeriproofClient, VeriproofSdkOptions, SessionMetadata } from '@veriproof/sdk-core';
import { PaymentStatusISO20022, PaymentStatusISO20022Meta, PaymentMessageType, PaymentMessageTypeMeta, PaymentRailType, PaymentRailTypeMeta } from '@veriproof/sdk-core/verticals/banking-financial-services';

const client = new VeriproofClient(
  VeriproofSdkOptions.createProduction({
    apiKey: process.env.VERIPROOF_API_KEY!,
    applicationId: 'banking-financial-services-production',
  }),
);

const session = client
  .startSession('banking-financial-services.review')
  .withSessionMetadata(SessionMetadata.forTransaction('txn-1001').withEnvironment('production'))
  .addStep('evaluate_workflow', { output: { status: 'completed' } })
  .withMetadata(PaymentStatusISO20022Meta.otelAttribute, PaymentStatusISO20022.ACTC)
  .withMetadata(PaymentMessageTypeMeta.otelAttribute, PaymentMessageType.pain.001)
  .withMetadata(PaymentRailTypeMeta.otelAttribute, PaymentRailType.fednow)

await session.complete();

• SDK: emit the OTel attribute shown on this page during the decision workflow.
• Policy: reference the matching `opa_policy_path` in governance rules.
• Evidence: surface the same label and value in the portal and exported record so reviewers are not translating between systems.

For a step-by-step getting-started walkthrough specific to this vertical, open the Banking & Financial Services SDK quick start. For the full core API reference, continue with TypeScript, Python, or .NET.

Highlighted Enum Categories

This reference page is rendered from the mirrored JSON file inside the docs app, not from a hand-written website model.

If you need the machine-readable asset for offline review, automation, or internal diffing, use the mirrored JSON download above.

Next: open the corresponding SDK reference under SDK documentation and then compare it with the public-site industry page to see how the same vocabulary is framed commercially.