Can I move from referral to embedded payments without rebuilding my product?
Yes. Your merchants start paying inside your product, under your brand, through a checkout and interface you configure on NORBr rather than code from scratch. Card-present runs on the same stack as online, so in-store becomes a setting instead of a second system. Your engineers keep shipping your product while the payment infrastructure runs underneath.
In detail
Yes. Moving from referral to embedded payments does not require rebuilding your product. Your merchants start paying inside it, under your brand, through a checkout and an interface you configure on NORBr rather than code from scratch.
The configuration covers what your merchants see: your domains, your theme, your menus and your hosted payment pages. Payment methods and providers are activated through contracts on the platform, and routing rules are set in the Console. Your existing product stays as it is, with payments added as a capability inside it.
How the transition usually works
- Set up your program structure and branding in the Console.
- Connect the providers and payment methods your merchants need.
- Integrate the checkout into your product and test in sandbox.
- Open production access once the program is cleared for live processing.
Card-present runs on the same stack as online, so adding in-store payments later is a setting rather than a second system. New methods and markets follow the same logic.
Your engineers keep shipping your product while the payment infrastructure runs underneath. The merchants you used to refer elsewhere now stay inside your platform, and the payment revenue they generate becomes yours.