Validation and checking services - WEBSALE Dokumentation

This page describes the available services for validating user input as well as the rule-based checks for payment and shipping methods. In addition, there are hard-coded services that connect a payment method to a payment provider, check captchas or convert values between units. The services are not classic configuration nodes with their own structure, but are referenced in the respective form or rule definitions, for example in account, checkout or payment/shipping configurations. The reference consists of the service name in the format <Servicetyp>.<Implementierung> and, if required, an options object:

{
  "service": "addressCheck.minLength",
  "options": {
    "len": 1
  }
}

Check services are usually listed in a validations list, which can contain multiple entries. The other services are referenced via a single field of type singleService.

Service type	Used in	Purpose
`addressCheck.*`	`accounts.addressField` → `validations`	Checks inputs in address fields.
`dataChecker.*`	`validations` of the form and customer data fields, for example `inquiry.form` or `customer.customerDataField`	Checks inputs in general form fields.
`paymentValidation.*`	`payment.payment` → `validations`	Decides whether a payment method is allowed.
`paymentFieldDisplayCheck.*`	`payment.paymentField` → `displayConditions`	Decides whether an additional field of a payment method is displayed in the checkout.
`shippingMethodValidation.*`	Shipping method → `validations`	Decides whether a shipping method is allowed.
`payment.*`	`payment.payment` → `onlineClearing`	Links a payment method to an online clearing provider.
`captchaCheck.*`	`inquiry.form` → `captcha` `payment.paymentBlock` → `captcha` `security.actionGuard` → `captcha`	Checks the captcha token sent by the frontend.
`unitConverter.*`	`customer.customerDataField` → `type.number.unit.dynamic.converter`	Converts the value of a customer data field when the unit changes.

`addressCheck.*` - Address validations

addressCheck.* contains checks for address fields (e.g. name, street, ZIP). The checks are stored in the respective field definitions under validations. The frontend displays the fields as configured and checks during input whether the entries are valid. This detects incorrect or invalid values early.

`addressCheck.minLength` - Minimum length

Checks the minimum length of the input in address fields.

Example configuration for (`accounts.addressField.firstName`)

{
  "label": "",
  "name": "firstName",
  "validations": [
    {
      "options": {
        "len": 1
      },
      "service": "addressCheck.minLength"
    }
  ]
}

Parameter overview

Parameter	Description
`len`	Desired minimum length as a number.

`addressCheck.maxLength` - Maximum length

Checks the maximum length of the input in address fields.

Example configuration for (`accounts.addressField.firstName`)

{
  "label": "",
  "name": "firstName",
  "validations": [
    {
      "options": {
        "len": 255
      },
      "service": "addressCheck.maxLength"
    }
  ]
}

Parameter overview

Parameter	Description
`len`	Desired maximum length as a number.

`addressCheck.numeric` - Digits only

Checks whether the input in address fields consists only of digits.

Example configuration for (`accounts.addressField.phone`)

{
  "label": "",
  "name": "phone",
  "validations": [
    {
      "service": "addressCheck.numeric"
    }
  ]
}

Parameter overview

Parameter	Description
—	No additional parameters.

`addressCheck.country` - Country code (ISO)

Checks whether the input or selection in country lists of the address data fields is a country code configured in the shop (ISO code: 2-letter, 3-letter or ISO number). The official ISO-3166-1 codes (alpha-2, alpha-3 and numeric) can be found on the website of the International Organization for Standardization (ISO): https://www.iso.org/iso-3166-country-codes.html

Example configuration for (`accounts.addressField.country`)

{
  "label": "",
  "name": "country",
  "validations": [
    {
      "service": "addressCheck.country"
    }
  ]
}

Parameter overview

Parameter	Description
—	No additional parameters.

`addressCheck.zip` - ZIP / postal code

Checks whether the input is a valid ZIP/postal code for the specified country. The ZIP rules come from the configuration. The associated country must be provided in the country field.

Example configuration for (`accounts.addressField.zip`)

{
  "label": "",
  "name": "zip",
  "validations": [
    {
      "service": "addressCheck.zip"
    }
  ]
}

Parameter overview

Parameter	Description
—	No additional parameters.

`addressCheck.salutation` - Salutation (code)

Checks whether the input is a valid salutation (code according to configuration).

Example configuration for (`accounts.addressField.salutationCode`)

{
  "label": "",
  "name": "salutationCode",
  "validations": [
    {
      "service": "addressCheck.salutation"
    }
  ]
}

Parameter overview

Parameter	Description
—	No additional parameters.

`addressCheck.regex` - Regular expression

Checks whether the input matches a regular expression.

Example configuration for (`accounts.addressField.additionalInfo`)

{
  "label": "",
  "name": "additionalInfo",
  "validations": [
    {
      "options": {
        "expression": "^((?i)(?!Postfach).)*$"
      },
      "service": "addressCheck.regex"
    }
  ]
}

Parameter overview

Parameter	Description
`expression`	Regular expression (string).

`addressCheck.phone` - Phone number

Checks whether the input is a valid phone number. A valid number consists of digits (without length restriction) and optionally an international dialling code. The + in the dialling code is replaced by 00 after successful validation.

Example configuration for (`accounts.addressField.phone`)

{
  "label": "",
  "name": "phone",
  "validations": [
    {
      "service": "addressCheck.phone"
    }
  ]
}

Parameter overview

Parameter	Description
—	No additional parameters.

`addressCheck.alpha` - Letters only (A–Z)

Checks whether the input consists only of Latin letters (case-insensitive).

Example configuration for (`accounts.addressField.additionalInfo`)

{
  "label": "",
  "name": "additionalInfo",
  "validations": [
    { "service": "addressCheck.alpha" }
  ]
}

Parameter overview

Parameter	Description
—	No additional parameters.

`addressCheck.alphanum` - Letters/digits (A–Z/0–9)

Checks whether the input consists only of Latin letters or digits (case-insensitive).

Example configuration for (`accounts.addressField.additionalInfo`)

{
  "label": "",
  "name": "additionalInfo",
  "validations": [
    { "service": "addressCheck.alphanum" }
  ]
}

Parameter overview

Parameter	Description
—	No additional parameters.

`addressCheck.legalSigns` - Allowed characters

Checks whether all characters in the input are contained in the allowed character set (case-sensitive).

Example configuration for (`accounts.addressField.additionalInfo`)

{
  "label": "",
  "name": "additionalInfo",
  "validations": [
    {
      "options": {
        "signs": "123456ABCSDEF"
      },
      "service": "addressCheck.legalSigns"
    }
  ]
}

Parameter overview

Parameter	Description
`signs`	Allowed characters (string).

`addressCheck.illegalSigns` - Forbidden characters

