Skip to content

Corporates & Treasury

One connection replaces every portal. Policy enforced before money moves, not investigated after.

Multinational & multi-entity

Treasury groups running hundreds of legal entities across dozens of banking relationships, in many currencies and jurisdictions.

The problem

Fragmented visibility and inconsistent control

Every bank brings its own portal, format, and cutoffs. Visibility fragments across entities, intercompany settlement drags over external rails, and controls drift jurisdiction by jurisdiction. The group carries one accountability with dozens of authorities.

Capabilities in play

  • One connection to every bank. One connection to all your banks at once, through the SWIFT Service Bureau reaching 12,000+ institutions.
  • Jurisdiction-aware Policy Engine. Limits, approvals, and screening configured once in the Policy Engine and enforced per jurisdiction, on every rail.
  • Consolidated balances and statements. Balances and statements across every bank and entity, normalized and current, in one view.
  • Private domain for intercompany flows. Group entities join a private settlement domain as verified members: positions net inside it and settle instantly, on-us.
  • Evidence & Audit Ledger group-wide. Every decision writes rule, version, inputs, outcome, and timestamp: one audit trail across every entity.

Use cases

  • Global payment factory. One governed channel for every entity, any format in, one view across the group.
  • Positions across all banks in one view. Positions across all banks, normalized and current, in one place.
  • Intercompany netting and settlement. Group entities settle on a private domain: positions net inside it, settlement is instant and on-us, and external-rail usage compresses to the net.
  • Jurisdiction-aware policy. One rulebook, applied per jurisdiction: limits, approvals, and screening set once and enforced everywhere.

Use-case gallery

Global payment factory

Situation today
Every entity pays through its own banks, portals, and formats. Treasury sees the results after the fact, and controls differ by country.
How CPN does it
Every entity originates through one governed channel, in any format. The Control Fabric applies one policy set, jurisdiction by jurisdiction, and every payment lands in one view.
Outcome
One channel, one rulebook, and one view across the group. Exceptions surface before money moves, not after.

Use-case gallery

Intercompany netting

Situation today
Entities settle with each other over external rails, paying external fees and FX on internal money.
How CPN does it
Group entities join a private settlement domain as KYB-verified members. Intercompany positions net inside the domain and settle on-us, instantly, with rich data attached.
Outcome
External-rail usage compresses to the net position. Rich data reconciles both sides automatically, and CPN takes no spread inside the network.

Value emphasisGovernance first and Economics through netting.

Commodity trading

Trading desks moving high-value payments on tight cutoffs to sanctions-sensitive counterparties around the world.

The problem

A frozen payment breaks a trade

Screening happens at the bank, after funds are committed. A false positive freezes the payment mid-flight, the cutoff passes, and the trade breaks while investigation drags on. Cutoffs and screening exposure rule the day.

Capabilities in play

  • Screening before release. Sanctions and PEP screening runs before release. A breach is not flagged. It does not proceed.
  • Confirmation of payee. Confirmation of payee on new counterparties: name and account checked before the first payment moves.
  • Warehouse and schedule. Cutoff handling and timed release: payments hold until their window and route on the path that settles inside it.
  • Trade finance messaging. LCs, guarantees, and collections carried over the bureau alongside your payment flows: FIN, InterAct, FileAct.
  • Evidence written per decision. The Evidence & Audit Ledger records every screening decision at the moment it is made: rule, version, inputs, outcome, timestamp.

Use cases

  • Sanctions-safe payments. Screened before send, so only clean payments leave. A breach is not flagged. It does not proceed.
  • Payee verification on new counterparties. Name and account confirmed before the first payment moves, cutting fraud and mispayment at source.
  • Cutoff-aware routing. Routing that knows every rail's cutoffs and picks the path that settles inside the window.
  • LCs and guarantees over the bureau. LCs, guarantees, and collections carried through the bureau alongside your payment flows.

Use-case gallery

Sanctions-safe payments

Situation today
Compliance is checked at the bank, after funds are committed. A hit means a frozen payment, a broken trade, and weeks of investigation.
How CPN does it
CPN screens every payment against sanctions, PEP, and risk lists before it leaves. A breach is not flagged. It does not proceed.
Outcome
Only clean payments leave. Screening evidence is written per transaction, at the moment of decision.

Value emphasisGovernance with settlement certainty as the product.

Supply chain & manufacturing

Manufacturers and distributors paying thousands of suppliers on recurring runs, with reconciliation load growing at the pace of the supplier base.

The problem

Onboarding risk and manual reconciliation at scale

Every new supplier is an onboarding risk, and every payment run ends in manual matching. The data that would reconcile both sides exists, it just does not travel with the payment.

Capabilities in play

  • Extended KYB at onboarding. Extended KYB on every supplier at onboarding, with expiry and renewal monitored in the Trust Vault.
  • Private domain for the supplier network. Suppliers transact as KYB'd members inside a private settlement domain you define and govern.
  • Rich data travels with the payment. The rich data layer carries PO, invoice, and line items with every transfer for two-sided straight-through processing.
  • Reconciliation automation. Reconciliation automation on both sides: payments arrive carrying the references that match them.
  • Programmable settlement timing. Release tied to your business rules: delivery confirmation, terms, or cash position.

