BharatX

If a client asks you about BharatX, they are not asking for a ledger recommendation. They are asking whether their consumer app should sit credit inside checkout. BharatX is white-labelled embedded credit infrastructure for India: APIs that power Buy Now Pay Later, Pay in 3 / Pay in X installments, embedded credit lines, Try and Buy, and Postpaid journeys on websites and apps that already own the customer relationship. It is listed here under fintech for a reason. CAs touch it when they advise D2C, e-commerce, or fintech clients, not when they close GST for a trading firm.

The product story is API-first. Payment gateways and consumer apps integrate; the credit experience can stay white-labelled so the brand on screen remains the merchant’s. Platforms are web-facing from the integrator’s side. Pricing is custom and subscription-shaped on paper, but the public plan table is essentially “Contact vendor for pricing” because you are buying credit rails, not seats for articled assistants. Founded in 2019, BharatX raised a $4.5M seed from Y Combinator, 8i Ventures, Multiply Ventures and Soma Capital. By its own account, Pay in 3 / Pay in X reached 1,000+ brands directly and through payment-gateway partners. In February 2025, super.money acquired BharatX, with the team collaborating to expand UPI-based credit offerings. That acquisition is not trivia for your file note. Contracting entity, brand name on invoices, and which API docs still apply can drift after a deal like that.

Your value in the room is translating checkout features into accounting events. When a customer chooses Pay in 3, the sale still needs a clean GST invoice for the goods or services. Settlement from the credit provider may lag plain UPI capture. Refunds, EMI cancellations, chargebacks, and failed collections each need an owner in the books. Map the funnel with the client’s product and finance leads: where credit is offered, what the merchant settles for, how delinquency is reported, and who owns KYC outcomes. If white-label makes the journey look native, auditors and tax officers still need documentation that the underlying sale and any finance charges were treated correctly. ITC questions, if they arise at all, depend on whether the merchant remains the supplier of the goods and how any fee invoices are drawn — do not assume; ask for sample settlement packs and fee invoices before go-live.

Commercial terms for embedded credit often blend technology fees, revenue share, and risk participation. Separate the SaaS-like API fee from lending economics so the client does not book a partnership as pure software expense when they are sharing credit risk. Flag language that makes the merchant look like a lender without saying so. Cash forecasting should treat settlement lag as its own line, not as “same as UPI, mostly.” For advisory clients who already run consumer apps, BharatX (inside the super.money story) is one India-native option on an embedded-credit shortlist alongside whatever their payment gateway already bundles. Your job is not to pick the coolest BNPL logo. Your job is to insist that conversion uplift is measured against reconciliation cost, dispute volume, and disclosure clarity.

Data sitting inside checkout is another pressure point. A third-party credit API sees customer and transaction signals at the moment of purchase. Ask how that data is retained, who is the data fiduciary for which fields, and what the merchant must tell customers in plain language. Word the privacy questions the way a board would: where does personal data go, for how long, and can the client pull an export if they unwind the integration. Pin versioned integration terms on the engineering side and the invoicing entity on the legal side, especially after the acquisition, and re-check both every few months. Acquired products get renamed; APIs get versioned; support channels move.

BharatX falls away quickly when the brief is expense cards, GST reconciliation, practice management, or any workflow without a consumer checkout. It is not an accounting tool. It will not file GSTR-1, match GSTR-2B, or draft a notice reply. Keep it on a fintech-advisory shelf. When you join a vendor call, bring a one-page list of revenue-recognition, settlement, and control questions. The pitch deck will celebrate conversion. Someone still has to write the memo that explains how those installments hit the books.