There seems to be either a bug in the viaklix payment module or a misunderstanding of how viaklix works and charges the client (or both).
According to Viaklix support, and confirmed twice by others in Viaklix, the ssl_customer_code field that is placed within:
zen_draw_hidden_field('ssl_customer_id', $_SESSION['customer_id']) .
Is actually meant to return the code of the type of card the customer is using. For those of us who are using the usual clients that we would normally meet, i.e. not fleet cards, not governments or others like that, the code should be 1111. When it is anything but this, the status of the transaction is degraded to some extent and this can increase the charges to the client!!!! Therefore the support personel at Viaklix say it is important to enter this code number, 1111, for each transaction.
We now have a conflict as the script uses this field for something else, namely, the internal shop customer id.
It can be fixed in this way. Replace:
zen_draw_hidden_field('ssl_customer_id', $_SESSION['customer_id']) .
With:
zen_draw_draw_hidden_field('ssl_customer_id', $_SESSION['customer_id']) .
zen_draw_draw_hidden_field('ssl_customer_code','1111') .
It returns the proper values in the shopkeeper's receipt and according to Viaklix this confirms it is done correctly.



