Skip to content
  • Package Travel Protection
  • Payments
  • Traveller Support
Menu
  • Package Travel Protection
  • Payments
  • Traveller Support

Onboarding

  • Onboarding Process
  • Documents required for Onboarding
  • Step by step guide to completing the Trust My Travel application form
  • Onboarding FAQs

Integration

  • Direct Integration: API
    • API Tokens 
    • HOW TO FIND TEST CREDIT CARDS 
    • API Integration FAQs
    • How to find your Channel Secret API Key
    • Integrate with us via API
    • How to find your Site ID, Site Name and Site Path
  • Indirect Integration: Third Party Systems
    • Integrate via your Reservation System
  • No Integration Required
    • How to create a Manual Booking

Frequently Asked Questions

  • Transaction Decline FAQs
  • Selecting a Base Currency FAQ’s
  • 3D Secure FAQs
  • Accepting Payment FAQs
  • Allocation FAQs
  • API Integration FAQs
  • Chargeback FAQs
  • Email Receipt FAQs
  • Interchange Plus (IC++) pricing FAQs
  • Manual Booking and Payment Link FAQs
  • Multi-Currency Pricing FAQs
  • Onboarding FAQs
  • Refund FAQs
  • Rolling Reserve FAQs
  • Trust Protects.Me logo FAQs

Accepting Payment

  • Accepting Payment FAQs
  • Card Scheme Rules
  • Alternative Payment Methods
  • How to view your Processing Channels
  • How to check the status of a Processing Channel
  • How to add a new Processing Channel
  • Transactions
    • Transaction types
    • Transaction Statuses 
    • How to view Recent Transactions
    • How to locate a specific Transaction
    • Selecting a Base Currency for a Processing Channel
    • What to do when a Transaction is declined
  • Refunds
    • How to process a full or partial Refund
    • Errors when Refunding
    • Refunding a legacy platform booking
  • Fraud Tools including 3D Secure
    • Understanding why a 3D Secure transaction has failed
    • Countries where 3D Secure is required
    • Fraud Tools
    • 3D Secure FAQs
    • What is 3D Secure?

Declaring Transactions for Protection

  • Option 1: Email the Support Team
  • Option 2: Use the “Bulk Upload” button for CSV files
  • Option 3: Uploading Transactions for declaration via API
  • Option 4: Manually declare a Transaction

Chargeback Management

  • What is a Chargeback?
  • Chargeback email notifications
  • Disputing a Chargeback
  • Dispute Codes and Supporting Documentation
  • What is a Retrieval Request?
  • Pre-Arbitration
  • Chargeback Statuses
  • Chargeback updates to the Infinity Platform -Q4 2022
  • Chargeback FAQs

Getting Paid

  • Pay-outs
  • Release Schedules
  • Trust My Travel fees and terminology
  • How to export / download a Statement
  • Understanding Exported Statements
  • Add or Update your Bank Details
  • Trust Ledger
    • Understanding the Trust Ledger ‘Owing’ and ‘History’ tabs
    • How to find the running balance of Available Funds
    • Credits and Debits Tab

Glossary

  • Glossary

Navigating the Infinity Platform

  • Accessing the platform
    • Setting your Password
  • Main Menu > Dashboard tab
    • Your Platform Homepage
  • Main Menu > Bookings tab
    • Amending a Payment Request on the Dashboard
    • How to locate a specific Booking
    • Unique Trust ID’s for Bookings and Transactions
    • How to check the status of a Booking
    • Manual Bookings
      • How to create a Manual Booking
      • How to create and edit a booking  to charge a deposit and a final payment
      • How to change the Balance Due Date
      • How to pre-define your company address
      • How to send a Payment Request email
      • How to edit a Manual Booking
      • Manual Booking and Payment Link FAQs
  • Main Menu > Channels tab
    • How to view your Processing Channels
    • How to check the status of a Processing Channel
    • How to add a new Processing Channel
  • Main Menu > Transactions tab
    • Transaction Statuses 
    • Unique Trust ID’s for Bookings and Transactions
    • Transaction types
    • How to view Recent Transactions
    • How to locate a specific Transaction
    • What to do when a Transaction is declined
    • Multi-Currency Pricing FAQs
    • Email Receipt FAQs
    • Refund FAQs
  • Main Menu > Ledger tab
    • Understanding the Trust Ledger ‘Owing’ and ‘History’ tabs
    • How to find the running balance of Available Funds
    • Credits and Debits Tab
  • Main Menu > Statements tab
    • How to view a payment or transaction from your Statement 
    • How to locate a specific Statement
    • Understanding Exported Statements
    • Trust My Travel fees and terminology
    • How to export / download a Statement
    • Rolling Reserve FAQs
  • Your Analytics page
    • Dashboard Analytics
  • Main Menu > Allocations tab
    • How to manually allocate funds between Channels
    • How to reverse an Allocation
    • How to edit an Allocation 
    • How to view and locate Allocations
    • Allocation FAQs
  • Main Menu > Credits and Debits tab
    • Credits and Debits Tab

Compliance

  • Displaying the Trust Protects.Me logo
  • Card Scheme Rules
  • Home
  • Knowledge Hub
  • Declaring Transactions for Protection
  • Option 2: Use the “Bulk Upload” button for CSV files

Option 2: Use the “Bulk Upload” button for CSV files

Your CSV file must be in a set format with the column headings – you can contact the support team who will provide you with a Financial Protection import template

Step 1 

Login to the Infinity Platform 