Opposite of legalSigns: the input must not contain any of the specified characters.

Example configuration for (`accounts.addressField.phone`)

{
  "label": "",
  "name": "phone",
  "validations": [
    {
      "options": {
        "signs": "*|~%${};\"<>§@()/-_#"
      },
      "service": "addressCheck.illegalSigns"
    }
  ]
}

Parameter overview

Parameter	Description
`signs`	Forbidden characters (string).

`addressCheck.date` - Date

Checks whether the input is a valid date and formats the input if needed.

Example configuration for (`accounts.addressField.additionalInfo`)

{
  "label": "",
  "name": "additionalInfo",
  "validations": [
    {
      "options": {
        "delimiter": "-",
        "dateformat": "DMY",
        "formatleadingzero": false
      },
      "service": "addressCheck.date"
    }
  ]
}

Parameter overview

Parameter	Description
`delimiter`	Separator between day/month/year (e.g. `-` for `15-10-2025`).
`dateformat`	Any combination of `D`, `M`, `Y` (e.g. `DMY` for `15-10-2025`).
`formatleadingzero`	If enabled (`true`), days/months are formatted with two digits (`5 → 05`). If disabled (`false`), leading zeros are removed (`05 → 5`). (Boolean)

`addressCheck.allowedSelection` - Selection (list element)

Validates whether the input matches a predefined selection value. The permitted values come from an address list under general.addressListElements, which is referenced via listElements. Typical use: check whether an address is, for example, a “packstation” or “private address”.

Example configuration for (`accounts.addressField.addressType`)

{
  "label": "",
  "name": "addressType",
  "validations": [
    {
      "options": {
        "listElements": "billAddressType"
      },
      "service": "addressCheck.allowedSelection"
    }
  ]
}

Parameter overview

Parameter	Description
`listElements`	Reference to the address list whose values are permitted. Permitted is the `dataId` of the list (e.g. `billAddressType`) or the full node path (e.g. `general.addressListElements.billAddressType`). Both notations are equivalent.

Interplay with the list’s addressType Whether the check takes effect at all depends on the addressType parameter of the referenced list:

`addressType` of the list	Check for billing address	Check for delivery address	Check without address type context
`"bill"`	takes effect	does not take effect	does not take effect
`"delivery"`	does not take effect	takes effect	does not take effect
`"both"`	takes effect	takes effect	takes effect
not set	takes effect	takes effect	does not take effect

If the check does not take effect, the field is accepted without an error – the validation fails silently instead of rejecting the input. The same applies if listElements references an ID for which no address list exists (e.g. after a typo or after deleting the list).Therefore, if a field unexpectedly accepts arbitrary values, first check the spelling of the reference and the addressType of the list.

Further reading

general.addressListElements – definition of the lists and their permitted values.
$wsConfig.listElements – output of the same list as a selection field in the form.

`dataChecker.*` - General field validations

dataChecker.* contains checks for general form fields that are not specific to an address. The checks are included in the respective field definition under validations. The frontend takes the specifications from the field definition and checks during input whether the entry is correct (e.g. length, format or forbidden characters). If a check fails, the shop outputs an error text that matches the respective check, for example “The input is too short.” for dataChecker.minLength. The texts for all dataChecker.* services are stored together in the general.dataCheckerValidationErrors node. For the additional fields of payment methods and for the online order form, subCode in the error object additionally names the failed service, for example dataChecker.minLength.

`dataChecker.minLength` - Minimum length

Checks the minimum length of the inputs in form input fields.

Example configuration for (`inquiry.form.catalogue.fields.firstName`)

{
  "label": "Vorname",
  "name": "firstName",
  "required": true,
  "validations": [
    { "options": { "len": 3 }, "service": "dataChecker.minLength" }
  ]
}

Parameter overview

Parameter	Description
`len`	Desired minimum length as a number.

`dataChecker.maxLength` - Maximum length

Checks the maximum length of the inputs in form input fields.

Example configuration for (`inquiry.form.catalogue.fields.firstName`)

{
  "label": "Vorname",
  "name": "firstName",
  "required": true,
  "validations": [
    { "options": { "len": 255 }, "service": "dataChecker.maxLength" }
  ]
}

Parameter overview

Parameter	Description
`len`	Desired maximum length as a number.

`dataChecker.numericChecker` - Digits only

Checks whether the input in form input fields consists only of digits.

Example configuration for (`inquiry.form.catalogue.fields.phone`)

{
  "label": "Telefon",
  "name": "phone",
  "validations": [
    { "service": "dataChecker.numericChecker" }
  ]
}

Parameter overview

Parameter	Description
—	No additional parameters.

`dataChecker.countryChecker` - Country code (ISO)

Checks whether the input or selection in country lists of the form fields is a country code configured in the shop (ISO code: 2-letter, 3-letter or ISO number). The official ISO-3166-1 codes (alpha-2, alpha-3 and numeric) can be found on the website of the International Organization for Standardization (ISO): https://www.iso.org/iso-3166-country-codes.html

Example configuration for (`inquiry.form.catalogue.fields.country`)

{
  "label": "Land",
  "name": "country",
  "validations": [
    { "service": "dataChecker.countryChecker" }
  ]
}

Parameter overview

Parameter	Description
—	No additional parameters.

`dataChecker.zipCodeChecker` - ZIP / postal code

Checks whether the input is a valid ZIP/postal code for the specified country. The ZIP rules come from the configuration. The associated country must be provided in the country field.

Example configuration for (`inquiry.form.catalogue.fields.zip`)

{
  "label": "Postleitzahl",
  "name": "zip",
  "validations": [
    { "service": "dataChecker.zipCodeChecker" }
  ]
}

Parameter overview

Parameter	Description
—	No additional parameters. (For country-specific checks, the `country` field must be available in the context.)

`dataChecker.salutation` - Salutation (code)

Checks whether the input is a valid salutation (code according to configuration).

Example configuration for (`inquiry.form.catalogue.fields.salutation`)

{
  "label": "Anrede",
  "name": "salutation",
  "validations": [
    { "service": "dataChecker.salutation" }
  ]
}

Parameter overview

Parameter	Description
—	No additional parameters.

`dataChecker.regex` - Regular expression

Checks whether the input matches a regular expression.

Example configuration for (`inquiry.form.catalogue.fields.additionalInfo`)

{
  "label": "Zusatzinformation",
  "name": "additionalInfo",
  "validations": [
    {
      "options": {
        "expression": "^((?i)(?!Postfach).)*$"
      },
      "service": "dataChecker.regex"
    }
  ]
}

Parameter overview

Parameter	Description
`expression`	Regular expression (string).

`dataChecker.email` - Email address

