Overview

Welcome to the onboarding guide for Newline’s EDAS. This guide outlines the key steps, technical requirements, and integration options to help you successfully launch deposit and payment capabilities within your platform.

Each section corresponds to a key milestone in your implementation journey.

Onboarding Phases

Integration
Required Data Files
Reconciliation & Monitoring
Authentication & Security
Payment Rails
Testing & UAT
Support

1. Integration

Begin by gathering integration requirements and selecting your method (MFT or API). Proceed with Data Transmission Setup and Connectivity Testing to validate secure communication with Fifth Third Bank.

Integration Method	Description	Key Capabilities	More Info
Managed File Transfer	Utilize the bank’s managed file transfer system to send and receive files securely.	Send files for transaction monitoring(accounts, transactions, beneficial owner, and business) reconciliation and batch payments securely to the bank. Receive omnibus account balance files.	MFT Guide
API	Real-time access via RESTful APIs.	Payment initiation; Reporting	API Reference

Connecting to Newline Using Managed File Transfer (MFT)

MFT Capabilities

Our MFT platform ensures secure and efficient data transmission and supports the following protocols:

FTP: Standard protocol for internet file transmission.
AS2 Over FTPS: Uses SMIME and HTTP/HTTPS for secure transport.
Connect: Optimized for high-volume peer-to-peer transfers.
Fifth Third Direct HTTPS: Secure data transmission via HTTPS.
File Encryption: PGP encryption for secure file transmission.

2. Required Data Files

Configure and validate all required data files (EDAS-specific and common specs). This step ensures readiness for reconciliation and compliance.

To successfully launch EDAS, you’ll need to integrate several key components that work together to ensure secure data exchange, accurate reconciliation, and regulatory compliance.

Reconciliation Specs

Once integration methods are established, EDAS requires specific data files to be submitted regularly to support account and transaction reconciliation.

EDAS Specific File Specs

These files are unique to EDAS and must be submitted daily to capture core financial and identity data:

Payment Transactions: Captures financial activity at the sub-ledger level, including inbound and outbound payments such as Wire, ACH, and Real-Time Payments. To learn more about Payment Transactions, view the Payment Transactions guide.
Person Entity:Represents an individual with legal identity, used for compliance, identity verification, and account association. To learn more about Person Entity, view the Person guide.

Common File Specs

These files are shared across EDAS and Card Issuing products and provide foundational account and business data:

Accounts: Defines deposit accounts held by individuals or businesses, including type, status, and balance. To learn more about Accounts, view the Accounts guide.
Business: Represents a registered organization that holds deposit accounts, including legal and registration details. To learn more about Business, view the Business guide.
Beneficial Ownership: Details individuals with ownership or control over a business for AML compliance. To learn more about Beneficial Ownership, view the Beneficial Ownership guide.

3. Reconciliation & Monitoring

Align internal systems with reconciliation specs and monitoring requirements. This phase may involve Development/Configuration of your platform to support ongoing data exchange.

Account Reconciliation: Account reconciliation outlines the procedures for aligning your internal records to ensure accurate financial reporting. For more information, please refer to the Account Reconciliation Guide.

Transaction Monitoring & Sanctions Screening: Details the requirements for anti-money laundering (AML) transaction monitoring, and sanctions screening. For more information, please refer to the Transaction Monitoring and Sanctions Screening Integration Guide. Note: This shared data model is distinct from the one used by Newline’s APIs.

4. Authentication & Security

Set up API credentials and implement token-based authentication. This step is critical before initiating payment flows or accessing secure endpoints.

API Credentials:

Program UID and HMAC Key provided by Newline
Required for token generation

Authentication Flow

Use POST /auth to obtain and refresh access tokens for secure API authentication.

For more information on token generation and credential setup, refer to the Authentication Guide for Sandbox and Production.

5. Payment Rails

Configure supported payment types (ACH, Wire, Instant Payments) based on your use case. Ensure all rails are tested and mapped to your internal systems.

Payment rails are the infrastructure that enables the movement of funds between accounts. EDAS supports multiple payment types:

ACH (Automated Clearing House): Supports batch-based electronic payments, including direct deposits and bill payments. Ideal for scheduled, low-cost transactions. For more information visit ACH Guide
Wire Transfers: Facilitates high-value, time-sensitive payments with same-day settlement. Commonly used for business-to-business transactions. For more information visit Wire Transfers Guide
Instant Payments: Enables real-time fund transfers with immediate availability. Suitable for use cases requiring fast settlement and confirmation. For more information visit Instant Payments Guide

For more information and detailed steps, please refer to the Payment Rails Setup resource.

6. Testing & UAT

Conduct Connectivity Testing and User Acceptance Testing (UAT) using Newline’s sandbox. Validate production files and simulate error scenarios before launch.

Newline provides a sandbox environment for testing. Refer to the Testing Scenarios Guide.

7. Support

After production launch, conduct a Post-Production Review and transition to Commercial Services. Use support channels for ongoing troubleshooting and maintenance.

Need help or personalized support? Email: [email protected]

Additional resources:

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 Specific File Specs Details file formats unique to the Embedded Deposit Account Solutions (EDAS) product, including payment transactions and person entities.
Card Issuing Specific File Specs Covers specifications for cardholder data, card metadata, and posted transactions specific to the Card Issuing Sponsorship program.