Guides
Learn More about Newline

Managed File Transfer (MFT) Connecting to the Bank

Managed File Transfer (MFT) Onboarding Checklist

This checklist outlines the information required to onboard Managed File Transfer (MFT) for CSV report delivery with Newline. Completing these items before onboarding helps ensure timely setup, predictable delivery behavior, and successful downstream processing.

MFT setup is required for both Sandbox and Production environments and is configured separately for each.

1. Confirm Use of Managed File Transfer (MFT)

Newline supports multiple integration methods for accessing reporting data. This checklist applies only when CSV reports will be delivered using Managed File Transfer (MFT).

☐ Confirm that MFT will be used for CSV report delivery

2. Environment Setup

MFT must be configured independently for each environment.

Please confirm setup for:

☐ Sandbox
☐ Production

The configuration steps, delivery behavior, and validation process are the same for both environments.

3. Delivery Model Selection (Push vs Pull)

Clients must select how CSV files are delivered.

Push Delivery (Preferred)

  • Newline pushes CSV files directly to a client‑provided SFTP location
  • Files are delivered automatically as soon as they are generated
  • Reduces polling, missed files, and operational overhead
  • Requires the client to provide destination connection details

Pull Delivery (By Exception)

  • Files are staged for client retrieval
  • File retention is limited
  • Clients must manage retrieval timing and avoid excessive polling
  • Requires discussion and approval during onboarding

Client decision required:

☐ Push delivery (recommended)
☐ Pull delivery (requires approval)

4. SFTP Directory and Routing Details

Clients must provide directory information where CSV files will be delivered.

Required details include:

  • Target directory path
  • Directory naming conventions
  • Whether wildcard routing is used
📘

Important — Wildcard Routing: If wildcard routing is configured, new CSV reports introduced in the future may automatically route to the same directory. Clients should ensure their systems are able to accept additional files unless alternative routing rules are established.

5. Encryption Preferences

Newline supports optional PGP encryption for secure file delivery and strongly recommends enabling encryption to protect sensitive data in transit.

Clients must confirm encryption preferences before MFT configuration begins.

Client decision required:

☐ Use PGP encryption
☐ Do not use encryption

If encryption is enabled, the client must provide:

  • A valid PGP public key

6. Reporting Configuration Alignment

CSV delivery depends on the program’s reporting configuration.

Please confirm which reporting modes and features are enabled:

☐ Intraday Reporting (interval selection required)
☐ Prior Day Reporting
☐ Client Authorization (if applicable — applies only to VRN reporting)

📘

Note: Client Authorization reports are generated only in conjunction with Virtual Reference Number (VRN) features. If VRNs are not enabled, Client Authorization reporting does not apply.

7. Delivery Cadence Expectations

Clients should review and confirm expectations for delivery timing and file behavior.

Intraday Reporting

  • Delivered at the client‑selected interval (for example, every 15 minutes or hourly)
  • All Intraday CSVs share the same cadence
  • Headers‑only files are expected during periods with no activity
  • Intraday reporting runs continuously, including weekends and holidays

Prior Day Reporting

  • Files begin generating at midnight UTC
  • Files are typically delivered within one hour
  • Delivery occurs daily, including weekends and holidays
  • Headers‑only files are expected on non‑business days

8. Retention and Re‑Delivery Expectations

Clients should be aware of the following operational considerations:

  • MFT is not intended to function as a long‑term file repository
  • Files should be ingested and stored downstream after delivery
  • For pull delivery, files may be deleted after retrieval or upon retention expiration
  • Re‑delivery may be requested if files are missing or deleted, subject to operational constraints

Exact retention and replay capabilities may vary based on delivery method and configuration.

9. Testing and Validation

Before production go‑live, clients should plan to:

  • Validate successful file delivery to the configured directory
  • Confirm the ability to ingest and process headers‑only files
  • Verify receipt across at least one complete delivery cycle
  • Review sample CSV files for structure, naming, and expected fields

Testing is typically completed during User Acceptance Testing (UAT).

10. Client Point of Contact

Please provide a primary technical contact for MFT onboarding.

This contact will be used for:

  • Connectivity coordination
  • Encryption validation (if applicable)
  • Delivery testing and confirmation

Required information:

  • Name
  • Email address
  • Role (implementation, engineering, operations)

11. Operational Notes (Important)

Clients should plan for the following behaviors:

  • CSV files may be delivered even when no transactional activity occurs
  • Reports may contain headers only; this indicates successful delivery
  • New CSV reports may be introduced over time as features are enabled
  • Clients will be notified in advance before new reports are introduced
  • Missing or malformed files should be escalated; headers‑only files should not


Updated 9 days ago