Checks whether the input is a valid email address.

Example configuration for (`inquiry.form.catalogue.fields.mail`)

{
  "label": "E-Mail-Adresse",
  "name": "mail",
  "validations": [
    { "service": "dataChecker.email" }
  ]
}

Parameter overview

Parameter	Description
—	No additional parameters.

`dataChecker.alphaClass` - Letters (min/different)

Ensures that the input contains at least minChars Latin letters (case-insensitive); optionally a minimum number of different letters.

Example configuration for (`inquiry.form.catalogue.fields.additionalInfo`)

{
  "label": "Zusatzinformation",
  "name": "additionalInfo",
  "required": true,
  "validations": [
    {
      "options": {
        "minChars": 8,
        "minDifferentChars": 2
      },
      "service": "dataChecker.alphaClass"
    }
  ]
}

Parameter overview

Parameter	Description
`minChars`	Minimum number of letters (number ≥ 0).
`minDifferentChars`	Minimum number of different letters (number ≥ 0).

`dataChecker.lowerAlphaClass` - Lowercase letters

Like alphaClass, but only lowercase letters.

Example configuration for (`inquiry.form.catalogue.fields.additionalInfo`)

{
  "label": "Zusatzinformation",
  "name": "additionalInfo",
  "required": true,
  "validations": [
    {
      "options": {
        "minChars": 8,
        "minDifferentChars": 2
      },
      "service": "dataChecker.lowerAlphaClass"
    }
  ]
}

Parameter overview

Parameter	Description
`minChars`	Minimum number of lowercase letters (number ≥ 0).
`minDifferentChars`	Minimum number of different lowercase letters (number ≥ 0).

`dataChecker.upperAlphaClass` - Uppercase letters

Like alphaClass, but only uppercase letters.

Example configuration for (`inquiry.form.catalogue.fields.additionalInfo`)

{
  "label": "Zusatzinformation",
  "name": "additionalInfo",
  "required": true,
  "validations": [
    {
      "options": {
        "minChars": 8,
        "minDifferentChars": 2
      },
      "service": "dataChecker.upperAlphaClass"
    }
  ]
}

Parameter overview

Parameter	Description
`minChars`	Minimum number of uppercase letters (number ≥ 0).
`minDifferentChars`	Minimum number of different uppercase letters (number ≥ 0).

`dataChecker.digitClass` - Digits

Like alphaClass, but for digits.

Example configuration for (`inquiry.form.catalogue.fields.additionalInfo`)

{
  "label": "Zusatzinformation",
  "name": "additionalInfo",
  "required": true,
  "validations": [
    {
      "options": {
        "minChars": 4,
        "minDifferentChars": 2
      },
      "service": "dataChecker.digitClass"
    }
  ]
}

Parameter overview

Parameter	Description
`minChars`	Minimum number of digits (number ≥ 0).
`minDifferentChars`	Minimum number of different digits (number ≥ 0).

`dataChecker.specialClass` - Special characters

Like alphaClass, but for special characters.

Example configuration for (`inquiry.form.catalogue.fields.additionalInfo`)

{
  "label": "Zusatzinformation",
  "name": "additionalInfo",
  "required": true,
  "validations": [
    {
      "options": {
        "minChars": 2,
        "minDifferentChars": 1
      },
      "service": "dataChecker.specialClass"
    }
  ]
}

Parameter overview

Parameter	Description
`minChars`	Minimum number of special characters (number ≥ 0).
`minDifferentChars`	Minimum number of different special characters (number ≥ 0).

`dataChecker.sequenceOfIdenticalCharacters` - Repeated characters (sequence)

Checks whether the same character occurs too often in a row.

Example configuration for (`inquiry.form.catalogue.fields.additionalInfo`)

{
  "label": "Zusatzinformation",
  "name": "additionalInfo",
  "required": true,
  "validations": [
    {
      "options": {
        "caseInsensitive": false,
        "maxSequence": 2
      },
      "service": "dataChecker.sequenceOfIdenticalCharacters"
    }
  ]
}

Parameter overview

Parameter	Description
`caseInsensitive`	Ignore case (boolean).
`maxSequence`	Maximum allowed repetition of a character (number ≥ 0).

`dataChecker.consecutiveNumbers` - Consecutive numbers

Checks for ascending or descending number sequences (e.g. 12345 or 54321).

Example configuration for (`inquiry.form.catalogue.fields.additionalInfo`)

{
  "label": "Zusatzinformation",
  "name": "additionalInfo",
  "required": true,
  "validations": [
    {
      "options": {
        "maxConsecutive": 2
      },
      "service": "dataChecker.consecutiveNumbers"
    }
  ]
}

Parameter overview

Parameter	Description
`maxConsecutive`	Maximum length of the number sequence (number ≥ 0).

`dataChecker.consecutiveLetters` - Consecutive letters

Checks for ascending or descending letter sequences (e.g. abcd or dcba).

Example configuration for (`inquiry.form.catalogue.fields.additionalInfo`)

{
  "label": "Zusatzinformation",
  "name": "additionalInfo",
  "required": true,
  "validations": [
    {
      "options": {
        "maxConsecutive": 2,
        "caseInsensitive": false
      },
      "service": "dataChecker.consecutiveLetters"
    }
  ]
}

Parameter overview

Parameter	Description
`maxConsecutive`	Maximum length of the letter sequence (number ≥ 0).
`caseInsensitive`	Ignore case (boolean).

`dataChecker.palindrome` - Palindrome

Checks whether the input is a palindrome (identical forwards/backwards, e.g. “Otto”).

Example configuration for (`inquiry.form.catalogue.fields.additionalInfo`)

{
  "label": "Zusatzinformation",
  "name": "additionalInfo",
  "required": true,
  "validations": [
    {
      "options": {
        "caseInsensitive": false
      },
      "service": "dataChecker.palindrome"
    }
  ]
}

Parameter overview

Parameter	Description
`caseInsensitive`	Ignore case (boolean).

`paymentValidation.*` - Payment method validation

paymentValidation.* contains rules that determine whether a payment method is allowed in the checkout. The check can depend, for example, on the country of the billing or shipping address, the customer type, the basket or the order value. These rules can be entered in the configuration of the respective payment method under validations. The frontend then only shows the payment methods that match, or prevents the selection when the conditions are not met. Here is the link to the corresponding configuration node payment: payment - Payment methods Evaluation in the frontend In the template, the configured rules are evaluated via the method $wsCheckout.isValidPayment(paymentId): it runs all services stored under validations and returns false as soon as at least one rule fails. Unavailable payment methods are therefore disabled or hidden in the selection.

