What Has Changed with the Introduction of OPI in OPERA Cloud
A summary of the key changes to Standard Operating Procedures that come with activating the Oracle Payment Interface (OPI).
Before You Begin
- None — this is a reference guide for reviewing before activating OPI at a property.
What You Need to Know
- Full card numbers are no longer stored: Previously, the full card number was stored in OPERA (encrypted, but accessible to users with the right permissions). With OPI active, the OPERA Credit Card Vault swaps the card for a Token ID, and no user has access to a guest's card number.
- Chargebacks need a new process: Since the card number is no longer stored, hotels that previously relied on the full card number to handle chargeback requests will need to agree a new chargeback process with their Payment Service Provider.
- Pay Only is for non-authorising card types: The Pay Only function accepts "Sale" transactions only, and is intended for card types that don't support pre-authorisations — such as debit cards, virtual credit cards, AliPay, and WeChat.
- Pre-authorisation releases depend on the bank: OPERA and OPI support the electronic Pre-Authorisation Release transaction type, but it's ultimately up to the card holder's bank to release the hold. Many banks don't support this message, so holds may remain visible on a guest's card even after a successful reversal request.
Tips & Best Practices
- Review all four areas before go-live: Walk through card storage, chargebacks, Pay Only setup, and pre-authorisation rules with your Payment Service Provider before activating OPI.
- Prefer payments over pre-authorisations where possible: This reduces the likelihood of guest complaints about holds that a bank is slow to release.
- Need help? For questions on transitioning to OPI, contact your Payment Service Provider.