Via the 1-CP integration layer, you integrate the merchant's booking engine with Cytric. Employees can then book specialized offers (e.g. long-stay apartments or parking) directly with the merchant, while profiles and booking data stay synchronized with Cytric.
Key features
Profile synchronization (CCPS): The 1-CP integration layer uses CCPS (cytric Companion for Profile Synchronization) to transfer employee data securely. During the Punch-Out to the merchant, their traveler details, billing information, credit card details and other data are transferred automatically. This makes the checkout fast and secure. More in Profile synchronization.
Punch-Out integration: You add links to the merchant's booking engine (via 1-CP) directly in the Cytric interface. There are two ways to do this:
As an additional button (tab): Next to standard tabs such as Hotel or Flight, a dedicated button for the merchant's offers is added and stays visible at all times. This suits categories Cytric does not cover yet, e.g. airport parking, serviced apartments or event bookings. The step-by-step guide is in Setting up custom buttons in Cytric.
As a rule-based alert: A message with a link appears depending on the search criteria. Examples:
Long stay: For a search of more than 7 nights, a message appears: "For long stays, please use our [merchant name] portal."
Group booking: If someone searches for more than 3 rooms, a message appears: "For group bookings, click here to use our [merchant name] portal for special rates."
Airport parking: If someone books a flight from certain airports, a pop-up suggests: "Driving to the airport? Book your discounted parking here."
Booking push-back (PNR): As soon as a booking is completed in the merchant's booking engine, the 1-CP integration layer automatically sends the reservation data back to Cytric.
Driving adoption and travel policy
So that employees understand why they should use this merchant, name the merchant directly in your travel policy. This makes clear that the additional button or link is the approved booking channel. Referring to the policy in rule-based alerts (e.g. "Per policy, long stays must be booked via [merchant name]") supports compliance.
How to get started
Ask your administrator to activate CCPS for 1-CP.
Work with your Cytric administrator or support team to set up the transfer links that lead to the merchant's booking engine via the 1-CP integration layer. The step-by-step guide is in Setting up custom buttons in Cytric.
Define the PNR queue and remarks fields so that 1-CP pushes the booking data back correctly.
If you need help with the setup, use the integration request form in the Help widget.