PB Pay Opens Payment Platform to Merchants

PB Pay has opened its online payment-aggregation platform to merchants, giving businesses a new way to accept UPI, cards, net banking, wallets and recurring payments through one integration. The rollout turns the PB Fintech subsidiary’s February regulatory authorisation into a customer-facing product, although the company has not disclosed merchant volumes, pricing, transaction value or launch clients.

Key takeaways

PB Pay’s official website now offers merchant registration, verification, API integration, sandbox testing and production onboarding.
The product lists one-time payments, recurring payments, EMI, UPI AutoPay, e-NACH and standing instructions among its supported methods.
PB Pay received Reserve Bank of India authorisation to operate as an online payment aggregator in February 2026.
PB Fintech approved an investment of up to ₹20 crore in PB Pay in July, subject to business requirements.
The strategic question is whether PB Pay remains internal infrastructure for the group or wins meaningful outside merchants.

Everyone else is reporting that PB Pay has gone live; we are explaining how a regulated payment layer could reduce PB Fintech’s dependence on third-party checkout providers while creating a separate merchant-infrastructure business.

PB Pay merchant rollout: confirmed facts

Item	Confirmed detail	What remains undisclosed
Operator	PB Pay Private Limited, a PB Fintech subsidiary	External merchant mix
Regulatory status	RBI online payment-aggregator authorisation effective February 6, 2026	Any later licence conditions
Merchant journey	Registration, KYC, API integration, sandbox testing and go-live	Average onboarding time
Payment methods	UPI, cards, net banking, wallets, EMI and recurring mandates	Commercial pricing and settlement schedule
Capital support	Up to ₹20 crore investment approved by PB Fintech in July 2026	Amount actually deployed

What PB Pay has actually launched

PB Pay describes a merchant-facing platform rather than a consumer wallet. Its website asks a business to create an account, complete KYC, integrate through APIs, test transactions in a sandbox and then switch to production. That sequence is the clearest evidence that the product is intended to serve operating merchants, not merely process payments invisibly inside Policybazaar.

The listed acceptance options span UPI, credit and debit cards, net banking, wallets, EMI and mandate-based payments. PB Pay also advertises UPI AutoPay, e-NACH, standing instructions on cards and one-time mandates. Those are standard categories in modern payment aggregation; their presence does not by itself establish superior approval rates, lower costs or faster settlement.

The distinction matters because a website going live is not the same as scale. PB Pay has not named anchor merchants, published processed transaction value, disclosed an active-merchant count or released independently audited reliability data. The launch therefore proves product availability and onboarding intent, not market traction.

Why the RBI authorisation matters

PB Fintech told exchanges in February that the RBI had granted PB Pay a Certificate of Authorisation under the Payment and Settlement Systems Act, effective February 6. Times of India, Fortune India and ETBFSI separately reported the authorisation at the time. That licence is the regulatory foundation for today’s merchant proposition, but the licence itself is not new.

An online payment aggregator sits between merchants, customers, banks and payment networks. It lets a merchant offer multiple payment methods through a common technical and commercial relationship. The regulated entity must also handle requirements around merchant due diligence, settlement, security, grievance handling and operational controls.

This is why PB Pay should not be described simply as another checkout page. Its value will depend on how reliably it routes payment attempts, reconciles transactions, supports refunds and disputes, settles funds and helps merchants resolve failures. Those operational details are where payment infrastructure earns or loses trust.

PB Pay gives PB Fintech a deeper payments layer

PB Fintech already owns large distribution businesses in insurance and credit through Policybazaar and Paisabazaar. Payments sit underneath many journeys on those platforms: a customer may pay an insurance premium, renew a policy, service a loan-related product or complete another financial purchase. Owning more of that layer could give the group greater control over checkout design, payment data, reconciliation and service recovery.

