Skip to content

Banks & FIs

Certified SWIFT connectivity without the infrastructure burden: no PKI, HSM, infrastructure maintenance, or security upgrade overhead.

Large financial institutions

Institutions running their own SWIFT estate under modernization and resilience pressure, with regulators asking harder questions about continuity.

The problem

A critical estate that is expensive to keep current

The in-house SWIFT estate is critical infrastructure with a rising bill: certification cycles, ISO 20022 migration, and resilience reviews that keep asking what happens when the primary path fails.

Capabilities in play

  • SIP-certified bureau operations. CPN operates a SWIFT-certified service bureau under the Shared Infrastructure Programme, assessed on SWIFT's cycle, not yours.
  • Dual-site, active-active resilience. Dual-site, active-active operations: a certified second path that stands ready when the primary cannot.
  • ISO 20022 transformation. MT to and from MX, any-to-any, transformed at the bureau with no internal rebuild.
  • Volume-grade monitoring and archiving. Monitoring, archiving, and investigations run at institutional volume by one accountable team.
  • 24/7 SLA-backed operations. Round-the-clock operations under SLA, with named escalation and full case history.

Use cases

  • Resilience and backup connectivity. The bureau runs as a certified second path, ready when the primary connection cannot be.
  • ISO 20022 without a migration project. Any-to-any transformation at the bureau: MT to and from MX, with no internal rebuild.
  • Volume-grade operations. Monitoring, archiving, and investigations run at institutional volume by one accountable team.

Value emphasisResilience first and modernization without the program.

Regional banks

Banks with real international volume and no ambition to run SWIFT operations as a core competence.

The problem

Specialist operations at unpredictable cost

Certified connectivity demands specialist staff, continuous compliance, and round-the-clock coverage. Run in-house, that is a fixed burden that scales badly with volume.

Capabilities in play

  • Complete outsourced bureau connectivity. Full SWIFT operations through the certified bureau, run end to end by CPN.
  • One accountable team. Investigations and exceptions handled end to end, with named people and SLAs.
  • Normalized reporting across banks. MT and camt statements normalized across counterparty banks, current and complete.
  • Bank-branded corporate services. Offer your corporate clients services powered by CPN, under your own brand.
  • Predictable operating cost. Specialist staffing, compliance cycles, and coverage move to the bureau at a predictable operating cost.

Use cases

  • Full SWIFT operations at predictable cost. Full SWIFT operations through the certified bureau at predictable cost.
  • Investigations handled end to end. Investigations and exceptions handled end to end, with named people and SLAs.
  • Client services under your brand. Offer your corporate clients services powered by CPN, under your own brand.

Value emphasisFull operations at predictable cost.

Credit unions & caisses

Member-owned institutions whose members expect international payments their infrastructure was never built to carry.

The problem

International reach without the infrastructure

Standing up SWIFT connectivity for member volumes rarely clears the business case. The choice has been to route through larger institutions or to say no to members.

Capabilities in play

  • SWIFT reach through the bureau. 12,000+ institutions reachable through one certified connection.
  • Screening and payee verification in-line. Sanctions screening and confirmation of payee applied to every member payment before release.
  • Statements and liquidity visibility. Balances and statements across counterparties, normalized and current.
  • Payment tracking via gpi. End-to-end tracking on international payments, current from send to delivery.

Use cases

  • Every institution through one certified connection. 12,000+ institutions reachable through one certified connection.
  • Member-facing international payments. International transfers as a member service, governed and tracked end to end.
  • Balances normalized across counterparties. Balances and statements across counterparties, normalized and current.

Value emphasisMember service at institutional grade.

International banks in Canada

Branches and subsidiaries of foreign institutions that need certified Canadian connectivity aligned to head-office standards.

The problem

Local operations on head-office standards

A Canadian presence needs certified local connectivity, local scheme behaviour, and reporting the head office can consume, without replicating the full home-market stack.

Capabilities in play

  • Certified local SWIFT operations. Bureau connectivity aligned to head-office standards from day one.
  • Canadian rules applied automatically. Jurisdiction policy for Canada encoded once and enforced on every payment.
  • Normalized upstream reporting. Statements and activity normalized into the formats the head office consumes.
  • Local operational support. A local team for investigations, exceptions, and changes, on your hours.

Use cases

  • Head-office standards from day one. Bureau connectivity aligned to head-office standards from day one.
  • Formats the head office consumes. Statements and activity normalized into the formats the head office consumes.
  • Canada policy encoded once. Jurisdiction policy for Canada encoded once and enforced on every payment.

Value emphasisLocal certainty with global consistency.

Correspondent banking

Correspondents carrying respondent relationships under de-risking pressure, where oversight obligations grow while margins thin.

The problem

Oversight you must prove on flows you cannot see

Regulators expect provable oversight of respondent flows. Without per-transaction evidence, the safe answer becomes exit, and another corridor thins.

Capabilities in play

  • Per-transaction screening evidence. Every screening decision written with rule, version, inputs, outcome, and timestamp.
  • Visibility across respondent flows. One view across respondent activity, current and complete.
  • Centralized exceptions and investigations. Exceptions and investigations handled in one queue, with full case history.
  • Hash-chained, tamper-evident ledger. The Evidence & Audit Ledger is hash-chained and tamper-evident, with per-access logging on evidence retrieval.

