Workstation service change log
Purpose: Look up what changed in a release of the VitaPay payment service on the workstation.
When to use this: When you're checking whether a fix has reached a station, when an error in this list matches what you're seeing, or before you escalate.
Current release: 5.2.10.0. See checking your version.
tip
Several fixes below behave differently depending on the Simphony version the station runs. When you report an issue, give both the service version and the Simphony version.
5.2.10.0
30 Jul 2026
- Compensates for very old SPI versions, where tips taken on a handheld in Mobile Terminal mode were dropped. An old SPI credits the gratuity from the other amount on a sale response and ignores the tip amount, which is the field the handheld reports its tip in. The service now mirrors the tip into the other amount before passing the response on. It leaves the response untouched when there is no tip, or when the other amount is already filled in, so newer versions are unaffected.
5.2.9.0
23 Jul 2026
- The amount the POS shows and the amount held on the card are now tracked separately. Previously, after the change in 5.2.8.1, the POS believed the reduced amount while the hold on the card was unchanged, and anything reading the authorised amount reported the old figure.
- Increment vouchers print the right total. A $100 authorisation reduced to $60 with $20 added was printing $120 instead of $80.
- Re-authorisation now works from the amount the POS shows, instead of putting the hold back up to the pre-reversal amount.
- A repeated reversal no longer declines with "AUTHD-USE CC VOUCHER REPRINT". It is acknowledged again with a correct voucher. Previously the operator was sent to Simphony's stored voucher, which showed the old amount.
Rollout
Every station at the venue must be on 5.2.9.0 or later. A reversal taken on an older station does not record the amount the POS shows, so vouchers and re-authorisations on the other stations can still be wrong.
5.2.8.1
24 to 30 Jun 2026
- A partial reversal is now handled locally. It no longer goes to the processor and no longer changes the amount held on the card. It is acknowledged immediately and returns a voucher showing the reduced amount. The lower amount settles at credit card close, where the amount captured comes from the POS total.
- Added diagnostic logging for TRANS DENIED 662 on increments, comparing what the station holds locally against the shared record.
5.2.8.0
23 Jun 2026
- Voiding a settled payment no longer makes the POS retry in a loop. Previously the void went to the processor, which only holds the pre-authorisation, so it came back as DUPL TRAN 794 and the POS kept retrying. The void is now applied on our side and returns success. Duplicate and already reversed responses from the processor are treated as success, as a backstop.
- An increment or reversal that works out to 0.00 no longer goes to the reader. The card is already authorised for that amount, so the service returns a clear decline telling the operator to reprint the existing voucher. The wording is shortened automatically for older Simphony, which limits the length of the message it will accept.
5.2.7.0
20 Jun 2026
- Timestamps reworked so all stations at a venue agree on the order of changes. The business date deliberately stays on venue local time, so the business day does not roll over mid evening and split a tab across two days.
- Syncing now overlaps the previous run slightly, so a transaction saved right on the boundary cannot be skipped.
- Increments, voids, adjustments and captures always read the shared record rather than the station's own copy. Previously a change made on another station could be calculated against an out of date authorised amount.
- Connection pool limits moved into the service config file, so they can be tuned per venue without a new build. Defaults are minimum 2, maximum 64, and a 30 second timeout. The pool is per station, so the venue total is roughly the number of stations multiplied by the maximum. At 50 stations or more, confirm the shared database accepts that many connections before raising the limit.
5.2.6.1
9 to 20 Jun 2026
- More settings moved to cloud configuration, so they no longer have to be set on the station.
5.2.6.0
8 Jun 2026
- Sales adjustments no longer fail. Simphony sends the tip on an adjustment in a different field than on a sale, and when the expected field was missing the adjustment failed outright. Both fields are now accepted, and a missing value is treated as zero.
5.2.5.0
2 Jun 2026
- Response message length is now chosen per request from the Simphony version that sent it. Simphony 19.6 and older get the short form, newer builds get the longer, more descriptive one.
5.2.4.0
1 Jun 2026
- Error responses are now accepted by Simphony 19.4. Previously they were sent in a shape 19.4 would not read, so it treated the outcome as unknown and fired a timeout reversal even though nothing had gone through. Errors are now shaped like a normal decline, which 19.4 accepts and does not reverse.
5.2.3.0
1 Jun 2026
- Error responses now include the two fields Simphony requires on every response. Leaving them out was the other cause of Simphony 19.4 treating the outcome as unknown and reversing.
- Long, multi-line error messages are no longer sent to older Simphony, which rejects them. The full text goes to the log instead.
5.2.2.0
1 Jun 2026
- Amounts that older Simphony versions leave out of the request are treated as zero on sales, refunds and authorisations. Previously the transaction failed.
5.2.1.0
13 to 20 May 2026
- Cardholder verification line removed from the printed voucher.
5.2.0.0
13 May 2026
- Void notifications to the cloud are retried instead of being lost when the cloud is briefly unreachable.
5.1.0.0 and 5.1.0.1
7 to 13 May 2026
- Multiple Merchant IDs per station. Transactions route per Merchant ID, all lookups are scoped to the Merchant ID, and existing records are migrated automatically, so records from different MIDs can no longer collide. See RVC routing.
- An offline transaction view and an admin view were added to the service's built in web page.
- Shorter receipt style, configurable.
- The cloud is told when a captured authorisation is voided, with its own retry, so the cloud ends up on the correct final state even when both a capture and a void are queued.
- A queued cloud record is no longer overwritten by a later failed update. Previously that meant the record was never created at all.
- Two updates to the same transaction can no longer race each other.
5.0.0.4
7 May 2026
- Charged tip fix.
5.0.0.3
30 Mar to 7 May 2026
- Capture fixes, and a void receipt.
5.0.0.2
22 Feb to 29 Mar 2026
- Transactions no longer fail to reach the cloud.
- Reader parameters are uploaded while the station is idle, instead of interrupting service.
5.0.0.1
22 Feb 2026
- Database fix.
5.0.0.0
23 Nov 2025 to 18 Feb 2026
Major release.
- NFC read added, for reading a card or fob identifier without taking a payment, with a view in the built in dashboard.
- Customer lookup corrected.
- Recurring transactions, and the 48 hour window.
- Invoice number handling, entry code and security check, and cardholder information capture.
- Voids print a receipt.
- Offline handling, and an increment fix.
- More detailed logging, and log clearing.
3.0.3.0
23 Nov 2025
- Guest number handling.
3.0.2.2
18 Nov 2025
- Authorisation handling rewritten and simplified.
- Configurable timeout, and cancel from a handheld.
3.0.1.2
19 Oct to 18 Nov 2025
- The service no longer depends on being installed to one fixed folder.
- Certification fixes.
3.0.1.1
2 Oct 2025
- Stable bug fix build.
3.0.1.0
31 Jul to 2 Oct 2025
- Cancel support, and reader cancel.
3.0.0.0
27 Jul 2025
- Refund and request handling changes.
2.9.0.0
15 Jul 2025
- Re-authorisation support.
2.8.0.0
6 to 7 Jul 2025
- Requests can be forwarded to a handheld, which is what Mobile Terminal mode uses.
- Control page, and configuration loaded at startup.
2.6.0.0 and 2.7.0.0
30 Jun 2025
- Sale receipt printing, and Level 2 data.
2.5.0.0
12 to 30 Jun 2025
- Both authorisation paths working.
- MOTO and quick chip, and a database fix.
2.4.0.0
9 Jun 2025
- Manual card entry for sales and authorisations.
2.3.0.0
21 May to 5 Jun 2025
- Update route added, which the VitaPay Updater uses.
- Setup issues resolved.
1.0
23 Sep 2024
- Initial build.
