Status Codes

General

Transaction Result
Code	Description	Possible Transaction Outcomes
`0`	Transaction Successful	-
`7005`	Transaction Failed	Missing Parameters Network Unavailable Request Timeout Service Unavailable Session Expired

Missing Parameters

Code	`9984`
Source	SDK
Root Cause	Missing required parameters from login.
Resolution	Perform refresh token.

Network Unavailable

Code	`1000`
Source	SDK
Root Cause	Internet is not detected.
Resolution	Connect to a stable network.

Request Timeout

Code	`1001`
Source	SDK
Root Cause	Service is currently unavailable.
Resolution	Please try again later. Connect to a stable network.

Service Unavailable

Code	`-1004`
Source	SDK
Root Cause	Service is currently unavailable.
Resolution	Please try again later. Connect to a stable network and perform refresh token again.

Code	`9010`
Source	Backend
Root Cause	Invalid service name/ version
Resolution	-

Code	`9011`
Source	Backend
Root Cause	Method invocation error
Resolution	-

Code	`10001`
Source	Backend
Root Cause	Service is currently unavailable.
Resolution	Please try again later.

Session Expired

Code	`2002`
Source	Backend
Root Cause	Session is expired or kicked out from others.
Resolution	Perform refresh token again.

Refresh Token

Transaction Result
Code	Description	Possible Transaction Outcomes
`7005`	Transaction Failed	Login Account Suspended Invalid Login Invalid SSO Token

Code	`3011`
Source	Backend
Root Cause	Merchant has exceeded a maximum number of attempts. Mobile user account is blocked / suspended.
Resolution	Please contact your merchant system administrator to reinstate the account via bank portal or merchant.

Code	`5010`
Source	Backend
Root Cause	Mobile user account login is invalid or the SSO token is invalidated.
Resolution	Please verify the login credentials and perform refresh token again.

Invalid SSO Token

Code	`14015`
Source	Backend
Root Cause	Mobile user's sso token has been revoked or mobile user is different from the previous.
Resolution	-

Sale / Refund

Transaction Result
Code	Description	Possible Transaction Outcomes
`0`	Transaction Successful	Transaction Approved
`7005`	Transaction Failed	Transaction Failed Transaction Pin Not Supported No Application Supported Transaction Declined GPO failed Transaction Online Failed Card Locked Appendix A Exceeded Maximum Monthly Transaction Limit Exceeded Maximum Transaction Limit Unable to Process Payment Host Error Service Unavailable - Failed to Establish Host Connection Service Unavailable - Connection Timeout Batch Upload Failed Card Expired / Not Effective Card Not Effective Yet Unable to Perform Transaction
`7024`	Transaction Cancelled	Transaction Cancelled
`520`	Attestation Failed	-

Transaction Approved

Code	`100`
Source	Backend

Transaction Failed

Code	`7056`
Source	SDK
Root Cause	Transaction failed due to “Bad Tap” in the midst of processing.
Resolution	-

Transaction Pin Not Supported

Code	`7059`
Source	SDK
Root Cause	Transaction failed due to transaction amount above CVM limit and card type is not supported for PIN.
Resolution	-

No Application Supported

Code	`9012`
Source	SDK
Root Cause	Transaction has been declined, card is declined by kernel.
Resolution	Try another card.

GPO Failed

Code	`7501`
Source	SDK
Root Cause	Exception during GPO command (Timeout/Tag lost). Applicable to JCB only.
Resolution	-

Transaction Online Failed

Code	`7020`
Source	SDK
Root Cause	Transaction trying to send online is not successful, possible missing key or didn't perform login.
Resolution	Perform refresh token.

Card Locked

Code	`7502`
Source	SDK
Root Cause	Card locked response during GPO command (6F00). Applicable to JCB only.
Resolution	-

Appendix A

Code	`2**`
Source	Backend
Root Cause	-
Resolution	-

Exceeded Maximum Monthly Transaction Limit

Code	`5111`
Source	Backend
Description	You have exceeded your maximum monthly transaction limit. Please contact our support hotline.
Root Cause	Total monthly transaction limit has exceeded.
Resolution	Bank may either increase the monthly transaction limit (change default maximum value) or disable limitation.

Exceeded Maximum Transaction Limit

Code	`5112`
Source	Backend
Description	You have exceeded your maximum per transaction limit. Please contact our support hotline.
Root Cause	Total per transaction limit is exceeded.
Resolution	Bank may either increase the per transaction limit (change default maximum value) or disable limitation.

Unable to Process Payment

Code	`5120`
Source	Backend
Description	Unable to process payment. Please try again. If problem persists, kindly contact our merchant hotline.
Root Cause	Batch is not ready. There is one or more processing / unsuccessful settlement.
Resolution	Please either settle transactions manually or retry the transaction again.

Host Error

Code	`8090`
Source	Backend
Description	Host error. Please contact our support hotline.
Root Cause	Host timeout or return an empty response. Service is currently unavailable.
Resolution	Please try again later. Connect to a stable network.

Service Unavailable - Failed to Establish Host Connection

Code	`8091`
Source	Backend
Description	Service is unavailable. Please try again later.
Root Cause	Unable to establish connection to host, host is possibly down. Service is currently unavailable.
Resolution	Please try again later. Connect to a stable network.