Use cases

  • Every decision written and timestamped. Every screening decision written with rule, version, inputs, outcome, and timestamp.
  • One view of respondent activity. One view across respondent activity, current and complete.
  • One queue with full case history. Exceptions and investigations handled in one queue, with full case history.
  • Provable screening at decision point. Evidence produced at the moment of decision, in a form regulators accept.

Value emphasisKeep the corridor open and prove the oversight.

Payments that violate policy are stopped before they leave, not flagged after they land.

Compliance

What comes off your team

CPN operates a SWIFT-certified (SIP) service bureau in Canada, and it runs the connection. The stack, the annual attestations, the release calendar, and the specialist cover move with it, while the evidence your regulator expects is produced per transaction.

  • SWIFT-certified bureau (SIP)

    CPN operates a SWIFT-certified service bureau under the Shared Infrastructure Programme, assessed on SWIFT's cycle, not yours.

  • The messaging stack runs here

    Messaging and communication interfaces are owned, patched, and upgraded by CPN, so the bank stops funding an always-on estate of its own.

  • No infrastructure upkeep

    No PKI to run and no HSMs to manage. Infrastructure maintenance and security upgrades sit with the bureau. Your own CSP attestation remains yours.

  • Releases and CSCF updates absorbed

    Every SWIFT release and CSCF update lands on the bureau, on SWIFT's calendar, so internal teams keep their own roadmap.

  • Specialist cover under SLA

    Certificates, release cycles, and 24/7 incident response are carried by a named team, so scarce SWIFT expertise stops being key-person risk.

  • The ISO 20022 bar cleared here

    Data quality, translation, and testing are met at the bureau, any-to-any, with no internal migration project.

  • Screening evidence per transaction

    Sanctions screening decisions written to the Evidence & Audit Ledger, per transaction, tamper-evident.

  • A regulated operator

    Registered Payment Service Provider under the Retail Payment Activities Act, supervised by the Bank of Canada. FINTRAC-registered Money Services Business.

Onboarding

Live in weeks, not months

  1. 01

    Discovery

  2. 02

    Configuration

  3. 03

    Connectivity

  4. 04

    Pilot

  5. 05

    Production

Configuration over custom builds, with 24/7 SLA-backed support from day one.

Want to measure the value this can drive for your business?

Under ten inputs. Three conservative percentages, framed as a floor, not a forecast.

Archetype preselected · In-house bank

Estimate your value

Indicative and archetype-driven.

CPN is a neutral utility, not a competitor.

CPN takes no spread. Your clients stay yours, your brand stays on the service, and the infrastructure burden moves to us.

Contact usSee the SWIFT Service Bureau

Before and after

The in-house estate collapses into one governed connection.

A bank running SWIFT itself carries all of this at once. Select a piece to see where it lands.

In house today

With CPN

One governed connection

One certified connection to SWIFT, operated under SLA by CPN. The bank keeps its clients, its brand, and its policy.

  • The messaging stackIn house today: The bank runs interfaces, middleware, and signing infrastructure for SWIFT inside its own estate. Every upgrade, every patch, and every certificate rotation is an internal project with its own change window.With CPN: Interfaces, middleware, and signing sit inside the bureau, operated under SLA. What the bank runs is a connection, not an estate, and the change calendar belongs to whoever operates it.
  • Annual attestationsIn house today: Attestation scope follows the bank because the bank operates the connection. Once a year, a team assembles evidence across the whole SWIFT estate and signs for it.With CPN: Attestation scope follows the bureau, because the bureau operates the connection. The bank's own evidence arrives per transaction instead of once a year, written as decisions are made.
  • Releases and updatesIn house today: SWIFT publishes mandatory releases on its own calendar, and the bank's roadmap is rewritten around them twice a year. Testing, cutover, and rollback planning land on the same people every time.With CPN: The release calendar belongs to the bureau. Mandatory updates are absorbed at the connection, so an internal roadmap is not rewritten around them, and the bank's teams stay on the bank's work.
  • Specialist coverIn house today: Certificates expire, cutovers run overnight, and incidents happen at three in the morning. Cover for all of it depends on a handful of specialists the bank has to hire, keep, and replace.With CPN: Certificates, cutovers, and overnight incidents become one team's standing duty, under SLA, with named escalation. The specialist cover is the bureau's to maintain, not the bank's to staff.
  • The ISO 20022 barIn house today: ISO 20022 is a translation and testing programme the bank has to run itself, across every system that reads a SWIFT message. The migration deadline becomes an internal project with its own budget.With CPN: Translation and testing happen at the connection. MT and MX both arrive in the format your systems already read, so the migration is absorbed at the bureau rather than scheduled inside the bank.

In house today

01The messaging stack

Interfaces, middleware, and signing sit inside the bureau. What the bank operates is a connection, not an estate.

02Annual attestations

Attestation scope follows whoever operates the connection. Your evidence arrives per transaction instead of once a year.

03Releases and updates

The release calendar belongs to the bureau, so an internal roadmap is not rewritten around it twice a year.

04Specialist cover

Certificates, cutovers, and overnight incidents become one team's standing duty, under SLA, with named escalation.

05The ISO 20022 bar

Translation and testing happen at the connection. MT and MX both arrive in the format your systems already read.

With CPN

One governed connection

One certified connection to SWIFT, operated under SLA by CPN. The bank keeps its clients, its brand, and its policy.