Task: Cruise Make Payment

The Cruise Make Payment task accepts payment for a booked cruise.

Section 1: Short Answer

Transaction Name:

CruiseMakePayment_1_0_1

Can any other transactions perform this same task?

No other transaction can perform this same task.

Can this task be performed in a sessionless environment?

This task can be performed in a sessionless environment.

Are the request and response identical on both the Apollo and Galileo systems?

The request and response are allowed only on Apollo.

Industry-specific knowledge required to understand this task.

Some LeisureShopper knowledge is required.

Special limits or distinct restrictions to the input data.

The same user ID that was used to reserve the cabin must be used throughout the payment process. Also, there is no cruise-industry standard for encoded data such as forms of payment, ports of call, and airports. Always confirm specific data formats with individual vendors.

Note: For Galileo Web Services client applications only, this transaction must be submitted using the SubmitCruiseTransaction method.

Section 2: Detailed Description

Request

Unless otherwise specified, use ALL CAPS in any request data.

The <CruisePaymentMods> is sent with the following to accept payment for the booked cruise:

<PNRInfo>. PNR/BF information.
<CreditCardPayment>. Credit card number, expiration date, and any other credit card information required by vendor (required if using credit card to pay).
<OtherFormOfPayment>. Other form of payment information, such as type of payment and information applicable to that form of payment (required if using form of payment other than credit card to pay).

Prerequisite Tasks

Payment rules for the selected vendor must be obtained prior to applying payment, using CruisePaymentRules_1_0.

Expected Response

If the Cruise Make Payment transaction completes successfully, the <CruisePriceBookingDetail> is returned with the following to indicate a good response:

<BookingDetail>. Selected package, cabin, fees, rate codes, booking status, time, dining option status.
<TextDisplay>. Vendor-supplied consumer advice text.
<CruisePrices>. The total base price of cruise and total price base on selected or applicable options, discounts, fees, and penalties.
<CruisePricePerPassenger>. Cruise prices broken out by passenger. This field may or may not be returned, depending upon the specific vendor response.
<UnavailableItems>. Requested items that are not available within the selected cruise package. This field may or may not be returned, depending upon the specific vendor response.

Error and Warning Responses

If Cruise Make Payment transaction encounters an error PRIOR to the End Transact, the <CruisePaymentInfo> with the <ErrText> tag is returned. If Cruise Make Payment transaction encounters an error AFTER the End Transact, the <CruisePriceBookingDetail> with the <ErrText> tag is returned. The following error messages may be received:

0002 – Transaction Not Allowed

0008 – Invalid Form of Payment

0014 – Invalid Credit Card Code

0015 – Invalid Document Number

0017 – Invalid Expiration Date

0027 – Invalid Data in Amount Field

0028 – Invalid Credit Card Number

0032 – Invalid Card Holder Name

0037 – Decimal Position Invalid for Specified Currency

0045 – Invalid Vendor Code

0046 – Invalid City Code

0048 – Invalid Currency Code

0054 – LeisureShopper Not Available

0119 – Invalid Address

0390 – System Error Occurred

1333 – Uniglobe Not Allowed

1340 – Invalid Vendor Record ID

1344 – Invalid Vendor Record ID

1354 – Invalid PNR Number

1355 – Invalid Package Start Date

1356 – Invalid Document Issue Date

9100 – Invalid Package ID

Text Not Found for MSG NBR - #### (error message number)

For a complete list of cruise errors, see Cruise Error Messages.

Follow-On Requests

Cruise Make Payment is the final required transaction in the cruise booking process.

Section 3: Tables

Request (Input) Tags

<BeginTransMods>

Terminal Equivalents:

Apollo: LSAP

Not available on Galileo.

Ordering	NWB	Min/Max	XML Tag
	2028	1-1	<BeginTransMods>

<PNRBFSecondaryBldChgMods>

Terminal Equivalents:

Apollo: LSAP

Not available on Galileo.

Ordering	NWB	Min/Max	XML Tag
	2110	1-?	<PNRBFSecondaryBldChgMods>

<CruisePaymentMods>

Terminal Equivalents:

Apollo: LSAP

Not available on Galileo.

Ordering	KLR	Min/Max	XML Tag
	LCM0	1-1	<PNRInfo>
	LCM6	0-1	<CreditCardPayment>
	LCM7	0-1	<OtherFormOfPayment>

<EndTransactMods>

Terminal Equivalents:

Apollo: LSAP

Not available on Galileo.

Ordering	NWB	Min/Max	XML Tag
	2030	1-1	<EndTransactMods>

Response (Output) Tags

<BeginTrans>

Ordering	NWB	Min/Max	XML Tag
	2029	1-1	<BeginTrans>

<PNRBFSecondaryBldChg>

Ordering	NWB	Min/Max	XML Tag
	2111	1-1	<PNRBFSecondaryBldChg>

<EndTransaction>

Ordering	NWB	Min/Max	XML Tag
	2031	1-1	<EndTransaction>

<CruisePriceBookingDetail>

Ordering	KLR	Min/Max	XML Tag
	EROR	1-1	<ErrText>
	LCBA	1-1	<BookingDetail>
	LCCX	1-1	<TextDisplay>
	LCPA	1-1	<CruisePrices>
	LCPD	1-1	<CruisePricePerPassenger>
	LCUC	1-1	<UnavailableItems>
	TEXT	1-1	<TextMsg>

<CruisePaymentInfo>

*Before End Transact

Ordering	KLR	Min/Max	XML Tag
	EROR	1-1	<ErrText>
	LCM8	1-1	<RejectedPayment> (currently not used)
	TEXT	1-1	<TextMsg>

Related Samples

CruiseMakePayment_1_0_1_1