Does a merchant need a separate billing provider to sell subscriptions on NORBr?
No. The Subscriptions module runs inside the operator's platform and is switched on per merchant account. Offers, rebills, retries, pauses and cancellations run on the acquiring connections already in place, so the merchant integrates no standalone billing engine and signs no new acquiring contract.
In detail
No. The Subscriptions module runs inside the operator's platform and is switched on per merchant account. Offers, rebills, retries, pauses and cancellations run on the acquiring connections already in place, so the merchant integrates no standalone billing engine and signs no new acquiring contract.
Billing inside the platform
The Subscriptions module is part of the operator's platform. When it is switched on for a merchant account, the merchant creates offers, sends customers to checkout with an offer ID, and the platform handles the first payment, the rebills, the retries, pauses and cancellations. The charges run on the acquiring connections the merchant already uses.
What the merchant does not need
- A standalone billing engine to integrate and keep in sync.
- A new acquiring contract for recurring payments.
- A separate vault for stored credentials; network tokens and stored cards stay on the platform.
- A second reporting tool for recurring revenue.
Why this matters for operators
Billing engines sold separately take a share of the merchant relationship and of the data. When subscriptions run inside the operator's platform, the operator keeps both and can price the module as a service. Merchants get one place for one-off and recurring payments, one transaction record, and one reconciliation. The module is white-label, so the merchant sees the operator's brand, as everywhere else on the platform.