square-exclamationFrequently Asked Questions (FAQ) and Known Issues

You can find frequently asked questions and commonly encountered errors in this section.

Card Service

Error on first card read after a chip transaction on x30TR/430TR

The completeEmv method must be executed after every chip transaction. This issue occurs if completeEmv is not performed when an error is encountered.

The broadcast containing card data is received twice, which leads to duplicate transactions.

This issue is typically caused by the CardService being bound multiple times.

To resolve it, a control flag should be implemented in the broadcast handling logic to prevent re-entrance and block duplicate processing when the broadcast is received more than once.

Failure to read on-us cards during the card routing flow after trigger.

When the application is launched through the parameter_action trigger, the EMV configuration files must be explicitly initialized.

In this scenario, the emv_config.xml and emvcl_config.xml files are required to be set using the following APIs:

  • setEMVConfig()

  • setEMVCLConfig()

KMS Service

400TR/1000TR TR31 Key Block Key Inject Error

According to the attached key block structure, the 'mode of use' for 'TPK' must be 'E'. This is because the PIN key should only be permitted for encryption purposes.

Failure to close receipt after power cut in foreign exchange transactions

The root cause of this issue is that, in the power cut scenario, the foreign currency amount is returned in the checkSaleReceiver response.

However, the amount that should be returned is the original TL amount sent at the beginning of the sale transaction.

Key Exchange 503 Error

This error typically occurs when the Complete Key Exchange operation is executed even though the Start Key Exchange process has not been successfully completed.

When this error is encountered, the first step should be to verify whether the Start Key Exchange process has completed successfully.

Printer Service

Failure to print logos on the receipt.

This issue may occur if the logo is not in monochrome format.

To resolve this issue, you can verify whether the logo is in the correct format by using the BitmapChecker.isMonochromeBitmap function located in the printerService module. After confirming that the logo meets the required structure, you may proceed with printing your external bitmap.

Protocol

Receipt not closing after a power cut during foreign currency transactions.

This error occurs because the amount value returned to the PGW within the intent after the checkSaleReceiver action contains the foreign currency amount.

The returned amount value should instead be the original TL amount received at the beginning of the transaction.

Last updated