Rejection shieldDomestic & cross-borderISO 20022 migrationSelf-serve API

Institutional toll card · ISO 20022

Usage-based tolls. Zero minimums.

Four deterministic modules. Every charge is a pure function of your traffic — no license fees, no implementation retainers, no sales cycle. Billed per message processed.

Toll card · deterministic engine
SHIELD

Rejection Shield

Scan before the rail rejects.

$50.00per message

Deterministic STP scan of every payment message before it touches the network. Field-level ISO 20022 validation, duplicate UETR detection, and rejection prediction — computed, never guessed.

  • Field-level MX validation
  • Duplicate UETR detection
  • STP-rate batch rollups
  • Live POST /api/v1/shield/scan
  • Inbound pacs.002 status mapping — $25/msg
Read the API spec →
CLEANSE

Address & BIC Remediation

The Nov 2026 CBPR+ cliff, solved.

1 bpsof gross

Converts unstructured AdrLine into the structured PostAdr format the networks now mandate — before the network NAKs the message. BICFI routing remediated at machine speed.

  • Structured PostAdr conversion
  • BICFI routing remediation
  • Gross-USD basis-point toll
  • CBPR+ structured-address ready
  • Live POST /api/v1/shield/cleanse
TRANSLATE

MX Conduit

MT103 → pacs.008, round-trip clean.

$10.00per message

MT103 / MT202 / JSON translation into MX pacs.008 with deterministic rendering. Every output re-parses to STP_READY on Fedwire before it ships. No drift, no guesswork.

  • MT103 → pacs.008
  • MT202 → pacs.009
  • Round-trip STP_READY verification
  • UETR generation (UUID v4)
Read the API spec →
HARMONIZE

Dialect Harmonizer

CBPR+ ↔ HVPS+, at the boundary.

$25.00per message

The dual-engine translation gate between cross-border CBPR+ and domestic HVPS+ (Fedwire) — BIC ↔ RTN native mapping, tag injection and stripping, and settlement-timing alignment. CBPR+ valid is not HVPS+ valid; the engine translates at the boundary.

  • BIC ↔ RTN native mapping
  • CBPR+ → HVPS+ tag injection / stripping
  • Settlement-timing alignment
  • Deterministic operation trace
  • pacs.004 return reconciliation — $50/msg
Read the API spec →

Full payment lifecycle is metered

You are billed on the forward path and the return loop.

  • Forward: SHIELD $50 / TRANSLATE $10 / HARMONIZE $25 per msg
  • Return: pacs.002 status $25 / pacs.004 return $50 per msg

Every chargeable event is logged against your usage ledger with the exact message reference — no surprise invoices. View every toll line in real time from your console.

Volume scaling

The toll stays flat. Your scale compounds.

Same per-message price at every tier
Launch
Tier 01

up to 500 msg/day

Self-serve API key, live dashboard, full toll card. Stand up in minutes — not months.

Traction
Tier 02

up to 5,000 msg/day

Bulk batch endpoint, priority processing, aggregate STP telemetry across your whole flow.

Scale
Tier 03

50,000+ msg/day

Dedicated enclave, reserved capacity, custom cleansing rulesets for your counterparties.

Where legacy FMI vendors quote seven-figure contracts and still take 6–18 months to stand up, XVILAN is live on the day you receive your API key — at a transparent per-message toll. No MSA required to start scanning. No BAA until you move money.

The pricing endpoint

Multi-currency toll card — served from the engine, not the marketing site. Try ?currency=EUR.

Get API access

$ curl https://xvilan.com/api/v1/pricing?currency=EUR

{

"currency": "USD",

"tolls": [

],

"note": "Usage-based. No fixed monthly minimum. Billed per message processed."

}

Regulation J · Fedwire · ISO 20022 CBPR+
Zero-PHI logging · OCI Confidential Compute