1.4.4 - Field Trial

Enable a POS server to cancel a payment or refund from the POS, giving them a way to end a transaction without interacting with the PED or for cancelling a transaction when the PED freezes. For PAC mode only and Authorisations, Voids and Clawbacks cannot be cancelled from the POS.

Servers can now reverse FreedomPay transactions after a ZCPS restart or the site PC going down. This also allows card validations to persist, meaning that claw backs can be taken after a service restart.

A supplemental package has been added so that China Union Pay can be accepted for payments, meaning FreedomPay PEDs can process this card scheme to reflect growing demand in UK market for China Union Pay.

We’ve streamlined the Roaming PED payment flow to make transactions faster and simpler. The extra confirmation screens (“Check Fully Paid” and “Main Menu”) have been removed, so the process now ends at the receipt screen with quick options for OK and Reprint Last Receipt. This reduces button presses, speeds up split-bill handling, and improves overall efficiency for busy environments.

Merchants can now block American Express (Amex) during offline processing if they bank with GlobalPay. Previously, Amex could be unintentionally approved when devices were offline and unable to verify the merchant’s “Amex not supported” setting. With the new “No Amex” package, devices know whether Amex is supported without needing to contact FreedomPay, ensuring offline Amex transactions are correctly prevented and rejected.

We’ve added support for Premier Inn ATOS Business Account cards in MAB sites through our FreedomPay card-present integration. This includes a new Aztec configuration to enable ATOS BIN mapping, ensuring the setting persists across upgrades.

We have removed the previous £100 minimum transaction limit for Dynamic Currency Conversion (DCC). DCC limits are now dependant on the payment provider ensuring the card‑scheme‑defined limits are adhered to, enabling customers to use DCC on lower‑value transactions where permitted.

This change removes the restriction introduced in FreedomPay 1.4.0 and prepares the platform for FreedomPay’s forthcoming scheme‑compliant limit‑handling solution. The feature is configurable at a site level.