3.35.0 - Setup & Operations

The following information describes the setup and use of features within this release of Aztec.

Addition of Payment Card Details to the Aztec Database

For Zonal customers using ZCPS FreedomPay, Aztec 3.35.0 now captures non-PCI card data from integrated card payments and stores it against the originating POS account in the Aztec database. This enables anonymised customer-spend analysis and supports use cases such as building loyalty profiles or targeted marketing — without ever holding the full card number. Contact your Zonal Account Representative for more information about retrieving this information.

It is recommended that should a customer wish to utilise this information for customer spend or loyalty analysis, they, as the data controller, should review their customer-facing privacy policy.

Data Captured per Transaction

For each integrated card payment processed via ZCPS FreedomPay, the following non-PCI fields are captured from the EFT audit trail:

Field	Description
Site Code	Site at which payment has been taken
Transaction ID	Aztec Transaction ID for the payment
Terminal ID	POS Terminal that has processed the payment
Card Scheme	The first 6 digits of the card number - this allows a processor to understand the Card Scheme
Card PAN Ending	The last 4 digits of the card number
Card Expiry	Expiry date of the card

Data Retention

Records older than 2 months are automatically deleted from both Site and Head Office databases; this retention period is fixed and not configurable.

Auto Serve Delayed Orders on Automatic Session Change

Setup

Use Delayed Order must already be enabled at the site
Auto end of day must be configured for the relevant Terminal Config Set (this drives the automatic session change)
You will need a Front of House employee to nominate as the Auto-Serve Delayed Order User

Zonal recommends creating a dedicated employee for this purpose rather than reusing an existing user (such as the Remote Mobile Ordering user) to prevent auto-serve activity from interfering with mobile ordering

Navigate to Base Data → Estate Structure → Site → Delayed Ordering

Set the new Auto-Serve Delayed Order User field by selecting an employee from the drop-down. The list includes Front of House Employees that are valid for the selected site(s). Leaving the field blank disables the functionality

Navigate to Communications

Perform a Comms Job & Send to POS to site

How does it work?

For each POS Server at the site the Aztec Back of House selects a terminal to use to perform the auto-serve:

Excluded hardware types: Kiosk, MOA OrderPad, MOA Pay At Table, iZone Tables. These will never be used
If the server has at least one non-Mobile Ordering terminal, the first terminal (lowest EposDeviceID) is selected
If the server only has Mobile Ordering terminals, the first Mobile Ordering terminal (lowest EposDeviceID) is selected as a fallback

Where a site has multiple POS servers, the rules are applied independently per server, so auto-serve runs across the full site

What is served automatically?

Order State	Past Collection Time	Behaviour at Automatic Session Change
Fully paid (zero balance)	Yes	Automatically served
Fully paid (zero balance)	No	Not served - remains open
Outstanding balance	Yes or No	Not served - remains open