Payment Handling

With payments there is meant to inform on expected, desired and effected payments AND to enter payments; this all in line with the valid data protection requirements.

Whereby with a request one might enter payments whereas the responses will inform you on the status of the payments respectively.

Payment Request

A brief explanation of some information displayed here

Here we show the information only which is helpful for a general understanding. The detailed information on all available elements, attributes, values etc. can be taken from the XSD Documentation.

Attribute	Values / Explanation
@Identifier	Beispiel
@Collection	Agency For agency debiting TourOperator For tour operator debiting; i.e. the customer directely pays to the tour operator OnSite In case the payment must be made on site, e.g. a sports course offered by the hotel Mixed Signals that the Tour Operator excepts any encashement method, which here - for a concrete payment - must not be entered

Payment Response

As extension of the request we here have the following additional information

Visualization

So we might follow the following workflow:

1. Pricing request / quote This will display the expected payments with a status "open" which at least is the total payable amount of the booking. In that case the

2. Book Within the request you can enter one or more payments With the according response one will receive back the correspondign status from Tour Operator perspective

3. Retrieve / display the booking Herewith you will receive back respectively the latest status of the (entered) payments at that time