{{ foreach $cPayment in $wsConfig.payments }}
  <input type="radio" name="paymentId" value="{{= $cPayment.id }}"
    {{ if not $wsCheckout.isValidPayment($cPayment.id) }} disabled{{ /if }}>
  <label>{{= $cPayment.name }}</label>
{{ /foreach }}

For the currently selected payment method, the reasons for a failed check are available under $wsCheckout.problems.payment. The subCode field names the failed service.

`paymentValidation.billCountry` - Validation of the country (billing address) for payment methods

Checks whether the country of the billing address is allowed for a payment method according to an “allow/deny” list. Via the options you can define which countries the rule applies to and whether this list allows or forbids countries.

Example configuration

"validations": [
  {
    "options": {
      "countryList": [
        "general.country.de",
        "general.country.at",
        "general.country.ch"
      ],
      "rule": "allow"
    },
    "service": "paymentValidation.billCountry"
  }
]

Parameter overview

Parameter	Description
`countryList`	List of countries to which this rule applies, as node IDs from `general.country` (for example `general.country.de`). The country of the address is matched to an active country node via the two- or three-letter ISO code or the numeric ISO code.
`rule`	Rule control. Possible values: - `allow` - countries in `countryList` are allowed. - `deny` - countries in `countryList` are not allowed.

`paymentValidation.billPhone` - Validation of the phone number

Checks whether a phone number is provided for the billing address (the field must not be empty).

Example configuration

"validations": [
  {
    "service": "paymentValidation.billPhone"
  }
]

There are no parameters for this service.

`paymentValidation.billDateOfBirth` - Validation of the date of birth

Checks whether a date of birth is provided for the billing address (the field must not be empty).

Example configuration

"validations": [
  {
    "service": "paymentValidation.billDateOfBirth"
  }
]

There are no parameters for this service.

`paymentValidation.shippingCountry` - Validation of the country (shipping address)

Checks whether the country of the shipping address is allowed according to an “allow/deny” list. Via the options you can define which countries the rule applies to and whether this list allows or forbids countries.

Example configuration

"validations": [
  {
    "options": {
      "countryList": [
        "general.country.gb"
      ],
      "rule": "deny"
    },
    "service": "paymentValidation.shippingCountry"
  }
]

Parameter overview

Parameter	Description
`countryList`	List of countries to which this rule applies, as node IDs from `general.country` (for example `general.country.de`). The country of the address is matched to an active country node via the two- or three-letter ISO code or the numeric ISO code.
`rule`	Rule control. Possible values: - `allow` - countries in `countryList` are allowed. - `deny` - countries in `countryList` are not allowed.

`paymentValidation.shippingMethod` - Validation of the shipping method for payment methods

Checks whether the selected payment method may only be used with certain shipping methods.

Example configuration

"validations": [
  {
    "options": {
      "shippingMethods": [
        "shipping.method.dhl",
        "shipping.method.pickup"
      ],
      "rule": "allow"
    },
    "service": "paymentValidation.shippingMethod"
  }
]

Parameter overview

Parameter	Description
`shippingMethods`	List of shipping method IDs to which this rule applies. The IDs correspond to the internal names of the shipping methods (e.g. `shipping.method.dhl`).
`rule`	Rule control. Possible values: - `allow` - shipping methods in `shippingMethods` are allowed. - `deny` - shipping methods in `shippingMethods` are not allowed.

`paymentValidation.accountType` - Validation of the customer type for payment methods

Checks whether the selected payment method may only be used for certain customer types (guest, new customer or existing customer).

Example configuration

"validations": [
  {
    "options": {
      "deny": [
        "guest",
        "newCustomer"
      ]
    },
    "service": "paymentValidation.accountType"
  }
]

Parameter overview

Parameter	Description
`deny`	List of customer types for which the payment method is blocked. Possible values: - “`guest`” - guest buyer - “`newCustomer`” - new customer - “`customer`” - existing customer

How the customer type is determined

guest - the customer orders as a guest (without a user account).
newCustomer - a signed-in customer who fulfils the new-customer rules configured in accounts.account.newCustomerRules at login. A new registration during checkout always results in the type newCustomer, regardless of the rules.
customer - any other signed-in customer. If no new-customer rules are configured, signed-in customers are always considered customer.

The customer type checked here is not identical to the template variable $wsCheckout.accountType (guest / new / registered): the latter reports the sign-in method chosen in the checkout, while the validation distinguishes between new and existing customers (newCustomer / customer). In the order data, customer and newCustomer are both reported as registered.

`paymentValidation.denyDifferingShippingAddress` - Validation of differing shipping addresses for payment methods

Checks whether the billing and shipping addresses are identical.
The payment method is only allowed when no differing shipping address is used.

Example configuration

"validations": [
  {
    "service": "paymentValidation.denyDifferingShippingAddress"
  }
]

Parameter overview

Parameter	Description
—	No additional parameters.

`paymentValidation.voucherDeny` - Validation of voucher products for payment methods

Checks whether voucher products are in the basket. When voucher products are in the basket, this payment method is not allowed.

Example configuration

"validations": [
  {
    "service": "paymentValidation.voucherDeny"
  }
]

Parameter overview

Parameter	Description
—	No additional parameters.

`paymentValidation.total` - Validation of minimum / maximum order value for payment methods

Checks whether the payment method may only be used when a certain minimum or maximum order value is reached or not exceeded.

Example configuration

"validations": [
  {
    "options": {
      "total": 600,
      "type": "max"
    },
    "service": "paymentValidation.total"
  }
]

Parameter overview

Parameter	Description
`total`	Threshold of the total (goods value) up to or from which the payment method is allowed.
`type`	Check type. Possible values: - “`min`” - the payment method is only allowed if the order value is at least `total`. - “`max`” - the payment method is only allowed if the order value does not exceed `total`.

If both a minimum and a maximum order value are to be checked at the same time, this check must be configured twice with different options.

`paymentValidation.inventoryState` - Validation of the inventory state for payment methods

Checks whether products with a specific stock level are in the basket. If a product in the basket has a status configured in deny, the payment method is not allowed.

Example configuration

"validations": [
  {
    "options": {
      "deny": [
        "red",
        "yellow"
      ]
    },
    "service": "paymentValidation.inventoryState"
  }
]

Parameter overview

Parameter	Description
`deny`	List of stock states for which the payment method is forbidden. Possible values: - “`red`” - sold out - “`yellow`” - only a few remaining - “`green`” - many available The thresholds of the individual stock levels are defined in `content.inventory`: content - Catalog (categories & products)

`paymentValidation.productDependency` - Validation of product dependencies for payment methods

Checks the products in the basket against the configuration checkout.productDependency.
A payment method is only offered when all referenced product dependencies are fulfilled. This way you couple a payment method to basket properties without duplicating the check logic. The actual conditions (product fields, free fields, value comparisons) are maintained centrally in checkout.productDependency.