Service Unavailable - Connection Timeout

Code	`8092`
Source	Backend
Description	Service is unavailable. Please try again later.
Root Cause	Connection to host has timeout from payment server side. Service is currently unavailable.
Resolution	Please try again later. Connect to a stable network.

Batch Upload Failed

Code	`8093`
Source	Backend
Description	Batch upload has failed. Please contact our support hotline.
Root Cause	Batch upload is not successfully completed based on host's response.
Resolution	-

Card Expired / Not Effective

Code	`9002`
Source	Backend
Root Cause	Customer's card is expired. Or merchant need to change device's year format to gregorian in some case.
Resolution	Make sure to set device's date to current date.

Card Not Effective Yet

Code	`9003`
Source	Backend
Root Cause	Card used is not effective yet, not activated or suspended.
Resolution	-

Unable to Perform Transaction

Code	`9004`
Source	Backend
Root Cause	Unable to perform transaction.
Resolution	-

Transaction Cancelled

Source	SDK
Root Cause	-
Resolution	-

Void

Transaction Result
Code	Description	Possible Transaction Outcomes
`7005`	Transaction Failed	Insufficient Privilleges Void Denied Void Error

Insufficient Privilleges

Code	`3012`
Source	Backend
Description	You do not have the required permissions to perform void payment or credit settlement functions.
Root Cause	Void / Settle buttons are disabled for users which do not have permission to void or settle transactions.

Void Denied

Code	`9022`
Source	Backend
Description	Void denied. Not allowed to void this transaction type.
Root Cause	This transaction type is not allowed to void.

Void Error

Code	`19000`
Source	Backend
Description	Error. Please call the support line (4000).
Root Cause	This transaction type is not allowed to void.

Send Receipt

Transaction Result
Code	Description	Possible Transaction Outcomes
`7005`	Transaction Failed	Invalid Mobile Number Invalid Email Address Email / SMS Service Unavailable

Invalid Mobile Number

Code	`5113`
Source	Backend
Root Cause	Customer entered an invalid phone number for e-receipt. Phone number is not between 10 to 11 digits.

Invalid Email Address

Code	`5114`
Source	Backend
Root Cause	Customer entered an invalid email address format for e-receipt.
Resolution	Make sure not to enter special characters or space.

Email / SMS Service Unavailable

Code	`5115`
Source	Backend
Description	Email / SMS service is currently not available. Please contact our support hotline.
Root Cause	Email / SMS e-receipt sending service is currently unavailable.

Get Transaction Status

Transaction Result
Code	Description	Possible Transaction Outcomes
`0`	Transaction Successful	Transaction Status Returned
`7005`	Transaction Failed	Service Unavailable

Transaction Status Returned

Code	`10x`
Source	Backend

Service Unavailable

Code	`10001`
Source	Backend
Description	Service is currently unavailable. Please try again later.
Root Cause	Invalid Transaction ID passed to API which unable to query the transaction.
Resolution	Make sure the valid Transaction ID is pass in.

QR Sales

Transaction Result
Code	Description	Possible Transaction Outcomes
`0`	Transaction Successful	QR Transaction Approved / Successful
`7005`	Transaction Failed	QR Payment Unsupported QR Type Unsupported QR Transaction Error

QR Transaction Approved / Successful

Code	`100`
Source	Backend
Description	QR Transaction approved /successfully.

QR Payment Unsupported

Code	`9500`
Source	SDK
Root Cause	QR Payment is not enabled for the account.
Resolution	Enable QR Payment support for the user account and perform token again.

QR Type Unsupported

Code	`9501`
Source	SDK
Root Cause	QR Payment is not enabled for the account.
Resolution	Enable QR Type support for the user account and perform refresh token again.

QR Transaction Error

Code	`19000`
Source	SDK
Description	Error. Please call the support line (4000).
Root Cause	QR transaction request failed.
Resolution	Request QR transaction again.

Attestation Error Codes

Code	`0`
Source	SDK
Root Cause	Operation carried out successfully
Resolution	(Not applicable)

Code	`-1`
Source	SDK
Root Cause	It usually occurs during development phase, when attestation library isn't being initialized
Resolution	Solve the integration error before production

Code	`-2`
Source	SDK
Root Cause	The permisison(s) required by the attestation library to carry out operations is(are) not granted by the user
Resolution	Prompt user to grant permission, or manually go to OS setting page to grant the permissions needed

Code	`1`
Source	SDK
Root Cause	Unexpected error that happens within attestation library
Resolution	Relaunch the App and retry attestation

Code	`2`
Source	SDK
Root Cause	Error occurs while carrying out attestation operations from attestation backend
Resolution	Relaunch the App and retry attestation

Code	`3`
Source	SDK
Root Cause	Data needed are not valid, usually occurs during development
Resolution	Resolving this error during development

Code	`4`
Source	SDK
Root Cause	Usually it occurs when reader is malfunctioned
Resolution	Relaunch the App and retry attestation, if problem persists, replace reader

Code	`5`
Source	SDK
Root Cause	Error when processing data in attestation library. Usually occurs during development phase
Resolution	Resolving this error during development. Relaunch the App to retry attestation

