Payment Handling: Unterschied zwischen den Versionen

Aus DRV STRING
Wechseln zu: Navigation, Suche
(Die Seite wurde neu angelegt: „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 requir…“)
 
Zeile 7: Zeile 7:
  
 
[[Datei:Capture PaymentRequest(Type).PNG|730px|rahmenlos|ohne]]
 
[[Datei:Capture PaymentRequest(Type).PNG|730px|rahmenlos|ohne]]
 +
 +
 +
=== 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.
 +
 +
 +
{| class="wikitable sortable"
 +
|-
 +
! Attribute!! Values / Explanation
 +
|-
 +
| @Identifier|| Beispiel
 +
|-
 +
| @Collection||
 +
{| class="wikitable sortable"
 +
 +
| 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|| Beispiel
 +
|}
 +
 +
|}
  
  

Version vom 25. Mai 2018, 10:47 Uhr

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

Capture PaymentRequest(Type).PNG


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 Beispiel


Payment Response

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

Capture PaymentResponse(Type).PNG



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

Von „http://string.drv.de/wiki/index.php?title=Payment_Handling&oldid=389“