Background
Due to RBI (Reserve bank of India) regulations on Liberalised remittance scheme in India, Indian residents are required to provide Permanent account Number (PAN- unique tax id for each tax payer), for all the foreign transactions. For PLS, this means, all the bookings for outside India hotels, where payment is collected by Rapid in INR currency would require PAN. While this regulation impacts majorly partners based in India, there could be few partners operating from outside India in INR currency and hence are impacted.
Requirement
The above regulation requires PAN number to be passed in each booking request for eligible bookings in the "tax_registration_number” field in the booking request. To ensure 100 % compliance, the booking API has been equipped with PAN validation logic which will cause the booking to fail in cases of no tax id (PAN), invalid tax id or a corporate tax id being provided. The booking API interacts with the India government’s PAN database via a third party API to perform the validation. Exclusively corporate partners and those partners on Expedia Affiliate Collect and paying Rapid in USD are exempted from the validation.
Example tax id
"tax_registration_number": "ADKRL6477H"
Expected Booking errors
In case the valid tax id is not being provided at the time of booking, the booking with fail with http code- 400 with one of the following 3 type of errors.
Http code 400
1. When tax_registration_number is Blank
| { |
| "type": "invalid_input", |
| "message": "An invalid request was sent in, please check the nested errors for details.", |
| "errors": [ |
| { |
| "type": "payments.tax_registration_number.required", |
| "message": "Tax registration number is required.", |
| "fields": [ |
| { |
| "name": "tax_registration_number", |
| "type": "body" |
| } |
| ] |
| } |
| ] |
| } |
2. When tax_registration_number is a corporate PAN number
| { |
| "type": "invalid_input", |
| "message": "An invalid request was sent in, please check the nested errors for details.", |
| "errors": [ |
| { |
| "type": "payments.tax_registration_number.is_corporate", |
| "message": "Corporate tax registration number provided.", |
| "fields": [ |
| { |
| "name": "tax_registration_number", |
| "type": "body", |
| "value": "XXXXXX" |
| } |
| ] |
| } |
| ] |
| } |
3. When tax_registration_number is Not valid (As per government’s data)
| { |
| "type": "invalid_input", |
| "message": "An invalid request was sent in, please check the nested errors for details.", |
| "errors": [ |
| { |
| "type" : "payments.tax_registration_number.invalid", |
| "message": "Tax registration number is invalid." |
| "fields": [ |
| { |
| "name": "tax_registration_number", |
| "type": "body", |
| "value": "XXXXXX" |
| } |
| ] |
| } |
| ] |
| } |
Switchbox setting – To be done by PC team
For all the in-scope profiles (cids/pids), Tax Registration Number Validation flag under Booking/Post booking tab needs to be enabled in Switchbox as below.
.
In Scope
- Bookings for properties outside India
- Bookings in INR currency
- Prepay bookings
Not in Scope
- Corporate specific profiles
- Profiles having Expedia Business Rates (EBR) enabled or Segments: Offline TMC or Online Booking Tool
- Affiliate Voyager Bookings- (Validation planned to be rolled out on 19th Oct 2023)
- EAC billing currency is USD or other than INR
Demo Link
Tableau Dashboard for PAN Errors
https://tableau-egap.sea.corp.expecn.com/#/site/EG/views/BookPANError/BookPANCalls?:iid=2
Comments
0 comments
Please sign in to leave a comment.