Code	`6`
Source	SDK
Root Cause	Error when processing data in attestation library. Usually occurs during development phase
Resolution	Resolving this error during development. Relaunch the App to retry attestation

Code	`7`
Source	SDK
Root Cause	Error when processing data in attestation library. Usually occurs during development phase
Resolution	Relaunch the App to retry attestation

Code	`8`
Source	SDK
Root Cause	Execution of a certain operation that is not permitted
Resolution	Relaunch the App to retry attestation

Code	`9`
Source	SDK
Root Cause	When device's memory is less than the attestation's library needs
Resolution	Suggest user to quit other memory draining apps. > Search "memory" in phone, usually phone will have option to free up memory > Quitting other not-in-use app from the background

Code	`10`
Source	SDK
Root Cause	This error will not be raised
Resolution	-

Code	`11`
Source	SDK
Root Cause	Google Play Service is not available
Resolution	Check the device and see Google Play Service is installed and updated

Code	`12`
Source	SDK
Root Cause	Google Safetynet is not available
Resolution	Check the device and see Google Play Service is installed and updated

Code	`256`
Source	SDK
Root Cause	This error will not be raised
Resolution	-

Code	`257`
Source	SDK
Root Cause	Needed file is missing or corrupted
Resolution	Try clear data from app Try re-installing app

Code	`258`
Source	SDK
Root Cause	Network down
Resolution	Check network (WiFi or Telco)

Code	`259`
Source	SDK
Root Cause	Attestation server returning unexpected response
Resolution	Relaunch the App to retry attestation If problem persists, replace reader

Code	`513`
Source	SDK
Root Cause	Security key is missing
Resolution	Try clear data from app Try re-installing app

Code	`514`
Source	SDK
Root Cause	Security key is corrupted
Resolution	Try clear data from app Try re-installing app

Code	`515`
Source	SDK
Root Cause	Security key is corrupted
Resolution	Try clear data from app Try re-installing app

Code	`516`
Source	SDK
Root Cause	Cryptographic operation carried out unsuccessfully
Resolution	Usually occurs when data of the app is corrupted. Can try clear data from app or re-installing app

Code	`517`
Source	SDK
Root Cause	Certificate of the attestation server in the device has expired
Resolution	Usually occurs and resolves internally If problem persist, try reinstalling app

Code	`518`
Source	SDK
Root Cause	Certificate file is missing. Probably due to data file corrupted
Resolution	First try checking if connection is working fine, whether device has a proper connection to the internet If it's working fine, try clear data from app Re-install app

Code	`519`
Source	SDK
Root Cause	Certificate isn't recognized. This usually happens when the app isn't installed from a legit app store
Resolution	Download and install app from proper App Store/ Play Store

Code	`520`
Source	SDK
Root Cause	The device has failed attestation. Usually happens when device is compromised/ jailbroken/ rooted
Resolution	Download and install app from proper App Store/ Play Store Change device

Code	`521`
Source	SDK
Root Cause	The reader has failed attestation. Usually occurs when the reader is not recognized, or malfunctioned
Resolution	Replace the reader

Code	`522`
Source	SDK
Root Cause	The reader has failed to activate. Usually occurs when the reader is not recognized, or malfunctioned
Resolution	Replace the reader

Code	`523`
Source	SDK
Root Cause	Provisioning operation has failed. Usually occurs when the data is corrupted while communicating with backend server
Resolution	Try clear data from app Try re-installing app

Code	`524`
Source	SDK
Root Cause	When the key exchange operation carried out unsuccessfully. Usually occurs when the data is corrupted while communicating with backend server. Or key files corrupted
Resolution	Try clear data from app Try re-installing app

Code	`769`
Source	SDK
Root Cause	Trying to login as a different user than previously logged in user
Resolution	App would resolve this by prompting user to confirm if s/he is intended to switch to another user

Code	`770`
Source	SDK
Root Cause	Trying to login as a different reader than previously logged in reader
Resolution	App would resolve this by prompting user to confirm if s/he is intended to switch to another reader

Code	`771`
Source	SDK
Root Cause	Trying to use a reader which firmware is incorrect
Resolution	Try another reader Check enviroment of reader "UAT/PROD"

Code	`772`
Source	SDK
Root Cause	Trying to use a reader which key is incorrect
Resolution	Try another reader Check enviroment of reader "UAT/PROD"

Code	`520001`
Source	SDK
Root Cause	COTS's time is not synchronized with server during attestation
Resolution	App would resolve this by prompt the user to synchronize time on the device

Code	`520002`
Source	SDK
Root Cause	Security patch version is outdated/non-compliance
Resolution	App would resolve this by updating to latest security patches if available

Code	`520003`
Source	SDK
Root Cause	Trying to use an application that downloaded from an unknown source
Resolution	Redownload the application from the legitimate App Store(Google Play)

Code	`520004`
Source	SDK
Root Cause	Trying to use an application or device that's fails play integrity verification
Resolution	Usually occurs when the COTS is not passing Play Integrity verification, using a CTS certified device can resolve this

Code	`520101`
Source	SDK
Root Cause	The device developer mode option is enabled
Resolution	Turn off device developer mode

