Project

General

Profile

Actions

Feature #626

open
MN AL

Spike: integrate the PhonePe QR and Indian Bank sound box for payment collection and confirmation in Billing

Feature #626: Spike: integrate the PhonePe QR and Indian Bank sound box for payment collection and confirmation in Billing

Added by Medha N. 16 days ago. Updated 3 days ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
NSS - NSS December 2026
Start date:
10/28/2026
Due date:
% Done:

0%

Estimated time:
Resolved By:

Description

Module: Billing → Payment collection (OPD registration, Quick Bill, pharmacy, radiology)
Environment: NSSH
Type: Spike / Research → Enhancement
Priority: P2

Background
NSSH collects UPI payments through two channels:

A PhonePe QR code.
An Indian Bank sound box, a QR plus a speaker that announces payments.

At the moment, staff hear or see the payment and then mark the bill as UPI paid by hand. There’s no automatic link between the payment and the bill, which risks wrong entries, missed payments and reconciliation gaps.

Goal
Find out how Clinq can collect payments and confirm them automatically against the bill for both channels.

What to explore

  1. PhonePe

Dynamic QR: PhonePe has an offline Dynamic QR solution. Clinq generates a QR for each bill with the exact amount, shows it on screen or the billing counter display, and gets the payment status by status check or callback. That marks the bill paid automatically. This is the best option.
Integrated Static QR: if the hospital keeps its existing printed PhonePe QR, check whether PhonePe’s integrated static QR flow gives transaction notifications or a transaction list that can be matched to bills by amount and time.
Confirm what NSSH’s PhonePe merchant account supports (PhonePe Business vs a PG or offline merchant account), and which credentials and onboarding are needed.
Reuse the PhonePe gateway work already in progress, including the callback handling and status check.

  1. Indian Bank sound box

No public developer API was found for the Indian Bank sound box. It looks like a closed device for payment announcements only.
Ask Indian Bank, through the hospital’s relationship manager, about:
Merchant APIs or webhooks for UPI credits to the hospital’s account or VPA.
A transaction report or statement export (CSV or SFTP) for daily reconciliation.
Whether the sound box’s VPA can be used to create dynamic QRs or collect requests.
Fallback: keep manual confirmation, but require a UPI transaction reference (UTR) to be entered, and reconcile against the bank statement.

Proposed flow (target)

The bill is created and the cashier selects UPI.
Clinq shows a dynamic QR for the bill amount, through PhonePe.
The patient pays, and the sound box or the PhonePe app announces it.
A PhonePe callback or status check confirms the payment, and Clinq marks the bill Paid automatically and stores the transaction ID and UTR.
If there’s no confirmation within the timeout, the screen shows “Pending” with a manual recheck, and nothing is marked paid automatically.
A daily reconciliation report matches bills to PhonePe and Indian Bank transactions.

Deliverables of the spike

A comparison of PhonePe Dynamic QR, PhonePe Static QR and Indian Bank: APIs available, cost, onboarding, effort.
Indian Bank’s answer on API or report availability.
A recommended approach and a rough effort estimate.
Follow-up implementation tickets.

Open questions for the hospital

What type of PhonePe merchant account do they have, and who holds the credentials?
Do both channels settle into the same bank account?
Do they want a QR displayed on a screen, a customer-facing display, or only the existing printed QR?
Who handles reconciliation (accounts or front desk), and how often?

RH Updated by Roshni Harish. 14 days ago Actions #1

  • Subject changed from Payment integration: PhonePe QR code and Indian Bank sound box to Spike: integrate the PhonePe QR and Indian Bank sound box for payment collection and confirmation in Billing
  • Description updated (diff)
  • Assignee set to Annet L.

AL Updated by Annet L. 3 days ago Actions #2

  • Target version set to NSS December 2026

Not part of the NSS release on 12 Nov. Moved to NSS December 2026.

Actions

Also available in: PDF Atom