Delivery
Deliver the mandate without building the engine.
Embed a deterministic, pre-certified engine instead of hand-building a multi-rulebook parser re-certified on every scheme release. One capability, system-agnostic, across every client's stack.
The hinge — your client's exposure is your delivery risk on a fixed-date programme. A hand-built parser is 13–23 months plus a permanent rulebook-maintenance tail that doesn't transfer to the next client. Buy the engine; bill the build.
How you deliverThe four components map onto your delivery.
| Placement | Any — inherits the client's edition (At-Source, In-Flight, or overlay) |
| Scope | Any — Party and/or Message |
| Channel preset | The client's — e.g. sepa-sct-out, swift-cbpr-in, corp-host-to-host |
| Pattern | System-agnostic sidecar into SAP, Oracle, Kyriba, Volante, Finastra or custom |
| Maintenance | 0 — ioNova carries scheme upgrades as config, not a re-build |
Endpoints you'll useSelected per engagement from the full U1–U20 set.
| Endpoint | Does |
|---|---|
EP-02 Process Batch Party Address | Client master-data migration & scrub. |
EP-08 / EP-09 Process (batch) Message | The all-steps pipeline for corporate or bank clients. |
EP-10 / EP-12 Check / Convert Message | Validate then correct, At-Source or In-Flight. |
EP-14 Extract Message Addresses | Readiness assessment at the start of an engagement. |
Recommended use casesAt-Source for corporates, In-Flight for banks / hubs.
ink_eraserClient migration & scrub
Correct
Data At-Source
Batch-clean a client's master data before go-live, up to 10,000 addresses per call.
EP-02 Process Batch Party Address
Watch out for — ARS is system-agnostic — the same capability transfers across every client's stack. ioNova carries the regulatory maintenance (config, not a re-build), so there's no maintenance tail on your books. Pick the edition (and its use cases) per engagement; resell, refer or co-deliver all remain open.