Opera V5 - Authorization Reversals

Overview

Oracle OPERA v5 automatically sends an authorisation reversal through Juno and the Oracle Payment Interface (OPI) when an existing pre-authorisation's card is replaced with a different card. This article explains when OPERA triggers the reversal, how to prompt it, and why a hold may still appear on the guest's card afterwards.

Applies to

What you'll achieve

After completing these steps, OPERA sends a reversal request for the pre-authorisation on the original card. Whether and when the hold disappears from the guest's card depends on the guest's bank.

Before you start

• A pre-authorisation must already exist on the reservation.
• The reversal happens automatically when the main card is replaced with a new card — there's no separate release action. 

Trigger the reversal

1. Open the reservation in OPERA v5.
2. Replace the main payment card with the new card (for example, change the payment method from Visa to Mastercard).
3. OPERA automatically sends the authorisation reversal request for the original card.

Example

If the authorisation at check-in was on a Visa card and the guest pays at check-out by Mastercard, change the payment method to Mastercard. OPERA then sends the reversal request for the Visa authorisation.

Expected result

The reversal of the removed payment appears in the authorisation reversal window in OPERA.

Troubleshooting

The guest still sees a hold on their card

OPERA and OPI send the reversal, but it's up to the cardholder's bank to release the pre-authorisation, and many banks don't support the electronic release message. The hold may remain until the bank releases it. To avoid unnecessary holds, review your authorisation rules carefully and, where possible, take a payment rather than a pre-authorisation.

Need more help?

Please contact 934 Support (support@weare934.com) with the amount, last 4 digits from the credit card and the date and time. Do not send full card numbers or login credentials by email or chat.