Token Usage
Time delay of 30min before token usable. When creating a token on the Pax Terminal with customer present, token is generate immediately but can only be actively be used after 30min. Root cause is the time gap until all back end systems have been actualized.

Workarround
In daily operation, this mostly doesn't cause any issues as token is used earliest when customer is checking out. If it is needed to charge customer right away, please use direct sales functions.

Token Only
Unusable token when only a token is beeing generated on the Pax Devices.
If only a token is generated during check-in process, a token without Pre-Auth, this token won't be usable. This issue does not apply on Pre-Auth transaction.

Workarround
Please use Pre-Auth Transaction, creating an authorization/reservation of the amount. Completing this transaction will work without any issue.

Current Version

JUNO Suite v2.04

Correct Transaction Posting in Oracle Opera:

This release resolves an issue that caused some credit card authorise and settlements to post incorrectly to Oracle Opera.

Description: Previously, a timing delay from a payment partner could result in missing authorisations or settlements being posted under an "unknown" card brand.
Resolution: We have implemented a permanent fix in coordination with our partner that ensures the card brand ID is always received correctly. All authorisations and settlements will now post to Opera accurately. No action is required.

In response to customer requests, this release introduces a new setting to print transaction receipt data directly on the Opera folio.

Description: While this data was previously only printed on the terminal receipt, hotels now have the flexibility to include it on the Opera folio.
How it Works: This functionality can be enabled or disabled via a new option in your Juno "Hotel Settings" dashboard to fit your operational needs.
Note: Please be aware that receipt data may not be available for all transaction types.