Error Code
CPoC/ MPoC SDK

Error code - SDK

NameTypeValueDescriptionExtra
SUCCESSGENERIC0Operation/ process successful
    INVALID_LICENSESDK41000Invalid licence
    • The SDK license is invalid, missing, or not accepted by the runtime
    • Reinstall or renew the valid MineSec license file and reinitialize the SDK
    SDK_INIT_FAILEDSDK41100Initialization failed; initSdk may not have been called
    • SDK initialization failed during startup or registration setup
    • Ensure initSdk is called before any SDK operation and retry initialization after checking the app environment
    SDK_NOT_INITIALIZED_OR_NOT_REGISTEREDSDK41101SDK is not initialized or not registered
    • The SDK has not completed its initialization flow or registration process
    • Call initSdk first, then complete registration before performing payment-related operations
    INSECURE_DEVICE_SETTINGSSDK41200Insecure device settings
    • The device does not meet the required security posture for SDK execution
    • Check developer options, ADB, rooted or emulator conditions, and any security hardening requirements
    INSECURE_RUNTIME_ENVIRONMENTSDK41300Insecure runtime environment
    • The app or runtime environment is not considered secure enough for payment operations
    • Review app integrity, runtime protections, overlays, jailbreak/root conditions, and security checks
    ATTESTATION_FAILEDSDK41400Attestation failed
    • The SDK could not prove that the device and runtime are in a trusted state
    • Retry attestation or verify device/runtime compliance and network connectivity to the attestation service
    INVALID_PARAMETERSSDK41500Invalid parameters
    • One or more input values do not conform to the expected SDK contract
    • Validate the request values, key IDs, and encrypted payload format before retrying
    KEY_OR_CRYPTO_FAILURESDK41600Key missing, invalid key or certificate, key provisioning failed, or crypto operation failed
    • The SDK cannot access a required key or certificate, or crypto processing failed
    • Check provisioning state, key injection, certificate validity, and retry with the correct key material
    REGISTRATION_FAILEDSDK41800Registration failed
    • The SDK could not complete registration with the AMS or backend service
    • Verify environment configuration, network access, license validity, and retry registration
    NETWORK_UNREACHABLESDK41900Network unreachable
    • The SDK could not reach the required service endpoint
    • Check connectivity, firewall settings, and backend availability before retrying
    NETWORK_TIMEOUTSDK42000Network timeout
    • The SDK request to the backend timed out while waiting for a response
    • Retry the operation and confirm network quality and server responsiveness
    SERVER_ERRORSDK42100Server error
    • The backend returned a server-side failure while processing the request
    • Review server logs or contact support if the issue persists across retries
    CLIENT_ERRORSDK42200Client error
    • The request was rejected by the service due to incorrect client-side data or validation
    • Check the request payload, environment configuration, and API contract for any mismatches
    CARD_PROCESSING_FAILEDSDK43000Card processing failed
    • The SDK could not complete the card transaction flow successfully
    • Check card support, app configuration, transaction parameters, and EMV setup before retrying
    NO_SUPPORTED_APP_ON_CARDEMV-3No supported application on the card
    • The card does not contain a supported payment application for the requested flow
    • Verify the card scheme compatibility and supported application list
    CARD_APP_NOT_SUPPORTED_OR_PROHIBITEDEMV-38Card application not supported or prohibited
    • The selected or detected app is not allowed for the current transaction flow
    • Check EMV app configuration and supported payment method constraints
    UNKNOWN_ERRORGENERIC99999Unknown error
    • The cause is not recognized by the SDK and requires deeper investigation
    • Collect logs and contact support for investigation if the issue persists
    TRANSACTION_INVALID_INPUTTRANSACTION70001Invalid input
    • The transaction request contains invalid or malformed values
    • Validate the transaction data before retrying the payment flow
    TRANSACTION_CARD_TAP_TIMEOUTTRANSACTION70002Card tap timed out
    • The user did not tap or complete card detection within the allowed time
    • Ask the user to retry the tap and confirm the device NFC state
    TRANSACTION_USER_CANCELLED_TAPTRANSACTION70003User cancelled the tap
    • The card tap flow was aborted by the user
    • Retry the transaction if a second attempt is required
    TRANSACTION_USER_CANCELLED_PINTRANSACTION70004User cancelled PIN entry
    • The user exited the PIN-pad flow before PIN completion
    • Retry and guide the user through PIN entry again if needed
    TRANSACTION_PIN_TIMEOUTTRANSACTION70005PIN entry timed out
    • The user did not complete the PIN entry before the timeout window expired
    • Retry the transaction and ask the user to complete the PIN entry promptly
    TRANSACTION_SECURITY_CHECK_FAILEDTRANSACTION70006Security check failed
    • A security validation aborted the transaction due to a risky or non-compliant runtime state
    • Verify app security posture and re-run the transaction once the condition is resolved
    TRANSACTION_ACTIVITY_QUITTRANSACTION70007Payment activity quit
    • The payment activity ended before the transaction was completed
    • Retry the transaction when the user returns to the payment flow
    TRANSACTION_KEY_LOADING_FAILEDTRANSACTION70008Card key loading failed
    • The required card key could not be loaded for transaction processing
    • Check key provisioning and device security state before retrying
    TRANSACTION_TIMEOUT_OR_RETRIES_EXCEEDEDTRANSACTION70009Processing timed out, or card read retries exceeded
    • The card processing exceeded the allowed time or retry limit
    • Retry the payment flow and review transaction timings and card read conditions
    TRANSACTION_CARD_DECLINEDTRANSACTION70010Card declined
    • The issuer or card authorization path rejected the transaction
    • Review the card status, transaction eligibility, and issuer response details
    TRANSACTION_DATA_VALIDATION_ERRORTRANSACTION70011Card data validation error
    • The card data did not pass the validation checks required by the EMV flow
    • Confirm card data integrity and retry the transaction if the card can be read again
    TRANSACTION_CRYPTO_ERRORTRANSACTION70012Crypto error
    • A cryptographic operation related to card data or transaction protection failed
    • Review key availability, encryption mode configuration, and key provisioning state
    TRANSACTION_DATA_ENCRYPTION_ERRORTRANSACTION70013Card data encryption error
    • The transaction payload could not be encrypted correctly using the configured method
    • Check the encryption mode, key availability, and scheme-specific requirements
    TRANSACTION_PAYMENT_METHOD_NOT_SUPPORTEDTRANSACTION70014Payment method not supported
    • The selected payment method is not supported by the current SDK configuration
    • Verify the supported payment methods and adjust the transaction configuration accordingly
    TRANSACTION_SCREEN_TOO_SMALLTRANSACTION70015Screen too small for the PIN pad
    • The display area is insufficient for the PIN pad layout required by the flow
    • Use a larger available display area or configure a compatible UI layout
    TRANSACTION_SDK_NOT_INITIALIZEDTRANSACTION70016SDK not initialized
    • The payment flow was started before the SDK completed initialization
    • Call initSdk before starting any payment or PIN flow
    TRANSACTION_SDK_RECOVERY_FAILEDTRANSACTION70017SDK could not recover after its process restarted
    • The SDK process restarted and could not restore its state automatically
    • Retry the initialization flow and validate the runtime state or backend connectivity
    TRANSACTION_RETRYABLE_FAILURETRANSACTION71004Retryable failure — retry
    • The failure is transient and should be retried by the calling application
    • Retry the transaction after verifying connectivity and SDK state
    TRANSACTION_PIN_KEY_NOT_READYTRANSACTION71005PIN key not ready — retry
    • The PIN key is not yet ready for the current operation and must be retried
    • Wait for key readiness or re-run the initialization and provisioning flow
    TRANSACTION_PIN_ENTRY_EXCEPTIONTRANSACTION71006PIN entry exception
    • An exception occurred while processing the PIN entry flow
    • Retry the flow and verify the UI and runtime conditions for the PIN pad
    TRANSACTION_OTHER_SOURCE_ERRORTRANSACTION72000Error from another source
    • The root cause originated outside the direct payment flow and must be investigated separately
    • Review surrounding SDK, app, and backend state before retrying
    MHD_SDK_NOT_AVAILABLESDK987136SDK is not registered successfully due to failed attestation or in-secure runtime
    • SDK is not registered successfully. You should call init function to re-registered
    • If this name returns suddenly in API calling. it means SDK attestation status is not in a secure status (SECURITY_FLAW or UNDER_ATTACKING), you can invoke attestation API manually to get a secure attestation result to clean the status
    MHD_SDK_LICENSE_INVALIDSDK987137License reading/ analysis fails
    • License is modified/ changed which makes license integrity validation fails
    MHD_SDK_LICENSE_PATH_INVALIDSDK987138Invalid license path
    • License name is incorrect
    • No license
    MHD_SDK_LICENSE_EXPIREDSDK987139Expired license
    • Please contact MineSec support to renew the license file
    MHD_SDK_INIT_EMVFAILSDK987140EMV Kernel Initialization fails
    • Reason to be added
    MHD_SDK_INIT_STORAGEFAILSDK987141SDK init keystone file encryption fails
      MHD_SDK_NOT_INITIALIZEDGENERIC987142SDK is not initialized yet, please do initialize first.
      • SDK is under attacking. All critical credentials are removed, and the SDK status is reset to uninitialized status
      MHD_SDK_JNI_OBJECT_NULLGENERIC987143Input parameter null
      • the application obfuscation impacts the API input parameters which removes some parameter due to incorrect obfuscation rules. In this case, you should contact support for investigation. meanwhile, try to disable obfuscation to see if the issue is still happening
      MHD_SDK_JNI_ARRAY_NULLGENERIC987144Input array parameter null
      • the application obfuscation impacts the API input parameters which removes some parameter due to incorrect obfuscation rules. In this case, you should contact support for investigation. meanwhile, try to disable obfuscation to see if the issue is still happening
      • This rarely happens after 1.10.105.11. For early versions, strongly recommend to migrate to 1.10.105.12 or newer
      MHD_SDK_JNI_METHOD_NOTEXISTGENERIC987145Java method not found, might due to application obfuscation causing some SDK’s API missing during the compiling
      • Please contact our support for the pro-guard rule
      • For early versions, recommend to migrate to 1.10.105.12 or newer
      MHD_SDK_JNI_CLASS_NOTEXISTGENERIC987146Java class not found, might due to application obfuscation causing some SDK’s API missing during the compiling
      • Please contact our support for the pro-guard rule.
      • This rarely happens after 1.10.105.11. For early versions, strongly recommend to migrate to 1.10.105.12 or newer
      MHD_SDK_JNI_CLASS_EXCEPTIONGENERIC987147JNI exception
      • JNI issue - this rarely happens after 1.10.105.11
      • For early versions, recommend to migrate to 1.10.105.12 or newer
      MHD_SDK_INIT_MEMORY_ERRORGENERIC987152[Deprecated since 1.10.105.12+] SDK security memory initialization fails
      • SDK init security data storage fails. This usually happens due to encrypted shared-reference fails or key store unusual exceptions
      • This name code has been removed from SDK after 1.10.105.11. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer
      MHD_SDK_INIT_DEVICE_ERRORGENERIC987168[Deprecated since 1.10.105.12+] This device can not be profiled
      • CyWall Initialization fails due to device security check
      • This name code has been removed from SDK after 1.10.105. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer
      MHD_SDK_NETWORK_TIMEOUTSDK987170[Deprecated since 1.10.105.12+] SDK connection timeout
      • CyWall Initialization fails due to network connection fails
      • This name code has been removed from SDK after 1.10.105. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer
      MHD_SDK_NETWORK_ERRORSDK987171[Deprecated since 1.10.105.12+] Remote server name
      • CyWall Initialization fails due to network connection names
      • This name code has been removed from SDK after 1.10.105. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer
      MHD_SDK_NETWORK_SERVER_NOTAVAILABLESDK987172[Deprecated since 1.10.105.12+] Remote server is not available
      • CyWall Initialization fails due to network server internal names
      • This name code has been removed from SDK after 1.10.105. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer
      MHD_SDK_NETWORK_SERVER_ERRORRESPONSESDK987173[Deprecated since 1.10.105.12+] Remote server name
      • CyWall Initialization fails due to network server name response
      • This name code has been removed from SDK after 1.10.105. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer
      MHD_SDK_RANDOM_SEEDING_FAILSDK987174SDK random number seeding fails
      • Random number seeding fails due to fails reading random number from remote cloudHSM server. it has to be retried again.
      • This name code has been removed from SDK after 1.10.105.12. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer
      • Might also due to DNS issue, please contact support
      MHD_SDK_SECURITY_GENERAL_ERRORSDK987175[Deprecated since 1.10.105.12+] SDK security core general name
      • CyWall Initialization fails due to unknown general names
      • This name code has been removed from SDK after 1.10.105.12. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer
      MHD_SDK_SECURITY_PARAMETERS_ERRORSDK987176[Deprecated since 1.10.105.12+] SDK security parameters name
      • Get CyWall identifier fails due to invalid parameter setting. This happens during CyWall initialization
      • This name code has been removed from SDK after 1.10.105.12. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer
      MHD_SDK_SECURITY_NOT_REGISTEREDSDK987177[Deprecated since 1.10.105.12+] SDK secure core is not registered
      • SDK registration process fails. This may happens the device and application are not compliance with the AM server cots baseline OR the network communication between SDK and backend fails
      • You should retry the registration process by calling init function
      • contact support if this continuously happens as this may be caused by non-compliance with AM Cots-Baseline
      MHD_SDK_SECURITY_NOT_INITIALIZEDSDK987178SDK secure core initialization fails
      • SDK is under attacking. all critical credentials are removed, and the SDK status is reset to uninitialized status. please re-init the SDK
      • This is the same as MHD_SDK_NOT_INITIALIZED
      MHD_GENERAL_ERRORGENERIC987391General unknown name
      • Native functions registration fails
      • Java execution flow throws an exception which are not expected
      • Security storage exception
      • Cryptographic operation exception
      • Please contact support for log checking & investigation
      MHD_SDK_INVALID_PARAMETERGENERIC991232Input parameters are invalid
      • Reading invalid data / cryptographic sensitive parameters from security storage
      • Reading invalid EMV parameters from local storage
      • Input data can’t be transformed to recognized format. For example. A hex string can NOT to converted to byte array due to the length
      MHD_SDK_LICENSE_FAILEDOPENLICENSE987175Fails to open license file
      • IO Exception happens during license file reading. This rarely happens but you should retry init again when this name happens
      MHD_STORAGE_ERR_KEY_NOTFOUNDSDK999425Cryptographic key is not found
      • key is not found from security key database. This may occur due to provide an incorrect key name OR the key is removed if attestation result is UNDER_ATTACKING.
      • if the key is the payment keys that are injected by application developer. try to re-inject the key to resolve this issue.
      • if the key is managed by SDK itself. try to clean the application data cache and reinitialize the SDK.
      MHD_STORAGE_ERR_DEIVCE_UNMATCHSDK999427Device clone attack
      • Please contact support or you can also uninstall the application and reinstall application to eliminate the issue.
      MHD_KMS_KEY_READ_ERRORKMS1016065Reading key name due to not found or be modified
      • SDK is under insecure attestation status, which blocks the cryptographic key reading operation. please check the attestation status of the SDK.
      • key content is compromised. it can not be recovered by SDK. this can be only resolved by re-inject the key.
      • key transformation fails as the content can not be transformed to a recognized key block. this can be only resolved by re-inject the key.
      MHD_KMS_NOTSUPPORTED_TR31KMS1016066TR31 package is not supported
      • please check the user manual to understand the steps to inject a key with TR31 package
      • if the issue continuously occurs, please contact support and provide the TR31 key block for analysis.
      MHD_KMS_INCORRECT_TR31HEADERKMS1016067TR31 header is invalid
      • please check the user manual to understand the steps to inject a key with TR31 package
      • if the issue continuously occurs, please contact support and provide the TR31 key block for analysis.
      MHD_KMS_INCORRECT_MACKMS1016068TR31 mac result is invalid
      • please check the user manual to understand the steps to inject a key with TR31 package
      • if the issue continuously occurs, please contact support and provide the TR31 key block for analysis.
      MHD_KMS_INCORRECT_ENCRYPTKMS1016069Encryption fails
      • please check the user manual to understand the steps to inject a key with TR31 package
      • if the issue continuously occurs, please contact support and provide the TR31 key block for analysis.
      MHD_KMS_INCORRECT_KEYSIZEKMS1016072Invalid key size
      • please check the user manual to understand the steps to inject a key with TR31 package
      • if the issue continuously occurs, please contact support and provide the TR31 key block for analysis.
      MHD_KMS_KEY_ENCODED_ERRORKMS1016081Invalid key encoding
      • The key reading from security crypto database is not recognized as the format/encoding is not expected. Re-inject key can resolve this issue.
      MHD_KMS_KEY_TYPE_ERRORKMS1016082Key type (key usage) and value unmatched
      • The key reading from security crypto database is not accepted as the key type is NOT correct.
      • The name also occurs if a wrong key type is provided when doing key derivation. (for example: DUKPT IK AES-128 can only generate AES-128 working key or TDES working key. it can’t generate AES-256 key)
      MHD_KMS_KEY_RSA_PARSEERRORKMS1016083RSA key parsing name
      • RSA key parsing from PEM file OR from E,D,N big integer fails. OR
      • provided PEM file is not a correct key. (example: provide private key PEM as public key PEM)
      MHD_EMV_KERNEL_NOT_AVAILABLEEMV1020160No matching EMV Kernel could be found
      • The EMV kernel initialization fails
      • The EMV kernel does not support the AID parameters due to the EMV Card scheme supporting setting by license file.
      MHD_EMV_NFC_PERMISSION_MISSEMV1020161Missing NFC permission
        MHD_EMV_NFC_CAMERA_PERMISSION_MISSEMV1020162Missing camera permission
          MHD_EMV_NFC_NETWORK_UNCONNECTTEDEMV1020163Network is not connected
            MHD_EMV_NFC_DISABLEDEMV1020164NFC is disabled
              MHD_EMV_ADB_ENABLEDEMV1020165ADB is enabled
                MHD_EMV_SIDE_LOADEDEMV1020166Side loaded
                  ERR_UNKNOWN_CODEGENERIC99999Unknown name
                  • native functions registration fails
                  • java execution flow throws an exception which are not expected
                  • security storage exception
                  • cryptographic operation exception
                  • for this issue, it should contact support for checking the logging in behind.
                  MHD_SDK_REGISTREDSDK0SDK registered
                    MHD_SDK_NETWORK_TIMEOUTSDK196616Network connection timeout
                      MHD_SDK_LICENSE_ABOUT_TO_EXPIRESDK131079[Deprecated since 1.10.105.12+] Initialization fails due to network server name response
                      • CyWall license is going to be expired
                      • This name code has been removed from SDK after 1.10.105. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                      MHD_SDK_CLIENT_CERTIFICATE_EXPIREDSDK131080Client certificate has expired
                      • The client certificate has expired, so re-registration is not possible anymore. A new registration needs to be carried out.
                      MHD_SDK_ALREADY_REGISTEREDSDK131081SDK already registered
                        MHD_SDK_NOT_REGISTEREDSDK131082SDK not registered
                        • you are invoking SDK APIs without SDK being registered successfully. please register it successfully prior to calling those APIs
                        MHD_GENERAL_ERRORSDK987391Unknown name
                        • native functions registration fails
                        • java execution flow throws an exception which are not expected.
                        • security storage exception
                        • cryptographic operation exception
                        • for this issue, it should contact support for checking the logging in behind.
                        MHD_SDK_STORAGE_DEVICE_MISMATCHSDK327685Application instance does not match the device
                        • device clone attacking. in this case, please contact with solution provider or support. you can also uninstall the application and reinstall application to eliminate the issue.
                        MHD_SDK_INVALID_SERVER_RESPONSESDK983045[Deprecated since 1.10.105.12+] Initialization fails due to network server name response
                        • This name code has been removed from SDK after 1.10.105. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                        MHD_SDK_INVALID_PARAMETERSDK991232Invalid parameters
                        • reading invalid data / cryptographic sensitive parameters from security storage
                        • reading invalid EMV parameters from local storage
                        • input data can’t be transformed to recognized format. (for example. A hex string can NOT to converted to byte array due to the length of
                        MHD_SDK_INIT_FAILSDK987136[Deprecated since 1.10.105.12+] Invalid SDK status
                        • SDK initialization fails due to invalid status in SdkCurrentStatus in SDK_CONTEXT
                        • This name code has been removed from SDK after 1.10.105. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                        MHD_SDK_SEC_FAILSDK987137[Deprecated since 1.10.105.12+] Security of SDK is impacted by some attacks
                        • One status in SdkCurrentStatus in SDK_CONTEXT failed
                        • This means security of SDK is impacted by some attacks
                        • This name code has been removed from SDK after 1.10.105. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                        MHD_SDK_REGISTRATION_FAILSDK987138[Deprecated since 1.10.105.12+] SDK is not registered
                        • SDK is not registered. SDK will not work under this status.
                        • This name code has been removed from SDK after 1.10.105. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                        MHD_SDK_LICENSE_EXPIREDSDK987139[Deprecated since 1.10.105.12+] SDK license is expired
                        • SDK license is expired. SDK will not work under this status
                        • This name code has been removed from SDK after 1.10.105.12 (no expiration date). for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                        MHD_SDK_EMV_INIT_FAILSDK987140EMV kernel initialization fails. please try re-init again.
                          MHD_SDK_STORAGE_INIT_FAILSDK987141Storage initialization fails. please try re-init again
                            MHD_SDK_NOT_AVAILABLESDK987142SDK internal warning due to not registered or expired license
                            • SDK latest attestation result is not “HEALTH” status. retry or re-open application to clean the status.
                            • SDK is under “block” status. contact service admin to unblock this SDK
                            MHD_SDK_OBJECT_NULLSDK987143SDK internal warn of object not existing
                            • Input parameters are NULL
                            • the application obfuscation impacts the API input parameters which removes some parameter due to incorrect obfuscation rules. In this case, you should contact support for investigation. meanwhile, try to disable obfuscation to see if the issue is still happening
                            MHD_SDK_ARRAY_NULLSDK987144SDK internal warn of array is not available
                            • Input parameters are NULL
                            • the application obfuscation impacts the API input parameters which removes some parameter due to incorrect obfuscation rules. In this case, you should contact support for investigation. meanwhile, try to disable obfuscation to see if the issue is still happening
                            MHD_SDK_METHOD_NOTEXISTSDK987145[Deprecated since 1.10.105.11+] SDK internal warn that method is not available
                            • SDK internal warn that method is not available
                            • the application obfuscation impacts the API definitions which removes some API methods due to incorrect obfuscation rules. In this case, you should contact support for investigation. meanwhile, try to disable obfuscation to see if the issue is still happening
                            • This rarely happens after 1.10.105.11. For early versions, strongly recommend to migrate to 1.10.105.12 or newer
                            MHD_SDK_CLASS_NOTEXISTSDK987146[Deprecated since 1.10.105.11+] SDK internal warn that class is not available
                            • the application obfuscation impacts the API definitions which removes some API methods due to incorrect obfuscation rules. In this case, you should contact support for investigation. meanwhile, try to disable obfuscation to see if the issue is still happening
                            • This rarely happens after 1.10.105.11. For early versions, strongly recommend to migrate to 1.10.105.12 or newer
                            MHD_SDK_JCLASS_EXCEPTIONSDK987147[Deprecated since 1.10.105.11+] SDK internal warn java class exceptions
                            • the application obfuscation impacts the API definitions which removes some API methods due to incorrect obfuscation rules. In this case, you should contact support for investigation. meanwhile, try to disable obfuscation to see if the issue is still happening
                            • This rarely happens after 1.10.105.11. For early versions, strongly recommend to migrate to 1.10.105.12 or newer
                            MHD_SDK_BOOLEAN_NULLSDK987148[Deprecated since 1.10.105.11+] SDK internal warn that boolean is not available
                            • the application obfuscation impacts the API definitions which removes some API methods due to incorrect obfuscation rules. In this case, you should contact support for investigation. meanwhile, try to disable obfuscation to see if the issue is still happening
                            • This rarely happens after 1.10.105.11. For early versions, strongly recommend to migrate to 1.10.105.12 or newer
                            MHD_KMS_INVALID_INPUTKMS1015808KMS operation input parameters are invalid
                            • key loading parameters are incorrect.(providing RSA wrapped key block for TR31 key injection)
                            • cipher operation. (for example: using a AES Key to do TDES operation. or signing data using encryption key)
                            MHD_KMS_RSA_GENKEYERRKMS1015809KMS mbedtls RSA key generation fails during registration stage
                            • It happens usually due to the insufficient random numbers OR memory management.
                            • Retry the API will usually resolve it.
                            MHD_KMS_RSA_EXPORTERRKMS1015810KMS RSA key exporting fails during registration stage
                            • It happens usually due to the insufficient random numbers OR memory management.
                            • Retry the API will usually resolve it.
                            MHD_KMS_RSA_INCORRECT_PARAMETER_HEXSIZEKMS1015811RSA Key size name, it must be 2048-bit or above, and hex string should be 2*N in length
                              MHD_KMS_READ_PKERRKMS1015812KMS read RSA public key from security key store fails
                              • it happens due to key is compromised
                              MHD_KMS_READ_SKERRKMS1015813KMS read RSA private key from security key store fails
                              • it happens due to key is compromised
                              MHD_KMS_KEY_NOT_EXISTKMS1015814Key can’t be found in crypto database
                                MHD_KMS_KEY_NOT_CORRECTKMS1015815Deprecated since 1.10.105.12+
                                • This name code has been removed from SDK after 1.10.105.12(no expiration date). for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                                MHD_KMS_AES_KEYSIZE_ERRKMS1015816Deprecated since 1.10.105.12+
                                • This name code has been removed from SDK after 1.10.105.12(no expiration date). for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                                MHD_KMS_AES_INCORRECT_IVKMS1015817Deprecated since 1.10.105.12+
                                • This name code has been removed from SDK after 1.10.105.12(no expiration date). for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                                MHD_KMS_AES_CIPHERMODE_NOTFOUNDKMS1015818Deprecated since 1.10.105.12+
                                • This name code has been removed from SDK after 1.10.105.12(no expiration date). for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                                MHD_KMS_OUTPUT_BUFFER_TOO_SMALLERKMS1015819Deprecated since 1.10.105.12+
                                • This name code has been removed from SDK after 1.10.105.12(no expiration date). for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                                MHD_KMS_AES_MODE_ERRORKMS1015820Deprecated since 1.10.105.12+
                                • This name code has been removed from SDK after 1.10.105.12(no expiration date). for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                                MHD_KMS_KEYNAME_NOTALLOWEDKMS1016064Deprecated since 1.10.105.12+
                                • This name code has been removed from SDK after 1.10.105.12(no expiration date). for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                                MHD_KMS_KEY_READ_ERRORKMS1016065SDK is under insecure attestation status, which blocks the cryptographic key reading operation. please check the attestation status of the SDK
                                • key content is compromised. it can not be recovered by SDK. this can be only resolved by re-inject the key.
                                • key transformation fails as the content can not be transformed to a recognized key block. this can be only resolved by re-inject the key.
                                MHD_KMS_NOTSUPPORTED_TR31KMS1016066TR31 key block is not supported by SDK
                                • please check the user manual to understand the steps to inject a key with TR31 package
                                • if the issue continuously occurs, please contact support and provide the TR31 key block for analysis
                                MHD_KMS_INCORRECT_TR31HEADERKMS1016067TR31 key block validation fails
                                • please check the user manual to understand the steps to inject a key with TR31 package
                                • if the issue continuously occurs, please contact support and provide the TR31 key block for analysis.
                                MHD_KMS_INCORRECT_MACKMS1016068TR31 package Mac verification fails
                                • This may happen when TR31 package is not correctly delivered or generated
                                MHD_KMS_INCORRECT_ENCRYPTKMS1016069Encryption process failed
                                • AES GCM operation fails (tag check fails)
                                • DUKPT Key generation fails (counter exceeds)
                                • crypto operation mode incorrect(it is neither CIPHER_ENCRYPT nor CIPHER_DECRYPT)
                                MHD_KMS_INCORRECT_PAYLOADKMS1016070Deprecated since 1.10.105.12+
                                • This name code has been removed from SDK after 1.10.105.12 (no expiration date). for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                                MHD_KMS_TR31PARSE_ERRORKMS1016071Fails to parse TR31 package
                                • TR31 package is incomplete OR
                                • TR31 format is not supported (key binding method). Please contact support
                                MHD_KMS_INCORRECT_KEYSIZEKMS1016072Key size is in correct
                                • E.g. provide a AES key array with key size exceeds 256 bits. AES max key size 256
                                • please check your key management solution
                                MHD_AST_ERR_PK_GEN_FAILKMS995329Deprecated since 1.10.105.11+
                                • This name code has been removed from SDK after 1.10.105.11. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                                MHD_AST_ERR_CSR_GEN_FAILKMS995330Deprecated since 1.10.105.11+
                                • This name code has been removed from SDK after 1.10.105.11. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                                MHD_AST_ERR_PK_NE_GEN_FAILKMS995331Deprecated since 1.10.105.11+
                                • This name code has been removed from SDK after 1.10.105.11. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                                MHD_AST_ERR_CURLE_COULDNT_RESOLVE_HOST_FAILKMS995334Deprecated since 1.10.105.11+
                                • This name code has been removed from SDK after 1.10.105.11. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                                MHD_AST_ERR_CURLE_COULDNT_CONNECT_FAILKMS995335Deprecated since 1.10.105.11+
                                • This name code has been removed from SDK after 1.10.105.11. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                                MHD_AST_ERR_CURLE_OPERATION_TIMEDOUT_FAILKMS995356Deprecated since 1.10.105.11+
                                • This name code has been removed from SDK after 1.10.105.11. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                                MHD_AST_ERR_CURLE_SSL_CONNECT_ERROR_FAILKMS995363Deprecated since 1.10.105.11+
                                • This name code has been removed from SDK after 1.10.105.11. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                                MHD_AST_ERR_CURLE_DRBG_SEEDINGFAILKMS995585Deprecated since 1.10.105.11+
                                • This name code has been removed from SDK after 1.10.105.11. for early versions, it is strongly recommended to migrate to 1.10.105.12 or newer.
                                EMV/ Kernel