1 Business Context

This guide describes best practices to determine the credit card payment method data needed to successfully create and update hotel reservations based on an integrated Oracle Payment Interface (OPI) at the property level.

Many hotels with OPERA Cloud are using the Oracle Payment Interface (OPI) to integrate with Payment Service Providers (PSP) to obtain tokens for the credit card number on reservations, and then process authorizations and payments to collect revenue. Therefore, it is important to know how best to handle credit card data as the payment method to successfully create/update reservations that can utilize this process.

Note:

API usage and capabilities are subject to change. For more information on API versioning, see the Versioning topic in the Oracle Hospitality Integration Platform User Guide.

For the most comprehensive and up-to-date information, including additional query parameters and detailed descriptions, always refer to the latest API specifications in GitHub. This will ensure that you are accessing the most current and complete set of features available.

Use Case	Description	Operation IDs
Reservation Payment Methods when OPI is not in use at the property.	Reservation system is ready to create or update a reservation to the property and will have the credit card number in the request.	getHotelInterfaces getOperaSettings getPaymentMethodsLOV postReservation
Reservation Payment Methods when OPI is in use at the property.	Reservation system is ready to create or update a reservation to the property and will have the token in the request.	getHotelInterfaces getOperaSettings getPaymentMethodsLOV postOpenPaymentTokenExchange postReservation