Zero Coupling
If Connex goes offline, every payment continues without interruption. We add a layer. We never become a dependency that can block money movement.
ArchitectureAlongside,
Alongside,
not in-line.
Your existing payment systems stay exactly as they are. Connex adds a verification layer that watches the handoffs, fills the data gaps, and keeps the permanent record - without touching a single transaction.
The Coordination Gap
The space between institutions.
When Institution A sends money and Institution B receives it, both maintain their own separate records. When those records disagree, there is no shared log. No neutral party who witnessed what happened. Every institution has its own version of the truth, and every institution has a financial interest in the outcome.
That is the coordination gap. It exists in every market where multiple institutions move money between each other. It cannot be solved by any participant in the payment network, because every participant has a stake in the result.
Data Completeness
What survives the handoff.
| Data Field | Legacy Payment Rail | Connex Gateway | Evidence Status |
|---|---|---|---|
| Creditor Address (Structured) | DroppedLost at handoff | EnrichedCBK codebook lookup | Verified |
| Transaction Purpose Code | MissingAbsent in legacy formats | EnrichedClassification engine | Verified |
| End-to-End Reference ID | TruncatedCut to 12 characters | PreservedFull 36-char reference | Verified |
| Cryptographic Handoff Proof | NoneNo neutral record exists | WitnessedMulti-node consensus | Verified |
How It Works
Capture. Enrich. Prove. Resolve.
01
Capture
Connect, without disruption.
Institutions connect via a lightweight, non-invasive API. Connex captures payment events in real time as money moves across institutional boundaries, without sitting in the transaction path and without any risk to payment operations.
02
Enrich
Fill in what was dropped.
Our enrichment engine reconstructs missing compliance fields, purpose codes, and structured address data, assembling a fully compliant ISO 20022 message from what the legacy system sent, even when critical fields were absent.
03
Prove
Witness the handoff.
Independent witness nodes observe the payment handoff and generate a tamper-evident proof bundle. No single institution controls this record. The proof is signed, timestamped, and immutable, ready for dispute resolution or regulatory review.
04
Resolve
Minutes, not weeks.
When a discrepancy occurs, any authorised party retrieves the proof bundle. The record shows exactly what was sent, what was received, and when, with cryptographic certainty. Disputes that took weeks can now be resolved in minutes.
What We Believe
Four constraints we never break.
Constraint 01
Constraint 02
Zero Knowledge
We do not store what we do not need. No transaction amounts. No account numbers. No customer names. Only the structural proof that the handoff happened.
Constraint 03
Zero Stake
We have no financial interest in any payment outcome. The witness must be completely neutral, or the evidence it produces means nothing in a dispute.
Constraint 04
Verify, Don't Trust
You do not need to take Connex's word for anything. Every proof can be independently verified by any authorised party using standard cryptographic methods.
Founding Cohort
See the architecture in a live briefing.
We walk through the full technical architecture, answer your specific integration questions, and show you exactly how Connex connects to your existing systems.