Skip to content

SWIFT Service Bureau

Direct access to SWIFT without the infrastructure overhead.

Independent, bank-grade access. You register and hold your own SWIFT BIC, CPN operates the certified connection, and payments, balances, and statements flow across all your banks.

SWIFT-certified bureau operated by CPN
SIP
institutions reachable through one connection
12,000+
PKI, HSM, infrastructure maintenance, or security upgrade burden on your team
0

Why SWIFT

One network every institution already reads

Your banks already speak this standard. The bureau is how you reach it without building it.

  • 01

    One message standard read everywhere

    MT and ISO 20022 are understood by every institution on the network, so one format carries an instruction to any bank you deal with.

  • 02

    A single secure channel

    One certified connection replaces thousands of bilateral integrations, each of which would carry its own keys, formats, and operating burden.

  • 03

    Member owned and cooperatively governed

    The network is owned by its members and governed cooperatively under strict oversight, so no single vendor sets the terms of access.

  • 04

    12,000+ institutions on one network

    Reach is what makes a single connection enough. Adding a bank becomes a BIC on an existing channel rather than a build.

What the bureau runs

The connection, and everything behind it

One certified connection carries the full SWIFT service set. Each item below is operated by CPN so it is not operated by you.

SWIFT

CPN Service Bureau

One certified connection. Everything listed here runs behind it, operated by CPN.

  1. 01

    Redundant infrastructure

    Robust, fully redundant infrastructure managed by SWIFT-certified experts.

  2. 02

    FIN and InterAct messaging

    FIN and InterAct messaging: payments, securities, FX, trade finance and treasury messages, including ISO 20022 compliant flows.

  3. 03

    FileAct file exchange

    FileAct: automated, secure file exchange for bulk payments, statements and reporting.

  4. 04

    RMA

    Relationship Management Application (RMA): manage and control your correspondent relationships.

  5. 05

    WebAccess and Micro-gateway

    SWIFT WebAccess (Browse) and Micro-gateway: governed access into additional SWIFT services.

  6. 06

    Fully managed operations

    Fully managed operations: security, compliance, maintenance and monitoring, end to end.

Bureau architecture

One connection drawn end to end

Everything the bureau runs sits between your back office and the network. Select a component to read what it does.

01Your side

02Inside the bureau

03Out to the network

Your side

Back office

Your ERP or core banking system creates the instruction and receives the outcome. Nothing about it changes in order to reach the network.

01Your side02
Back office
Your ERP or core banking system creates the instruction and receives the outcome. Nothing about it changes in order to reach the network.
Operators
Treasury and operations staff work in the systems they already use, reaching the bureau through controlled, named access.
02Encrypted connection
Encrypted connection
A private encrypted link from your environment into the bureau. Traffic never crosses the open internet unprotected.
03Inside the bureau05
Messaging interface
The certified interface that creates, validates, and queues messages, applying the release controls your policy sets before anything moves.
Communication interface
The layer that hands messages to the network and takes delivery of everything coming back, in order and under acknowledgement.
Connectors
Middleware, secure file transfer, and API endpoints that meet your systems in the formats they already produce.
API micro-gateway
A narrow API surface for the calls your systems make most: submit a payment, fetch a balance, read a status.
HSM-protected signing
Hardware security modules hold the PKI certificates and sign every message, so no key material ever sits with your team.
04Four resilient connections
Four resilient connections
Four private connections of equal capacity carry traffic to SWIFT, so no single link is the one that has to hold.
05Out to the network02
SWIFT
The network itself, carrying your traffic under your own BIC across the connection CPN keeps certified.
12,000+ institutions
Every connected institution is reachable through the same channel, which is what turns a new banking relationship into a BIC rather than a project.

Access models

Three ways to reach SWIFT

Bank channels, direct membership, or a certified bureau: the difference is who carries the infrastructure and who keeps the independence.

01Through your bank
Reach
One bank's network, one portal and format per bank
Your BIC
None: payments travel under your bank's identity
Infrastructure
None to run, but every bank is a separate integration
Attestation
None required
Onboarding
Each new bank means another portal, another key, another format
Deployment
Whatever your bank offers, on your bank's terms
Operations
Your bank's queue, on your bank's timeline
02Direct SWIFT membership
Reach
The full network, if you build and staff for it
Your BIC
Yours, with everything operating it implies
Infrastructure
PKI, HSM, connectivity, and upgrades on your team
Attestation
Annual CSP attestation carried by your organization
Onboarding
Every new BIC and counterparty is a project on your plan
Deployment
Yours to design, build, and keep certified
Operations
A round-the-clock operations function you staff yourself
03CPN Service BureauSIP-certified bureau
Reach
12,000+ institutions through one connection
Your BIC
Yours: CPN operates the certified connection behind it
Infrastructure
Run by CPN in certified facilities
Attestation
Your own CSP attestation, on infrastructure CPN maintains and upgrades
Onboarding
New banks, BICs, and counterparties in weeks rather than months
Deployment
Dedicated, shared, cloud, or on-premises
Operations
Monitoring, archiving, and a team you can call

Through your bank

Reach
One bank's network, one portal and format per bank
Your BIC
None: payments travel under your bank's identity
Infrastructure
None to run, but every bank is a separate integration
Attestation
None required
Onboarding
Each new bank means another portal, another key, another format
Deployment
Whatever your bank offers, on your bank's terms
Operations
Your bank's queue, on your bank's timeline

Direct SWIFT membership

Reach
The full network, if you build and staff for it
Your BIC
Yours, with everything operating it implies
Infrastructure
PKI, HSM, connectivity, and upgrades on your team
Attestation
Annual CSP attestation carried by your organization
Onboarding
Every new BIC and counterparty is a project on your plan
Deployment
Yours to design, build, and keep certified
Operations
A round-the-clock operations function you staff yourself

SIP-certified bureau

CPN Service Bureau

Reach
12,000+ institutions through one connection
Your BIC
Yours: CPN operates the certified connection behind it
Infrastructure
Run by CPN in certified facilities
Attestation
Your own CSP attestation, on infrastructure CPN maintains and upgrades
Onboarding
New banks, BICs, and counterparties in weeks rather than months
Deployment
Dedicated, shared, cloud, or on-premises
Operations
Monitoring, archiving, and a team you can call

Already on a service bureau?

Transitions are quiet by design. Your BIC, message flows, and operating procedures carry over without interruption, cutover is planned around your payment calendar, and the team answering today keeps answering.

Reach the whole network. Run none of the infrastructure.