Example configuration

The “Pay by invoice” option should be blocked as soon as a personalised product (e.g. with an engraving) is in the basket. Because personalised items cannot be returned, they carry a higher payment-default risk. You define the condition “no engraving in the basket” in checkout.productDependency and reference it here afterwards.

"validations": [
  {
    "options": {
      "list": [
        "checkout.productDependency.noEngraving"
      ]
    },
    "service": "paymentValidation.productDependency"
  }
]

Parameter overview

Parameter	Description
`list`	List of IDs of configurations from checkout.productDependency to be checked. For the validation to succeed and the payment method to be offered, all values specified here must be fulfilled.

`paymentValidation.userAgent` - Validation of the user agent for payment methods

Checks whether a payment method is displayed based on the customer’s device or browser. Devices and browsers automatically transmit a technical identifier when a page is called up — the so-called user agent. Based on this identifier, it can be detected, for example, whether someone is using an iPhone, an iPad or a Mac. The terms entered in userAgents are checked against this identifier; a single match is enough. This allows a payment method to be enabled or blocked specifically for certain devices or browsers — for example, when Apple Pay should only be displayed to customers using an Apple device or a compatible browser.

Example configuration

"validations": [
  {
    "options": {
      "userAgents": [
        "Macintosh",
        "Mac OS X",
        "iPhone",
        "iPad"
      ],
      "rule": "allow"
    },
    "service": "paymentValidation.userAgent"
  }
]

Parameter overview

Parameter	Description
`userAgents`	List of terms searched in the customer’s device/browser identifier. One match is enough. The values are not predefined by WEBSALE, but correspond to the actual strings that the respective device or browser transmits. The correct values must be determined on the respective device itself, e.g. via the browser console.
`rule`	Rule control. Possible values: - `allow` - payment method is only displayed when at least one term from `userAgents` is detected. - `deny` - payment method is hidden when a match is found.

`paymentFieldDisplayCheck.*` - Display conditions for additional fields

paymentFieldDisplayCheck.* contains conditions that control when an additional field of a payment method is displayed in the checkout. For example, a field appears only for certain billing countries or only if another additional field has a specific value. The conditions are entered in the field definition under displayConditions. If multiple conditions are stored, all of them must be met. Unlike the checks under validations, the conditions do not produce an error message. If a condition is not met, the shop hides the field, does not check it and does not require it, even as a required field. If a condition cannot be evaluated, it is considered not met and the field remains hidden. This applies, for example, to an address that cannot be loaded or to an incomplete configuration. The cause is then recorded in the LogManager.

`paymentFieldDisplayCheck.billCountry` / `shippingCountry` - Country of the billing or shipping address

Checks the country of the billing address (billCountry) or shipping address (shippingCountry) selected in the checkout against a country list.

Example configuration

"displayConditions": [
  {
    "options": {
      "countryList": [
        "general.country.de",
        "general.country.at"
      ],
      "rule": "allow"
    },
    "service": "paymentFieldDisplayCheck.billCountry"
  }
]

Parameter overview

Parameter	Description
`countryList`	List of countries as node IDs from `general.country`, for example `general.country.de`. The country of the address is matched to an active country node via the two- or three-letter ISO code or the numeric ISO code.
`rule`	Rule control. Possible values: - `allow` - The field is only displayed for countries from `countryList`. - `deny` - The field is hidden for countries from `countryList`. With any other value, the field remains hidden.

The condition is not met if the address cannot be loaded or its country is not configured as an active country node.

Without a differing shipping address, shippingCountry checks the country of the billing address.

`paymentFieldDisplayCheck.billAddressField` / `shippingAddressField` - Field of the billing or shipping address

Checks a single field of the billing address (billAddressField) or shipping address (shippingAddressField) selected in the checkout.

Example configuration

The field is only displayed if the billing address does not contain a company:

"displayConditions": [
  {
    "options": {
      "field": "company",
      "type": "empty"
    },
    "service": "paymentFieldDisplayCheck.billAddressField"
  }
]

Parameter overview

Parameter	Description
`field`	Name of the address field. For standard fields, the base name, for example `company` or `zip`. For additional fields of the address, `custom.<name>`.
`type`	Type of comparison. Possible values: - `filled` - field is not empty - `empty` - field is empty - `value` / `notvalue` - value is equal / not equal to `value` - `inlist` / `notinlist` - value is / is not contained in `list` - `prefix` / `notprefix` - value starts / does not start with `value`
`value`	Comparison value for `value`, `notvalue`, `prefix` and `notprefix`.
`list`	List of values for `inlist` and `notinlist`. If the list is empty or missing, the condition is considered met for both types.

The condition is not met if the address cannot be loaded, field or type is missing, the field does not exist in the address or type has an unknown value.

`paymentFieldDisplayCheck.paymentField` - Value of another additional field

Checks the current value of another additional field from the current checkout. This lets you build dependent fields that only appear after a specific input.

Example configuration

The field is only displayed if the checkbox is checked in the additional field invoiceToCompany:

"displayConditions": [
  {
    "options": {
      "field": "invoiceToCompany",
      "type": "value",
      "value": "true"
    },
    "service": "paymentFieldDisplayCheck.paymentField"
  }
]

Parameter overview

Parameter	Description
`field`	Technical name (`name`) of the other additional field from `payment.paymentField`.
`type`	Type of comparison. The same eight values apply as for `billAddressField` above.
`value`	Comparison value for `value`, `notvalue`, `prefix` and `notprefix`. Checkboxes return the value `true` or `false` as text.
`list`	List of values for `inlist` and `notinlist`. If the list is empty or missing, the condition is considered met.

The condition is not met if field or type is missing or type has an unknown value.

The shop only stores the value of an additional field with the CheckoutSetPaymentFields action. A dependent field therefore only appears after the form has been submitted, for example automatically on every change.

`shippingMethodValidation.*` - Shipping method validation

shippingMethodValidation.* contains rules that determine whether a shipping method is allowed in the checkout. The check can depend, for example, on the shipping country, the goods value, product types or the selected payment method. These rules can be entered in the configuration of the respective shipping method under validations. The frontend then only offers the shipping methods that match the current conditions. Evaluation in the frontend In the template, the configured rules are evaluated via the method $wsCheckout.isValidShippingMethod(shippingMethodId) (same pattern as for payment methods). The reasons for a disabled shipping method can additionally be output via $wsCheckout.getShippingMethodDisabledErrors(shippingMethodId).

`shippingMethodValidation.shippingCountry` - Validation of the country (shipping address)

Example configuration

