Skip to main content
All work

In partnership with Omnipay Solutions · 2026

Nexuz Edge Gateway

An operator platform that wires merchants into a white-labelled card gateway, with hosted and installed delivery paths.

Pre-releaseBuilt and rehearsed end to end in test mode. The first live merchant charge is the next step.
  • Card tokenisation
  • 3-D Secure
  • Server-side validation
  • Operator console
Visit edge.nexuz.uk
The Nexuz Edge operator console sign-in screen shown in a NEXUZ browser frame

Private platform · sign-in only · pre-release

The brief

What had to change.

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 credentials off the merchant's front end.

Built with Omnipay Solutions as the payments partner: they own the merchant relationship and the account issuance. The technical side (gateway configuration, credentials, authentication and feature flags) was the bottleneck.

The platform is deliberately not merchant-facing. There is no self-signup; acquisition belongs on the partner's own site.

Approach

How it was built.

  1. One merchant record, one source of truth

    Identifier, credentials, permitted domains, currency and amount rules live on a single merchant record. Onboarding becomes data entry rather than bespoke engineering.

  2. Hosted path for the majority

    One managed integration drop-in. Card details are tokenised inside the merchant's own page and never touch our storage, strong customer authentication runs before capture, and the charge is validated server-side before it reaches the gateway.

  3. Installed path where hosting demands it

    A generated, self-contained package running identical charge and response handling on the merchant's own host with their own credentials: same behaviour, different deployment.

  4. 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

5 parts, one system.

  • Merchant registry with encrypted credentials and domain allow-listing

  • Hosted integration with card tokenisation and strong customer authentication

  • Charge handling with server-side amount re-validation

  • Package generator for self-hosted merchant integrations

  • Separate test and live operator consoles

What it will change

Built so that bringing a signed merchant live is data entry on one record rather than a bespoke engineering job: a hosted path for most merchants, a self-contained package for the rest, and card credentials that never leave the server.

Ownership

Operated internally by Nexuz in partnership with Omnipay Solutions, who own the merchant relationship. Merchant credentials stay server-side; the merchant's page never holds them.

Available as a service

Card processing, placed and integrated.

The same gateway placement built here is available as a standalone service line for other platforms. We source the merchant account, configure the gateway, and build the integration into your checkout, with one party accountable for the whole path.

See the service line

Next step

Tell us what the business runs on today.

No pitch deck and no discovery fee. If something off the shelf would serve you better, we will say so before either of us spends money.

Or email zbarnett@nexuz.uk