Payments

Stripe

Getting paid shouldn't mean chasing a check. Nexus can put any invoice in front of a client as a Stripe-hosted payment page, or put a recurring contract on autopilot with ACH or card auto-charge.

How it works

Push any Suite invoice to Stripe as a customer-payable hosted invoice with its own hosted payment URL
Map a recurring contract to a Stripe Subscription so Stripe auto-charges on schedule (ACH or card) — the payment method is collected through a Stripe-hosted Setup Session, so card and bank details never touch the app
A signature-verified Stripe webhook records paid invoices back into Suite (with a dedupe window against duplicate/replayed events) and reflects subscription cancellations and failed-payment notices
The app only configures and authorizes billing — Stripe is what actually moves the money; there is no charge or capture logic in this codebase

Live once a Stripe secret key is configured — real Invoice/Subscription/webhook calls; unconfigured tenants see clearly marked simulated IDs instead of a broken flow.

Other integrations

Syncro

Moving off Syncro doesn't have to mean a hard cutover date. Nexus pulls your existing Syncro tickets in on a schedule so both systems can run in parallel until you're ready to switch.

FortiGate, Omada, Meraki & UniFi

Whatever network gear you've already standardized on across client sites, Nexus folds its monitoring into the same console as everything else — no separate vendor portal per brand.

Jamf

For clients on Apple hardware, Jamf-managed devices show up in the same unified console as everything else Nexus manages — one pane of glass across a mixed fleet.

See Stripe inside Nexus.

Join the design-partner cohort and we'll show you exactly how your existing stack folds into the console.