Nexus does not settle from batches. It reads the operational event stream directly, the same one that records every transaction, state change, and reconciliation across the platform.
Because settlement is derived from the event log rather than reconstructed from parallel systems, the settlement outcome matches the operational outcome. Reconciliation between operations and settlement stops being a process. It becomes a property of the architecture.
Settlement obligations are calculated from the operational event log. There is no batch cycle, no lag between operations and settlement, and no parallel reconciliation to maintain.
Settle across every participant in a payment flow (acquirer, issuer, scheme, bank, merchant) in one pass. This is genuine multi-party settlement, not one-to-one settlement stitched together into something that resembles it.
The settlement engine has no commercial exposure to the settlement outcome. It deploys under the institution's control, and it is not operated by a party with skin in the game.
Every settlement outcome is traceable to the operational events that produced it. External auditors receive scoped, evidence-grade read access.
Settlement states can be derived from the underlying event model, giving institutions a consistent view of what happened, when it happened, and how each transaction reached its final state.
Nexus reads the platform's event stream and projects it into a settlement model. Financial obligations between participants are calculated deterministically from the events that produced them. The settlement outcome is a function of the events. The events are the audit trail. The audit trail is immutable.
This changes the nature of settlement disputes. In legacy systems, disputes get reconciled across parallel data sources: the acquirer's view against the issuer's view against the scheme's view against the institution's own. In Nexus, every participant settles from the same event stream. Disputes reduce to disagreements about how to interpret an event, not disagreements about which data source is authoritative.
Every settlement system on the market is operated by someone with a commercial interest in the outcome. A bank. A scheme. A processor. A settlement provider. That is not a criticism of how the industry works. It is a description of it.
Nexus is architected differently. The institution deploys it, owns the infrastructure, and governs it under its own rules. No third party sits between the institution and its own financial obligations.
For institutions where this matters (banks running multi-scheme settlement, marketplaces settling across sellers and buyers, high-GMV operators managing settlement across acquirers), the difference is categorical.
Nexus deploys in sovereign, managed, or hybrid model. Sovereign is the most common for institutions where settlement neutrality is a strategic priority.
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.
Nexus operates natively with other MonTechSys planes, reading the same event model and settling against the same operational truth.
