This Changelog post outlines the updates made to the Newline Platform in August 2026.

What We Improved

This changelog highlights the enhancements, new capabilities, and documentation releases introduced to the Newline Platform during August 2026. These updates are designed to improve payment functionality, strengthen alignment with industry standards, and provide developers with the resources needed to accelerate implementation and onboarding. From ISO 20022 wire-readiness enhancements and comprehensive ETAS documentation to upcoming RTP payment capabilities, our focus remains on delivering a more flexible, scalable, and intuitive experience for our clients and partners.

Purpose of Payment Documentation Update

To support an upcoming enhancement to RTP payment initiation, we published documentation describing support for an optional purpose_of_payment field for outgoing RTP transfers. The feature has been developed and is currently undergoing final readiness activities before general availability.

Documentation is now available to help clients prepare their integrations ahead of the planned September release.

• Transfers API Documentation Update: Added documentation for the optional purpose_of_payment field that will be supported within the Instant Payment object when creating RTP transfers.
• Validated RTP Purpose Codes: Documentation includes the approved RTP Purpose of Payment codes that will be accepted once the feature is enabled.
• RTP Network Mapping: Documentation outlines how supported values will map to the RTP network purposeOfPaymentCode field.
• Validation Behavior: Documentation describes validation requirements and expected error responses for unsupported values.
• Backward Compatibility: The upcoming enhancement is fully backward compatible and will remain optional for existing integrations.
• Transaction Retrieval Support: Documentation includes response examples showing how the purpose_of_payment field will be returned through:
  • GET /Transfers
  • GET /Transactions
• Planned Availability: The feature is complete and currently controlled through a feature flag while final RTP readiness activities are being completed. General availability is planned for September 2026.
• Transfers API Reference Guide Update: Added documentation to the Transfers API Reference Guide describing supported Purpose of Payment values, definitions, and implementation guidance so clients can prepare for adoption upon release.

ISO 20022 Structured Wire Address Enablement

During August 2026, structured wire address support was enabled in the Sandbox environment for all customers. This milestone allows clients to begin testing ISO 20022-compliant wire address formats as part of their migration and implementation planning efforts.

• Sandbox Availability: Enabled structured wire-address support for all Sandbox customers.
• ISO 20022 Readiness: Supports testing of structured address formats aligned with ISO 20022 requirements.
• Migration Flexibility: Continues to support both structured and unstructured address formats during transition activities.
• Expanded Testing Capability: Allows clients to validate wire origination, receipt, and reporting workflows using structured address data.
• Developer Enablement: Complements the ISO 20022 documentation released previously by providing a live Sandbox environment for implementation testing.

New Developer Documentation

Published the initial set of implementation and onboarding resources for the Embedded Transaction Account Solution (ETAS). These guides provide comprehensive support for clients integrating with ETAS, including onboarding requirements, API and file-based integration workflows, testing and production readiness activities, file specifications, troubleshooting guidance, and frequently asked questions. Together, these materials establish the foundational documentation framework for ETAS implementations and future product enhancements.

ETAS Quick Start Onboarding Guide: Provides a high-level overview of ETAS, implementation prerequisites, client responsibilities, onboarding phases, and the overall implementation journey. This serves as the primary entry point for all ETAS integrations.

ETAS API Integration Guide: Walks developers through API onboarding, authentication setup, supported payment rails, testing requirements, production readiness activities, and available support resources.

ETAS Batch File Integration Guide: Covers the file-based integration process, including SFTP setup, business and transaction file requirements, testing procedures, reconciliation activities, and production onboarding considerations.

ETAS File Specifications Overview: Serves as the landing page for ETAS file-based integrations, providing an overview of the Business and Transaction file specifications, their intended uses, and the supporting resources needed to generate, validate, and transmit files to the Newline DataMart environment. It also directs implementation teams to the appropriate specification document based on their integration needs.

ETAS File Specs (Downloadable): Defines the purpose, structure, validation requirements, submission process, and field-level requirements for the Business File transmitted to Newline DataMart.

ETAS Frequently Asked Questions (FAQ): Provides answers to common onboarding, integration, testing, reconciliation, and support questions that clients may encounter during implementation.

ETAS Troubleshooting Guide: Contains troubleshooting steps for common authentication, API connectivity, payment processing, SFTP, file validation, reconciliation, and production readiness issues.

What We Fixed

• No bug fixes were required this month.

Why It Matters

The August 2026 updates deliver meaningful improvements for both payment operations and developer enablement.

Documentation published this month for the upcoming purpose_of_payment enhancement helps organizations prepare for support of standardized RTP payment purpose information. Once enabled, the feature will allow clients to include RTP Purpose of Payment codes when originating Instant Payments, providing richer transaction context, improving interoperability with RTP messaging standards, and supporting payment categorization and reporting requirements. Publishing the documentation ahead of release allows implementation teams time to prepare integrations before the feature becomes generally available.

The publication of the initial ETAS implementation and onboarding documentation establishes a centralized foundation for clients integrating with the Embedded Transaction Account Solution. These resources streamline implementation planning, reduce onboarding complexity, provide clear technical guidance, and support successful production readiness across both API and file-based integration models.

In addition, enabling ISO 20022 structured wire-address support in Sandbox provides customers with an opportunity to begin validating migration scenarios and testing structured wire-payment workflows ahead of broader adoption. This milestone moves Newline closer to full ISO 20022 readiness while reducing implementation risk for clients.

The absence of bug fixes this month also reflects the stability of the platform during this release cycle.

Together, these enhancements reinforce Newline's commitment to delivering modern payment capabilities, robust developer resources, and a seamless integration experience that helps clients bring innovative financial solutions to market more efficiently. For questions or further details, please contact Jennifer Morales.