EDAS Specific File Specs
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 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)
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.
For more information on the shared or general file specs please visit our Shared Operational Resources or our General Files Specs Page.
Updated about 6 hours ago