What shipped in September 2026

Every cancelled payment carries the reason it was cancelled: who cancelled a link, a card machine decline or time-out in the machine's own words, a payment request that never reached the terminal, or a pre-authorisation released. It shows under the status in Payments, in the payment detail, in the CSV export and in the API. Older cancellations have been filled in where the record allowed.

Payments started from the portal, the Card machine page or an integration such as Salesforce now print the usual merchant and customer receipts on the terminal, exactly like a payment keyed on the machine. The emailed receipt still goes out as well. Connectors on 1.8 or later pick this up automatically.

The Terminals page now always offers Set up this computer, so each reception or consulting-room PC can run its own connector. Connectors are named after their computer, each card machine is paired from one of them, and the portal sends that machine's payments to that computer only. If the computer paired with a machine is asleep, the portal says which one, rather than a generic offline message.

Once the practice connector is installed on a computer, it stays current on its own: when Medipay ships a new version, every running connector picks it up within a minute, verifies it, and switches over without stopping, so nobody has to run the install command again. The Terminals page shows which version is running.

Every settlement-feed import, scheduled or uploaded by Medipay, now re-checks the rows it just created against payments taken through Medipay and removes any duplicate before it can appear in Payments or reach your accounting software. A daily check also watches every clinic on the feed. You should never see a payment twice; if you do, tell us and we will see exactly which import let it through.

Where the settlement feed had already created a second Online (ONL) row for a payment taken through a Medipay pay link or the virtual terminal, Medipay operations can now list those pairs and remove the duplicate row, leaving the original payment untouched. New duplicates stopped on 3 September.

When you reinstall the practice connector on a new computer and the old one is retired, the machines it had paired are now marked as needing pairing again, and the Terminals page asks for it. Sending to an unpaired machine, from the portal or the API, is refused straight away with a clear message instead of failing at the machine.

When the practice connector shows Offline, the Terminals page now offers Reinstall on this computer. It detects whether you are on a Mac or Windows, gives you the one-line command for that computer, and retires the previous connector so an old laptop cannot pick up payments if it comes back. The card turns green on its own once the new connector is running; then press Pair on each machine, since pairings belong to the old computer.

Every team member now has their own permanent 'pay us' link (Pay links → Copy my payment link). Paste it into your email signature or invoice emails; the patient opens it, enters their name and reference, and chooses the amount. Payments made through your link are recorded as taken by you, so the payments list and exports show who actually sent it. The clinic's older shared link keeps working and is credited to the workspace owner.

A payment taken through a Medipay pay link or the virtual terminal could show up a second time, as an Online row with an ONL reference, once the acquirer's settlement file arrived. The feed now recognises payments Medipay took itself by amount, card and time, so each payment appears once. Payments taken outside Medipay still arrive from the feed as before.