Guest Sees Two Charges for a Single Payment (Opera Cloud)

Who this is for: 

Front desk and reservations staff using Opera Cloud who take card payments at check-in or during a stay.

What you might see

A guest pays for their stay, and everything looks normal at the time. Later, the guest notices two charges on their card for what should have been a single payment.

When you check Opera's change log, it may show that the first attempt "failed" or was "denied," making it look like only the second attempt actually went through. In reality, both attempts were successfully processed and charged to the guest's card.

Why this happens

This is a known issue in Opera Cloud, confirmed by Oracle Support. Occasionally, Opera sends two separate payment requests for the same charge, roughly a minute apart. Due to a bug in how Opera processes the payment response, it can incorrectly treat a successful authorization as failed and automatically retry - even though the original payment actually went through. Both requests then get approved and charged.

This is a Opera Cloud issue, not something happening on the payment processing side - our records show both transactions completed successfully.

Fix status: Oracle has confirmed the correction is included in Opera Cloud version 26.3. Once your property is upgraded to 26.3 or later, this specific issue is not expected to recur. Your Oracle account manager will notify you when an upgrade is scheduled - we don't control that timeline on our end.

What to do if this happens

1. Check the guest's folio/ledger in Opera to confirm there really are two charges for the same payment.
2. Refund the duplicate from Opera if you're able to - this is usually the fastest route for the guest.
3. If you can't process the refund from your side, contact 934 AG support with the guest name, reservation number, and card details (last 4 digits and amount). We can process the refund for you.

Why this matters

Because Opera's own change log can show the first attempt as "failed," it's easy to assume only one charge went through. Always check the actual ledger/folio rather than relying on the change log status alone when a guest reports what looks like a double charge.