"validations": [
  {
    "options": {
      "countryList": [
        "general.country.de",
        "general.country.at"
      ],
      "rule": "allow"
    },
    "service": "shippingMethodValidation.shippingCountry"
  }
]

Parameter overview

Parameter	Description
`countryList`	List of countries to which this rule applies, as node IDs from `general.country` (for example `general.country.de`). The country of the address is matched to an active country node via the two- or three-letter ISO code or the numeric ISO code.
`rule`	Rule control. Possible values: - `allow` - countries in `countryList` are allowed. - `deny` - countries in `countryList` are not allowed.

`shippingMethodValidation.paymentMethod` - Validation of the payment method for shipping methods

Checks whether a shipping method may only be used with certain payment methods.

Example configuration

"validations": [
  {
    "options": {
      "paymentMethods": [
        "payment.method.invoice",
        "payment.method.prepayment"
      ],
      "rule": "allow"
    },
    "service": "shippingMethodValidation.paymentMethod"
  }
]

Parameter overview

Parameter	Description
`paymentMethods`	List of payment method IDs to which this rule applies. The IDs correspond to the internal names of the payment methods (e.g. `payment.method.invoice`)
`rule`	Rule control. Possible values: - `allow` - payment methods in `paymentMethods` are allowed. - `deny` - payment methods in `paymentMethods` are not allowed.

`shippingMethodValidation.valueOfGoods` - Validation of the minimum/maximum order value for shipping methods

Checks whether the shipping method may only be used when a certain minimum or maximum order value is reached or not exceeded.

Example configuration

"validations": [
  {
    "options": {
      "valueOfGoods": 100,
      "type": "min"
    },
    "service": "shippingMethodValidation.valueOfGoods"
  }
]

Parameter overview

Parameter	Description
`valueOfGoods`	Threshold of the total (goods value) up to or from which the shipping method is allowed.
`type`	Check type. Possible values: - “`min`” - the shipping method is only allowed if the order value is at least `valueOfGoods`. - “`max`” - the shipping method is only allowed if the order value does not exceed `valueOfGoods`.

`shippingMethodValidation.productType` - Validation of the product type for shipping methods

Checks whether all products in the basket have a matching product type.

Example configuration

"validations": [
  {
    "options": {
      "rule": "allow",
      "ruleList": [
        "productType.digital"
      ],
      "includeList": [
        "productType.service"
      ]
    },
    "service": "shippingMethodValidation.productType"
  }
]

Parameter overview

Parameter	Description
`rule`	Check type. Possible values: - “`allow`” - only product types from `ruleList` and `includeList` are allowed. - “`deny`” - product types from `ruleList` are not allowed. Exception: product types from `includeList` are always allowed.
`ruleList`	List of product types that — depending on `rule` — are allowed or not allowed.
`includeList`	List of product types that are always allowed.

`shippingMethodValidation.productDependency` - Validation of product dependencies for shipping methods

Checks the products in the basket against the configuration checkout.productDependency.

Example configuration

"validations": [
  {
    "options": {
      "list": [
        "checkout.productDependency.digitalOnly",
        "checkout.productDependency.noBulkyGoods"
      ]
    },
    "service": "shippingMethodValidation.productDependency"
  }
]

Parameter overview

Parameter	Description
`list`	List of IDs of configurations from `checkout.productDependency` to be checked. For the validation to succeed, all values specified here must be fulfilled.

`shippingMethodValidation.expressCheckout` - Validation of the express checkout for shipping methods

Checks whether a shipping method is allowed depending on the payment method used in the express checkout. The check applies to PayPal Express as well as Apple Pay and Google Pay Express (PayPal Commerce Platform).

Example configuration

The shipping method should not be selectable if the customer runs the ordering process as a PayPal Express Checkout:

"validations": [
  {
    "options": {
      "rule": "deny",
      "ruleList": [
        "paypalCheckout"
      ]
    },
    "service": "shippingMethodValidation.expressCheckout"
  }
]

Parameter overview

Parameter	Description
`rule`	Check type. Possible values: - “`deny`” - if the ordering process runs as an express checkout with a payment method from `ruleList`, the shipping method is blocked. Outside the express checkout, the shipping method is allowed. - “`allow`” - the shipping method is only allowed if the ordering process runs as an express checkout with a payment method from `ruleList`. In the normal checkout (no express checkout active), the shipping method is therefore always blocked — `allow` thus defines a pure express-checkout shipping method.
`ruleList`	List of payment method IDs that — depending on `rule` — are allowed or forbidden in the express checkout. The IDs correspond to the identifiers of the payment methods from payment.payment (e.g. `paypalCheckout`).

If the check fails, the validation returns the error expressCheckoutDenied or expressCheckoutNotAllowed. In the frontend, it can be output via $wsCheckout.getShippingMethodDisabledErrors().

`payment.*` - Online clearing services

An online clearing service processes the payment of a payment method in real time via a payment provider. The assignment is made in the payment method under payment.payment in the onlineClearing field. Payment methods without onlineClearing are considered offline payment methods, for example prepayment or invoice without a provider. Unlike the validation and check services, an online clearing service is not referenced in a validations list but via a field of type singleService. Each payment method references exactly one service. The provider-specific settings are stored in the payment.computopHosted, payment.stripe and payment.payPalCheckout nodes. The service options only control which shop pages the customer is directed to during payment.

Pending payments and pending page

All three services support a pending page. The shop displays it while a payment has not yet been completed at the provider. During this time, the session is locked. The customer can then only open the pending page, the order confirmation, the order flow and the home page. If they open any other page, the shop redirects them back to the pending page. The shop appends the parameter wsPaymentStatus=refresh to the URL of the pending page. If the payment has been completed in the meantime, the shop redirects directly to the order confirmation when the pending page is opened. If no pending page is stored in the service options, the shop falls back to the pendingTemplate field in the general.subshopView node. The exact order per provider is described in the following sections.

`payment.computop-hosted` - Computop Hosted Payment Page

Redirects the customer to Computop’s hosted payment page. To do this, the shop first renders its own page with a form that passes the payment data to Computop via POST. This page is defined via the view option. The ID of the payment method under payment.payment must match the id of an entry under payment.computopHosted and correspond to a payment method supported by Computop. Otherwise, the shop aborts the payment with the log message payment method invalid, not defined in computopHosted config.

Example configuration (`payment.payment.creditcard` → `onlineClearing`)

"onlineClearing": {
  "service": "payment.computop-hosted",
  "options": {
    "view": "computop_redirect.htm",
    "pendingView": "computop_pending.htm"
  }
}

Parameter overview

