The Connexum Platform

Obligation intelligence — for institutions and merchants.

Two products. One obligation layer. Connexum enforces regulatory SLAs across every settlement participant — automatically. Connexum Merchant executes operational fixes for small businesses without requiring staff to act on them.

ACQUIRER PROCESSOR ISSUER NETWORK
120
pytest tests · all passing
15/15
adversarial breakage datasets
2.26s
100K transactions
22
backoffice connectors
10
detection modules
The problem

Settlement obligations don't wait for manual reconciliation.

Reg E demands action in 10 business days. BSA SAR filings must clear within 30. OFAC freezes are instantaneous. Every missed deadline is a regulatory event with a dollar consequence.

BSA

SAR Filing Windows

31 CFR §1020.320 requires SAR detection and filing within strict time bounds. Manual reconciliation misses the pattern until it's already a violation.

Reg E

Provisional Credit Clocks

§205.11 starts a 10-business-day clock the moment a dispute is received. Most issuers track this in spreadsheets — and lose.

OFAC

Instantaneous Freeze

31 CFR Part 560 requires same-day counterparty freeze on SDN match. A match that clears through settlement without detection is a sanctions violation.

PCI DSS

Retention Governance

Req. 10.7 mandates audit-log retention and chain-of-custody proof. Most settlement stacks have no log-governance layer at all.

Visa VDR

30-Day Pipeline SLA

Visa's VDR requires stuck transactions to surface and resolve within 30 days. Without automated detection, the deadline passes silently.

MC MDR

45-Day Batch Proof

Mastercard's MDR requires end-of-day batch reconciliation and 45-day audit trail. Batch discrepancies compound when not caught at the transaction level.

Architectural invariants

Three commitments that don't bend.

I

Zero information leakage

No participant can infer any counterparty's transaction details from Connexum outputs. All cross-party signals are aggregate and one-way.

II

Obligation-aware routing

Every module is wired to its citation: Reg E §205.11, BSA 31 CFR §1020.320, OFAC 31 CFR Part 560. The consequence of breach is part of the detection signal.

III

Auditable proof

Every decision, every SLA clock, every triggered threshold is written to an append-only audit ledger. Connexum's own output is subject to independent attestation.

Two products

Settlement control and merchant execution — both built, both validated.

Explore Connexum

Six stages. Ten modules. Four participants.

Every section below is a production-validated capability, not a roadmap item.