Understanding Swift Delivery Types: Fin, InterAct, and FileAct Explained

In a previous article, we explored how a Swift message works, breaking down the structure, purpose, and flow of financial messages exchanged across the Swift network. That foundational overview helped demystify the mechanics behind this global financial communication rail. 

This article builds on that concept by diving deeper into the delivery types and file formats that underpin Swift messaging, including FIN, InterAct, and FileAct. These delivery types represent the rails through which financial messages travel, each with its own format, speed, and business use case. As you navigate the ISO 20022 migration and embrace real-time payments, understanding these rails is essential to strategic planning.

What Are Swift Delivery Types?

Swift offers three primary messaging services, often referred to as “rails.”

• FIN – Traditional, text-based messaging using MT formats, classic, or legacy protocol
• InterAct – XML based messaging using MX formats, aligned with ISO 20022
• FileAct – Bulk file transfer service supporting any format

Each rail serves a distinct purpose and supports different business use cases.

Swift FIN: The Classic Rail

FIN is Swift’s original messaging service, first introduced in 1977, and for decades it served as the backbone of global financial communication. It uses MT (message type) format and is a rigid, text-based structure. With the global shift toward ISO 20022, which is a richer and more flexible XML-based messaging standard, FIN is no longer the default for payment messaging and is considered a legacy protocol.

Key Features:

• Text-based, predefined fields
• Store-and-forward delivery model
• Common message types include MT103 (customer credit transfer) and MT940 (account statement)

Historical Use Cases:

• High volume, routine transactions
• Wire transfers, confirmations, and end-of-day reporting

Why It Still Matters:

• Many homegrown or legacy systems still only support the MT formats
• In some cases, some banks or non-bank financial institutions (NBFIs) and message categories will continue using FIN during the transition period.
• Understanding FIN is still relevant for interpreting historical data and non-payment workflows.

Swift InterAct: The New Standard Rail

InterACT is Swift’s modern messaging service designed to support MX (Message XML) formats based on the ISO 20022 standard. Designed for richer, more structured data exchange, InterAct has become the default rail for most payment messages following the global migration from legacy MT formats. Its adoption marks a pivotal shift in financial messaging, enabling enhanced data granularity, interoperability, and real-time responsiveness to meet the evolving needs of banks and NBFIs worldwide.

Key Features:

• XML-based, flexible structure (like how a webpage or email are coded)
• Real-time or synchronous messaging (like a live conversation where both parties are actively engaged at the same time)
• Supports multiple standards (e.g., CBPR+ for Swift cross-border, SEPA for Europe, LYNX in Canada)

Business Use Cases:

• Structured, enriched data improves accuracy of compliance checks and simplifies regulatory reporting.
• Standards-based formats unify payment processes across multiple scenarios—not just wires—reducing complexity for corporates.
• InterAct connects platforms efficiently, reducing manual steps and speeding up payment workflows.

U.S. Multi-Bank Reporting

Through InterAct and FileAct, corporates in the US can aggregate account information and payment instructions from multiple banks, even if they aren’t Swift members themselves, using a single interface. This streamlines reporting and simplifies treasury operations across banks and NBFIs.  

Swift FileAct: The Bulk Rail

FileAct is Swift’s secure file transfer service, designed for transmitting large volumes of data in any format. Unlike FIN and InterAct, FileAct is format-agnostic, meaning it can handle MT, MX, or proprietary files such as spreadsheets, PDFs, and custom payment instructions.

Key Features:

• Supports all file types (e.g., BAI2, TMS, PDFs)
• One connection can reach hundreds of correspondents
• Replaces point-to-point sFTP setups

Business Use Cases:

• Payroll files, daily reports, back-office data
• Efficient for batch processing and large data volumes
• Consolidated reporting files from multiple banks in a single batch

Choosing the Right Swift Rail for Your Use Case

With multiple delivery types available, selecting the appropriate Swift rail depends on the nature of the transaction, the format of the data, and the business needs of your bank or NBFI.

Here’s a quick comparison to help you decide which rail fits your needs.

This decision matrix helps align messaging strategy with operational efficiency, compliance, and modernization goals.

How Swift Rail Selection Works

Now that you have a better understanding of what each rail is used for, let’s get into who/what decides which Swift rail is used for any given message. Typically, it’s a combination of message format, business purpose, and system configuration. In most cases, the selection is automated, not manual.

Message Format Drives the Rail

As a reminder:

• MT messages are sent via FIN
• MX messages are sent via InterAct
• Files (like BAI2, XML, PDFs) are sent via FileAct

The format of the message itself determines the delivery type. If a payment instruction is structured as an MX message, it will automatically be routed through InterAct.

System Configuration

Banks and NBFIs configure their Swift infrastructure to support specific rails. These configurations are typically set during onboarding or integration and dictate how messages are routed.

Smart Routing via Technology Platforms

Many financial technology platforms and treasury systems are designed to automatically route message to the appropriate Swift rail based on message type, destination, and business rules. This ensures compliance, efficiency, and consistency – without requiring manual selection for each transaction.

Swift Messaging in Context: Why It Matters Today

The evolution of Swift messaging—from FIN to InterAct and FileAct—is more than a technical upgrade. It reflects a broader shift in the financial industry toward standardization, automation, and real-time data exchange. As global payment systems modernize, the ability to send and receive structured, interoperable messages becomes essential for:

• Regulatory compliance: ISO 20022 enables richer data for AML, KYC, and audit trails.
• Process optimization: Automated processing reduces manual intervention and errors.
• Global interoperability: A common messaging standard simplifies cross-border transactions.
• Treasury evolution: Corporates benefit from consolidated reporting and faster reconciliation.

Understanding Swift delivery types helps align your financial messaging strategy with today’s financial realities—and tomorrow’s innovations.

Frequently Asked Questions

Q. What’s the difference between MT and MX formats?
A. MT (message type) is text-based format used in FIN. MX is XML-based and used in InterAct, aligned with ISO 20022.

Q. Can FileAct transmit MX messages?
A. Yes. FileAct is format-agnostic and can transmit MT, MX, or proprietary files.

Q. Is FIN being phased out?
A. Not entirely. While payment messages have migrated to InterAct, FIN remains active for other categories like securities and foreign exchange.

Q. Is rail selection manual?
A. Not per transaction. The initial setup – choosing which railst to support and how messages are formatted – is a strategic decision made during implementation. Once configured, routing is handled automatically by the system or platform.

Choose the Right Rail for Smarter Financial Messages

As Swift messaging continues to evolve, understanding the difference between FIN, InterAct, and FileAct – and how they relate to ISO 20022 – is essential for banks and NBFIs. These delivery types are more than technical protocols; they’re strategic tools to support digital transformation, compliance, and process agility.

By choosing the right rail for the right use case, and understanding how message routing works behind the scenes, you’re in a better position for a future of smarter, faster, and more connection financial communication.

Download the Delivery Rail Decision Matrix

Learn More about Swift Delivery Types