Use cases

  • Supplier network as a private domain. Suppliers join as KYB'd members and transact by CPN ID inside a domain you govern.
  • Rich data payloads. PO, invoice, and line items carried with every transfer for two-sided straight-through processing.
  • Exceptions become the exception. Payments arrive carrying the references that match them, so exceptions become the exception.
  • Dynamic settlement timing. Release tied to your business rules: delivery confirmation, terms, or cash position.

Value emphasisEconomics growing into Network Power.

High-growth and mid-market multi-bank treasury

Treasuries that outgrew the single-bank portal but have no appetite for running SWIFT infrastructure or hiring a treasury technology team.

The problem

Portal sprawl without a technology team

Each new bank adds another portal, another token, another format. The alternatives have been heavy: build SWIFT connectivity in-house, or live with the sprawl and the control gaps it hides.

Capabilities in play

  • Bureau access with no attestation burden. Certified bureau access with no PKI, no HSM, and no infrastructure maintenance or security upgrade burden on your team.
  • ERP and TMS integration. Payments flow from the systems you already run, with Ripple Treasury available where no TMS exists.
  • Consolidated view across every bank. Balances, statements, and payment status across every bank, normalized and current, in one view.
  • A team you can call. Named people for changes, investigations, exceptions, and unique requests.
  • A growth path. A growth path into digital corridors and private domains, when the business asks for it.

Use cases

  • Bureau access without the overhead. Certified SWIFT reach with no PKI, no HSM, and no infrastructure maintenance or security upgrade burden on your team.
  • Payments from systems you already run. Payments flow from the systems you already run. Ripple Treasury is available where no TMS exists.
  • Named people for exceptions and changes. Named people for changes, investigations, exceptions, and unique requests.
  • Extend to corridors and private domains. Start with governed bank connectivity. Extend to digital corridors and private domains when the business asks.

Value emphasisGovernance now and the path later.

You own the risk. Not the rail.

Compliance

Compliance carried by the platform

Screening, verification, and evidence are platform functions, applied to every payment before it moves. Your policy is enforced in-line, and the audit trail writes itself.

  • Screened before send

    Sanctions, PEP, and risk-list screening runs before release, so payments never freeze downstream.

  • Payee confirmed

    Confirmation of payee verifies name and account match before execution, cutting fraud and mispayment at source.

  • Evidence on every decision

    The Evidence & Audit Ledger records rule, version, inputs, outcome, and timestamp: audit committee readiness by default.

  • 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 across FX cost, liquidity requirement, and payment operations, framed as a floor, not a forecast.

Archetype preselected · Multinational treasury

Estimate your value

Indicative and archetype-driven.

Set your rules once. CPN applies them to every transaction, on every rail.

Contact usExplore the platform

Before and after

The bank-by-bank setup collapses into one governed connection.

A multi-bank treasury keeps a separate arrangement with every bank it uses. Select a piece to see what replaces it.

Today

With CPN

One governed connection

One channel to every bank, with policy applied before release and one audit trail behind every payment.

  • A portal to log intoToday: Every bank comes with its own portal, and each one has its own login, its own screens, and its own idea of how a payment is entered. A treasury with a dozen banks logs into a dozen systems to see one position.With CPN: Every account is reachable through one governed channel, so logging in stops being how a payment gets made. Instructions originate once, in one place, and reach every bank from there.
  • A security key to holdToday: Each bank issues its own security key or token, and each one has to be held, renewed, and handed over when people change roles. Authority to release a payment lives in as many places as there are banks.With CPN: One set of credentials and one approval model cover every bank. Authority is granted and withdrawn in a single place, and the audit trail shows who released what, wherever it went.
  • A statement format to parseToday: Statements arrive in a different format from every bank, and month-end reconciliation is a manual effort across teams and spreadsheets. The same balance means something slightly different depending on who reported it.With CPN: Every account feeds one normalized statement stream, reconciled automatically, with exceptions surfaced the moment they occur. MT and camt arrive in the shape your systems already read.
  • A spreadsheet as the recordToday: Positions, payment status, and approvals live in a workbook because nowhere else holds all of them at once. The spreadsheet is the record, and it is only as current as the last person who updated it.With CPN: Positions and status come from the connection itself, current and normalized across every bank. The workbook stops being the only place the truth lives, and the audit trail is written as decisions happen.
  • A host-to-host build to maintainToday: Every host-to-host connection is a build your team maintains: format mapping, certificate rotation, cutover testing, and the overnight incident when a bank changes something. Each new bank adds another one.With CPN: Format mapping, certificate management, and day-to-day operations sit with the bureau, not in your integration backlog. Adding a bank becomes a BIC on an existing channel rather than a project.

Today

01A portal to log into

Every account is reachable through one channel, so logging in stops being how a payment gets made.

02A security key to hold

One set of credentials and one approval model, with authority granted and withdrawn in a single place.

03A statement format to parse

MT and camt statements arrive normalized across every bank, current, in one view.

04A spreadsheet as the record

Positions and status come from the connection itself, so the workbook stops being the only place the truth lives.

05A host-to-host build to maintain

Format mapping, certificate management, and day-to-day operations sit with the bureau, not in your integration backlog.

With CPN

One governed connection

One channel to every bank, with policy applied before release and one audit trail behind every payment.