Payments built into OPERA not beside it.
Embedded payments for Oracle OPERA
Kovena connects to Oracle OPERA through OPI Cloud, so card-on-file, pay-by-link, charges and refunds all happen inside OPERA. One certified integration, ready to roll out across your entire property base.
PCI DSS L1
Level 1 provider, card data secured in Kovena’s Level 1 vault
15+
Currencies supported on one gateway
Real time
OPERA runs your properties.
Payments should run inside it, not beside it.
Payments that run beside OPERA split your data across two systems, and push PCI exposure onto your merchants. Embedded, they become part of the operations: you own the transaction economics, reconciliation clears in real time, and card data is tokenised in OPERA and held in Kovena’s PCI DSS Level 1 vault, so PCI scope sits with Oracle and Kovena, not the property. The workflow your merchants already trust, now working for you.
Embedding Kovena in OPERA solves a different problem for each leader on your side. Select a role to see the pain it removes and what it delivers.
Integration & PCI architecture
Reconciliation & cost
Guest experience & revenue
Integration & PCI architecture
Head of Technology
Embedded payments in OPERA, with nothing to build and no added PCI scope
Owns integration, PCI architecture and card-data security
- Fractured payment processes across separate systems – OTAs, booking engines, channel managers, unintegrated terminals and OPERA – with card data arriving from every source.
- No consolidated way to handle card data from multiple booking sources, whether it comes from an OTA, a booking engine, or an operator-initiated payment taken by the reservations team.
- Keeping card data secure as it moves across thousands of properties and systems.
- Fractured payment processes across separate systems – OTAs, booking engines, channel managers, unintegrated terminals and OPERA – with card data arriving from every source.
- No consolidated way to handle card data from multiple booking sources, whether it comes from an OTA, a booking engine, or an operator-initiated payment taken by the reservations team.
- Keeping card data secure as it moves across thousands of properties and systems.
Reconciliation & cost
Head of Finance / Payments
Real-time reconciliation, automatic postings, faster close with fewer chargebacks
Owns reconciliation, chargebacks, postings and cost
- Manual reconciliation and postings that delay close and tie up the team.
- Chargebacks and disputes managed inconsistently across regions and currencies.
- Layered reporting and end-of-day batch fees eroding payment margin.
- Real-time reconciliation in a single dashboard with a clean, timestamped audit trail. No end-of-day batch fees.
- Automatic postings back into OPERA, so settlement and card data match without manual work.
- Fewer chargebacks with travel-specific 3D Secure and a full audit trail to win disputes.
- Local acquiring with 15+ currencies.
Guest experience & revenue
Head of Operations / Revenue
Smoother front desk experience with fewer declines and reduced admin
Owns guest experience, arrivals and revenue capture
- Card friction at check-in that slows arrivals and frustrates guests.
- Deposits and pre-authorisations chased by hand at the front desk.
- Failed or declined cards that cost revenue and staff time to recover.
- Faster arrivals. Payments handled inside OPERA remove card friction at check-in.
- Deposits and pre-auths captured automatically, no longer chased by hand.
- Real-time visibility for staff, with less admin and a smoother guest experience.
One certified integration. Embed Payments inside OPERA.
Kovena is an embedded payments platform built for travel. We process card payments inside OPERA through OPI Cloud, Oracle’s payment interface layer. Card numbers are collected through the OPERA Payment Interface and stored securely with Kovena to PCI DSS Level 1, minimising PCI compliance risk and fraud exposure for the property.
Why it matters: because Kovena integrates through OPI Cloud, payments appear inside OPERA with no separate portal for staff to learn. Card details are exchanged for a secure token and the card number is held in Kovena’s Level 1 vault, so PCI scope sits with Oracle and Kovena rather than the property. Against any reservation, staff can take card-on-file payments, send a pay-by-link, process charges and linked refunds, and check deposit status, all without leaving OPERA.
One certified integration. Embed Payments inside OPERA.
The integration is designed so the sensitive data never leaves Oracle’s environment. Your platform keeps its risk posture, and your merchants keep their trust.
Card data captured in OPERA, secured by Kovena
Guest cards are collected via an OPERA-connected booking engine, an OTA, or entered directly into the OPI interface by hotel staff or the reservations team, then stored in Kovena's PCI DSS Level 1 vault.
Tokenization
Card details are replaced with a secure token. The underlying card number is held in Kovena's Level 1 vault, not in property systems.
PCI scope sits with Oracle and Kovena
Because card data is handled through Oracle and stored in Kovena's PCI DSS Level 1 vault, PCI scope sits with Oracle and Kovena, not with the property.
Travel-specific 3D Secure
Industry-specific 3DS, configurable to each property's risk and guest experience preferences.
A structured go-live, led with Oracle.
Oracle leads the technical configuration, Kovena confirms gateway readiness, and your team validates from your end. Most properties complete this in a single session.
Onboard & configure
Kovena sets up the merchant and gateway before the call. No property action needed.
Implementation call
Oracle connects OPERA to Kovena and runs the token exchange test with the team.
End-to-end testing
Validate charge, refund and pay-by-link in OPERA and the Kovena dashboard.
Bulk tokenization
Future reservations are tokenised in the background, with no downtime.
Live
Payments run inside OPERA, with real-time visibility for finance.
Rolling out across your property base
Go live one property at a time so each has full attention at launch. Let each run for three to five days before scheduling the next. Deposit rules are set at template level and copied to every property, keeping policy consistent across the group.
Simple, transparent pricing.
Pricing is tailored to each property’s volumes and card mix. We put real numbers to it before you commit.
Acquirer agnostic
Not tied to a single acquirer. Kovena's smart routing sends each transaction down the best available path, with built-in redundancy if an acquirer is unavailable.
No end-of-day batch fees
One real-time dashboard across payment types, instead of layered reporting fees.
The easiest path to embedding payments into your OPERA properties
Let’s jump on a scoping call. We tailor pricing to your properties and confirm the OPI Cloud setup with Oracle.