Form of payment
HELP FOP or H/FOP
MyTravelport search: Enter Multiple Forms of Payment (FMR)
Once you know the form of payment that a passenger will be using to pay for their journey, there are several ways to enter the information into the booking file, and there are various forms of payment that can be added.
This topic covers:
-
Add form of payment using form of payment entry, ticket modifier update entries, using ticketing entry.
-
Cancel pending authorized funds
Add form of payment
One option is to use the booking file Form of Payment entry:
Format |
Explanation |
---|---|
F.S |
Cash |
F.CK |
Check / Cheque |
F.INV12345 |
Invoice number |
F.NONREF |
Non-refundable without reference to issuing agent |
F.VI4XXXXXXXXXX0028/*D1226*A1234 |
Credit card with date of expiry (no spaces in the credit card number), with a previously obtained approval number. Important note: If no approval code is added to the entry, the system will automatically seek approval for the fare amount again when the ticket is issued. |
F.MSFREETEXT |
Miscellaneous payment |
F.@CK |
To change the FOP to check/cheque |
Alternatively, add the form of payment to the filed fare, using Ticket Modifier Update entries:
Entry |
Description |
---|---|
TMU |
Ticket modifier update |
1 |
Filed fare number 1 |
F |
Form of payment entry code |
CK |
FOP code (check/cheque) |
Another alternative is to add the form of payment in the ticketing entry:
Entry |
Description |
|
---|---|---|
TKP1 |
Ticketing modifier update |
|
P1 |
Filed fare number 1 |
|
F |
Form of payment entry code |
|
CK |
FOP code (cheque) |
|
Find more information on how to display, modify and delete the Form of Payment in the booking file (FOP), in the Optional Fields section.
Add an authorization code to a form of payment stored as a ticket modifier (TMU)
HELP JV or H/JV
If you have previously obtained approval from a credit card company for payment for a ticket, you must add the authorization code to the TMU field; otherwise, the system will automatically seek approval again for the fare amount when the ticket is issued.
Refer to the following formats for credit card authorization/approval.
Format |
Explanation |
---|---|
JVVI4XXXXXXXXXXX1111/V1 |
Verifies the card only, no approval code |
JVVI4XXXXXXXXXXX1111/T410.00/D1226/MBA |
Request credit card approval mandatory expiry date, amount total, and airline vendor code |
Refer to the following format explanation:
JVVI4XXXXXXXXXXX1111/T410.00/D1226/MBA
Format |
Explanation |
---|---|
JV |
Function identifier |
VI4XXXXXXXXXXX1111/ |
Credit card number and separator |
T410.00/ |
Transaction amount in the currency of agency location and separator |
D1226/ |
Credit card expiry date and separator |
MBA |
Merchant and airline vendor code (BA) |
Once you have obtained approval for the transaction from the credit card company, store the approval code with the TMU entry.
Example for approval code A1254: TMU1FVI4XXXXXXXXXXX1111*D1226*A1254
Cancel Pending Authorized Funds from Customer Card Accounts
The JVR entry provides the ability for a request to be submitted for an approval code to be reversed. The function requires credit/debit card vendor code, number (Short or Full) and approval code that is to be reversed. This information is used to search an internal database for a match. If a match is found, a reversal request will be sent to the card issuer using data retained from the approval response. If no approval code match is found, the agent will receive an error response.
The release of Authorisation Reversals applies to multiple Credit Card Vendors including American Express, JCB, Discover, Diners Club, Mastercard and Visa cards. However, if a vendor does not allow a reversal an error will be returned.
The Travelport system database will store credit card approval codes for all transactions for ~30-calendar days and then the approval data will be purged from the system.
Input:
PPPCCNNNN/AAAAAA (Short entry)
PPPCCNNNNNNNNNNNNNNN/AAAAAA (Full entry)
Explanation:
Format |
Explanation |
---|---|
PPP |
Primary action code – JVR for Travelport+ (1G) |
CC |
Payment card vendor code |
NNNN |
(Short entry) – Last 4-digits of credit card account number |
NNNNNNNNNNNNNNNN |
(Full entry) – Full credit card account number |
XXXXXX |
Approval code – up to six (6) alphanumeric characters |
Example:
>JVRAX4004/003456 (Short entry)
>JVRAX3XXXXXXXXXXX004/003456 (Full entry)
Note: Enter the exact approval code as returned by authorization entry.
The approval code must be input as returned from the card vendor. An error will occur if approval code 3456 is entered with reversal entry, but the actual approval code returned by vendor was 003456.
Input Validation Error Responses:
Any error on card number validation:
Invalid length or invalid character in approval code:
Credit Card Reversal Response Messages:
Approved Reversal Response:
AUTH 432567 REVERSED |
---|
Non-Approved Reversal Response:
AUTH 432567 UNABLE TO REVERSE |
---|
MyTravelport search: Credit card errors
Response |
What it means |
---|---|
AUTHORISATION IS NOT ALLOWED |
The link in the vendor control database is set to OFF. Contact the Travelport+ Help Desk. |
CARD EXPIRED |
Telephone the card vendor for authorization |
CARD NUMBER/VENDOR DO NOT MATCH |
You have included the two-letter card vendor code in the entry that does not match the card number. Note: The card number also identifies the card issuer. You do not need to include the vendor code in your entry. |
CARD NOT VALID FOR USE ON TRAVELPORT GALILEO |
The optional vendor ID code is invalid, or the card number that was input does not match an existing vendor code. |
CARD NOT YET VALID |
Check whether the cardholder has another copy of the card which is about to expire and re-enter using the details of that card. Or call the card vendor for authorization. |