Parameter	Description
`view`	Template (view) with the POST form to Computop. After the order is submitted, the shop redirects the customer to this page.
`pendingView`	Template (view) that the customer sees while the payment is still pending. Optional. If the value is empty, the shop uses `pendingTemplate` from `general.subshopView`. If that is also empty, the customer stays on the order confirmation.

`payment.stripe` - Stripe

Connects Stripe as a payment provider. The payment runs via the Stripe widget in the order flow. If the customer selects a payment option with a redirect in the widget, they return to the shop via the page from the view option. The Stripe account settings are stored in the payment.stripe node. The integration in the template is described in Stripe in the frontend.

Example configuration (`payment.payment.stripe` → `onlineClearing`)

"onlineClearing": {
  "service": "payment.stripe",
  "options": {
    "view": "stripe_pending.htm"
  }
}

Parameter overview

Parameter	Description
`view`	Template (view) to which Stripe redirects the customer after payment and which serves as the pending page. Optional. The shop builds the return address from it with the parameter `wsPaymentStatus=refresh`. If the value is empty, the shop does not pass its own return address to Stripe.

`payment.paypal-checkout` - PayPal Checkout

Connects PayPal Checkout (PayPal Commerce Platform) as a payment provider. The return pages for confirmation, cancellation and errors are defined by the payment.payPalCheckout node. The service’s view option defines the page for payments that are still pending after submission, for example for purchase on invoice via PayPal.

Example configuration (`payment.payment.paypalCheckout` → `onlineClearing`)

"onlineClearing": {
  "service": "payment.paypal-checkout",
  "options": {
    "view": "paypal_checkout_pending.htm"
  }
}

Parameter overview

Parameter	Description
`view`	Template (view) that the customer sees while the payment is still pending. Optional. If the value is empty, the shop uses `pendingTemplate` from `payment.payPalCheckout`. If that is also empty, it uses `pendingTemplate` from `general.subshopView`.
`clearingFields`	Only for PayPal purchase on invoice: assigns the date of birth (`birthdate`) and phone number (`phone`) each to an additional field of the payment method. You enter the technical name of the additional field. Optional. See Example: PayPal purchase on invoice.

`captchaCheck.*` - Captcha check

A captcha service checks whether a request comes from a human. To do this, the frontend integrates the provider’s captcha and sends its token to the shop with the action. The service forwards the token to the provider for verification. The provider’s credentials are stored in the security node. The reference to the service determines which provider performs the check at a given point. Three places can use a captcha service:

inquiry.form in the captcha field protects a form. The check runs every time the InquirySend action is executed.
payment.paymentBlock in the captcha field secures order completion against repeated payment attempts. The check only runs once the shop requires a captcha after several failed attempts. Whether this is the case is output by $wsCheckout.paymentCaptchaRequired.
security.actionGuard in the captcha field protects any action.

Example configuration (`inquiry.form.contact` → `captcha`)

"captcha": {
  "service": "captchaCheck.friendlyCaptchaV1"
}

Both services first check cookie consent. If consent is missing for the consent service whose name is in the name field of the provider node, the check fails without a request to the provider. The name field must therefore match the name of the service in consent management. The shop expects the token in a fixed request parameter of the action. The name cannot be configured.

Service	Provider node	Request parameter
`captchaCheck.recaptchav3`	`security.recaptchav3`	`wscaptchatoken`
`captchaCheck.friendlyCaptchaV1`	`security.friendlyCaptchaV1`	`frc-captcha-solution`

If the check fails for InquirySend or at order completion, the action returns the error code captchaFailed. You maintain the corresponding text in the action’s error text node, for example under actions.inquirySend.

`captchaCheck.recaptchav3` - Google reCAPTCHA v3

Checks a Google reCAPTCHA v3 token. Google returns a score between 0.0 and 1.0 for each token. If it is below minimumScore from security.recaptchav3, the check is considered failed.

Example configuration

"captcha": {
  "service": "captchaCheck.recaptchav3"
}

Parameter overview

Parameter	Description
`errorMessage`	Error text of the service. Optional. If the check fails, the `InquirySend` and `CheckoutConfirm` actions output the text for the error code `captchaFailed` instead.

`captchaCheck.friendlyCaptchaV1` - Friendly Captcha v1

Checks a Friendly Captcha v1 solution. The shop sends the solution together with apiKey and siteKey from security.friendlyCaptchaV1 to the provider’s verifyUrl.

Example configuration

"captcha": {
  "service": "captchaCheck.friendlyCaptchaV1"
}

Parameter overview

Parameter	Description
`errorMessage`	Error text of the service. Optional. If the check fails, the `InquirySend` and `CheckoutConfirm` actions output the text for the error code `captchaFailed` instead.

`unitConverter.*` - Unit conversion

A customer data field of type number can have a dynamic unit. The customer then selects the unit from a list, for example meters or centimeters. If they change the unit, a conversion service converts the entered value to the new unit. The service is entered in the customer data field under customer.customerDataField in the type.number.unit.dynamic.converter field. Without an entry, the shop stores the value unchanged with the new unit.

`unitConverter.orderOfMagnitude` - Conversion using factors

Converts using the factors stored on the units under unitOptions. The service itself has no options. The conversion follows this formula:

neuer Wert = Wert × Faktor der gewählten Einheit ÷ Faktor der vorherigen Einheit

The previous unit is the unit from the session. If none is stored there, the shop uses the unit stored in the customer account. If none is known there either, it calculates with the factor 1. If the factor of the previous unit is 0, the conversion results in 0. The factor indicates how many units correspond to a reference quantity. You should therefore give the base unit from baseUnitName the factor 1. This way, the conversion is also correct if no previous unit is known.

Example configuration (`customer.customerDataField.raumhoehe` → `type`)

"number": {
  "numDecimals": 2,
  "unit": {
    "dynamic": {
      "baseUnitName": "m",
      "unitOptions": [
        { "name": "m", "label": "<Textbaustein>", "factor": 1 },
        { "name": "cm", "label": "<Textbaustein>", "factor": 100 },
        { "name": "mm", "label": "<Textbaustein>", "factor": 1000 }
      ],
      "converter": {
        "service": "unitConverter.orderOfMagnitude"
      }
    }
  }
}

If the customer entered 2.5 in meters and switches to centimeters, the shop stores 2.5 × 100 ÷ 1 = 250.

Parameter overview

Parameter	Description
—	No parameters. The factors come from `unitOptions[].factor` of the customer data field.

​addressCheck.* - Address validations

​addressCheck.minLength - Minimum length

​Example configuration for (accounts.addressField.firstName)

​Parameter overview

​addressCheck.maxLength - Maximum length

​Example configuration for (accounts.addressField.firstName)

​Parameter overview

​addressCheck.numeric - Digits only

