Provider Help Center

Q: Will providers be able to disable PCP once it is enabled, after April 1st, 2024? 

A: The timeline has been extended from April 1st to April 30th, 2024.
After April 30th, 2024, PCP_v2 will be integrated into the reservation API and will be enabled for all providers. So, it can’t be disabled 

 

Q: Will the new development of PCP_v2 impact only properties in the 3 states in the US or all properties? Do I need to implement the new version of PCP if I do not support any properties in those states?
A: Yes, all partners are requested to implement the pcp_v2 (even if you don’t support any US states). Failing so can impact in raising errors.

Q: Should providers in Japan implement and go through the capability assessment process for PCP ? 
A: PCP_v2  integrates into the reservation API and is made available to everyone. Booking will start sharing payment and tax information with the providers. Failure to implement PCP_v2 may result in the provider encountering an error.

Q: For BankTransfer reservations, would the following element be also included in the notification? How will the rest of PCP information be delivered?
<cc_current_balance>
<cc_activation_date>
<vcc_expiration_date>

A: Yes, those elements will be included however the value will be NULL.

Q: Currently price_details displays <extracomponent@text in the preferable language of the properties.Would booking translate the list of “Indirect Tax (Withheld Tax)”in each language available in our system?
A: The withheld tax flag will only be in English. At the moment, there are no plans to translate to other languages.

Q: Can a VCC (virtual credit card) be charged through a credit card provider like a regular credit card? 
A: Yes, VCC can be charged like a regular credit card.
 

Q: What changes for a non PCI compliant channel manager? 
A: Nothing changes for the PCI compliant provider. For Non PCI compliant providers, sensitive  fields will show as  NULL.

Q: Is this applicable for BankTransfer as well, the taxes breakdown details?
A: Yes, it's applicable to Bank transfer, VCC and agency reservation.
 

Q: Is PCP v2 the same as vcc_payment_v2?
A: PCP v2 is payment_clarity_package_v2, not the same as vcc_payment_v2. vcc_payment_v2 is PCP_v1.
 

Q: How to distinguish "Guest View" from "Property View". knowing that on the XML it comes only 1 type of Excluded/Included on OTA messages?
A: On OTA schema, there is just one view (property view) but on B.xml, we've guest view as well as property view. One can refer to the technical documentation to get more details. 

Q: As you mentioned that it will be mainly for properties from the US, will it affect the properties from other parts of the world, if we make the change?
A: At the moment, it will not impact other countries but it's important for our partners to upgrade to pcp_v2 (even if they don't have US connected properties). Other countries will gradually come in as a part of the 2024 roadmap. For other properties, it will be tax and payment breakdown without any changes to the tax remittance at all
 

Q: What will happen with withheld taxes when cancellation occurs?
A: Cancellation policy will be applicable in such cases. If it's a refundable cancellation policy, we’ll transfer/ put the taxes back to the original payment method and incase of non-refundable cancellation policy, we’ll not be able to return the taxes.

 

Q: If a tax item is included but withheld, how does that affect the property payout?
A: Withheld components will be excluded so they could be included in the guest view (i.e - guest has paid for that). But if a component is withheld In the hotel view, it's going to say included equals no, or excluded.because it's not going to be a part of the property payout.

 

Q: If we do not update this functionality, will we lose the current ability to get the payment breakdown? We have the ability to look at the price breakdown now but it sounds like without the upgrade, we'll have discrepancies in the price breakdown intake.
A: You will not lose the ability to get the payment breakdown. It'll still come through. But then, from 1st April onwards, it'll start taking the updated flag behavior. That will influence the ability to consume the correct price breakdown from Booking.

 

Q: Is it backwards compatible? Especially the part of Guest vs Property view (excluded-excluded/excluded-included etc.) changes. Is it okay to launch it a bit earlier ?
A: An early launch is absolutely fine. Backward Compatibility is not possible after April 1st. The first version (PCP_v2) becomes the default version and PCP_V1 gets deprecated. Please be informed, after April 1st, PCP_V2 becomes the default part of Reservation_API


Q: What would <reservation>/ <total_price> and  <reservation>/ <room>/<total_price> represent when PCP v2 is turned on?
A: Please refer to the Technical documentation for details.

 
Q: What is the capability assessment  process for PCP_V2? 
A: This is a visual and technical verification of the partner’s system with a member of the Professionals Services team to confirm that all relevant VCC, tax and charge details are available in a way that their connected properties are able to easily consume and action on this information.

The partner will give a walkthrough to demonstrate how this feature works in their system. If the visual and technical checks pass, the Professional Services team will confirm that the implementation is approved. If not, recommendations will be provided and another capability assessment should be scheduled.

We’ll be sharing more details on the process soon.

Q: When do I need the self-assessment guidebook?
A: Once you implement PCP_V2 and run the testing, you can refer to the self-assessment guidebook to ensure whether implementation has been done as expected or not. The guidebook will be available soon in the third week of March.