Code	`520102`
Source	SDK
Root Cause	The device ADB is enabled
Resolution	Turn off device developer mode

Code	`520103`
Source	SDK
Root Cause	Rooted device detected
Resolution	Use non rooted device

Code	`520104`
Source	SDK
Root Cause	The device USB debugging is enabled
Resolution	Turn off device developer mode

Code	`520105`
Source	SDK
Root Cause	The app run on a emulator
Resolution	Install app on real device

Code	`520106`
Source	SDK
Root Cause	Malicious hooking activity, or hooking app in the background
Resolution	Delete malicious app that causing the hooked events

Mobile Error Codes

Code	`-1001`
Source	SDK
Root Cause	Connection request timeout
Resolution	Retry the action. This is sometimes due to bad connection. Inform mobile support if issue still persist

Code	`-1003`
Source	SDK
Root Cause	Connection error to payment server - cannot find from path link.
Resolution	Inform server support team

Code	`-1004`
Source	SDK
Root Cause	Service is currently unavailable
Resolution	Please try again later. Connect to a stable network and perform refresh token again.

Code	`-1005`
Source	SDK
Root Cause	Connection network to payment server is dropped off
Resolution	Retry action Inform server support if issue still persist

Code	`-1006`
Source	SDK
Root Cause	Certificate pinning
Resolution	Inform server support team

Code	`-1202`
Source	SDK
Root Cause	Secure certification of payment server is untrusted
Resolution	Inform server support team

Code	`1001`
Source	SDK
Root Cause	This error code is only happened during payment process when payment timeout of 70s is triggered
Resolution	Please check the sales history to make sure this transaction is not recorded. Then, retry the transaction.

Code	`1002`
Source	SDK
Root Cause	Unrecoverable error occur from payment server side. Need payment log for further troubleshoot
Resolution	Retry the action. This is sometimes due to bad connection.

Code	`1006`
Source	SDK
Root Cause	Certificate of SSL has expired or got issue in cert pinning
Resolution	Inform server support team

Code	`2002`
Source	SDK
Root Cause	Device's session has expired, possible cause include server restart (manually triggered by dev)
Resolution	Perform re-login

Code	`3032`
Source	SDK
Root Cause	Faulty reader due to key injection issue, i.e. reader didn't perform/pass key injection test
Resolution	Replace new reader

Code	`6000`
Source	SDK
Root Cause	The reader has been tampered and will need to be returned and replaced with a new reader
Resolution	Replace new reader

Code	`6001`
Source	SDK
Root Cause	(Not specified)
Resolution	Check internet connection Check if reader has sufficient battery level

Code	`7004`
Source	SDK
Root Cause	The bank has returned the message 'Transaction Declined' when processing the transaction
Resolution	Try with another card

Code	`7005`
Source	SDK
Root Cause	The bank has returned the message 'Transaction Failed' when processing the transaction
Resolution	Retry with existing card Try with another card

Code	`7028`
Source	SDK
Root Cause	The transaction has timed out. The customer is advised to remove their card and try again
Resolution	Retry with existing card Try with another card

Code	`7024`
Source	SDK
Root Cause	Cancel transaction while entering the Cardholder PIN
Resolution	(Not specified)

Code	`7041`
Source	SDK
Root Cause	Happen during contactless transaction: when the card tapped and removed immediately from the FLite reader; Paywave-inactivated-card tried to make contactless transaction
Resolution	Try with another interface (if perform contactless trx, advice user to try with contact) Try with another card

Code	`7054`
Source	SDK
Root Cause	FLite reader activation processes failed during first time connecting / new device (TBC)
Resolution	Disconnect and reconnect the reader

Code	`7056`
Source	SDK
Root Cause	The transaction has failed for an unknown reason
Resolution	This error code is obsoleted, if indeed receive this error code, please consult IT

Code	`7060`
Source	SDK
Root Cause	Card scheme not supported or min amount is not met for the campaign
Resolution	Check if customer's card or amount is within supported campaign setup

Code	`9803`
Source	SDK
Root Cause	The POS application has tried to initiate a payment with an invalid payment amount. Ensure the value is not 0 or empty
Resolution	Enter amount other than 0 If user has entered amount other than 0 but issue persists, contact mobile support team

Code	`9804`
Source	SDK
Root Cause	The POS application has tried to void the payment
Resolution	Check if transaction reference number is valid Check if transaction status is Approved

Code	`9805`
Source	SDK
Root Cause	The POS application has tried to initiate an action that is not supported or not enabled on this account
Resolution	Check if partner is enabled for the action type

Code	`9812`
Source	SDK
Root Cause	An error occurred when trying to complete a quickchip payment
Resolution	Check if quickchip is enabled for user Check if reference number is valid Check if SSO company identifier is valid Enable quickchip if required

Code	`9987`
Source	SDK
Root Cause	The POS application has attempted to initiate a quickchip payment but quickchip is disabled for this merchant
Resolution	-

Code	`9990`
Source	SDK
Root Cause	Your device is detected to be rooted or jailbroken
Resolution	(Not specified)

Code	`9991`
Source	SDK
Root Cause	When route from 3rd party app to MPOS app and detects MPOS app does not have any user activated before
Resolution	Please guide merchant to do activation on the MPOS app first. Then only connect via 3rd party app

