GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX

SWIFT / Learning brief

FINplus and Browse

Your notes

What this means in plain language

FINplus is the SWIFTNet service that carries ISO 20022 messages for cross-border payments and securities, alongside legacy FIN. This article explains FINplus, the interactive Browse service, and FileAct's two delivery modes.

As Swift moves from its older MT (Message Type) messages to the richer ISO 20022 (International Organization for Standardization standard 20022) MX format, it needed a service to carry the new traffic. FINplus is that service. It is a SWIFTNet InterAct store-and-forward service dedicated to ISO 20022 messages, and it is the transport used for cross-border payments under CBPR+ (Cross-Border Payments and Reporting Plus) and for securities flows. It runs alongside the legacy FIN service, so institutions can support both message styles during the transition. Separately, Browse is the interactive, screen-based service: instead of system-to-system messaging, a person uses a secured browser session to reach a Swift application by hand. And FileAct, the file-transfer service, matters here because it can deliver in two modes: store-and-forward, where Swift holds a file until the receiver is ready, and real-time, where the file passes straight through. Together these describe how different kinds of Swift traffic actually flow.

Understand the full idea, step by step

When an industry changes the language its messages are written in, it cannot switch everyone overnight — some banks are ready for the new format while others still speak the old one. SWIFT's answer was not a hard cutover but a second lane running alongside the first. That lane is FINplus, and understanding it explains how ISO 20022 payments cross borders today without breaking the flows that still use the classic format.

FINplusthe store-and-forward service carrying ISO 20022 messages

FINplus is the SWIFTNet service built to carry ISO 20022 messages — the richer MX format replacing older MT messages. Technically it is an InterAct store-and-forward service: SWIFT accepts a message, holds and validates it centrally, and delivers it when the receiver is available, rather than requiring both parties online at once. It is the transport for cross-border payments under CBPR+ (Cross-Border Payments and Reporting Plus), the market practice defining how banks exchange ISO 20022 payment messages between each other, and it also carries securities flows.

Two lanes of one road

Crucially, FINplus runs in parallel with the legacy FIN service. During the migration, some counterparties are ready for MX while others still send MT, so a bank commonly operates both: FIN for the remaining classic messages, FINplus for the ISO 20022 traffic. Treating them as two lanes of the same road — rather than a hard switch — is what lets the migration happen without stranding flows. The exact scope and timelines are set by SWIFT and vary by message category, so a practitioner checks the current programme rather than assuming a single switch-over date.

Browsethe interactive, screen-based SWIFTNet service for manual tasks

Not every interaction with SWIFT is a system-to-system message. Browse lets an authorised user reach a SWIFT or partner application through a secured browser session — to consult a service, review information, or complete an administrative action that has no automated message flow. The security still comes from SWIFTNet underneath: the session is authenticated and encrypted through the same connectivity components, so a Browse user is identified as firmly as a message sender. It covers the human-in-the-loop cases that pure messaging does not.

Automated messaging vs the manual path
FIN / FINplus / FileActBrowse
How it is usedSystem-to-system, automatedA person, through a secured browser session
CarriesPayment and other structured messages, or filesScreen interactions with a SWIFT/partner application
Typical useThe bulk of live trafficOccasional configuration, monitoring, or exception handling

You may be wondering: if FINplus is ISO 20022 and so is much of InterAct, why give payments their own service at all?

Because cross-border payments need the reliability of store-and-forward and a defined market practice around them. FINplus provides an InterAct store-and-forward path shaped specifically for CBPR+ payment and securities traffic, so banks get the hold-and-deliver reliability they know from FIN, but for ISO 20022 messages. It is less a brand-new idea than the familiar store-and-forward reliability applied to the new message format — which is exactly why it can run beside FIN during the transition.

FOR NOW, REMEMBER

  • FINplus is an InterAct store-and-forward service carrying ISO 20022 (MX) messages for cross-border payments under CBPR+, and securities flows.
  • It runs in parallel with legacy FIN, so banks operate both lanes during the migration rather than switching overnight.
  • Browse is the interactive, screen-based SWIFTNet service for manual tasks that have no automated message flow.
  • Browse traffic is secured by SWIFTNet just like messaging, and is used sparingly beside the automated services.

TRY IT YOURSELF

During the ISO 20022 migration, Bank Alfa can send MX to some counterparties but still receives MT from others. What does this imply for its SWIFT setup?

Bank Alfa must switch entirely to FINplus and stop using FIN, or its MT counterparties will be unreachable.

Not this one — A hard switch would strand the counterparties still sending MT. FINplus is designed to run alongside FIN precisely so a bank does not have to abandon the classic lane before everyone is ready.

