CWT Software Configuration Handbook
Element Path: <cwt><PAYMENTSERVICE><inputRules><rule><selection>
The selection element defines which payment service shall be selected if the trigger is activated.
attributes
articleId
| Value: | –1 or 0 – 65535 |
| Default: | -1 |
| Description: | The identifier of the article that shall be selected for the defined Key. If not defined then the function is turned OFF. |
Key
| Value: | Any number of characters |
| Default: | - |
| Description: | Output value from the user-identifier selection algorithm. |
paymentServiceId
| Value: | –1 or 0 – 65535 |
| Default: | – |
| Description: | Defines which payment service to select when trigger activated. If not defined then the function is turned OFF. |
When a selection of PaymentService is included, the selection will be asynchronous (a thread switch is performed). This means that further actions like OnPurchasePrerequisitesInputDone cannot be executed in the same button that triggered the user identifier select. A solution can be to add the next action in an AutoClick-button in the next panel.
When selecting Article or TariffPackage the selection is performed synchronously, i.e. direct.
tariffPackageId
| Value: | –1 or 0 – 65535 |
| Default: | -1 |
| Description: | The identifier of the tariff package that shall be selected for the defined Key. If not defined then the function is turned OFF. |
lockArticle
| Value: | true, false |
| Default: | false |
| Description: | If set to true the selection is locked afterwards, meaning no further selection of PAT is possible in the current purchase. |
Example:
Set-up with Post Payment and Pre-Payment in the same terminal. Post Payment with Card only is default. If a coin is inserted during default payment service, the Payment Service will change to paymentServiceId = 1 for PrePay:
<CORE defaultPaymentServiceId="0">
<PAYMENTSERVICE paymentServiceId="0" name="PostPay" postPay="true">
<payUnit name="Card"/>
<inputRules>
<rule triggerUnit="Coin">
<selection paymentServiceId="1"/>
</rule>
</inputRules>
</PAYMENTSERVICE>
<PAYMENTSERVICE paymentServiceId="1" name="PrePay" postPay="false">
<payUnit name="Coin"/>
</PAYMENTSERVICE>
| Note: If Post Payment with EMV Artema Scandinavia should be combined with Prepayment, the Payment Service for Post Payment must be default. |
Example:
For inputRules used with userIdentifierDll defined to use a specific algorithm for transforming the code input to a Key, which is mapped to a selection:
<PAYMENTSERVICE paymentServiceId="0" name="Default" step="true"
userIdentifier="Code" defaultArticleId="1" defaultTariffId="1"
articleChoice="false" tariffChoice="false”>"
<payUnit name="Coin"/>
<payUnit name="Ext0"/>
<inputRules>
<rule triggerUnit="UserIdentifier"
userIdentifierDll=" SpainEmpark.dll">
<selection key="0" tariffPackageId="20"/>
<selection key="1" tariffPackageId="21"/>
<selection key="2" tariffPackageId="22"/>
<selection key="3" tariffPackageId="23" articleId="5"/>
<selection key="4" tariffPackageId="24" articleId="3"/>
<selection key="5" tariffPackageId="25" articleId="1"/>
</rule>
</inputRules>
</PAYMENTSERVICE>
Example:
For inputRules used without defined userIdentifierDll where the code input is mapped to a tariff package without any algorithm applied. In this Example: the input of “A1” as code results in selection of tariff package with id 10:
<PAYMENTSERVICE paymentServiceId="0" name="Default" step="true" userIdentifier="Code" defaultArticleId="1" defaultTariffId="1" articleChoice="false" tariffChoice="false”>"
<payUnit name="Coin"/>
<payUnit name="Ext0"/>
<inputRules>
<rule triggerUnit="UserIdentifier">
<selection key="A1" tariffPackageId="10"/>
<selection key="B1" tariffPackageId="11"/>
<selection key="C1" tariffPackageId="12"/>
</rule>
</inputRules>
</PAYMENTSERVICE>
