Getting Started tfPay OTAs, TMCs, OBTs

    •    Review the guide of tfPay solution (this guide)
    •    Complete and send back to us the tfPay Go live check list (it will be sent separately)
    •    Configure your requests to our API (In this guide too)
    •    Make a deposit (if it is your selected payment method)
    •    We/TF set up an account and provide you the credentials
    •    Run tests (more details will be provided at the later stage)
    •    Once you are satisfied with tests, you go live with TF.Prepaid bookings

STEP 1: AGREEMENT

In order to discuss and have a tfPay Agreement in place please contact our Sales or Accounts team at: sales@travelfusion.com.

STEP 2: PROFILE SETUP

Once the agreement is signed our Operation Team will set up your company’s profile (branch configuration and suppliers) according to your requirements. Please view the suppliers we support.

STEP 3: SELECT tfPay OPTIONS

A) tfCB (Travelfusion CashBack) Deposit / Credit
Customer sets up a deposit account with Travelfusion in your chosen currency. Travelfusion manages the payment and settlement for each booking and the booking amount will be deducted from your deposit. Detailed online reports show the account activity and deposit balances. You will be charging your customers directly. 

In case of the Credit option, the logic works similar to tfCB Deposit option, but you don't need to deposit with us the money in advance. TF will pay to the airlines with our payment solutions and you need to clear your credit in certain periods or when you reach a specific amount of credit.  The tfCB Credit  is only available after an evaluation from our @Finance Team, please take in consideration below 2 points:

1. What is your estimated booking numbers and spending per month? amd

2. A bank guarantee is needed in order to join TF.Credit solution. 

B) tfMerchant
In this case Travelfusion acts as the merchant processing the card which is submitted at the time of booking. Travelfusion then settles directly with each supplier. To activate TF.Merchant you will need to discuss with Travelfusion how to ensure that there are no fraudulent transactions.

Option tfCB Debit/Credit
This option enables having a deposit or credit account with Travelfusion with the following considerations:

A. Branch TF.pay Configuration: managed by our Operation Team;
B. Deposit/Credit Currencies: You have the option to select one or any number of currencies for your deposits/balances. Deposit currencies available are: AUD, USD, GBP, EUR, JPY, SGD, THB, TRY, NOK, SEK, DKK, PLN, HKD, CNY
C. Currency Exchange Rates, valid at the time of the transaction, are applied for payments made by Travelfusion in the supported currencies, and quoted and charged to your deposits. 
D. Non-Deposit Currencies: Currency exchange rate charges apply to payments made to travel suppliers using currencies that are not listed above in section B.
E. Billing Details: Both options, 'Process Bookings by Applicable Criteria’ and 'Always Process Bookings as Travelfusion Payment' require that you provide Travelfusion with an always up-to-date and valid credit card and billing information.
F. Fares, Currencies & Mark Ups: It is possible with tfCB to configure your account to return detailed information on fares including a variety of fees, such as transaction fees; as well as add mark-ups at the search stages of the booking process; and manage agents’ preferred currencies.

Option tfMerchant
In this option you allow Travelfusion to be the Merchant for either the full transaction or just the booking fee portion of it with the following considerations:

A. Branch Configuration: managed by our Operation Team.
B. Form of Payment (FOP): You need to submit either your own or your customer’s FOP to Travelfusion.
C. Fares, Currencies & Mark Ups. It is possible with tfMerchant to configure your account to return detailed information on fares including a variety of fees, such as transaction fees; as well as add mark-ups at the search stages of the booking process. 

STEP 4: API CONFIGURATION FOR 

1)  tfCB Debit/Credit

Flights and Rail 

This configuration is applicable only when bookings are processed as Travelfusion Payment and not valid when using the tfMerchant. In the ‘ProcessDetails’ response Travelfusion flags ‘UseTFPrepay’, as an optional RequiredParameter, if the booking is processed as a Travelfusion payment. Please note that this is a per-booking parameter and Travelfusion may not return ‘UseTFPrepay’, even if the booking is for the same supplier.

<RequiredParameterList>
<RequiredParameter>
<Name>UseTFPrepay</Name>
<DisplayText></DisplayText>
<PerPassenger>false</PerPassenger>
<IsOptional>true</IsOptional>
</RequiredParameter>

Later on, in ProcessTerms request, you need to submit below value under ‘UseTFPrepay’.

Value: “Always” Process Bookings as Travelfusion Payment: This booking will always be processed as Travelfusion payment, and the credit card details you submit to us will be ignored and will not be submitted to the supplier.

The final price we return in the ‘ProcessTerms’ response is the estimated price for the card type that was submitted to us in the Terms request. If you chose ‘Always Process Bookings as Travelfusion payment’, we will select a credit card type.

In ‘ProcessTerms’ request, the parameter ‘UseTFPrepay’ need to be submitted within the BookingProfile XML element, for the entire booking, and not on a per-passenger basis. In this stage you also need to submit the full billing details, which include full credit card details including the card type.

<CustomSupplierParameterList>
<CustomSupplierParameter>
<Name>UseTFPrepay</Name>
<Value>Always</Value> 
</CustomSupplierParameter>
</CustomSupplierParameterList>

The ‘UseTFPrepay’ parameter gives you the flexibility on a per booking basis. Furthermore, it allows you to support a quick switch back to a non-payment by Travelfusion configuration. It is also useful to cater for cases, in which a payment method cannot be supported (i.e. you run out of credit). tfPay generates alerts and advises us when to inform you of such cases. We ask you to respond to these alerts as quickly as possible.

Booking stage: tfPay returns the final booking price, based on the response from the supplier. Price changes from the Terms stage to the final booking response are rare but we know they can happen, for various reasons. Please note that if you change the end-user’s card, before you submit the booking request to Travelfusion, you may need to cater for cases, in which the charge is higher than quoted in the ‘Terms’ response.

