Commercial Model · Figures on Request

ISO 20022 Address Solution Pricing: The ioNova ARS Model

Commercial reference · Last reviewed 26 July 2026

ioNova ARS pricing is built from five dimensions: an edition matched to your role (Treasury, Banking or Transact), a platform tier, banded annual message volume with per-message rates that decline at scale, your deployment mode (SaaS, private cloud/VPC, on-premise or air-gapped) and a support tier. Contracts are annual as standard, quoted in EUR, USD or GBP — and the 246-country reference data is included, with no separate licence.

TL;DR Three editions (Treasury · Banking · Transact) · metered by annual message volume across eight declining bands · four deployment modes · Bronze→Platinum support with 99.0–99.95% uptime SLAs · annual term standard, multi-year available · Exceptions Workbench, dashboards and GeoPostcodes-sourced 246-country data included · sandbox in days, live in 2–4 weeks. No published price list — figures on request.

3
Editions — Treasury · Banking · Transact
4
Deployment modes — SaaS · VPC · on-prem · air-gapped
246
Countries of reference data — included
2–4 wks
Standard SaaS go-live
The Model

How ioNova ARS pricing is structured

DimensionWhat it meansWhat moves it
EditionTreasury (corporates) · Banking (banks/PSPs) · Transact (correspondent FIs/hubs)Your role in the payment chain
Platform tierThe integration and deployment envelope, from REST-and-file entry to OEM-embedded partner scopeChannels enabled; single vs multi-entity
Message volumeBanded per-message rates that decline as annual volume rises (eight bands, reaching nine-figure counts)Annual address-resolution volume
Deployment modeMulti-tenant SaaS (baseline) → private cloud/VPC → on-premise → air-gapped dedicatedIsolation and residency requirements
Support tierBronze · Silver · Gold · Platinum — uptime SLAs 99.0% → 99.95%Response model, from business-hours email to 24/7 with named contacts

An annual subscription is the standard term (multi-year available); implementation is a one-time scoped programme. Quotes are issued in EUR, USD or GBP. ioNova does not publish a price list — the model above is the complete structure, and figures are provided on request against your volumes and deployment requirements.

Editions

Three editions, one engine

ARS TreasuryARS BankingARS Transact
Built forCorporate treasury, shared service centres, TMS/ERP estatesBanks and PSPsCorrespondent FIs and payment hubs
Core jobCompliant pain.001 / payment-file output from master dataPoint-of-entry validation; in-flight pacs/camt correctionHigh-volume message streams across schemes
Typical channelsREST API, SFTP, DatabaseREST API, IBM MQ, Kafka, DatabaseAll six mechanisms incl. MCP
Deployment modesSaaS · VPCSaaS · VPC · on-premiseSaaS · VPC · on-premise · air-gapped
Included in every edition
All 27 API endpoints (5 groups) · Exceptions Workbench · operational dashboards · 246-country postal reference data (GeoPostcodes-sourced, embedded — no separate data licence) · ~98% automatic STP, >99% with the Workbench · sub-50ms P95 pipeline.
Total Cost of Ownership

Build vs buy: the cost frame that matters

PathTime to compliantResidual risk
Build in-house18–36 months of engineering to parityData licensing, scheme-change maintenance, key-person risk
Retrofit a postal-validation API26–40 weeks of integrationPostal output ≠ payment-grade ISO 20022 XML; compliance gaps unresolved
ioNova ARSSandbox in days · live in 2–4 weeksDeterministic engine, audit trail, scheme updates included

Source: ioNova 25-criterion evaluation framework (composite 4.90/5) — see /compare.

With the 15 November 2026 cutover fixed, time-to-compliant dominates total cost of ownership: every month of build or retrofit delay is a month of repair costs, degraded STP and deadline risk that no licence saving recovers.

Get figures for your volumes

A 30-minute demo covers the edition and deployment mode that fits your estate, then a quote built on your annual message volume — in EUR, USD or GBP.

Book a demo
FAQ

Frequently asked questions

How is the ioNova ISO 20022 address solution priced?
ioNova ARS is priced on five dimensions: platform tier, annual message volume (banded per-message rates that decline with scale), the integration mechanisms you enable, deployment mode (multi-tenant SaaS, private cloud/VPC, on-premise or air-gapped) and support level. Contracts are annual as standard and quoted in EUR, USD or GBP; figures are provided on request.
Is there a free tier?
ioNova does not publish a free production tier. Evaluation starts in the developer sandbox at dev.ionova.ai — running in days — so engineering teams can exercise the 27 API endpoints against real address data before any production commitment; production plans then go live in as little as 2–4 weeks.
Is the 246-country reference data licensed separately?
No. The 246-country postal reference dataset (GeoPostcodes-sourced) is embedded in every ioNova ARS edition. There is no separate data licence to negotiate or renew, and reference-data updates — including historical place-name changes such as Bombay to Mumbai — are included in the subscription.
What is the standard contract length?
An annual subscription is the standard commercial term, covering the platform fee, metered message volume, enabled integrations, deployment add-ons and the support tier. Multi-year terms are available commercially, and implementation is scoped as a one-time programme at the start of the engagement.
How does pricing scale with message volume?
Message charges are banded: the per-message rate steps down as annual volume grows, across eight volume bands that reach nine-figure annual message counts. High-volume correspondent banking and payment-hub deployments therefore see materially lower unit economics than entry-volume tiers.
Do deployment modes change the price?
Yes. Multi-tenant SaaS is the baseline; private cloud/VPC, on-premise, white-label and air-gapped dedicated infrastructure are priced as deployment add-ons on top of the platform tier. Higher-isolation modes also carry longer implementation programmes than the standard 2–4 week SaaS onboarding.
What support levels are available?
Four support tiers — Bronze, Silver, Gold and Platinum — carry uptime SLAs from 99.0% to 99.95%, escalating from business-hours email support with self-service onboarding to 24/7 critical response with a named account manager, SLA credits and a dedicated customer-success and engineering contact.
How does the cost compare with building an address solution in-house?
ioNova's 25-criterion evaluation framework puts an in-house build at 18–36 months of engineering before reaching parity, and a postal-API retrofit at 26–40 weeks with payment-compliance gaps unresolved. ioNova ARS starts in the sandbox in days and goes live in 2–4 weeks — the dominant driver of its total cost of ownership and payback period.
Notes

Sources & further reading

ioNova reference material

  • ioNova ARS commercial model — structure only; figures on request.
  • ioNova 25-criterion evaluation framework.
  • ioNova ARS platform facts: 27 endpoints in 5 groups · 246 countries · ~98% automatic STP, >99% with the Exceptions Workbench · sub-50ms P95.
Keep Reading

Related

The developer view

27 REST endpoints, OpenAPI 3.x, six integration mechanisms — the address parsing API.

Solutions by role

Treasury, banking, hubs, API providers — seven ways to deploy one engine.

For banks

What the structured-address mandate means for banks and PSPs, end to end.

For corporates

Treasury and shared-service view: compliant payment files from your ERP/TMS data.

How ioNova compares

The 25-criterion evaluation framework across 11 vendor approaches.

The ISO 20022 deadline

What is rejected from 15 November 2026 and the T-90 countdown plan.

Structured address mandate

The live guide to the November 2026 structured-address mandate.

Technical documentation

Quickstart, auth, channels and the full API reference — dev.ionova.ai.