Skip to content

Machine integration

Payments & POS Integration: Card and UPI Collection at Billing Counters

Take payment at the front desk or pharmacy counter and have it recorded against the right bill, without keying amounts twice.

In short

Payments integration connects card POS terminals and UPI QR devices to billing in DevOrbital HMS, so the amount due is sent to the device and the payment outcome is recorded on the bill. It is meant to reduce re-keying and make reconciliation by payment mode easier. Each terminal is assessed and enabled independently, and manual payment entry remains available.

Device types

What can be connected

  • Card and POS terminals
  • UPI QR terminals and soundboxes
  • Dynamic QR display screens
  • Mobile and handheld payment terminals
  • Pharmacy counter payment devices
  • Self-service payment kiosks

Data flow

What the integration does

Amount goes to the terminal

Where the terminal supports it, the bill total is sent to the device so staff do not type the amount a second time.

Payment status returns to the bill

The outcome, such as success or failure, and a reference are recorded against the bill, so the receipt matches what was collected.

UPI QR payments are matched

For QR-based payments, a reference or dynamic QR per bill helps tie each payment to the right patient and invoice.

Payment-mode splits for reconciliation

Collections by cash, card, UPI and other modes feed Reports & Analytics, so the daily cash book can be checked against terminal settlements.

Multiple counters and units

OPD, IPD discharge, emergency and each pharmacy unit can use their own terminals, with collections reported separately.

Interfaces

Commonly used protocols

Which interface applies depends on the device. We assess each one during onboarding — nothing here is a promise that a specific model works.

Terminal or acquirer API

Commonly offered by payment providers so a billing system can push an amount and receive a status; availability depends on the provider and device.

Dynamic QR generation

Commonly used for UPI: a unique QR is generated per bill so payment can be matched automatically, where the provider supports it.

Manual reference entry

A fallback where staff enter or select the payment reference when no direct link is available.

How we scope it

From first conversation to go-live

  1. 1

    Counter and device discovery

    We list where payments are taken and which terminals and payment providers you use today.

  2. 2

    Interface specification

    We confirm what your provider or terminal offers, whether an API, dynamic QR or neither, and what the HMS should record.

  3. 3

    Test in staging

    We test amounts, successes, failures and cancellations in a test setup, using the provider's test facilities where available.

  4. 4

    Go-live per counter

    Terminals are switched on one counter at a time, with manual payment entry as a fallback.

  5. 5

    Support

    New terminals, provider changes or counters are handled as separately scoped work.

Benefits

Why connect devices at all

Less re-keying

Amounts entered once reduce mismatches between the bill and the terminal slip.

Easier daily reconciliation

Payment-mode splits and recorded references make end-of-day checks faster.

Clearer receipts

Each receipt reflects what was actually collected and how.

Counter-by-counter rollout

You can start at the pharmacy or front desk and extend later.

In practice

An illustrative example

Illustrative scenario · not a customer story

A discharge payment by card

Billing executive

The family is ready to settle the final bill. The billing executive confirms the total, sends it to the card terminal, and the family taps their card. The terminal returns success and the reference is recorded on the bill. The receipt prints with the correct payment mode. At the end of the day, the finance manager compares the card total in the report with the terminal settlement and finds them aligned. This is an illustrative composite, not a real hospital.

Why connect payment devices to hospital billing?

In a busy billing counter, the same amount is often typed twice: once into the billing screen and once into the terminal. A slip in either place creates a mismatch that someone must trace later. Linking the two means the amount is entered once, and the payment outcome is recorded on the bill.

Hospital billing software in DevOrbital HMS already records payment mode and provides payment-mode splits through Reports & Analytics. The integration adds the device-level reference that makes those splits easy to verify. For the leakage angle, see reduce billing leakage and our article on reducing hospital billing leakage.

What about security and card data?

Payment card handling is regulated, and responsibility sits primarily with the terminal and your payment provider. A well-designed integration sends amounts and receives outcomes and references without the HMS handling card details. We will confirm exactly what data flows in each direction for your provider during scoping, and you should check requirements with your payment partner.

Counters are not only at the front desk. Pharmacy sales can use their own terminals through the pharmacy management system, and insured patients with a co-payment can pay the balance through the same device while the claim runs through Insurance & TPA management. Compatibility depends on the terminal and provider and is assessed per device. See also barcode and QR scanning for other counter workflows.

FAQ

Frequently asked questions

It depends on the terminal and your payment provider, because a direct link needs an API or similar option. Each device is assessed individually. If a direct link is not available, payments can still be recorded manually with a reference.

The design intent is that card details stay with the terminal and payment provider, and the HMS records amount, outcome and reference. We confirm exactly what flows during scoping.

Where your provider supports dynamic QR or a payment API, payments can be matched to the bill. Otherwise a reference is recorded manually.

Yes. Each pharmacy unit has its own billing, and terminals can be set up per counter, with collections reported separately.

Yes. Manual payment entry remains available so billing is never blocked by a device.

Keep exploring

Related reading and systems

Read this next

All articles →

Tell us about your equipment

Share the devices you want connected and we will tell you what it takes — each one is scoped and enabled independently.