Control does not automatically mean that every transaction will move to PB Pay. Group companies have existing relationships, regulated obligations and practical reasons to use more than one provider. A resilient merchant may also maintain multiple payment gateways so that one outage or routing problem does not halt collections.

PB Pay’s larger opportunity is outside the parent group. If independent merchants adopt the platform, the subsidiary could become a distinct business rather than a captive cost centre. That would place it against experienced payment companies competing on pricing, developer experience, acceptance rates, settlement, fraud tools and support.

The ₹20 crore support is a ceiling, not launch revenue

In July, PB Fintech disclosed board approval to invest up to ₹20 crore in PB Pay. The wording is important: “up to” describes a maximum approved commitment, not necessarily cash already transferred on the announcement date. It also says nothing about PB Pay’s revenue, valuation or merchant volume.

Payment aggregation requires technology, security, compliance, banking relationships and working operational capacity. Parent funding can support that build-out, but the commercial test remains external usage and sustainable unit economics. Merchants routinely compare gateway charges, settlement cycles, success rates and escalation quality before concentrating volume with a provider.

What merchants should verify before integrating

A merchant considering PB Pay should request a written commercial schedule rather than infer it from a product page. Key questions include the merchant discount or gateway fee by payment method, GST treatment, settlement timing, reserve policies, refund handling, chargeback processes, international-card support, recurring-payment rules and service-level commitments.

Technical teams should evaluate API documentation, webhook reliability, idempotency controls, sandbox fidelity, reconciliation exports and failure-code clarity. Finance teams should test whether settlement reports match order and refund records. Security teams should confirm responsibility boundaries for card data, credentials and incident reporting.

The official site uses broad marketing language about security and low-friction payments. Those statements should be validated through contracts, technical documentation and live performance data. Lapaas Voice has previously examined how a new Viyona UPI switch adds infrastructure competition and how Zerodha’s merchant-banking move deepens its financial stack; in each case, regulatory entry is the starting line rather than proof of execution.

Businesses should also decide how much traffic to direct to a new provider during an initial rollout. A controlled launch can begin with one payment method, a limited customer segment or a small share of checkout traffic while the merchant measures failures, refunds and reconciliation quality. That approach does not imply distrust; it recognises that a payment system touches revenue, customer support and accounting at the same time.

PB Pay’s affiliation with a listed financial-technology group may help prospective merchants assess ownership and governance, but group backing cannot substitute for product evidence. Procurement teams still need clear escalation contacts, data-retention terms, business-continuity arrangements and an exit plan that lets them move volume without disrupting customers.

What evidence would prove traction

The next meaningful disclosures would be named independent merchants, active-merchant count, processed value, payment success rates, settlement performance and the share of volume originating outside PB Fintech. None of those figures is available in the public materials reviewed for this article.

Evidence of repeat usage would matter more than registrations. Merchant onboarding can be easy while production volume remains small. Conversely, a limited number of high-volume merchants can make processed value look large without proving broad product-market fit.

PB Pay is now a usable merchant proposition backed by an RBI-authorised entity, but its competitive significance will be determined by operating data that PB Fintech has not yet published: real merchants, sustained payment volume, reliability and economics.

Frequently asked questions

What is PB Pay?

PB Pay is a PB Fintech subsidiary authorised by the Reserve Bank of India to operate as an online payment aggregator. Its merchant platform offers integration and acceptance for multiple digital payment methods.

Is PB Pay the same as Policybazaar?

No. PB Pay is a separate subsidiary in the PB Fintech group. Policybazaar is the group’s insurance-distribution platform, while PB Pay provides payment-aggregation infrastructure.

Which payment methods does PB Pay support?

Its official product site lists UPI, cards, net banking, wallets, EMI and several recurring or mandate-based methods. Merchants should confirm precise availability and commercial terms during onboarding.

Has PB Pay disclosed how many merchants use it?

No public merchant count, transaction value or named launch-client list was found in the materials reviewed. The current evidence establishes availability, not scale.