EDAS Onboarding Guide

Overview

Welcome to the onboarding guide for Newline’s EDAS. It 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

  1. Integration
  2. Authentication
  3. Payment Rails
  4. Testing & UAT
  5. Support

1. Integration

EDAS requires two integration methods; Managed File Transfer and API.

Integration MethodDescriptionKey CapabilitiesMore Info
Managed File TransferUtilize 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
APIReal-time access via RESTful APIs.Payment initiation; ReportingAPI Reference

Connecting to Newline Using Managed File Transfer (MFT)

MFT Capabilities

Our MFT platform oversees secure and efficient data transmission with support for 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.

Implementation Steps

The implementation process includes:

  • Data Gathering/Requirements: Configure your product or service.
  • Data Transmission Setup and Testing: Establish and test connectivity with Fifth Third Bank.
  • Development/Configuration: Configure product requirements.
  • Connectivity Testing: Validate customer-bank connectivity.
  • User Acceptance Testing (UAT): Test production files for accuracy.
  • Production: Move the project to production.
  • Post-Production Review: Final review and handoff to Commercial Services.

2. Authentication & Security

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, which are used to authenticate API requests securely.
For more information on token generation and credential setup, refer to the Authentication Guide for Sandbox and Production.

3. Payment Rails

Payment rails are the infrastructure used to support different types. Newline supports multiple payment types.

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

4. Testing & UAT

Newline provides a Sandbox environment for testing. For detailed testing instructions, including how to simulate failures and validate flows, refer to the Testing Scenarios Guide.

5. Support

Need help or more personalized support? Please reach out to
[email protected]
For troubleshooting and FAQs, visit the Support and Error Guides.