Overview

This page outlines the file specifications for the Embedded Deposit Account Solutions (EDAS) product. EDAS enables clients to offer deposit accounts and requires structured data submissions to support transaction monitoring and sanctions screening.

Payment Transaction

Payment Transaction represents transaction records submitted by clients as part of the Embedded Deposit Accounts Solutions (EDAS) product. The Payment Transaction entity captures financial activity at the subledger level, representing both inbound and outbound payments to and from deposit accounts.

Key characteristics:

• Includes credits (e.g., deposits, incoming transfers) and debits (e.g., withdrawals, outgoing payments).
• Each record reflects a discrete financial event, including metadata necessary for reconciliation and monitoring.
• Transactions must be reported with sufficient detail to support:
• Transaction Monitoring
• Sanctions Screening
• Travel Rule Compliance (for applicable payments)

Person

This Person entity represents a person who possesses distinct legal rights and is associated with a deposit account product. The entity should contain all legal details of a person.

Related Resources

These resources provide essential guidance for implementing and maintaining your program across EDAS and Card Issuing. Refer to each for entity definitions, file formats, and operational requirements.

• Common Issuing File Specs Defines shared data structures for accounts, businesses, and beneficial ownership. Required for BSA/AML compliance and sanctions screening.

• EDAS Onboarding Guide Provides integration methods, daily file delivery instructions, and reconciliation requirements for EDAS programs.