How do I add a form of payment in Galileo?

In the booking file: F.S for cash, F.CK for cheque, F.VI4111111111111111/D1228 for a card; *FOP shows it. On a filed fare: TMU1FS or TMU1FVI4111111111111111*D1228, with *D instead of /D.
Unofficial guide, written with AI
GateRoam's own guide, written in our own words with the help of AI tools. It is not official Travelport documentation and has not been reviewed or approved by Travelport. It can contain mistakes: try every entry in a Travelport+ training PCC first, or check Travelport's own help, before you use it on a live booking. GateRoam is independent and not affiliated with or endorsed by Travelport. Travelport, Travelport+ and Galileo are trademarks of Travelport.
Not yet checked in a live office
Try the entries in a Travelport+ training PCC first: some rules differ by market and by office.

When

Use this card to record how the client pays before you issue. Galileo accepts the form of payment in two places: the booking file's payment field (F.) and the filed fare itself, as a ticket modifier (TMU1F…). It can also be given in the issue entry for one issue only.

Check first

  • Your agency's rule for its BSP stock: when the agency pays BSP (cash, invoice) and when the airline charges the client's card. Ask your senior agent if unsure.
  • For a card: the two-letter card code, the number, and expiry month and year.

Steps

#EntryWhat it doesWhy
1F.S · F.CKCash · cheque in the booking file.The usual non-card payments.
2F.INV20261012Invoice, with your reference after INV.Clients the agency bills.
3F.VI4111111111111111/D1228Card, expiry after /D as MMYY.Client's card in the booking file.
4*FOPShows the payment field.Check before issuing.
5F.@CK · F.@Replaces the payment with cheque · deletes it.There is one payment field per booking.
6TMU1FS · TMU1FVI4111111111111111*D1228Stores cash · a card on filed fare 1.In modifiers the expiry follows *D.
7TMU1P2F@SChanges the payment for passenger 2 only.Different payers inside one filed fare.
8TKP1P2F@CKIssues filed fare 1 for passenger 2, paid by cheque.A one-off change at the moment of issue.
9*FF1Shows the filed fare with its modifiers.Confirms the payment stored on it.

Smartpoint: the booking file script Create/Edit customer information → Payment fills the F. field with a form.

Check it worked

*FOP shows the booking's payment; *FF1 shows any payment stored on filed fare 1.

Traps

  • Two card syntaxes. The booking field writes the expiry as /D1228, ticket modifiers as *D1228. Copying one into the other is a classic slip.
  • An expiry date is needed on every card except UATP.
  • A card the airline does not accept can be forced with a manual approval code (F.CC…/D…/A…), but that is at your own risk: the agency may receive an ADM for it.
  • Card numbers go in payment fields only — never in remarks or the notepad.
  • Airlines that sell outside BSP may want the card as a booking guarantee in an SSR instead — see Direct payment carriers — book airlines paid directly, no ticket.

Related

Ticketing as a free PDF All free Galileo PDFs

Read next

Galileo MCP: connect Claude and ChatGPT to Travelport+

A Galileo MCP server lets Claude or ChatGPT search and price Travelport+ flights with your agency's own fares. What it does, what you need, how to connect.

Ask your AI assistant instead

This answer is one card of GateRoam's Galileo guide. Inside GateRoam your AI assistant reads the whole guide and answers in your own words, step by step. Connect Claude or ChatGPT. Free during early access, no Travelport keys needed. With your agency's Travelport access connected, it also searches and prices flights in Travelport+.