Introduction

Some Reservation Module (RM) connectors require bookings to be paid for at the time of booking.  Dolphin Dynamics have integrated with Travelfusion's tfVPay offering, to allow RM customers to securely process certain supplier payments in real-time via single use virtual cards. 

This integration is currently in place for Web Fares (e.g. easyJet) and Expedia Rapid V3 hotels.

RM booking flow with a single use virtual card

1. RM user adds to the cart a product that needs to be paid for at the time of booking.
2. Supplier is configured to be paid via tfVPay (therefore using a single use virtual card as form of supplier payment).
3. User clicks on the Book button.
4. The RM sends a request to tfVPay to generate a single use virtual card. NOTE: The RM requests a single use virtual card per booking. If a folder includes two bookings configured to be paid via tfVPay, the RM requests two single use virtual cards.
5. If the single use virtual card is successfully issued, tfVPay replies to the RM providing all the credit card details. NOTE: At this stage, the credit on the tfVPay account is decreased by the value of the single use virtual card, but the card is not charged yet.
6. The RM attempts to make the booking with the supplier using the credit card details provided by tfVPay.
7. If the booking is successful, the connector charges the single use virtual card.  The tfVPay account balance is depleted by the appropriate amount.
8. If the booking is not successful, the single use virtual card is not charged. NOTE: When the single use virtual card is not used, the RM automatically sends a request to tfVPay to cancel the single use virtual card. If the single use virtual card cannot be cancelled via the API, the RM user will be presented with a message to contact their system administrator to manually cancel the single use virtual card on the tfVPay portal.
9. If the single use virtual card cannot be issued, the booking will not be attempted.

Configuration Changes

To support the integration of tfVPay some RM settings have been changed or introduced:

Product Connector

• In the RM Settings > Product Connectors > Other Connections tab > tfVPay has been added as a connector/virtual payment provider.
• This is where your tfVPay credentials will be configured, thus enabling tfVPay as a form of payment in the RM.

Supplier card details settings

• In the RM Settings > Suppliers > Card Details tab contains a new credit card name option called Travelfusion (tfVPay).

Supplier payment settings

• The RM Settings > Suppliers > Payment tab is used to associate specific connectors/web fares airlines with a payment method.
• Once Travelfusion (tfVPay) is configured in the Card Details tab, the Travelfusion (tfVPay) option will be available in the Credit card dropdown.

Changes to the booking flow

The booking flow will not be affected by the adoption of tfVPay single use virtual card. If anything, it will be more seamless as virtual cards will be issued behind the scenes and it will no longer be necessary to enter card information into the RM manually .
One small change worth mentioning is when tfVPay is configured as the payment method, the Payment to vendor section appears as follows:

If you wish to enable tfVPay in the RM, please email our Support Team at support@dolphind.com.