Payments partnership · Payments infrastructure · 2026
Nexuz Edge Gateway
An operator platform that wires merchants into a white-labelled NMI gateway, with hosted embed and installed code-pack delivery paths.
- Collect.js tokenization
- Gateway.js 3DS
- NMI
- Server-side amount validation
How it is put together
Context
The partner owns the merchant relationship and the MID issuance. The technical side — gateway account configuration, keys, 3DS and feature flags — was the bottleneck.
The platform is deliberately not merchant-facing. There is no self-signup here; merchants log into the gateway for reporting, and acquisition belongs on the partner's own site.
Problem — A payments partner signing merchants faster than they could be technically onboarded, with each integration configured by hand and no consistent way to keep merchant keys off the merchant's front end.
Approach
How it was built.
- 01
One merchant row, one source of truth
Slug, tokenization key, encrypted security key, allowed domains, currency and amount rules live on a single merchant record. Onboarding becomes data entry rather than bespoke engineering.
- 02
Hosted path for the majority
One embed script served from a Nexuz subdomain. Collect.js tokenizes card fields inside the merchant's own page, 3DS runs through Gateway.js, and the charge posts to a public endpoint that re-validates the amount server-side before it ever reaches the gateway.
- 03
Installed path where hosting demands it
A generated, self-contained code pack running identical charge and response-parsing logic on the merchant's own host with their own key — same behaviour, different deployment.
- 04
Never trust a client-side amount
The amount presented in the browser is treated as a suggestion. The server re-derives and validates it against the merchant's configured rules before authorising anything.
What was built
- Merchant registry with encrypted security keys and domain allow-listing
- Hosted embed script with Collect.js tokenization and Gateway.js 3DS
- Public charge endpoint with server-side amount re-validation
- Code-pack generator for self-hosted merchant integrations
- Sandbox and live operator consoles
Outcome
A single-operator console where a signed merchant becomes a configured, live integration — one embed script for most, a self-contained code pack for the rest, with the private key never leaving the server.
Ownership
Operated internally at dev.nexuz.uk. Merchant private keys stay server-side; the merchant's page never holds them.
Next step
Tell me what the business runs on today.
No pitch deck, no discovery fee. If something off the shelf would genuinely serve you better, I will say so before either of us spends money.
Prefer to write it down? Send a full enquiry with what you are trying to build.