How the Sertifi Opera Cloud (OHIP) Integration Works

Overview

Sertifi integrates with Opera Cloud using Oracle's Hospitality Integration Platform (OHIP). This integration allows credit card authorization data and payment information collected through Sertifi to be automatically posted to the corresponding guest reservation in Opera Cloud — eliminating manual data entry at the front desk.

This article explains how the integration works at a high level, and what happens on both the Sertifi and Opera sides during the process.

How the eAuthorize Workflow Works (Opera Cloud)

1. Your front desk or reservation team sends a credit card authorization form to a guest through Sertifi.
2. The guest receives the form by email, opens it, and fills in their credit card information along with their First Name, Last Name, Confirmation Number, and Arrival Date.
3. When the guest submits the form, Sertifi validates that the information matches the reservation in Opera Cloud.
4. If everything matches, Sertifi securely pushes the authorization data — including the payment method, card token, and folio window assignment — directly into the guest's Opera reservation.
5. Your front desk can see the authorization information in the guest's reservation under Billing > Payment Instructions in Opera.
6. If the push fails for any reason, it will appear in the Opera Status Report in Sertifi, where it can be corrected and re-pushed.

How the ePayments Workflow Works (Opera Cloud)

1. Your team sends a payment request to a guest through Sertifi, including the Opera reservation Confirmation Number.
2. The guest receives the payment request, enters their payment information, and submits.
3. Sertifi processes the payment through your property's payment gateway.
4. Once payment is collected, Sertifi pushes the payment record to Opera Cloud using the confirmation number to locate the correct reservation.
5. The payment posts to the designated folio window in Opera.
6. If the push fails, it will appear in the Opera Status Report for correction and retry.

Key Things to Know

• Matching is required: The guest information entered on the Sertifi form must match the reservation in Opera exactly. Mismatches in name, arrival date, or confirmation number will cause the push to fail.
• Folio windows: Your property configures which folio window Sertifi posts to. This can be set as a fixed window or dynamic (first available). Window 1 is typically reserved for the guest's own payment method.
• Payment method codes: Sertifi uses your Opera-configured card type codes (e.g., VA for Visa, AX for American Express) to post payment method information. For ePayments specifically, your property must have separate payment codes linked to transaction codes with a Manual processing type.
• Failed pushes don't mean lost data: If a push to Opera fails, Sertifi still retains the authorization or payment information. You can correct the issue and re-push from the Opera Status Report.

Need Help?

If you are experiencing consistent push failures or have questions about how your Opera Cloud integration is configured, contact Sertifi Support with your property name and a description of the issue.