Do merchants have to change their integration to use Ecommpay?

Short answer

No. Merchants that already process through NORBr keep the same API and checkout. The operator activates Ecommpay in their payment stack and sets the routing rules, and stored cards remain usable through tokenization, so shoppers do not have to enter their card again when a payment is routed to Ecommpay.

In detail

No. Merchants that already process through NORBr keep the same API and checkout. The operator activates Ecommpay in their payment stack and sets the routing rules, and stored cards remain usable through tokenization, so shoppers do not have to enter their card again when a payment is routed to Ecommpay.

Nothing changes on the merchant side

Merchants that process through NORBr use one API and one checkout, whatever the providers behind them. When the operator activates Ecommpay for a merchant and routes traffic to it, the merchant's integration is untouched. The same calls, the same hosted page, the same webhooks.

Stored cards

  • Cards saved by the merchant's customers are held as universal tokens in the NORBr Vault, pointing to network tokens where available.
  • A payment routed to Ecommpay uses the same token; the shopper does not re-enter the card.
  • Subscriptions keep billing without interruption.

What the operator does

Activates Ecommpay in the merchant's payment stack, sets routing rules, and watches the first transactions in reporting. If the operator wants to test before committing, it can route a share of traffic to Ecommpay and compare approval rates and costs with the current provider. The merchant may not even be told, unless the operator chooses to; from the merchant's perspective, payments simply continue. This is what makes a provider change a routing decision rather than a migration.

Still have a question?

Our team walks you through the platform with your use case on the table.

Book a demo