Code	`9992`
Source	SDK
Root Cause	SDK unexcepted exception
Resolution	Inform mobile support team

Code	`9993`
Source	SDK
Root Cause	Get KSN Fail, this device is malfunction or is not yet injected
Resolution	Replace new reader

Code	`9994`
Source	SDK
Root Cause	Unexpected error occur from mobile app side
Resolution	Relogin and retry action Inform terminal support if issue still persist

Code	`9996`
Source	SDK
Root Cause	Unexpected error occur from payment server side. Possible that payment server does not response data to mobile app
Resolution	Relaunch application and retry action Inform server support if issue still persist

Code	`9997`
Source	SDK
Root Cause	Either reader or card is accidentally or purposely being loose connection/disconnected from phone
Resolution	Ensure card is inserted properly

Code	`9998`
Source	SDK
Root Cause	Invalid hash value field return from payment server. Need to debug via payment log
Resolution	Retry action Inform server support if issue still persist

Code	`9999`
Source	SDK
Root Cause	Invalid session value field return from payment server. Need to debug via payment log
Resolution	Retry action Inform server support if issue still persist

Server Error Codes

Init Error

Code	`2001`
Source	SDK
Root Cause	Initialization fault
Resolution	This error code is obsoleted, if indeed receive this error code, pls consult IT

Code	`2002`
Source	SDK
Root Cause	Device's session has expired, possible cause include server restart (manually triggered by dev)
Resolution	Perform re-login

Code	`2012`
Source	SDK
Root Cause	Mobile user is trying to access in invalid page in sales history
Resolution	Please refresh the page

Application Staff

Code	`3011`
Source	SDK
Root Cause	Mobile user account is blocked/ suspended. User needs to reinstate the account via bank portal or merchant portal
Resolution	Reinstate mobile user account via bank portal or merchant portal

Code	`3012`
Source	SDK
Root Cause	Rare scenario: VOID or Settle buttons are disabled if user doesn't have permission but just in case, we prepare an error message if there is any logic error in frontend OR user permission has been revoked 'after' successful L2 login
Resolution	Enable void payment or settle credit for this user via bank portal Void transaction via merchant portal

Code	`3013`
Source	SDK
Root Cause	Merchant account has been suspended. User need to reactivate account via bank portal to accept transaction
Resolution	Reinstate mobile user account if required

Code	`3014`
Source	SDK
Root Cause	Merchant account has been terminated
Resolution	Check with merchant PIC if account has not been active for the past three months after suspended and reactivate it Check with merchant PIC if account has been deleted or removed from the system and reactivate it

Application Reader

Code	`3020`
Source	SDK
Root Cause	Merchant's phone/device does not match
Resolution	This error code is obsoleted, if indeed receive this error code, pls consult IT

Code	`3021`
Source	SDK
Root Cause	Reader not belongs to Bank
Resolution	This error code is obsoleted, if indeed receive this error code, pls consult IT

Code	`3022`
Source	SDK
Root Cause	This error code is obsoleted, if indeed receive this error code, please consult IT
Resolution	This error code is obsoleted, if indeed receive this error code, pls consult IT

Code	`3023`
Source	SDK
Root Cause	Phone ID sent from mobile apps is not the same as per registered
Resolution	Check if UDID is sent to server via app

Code	`3029`
Source	SDK
Root Cause	-
Resolution	Perform registration action type via 3rd party app

Code	`3030`
Source	SDK
Root Cause	Mobile user attempts to login using a reader that doesn't belong to the company/merchant that the current mobile user is associated with
Resolution	Check if reader serial number is registered to merchant account Register reader to associated merchant if found not registered

Code	`3031`
Source	SDK
Root Cause	Reader suspended from portal
Resolution	Please reinstate the reader Please switch to a different reader which is active and registered under the same MID

Code	`3032`
Source	SDK
Root Cause	Key injection is not performed for the current reader that mobile user is using. Suggest to redo key injection with security team
Resolution	Replace new reader

Code	`3033`
Source	SDK
Root Cause	Key injection failed
Resolution	Replace new reader

Application Error

Code	`5009`
Source	SDK
Root Cause	User tries to login into key injection app using an invalid user id. The login information associated with this terminal is not valid. The Android device should be disassociated from the merchant and the unit re-registered
Resolution	Ensure mobile user role can perform admin login Please use the correct app with the correct app identifier Redo the key injection for this app

Code	`5010`
Source	SDK
Root Cause	Invalid user login or mobile user, or mobile user or company has been suspended
Resolution	Check if entered user ID is valid Check if User ID status is Active Check if merchant status is Active Check if parent company status is Active Check if login user ID match with app/project

Code	`5011`
Source	SDK
Root Cause	Mobile user enters an invalid PIN
Resolution	Enter exact 6 digit of User PIN

Code	`5012`
Source	SDK
Root Cause	User cannot re-use any of the last 5 PIN that was used before
Resolution	Use a new PIN that has not been used for the previous 5 times

Code	`5013`
Source	SDK
Root Cause	Activation fails. Please check activation code
Resolution	Make sure the activation code is correct and has not expired

