Overview

RTP User

• flaik Bookings will use the same RTP User as the Resort Service API already uses

• This is configured in the AppSettings.json for the Resort Service.

• The Operator ID should be updated in RTP to have transaction permissions in OneResort.

• Recommendation: the flaik user has a distinct Security Group assigned to them with similar permissions to Aspenware or other eCommerce RTP users.

Sale Location

• Product Headers and Payment Methods must be available at the Sale/Audit Location specified for flaik Bookings.

• We assume the Sale Location Code is the same as the Audit Location Code.

• Recommendation: It is up to each resort to determine if you need to create a new sale location for flaik Bookings, but we recommend separating it out from other existing integrations so it can be reported on and managed separately.

• See below for what we require to set up a new location.

Sales Channel

• If your Private Lesson products have distinct pricing for different Sales Channels, keep in mind that flaik will use the pricing for the Sales Channel you have specified.