Overview
When Oracle OPERA v5 is connected to Juno through the Oracle Payment Interface (OPI), every card in the OPERA database is replaced by a token ID. Tokens keep card data secure, but they aren't card numbers and behave differently: a token belongs to one reservation and can't be copied to other reservations or saved to guest profiles. This article explains what you can and can't do with tokens.
Applies to
| Product | Juno Hospitality Suite |
| Integration | Oracle OPERA v5 (on-premise) via Oracle Payment Interface (OPI) |
| Version | OPERA v5 |
| Audience | Front office, reservations and OPERA administrators |
What you'll achieve
You'll know how tokenised cards behave in OPERA v5, so you can plan reservation and payment workflows around them.
Why cards are tokenised
When OPI is implemented, all cards stored in the OPERA database are tokenised. Only the token ID is stored in OPERA, which secures the card data your property needs to hold. No OPERA user can see a guest's full card number.
What you can and can't do with a token
| Action | Supported? |
| Copy a token from one reservation to another | No |
| Save a token to a guest profile | No |
| Copy a token from one folio window to another on the same reservation | Yes |
What this means day to day
- For a new reservation — including a repeat stay by the same guest — capture the card again. It can't be reused from an earlier reservation or the guest profile.
- To charge the same card on another folio window of the same reservation, copy the token between windows.
- To check which token is stored on a reservation, view the token ID.
Troubleshooting
The card from a previous stay isn't available on the new reservation
This is expected. Tokens can't be copied between reservations or saved to guest profiles. Capture the card on the new reservation.
Need more help?
Please contact your integration partner.
Comments
0 comments
Article is closed for comments.