Overview
In Oracle Opera, a card token must reach the reservation within a short time limit. If the token takes too long to arrive, Opera ends the request with a timeout and the card is not stored. The Juno Universal Token (JUT) removes this time-sensitive step: it creates a secure token for the card in milliseconds, at the moment the card is captured. This article explains when timeouts happen, how JUT works, what to check at check-in, and how to opt out.
Applies to
| Product | Juno Hospitality Suite |
| Feature | Juno Universal Token (JUT) |
| Integration | Oracle Opera |
| Audience | Property managers, front office and reservations teams |
What you'll achieve
After reading this article, you understand why a card token can time out in Opera, how JUT avoids that dependency, what your front desk should still check, and how to switch JUT off if you prefer not to use it.
Before you start
- This article applies to properties that use Oracle Opera with Juno.
- No action is needed to benefit from JUT.
Operational steps
1. Understand why a token can time out
Juno sits directly in the request and response path between the acquirer and your property management system (PMS). Juno does not hold or relay messages on a separate track. If one side is slow to respond, that delay passes straight through to the other side. Juno neither absorbs the delay nor adds to it.
Opera enforces a time limit for tokenisation. If the token has not arrived in time, Opera reports a timeout and the card is not stored on the reservation. This is most noticeable during high-volume booking periods.
2. Know what JUT does
The Juno Universal Token is a tokenisation method within Juno. When a card is presented, JUT generates a secure, universal token for it, whether or not the issuer has activated the card yet. It operates in milliseconds, so the time-sensitive round trip no longer determines whether the token reaches the reservation. This helps in two common situations:
- OTA virtual cards that arrive before activation. Depending on a hotel's tariff structure, some virtual credit cards (VCCs) from online travel agencies (OTAs) reach Opera before the card issuer has activated them. Without JUT, this can prevent the card from being stored at all. JUT tokenises the card regardless of activation status, so the payment details are captured and available when the card becomes active.
- Time-sensitive tokenisation. Where Opera would otherwise return an error because a token did not arrive in time, JUT generates the token in milliseconds.
3. Keep validating the card at check-in
JUT tokenises a card at the moment it is captured and does not confirm its validity again later. This is the same situation as when the acquirer tokenises the card directly.
The case to be aware of is a direct booking made through your property's own booking engine. If the card is tokenised well before arrival, it may no longer be valid at check-in, for example because it has expired, been cancelled or been replaced.
For this reason, we recommend that your front desk continues to validate the stored card at check-in, as it normally would with a pre-authorisation, rather than relying on the token alone as proof of a chargeable card.
4. Opt out if you do not want to use JUT
You can opt out at any time. Send a short email to support@weare934.com to say that you would like JUT to be disabled for your property, and include your property name. 934 Support will take care of it.
Expected result
The card token reaches the reservation without depending on how quickly the acquirer responds. Cards that were tokenised before JUT was enabled remain valid and do not need to be changed.
Troubleshooting
An OTA virtual card was not stored on the reservation
Likely cause: the card had not yet been activated by the issuer when it reached Opera.
What to check: whether JUT is enabled for your property.
What to do: contact 934 Support at support@weare934.com and ask whether JUT is enabled for your property.
Opera reports a tokenisation timeout
Likely cause: the token did not reach Opera within its time limit, for example because a response in the request path was slow.
What to check: whether JUT is enabled for your property.
What to do: if JUT is enabled and the timeout still occurs, contact 934 Support and include the property name, the date and time, and the reservation reference
Related articles
Need more help?
If you have questions about how JUT works for your property, contact your Customer Success Manager or support@weare934.com.
Comments
0 comments
Article is closed for comments.