Connexum is designed for the full settlement chain — not one participant in isolation. Each participant gets a purpose-fit module profile, obligation set, and connector stack. The platform coordinates across all four without leaking information between them.
Acquirers carry the largest chargeback liability surface in the settlement chain. Connexum's acquirer profile enforces transaction matching, batch reconciliation, fee auditing, and chargeback-window SLAs across the full merchant portfolio — automatically.
Visa and Mastercard chargeback evidence is assembled automatically within the 120-day window. Miss the window; absorb the liability. Connexum doesn't miss windows.
End-of-day batch proof runs against every settlement file. Discrepancies surface at the transaction level — not after a month of reconciliation by hand.
Interchange and network-fee billing is validated against the settlement file on every cycle. Overbilling is caught in the same run that closes the books.
An acquirer with a 500-merchant portfolio running 3,000 TPS peak generates approximately 420 settlement batches per month. Without automated reconciliation, a 2.5% failed-batch rate means roughly 10 batches per month in manual resolution queues. Connexum reduces that to near-zero — and generates the Mastercard MDR report as a by-product of the daily run.
Processors sit downstream from acquirers and upstream from issuers, carrying the funding-validation and stuck-transaction risk surface. Connexum's processor profile enforces funding-file reconciliation, Reg E provisional-credit windows, and pipeline-stall detection across the full transaction volume.
Funding files are reconciled against the GL in real time. Shortfalls surface before the settlement window closes — not after the funds have moved.
The 10-business-day provisional-credit obligation starts the moment a dispute event is received. Connexum runs the clock automatically and escalates at day 8.
Pipeline stalls are detected and flagged before the 30-day VDR window expires. The VDR report is a by-product of detection — not a separate reporting exercise.
A processor handling 50 million transactions per day operates at roughly 580 TPS peak. At a 3% failed-batch rate, that's approximately 63 discrepancy events per month in manual resolution. Connexum reduces manual intervention to exception-only and generates the Reg E audit trail as part of the daily run.
Issuers carry the Reg E provisional-credit obligation, OFAC SDN screening responsibility, BSA SAR filing duty, and PCI audit-log governance requirement. Connexum's issuer profile enforces all four — automatically and in real time.
SDN list match triggers a same-day freeze protocol. OFAC notice package is assembled automatically. Missing this by even one settlement cycle is a regulatory violation with civil penalty exposure up to $311K per instance.
Suspicious-activity patterns are detected at the transaction level. The BSA 30-day filing window is tracked from detection, not from the compliance team's manual review queue.
Connexum enforces the 12-month retention calendar, maintains log chain-of-custody, and generates the Req. 10.7 audit export. Card-brand fine risk from log-governance failure is eliminated as a standing operational concern.
A mid-size issuer with 2 million cardholders generates approximately 2,400 TPS peak and files 30–50 SARs per year. Without automated pattern detection, SAR-eligible transactions typically surface in the compliance queue 15–20 days after the event — inside the 30-day window, but with no margin for review or filing. Connexum surfaces the pattern on the same day the transaction clears.
Card networks operate the authoritative settlement rail and hold cross-participant visibility that no single participant has. Connexum's network profile enforces the VDR 30-day SLA, chargeback-window tracking, SAR pattern detection, and OFAC screening across the full transaction volume — and exports compliance artifacts back to participating acquirers and issuers.
Stuck-transaction detection runs against the full network transaction set. The VDR 30-day report is generated automatically — no manual pipeline audit required.
Card networks carry OFAC screening authority that individual participants don't have. Connexum's OFAC module runs at the network level and exports the freeze event to affected participants without leaking counterparty data.
The network profile is designed for embedded deployment — Connexum runs inside the network's settlement stack and distributes compliance artifacts to participants via the existing network API. No participant-side integration required.
A card network processing 100 million transactions per day operates at approximately 1,160 TPS peak. At this volume, a 1% OFAC false-negative rate is approximately 1 million transactions per day that bypass screening. Connexum runs SDN match at ingestion — before clearing, not after.
Select your participant type, modules, and deployment model. The Deal Composition Engine builds the offer in real time.