Overview

The ETAS API Integration enables clients to initiate, manage, and monitor payment activity using Newline's API platform. This integration serves as the primary connection point between your platform and ETAS payment services. Clients use the API integration to submit payment instructions, retrieve transaction information, and support embedded payment experiences within their applications. ETAS utilizes the same authentication and API framework currently used across Newline services.

Before You Begin

Before starting API development, confirm that:

• The ETAS onboarding process has been initiated.
• Required agreements have been executed.
• Technical contacts have been identified.
• Payment rails have been selected.
• Development resources have been assigned.
• Access to Newline API documentation has been provided.

Integration Workflow

A typical API implementation follows this sequence:
Step 1: Configure Authentication: Establish secure access to Newline APIs.
Step 2: Connect to the Sandbox Environment: Validate connectivity and credentials.
Step 3: Implement Payment Workflows: Configure payment rails and transaction processing.
Step 4: Complete Testing: Validate all payment and operational workflows.
Step 5: Production Deployment: Move approved integrations into production.

Authentication

Authentication requirements for ETAS are consistent with existing Newline APIs. During onboarding, implementation teams will provide the credentials and information necessary to access the platform.

Prerequisites

Before configuring authentication:

• Receive API credentials.
• Securely store credentials.
• Establish certificate and secret management processes.
• Review security requirements.

Authentication Setup

Authentication implementation should include:

• Credential configuration
• Access token generation
• Token renewal handling
• Authorization validation
• Error handling for expired or invalid credentials

Validation Checklist

Confirm that you can:

• Authenticate successfully.
• Retrieve access tokens.
• Connect to sandbox endpoints.
• Receive authorized responses.
• Handle authentication failures appropriately.

For more information please visit our Authentication Guide.

Payment Rails

Payment rail configuration is the primary implementation activity after authentication has been completed. ETAS supports the following payment services.

ACH

ACH services support:

• Inbound ACH transactions
• Outbound ACH transactions
• Standard ACH
• Same Day ACH (where enabled)

For more information please visit our ACH API Reference Page

Typical use cases include:

• Vendor payments
• Payroll payments
• Business disbursements
• Funding transactions

Implementation Tasks

• Configure ACH workflows.
• Validate request structures.
• Test inbound and outbound scenarios.
• Validate transaction status responses.

Wire Transfers

Wire services support domestic payment activity.

Implementation Tasks

• Configure wire payment workflows.
• Validate wire payment requests.
• Process wire transaction responses.
• Test wire status monitoring.

For more information please visit our Wire API Reference Page

Book Transfers

Book Transfers support movement of funds between Fifth Third accounts.

Implementation Tasks

• Configure transfer workflows.
• Validate transaction processing.
• Test balance movement scenarios.
• Verify transaction status reporting.

For more information please visit our Book Transfers API Reference Page

Testing

All API integrations must successfully complete testing before production deployment. For more information please visit our Sandbox and Testing Errors Guide.

Connectivity Testing

Validate:

• Credential configuration
• Authentication
• Endpoint access
• Request/response handling

Payment Rail Testing

Validate each payment rail being implemented. Testing should include:

• Successful transactions
• Validation failures
• Error responses
• Status updates
• Transaction lifecycle events

Reconciliation Testing

Verify that:

• Ledger balances reconcile properly.
• Transaction activity matches reporting outputs.
• API responses align with expected results.
• Operational controls function correctly.

User Acceptance Testing (UAT)

Prior to production approval, clients should confirm:

• Business requirements are met.
• Workflows perform as expected.
• Operational procedures are documented.
• Support teams are prepared for production use.

Production Readiness

Before go-live:

Security

• Authentication validated
• Credentials secured
• Access controls implemented
• Monitoring configured

Functionality

• Payment rails tested
• Reconciliation validated
• Error handling verified
• Reporting reviewed

Operations

• Support procedures documented
• Escalation contacts identified
• Production deployment approved

Support

Your implementation team will support the API onboarding process from initial setup through production deployment. During implementation, clients typically receive documentation, review technical requirements, and participate in walkthrough sessions prior to testing activities.

Support During Implementation

Implementation support includes:

• Authentication assistance
• Connectivity troubleshooting
• Payment workflow reviews
• Testing coordination
• Reconciliation validation
• Production readiness reviews

When to Contact Support

Contact your implementation team if:

• Authentication requests are failing.
• API responses differ from expected behavior.
• Payment testing cannot be completed.
• Reconciliation variances are identified.
• Production deployment questions arise.

Next Steps

Once API configuration has been completed:

1. Finalize payment rail testing.
2. Complete reconciliation validation.
3. Obtain production approval.
4. Continue with the Batch File Integration Guide to complete the DataMart integration requirements.