Change the engine.

Keep the front.

You upgrade connector by connector, live the whole way through.

Your merchants keep the interface, the login and the reporting they already use. Underneath, each provider moves onto NORBr one connector at a time, with old and new running in parallel until you switch. Every merchant stays live, and the cutover happens on your schedule.

Book a demo

Migrate connector by connector.

A platform migration usually arrives as a single cutover date and a held breath. Here it runs as a controlled sequence, one connector at a time, with each step confirmed before the next begins.

Your merchants stay live throughout.

While the engine changes underneath, your merchants keep working as usual. They log into the same portal, on the same domain, with the same reporting they rely on, and every session stays live from the first connector to the last. The migration happens on your side, so their day continues on theirs.

Enrich your catalog through the API.

If your front already works, keep it. Connect to NORBr through the API and add new payment methods and acquirers to your catalog as configuration, not as a project. Local methods like iDEAL, Wero, PIX or Bizum become available to your merchants the moment you switch them on, so your offer grows on the day you decide.
→ Adding acquirers and methods and routing across them is the subject of Payment rails.

Offer a new white-label front.

When you want to give your merchants more than methods, adopt the white-label environment. Apply your brand down to the component, and shape the interface, the flows and the reporting your merchants see every day. It is the most customizable environment on the market, so the experience carries your identity, not a template. Your merchants get a front that sets you apart, and you own the relationship end to end.

→ Shaping that branded environment is what the White-Label Platform makes possible.

Change the engine.

Keep the front.

Modernize the business your merchants already trust.