Settlement Finality
Institutional blueprint governing message validation, network routing, and irrevocable settlement across the ISO 20022 rails XVILAN sits above.
Terms of Settlement
Regulation J Statutory Disclosure — Irrevocable Settlement Protocols for ISO 20022 Message Routing
This binding regulatory document governs all message throughput and settlement routing handled by the XVILAN middleware infrastructure. XVILAN is a financial technology software provider positioned above the payment networks — it does not hold deposits, transmit funds directly, or act as a depository institution.
ARTICLE I: Message Scope & Rail Coverage
XVILAN processes ISO 20022 MX payment messages — principally pacs.008 (FIToFI Customer Credit Transfer) and pacs.009 (Financial Institution Credit Transfer) — plus MT103 legacy input and canonical JSON payloads. Every message carries a mandatory UETR (Universally Unique Transaction Identifier, UUID v4) per the ISO 20022 migration standard.
The engine supports routing preparation for Fedwire and FedNow (HVPS+ domestic USD rails), RTP, and CBPR+ (cross-border), and performs dialect harmonization between the CBPR+ and HVPS+ usage guidelines at the network boundary. XVILAN is a software-first data router, not a bank, an MSB, or a money transmitter.
ARTICLE II: Regulation J & Irrevocability Provisions
All financial transaction payloads validated and routed by this technology engine are structured according to ISO 20022 credit transfer standards and prepared for submission to the real-time networks (Fedwire, FedNow, RTP, CBPR+).
In strict compliance with Federal Reserve Regulation J (12 C.F.R. Part 210, Subpart C) and Uniform Commercial Code (UCC) Article 4A statutory lines, all fund transfers executed through the underlying networks are completely final and irrevocable once confirmed by the network. XVILAN does not control, cancel, or reverse network settlement events.
Irrevocable Finality
All transaction messaging generated through the ISO 20022 pipeline matches strict Federal Reserve Regulation J (12 C.F.R. Part 210, Subpart C) and UCC Article 4A statutory boundaries. Once a message is validated and confirmed by the network, the settlement instruction is final and binding on all parties. No countermand, stop-payment order, or revocatory instruction shall be honored.
Settlement Rigidity
Real-time transactions routing through the rails are discrete, individual, and completely irreversible once registered on central bank ledgers. Each transaction constitutes a separate, irrevocable funds transfer under UCC Article 4A. The system does not support netting, aggregation, or retroactive reclassification of completed settlement events.
Liability Boundary
XVILAN accepts no stop-payment overrides or retroactive reversal commands once structural network confirmation executes. The message originator bears full responsibility for the accuracy of all payment data submitted prior to network confirmation. Post-confirmation disputes are limited to off-network reconciliation mechanisms as defined in Article IV.
ARTICLE III: Deterministic Validation & Toll Assessment
XVILAN's deterministic engines compute every finding from the message payload itself — no inference, no statistical fabrication. The toll card is assessed per message on a usage basis:
1. SHIELD ($50): Rejection Shield scan. Deterministic pre-flight analysis of a pacs.008/MT103/JSON payload against the target rail's validation profile.
2. CLEANSE (1 basis point of gross USD): Remediation of structured-address and BIC defects ahead of the November 14, 2026 CBPR+ unstructured-address mandate.
3. TRANSLATE ($10): Conversion between MT103, canonical JSON, and ISO 20022 MX message formats.
4. HARMONIZE ($25): CBPR+ to HVPS+ dialect conversion at the network boundary — BIC to RTN mapping, address-structure conversion, and cross-rail tag injection.
Tolls are computed by the deterministic engine in src/lib/billing/iso20022-tolls.ts and mirrored by the live /api/v1/pricing endpoint. No fee is assessed on messages that fail validation and never reach the rail.
ARTICLE IV: Jurisdiction & Governing Protocols
This settlement document is governed exclusively under United States Federal law, utilizing structural regulatory boundaries overseen by the Federal Reserve Board. Any operational disputes arising from algorithmic validation execution or billing reconciliation will be handled exclusively via expedited binding institutional arbitration inside private judicial panels, preventing any disruption to the public front-end system interfaces.
ARTICLE V: Billing Rails & Fee Capture
Stripe Enterprise Rails
All billing is processed via Stripe, Inc. enterprise settlement paths. XVILAN is a financial technology software provider and does not accept deposits or hold client funds. Billing is limited to the per-message toll card described in Article III.
Fee Capture Mechanics
Per-message tolls are metered deterministically at the point of engine invocation. The toll is calculated from the validated message count and, for CLEANSE, the gross USD value of the message. No fee is assessed on messages rejected before processing. There are zero fixed monthly minimums and no long sales cycles.
OCI Enclave Billing
Enterprise deployments are billed through Stripe enterprise rails against the per-message toll card. XVILAN's primary institutional compute resides on Oracle Cloud Infrastructure confidential VMs (AMD SEV-SNP) in the Frankfurt region, with OCI SOC 2 Type II and ISO 27001 inherited at the hardware layer.
ARTICLE VI: Zero-Payload Hardware Boundary & Data Isolation
Zero-Payload Logging
XVILAN operates under a strict zero-PHI / zero-payload logging mandate. Message content is never written to stdout, stderr, application logs, or telemetry streams — only operational metadata (message count, rail, toll line items) is retained. All compute occurs inside hardware-isolated OCI Confidential Computing enclaves using AMD SEV-SNP trusted execution environments on Oracle Cloud Infrastructure.
Immutable Audit Records
All audit logs are preserved in a non-persistent, read-only memory pool within OCI confidential VMs, immune to external system interception or database tracking. Transaction records are written once and are immutable by design — no administrative interface, database user, or external actor possesses the capability to modify, delete, or redact completed audit entries. The read-only memory pool operates independently of the application database layer.
Dialect Harmonization Boundary
The harmonization engine converts messages between the CBPR+ and HVPS+ usage guidelines at the network boundary — mapping BICFI to RTN, restructuring addresses, and injecting or removing cross-rail tags. Per the BIS PIE task force, a message valid under CBPR+ is not automatically valid under HVPS+; banks translate at the boundary. XVILAN performs this translation deterministically inside the enclave.
ARTICLE VII: Authority & Strategic Enforcement
Establishes Absolute Authority
Citing 12 C.F.R. Part 210 and UCC Article 4A in this binding regulatory document immediately alerts legal and compliance teams that all counterparties acknowledge and understand federal transaction structures. This statutory framework establishes the XVILAN middleware as a recognized data router operating above the same legal gravity as Fedwire and CHIPS participants.
Anchors the Deterministic Engine Concept
The deterministic validation, cleansing, translation, and harmonization engines operate strictly inside the hardware security perimeter. Each engine executes within its own dedicated enclave instance, with inter-engine communication mediated exclusively through attested TLS channels. No engine possesses the ability to export message payloads, modify settlement instructions, or alter audit records.
XVILAN Systemic Infrastructures LLC — ISO 20022 Data Router & Regulation J Statutory Disclosure — All Rights Reserved