Aristocrat Loyalty

The following operations are supported as part of this gaming integration product. Only the operations listed below are currently supported.

Table 6-22 Aristocrat Loyalty

Function How it works Direction

Player Enrollment

  • OPERA Cloud sends the name and address information for a new player profile to Loyalty.

  • Loyalty creates a player profile and responds to OPERA Cloud with the player ID.

OPERA Cloud–> LOYALTY

Profile Lookup

  • OPERA Cloud users can search Loyalty for profile(s) based on Player ID or Last and/or First Name.

  • Loyalty returns a list of profiles matching the criteria requested, which the OPERA Cloud user views on-screen.

OPERA Cloud –> LOYALTY

Profile Fetch

  • The OPERA Cloud user selects a profile from a list provided during the Lookup operation.

  • Loyalty returns the patron’s name, addresses, birth date, and email address; OPERA Cloud will either insert a new profile record or merge the data into an existing record.

OPERA Cloud –> LOYALTY

Profile Update

OPERA Cloud notifies Loyalty of any changes made to the name and/or address, telephone, and email on any OPERA Cloud profile that has an associated Loyalty Player Id.

OPERA Cloud –> LOYALTY

Reservation Notification

When a reservation is created/changed or cancelled, OPERA Cloud sends a notification message (including reservation status) to Loyalty for the associated player.

OPERA Cloud –> LOYALTY

Comp Postings

  • OPERA Cloud sends a comp request to Loyalty when a charge is posted to a comp window (101‐108). A comp posting is any charge that was moved to a comp window, regardless of whether it was originally posted manually, through the End of Day sequence, or by POS interface to OPERA Cloud.

  • To void a comp transaction, you must move back to a cash window (1-8). A Void is then sent to Loyalty.

  • Loyalty will either approve or decline the comp posting. Approval status appears on the OPERA Cloud Comp Journal screen.

  • OPERA Cloud sends comp postings to Loyalty in monetary value / amount only.

  • OPERA Cloud sends comps monetary value / amount to only one default bucket in Loyalty.

    Note:

    Do not move transactions between comp windows (101-108).

OPERA Cloud –> LOYALTY

Required Information

To invoke the loyalty webservices from OPERA Cloud, below are the required details that needs to be requested for configuration:

  • Webservice URL for PartnerNameService [ex: http://{hostname}:{port}/PartnerNameService]

  • Webservice URL for PartnerGamingService [ex: http://{hostname}:{port}/PartnerGamingService]

  • Webservice URL for PartnerReservationService [ex: http://{hostname}:{port}/PartnerReservationService]

The integration between OPERA Cloud and Aristocrat Loyalty uses the following Webservice operations.

Table 6-23 Webservice operations

Webservice Operation Function

PartnerNameService

ProfileLookup

Profile Lookup

PartnerNameService

FetchProfile

Profile Fetch

PartnerGamingService, PartnerNameService

EnrollProfile, FetchProfile

Profile Enrollment

PartnerNameService

UpdateProfile

Profile Update

PartnerReservationService

ReservationNotification

Reservation Notification

PartnerGamingService

CompPost

Comp Postings

For further details on Loyalty configurations, please get in touch with your Aristocrat Loyalty point of contact or your Oracle Hospitality point of contact.

Parent topic: Gaming Vendor Specific Configurations