What are the options for adding embedded payments to a platform?
There are three. Referring merchants to a third party is fast but hands over the experience and the economics. Building in-house keeps control but brings licensing, certifications, PCI scope and connector maintenance for years. Launching on white-label infrastructure keeps your brand, checkout, data and merchant relationship, while the infrastructure and its compliance load run on NORBr.
In detail
There are three paths, and they differ on what you keep and what you carry.
Refer merchants to a third party
This is the fastest option. A payment provider serves your merchants directly, and you may receive a referral fee. You also hand over the checkout experience, the payment data and most of the economics, and your merchants deal with another brand for part of their business.
Build in house
Building keeps control, but brings licensing, scheme certifications, PCI scope, fraud tooling and connector maintenance. These take years to put in place and need constant upkeep, and they pull your engineers away from the product your merchants chose you for.
Launch on white-label infrastructure
You keep your brand, your checkout, your data and your merchant relationship, while the infrastructure and its compliance load run on NORBr. Provider integrations, certifications and connector maintenance stay on the infrastructure side. Online and in-store run on one stack, so card-present is a setting rather than a second system.
The useful question is narrower than build versus buy: what must stay yours, and what should never have been your job. Your brand, merchant relationship and economics belong in the first group. Licensing, certifications and connector maintenance belong in the second.