Can an operator choose which merchants get Indian payment methods?

Short answer

Yes. Once PayU is activated in the operator's NORBr environment, it is enabled per merchant and per payment method. The operator decides which merchants offer UPI, netbanking or Indian cards, how those methods are presented at checkout and how they are routed, without a new integration project for each seller.

In detail

Yes. Once PayU is activated in the operator's NORBr environment, it is enabled per merchant and per payment method. The operator decides which merchants offer UPI, netbanking or Indian cards, how those methods are presented at checkout and how they are routed, without a new integration project for each seller.

Per merchant and per method

Once PayU is activated in the operator's environment, with the operator's own agreement and credentials, its methods are enabled per merchant account. The operator decides which merchants offer UPI, netbanking or Indian cards, and in which combination. A merchant with no Indian customers never sees them.

What the operator controls

  • Which merchants are enabled, and when.
  • How the methods appear at checkout: order, labels, markets where they show.
  • Routing: Indian traffic to PayU, other traffic to other providers.
  • Pricing to the merchant for these methods.

Why no new integration per seller

The integration with PayU is done once on the platform. Each merchant activation is configuration, and the merchant's checkout picks up the new methods without a code change. For an operator whose merchants sell to India, this means offering local methods on the first day of a merchant's interest rather than after a project. Reporting shows Indian volume per merchant and method, which tells the operator where the activation paid off and which merchants to approach next.

Still have a question?

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

Book a demo