Code	`5014`
Source	SDK
Root Cause	Last attempt for user to login before mPOS suspends the mobile user
Resolution	Ensure entered User ID and User PIN are valid. Last attempt to enter correct User ID and User PIN before account is suspended Alternatively, user can reset PIN to retrieve credentials

Code	`5015`
Source	SDK
Root Cause	New PIN is vulnerable. It is sequential, repetitive or commonly-used
Resolution	Ensure new PIN is not within the list of vulnerable PINS

Code	`5016`
Source	SDK
Root Cause	First Time Activation not performed
Resolution	Please perform First Time Activation

Code	`5017`
Source	SDK
Root Cause	Entered invalid business registration number for first time registration
Resolution	Check if enter BRN match as per registration via bank portal

Code	`5018`
Source	SDK
Root Cause	Entered invalid email address for first time activation
Resolution	Check if enter email address match as per registration via bank portal

Code	`5019`
Source	SDK
Root Cause	User ID is activated
Resolution	User ID has been activated via first time activation, please proceed with normal activation Enter User ID and temp User PIN to proceed

Code	`5020`
Source	SDK
Root Cause	There is a newer version of the mpos app in appstore or Google Play. User will be redirected to the correct appstore or Google Play after 'confirmation'
Resolution	Download latest update to proceed

Code	`5021`
Source	SDK
Root Cause	(Not specified)
Resolution	User has an active PIN reset activity, perform account reactivation with temp User PIN

Code	`5023`
Source	SDK
Root Cause	MCCS Blocked
Resolution	MCCS must be enabled to perform MyDebit transaction Proceed with a non-Mydebit transaction

Code	`5024`
Source	SDK
Root Cause	User account is currently logged in on another device. User will hit session expire on the other device once confirm switch device
Resolution	New login session is detected, advice user to proceed with confirm switch device to continue

Code	`5025`
Source	SDK
Root Cause	Login expired by new device
Resolution	New login session is detected, user will be logged out of existing device. Continue in new logged in device or relogin into existing device

Code	`5026`
Source	SDK
Root Cause	(Not specified)
Resolution	User is allowed to skip or update to new version

Mobile Error

Code	`5110`
Source	SDK
Root Cause	This is a general error indicating the transaction cannot continue and the user should be instructed to try again
Resolution	Request user to retry transaction Request user to retry transaction with another card If issue persists, contact L2 to troubleshoot

Code	`5111`
Source	SDK
Root Cause	Total monthly transaction limit is exceeded. Bank may either increase the limit or disable the checking (default to maximum value)
Resolution	Check if user's monthly transaction limit has exceeded as per configuration Contact support to consult bank/MSU to increase limit

Code	`5112`
Source	SDK
Root Cause	Total per transaction limit is exceeded. Bank may either increase the per transaction limit or disable the checking
Resolution	Check if user's transaction limit per transaction has exceeded as per configuration Contact support to consult bank/MSU to increase limit

Code	`5113`
Source	SDK
Root Cause	User entered an invalid phone number. Phone number is not between 10 to 11 digit
Resolution	Ensure user entered a valid mobile number format Format should be between 10 - 11 digits

Code	`5114`
Source	SDK
Root Cause	Invalid email address format
Resolution	Ensure user entered a valid email address format (E.g. xxx@xxx.xxx)

Code	`5115`
Source	SDK
Root Cause	Email / SMS service is currently down
Resolution	Contact L2 to check email service availability Contact L2 to check sms service availability

Code	`5116`
Source	SDK
Root Cause	Total daily transaction limit is exceeded. Bank may either increase the limit or disable the checking (default to maximum value)
Resolution	Contact support to consult bank/MSU to increase limit Check if user's daily transaction limit has exceeded as per configuration

Code	`5117`
Source	SDK
Root Cause	Daily transaction count is exceeded. Bank may either increase the limit or disable the checking (Default to maximum value)
Resolution	Contact support to consult bank/MSU to increase limit Check if user's daily transaction count has exceeded as per configuration

Code	`5118`
Source	SDK
Root Cause	Total monthly transaction count is exceeded. Bank may either increase the count or disable the checking (default to maximum value)
Resolution	Contact support to consult bank/MSU to increase limit Check if user's monthly transaction limit has exceeded as per configuration

Code	`5120`
Source	SDK
Root Cause	Batch is not ready. There is either one or more processing/ unsuccessful settlement. Please either settle it manually or wait for the next round of retry else new payment will not be able to proceed
Resolution	Check if user payment type's associated TID batch status Retry settle credit via bank portal/merchant portal Inform server support team if issue still persist

Payment Error

Code	`5555`
Source	SDK
Root Cause	The system is currently down
Resolution	Contact L2 to check for host availability

Code	`7056`
Source	SDK
Root Cause	Transaction amount exceeded limit
Resolution	check transaction limit in portal increase transaction limit if applicable in the event if transaction has reached cap and not able to perform further transaction, have to wait for next day

Code	`8090`
Source	SDK
Root Cause	Host timeout or return empty response
Resolution	Contact L2 to check for host availability

Code	`8091`
Source	SDK
Root Cause	Unable to establish connection to host. Possibly host is down
Resolution	Contact L2 to check for host availability

Code	`8092`
Source	SDK
Root Cause	Connection to host has timeout from payment server side
Resolution	Contact L2 to check for host availability

