Cross-border payments accumulate reconciliation debt at every jurisdictional and currency boundary. Data models, reporting formats, and regulatory frames all differ from one region to the next, and every crossing point becomes a surface where those differences have to be reconciled.
CrossStream is architected so cross-border settlement runs in the same event-reconstruction model as domestic settlement. Jurisdictional and currency boundaries become properties of the events themselves, not fault lines the reconciliation has to bridge.
One architectural model for settlement across jurisdictions. It is not one system stitched into another across borders.
Data resides where regulation requires. The event log stays coherent across regions while the physical storage respects sovereignty.
Currency conversion, FX exposure, and multi-currency reconciliation are all architectural features. They are not per-corridor customisations added later.
Regulatory reporting is generated per jurisdiction from the shared audit trail. There is no separate reporting integration to build for each regulator.
Settlement across jurisdictions is one settlement, not many. CrossStream reads the same event stream as Nexus, enforces per-region data residency at the substrate level, and settles across every jurisdiction in a single pass.
CrossStream operates on the same substrate as Nexus. The event model, identity model, and audit trail are shared. What CrossStream adds is per-jurisdiction context: regulatory frame, data residency requirement, currency, and reporting format all become properties of the events themselves.
The result is that a cross-border settlement outcome is derivable from the same event log a domestic settlement outcome is derivable from. Auditors, regulators, and the institution's own compliance teams all work from the same source.
CrossStream fits institutions where cross-border settlement is a first-class operational concern, rather than an edge case handled by a separate system.
Cross-border settlement across the bank's own branches, correspondent relationships, and multi-currency exposure.
Settlement across the processor's own multi-jurisdiction footprint plus scheme settlement.
Cross-border marketplace settlement without a separate reconciliation layer per corridor.
CrossStream deploys in sovereign, managed, or hybrid model. Hybrid is common for cross-border deployments: sovereign per jurisdiction where required, managed where not.
Institution-hosted, institution-operated. Full ownership of infrastructure and roadmap.
MonTechSys-hosted, institution-governed. Reduced operational burden with ownership of policy and data preserved.
Selective planes hosted, others deployed in-institution. Chosen per regulatory requirement.
CrossStream inherits the shared substrate. That is the same event model, identity model, and audit trail every other MonTechSys plane operates on.
