Merge pull request #3 from qenta-cee/rc-21cw5_2

Rc 21cw5 2

online-guides/modules/ROOT/pages/back-end_operations/transaction-based/recurpayment.adoc

@@ -7,9 +7,9 @@ recurPayment is one of the xref:back-end_operations/transaction-based/start.adoc
 
 The operation recurPayment is used to create a new order and a new payment attempt by reusing the payment information available in a previous order, the so-called source order.
 
-The** required order** of the parameter values when computing the *fingerprint* for xref:wcp/start.adoc[Wirecard Checkout Page] is: `+customerId+`, `+shopId+`, `+toolkitPassword+`, `+secret+`, `+command+`, `+language+`, `+orderNumber+`, `+sourceOrderNumber+`, `+autoDeposit+`, `+orderDescription+`, `+amount+`, `+currency+`, `+orderReference+`, `+customerStatement+`, `+mandateId+`, `+mandateSignatureDate+`, `+creditorId+`, `+dueDate+`, `+transactionIdentifier+` and `+useIbanBic+`.
+The** required order** of the parameter values when computing the *fingerprint* for xref:wcp/start.adoc[Wirecard Checkout Page] is: `+customerId+`, `+shopId+`, `+toolkitPassword+`, `+secret+`, `+command+`, `+language+`, `+orderNumber+`, `+sourceOrderNumber+`, `+autoDeposit+`, `+orderDescription+`, `+amount+`, `+currency+`, `+orderReference+`, `+customerStatement+`, `+mandateId+`, `+mandateSignatureDate+`, `+creditorId+`, `+dueDate+`, `+transactionIdentifier+`, `+useIbanBic+`, `+merchantTokenizationFlag+` and `+periodicType+`.
 
-The *required order* of the parameter values when computing the *fingerprint* for xref:wcs/start.adoc[Wirecard Checkout Seamless] is: `+customerId+`, `+shopId+`, `+password+`, `+secret+`, `+language+`, `+orderNumber+`, `+sourceOrderNumber+`, `+autoDeposit+`, `+orderDescription+`, `+amount+`, `+currency+`, `+orderReference+`, `+customerStatement+`, `+mandateId+`, `+mandateSignatureDate+`, `+creditorId+`, `+dueDate+`, `+transactionIdentifier+` and `+useIbanBic+`.
+The *required order* of the parameter values when computing the *fingerprint* for xref:wcs/start.adoc[Wirecard Checkout Seamless] is: `+customerId+`, `+shopId+`, `+password+`, `+secret+`, `+language+`, `+orderNumber+`, `+sourceOrderNumber+`, `+autoDeposit+`, `+orderDescription+`, `+amount+`, `+currency+`, `+orderReference+`, `+customerStatement+`, `+mandateId+`, `+mandateSignatureDate+`, `+creditorId+`, `+dueDate+`, `+transactionIdentifier+`, `+useIbanBic+`, `+merchantTokenizationFlag+` and `+periodicType+`.
 
 [#AdditionalRequiredRequestParameters]
 === Additional required request parameters
@@ -23,6 +23,40 @@ The *required order* of the parameter values when computing the *fingerprint* fo
 |sourceOrderNumber |Numeric with a variable length of up to 9 digits. |Original order number used for new payment.
 |===
 
+[#AdditionalRequiredRequestParametersForCreditCard]
+==== Additional required request parameters for credit card
+
+According to credit card company requirements for risk minimization, there are two parameters for recurring payments for Wirecard Checkout Page and Wirecard Checkout Seamless:
+
+[cols=",,",options="header",]
+|===
+|Parameter |Data type |Short description
+|merchantTokenizationFlag |Boolean |Used to set whether credit card details are stored for later use.
+|periodicType |Enumeration |2 possible values: `+ucof+`, `+recurring+`. +
+|===
+
+[#Merchanttokenizationflag]
+===== merchantTokenizationFlag
+
+Use this request parameter to set the recurring flaggings for specific orders. +
+You have to set the `+merchantTokenizationFlag+` to TRUE to save consumer's card details for later use (e.g. one-click or auto-top-up or subscriptions).
+
+[#Periodictype]
+===== periodicType
+
+This request parameter may be used to set the periodic type of initial and recurring payments. +
+It may be set to 3 different values:
+
+[cols=",",options="header",]
+|===
+|periodicType value |Description
+|`+ucof+` |for unscheduled recurring payments (with different amounts)
+|`+recurring+` |for recurring payments like subscriptions (with same interval and same amount)
+|===
+
+Regarding the *fingerprint calculation*, the relevant credit card parameters are appended to the payment facilitator parameters in the described order.
+
+
 [#AdditionalOptionalRequestParameters]
 === Additional optional request parameters
 
@@ -150,39 +184,6 @@ Recurring transactions for Computop do not require the parameter `+useIbanBic+`.
 
 Recurring transactions for Hobex do neither require the parameter `+useIbanBic+` nor the parameter `+transactionIdentifier+`.
 
-[#AdditionalOptionalRequestParametersForCreditCard]
-==== Additional optional request parameters for credit card
-
-According to credit card company requirements for risk minimization, there are two parameters for recurring payments for Wirecard Checkout Page and Wirecard Checkout Seamless:
-
-[cols=",,",options="header",]
-|===
-|Parameter |Data type |Short description
-|merchantTokenizationFlag |Boolean |Used to set whether credit card details are stored for later use.
-|periodicType |Enumeration |2 possible values: `+ucof+`, `+recurring+`. +
-|===
-
-[#Merchanttokenizationflag]
-===== merchantTokenizationFlag
-
-Use this request parameter to set the recurring flaggings for specific orders. +
-You have to set the `+merchantTokenizationFlag+` to TRUE to save consumer's card details for later use (e.g. one-click or auto-top-up or subscriptions).
-
-[#Periodictype]
-===== periodicType
-
-This request parameter may be used to set the periodic type of initial and recurring payments. +
-It may be set to 3 different values:
-
-[cols=",",options="header",]
-|===
-|periodicType value |Description
-|`+ucof+` |
-|`+recurring+` |
-|===
-
-Regarding the *fingerprint calculation*, the relevant credit card parameters are appended to the payment facilitator parameters in the described order.
-
 [#DetailedDescriptionOfParameters]
 ==== Detailed description of parameters