Your platform.

Your brand.

The infrastructure is ours. Your brand is yours.

Launch a branded payment platform with your own domains, menus, scopes, roles and payment stack. Your users experience everything under your brand. The infrastructure layer underneath is ours.

Book a demo
Everything you need. Already built.

A payment platform is not just an API. It needs white-label branding, configurable menus, multi-layer scope hierarchies, role-based permissions, hosted payment pages, provider contract management, event delivery, operational reporting and audit trails. NORBr provides every one of these as configurable,  production-ready infrastructure.

Custom domains and branding

icône

Configurable menus per scope

icône

Role-based permissions

icône

Multi-layer scope hierarchy

icône

Hosted payment pages

icône

Audit logs and event delivery

Configure, not construt.

Brand the interface
Your merchants log in to a console that carries your brand. Custom domain. ‍Your themes. Your hosted pages. They never know there's a layer underneath.
Control who sees what
Expose capabilities by role, scope, market or client type. Read-only by default when a user can inspect but not edit. Explicit flows when changes matter.
Govern without developing
Rename menus, hide modules, configure hosted pages and set domain rules from the Console. No engineering work required for operational changes.

However you operate, model it exactly.

Your business has a shape. NORBr takes exactly that shape. Payment operators come in many shapes. You might resell payment services under your own brand, embed payments inside your software, act as the master merchant for a marketplace, or run an ISO on your own gateway. NORBr models each of these with the same scope levels, and TeamSpaces sit on top for the way your teams actually work. Find the one closest to yours.

You power a franchise network
One of your merchants is a franchise brand selling across many countries, online and in store.
You resell payments under your brand
You take payment infrastructure and resell it as your own product. The operators you serve do the same with theirs, one level down, and their merchants sit below that. At every level, the layer beneath carries the brand above it: a merchant sees the operator it signed with, that operator sees you, and the infrastructure behind you stays out of sight. You run the whole cascade. Each party works within its own layer.
You embed payments in your software
You sell software, and payments are a feature inside it. The businesses using your software pay through it as if the capability were built in house. You configure the payment side from one place, across every account, and your engineering team stays on the product. The structure stays as flat as you need: use the levels that fit, skip the ones you don't. Payments feel native, and the infrastructure stays out of view.
Your ISO, your own gateway
You are the master merchant, and your sellers transact under you. You onboard them, you own the merchant relationship, and you move their payouts, all from one structure. Sellers join in the hundreds, each as its own account, grouped into the cohorts you actually manage. Each seller works inside its own account and sees only its own activity. You see the whole marketplace, and the settlement that flows across it.
You are the master merchant
You run an ISO, and you built your own gateway on top of the infrastructure. You bring merchants onto acquiring relationships at better terms, and each merchant keeps its own account and its own MID. The structure stays flat and wide, one entry per merchant, however many you sign. You provide the technology and the routing. The acquiring bank carries the funds, and you carry the relationship.
Built to last. On your terms.
Infrastructure decisions are long-term commitments. The provider you choose today shapes what you can offer in three years. NORBr is built on a decade of payment operations expertise, certified annually by independent auditors, and designed to grow with your platform at any scale. Provider-agnostic by design. Modular by architecture. The stack your merchants run on is the same one enterprises trust for millions of transactions a month.
10+
years payment expertise
NORBR
40+
certified providers
NORBR
PCI DSS
AOC 2026–2027
NORBR

From configuration to live platform.

Define scopes
Set up MPM, PM, Companies, Merchant Accounts.
Configure brand
Apply domains, themes, menus and hosted UI.
Assign access
Grant roles, permissions and TeamSpaces.
Activate payments
Connect providers through governed contracts.
Go live, stay invisible
Your merchants run under your brand. NORBr remains invisible.
Depth your competitors can't ship.
Branding a payment platform is the easy part. The hard part is offering each merchant an experience that matches its business: its team structure, its terminology, its reporting standards, its finance processes. You configure that depth without writing a line of code for it. How access to all of it is governed lives in Platform Operations & Security.
Views your merchants configure themselves
Your merchants build the views they need from any object table in your platform: transactions, orders, contracts, tokens, operations. They choose the columns, the filters, the sort order. They save those views and share them across their own teams. You ship the canvas. They make it theirs.
Internal nomenclature, respected
Column names, field labels and view titles can be renamed to match each merchant's internal nomenclature. A merchant that calls its transactions "operations" sees "operations". A merchant that calls them "tickets" sees "tickets". No glossary mismatch between your platform and their internal language.
Column formats tuned to the last detail
Every column type carries its own display options. Dates, amounts, currencies and statuses can each be rendered the way your merchants need to read them. Numeric columns can carry a footer calculation, like sum or average, directly inside the table. The data does not change. The way each merchant reads it does.
Saved searches attached to the views that need them
Filter combinations get complex fast. Your merchants build a search form once, name it, and attach it to the view where it belongs. The search becomes part of the view, not a one-off query lost at the next refresh. Reusable. Reproducible. Shared with the right people when needed.
Private, shared or team-wide. Every view has its audience.
Every view your merchants create has a visibility rule. Private when it serves one person's workflow. Shared with named colleagues when it supports a specific collaboration. Made available to a whole team when it should become standard practice. The view system carries its own permission model, decided by the merchant.
Dashboards composed from the widgets that matter
Each merchant composes its own dashboards. They pick the visualization that fits the indicator, place it, resize it, group it with others. The same metric can live in different dashboards under different forms, depending on who is looking at it. Operational reality drives the layout, not the platform default.
Exports that match their processes
Every view your merchants build can become an export. Column names, field order, file format and filename pattern all carry over. The CSV that lands in their finance system matches their accounting standard from the first run. No reformatting step. No second-class report builder.

The best infrastructure is the one
your merchants never notice.

Discretion isn’t a feature we sell. It’s how the product is built.

Book a demo