Step 2 

Select “Transactions” from the main menu, on the left-hand side 

Step 3 

Select “Bulk Upload” on the top right 

Step 4

Upload your CSV file

Step 5

Click on ‘Import’

Step 6

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

*Please note you will need to clear all contents outside of your data, a step by step on how to do this is included in ‘Hints and Tips for a successful upload’*

Step 7

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

Step 8

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. ** 

Step 9

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

A successful upload will look like this:

Step 10

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

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

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

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.

Hints and Tips for a successful upload

File FormatThe file must be in a set format with the column headings – you can contact the support team who will provide you with a Financial Protection import template.

Please ensure no special characters are used in the names or description columns as this will cause the file upload to be unsuccessful.
SpacesPlease ensure that there are no ‘spaces’ after the name in the following columns:
booking_firstname
booking_surname
transaction_payee_name
transaction_payee_surname
Upload File Codes2 Letter ISO Country codes
Codes in the correct format can be found here: 2 Letter ISO Country Codes 
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

 3 Letter Currency codes
Codes in the correct format can be found here: 3 Letter Currency Codes

PSP ID Codes
PSP ID Codes in the correct format can be found here: PSP ID Codes
PSP ID must be used, not name of PSP.
Empty fieldsCheck below which fields are mandatory.
Do not put dashes or anything else in empty fields.
Column Name
Channels
This must be the correct channel ID from the TMT Dashboard that you wish these transactions to be declared against
This field cannot be empty.
https://trustmytravel.com/knowledgehub/view-channels/
Column Name
Booking_Date
The booking date must be typed in using the correct format yyyy/mm/dd
Column Name
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.
Column Name Transaction_TotalTransaction total in cents.
Values must not have a decimal point e.g., £100.00 should be put as 10000
Only positive values are permitted
Column Name
Booking_id
This is not a Transaction Trust ID.
To find the Booking Trust ID check out this help page.
https://trustmytravel.com/knowledgehub/locate-booking/
 
Have you amended the Booking Total to reflect this addition?
To do this you need to:
Locate the booking on the TMT dashboard and click ‘Edit’
Amend the Total Value to equal the value of the amount paid PLUSthe amount you wish to be paid.
Press the green ‘Save’ button once you have finished your edit.
https://trustmytravel.com/knowledgehub/deposit-final-payment/
Errors and Failed UploadsIf 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.

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.**
Clearing contents for blank lines and columnsIn order to upload successfully you will need to clear any cells outside of your data. Please follow the quick step by step on how to do this below;

• Highlight the empty lines / rows by using the command Ctrl + Shift + The down arrow key
• Right click and click Clear Contents

• Highlight the empty columns by using the command Ctrl + Shift + The right arrow key
• Right click and click Clear Contents

CSV File Layout

Please check below to:
1. Identify which columns are mandatory.
2. Help you identify what should be put in those fields.

Column Name MandatoryNotes
channelsYesTMT ID of the processing channel in use.  

This must be a Protection Only channel. 
booking_first name YesFirst name of customer the booking is for. 
booking_surname YesSurname of customer the booking is for. 
booking_email YesValid email address of customer the booking is for. 
booking_date YesThis 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. 
booking_description YesDescription of what the booking consists of, and therefore what is being protected. 
booking_total YesBooking 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. 
booking_countries YesISO 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: 2 Letter ISO Country Codes 
Only one country code should be supplied – use the country where most of the booking takes place. 
transaction_currencies YesISO 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: 3 Letter Currency Codes
transaction_total YesTransaction total in cents. 

Values must not have a decimal point e.g., £100.00 should be put as 10000 

Only positive values are permitted 
transaction_psp YesID of the PSP (Payment Services Provider) used to process the transaction.  

IDs can be obtained here PSP ID Codes
PSP ID must be used, not name of PSP 
transaction_payee_name YesFirst name of the customer who made payment 
transaction_payee_surname YesSurname of the customer who made payment 
transaction_payee_email YesValid email address of the customer who made payment 
transaction_payee_countries YesISO 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:
2 Letter ISO Country Codes 
booking_pax NoNumber of people the booking is for. 
booking_reference NoYour reference for the booking. 

This is not mandatory but will be useful for you cross checking your bookings on our dashboard 
transaction_last_four NoLast four digits of credit card used for payment. 
transaction_bin_number NoBIN number of credit card used for payment.  

A BIN (bank identification number) is the first four to six numbers that appear on payment cards  
transaction_card_types NoYou can only use 1 of the 5 words as written below. 
Any variation and the upload will fail.  
These must be input in lower case with no capital letters. 
 
visa  
master  
amex  
discover  
other 
booking_id Yes, if an additional transaction is being added to an existing booking Booking Trust ID of a previously uploaded booking that is having an additional transaction added
(e.g., 3-3772430). 

Paying for your Protection

  • You will see an invoice (Statement of Fees) on the dashboard on the 1st of each month.  
  • An invoice will also be sent to you by the Trust My Travel 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.
Option 1: Email the Support TeamOption 3: Uploading Transactions for declaration via API

Get Started

Apply Online

Platform Login

Password Reset

Quick Links

Protection

Payments

Support

Knowledge Hub

Integration Documentation

Traveller Support

Terms

Worldwide Privacy Notice

Trust My Travel Terms of Service

Registered in England & Wales: 07686 704 VAT Number: 123 332 066

Thank you for your message and interest in Trust My Travel.

We will get back to you with an answer within 48 hours.