Code	`8093`
Source	SDK
Root Cause	Batch upload is not successfully completed based on host's response
Resolution	Contact L2 to check for host availability

Code	`8094`
Source	SDK
Root Cause	Unable to decrypt host response
Resolution	Contact L2 to check for host availability

Code	`8095`
Source	SDK
Root Cause	Unable to receive any response from host (Host communication using API)
Resolution	Contact L2 to check for host availability

Code	`8096`
Source	SDK
Root Cause	Host returns 404 not found (Host communication using API)
Resolution	Contact L2 to check for host availability

Code	`8101`
Source	SDK
Root Cause	Amount is not populated/null in data sent by mobile (SDK only)
Resolution	Enter amount other than 0 If user has entered amount other than 0 but issue persists, contact mobile support team

Code	`8102`
Source	SDK
Root Cause	Reader unable to read magstripe track2 data. Magstripe data was invalid. Either the card or the reader was faulty. Test with a different magstripe card to determine root cause
Resolution	Try with another card Replace new reader if issue still persist

Code	`8103`
Source	SDK
Root Cause	Magstripe is not allowed for this card. Please use chip transaction instead
Resolution	Try with another interface (If perform magstripe trx, advice user to try with contact) Try with another card

Code	`8104`
Source	SDK
Root Cause	KSN is null in data sent by mobile
Resolution	Inform server support team

Code	`14111`
Source	SDK
Root Cause	Exceeded void window of 25 mins
Resolution	Expected not allowed to void after transaction has been approved for 25 mins Advice to perform refund action via mobile app to refund transaction

BIN range Error

Code	`8201`
Source	SDK
Root Cause	App/terminal when ask blocked bin from server, but didnt provide revision field
Resolution	Check if app/terminal provided revision number (mandatory)

Code	`8202`
Source	SDK
Root Cause	Revision received is less than 0 or higher than latest file revision
Resolution	Check if app/terminal provided accurate revision number

Code	`8203`
Source	SDK
Root Cause	No bin file found in system
Resolution	Bin data is not registered/ does not support the following scheme. Please use another card

Pre-Auth

Code	`8204`
Source	SDK
Root Cause	Transaction amount exceed
Resolution	Check preauth amount via portal Preauth sales completion amount must be equal or below approved preauth amount

Code	`8205`
Source	SDK
Root Cause	The transaction cannot be found, for example when performing void
Resolution	Check if transaction reference number is valid Check if approval code for preauth sales completion is valid/match

Code	`8206`
Source	SDK
Root Cause	Duplicate transaction reference no, All reference no should be unique
Resolution	Check if transaction reference number is unique Enter/pass in valid and unique reference number for each transaction

Invalid card, Card application not supported

Code	`8207`
Source	SDK
Root Cause	Error invalid merchant data
Resolution	Merchant's entered merchant data is invalid, not allowed to enter spacing Merchant's entered merchant data has exceeded max limit. Only allowed to enter max 20 alphanumeric characters for EU and max 30 alphanumeric characters for NA

Code	`14010`
Source	SDK
Root Cause	Your SSO token has been revoked
Resolution	Re-enable SSO for MUID

Code	`14011`
Source	SDK
Root Cause	You are not permitted to perform SSO operations
Resolution	Check if MUID has enabled with SSO Enable SSO for MUID if required

Code	`14012`
Source	SDK
Root Cause	Invalid SSO token
Resolution	Relogin to get new SSO token Contact server support team if issue still persist

Code	`14013`
Source	SDK
Root Cause	You are not permitted to perform any operations
Resolution	Check if MUID enabled for manual SSO login

Code	`14014`
Source	SDK
Root Cause	Please perform activation on PlugNPay
Resolution	Please complete the user activation to proceed

Code	`14015`
Source	SDK
Root Cause	Invalid Company SSO Identifier
Resolution	Check if SSO in enabled for the company Check if the SSO company identifier is valid and match in bank portal or merchant portal Enable SSO for the company if needed

Code	`14017`
Source	SDK
Root Cause	Void denied. This transaction has been voided or pending void
Resolution	Restart terminal and check transaction history again

Code	`14100`
Source	SDK
Root Cause	User does not have reset pin session
Resolution	Perform reset user PIN

Code	`14101`
Source	SDK
Root Cause	Company country and Mobile User Country not match
Resolution	Check on the developer ID used for the mobile user's country

OTP Error Messages

Code	`14110`
Source	SDK
Root Cause	The activation code is expired. Please request for a new activation code.
Resolution	Request new activation code

Code	`14111`
Source	SDK
Root Cause	Invalid OTP. Please fill in with correct Authentication Code.
Resolution	Input correct OTP received by merchant

Code	`14112`
Source	SDK
Root Cause	OTP has expired. Please click on "Resend OTP" for your new Authentication Code.
Resolution	Request new OTP

Activation Code Expired

Code	`15001`
Source	SDK
Root Cause	Upload ID exist with a CONFIRMED status
Resolution	This error code is obsoleted, if indeed receive this error code, please consult IT

Code	`15002`
Source	SDK
Root Cause	Upload ID exist with an unknown status
Resolution	This error code is obsoleted, if indeed receive this error code, please consult IT