Bank Alfa operates both lanes — FIN for the remaining MT traffic and FINplus for the ISO 20022 traffic — until the migration completes.

Correct — Right. Running FIN and FINplus in parallel is the point: it lets the bank exchange MX where possible and still handle MT where needed, without breaking flows mid-migration.

Bank Alfa should handle all of this through Browse, logging in manually to convert each message.

Not this one — Browse is for manual, screen-based tasks with no automated flow — not for carrying or converting payment traffic. Automated payments run over FIN, FINplus, or FileAct, not by hand.

You have now met the network, the connectivity, the interfaces, and the messaging services. The topic behind them ties the platform together — how these services and standards fit into SWIFT's wider service portfolio.

KEEP GOING

Three things to remember

  1. 01

    FINplus is a SWIFTNet InterAct store-and-forward service that carries ISO 20022 (MX) messages for CBPR+ cross-border payments and securities.

  2. 02

    FINplus runs alongside legacy FIN so institutions can support both MT and MX messages during the migration.

  3. 03

    Browse is the interactive screen-based service, and FileAct offers both store-and-forward and real-time delivery modes.

Where you would use this

USE CASE 01

A payments team routes CBPR+ cross-border ISO 20022 messages over FINplus while keeping legacy FIN for remaining MT traffic.

USE CASE 02

An operator uses a Browse session to log into a Swift application and complete a task by hand.

USE CASE 03

An integration team chooses between FileAct store-and-forward and real-time modes based on how quickly a file must arrive.

Put the idea into a real situation

Illustrative example: a fictional bank, Coastline Bank, is migrating cross-border payments to ISO 20022. On one business day it sends 5,000 CBPR+ payment messages over FINplus and, in parallel, still sends 900 legacy MT messages over FIN for counterparties not yet ready for MX. It also transfers one end-of-day reconciliation file of 240,000 records using FileAct in store-and-forward mode, so Swift holds the file until the receiver's overnight batch window opens at 02:00. An operator separately uses a Browse session to check a delivery report by hand.

Evidence & review

REVIEWED 2026-07-13

FINplus, CBPR+ cross-border ISO 20022 payments, and the Browse service in general terms; scope and timelines are set by SWIFT and vary by message category.

What this brief simplifies: Presents FINplus as store-and-forward ISO 20022 alongside FIN and Browse as the manual path, without full migration scope, category-by-category timelines, or portal specifics.

Sources for this brief4
  1. Official requirement

    ISO 20022 Standards (Swift ISO 20022 adoption programme)Swift · FINplus as InterAct store-and-forward for ISO 20022

    Describes the Swift community's adoption of ISO 20022 for cross-border payments and reporting, including the CBPR+ migration and the end of MT-MX coexistence. · Checked 2026-07-12

    Programme milestones change over time; the coexistence period for in-scope cross-border payment instructions ended in November 2025. Check swift.com for the current timeline.

  2. Market practice

    Cross-Border Payments and Reporting Plus (CBPR+) usage guidelinesSwift (CBPR+ working group) · CBPR+ cross-border ISO 20022 payment messaging

    Defines how ISO 20022 messages (including pacs.008, pacs.009, pacs.002, pacs.004, and camt investigation messages) are used and validated for cross-border payments on the Swift network. · Checked 2026-07-12

    Full guidelines require MyStandards access; content here relies on public summaries. MT-to-CBPR+ translation rules are published on Swift's translation portal.

  3. Market practice

    Swift products and servicesSwift · Browse interactive service; parallel running of FIN and FINplus

    Describes Swift's messaging, connectivity, global payments innovation, platform, and compliance services offered to member institutions. · Checked 2026-07-13

    Used for the public overview of product details documented behind swift.com.

  4. Simplified educational illustration

    Payments Signal editorial teaching modelsPayments Signal

    This site's own simplified teaching models. · Checked 2026-07-12

    Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.

Learn this properly

Related briefs

View SWIFT archive

What a payment declares about itself — and who carries it

Every ISO 20022 payment carries two kinds of metadata: coded fields that declare what the payment is — service level, local instrument, category purpose, purpose — and an agent chain that names who moves it, bank by bank. This article reads a fictional pacs.008 field by field: what each code means, why there are four purpose-ish fields and not one, and how the instructing, previous-instructing, intermediary and reimbursement agents thread a payment across borders.

READ BRIEF

The ISO 20022 migration timeline

The move from MT to ISO 20022 is a dated schedule, not a single switch: CBPR+ coexistence from March 2023, CHIPS in 2024, Fedwire's cut-over on 14 July 2025, the end of cross-border MT coexistence in November 2025, mandatory structured or hybrid addresses from 15 November 2026, and later statement-message retirements through 2027-2028.

READ BRIEF