ISO 20022Deterministic engineCBPR+ ready

Deterministic by design.

XVILAN is a deterministic ISO 20022 data router above the payment rails. Four toll modules — SHIELD, CLEANSE, TRANSLATE, HARMONIZE — validate, remediate, translate, and harmonize MT and MX traffic into STP-ready pacs.008. Every result computed, never guessed.

Run a free scan Read the API docs
$4.7T
Avg daily value over Fedwire
4
Deterministic toll modules
0
Fixed monthly minimums
99.99%
Uptime SLA on the shield
The toll modules

Four modules. Deterministic pricing.

Each module is a pure function of your traffic — a transparent per-message toll, with zero fixed monthly minimums.

$50 / message

SHIELD

Deterministic STP rejection scan

A rule-based scan that runs before your message touches the rail. Field-level validation and rejection prediction, computed from the message itself — never guessed.

  • Field-level MX validation
  • Duplicate UETR detection
  • Rejection prediction
  • Batch STP-rate rollups
POST /api/v1/shield/scan
1 bps of gross USD

CLEANSE

Structured PostAdr + BICFI remediation

Converts unstructured address lines into CBPR+ structured PostAdr and remediates BICFI routing before the network can NAK. The Nov 14, 2026 structured-address cliff, solved.

  • Unstructured AdrLine to structured PostAdr
  • BICFI routing remediation
  • Pre-flight for the Nov 14, 2026 CBPR+ mandate
  • Applied before translation, not after
POST /api/v1/shield/cleanse
$10 / message

TRANSLATE

MT103 / MT202 / JSON to MX pacs.008 / pacs.009

Renders legacy and JSON payment instructions into MX pacs.008 / pacs.009 with a generated UETR (UUID v4) and a round-trip re-parse that must return STP_READY.

  • MT103 / MT202 / JSON to MX
  • pacs.008 / pacs.009 output
  • UETR generation — UUID v4
  • Round-trip re-parse must return STP_READY
POST /api/v1/mx/translate
$25 / message

HARMONIZE

CBPR+ ↔ HVPS+ in-flight dialect harmonization

The dual-engine translation gate. Validates CBPR+ elements, strips cross-border routing tags, and injects the mandatory HVPS+ Fedwire identifiers the moment an international payment lands on a domestic rail.

  • BIC ↔ RTN native mapping
  • CBPR+ → HVPS+ tag injection / stripping
  • Cross-rail settlement-timing alignment
  • Flawless Fedwire handoff, guaranteed by construction
POST /api/v1/mx/harmonize
Self-serve endpoints
POST /api/v1/shield/scanPOST /api/v1/shield/scan/batch (up to 1,000 msgs)POST /api/v1/shield/cleansePOST /api/v1/mx/translatePOST /api/v1/mx/harmonizeGET /api/v1/pricingPOST /api/free-scan
Both rails in parallel

One engine, two highways.

Domestic sweep on Fedwire today, cross-border readiness ahead of the November 14, 2026 CBPR+ structured-address cliff.

Domestic · USD

Fedwire

$4.7T avg daily value
  • Real-time gross settlement (RTGS)
  • UETR mandatory on every message
  • No structured-address mandate — lower NAK surface
  • High-volume sweep target for corporate treasuries
Global · Multi-currency

CBPR+ (Cross-Border)

Nov 14, 2026 cliff
  • Structured-address mandate — unstructured AdrLine NAKed at network level
  • UETR (UUID v4) required on all business messages
  • pacs.008 / pacs.009 structured fields enforced
  • Pre-flight cleanse before the network rejects
The pipeline

Ingest. Scan. Cleanse. Translate. Harmonize. Deliver.

Six deterministic stages. Each one verifiable, each one billed as a transparent toll on your usage.

01

Ingest

MT103 / MT202 / JSON / MX lands on the API, validated against a strict schema.

02

SHIELD

Deterministic STP scan — field-level MX validation, duplicate UETR detection.

03

CLEANSE

Structured PostAdr + BICFI remediation. The CBPR+ cliff, absorbed before the NAK.

04

TRANSLATE

Render to MX pacs.008 / pacs.009. Round-trip re-parse must return STP_READY.

05

HARMONIZE

CBPR+ ↔ HVPS+ boundary translation — BIC ↔ RTN mapping, cross-rail tag injection.

06

Deliver

STP_READY message handed back to your treasury or bank connection.

Institutional grade

Hardware-enforced. Data stays dark.

Payment payloads are processed inside HSM-backed enclaves with zero-PHI logging and a Neon persistence ledger. The engine is deterministic — every result is computed from the message, never guessed.

Zero-PHI logging

Telemetry only — never the payment payload.

HSM-backed enclaves

Keys and processing isolated in hardware.

Neon persistence ledger

Serverless persistence, no local storage.

Deterministic engine

Computed, never guessed — no LLM in the money path.

No MSA to start scanning. No BAA until you move money.

$ curl -X POST https://xvilan.com/api/v1/shield/scan \

-H "X-API-Key: $XVILAN_KEY" \

-d '{"rail": "FEDWIRE", "contentType": "MX_XML"}'

{

"status": "STP_READY",

"duplicateUetrDetected": false,

"rail": "FEDWIRE",

"billing": {"service": "SHIELD", "chargeUsd": 50}

}

Start scanning today. No minimums. No sales cycle.

Get your API key, POST your first message to the shield, and see deterministic STP results in seconds — not months.

Request API access Run a free scan