Hotels
This configuration is applicable only when bookings are processed as Travelfusion payment and not valid when using the tfPay Merchant payment methods. In the CheckDetailsHotel response Travelfusion flags ‘UseTFPrepay’, as an optional RequiredParameter, if the booking is processed as a Travelfusion payment. Please note that this is a per-booking parameter and Travelfusion may not return ‘UseTFPrepay’ even if the booking is for the same supplier.

<RequiredParameterList>
<RequiredParameter>
           <PerRoom>false</PerRoom>
<Name>UseTFPrepay</Name>
<DisplayText></DisplayText>
<PerPassenger>false</PerPassenger>
<IsOptional>true</IsOptional>
</RequiredParameter>

Later on, in StartTermsHotel request, you need to submit the value ‘Always’ under ‘UseTFPrepay’. Here is where you specify the payment logic you selected (see ‘Payment Logic’ above).

“Always” Process Bookings as Travelfusion Payment: This booking will always be processed as Travelfusion payment, and the credit card details you submit to us will be ignored and will not be submitted to the supplier.
The final price we return in the ‘ProcessTerms’ response is the estimated price for the card type that was submitted to us in the Terms request. If you chose ‘Always Process Bookings as Travelfusion Payment’, we will select a credit card type.

In StartTermsHotel request, the parameter ‘UseTFPrepay’ need to be submitted within the BookingProfile XML element, for the entire booking, and not on a per-passenger basis. In this stage you also need to submit the full billing details, which include full credit card details including the card type.

<CustomSupplierParameterList>
<CustomSupplierParameter>
<Name>UseTFPrepay</Name>
<Value>Always</Value> 
</CustomSupplierParameter>
</CustomSupplierParameterList>

The ‘UseTFPrepay’ parameter gives you the flexibility on a per-booking basis. Furthermore, it allows you to support a quick switch back to a non-payment by Travelfusion configuration. It is also useful to cater for cases, in which a payment method may not be supported because of insufficient funds (i.e. you run out of credit). tfPay generates alerts and advises us when to inform you of such cases. We ask you to respond to these alerts as quickly as possible.

Booking stage: tfPay returns the final booking price, based on the response from the supplier. Price changes from the Terms stage to the final booking response are rare but we know they can happen, for various reasons. Please note that if you change the end-user’s card, before you submit the booking request to Travelfusion, you may need to cater for cases, in which the charge is higher than quoted in the ‘Terms’ response.

2) tfMerchant Method

Flights, Hotels and Rail
This configuration is applicable only when you authorize Travelfusion to be the Merchant for either the full transaction or just the booking fee portion of a booking. Once we activate the Merchant method at our end the following changes in the booking flow are generated:
Additional taxes will be displayed, such as the 'Card Fee', under the Leg/Group price ‘TaxItemList’;
You will receive the following SupplierInfo item:

<SupplierInfoList>
<SupplierInfo>
<DisplayName>Merchant Booking</DisplayName>
<InfoType>text</InfoType>
<Info>The booking is being processed through the merchant system</Info>
</SupplierInfo>
</SupplierInfoList>

Please ensure that your system can parse this. Failing such means that the booking is not being processed through the Merchant System. We request that your application dynamically handles situations in which our operation team advises you of any de-activation of the merchant system.

STEP 5: DEPOSIT

This step is applicable when bookings are processed under the tfCB Deposit payment method. In this step we will setup your account in your preferred currency and then Travelfusion Finance Team will help you through the process of making your first deposit, by transferring funds into our account. Travelfusion requires an initial deposit of EUR/GBP 5,000.00 to cover the initial batch of bookings.

We have well-defined processes in place to provide you with full transparency (24/7 administrative system) and access to the status of your funds at any time that is closely monitored by our team.

STEP 6: TESTING

This step is designed to ensure that all the settings are in configured, ready to be implemented and requires a designated person from your organization to work with us. This step also includes testing your ability to switch back to a non-prepay configuration. Please note that TF.Pay does not support fake booking functionality. Though we recommend you to run tests as follows: You can submit a ProcessTerms request without completing a real booking (not submitting StartBooking request). The ReferenceId is TFBookingReference returned successfully indicates that your ProcessTerms request is good and TF.Pay works fine. Here you don't need to pay any fees instead it returns the final price that you are going to be charged. 

STEP 7: IMPLEMENT

After successful testing Travelfusion will grant you permission to switch on tfPay for tested suppliers and go into production.

STEP 8: SUPPORT

After the full implementation, you will receive support from our Accounts Management team. Billing reports will be sent to you on a quarterly basis. 

Special Notes:

Communication: It is important that we work closely together and have a constant communication hence please provide us with the contact details of the person at your organization who is responsible for managing your billing and Travelfusion account and whom our team can contact when needed.

Monitoring: Travelfusion monitors the live traffic and the state of your account, when the Payment Deposit method is used. Our system of automated alerts enables us to flag any bottlenecks preventing you from booking. We also monitor your account and will alert you in the event it falls into the red zone.

Access: Travelfusion offers you access to your bookings in our https://reports.travelfusion.com/ tool. 
Changes, Cancellations and Refunds: It is your responsibility to manage changes and cancellations directly with your suppliers regardless what payment method is used. Refunds are normally reimbursed to the original method of payment and will automatically appear as a credit on your account. We provide support on a case-by-case basis in the event that a refund to the end-user is needed.

Charges: Please note that some of these charges are in-corporated into the booking price while others are invoiced in the your Billing Report we generate every month.

CONTACT

For more information and any inquiry please contact sales@travelfusion.com.