Provider & rails
Enforce address quality at the edge.
You route traffic no single bank controls. Gate-and-repair every transiting pacs in-flight, corridor by corridor, under 50ms — one integration cleans traffic for every institution on the hub.
The hinge — the broadest enforcement point in the network is also the broadest billable service. The rollout unit is the corridor, not the client — light one up, then propagate.
Where you call ARSAll in flight, at the network edge.
| Placement | In-Flight |
| Scope | Message (routed pacs) |
| Channel preset | swift-cbpr-in / corp-host-to-host |
| Pattern | Edge gate: shadow per corridor → enforced, with a circuit-breaker; sub-50ms inline |
| Transports | REST · IBM MQ · Kafka · SFTP |
Endpoints you'll useClassify, gate, repair, render — in line.
| Endpoint | Does |
|---|---|
EP-10 Check Message Addresses | Gate all routed files at the boundary. |
EP-12 Convert Message Addresses | Repair transiting pacs inline, keeping STP. |
EP-09 Process Batch Message Addresses | End-of-day sweep, up to 100 messages per call. |
EP-13 Render Message Addresses | Down-render to legacy MT for far-side correspondents. |
EP-14 Extract Message Addresses | Portfolio readiness scan across all routed traffic. |
Recommended use casesThe widest reach of any audience.
Watch out for — the gate adds no routing latency (sub-50ms inline) and a circuit-breaker keeps payments moving if ARS is unavailable. Roll out corridor-by-corridor in shadow first. Pass returns / recalls through unmodified (EPC §8.3).