What stays my responsibility once the infrastructure is in place?
The commercial relationship with your merchants, the onboarding decisions you make about them, the pricing you set, the provider relationships you choose to hold directly, and the support you offer under your brand. The infrastructure covers the platform, the connections and the operational surfaces your merchants work in.
In detail
The parts that define your offer stay with you. The infrastructure and its compliance load move to NORBr.
What stays yours
- The commercial relationship with your merchants, under your name and your terms.
- The onboarding decisions you make about each merchant.
- The pricing you set for your merchants and the margin you keep.
- The provider relationships you choose to hold directly.
- The support you offer, under your brand.
What runs on NORBr
The platform itself, the connections to acquirers and payment methods, scheme certifications, PCI scope, connector maintenance and the operational surfaces your merchants work in, from the console to hosted payment pages. These keep running after go-live, including scheme updates and connector changes.
Drawing the line this way lets your team focus on what makes your offer different. Your engineers stay on your product instead of maintaining payment plumbing, and your operations team works on merchants rather than integrations. The configuration of the platform, such as domains, themes, menus, routing rules and roles, is in your hands through the Console, so you shape the experience without carrying the infrastructure underneath it. NORBr stays invisible in your merchant relationship and never sells to your merchants.