The Connexum Platform

Two products. Two distinct problems.

Connexum addresses obligation compliance inside the card rails. Connexum Merchant addresses operational execution on the merchant side. Different audiences, different capabilities, different obligations.

Connexum

Settlement Control Plane

A six-stage pipeline that enforces every regulatory SLA inside the card settlement network — automatically, in real time.

For: Acquirers · Processors · Issuers · Card Networks
Detection modules10
Pipeline stages6
100K transactions2.26 s
Backoffice connectors22
Tests passing120 / 120

Reg E demands provisional credit within 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 — and manual reconciliation cannot keep up.

The regulation is the configuration. Every module is wired directly to its statutory citation. No parameter to tune, no threshold to calibrate — the obligation defines the behaviour.
Reg E · §205.11

Provisional credit clock

10-business-day dispute clock enforced per dispute, per participant. Starts automatically on intake.

BSA · 31 CFR §1020.320

SAR trigger & case file

Citation-anchored SAR detection. Case file auto-generated when threshold is met. No human in the detection loop.

OFAC · 31 CFR Part 560

SDN screening

Every settlement event screened. Same-day freeze on SDN match. Zero-tolerance on timing.

Visa VDR / MC MDR

Pipeline SLA enforcement

Stuck-transaction detection at 30 days. Batch reconciliation proof at 45 days. Both enforced without configuration.

PCI DSS · Req 10.7

Audit-log retention

Chain-of-custody written to an append-only ledger. Subject to independent attestation.

All four participants

Zero information leakage

No participant infers any counterparty detail from Connexum outputs. Signals are aggregate and one-way.

Connexum Merchant

Operations Execution Engine

Reads what the merchant already emits, finds where margin and time are leaking, and executes the fix — inside authority the owner granted once.

SMB Merchants — Backoffice Automation · Revenue Retention · Improved Supplier Margins
Execution modules32 / 32
Pipeline stages9
Industries supported11
Native vendor adapters5
Tests passing1,844 / 1,844

An owner with no staff cannot act on a queue of twenty correct findings. An advisory tool that hands them one is a new job, not a solution. Connexum Merchant executes. It does not advise.

Every figure traces to the merchant's own statement. No interchange tables, no published card-network rates, no industry averages. If it isn't on their ledger or processor statement, the engine doesn't use it.
Fulfilment

Stuck-order detection

Point-in-time forecast. Validated: 84% recall · 95% precision at conservative thresholds on real marketplace data.

Returns

Refund & return control

Ranked watchlist on breadth signal. Never asserts a product is the cause — wrong 93% of the time on real data.

Receivables

A/R escalation & collections

Unpaid invoices never enter the card rails. Module reads the ledger directly and escalates inside granted authority.

Payments

Failed card recovery

Reads processor response codes. Executes retry or card-update sequences within the authority ladder. No interchange tables used.

Payments

Fee validation & MCC correction

Identifies billing disputes and MCC mismatches against the merchant's own processor statement. Every figure traced to a line item.

Native adapters

QuickBooks · Square · Stripe · Shopify · Jobber

Five real adapters across ledger, POS, payments, eCommerce, and field-service scheduling. Pre-qualified before each installation.

One connection between them

The settlement plane feeds the merchant lane.

Connexum Merchant reads the SCP's merchant lane over HTTP — chargeback evidence, reconciliation position, and deviation signals flow directly into the execution engine. The products operate independently. The data contract is the only connection between them, and it crosses no silo boundary.