Code	`15003`
Source	SDK
Root Cause	Error total comparison
Resolution	This error code is obsoleted, if indeed receive this error code, please consult IT

Code	`15004`
Source	SDK
Root Cause	Offline unknown status
Resolution	This error code is obsoleted, if indeed receive this error code, please consult IT

Code	`15005`
Source	SDK
Root Cause	Transaction auth type unknown
Resolution	This error code is obsoleted, if indeed receive this error code, please consult IT

Code	`15006`
Source	SDK
Root Cause	Transaction status unknown
Resolution	This error code is obsoleted, if indeed receive this error code, please consult IT

Code	`15007`
Source	SDK
Root Cause	Error processing contactless transaction's transaction date
Resolution	This error code is obsoleted, if indeed receive this error code, please consult IT

Code	`15008`
Source	SDK
Root Cause	Error processing contactless transaction's transaction time
Resolution	Contact support to assist checking on transaction time value return by host.

Code	`15009`
Source	SDK
Root Cause	Transaction transaction null
Resolution	Contact server IT to assist checking on transaction time value return by host.

Code	`15010`
Source	SDK
Root Cause	Reader serial no., total transaction count/amount cannot be null
Resolution	Contact server IT to assist checking on transaction time value return by host.

Code	`15011`
Source	SDK
Root Cause	MID does not exist
Resolution	Check if associated MUID has active MID Enable MID if required

Code	`15012`
Source	SDK
Root Cause	No TID available assigned to the MID
Resolution	Check if TID is assigned for this mobile user account Contact MSU if mobile user account has no assigned TID

Code	`15013`
Source	SDK
Root Cause	Track2 cannot be null
Resolution	Retry with existing card Try with another card

Reporting Error

Code	`16001`
Source	SDK
Root Cause	Detected location of transaction is out of allowed boundaries.
Resolution	Retry the transaction again, if issue persist, contact IT support Download PDF receipt via portal

Code	`16002`
Source	SDK
Root Cause	Transaction not exist
Resolution	Check if other transactions cannot sent receipt, if issue persist, contact IT support

Code	`16003`
Source	SDK
Root Cause	Receipt not exist
Resolution	Check if other transactions has the ability to send receipt. If issue persists, contact server support Remarks: FP QR does not support receipt

Code	`16004`
Source	SDK
Root Cause	QR token expired
Resolution	Press back and restart payment process Close app and restart app

Geofencing Error - Recoverable

Code	`17001`
Source	SDK
Root Cause	(Not specified)
Resolution	Check if there is GPS connectivity in the area Check if the location is within the geofencing area (refer to project)

Code	`17002`
Source	SDK
Root Cause	(Not specified)
Resolution	Stand at an area that has GPS coverage Make sure location is within geofenced area (refer to project) If problem persist, contact server IT for investigation

Code	`17003`
Source	SDK
Root Cause	(Not specified)
Resolution	Close application, turn off GPS, restart device Turn on GPS and try again If issue persists, contact server IT for investigation

Geofencing Error - Non recoverable

Code	`17004`
Source	SDK
Root Cause	(Not specified)
Resolution	Ensure app is used within application geofenced country (refer to project)

Code	`17005`
Source	SDK
Root Cause	Error during initialization
Resolution	Stand at an area that has GPS coverage Make sure location is within geofenced area (refer to project)

Code	`17006`
Source	SDK
Root Cause	There are still pending unresolved transaction
Resolution	This error code is obsoleted, if indeed receive this error code, pls consult IT

Code	`17007`
Source	SDK
Root Cause	Country Code passed in the API is not in uppercase
Resolution	Ensure that country code is in uppercase.

Code	`18000`
Source	SDK
Root Cause	Inactive service code
Resolution	Check what transaction perform by this user, then verify if user has been enable to perform such transaction type (eg: Alipay QR)

Code	`18001`
Source	SDK
Root Cause	Unathorized service access
Resolution	This error code is obsoleted, if indeed receive this error code, pls consult IT

Code	`18002`
Source	SDK
Root Cause	(Not specified)
Resolution	This error code is obsoleted, if indeed receive this error code, pls consult IT

Code	`18003`
Source	SDK
Root Cause	Unified payment not supported
Resolution	This error code is obsoleted, if indeed receive this error code, pls consult IT

Code	`18004`
Source	SDK
Root Cause	Fasstap reader acceptance not enabled.
Resolution	Check if Fasstap reader acceptance is enabled If Fasstap reader acceptance is not enabled, enable it via bank portal

Code	`18005`
Source	SDK
Root Cause	Lighthouse reader acceptance not enabled
Resolution	Check if Lighthouse reader accpetance is enabled If Lighthouse reader acceptance is not enabled, enable it via bank portal

Code	`18006`
Source	SDK
Root Cause	K9 reader acceptance not enabled
Resolution	Check if k9 reader acceptance is enabled If k9 reader acceptance is not enabled, enable it via bank portal

Code	`19001`
Source	SDK
Root Cause	Please contact Soft Space if this problem persists (SPoC caPEM validation error)
Resolution	Retry the transaction again, if issue persist, contact server IT

SDK Integration

Start building your Fasstap™ integration.

Transaction Events