Worldline by Travel-Hub

Worldline is a global leader in secure payments and trusted transactions. Specifically tailored for the travel sector, Worldline by Travel Hub provides sophisticated payment processing for airlines, hospitality, and travel agencies.

As a payment and fraud orchestrator, our platform allows you to easily connect your Worldline by Travel Hub merchant account directly into your payment flow. This enables you to leverage Worldline's robust, travel-specific processing capabilities (such as flight/passenger data handling and tokenization) as part of a rules-based payment strategy, helping you optimize acceptance rates and reduce costs.

This guide will walk you through the credentials needed to connect Worldline by Travel Hub in our Admin.

Supported Operations by Country

Requisites

Before you can configure Worldline by Travel Hub in our Admin, you must have an active merchant account with them. During your onboarding, Worldline will provide you with a set of unique credentials for your Partner API integration.

Please gather the following required fields from your integration manager or welcome documents:

• MerchantID: Composed often by an 8-digit code provided by Worldline
• User: API user composed by 16-digit string provided by Worldline
• PassPhase: API password composed by 16-digit string provided by Worldline.

Configuration Steps

Connecting Worldline is a simple, one-time setup in our Admin portal.

1. Log in to your Admin portal.

2. Go to Connections.

3. Search for Elavon and click Connect.

   

4. A form will appear. Enter the following information and credentials:

2. Select if you want this connection in a Sale (Purchase) or Pre Authorization (Authorization) mode.
3. If required, you can enable our 3DS MPI to secure transactions with Worldline following this guide.
4. Click "Save".
5. Our system will validate the credentials, and Elavon will appear as "Active" in your list of connected processors.

Add Worldline to your transaction flow

Your Elavon connection is now active!

Go to the Payment Strategy section of the Admin to build rules that define which transactions are routed to Elavon.