Does an operator need its own developers to activate a new provider on NORBr?

No. Provider integrations are built in Connector Admin, certified and maintained as part of the global payment network. Once a provider is connected, the operator activates its methods per merchant and decides with routing rules where it applies. The operator's developers stay focused on its own product and systems.

Activation is configuration

Provider integrations are built in Connector Admin by NORBr's integration team, certified, and maintained as part of the global payment network. Once a provider is connected, an operator activates it by entering its credentials, enabling the provider's methods per merchant in Payment Stack & Activation, and setting routing rules that decide where it applies. None of that requires code.

What the operator's developers do instead

• Integrate the operator's own product with the platform once, through the API or the hosted checkout.
• Build the operator's own features on top of the data: dashboards, workflows, integrations with its software.
• Nothing when a provider is added, changed or replaced.

What this changes

Adding a provider becomes a commercial and operational decision rather than an engineering project. The operator signs with the provider, completes its onboarding, receives credentials and activates. The time from decision to first transaction is measured in days, and depends mostly on the provider's onboarding. Operators that have lived through provider integrations in-house, with their certification cycles and maintenance, usually cite this as the main reason to move to white-label infrastructure.