Transaction Monitoring Data Integration Guide

This guide outlines the data specifications and implementation steps required to support transaction monitoring for regulatory compliance. It is not a fraud detection or fraud liability tool, and should not be interpreted as such. Instead, it ensures that the appropriate data is delivered to support the bank’s internal Financial Crimes Oversight processes.

1. Engagement and Setup

Initial Engagement

We will provide detailed implementation documentation that includes:

• File specifications
• Transaction type templates
• Testing requirements
• Error handling procedures

These documents are designed to help your team prepare and validate the required data feeds.

2. File Specification Requirements

File Format

• Type: Pipe-delimited text
• Encoding: UTF-8
• Extension: .txt

File Naming Convention

• Format: ACRONYM_ENV_ENTITY_YYYYMMDD.txt
• Components:
  • ACRONYM: Four-letter client identifier
  • ENV: T for Test, P for Production
  • ENTITY: e.g., CARD
  • YYYYMMDD: File date

Examples:

• Test File: ABCD_T_CARD_20240910.txt
• Test Control File: ABCD_T_CARDCONTROL_20240910.txt
• Production File: ABCD_P_CARD_20240910.txt
• Production Control File: ABCD_P_CARDCONTROL_20240910.txt

Delivery Cadence

• Test Files: As needed during implementation
• Production Files: Daily, unless otherwise specified

3. Required Data Entities

Each file must include the following entities. For full field-level requirements, naming conventions, and validation rules, refer to the linked specification pages:

• Cardolder Requirements
  Includes legal name, address, phone number, and government-issued ID.

• Card Requirements
  Includes card number, open/expiration dates, status, and balance.

• Posted Transactions Requirements
  Includes transaction amount, merchant details, and timestamps.

• Business Requirements
  Includes business registration and legal entity information.

• Beneficial Owners Requirements
  Includes ownership percentage, identification, and role.

4. Kickoff Call

We’ll schedule a kickoff call to:

• Review implementation documents
• Align on timelines
• Outline the testing process

5. Path to Production

Sign-Off Before Implementation

A formal sign-off is required to confirm alignment before implementation begins.