---
title: "Banks & PSPs"
url: "https://dev.ionova.ai/solutions/banks"
image: "https://dev.ionova.ai/_og/d/c_Ocean.takumi,title_~QmFua3MgJiBQU1Bz,props_eyJ0aGVtZSI6eyJtb2RlIjoibGlnaHQiLCJjb2xvcnMiOnsicHJpbWFyeSI6IiMyRTUwOTAifX19,p_Ii9zb2x1dGlvbnMvYmFua3Mi,s_ttC8R4TtAuWRnn0u.png"
---

[Docs](https://dev.ionova.ai/) › [Solutions](https://dev.ionova.ai/solutions) › Banks & PSPs

Provider & rails

# Two businesses, _one engine_.

Keep your own outbound `pacs.008` compliant at the network boundary — and offer the address-quality fix to the corporate clients and correspondents who send through you. One engine, two placements.

**The hinge —** EPC §3.2 forbids you from silently correcting a client's counterparty address. So you run two things on one engine: an **In-Flight** correction gate on your own wire, and an At-Source white-label **PreCheck** your clients call before they submit.

Where you call _ARS_Both sides of the line.

|                |                                                                                  |
| :------------- | :------------------------------------------------------------------------------- |
| Placement      | In-Flight (your pacs) + At-Source (client PreCheck)                              |
| Scope          | Message (pacs.008 / pacs.009) + Party Address (client checks)                    |
| Channel preset | swift-cbpr-in (gate) · cop-verify (PreCheck)                                     |
| Pattern        | In-flight gate: shadow-mode → enforced corridor-by-corridor, with a circuit-breaker |
| Connectors     | Volante VolPay · Finastra FusionFabric · SWIFT Alliance                          |

Your channel _preset_Repair inbound / outbound `pacs.008` for screening and legacy.

```json
{
  "channelName": "swift-cbpr-in",
  "channelSelection": {
    "channel": "swift", "schemeVersion": "SR2026", "direction": "INBOUND",
    "pspCountry": "GB", "timezone": "Europe/London"
  },
  "corridor": { "sendingCountry": "US", "receivingCountry": "GB", "currency": "USD" },
  "preferences": {
    "outputMode": "CBPR_PLUS", "autoRepairMode": "STANDARD", "targetFormat": "auto",
    "quality": "premium", "repairConfidenceThreshold": 0.85
  }
}
```

Endpoints you'll _use_All four operations, on both sides.

| Endpoint                              | Does                                                          |
| :------------------------------------ | :------------------------------------------------------------ |
| EP-10 / EP-12 Check / Convert Message | Gate-keep and repair inbound client files.                    |
| EP-12 Convert Message Addresses       | Repair pacs.008 addresses in transit, keeping STP.            |
| EP-08 Process Message Addresses       | Full pipeline on your own outbound pacs before release.       |
| EP-13 Render Message Addresses        | Down-render a whole message to MT for a legacy correspondent. |
| EP-15 R-Transaction Message           | Detect returns / recalls and pass them through untouched.     |
| EP-03 Check Party Address             | The client-facing PreCheck (address-level).                   |

Recommended _use cases_Gate, repair, render, and never touch a return.

securityGate-keep inbound client payment files

Gate · Validate to Correct

Message In-Flight

Validate and repair client files before they ever enter inter-PSP space.

EP-10 / EP-12 Check and Convert Message Single-msg · pain + pacs

mergeRepair pacs.008 addresses in transit

Correct

Message In-Flight

Correct non-compliant addresses as the message transits, keeping straight-through processing.

EP-12 Convert Message Addresses Single-msg · pacs

outputRender a whole message for a legacy correspondent

Render

Message In-Flight

Down-render all addresses in a pacs.008 to unstructured for an MT correspondent.

EP-13 Render Message Addresses Single-msg · pacs to MT

replayHandle returns and recalls safely

Validate · exempt

Message In-Flight

Assess the EPC Section 8.3 exemption on R-transactions; never modify the original address.

EP-15 R-Transaction Message Single-msg · pacs / camt

**Watch out for —** roll the gate out in **shadow-mode** first, then enforce corridor-by-corridor with a **circuit-breaker** — if ARS is unavailable, traffic routes exactly as it does today. Never modify returns / recalls (EPC §8.3) — use `EP-15`. Offer client correction as a PreCheck, not silent counterparty edits (EPC §3.2).

Where next

[Payment hubs](https://dev.ionova.ai/solutions/hubs)[Compliance](https://dev.ionova.ai/solutions/compliance)[Channels](https://dev.ionova.ai/channels)[API reference](https://dev.ionova.ai/apis)