ISO 20022. Above the rails.
XVILAN is the data router between your treasury and the payment networks — scanning, cleansing, and translating ISO 20022 messages before they ever touch Fedwire or CBPR+. Deterministic engine, transparent toll, live the day you receive your API key.
$ curl -X POST \
-H "x-api-key: xvilan_live_••••••••" \
-d @pacs.008.xml \
https://www.northstarclaim.com/api/v1/shield/scan
{
"status": "STP_READY",
"duplicateUetrDetected": false,
"rail": "FEDWIRE",
"billing": {
"service": "SHIELD",
"chargeUsd": 50
}
}
Why every institution must adapt before Nov 14, 2026
NOV 14, 2026
Unstructured postal addresses are NAKed at the network. No contingency. No fallback. Every pacs.008, pacs.009, pacs.004, and pain.001 must carry structured TwnNm + Ctry.
A data router. Not a bank.
XVILAN sits passively above Fedwire, CHIPS, FedNow, and RTP — scanning, cleansing, and translating ISO 20022 messages before they touch the network. We never hold funds, never take custody, and never need a money transmitter license.
Where legacy FMI vendors run 6–18 month implementations behind seven-figure contracts, XVILAN is a self-serve API with deterministic pricing. The toll is a pure function of your traffic — nothing is invented, everything is computed.
Deterministic engine
Every scan, cleanse, and translation is a pure function. No LLM output in the money path. No hallucinated numbers.
Zero-PHI / zero-secret logging
Payment payloads are processed in volatile enclave memory. Logs carry telemetry, never the message.
Self-serve from day one
API key → first scan. No sales cycle, no MSA required to start, no implementation retainers.
Above the rails that move the world's money.
One engine, two highways. Domestic sweep on Fedwire today, cross-border readiness ahead of the November 2026 CBPR+ cliff.
Fedwire
$4.7T / day- Real-time gross settlement (RTGS)
- UETR mandatory on every message
- No structured-address mandate — lower NAK surface
- High-volume sweep target for corporate treasuries
CBPR+ (Cross-Border)
Nov 14, 2026 cliff- Structured-address mandate — unstructured AdrLine NAKed
- UETR (UUID v4) required on all business messages
- pacs.008 / pacs.009 structured fields enforced
- Pre-flight cleanse before the network rejects
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.
Rejection Shield
Scan before the rail rejects.
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
Address & BIC Remediation
The Nov 2026 CBPR+ cliff, solved.
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
MX Conduit
MT103 → pacs.008, round-trip clean.
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)
Dialect Harmonizer
CBPR+ ↔ HVPS+, at the boundary.
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
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.
up to 500 msg/day
Self-serve API key, live dashboard, full toll card. Stand up in minutes — not months.
up to 5,000 msg/day
Bulk batch endpoint, priority processing, aggregate STP telemetry across your whole flow.
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.
$ curl https://www.northstarclaim.com/api/v1/pricing?currency=EUR
{
"currency": "USD",
"tolls": [
],
"note": "Usage-based. No fixed monthly minimum. Billed per message processed."
}
Ingest. Scan. Cleanse. Translate. Harmonize. Deliver.
Six deterministic stages. Each one verifiable, each one billed as a transparent toll on your usage.
Ingest
MT103 / MT202 / JSON / MX lands on the API. Validated against a strict schema.
SHIELD
Deterministic STP scan — field-level validation, duplicate UETR detection.
CLEANSE
Structured address + BIC remediation. The CBPR+ cliff, absorbed before the NAK.
TRANSLATE
Render to MX pacs.008. Round-trip re-parse must return STP_READY.
HARMONIZE
CBPR+ ↔ HVPS+ boundary translation — BIC ↔ RTN mapping, cross-rail tag injection.
Deliver
STP_READY message handed back to your treasury or bank connection.
Built for the teams that move money.
Corporate Treasury
Pre-flight every Fedwire instruction before it leaves your bank connection. Kill rejections at the source.
Fintechs & PSPs
Embed ISO 20022 in a day. One self-serve API for scan, cleanse, translate, and harmonize — no vendor calls.
Correspondent Desks
Cleanse cross-border traffic ahead of the November 2026 structured-address mandate and harmonize CBPR+ ↔ HVPS+ at the boundary.
Hardware-enforced. Data stays dark.
Payment payloads are processed inside HSM-backed enclaves with confidential computing. Payloads are never written to logs, and reasoning runs on local AI — no external API exposure.
Premium Key Vault. No plaintext secrets.
Hardware isolation during processing.
Telemetry only — never the payload.
No external inference on the money path.
$ curl -X POST https://www.northstarclaim.com/api/v1/shield/scan \
-H "X-API-Key: $XVILAN_KEY" \
-d '{"rail": "FEDWIRE", "contentType": "MX_XML"}'
{
"status": "STP_READY",
"duplicateUetrDetected": false,
"billing": {"service": "SHIELD", "chargeUsd": 50}
}
Straight answers.
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.