​Example configuration for (accounts.addressField.phone)

​Parameter overview

​addressCheck.country - Country code (ISO)

​Example configuration for (accounts.addressField.country)

​Parameter overview

​addressCheck.zip - ZIP / postal code

​Example configuration for (accounts.addressField.zip)

​Parameter overview

​addressCheck.salutation - Salutation (code)

​Example configuration for (accounts.addressField.salutationCode)

​Parameter overview

​addressCheck.regex - Regular expression

​Example configuration for (accounts.addressField.additionalInfo)

​Parameter overview

​addressCheck.phone - Phone number

​Example configuration for (accounts.addressField.phone)

​Parameter overview

​addressCheck.alpha - Letters only (A–Z)

​Example configuration for (accounts.addressField.additionalInfo)

​Parameter overview

​addressCheck.alphanum - Letters/digits (A–Z/0–9)

​Example configuration for (accounts.addressField.additionalInfo)

​Parameter overview

​addressCheck.legalSigns - Allowed characters

​Example configuration for (accounts.addressField.additionalInfo)

​Parameter overview

​addressCheck.illegalSigns - Forbidden characters

​Example configuration for (accounts.addressField.phone)

​Parameter overview

​addressCheck.date - Date

​Example configuration for (accounts.addressField.additionalInfo)

​Parameter overview

​addressCheck.allowedSelection - Selection (list element)

​Example configuration for (accounts.addressField.addressType)

​Parameter overview

​dataChecker.* - General field validations

​dataChecker.minLength - Minimum length

​Example configuration for (inquiry.form.catalogue.fields.firstName)

​Parameter overview

​dataChecker.maxLength - Maximum length

​Example configuration for (inquiry.form.catalogue.fields.firstName)

​Parameter overview

​dataChecker.numericChecker - Digits only

​Example configuration for (inquiry.form.catalogue.fields.phone)

​Parameter overview

​dataChecker.countryChecker - Country code (ISO)

​Example configuration for (inquiry.form.catalogue.fields.country)

​Parameter overview

​dataChecker.zipCodeChecker - ZIP / postal code

​Example configuration for (inquiry.form.catalogue.fields.zip)

​Parameter overview

​dataChecker.salutation - Salutation (code)

​Example configuration for (inquiry.form.catalogue.fields.salutation)

​Parameter overview

​dataChecker.regex - Regular expression

​Example configuration for (inquiry.form.catalogue.fields.additionalInfo)

​Parameter overview

​dataChecker.email - Email address

​Example configuration for (inquiry.form.catalogue.fields.mail)

​Parameter overview

​dataChecker.alphaClass - Letters (min/different)

​Example configuration for (inquiry.form.catalogue.fields.additionalInfo)

​Parameter overview

​dataChecker.lowerAlphaClass - Lowercase letters

​Example configuration for (inquiry.form.catalogue.fields.additionalInfo)

​Parameter overview

​dataChecker.upperAlphaClass - Uppercase letters

​Example configuration for (inquiry.form.catalogue.fields.additionalInfo)

​Parameter overview

​dataChecker.digitClass - Digits

​Example configuration for (inquiry.form.catalogue.fields.additionalInfo)

​Parameter overview

`addressCheck.*` - Address validations

`addressCheck.minLength` - Minimum length

Example configuration for (`accounts.addressField.firstName`)

Parameter overview

`addressCheck.maxLength` - Maximum length

Example configuration for (`accounts.addressField.firstName`)

Parameter overview

`addressCheck.numeric` - Digits only

Example configuration for (`accounts.addressField.phone`)

Parameter overview

`addressCheck.country` - Country code (ISO)

Example configuration for (`accounts.addressField.country`)

Parameter overview

`addressCheck.zip` - ZIP / postal code

Example configuration for (`accounts.addressField.zip`)

Parameter overview

`addressCheck.salutation` - Salutation (code)

Example configuration for (`accounts.addressField.salutationCode`)

Parameter overview

`addressCheck.regex` - Regular expression

Example configuration for (`accounts.addressField.additionalInfo`)

Parameter overview

`addressCheck.phone` - Phone number

Example configuration for (`accounts.addressField.phone`)

Parameter overview

`addressCheck.alpha` - Letters only (A–Z)

Example configuration for (`accounts.addressField.additionalInfo`)

Parameter overview

`addressCheck.alphanum` - Letters/digits (A–Z/0–9)

Example configuration for (`accounts.addressField.additionalInfo`)

Parameter overview

`addressCheck.legalSigns` - Allowed characters

Example configuration for (`accounts.addressField.additionalInfo`)

Parameter overview

`addressCheck.illegalSigns` - Forbidden characters

Example configuration for (`accounts.addressField.phone`)

Parameter overview

`addressCheck.date` - Date

Example configuration for (`accounts.addressField.additionalInfo`)

Parameter overview

`addressCheck.allowedSelection` - Selection (list element)

Example configuration for (`accounts.addressField.addressType`)

Parameter overview

`dataChecker.*` - General field validations

`dataChecker.minLength` - Minimum length

Example configuration for (`inquiry.form.catalogue.fields.firstName`)

Parameter overview

`dataChecker.maxLength` - Maximum length

Example configuration for (`inquiry.form.catalogue.fields.firstName`)

Parameter overview

`dataChecker.numericChecker` - Digits only

Example configuration for (`inquiry.form.catalogue.fields.phone`)

Parameter overview

`dataChecker.countryChecker` - Country code (ISO)

Example configuration for (`inquiry.form.catalogue.fields.country`)

Parameter overview

`dataChecker.zipCodeChecker` - ZIP / postal code

Example configuration for (`inquiry.form.catalogue.fields.zip`)

Parameter overview

`dataChecker.salutation` - Salutation (code)

Example configuration for (`inquiry.form.catalogue.fields.salutation`)

Parameter overview

`dataChecker.regex` - Regular expression

Example configuration for (`inquiry.form.catalogue.fields.additionalInfo`)

Parameter overview

`dataChecker.email` - Email address

Example configuration for (`inquiry.form.catalogue.fields.mail`)

Parameter overview

`dataChecker.alphaClass` - Letters (min/different)

Example configuration for (`inquiry.form.catalogue.fields.additionalInfo`)

Parameter overview

`dataChecker.lowerAlphaClass` - Lowercase letters

Example configuration for (`inquiry.form.catalogue.fields.additionalInfo`)

Parameter overview

`dataChecker.upperAlphaClass` - Uppercase letters

Example configuration for (`inquiry.form.catalogue.fields.additionalInfo`)

Parameter overview

`dataChecker.digitClass` - Digits

Example configuration for (`inquiry.form.catalogue.fields.additionalInfo`)

Parameter overview