Lodge Card Processes
How lodge-card payments are captured, matched and settled in Midoco.
This Knowledge Base article endeavours to inform you about Level 3/Enhanced Data delivery for credit card transactions in Midoco Midoffice.
Both, the card brand and the card issuer have a bearing on the process in Midoco Midoffice due to the partner´s/interface´s capabilities.
General process overview
The lodge card or enhanced data process for credit cards in Midoco Midoffice consists of both, detecting a card that might require such data as well as transmitting the data through the corresponding interface.
For that process, the payment transaction itself does not necessarily take place in Midoco. It´s also possible (dependig on the interface capabilities) to just transmit the data enhancement for a payment that e.g. happened in the GDS. This requires DC settings on the supplier.
In order to get the lodge card process started and running, here is the how-to:
- Please inform Midoco about the mandatory fields of a lodge card.
- Midoco needs to have an interface for the enhanced data delivery in place.
- The enhanced data for an individual booking need to be provided in Midoco.
- The delivery process has to be triggered.
Let´s be specific
Mandatory Fields
Midoco is able to do a validation for you, which checks for all mandatory information being present for a credit card. That validation is based on the mandatory fields setup being known in Midoco.
To detect a lodge card and their mandatory field requirements, there are two checks in Midoco Midoffice:
- The lodge card BIN Range(s) are communicated to Midoco and set up in background. A BIN Range is basically digits 1 up to 6 of a credit card number.
- The mandatory field definition of a specific lodge card is communicated to Midoco and set up in background.
This article will provide you with details regarding those two checks and how that data is/needs to be provided to Midoco.
Interfaces
Airplus/Acceptance UATP Cards
Midoco´s Airlus TAMARA 1.40 interface not only handles the payment transaction (so transmitting money from the customer card to the merchant account) but also the enhanced data transmission.
When issuing the invoice in Midoco (printing it, not only preparing it), the payment authorisation is done.
On a successful authorisation, the invoice is dispatched an the data is prepared for the once-a-night TAMARA transmission batch including the enhanced data hand-off.
Detecting the lodge card and mandatory fields: Airplus
All UATP card numbers of Airplus are in scope for the enhanced data delivery.
There is an automatic request to Airplus for the mandatory fields triggered by Midoco, which means you do not have to take action.
Airplus Virtual Cards
Airplus has another card product in use with its Virtual Accounts based on issuing virtual MASTERCARD card numbers. Here the transmission process to Airplus is identical to the UATP process. Airplus expects a slightly modified type of additional data delivery (a different dialect of the TAMARA 1.40 delivery). However, this has purely technical implications and no discernible difference for you when working with Midoco Midoffice.
Detecting the card requirements
Having said the above, there is a difference in the setup, though.
Contrary to UATP, with the virtual credit card product of Airplus the required data definition is not found on the virtual card itself but on the parent Airplus Account. Hence Midoco would need to know this Airplus Account Number (12digit number starting on 14...) in order to request the required and optional fields definition set up for that account.
There are 2 options for that required setup in Midoco:
- Should you also be entitled to create virtual credit cards on behalf of your client you may use Midoco´s virtual credit card functionality. The linked article describes the setup of the Airplus Account Number in CRM.
- In case you want to do the TAMARA enrichment for virtual cards only, please set up a CRM attribute having the Type ID 'AIRPLUS_VIRTUAL_CARD_ACCOUNT' (spelling needs to be exactly like that, description ). After that, please assign this attribute to your client's CRM profile in Midoco and enter the clients Airplus Account Number in that attribute.
Detecting the lodge card and mandatory fields: Airplus Virtual Cards
Having the above setup in place retrieving the mandatory field definition for the virtual cards is handled alike the UATP process in background.
American Express (BTA/IBTA/LVAN)
American Express both issues Corporate Cards and Consumer Cards. Corporate Cards - namely BTA/IBTA and LVAN are the ones that require an enhanced data feed.
Midoco´s American Express interface covers lodge cards as well as regular corporate cards and consumer cards and processes both the payment transaction itself as well as the lodge data enrichment. When prining the invoice, Midoco triggers the authorisation request on a billing position level to American Express checking for the card to have sufficient limits.
A successful authorisation results in the invoice print being finished and the payment to already be registered.
In a nightly batch request (TADC) Midoco both captures the payment and submits the lodge data enrichment for that transaction.
Detecting the lodge card and mandatory fields: AMEX
American Express offers a data feed to communicate (almost all) information Midoco users require for the lodge process. As important information is missing in that feed and the process described below would be needed nevertheless, the feed is currently not used/implemented.
American Express Lodge Cards (so the ones requiring enhanced data) are designed and issued for a specific cardholder-merchant combination.
- Midoco was provided with AMEX BIN ranges of their lodge card products.
- This is where you are required to take action:
- Please create a / find your customer in Midoco CRM (the CRM ID will be needed).
- Please set up the AMEX lodge card as a credit card in the customer's CRM profile (the returned Midoco Token will be needed).
- Please fill the Template for the Lodge Card Setup
- In case you are wondering how to fill that document, please get in touch with AMEX (as they set up that definition you need to provide in the document)
- Please issue a Helpdesk Request of type Lodge Card Setup, provide the CRM ID and the Midoco Token for which you want us to do the mandatory fields setup.
BTA/IBTA/LVAN required information
Next to the mandatory fields that can be set up with a card there are travel information which American Express requires to be provided in the interface. They vary by item type.
For good messure, the following fields should be provided - Midoco at least is going to check for the ones that are displayed in bold text and will result in an error message in the application when missing or wrong format.
General
- Consultant/Agent Name
- Destination Name
- Traveller First Name
- Traveller Last Name
- Supplier Name
- Invoice Number (Billing Document Number in Midoco)
- Invoice Date
Flights/Tickets
- Ticket Number (3 digits BSP Validator, 10 digits Ticket Number)
- Ticket Issue Date
- Ticket Print Type (E or P)
- (all tickets need assignment to min. 1 segment)
- Segments incl:
- Departure Code (3 Letter Code)
- Arrival Code (3 Letter Code)
- Departure Date
- Arrival Date
- Carrier (2 Letters)
- Flight Number (1-4 Digits)
Rail
- Booking ID
- Departure Date
Hotel/Accommodation
- Check-In Date
- Check-Out Date
- Price (given in the Accommodation Details tab)
- Booking ID (Folio Number)
Car Hire
- Pick-Up Date
- Pick-Up City Name
- Drop-Off Date
- Drop-Off City Name
- Booking ID (Car Rental Agreement Number)
Diners Club Europe
Midoco's interface to Diners Club Europe both covers the payment transaction and the enhanced data delivery. In contrast to the other interfaces, Diners Club Europe does not require an authorisation of the payment transaction.
This interface was designed by Diners Club Europe to only cover EUR currency transactions. For non-EUR transactions, please check our Dataflexnet interface.
Detecting the lodge card and mandatory fields: Diners Club Europe
- Midoco got a list of BIN Ranges of Diners Club Europe lodge cards and sets the ranges in background for you.
- This is where you are required to take action:
- Please create a / find your customer in Midoco CRM (the CRM ID will be needed).
- Please set up the lodge card as a credit card in the customer's CRM profile (the returned Midoco Token will be needed).
- Please fill the Template Lodge Card Setup
- Please issue a Helpdesk Request of type Lodge Card Setup, provide the CRM ID and the Midoco Token for which you want us to do the mandatory fields setup.
OLB MASTERCARD (via Travelbasys)
Midoco, Travelbasys and the card issuer OLB Bank built an enhanced data feed for OLB issued MASTERCARD lodge cards.
The payment transaction itself and the lodge data feed use separate interfaces. The payment transaction itself (so moving money from the cardholder to the merchant account) needs to be triggered using your established payment provider for MASTERCARD transactions in Midoco Midoffice.
The enhanced data feed uses a separate interface that transmits the data to our partner Travelbasys who takes care of feeding OLB Bank with the data in the expected format.
OLB Bank and the service provider Travelbasys can only do the data matching between the enhanced feed sent by Midoco to the financial transaction sent by the PSP when:
- Individual Invoices are issued (not bulk invoices which may be open for several days/weeks).
- Invoice issuance (printing the invoice) should be done immediately (aka on the day the financial transaction happened) without any delay. Printing the invoice later causes matching issues or prevents matching at Travelbasys at all.
Detecting the lodge card and mandatory fields: OLB MASTERCARD
Both, the BIN Range announcement as well as the information about mandatory fields for individual card numbers is done via a background process.
You do not need to take action here.
VISA (via Travelbasys)
Similar to the Degussa process described above, VISA lodge cards are handled in Midoco Midoffice, meaning:
The VISA payment transaction is done using your established payment provider for VISA transactions in Midoco Midoffice.
The lodge data feed is triggered as a batch transmission sending the data to our partner Travelbasys who takes care of feeding VISA with the data.
Detecting the lodge card and mandatory fields: VISA
Both steps are covered automatically in a background process.
Midoco received the information of newly created lodge cards incl. their mandatory field definition.
Your customer who requires enhanced credit card data needs to get in touch with their card issuing bank.
The lodge card issuing bank of your customer needs to get in touch with VISA informing them that they expect an enhanced data feed for this card.
VISA will take all required follow-up action.
Dataflexnet (MASTERCARD and Diners non-EUR)
GLOBAL-815 - Enhanced Credit Card Information Feed (brand-independent) via DATAFLEXNET Geschlossen
MASTERCARD also issues lodge cards alike VISA. Our partner Dataflexnet is able to handle the enhanced data collection and transmission to MASTERCARD.
The same applies to lodge data for Diners Club Cards having non-EUR transactions (or mostly non-EUR transactions)
The Dataflexnet interface description and setup requirements are detailed in the linked article.
Detecting the lodge card and mandatory fields: Dataflexnet
As there is no process available to feed Midoco automatically with Lodge Card Setup information, using this interface requires you to take action.
In case we do not get the following information from you, we are not able to trigger any enhanced data feed for that card.
This refers to the below-mentioned two bullet points:
- Midoco does not get any kind of feed, not even a BIN Range indicator, so Midoco relies completely on getting the information provided by you.
- Your action is required:
- Please create a / find your customer in Midoco CRM (the CRM ID will be needed).
- Please set up the lodge card as a credit card in the customer's CRM profile (the returned Midoco Token will be needed).
- Please fill the Template for the Lodge Card Setup
- Please issue a Helpdesk Request of type Lodge Card Setup, provide the CRM ID and the Midoco Token for which you want us to do the mandatory fields setup.
- Midoco Helpdesk will also take care of setting the BIN Range of the Token you provided in Background.
Provide the individual data
Once the setup process is done for the lodge card (described above), it´s time to get the process started:
For each individual trip/order you would need to provide the corresponding enhanced data that apply to this trip/service (e.g. the cost centre, the project code, the orderer etc.)
This can be done either by
- transmitting the data via Remark or
- entering the data manually in the order.
On detection of a lodge card with corresponding lodge card setup in Midoco the application will check for the mandatory fields of that card and will remind you in case data is missing or of a wrong syntax.
Printing the invoice is only possible in case the mandatory information is provided correctly.
Trigger the lodge/enhanced data delivery
Once all the mandatory information is provided in the order/ in the billing document, you are only left with one task to do: print the invoice.
Just preparing the invoice but not printing/issuing it, will not do the trick, it´s the invoice issue process which is going to trigger both the payment transaction itself and the enhanced data feed.