Please enable JavaScript to view this site.

WebOffice  2.66 Complete Guide

Navigation: Support Menu > System Management > Card Management > Card Number Prefixes > Validation rules

Additional validation rules for CWT terminals

Scroll Prev Top Next More
For MP 104:
For the validation rules for the MP 104 terminal see document MP 104 System Manual 7.8

Rule

Explanation

Axx(op)X:Y;Z

Checks that the character in position xx is the same as the one entered or, if it is a digit, is within the interval specified.  Intervals are written X:Y. Different intervals, and intervals and individual characters, are separated by semicolons.  Individual characters and intervals can be mixed.

Bxx:yy(op)XX;YY:ZZ

Checks that the numeric string from position xx to position yy contains one of the values that follow.  Individual numbers, such as 56, and intervals are written XX and YY:ZZ, respectively.  Individual numbers and intervals can be mixed.

C3

Tells the machine that the magnetic-stripe card is a test card.

See the MP 104 manual Installation and maintenance, chapter Accessories, regarding of ordering such cards.

D[x]

D = No date checking performed.
Dx = Date checking starts from position x.

If rule D is not used, date checking will be carried out as usual, that is, on the 4 positions following the separator.  On cards without separator, date check can only be performed using rule Dx.

Gx

Ground limit minimum ticks.

Ifxx:yy(op)XX;YY:ZZ?command

Checks if the number in position xx is equal to the specified number or is within the specified number interval.  Interval is written as X:Y. Different intervals, and intervals and individual numbers, are separated by semicolons.  Individual numbers and intervals can be mixed.

IMPORTANT!

If the conditions are NOT met, the service command will NOT be executed and the card WILL BE accepted.

Example 1

Card No.: 700101027641123 (pos. 0–14)

700101_IF11:11=5?A7=9# meaning … If position 11 = 5 then execute command ‘A7=9’ stating that pos. 7 must be equal to 9.  The command will not be executed because pos. 11 = 1.  The fact that pos. 7 is not equal to 9 does not matter in this case.  The card will be accepted if the prefix and other rules are met.

Example 2

700101_IF8:9!22:24?A13!3# meaning… If pos. 8–9 are not equal to 22, 23 or 24 then execute command ‘A13!3’ stating that pos. 13 must not be equal to 3.

With card No. 7001010123456789014 (pos. 0–18) the command will not be executed because pos. 8–9 = 23.  The card will be accepted because pos. 13 is not tested.

With card No. 7001010987654321016 (pos. 0–14) the command will be executed because pos. 8–9 is not equal to 22, 23 or 24.  The card will not be accepted because pos. 13 is equal to 3.

Pt:u;v;x;y:z

Check if card is valid in current article.

This rule is useful if you want to block certain credit cards in some tariff packages while allowing the same card in other tariff packages.

Sxx:yy:zz

Carries out a checksum test of all digits from position xx through position yy and checks that the result is the same as the number in position zz.

Xx=y

Relative positioned Service Code evaluation

Service code is for most of cards positioned relative a separator, so the service code can be retrieved without any fixed position knowledge.

Service code has 3 digits where each digit has a meaning rather than the whole 3-digit number.

Add new validation rule ‘X2=3’ meaning ‘Check that service code Digit 2 equals 3.  If it doesn't the rule fails’

CS

Relative positioned Checksum evaluation

Checksum and what to include in checksum calculation is for the most of cards positioned relative a separator so the information can be retrieved without any fixed position knowledge.  Add new validation rule, e.g. ‘CS’ meaning ‘Calculate the checksum and verify it.’

For cards that do not have a checksum, relative a separator the existing validation rule ‘S…’ can be used.  When using CS will the checksum position be the last digit of the PAN (digit before the = separator).