Uploading Bookings for Protection

Uploading Bookings to be financially protected

Three ways to upload Bookings, when the transaction has been processed outside of our system, to be financially protected

Hints and Tips for a successful CSV file

Errors

Paying for your Protection

Uploading your Bookings to be financially protected

  • Option 1: Email
  • Option 2: Manual Upload
  • Option 3: API Upload

Email your upload CSV file to trust@trustmy.group. The Support Team will upload the file for you.

The file must be in a set format with the column headings - you can contact the support team who will provide you with a protection only import template.

Please ensure no special characters are used in the names or description columns as this will cause the file to be unsuccessful. Also ensure there are no spaces after the name in the following columns:

booking_firstname

booking_surname

transaction_payee_name

transaction_payee_surname

If there any errors during the upload the Support Team may need to come back to you for clarification, and this will delay your bookings being Financially Protected.

 

When does Protection begin?

If you use this option, Customer Protection does not start until the CSV has been successfully uploaded to the Trust Protects dashboard and email confirmation has been received, so please ensure it is in the correct format to avoid delays.

Use the Bulk Upload button on the Trust Protects dashboard to upload your CSV file following the instructions below.

1. Go to the Trust My Travel dashboard

2. Select Transactions on the left-hand side

3. Select Bulk Upload on the top right

4. Upload your CSV file here

5. Click on Import

6. If you get an error message, you will see this screen

7. Click on the red error and a pop up will display telling you what you need to do to get a successful upload

8. When you do the second upload, only upload the failed records.

9. A successful upload will look like this:

** Please be aware that if you upload the entire file again you will create duplicate records and you will be charged twice. **

10. You can then check that your bookings have been uploaded by clicking on the bookings tab on the left-hand side

11. You can also check the transactions associated with the bookings in the transactions tab on the left-hand side.

12. These bookings are now protected, and you will receive an invoice at the end of the month.

 

When does Protection begin?

If you use this option, Customer Protection does not start until the CSV has been successfully uploaded and email confirmation has been received by the cardholder.

Use the API to bulk upload the bookings that you require protecting. Technical integration documentation can be found here: https://api.trustmytravel.com/#891392b5-ebcb-46a8-92cb-113f75524e3c

Use the API to bulk upload the bookings that you require protecting. You can upload the initial transaction/deposit and subsequent payments/final balance if the initial TMT Booking Trust ID is referred to.

https://api.trustmytravel.com/#8990192e-e83b-4b8a-afc7-4f2817424cda

When does Protection begin?

If you use this option, Customer Protection begins once the upload has been successfully received.

CSV File Layout

Please check below to

1. Identify which columns are mandatory.

2.help you identify what should be put in those fields.

Channels

TMT ID of the channel in use.
This must be a Protection Only channel.

Mandatory? Yes.

booking_firstname

First name of customer the booking is for.

Mandatory? Yes.

booking_surname

Surname of customer the booking is for. 

Mandatory? Yes.

booking_email

Valid email address of customer the booking is for. 

Mandatory? Yes.

booking_date

This is the end date of the tour or activity, and therefore when the booking is protected until.
Dates must be in this format YYYY-MM-DD (e.g. 2022-01-19) 

This is not the date that the booking was created. 

Mandatory? Yes.

booking_description

Description of what the booking consists of, and therefore what is being protected. 

Mandatory? Yes.

booking_total

Booking total in currency of channel in cents.
Values must not have a decimal point e.g. £100.00 should be put as 10000
Only positive values are permitted.
A booking must have a total.
This field cannot be empty.

Mandatory? Yes.

booking_countries

ISO 3166-1 alpha-2 country code for country the booking takes place in.
N.B. UK is GB in 2 letter country code.
Codes in the correct format can be found here: https://docs.trustmytravel.com/protection-only-psps/iso-codes.html
Only one country code should be supplied – use the country where most of the booking takes place.

Mandatory? Yes.

transaction_currencies

ISO 4217 currency code that payment was made in.  
This must be the same currency as the booking.  
Codes in the correct format can be found here: https://docs.trustmytravel.com/protection-only-psps/iso-codes.html  

Mandatory? Yes.

transaction_total

Transaction total in cents.
Values must not have a decimal point e.g., £100.00 should be put as 10000. Only positive values are permitted

Mandatory? Yes.

transaction_psp

ID of the PSP (Payment Services Provider) used to process the transaction.  
IDs can be obtained here https://docs.trustmytravel.com/protection-only-psps/.   
PSP ID must be used, not name of PSP 

Mandatory? Yes.

transaction_payee_name

First name of the customer who made payment.

Mandatory? Yes.

transaction_payee_surname

Surname of the customer who made payment.

Mandatory? Yes.

transaction_payee_email

Valid email address of the customer who made payment.

Mandatory? Yes.

transaction_payee_countries

ISO 3166-1 alpha-2 country code for country of the customer who made payment.
N.B. UK is GB in 2 letter country code.
IDs can be obtained here https://docs.trustmytravel.com/protection-only-psps/iso-codes.html

Mandatory? Yes.

booking_pax

Number of people the booking is for.

Mandatory? No.

booking_reference

Your reference for the booking. This is not mandatory but will be useful for you cross checking your bookings on our dashboard.

Mandatory? No.

transaction_last_four

Last four digits of credit card used for payment.

Mandatory? No.

transaction_bin_number

BIN number of credit card used for payment.  A BIN (bank identification number) is the first four to six numbers that appear on payment cards.

Mandatory? No.

transaction_card_types

Card type of credit card used for payment. You can only put visamasteramexdiscover or other - no other words can be used in this column and it must all be lower case.

Mandatory? No.

booking_id

Booking Trust ID of a previously uploaded booking that is having an additional transaction added (e.g. 3-3772430).

Mandatory? Yes, if an additional transaction is being added to an existing booking.

Upload File Codes

  • 2 letter ISO country codes
  • 3 letter currency codes
  • PSP ID Codes

Codes in the correct format can be found here: https://docs.trustmytravel.com/protection-only-psps/iso-codes.html 

Only one country code should be supplied – use the country where most of the booking takes place.

N.B. UK is GB in 2 letter country code

Codes in the correct format can be found here: https://docs.trustmytravel.com/protection-only-psps/iso-codes.html  

PSP ID Codes can be found here: https://docs.trustmytravel.com/protection-only-psps/

PSP ID must be used, not name of PSP.

Hints and tips for a successful file upload

Empty Fields

Check above which fields are mandatory.

Do not put dashes or anything else in empty fields.

Screenshot 2022-04-14 at 13.17.04
Screenshot 2022-04-14 at 13.12.24

Failed Upload

 If your upload file fails, you will be advised what has failed so you can rectify the issues and upload again. When you do the second upload, only upload the failed records.

**Please be aware that if you upload the entire file again you will create duplicate records and you will be charged twice.**

Errors

Upload file - errors
Screenshot 2022-06-17 at 14.46.19

If you receive an error and cannot find the clarification or resolution you need detailed above, please contact us at membersupport@trustmytravel.com attaching a screenshot of the error message. We will work with you to resolve the error(s) and ensure your bookings are protected.

Paying for your Protection

Screenshot 2022-04-14 at 09.54.08

You will see an invoice (statement of fees) on the dashboard on the 1st of each month.  

An invoice will be sent to you by the Accounts Department.

This invoice needs paying within 10 business days.

Payment details will be on the invoice.

If your invoice is not paid on time, it may mean future protection is suspended.