Mobile Money V100R003 Error Codes Reference 01

Mobile Money
V100R003
Error Codes Reference
Issue 01
Date 2017-07-28
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2017. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 01 (2017-07-28) Huawei Proprietary and Confidential i

Copyright © Huawei
Technologies Co., Ltd.
Mobile Money
Error Codes Reference About This Document
About This Document
Author
Prepared by Xu Xian Date 2017-06-22
Reviewed by Jin Jing Date 2017-06-23
Tested by Liu Chengfang Date 2017-06-23
Approved by Li Shaoshao Date 2017-07-28
Purpose
This document provides guides to get the reference information of the Mobile Money System
error codes.
Intended Audience
This document is intended for:
 Technical support engineers
 Maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates an imminently hazardous situation which, if not

avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.
Issue 01 (2017-07-28) Huawei Proprietary and Confidential ii

Copyright © Huawei
Mobile Money
Symbol Description

avoided, may result in minor or moderate injury.

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to
personal injury.
Calls attention to important information, best practices
and tips.
NOTE is used to address information not related to
personal injury, equipment damage, and environment
deterioration.
Privacy Notice
The Privacy Notice describes policies used by the Mobile Money system to protect user data
and privacy data. However, the Mobile Money system may not be able to solves all doubts on
data processing. Therefore, read this Privacy Notice carefully and process user data and
privacy data promptly and properly.
Some functions provided by the product collect certain user data, such as the user number,
user name, age, bank account, and transaction details. You are obligated to take considerable
measures, in compliance with the laws of the countries concerned and the user privacy
policies of your company, to ensure that the personal data of users is fully protected. In the
Mobile Money system, the following functions and processing modes may involve user data:
The Mobile Money system has strict control on the access permission of the operating system, database,
and foreground to ensure that user privacy data is properly protected.
 Identity management function
When a carrier operator, organization, organization operator, or user is registered with
the Mobile Money system, information such as the email address and mobile number
needs to be provided for receiving system information. In addition, other user data such
as the contact, bank account, name, and age.
All user data is stored in the database of the Mobile Money system. The user password,
PIN, and bank account are stored in encrypted mode. After a user stays in the Closed
state for a period of time (six months by default, which is configurable), data of the user
is migrated to the historical data archive database. Only maintenance operators with
related permission can query data in the historical data archive database.
 Transaction details recording function
To calculate fees generated when users use services, the Mobile Money system provides
the function of recording transaction details, including the transaction SN, status,
initiation time, initiator, accumulator, and account entry. The transaction details are
stored in the database.
Issue 01 (2017-07-28) Huawei Proprietary and Confidential iii

Copyright © Huawei
Mobile Money
After a transaction is completed for a period of time (six months by default, which is
configurable), the transaction details record is migrated to the historical data archive
database. Only maintenance operators with related permission can query data in the
historical data archive database.
 Data backup function
To avoid data change by mistake, which can result in system faults or user data faults,
the product prompts carriers to back up data periodically. The backup data may involve
information about partners and end users. For example, data in the Oracle database may
involve information such as customer numbers and transaction records. The backup data
can be used only for data recovery. For details about the backup data storage time, see
backup policies in the Backup and Restore. Expired backup data can be automatically
deleted.
 Log function
To help maintenance personnel understand the system running status and troubleshoot
faults quickly, the Mobile Money system provides the log recording function. The logs
record information such as the transaction amount and identities of both transaction
parties. The Mobile Money system stores log files on the server. The log server access
permission is strictly controlled. The Mobile Money system provides anonymization
tools. If log files are transferred out of the customer's network, anonymization tools
should be used for processing the log files to ensure that security-sensitive data such as
the name, gender, age, birthday, password, phone number, and account balance of a user
is not collected. The Mobile Money system cannot delete log files copied to a local disk.
After using the log files copied to a local disk, users need to process the log files
properly.
 Fault information collection function
To find the fault reasons, necessary service logs and transaction details may need to be
collected, and the logs may contain user information such as the user number and bank
account. The Mobile Money system provides anonymization tools to ensure the safety of
involved user information. After troubleshooting, maintenance personnel needs to delete
the collected information promptly.
Huawei support engineers can perform maintenance operations only after being authorized by
the customer and provide related information for the customer actively, and are forbidden to
perform any operations that are not approved by the customer. To transfer fault locating data
out of the customer's network, Huawei support engineers must obtain the written
authorization of the customer and follow the local laws to perform the operation. After
troubleshooting, involved user data must be safely deleted under the supervision of the
customer.
Change History
Changes between document versions are cumulative. Therefore, the latest document issue
contains all changes made in previous issues.
Issue 01 (2017-07-28) Huawei Proprietary and Confidential iv

Copyright © Huawei
Mobile Money
Issue 01 (2017-07-28)
This is the first issue of the document. It is released for release R4 IT1 of the software.
Issue 01 (2017-07-28) Huawei Proprietary and Confidential v

Copyright © Huawei
Mobile Money
Error Codes Reference 1 Error Code Description
1 Error Code Description
About This Chapter

The system can generate error codes based on service processing results.
1.1 Categories
1.2 View Method
1.1 Categories
Error codes are categorized as follows:
 System error code
A system error code indicates a system or internal error. End uses (such as customer,
operator, and organization) do not need to know the details of such an error. One
notification type can be configured for all system errors.
 Web notification error code
A web notification error code indicates an error to be displayed on the graphical user
interface (GUI). No notification type needs to be configured for such an error, because
the error code description will be displayed on the GUI. As these messages are shown to
operators, they can be configured with lower priorities.
 USSD notification error code
A USSD notification error code indicates an error message that will be shown in a USSD
menu. This type of error code does not need to be linked to a notification type. The
system will display the description message for the error code.
 Business error code
A business error code indicates an error code for which a notification type must be
configured. The error message will be sent to end users. If we do not link a notification
type to the error code, the system will send the error code description message
predefined in the system to end users.
 Common error code
Issue 01 (2017-07-28) Huawei Proprietary and Confidential 1

Copyright © Huawei
Mobile Money
Error Codes Reference 1 Error Code Description
A common error code is used only for error code *. It needs to be linked to an
STAND_FAILURE_MESSAGE notification type so that an error message will be sent if
an error notification configuration is missing.
1.2 View Method

If the scenario of an error code occurs, the system generates the corresponding error
information. You can view the error information in the following ways:
 Portal
If the scenario of an error code occurs when an operator performs an operation on a
portal, the system displays the error information on the portal.
 Error logs
You can also view error information in error logs by searching for keywords or error
codes.
The following uses the BCS module as an example to describe how to view error information
in error logs.
Log in to the server as the bcs user.
Step 1 Enter the $HOME/log/debug directory.
Step 2 Open the bcs_debug.log file and search for the ERROR keyword.
----End

Copyright © Huawei
Mobile Money
Error Codes Reference 2 AG Error Codes
2 AG Error Codes
About This Chapter

The error codes contain the following units:
2.1 AG45000
2.2 AG45001
2.3 AG45006
2.4 AG45008
2.5 AG45010
2.6 AG45011
2.7 AG45016
2.8 AG45018
2.9 AG45019
2.10 AG45020
2.11 AG45021
2.12 AG45022
2.13 AG45023
2.14 AG45024
2.15 AG45025
2.16 AG45028
2.17 AG45030
2.18 AG45031
2.19 AG45032
2.20 AG45033

Copyright © Huawei
Mobile Money
2.21 AG45036
2.22 AG45039
2.23 AG45040
2.24 AG45041
2.25 AG45042
2.26 AG45043
2.27 AG45044
2.28 AG45045
2.29 AG45101
2.30 AG45300
2.31 AG45301
2.32 AG45302
2.33 AG45303
2.34 AG45304
2.35 AG45305
2.36 AG45306
2.37 AG45307
2.38 AG45308
2.39 AG45309
2.40 AG45311
2.41 AG45312
2.42 AG45313
2.43 AG45314
2.44 AG45315
2.45 AG45500
2.46 AG45501
2.47 AG45502
2.48 AG45503
2.49 AG45504
2.50 AG45505
2.51 AG45506
2.52 AG45507
2.53 AG45514

Copyright © Huawei
Mobile Money
2.54 AG45515
2.55 AG45516
2.56 AG45700
2.57 AG45701
2.58 AG45702
2.59 AG45703
2.60 AG45704
2.61 AG45705
2.62 AG45900
2.63 AG45901
2.64 AG45902
2.65 AG45903
2.66 AG45904
2.67 AG45905
2.68 AG45906
2.69 AG49000
2.70 AG49003
2.71 AG49004
2.72 AG49005
2.73 AG49006
2.74 AG49007
2.75 AG49008
2.76 AG49009
2.77 AG49010
2.78 AG49011
2.79 AG49012
2.80 AG49013
2.81 AG49014
2.82 AG49015
2.83 AG49016
2.84 AG49017
2.85 AG49018
2.86 AG49019

Copyright © Huawei
Mobile Money
2.87 AG49020
2.88 AG49021
2.89 AG_EXT1000
2.90 AG_EXT1001
2.91 NC40001
2.92 NC40005
2.93 NC40008
2.94 NC40009
2.95 NC40010
2.96 NC40011
2.97 NC40012
2.98 NC40013
2.99 NC40700
2.100 NC40907
2.101 NC41001
2.102 NC41007
2.103 NC41100
2.104 NC41101
2.105 NC41102
2.106 NC41300
2.107 NC41301
2.108 UMC60503
2.109 UMC60504
2.110 UMC60505
2.111 UMC60506
2.112 UMC60507
2.113 UMC60508
2.114 UMC60509
2.115 UMC60510
2.116 UMC60512
2.117 UMC60513
2.118 UMC60514
2.119 UMC60515

Copyright © Huawei
Mobile Money
2.120 UMC60516
2.121 UMC60517
2.122 UMC60518
2.123 UMC60519
2.124 UMC60520
2.125 UMC60521
2.126 UMC60522
2.127 UMC60523
2.128 UMC60524
2.129 UMC60525
2.130 UMC60528
2.131 UMC60529
2.132 UMC60530
2.133 UMC60531
2.134 UMC60532
2.135 UMC60533
2.136 UMC60534
2.137 UMC65001
2.1 AG45000
Description
The access message is empty.
Scenario
The body of the access request message is empty, or the message is in an incorrect format.
Access Channel
API, STK, USSD
Possible Causes
 The message for accessing the access gateway (AG) is empty.
 The message for accessing the AG is in an incorrect format.
Procedure
Modify the access message based on the interface documents for various access channels.

Copyright © Huawei
Mobile Money
2.2 AG45001
Description
The system does not support the requested service.
Scenario
The command word or service type specified in the request message is incorrect.
Access Channel
API, STK, USSD
Possible Causes
 The command word in the request message is incorrect.
 The service type in the request message is incorrect.
Procedure
Verify the command word or service type in the request message in the AG access message
file.
2.3 AG45006
Description
Failed to parse the message.
Scenario
The request message is invalid.
Access Channel
API, STK, USSD
Possible Causes
The request message is invalid.
Procedure
Verify the request message in the AG access message file.

Copyright © Huawei
Mobile Money
2.4 AG45008
Description
No parameter delimiter is found.
Scenario
The parameter delimiter does not exist in the USSD CMD access request message.
Access Channel
USSD
Possible Causes
The parameter delimiter in the USSD CMD access message does not exist.
Procedure
Correct the message content.
2.5 AG45010
Description
Call service failed.
Scenario
After the properly receiving and processing outbound access messages of background NEs,
the AG attempts to send the message to a third-party system. However, invoking third-party
services fails.
Access Channel
API, STK, USSD
Possible Causes
AG internal service unavailable.
Procedure
1. Log in to the AG host as an AG user.
2. Follow instructions related to third-party service addresses in the commissioning guide
to check whether third-party service address configurations are correct.
If no, modify the configurations and restart the AG.
If yes, send log/debug/ag_debug.log for the AG to Huawei engineers for fault diagnosis.

Copyright © Huawei
Mobile Money
2.6 AG45011
Description
AG service does not exist.
Scenario
After access messages are properly parsed, a correct ServiceAdapter instantiation object is not
found to be forwarded.
Access Channel
API, STK, USSD
Possible Causes
 AG runs abnormally.
 AG's service routing configuration error.
Procedure
2. Check whether the cps-ag.servicerouter.config.xml file exists in /config/release and
whether the permission for the file is correct.
If the file does not exist, AG deployment may be abnormal. Contact Huawei engineers.
If the file exists but the permission for the file is incorrect, grant the correct permission
for the file and restart the AG.
If the file exists and the permission for the file is correct, send the file and
log/debug/ag_debug.log for the AG to Huawei engineers for fault diagnosis.
2.7 AG45016
Description
Call remote procedure call protocol (RPC) service failed.
Scenario
After properly receiving and processing access messages, the AG attempts to forward the
messages to background NEs. However, invoking an RPC service fails.
Access Channel
API, STK, USSD
Possible Causes
Mobile Money internal service unavailable.

Copyright © Huawei
Mobile Money
Procedure
2. Check whether RegIP and RegPort are set to the registration center Internet Protocol (IP)
address and port respectively in /config/global.env.xml.
If no, correct the values of RegIP and RegPort and restart the AG.
If yes, the network may be abnormal between the AG and the registration center. Resolve
the network abnormality.
3. If the fault persists, send log/debug/ag_debug.log for the AG to Huawei engineers for
fault diagnosis.
2.8 AG45018
Description
Access gateway (AG) internal error.
Scenario
Request processing fails due to internal causes, such as AG's program bugs or background
data configuration inconsistency.
Access Channel
API, STK, USSD
Possible Causes
 AG and redis server disconnected.
 AG decrypted data from unified configuration center (UCC) failed for incorrect private
key.
Procedure
1. Check the redis server's status.
2. Check the configuration file in AG for redis connection.
3. Ensure ag and ucc use the same private key.
2.9 AG45019
Description
The initiator has no permission to access the service.
Scenario
Third-party systems that access the system through API have no permission to use specified
services.

Copyright © Huawei
Mobile Money
Access Channel
API
Possible Causes
The third party that accesses the system through an API has no permission to request for the
service.
Procedure
1. Log in to the service provider (SP) Portal as an SP operator.
2. Choose My Functions > Operational Configuration > API > API Caller
Management.
3. Find the third party by the third party ID, and edit the Support All Commands
configuration item for the third party.
− If Support All Commands is set to Yes, the third party has the permission to access
all services.
− If Support All Commands is set to No, you need to add service permissions from
the Command List to the Assigned Commands column.
2.10 AG45020
Description
Database error.
Scenario
An error occurs when the AG accesses the database. For example, data is required to be
recorded in the service serial table when the AG accesses the database through API and STK
message logs are required to be recorded when the AG accesses the database through STK.
Access Channel
API, STK
Possible Causes
While the request message from API is saved to database, error occurred.
Procedure
Check the database connection.

Copyright © Huawei
Mobile Money
2.11 AG45021
Description
Requests with the same OriginatorConversationID exist within a cycle.
Scenario
A duplicate third-party service ID exists.
Access Channel
API
Possible Causes
A duplicate third-party service ID exists.
Procedure
Disable the duplicate check function for messages sent using the API channel, or prevent
requests with the same OriginatorConversationID exist within a cycle.
2.12 AG45022
Description
IP address verification failed.
Scenario
When the API Caller initiates transactions through API, the API Caller's IP address is in the
blacklist or not in the white list.
Access Channel
API
Possible Causes
The API Caller's IP address is in blacklist or not in the white list.
Procedure
1. Log in to the SP Portal as an SP operator.
2. Choose My Functions > Operational Configuration > System Parameter > Generic
API.
3. Set Limit Rule for IP Address to Yes.
4. Click API Caller Management.

Copyright © Huawei
Mobile Money
5. Edit the third party, remove the IP address of the API caller from the blacklist of the
third party, or add the IP address to the white list of the third party.
2.13 AG45023
Description
The parameters are invalid.
Scenario
Verification on parameters contained in access or outbound access request messages fails. For
example, mandatory parameters are missing or parameter values are invalid.
Access Channel
API, STK, USSD
Possible Causes
The parameter values in the request message are invalid.
Procedure
Modify parameter values based on the interface documents for various access channels.
2.14 AG45024
Description
The message format is incorrect.
Scenario
Messages accessed through each channel are in an incorrect format.
Access Channel
API, STK, USSD
Possible Causes
The message format is incorrect.
Procedure
Modify the request message based on the interface documents for various access channels.

Copyright © Huawei
Mobile Money
2.15 AG45025
Description
The third party does not exist.
Scenario
When the API Caller initiates a transaction through API, the third-party ID specified in the
API packet does not exist in the system.
Access Channel
API
Possible Causes
The third-party ID specified in the API packet does not exist.
Procedure
2. Choose My Functions > Operational Configuration > API > API Caller
Management.
3. Add the third party.
2.16 AG45028
Description
User name or password error.
Scenario
When the API Caller initiates a transaction through API, verification on the caller password
specified in the API packet fails.
Access Channel
API
Possible Causes
User name or password error.
Procedure
Use correct user name and password.

Copyright © Huawei
Mobile Money
2.17 AG45030
Description
System overloaded.
Scenario
The current system has reached the maximum capacity to process requests.
Access Channel
API, STK, USSD
Possible Causes
The current system has reached the maximum load capacity to process requests.
Procedure
1. Log in to the SP portal or Admin portal. Choose Access Gateway Configuration or API
Gateway Configuration in My Functions > Operational Support > Flow Control
Policy.
2. Check whether thresholds are small.
If thresholds are small, adjust them based on the deployment plan and check whether the
fault persists.
3. If the fault persists, send log/debug/ag_debug.log for the AG to Huawei engineers for
fault diagnosis.
2.18 AG45031
Description
The message is already sent and cannot be sent again.
Scenario
The API result message destined for a third-party system has been sent to the third-party
system and does not need to be sent again.
Access Channel
API
Possible Causes
The message is already sent and cannot be sent again.

Copyright © Huawei
Mobile Money
Procedure
The message is already successfully sent. Do not send it again.
2.19 AG45032
Description
The STK message times out.
Scenario
The message packets to be assembled into an STK request are not successfully sent in a
specified time period.
Access Channel
STK
Possible Causes
The message packets to be assembled into an STK request are not successfully sent in a
specified time period.
Procedure
Confirm the largest interval between message segments of a big request with the carrier.
Instruct Huawei engineers to modify preconfigured data based on the confirmation result.
2.20 AG45033
Description
A time-out error occurred when an external service is invoked.
Scenario
Invoking a third-party service, for example, invoking a third-party WebService interface
during pay bill and buy airtime services, times out.
Access Channel
API
Possible Causes
A time-out error occurred when an external service is invoked.

Copyright © Huawei
Mobile Money
Procedure
Send the service request again.
2.21 AG45036
Description
The organization has no key.
Scenario
A transaction is initiated through API. When the value of KeyOwner is 2, the key of the
organization to which the organization operator belongs is used to encrypt sensitive data in the
packet. However, no key is configured for the organization in the system.
Access Channel
API
Possible Causes
The organization has no key.
Procedure
2. Choose My Functions > Operational Configuration > API > API Initiator Key
Management.
3. Configure a key for the organization.
2.22 AG45039
Description
Message-oriented middleware (MOM) connection failed.
Scenario
The AG declines requests because connection between the AG and MOM is terminated.
Access Channel
API, STK, USSD
Possible Causes
The connection between the AG and MOM is terminated or fails to be established.

Copyright © Huawei
Mobile Money
Procedure
1. Verify whether the address of the remigration center is correctly configured in the AG.
2. Verify whether the MOM address is correctly configured in the remigration center.
3. Verify whether the network between the AG and MOM works properly.
2.23 AG45040
Description
The system is being maintained.
Scenario
The AG declines the request because system maintenance is enabled.
Access Channel
API, STK, USSD
Possible Causes
The AG declines the request because the system maintenance flag is enabled.
Procedure
The following operations must be performed under instructions from a Huawei engineer:
Verify that the system maintenance is complete and change the system maintenance flag false.
2.24 AG45041
Description
The system is overloaded, resulting in abnormal response latency.
Scenario
The BCS is overloaded and the number of messages to be processed in the MOM has reached
the lightweight overload threshold.
Access Channel
API, STK, USSD
Possible Causes
The BCS is overloaded and the number of messages to be processed in the MOM has reached
the threshold.

Copyright © Huawei
Mobile Money
Procedure
1. Log in to the BCS host as the bcs user.
2. Run the ps -x command to check whether the BCS process is started.
− If the BCS process is not started, restart the BCS.
− If the BCS process is running properly, the BCS may be slow in response, and you
need to wait for the BCS to respond to the current request.
2.25 AG45042
Description
The system is overloaded and cannot process new access requests.
Scenario
The message queue (MQ) is disconnected, or the BCS is overloaded and the number of
messages to be processed in the MOM has reached the lightweight overload threshold.
Access Channel
API, STK, USSD
Possible Causes
The MQ is disconnected, or the BCS is overloaded and the number of messages to be
processed in the MOM has reached the threshold.
Procedure
1. Log in to the MQ host as the mq user.
2. Run the ps -x command to check whether the MQ process is started. If the MQ process is
not started, restart the MQ.
3. Log in to the BCS host as the bcs user.
4. Run the ps -x command to check whether the BCS process is started.
− If the BCS process is not started, restart the BCS.
− If the BCS process is running properly, the BCS may be slow in response, and you
need to wait for the BCS to respond to the current request.
2.26 AG45043
Description
The conditions are not monotonically increasing.

Copyright © Huawei
Mobile Money
Scenario
Service levels (level0-level2) configured on web pages and conditional values are not
monotonically increasing. For example, the condition value of level0 is 1000, but the
condition value of level2 is 500.
Access Channel
System
Possible Causes
Service levels (level0-level2) and conditional values are not monotonically increasing, for
example, the value for level 0 is 10000, but the value for level 1 is 5000.
Procedure
1. Choose My Functions > Operations > Condition Service > Message Queue
Management on the portal.
2. Verify that the service levels (level0-level2) and conditional values are monotonically
increasing.
2.27 AG45044
Description
The service level condition does not exist.
Scenario
An exception occurs when a service level condition is obtained from the local cache.
Access Channel
System
Possible Causes
An access request is sent before the system is fully started.
Procedure
1. The cause may be that the system has not read all data from the cache. Wait for five
minutes and try again.
If the problem disappears, ignore the following steps.
2. If the problem persists, the cause may be that an exception has occurred in the startup
process, and the cache cannot be read. In this case, restart the AG and try again.
If the problem disappears, ignore the following steps.
3. Check whether the UCC subsystem is started.

Copyright © Huawei
Mobile Money
a. Log in to the registration center management page through a Web browser and click
Node Query.
b. Enter UCC in the Zone textbox on the Node Query page and click Query.
c. Check whether the query result contains a record whose App Name is set to
UnifiedConfigCenter. If no, the UCC is not started, and you need to start the UCC.
d. If the UCC is started but the problem persists, contact a Huawei engineer for help.
2.28 AG45045
Description
An encryption or decryption error occurred in the AG.
Scenario
An encryption or decryption error occurred when the AG interacts with the third party.
Access Channel
USSD
Possible Causes
 The kiosk-10001.private and kiosk-master.public configuration files are missing.
 The kiosk-10001.private and kiosk-master.public configuration files are modified.
Procedure
1. Check whether the kiosk-10001.private and kiosk-master.public files exist in the
/config/local/ directory of the AG.
If the files exist, check whether the file sizes are 486 and 596 bytes respectively. If the
file sizes are correct, check whether all kioskId configurations in the
mobilink.shortcode.properties file are the same as the 5-digit numeral configured in
the kiosk-10001.private file.
2. In any of the following scenarios, ask the NDARA for a new encryption and decryption
key, and save the key to the /config/local/ directory:
− The file sizes are correct but encryption and decryption still fail.
− The file sizes are incorrect.
− The files do not exist.
If the kiosk-*****.private (***** indicates a 5-digit numeral) file name provided by
NDARA is changed, all kioskId configurations in the mobilink.shortcode.properties file in the
/config/local/ directory must also be changed to the new 5-digit numeral.

Copyright © Huawei
Mobile Money
2.29 AG45101
Description
Failed to update the STK sequence table.
Scenario
A menu sequence number and user data header (UDH) sequence number are generated during
STK menu sending.
Access Channel
STK
Possible Causes
Failed to update the STK sequence table.
Procedure
Check the database connection.
2.30 AG45300
Description
The {0} parameter is not supported.
The {0} variable indicates the path of the redundant parameter. For example,
Request.Transaction.Parameters.Amount indicates that the Amount parameter in the
Request.Transaction.Parameters path is redundant.
Scenario
An access request message contains a redundant parameter.
Access Channel
API, STK, USSD
Possible Causes
A message for accessing the AG through a channel contains a redundant parameter.
Procedure
Refer to the interface document of the access channel and delete the redundant parameter.

Copyright © Huawei
Mobile Money
2.31 AG45301
Description
The {0} parameter is mandatory.
The {0} variable indicates the path of the missing mandatory parameter. For example,
Request.Transaction.Parameters.Amount indicates that the mandatory parameter Amount in the
Request.Transaction.Parameters path is missing.
Scenario
An access request message lacks a mandatory parameter.
Access Channel
API, STK, USSD
Possible Causes
A message for accessing the AG through a channel lacks a mandatory parameter.
Procedure
Refer to the interface document of the access channel and add the missing mandatory
parameter.
2.32 AG45302
Description
A message for accessing the AG through a channel contains an empty parameter {0}.
The {0} variable indicates the path of the empty mandatory parameter. For example,
Request.Transaction.Parameters.Amount indicates that the mandatory parameter Amount in the
Request.Transaction.Parameters path is empty.
Scenario
A parameter in the access request message is empty.
Access Channel
API, STK, USSD
Possible Causes
A message for accessing the AG through a channel contains an empty parameter.

Copyright © Huawei
Mobile Money
Procedure
Specify a value for the empty parameter based on the prompt information.
2.33 AG45303
Description
The format of parameter {0} is incorrect.
The {0} variable indicates the path of the parameter. For example,
Request.Transaction.Parameters path is in an incorrect format.
Scenario
A parameter in the access request message is in an incorrect format.
Access Channel
API, STK, USSD
Possible Causes
A message for accessing the AG through a channel contains a parameter in an incorrect
format.
Procedure
Refer to the interface document of the access channel and correct the parameter format.
2.34 AG45304
Description
Failed to decrypt the {0} parameter.
The {0} variable indicates the path of the parameter. For example, Request.Identity.Caller.Password
indicates that the Password parameter in the Request.Identity.Caller path cannot be decrypted.
Scenario
An encrypted parameter in the access request message cannot be decrypted.
Access Channel
API, STK

Copyright © Huawei
Mobile Money
Possible Causes
A message for accessing the AG through a channel contains an encrypt parameter that cannot
be decrypted.
Procedure
1. If a request initiated by a third-party initiator through the API channel contains a
parameter that cannot be decrypted, verify whether the key used by the initiator is the
same as the key used to encrypt the parameter.
If a request initiated on a mobile phone through the STK channel contains a parameter
that cannot be decrypted, verify whether the key used by the subscriber identity module
(SIM) card of the mobile phone is the same as the key used to encrypt the parameter.
2. If the keys are inconsistent, change the key and verify that they are consistent.
3. If the keys are consistent, contact a Huawei engineer for help.
2.35 AG45305
Description
Failed to convert the {0} parameter.
The {0} variable indicates the path of the parameter. For example,
Request.Transaction.Parameters path cannot be converted.
Scenario
A parameter in the request message cannot be converted.
Access Channel
API, STK, USSD
Possible Causes
A message for accessing the AG through a channel contains an external parameter which
cannot be converted into an internal parameter.
Procedure
Refer to the interface document of the access channel and modify the parameter format.
2.36 AG45306
Description
The value of the {0} parameter is outside of the valid value range.

Copyright © Huawei
Mobile Money
The {0} variable indicates the path of the parameter. For example, Request.KeyOwner indicates that
the KeyOwner parameter in the Request path is outside of the valid value range.
Scenario
The request message contains a parameter whose value is outside of the valid value range.
Access Channel
API, STK, USSD
Possible Causes
A message for accessing the AG through a channel contains a parameter whose value is
outside of the valid value range.
Procedure
Refer to the interface document of the access channel and modify the parameter to ensure that
the value is inside the valid value range.
2.37 AG45307
Description
The outgoing request is out of the validity period.
Scenario
An outgoing request is out of the validity period.
Access Channel
API
Possible Causes
An outgoing request is out of the validity period.
Procedure
Find the cause why the outgoing request is out of the validity period. For example, check AG
status.

Copyright © Huawei
Mobile Money
2.38 AG45308
Description
The value of the KeyOwner parameter is invalid.
Scenario
The KeyOwner parameter is set to an invalid value in an API request from a third-party
system.
Access Channel
API
Possible Causes
In a third-party request, the KeyOwner parameter is not set to 1 which indicates a third-party
key or 2 which indicates an initiator key.
Procedure
Set the KeyOwner parameter to a valid value.
2.39 AG45309
Description
The identifier does not exist, and the transaction fails.
Scenario
The identifier (internal identity type) to be obtained by the AG during a BuyAirtime
transaction does not exist.
Access Channel
Web, USSD
Possible Causes
The identifier (internal identity type) to be obtained by the AG during a BuyAirtime
Procedure
Enter an identifier that exists.

Copyright © Huawei
Mobile Money
2.40 AG45311
Description
The AG considers that IdentityType is blank.
Scenario
IdentityType queried by the AG by invoking the BCS interface QueryIdentityService is
blank.
Access Channel
STK
Possible Causes
The identity whose type is queried by invoking the QueryIdentityService interface does not
exist in the system.
Procedure
Register the identity.
2.41 AG45312
Description
The customer has not logged in to the App.
Scenario
This error is reported when a customer initiates a request using the mobile App without login.
Access Channel
APP
Possible Causes
The customer has not logged in to the App.
Procedure
Log in to the App first.

Copyright © Huawei
Mobile Money
2.42 AG45313
Description
The login session has timed out.
Scenario
This error is reported when a customer initiates a request using the mobile App but the login
session has timed out.
Access Channel
APP
Possible Causes
The login session has timed out.
Procedure
Log in to the App again.
2.43 AG45314
Description
The verification code fails the verification. The entered verification code is incorrect.
Scenario
This error is reported when the entered verification code is incorrect.
Access Channel
Web, USSD, STK, API
Possible Causes
The entered verification code is incorrect.
Procedure
Enter the correct verification code.

Copyright © Huawei
Mobile Money
2.44 AG45315
Description
M-PESA is undergoing scheduled maintenance.
Scenario
The subscriber access the system through the API channel when some NEs are upgraded. A
message is displayed indicating that the system is being upgraded.
Access Channel
API
Possible Causes
The subscriber access the system through the API channel when some NEs are upgraded.
Procedure
Wait until the upgrade is completed.
2.45 AG45500
Description
The response for invoking the {1} service provided by {0} is incorrect: {2}
{0}: indicates the name of an network element (NE).

{1}: indicates the name of a service provided by the NE.
{2}: indicates the response content.
Scenario
AG parses an external request into a service request to be sent to an internal NE and invokes
the corresponding service.
Access Channel
System
Possible Causes
The response message is in an incorrect format when an NE service is invoked.

Copyright © Huawei
Mobile Money
Procedure
Obtain logs from the AG and the invoked NE and sent the logs to a Huawei engineer for
analysis.
2.46 AG45501
Description
Failed to generate a verification code. The system is busy or an internal error occurs.
Scenario
This error is reported when a verification code is failed to be generated.
Access Channel
Web, USSD, STK, API
Possible Causes
The system is busy or an internal error occurs.
Procedure
Apply for a verification code again.
2.47 AG45502
Description
The structure version in the password obfuscation result must be a number of two digits.
Scenario
This error is reported when the structure version in the password obfuscation result is not a
number of two digits.
Access Channel
Web, USSD, STK, API
Possible Causes
The structure version in the password obfuscation result is not a number of two digits.
Procedure
Obfuscate the password based on the correct rule.

Copyright © Huawei
Mobile Money
2.48 AG45503
Description
The obfuscation parameter must be set to a 4-digit string of letters and digits.
Scenario
This error is reported when the value of the obfuscation parameter for obfuscating the
password is not a 4-digit string of letters and digits.
Access Channel
Web, USSD, STK, API
Possible Causes
The value of the obfuscation parameter for obfuscating the password is not a 4-digit string of
letters and digits.
Procedure
2.49 AG45504
Description
The quence number in the password obfuscation result must be a number of two digits.
Scenario
This error is reported when the quence number in the password obfuscation result is not a
number of two digits.
Access Channel
Web, USSD, STK, API
Possible Causes
The quence number in the password obfuscation result is not a number of two digits.
Procedure

Copyright © Huawei
Mobile Money
2.50 AG45505
Description
The length of the obfuscated password is incorrect.
Scenario
This error is reported when the length of the obfuscated password is incorrect.
Access Channel
Web, USSD, STK, API
Possible Causes
The length of the obfuscated password is incorrect.
Procedure
2.51 AG45506
Description
The timestamp during password obfuscation is inconsistent with that in the request.
Scenario
This error is reported when the timestamp during password obfuscation is inconsistent with
that in the request.
Access Channel
Web, USSD, STK, API
Possible Causes
The timestamp during password obfuscation is inconsistent with that in the request.
Procedure

Copyright © Huawei
Mobile Money
2.52 AG45507
Description
The ConversationID during password obfuscation is inconsistent with that in the request.
Scenario
This error is reported when the ConversationID during password obfuscation is inconsistent
with that in the request.
Access Channel
Web, USSD, STK, API
Possible Causes
The ConversationID during password obfuscation is inconsistent with that in the request.
Procedure
2.53 AG45514
Description
The parameter length is invalid.
Scenario
This error is reported if the length of the ISO8583 parameter is invalid.
Access Channel
API
Possible Causes
The parameter length exceeds the maximum or is less than the minimum.
Procedure
Ensure that the parameter length is valid.

Copyright © Huawei
Mobile Money
2.54 AG45515
Description
The menu length is invalid.
Scenario
This error is reported when the menu length is invalid.
Access Channel
API
Possible Causes
The menu length exceeds the maximum or is less than the minimum.
Procedure
Ensure that the menu length is valid.
2.55 AG45516
Description
The SPID does not exist.
Scenario
This error is reported when the SPID does not exist.
Access Channel
API
Possible Causes
The SPID does not exist.
Procedure
Ensure that the SPID exists.

Copyright © Huawei
Mobile Money
2.56 AG45700
Description
Failed to send deliver_resp to the short message service center (SMSC).
Scenario
Upon receiving a request from the SMSC, the AG returns a response message.
Access Channel
System
Possible Causes
Failed to send deliver_resp to the SMSC.
Procedure
1. Log in to the AG as the ag user.
2. Run the netstat command to verify the connection between the AG and SMSC.
3. If they are disconnected, restart the AG.
2.57 AG45701
Description
Failed to send submit_sm to the SMSC.
Scenario
The AG failed to send submit_sm to the SMSC.
Access Channel
STK
Possible Causes
Failed to send submit_sm to the SMSC.
Procedure
2. Run the netstat command to check whether the connection between the AG and the
SMSC exists. If the connection does not exist, restart the AG.

Copyright © Huawei
Mobile Money
2.58 AG45702
Description
Failed to send the STK menu sending result to the BCS.
Scenario
The AG failed to send the STK menu sending result to the BCS.
Access Channel
STK
Possible Causes
Failed to send the STK menu sending result to the BCS.
Procedure
2. Run the netstat command to check whether the connection between the AG and the MQ
exists. If the connection does not exist, restart the AG.
2.59 AG45703
Description
A timeout occurs during STK menu sending.
Scenario
Access Channel
STK
Possible Causes
Procedure
Find the cause of the STK menu sending failure. For example, check SMSC status and check
whether the receiver has switched off the mobile phone.

Copyright © Huawei
Mobile Money
2.60 AG45704
Description
The third party sends a simple object access protocol (SOAP) fault.
Scenario
This error code is generated when the system receives a SOAP fault from a third party after
sending a SOAP request to the third party.
Access Channel
API
Possible Causes
The AG receives a SOAP fault from the third party.
Procedure
Verify that the SOAP request sent to the third party is correct.
2.61 AG45705
Description
No SOAP fault template is found in the template warehouse.
Scenario
This error code is generated when no SOAP fault template is found in the template
warehouse.
Access Channel
API
Possible Causes
No SOAP fault template is found in the template warehouse.
Procedure
Check AG template configurations.

Copyright © Huawei
Mobile Money
2.62 AG45900
Description
A configuration file to be loaded by the AG is in an incorrect format.
Scenario
Access Channel
System
Possible Causes
Procedure
Correct the file format and restart the AG.
2.63 AG45901
Description
The AG template is incorrectly configured.
Scenario
The AG reloads a service template after start because changes are detected.
Access Channel
System
Possible Causes
A service template to be loaded by the AG is incorrectly configured.
Procedure
1. Log in to the SP portal as an SP operator.
2. Choose My Functions > Operational Configuration > API > AG Template
Configuration.
3. Locate the template configuration based on the channel, command, and parameter
information.
4. Modify the template configurations.

Copyright © Huawei
Mobile Money
2.64 AG45902
Description
AG system parameter values are invalid.
Scenario
When obtaining system parameters, the AG failed to parse system parameter values.
Access Channel
API, STK, USSD
Possible Causes
AG system parameter values are invalid.
Procedure
Obtain AG logs and send them to Huawei engineer for an analysis.
2.65 AG45903
Description
The destination uniform resource identifier (URI) is invalid.
Scenario
The format of the destination URI sent from the HomeSend does not meet the requirements.
Access Channel
API
Possible Causes
The system does not support the destination URI.
Procedure
Enter a correct destination URI.

Copyright © Huawei
Mobile Money
2.66 AG45904
Description
The value of CallerType is invalid.
Scenario
In the API access request message, the value of CallerType does not meet the requirement.
Access Channel
API
Possible Causes
The value of CallerType is not in the valid range.
Procedure
Enter a correct value for the CallerType parameter.
2.67 AG45905
Description
License verification fails because the current number of requests exceeds the total number of
requests allowed to be received within a cycle.
Scenario
During license verification, the number of requests exceeds the total number of requests
allowed to be received within a cycle.
Access Channel
STK, USSD, API
Possible Causes
The current number of requests exceeds the total number of requests allowed to be received
within a cycle.
Procedure
Increase the transaction per second (TPS) in the license file.

Copyright © Huawei
Mobile Money
2.68 AG45906
Description
The certificate is invalid.
Scenario
When a third party initiates a request, the certificate does not match or is incorrectly
configured.
Access Channel
API
Possible Causes
An secure hypertext transfer protocol (HTTPS) request from a third party does not have a
certificate or has an invalid certificate.
Procedure
Verify that a certificate is correctly configured.
2.69 AG49000
Description
No response is sent back within the specified period.
Scenario
This error is reported when the BCS does not send back a response to the schema API request
within the specified period.
Access Channel
API
Possible Causes
The BCS does not send back a response to the schema API request within the specified
period.
Procedure
Check the NE running status or extend the timeout interval.

Copyright © Huawei
Mobile Money
2.70 AG49003
Description
The image fails to be obtained.
Scenario
This error is reported if the corresponding image cannot be found in the attachment.
Access Channel
API, APP
Possible Causes
The corresponding image cannot be found in the attachment.
Procedure
Verify that the image has been uploaded and the image size and format are correct.
2.71 AG49004
Description
The format of the uploaded image is invalid.
Scenario
This error is reported if the format of the uploaded image is invalid.
Access Channel
API, APP
Possible Causes
The format of the uploaded image is invalid.
Procedure
Verify that the format of the uploaded image matches that supported by the system.

Copyright © Huawei
Mobile Money
2.72 AG49005
Description
The size of the uploaded image is invalid.
Scenario
This error is reported if the size of the uploaded image is invalid.
Access Channel
API, APP
Possible Causes
The size of the uploaded image is invalid.
Procedure
Verify that the size of the uploaded image matches that supported by the system.
2.73 AG49006
Description
The image fails to be saved.
Scenario
This error is reported if the image fails to be saved.
Access Channel
API, APP
Possible Causes
The image fails to be saved.
Procedure
Verify that the system is correctly connected to the file system and the image is valid.

Copyright © Huawei
Mobile Money
2.74 AG49007
Description
The access message fails to be returned.
Scenario
This error is reported when the mapping between the adapter class name and channel protocol
name is not configured in the ag.adapter.access.policy.properties file.
Access Channel
Web
Possible Causes
The mapping between the adapter class name and channel protocol name is not configured in
the ag.adapter.access.policy.properties file.
Procedure
Configure the mapping between the adapter class name and channel protocol name in the
ag.adapter.access.policy.properties file, and restart the AG or refresh the cache.
2.75 AG49008
Description
Scenario
This error is reported when the protocol access is disabled on the portal.
Access Channel
Web
Possible Causes
The protocol access is disabled on the portal.
Procedure
Enable the protocol access on the portal.

Copyright © Huawei
Mobile Money
2.76 AG49009
Description
The bill issuer fails to return bill info.
Scenario
When perform the Query Bill Info operation, the third-party fails to return bill info.
Access Channel
API
Possible Causes
The bill issuer fails to return bill info.
Procedure
Contact the third party.
2.77 AG49010
Description
The settlement organization is not configured in the Mobile Money system.
Scenario
This error is reported when a settlement organization initiates settlement date switching, the
configuration of the settlement organization cannot be found in the system.
Access Channel
ISO8583
Possible Causes
When a settlement organization initiates settlement date switching, the configuration of the
settlement organization cannot be found in the system.
Procedure
Configure the settlement organization in the Mobile Money system.

Copyright © Huawei
Mobile Money
2.78 AG49011
Description
The settlement date is incorrect.
Scenario
This error is reported when a settlement organization initiates settlement date switching, the
entered settlement date is incorrect.
Access Channel
ISO8583
Possible Causes
When a settlement organization initiates settlement date switching, the entered settlement date
is incorrect.
Procedure
Enter a correct settlement date.
2.79 AG49012
Description
Scenario
This error is reported when an international transfer transaction is initiated and the key value
required for decrypting the request is not configured in the system parameter.
Access Channel
API
Possible Causes
The key value required for decrypting the request is not configured in the system parameter,
leading to decryption failure.
Procedure
Configure the following system parameter key value: Operational Configuration --System
Parameter--Telkomsel Integration--KEY of IMT Integration with Telkomsel

Copyright © Huawei
Mobile Money
2.80 AG49013
Description
Scenario
This error is reported when an international transfer transaction is initiated but the request
length is insufficient.
Access Channel
API
Possible Causes
The request length is insufficient.
Procedure
Initiate a correct request.
2.81 AG49014
Description
Scenario
This error is reported when an international transfer transaction is initiated but the request
password fails to be verified.
Access Channel
API
Possible Causes
The request password fails to be verified.
Procedure
Initiate a request containing the correct password.

Copyright © Huawei
Mobile Money
2.82 AG49015
Description
The corresponding certificate serial number is not transferred on the client.
Scenario
This error is reported if the certificate serial number that the 7-layer model obtains from the
HTTPS is empty.
Access Channel
All
Possible Causes
Procedure
2.83 AG49016
Description
The bill due date has expired.
Scenario
This error is reported if the bill due date has expired when customer initiates a Pay Bill
transaction through the USSD channel.
Access Channel
Web,USSD,API
Possible Causes
The bill due date has expired.
Procedure
Send the payment information to the third party.

Copyright © Huawei
Mobile Money
2.84 AG49017
Description
The bill has been paid.
Scenario
This error is reported if the bill has been paid when customer initiates a Pay Bill transaction
through the USSD channel.
Access Channel
Web,USSD,API
Possible Causes
The bill has been paid.
Procedure
Send the payment information to the third party.
2.85 AG49018
Description
Since CNS Suspend Status is set to Suspended for the role, the function of modifying Disable
CNS is unavailable.
Scenario
This error is reported when CNS Suspend Status is changed to Suspended for a customer and
the Disable CNS is modified through the STK channel.
Access Channel
POS
Possible Causes
When CNS Suspend Status is set to Suspended for the role, the function of modifying Disable
CNS is suspended.
Procedure
Change the value of CNS Suspend Status to Normal.

Copyright © Huawei
Mobile Money
2.86 AG49019
Description
The eBus configuration of ISO8583 is incorrect in the data table
CPS_ISO8583_LINK_CONF.
Scenario
This error code is reported when the eBus service of ISO8583 is configured incorrectly.
Access Channel
ISO8583
Possible Causes
The eBus configuration of ISO8583 is incorrect in the data table
CPS_ISO8583_LINK_CONF.
Procedure
Contact the customer service center.
2.87 AG49020
Description
The ISO8583 channel cannot send messages or receives third-party messages because the
channel is in the sign-off state.
Scenario
This error is reported when the ISO8583 channel cannot send messages or receives third-party
messages because the channel is in the sign-off state.
Access Channel
ISO8583
Possible Causes
The ISO8583 channel cannot send messages or receives third-party messages because the
channel is in the sign-off state.
Procedure

Copyright © Huawei
Mobile Money
2.88 AG49021
Description
The PROTOCOL of ISO8583is configured incorrectly.
Scenario
This error code is reported when PROTOCOL of ISO8583 is configured incorrectly.
Access Channel
ISO8583
Possible Causes
The PROTOCOL of ISO8583is configured incorrectly.
Procedure
2.89 AG_EXT1000
Description
The new MPIN and confirmation MPIN are different.
Scenario
This error is reported when the MPIN is modified through a handset but the new MPIN and
confirmation MPIN are different.
Access Channel
API
Possible Causes
The new MPIN and confirmation MPIN are different.
Procedure
Set the confirmation MPIN the same as the new MPIN.

Copyright © Huawei
Mobile Money
2.90 AG_EXT1001
Description
The format of specified personal identification number (PIN) is incorrect.
Scenario
This error is reported when the regular verification of PIN codes is configured for AG
templates but the entered PIN code is in incorrect format.
Access Channel
USSD, SMS
Possible Causes
The format of specified PIN is incorrect.
Procedure
Verify that the PIN format is correct.
2.91 NC40001
Description
The notification type ID cannot be empty.
Scenario
A notification is sent. The error code is used only in internal verification and the error seldom
occurs in any channels.
Access Channel
System
Possible Causes
The notification type ID is empty in the request object in the context submitted by the request
initiator.
Procedure
Ask a Huawei engineer to check whether the notification ID is null in the program code.

Copyright © Huawei
Mobile Money
2.92 NC40005
Description
The notification template does not exist.
Scenario
A notification is sent.
Access Channel
System
Possible Causes
 The notification template does not exist in the system.
 The cache content is not synchronized to the AG system.
Procedure
Check whether the CPS_NC_TYPE table in the AuditDB database contains the notification
template.
2.93 NC40008
Description
The notification request object cannot be empty.
Scenario
Access Channel
System
Possible Causes
The request object is empty in the request submitted by the notification request initiator.
Procedure
Ask a Huawei engineer to check whether the notification request object is null in the program
code.

Copyright © Huawei
Mobile Money
2.94 NC40009
Description
The notification request set cannot be empty.
Scenario
Access Channel
System
Possible Causes
The request set is empty in the request submitted by the notification request initiator.
Procedure
Ask a Huawei engineer to check whether the notification request set is null in the program
code.
2.95 NC40010
Description
The notification receiver cannot be empty.
Scenario
Access Channel
System
Possible Causes
The notification receiver is empty in the request object in the context submitted by the request
initiator.
Procedure
Ask a Huawei engineer to check whether the notification receiver is null in the program code.

Copyright © Huawei
Mobile Money
2.96 NC40011
Description
The notification channel cannot be empty.
Scenario
Access Channel
System
Possible Causes
The notification channel is empty in the request object in the context submitted by the request
initiator.
Procedure
Ask a Huawei engineer to check whether the notification channel is null in the program code.
2.97 NC40012
Description
The operation requested by the notification request initiator is not supported.
Scenario
Access Channel
System
Possible Causes
The operation requested by the notification request initiator is incorrect.
Procedure
Ask a Huawei engineer to check whether the program code supports the requested operation.

Copyright © Huawei
Mobile Money
2.98 NC40013
Description
The notification channel requested is not supported.
Scenario
Access Channel
System
Possible Causes
The notification channel requested by the notification request initiator is incorrect.
Procedure
Ask a Huawei engineer to check whether the program code supports the requested notification
channel.
2.99 NC40700
Description
The notification context cannot be empty.
Scenario
Access Channel
System
Possible Causes
The notification context object is empty in the request submitted by the notification request
initiator.
Procedure
Ask a Huawei engineer to check whether the notification context object is null in the program
code.

Copyright © Huawei
Mobile Money
2.100 NC40907
Description
The notification variable is not found.
Scenario
Access Channel
System
Possible Causes
 The notification variable does not exist.
 The notification variable is not found in the cache.
Procedure
Verify whether the notification variable exists in the cps_nc_variable table in the sysdb.
 If no, add the variable in the My Functions > Operational Configuration >
Notification Configuration > Notification Variable menu path on the portal.
 If yes, data in the cache is not updated. Refresh the cache using the cashview tool.
2.101 NC41001
Description
Notification not support Encoding. The encoding format is not supported.
Scenario
Access Channel
System
Possible Causes
The MessageCode parameter in the nc.env.xml configuration file specifies an encoding
format not supported by the SMSC.
Procedure
1. Check whether the encoding format currently used by the SMSC is correctly configured
in the nc.env.xml file.

Copyright © Huawei
Mobile Money
Log in to the server as the ag user. The configuration file path is

config\release\nc.env.xml.
For the encoding format supported by the SMSC, contact the vendor.
2. After modifying the configuration file, restart the AG module.
2.102 NC41007
Description
The notification message object cannot be empty.
Scenario
Access Channel
System
Possible Causes
The notification message object is empty in the request submitted by the notification request
initiator.
Procedure
Ask a Huawei engineer to check whether the notification message object is null in the
program code.
2.103 NC41100
Description
Failed to encrypt or decrypt the string.
Scenario
Access Channel
System
Possible Causes
The string to be encrypted or decrypted is empty.

Copyright © Huawei
Mobile Money
Procedure
Ask a Huawei engineer to check whether the string to be encrypted or decrypted is empty in
the program code.
2.104 NC41101
Description
The SMS UserName length cannot more than 16.
Scenario
The AG is started.
Access Channel
System
Possible Causes
The length of the Username.parameter in the nc.env.xml configuration file exceeds 16 bytes.
Procedure
1. Ask the SMSC maintenance engineer to change the login user name to a value with less
than 16 bytes.
2. If the SMSC maintenance engineer has changed the login user name, the Username.
parameter in the config\release\nc.env.xml file must be modified accordingly.
2.105 NC41102
Description
The length of the password used to connect to the SMSC cannot exceed 9 bytes.
Scenario
The AG is started.
Access Channel
System

Copyright © Huawei
Mobile Money
Possible Causes
The value of the sms.connection.password field in the sms_sender_config.properties
configuration file contains more than 9 bytes.
Procedure
1. Ask the SMSC maintenance engineer to change the login password to a value with less
than 9 bytes.
2. If the SMSC maintenance engineer have changed the login password, the Password field
in the nc.env.xml configuration file must be change accordingly. Log in to the server as
the ag user. The configuration file path is config\release\nc.env.xml.
2.106 NC41300
Description
Get the System Parameter failed.
Scenario
Access Channel
System
Possible Causes
 An error occurred when the system converted the number of notification failure records
to be read at one time to an integer.
 An error occurred when the system converted the number of deferred notification records
to be read at one time to an integer.
Procedure
1. Verify whether the value of the FAILURE_NOTIFICATION_READING_AMOUNT
field in the CPS_SYS_PARAM_INSTANCE table in the SysDB database is correct.
2. Verify whether the value of the
DEFERRED_NOTIFICATION_READING_AMOUNT field in the
CPS_SYS_PARAM_INSTANCE table in the SysDB database is correct.
2.107 NC41301
Description
Failed to obtain configuration parameters from a local AG configuration file.

Copyright © Huawei
Mobile Money
Scenario
Access Channel
System
Possible Causes
Failed to obtain configuration parameters from a local AG configuration file.
Procedure
Check the configuration files configured in the i18n.default.locationPattern field in the
classes/bme.properties file in the AG environment. Check whether the parameter values
match with the configuration descriptions based on keys in the error descriptions.
2.108 UMC60503
Description
Session timeout.
Scenario
The USSD transaction session initiated by a subscriber using its mobile phone times out.
Access Channel
USSD
Possible Causes
USSD session exceeds the specified threshold.
Procedure
Check whether session timeout necessarily recur.
If no, please re-initiate the session request.
If yes, send AG logs in the /log/debug/ag_debug.log to a Huawei engineer for fault
diagnosis.

Copyright © Huawei
Mobile Money
2.109 UMC60504
Description
Information about the MSISDN does not exist. Register the identity first.
Scenario
When a subscriber initiates a transaction through USSD, the identity of the used MSISDN
does not exist in the Mobile Money.
Access Channel
USSD
Possible Causes
The identity of the MSISDN does not exist in the Mobile Money.
Procedure
Bring your identity documents and register with a nearby agent
2.110 UMC60505
Description
Subscribe to an USSD product first.
Scenario
A subscriber who has not subscribed to any USSD product initiates a USSD transaction by
using a mobile phone.
Access Channel
USSD
Possible Causes
The identity has not subscribed to any USSD product.
Procedure
Contact the customer service center to subscribe to an USSD product.

Copyright © Huawei
Mobile Money
2.111 UMC60506
Description
The internal template configuration file does not exist.
Scenario
No template configuration file is found for the channel during AG NE startup.
Access Channel
System
Possible Causes
No internal template configuration file is found for the channel.
Procedure
Verify whether the *_template.xml file exists in the WEB-INF/classes/menu path.
2.112 UMC60507
Description
No template is found.
Scenario
When a subscriber initiates a transaction through USSD, the AG finds no template
configuration file that matches the USSD channel.
Access Channel
System
Possible Causes
The specified template does not exist.
Procedure
Please check whether the specified template exists in the template configuration file in the
WEB-INF/classes/menu directory.

Copyright © Huawei
Mobile Money
2.113 UMC60508
Description
Render USSD menu failed.
Scenario
When a subscriber initiates a transaction through USSD, generating menu content by the AG
fails.
Access Channel
System
Possible Causes
Failed to render USSD menu. Cause: {0}.
The {0} variable indicates the cause of the menu generation failure by the AG, for example, Invalid
current menu item.
Procedure
Please check the jexl syntax of corresponding USSD template.
2.114 UMC60509
Description
The system is in maintenance status.
Scenario
Transactions initiated through USSD fail due to internal causes, such as incorrect background
USSD process configurations, cache loading failures, and program bugs.
Access Channel
USSD
Possible Causes
Unexpected error occurred during runtime.
Procedure
1. Check the NE status.
2. Send AG logs in the /log/debug/ag_debug.log to a Huawei engineer for fault diagnosis.

Copyright © Huawei
Mobile Money
2.115 UMC60510
Description
The status of identity is frozen.
Scenario
A subscriber in the frozen status initiates a transaction through USSD.
Access Channel
USSD
Possible Causes
The status of identity is frozen.
Procedure
Please call customer service center.
2.116 UMC60512
Description
The customer status cannot be authenticated.
Scenario
When a subscriber initiates a transaction through USSD, the customer status is invalid.
Access Channel
USSD
Possible Causes
The customer status is invalid.
Procedure
Contact the customer service center to activate the customer.

Copyright © Huawei
Mobile Money
2.117 UMC60513
Description
The PIN is locked.
Scenario
When a subscriber initiates a transaction through USSD, the number of consecutive times for
which the subscriber enters an incorrect PIN exceeds the upper limit.
Access Channel
USSD
Possible Causes
The number of PIN attempts has reached the upper limit.
Procedure
Contact the customer service center to unlock the PIN.
2.118 UMC60514
Description
The PIN is about to expire.
Scenario
When a subscriber whose PIN is about to expire initiates a transaction through USSD, the AG
properly sends back a menu list and a message indicating that the subscriber's PIN is about to
expire.
Access Channel
USSD
Possible Causes
The PIN is about to expire.
Procedure
Reset your PIN in the Change PIN menu.

Copyright © Huawei
Mobile Money
2.119 UMC60515
Description
The PIN has expired.
Scenario
A subscriber whose PIN has expired initiates a transaction through USSD.
Access Channel
USSD
Possible Causes
The PIN has expired.
Procedure
Contact the customer service center to reset the PIN.
2.120 UMC60516
Description
The identity needs to be activated.
Scenario
When a subscriber in the Pending Active status initiates a transaction through USSD, the AG
sends back a message indicating that the subscriber needs to be activated first.
Access Channel
USSD
Possible Causes
The identity is in the Pending Active status.
Procedure
Activate the identity in the Customer Activate menu.

Copyright © Huawei
Mobile Money
2.121 UMC60517
Description
The status of the organization to which the till belongs is invalid.
Scenario
When an organization operator initiates a USSD transaction by using the till, the status of the
organization to which the till belongs is invalid.
Access Channel
USSD
Possible Causes
The organization to which the till belongs is neither in the Active status nor in the Pending
Active status.
Procedure
Contact the customer service center to activate the till.
2.122 UMC60518
Description
The PIN does not exist.
Scenario
A subscriber for whom no PIN is configured initiates a transaction through USSD.
Access Channel
USSD
Possible Causes
The identity has no PIN in the system.
Procedure
Contact the customer service center to set a PIN.

Copyright © Huawei
Mobile Money
2.123 UMC60519
Description
The identity has no permission to run in the session.
Scenario
When transaction parameters are collected during interaction with the AG, MSISDNs used by
the subscriber are inconsistent.
Access Channel
USSD
Possible Causes
The identity has no permission to run in the session.
Procedure
Please re-initiate a new session request.
2.124 UMC60520
Description
Your {0} is locked.
The {0} variable indicates the security credential, for example, PIN.
Scenario
A subscriber whose security credential (PIN or password) is locked initiates a transaction
through USSD.
Access Channel
USSD
Possible Causes
Your {0} is locked.
Procedure
Please unlock {0} first.

Copyright © Huawei
Mobile Money
2.125 UMC60521
Description
To use services normally, please get registered first.
Scenario
An unregistered subscriber initiates a USSD transaction by using a mobile phone.
Access Channel
USSD
Possible Causes
The customer is not registered.
Procedure
Bring your identity documents and register with a nearby agent
2.126 UMC60522
Description
Your request is being processed. Please wait for the confirmation short message.
Scenario
After all transaction parameters are collected, the AG sends back a message asking the
subscriber to wait for the processing result from the background.
Access Channel
USSD
Possible Causes
The request is ended normally.
Procedure
Your request is being processed. Please wait for the confirmation short message.

Copyright © Huawei
Mobile Money
2.127 UMC60523
Description
You have cancelled the request.
Scenario
When transaction parameters are collected during interaction with the AG, the AG sends back
a message indicating that a transaction is cancelled if the subscriber cancels the transaction.
Access Channel
System
Possible Causes
The request is cancelled.
Procedure
You have cancelled the request.
2.128 UMC60524
Description
Please select menu.
Scenario
A message is displayed to prompt a subscriber to choose a menu from the USSD menu list.
Access Channel
USSD
Possible Causes
Prompt customer to choose menu.
Procedure
Please choose menu from menu list.

Copyright © Huawei
Mobile Money
2.129 UMC60525
Description
System error. Parameters in the menu do not match with parameters configured in the process
template.
Scenario
The parameters configured in menus do not match with those configured in the process
template.
Access Channel
System
Possible Causes
Parameters in the menu do not match with parameters configured in the process template.
Procedure
Verify that parameters in the menu match with parameters configured in the process template.
2.130 UMC60528
Description
The STK menu content in the XML file does not meet specifications.
Scenario
When parsing an XML file that stores STK initial activation menus and normal menus, the
AG finds that the file content does not meet specifications.
Access Channel
STK
Possible Causes
The STK menu content in the XML file does not meet specifications.
Procedure
Modify the STK menu content in the XML file.

Copyright © Huawei
Mobile Money
2.131 UMC60529
Description
The MSISDN does not meet specifications.
Scenario
During MSISDN encoding, it is found that an MSISDN does not meet specifications.
Access Channel
STK
Possible Causes
The MSISDN does not meet specifications.
Procedure
Change the MSISDN.
2.132 UMC60530
Description
An error occurred when compiling a binary menu.
Scenario
An error occurred when the AG compiled a binary menu during STK menu generation.
Access Channel
STK
Possible Causes
An error occurred when compiling a binary menu.
Procedure
Send AG logs in the /log/debug/ag_debug.log to a Huawei engineer for fault diagnosis.

Copyright © Huawei
Mobile Money
2.133 UMC60531
Description
Operation failed because the status of the identity does not support the current service.
Scenario
When a till or customer requests menus through the USSD channel, the till or customer is not
in the active or pending status.
Access Channel
USSD
Possible Causes
The status of the identity does not support the current service.
Procedure
2.134 UMC60532
Description
The subscriber subscribes to excessive services.
Scenario
When the AG dynamically generates STK menus, more than 8 submenus are generated at the
same level.
Access Channel
STK
Possible Causes
The AG can create a maximum of 8 submenus at the same level.
Procedure
Unsubscribe from some products or reduce some product services.

Copyright © Huawei
Mobile Money
2.135 UMC60533
Description
The STK template is not configured for some STK menus.
Scenario
When the AG dynamically generates STK menus, some STK templates are not configured for
some menus.
Access Channel
STK
Possible Causes
An STK template must be configured for each STK menu.
Procedure
2. Choose My Functions > Operational Configuration > UMC. Configure an STK
template for each STK menu on the Customer Menu and Organization Operator
Menu pages.
2.136 UMC60534
Description
The STK menu fails to be pushed.
Scenario
This error is reported when the number of same-level STK menus pushed to a customer' or
till's mobile phone exceeds eight.
Access Channel
STK
Possible Causes
The number of pushed menus at the same level exceeds eight.
Procedure
Use either of the following methods to solve the problem:
 Choose My Functions > Operational Configuration > UMC.

Copyright © Huawei
Mobile Money
Under Customer Menu or Organization Operator Menu, adjust the menu

configuration to ensure that number of menus at the same level does not exceed eight.
 Adjust the product subscribed by an identity and ensure that the number of same-level
menus associated with the subscribed service does not exceed eight.
2.137 UMC65001
Description
The third-party system detects that the recharge MSISDN is incorrect or an error is reported
during the message sending and receiving.
Scenario
This error is reported if the recharge MSISDN is incorrect or an error is reported during the
message sending and receiving.
Access Channel
API, APP, UMC, Web
Possible Causes
The third-party system detects that the recharge MSISDN is incorrect or an error is reported
during the message sending and receiving.
Procedure
Verify that the recharge MSISDN is in correct status and messages can be sent and received
correctly.

Copyright © Huawei
Mobile Money
Error Codes Reference 3 BCR Error Codes
3 BCR Error Codes
About This Chapter

3.1 Rep10000
3.2 Rep10001
3.3 Rep10002
3.4 Rep10003
3.5 Rep10004
3.6 Rep10005
3.7 Rep10006
3.8 Rep10007
3.9 Rep10008
3.10 Rep10009
3.11 Rep10010
3.12 Rep10011
3.13 Rep10012
3.14 Rep10013
3.15 Rep10014
3.16 Rep10015
3.17 Rep10016
3.18 Rep10017
3.19 Rep10018
3.20 Rep10019

Copyright © Huawei
Mobile Money
3.21 Rep10020
3.22 Rep10021
3.23 Rep10022
3.24 Rep10023
3.25 Rep10024
3.26 Rep10025
3.27 Rep10026
3.28 Rep10027
3.29 Rep10028
3.30 Rep10029
3.31 Rep10030
3.32 Rep10031
3.33 Rep10032
3.34 Rep10033
3.35 Rep10034
3.36 Rep10035
3.37 Rep10036
3.38 Rep10037
3.39 Rep10038
3.40 Rep10039
3.41 Rep10040
3.42 Rep10041
3.43 Rep10042
3.1 Rep10000
Description
The name or format of the file to be uploaded is incorrect.
Scenario
This error code is generated if the name or format of a file to be uploaded is incorrect.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
A file to be uploaded does not meet requirements.
Procedure
Upload a file that meets requirements.
3.2 Rep10001
Description
File content does not meet requirements.
Scenario
This error code is generated if the content of a file to be uploaded is incorrect.
Access Channel
Web
Possible Causes
File content has been tampered with.
Procedure
Upload a correct file.
3.3 Rep10002
Description
The question code or question name already exists.
Scenario
This error code is generated if question code or question name entered by an operator during
system problem addition already exists.
Access Channel
Web
Possible Causes
The question code or question name already exists.

Copyright © Huawei
Mobile Money
Procedure
Change the question code or question name.
3.4 Rep10003
Description
The configuration set is being loaded.
Scenario
The configuration set to be loaded is being loaded.
Access Channel
Web
Possible Causes
The configuration set is being loaded.
Procedure
Wait until loading the configuration set is complete.
3.5 Rep10004
Description
The configuration set is being unloaded.
Scenario
The configuration set to be loaded is being unloaded.
Access Channel
Web
Possible Causes
The configuration set is being unloaded.
Procedure
Wait until unloading the configuration set is complete.

Copyright © Huawei
Mobile Money
3.6 Rep10005
Description
Loading a configuration set fails.
Scenario
Access Channel
Web
Possible Causes
Procedure
Collect {HOME}/log/debug/portal_debug.log as the repportal user and send it to Huawei
engineers for troubleshooting.
3.7 Rep10006
Description
There is no available data source to load configuration set.
Scenario
Access Channel
Web
Possible Causes
Procedure
Wait until there is an idle data source.

Copyright © Huawei
Mobile Money
3.8 Rep10007
Description
The configuration data of a configuration set is blank.
Scenario
The data file package of the configuration set to be exported is blank.
Access Channel
Web
Possible Causes
The configuration data of a configuration set is blank.
Procedure
Load configuration data before exporting the configuration set.
3.9 Rep10008
Description
The configuration set cannot be tested.
Scenario
A configuration set on the repository portal is not in the draft state and cannot be tested.
Access Channel
Web
Possible Causes
The configuration set is not in the draft state.
Procedure
The configuration set is not in the draft state. Select another configuration set, and try again.

Copyright © Huawei
Mobile Money
3.10 Rep10009
Description
Scenario
Only one of configuration sets in the same Mobile Money system version on the repository
portal can be tested at a time.
Access Channel
Web
Possible Causes
Only one of configuration sets in the same Mobile Money system version can be tested at a
time.
Procedure
Test the configuration set after associated configuration sets are tested.
3.11 Rep10010
Description
Scenario
A configuration set on the repository portal is not loaded to the system database and cannot be
tested.
Access Channel
Web
Possible Causes
The configuration set is not loaded to the system database.
Procedure
Load the configuration set to the system database and test the configuration set.

Copyright © Huawei
Mobile Money
3.12 Rep10011
Description
Scenario
A configuration set on the repository portal has no test environment and cannot be tested.
Access Channel
Web
Possible Causes
The configuration set has no test environment.
Procedure
Add a test environment for the configuration set and test it.
3.13 Rep10012
Description
Scenario
A configuration set on the repository portal has multiple test environments and cannot be
tested.
Access Channel
Web
Possible Causes
The configuration set has multiple test environments.
Procedure
Verify that the configuration set has only one test environment and test it.

Copyright © Huawei
Mobile Money
3.14 Rep10013
Description
Scenario
A test or deployment task is in progress in the test environment for a configuration set on the
repository portal, and the configuration set cannot be tested.
Access Channel
Web
Possible Causes
A test or deployment task is in progress in the test environment for the configuration set.
Procedure
Test the configuration item when the test or deployment task is complete.
3.15 Rep10014
Description
The configuration set has been unloaded.
Scenario
A configuration set to be unloaded has been unloaded.
Access Channel
Web
Possible Causes
The configuration set has been unloaded.
Procedure
Open the current page again.

Copyright © Huawei
Mobile Money
3.16 Rep10015
Description
The current configuration set is not in the Released state.
Scenario
The configuration set involved during deployment task execution is not in the Released state.
Access Channel
Web
Possible Causes
The configuration set is in an abnormal state.
Procedure
Select another configuration set.
3.17 Rep10016
Description
The Mobile Money environment must be a valid environment currently managed by the
configuration repository.
Scenario
The Mobile Money environment involved during deployment task execution is not a valid
environment currently managed by the configuration repository.
Access Channel
Web
Possible Causes
The Mobile Money environment is not a valid environment.
Procedure
Select another Mobile Money environment.

Copyright © Huawei
Mobile Money
3.18 Rep10017
Description
Another test or deployment task is in progress in the current Mobile Money environment.
Scenario
Another test or deployment task is in progress in the Mobile Money environment involved
during deployment task execution.
Access Channel
Web
Possible Causes
Another test or deployment task is in progress.
Procedure
Select another Mobile Money environment.
3.19 Rep10018
Description
Querying deployment results failed.
Scenario
The found deployment results are incorrect.
Access Channel
Web
Possible Causes
Deployment results are incorrect.
Procedure
Select another Mobile Money environment, and query deployment results.

Copyright © Huawei
Mobile Money
3.20 Rep10019
Description
Sending an HTTPS command fails.
Scenario
Sending an HTTPS request times out during HTTPS command sending.
Access Channel
Web
Possible Causes
Sending an HTTPS request times out.
Procedure
Check the network, or resend an HTTPS request.
3.21 Rep10020
Description
The configuration set cannot be locked.
Scenario
locked.
Access Channel
Web
Possible Causes
Procedure
Load the configuration set to the system database and lock the configuration set.

Copyright © Huawei
Mobile Money
3.22 Rep10021
Description
The configuration set cannot be locked.
Scenario
A configuration set on the repository portal is not in the draft state and cannot be locked.
Access Channel
Web
Possible Causes
Procedure
Verify that the configuration set is in the draft state and lock it.
3.23 Rep10022
Description
The configuration set cannot be locked again.
Scenario
A configuration set on the repository portal has been locked and cannot be locked again.
Access Channel
Web
Possible Causes
The configuration set has been locked.
Procedure
Unlock the configuration set and lock it.

Copyright © Huawei
Mobile Money
3.24 Rep10023
Description
The configuration set cannot be released.
Scenario
A configuration set on the repository portal is not in the draft state and cannot be released.
Access Channel
Web
Possible Causes
Procedure
Verify that the configuration set is in the draft state and release it.
3.25 Rep10024
Description
Scenario
released.
Access Channel
Web
Possible Causes
Procedure
Load the configuration set to the system database and release the configuration set.

Copyright © Huawei
Mobile Money
3.26 Rep10025
Description
Scenario
A configuration set on the repository portal is being tested and cannot be released.
Access Channel
Web
Possible Causes
The configuration set is being tested.
Procedure
Release the configuration set when the test is complete.
3.27 Rep10026
Description
The status code returned during HTTPS command sending is {0}.
Scenario
An exception occurs when sending an HTTPS request during HTTPS command sending.
Access Channel
Web
Possible Causes
An exception occurs when sending an HTTPS request.
Procedure
Perform analysis based on the status code.

Copyright © Huawei
Mobile Money
3.28 Rep10027
Description
Scenario
A configuration set has been locked, and the operation cannot be performed.
Access Channel
Web
Possible Causes
Procedure
Unlock the configuration set and perform the operation.
3.29 Rep10028
Description
The configuration set is being deployed in the test environment.
Scenario
A configuration set is being deployed in the test environment, and the operation cannot be
performed.
Access Channel
Web
Possible Causes
The configuration set is being deployed in the test environment.
Procedure
Perform the operation when the deployment is complete.

Copyright © Huawei
Mobile Money
3.30 Rep10029
Description
An error occurs when unloading the configuration set.
Scenario
Unloading a configuration set fails.
Access Channel
Web
Possible Causes
An error occurs when unloading the configuration set.
Procedure
Collect /log/debug/portal_debug.log as the repportal user and send it to Huawei engineer
for troubleshooting.
3.31 Rep10030
Description
Creating a configuration set by importing a file fails.
Scenario
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
3.32 Rep10031
Description
Scenario
Creating configuration sets by importing a .zip file fails because the number of files obtained
after decompression is incorrect.
Access Channel
Web
Possible Causes
The number of files contained in the imported .zip file is incorrect.
Procedure
Import the correct configuration set data file.
3.33 Rep10032
Description
Scenario
Creating configuration sets by importing a .zip file fails because file content is tampered with.
Access Channel
Web
Possible Causes
The content of files contained in the imported .zip file is tampered with.
Procedure
Verify that the imported configuration set data file is not tampered with.

Copyright © Huawei
Mobile Money
3.34 Rep10033
Description
Scenario
The Mobile Money system version number in an imported file for creating configuration sets
does not exist in the system.
Access Channel
Web
Possible Causes
The Mobile Money system version number in the file that stores basic configuration set
information and is contained in the imported .zip file does not exist in the system.
Procedure
Verify that Mobile Money system version numbers in the imported .zip file are correct.
3.35 Rep10034
Description
Creating configuration sets by replication fails.
Scenario
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
3.36 Rep10035
Description
The HTTPS password fails the verification performed when an HTTPS request is received.
Scenario
The HTTPS password fails the verification performed when an HTTPS request is received.
Access Channel
Web
Possible Causes
The HTTPS password is incorrect.
Procedure
Verify that the HTTPS password is correct.
3.37 Rep10036
Description
The configuration set cannot be unlocked again.
Scenario
A configuration set on the repository portal has been unlocked and cannot be unlocked again.
Access Channel
Web
Possible Causes
The configuration set has been unlocked.
Procedure
Verify the configuration set has been locked and try again.

Copyright © Huawei
Mobile Money
3.38 Rep10037
Description
The export is not allowed.
Scenario
A configuration set on the repository portal is being loaded or unloaded and cannot be
exported.
Access Channel
Web
Possible Causes
A configuration set is being loaded or unloaded.
Procedure
Try again later.
3.39 Rep10038
Description
An error occurred when exporting the file.
Scenario
A configuration set on the repository portal is writing database data to the file.
Access Channel
Web
Possible Causes
An error occurred when exporting the file.
Procedure

Copyright © Huawei
Mobile Money
3.40 Rep10039
Description
The file fails to be uploaded.
Scenario
During a configuration set test on the repository portal, after a file is uploaded to the Mobile
Money system, the BTS NE obtains the file for deployment. A file fails to be uploaded due to
incorrect environment configuration.
Access Channel
Web
Possible Causes
The environment configuration is incorrect.
Procedure
Log in to the repository portal, choose Configuration Management > Environment
Management and verify that the environment configuration is correct.
3.41 Rep10040
Description
Failed to refresh the cache of the portal.
Scenario
This error is reported when the portal whose cache is refreshed is not a valid repository portal.
Access Channel
Web
Possible Causes
The portal whose cache is refreshed is not a valid repository portal.
Procedure
Ensure that the repository portal is correctly configured.

Copyright © Huawei
Mobile Money
3.42 Rep10041
Description
The selected configuration set to be upgraded or the target version is incorrect.
Scenario
This error is reported during the configuration set upgrade if the selected configuration set to
be upgraded or the target version is incorrect.
Access Channel
Web
Possible Causes
The selected configuration set to be upgraded or the target version is incorrect.
Procedure
Ensure that the selected configuration set to be upgraded and the target version are correct.
3.43 Rep10042
Description
The HTTPS request fails.
Scenario
This error is reported if the Secret Word Policy menu is chosen on the configuration set
details page after a configuration set is unloaded on the Database Management page.
Access Channel
Web
Possible Causes
 The HTTPS link address is incorrect.
 The HTTPS link address does not exist.
 The server is down.
Procedure
Check the HTTPS link address.

Copyright © Huawei
Mobile Money
Error Codes Reference 4 BCS Error Codes
4 BCS Error Codes
About This Chapter

4.1 BCS50001
4.2 BCS50002
4.3 BCS50003
4.4 BCS50004
4.5 BCS50005
4.6 BCS50006
4.7 BCS50007
4.8 BCS50008
4.9 BCS50009
4.10 BCS50010
4.11 BCS50011
4.12 BCS50012
4.13 BCS50013
4.14 BCS50014
4.15 BCS50015
4.16 BCS50016
4.17 BCS50017
4.18 BCS50018
4.19 BCS50019
4.20 BCS50020

Copyright © Huawei
Mobile Money
4.21 BCS50021
4.22 BCS50022
4.23 BCS50024
4.24 BCS50025
4.25 BCS50026
4.26 BCS50027
4.27 BCS50028
4.28 BCS50029
4.29 BCS50030
4.30 BCS50031
4.31 BCS50032
4.32 BCS50033
4.33 BCS50034
4.34 BCS50035
4.35 BCS50036
4.36 BCS50037
4.37 BCS50038
4.38 BCS50039
4.39 BCS50040
4.40 BCS50041
4.41 BCS50042
4.42 BCS50043
4.43 BCS50044
4.44 BCS50045
4.45 BCS50046
4.46 BCS50047
4.47 BCS50048
4.48 BCS50049
4.49 BCS50050
4.50 BCS50051
4.51 BCS50052
4.52 BCS50053
4.53 BCS50054

Copyright © Huawei
Mobile Money
4.54 BCS50055
4.55 BCS50056
4.56 BCS50057
4.57 BCS50058
4.58 BCS50059
4.59 BCS50060
4.60 BCS50061
4.61 BCS50062
4.62 BCS50063
4.63 BCS50064
4.64 BCS50065
4.65 BCS50066
4.66 BCS50067
4.67 BCS50068
4.68 BCS50069
4.69 BCS50070
4.70 BCS50071
4.71 BCS50072
4.72 BCS50073
4.73 BCS50074
4.74 BCS50075
4.75 BCS50076
4.76 BCS50077
4.77 BCS50078
4.78 BCS50079
4.79 BCS50080
4.80 BCS50081
4.81 BCS50082
4.82 BCS50083
4.83 BCS50084
4.84 BCS50085
4.85 BCS50086
4.86 BCS50087

Copyright © Huawei
Mobile Money
4.87 BCS50088
4.88 BCS50089
4.89 BCS50090
4.90 BCS50091
4.91 BCS50092
4.92 BCS50093
4.93 BCS50094
4.94 BCS50095
4.95 BCS50096
4.96 BCS50097
4.97 BCS50098
4.98 BCS50099
4.99 BCS50100
4.100 BCS50101
4.101 BCS50102
4.102 BCS50103
4.103 BCS50104
4.104 BCS50105
4.105 BCS50106
4.106 BCS50107
4.107 BCS50108
4.108 BCS50109
4.109 BCS50110
4.110 BCS50111
4.111 BCS50112
4.112 BCS50113
4.113 BCS50114
4.114 BCS50115
4.115 BCS50116
4.116 BCS50117
4.117 BCS50118
4.118 BCS50119
4.119 BCS50120

Copyright © Huawei
Mobile Money
4.120 BCS50121
4.121 BCS50122
4.122 BCS50123
4.123 BCS50124
4.124 BCS50125
4.125 BCS50126
4.126 BCS50127
4.127 BCS50128
4.128 BCS50129
4.129 BCS50130
4.130 BCS50131
4.131 BCS50132
4.132 BCS50133
4.133 BCS50134
4.134 BCS50135
4.135 BCS50136
4.136 BCS50137
4.137 BCS50138
4.138 BCS50139
4.139 BCS50140
4.140 BCS50141
4.141 BCS50142
4.142 BCS50143
4.143 BCS50144
4.144 BCS50145
4.145 BCS50146
4.146 BCS50147
4.147 BCS50148
4.148 BCS50149
4.149 BCS50150
4.150 BCS50151
4.151 BCS50152
4.152 BCS50153

Copyright © Huawei
Mobile Money
4.153 BCS50154
4.154 BCS50155
4.155 BCS50156
4.156 BCS50157
4.157 BCS50158
4.158 BCS50159
4.159 BCS50160
4.160 BCS50161
4.161 BCS50162
4.162 BCS50163
4.163 BCS50164
4.164 BCS50165
4.165 BCS50166
4.166 BCS50167
4.167 BCS50168
4.168 BCS50169
4.169 BCS50170
4.170 BCS50171
4.171 BCS50172
4.172 BCS50173
4.173 BCS50174
4.174 BCS50175
4.175 BCS50176
4.176 BCS50177
4.177 BCS50178
4.178 BCS50179
4.179 BCS50180
4.180 BCS50181
4.181 BCS50182
4.182 BCS50183
4.183 BCS50184
4.184 BCS50185
4.185 BCS50186

Copyright © Huawei
Mobile Money
4.186 BCS50187
4.187 BCS50189
4.188 BCS50190
4.189 BCS50191
4.190 BCS50192
4.191 BCS50193
4.192 BCS50194
4.193 BCS50195
4.194 BCS50196
4.195 BCS50197
4.196 BCS50198
4.197 BCS50199
4.198 BCS50200
4.199 BCS50201
4.200 BCS50202
4.201 BCS50203
4.202 BCS50204
4.203 BCS50205
4.204 BCS50206
4.205 BCS50207
4.206 BCS50208
4.207 BCS50209
4.208 BCS50210
4.209 BCS50211
4.210 BCS50212
4.211 BCS50213
4.212 BCS50214
4.213 BCS50215
4.214 BCS50216
4.215 BCS50217
4.216 BCS50218
4.217 BCS50219
4.218 BCS50220

Copyright © Huawei
Mobile Money
4.219 BCS50221
4.220 BCS50222
4.221 BCS50223
4.222 BCS50224
4.223 BCS50225
4.224 GV50000
4.225 GV50001
4.226 GV50002
4.227 GV50003
4.228 GV50004
4.229 GV50005
4.230 GV50006
4.231 GV50007
4.232 GV50008
4.233 GV50009
4.234 GV50010
4.235 GV50011
4.236 GV50012
4.237 GV50016
4.238 GV50013
4.239 GV50014
4.240 GV50015
4.241 GV50017
4.242 GV50018
4.243 GV50019
4.244 GV50020
4.245 GV50021
4.246 GV50022
4.247 GV50023
4.248 GV50024
4.249 GV50025
4.250 GV50026
4.251 GV50027

Copyright © Huawei
Mobile Money
4.252 GV50028
4.253 GV50029
4.254 GV50030
4.255 GV50031
4.256 GV50032
4.257 GV50033
4.258 GV50034
4.259 GV50035
4.260 GV50036
4.261 GV50037
4.262 GV50038
4.263 GV50039
4.264 GV50040
4.265 GV50041
4.266 GV50042
4.267 GV50043
4.268 GV50044
4.269 GV50045
4.270 GV50046
4.271 GV50047
4.272 GV50048
4.273 GV50049
4.274 GV50050
4.275 GV50051
4.276 GV50052
4.277 GV50053
4.278 GV50054
4.279 GV50055
4.280 GV50056
4.281 GV50057
4.282 GV50058
4.283 GV50059
4.284 GV50060

Copyright © Huawei
Mobile Money
4.285 GV50061
4.286 GV50062
4.287 GV50067
4.288 GV50068
4.289 GV50069
4.290 GV50070
4.291 GV50071
4.292 GV50072
4.293 GV50073
4.294 GV50074
4.295 GV50075
4.296 GV50076
4.297 GV50077
4.298 GV50078
4.299 GV50079
4.300 GV50080
4.301 GV50081
4.302 GV50082
4.303 GV50083
4.304 GV50084
4.305 GV50085
4.306 GV50086
4.307 GV50087
4.308 GV50089
4.309 GV50090
4.310 GV50091
4.311 GV50092
4.312 GV50093
4.313 GV50094
4.314 GV50095
4.315 GV50096
4.316 GV50097
4.317 GV50098

Copyright © Huawei
Mobile Money
4.318 GV50099
4.319 GV50100
4.320 GV50101
4.321 GV50102
4.322 GV50103
4.323 GV50104
4.324 GV50105
4.325 GV50106
4.326 GV50107
4.327 GV50108
4.328 GV50109
4.329 GV50110
4.330 GV50111
4.331 GV50112
4.332 GV50113
4.333 GV50114
4.334 GV50115
4.335 GV50116
4.336 GV50117
4.337 GV50118
4.338 GV50119
4.339 GV50120
4.340 GV50121
4.341 GV50122
4.342 GV50123
4.343 GV50124
4.344 GV50500
4.345 GV50501
4.346 IC11221
4.347 IC12001
4.348 IC13200
4.349 IC13307
4.350 IC14004

Copyright © Huawei
Mobile Money
4.351 IC19300
4.352 IC19301
4.353 IC19303
4.354 IC19306
4.355 IC19503
4.356 IC19506
4.357 IC40000
4.358 IC40004
4.359 IC40005
4.360 IC40006
4.361 IC40007
4.362 IC40009
4.363 IC40010
4.364 IC40011
4.365 IC40012
4.366 IC40013
4.367 IC40014
4.368 IC40015
4.369 IC40017
4.370 IC40018
4.371 IC40019
4.372 IC40020
4.373 IC40021
4.374 IC40022
4.375 IC40023
4.376 IC40024
4.377 IC40025
4.378 IC40026
4.379 IC40028
4.380 IC40029
4.381 IC40036
4.382 IC40037
4.383 IC40038

Copyright © Huawei
Mobile Money
4.384 IC40039
4.385 IC40040
4.386 IC40041
4.387 IC40042
4.388 IC40043
4.389 IC40044
4.390 IC40045
4.391 IC40046
4.392 IC40047
4.393 IC40048
4.394 IC40049
4.395 IC40050
4.396 IC40051
4.397 IC40052
4.398 IC40053
4.399 IC40054
4.400 IC40055
4.401 IC40056
4.402 IC40057
4.403 IC40058
4.404 IC40059
4.405 IC40060
4.406 IC40061
4.407 IC40062
4.408 IC40063
4.409 IC40064
4.410 IC40065
4.411 IC40066
4.412 IC40067
4.413 IC40068
4.414 IC40069
4.415 IC40070
4.416 IC40071

Copyright © Huawei
Mobile Money
4.417 IC40072
4.418 IC40073
4.419 IC40074
4.420 IC40075
4.421 IC40076
4.422 IC40077
4.423 IC40078
4.424 IC40079
4.425 IC40080
4.426 IC40081
4.427 IC40082
4.428 IC40083
4.429 IC40084
4.430 IC40085
4.431 IC40086
4.432 IC40087
4.433 IC40088
4.434 IC40089
4.435 IC40091
4.436 IC40092
4.437 IC40093
4.438 IC40097
4.439 IC40098
4.440 IC40109
4.441 IC40110
4.442 IC40111
4.443 IC40112
4.444 IC40113
4.445 IC40114
4.446 IC40115
4.447 IC40116
4.448 IC40121
4.449 IC40123

Copyright © Huawei
Mobile Money
4.450 IC40124
4.451 IC40125
4.452 IC40127
4.453 IC40128
4.454 IC40129
4.455 IC40130
4.456 IC40131
4.457 IC40132
4.458 IC40133
4.459 IC40134
4.460 IC40135
4.461 IC40136
4.462 IC40137
4.463 IC40138
4.464 IC40139
4.465 IC40140
4.466 IC40141
4.467 IC40142
4.468 IC40143
4.469 IC40144
4.470 IC40145
4.471 IC40146
4.472 IC40147
4.473 IC40149
4.474 IC40150
4.475 IC40151
4.476 IC40152
4.477 IC40153
4.478 IC40154
4.479 IC40155
4.480 IC40156
4.481 IC40157
4.482 IC40158

Copyright © Huawei
Mobile Money
4.483 IC40159
4.484 IC40160
4.485 IC40161
4.486 IC40162
4.487 IC40163
4.488 IC40164
4.489 IC40165
4.490 IC40166
4.491 IC40167
4.492 IC40168
4.493 IC40169
4.494 IC40171
4.495 IC40172
4.496 IC40189
4.497 IC40190
4.498 IC40191
4.499 IC40192
4.500 IC40193
4.501 IC40194
4.502 IC40195
4.503 IC40196
4.504 IC40197
4.505 IC40198
4.506 IC40199
4.507 IC40200
4.508 IC40201
4.509 IC40202
4.510 IC40203
4.511 IC40204
4.512 IC40205
4.513 IC40206
4.514 IC40207
4.515 IC40208

Copyright © Huawei
Mobile Money
4.516 IC40209
4.517 IC40210
4.518 IC40211
4.519 IC40212
4.520 IC40213
4.521 IC40214
4.522 IC40215
4.523 IC40216
4.524 IC40217
4.525 IC40218
4.526 IC40219
4.527 IC40238
4.528 IC40239
4.529 IC40240
4.530 IC40241
4.531 IC40243
4.532 IC40247
4.533 IC40248
4.534 IC40249
4.535 IC40250
4.536 IC40251
4.537 IC40252
4.538 IC40258
4.539 IC40254
4.540 IC40255
4.541 IC40256
4.542 IC40257
4.543 IC40253
4.544 IC40259
4.545 IC40260
4.546 IC40261
4.547 IC40264
4.548 IC40265

Copyright © Huawei
Mobile Money
4.549 IC40266
4.550 IC40267
4.551 IC40268
4.552 IC40269
4.553 IC40270
4.554 IC40271
4.555 IC40272
4.556 IC40273
4.557 IC40274
4.558 IC40275
4.559 IC40276
4.560 IC40286
4.561 IC40287
4.562 IC40288
4.563 IC40289
4.564 IC40290
4.565 IC40291
4.566 IC40292
4.567 IC40293
4.568 IC40295
4.569 IC40296
4.570 IC40297
4.571 IC40298
4.572 IC40299
4.573 IC40300
4.574 IC40301
4.575 IC40302
4.576 IC40303
4.577 IC40304
4.578 IC40316
4.579 IC40317
4.580 IC40318
4.581 IC40319

Copyright © Huawei
Mobile Money
4.582 IC40320
4.583 IC40321
4.584 IC40305
4.585 IC40306
4.586 IC40323
4.587 IC40326
4.588 IC40327
4.589 IC40336
4.590 IC40337
4.591 IC40338
4.592 IC40339
4.593 IC40340
4.594 IC40341
4.595 IC40342
4.596 IC40343
4.597 IC40345
4.598 IC40344
4.599 IC40346
4.600 IC40347
4.601 IC40348
4.602 IC40349
4.603 IC40350
4.604 IC40351
4.605 IC40352
4.606 IC40353
4.607 IC40354
4.608 IC40355
4.609 IC40356
4.610 IC40357
4.611 IC40358
4.612 IC40359
4.613 IC40360
4.614 IC40361

Copyright © Huawei
Mobile Money
4.615 IC40362
4.616 IC40363
4.617 IC40364
4.618 IC40365
4.619 IC40366
4.620 IC40367
4.621 IC40368
4.622 IC40369
4.623 IC40370
4.624 IC40371
4.625 IC40372
4.626 IC40373
4.627 IC40374
4.628 IC40375
4.629 IC40376
4.630 IC40377
4.631 IC40378
4.632 IC40379
4.633 IC40410
4.634 IC40411
4.635 IC40412
4.636 IC40426
4.637 IC40427
4.638 IC40428
4.639 IC40429
4.640 IC40430
4.641 IC40433
4.642 IC40434
4.643 IC40435
4.644 IC40436
4.645 IC40437
4.646 IC40438
4.647 IC40439

Copyright © Huawei
Mobile Money
4.648 IC40440
4.649 IC40441
4.650 IC40442
4.651 IC40443
4.652 IC40444
4.653 IC40445
4.654 IC40446
4.655 IC40447
4.656 IC40451
4.657 IC40452
4.658 IC40453
4.659 IC40454
4.660 IC40455
4.661 IC40456
4.662 IC40457
4.663 IC40458
4.664 IC40459
4.665 IC40469
4.666 IC40470
4.667 IC40471
4.668 IC40472
4.669 IC40473
4.670 IC40475
4.671 IC40476
4.672 IC40477
4.673 IC40478
4.674 IC40479
4.675 IC40480
4.676 IC40481
4.677 IC40482
4.678 IC40483
4.679 IC40484
4.680 IC40485

Copyright © Huawei
Mobile Money
4.681 IC40486
4.682 IC40487
4.683 IC40488
4.684 IC40489
4.685 IC40490
4.686 IC40491
4.687 IC40492
4.688 IC40493
4.689 IC40495
4.690 IC40496
4.691 IC40497
4.692 IC40498
4.693 IC40499
4.694 IC40500
4.695 IC40501
4.696 IC40502
4.697 IC40503
4.698 IC40504
4.699 IC40505
4.700 IC40506
4.701 IC40507
4.702 IC40508
4.703 IC40509
4.704 IC40510
4.705 IC40511
4.706 IC40512
4.707 IC40513
4.708 IC40517
4.709 IC40518
4.710 IC40519
4.711 IC40520
4.712 IC40521
4.713 IC40522

Copyright © Huawei
Mobile Money
4.714 IC40523
4.715 IC40524
4.716 IC40525
4.717 IC40526
4.718 IC40527
4.719 IC40540
4.720 IC40544
4.721 IC40545
4.722 IC40548
4.723 IC40549
4.724 IC40550
4.725 IC40551
4.726 IC40552
4.727 IC40553
4.728 IC40554
4.729 IC40555
4.730 IC40556
4.731 IC40557
4.732 IC40561
4.733 IC40562
4.734 IC40563
4.735 IC40564
4.736 IC40565
4.737 IC40566
4.738 IC40567
4.739 IC40568
4.740 IC40569
4.741 IC40570
4.742 IC40571
4.743 IC40572
4.744 IC40573
4.745 IC40574
4.746 IC40575

Copyright © Huawei
Mobile Money
4.747 IC40576
4.748 IC40577
4.749 IC40578
4.750 IC40580
4.751 IC40581
4.752 IC40582
4.753 IC40583
4.754 IC40584
4.755 IC40585
4.756 IC40586
4.757 IC40587
4.758 IC40588
4.759 IC40589
4.760 IC40590
4.761 IC40591
4.762 IC40592
4.763 IC40593
4.764 IC40596
4.765 IC40597
4.766 IC40598
4.767 IC40599
4.768 IC40600
4.769 IC40601
4.770 IC40602
4.771 IC40603
4.772 IC40604
4.773 IC40608
4.774 IC40609
4.775 IC40610
4.776 IC40611
4.777 IC40612
4.778 IC40613
4.779 IC40619

Copyright © Huawei
Mobile Money
4.780 IC40621
4.781 IC40625
4.782 IC40626
4.783 IC40627
4.784 IC40628
4.785 IC40629
4.786 IC40630
4.787 IC40631
4.788 IC40632
4.789 IC40635
4.790 IC40636
4.791 IC40637
4.792 IC40638
4.793 IC40639
4.794 IC40640
4.795 IC40641
4.796 IC40642
4.797 IC40643
4.798 IC40644
4.799 IC40645
4.800 IC40646
4.801 IC40647
4.802 IC40648
4.803 IC40649
4.804 IC40650
4.805 IC40651
4.806 IC40652
4.807 IC40653
4.808 IC40654
4.809 IC40655
4.810 IC40656
4.811 IC40657
4.812 IC40658

Copyright © Huawei
Mobile Money
4.813 IC40659
4.814 IC40660
4.815 IC40661
4.816 IC40662
4.817 IC40663
4.818 IC40664
4.819 IC40665
4.820 IC40666
4.821 IC40667
4.822 IC50001
4.823 IC50002
4.824 IC50003
4.825 IC50004
4.826 IC50005
4.827 IC50006
4.828 IC50007
4.829 IC50008
4.830 IC50009
4.831 IC50010
4.832 IC50011
4.833 IC50012
4.834 IC50013
4.835 IC50014
4.836 IC50015
4.837 IC50016
4.838 IC50017
4.839 IC50018
4.840 IC50019
4.841 IC50020
4.842 IC50021
4.843 IC50022
4.844 IC50023
4.845 IC50024

Copyright © Huawei
Mobile Money
4.846 IC50025
4.847 IC50026
4.848 IC50027
4.849 IC50028
4.850 IC50029
4.851 IC50030
4.852 IC50031
4.853 IC50032
4.854 IC50033
4.855 IC50034
4.856 IC50035
4.857 IC50036
4.858 IC50037
4.859 IC50038
4.860 IC50039
4.861 IC50040
4.862 IC50041
4.863 IC50042
4.864 IC50043
4.865 IC50044
4.866 IC50045
4.867 IC50046
4.868 IC50047
4.869 IC50048
4.870 IC50049
4.871 IC50050
4.872 IC50051
4.873 IC50052
4.874 IC50053
4.875 IC50054
4.876 IC50055
4.877 IC50056
4.878 IC50057

Copyright © Huawei
Mobile Money
4.879 IC50058
4.880 IC50059
4.881 IC50060
4.882 IC50061
4.883 IC50062
4.884 IC50063
4.885 IC50064
4.886 IC50065
4.887 IC50066
4.888 IC50067
4.889 IC50068
4.890 IC50069
4.891 IC50070
4.892 IC50071
4.893 IC50072
4.894 IC50073
4.895 IC50074
4.896 IC50075
4.897 IC50076
4.898 IC50077
4.899 IC50078
4.900 IC50079
4.901 IC50080
4.902 IC50081
4.903 IC50082
4.904 IC50083
4.905 IC50084
4.906 IC50085
4.907 IC50086
4.908 IC50090
4.909 IC50091
4.910 IC50092
4.911 IC50093

Copyright © Huawei
Mobile Money
4.912 LP10000
4.913 LP10001
4.914 LP10002
4.915 LP10003
4.916 LP10004
4.917 LP10005
4.918 LP10006
4.919 LP10007
4.920 LP10008
4.921 LP10009
4.922 LP10010
4.923 LP10011
4.924 LP10012
4.925 LP10013
4.926 LP10014
4.927 LP10015
4.928 LP10016
4.929 LP10017
4.930 LP10018
4.931 LP10019
4.932 LP10020
4.933 LP10021
4.934 LP10022
4.935 LP10023
4.936 LP10024
4.937 LP10025
4.938 LP10026
4.939 LP10027
4.940 LP10028
4.941 LP10029
4.942 LP10030
4.943 LP10031
4.944 LP10032

Copyright © Huawei
Mobile Money
4.945 LP10033
4.946 LP10034
4.947 LP10035
4.948 LP10036
4.949 LP10037
4.950 LP10038
4.951 LP10039
4.952 LP10040
4.953 LP10041
4.954 LP10042
4.955 LP10043
4.956 LP10044
4.957 LP10045
4.958 LP10046
4.959 LP10047
4.960 LP10048
4.961 LP10049
4.962 LP10050
4.963 LP10051
4.964 LP10052
4.965 LP10053
4.966 LP10054
4.967 TC30000
4.968 TC30001
4.969 TC30002
4.970 TC30003
4.971 TC30004
4.972 TC30005
4.973 TC30006
4.974 TC30007
4.975 TC30008
4.976 TC30009
4.977 TC30010

Copyright © Huawei
Mobile Money
4.978 TC30011
4.979 TC30012
4.980 TC30013
4.981 TC30065
4.982 TC30066
4.983 TC30067
4.984 TC30068
4.985 TC30070
4.986 TC30071
4.987 TC30072
4.988 TC30073
4.989 TC30074
4.990 TC30075
4.991 TC30076
4.992 TC30077
4.993 TC30087
4.994 TC30088
4.995 TC30090
4.996 TC30091
4.997 TC30100
4.998 TC30101
4.999 TC30102
4.1000 TC30104
4.1001 TC30105
4.1002 TC30111
4.1003 TC30112
4.1004 TC30113
4.1005 TC30114
4.1006 TC30115
4.1007 TC30116
4.1008 TC30117
4.1009 TC30118
4.1010 TC30119

Copyright © Huawei
Mobile Money
4.1011 TC30120
4.1012 TC30121
4.1013 TC30122
4.1014 TC30123
4.1015 TC30124
4.1016 TC30125
4.1017 TC30126
4.1018 TC30127
4.1019 TC30128
4.1020 TC30129
4.1021 TC30131
4.1022 TC30132
4.1023 TC30133
4.1024 TC30134
4.1025 TC30135
4.1026 TC30136
4.1027 TC30137
4.1028 TC30138
4.1029 TC30139
4.1030 TC30140
4.1031 TC30141
4.1032 TC30142
4.1033 TC30143
4.1034 TC30144
4.1035 TC30145
4.1036 TC30146
4.1037 TC30147
4.1038 TC30148
4.1039 TC30150
4.1040 TC30151
4.1041 TC30152
4.1042 TC30153
4.1043 TC30154

Copyright © Huawei
Mobile Money
4.1044 TC30155
4.1045 TC30156
4.1046 TC30158
4.1047 TC30179
4.1048 TC30180
4.1049 TC30181
4.1050 TC30182
4.1051 TC30183
4.1052 TC30189
4.1053 TC30190
4.1054 TC30191
4.1055 TC30192
4.1056 TC30193
4.1057 TC30194
4.1058 TC30195
4.1059 TC30197
4.1060 TC30198
4.1061 TC30199
4.1062 TC30200
4.1063 TC30201
4.1064 TC30202
4.1065 TC30203
4.1066 TC30204
4.1067 TC30205
4.1068 TC30206
4.1069 TC30207
4.1070 TC30211
4.1071 TC30212
4.1072 TC30213
4.1073 TC30216
4.1074 TC30217
4.1075 TC30218
4.1076 TC30219

Copyright © Huawei
Mobile Money
4.1077 TC30220
4.1078 TC30221
4.1079 TC30222
4.1080 TC30238
4.1081 TC30239
4.1082 TC30240
4.1083 TC30241
4.1084 TC30242
4.1085 TC30243
4.1086 TC30244
4.1087 TC30245
4.1088 TC30246
4.1089 TC30247
4.1090 TC30248
4.1091 TC30249
4.1092 TC30250
4.1093 TC30251
4.1094 TC30252
4.1095 TC30253
4.1096 TC30254
4.1097 TC30255
4.1098 TC30256
4.1099 TC30257
4.1100 TC30258
4.1101 TC30259
4.1102 TC30260
4.1103 TC30261
4.1104 TC30262
4.1105 TC30263
4.1106 TC30264
4.1107 TC30265
4.1108 TC30266
4.1109 TC30267

Copyright © Huawei
Mobile Money
4.1110 TC30268
4.1111 TC30269
4.1112 TC30270
4.1113 TC30271
4.1114 TC30272
4.1115 TC30273
4.1116 TC30274
4.1117 TC30275
4.1118 TC30276
4.1119 TC30277
4.1120 TC30278
4.1121 TC30279
4.1122 TC30280
4.1123 TC30281
4.1124 TC30282
4.1125 TC30283
4.1126 TC30284
4.1127 TC30285
4.1128 TC30286
4.1129 TC30287
4.1130 TC30288
4.1131 TC30292
4.1132 TC30293
4.1133 TC30294
4.1134 TC30295
4.1135 TC30311
4.1136 TC30316
4.1137 TC30317
4.1138 TC30318
4.1139 TC30319
4.1140 TC30320
4.1141 TC30321
4.1142 TC30322

Copyright © Huawei
Mobile Money
4.1143 TC30323
4.1144 TC30324
4.1145 TC30325
4.1146 TC30326
4.1147 TC30327
4.1148 TC30328
4.1149 TC30329
4.1150 TC30330
4.1151 TC30331
4.1152 TC30332
4.1153 TC30333
4.1154 TC30334
4.1155 TC30335
4.1156 TC30340
4.1157 TC30341
4.1158 TC30351
4.1159 TC30352
4.1160 TC30354
4.1161 TC30355
4.1162 TC30358
4.1163 TC30359
4.1164 TC30360
4.1165 TC30361
4.1166 TC30362
4.1167 TC30363
4.1168 TC30364
4.1169 TC30365
4.1170 TC30366
4.1171 TC30374
4.1172 TC30375
4.1173 TC30380
4.1174 TC30381
4.1175 TC30382

Copyright © Huawei
Mobile Money
4.1176 TC30383
4.1177 TC30384
4.1178 TC30385
4.1179 TC30386
4.1180 TC30387
4.1181 TC30388
4.1182 TC30389
4.1183 TC30398
4.1184 TC30399
4.1185 TC30400
4.1186 TC30401
4.1187 TC30402
4.1188 TC30403
4.1189 TC30404
4.1190 TC30405
4.1191 TC30406
4.1192 TC30407
4.1193 TC30408
4.1194 TC30409
4.1195 TC30410
4.1196 TC30414
4.1197 TC30416
4.1198 TC30417
4.1199 TC30418
4.1200 TC30419
4.1201 TC30420
4.1202 TC30421
4.1203 TC30422
4.1204 TC30423
4.1205 TC30424
4.1206 TC30425
4.1207 TC30426
4.1208 TC30427

Copyright © Huawei
Mobile Money
4.1209 TC30430
4.1210 TC30431
4.1211 TC30432
4.1212 TC30433
4.1213 TC30434
4.1214 TC30435
4.1215 TC30436
4.1216 TC30437
4.1217 TC30438
4.1218 TC30439
4.1219 TC30440
4.1220 TC30441
4.1221 TC30442
4.1222 TC30443
4.1223 TC30444
4.1224 TC30445
4.1225 TC30446
4.1226 TC30447
4.1227 TC30448
4.1228 TC30449
4.1229 TC30450
4.1230 TC30451
4.1231 TC30452
4.1232 TC30453
4.1233 TC30454
4.1234 TC30455
4.1235 TC30456
4.1236 TC30457
4.1237 TC30458
4.1238 TC30459
4.1239 TC30460
4.1240 TC30461
4.1241 TC30462

Copyright © Huawei
Mobile Money
4.1242 TC30463
4.1243 TC30464
4.1244 TC30465
4.1245 TC30466
4.1246 TC30467
4.1247 TC30468
4.1248 TC30469
4.1249 TC30470
4.1250 TC30471
4.1251 TC30472
4.1252 TC30475
4.1253 TC30484
4.1254 TC30489
4.1255 TC30490
4.1256 TC30491
4.1257 TC30492
4.1258 TC30493
4.1259 TC30494
4.1260 TC30497
4.1261 TC30498
4.1262 TC30499
4.1263 TC30500
4.1264 TC30501
4.1265 TC30502
4.1266 TC30503
4.1267 TC30504
4.1268 TC30505
4.1269 TC30506
4.1270 TC30507
4.1271 TC30508
4.1272 TC30509
4.1273 TC30510
4.1274 TC30511

Copyright © Huawei
Mobile Money
4.1275 TC30512
4.1276 TC30513
4.1277 TC30514
4.1278 TC30516
4.1279 TC30518
4.1280 TC30519
4.1281 TC30522
4.1282 TC30523
4.1283 TC30524
4.1284 TC30525
4.1285 TC30526
4.1286 TC30527
4.1287 TC30528
4.1288 TC30529
4.1289 TC30530
4.1290 TC30531
4.1291 TC30532
4.1292 TC30533
4.1293 TC30534
4.1294 TC30535
4.1295 TC30536
4.1296 TC30537
4.1297 TC30538
4.1298 TC30539
4.1299 TC30540
4.1300 TC30545
4.1301 TC30546
4.1302 TC30547
4.1303 TC30549
4.1304 TC30550
4.1305 TC30551
4.1306 TC30552
4.1307 TC30553

Copyright © Huawei
Mobile Money
4.1308 TC30554
4.1309 TC30557
4.1310 TC30558
4.1311 TC50001
4.1312 TC50002
4.1313 TC50003
4.1314 TC50004
4.1315 TC50005
4.1316 TC50006
4.1317 TC50007
4.1318 TC50008
4.1319 TC50009
4.1320 TC50010
4.1321 TC50011
4.1322 TC50012
4.1323 TC50013
4.1324 TC50014
4.1325 TC50015
4.1326 TC50016
4.1327 TC50017
4.1328 TC50018
4.1329 TC50019
4.1330 TC50020
4.1331 TC50021
4.1332 TC50022
4.1333 TC50023
4.1334 TC50024
4.1335 TC50025
4.1336 TC50026
4.1337 TC50027
4.1338 TC50028
4.1339 TC50029
4.1340 TC50030

Copyright © Huawei
Mobile Money
4.1341 TC50031
4.1342 TC50032
4.1343 TC50033
4.1344 TC50034
4.1345 TC50035
4.1346 TC50036
4.1347 TC50037
4.1348 TC50038
4.1349 TC50039
4.1350 TC50040
4.1351 TC50041
4.1352 TC50042
4.1353 TC50043
4.1354 TC50044
4.1355 TC50045
4.1356 TC50046
4.1357 TC50047
4.1358 TC50048
4.1359 TC50049
4.1360 TC50050
4.1361 TC50051
4.1362 TC50052
4.1363 TC50053
4.1364 TC50054
4.1365 TC50055
4.1366 TC50056
4.1367 TC50057
4.1368 TC50058
4.1369 TC50060
4.1370 TC50061
4.1371 TC50062
4.1372 TC50063
4.1373 TC50064

Copyright © Huawei
Mobile Money
4.1374 TP30000
4.1375 TP30002
4.1376 TP30003
4.1377 TP30004
4.1378 TP30005
4.1379 TP30006
4.1380 TP30008
4.1381 TP30011
4.1382 TP30012
4.1383 TP30013
4.1384 TP30014
4.1385 TP30015
4.1386 TP30016
4.1387 TP30017
4.1388 TP30018
4.1389 TP30019
4.1390 TP30020
4.1391 TP30021
4.1392 TP30022
4.1393 TP30023
4.1394 TP30024
4.1395 TP30025
4.1396 TP30027
4.1397 TP30028
4.1398 TP30031
4.1399 TP30032
4.1400 TP30033
4.1401 TP30034
4.1402 TP30035
4.1403 TP30036
4.1404 TP30037
4.1405 TP30038
4.1406 TP30039

Copyright © Huawei
Mobile Money
4.1407 TP30044
4.1408 TP30045
4.1409 TP30046
4.1410 TP30047
4.1411 TP30048
4.1412 TP30049
4.1413 TP30051
4.1414 TP30052
4.1415 TP30053
4.1416 TP30054
4.1417 TP30055
4.1418 TP30056
4.1419 TP30057
4.1420 TP30058
4.1421 TP30059
4.1422 TP30060
4.1423 TP30061
4.1424 TP30062
4.1425 TP30063
4.1426 TP30064
4.1427 TP30065
4.1428 TP30066
4.1429 TP30067
4.1430 TP30068
4.1431 TP30069
4.1432 TP30070
4.1433 TP30071
4.1434 TP30072
4.1435 TP30073
4.1436 TP30075
4.1437 TP30076
4.1438 TP30077
4.1439 TP30078

Copyright © Huawei
Mobile Money
4.1440 TP30079
4.1441 TP30081
4.1442 TP30083
4.1443 TP30084
4.1444 TP30085
4.1445 TP30086
4.1446 TP30091
4.1447 TP30092
4.1448 TP30093
4.1449 TP30094
4.1450 TP30095
4.1451 TP30096
4.1452 TP30110
4.1453 TP30111
4.1454 TP30112
4.1455 TP30113
4.1456 TP30114
4.1457 TP30115
4.1458 TP30116
4.1459 TP30117
4.1460 TP30119
4.1461 TP30120
4.1462 TP30123
4.1463 TP30124
4.1464 TP30125
4.1465 TP30127
4.1466 TP30130
4.1467 TP30131
4.1468 TP30136
4.1469 TP30140
4.1470 TP30141
4.1471 TP30150
4.1472 TP30160

Copyright © Huawei
Mobile Money
4.1473 TP30170
4.1474 TP30201
4.1475 TP30202
4.1476 TP30203
4.1477 TP30204
4.1478 TP30205
4.1479 TP30207
4.1480 TP30208
4.1481 TP30209
4.1482 TP30210
4.1483 TP30211
4.1484 TP30230
4.1485 TP30231
4.1486 TP30300
4.1487 TP30301
4.1488 TP30302
4.1489 TP30303
4.1490 TP30400
4.1491 TP30401
4.1492 TP30402
4.1493 TP30403
4.1494 TP30404
4.1495 TP30405
4.1496 TP30406
4.1497 TP30407
4.1498 TP30408
4.1499 TP30409
4.1500 TP30450
4.1501 TP30454
4.1502 TP30455
4.1503 TP35002
4.1504 TP35005
4.1505 TP35006

Copyright © Huawei
Mobile Money
4.1506 TP35007
4.1507 TP35008
4.1508 TP35009
4.1509 TP35010
4.1510 TP35011
4.1511 TP35013
4.1512 TP35014
4.1513 TP36500
4.1514 TP36501
4.1515 TP36503
4.1516 TP36504
4.1517 TP36506
4.1518 TP36512
4.1519 TP36513
4.1520 TP36514
4.1521 TP36515
4.1522 TP36516
4.1523 TP36521
4.1524 TP36522
4.1525 TP36523
4.1526 TP36524
4.1527 TP39003
4.1528 TP39004
4.1529 TP39040
4.1530 TP39041
4.1531 TP39042
4.1532 TP39051
4.1533 TP39998
4.1534 TP39999
4.1535 TP40000
4.1536 TP40001
4.1537 TP40002
4.1538 TP40003

Copyright © Huawei
Mobile Money
4.1539 TP40004
4.1540 TP40005
4.1541 TP40006
4.1542 TP40007
4.1543 TP40008
4.1544 TP40009
4.1545 TP40010
4.1546 TP40011
4.1547 TP40012
4.1548 TP40013
4.1549 TP40014
4.1550 TP40015
4.1551 TP40016
4.1552 TP40017
4.1553 TP40018
4.1554 TP40019
4.1555 TP40020
4.1556 TP40021
4.1557 TP40022
4.1558 TP40023
4.1559 TP40024
4.1560 TP40025
4.1561 TP40026
4.1562 TP40027
4.1563 TP40028
4.1564 TP40029
4.1565 TP40030
4.1566 TP40031
4.1567 TP40032
4.1568 TP40033
4.1569 TP40034
4.1570 TP40035
4.1571 TP40036

Copyright © Huawei
Mobile Money
4.1572 TP40037
4.1573 TP40038
4.1574 TP40039
4.1575 TP40040
4.1576 TP40041
4.1577 TP40042
4.1578 TP40043
4.1579 TP40045
4.1580 TP40046
4.1581 TP40047
4.1582 TP40048
4.1583 TP40049
4.1584 TP40050
4.1585 TP40051
4.1586 TP40052
4.1587 TP40053
4.1588 TP40054
4.1589 TP40055
4.1590 TP40056
4.1591 TP40057
4.1592 TP40058
4.1593 TP40059
4.1594 TP40060
4.1595 TP40061
4.1596 TP40062
4.1597 TP40063
4.1598 TP40064
4.1599 TP40065
4.1600 TP40066
4.1601 TP40067
4.1602 TP40069
4.1603 TP40070
4.1604 TP40071

Copyright © Huawei
Mobile Money
4.1605 TP40072
4.1606 TP40073
4.1607 TP40074
4.1608 TP40075
4.1609 TP40076
4.1610 TP40077
4.1611 TP40078
4.1612 TP40079
4.1613 TP40080
4.1614 TP40081
4.1615 TP40082
4.1616 TP40083
4.1617 TP40085
4.1618 TP40087
4.1619 TP40088
4.1620 TP40089
4.1621 TP40090
4.1622 TP40091
4.1623 TP40092
4.1624 TP40093
4.1625 TP40094
4.1626 TP40095
4.1627 TP40096
4.1628 TP40097
4.1629 TP40098
4.1630 TP40099
4.1631 TP40100
4.1632 TP40101
4.1633 TP40102
4.1634 TP40103
4.1635 TP40104
4.1636 TP40105
4.1637 TP40106

Copyright © Huawei
Mobile Money
4.1638 TP40107
4.1639 TP40108
4.1640 TP40109
4.1641 TP40110
4.1642 TP40111
4.1643 TP40112
4.1644 TP40113
4.1645 TP40114
4.1646 TP40115
4.1647 TP40116
4.1648 TP40117
4.1649 TP40118
4.1650 TP40147
4.1651 TP40148
4.1652 TP40149
4.1653 TP40150
4.1654 TP40151
4.1655 TP40119
4.1656 TP40120
4.1657 TP40121
4.1658 TP40122
4.1659 TP40123
4.1660 TP40124
4.1661 TP40125
4.1662 TP40126
4.1663 TP40127
4.1664 TP40128
4.1665 TP40129
4.1666 TP40130
4.1667 TP40131
4.1668 TP40132
4.1669 TP40133
4.1670 TP40134

Copyright © Huawei
Mobile Money
4.1671 TP40135
4.1672 TP40136
4.1673 TP40137
4.1674 TP40138
4.1675 TP40139
4.1676 TP40140
4.1677 TP40141
4.1678 TP40142
4.1679 TP40143
4.1680 TP40144
4.1681 TP40145
4.1682 TP40146
4.1683 TP40152
4.1684 TP40153
4.1685 TP40154
4.1686 TP40155
4.1687 TP40156
4.1688 TP40157
4.1689 TP40159
4.1690 TP40162
4.1691 TP40163
4.1692 TP40164
4.1693 TP40165
4.1694 TP40166
4.1695 TP40167
4.1696 TP40168
4.1697 TP40169
4.1698 TP40170
4.1699 TP40171
4.1700 TP40172
4.1701 TP40173
4.1702 TP40174
4.1703 TP40175

Copyright © Huawei
Mobile Money
4.1704 TP40176
4.1705 TP40177
4.1706 TP40178
4.1707 TP40179
4.1708 TP40180
4.1709 TP40181
4.1710 TP40182
4.1711 TP40184
4.1712 TP40185
4.1713 TP40186
4.1714 TP40187
4.1715 TP40188
4.1716 TP40189
4.1717 TP40190
4.1718 TP40191
4.1719 TP40192
4.1720 TP40193
4.1721 TP40194
4.1722 TP40199
4.1723 TP40200
4.1724 TP40201
4.1725 TP40202
4.1726 TP40203
4.1727 TP40204
4.1728 TP40205
4.1729 TP40206
4.1730 TP40207
4.1731 TP40208
4.1732 TP40209
4.1733 TP40210
4.1734 TP40211
4.1735 TP40212
4.1736 TP40213

Copyright © Huawei
Mobile Money
4.1737 TP40214
4.1738 TP40215
4.1739 TP40216
4.1740 TP40217
4.1741 TP40218
4.1742 TP40219
4.1743 TP40220
4.1744 TP40222
4.1745 TP40223
4.1746 TP40224
4.1747 TP40225
4.1748 TP40228
4.1749 TP40229
4.1750 TP40230
4.1751 TP40231
4.1752 TP40232
4.1753 TP40233
4.1754 TP40234
4.1755 TP40235
4.1756 TP40236
4.1757 TP40237
4.1758 TP40238
4.1759 TP40239
4.1760 TP40240
4.1761 TP40241
4.1762 TP40242
4.1763 TP40243
4.1764 TP40244
4.1765 TP40245
4.1766 TP40246
4.1767 TP40247
4.1768 TP40248
4.1769 TP40249

Copyright © Huawei
Mobile Money
4.1770 TP40250
4.1771 TP40251
4.1772 TP40252
4.1773 TP40253
4.1774 TP40254
4.1775 TP40255
4.1776 TP40256
4.1777 TP40261
4.1778 TP40262
4.1779 TP40263
4.1780 TP40267
4.1781 TP40268
4.1782 TP40269
4.1783 TP40270
4.1784 TP40271
4.1785 TP40272
4.1786 TP40273
4.1787 TP40274
4.1788 TP40275
4.1789 TP40276
4.1790 TP40277
4.1791 TP40278
4.1792 TP40279
4.1793 TP40289
4.1794 TP40290
4.1795 TP40291
4.1796 TP40292
4.1797 TP40293
4.1798 TP40294
4.1799 TP40295
4.1800 TP40296
4.1801 TP40297
4.1802 TP40260

Copyright © Huawei
Mobile Money
4.1803 TP40264
4.1804 TP40265
4.1805 TP40298
4.1806 TP40299
4.1807 TP40300
4.1808 TP40301
4.1809 TP40302
4.1810 TP40303
4.1811 TP40304
4.1812 TP40305
4.1813 TP40306
4.1814 TP40307
4.1815 TP40308
4.1816 TP40221
4.1817 TP40226
4.1818 TP40227
4.1819 TP40257
4.1820 TP40258
4.1821 TP40259
4.1822 TP40266
4.1823 TP40280
4.1824 TP40281
4.1825 TP40282
4.1826 TP40283
4.1827 TP40284
4.1828 TP40285
4.1829 TP40286
4.1830 TP40287
4.1831 TP40288
4.1832 TS20001
4.1833 TS20002
4.1834 TS20003
4.1835 TS20004

Copyright © Huawei
Mobile Money
4.1836 TS20005
4.1837 TS20006
4.1838 TS20008
4.1839 TS20009
4.1840 TS20010
4.1841 TS24003
4.1842 TS24004
4.1843 TS24005
4.1844 TS24100
4.1845 TS28007
4.1846 TS28008
4.1847 TS28009
4.1848 TS28010
4.1849 TS28011
4.1850 TS28012
4.1851 TS28013
4.1852 TS28300
4.1853 TS39600
4.1854 TS39601
4.1855 TS39602
4.1856 TS39603
4.1857 TS39604
4.1858 TS39605
4.1859 TS39606
4.1860 TS39607
4.1861 TS39608
4.1862 TS39609
4.1863 TS39611
4.1864 RN36000
4.1865 RN36001
4.1866 RN36014
4.1867 RN36015
4.1868 RN36018

Copyright © Huawei
Mobile Money
4.1869 RN36025
4.1870 RN36027
4.1871 RN36029
4.1872 RN36030
4.1873 RN36031
4.1874 RN36032
4.1875 RN36034
4.1876 RN36035
4.1877 RN36036
4.1878 RN36037
4.1879 RN36038
4.1880 RN36039
4.1881 RN36040
4.1882 RN36041
4.1883 RN36042
4.1884 RN36043
4.1885 RN36044
4.1886 RN36045
4.1887 RN36046
4.1888 RN36047
4.1889 RN36049
4.1890 RN36052
4.1891 RN36055
4.1892 RN36056
4.1893 RN36058
4.1894 RN36060
4.1895 RN36061
4.1896 RN36062
4.1897 RN36070
4.1898 RN36071
4.1899 RN36072
4.1900 WF55006

Copyright © Huawei
Mobile Money
4.1 BCS50001
Description
The incentive rule does not exist.
Scenario
This error is reported when the incentive rule does not exist.
Access Channel
POS
Possible Causes
The incentive rule does not exist.
Procedure
Check the correctness of the entered data.
4.2 BCS50002
Description
The incentive rule has expired.
Scenario
This error is reported when the incentive rule has expired.
Access Channel
POS
Possible Causes
The incentive rule has expired.
Procedure
Select a valid incentive rule.

Copyright © Huawei
Mobile Money
4.3 BCS50003
Description
The incentive rule is not released.
Scenario
This error is reported when the incentive rule is not released.
Access Channel
POS
Possible Causes
The incentive rule is not released.
Procedure
Release the incentive rule on the configuration page before using the rule.
4.4 BCS50004
Description
The subscriber has subscribed to the incentive rule.
Scenario
This error is reported when the incentive rule has been subscribed to by the organization.
Access Channel
POS
Possible Causes
The subscriber has subscribed to the incentive rule.
Procedure
Subscribe to other incentive rules.

Copyright © Huawei
Mobile Money
4.5 BCS50005
Description
The requested incentive payment detail information does not exist.
Scenario
This error is reported when the requested incentive payment detail information does not exist.
Access Channel
POS
Possible Causes
The requested incentive payment detail information does not exist.
Procedure
Check the data correctness and initiate the operation again.
4.6 BCS50006
Description
Parameters in the incentive file import request are incorrect.
Scenario
This error is reported when the parameters in the incentive file import request are incorrect.
Access Channel
POS
Possible Causes
Parameters in the incentive file import request are incorrect.
Procedure
Check the parameters and try again.

Copyright © Huawei
Mobile Money
4.7 BCS50007
Description
The organization does not exist.
Scenario
This error is reported when the organization does not exist.
Access Channel
POS
Possible Causes
Procedure
Ensure that the entered organization information is correct.
4.8 BCS50008
Description
The file type configured for incentive file import does not exist.
Scenario
This error is reported when the file type configured for incentive file import does not exist.
Access Channel
POS
Possible Causes
The file type configured for incentive file import does not exist.
Procedure
Ensure that the file type configured for file import and the request data are correct.

Copyright © Huawei
Mobile Money
4.9 BCS50009
Description
Failed to import the incentive statement.
Scenario
This error is reported when the incentive statement is failed to import.
Access Channel
POS
Possible Causes
Procedure
4.10 BCS50010
Description
The current asynchronous task cannot be queried based on the order ID.
Scenario
This error is reported when the OutBound message is called back after the transaction is
completed but the OutBound asynchronous task fails to be loaded based on the order ID.
Access Channel
POS
Possible Causes
The current asynchronous task cannot be queried based on the order ID.
Procedure
Check the entered order ID information.

Copyright © Huawei
Mobile Money
4.11 BCS50011
Description
No organization associated with the entered organization short code {0} is found in the
system.
{0} indicates a short code value.
Scenario
This error is reported if the organization short code entered in the Dompetky Bill Payment
transaction request does not exist.
Access Channel
POS
Possible Causes
The entered organization short code {0} does not exist.
Procedure
Check the entered organization short code.
4.12 BCS50012
Description
The location verification fails.
Scenario
This error is reported when a request requiring location verification is initiated but the
location verification fails.
Access Channel
USSD, APP
Possible Causes
A request requiring location verification is initiated but the location verification fails.
Procedure
Check whether the current location belongs to the home area of the user.

Copyright © Huawei
Mobile Money
4.13 BCS50013
Description
The MSISDN verification fails.
Scenario
This error is reported when a transaction is initiated but no MSISDN is entered.
Access Channel
USSD, APP
Possible Causes
A transaction is initiated but no MSISDN is entered.
Procedure
Ensure that the MSISDN is entered.
4.14 BCS50014
Description
The KYC field {1} of the organization whose short code is {0} is empty.
{0} indicates a short code.

{1} indicates a KYC field name.
Scenario
This error is reported when the corresponding KYC is not configured for the current
organization.
Access Channel
POS
Possible Causes
The corresponding KYC is not configured for the current organization.
Procedure
Check the KYC configuration of the current organization.

Copyright © Huawei
Mobile Money
4.15 BCS50015
Description
The EFT file fails to be exported because the file name is the same as that of an existing EFT
file on the SFTP server.
Scenario
This error is reported in the following scenario: When exporting the EFT file, the system
detects that the exported EFT file name is the same as that of an existing EFT file on the SFTP
server.
Access Channel
Web
Possible Causes
The exported EFT file name is the same as that of an existing EFT file on the SFTP server.
Procedure
Choose My Functions > Finance > Reconciliation Management > Finance Parameter >
Financial Generic Parameters and check whether the Overwirte same EFT file function is
enabled.
4.16 BCS50016
Description
The system receives a failure response from the third-party system and an AG policy is
configured not to process this fault.
Scenario
The system receives a failure response from the third-party system and an AG policy is
configured not to process this fault.
Access Channel
Web, API, STK, USSD, APP
Possible Causes
The outbound message sending fails or times out or the outbound message is successfully
sent. The third-party system returns a failure response and the AG configures a background
policy not to process the fault.

Copyright © Huawei
Mobile Money
Procedure
View failure details in the outbound message log table and perform the corresponding
operation.
4.17 BCS50017
Description
The system receives a failure response from the third-party system, an AG policy is
configured to reverse the transaction, and the reversal is successful.
Scenario
configured to reverse the transaction, and the reversal is successful.
Access Channel
Possible Causes
sent. The third-party system returns a failure response, the AG configures a background policy
to reverse the transaction, and the reversal is successful.
Procedure
operation.
4.18 BCS50018
Description
configured to reverse the transaction, and the reversal fails.
Scenario
configured to reverse the transaction, and the reversal fails.
Access Channel

Copyright © Huawei
Mobile Money
Possible Causes
sent. The third-party system returns a failure response, the AG configures a background policy
to reverse the transaction, and the reversal fails.
Procedure
operation.
4.19 BCS50019
Description
The third-party system fails to verify the recharge number.
Scenario
This error is reported when the recharge number status fails to be verified.
Access Channel
Possible Causes
The third-party system fails to verify the recharge number.
Procedure
Ensure that the entered number is correct.
4.20 BCS50020
Description
The manual payment fails.
Scenario
This error is reported if the manual payment fails.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The manual payment fails.
Procedure
Perform the operation again after checking the balance and point rewarding.
4.21 BCS50021
Description
The operator fails to be closed because the operator has to-be-processed tasks.
Scenario
This error is reported when the status of an operator with to-be-processed tasks is changed to
Closed.
Access Channel
POS
Possible Causes
The status of an operator with to-be-processed tasks is changed to Closed.
Procedure
Process the tasks and then close the operator.
4.22 BCS50022
Description
The organization fails to be closed because it has uncompleted commission roll-up tasks.
Scenario
This error is reported when the organization to be closed has uncompleted commission roll-up
tasks.
Access Channel
POS
Possible Causes
The organization to be closed has uncompleted commission roll-up tasks.

Copyright © Huawei
Mobile Money
Procedure
Close the organization after all commission roll-up tasks of the organization are completed.
4.23 BCS50024
Description
The third-party system does not return an authentication result in a specified time period.
Scenario
In a buy goods transaction, the third-party verification times out.
Access Channel
Web, USSD, API, STK
Possible Causes
The AG returns a message indicating a third-party authentication timeout.
Procedure
Send the buy goods request again.
4.24 BCS50025
Description
The client ID or token is incorrect.
Scenario
This error is reported when the third-party system fails to verify the token through the
Validate Token interface of the Schema API.
Access Channel
API
Possible Causes
The client ID or token is incorrect.
Procedure
Enter the correct client ID or token.

Copyright © Huawei
Mobile Money
4.25 BCS50026
Description
The bank difference file fails to be imported.
Scenario
This error is reported when the bank difference file fails to be imported.
Access Channel
System
Possible Causes
The bank difference file fails to be imported because the file is incorrect.
Procedure
View import logs for details.
4.26 BCS50027
Description
The bank difference file content exceeds the maximum value {0} configured in the system.
{0} indicates the maximum value of the bank difference file content configured in the system.
Scenario
This error is reported when the bank difference file content exceeds the maximum value {0}
configured in the system.
Access Channel
System
Possible Causes
The bank difference file content exceeds the maximum value {0} configured in the system.
Procedure
Reduce content in a bank difference file.

Copyright © Huawei
Mobile Money
4.27 BCS50028
Description
The token verification session times out.
Scenario
This error is reported when a third-party system verifies the token through the Validate Token
interface of the Schema API but the token verification session times out.
Access Channel
API
Possible Causes
The token verification session times out.
Procedure
Log in to the system again.
4.28 BCS50029
Description
The MSISDN of the organization operator fails to be modified.
Scenario
This error is reported when the MSISDN of an organization operator is modified but the
entered MSISDN is the same as the original MSISDN.
Access Channel
Web
Possible Causes
The new MSISDN is the same as the original one.
Procedure
Ensure that the entered MSISDN is correct.

Copyright © Huawei
Mobile Money
4.29 BCS50030
Description
The entered value of {0} is {1}. The verification fails.

{1} indicates a KYC field value.
Scenario
This error is reported during transaction initiation if the entered KYC information about the
request party is incorrect.
Access Channel
Web
Possible Causes
The entered KYC information about the request party is incorrect.
Procedure
Enter the correct KYC information.
4.30 BCS50031
Description
The entered value of {0} is empty. The verification fails.
Scenario
This error is reported during transaction initiation if the entered KYC information about the
request party is empty.
Access Channel
Web
Possible Causes
The entered KYC information about the request party is empty.

Copyright © Huawei
Mobile Money
Procedure
4.31 BCS50032
Description
The external error code contains the error code mapping and fails to be deleted.
Scenario
This error is reported when the external error code to be deleted contains the error code
mapping.
Access Channel
System
Possible Causes
The deleted external error code contains the error code mapping.
Procedure
Delete the error code mapping before deleting the external error code.
4.32 BCS50033
Description
The entered KYC information is incorrect and the PIN fails to be reset.
Scenario
This error is reported when a customer resets the PIN, the entered KYC information is
incorrect.
Access Channel
POS
Possible Causes
When a customer resets the PIN, the entered KYC information is incorrect.
Procedure
Enter correct KYC information.

Copyright © Huawei
Mobile Money
4.33 BCS50034
Description
The PIN already exists and cannot be created again.
Scenario
This error is reported when a customer creates a PIN, the PIN already exists.
Access Channel
POS
Possible Causes
When a customer creates a PIN, the PIN already exists.
Procedure
Reset the PIN and then create a PIN.
4.34 BCS50035
Description
The entered account does not exist.
Scenario
This error is reported when historical transaction records are queried, the entered account does
not exist.
Access Channel
POS
Possible Causes
When historical transaction records are queried, the entered account does not exist.
Procedure
Enter a correct account.

Copyright © Huawei
Mobile Money
4.35 BCS50036
Description
The query time period cannot be greater than {0} days.
{0}: maximum number of days for querying historical transaction records.
Scenario
This error is reported when historical transaction records are queried, the entered query time
period is too long.
Access Channel
POS
Possible Causes
When historical transaction records are queried, the entered query time period is too long.
Procedure
Enter a correct query time period.
4.36 BCS50037
Description
Transaction {0} is manually canceled by Bank Switching.
{0}: order ID.
Scenario
This error is reported when Bank Switching manually cancels the Cash Out transaction.
Access Channel
Web, USSD, API, STK
Possible Causes
Transaction {0} is manually canceled by Bank Switching.
Procedure
Bank Switching manually cancels the transaction. No solution is required.

Copyright © Huawei
Mobile Money
4.37 BCS50038
Description
The SetPIN operation cannot be initiated by non-registered customers.
Scenario
The SetPIN operation can be initiated only by users who are not created in the system or
registered customers who are in Pending Active state and have no PIN. This error is reported
if a lite or unregistered customer initiates the SetPIN operation.
Access Channel
USSD, APP
Possible Causes
The customer initiating the SetPIN operation has been created in the system but is not a
registered customer.
Procedure
Initiate the SetPIN operation as a registered customer.
4.38 BCS50039
Description
The SetPIN operation must be initiated by a registered customer in Pending Active state.
Scenario
if a registered customer who is not in Pending Active state initiates the SetPIN operation.
Access Channel
USSD, APP
Possible Causes
The customer initiating the SetPIN operation is not in Pending Active state.
Procedure
Initiate the SetPIN operation as a registered customer in Pending Active state.

Copyright © Huawei
Mobile Money
4.39 BCS50040
Description
The SetPIN operation cannot be initiated by a customer with a PIN.
Scenario
if a registered customer with a PIN initiates the SetPIN operation.
Access Channel
USSD, APP
Possible Causes
The customer initiating the SetPIN operation already has a PIN.
Procedure
The SetPIN operation cannot be initiated by a customer with a PIN.
4.40 BCS50041
Description
The transferred MSISDN cannot be empty.
Scenario
An MSISDN must be transferred for the SetPIN operation. This error is reported if the
transferred MSISDN is empty.
Access Channel
USSD, APP
Possible Causes
The transferred MSISDN is empty.
Procedure
Ensure that the transferred MSISDN is not empty.

Copyright © Huawei
Mobile Money
4.41 BCS50042
Description
The organization loan service cannot be initiated because the O2Clink does not exist between
the organization and customer.
Scenario
This error is reported when the organization loan service is initiated but the O2Clink does not
exist between the organization and customer.
Access Channel
USSD, APP
Possible Causes
The O2Clink does not exist between the organization and customer.
Procedure
Contact the organization to establish the O2Clink between the organization and customer.
Then, initiate the organization loan service.
4.42 BCS50043
Description
The loan transaction fails to be initiated because the loan amount {0} is not supported.
{0} indicates denomination code.
Scenario
This error is reported when the organization loan service is initiated but the entered loan
denomination code {0} does not exist in the system.
Access Channel
USSD, APP
Possible Causes
The entered loan amount {0} does not exist in the system.
Procedure
Enter a correct loan denomination code.

Copyright © Huawei
Mobile Money
4.43 BCS50044
Description
The entered name is too short or the bank does not exist.
Scenario
This error is reported when no switching bank information is queried.
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
4.44 BCS50045
Description
The MSISDN is mandatory.
Scenario
This error is reported when msisdn mandatory is set to Yes in Reasontype, the msisdn
identifier is not transferred in the transaction request, and the transaction fails.
Access Channel
API, USSD, APP
Possible Causes
The MSISDN is mandatory.
Procedure
Ensure that the MSISDN is set.

Copyright © Huawei
Mobile Money
4.45 BCS50046
Description
The receiver's PIN is not transferred.
Scenario
This error is reported if the reason type is configured to verify the receiver's PIN but the PIN
is not transferred.
Access Channel
API, USSD, APP
Possible Causes
The receiver's PIN is not transferred.
Procedure
Ensure that the receiver's PIN is transferred.
4.46 BCS50047
Description
The PIN fails to be reset because the entered KYC information is incorrect.
Scenario
This error is reported when a customer resets the PIN, the entered KYC information is
incorrect.
Access Channel
pos
Possible Causes
When a customer resets the PIN, the entered KYC information is incorrect.
Procedure

Copyright © Huawei
Mobile Money
4.47 BCS50048
Description
The account adjustment operation fails.
Scenario
This error is reported when the account adjustment operation is initiated but the entered
account does not exist or has been closed.
Access Channel
Web,USSD,API
Possible Causes
The entered account does not exist or has been closed.
Procedure
Ensure that the entered account number is correct.
4.48 BCS50049
Description
The SN or UID already exists.
Scenario
This error is reported if the NFC information fails to be verified during batch import of NFC
tag resources.
Access Channel
Web
Possible Causes
The SN or UID already exists.
Procedure
Change the SN or UID to the unused NFC tag.

Copyright © Huawei
Mobile Money
4.49 BCS50050
Description
The unlink operation fails because the current identity does not have the NFC tag information.
Scenario
This error is reported when the NFC tag of a unlink identity is initiated.
Access Channel
USSD, WEB, APP, API, SMS
Possible Causes
The current identity does not have the NFC tag information.
Procedure
Do not unlink the identity because the identity does not have the NFC tag information.
4.50 BCS50051
Description
The unlink operation fails to be initiated because the NFC tag where the UID is {0} is not the
tag of the current identity.
{0} indicates the UID of the NFC tag, for example, CE71D4C1.
Scenario
This error is reported when the NFC tag of a unlink identity is initiated.
Access Channel
USSD, WEB, APP, API, SMS
Possible Causes
The NFC tag where the UID is {0} is not the tag of the current identity.
Procedure
Enter the tag of the identity to be unlinked.

Copyright © Huawei
Mobile Money
4.51 BCS50052
Description
The primary party's PIN is not transferred.
Scenario
This error is reported if the reason type is configured to verify the primary party's PIN but the
PIN is not transferred.
Access Channel
API, USSD, APP
Possible Causes
The primary party's PIN is not transferred.
Procedure
Ensure that the primary party's PIN is transferred.
4.52 BCS50053
Description
User {0} has not bound a bank account in the bank whose bank code is {1}.
{0} indicates the identity name.

{1} indicates the bank code, that is, the short code of a bank.
Scenario
This error is reported if the bank transfers money to the MFS through TRX but the user has
not bound a bank card.
Access Channel
All
Possible Causes
User {0} has not bound a bank account in the bank whose bank code is {1}.
Procedure
Bind a bank card.

Copyright © Huawei
Mobile Money
4.53 BCS50054
Description
The Direct Debit Mandate has expired.
Scenario
This error is reported if the expiration date is configured for the Direct Debit Mandate but the
current transaction initiation time is later than the expiration date.
Access Channel
WEB, API, USSD, APP
Possible Causes
The Direct Debit Mandate has expired.
Procedure
Bind the Direct Debit Mandate again.
4.54 BCS50055
Description
If an identity is allowed to bind multiple bank cards of the same bank, the account information
is mandatory.
Scenario
is mandatory. This error is reported during bank card binding if the account information is not
configured.
Access Channel
API,USSD,SMS,APP
Possible Causes
is mandatory.
Procedure
Enter the bank account information.

Copyright © Huawei
Mobile Money
4.55 BCS50056
Description
There is not only one of the StickerSerialNumber, StickerUID, and PhoneUID parameters is
not empty.
Scenario
The LinkNFCTag interface has three parameters: StickerSerialNumber, StickerUID, and
PhoneUID. In the actual scenario, only one of these parameters is not empty. This error is
reported if there is not only one of these parameters is not empty.
Access Channel
USSD, APP
Possible Causes
There is not only one of the StickerSerialNumber, StickerUID, and PhoneUID parameters is
not empty.
Procedure
Ensure that there is only one of the StickerSerialNumber, StickerUID, and PhoneUID
parameters is not empty.
4.56 BCS50057
Description
The transferred StickerSerialNumber parameter is in incorrect format.
Scenario
This error is reported if the transferred StickerSerialNumber parameter is in incorrect format.
Access Channel
USSD, APP
Possible Causes
The transferred StickerSerialNumber parameter is in incorrect format.
Procedure
Ensure that the StickerSerialNumber parameter is in correct format.

Copyright © Huawei
Mobile Money
4.57 BCS50058
Description
The transferred StickerUID parameter is in incorrect format.
Scenario
This error is reported if the transferred StickerUID parameter is in incorrect format.
Access Channel
USSD, APP
Possible Causes
The transferred StickerUID parameter is in incorrect format.
Procedure
Ensure that the StickerUID parameter is in correct format.
4.58 BCS50059
Description
The transferred PhoneUID parameter is in incorrect format.
Scenario
This error is reported if the transferred PhoneUID parameter is in incorrect format.
Access Channel
USSD, APP
Possible Causes
The transferred PhoneUID parameter is in incorrect format.
Procedure
Ensure that the PhoneUID parameter is in correct format.

Copyright © Huawei
Mobile Money
4.59 BCS50060
Description
The sticker to be associated does not exist.
Scenario
This error is reported when the LinkNFC operation is initiated but the transferred
StickerSerialNumber parameter is in incorrect format.
Access Channel
USSD, APP
Possible Causes
The sticker to be associated does not exist.
Procedure
Enter a correct sticker.
4.60 BCS50061
Description
The sticker to be associated has been associated.
Scenario
Access Channel
USSD, APP
Possible Causes
The sticker to be associated has been associated.
Procedure

Copyright © Huawei
Mobile Money
4.61 BCS50062
Description
The sticker to be associated was associated by another customer and can only be associated by
the customer again.
Scenario
Access Channel
USSD, APP
Possible Causes
The sticker to be associated was associated by another customer and can only be associated by
the customer again.
Procedure
4.62 BCS50063
Description
The entered phone UID has been associated.
Scenario
Access Channel
USSD, APP
Possible Causes
The entered phone UID has been associated.
Procedure
Enter a correct phone UID.

Copyright © Huawei
Mobile Money
4.63 BCS50064
Description
The entrusted deduction account {0} of the transaction is in {1} state and fails to be
authenticated. The current service cannot be handled.
{0}: indicates the account alias.

{1}: indicates the account status.
Scenario
This error is reported if the bank transfers money to the MFS through TRX but the entrusted
deduction account of the transaction fails to be authenticated.
Access Channel
All
Possible Causes
The entrusted deduction account {0} of the transaction is in {1} state and fails to be
Procedure
Ensure that the account is in correct status.
4.64 BCS50065
Description
The entrusted deduction identity {0} of the transaction is in {1} state and fails to be
{0}: indicates the brief description of the identity.

{1}: indicates the identity status.
Scenario
This error is reported if the bank transfers money to the MFS through TRX but the entrusted
deduction identity of the transaction fails to be authenticated.
Access Channel
All

Copyright © Huawei
Mobile Money
Possible Causes
The entrusted deduction identity {0} of the transaction is in {1} state and fails to be
Procedure
Ensure that the identity is in correct status.
4.65 BCS50066
Description
The KYC attribute format is incorrect in the files uploaded in batches.
Scenario
This error is reported if the KYC attribute format is incorrect in the files uploaded in batches.
Access Channel
Web (Bulk)
Possible Causes
The KYC attribute format is incorrect in the files uploaded in batches.
Procedure
Set KYC attributes based on the template.
4.66 BCS50067
Description
The specified voucher does not exist or is in an invalid state.
Scenario
The specified voucher does not exist or is not in the active state.
Access Channel
Web, STK, USSD, API
Possible Causes
The specified voucher does not exist or is in an invalid state.

Copyright © Huawei
Mobile Money
Procedure
Reapply for a voucher by referring to the user manual.
4.67 BCS50068
Description
Failed to close {0}.
{0}:indicates the idenitty public name.
Scenario
This error is reported when an SP operator closes an identity having unclosed processes.
Access Channel
POS
Possible Causes
{0} has uncompleted workflows or transactions.
Procedure
Ensure that the identity does not have unclosed tasks.
4.68 BCS50069
Description
The transfer transaction fails.
Scenario
This error is reported when an international transfer transaction is initiated and the transaction
request is forwarded to the Local Remittance Partner1 but the third-party system does not
respond.
Access Channel
API
Possible Causes
When the transaction request is forwarded to the Local Remittance Partner1, the third-party
system does not return the corresponding response.

Copyright © Huawei
Mobile Money
Procedure
Initiate the transfer transaction again.
4.69 BCS50070
Description
The voucher of the voucher type cannot be redeemed.
Scenario
This error is reported during voucher verification if the voucher type of the entered voucher is
not the required one.
Access Channel
Web, STK, USSD, API
Possible Causes
The voucher type of the entered voucher is not the required one.
Procedure
Ensure that the voucher type of the used voucher is correct.
4.70 BCS50071
Description
The current day is a holiday in the holiday table {0} and transactions cannot be initiated on
the day.
{0}:indicates the holiday name.
Scenario
This error is reported when the transaction is initiated on a holiday but fails to be initiated.
Access Channel
All
Possible Causes
The current day is a holiday in the holiday table {0} and transactions cannot be initiated on
the day.

Copyright © Huawei
Mobile Money
Procedure
Do not initiate a transaction on holidays.
4.71 BCS50072
Description
The offline wallet to be activated already exists and is not in disabled state.
Scenario
This error is reported when a customer activates an offline wallet but the offline wallet
already exists and is not in disabled state.
Access Channel
Web
Possible Causes
The offline wallet to be activated already exists and is not in disabled state.
Procedure
Ensure that offline wallet to be activated does not exist or is in disabled state.
4.72 BCS50073
Description
The customer is not bound to a unique NFC sticker.
Scenario
This error is reported when a customer activates an offline wallet but the customer is not
bound to a unique NFC tag.
Access Channel
Web
Possible Causes
The customer is not bound to a unique NFC sticker.

Copyright © Huawei
Mobile Money
Procedure
Ensure that the customer who activates the offline wallet has been bound to a unique NFC tag
and the NFC tag must be an NFC sticker.
4.73 BCS50074
Description
The current offline wallet is not in enabled state.
Scenario
This error is reported if an offline wallet recharge transaction is initiated but the offline wallet
is not in enabled state.
Access Channel
Web
Possible Causes
The current offline wallet is not in enabled state.
Procedure
Ensure that the offline wallet to be recharged is in enabled state.
4.74 BCS50075
Description
The current offline wallet does not support automatic recharge.
Scenario
This error is reported if an offline wallet recharge transaction is initiated but the offline wallet
does not support automatic recharge.
Access Channel
Web
Possible Causes
The current offline wallet does not support automatic recharge.

Copyright © Huawei
Mobile Money
Procedure
Ensure that the offline wallet to be recharged supports the automatic recharge transaction.
4.75 BCS50076
Description
The third-party system fails to be invoked during recharge transaction initiation.
Scenario
This error is reported when the third-party system fails to be invoked during recharge
transaction initiation.
Access Channel
Web
Possible Causes
The third-party system fails to be invoked during recharge transaction initiation.
Procedure
Ensure that the third-party recharge service can be invoked normally.
4.76 BCS50077
Description
When an NFC tag is unlinked, the offline wallet corresponding to the NFC tag is in enabled
state.
Scenario
This error is reported when an NFC tag is unlinked but an offline wallet in enabled state
exists.
Access Channel
Web
Possible Causes
When an NFC tag is unlinked, the offline wallet corresponding to the NFC tag is in enabled
state.

Copyright © Huawei
Mobile Money
Procedure
Ensure that the offline wallet corresponding to the NFC tag to be unlinked does not exist or is
not in enabled state.
4.77 BCS50078
Description
The Out Going service of the AG fails to be invoked.
Scenario
Access Channel
Web
Possible Causes
Procedure
Ensure that the Out Going service of the AG can be invoked normally.
4.78 BCS50079
Description
Owners cannot modify the KYC.
Scenario
This error is reported when a customer cannot modify the CNS KYC through self service
because owners cannot modify the KYC.
Access Channel
Web
Possible Causes
Owners cannot modify the KYC.
Procedure
Check the KYC configuration.

Copyright © Huawei
Mobile Money
4.79 BCS50080
Description
The KYC does not need to be modified because the value is already the same as the expected
one.
Scenario
This error is reported when a customer cannot modify the CNS KYC because the KYC value
is already the expected one.
Access Channel
Web
Possible Causes
The KYC does not need to be modified because the value is already the same as the expected
one.
Procedure
Ensure that the request parameters are correct.
4.80 BCS50081
Description
The CNS function has been disabled for the initiator.
Scenario
This error is reported when the CNS operation fails to be initiated because the CNS function
of the initiator is disabled.
Access Channel
Web
Possible Causes
The CNS function has been disabled for the initiator.
Procedure
Ensure that the CNS function has been enabled for the initiator.

Copyright © Huawei
Mobile Money
4.81 BCS50082
Description
The CNS function is disabled for the initiator.
Scenario
This error is reported when the CNS operation fails to be initiated because the CNS function
flag of the initiator is disabled.
Access Channel
Web
Possible Causes
The CNS function is disabled for the initiator.
Procedure
Ensure that the CNS function has been enabled for the initiator.
4.82 BCS50083
Description
The CNS function has been disabled for the recipient.
Scenario
This error is reported when the CNS operation fails to be initiated because function of
querying the recipient name is disabled.
Access Channel
Web
Possible Causes
The CNS function has been disabled for the recipient.
Procedure
Ensure that the CNS function has been enabled for the recipient.

Copyright © Huawei
Mobile Money
4.83 BCS50084
Description
The recipient name cannot be queried.
Scenario
This error is reported when the CNS operation fails to be initiated because the recipient
disables the function of querying the recipient name.
Access Channel
Web
Possible Causes
The recipient name cannot be queried.
Procedure
Ensure that the CNS function has been enabled for the recipient.
4.84 BCS50085
Description
The identity to be closed has offline wallets in enabled state.
Scenario
This error is reported when an identity having offline wallets in enabled state is closed.
Access Channel
Web
Possible Causes
The identity to be closed has offline wallets in enabled state.
Procedure
Ensure that the identity to be closed does not have offline wallets in enabled state.

Copyright © Huawei
Mobile Money
4.85 BCS50086
Description
When a customer initiates a modification request, the modified Beneficiaryreference cannot
be the same as the original Beneficiaryreference.
Scenario
This error is reported during Beneficiaryreference modification if the modified
Beneficiaryreference is the same as the original Beneficiaryreference.
Access Channel
API
Possible Causes
The modified Beneficiaryreference is the same as the original Beneficiaryreference.
Procedure
Ensure that the modified Beneficiaryreference is different from the original
Beneficiaryreference.
4.86 BCS50087
Description
When the beneficiary information is updated for a customer, the MSISDN of the beneficiary
does not exist.
Scenario
This error is reported when the beneficiary information is updated for a customer but the
beneficiary does not exist.
Access Channel
API, USSD
Possible Causes
When the beneficiary information is updated for a customer, the beneficiary does not exist.
Procedure
Ensure that the beneficiary exists.

Copyright © Huawei
Mobile Money
4.87 BCS50088
Description
An error is reported when an organization of the specified level is queried.
Scenario
This error is reported when an organization of the specified level is queried but no matching
organization is found or multiple matching organizations are found.
Access Channel
WEB,API,APP,USSD
Possible Causes
When an organization of the specified level is queried but no matching organization is found
or multiple matching organizations are found.
Procedure
Ensure that only one matching organization is found.
4.88 BCS50089
Description
The Promotion does not respond.
Scenario
This error is reported after coupons are rewarded and the BCS submits information to the
Promotion but the Promotion does not respond.
Access Channel
POS
Possible Causes
The Promotion does not respond.
Procedure
Try again later.

Copyright © Huawei
Mobile Money
4.89 BCS50090
Description
During NFC linking, the identity already has an offline wallet that is not in disabled state.
Scenario
This error is reported during NFC linking if the identity already has an offline wallet that is
not in disabled state.
Access Channel
Web
Possible Causes
During NFC linking, the identity already has an offline wallet that is not in disabled state.
Procedure
Initiate the NFC tag linking operation after ensuring that the offline wallet corresponding to
the NFC tag to be linked does not exist or is in disabled state.
4.90 BCS50091
Description
The transaction fails to be queried.
Scenario
This error is reported when the customer initiating the transaction details query operation is
different from the customer initiating the transaction.
Access Channel
API
Possible Causes
The queried transaction is not initiated by the customer initiating the query.
Procedure
Query transactions initiated by the customer initiating the query.

Copyright © Huawei
Mobile Money
4.91 BCS50092
Description
When the Auto Topup status is modified for the offline wallet, the input parameter is
incorrect.
Scenario
This error is reported when the Auto Topup status is modified for the offline wallet but the
input parameter is incorrect.
Access Channel
Web
Possible Causes
When the Auto Topup status is modified for the offline wallet, the input parameter is
incorrect.
Procedure
Change the Auto Topup status for the offline wallet after ensuring that the input parameter is
correct.
4.92 BCS50093
Description
When the Auto Topup status is modified for the offline wallet, the offline wallet is not unique.
Scenario
This error is reported when the Auto Topup status is modified for the offline wallet but the
offline wallet is not unique.
Access Channel
Web
Possible Causes
When the Auto Topup status is modified for the offline wallet, the offline wallet is not unique.
Procedure
Change the Auto Topup status for the offline wallet after ensuring that the offline wallet is
unique.

Copyright © Huawei
Mobile Money
4.93 BCS50094
Description
The customer has activated an organization FSI product.
Scenario
This error is reported when a customer using a small SIM card has activated an organization
FSI product and activates another organization FSI product.
Access Channel
API, USSD, APP
Possible Causes
A customer using a small SIM card is not allowed to activate multiple organization FSI
products.
Procedure
Deactivate the activated FSI product first.
4.94 BCS50095
Description
The MNP operation fails.
Scenario
This error is reported when the MNP operation fails to be initiated because the MNP operation
object does not have dormant process records.
Access Channel
Web
Possible Causes
No dormant process record is found.
Procedure
Ensure that the MNP operation object has dormant process records.

Copyright © Huawei
Mobile Money
4.95 BCS50096
Description
The offline wallet fails to be disabled.
Scenario
This error is reported when the offline wallet fails to be disabled.
Access Channel
Web
Possible Causes
The offline wallet to be disabled is in initiating state.
Procedure
Ensure that the offline wallet to be disabled is not in initiating state.
4.96 BCS50097
Description
When the auto topup status is modified for the offline wallet, the entered value of AutoTopUp
is not 0 or 1.
Scenario
This error is reported when the auto topup status is modified for the offline wallet but the
entered value of AutoTopUp is not 0 or 1.
Access Channel
Web
Possible Causes
When the auto topup status is modified for the offline wallet, the entered value of AutoTopUp
is not 0 or 1.
Procedure
Ensure that the value of AutoTopUp is 0 or 1.

Copyright © Huawei
Mobile Money
4.97 BCS50098
Description
{0} fails to be redeemed.
{0} indicates the coupon ID.
Scenario
This error is reported when a coupon fails to be redeemed.
Access Channel
USSD, API
Possible Causes
The coupon fails to be redeemed.
Procedure
Verify that the coupon can be redeemed nromally.
4.98 BCS50099
Description
The third-party system returns a message indicating that the SIM card fails to be initiated.
Scenario
This error is reported durign SIM card registration when the third-party system returns a
registration failure message.
Access Channel
Web
Possible Causes
The third-party system returns a message indicating that the SIM card fails to be initiated.
Procedure
Ensure that the input information is correct.

Copyright © Huawei
Mobile Money
4.99 BCS50100
Description
The initiator is not an SP operator.
Scenario
This error is reported when coupons are rewarded to users manually or in batches but the
reward fails because the initiator is not an SP operator.
Access Channel
POS
Possible Causes
The initiator is not an SP operator.
Procedure
Perform the operation as an SP operator.
4.100 BCS50101
Description
The identity status tag {0} does not exist or does not belong to the current identity type {1}.
{0}: indicates the identity stats tag. {1}: Indicates the identity type.
Scenario
This error is reported when the status tag definition is queried based on the unique name of
the status tag and the allocated identity type but the query result is empty.
Access Channel
WEB, SYSTEM
Possible Causes
The identity status tag {0} does not exist or does not belong to the current identity type {1}.
Procedure
Ensure that the request parameter is correct and has been allocated to the current identity type.

Copyright © Huawei
Mobile Money
4.101 BCS50102
Description
The status tag {0} has been added for the identity and cannot be added again.
Scenario
This error is reported when a status tag instance fails to be added for an identity because the
status tag already exists.
Access Channel
WEB, SYSTEM
Possible Causes
The status tag {0} has been added for the identity and cannot be added again.
Procedure
Ensure that the status tag to be added has not been added for the identity.
4.102 BCS50103
Description
The identity does not have the status tag {0} and the deletion fails.
Scenario
This error is reported when a status tag instance fails to be deleted for an identity because the
status tag does not exist.
Access Channel
WEB, SYSTEM
Possible Causes
The identity does not have the status tag {0} and the deletion fails.
Procedure
Ensure that the name of the status tag to be deleted is correct and the status tag has been
allocated to the identity.

Copyright © Huawei
Mobile Money
4.103 BCS50104
Description
In the API request, the initiator is a customer but the recipient is not a customer or the initiator
and recipient are not the same customer.
Scenario
This error is reported during offline transaction query if the initiator is a customer but the
recipient is not a customer or the initiator and recipient are not the same customer.
Access Channel
API
Possible Causes
In the API request, the initiator is a customer but the recipient is not a customer or the initiator
and recipient are not the same customer.
Procedure
Ensure that ReceiverParty must be the same customer as the initiator or is empty in the API
request when the initiator is a customer.
4.104 BCS50105
Description
In the API request, the initiator is an SP but the recipient is not a customer.
Scenario
This error is reported during offline transaction query if the initiator is an SP but the recipient
is not a customer.
Access Channel
API
Possible Causes
In the API request, the initiator is an SP but the recipient is not a customer.
Procedure
Ensure that the ReceiverParty is a customer in the API request when the initiator is an SP.

Copyright © Huawei
Mobile Money
4.105 BCS50106
Description
In the API request, the NFC link information of the customer does not exist.
Scenario
This error is reported during offline transaction query if the NFC link information of the
queried customer does not exist.
Access Channel
API
Possible Causes
In the API request, the NFC link information of the customer does not exist.
Procedure
Ensure that the NFC link information of the customer exists.
4.106 BCS50107
Description
In the API request, the NFC sticker information of the customer does not exist.
Scenario
This error is reported during offline transaction query if the NFC sticker information of the
queried customer does not exist.
Access Channel
API
Possible Causes
In the API request, the NFC sticker information of the customer does not exist.
Procedure
Ensure that the NFC sticker information of the customer exists.

Copyright © Huawei
Mobile Money
4.107 BCS50108
Description
In the API request, the NFC sticker information of the customer is not unique.
Scenario
This error is reported during offline transaction query if the NFC sticker information of the
queried customer is not unique.
Access Channel
API
Possible Causes
In the API request, the NFC sticker information of the customer is not unique.
Procedure
Ensure that the NFC sticker information of the customer is unique.
4.108 BCS50109
Description
An error occurs in the settlement system when the MQ is synchronously invoked to query the
settlement system. The detailed description about the error is as follows: {0}
{0} indicates error description.
Scenario
This error is reported during offline transaction query if the MQ is synchronously invoked to
query the settlement system but an error occurs in the settlement system.
Access Channel
API
Possible Causes
An error occurs in the settlement system when the MQ is synchronously invoked to query the
settlement system.
Procedure
Contact engineers of the settlement system to troubleshoot the fault.

Copyright © Huawei
Mobile Money
4.109 BCS50110
Description
An error occurs when the MQ is synchronously invoked to query the settlement system.
Scenario
This error is reported during offline transaction query if the MQ is synchronously invoked to
query the settlement system but the MQ is abnormal.
Access Channel
API
Possible Causes
An error occurs when the MQ is synchronously invoked to query the settlement system.
Procedure
Ensure that the MQ is normal when the MQ is synchronously invoked to query the settlement
system.
4.110 BCS50111
Description
The bank branch short code must be entered.
Scenario
This error is reported when a settlement transaction is initiated in the settlement system but
the bank short code is not entered.
Access Channel
SYSTEM
Possible Causes
The bank branch short code is not entered.
Procedure
Enter a bank branch short code.

Copyright © Huawei
Mobile Money
4.111 BCS50112
Description
The bank corresponding to {0} does not exist.
{0}: indicates bank short code.
Scenario
the bank corresponding to the entered bank short code does not exist.
Access Channel
SYSTEM
Possible Causes
The bank corresponding to {0} does not exist.
Procedure
Enter a correct bank branch short code.
4.112 BCS50113
Description
The bank control account corresponding to {0} does not exist.
{0}: indicates bank short code.
Scenario
Access Channel
SYSTEM
Possible Causes
Procedure
Enter a correct bank branch short code.

Copyright © Huawei
Mobile Money
4.113 BCS50114
Description
The txnDate field must be set.
Scenario
This error is reported when the code stream query is initiated in the reconciliation system but
txnDate is not set.
Access Channel
SYSTEM
Possible Causes
The txnDate field is not set.
Procedure
Set txnDate.
4.114 BCS50115
Description
The traceNumber field must be set.
Scenario
This error is reported when the code stream query is initiated in the reconciliation system but
traceNumber is not set.
Access Channel
SYSTEM
Possible Causes
The traceNumber field is not set.
Procedure
Set traceNumber.

Copyright © Huawei
Mobile Money
4.115 BCS50116
Description
The RequestId parameter must be set.
Scenario
This error is reported when the transaction status query is initiated in the settlement system
but RequestId is not set.
Access Channel
SYSTEM
Possible Causes
The RequestId field is not set.
Procedure
Set RequestId.
4.116 BCS50117
Description
The RequestTime parameter must be set.
Scenario
but RequestTime is not set.
Access Channel
SYSTEM
Possible Causes
The RequestTime field is not set.
Procedure
Set RequestTime.

Copyright © Huawei
Mobile Money
4.117 BCS50118
Description
The settlement order does not exist.
Scenario
the settlement order does not exist.
Access Channel
SYSTEM
Possible Causes
The settlement order does not exist.
Procedure
Enter a correct order ID.
4.118 BCS50119
Description
The SIM card fails to be queried.
Scenario
This error is reported when the SIM card status fails to be queried.
Access Channel
USSD
Possible Causes
When the SIM card is queried, the third-party system returns a failure message.
Procedure
Resend the request to query the SIM card status.

Copyright © Huawei
Mobile Money
4.119 BCS50120
Description
The number of activated SIM cards fails to be queried.
Scenario
This error is reported when the number of activated SIM cards fails to be queried.
Access Channel
USSD
Possible Causes
When the number of activated SIM cards is queried, the third-party system returns a failure
message.
Procedure
Resend the request to query the number of activated SIM cards.
4.120 BCS50121
Description
The Simponi bill amount fails to be queried.
Scenario
This error is reported if the Simponi bill amount fails to be queried.
Access Channel
API
Possible Causes
When the Simponi bill amount is queried, the third-party system returns a failure message.
Procedure
Resend the request to query the Simponi bill amount.

Copyright © Huawei
Mobile Money
4.121 BCS50122
Description
An unbound bank card is used for initiating transactions.
Scenario
This error is reported if an unbound bank card is used for initiating transactions.
Access Channel
POS
Possible Causes
An unbound bank card is used for initiating transactions.
Procedure
Use a bound bank card to initiate transactions.
4.122 BCS50123
Description
The initiator cannot reverse the transaction.
Scenario
This error is reported when an initiator reverses a transaction that the initiator cannot reverse.
Access Channel
Web
Possible Causes
The initiator cannot reverse the transaction.
Procedure
Ensure that the initiator can reverse the transaction.

Copyright © Huawei
Mobile Money
4.123 BCS50124
Description
When the transaction is reversed, Org Operator is set to ReceiverParty.
Scenario
This error is reported when a transaction is reversed but Org Operator is set to ReceiverParty.
Access Channel
Web
Possible Causes
When the transaction is reversed, Org Operator is set to ReceiverParty.
Procedure
Do not set Org Operator to ReceiverParty during transaction reversal.
4.124 BCS50125
Description
The value of EventSource in the request must be 20 or 21.
Scenario
but the value of EventSource is not 20 or 21.
Access Channel
SYSTEM
Possible Causes
The value of EventSource in the request is not 20 or 21.
Procedure
Set EventSource to a correct value.

Copyright © Huawei
Mobile Money
4.125 BCS50126
Description
The OriginalConversionID field in the request cannot be empty.
Scenario
but OriginalConversionID in the request is empty.
Access Channel
SYSTEM
Possible Causes
The OriginalConversionID field in the request is empty.
Procedure
Set OriginalConversionID to a correct value.
4.126 BCS50127
Description
The length of OriginalConversionID exceeds the maximum.
Scenario
the length of OriginalConversionID exceeds the maximum.
Access Channel
SYSTEM
Possible Causes
The length of OriginalConversionID exceeds the maximum.
Procedure
Ensure that the length of OriginalConversionID does not exceed the maximum.

Copyright © Huawei
Mobile Money
4.127 BCS50128
Description
The code stream query result does not exist.
Scenario
This error is reported when the code stream query is initiated in the settlement system but the
query result does not exist.
Access Channel
SYSTEM
Possible Causes
The code stream query result does not exist.
Procedure
Enter correct parameter to query code streams.
4.128 BCS50129
Description
The value of channel is not 1012.
Scenario
This error is reported when the query is initiated in the settlement system but the value of
channel is not 1012.
Access Channel
SYSTEM
Possible Causes
When the query is initiated in the settlement system, the value of channel is not 1012.
Procedure
Set channel to a correct value.

Copyright © Huawei
Mobile Money
4.129 BCS50130
Description
The format of request time is incorrect.
Scenario
This error is reported when the query is initiated in the settlement system but the format of
request time is incorrect.
Access Channel
SYSTEM
Possible Causes
The format of request time is incorrect.
Procedure
Ensure that the format of request time is correct.
4.130 BCS50131
Description
The {0} field cannot be set to {1}.
{0}: Name of a parameter.

{1}: Value of a parameter.
Scenario
A bulk task parameter is set to an incorrect value.
Access Channel
USSD, Web, STK
Possible Causes
The {0} field cannot be set to {1}.
Procedure
Verify that bulk file parameters are correctly set.

Copyright © Huawei
Mobile Money
4.131 BCS50132
Description
The state tag {0} of the transaction credit party restricts the fund transfer-in and the
transaction fails.
{0} indicates that the fund transfer-out is restricted for the transaction credit party.
Scenario
This error is reported when the state tags of both transaction parties are verified in the
transaction process but a state tag of the credit party is configured to restrict the fund transfer-
in.
Access Channel
Web, SYSTEM
Possible Causes
The state tag {0} of the transaction credit party restricts the fund transfer-in and the
transaction fails.
Procedure
Verify that the state tag of the credit party is configured correctly.
4.132 BCS50133
Description
The state tag {0} of the transaction debit party restricts the fund transfer-out and the
transaction fails.
{0} indicates that the fund transfer-out is restricted for the transaction debit party.
Scenario
This error is reported when the state tags of both transaction parties are verified in the
transaction process but a state tag of the debit party is configured to restrict the fund transfer-
out.
Access Channel
Web, SYSTEM

Copyright © Huawei
Mobile Money
Possible Causes
The state tag {0} of the transaction debit party restricts the fund transfer-out and the
transaction fails.
Procedure
Verify that the state tag of the debit party is configured correctly.
4.133 BCS50134
Description
The Incentive Payment fails to be manually initiated.
Scenario
This error is reported when the Incentive Payment fails to be manually initiated.
Access Channel
Web
Possible Causes
The corresponding incentive payment failed record does not exist when the incentive payment
is manually initiated.
Procedure
Refresh the page and ensure that the corresponding incentive payment failed record exists.
4.134 BCS50135
Description
The transaction status obtained based on the transaction ID {0} is not Authorized and the
authorization-related operation cannot be performed on the transaction.
{0} indicates the transaction ID.
Scenario
This error is reported when authorization-related operations are performed on a transaction
but the transaction is not in Authorize state.

Copyright © Huawei
Mobile Money
Access Channel
All
Possible Causes
The transaction ID {0} is incorrect.
Procedure
Enter the correct transaction ID {0} and ensure that the transaction is in Authorize state.
4.135 BCS50136
Description
The entered start time and end time must be in the correct time range.
Scenario
This error is reported during organization statement query when the entered start time or end
time is incorrect.
Access Channel
POS
Possible Causes
The entered start time or end time is incorrect.
Procedure
Enter the correct start time and end time.
4.136 BCS50137
Description
The SFTP server fails to be connected.
Scenario
This error is reported when the Dow Jones file is updated but the SFTP server cannot be
connected.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The SFTP server fails to be connected.
Procedure
Check whether the configuration file is correct.
4.137 BCS50138
Description
The Dow Jones file fails to be downloaded from the SFTP server.
Scenario
This error is reported when the Dow Jones file fails to be downloaded from the SFTP server.
Access Channel
Web
Possible Causes
The Dow Jones file fails to be downloaded from the SFTP server.
Procedure
Verify that the file exists and the account password is correct.
4.138 BCS50139
Description
The full or incremental file and checksum file fail the MD5 verification.
Scenario
This error is reported when the Dow Jones file is updated and downloaded but the full or
incremental file and checksum file fail the MD5 verification.
Access Channel
Web
Possible Causes
The downloaded full or incremental file is incomplete.

Copyright © Huawei
Mobile Money
Procedure
Download the file again.
4.139 BCS50140
Description
The file fails to be uploaded to the SFTP server.
Scenario
This error is reported when the Dow Jones file is updated and downloaded but the file fails to
be uploaded to the SFTP server.
Access Channel
Web
Possible Causes
The SFTP server is disconnected.
Procedure
Check whether the SFTP server is connected normally.
4.140 BCS50141
Description
The size of the file to be downloaded from the SFTP server is too large.
Scenario
This error is reported when the Dow Jones file is updated and downloaded but the size of the
file to be downloaded from the SFTP server is too large.
Access Channel
Web
Possible Causes
The size of the file to be downloaded from the SFTP server is too large.
Procedure
Increase the maximum size of the file to be downloaded from the SFTP server.

Copyright © Huawei
Mobile Money
4.141 BCS50142
Description
The Dow Jones file update and download times out.
Scenario
This error is reported when the Dow Jones file update and download times out.
Access Channel
Web
Possible Causes
The Dow Jones file update and download times out.
Procedure
Increase the timeout interval of the scheduled task.
4.142 BCS50143
Description
The time of the ZIP file is incorrect.
Scenario
This error is reported when the Dow Jones file is updated and downloaded but the time of the
ZIP file is incorrect.
Access Channel
Web
Possible Causes
The time of the ZIP file is incorrect.
Procedure
Modify the ZIP file time to a correct one.

Copyright © Huawei
Mobile Money
4.143 BCS50144
Description
The watchlist file fails to be parsed.
Scenario
This error is reported when the Dow Jones file is updated and downloaded but the watchlist
file fails to be parsed.
Access Channel
Web
Possible Causes
The watchlist file fails to be parsed.
Procedure
Download and parse the file again.
4.144 BCS50145
Description
The ZIP file fails to be decompressed.
Scenario
This error is reported when the Dow Jones file is updated and downloaded but the ZIP file
fails to be decompressed.
Access Channel
Web
Possible Causes
The ZIP file fails to be decompressed.
Procedure
Download and decompress the file again.

Copyright © Huawei
Mobile Money
4.145 BCS50146
Description
The file fails to be compressed.
Scenario
This error is reported when the Dow Jones file is updated and downloaded but the file fails to
be compressed.
Access Channel
Web
Possible Causes
The file fails to be compressed.
Procedure
Compress the file again.
4.146 BCS50147
Description
The referenceList file fails to be parsed.
Scenario
This error is reported when the Dow Jones file is updated and downloaded but the
referenceList file fails to be parsed.
Access Channel
Web
Possible Causes
The referenceList file is incorrect.
Procedure
Download and parse the file again.

Copyright © Huawei
Mobile Money
4.147 BCS50148
Description
The record does not exist.
Scenario
This error is reported when the Dow Jones file is updated and downloaded but the record does
not exist.
Access Channel
Web
Possible Causes
The record does not exist.
Procedure
Verify that the record exists.
4.148 BCS50149
Description
More than one record exists.
Scenario
This error is reported when the Dow Jones file is updated and downloaded but more than one
record exists.
Access Channel
Web
Possible Causes
More than one record exists.
Procedure
Check the record again.

Copyright © Huawei
Mobile Money
4.149 BCS50150
Description
The record check is rejected.
Scenario
This error is reported when the Dow Jones file is updated and downloaded but the record
check is rejected.
Access Channel
Web
Possible Causes
The record check is rejected.
Procedure
Check the record again.
4.150 BCS50151
Description
The path does not exist.
Scenario
This error is reported when the Dow Jones file is updated and downloaded but the path does
not exist.
Access Channel
Web
Possible Causes
The path does not exist.
Procedure
Verify that the path is correct.

Copyright © Huawei
Mobile Money
4.151 BCS50152
Description
The receipt number queried based on OriginalConversationID does not match the originally
entered receipt number. The two recipient numbers correspond to different transaction
records.
Scenario
This error is reported during transaction status query when ReceiptNumber does not match
OriginatorConversationID.
Access Channel
POS
Possible Causes
ReceiptNumber does not match OriginatorConversationID.
Procedure
Enter only one of the two parameters or two matching parameters for query.
4.152 BCS50153
Description
The entered MTCN does not comply with the MTCN of the third-party system.
Scenario
This error is reported during IMT transaction if the MTCN sent to the third-party system fails
to be verified.
Access Channel
USSD
Possible Causes
The entered MTCN does not comply with the MTCN of the third-party system.
Procedure
Cancel the transaction.

Copyright © Huawei
Mobile Money
4.153 BCS50154
Description
The difference between the estimated amount and the actual amount exceeds the allowed
range.
Scenario
This error is reported during IMT transaction if the difference between the estimated amount
and actual amount exceeds the allowed range.
Access Channel
USSD
Possible Causes
The difference between the estimated amount and the actual amount exceeds the allowed
range.
Procedure
Cancel the transaction.
4.154 BCS50155
Description
The voucher does not support the secret code.
Scenario
This error is reported when the voucher type is configured not to require the secret code but
the voucher secret code is entered.
Access Channel
API
Possible Causes
The voucher secret code is entered.
Procedure
Do not enter the voucher secret code.

Copyright © Huawei
Mobile Money
4.155 BCS50156
Description
The MSISDN of the identity is mandatory.
Scenario
This error is reported when the PIN management mode is Enhanced but the MSISDN of the
identity corresponding to the PIN is empty.
Access Channel
Web
Possible Causes
The MSISDN of the identity is mandatory.
Procedure
Set the MSISDN of the identity.
4.156 BCS50157
Description
The PIN has expired and must be reset before modification.
Scenario
This error is reported when the PIN management mode is Enhanced but the PIN to be
modified has expired.
Access Channel
Web
Possible Causes
The PIN has expired and must be reset before modification.
Procedure
Reset the PIN and then modify it.

Copyright © Huawei
Mobile Money
4.157 BCS50158
Description
The signature of the dormant txn table is tampered with.
Scenario
This error is reported when a refund transaction is initiated after the dormant txn table
signature is tampered with.
Access Channel
Pos
Possible Causes
The system data is abnormal and the signature of the dormant txn table in the background is
tampered with.
Procedure
Contact Huawei engineers for help, or visit http://icare.huawei.com and submit a fault
application report.
4.158 BCS50159
Description
The signature of the customer recycled table is tampered with.
Scenario
This error is reported when a refund transaction is initiated after the customer recycled table
Access Channel
Pos
Possible Causes
The system data is abnormal and the signature of the customer recycled table in the
background is tampered with.
Procedure
application report.

Copyright © Huawei
Mobile Money
4.159 BCS50160
Description
The signature of the org recycled table is tampered with.
Scenario
This error is reported when a refund transaction is initiated after the org recycled table
Access Channel
Pos
Possible Causes
The system data is abnormal and the signature of the org recycled table in the background is
tampered with.
Procedure
application report.
4.160 BCS50161
Description
The signature of the group recycled table is tampered with.
Scenario
This error is reported when a refund transaction is initiated after the group recycled table
Access Channel
Pos
Possible Causes
The system data is abnormal and the signature of the group recycled table in the background
is tampered with.
Procedure
application report.

Copyright © Huawei
Mobile Money
4.161 BCS50162
Description
The input information is incorrect or the system is abnormal.
Scenario
This error is reported when the initial request of the SCB bulk payment fails to be verified.
Access Channel
API
Possible Causes
The initial request of the SCB bulk payment fails to be verified.
Procedure
Apply for the verification again.
4.162 BCS50163
Description
The verification is repeated or the system is abnormal.
Scenario
This error is reported when the SCB bulk payment verification and execution result fail to be
queried.
Access Channel
API
Possible Causes
The SCB bulk payment verification and execution result fail to be query.
Procedure
Apply for the verification again.

Copyright © Huawei
Mobile Money
4.163 BCS50164
Description
The system is abnormal.
Scenario
This error is reported when the SCB bulk daily settlement parameter is missing.
Access Channel
API
Possible Causes
The SCB bulk daily settlement parameter is missing.
Procedure
Perform the query again.
4.164 BCS50165
Description
The input information is incorrect or the system is abnormal.
Scenario
This error is reported when the daily bills fail to be queried.
Access Channel
API
Possible Causes
The daily bills fail to be queried.
Procedure
Perform the query again.

Copyright © Huawei
Mobile Money
4.165 BCS50166
Description
The value of TerritoryId does not exist or a node of the same level already has the
information.
Scenario
This error is reported if the value of TerrotoryId in the Bulk LACCI or Boundary LACCI task
does not exist.
Access Channel
POS
Possible Causes
The value of TerritoryId does not exist or a node of the same level already has the
information.
Procedure
Ensure that the value of TerritoryId exists and nodes of the same level does not have the
information.
4.166 BCS50167
Description
The tax amount cannot be greater than the charge amount.
Scenario
This error is reported during basic transaction taxing if the tax amount is greater than the
charge amount.
Access Channel
Web, STK, USSD, API
Possible Causes
The tax amount cannot be greater than the charge amount.
Procedure
Enter a correct primary transaction amount. To check the tax amount, choose My Functions
> Core Configuration > Tax Code.

Copyright © Huawei
Mobile Money
4.167 BCS50168
Description
The entered identity type does not exist or is in incorrect state.
Scenario
This error is reported when the SCB Bulk Payment identity fails to be verified and the
verification result is {0}
Access Channel
API
Possible Causes
The SCB Bulk Payment identity fails to be verified and the verification result is {0}.
Procedure
Apply for verification again.
4.168 BCS50169
Description
Organization {0} must subscribe to at least one Pay Bill product.
The {0} variable indicates the short code of an organization.
Scenario
This error is reported if the entered organization does not subscribe to any Pay Bill product.
Access Channel
API
Possible Causes
Organization {0} has not subscribed to any Pay Bill product.
Procedure
Subscribe to at least one Pay Bill product for the organization.

Copyright © Huawei
Mobile Money
4.169 BCS50170
Description
Both the credit party and debit party are empty in the request parameters.
Scenario
This error is reported during the identity transaction record list query if both the transaction
credit party and debit party are empty.
Access Channel
USSD,STK,API,WEB
Possible Causes
Both the credit party and debit party are empty in the request parameters.
Procedure
Ensure that at least one of the credit party and debit party is not empty in the request
parameters.
4.170 BCS50171
Description
The time interval between the start time and end time in the request parameters exceeds 24
hours.
Scenario
This error is reported during the identity transaction record list query if the time interval
between the start time and end time in the request parameters exceeds 24 hours.
Access Channel
USSD,STK,API,WEB
Possible Causes
The time interval between the start time and end time in the request parameters exceeds 24
hours.
Procedure
Ensure that the time interval between the start time and end time in the request parameters
does not exceed 24 hours.

Copyright © Huawei
Mobile Money
4.171 BCS50172
Description
The transmitted data or promotion data is incorrect.
Scenario
This error is reported if the promotion data is incorrect during manual coupon rewarding.
Access Channel
POS
Possible Causes
The transmitted data or promotion data is incorrect.
Procedure
Check whether the data you have entered or Promotion data is correct.
4.172 BCS50173
Description
The system stays in the maintenance status.
Scenario
The BO&Transaction field can be disabled before upgrade to reject some services. This error
is reported when the field is enabled before upgrade and all corresponding transactions and
BOs are rejected.
Access Channel
All
Possible Causes
The system stays in the maintenance status.
Procedure
Try again later.

Copyright © Huawei
Mobile Money
4.173 BCS50174
Description
The organization account status cannot be changed independently.
Scenario
This error is reported when the organization account status cannot be changed but an
organization account status change request is initiated.
Access Channel
All
Possible Causes
An organization account status change request is initiated.
Procedure
Do not initiate the organization account status change request.
4.174 BCS50175
Description
The online QR code fails to be generated for the customer.
Scenario
This error is reported when a customer fails to apply for an online QR code through the app.
Access Channel
API
Possible Causes
The online QR code fails to be generated for the customer.
Procedure
Apply for the online QR code again.

Copyright © Huawei
Mobile Money
4.175 BCS50176
Description
No PIN is available.
Scenario
This error is reported when the Customer Get Start PIN service is initiated in the SoapUI but
the value of NeedStartPIN is not 1.
Access Channel
POS
Possible Causes
The PIN cannot be obtained due to system parameter restriction.
Procedure
application report.
4.176 BCS50177
Description
At least one KYC field must be set.
Scenario
This error is reported when the Customer Get Start PIN service is initiated in the SoapUI but
the entered customer KYC information does not exist.
Access Channel
POS
Possible Causes
At least one KYC field must be set.
Procedure
Set at least one KYC field.

Copyright © Huawei
Mobile Money
4.177 BCS50178
Description
The Dompetku MSISDN corresponding to the organization short code {0} cannot be empty.
{0} indicates the organization short code.
Scenario
This error is reported when the Dompetku MSISDN corresponding to the organization short
code is empty.
Access Channel
POS
Possible Causes
The Dompetku MSISDN corresponding to the organization short code {0} is empty.
Procedure
Ensure that the Dompetku MSISDN is not empty.
4.178 BCS50179
Description
The entered MSISDN of the customer does not exist.
Scenario
This error is reported during coupon reward if the entered MSISDN of the customer does not
exist.
Access Channel
POS
Possible Causes
The entered MSISDN of the customer does not exist.
Procedure
Enter the correct MSISDN.

Copyright © Huawei
Mobile Money
4.179 BCS50180
Description
The operator does not have the permission to reward the coupon.
Scenario
This error is reported if the operator rewarding the coupon is not an SP operator.
Access Channel
POS
Possible Causes
The operator rewarding the coupon is not an SP operator.
Procedure
Select an SP operator to perform the reward.
4.180 BCS50181
Description
The entered number of rewarded coupons is invalid.
Scenario
This error is reported during coupon reward if the number of rewarded coupons is invalid.
Access Channel
POS
Possible Causes
The number of rewarded coupons must be greater than 0.
Procedure
Enter a correct number of rewarded coupons.

Copyright © Huawei
Mobile Money
4.181 BCS50182
Description
The message data is incorrect or the configuration is abnormal.
Scenario
This error is reported when the Promotion invokes the Mobile Money system to send an
outbound message but the message fails to be sent.
Access Channel
POS
Possible Causes
The outbound message fails to be sent to the third-party system.
Procedure
Verify the related data and configuration.
4.182 BCS50183
Description
The amount returned by the Promotion is abnormal or is not in the expected format.
Scenario
This error is reported when the special price of an offering is queried but the amount returned
by the Promotion is abnormal.
Access Channel
POS
Possible Causes
The amount returned by the Promotion is abnormal.
Procedure
Ensure that the amount returned by the Promotion is normal and in correct format.

Copyright © Huawei
Mobile Money
4.183 BCS50184
Description
When a bank reconciliation entry is recorded through the API channel, some mandatory fields
are empty.
Scenario
This error is reported when a bank reconciliation entry is recorded through the API channel
but some mandatory fields are empty.
Access Channel
POS
Possible Causes
When a bank reconciliation entry is recorded through the API channel, some mandatory fields
are empty.
Procedure
Ensure that all mandatory parameters are set.
4.184 BCS50185
Description
When a bank reconciliation entry is recorded through the API channel, the Reasontype
parameter is not in the system parameter list.
Scenario
but the Reasontype parameter is not in the system parameter list.
Access Channel
POS
Possible Causes
When a bank reconciliation entry is recorded through the API channel, the Reasontype
parameter is not in the system parameter list.
Procedure
Ensure that the Reasontype parameter is set correctly.

Copyright © Huawei
Mobile Money
4.185 BCS50186
Description
When a bank reconciliation entry is recorded through the API channel, the bank does not
exist.
Scenario
but no bank is found based on BranchId.
Access Channel
POS
Possible Causes
When a bank reconciliation entry is recorded through the API channel, no bank is found based
on BranchId.
Procedure
Ensure that the input parameter values are correct.
4.186 BCS50187
Description
When a bank reconciliation entry is recorded through the API channel, the bank is not in
active state.
Scenario
but the bank is not in active state.
Access Channel
POS
Possible Causes
When a bank reconciliation entry is recorded through the API channel, the bank is not in
active state.
Procedure
Ensure that the input parameter values are correct.

Copyright © Huawei
Mobile Money
4.187 BCS50189
Description
The Validation KYC and Validation KYC value fields must both have values or both be
empty.
Scenario
This error is reported when the bulk payment task is uploaded but only one of the Validation
KYC and Validation KYC value fields in the bulk file has value.
Access Channel
POS
Possible Causes
Only one of the Validation KYC and Validation KYC value fields in the bulk file has value.
Procedure
Set both the Validation KYC and Validation KYC value fields.
4.188 BCS50190
Description
An SP cannot be the initiator of the Dompetku Bill Payment service.
Scenario
This error is reported if an SP initiates a Dompetku Bill Payment transaction as the initiator.
Access Channel
Web
Possible Causes
An SP cannot be the initiator of the Dompetku Bill Payment service.
Procedure
Use an organization as the initiator to initiate the Dompetku Bill Payment service.

Copyright © Huawei
Mobile Money
4.189 BCS50191
Description
The PIN of the primary party fails to be verified.
Scenario
This error is reported when the PIN of the primary party fails to be verified.
Access Channel
POS
Possible Causes
The PIN of the primary party is incorrect.
Procedure
Enter the correct PIN to initiate the request again.
4.190 BCS50192
Description
The PIN of the receiver fails to be verified.
Scenario
This error is reported when the PIN of the receiver fails to be verified.
Access Channel
POS
Possible Causes
The PIN of the receiver is incorrect.
Procedure
Enter the correct PIN to initiate the request again.

Copyright © Huawei
Mobile Money
4.191 BCS50193
Description
Because the bank account entered has existed in the identity, the error occurred in updating
the bank account linked to the identity.
Scenario
This error is reported when a bank account associated to an identity is updated but the bank
account already exists in the identity.
Access Channel
Web, USSD, API
Possible Causes
The bank account already exists in the identity.
Procedure
Enter another bank account.
4.192 BCS50194
Description
Failed to update the bank account associated to the identity.
Scenario
This error is reported when a bank account associated to an identity is updated but the bank
account already exists in another identity.
Access Channel
Web, USSD, API
Possible Causes
The bank account already exists in another identity.
Procedure

Copyright © Huawei
Mobile Money
4.193 BCS50195
Description
The GOODS system returns the error information {0}.
{0}: Error information returned by a third-party system.
Scenario
This error is reported when exchanging for goods in the GOODS system and there are no
sufficient points or goods or the goods have expired.
Access Channel
Web
Possible Causes
Points or goods are insufficient or the goods have expired.
Procedure
Contact the owner of the GOODS system.
4.194 BCS50196
Description
Although the transaction amount is 0 the Decrease Charge is not 0.
Scenario
This error is reported when the 0-value tranaction or action service has been configured
Decrease Charge.
Access Channel
POS
Possible Causes
Although the transaction amount is 0 the Decrease Charge is not 0.
Procedure
Check whether this type of service has been configured Decrease Charge in Reason Type. If
so, remove the configuration or change it to non-Decrease Charge.

Copyright © Huawei
Mobile Money
4.195 BCS50197
Description
The transaction amount is smaller than the total amount of Decrease Charges. After deducting
the charges, the transaction amount is smaller than or equal to 0.
Scenario
This error is reported when the total amount of Decrease Charges is larger than or equal to the
amount of the current transaction.
Access Channel
POS
Possible Causes
The configuration of Charge Profile is incorrect. As a result, the transaction amount is smaller
than the total amount of Decrease Charges. After deducting the charges, the transaction
amount is smaller than or equal to 0.
Procedure
Modifying the charging configuration of the service.
4.196 BCS50198
Description
The configured account type is inconsistent with that required in the transaction requirements.
Scenario
This error is reported when the account type is configured incorrectly.
Access Channel
POS
Possible Causes
The charge account type is configured incorrectly.
Procedure
Ensure that the charge of Decrease is correctly configured in the reason type of the service.

Copyright © Huawei
Mobile Money
4.197 BCS50199
Description
When the credit limit is adjusted, the entered new credit limit is 0.
Scenario
This error is reported during credit limit adjustment if the entered new credit limit is 0.
Access Channel
WEB,API
Possible Causes
The new credit limit entered during credit limit adjustment is incorrect. The credit limit
cannot be 0.
Procedure
Enter a new credit limit that is not 0.
4.198 BCS50200
Description
When the credit limit is adjusted, the entered new credit limit is a negative number.
Scenario
This error is reported during credit limit adjustment if the entered new credit limit is a
negative number.
Access Channel
WEB,API
Possible Causes
The new credit limit entered during credit limit adjustment is less than 0. The credit limit must
be greater than or equal to 0.
Procedure
Enter a correct credit limit.

Copyright © Huawei
Mobile Money
4.199 BCS50201
Description
The new credit limit exceeds the maximum for the account type.
Scenario
This error is reported during credit limit adjustment if the new credit limit exceeds the
maximum for the account type.
Access Channel
WEB,API
Possible Causes
The new credit limit of the current account exceeds the maximum for the account type.
Procedure
Enter a correct new credit limit.
4.200 BCS50202
Description
The target account type does not support the credit limit.
Scenario
This error is reported during credit limit adjustment if the target account type does not support
the credit limit.
Access Channel
WEB,API
Possible Causes
The target account type does not support the credit limit.
Procedure
Ensure that the target account type supports the credit limit.

Copyright © Huawei
Mobile Money
4.201 BCS50203
Description
During repayment, the entered target amount of the credit party should be greater than the
current amount.
Scenario
This error is reported during repayment if the entered target amount of the credit party is less
than or equal to the current amount.
Access Channel
WEB,API
Possible Causes
The account entered during credit limit adjustment does not exist.
Procedure
Ensure that the target account type supports the credit limit.
4.202 BCS50204
Description
During repayment, the entered target amount of the credit party does not match the specified
transaction amount.
Scenario
This error is reported during repayment if the entered target amount of the credit party does
not match the specified transaction amount.
Access Channel
WEB,API
Possible Causes
During repayment, the entered transaction amount cannot make the account balance after
repayment reaches the target amount.
Procedure
Enter the correct target amount and transaction amount.

Copyright © Huawei
Mobile Money
4.203 BCS50205
Description
During credit limit adjustment, the specified account is not entered and the default account to
be adjusted is not found.
Scenario
This error is reported during credit limit adjustment if Account No is not entered and the
default account to be adjusted is not found.
Access Channel
WEB,API
Possible Causes
The Account No is not entered and no or multiple accounts to be adjusted are matched.
Procedure
Enter the specified account to adjust the credit limit.
4.204 BCS50206
Description
During credit limit adjustment, the entered currency does not match the account number.
Scenario
This error is reported during credit limit adjustment if the entered currency does not match the
account number.
Access Channel
WEB,API
Possible Causes
During credit limit adjustment, the currency of the account to be adjusted is inconsistent with
the entered currency.
Procedure
Enter the correct currency and account number.

Copyright © Huawei
Mobile Money
4.205 BCS50207
Description
The initiator of the credit limit adjustment is incorrect.
Scenario
This error is reported if the initiator of the credit limit adjustment is not an SP operator.
Access Channel
WEB,API
Possible Causes
Only an SP operator can initiate the credit limit adjustment operation.
Procedure
Enter the initiator information.
4.206 BCS50208
Description
The entered bank information does not exist in the system.
Scenario
This error is reported during organization creation if the entered bank name or bank ID is
incorrect.
Access Channel
POS
Possible Causes
When an organization is created, only the bank information exists in the system can be
entered.
Procedure
Enter the correct bank information.

Copyright © Huawei
Mobile Money
4.207 BCS50209
Description
The bank information is not entered.
Scenario
This error is reported during organization creation when the bank information mandatory for
the trust level corresponding to the selected product is empty.
Access Channel
POS
Possible Causes
When an organization is created, the bank information is mandatory for the trust level
corresponding to the selected product.
Procedure
Change the product or add the bank information.
4.208 BCS50210
Description
Related information needs to be entered in sequence.
Scenario
This error is reported during organization creation if the bank information is not entered in the
required sequence.
Access Channel
POS
Possible Causes
When an organization is created, the bank information is not entered in the required sequence.
Procedure
Configure information in the following sequence: [Bank], [Bank Branch], [Bank Account
Name], [Bank Account Number], and [Currency].

Copyright © Huawei
Mobile Money
4.209 BCS50211
Description
The balance in account {2} of account type {1} of identity {0} is insufficient for the
transaction.
{0}: indicates identity name.

{1}: indicates account type.
{2}: indicates account.
Scenario
The account balance of a subscriber is insufficient during transaction execution.
Access Channel
Web, STK, USSD, API
Possible Causes
The balance in the specified account is insufficient for the transaction.
Procedure
Recharge through an SP or agent.
4.210 BCS50212
Description
When the credit limit of a subscriber account is adjusted, the account {0} is abnormal.
 {0}: indicates the account name.

 {1}: indicates the current status of the account.
 {2}: indicates the list of accounts whose credit limit can be adjusted.
Scenario
This error is reported when the credit limit of a subscriber account is adjusted but the account
is abnormal.
Access Channel
Web, API

Copyright © Huawei
Mobile Money
Possible Causes
When the credit limit of a subscriber account is adjusted, the account {0} is in {1} state. The
credit limit can be adjusted only for accounts in {2} state.
Procedure
Specify a normal account or change the status of the account.
4.211 BCS50213
Description
No matching bank is found based on the bank name and branch name.
Scenario
This error is reported when the identity bank account is added, deleted, or modified but the
parsed bank fails the verification.
Access Channel
POS
Possible Causes
No matching bank is found based on the bank name and branch name.
Procedure
Verify that the entered bank exists in the system.
4.212 BCS50214
Description
No matching bank account is found based on the bank name and branch name.
Scenario
parsed bank account fails the verification.
Access Channel
POS

Copyright © Huawei
Mobile Money
Possible Causes
No matching bank account is found based on the bank name and branch name.
Procedure
Verify that the entered bank account exists in the system.
4.213 BCS50215
Description
The identity is not in the active state and the bank account of the identity cannot be operated.
Scenario
parsed identity fails the verification.
Access Channel
POS
Possible Causes
The identity is not in the active state.
Procedure
Ensure that the identity is in the active state.
4.214 BCS50216
Description
The entered parameters are incomplete and the bank account cannot be operated.
Scenario
entered parameters are incomplete and fail the verification.
Access Channel
POS
Possible Causes
The entered parameters are incomplete.

Copyright © Huawei
Mobile Money
Procedure
Enter complete parameters.
4.215 BCS50217
Description
The entered bank is not in the active state and the operation is not allowed.
Scenario
entered bank is not in the active state and fails the verification.
Access Channel
POS
Possible Causes
The entered bank is not in the active state.
Procedure
Ensure that the bank is in the active state.
4.216 BCS50218
Description
Bank accounts of the others type cannot be modified and bank accounts cannot be changed to
be of the others type.
Scenario
This error is reported when the bank account is changed to be of the others type or the bank
account of the others type is modified.
Access Channel
POS
Possible Causes
The modification is incorrect.

Copyright © Huawei
Mobile Money
Procedure
Do not modify bank accounts of the others type or change bank accounts to be of the others
type.
4.217 BCS50219
Description
The credit limit cannot be performed for the entered receiver.
Scenario
This error is reported when the credit limit is adjusted for the entered receiver.
Access Channel
Web, API
Possible Causes
Currently, the credit limit can be adjusted only for customers, organizations, and groups. The
entered receiver is not one of them.
Procedure
Enter a correct receiver.
4.218 BCS50220
Description
When the rule profile of an SP operator is modified, the transferred rule profile is empty.
Scenario
This error is reported when the rule profile of an SP operator is modified but the transferred
rule profile is empty.
Access Channel
POS
Possible Causes
When the rule profile of an SP operator is modified, the transferred rule profile is empty.

Copyright © Huawei
Mobile Money
Procedure
Ensure that the transferred rule profile is not empty.
4.219 BCS50221
Description
When the rule profile of an SP operator is modified, the transferred rule profile is the same as
the existing one.
Scenario
This error is reported when the rule profile of an SP operator is modified but the transferred
rule profile is the same as the existing one.
Access Channel
POS
Possible Causes
When the rule profile of an SP operator is modified, the transferred rule profile is the same as
the existing one.
Procedure
Ensure that the transferred rule profile is different from the rule profile to be modified.
4.220 BCS50222
Description
The bank account change fails.
Scenario
This error is reported when you change a bank account through api channel and the bank
account does not exist.
Access Channel
POS
Possible Causes
This error is reported when you change a bank account that does not exist.

Copyright © Huawei
Mobile Money
Procedure
Check whether the bank account exists in the system.
4.221 BCS50223
Description
The TrustLevel of the offering requires bank information. The bank account cannot be
deleted.
Scenario
This error is reported when you delete an organization's only one bank account and bank
information is required by the organization's TrustLevel.
Access Channel
API
Possible Causes
The TrustLevel of the offering requires bank information. The bank account cannot be
deleted.
Procedure
Enter bank information.
4.222 BCS50224
Description
Failed to create the operator because the rule profile ID does not belong to the sp operator.
Scenario
When an operator is created, the rule profile does not belong to the SP operator.
Access Channel
POS
Possible Causes
Rule profile {0} does not belong to an sp operator.
{0}: indicates a rule profile name.

Copyright © Huawei
Mobile Money
Procedure
Fill in a rule profile.
4.223 BCS50225
Description
Data in the fundsReserveRecord table is tampered with.
Scenario
This error is reported when the accout signature fails and the data is tampered with.
Access Channel
POS
Possible Causes
Data in the fundsReserveRecord table is tampered with.
Procedure
Ensure that the data is correct.
4.224 GV50000
Description
The password status of the receiving party {0} is {1}. Status authentication failed, and the
current service cannot be processed. {1} is the password status, such as Locked.
{0}: indicates name of a receiver party.

{1}: indicates status of a password.
Scenario
All the BOs and transactions whose password status must be authenticated.
Access Channel
Web, USSD, STK, API
Possible Causes
Service processing failed because the password status of a transaction receiving party is
invalid.

Copyright © Huawei
Mobile Money
Procedure
Change the password status of the transaction receiving party.
4.225 GV50001
Description
The entity of the registration party must be an SP or organization.
Scenario
All the business operation (BO) operations and transaction operations.
Access Channel
Web, USSD, STK, API
Possible Causes
Procedure
4.226 GV50002
Description
The entity of the initiating party must be an operator or customer.
Scenario
All the BO operations and transaction operations.
Access Channel
Web, USSD, STK, API
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
4.227 GV50003
Description
The access device must be a till or customer.
Scenario
All the BO operations or transaction operations that a till or customer takes part in.
Access Channel
Web, USSD, STK, API
Possible Causes
Procedure
4.228 GV50004
Description
The entity ID {0} is not supported.
{0}: uniquely identifies an identity. For example, the MSISDN value of a customer is 4000000.
Scenario
All the BO operations and transaction operations.
Access Channel
Web, USSD, STK, API
Possible Causes
The entity ID {0} is not supported.
Procedure
Enter an existing entity ID.

Copyright © Huawei
Mobile Money
4.229 GV50005
Description
The personal identification number (PIN) of the {0} receiver is in the {1} status which does
not support the current service.

{1}: indicates status of the entity PIN.
Scenario
All BO operations and transaction operations that have requirements on identity PIN status.
Access Channel
Web, USSD, STK, API
Possible Causes
Service processing failed due to the incorrect PIN status of a transaction party.
Procedure
Modify the PIN status of the transaction party.
4.230 GV50006
Description
The customer's mobile station international ISDN number (MSISDN) is not within the
specified range.
Scenario
A customer is created or customer MSISDN is changed.
Access Channel
Web, USSD
Possible Causes
The MSISDN does not exist in the range.
Procedure
View MSISDN range of the customer. Check whether the MSISDN is in the range. If the
MSISDN is not in the range, select the MSISDN in the range.

Copyright © Huawei
Mobile Money
4.231 GV50007
Description
The till's MSISDN is not within the specified range.
Scenario
A till is created or the till MSISDN is changed.
Access Channel
Web, USSD
Possible Causes
Procedure
View MSISDN range of the till. Check whether the MSISDN is in the range. If the MSISDN
is not in the range, select the MSISDN in the range.
4.232 GV50008
Description
The organization operator's MSISDN is not within the specified range.
Scenario
An operator is created and the operator MSISDN is changed.
Access Channel
Web, USSD
Possible Causes
Procedure
View MSISDN range of the organization operator. Check whether the MSISDN is in the
range. If the MSISDN is not in the range, select the MSISDN in the range.

Copyright © Huawei
Mobile Money
4.233 GV50009
Description
There are duplicate fields in the bulk file.
Scenario
Access Channel
Web
Possible Causes
There are more than one {0} fields.
{0}: indicates field name in bulk files.
Procedure
Delete the duplicate fields.
4.234 GV50010
Description
The {0} order cannot be cancelled.
{0}: indicates order ID.
Scenario
The transaction cancellation operation is initiated on the portal.
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
4.235 GV50011
Description
The Password of the {0} receiver is in the {1} status which does not support the current
service.

{1}: indicates password status.
Scenario
All the BO operations whose password status is to be verified.
Access Channel
Web, USSD, STK, API
Possible Causes
Service processing failed due to a status authentication failure.
Procedure
Modify the Password status of the transaction party.
4.236 GV50012
Description
The Till status is incorrect.
Scenario
All the BO operations that a till takes part in.
Access Channel
Web, USSD, STK, API
Possible Causes
The Till status is incorrect.
Procedure
Modify the Till status.

Copyright © Huawei
Mobile Money
4.237 GV50016
Description
Failed to parse the parameter {0}.
{0}: indicates parameter name in bulk files.
Scenario
This error occurs when parameter parsing failed because the input of parameter names related
to a bulk task is incorrect.
Access Channel
Web
Possible Causes
The {0} parameter name is incorrect.
Procedure
Verify that the parameter name is correct.
4.238 GV50013
Description
The file content lacks root node {0}.
{0}: indicates root note.
Scenario
The content of bulk files to be imported is verified.
Access Channel
Web
Possible Causes
Procedure
Verify that the file content meets the template requirements.

Copyright © Huawei
Mobile Money
4.239 GV50014
Description
The {0} field is mandatory.
{0} variable indicates the field name in bulk files.
Scenario
The content of bulk files to be imported is verified.
Access Channel
Web
Possible Causes
Procedure
4.240 GV50015
Description
Failed to modify the know your customer (KYC) field.
Scenario
The identity KYC is changed.
Access Channel
Web, USSD, STK, API
Possible Causes
The {0} KYC field is read-only and cannot be modified.
{0} variable indicates the KYC field name.
Procedure
1. Choose My Functions > Operational Configuration > KYC Configuration > KYC
Field.

Copyright © Huawei
Mobile Money
2. Search for the field and verify its attributes.
4.241 GV50017
Description
The value length exceeds the upper limit.
Scenario
All the BO operations that carry digit parameters.
Access Channel
Web, USSD, STK, API
Possible Causes
The value length exceeds the upper limit.
Procedure
Enter a value with a proper length.
4.242 GV50018
Description
The bulk file is invalid. Error message: {0}
The {0} variable indicates bulk file field content whose format is incorrect.
Scenario
The content and format of bulk files in a bulk is verified.
Access Channel
Web
Possible Causes
The content of the bulk file is in an incorrect format.
Procedure
Modify the file content as required.

Copyright © Huawei
Mobile Money
4.243 GV50019
Description
The bulk file fails to be verified because the number of fields in the {0} record is incorrect.
Scenario
The number of fields in the {0} record in the bulk file is verified when the bulk task verifies
the upload bulk file.
Access Channel
Web
Possible Causes
Procedure
Upload an effective bulk file.
4.244 GV50020
Description
Verification failed. MSISDN {0} must be set to a numeral.
The {0} variable indicates an MSISDN for number porting.
Scenario
The MSISDN is verified during some actions, such as number porting, customer creation.
Access Channel
Web, USSD, STK
Possible Causes
Verification failed. MSISDN {0} must be set to a numeral.
Procedure
Enter a valid MSISDN.

Copyright © Huawei
Mobile Money
4.245 GV50021
Description
The service fails to be processed because the PIN status of {0} is {1} and fails to be
authenticated.
The {0} variable indicates the description of an identity, and the {1} variable indicates the status of a
PIN.
Scenario
All the BO operations, actions or transactions that need to verify PIN status.
Access Channel
Web, USSD, STK, API
Possible Causes
The service fails to be processed because the PIN status is invalid.
Procedure
Change the status of the PIN.
4.246 GV50022
Description
Failed to create the operator.
Scenario
An operator is created.
Access Channel
Web, API
Possible Causes
The operator name already exists.
Procedure
Change the operator name.

Copyright © Huawei
Mobile Money
4.247 GV50023
Description
Failed to create the operator because the operator ID already exists.
Scenario
An operator is created.
Access Channel
Web, USSD, STK, API
Possible Causes
The operator ID already exists.
Procedure
Change the operator ID.
4.248 GV50024
Description
Failed to subscribe to the product for the identity.
Scenario
An identity product is subscribed.
Access Channel
Web
Possible Causes
The identity has already subscribed to the product.
Procedure
Change the product to be added.

Copyright © Huawei
Mobile Money
4.249 GV50025
Description
The {0} field cannot exist in the bulk file.
{0} variable indicates the invalid field name.
Scenario
The content of bulk files to be uploaded is verified.
Access Channel
Web, API
Possible Causes
The {0} field cannot exist in the bulk file.
Procedure
4.250 GV50026
Description
The value of KYC {0} is incorrect.
The {0} variable indicates the KYC field name.
Scenario
The KYC of an Identity is modified.
Access Channel
Web, USSD, API
Possible Causes
The value of KYC {0} is incorrect.
Procedure
Please check the KYC value.

Copyright © Huawei
Mobile Money
4.251 GV50027
Description
The content of the bulk file is incorrect.
Scenario
The input file content in a bulk task is incorrect.
Access Channel
Web, API
Possible Causes
Procedure
Verify that the content meets the format requirement of the template.
4.252 GV50028
Description
Task assignment failed.
Scenario
An SP or organization operator assigns a workflow task to another operator.
Access Channel
Web
Possible Causes
The operator who assigns task {0} to another operator is not the task owner.
The {0} variable indicates the ID of the task to be assigned.
Procedure
Only the owner of a task can assign the task to another operator.

Copyright © Huawei
Mobile Money
4.253 GV50029
Description
Task escalation failed.
Scenario
An SP or organization operator manually escalates a workflow task to inform an operator at a
higher level.
Access Channel
Web
Possible Causes
No escalation rule is configured for task {0}.
The {0} variable indicates the ID of the task to be assigned.
Procedure
Configure escalation rules for the task before escalating it.
4.254 GV50030
Description
Task investigation failed.
Scenario
A task owner can specify another operator to investigate a task if the owner has misgivings
about the task.
Access Channel
Web
Possible Causes
No operator is specified for the task investigation.
Procedure
Specify an operator for the task investigation.

Copyright © Huawei
Mobile Money
4.255 GV50031
Description
Scenario
An SP or organization operator can initiate investigation for certain workflow tasks if they
have misgivings about the task, but some tasks cannot be investigated.
Access Channel
Web
Possible Causes
Task {0} does not support investigation.
The {0} variable indicates the ID of a task that cannot be investigated.
Procedure
The task does not support investigation.
4.256 GV50032
Description
Cannot find the bulk data uniqueness getter.
Scenario
Cannot find the bulk data uniqueness getter when verifying bulk data.
Access Channel
-
Possible Causes
The data uniqueness key is incorrect.
Procedure
Please verify the data uniqueness key.

Copyright © Huawei
Mobile Money
4.257 GV50033
Description
Customer care authentication for the initiator failed.
Scenario
Customer care authentication for the initiator failed during a public authentication for a
transaction or action.
Access Channel
Web, STK, USSD, API
Possible Causes
Customer care authentication for the initiator failed.
Procedure
Change the initiator or wait until the initiator status is not Suspended in the Customer Care
system.
4.258 GV50034
Description
The short code is in an incorrect format.
Scenario
When an organization is created or when an organization attribute is modified, the short code
format is incorrect.
Access Channel
Web, API
Possible Causes
Short code {0} is in an incorrect format.
The {0} variable indicates the short code.
Procedure
Enter a short code in the correct format.

Copyright © Huawei
Mobile Money
4.259 GV50035
Description
The {0} parameter must be set to a numeral.
The {0} field indicates the name of a bulk field in the bulk file.
Scenario
The field must be set to a numeral.
Access Channel
Web, API
Possible Causes
Procedure
Verify the {0} field in the bulk file that is uploaded.
4.260 GV50036
Description
A bulk file cannot contain multiple {0}:{1}.
The {0} variable indicates the name of a bulk field in the bulk file.
The {1} variable indicates the value of the {0} field.
Scenario
Records in a bulk file must be unique.
Access Channel
Web
Possible Causes
There are multiple {0}:{1} in the same bulk file
Procedure
Verify whether the file that is uploaded contains multiple {0}:{1}.

Copyright © Huawei
Mobile Money
4.261 GV50037
Description
The till product already exists.
Scenario
When till products are added in bulk, the system reports this error if a till product already
exists.
Access Channel
Web
Possible Causes
The till product already exists.
Procedure
Modify the till product and try again.
4.262 GV50038
Description
The {0} parameter is mandatory and cannot be set to a space.
The {0} variable indicates the parameter name.
Scenario
A mandatory parameter in a bulk task file is set to a space.
Access Channel
Web
Possible Causes
The {0} mandatory parameter is set to a space.
Procedure
Verify that the {0} parameter is not set to a space.

Copyright © Huawei
Mobile Money
4.263 GV50039
Description
Authentication failed. The organization status of the initiator is not Active.
Scenario
The organization status of the initiator is not Active during customer care handset (CCH)
transaction reversal.
Access Channel
STK, USSD
Possible Causes
Authentication failed. The organization status of the initiator is not Active.
Procedure
Change the organization status of the initiator to Active.
4.264 GV50040
Description
Authentication failed. The status of the receiver is not Active or Capped.
Scenario
The status of the receiver is not Active or Capped during CCH transaction reversal.
Access Channel
STK, USSD
Possible Causes
Authentication failed. The status of the receiver is not Active or Capped.
Procedure
Change the status of the receiver to Active or Capped.

Copyright © Huawei
Mobile Money
4.265 GV50041
Description
Revenue settlement failed.
Scenario
When an SP or organization operator initiates revenue settlement for an organization, no
revenue settlement information has been configured for the organization.
Access Channel
Web, System
Possible Causes
The revenue settlement configuration information does not exist.
Procedure
View the organization details page and verify whether revenue settlement information is
configured for the organization.
4.266 GV50042
Description
The content under {0} is empty.
0: node ID is an XML file.
Scenario
The content under a node in the bulk task file uploaded is empty.
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
4.267 GV50043
Description
Operation failed because KYC Field Type:{0} is not unique.
{0}: indicates a duplicate KYC Field Type, such as [Personal Info][CNIC].
Scenario
Verification during bulk operation.
Access Channel
Web
Possible Causes
KYC Field Type:{0} is not unique.
Procedure
Verify that the content of the bulk file is correct.
4.268 GV50044
Description
Customer care authentication for the receiver failed.
Scenario
Customer care authentication for the receiver failed during a public authentication for a
transaction or action.
Access Channel
Web, STK, USSD, API
Possible Causes
Customer care authentication for the receiver failed.
Procedure
Change the receiver or wait until the receiver status is not Suspended in the Customer Care
system.

Copyright © Huawei
Mobile Money
4.269 GV50045
Description
Service authentication failed because identity {0} to which the transaction debit account
belongs is in the {1} status.
{0}: indicates the name of an identity, such as ww.

{1}: indicates the current status of an identity.
Scenario
The status of a transaction party fails to be authenticated during a transaction.
Access Channel
Web, STK, USSD, API
Possible Causes
Service processing failed because the status of a transaction party is invalid.
Procedure
Modify the status of the transaction party.
4.270 GV50046
Description
Service authentication failed because organization {0} to which the transaction debit party

Scenario
Access Channel
Web, STK, USSD, API
Possible Causes

Copyright © Huawei
Mobile Money
Procedure
4.271 GV50047
Description
Service authentication failed because organization {0} to which the transaction credit party

Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
4.272 GV50048
Description
Service authentication failed because organization {0} is in the {1} status.

Scenario
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
Procedure
4.273 GV50049
Description
Service authentication failed because identity {0} to which the transaction credit account

Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
4.274 GV50050
Description
Service authentication failed because organization {0} to which the transaction credit party
{0}: indicates the name of an identity.

Scenario
The status of an identity is invalid during a transaction.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
Service processing failed because the status of the organization to which the transaction credit
party belongs is invalid.
Procedure
Modify the status of the organization to which the transaction credit party belongs.
4.275 GV50051
Description
Service authentication failed because organization {0} to which the transaction debit party

Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Service processing failed because the status of the organization to which the transaction debit
party belongs is invalid.
Procedure
Modify the status of the organization to which the transaction debit party belongs.
4.276 GV50052
Description
Service authentication failed because the identity {0} to which the access device belongs is in
the {1} state.

Copyright © Huawei
Mobile Money

Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Service processing failed because the status of the identity to which the access device belongs
is invalid.
Procedure
Modify the status of the identity {0} to which the access device belongs.
4.277 GV50053
Description
The receiver does not exist.
Scenario
A receiver whose information is to be queried does not exist.
Access Channel
Web, STK, USSD, API
Possible Causes
 The identity is not registered.
 The query conditions are incorrect.
Procedure
1. Verify that the identity is registered.
2. Verify that the query conditions are correct.

Copyright © Huawei
Mobile Money
4.278 GV50054
Description
The initiator does not exist.
Scenario
An initiator whose information is to be queried does not exist.
Access Channel
Web, STK, USSD, API
Possible Causes
 The identity is not registered.
Procedure
1. Verify that the identity is registered.
4.279 GV50055
Description
The account owner identity {0} of the credit party is in the {1} status. Status authentication
fails, and the current service is forbidden.
{0}: indicates identity identifier, for example, MSISDN or short code.

{1}: indicates identity status.
Scenario
Identity status is invalid when a transaction is initiated.
Access Channel
Web, STK, USSD, API
Possible Causes
The account owner identity status of the credit party is incorrect, causing a service failure.
Procedure
Change the account owner identity status of the credit party.

Copyright © Huawei
Mobile Money
4.280 GV50056
Description
The account owner identity {0} of the debit party is in the {1} status. Status authentication
fails, and the current service is forbidden.
{0}: indicates identity identifier, for example, MSISDN or short code.

Scenario
Identity status is invalid when a transaction is initiated.
Access Channel
Web, STK, USSD, API
Possible Causes
The account owner identity status of the debit party is incorrect, causing a service failure.
Procedure
Change the account owner identity status of the debit party.
4.281 GV50057
Description
An encryption exception has occurred, Encryption failed.
Scenario
Encryption failed. Possible causes include: the key is incorrect or does not exist, or the
connection to the HSM is terminated.
Access Channel
Web, STK, USSD, API
Possible Causes

Copyright © Huawei
Mobile Money
Procedure
Change the key based on the exception description and try again. If the problem persists,
locate the error cause and perform troubleshooting based on information in the
/log/debug/*_debug.log file under the help of a Huawei engineer.
4.282 GV50058
Description
The preferred notification language input is incorrect.
Scenario
This error occurs if the input preferred notification language is incorrect when an SP operator
or organization operator creates organizations in batches or changing organization KYCs on
the web client.
Access Channel
Web, API
Possible Causes
The system does not support the preferred notification language.
Procedure
Choose My Functions > Core Configuration > Language and check whether the preferred
notification language is within the language code range.
4.283 GV50059
Description
Localization configuration of the date or time is incorrect.
Scenario
Localization of the date or time is not configured.
Access Channel
Web
Possible Causes
Localization configuration of the date or time in the default language does not exist.

Copyright © Huawei
Mobile Money
Procedure
1. Choose My Functions > Core Configuration > Language and check the default
language configuration.
2. Choose My Functions > Operational Configuration > Localization > Date and Time
and check localization configuration of the date or time in the default language.
4.284 GV50060
Description
The system is busy. Try again later.
Scenario
All transaction operations.
Access Channel
Web, STK, USSD, API
Possible Causes
Failed to verify whether the transaction request is repetitive.
Procedure
Obtain the BCS debug logs and contact a Huawei engineer for help, or access
http://icare.huawei.com and submit a fault report.
4.285 GV50061
Description
The number of optimistic lock update times has exceeded the upper limit {0}.
{0}: indicates the number of times an optimistic lock can be updated.
Scenario
When a user clicks Cancel during a Send Money or Pay Bill transaction by USSD, the number
of optimistic lock update times has exceeded the upper limit.
Access Channel
USSD

Copyright © Huawei
Mobile Money
Possible Causes
The system is busy.
Procedure
Try again later.
4.286 GV50062
Description
There are multiple Customer Name Search records.
Scenario
When a user clicks Cancel during a Send Money or Pay Bill transaction by USSD, there are
duplicate records when the system updates the counter.
Access Channel
USSD
Possible Causes
The database contains duplicate data.
Procedure
Check whether the database contains duplicate data.
4.287 GV50067
Description
The Channel parameter is invalid.
Scenario
When the PIN or password of the initiator is decrypted, the decryption method varies based
on the channel parameter from the access gateway (AG). If the channel reported by the AG is
invalid, the system reports this error.
Access Channel
STK, API

Copyright © Huawei
Mobile Money
Possible Causes
The Channel parameter is invalid.
Procedure
Send identity center logs in the /log/debug/ic_debug.log to a Huawei engineer for fault
diagnosis.
4.288 GV50068
Description
Decryption failed. The obfuscated security credential is shorter than the minimum length.
Scenario
When an obfuscated security credential is decrypted, the length of the security credential is
less than the prefix length or the minimum length of an obfuscated security credential.
Access Channel
STK, API
Possible Causes
Decryption failed. The obfuscated security credential is shorter than the minimum length.
Procedure
Obfuscate the security credential in a correct format.
4.289 GV50069
Description
The Timestamp is inconsistent with that in the ciphertext.
Scenario
When an operation is initiated through the API channel, the specified Timestamp is
inconsistent with the ciphertext value.
Access Channel
API

Copyright © Huawei
Mobile Money
Possible Causes
The Timestamp is inconsistent with that in the ciphertext.
Procedure
Enter a valid Timestamp that is consistent with the timestamp in the ciphertext.
4.290 GV50070
Description
The value of OriginatorConversationID is inconsistent with that in the ciphertext.
Scenario
When an operation is initiated through the API channel, the specified
OriginatorConversationID is inconsistent with the ciphertext value.
Access Channel
API
Possible Causes
The value of OriginatorConversationID is inconsistent with that in the ciphertext.
Procedure
Enter a valid OriginatorConversationID that is consistent with the
OriginatorConversationID in the ciphertext.
4.291 GV50071
Description
Failed to decrypt the security credential of the initiator.
Scenario
When an operation is initiated through the API channel, KeyOwner is set to 2 but the initiator
is not an organization operator.
Access Channel
API

Copyright © Huawei
Mobile Money
Possible Causes
Failed to decrypt the security credential of the initiator.
Procedure
If KeyOwner is set to 2, the initiator must be an organization operator.
4.292 GV50072
Description
Decryption failed. The organization PIN key does not exist.
Scenario
When an operation is initiated through the API channel, the organization PIN key does not
exist.
Access Channel
API
Possible Causes
Decryption failed. The organization PIN key does not exist.
Procedure
diagnosis.
4.293 GV50073
Description
The KeyOwner parameter is invalid.
Scenario
When an operation is initiated through the API channel, the KeyOwner field is set to an
invalid value.
Access Channel
API

Copyright © Huawei
Mobile Money
Possible Causes
The KeyOwner parameter is invalid.
Procedure
Enter a valid KeyOwner. The value 1 indicates that an API caller key is used. The value 2
indicates that an organization key is used.
4.294 GV50074
Description
Decryption failed. The specified counter is inconsistent with that in the ciphertext.
Scenario
When an operation is initiated through the STK channel, the specified Counter is inconsistent
with the ciphertext value.
Access Channel
STK
Possible Causes
Decryption failed. The specified counter is inconsistent with that in the ciphertext.
Procedure
Enter correct ciphertext in the PIN+Counter format.
4.295 GV50075
Description
Failed to authenticate the API caller. The password is incorrect.
Scenario
When an operation is initiated through the API channel, the password is incorrect when the
API caller is authenticated.
Access Channel
API

Copyright © Huawei
Mobile Money
Possible Causes
Failed to authenticate the API caller. The password is incorrect.
Procedure
Enter a correct password.
4.296 GV50076
Description
If the Exclude Rule Profile attribute is set to No, the account rule profile of account type {0}
must not be empty.
{0}: indicates the name of an account type.
Scenario
When customers are created in bulk or by USSD, the Exclude Rule Profile attribute is set to
No but the account type is not associated with an account rule profile.
Access Channel
Web, API, USSD, STK
Possible Causes
 No account rule profile is configured for the account type.
 No default account rule profile is associated with account type {0}.
Procedure
 Specify an account rule profile for the account type.
 Configure a default account rule profile for account type {0} in the My Functions >
Operational Configuration > Assignment Management > Account Rule Profile
menu.
4.297 GV50077
Description
The specified organization is not in the Active state.
Scenario
When an internal account is created, the specified organization is not in the Active state.

Copyright © Huawei
Mobile Money
Access Channel
Web, API, USSD, STK
Possible Causes
The specified organization is not in the Active state.
Procedure
Enter an organization in the Active state.
4.298 GV50078
Description
If the Exclude Rule Profile attribute is set to Yes for account type {0}, the Account Rule
Profile parameter must be left empty for the account type.
{0}: indicates the name of an account type.
Scenario
When the account rule profile of a customer is modified, if the Exclude Rule Profile attribute
is set to Yes for account type, the Account Rule Profile parameter must be left empty for the
account type.
Access Channel
Web, Web(Bulk), USSD, STK, API
Possible Causes
The Account Rule Profile parameter is not empty.
Procedure
Leave the Account Rule Profile parameter empty.
4.299 GV50079
Description
The credential value is the same as the operator ID or the inverted operator ID.
{0}: indicates security credential name.

Copyright © Huawei
Mobile Money
Scenario
Security credential of an Identity is modified or the security credential is created.
Access Channel
Web, USSD, STK, API
Possible Causes
The value of {0} must be different from the operator ID or the inverted operator ID.
Procedure
Enter a correct credential.
4.300 GV50080
Description
The BO or transaction has failed because the task has been rejected.
Scenario
When the task of a transaction or BO initiated through an API is rejected, this error code is
returned to the AG.
Access Channel
API
Possible Causes
The task is rejected.
Procedure
Abandon this operation.
4.301 GV50081
Description
The BO or transaction has failed because the task has expired.
Scenario
When the task of a transaction or BO initiated through an API has expired, this error code is
returned to the AG.

Copyright © Huawei
Mobile Money
Access Channel
API
Possible Causes
The task to be approved has expired.
Procedure
Initiate the transaction or BO again and remind the approver to approval the task.
4.302 GV50082
Description
When the trust level of an identity is degraded after KYC change, account type {0} has no
default account rule profile.
{0}: indicates account type name.
Scenario
When the trust level of an identity is degraded after KYC change, an account type has no
Access Channel
Web, Web(Bulk), USSD, STK, API
Possible Causes
When the trust level of an identity is degraded after KYC change, account type {0} has no
Procedure
Configure a default account rule profile for account type {0} in the My Functions >
Operational Configuration > Assignment Management > Account Rule Profile menu.
4.303 GV50083
Description
The API password of the {0} initiator is in the {1} state which does not support the current
service.

Copyright © Huawei
Mobile Money
{0}: indicates the name of an initiator.

{1}: indicates the API password status of an initiator.
Scenario
All actions that require permission control.
Access Channel
API
Possible Causes
Procedure
4.304 GV50084
Description
The structure version must be set to a 2-digit numeral.
Scenario
During PIN obfuscation, the structure version parameter is not set to a numeral.
Access Channel
API
Possible Causes
The structure version is not a numeral.
Procedure
Set the structure version to a 2-digit numeral.
4.305 GV50085
Description
The obfuscation parameter must be set to a 4-digit string containing letters and digits.

Copyright © Huawei
Mobile Money
Scenario
During PIN obfuscation, the obfuscation parameter contains characters other than digits and
letters.
Access Channel
API
Possible Causes
The obfuscation parameter contains characters other than digits and letters.
Procedure
Set the obfuscation parameter to a 4-digit string containing letters and digits.
4.306 GV50086
Description
The Sequence Number parameter must be set to a 2-digit numeral.
Scenario
During PIN obfuscation, the Sequence Number parameter is not set to a 2-digit numeral.
Access Channel
API
Possible Causes
The Sequence Number parameter is not set to a numeral.
Procedure
Set the Sequence Number parameter to a 2-digit numeral.
4.307 GV50087
Description
Operation failed. The encryption algorithm used by the ApiCaller must be the same as that
used by the initiator when KeyOwner is set to 1.

Copyright © Huawei
Mobile Money
Scenario
When KeyOwner is set to 1 for an operation initiated through an API, the error code is
reported if the encryption algorithm used by the ApiCaller is different from that used by the
initiator.
Access Channel
API
Possible Causes
KeyOwner is set to 1, and the encryption algorithm used by the ApiCaller is different from
that used by the initiator.
Procedure
Verify that the encryption algorithm used by the ApiCaller is the same as that used by the
initiator.
4.308 GV50089
Description
No default charge profile is specified for the new trust level, and the original charge profile is
not an assignable charge profile for the new trust level.
Scenario
When an operator modifies an identity's KYC information on the portal or using a bulk task,
the identity's trust level changes and the system sets the identity's charge profile to the default
charge profile specified for the new trust level. If no default charge profile is specified for the
new trust level, the system checks whether the original charge profile is an assignable charge
profile for the new trust level. If the original charge profile is not an assignable charge profile
for the new trust level, the system generates this error code.
Access Channel
Web
Possible Causes
The identity's charge profile is not an assignable charge profile for trust level {0}.
{0} indicates trust level name.
Procedure
Modify parameter settings and retry.

Copyright © Huawei
Mobile Money
4.309 GV50090
Description
No default charge profile is specified for the product, and the original charge profile is not an
assignable charge profile for the product.
Scenario
the identity's trust level changes and the system sets the identity's charge profile to the default
charge profile specified for the new trust level. If no default charge profile is specified for the
product, the system checks whether the original charge profile is an assignable charge profile
for the product. If the original charge profile is not an assignable charge profile for the
product, the system generates this error code.
Access Channel
Web
Possible Causes
The identity's charge profile is not an assignable charge profile for product {0}.
{0} indicates product name.
Procedure
Modify parameter settings and retry.
4.310 GV50091
Description
The identity corresponding to {0} has not subscribed to product {1}.
{0} indicates a MSISDN or short code.

{1} indicates a product name.
Scenario
An identity has not subscribed to a product.
Access Channel
Web(Bulk)

Copyright © Huawei
Mobile Money
Possible Causes
An identity has not subscribed to a product.
Procedure
Enable the identity corresponding to {0} to subscribe to product {1}.
4.311 GV50092
Description
The currency {0} of the bank card is the same as an existing one.
{0}: currency code.
Scenario
When modifying organizations' bank card KYC information through the API channel or
modifying the information in bulk through the web channel, an operator must enter bank card
information. If the currency in the entered information is the same as an existing currency of
an identity, this error code is generated.
Access Channel
Web(Bulk), API
Possible Causes
The currency {0} of the bank card is the same as an existing one.
Procedure
Enter a correct currency.
4.312 GV50093
Description
The currency {0} is invalid.
{0}: currency code.
Scenario

Copyright © Huawei
Mobile Money
information. If the currency in the entered information is not supported by the system, this
error code is generated.
Access Channel
Web(Bulk), API
Possible Causes
The system does not support the currency {0}.
Procedure
Enter a correct currency.
4.313 GV50094
Description
The currency {0} is not the default currency.
{0}: currency code.
Scenario
information. If the currency in the entered information is not the default currency, this error
code is generated.
Access Channel
Web(Bulk), API
Possible Causes
The currency {0} is not the default currency.
Procedure
Enter the default currency.
4.314 GV50095
Description
The KYC {0} value cannot be entered for identity registration.

Copyright © Huawei
Mobile Money
{0} indicates KYC name.
Scenario
The value of the INPUT4REGISTRATION field added to the CPS_KYC_FIELD table is
0, indicating that the KYC value cannot be entered during identity registration. An error is
reported when this KYC value is entered for identity registration.
Access Channel
Web, STK, USSD, API
Possible Causes
The KYC {0} value is entered for identity registration.
Procedure
Change the value of the INPUT4REGISTRATION parameter in the CPS_KYC_FIELD
table to 1 or leave it empty.
4.315 GV50096
Description
The answer to the security question is shorter than the minimum length.
Scenario
An error is reported when an operator enters an answer shorter than the minimum length of
the security question. An operator can configure the security question and answer during first
time login, after successful login (under the My Preference menu), or upon request.
Access Channel
Web
Possible Causes
The answer to the security question is shorter than the minimum length.
Procedure
Enter an answer that is longer than the minimum length.

Copyright © Huawei
Mobile Money
4.316 GV50097
Description
The answers to different questions must be different.
Scenario
An error is reported when an operator enters the same answer to different security questions.
An operator can configure the security question and answer during first time login, after
successful login (under the My Preference menu), or upon request.
Access Channel
Web
Possible Causes
An operator enters the same answer to different security questions.
Procedure
Enter different answers to different questions.
4.317 GV50098
Description
Failed to modify the bank card information.
Scenario
When the bank card information of an organization is modified, the bank card information
cannot be modified if the bank card has been used for transaction.
Access Channel
Web
Possible Causes
The bank card has been used for transaction and cannot be modified.
Procedure
Process transactions related to the bank card promptly.

Copyright © Huawei
Mobile Money
4.318 GV50099
Description
Set either of the two optional fields.
Scenario
This error occurs when an operator initiates a request through the API channel and two
optional AG template fields in the request are both set or not set.
Access Channel
API
Possible Causes
Both of the two optional fields are set or not set.
Procedure
Set the field correctly.
4.319 GV50100
Description
The queried data is not generated or query condition is incorrect.
Scenario
This error is reported when an operator queries messages but the queried data is not generated
or the query condition is incorrect.
Access Channel
API
Possible Causes
The queried data is not generated or query condition is incorrect.
Procedure
Verify that the query condition is correct and queried data exists.

Copyright © Huawei
Mobile Money
4.320 GV50101
Description
Operation failed. The Till has no default organization operator.
Scenario
All services processed by the BCS.
Access Channel
USSD, STK
Possible Causes
The Till has no default organization operator.
Procedure
Modify the Till information.
4.321 GV50102
Description
Failed to query the pseudocode. The pseudocode dictionary is not configured or configured
incorrectly.
Scenario
When a subscriber or an SP operator queries the pseudocode of a subscriber, the system
generates a pseudocode according to the preset pseudocode dictionary. This error is reported if
the pseudocode dictionary is not configured or configured incorrectly.
Access Channel
Web, USSD, STK, SMS
Possible Causes
The pseudocode dictionary is not configured or configured incorrectly.
Procedure
Run the $HOME/tools/pseudocode.sh script on the BCS NE.

Copyright © Huawei
Mobile Money
4.322 GV50103
Description
Account {0} is already a hot account.
{0} indicates an account number.
Scenario
This error is reported when the account to be set as a hot account is already a hot account.
Access Channel
Web
Possible Causes
Account {0} is already a hot account.
Procedure
Do not set the account as a hot account again.
4.323 GV50104
Description
The message content cannot be queried.
Scenario
This error is reported when the system does not support the MSG message query.
Access Channel
API
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
4.324 GV50105
Description
The KYC field is invalid and in an incorrect format.
Scenario
An Identity is created or the KYC of the Identity is modified.
Access Channel
Web, USSD, STK
Possible Causes
The value of the {0} KYC field is in an incorrect format.
{0}: indicates KYC field name.
Procedure
Field.
2. Verify the format requirement for the KYC field.
3. Return to the previous page and set the KYC field to a value in the correct format.
4. 4. If the fault persists, check whether the corresponding KYC field is of the date or
datetime type. If yes, choose My Functions > Operational Configuration >
Localization > Date and Time and check time configuration in Date and Time Format
for Bulk Task.
4.325 GV50106
Description
The ID expiration date cannot be earlier than the effective date.
Scenario
This error is reported when ID details of the KYC are modified but the effective date is later
than the expiration date.
Access Channel
API
Possible Causes
The ID expiration date cannot be earlier than the effective date.

Copyright © Huawei
Mobile Money
Procedure
Ensure that the ID expiration date is not earlier than the effective date.
4.326 GV50107
Description
The ID expiration date cannot be earlier than the current date.
Scenario
This error is reported when ID details of the KYC are modified but the expiration date is
earlier than the current date.
Access Channel
API
Possible Causes
The ID expiration date cannot be earlier than the current date.
Procedure
Ensure that the ID expiration date is not earlier than the current date.
4.327 GV50108
Description
The certificate expiration date cannot be earlier than the effective date.
Scenario
This error is reported when certificate details of the KYC are modified but the effective date
is later than the expiration date.
Access Channel
API
Possible Causes
The certificate expiration date cannot be earlier than the effective date.
Procedure
Ensure that the certificate expiration date is not earlier than the effective date.

Copyright © Huawei
Mobile Money
4.328 GV50109
Description
The certificate expiration date cannot be earlier than the current date.
Scenario
This error is reported when certificate details of the KYC are modified but the expiration date
is earlier than the current date.
Access Channel
API
Possible Causes
The certificate expiration date cannot be earlier than the current date.
Procedure
Ensure that the certificate expiration date is not earlier than the current date.
4.329 GV50110
Description
The request fails to be processed. The initiator and receiver are not the same customer.
Scenario
This error is reported when the BO operation request initiator is a customer but the initiator
and receiver are not the same customer.
Access Channel
API
Possible Causes
The initiator and receiver are not the same customer.
Procedure
Ensure that the MSISDNs of the initiator and receiver are the same.

Copyright © Huawei
Mobile Money
4.330 GV50111
Description
The {0} account of the debit party is in the {1} state and cannot be used to perform
transactions.
{0}: indicates the name of an account.

{1}: indicates the status of an account.
Scenario
This error is reported when the account of the debit party of the transaction is in the invalid
state and fails to be authenticated.
Access Channel
Web
Possible Causes
The account status of the debit party is invalid.
Procedure
 Solution 1: Change the account state of the debit party to a valid state and perform the
transaction again.
 Solution 2: Select a debit party whose account is in a valid state and perform the
transaction again.
4.331 GV50112
Description
The value of parameter {0} is incorrect. The initiator organization queried by the organization
entity ID or short code does not exist.
{0} indicates an organization ID or short code.
Scenario
This error is reported in operations involving all organizations if the initiator organization
queried by the organization entity ID or short code does not exist.
Access Channel
API

Copyright © Huawei
Mobile Money
Possible Causes
The value of parameter {0} is incorrect.
Procedure
Enter a correct parameter value to query the organization.
4.332 GV50113
Description
The value of parameter {0} is incorrect. The receiver organization queried by the organization
entity ID or short code does not exist.
{0} indicates an organization ID or short code.
Scenario
This error is reported in operations involving all organizations if the receiver organization
queried by the organization entity ID or short code does not exist.
Access Channel
API
Possible Causes
Procedure
Enter a correct parameter value to query the organization.
4.333 GV50114
Description
The {0} account of the credit party is in the {1} state and cannot be used to perform
transactions.


Copyright © Huawei
Mobile Money
Scenario
This error is reported when the account of the credit party of the transaction is in the invalid
state and fails to be authenticated.
Access Channel
Web
Possible Causes
The account status of the credit party is invalid.
Procedure
 Solution 1: Change the account state of the credit party to a valid state and perform the
transaction again.
 Solution 2: Select a debit party whose account is in a valid state and perform the
transaction again.
4.334 GV50115
Description
The value of parameter {0} is incorrect. The group queried by the group identity ID or group
code does not exist.
{0} indicates a group identity ID or group code.
Scenario
This error is reported in operations involving all group members if the group queried by the
group identity ID or group code does not exist.
Access Channel
API
Possible Causes
Procedure
Enter a correct parameter value to query the group.

Copyright © Huawei
Mobile Money
4.335 GV50116
Description
The parameter is incorrect. The group member queried by the group identity ID or group
member ID does not exist or is in an incorrect state.
Scenario
This error is reported in operations involving all group members if the group member queried
by the group identity ID or group member ID does not exist or is in an incorrect state.
Access Channel
API
Possible Causes
The parameter is incorrect.
Procedure
Enter a correct parameter value to query the group information.
4.336 GV50117
Description
The parameter is incorrect. The group member role queried by the group identity ID or group
member ID does not exist.
Scenario
This error is reported in operations involving all group members if the group member role
queried by the group identity ID or group member ID does not exist.
Access Channel
API
Possible Causes
Procedure
Enter a correct parameter value to query the group information.

Copyright © Huawei
Mobile Money
4.337 GV50118
Description
The status of requester identity {0} is {1}. The status fails the authentication and the current
service cannot be processed.
{0} indicates a name of the requester.

{1} indicates the status of the requester.
Scenario
This error is reported for all operations requiring permission control if the transaction party
status is incorrect.
Access Channel
Web, USSD, API, STK
Possible Causes
Procedure
4.338 GV50119
Description
Operation failed. The following KYC field already exists in the system: {0}.
{0}: list of KYC fields requiring uniqueness verification.
Scenario
This error is reported during identity creation or KYC modification if some configured KYC
fields requiring uniqueness verification already exist in the system.
Access Channel
Web, API, STK
Possible Causes
The following KYC field must be unique in the system: {0}.

Copyright © Huawei
Mobile Money
Procedure
Ensure that the KYC information is correct.
4.339 GV50120
Description
Operation failed. The combined length of values of the following KYC fields cannot exceed
2000: {0}.
{0}: list of KYC fields requiring uniqueness verification.
Scenario
This error is reported during identity creation or KYC modification if the length of some
configured KYC fields requiring uniqueness verification exceeds the maximum.
Access Channel
Web, API, STK
Possible Causes
The combined length of values of KYC fields for uniqueness verification exceeds 2000.
Procedure
Ensure that the KYC information is correct.
4.340 GV50121
Description
The certificate number {0} is in the blacklist and the operation cannot be performed.
{0} indicates the certificate number, for example, ID number and passport number.
Scenario
This error is reported when an identity is created, an identity is modified, or an identity
initiates an operation but the certificate number is in the blacklist.
Access Channel
POS

Copyright © Huawei
Mobile Money
Possible Causes
The certificate number {0} is in the blacklist.
Procedure
Contact customer service personnel.
4.341 GV50122
Description
Product {0} is incorrect and the identity fails to be created.
{0} indicates a product name.
Scenario
This error is reported when the identity bulk creation task is executed but the entered product
is incorrect.
Access Channel
Web, API
Possible Causes
Product {0} is not of the integer type.
Procedure
Enter a correct product and initiate the bulk task again.
4.342 GV50123
Description
The parameter value {0} is incorrect. No person is found based on the person ID or ID
number.
{0} indicates the person ID or ID number.
Scenario
This error is reported when no person is found based on the person ID or ID number.

Copyright © Huawei
Mobile Money
Access Channel
POS
Possible Causes
The parameter value {0} is incorrect.
Procedure
Enter a correct value for the parameter to query for the person.
4.343 GV50124
Description
The KYC field {0} is mandatory for the current trust level and cannot be left empty.
Scenario
This error is reported when the trust level of an identity is modified but the KYC field is
empty.
Access Channel
Web, API
Possible Causes
The KYC field {0} is left empty.
Procedure
Set the KYC field to a correct value.
4.344 GV50500
Description
The direct debit mandate corresponding to the payer is not found based on the direct debit
unique reference number.
Scenario
This error is reported if the direct debit mandate corresponding to the identity of the payer is
not found based on the direct debit unique reference number.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API, Web(Bulk)
Possible Causes
The corresponding direct debit mandate is not found.
Procedure
Check input parameters and ensure that the direct debit unique reference number is correct.
4.345 GV50501
Description
No identity is found based on card type {0} and card number {1}.
{0} indicates card type.

{1} indicates card number.
Scenario
This error is reported during swipe-card transaction if no identity is found based on card type
and card number.
Access Channel
Web, STK, USSD, API
Possible Causes
No identity is found based on card type {0} and card number {1}.
Procedure
Select an activated card for swipe-card transactions.
4.346 IC11221
Description
Failed to create account {0}.
{0}: indicates shared account name.

Copyright © Huawei
Mobile Money
Scenario
When a child organization is created or when a product is subscribed to for a child
organization, the generated shared account does not exist in the parent organization.
Access Channel
Web, USSD
Possible Causes
The parent organization does not have the specified shared account {0} ({1}).
{0}: indicates shared account name.

{1}: indicates currency name.
Procedure
Verify whether the shared account exists in the parent organization.
4.347 IC12001
Description
Failed to query the customer.
Scenario
Any transaction or action that involves customers whose information cannot be found based
on the primary key ID.
Access Channel
Web, STK, USSD, API
Possible Causes
Information about this customer does not exist in the database.
Procedure
Data exception. Contact Huawei engineers.
4.348 IC13200
Description
The device number already exists, failed to add the device.

Copyright © Huawei
Mobile Money
Scenario
When a device is added for an organizations or customer, the device number already exists.
Access Channel
Web
Possible Causes
The device number exists.
Procedure
Use another device number, or contact customer service representatives to delete the existing
number if the original is not used anymore and add it again.
4.349 IC13307
Description
The length of the MSISDN is {0}, and has exceeded the valid range from {1} to {2}.
{0}: indicates the length of the specified MSISDN.

{1}: indicates the minimum MSISDN length.
{2}: indicates the maximum MSISDN length.
Scenario
The length of the specified MSISDN exceeds the valid range.
Access Channel
Web
Possible Causes
The MSISDN length is not in the valid range.
Procedure
Set the MSISDN to a value with a length in the range from {1} to {2}.
4.350 IC14004
Description
The operator does not exist.

Copyright © Huawei
Mobile Money
Scenario
All actions that involve operators
Access Channel
Web, STK, USSD, API
Possible Causes
 The operator is not registered.
Procedure
1. Verify that the operator is registered.
4.351 IC19300
Description
The MSISDN is ported out.
Scenario
Create a customer or till.
Access Channel
Web, USSD
Possible Causes
 The MSISDN specified for the customer to be created has been ported out.
 The MSISDN specified for the till to be created has been ported out.
Procedure
Enter another MSISDN.
4.352 IC19301
Description
The input MSISDN is blank or does not exist.

Copyright © Huawei
Mobile Money
Scenario
Create a customer or till.
Access Channel
Web, USSD
Possible Causes
Procedure
Check whether the MSISDN is correct.
4.353 IC19303
Description
The MSISDN is not in the customer or till number segment range.
Scenario
When a customer or till is created, the MSISDN is not within a specified range.
Access Channel
Web, USSD, STK, API
Possible Causes
Procedure
Verify that the MSISDN is in the customer or till number segment range. If the MSISDN is
not in the range, select the MSISDN in the range.
4.354 IC19306
Description
The device whose MSISDN is {0} does not exist.
Scenario
All operations that involve customer MSISDNs

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
The related MSISDN device is not found.
Procedure
Check whether the input MSISDN is correct.
4.355 IC19503
Description
The account whose account No. is {1} in identity {0} is not found.
{0}: indicates the public name of the identity.

{1}: indicates the account type to be queried.
Scenario
No account is found for the identity based on the account type. That is, the identity has no
account of this type.
Access Channel
Web, STK, USSD, API
Possible Causes
The account whose account No. is {1} in identity {0} does not exist.
Procedure
System error. Send transaction center logs in the /log/debug/tc_debug.log to a Huawei
engineer for fault diagnosis.
4.356 IC19506
Description
The bank ID {0} is not found.
Scenario
All actions or transactions that involve banks

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
The bank ID {0} does not exist.
Procedure
System error. Contact Huawei engineers.
4.357 IC40000
Description
Failed to configure the charge distribution model.
Scenario
A profit sharing mode cannot be configured for an organization that is not an aggregator child
organization.
Access Channel
Web
Possible Causes
The current organization is not a child organization of the Aggregator type.
Procedure
A charge distribution model cannot be configured for the current organization. Select a correct
organization type.
4.358 IC40004
Description
Failed to change the identity Account Rule Profile.
Scenario
When you query Account Rule Profile by Trust Level, Identity Type, and Account Type, the
result is blank.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
When you query Account Rule Profile by Trust Level, Identity Type, and Account Type, the
result is blank.
Procedure
1. Access the portal.
2. Choose My Functions > Operational Configuration > Assignment Management >
Account Rule Profile.
3. Configure the Rule Profile for the identity trust level.
4.359 IC40005
Description
Failed to add a data extractor.
Scenario
The data extractor to be added exists in the database table.
Access Channel
Web
Possible Causes
The data extractor exists in the database.
Procedure
Select another available organization.
4.360 IC40006
Description
Failed to add a data extractor scheduled task.
Scenario
The number of scheduled tasks exceeds the quantity specified by the system parameter when
you add data extractor scheduled tasks.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The number of scheduled tasks exceeds the number specified by system parameters. The
adding failed.
Procedure
2. Choose My Functions > Operational Configuration > System Parameter > Data
Extractor.
3. Change the value of Maximum Schedules to a larger value.
4.361 IC40007
Description
Failed to add a data client.
Scenario
The data client to be added exists in the database table when you add a data client.
Access Channel
Web
Possible Causes
The data client exists in the database table.
Procedure
Select another available O2B organization.
4.362 IC40009
Description
Failed to change data client status.
Scenario
When you change data client status, the original status is the same as the target status. (Data
clients have only two types of status: active and close.)

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The target status is the same as the original status and cannot be changed.
Procedure
Select another status.
4.363 IC40010
Description
Failed to change or delete a data extractor.
Scenario
The data extractor to be changed or deleted does not exist.
Access Channel
Web
Possible Causes
The data extractor does not exist.
Procedure
2. Choose Search > Pay Bill Data Extractorand check whether the data extractor exists.
3. If the data extractor exists, contact Huawei engineers. If the data extractor does not exist,
cancel the operation.
4.364 IC40011
Description
Failed to change or delete the data client.
Scenario
The data client to be changed or deleted does not exist.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The data client does not exist.
Procedure
2. Choose Search > Pay Bill Data Extractor and check whether the data extractor
contains the data client.
4.365 IC40012
Description
Failed to add or modify a data extractor scheduled task.
Scenario
The receiver of the message indicating the failure to execute a scheduled task is not an service
provider (SP) operator or data extractor organization operator when you add or modify a data
extractor scheduled task.
Access Channel
Web
Possible Causes
The message receiver is not an SP operator or data extractor organization operator.
Procedure
Select an SP operator or data extractor organization operator as the message receiver.
4.366 IC40013
Description

Copyright © Huawei
Mobile Money
Scenario
The input interval is invalid when you add or modify a data extractor scheduled task.
Access Channel
Web
Possible Causes
The interval for executing a scheduled task is invalid.
Procedure
Enter the valid interval. For example:
 Interval Time is 1 to 12 if Interval Type is set to MONTH.
 Interval Time is 1 to 28 if Interval Type is set to Day.
 Interval Time is 1 to 23 if Interval Type is set to Hour.
 Interval Time is 5 to 59 if Interval Type is set to Minute.
 Interval Time is 1 to 52 if Interval Type is set to Week.
4.367 IC40014
Description
Scenario
The input effective time or expiry time is invalid when you add or modify a data extractor
scheduled task.
Access Channel
Web
Possible Causes
The effective time or expiry time of a scheduled task is invalid.
Procedure
Enter the valid effective time or expiry time. The effective time is earlier than the expiry time,
and the expiry time is later than the current time.

Copyright © Huawei
Mobile Money
4.368 IC40015
Description
Scenario
The receiver of the message indicating the failure to execute a scheduled task is duplicate
when you add or modify a data extractor scheduled task.
Access Channel
Web
Possible Causes
Duplicate operators are defined as the message receiver.
Procedure
Check whether duplicate message receivers exist.
4.369 IC40017
Description
Failed to change data client status.
Scenario
The changed data client status is incorrect and cannot be parsed as the data client status.
Access Channel
Web
Possible Causes
The input status cannot be parsed as the data client status.
Procedure
Enter the valid data client status. For example, 0 indicates close, and 1 indicates active.

Copyright © Huawei
Mobile Money
4.370 IC40018
Description
Failed to change or delete the data client.
Scenario
The data client to be changed or deleted does not belong to the data extractor.
Access Channel
Web
Possible Causes
The {0} data client does not belong to the current data extractor.
{0}: indicates a data client.
Procedure
Enter a valid data extractor and data client.
4.371 IC40019
Description
Failed to modify or delete a scheduled task.
Scenario
The scheduled task to be modified or deleted does not exist.
Access Channel
Web
Possible Causes
The scheduled task does not exist.
Procedure
2. Choose Search > Pay Bill Data Extractor and check whether the data extractor details
contain the scheduled task.

Copyright © Huawei
Mobile Money
4.372 IC40020
Description
Failed to modify or delete a scheduled task.
Scenario
The data extractor does not contain the scheduled task to be modified or deleted.
Access Channel
Web
Possible Causes
The data extractor does not contain the scheduled task.
Procedure
2. Choose Search > Pay Bill Data Extractorand check whether the data extractor details
contain the scheduled task.
4.373 IC40021
Description
The operator certificate is reclaimed.
Scenario
The digital certificate is reclaimed when an operator logs in.
Access Channel
Web
Possible Causes
The operator certificate is reclaimed.
Procedure
Obtain a new certificate.

Copyright © Huawei
Mobile Money
4.374 IC40022
Description
The digital certificate does not exist.
Scenario
The digital certificate does not exist when an operator logs in.
Access Channel
Web
Possible Causes
The digital certificate cannot be found.
Procedure
Check the digital certificate.
4.375 IC40023
Description
The digital certificate is incorrect.
Scenario
The digital certificate is incorrect when an operator logs in.
Access Channel
Web
Possible Causes
Procedure
Check the digital certificate.

Copyright © Huawei
Mobile Money
4.376 IC40024
Description
The digital certificate is in the suspended state.
Scenario
The digital certificate is in the suspend state when an operator logs in.
Access Channel
Web
Possible Causes
The digital certificate is in the suspended state.
Procedure
Check the status of the digital certificate.
4.377 IC40025
Description
The {0} operator cannot perform this operation.
{0} indicates the operator status.
Scenario
When an operator attempts to log in, the operator status is incorrect, and the operator cannot
log in.
Access Channel
Web
Possible Causes
The {0} operator cannot perform this operation.
Procedure
Check the operator status.

Copyright © Huawei
Mobile Money
4.378 IC40026
Description
The status of the organization where the operator is located is inactive.
Scenario
Access Channel
Web
Possible Causes
Procedure
Check the organization status.
4.379 IC40028
Description
Failed to add the O2O Link.
Scenario
The O2O Link exists when you add the O2O Link.
Access Channel
Web
Possible Causes
The O2O Link exists.
Procedure
System error. Contact a Huawei engineer for help.

Copyright © Huawei
Mobile Money
4.380 IC40029
Description
Failed to add the O2O Link.
Scenario
The O2O Link to be changed does not exist.
Access Channel
Web
Possible Causes
The O2O Link does not exist.
Procedure
4.381 IC40036
Description
The operation failed. The identity status is not Active.
Scenario
The current operation is not supported when the identity status is not Active.
Access Channel
Web, USSD,STK, API
Possible Causes
The identity status is not Active.
Procedure
Check the identity status.

Copyright © Huawei
Mobile Money
4.382 IC40037
Description
Failed to redo the mobile number portability (MNP) task.
Scenario
Failed to redo the MNP task if the corresponding MNP task is not found.
Access Channel
Web
Possible Causes
The MNP task to be redone does not exist.
Procedure
Select a correct MNP task.
4.383 IC40038
Description
Failed to redo the MNP task.
Scenario
The MNP task is complete and does not need to be redone.
Access Channel
Web
Possible Causes
The MNP task does not need to be redone.
Procedure
Select a correct MNP task.

Copyright © Huawei
Mobile Money
4.384 IC40039
Description
Failed to import the MNP task.
Scenario
The path of the MNP file cannot be found during MNP file reading in MNP task execution.
Access Channel
System
Possible Causes
The path of the MNP file to be imported cannot be found.
Procedure
Set the system parameter MNP File Path correctly.
4.385 IC40040
Description
Failed to import the MNP file.
Scenario
Importing an MNP file failed if the file is being processed by another task.
Access Channel
System
Possible Causes
The MNP file is locked by another task.
Procedure
Wait until the processing another task is complete.

Copyright © Huawei
Mobile Money
4.386 IC40041
Description
Scenario
Importing an MNP file failed if the MNP file cannot be found.
Access Channel
System
Possible Causes
Unprocessed MNP file cannot be found.
Procedure
Put the MNP file to the to-be-processed directory.
4.387 IC40042
Description
Scenario
Importing an MNP file failed if an error occurs when reading the MNP file failed.
Access Channel
System
Possible Causes
Failed to read the MNP file.
Procedure
Check whether MNP file content is correct.

Copyright © Huawei
Mobile Money
4.388 IC40043
Description
Failed to change the organization relationship.
Scenario
The organization cannot have sub-organizations or all the sub-organizations must be closed.
Otherwise, changing the organization relationship failed.
Access Channel
Web
Possible Causes
The current organization has sub-organizations that are not closed.
Procedure
Close all the sub-organizations in the current organization.
4.389 IC40044
Description
Scenario
During an organization relationship change, the organization has incomplete transactions.
Access Channel
Web
Possible Causes
The current organization has unfinished transactions.
Procedure
Ensure that all the transactions of the current organization are closed before changing the
organization relationship.

Copyright © Huawei
Mobile Money
4.390 IC40045
Description
Scenario
The organization cannot have vouchers that are not extracted. Otherwise, changing the
organization relationship failed.
Access Channel
Web
Possible Causes
The current organization has vouchers that are not extracted.
Procedure
Ensure that processing of all vouchers is complete before changing the organization
relationship.
4.391 IC40046
Description
Scenario
Some accounts may need to be closed for the organization relationship change. These
accounts cannot have any balance. If the accounts have balance, the change failed.
Access Channel
Web
Possible Causes
The organization account balance is not 0.
Procedure
Clear the organization account balance and change the organization relationship.

Copyright © Huawei
Mobile Money
4.392 IC40047
Description
The user name and operator ID are blank.
Scenario
This error message is reported if both the user name and operator ID in the imported file are
blank when you change organization operator roles in batches.
Access Channel
Web(Bulk)
Possible Causes
The user name and operator ID are blank.
Procedure
Enter a user name and operator ID.
4.393 IC40048
Description
The entered role is not the existing role of the operator.
Scenario
This error message is reported if the role entered for the import file is not the existing role of
the operator when you delete operator roles in batches.
Access Channel
Web(Bulk)
Possible Causes
The entered role is not the existing role of the operator.
Procedure
Delete this role from the import file.

Copyright © Huawei
Mobile Money
4.394 IC40049
Description
The security credential of the user is incorrect.
Scenario
During security credential verification, the security credentials are found incorrect.
Access Channel
Web, API, STK, USSD
Possible Causes
The value of {0} is incorrect.
The variable {0} indicates a security credential name, such as Password.
Procedure
4.395 IC40050
Description
Failed to authenticate {0}.
The variable {0} indicates a security credential name. A security credential can be a password, PIN, or
secret word.
Scenario
The security credential is locked.
Access Channel
Web, API, STK, USSD
Possible Causes
The {0} security credential is locked.
Procedure
Unlock the security credential and try again.

Copyright © Huawei
Mobile Money
4.396 IC40051
Description
The current security credential has expired.
Scenario
The security credential has expired.
Access Channel
Web, API, STK, USSD
Possible Causes
The {0} security credential has expired.
secret word.
Procedure
1. Click My Preference on the upper right of the page.
2. Choose Basic Info > Change Password and change the password.
3. In the navigation tree, click Change PIN.
4. In the navigation tree, click Change Secret Word to change the secret word.
4.397 IC40052
Description
The security credential is too short.
Scenario
When a user creates or modifies a security credential, the length of the created or modified
credential is less than the minimum length specified in the security credential policy.
Access Channel
Web, API, STK, USSD
Possible Causes
The length of {0} is shorter than the minimum length {1}.

Copyright © Huawei
Mobile Money
The variable {0} indicates a security credential name, and {1} indicates the minimum length of a
security credential value. A security credential can be a password, PIN, or secret word.
Procedure
Enter a security credential with a length equal to or greater than the minimum length.
4.398 IC40053
Description
The security credential is too long.
Scenario
When a user creates or modifies a security credential, the length of the created or modified
credential is greater than the maximum length specified in the security credential policy.
Access Channel
Web, API, STK, USSD
Possible Causes
The length of {0} is greater than the maximum length {1}.
The variable {0} indicates a security credential name, and {1} indicates the maximum length of a
Procedure
Enter a security credential with a length equal to or less than the maximum length.
4.399 IC40054
Description
The number of digits in the security credential does not meet the credential policy
requirement.
Scenario
When a user creates or modifies a security credential, the number of digits in the created or
modified credential does not meet the requirements specified in the security credential policy.

Copyright © Huawei
Mobile Money
Access Channel
Web, API, STK, USSD
Possible Causes
The {0} security credential must contain at least {1} digits.
The variable {0} indicates a security credential name, and {1} indicates the number of digits in a
Procedure
Enter the valid security credential.
4.400 IC40055
Description
The number of letters in the security credential does not meet the credential policy
requirement.
Scenario
When a user creates or modifies a security credential, the number of letters in the created or
modified credential does not meet the requirements specified in the security credential policy.
Access Channel
Web, API, STK, USSD
Possible Causes
The {0} security credential must contain at least {1} letters.
The variable {0} indicates a security credential name, and {1} indicates the number of letters in a
Procedure
4.401 IC40056
Description
The number of special characters in the security credential does not meet the credential policy
requirement.

Copyright © Huawei
Mobile Money
Scenario
When a user modifies a security credential, the number of special characters in the modified
credential does not meet the requirements specified in the security credential policy.
Access Channel
Web, API, STK, USSD
Possible Causes
The {0} security credential must contain at least {1} special characters.
The variable {0} indicates a security credential name, and {1} indicates the number of special characters
in a security credential value. A security credential can be a password, PIN, or secret word.
Procedure
4.402 IC40057
Description
The number of uppercase letters in the security credential does not meet the credential policy
requirement.
Scenario
When a user modifies a security credential, the number of upper-case letters in the modified
credential does not meet the requirements specified in the security credential policy.
Access Channel
Web, API, STK, USSD
Possible Causes
The {0} security credential must contain at least {1} uppercase letters.
The variable {0} indicates a security credential name, and {1} indicates the number of upper-case letters
in a security credential value. A security credential can be a password, PIN, or secret word.
Procedure

Copyright © Huawei
Mobile Money
4.403 IC40058
Description
The credential format does not meet credential policies.
Scenario
When a user modifies a security credential, the format of the credential does not meet the
requirements specified in the security credential policy.
Access Channel
Web, API, STK, USSD
Possible Causes
The format of {0} is incorrect.
secret word.
Procedure
1. Choose My Functions > Core Configuration > Security Credential.
2. Check security credential policies.
4.404 IC40059
Description
The new security credential is blacklisted.
Scenario
The new security credential is blacklisted when a subscriber changes the security credential.
Access Channel
Web, API, STK, USSD
Possible Causes
The new security credential is blacklisted.
Procedure

Copyright © Huawei
Mobile Money
4.405 IC40060
Description
The operator is not allowed to perform the operation because the security credential is in the
Pending status.
Scenario
During certain operations, a security credential is in the Pending status.
Access Channel
Web, API, STK, USSD
Possible Causes
Security credential {0} is in the Pending status.
secret word.
Procedure
Activate the credential.
4.406 IC40061
Description
A security credential must not contain two consecutive identical letters.
Scenario
When a user modifies a security credential, two consecutive same characters are contained in
the credential.
Access Channel
Web, API, STK, USSD
Possible Causes
The security credential contains two consecutive identical letters.
Procedure

Copyright © Huawei
Mobile Money
4.407 IC40062
Description
The credential must be different from historical ones.
Scenario
When a user modifies a security credential, a used credential is contained.
Access Channel
Web, API, STK, USSD
Possible Causes
A security credential must be different from historical ones.
Procedure
Enter a valid security credential.
4.408 IC40063
Description
The {0} security credential is changed too frequently. Try again later.
The variable {0} indicates a security credential name. For example, Password, PIN.
Scenario
The interval at which the security credential is changed is shorter than the minimum interval
specified in the credential policy.
Access Channel
Web, API, STK, USSD
Possible Causes
The {0} security credential is changed too frequently.
Procedure
Try again later.

Copyright © Huawei
Mobile Money
4.409 IC40064
Description
The security credential is the same as the user name or the inverted user name.
Scenario
When a user modifies a security credential, the modified credential is the same as the login
account or the account in reverse order.
Access Channel
Web, API, STK, USSD
Possible Causes
The value of {0} must be different from the user name and the inverted user name.
secret word.
Procedure
Enter a valid security credential.
4.410 IC40065
Description
The identity's security credential is about to expire.
Scenario
When a security credential is about to expire, a user receives this message asking a user to
modify the credential upon a login.
Access Channel
Web, API, STK, USSD
Possible Causes
The {0} security credential is about to expired.
secret word.

Copyright © Huawei
Mobile Money
Procedure
4.411 IC40066
Description
Operation failed. The {0} security credential is already unlocked.
secret word.
Scenario
The security credential is in the Unlocked status and does not need to be unlocked again.
Access Channel
Web, API, STK, USSD
Possible Causes
The security credential is already unlocked and does not need to be unlocked again.
Procedure
Verify whether the security credential is in the unlocked status.
4.412 IC40067
Description
Operation failed. The {0} security credential is already locked.
secret word.
Scenario
The security credential is already locked and cannot be locked again.

Copyright © Huawei
Mobile Money
Access Channel
Web, API, STK, USSD
Possible Causes
The credential is already locked and cannot be locked again.
Procedure
Verify whether the security credential is in the locked status.
4.413 IC40068
Description
Failed to generate {0}.
secret word.
Scenario
A random security credential fails to be generated after 1000 attempts.
Access Channel
Web, API, STK, USSD
Possible Causes
The number of times for generating security credentials exceeds 1000, but no valid {0}
security credential is generated.
Procedure
2. Choose My Functions > Core Configuration > Security Credential > PIN Blacklist.
3. Check whether the blacklist contains all digits ranging from 0 to 9, and delete
unnecessary digits. Regenerate security credentials.
If the problem persists, contact a Huawei engineer for help.
4.414 IC40069
Description
Operation failed.

Copyright © Huawei
Mobile Money
Scenario
All actions that need verify security credential.
Access Channel
Web, API, STK, USSD
Possible Causes
No security credential is found.
Procedure
Contact a Huawei engineer for help.
4.415 IC40070
Description
A secret word is not a security credential.
Scenario
During security credential verification, a secret word is entered, which cannot be used as a
security credential.
Access Channel
Web, API, STK, USSD
Possible Causes
Procedure
4.416 IC40071
Description
Account Type {0} does not apply to Identity {1}.
The variable {0} indicates the account type.

The variable {1} indicates the identity type.

Copyright © Huawei
Mobile Money
Scenario
The account type selected for the identity to be created does not apply to the identity.
Access Channel
Web, USSD
Possible Causes
Account Type {0} does not apply to Identity {1}.
Procedure
Select an applicable account type.
4.417 IC40072
Description
Failed to add the C2O link.
Scenario
The C2O link to be added already exists.
Access Channel
Web
Possible Causes
The C2O link already exists.
Procedure
The C2O link already exists and cannot be created again.
4.418 IC40073
Description
Failed to find the identity.
Scenario
The identity to be queried does not exist.

Copyright © Huawei
Mobile Money
Access Channel
Web, API, STK, USSD
Possible Causes
Information about {0} does not exist.
The variable {0} indicates identity name.
Procedure
Verify the packet and query conditions.
4.419 IC40074
Description
Failed to find the device.
Scenario
The device of the identity cannot be found.
Access Channel
Web, API, STK, USSD
Possible Causes
The device does not exist.
Procedure
Verify the packet and query conditions.
4.420 IC40075
Description
Failed to add the till device.
Scenario
The till for which a device is to be added already has a device.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
One till can have only one device.
Procedure
Verify whether a device has already been configured for the till.
4.421 IC40076
Description
The Registered By field is set to an organization not in the Active status.
Scenario
The organization by which a customer is registered must be in the Active status.
Access Channel
Web, USSD, API
Possible Causes
The Registered By field is set to an organization not in the Active status.
Procedure
Activate the organization first.
4.422 IC40077
Description
Failed to change the O2C link.
Scenario
The O2C link number is set to an invalid value. Failed to change the O2C link.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The O2C link number is set to an invalid value.
Procedure
Set O2C Link Number to a correct value.
4.423 IC40078
Description
The current call has been closed and cannot be closed again.
Scenario
Access Channel
Web
Possible Causes
The current call has been closed.
Procedure
4.424 IC40079
Description
Failed to delete the bank account.
Scenario
The bank card of the bank account to be deleted does not exist.
Access Channel
Web
Possible Causes
Failed to delete the bank account because the bank card does not exist.

Copyright © Huawei
Mobile Money
Procedure
4.425 IC40080
Description
Failed to query the default SP operator.
Scenario
The default SP operator to be queried does not exist.
Access Channel
Web, System, API, USSD
Possible Causes
The default SP operator does not exist.
Procedure
1. Choose My Functions > Operational Configuration > System Parameter >
Transaction.
2. Change the SP Operator Initiating Transaction field to an operator that exists in the
system.
4.426 IC40081
Description
Status authentication failed because the CommandID is empty.
Scenario
All the BO operations.
Access Channel
Web
Possible Causes
Status authentication failed because the CommandID is empty.

Copyright © Huawei
Mobile Money
Procedure
4.427 IC40082
Description
Failed to query the identity type status.
Scenario
The current status of the identity type is empty when the identity type is manually changed.
Access Channel
Web
Possible Causes
The identity type status is empty.
Procedure
4.428 IC40083
Description
Scenario
The current status of the identity type is not supported when the identity type status is
manually changed.
Access Channel
Web
Possible Causes
The identity type does not support the current status.
Procedure

Copyright © Huawei
Mobile Money
4.429 IC40084
Description
Scenario
The current status of the identity type cannot be parsed when the identity type status is
manually changed.
Access Channel
Web
Possible Causes
The specified identity status cannot be parsed into a valid identity type status.
Procedure
Enter a valid identity status, such as 00 which indicates New and 02 which indicates Pending
Active.
4.430 IC40085
Description
The operator's password has been locked.
Scenario
Access Channel
Web, STK, USSD, STK
Possible Causes
Procedure
The operator's password has been locked. Unlock the password first.

Copyright © Huawei
Mobile Money
4.431 IC40086
Description
An initiator cannot perform an operator on the self.
Scenario
An initiator cannot change the information of the self.
Access Channel
Web, STK, USSD
Possible Causes
An initiator cannot perform an operator on the self.
Procedure
Ask another operator to log in to the system and perform this operation.
4.432 IC40087
Description
Operation failed.
Scenario
All the BO operations.
Access Channel
Web, STK, USSD
Possible Causes
You must enter either the {0} or the {1} identity flag type.
Variables {0} and {1} indicate entity flag types.
Procedure
Verify that the settings of the identity flags.

Copyright © Huawei
Mobile Money
4.433 IC40088
Description
Operation failed.
Scenario
The operator and till does not belong to the same organization.
Access Channel
API, USSD, STK
Possible Causes
The operator and till does not belong to the same organization.
Procedure
Verify that the operator and the till belong to the same organization.
4.434 IC40089
Description
Failed to change the Pay Bill Validator.
Scenario
Change operation failed because the Pay Bill Validator is invalid.
Access Channel
Web
Possible Causes
The specified Pay Bill Validator is invalid.
Procedure
Enter a valid Pay Bill Validator.

Copyright © Huawei
Mobile Money
4.435 IC40091
Description
The customer to be activated must be in the Pending active status.
Scenario
During customer activation, the customer is not in the Pending Active status.
Access Channel
API, USSD, STK
Possible Causes
The customer to be activated is not in the Pending active status.
Procedure
Select a customer in the Pending Active status.
4.436 IC40092
Description
The user name does not exist or the password is incorrect.
Scenario
All actions that need verify the user name or password.
Access Channel
Web, STK, USSD, STK
Possible Causes
Procedure
Enter a correct user name and password.

Copyright © Huawei
Mobile Money
4.437 IC40093
Description
Query operation failed because of invalid security credential status.
Scenario
The security credential status does not support identity service query.
Access Channel
USSD, STK
Possible Causes
The security credential status does not support identity service query.
Procedure
Select an identity with a valid security credential.
4.438 IC40097
Description
The product {0} is not matched with the till.
The variable {0} indicates the product to be changed.
Scenario
The product is not matched with the till when assign the product of the organization till.
Access Channel
Web
Possible Causes
The product {0} is not matched with the till.
Procedure
Please check the organization product.

Copyright © Huawei
Mobile Money
4.439 IC40098
Description
Failed to create the O2C link because the customer is in the Closed status.
Scenario
The customer for whom an O2C link is to be created is in the Closed status.
Access Channel
Web
Possible Causes
The customer is in the Closed status.
Procedure
Modify the customer status before creating an O2C link.
4.440 IC40109
Description
Operation failed. The receiver is an unregistered customer.
Scenario
The receiver involved in the business operation (BO) operations is an unregistered customer.
Access Channel
Web, USSD, STK, API
Possible Causes
The receiver is an unregistered customer.
Procedure
Verify that the receiver is a registered customer and try again.

Copyright © Huawei
Mobile Money
4.441 IC40110
Description
Failed to add a data extractor or data client because the organization is in the New or Close
status.
Scenario
When a data extractor or data client is added for an organization, the organization is in the
New or Close status.
Access Channel
Web
Possible Causes
Failed to add a data extractor or data client because the organization is in the New or Close
status.
Procedure
Select an organization that is not in the New or Close status.
4.442 IC40111
Description
Failed to modify the operator's role.
Scenario
The operator whose role is to be modified must serve as more than one role.
Access Channel
Web
Possible Causes
The operator must have at least one role.
Procedure
Verify that the operator has at least one role.

Copyright © Huawei
Mobile Money
4.443 IC40112
Description
Failed to calculate the business operation fee. Error cause: {0}
The variable {0} indicates an error reason.
Scenario
Calculating a business operation fee fails.
Access Channel
Web, API, STK, USSD
Possible Causes
Failed to calculate the business operation fee. Error cause: {0}
Procedure
Verify that charging configurations for business operation fees are correct.
4.444 IC40113
Description
Failed to assign the operator to the {0} task.
The variable {0} indicates a task to be executed.
Scenario
The operator to which permission is assigned does not exist, and therefore, distributing the
operator to the {0} task fails.
Access Channel
Web
Possible Causes
The operator to which the task is to be assigned does not exist.
Procedure
Select an existing operator.

Copyright © Huawei
Mobile Money
4.445 IC40114
Description
The {0} role and the {1} role are mutually exclusive and cannot be assigned to the same
operator.
The variable {0} indicates a newly-added role, and {1} indicates a conflicted role.
Scenario
During operator role creation or modification, the roles conflict with each other.
Access Channel
Web
Possible Causes
The {0} role and the {1} role are mutually exclusive.
Procedure
Verify that the roles are not mutually exclusive.
4.446 IC40115
Description
The {0} role is not in the available role range and cannot assigned to the operator.
Scenario
During operator role creation or modification, the operator role is not in the assignment range.
Access Channel
Web
Possible Causes
The {0} role is not in the available role range.
Procedure
Verify that the role is in the available role range.

Copyright © Huawei
Mobile Money
4.447 IC40116
Description
When an organization operator creates a customer, the Registered by field must be set to the
home organization of the operator.
Scenario
When an organization operator creates a customer, the Registered by field is not set to the
home organization of the operator.
Access Channel
Web(Bulk)
Possible Causes
The Registered by field is not set to the home organization of the operator.
Procedure
Set the Registered by field to the home organization of the operator.
4.448 IC40121
Description
Bank {0} already has the non-control account instance {1}, and no more non-control account
instance can be created for the same account type.
The variable {0} indicates a bank ID, and {1} indicates an account type ID.
Scenario
A non-control account is added for a bank on the Bank Client page on the portal. The bank
{0} already has a non-control account instance {1}. No account of the same type can be
created for the bank.
Access Channel
Web
Possible Causes
Bank {0} already has the non-control account instance {1}, and no more non-control account
instance can be created for the same account type.

Copyright © Huawei
Mobile Money
Procedure
Select another bank or account type, or cancel the operation.
4.449 IC40123
Description
The new Identity Sub Type {0} must be different from the old one.
The {0} variable indicates the value of Identity Sub Type.
Scenario
When a customer is upgraded or when a customer upgrade task is created, operation fails
because the new Identity Sub Type is the same as the old one. The {0} variable indicates the
value of Identity Sub Type.
Access Channel
Web, API
Possible Causes
The new Identity Sub Type {0} is the same as the old one.
Procedure
Set Identity Sub Type to a valid value.
4.450 IC40124
Description
Failed to authenticate the customer.
Scenario
Failed to authenticate a customer in the Take a Call menu.
Access Channel
Web
Possible Causes
The score of correct authentication information does not meet the minimum requirement.

Copyright © Huawei
Mobile Money
Procedure
Enter correct authentication information and verify that the score of correct authentication
information meets the minimum requirement.
4.451 IC40125
Description
Failed to authenticate the organization operator.
Scenario
Failed to authenticate an organization operator in the Take a Call menu.
Access Channel
Web
Possible Causes
The score of correct authentication information does not meet the minimum requirement.
Procedure
Enter correct authentication information and verify that the score of correct authentication
information meets the minimum requirement.
4.452 IC40127
Description
Failed to authenticate the product.
Scenario
An SP or organization operator updates a product of a child organization on the web portal.
Access Channel
Web, API
Possible Causes
The identity model of the selected product is inconsistent with the identity model of the
organization.

Copyright © Huawei
Mobile Money
Procedure
Select a product whose identity model is consistent with the identity model of the child
organization.
4.453 IC40128
Description
Failed to authenticate the product.
Scenario
An SP or organization operator updates a product of a top organization on the web portal.
Access Channel
Web, API
Possible Causes
The identity model of the selected product does not have a default accounting model.
Procedure
Set a default accounting model for the identity model.
4.454 IC40129
Description
After an identity's trust level is downgraded, products that do not fit the new trust level need
to be deleted. If the account balance of a product to be deleted is not zero, the system displays
this error message.
Scenario
After an identity's trust level is downgraded due to KYC changes performed by an operator on
the portal or using a bulk task, the system checks if there is any product that does not fit the
new trust level and needs to be deleted. If there is a product to be deleted but the balance in
the product account is not zero, the system displays this error message.
Access Channel
Web
Possible Causes
The balance in the {1} account of the {0} product is not zero.

Copyright © Huawei
Mobile Money
The {0} variable indicates the alias of a product.

The {1} variable indicates the alias of an account.
Procedure
Verify that the account balance of the product to be deleted is zero.
4.455 IC40130
Description
The downgrade operation is not allowed by the downgrade matrix.
Scenario
the system checks whether the KYC changes will trigger a trust level downgrade. If yes, the
system checks whether the downgrade operation is allowed by the downgrade matrix. If it is
not allowed, the system displays this error message.
Access Channel
Web, API
Possible Causes
Based on settings in the downgrade matrix, trust level {0} cannot be downgraded to {1}.
The {0} variable indicates the original trust level of an identity. The
{1} variable indicates the new trust level of an identity.
Procedure
Verify whether the downgrade operation is allowed by the downgrade matrix.
4.456 IC40131
Description
No product can be specified during the process of downgrading an identity's trust level by
modifying the KYC information.
Scenario
No product can be specified during the process of downgrading an identity's trust level by

Copyright © Huawei
Mobile Money
Access Channel
Web, API
Possible Causes
A product is specified during the process of downgrading an identity's trust level by
Procedure
Modify the parameter settings and try again.
4.457 IC40132
Description
No product is specified for the identity, and the identity's trust level has no default product.
Scenario
When creating an identity, an operator does not specify a product for the identity, and the trust
level of the identity has no default product.
Access Channel
Web
Possible Causes
No product is specified for the identity, and the identity's trust level has no default product.
Procedure
4.458 IC40133
Description
Failed to create or upgrade the customer.
Scenario
The trust level specified is incorrect when a customer is created or upgraded.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The specified trust level is incorrect.
Procedure
Enter a correct trust level.
4.459 IC40134
Description
When identity identification information is created, the Expiration Time system parameter is
invalid.
Scenario
When the Identify Context identification information is created, the expiration time
configured in the CPS_IDENTIFY_CONTEXT_PERIOD system parameter is invalid.
Access Channel
USSD
Possible Causes
The system parameter does not exist or is set to an invalid value.
Procedure
Choose My Functions > Operational Configuration > CCH Configuration and modify the
Identification Validity Period field.
4.460 IC40135
Description
When customer identification information is created, the customer is not a registered
customer.
Scenario
When Identify Customer identification information is created, the customer is not a registered
customer.
Access Channel
USSD

Copyright © Huawei
Mobile Money
Possible Causes
The customer is not a registered customer.
Procedure
Select a registered customer or register the customer.
4.461 IC40136
Description
The Date of Birth (DOB) format is incorrect during a CCH service.
Scenario
The Date of Birth (DOB) does not meet the calendar format requirement during a CCH
service.
Access Channel
USSD
Possible Causes
The DOB format is incorrect during a CCH service.
Procedure
Enter the DOB in a valid format.
4.462 IC40137
Description
The DOB is inconsistent with the date of birth in the KYC information
Scenario
The DOB is inconsistent with the date of birth in the database during a CCH service.
Access Channel
USSD
Possible Causes
The DOB is inconsistent with the date of birth in the database.

Copyright © Huawei
Mobile Money
Procedure
Enter a correct DOB.
4.463 IC40138
Description
The identification information of the receiver or requester is invalid during a CCH service.
Scenario
The identity is not identified by the current operator or the identification has expired during a
CCH service.
Access Channel
USSD
Possible Causes
The receiver or requester is not identified by the current operator or the identification has
expired.
Procedure
Identify the identity first.
4.464 IC40139
Description
The DOB to be updated does not meet the update criteria.
Scenario
The DOB to be updated does not meet the update criteria.
Access Channel
USSD
Possible Causes
The customer's DOB does not meet the update criteria.

Copyright © Huawei
Mobile Money
Procedure
Choose My Functions > Operational Configuration > CCH Configuration to modify the
DOB update criteria.
4.465 IC40140
Description
Operation failed because the receiver identity's account is not in the Active status.
Scenario
When an organization initiates a CCH service for an identity, a fee needs to be charged from
the identity, but the identity's account is not in the Active status.
Access Channel
USSD
Possible Causes
The receiver identity's account is not in the Active status.
Procedure
Change the receiver identity's account status on the identity info page.
4.466 IC40141
Description
The receiver identity's account balance is insufficient during a CCH service.
Scenario
When an organization initiates a CCH service for an identity, a fee needs to be charged from
the identity, but the identity's account balance is insufficient.
Access Channel
USSD
Possible Causes
The receiver identity's account balance is insufficient during a CCH service.

Copyright © Huawei
Mobile Money
Procedure
Recharge the receiver identity or transfer money to the receiver identity first.
4.467 IC40142
Description
Operation failed because the initiator has no CCH service permission during a CCH service.
Scenario
Organization operators must have the permission before initiating a CCH service.
Access Channel
USSD
Possible Causes
The initiator has no CCH service permission during a CCH service.
Procedure
Assign the CCH service permission to the initiator.
4.468 IC40143
Description
The new trust level has no default charge profile, and the old charge profile is not an
assignable charge profile of the new trust level.
Scenario
the system checks whether the KYC changes will trigger a trust level change. If the trust level
of an identity is upgraded or downgraded when KYC information of the identity is modified,
the system checks whether the new trust level has a default charge profile. If the new trust
level has a default charge profile, the system sets the identity's charge profile to the default
charge profile. If the new trust level has no default charge profile, the system continues to
check whether the old charge profile is an assignable charge profile of the new trust level. If
no, the system reports this error.
Access Channel
Web, API

Copyright © Huawei
Mobile Money
Possible Causes
The charge profile of the identity is not an assignable charge profile of trust level {0}.
The {0} variable indicates the new trust level of an identity after KYC changes.
Procedure
4.469 IC40144
Description
The new trust level has no default rule profile, and the old rule profile is not an assignable rule
profile of the new trust level.
Scenario
the system checks whether the KYC changes will trigger a trust level change. If the trust level
of an identity is upgraded or downgraded when KYC information of the identity is modified,
the system checks whether the new trust level has a default rule profile. If the new trust level
has a default rule profile, the system sets the identity's rule profile to the default rule profile. If
the new trust level has no default rule profile, the system continues to check whether the old
rule profile is an assignable rule profile of the new trust level. If no, the system reports this
error.
Access Channel
Web, API
Possible Causes
The rule profile of the identity is not an assignable rule profile of trust level {0}.
The {0} variable indicates the new trust level of an identity after KYC changes.
Procedure

Copyright © Huawei
Mobile Money
4.470 IC40145
Description
When creating an organization, an operator must manually enter an identity model for the
organization. Meanwhile, the system also calculates an identity model based on products
selected for the organization. The two are not consistent.
Scenario
When creating an organization, an operator must manually enter an identity model for the
organization. Meanwhile, the system also calculates an identity model based on products
selected for the organization. If the two are not consistent, the system displays this error
message.
Access Channel
Web
Possible Causes
The identity model calculated based on the selected product(s) is inconsistent with the
specified identity model.
Procedure
4.471 IC40146
Description
The Identity Model field is left empty when a child organization is created.
Scenario
If the Identity Model field is left empty when a child organization is created, the system
displays this error message.
Access Channel
Web, API
Possible Causes
The Identity Model field is mandatory for a child organization.
Procedure

Copyright © Huawei
Mobile Money
4.472 IC40147
Description
The account model specified for an organization to be created has no identity model.
Scenario
If the account model specified for an organization to be created has no identity model, the
system reports this error.
Access Channel
Web
Possible Causes
Accounting model {0} has no identity model.
The {0} variable indicates the name of an accounting model.
Procedure
4.473 IC40149
Description
The dormant account cannot be reactivated because the customer MSISDN does not exist.
Scenario
Access Channel
Web
Possible Causes
Procedure
Please add a device for the customer.

Copyright © Huawei
Mobile Money
4.474 IC40150
Description
The dormant account cannot be reactivated because the customer has e-money in the SP
holding account.
Scenario
holding account.
Access Channel
Web
Possible Causes
holding account.
Procedure
Please verify the transaction status of the customer's account.
4.475 IC40151
Description
Failed to obtain the file from the uniform resource locator (URL).
Scenario
The system reports an error when a license is revoked.
Access Channel
System
Possible Causes
The URL is incorrect or the network is disconnected.
Procedure
Please verify that the URL is correct and that the network works properly.

Copyright © Huawei
Mobile Money
4.476 IC40152
Description
The specified account rule profile {0} does not exist in the system or has not taken effect.
Failed to authenticate the account rule profile {0}.
{0} indicates account rule profile.
Scenario
An SP or organization operator updates an account rule profile on the web portal.
Access Channel
Web
Possible Causes
The specified account rule profile {0} does not exist in the system or has not taken effect.
Procedure
Choose My Functions > Operational Configuration > Assignment Management >
Account Rule Profile, configure an account rule profile, and enable the account rule profile
to take effect.
4.477 IC40153
Description
Failed to authenticate the charge profile.
Scenario
An SP or organization operator updates a charge profile on the web portal.
Access Channel
Web
Possible Causes
The specified charge profile does not exist, or the effective time of the charge profile to be
subscribed to is later than the current time.
Procedure
Select a valid charge profile.

Copyright © Huawei
Mobile Money
4.478 IC40154
Description
By default, the Mobile Money does not support the function for downgrading the trust level of
an identity by modifying the KYC information. If KYC changes result in trust level
downgrade, the system throws this exception.
Scenario
an identity by modifying the KYC information. This function can be enabled by setting the
bp_ic_identity\IdentityConfigItem\IsSurpportTrustLevelDowngrade configuration item to
True.
Access Channel
Web
Possible Causes
an identity by modifying the KYC information.
Procedure
If your office requires the function for downgrading the trust level of an identity by modifying
the KYC information, contact a Huawei engineer for help.
4.479 IC40155
Description
The Reserved Balance or Unclear Balance of the account to be closed is not 0.
Scenario
The Reserved Balance or Unclear Balance of an account is not 0 in processes such as number
recycle or MNP.
Access Channel
Web
Possible Causes
The Reserved Balance or Unclear Balance of the account to be closed is not 0.

Copyright © Huawei
Mobile Money
Procedure
Please verify the Reserved Balance or Unclear Balance of the account.
4.480 IC40156
Description
Role {0} to be deleted for an operator has not been assigned to the operator.
{0}: indicates the ID of a role.
Scenario
When roles of an SP or organization operator are modified in batches, the bulk file contains a
role that is not assigned to the operator.
Access Channel
Web
Possible Causes
Role {0} to be deleted for an operator has not been assigned to the operator.
Procedure
The bulk file contains a role that is not assigned to the operator.
4.481 IC40157
Description
Role {0} to be assigned to an operator has already been assigned to the operator.
Scenario
When roles of an SP or organization operator are modified in batches, the bulk file contains a
role that is already assigned to the operator.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
Role {0} to be assigned to an operator has already been assigned to the operator.
Procedure
The bulk file contains a role that is already assigned to the operator.
4.482 IC40158
Description
The bulk file contains duplicate records for role {0}.
Scenario
When roles of an SP or organization operator are modified in batches, the bulk file contains
duplicate records for a role.
Access Channel
Web
Possible Causes
The bulk file contains duplicate records for role {0}.
Procedure
Deduplicate role records in the bulk file.
4.483 IC40159
Description
Product {0} to be closed for an identity has not been subscribed to by the identity.
{0}: indicates the ID of a product.
Scenario
When products of a customer or organization are modified in bulk, the bulk file contains a
product that has not been subscribed to by the customer or organization.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
Product {0} to be closed for an identity has not been subscribed to by the identity.
Procedure
Delete the product that has not been subscribed to by the identity from the bulk file.
4.484 IC40160
Description
Product {0} to be added for an identity has already been subscribed to by the identity.
Scenario
When products are subscribed to for a customer or organization in bulk, the bulk file contains
a product that has already been subscribed to by the customer or organization.
Access Channel
Web
Possible Causes
Product {0} to be added for an identity has already been subscribed to by the identity.
Procedure
Delete the product that has been subscribed to by the identity from the bulk file.
4.485 IC40161
Description
The bulk file contains duplicate records for product {0} to be subscribed to.

Copyright © Huawei
Mobile Money
Scenario
When products are subscribed to for a customer or organization in bulk, the bulk file contains
duplicate records for product {0}.
Access Channel
Web
Possible Causes
The bulk file contains duplicate records for product {0} to be subscribed to.
Procedure
Deduplicate product records in the bulk file.
4.486 IC40162
Description
No default rule profile is configured for the current Trust Level. Failed to create or modify the
identity.
Scenario
Create or modify a customer or organization.
Access Channel
Web, API, USSD
Possible Causes
No default rule profile is matched for the trust level.
Procedure
Configure a default rule profile for the trust level.
4.487 IC40163
Description
The identity model of the top organization is not Mixed, and the identity models of the child
organization and top organization are inconsistent.

Copyright © Huawei
Mobile Money
Scenario
When a child organization is created, if the identity model of the top organization is not
Mixed, the identity models of the child organization and top organization must be consistent;
otherwise, the system reports this exception.
Access Channel
Web, API
Possible Causes
The identity model of the child organization is inconsistent with the identity model of the top
organization.
Procedure
Verify that the identity models of the child organization and top organization are consistent.
4.488 IC40164
Description
During a CCH service, the till of the receiver is not in the Active status.
Scenario
When an organization operator initiates a CCH service, the till of the receiver is in the
incorrect status.
Access Channel
USSD
Possible Causes
During a CCH service, the till of the receiver is not in the Active status.
Procedure
Change the status of the initiator till to Active.
4.489 IC40165
Description
Security credential {0} does not exist.

Copyright © Huawei
Mobile Money
{0}: indicates the name of a security credential.
Scenario
When an operator unlocks a PIN or reset the PIN, the system verifies whether the security
credential of the receiver exists.
Access Channel
Web
Possible Causes
Security credential {0} does not exist.
Procedure
Check whether security credential {0} exists. If the problem persists, contact a Huawei
engineer for help.
4.490 IC40166
Description
Operation failed. The account type used by the identity has become invalid.
Scenario
Create or modify an account for an identity.
Access Channel
Web
Possible Causes
Account type {0} has become invalid.
{0}: indicates the ID of an account type.
Procedure
Close or delete the account of the invalid account type.

Copyright © Huawei
Mobile Money
4.491 IC40167
Description
MNP operation failed.
Scenario
MNP operation.
Access Channel
Web
Possible Causes
The time in record {0} is later than the current time.
{0}: indicates the time of a record.
Procedure
Change the MNP record time to a time earlier than the current time.
4.492 IC40168
Description
MNP operation failed.
Scenario
MNP operation.
Access Channel
Web
Possible Causes
The MNP record {0} already exists, and record time is earlier than the time {1} recorded in
the system.
{0}: indicates the MSISDN of a record.
Procedure
Change the time of the MNP record {0} to a time later than {1}.

Copyright © Huawei
Mobile Money
{0}: indicates the MSISDN of a record.

{1}: indicates the MNP time in the system.
4.493 IC40169
Description
Failed to subscribe to product {0}.
Scenario
When an SP or organization operator creates a child organization or subscribes to a non-
hierarchy product for the organization, the system verifies whether the non-hierarchy product
supports a shared account.
Access Channel
Web
Possible Causes
Account {1} required by non-hierarchy product {0} must be owned by the current
organization.
{0}: indicates the name of the non-hierarchy product to be subscribed to.

Procedure
Verify whether the non-hierarchy product can be assigned to the current organization.
4.494 IC40171
Description
The certificate has been revoked.
Scenario
When an operator logs in to the portal, the system verifies whether the certificate of the
operator has been revoked.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The certificate has been revoked.
Procedure
Update the certificate.
4.495 IC40172
Description
Failed to assign the role.
Scenario
Create an operator or assign a role.
Access Channel
Web, USSD
Possible Causes
Role {0} does not exist or is not in the Released status.
Procedure
Verify that the role exists and is in the Released status.
4.496 IC40189
Description
Failed to modify {0}. {0}: {1} cannot be changed to {2}.
{0}: indicates the name of an identity attribute, such as Rule Profile.

{1}: indicates the current value of an identity attribute, such as Rule Profile ID.
{2}: indicates the new value of an identity attribute.
Scenario
When an SP or organization operator modifies identity attributes in batches on a web page, an
attribute value cannot be changed from the current value to the new value.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
{0}: {1} cannot be changed to {2}.
Procedure
Verify whether {0}: {1} can be changed to {2}. If yes, a system error has occurred, and you
need to contact a Huawei engineer for help. If no, change {0}: {1} to another value.
4.497 IC40190
Description
Failed to delete the {2} attribute.
Scenario
When an SP or organization operator deletes identity attributes in batches on a web page, an
attribute to be deleted does not exist.
Access Channel
Web
Possible Causes
Deletion failed because {0}: {1} does not have {2}: {3}.
{0}: indicates the name of an identity type attribute, such as Customer.

{1}: indicates the identifier of an identity, such as customer MSISDN 86812530001.
{2}: indicates the name of the attribute to be deleted, such as Product.
{3}: indicates the identifier of the attribute to be deleted, such as Product ID 10000007.
Procedure
Verify whether {0}: {1} has {2}: {3}. If yes, a system error has occurred, and you need to
contact a Huawei engineer for help. If no, delete another {2} attribute.
4.498 IC40191
Description
Failed to add {0}.

Copyright © Huawei
Mobile Money
Scenario
When an SP or organization operator adds identity attributes in batches on a web page, an
attribute to be added already exists.
Access Channel
Web
Possible Causes
{0}: {1} already has {2}: {3}. The attribute value cannot be added again.
{0}: indicates the name of an identity type attribute, such as Customer.

{1}: indicates the identifier of an identity, such as customer MSISDN 86812530001.
{2}: indicates the name of an attribute to be added, such as Product.
{3}: indicates the identifier of the attribute to be added, such as Product ID 10000007.
Procedure
Verify whether {0}: {1} has {2}: {3}. If yes, a system error has occurred, and you need to
contact a Huawei engineer for help. If no, add another {2} attribute.
4.499 IC40192
Description
No record is found based on the record identifier {0}.
{0}: detail information of a record identifier, such as ID Type:01, ID Number:1234, ID Effective

Date:20150114.
Scenario
When an SP or organization operator creates a bulk task for modifying multi-value identity
KYC fields, the system parses the record identifiers.
Access Channel
Web, API
Possible Causes
No record is found based on a record identifier.
Procedure
Check whether the record identifier has a corresponding record.

Copyright © Huawei
Mobile Money
4.500 IC40193
Description
Multiple records are found based on the record identifier {0}.
{0}: detail information of a record identifier, such as ID Type:01, ID Number:1234.
Scenario
Access Channel
Web, API
Possible Causes
Multiple records are found based on a record identifier.
Procedure
Provide more record identifiers to increase the precision.
4.501 IC40194
Description
The {0} value of the record identifier is mandatory.
{0}: KYC type of a record identifier, such as ID type.
Scenario
Access Channel
Web, API
Possible Causes
A mandatory value of a record identifier is missing.

Copyright © Huawei
Mobile Money
Procedure
Verify that mandatory values are configured.
4.502 IC40195
Description
Task failed.
Scenario
Process a workflow task.
Access Channel
Web
Possible Causes
The {0} operator who is assigned a workflow task does not exist or is not in the Active status.
{0}: ID of an operator.
Procedure
Check whether the operator exists and verify the operator status.
4.503 IC40196
Description
Task failed.
Scenario
Process a workflow task.
Access Channel
Web
Possible Causes
The organization to which the {0} operator who processes the workflow task belongs does not
meet the Organization Mapping requirement.

Copyright © Huawei
Mobile Money
{0}: ID of an operator.
Procedure
Abandon this task.
4.504 IC40197
Description
Scenario
Investigate a workflow task.
Access Channel
Web
Possible Causes
The investigated operator or role does not meet the Organization Mapping requirement.
Procedure
Investigate another operator or role.
4.505 IC40198
Description
Revenue settlement failed.
Scenario
During revenue settlement, an operator of a top organization can initiate revenue settlement
for owned stores within the organization hierarchy. Operators of other types of organizations
can initiate revenue settlement only for the home organization.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
An operator of a top organization can initiate revenue settlement for owned stores within the
organization hierarchy. Operators of other types of organizations can initiate revenue
settlement only for the home organization.
Procedure
Verify the relationship between the operator and the organization.
4.506 IC40199
Description
Default product {1} of segment {0} is invalid.
{0}: Name of a segment.

{1}: Name of a product.
Scenario
When a KYC field is modified, the status of the default product of a segment is not Released,
or the product does not in the validity period.
Access Channel
Web, STK, API
Possible Causes
Default product {1} of segment {0} is invalid.
Procedure
Check the status or validity period of the {1} default product of segment {0}.
4.507 IC40200
Description
Default product {1} of trust level {0} is invalid.
{0}: Name of a trust level.


Copyright © Huawei
Mobile Money
Scenario
When a KYC field is modified, the status of the default product of a trust level is not
Released, or the product does not in the validity period.
Access Channel
Web, STK, API
Possible Causes
Default product {1} of trust level {0} is invalid.
Procedure
Check the status or validity period of the {1} default product of trust level {0}.
4.508 IC40201
Description
The {0} product is invalid.
Scenario
When KYC fields are modified in bulk, the status of a specified product is not Released, or
the product does not in the validity period.
Access Channel
Web, STK, API
Possible Causes
The {0} product is invalid.
Procedure
Check the status or validity period of the {0} product.
4.509 IC40202
Description
The default account rule profile of segment {0} is in an invalid status or not in the validity
period.

Copyright © Huawei
Mobile Money
Scenario
When a customer or organization is created or when a KYC field of a customer or
organization is modified, the system assigns a value to each account based on the default
account rule profile of a segment. If the account rule profile of the segment is in an invalid
status or not in the validity period, the system throws this exception.
Access Channel
Web, STK, API
Possible Causes
The default account rule profile of segment {0} is invalid.
Procedure
Check the status or validity period of the default account rule profile of segment {0}.
4.510 IC40203
Description
The default charge profile of segment {0} is in an invalid status or not in the validity period.
Scenario
charge profile of a segment. If the charge profile of the segment is in an invalid status or not
in the validity period, the system throws this exception.
Access Channel
Web, STK, API
Possible Causes
The default charge profile of segment {0} is invalid.
Procedure
Check the status or validity period of the default charge profile of segment {0}.

Copyright © Huawei
Mobile Money
4.511 IC40204
Description
The default identity rule profile of segment {0} is in an invalid status or not in the validity
period.
Scenario
identity rule profile of a segment. If the identity rule profile of the segment is in an invalid
status or not in the validity period, the system throws this exception.
Access Channel
Web, STK, API
Possible Causes
The default identity rule profile of segment {0} is invalid.
Procedure
Check the status or validity period of the default identity rule profile of segment {0}.
4.512 IC40205
Description
Failed to create the organization.
Scenario
When an organization is created, the configured settlement profile is incorrect.
Access Channel
Web
Possible Causes
Settlement profile {0} cannot be found or is not in the Released status.
{0}: ID of a settlement profile.

Copyright © Huawei
Mobile Money
Procedure
Select a settlement profile in the Released status.
4.513 IC40206
Description
Failed to create the organization.
Scenario
When an organization is created, the configured settlement period cycle is incorrect.
Access Channel
Web
Possible Causes
The period cycle is empty or incorrect. The period cycle can only be set to Day, Week, or
Month.
Procedure
Select a correct period cycle.
4.514 IC40207
Description
The task processing operation fails.
Scenario
An error occurs during the task status check in the workflow task processing.
Access Channel
Web
Possible Causes
The task {0} is not in the to-be-processed status, and the operation fails.
{0}: task ID.

Copyright © Huawei
Mobile Money
Procedure
Check whether the selected task status is correct. The task must be in the to-be-processed
status.
4.515 IC40208
Description
Failed to create a manual task.
Scenario
The specified operator or role does not have corresponding permission when a manual task is
created.
Access Channel
Web
Possible Causes
The operator or role specified in the manual task does not have corresponding permission.
Procedure
Select an operator or role who has the processing permission.
4.516 IC40209
Description
MSISDN {0} is not bound to a SIM card.
{0} indicates the mobile number of a receiver.
Scenario
An MSISDN is not bound to a SIM card when operations such as Remove SIM, Update
Menu, and Push Activate Menu are performed.
Access Channel
Web, STK, BULK
Possible Causes
MSISDN {0} is not bound to a SIM card.

Copyright © Huawei
Mobile Money
Procedure
1. Log in to the SP Portal. Choose Search > Customer or Search > Till.
2. Choose SIM Manager and Reuse SIM to bind MSISDN {0} to a SIM card.
4.517 IC40210
Description
MSISDN {0} has been bound to SIM card {1}.
{0} indicates the mobile number of a receiver.

{1} indicates the ID of a SIM card.
Scenario
An MSISDN has been bound to a SIM card when operations such as Reuse SIM are
performed.
Access Channel
Web
Possible Causes
MSISDN {0} has been bound to SIM card {1}.
Procedure
1. Log in to the SP Portal. Choose Search > Customer or Search > Till.
2. Choose SIM Manager and Remove SIM to unbind MSISDN {0} from SIM card {1}.
4.518 IC40211
Description
SIM card {0} is not in the idle pool.
{0} indicates the ID of a SIM card.
Scenario
The SIM card whose integrated circuit card identifier (ICCID) is selected during the Reuse
SIM operation is not in the idle pool.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
SIM card {0} is not in the idle pool.
Procedure
Select an ICCID in the idle pool, that is, an ICCID in the CPS_IDLE_SIM_POOL table.
4.519 IC40212
Description
The entered customer birthday {0} is in an incorrect format.
{0} indicates an entered birthday.
Scenario
The customer birthday entered during SIM card activation is in an incorrect format.
Access Channel
STK
Possible Causes
The entered customer birthday {0} is in an incorrect format.
Procedure
Enter a customer birthday in the format of MMDDYYYY.
4.520 IC40213
Description
The entered customer birthday ({0}) is inconsistent with the customer birthday stored in the
database.
{0} indicates an entered birthday.

Copyright © Huawei
Mobile Money
Scenario
The customer birthday entered during SIM card activation is inconsistent with that stored in
the database.
Access Channel
STK
Possible Causes
The entered customer birthday ({0}) is inconsistent with the customer birthday stored in the
database.
Procedure
Log in to the SP Portal. Choose Search > Customer > Info. Query the customer birthday.
Enter the found customer birthday.
4.521 IC40214
Description
The initiator is in the Pending Change status and the values of New PIN and Old PIN are the
same.
Scenario
This message is displayed during SIM card activation when the initiator is in the Pending
Change status and the values of New PIN and Old PIN are the same.
Access Channel
STK
Possible Causes
The initiator is in the Pending Change status and the values of New PIN and Old PIN are the
same.
Procedure
Ensure that the values of New PIN and Old PIN are different.
4.522 IC40215
Description
The STK menu size is greater than the SIM size.

Copyright © Huawei
Mobile Money
Scenario
During STK menu sending, the STK menu size is greater than the SIM size.
Access Channel
Web, STK, BULK
Possible Causes
The STK menu size is greater than the SIM size.
Procedure
diagnosis.
4.523 IC40216
Description
No specific key exists.
Scenario
No specific key exists during STK menu sending.
Access Channel
Web, STK, BULK
Possible Causes
No specific key exists.
Procedure
diagnosis.
4.524 IC40217
Description
Target environment short number {0} does not exist.
{0} indicates a target environment short number.

Copyright © Huawei
Mobile Money
Scenario
The data dictionary information about an irrelevant target environment short number is found.
Access Channel
Web, BULK
Possible Causes
Target environment short number {0} does not exist.
Procedure
Enter a valid target environment short number.
4.525 IC40218
Description
Customer or organization account is not in the active status.
Scenario
Customer or organization account is not in the active status during SIM card activation.
Access Channel
STK
Possible Causes
Customer or organization account is not in the active status.
Procedure
Change the status of customer or organization account to active.
4.526 IC40219
Description
The device of customer or till is not in the active status.
Scenario
The customer or till device is not in the active status.

Copyright © Huawei
Mobile Money
Access Channel
STK
Possible Causes
The device of customer or till is not in the active status.
Procedure
Change the status of the customer or till device to active.
4.527 IC40238
Description
Failed to modify a multiple KYC field because the expiration date is earlier than the current
date.
Scenario
An SP or organization operator creates a bulk task for modifying identity KYC information on
the portal.
Access Channel
Web
Possible Causes
The expiration date is earlier than the current date.
Procedure
Verify that the expiration date is later than the current date.
4.528 IC40239
Description
Failed to modify the identity KYC information because the date of birth is later than the
current date.
Scenario
the portal.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The date of birth is later than the current date.
Procedure
Verify that the date of birth is earlier than the current date.
4.529 IC40240
Description
Failed to modify a multiple KYC field because the effective date is later than the expiration
date.
Scenario
the portal.
Access Channel
Web
Possible Causes
The effective date is later than the expiration date.
Procedure
Verify that the effective date is earlier than the expiration date.
4.530 IC40241
Description
Failed to obtain the UMC menu.
Scenario
The service list query result is empty when operations such as Update Menu and Push
Activate Menu are executed.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, Web(Bulk)
Possible Causes
The service list of the STK channel of the identity is empty.
Procedure
Add services whose channels are set to STK.
4.531 IC40243
Description
Failed to create the task.
Scenario
Create a workflow task.
Access Channel
USSD, Web
Possible Causes
No definition or configuration is found for task {0}.
{0}: indicates the task type name.
Procedure
Contact a Huawei engineer to add predefined data for the task.
4.532 IC40247
Description
The Password field is mandatory during security credential change through the web channel.
Scenario
When the security credential of an identity is changed through the web channel, the Password
field is mandatory.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The password is empty.
Procedure
4.533 IC40248
Description
BO operation failed.
Scenario
Initiate a BO operation on the AG.
Access Channel
USSD, API, STK
Possible Causes
Service code {0} is invalid, and no service is found.
{0}: indicates a service code.
Procedure
Verify whether the service code is correct. The service code set to the action type must
correspond to a valid service in the system.
4.534 IC40249
Description
The security credential has been locked because the number of input errors has reached the
upper limit.
Scenario
All operations that need to verify security credential.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, Bulk, USSD, API
Possible Causes
The security credential has been locked because the number of input errors has reached the
upper limit.
Procedure
Contact the system administrator for help.
4.535 IC40250
Description
Failed to create the investigation task.
Scenario
Create a workflow task.
Access Channel
Web
Possible Causes
The {0} operator or role does not meet the organization mapping requirement.
{0}: indicates the name of an operator or role.
Procedure
Select an operator or role that meet the organization mapping requirement.
4.536 IC40251
Description
Operation failed. The task expiration time cannot be 0.
Scenario
When a task is investigated, the portal and BCS do not allow values of Day, Hour, and Minute
to be 0 at the same time.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The task expiration time is 0.
Procedure
Set the expiration time correctly.
4.537 IC40252
Description
The rule profile does not apply to identity.
Scenario
The Trust Level selected when an identity is created is not associated with any rule profile.
Access Channel
Web, API
Possible Causes
The Trust Level of the identity is not associated with the rule profile.
Procedure
Account Rule Profile.
2. Edit the identity's rule profile.
3. Assign a rule profile for the trust level.
4.538 IC40258
Description
The Subscriber Recycling scheduled task fails.
[File failed to be processed: {0}]
[File failed to be downloaded: {1}]
{0}: file failed to be processed.

Copyright © Huawei
Mobile Money
{1}: file failed to be downloaded.
Scenario
The Subscriber Recycling scheduled task is executed.
Access Channel
Web
Possible Causes
Failed to obtain Subscriber Recycling files.
Procedure
Check the file permission and format and ensure that the format is correct.
4.539 IC40254
Description
[File processed successfully: {0}]
{0}: file processed successfully.

{2}: file failed to be downloaded
Scenario
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
4.540 IC40255
Description
Failed to download the file {0}.
{0}: .flg file name.
Scenario
Access Channel
Web
Possible Causes
Failed to download the file.
Procedure
4.541 IC40256
Description
[File failed to be moved: {1}]

{1}: file failed to be moved.
Scenario
Access Channel
Web
Possible Causes
Failed to move Subscriber Recycling files to the backup directory.

Copyright © Huawei
Mobile Money
Procedure
Check the file permission and format and ensure that the backup path is correct.
4.542 IC40257
Description
[File failed to be moved: {3}]

{2}: file failed to be downloaded.
{3}: file failed to be moved.
Scenario
Access Channel
Web
Possible Causes
Procedure
Check the file permission and format and ensure that the format and backup path are correct.
4.543 IC40253
Description
Failed to query the service list because the customer is not registered.
Scenario
During USSD menu generation, the customer is detected as an unregistered customer when
the service list is queried.

Copyright © Huawei
Mobile Money
Access Channel
USSD
Possible Causes
Failed to query the service list because the customer is not registered.
Procedure
Register the customer.
4.544 IC40259
Description
ICCID {0} exists in the idle pools.
{0}: indicates ICCID.
Scenario
This error occurs when the idle pools contain the SIM card with the same ICCID during SIM
card removal.
Access Channel
Web
Possible Causes
ICCID {0} exists in the idle pools.
Procedure
Send identity center logs in the /log/debug/bcs_debug.log to a Huawei engineer for fault
diagnosis.
4.545 IC40260
Description
Failed to return for modification. The task creator must have the web access channel.
Scenario
This error occurs when you return an approval task for modification.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The task initiating channel of a task creator does not have the web access channel.
Procedure
The task cannot be returned for modification. This operation is not allowed.
4.546 IC40261
Description
The authentication is completed for the order whose transaction sequence number {0}. The
approval transaction fails.
{0}: transaction sequence number.
Scenario
The transaction workflow is to be approved.
Access Channel
Web
Possible Causes
The authentication is completed for the order whose transaction sequence number {0}.
Procedure
Check the transaction status based on the transaction sequence number {0}.
4.547 IC40264
Description
Query operation failed because the number of records in the query result is too large.
Scenario
The number of records in the query result to be displayed in different pages is too large.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The number of records in the query result is {0}, which exceeds the upper limit {1}
configured at the system level.
{0}: indicates the number of customers found based on the query conditions.
{1}: indicates the value configured in System Parameter > Portal Parameters > Maximum Number of
search result set.
Procedure
Enter more specific query conditions to narrow down the query scope.
4.548 IC40265
Description
The operator's role is not in the validity period.
Scenario
The role of an operator who attempts to log in to the system is not in the validity period.
Access Channel
Web
Possible Causes
The effective date of the operator's role is later than the current date, or the expiration date of
the operator's role is earlier than the current date.
Procedure
Modify the effective or expiration date of the operator's role.
4.549 IC40266
Description
The original status {0} does not match with the current status {1}.
{0}: indicates the original status of an identity.

Copyright © Huawei
Mobile Money
Scenario
When the status of an identity is modified, the original status does not match with the current
status.
Access Channel
Web
Possible Causes
The original status {0} does not match with the current status {1}.
Procedure
Change the identity status to status that matches with the original status.
4.550 IC40267
Description
The {0} reason for changing the status of an identity is invalid.
{0}: indicates the reason for changing the status of an identity.
Scenario
When the status of an identity is changed on the portal, the specified reason is invalid.
Access Channel
Web
Possible Causes
The reason for changing the status of an identity does not exist in the data dictionary.
Procedure
Choose My Functions > Operational Configuration > Data Dictionary to query for the
reason value range for changing the status of an identity, and enter a valid value.

Copyright © Huawei
Mobile Money
4.551 IC40268
Description
Failed to add the link type relationship.
Scenario
The link type relationship to be added for the organization already exists.
Access Channel
Web
Possible Causes
The link type relationship already exists in the organization.
Procedure
Select another link type.
4.552 IC40269
Description
Failed to modify or delete the link type relationship.
Scenario
When a link type relationship is modified or deleted for an organization, the link type
relationship does not exist.
Access Channel
Web
Possible Causes
The link type relationship does not exist in the organization.
Procedure
Select another link type relationship.

Copyright © Huawei
Mobile Money
4.553 IC40270
Description
Failed to add or modify the link type relationship.
Scenario
When a link type relationship is added or modified for an organization, the new master link
type is included in the slave link type.
Access Channel
Web
Possible Causes
The master link type is included in the slave link type.
Procedure
Remove the master link type from the slave link type.
4.554 IC40271
Description
Failed to associate the financial service integration (FSI) provisioning product with the core
product.
Scenario
When an FSI provisioning product is associated with a core product for an organization, the
FSI provisioning product has already been associated with another organization.
Access Channel
Web
Possible Causes
The FSI provisioning product has been associated with another organization.
Procedure
Select a correct FSI product.

Copyright © Huawei
Mobile Money
4.555 IC40272
Description
Failed to associate the FSI provisioning product with the core product.
Scenario
When an FSI provisioning product is associated with a core product for an organization, the
FSI provisioning product has already been associated with the core product.
Access Channel
Web
Possible Causes
The FSI provisioning product of the organization has already been associated with the core
product.
Procedure
Select a correct FSI product relationship.
4.556 IC40273
Description
Failed to activate the FSI product.
Scenario
When a customer activates an FSI product, the selected organization is not an FSI
organization.
Access Channel
Web, STK, API
Possible Causes
The selected organization is not an FSI organization.
Procedure
Select a correct organization.

Copyright © Huawei
Mobile Money
4.557 IC40274
Description
Scenario
When a customer activates an FSI product, the selected organization does not have a
provisioning product relationship.
Access Channel
Web, STK, API
Possible Causes
The selected organization does not have a provisioning product relationship.
Procedure
Create a provisioning product relationship for the organization.
4.558 IC40275
Description
Scenario
When a customer activates an FSI product, the customer has not subscribed to the
provisioning product, or the provisioning product that has been subscribed to has not taken
effect.
Access Channel
Web, STK, API
Possible Causes
The customer has not subscribed to the provisioning product, or the provisioning product that
has been subscribed to has not taken effect.
Procedure
Subscribe to the provisioning product first, or activate the provisioning product that has taken
effect.

Copyright © Huawei
Mobile Money
4.559 IC40276
Description
Failed to activate the FSI product. The Core Product has been activated or the customer, group
or organization already has a link between the Core Product and the organization.
Scenario
The FSI product of the customer, group or organization has already been activated.
Access Channel
Web, STK, API
Possible Causes
The Core Product has been activated or the customer, group or organization already has a link
between the Core Product and the organization.
Procedure
Activate another provisioning product.
4.560 IC40286
Description
This operation is not allowed.
Scenario
An FSI core product cannot be assigned to a customer to be created or upgraded.
Access Channel
Web, API
Possible Causes
You are not allowed to add an FSI core product.
Procedure
Delete the FSI core product.

Copyright © Huawei
Mobile Money
4.561 IC40287
Description
Failed to modify the customer's product. The expiration date of an FSI core product is
changed.
Scenario
The expiration date of an FSI core product is changed for a customer.
Access Channel
Web, API
Possible Causes
The expiration date of FSI core product {0} cannot be changed.
{0}: indicates the name of a product.
Procedure
Do not change the expiration date of FSI core product {0}.
4.562 IC40288
Description
Access Channel
Failed to modify the customer's product. The effective date of an FSI core product is changed.
Web, API
Possible Causes
The effective date of FSI core product {0} cannot be changed.
Procedure
Do not change the effective date of FSI core product {0}.

Copyright © Huawei
Mobile Money
4.563 IC40289
Description
Failed to modify the customer's product. The status of an FSI core product is changed.
Scenario
The status of an FSI core product is changed for a customer.
Access Channel
Web, API
Possible Causes
The status of FSI core product {0} cannot be changed.
Procedure
Do not change the status of FSI core product {0}.
4.564 IC40290
Description
Failed to modify the customer's product. Another FSI core product is added.
Scenario
Another FSI core product is added for a customer.
Access Channel
Web, API
Possible Causes
You are not allowed to add an FSI core product {0}.
Procedure
Do not add an FSI core product.

Copyright © Huawei
Mobile Money
4.565 IC40291
Description
Scenario
A customer who has no MSISDN attempts to activate an FSI product.
Access Channel
Web, API, STK
Possible Causes
The customer has no MSISDN and therefore cannot activate the FSI product.
Procedure
Add an MSISDN before activating the FSI product.
4.566 IC40292
Description
Operation failed because the FSI link is already in the Closed state.
Scenario
An SP operator attempts to unlink a closed FSI link.
Access Channel
Web
Possible Causes
The FSI link is already in the Closed state.
Procedure
Verify that the FSI link is not in the Closed state.

Copyright © Huawei
Mobile Money
4.567 IC40293
Description
Failed to query the transaction status. The initiator does not exist or the user name or
password is incorrect.
Scenario
The initiator fails to be verified when transaction status is queried.
Access Channel
API
Possible Causes
The initiator does not exist or the user name or password is incorrect.
Procedure
Verify that the user name and password of the initiator is correct.
4.568 IC40295
Description
No transaction result is found based on the specified parameter values.
Scenario
The result of a transaction status query operation is empty.
Access Channel
API
Possible Causes
No transaction result is found based on the specified parameter values.
Procedure
Check whether the transaction query parameters are correct.

Copyright © Huawei
Mobile Money
4.569 IC40296
Description
More than one transaction record is found based on OriginatorConversationID.
Scenario
When transaction status is queried, more than one transaction record is found based on
OriginatorConversationID.
Access Channel
API
Possible Causes
More than one transaction record is found based on OriginatorConversationID.
Procedure
Check whether the transaction query parameters are correct.
4.570 IC40297
Description
The operator has no permission to query transaction status.
Scenario
When transaction status is queried, the operator has no permission to query transaction status.
Access Channel
API
Possible Causes
The operator has no permission to query transaction status.
Procedure
Perform the query operation as an operator who has the permission to query transaction status.

Copyright © Huawei
Mobile Money
4.571 IC40298
Description
Failed to query the transaction status. The receiver is not a valid organization.
Scenario
When transaction status is queried, the receiver fails to be verified.
Access Channel
API
Possible Causes
The receiver is not a valid organization.
Procedure
Verify that the receiver is valid.
4.572 IC40299
Description
No record is found based on Receipt Number.
Scenario
When transaction status is queried, no transaction record is found based on Receipt Number.
Access Channel
API
Possible Causes
No record is found based on Receipt Number.
Procedure
Verify that the Receipt Number parameter is valid.

Copyright © Huawei
Mobile Money
4.573 IC40300
Description
No record is found based on OriginatorConversationID or ConversationID.
Scenario
When transaction status is queried, no record is found based on OriginatorConversationID or
ConversationID.
Access Channel
API
Possible Causes
No record is found based on OriginatorConversationID or ConversationID.
Procedure
Verify that value of OriginatorConversationID or ConversationID is valid.
4.574 IC40301
Description
Failed to query the transaction status. The receiver fails to be matched with the debit or credit
party.
Scenario
When transaction status is queried, the receiver fails to be matched with the debit or credit
party.
Access Channel
API
Possible Causes
The receiver fails to be matched with the debit or credit party.
Procedure
Verify that the Receiver parameter is valid.

Copyright © Huawei
Mobile Money
4.575 IC40302
Description
Failed to query the transaction status. The format of Receipt Number is incorrect.
Scenario
When transaction status is queried, the format of Receipt Number is incorrect.
Access Channel
API
Possible Causes
The format of Receipt Number is incorrect.
Procedure
Verify that the Receipt Number parameter is in a correct format.
4.576 IC40303
Description
Only one of the ReceiptNumber, OriginatorConversationID, and ConversationID query
conditions can be specified.
Scenario
When transaction status is queried, more than one of the ReceiptNumber,
OriginatorConversationID, and ConversationID query conditions are specified.
Access Channel
API
Possible Causes
More than one of the ReceiptNumber, OriginatorConversationID, and ConversationID query
conditions are specified.
Procedure
Verify that only one of the ReceiptNumber, OriginatorConversationID, and ConversationID
query conditions is specified.

Copyright © Huawei
Mobile Money
4.577 IC40304
Description
The identity type of the receiver is invalid.
Scenario
During customer verification, the identity type of the receiver is not customer.
Access Channel
STK, USSD
Possible Causes
The identity type of the receiver is invalid.
Procedure
Verify the customer.
4.578 IC40316
Description
Failed to activate the FSI product. The FSI link does not meet the link type dependency
requirement.
Scenario
When a customer activates an FSI product, the FSI link to be created for the customer does
not meet the link type dependency requirement.
Access Channel
Web, STK, API
Possible Causes
The FSI link to be created for the customer does not meet the link type dependency
requirement.
Procedure
Activate the product that depends on the link type.

Copyright © Huawei
Mobile Money
4.579 IC40317
Description
Failed to modify the customer's link status.
Scenario
The FSI link for which the status is to be changed for a customer does not exist.
Access Channel
Web, API
Possible Causes
The link to be modified does not exist.
Procedure
Select a correct link.
4.580 IC40318
Description
The financial service integration (FSI) product fails to be activated for the customer.
Scenario
When a customer activates an FSI product, the activation confirmation from the financial
institution (FI) organization has timed out.
Access Channel
Web, STK, API
Possible Causes
The activation confirmation from the FI organization has timed out.
Procedure
Try again to activate the product.

Copyright © Huawei
Mobile Money
4.581 IC40319
Description
The FSI product fails to be activated for the customer.
Scenario
When a customer activates an FSI product, the customer attributes submitted by the FI are
incorrect.
Access Channel
Web, STK, API
Possible Causes
The customer attributes submitted by the FI are incorrect.
Procedure
Enter correct customer attributes.
4.582 IC40320
Description
Failed to add an FI KYC verification rule for the organization.
Scenario
When the FI KYC verification rule is modified for an organization, the rule with the attribute
name already exists.
Access Channel
Web
Possible Causes
The rule with the attribute name {0} already exists.
{0} indicates attribute name.
Procedure
Use other attribute names.

Copyright © Huawei
Mobile Money
4.583 IC40321
Description
Failed to edit or delete an FI KYC verification rule for an organization.
Scenario
When the FI KYC verification rule is modified for an organization, the rule with the attribute
name does not exist.
Access Channel
Web
Possible Causes
The rule with attribute name {0} does not exist.
{0} indicates an attribute name.
Procedure
Verify that the attribute name is correct.
4.584 IC40305
Description
The ReceiptNumber query condition is missing when the status of a transaction is queried.
Scenario
The ReceiptNumber query condition is missing when the status of a transaction is queried.
Access Channel
API
Possible Causes
The ReceiptNumber query condition is missing.
Procedure
Verify whether the ReceiptNumber parameter exists.

Copyright © Huawei
Mobile Money
4.585 IC40306
Description
No Transaction ReceiptNumber is found based on OriginatorConversationID or
ConversationID.
Scenario
When the status of a transaction is queried, no transaction ReceiptNumber is found based on
OriginatorConversationID or ConversationID.
Access Channel
API
Possible Causes
No transaction ReceiptNumber is found based on OriginatorConversationID or
ConversationID.
Procedure
Verify that value of OriginatorConversationID or ConversationID is valid.
4.586 IC40323
Description
Failed to initiate the investigation task.
Scenario
Investigate a workflow task.
Access Channel
Web
Possible Causes
The operator is not allowed to initiate an investigation on the customer.
Procedure
Initiate the investigation as another operator.

Copyright © Huawei
Mobile Money
4.587 IC40326
Description
Failed to unlink the FSI link.
Scenario
When an SP operator attempts to unlink an FSI link, there is no FSI link that can be unlinked.
Access Channel
Web, API
Possible Causes
There is no FSI link that can be unlinked.
Procedure
Verify that the FSI link can be unlinked.
4.588 IC40327
Description
The account type is associated with organization {0}.
{0}: indicates the ID of an organization.
Scenario
When a multi-instance internal account is created, the account type is associated with an
organization.
Access Channel
Web
Possible Causes
The account type is associated with organization {0}.
Procedure
Select another organization.

Copyright © Huawei
Mobile Money
4.589 IC40336
Description
The target state specified for the identity is invalid.
Scenario
When changing the state of an identity through the web or API channel, an operator enters an
invalid target state.
Access Channel
Web, API
Possible Causes
The target state specified for the identity is invalid.
Procedure
Check whether the target state of the identity is valid.
4.590 IC40337
Description
Scenario
When a customer activates an FSI product, the corresponding FI organization is not in the
Active state.
Access Channel
Web, STK, API, USSD
Possible Causes
The FI organization is not in the Active state.
Procedure
The organization link cannot be activated. Abandon this operation.

Copyright © Huawei
Mobile Money
4.591 IC40338
Description
Failed to set the operator's password. The two passwords entered are inconsistent.
Scenario
When the password is set for an operator whose access channel is API, the two passwords
entered are inconsistent.
Access Channel
Web
Possible Causes
The passwords entered are inconsistent.
Procedure
Verify that the two passwords are consistent.
4.592 IC40339
Description
Failed to set the operator's password. The access channel is not API.
Scenario
The access channel of an operator whose password is to be manually set is not API.
Access Channel
Web
Possible Causes
The operator's access channel is not API. The password can be manually set only for an
operator whose access channel is API.
Procedure
The operation is not allowed.

Copyright © Huawei
Mobile Money
4.593 IC40340
Description
Failed to change the operator's access channel. The access channel can be changed only
between web and handset.
Scenario
The access channel of an operator is changed to a channel which is not web or handset.
Access Channel
Web
Possible Causes
The access channel can be changed only between web and handset.
Procedure
Verify that the access channel is changed from web to handset or from handset to web.
4.594 IC40341
Description
Failed to change the operator's access channel.
Scenario
The access channel of an operator is changed to API and web or API and handset at the same
time.
Access Channel
Web
Possible Causes
The access channel cannot be set to API and web or API and handset at the same time.
Procedure
Do not select the API channel and the web or handset channel at the same time.

Copyright © Huawei
Mobile Money
4.595 IC40342
Description
FSI activation failed. The short code in the confirmation message is incorrect.
Scenario
During FSI activation, the confirmation message from a third party system is incorrect.
Access Channel
Web, STK, USSD, API
Possible Causes
The short code in the confirmation message from a third-party does not match with the FI
organization of the order.
Procedure
The confirmation message is invalid. Abandon this operation.
4.596 IC40343
Description
Failed to modify the revenue settlement profile because the organization has an unfinished
revenue settlement task.
Scenario
When an operator modifies the revenue settlement profile of an organization, the organization
has an unfinished revenue settlement task.
Access Channel
Web
Possible Causes
The organization has an unfinished revenue settlement task.
Procedure
Complete the revenue settlement task first.

Copyright © Huawei
Mobile Money
4.597 IC40345
Description
Failed to modify the customer's KYC information.
Scenario
When an operator changes the KYC information of a customer using the CCH function, the
specified KYC values are invalid. Only one of DOB and ID Details can be specified.
Access Channel
USSD, STK
Possible Causes
The specified KYC values are invalid. You must specify only one of DOB or ID details.
Procedure
Enter valid KYC values.
4.598 IC40344
Description
Failed to change the identity status. The target status is the same as the old status.
Scenario
When the status of an identity is changed, the target status is the same as the old status.
Access Channel
Web, API, USSD, STK
Possible Causes
Failed to change the identity status. The target status is the same as the old status.
Procedure
Enter a valid target status.

Copyright © Huawei
Mobile Money
4.599 IC40346
Description
FSI activation failed because a third-party FI organization has rejected the activation request.
Scenario
When an FSI is activated, a third-party FI organization rejects the activation request.
Access Channel
Web, API, USSD, STK
Possible Causes
A third-party FI organization has rejected the activation request.
Procedure
The FI organization does not allow the customer to activate the FSI. Abandon this operation.
4.600 IC40347
Description
An input parameter of the method is invalid.
Scenario
The length, type, or format of an input parameter of the method is incorrect.
Access Channel
Web, API, USSD, STK
Possible Causes
Procedure
Enter a correct value.

Copyright © Huawei
Mobile Money
4.601 IC40348
Description
During account status change, the {0} account is invalid because it does not exist or does not
belong to the current identity.
{0}: indicates Account No.
Scenario
The account whose status is to be modified is invalid.
Access Channel
Web, API, USSD, STK
Possible Causes
The {0} account is invalid because it does not exist or does not belong to the current identity.
Procedure
Verify that the account is valid.
4.602 IC40349
Description
Failed to change the parent organization of the child organization because the new parent
organization is in an invalid state.
Scenario
The new parent organization is in an invalid state when the parent organization of a child
organization is changed.
Access Channel
Web
Possible Causes
organization is in an invalid state.
Procedure
Check whether the new parent organization is in the Active, Suspended, or Frozen state.

Copyright © Huawei
Mobile Money
4.603 IC40350
Description
Failed to change the parent organization of the child organization because the child
organization has child organizations.
Scenario
The child organization whose parent organization is to be changed has child organizations.
Access Channel
Web
Possible Causes
organization has child organizations.
Procedure
Verify that the child organization whose parent organization is to be changed has no child
organizations.
4.604 IC40351
Description
As hierarchy level is different before and after parent organization updated, operation failed.
Scenario
When the parent organization of a child organization is changed, the hierarchy level of the
child organization is different before and after the change.
Access Channel
Web
Possible Causes
Failed to change the parent organization of the child organization because the hierarchy level
of the child organization is different before and after the change.
Procedure
Select a correct parent organization.

Copyright © Huawei
Mobile Money
4.605 IC40352
Description
Cannot change parent organization for the child organization because the parent organization
does not support the identity model that child organization has.
Scenario
When the parent organization of a child organization is changed, the identity model does not
match with the accounting model of the top organization.
Access Channel
Web
Possible Causes
Failed to change the parent organization of the child organization because the accounting
model of the top organization does not support the identity model of the child organization.
Procedure
4.606 IC40353
Description
organization is the same as the old one.
Scenario
When the parent organization of a child organization is changed, the new parent organization
is the same as the old one.
Access Channel
Web
Possible Causes
organization is the same as the old one.
Procedure
Select another parent organization.

Copyright © Huawei
Mobile Money
4.607 IC40354
Description
The parent organization is not allowed to be changed for child organization if there is pending
transactions.
Scenario
When the parent organization of a child organization is changed, the child organization has a
transaction in the Pending state.
Access Channel
Web
Possible Causes
organization has a transaction in the Pending state.
Procedure
Complete the pending transaction first.
4.608 IC40355
Description
The parent organization is not allowed to be changed if there is pending tasks.
Scenario
When the parent organization of a child organization is changed, the child organization has a
business operation in the Pending state.
Access Channel
Web
Possible Causes
organization has a business operation in the Pending state.
Procedure
Complete the pending business operation first.

Copyright © Huawei
Mobile Money
4.609 IC40356
Description
The parent organization is not allowed to be changed if there is on-going commission process
not finished.
Scenario
When the parent organization of a child organization is changed, the child organization has an
on-going commission process.
Access Channel
Web
Possible Causes
organization has an on-going commission process.
Procedure
Complete the commission process first.
4.610 IC40357
Description
The parent organization is not allowed to be changed if there is still fund left on the account
which is no more used.
Scenario
When the parent organization of a child organization is changed, an account of the child
organization has a balance and cannot be closed.
Access Channel
Web
Possible Causes
Failed to change the parent organization of the child organization because the balance of the
child organization is not zero.
Procedure
Clear the account balance first.

Copyright © Huawei
Mobile Money
4.611 IC40358
Description
Cannot change parent organization for the child organization because the parent organization
does not support the identity model that child organization has.
Scenario
When the parent organization of a child organization is changed, the identity model of the
new parent organization does not support the identity model of the child organization.
Access Channel
Web
Possible Causes
Failed to change the parent organization of the child organization because the identity model
of the new parent organization does not support the identity model of the child organization.
Procedure
4.612 IC40359
Description
The new identity model is not yet supported by the parent organization.
Scenario
When the identity model of a child organization is changed, the parent organization does not
support the new identity model.
Access Channel
Web
Possible Causes
The parent organization does not support the new identity model.
Procedure
Verify whether the parent organization supports the current identity model.

Copyright © Huawei
Mobile Money
4.613 IC40360
Description
It is not allowed to change the identity model for the current organization.
Scenario
The child organization does not support identity model change.
Access Channel
Web
Possible Causes
The child organization does not support identity model change.
Procedure
Check whether the current organization is at the second level.
4.614 IC40361
Description
The identity model is not allowed to be changed if there is pending transactions.
Scenario
When the identity model of a child organization is changed, the child organization has a
transaction in the Pending state.
Access Channel
Web
Possible Causes
The identity model of the current organization cannot be changed because the organization
has a pending transaction.
Procedure
Complete the pending transaction first.

Copyright © Huawei
Mobile Money
4.615 IC40362
Description
The identity model is not allowed to be changed if there is pending tasks.
Scenario
When the identity model of a child organization is changed, the child organization has a task
in the Pending state.
Access Channel
Web
Possible Causes
has a pending task.
Procedure
Complete the pending task first.
4.616 IC40363
Description
The identity model is not allowed to be changed if the on-going commission process is not
finished.
Scenario
When the identity model of a child organization is changed, the child organization has an
ongoing commission process.
Access Channel
Web
Possible Causes
has an ongoing commission process.
Procedure
Complete the commission process first.

Copyright © Huawei
Mobile Money
4.617 IC40364
Description
No default charge distribution model defined for Aggregated identity model.
Scenario
When the identity model of a child organization is changed, no default charge distribution
model is configured for the child organization.
Access Channel
Web
Possible Causes
The identity model of the current organization cannot be changed because no default charge
distribution model is configured for the organization.
Procedure
Configure the Charge Distribution Model parameter first.
4.618 IC40365
Description
Failed to change the parent organization because the new parent organization has no sharing
account.
Scenario
The parent organization of a child organization is changed to a new parent organization that
has no sharing account.
Access Channel
Web
Possible Causes
Failed to change the parent organization because the new parent organization has no sharing
account.
Procedure
Verify whether the accounting model of the parent organization requires a sharing account.

Copyright © Huawei
Mobile Money
4.619 IC40366
Description
ID or DOB provided is invalid, please check your ID or DOB.
Scenario
The DOB or ID of a SIM activation initiator is incorrect.
Access Channel
STK
Possible Causes
ID or DOB provided is invalid, please check your ID or DOB.
Procedure
Set DOBID to a value the same as the DOB or any ID Number.
4.620 IC40367
Description
When a SIM card is activated on a till, the organization of the till has no operator.
Scenario
Access Channel
STK
Possible Causes
Procedure
Create an organization operator before activating the till.

Copyright © Huawei
Mobile Money
4.621 IC40368
Description
When a SIM card is activated, the operator is in an invalid state.
Scenario
When a SIM card is activated, the organization operator obtained by DOBID or PIN is in an
invalid state.
Access Channel
STK
Possible Causes
When a SIM card is activated, the operator is in an invalid state.
Procedure
Change the status of the operator to Pending Active or Active.
4.622 IC40369
Description
Your PIN is incorrect, please check your PIN.
Scenario
When a SIM card is activated, the organization operator PIN obtained by DOBID is incorrect.
Access Channel
STK
Possible Causes
Your PIN is incorrect, please check your PIN.
Procedure
Enter a correct PIN.

Copyright © Huawei
Mobile Money
4.623 IC40370
Description
Please ensure you have an operator with permission to activate a till.
Scenario
When activating a SIM card, the operator has no permission to activate a till.
Access Channel
STK
Possible Causes
Please ensure you have an operator with permission to activate a till.
Procedure
Verify that the operator has the permission to perform the operation.
4.624 IC40371
Description
The identity model is not allowed to be changed if there is still fund left on the account which
is no more used.
Scenario
When the identity model of a organization is changed,, an account of the organization has a
balance and cannot be closed.
Access Channel
Web
Possible Causes
Failed to change the identity model of a organization because the balance of the organization
is not zero.
Procedure
Clear the account balance first.

Copyright © Huawei
Mobile Money
4.625 IC40372
Description
Shared account {0} does not exist in the parent organization.
{0} indicates account type name.
Scenario
When the product of a child organization is changed, the parent organization does not have
the corresponding shared account.
Access Channel
Web
Possible Causes
Failed to change the product of a child organization because the parent organization does not
have the corresponding shared account.
Procedure
Check whether the parent organization has the corresponding shared account.
4.626 IC40373
Description
When a product is changed for a child organization, the new product must comply with the
identity model of a product already subscribed to by the child organization.
Scenario
When a product is changed for a child organization, the new product does not comply with the
identity model of a product already subscribed to by the child organization.
Access Channel
Web
Possible Causes
The new product does not comply with the identity model of a product already subscribed to
by the child organization.

Copyright © Huawei
Mobile Money
Procedure
Close existing products with the identity model.
4.627 IC40374
Description
Failed to activate the till SIM card because the organization of the till is in an invalid state.
Scenario
When a till SIM card is activated, the organization of the till is in an invalid state or does not
exist.
Access Channel
STK
Possible Causes
Failed to activate the till SIM card because the organization of the till is in an invalid state.
Procedure
Change the status of the organization of the till to Active.
4.628 IC40375
Description
The current operation is not allowed because the password of the API caller fails to be
authenticated.
Scenario
Access Channel
API
Possible Causes
The password is incorrect during API caller authentication.
Procedure

Copyright © Huawei
Mobile Money
4.629 IC40376
Description
FSI activation failed because a mandatory KYC field is missing.
Scenario
During FSI activation, a mandatory KYC field is missing.
Access Channel
API, STK, USSD, Web
Possible Causes
The {0} mandatory field is missing.
{0} indicates a mandatory KYC field name.
Procedure
Provide the mandatory KYC information in the Mobile Money system.
4.630 IC40377
Description
FSI activation failed because the specified MSISDN does not belong to any customer.
Scenario
During FSI activation, the specified MSISDN does not belong to any customer.
Access Channel
API, STK, USSD, Web
Possible Causes
The specified MSISDN does not belong to any customer.
Procedure
Enter a correct MSISDN.

Copyright © Huawei
Mobile Money
4.631 IC40378
Description
Your PIN is locked, please unlock your PIN.
Scenario
When a till menu is activated through by STK, the PIN of the found operator is locked.
Access Channel
STK
Possible Causes
The operator's PIN has been locked.
Procedure
Unlock the PIN.
4.632 IC40379
Description
The initiator of the transaction query operation and the initiator of the transaction belong to
different organizations.
Scenario
Access Channel
API
Possible Causes
Procedure
Enter an operator of the organization to which the transaction initiator belongs.

Copyright © Huawei
Mobile Money
4.633 IC40410
Description
The selected product does not support the charge profile.
Scenario
The charge profile is not associated with the selected product when the KYC information of
an identity is modified.
Access Channel
Web
Possible Causes
The charge profile is not associated with the selected product.
Procedure
Charge Profile.
2. Assign the charge profile to the selected product.
4.634 IC40411
Description
Operators are not allowed to approve workflow tasks created by themselves.
Scenario
This error code is generated when an operator approves a workflow task created by
himself/herself.
Access Channel
Web
Possible Causes
Operators are not allowed to approve workflow tasks created by themselves.
Procedure
Enable another operator to log in and approve the workflow task.

Copyright © Huawei
Mobile Money
4.635 IC40412
Description
The length of the bank card number from which the first six characters are obtained as an
IMD does not meet requirements.
Scenario
This error code is generated when the length of the bank card number from which the first six
characters are obtained as an IMD does not meet requirements.
Access Channel
USSD
Possible Causes
The length of the bank card number does not meet requirements.
Procedure
Change the bank card number.
4.636 IC40426
Description
The input region is incorrect.
Scenario
The region input during bulk organization creation is not selectable.
Access Channel
Web(Bulk)
Possible Causes
The region {0} is not selectable.
{0} indicates a region name.
Procedure
Input the correct region.

Copyright © Huawei
Mobile Money
4.637 IC40427
Description
The account type has been associated with the selected currency.
Scenario
This error code is generated if the account type selected during the creation of a single-
instance internal account has been associated with the selected currency.
Access Channel
Web
Possible Causes
The account type has been associated with the selected currency.
Procedure
Select another currency.
4.638 IC40428
Description
The order whose transaction sequence number is {0} is uncompleted, and the workflow needs
to be reserved.
{0}: order ID.
Scenario
A review workflow is in progress.
Access Channel
Web
Possible Causes
The order whose transaction sequence number is {0} is uncompleted, and the workflow needs
to be reserved.
Procedure
Obtain and analyze log/debug/tc_debug.log and log/debug/ic_debug.log.

Copyright © Huawei
Mobile Money
4.639 IC40429
Description
The receiver number must be a customer number.
Scenario
The receiver number entered when customer KYC information is queried or updated through
the API channel is a till number.
Access Channel
API
Possible Causes
The receiver number is not a customer number.
Procedure
Enter the correct customer number.
4.640 IC40430
Description
The identity does not have the {0} account.
{0} indicates an account alias.
Scenario
An identity whose account status is changed in bulk does not have the account in a record in
the bulk file.
Access Channel
Web(Web)
Possible Causes
The identity does not have the {0} account.
Procedure
Verify that the identity has the {0} account.

Copyright © Huawei
Mobile Money
4.641 IC40433
Description
An error occurred when adding a beneficiary for the customer. The number of beneficiaries
owned by a customer reaches {0}.
{0} indicates the maximum number of beneficiaries owned by a customer.
Scenario
The number of beneficiaries owned by the customer for which a beneficiary is being added
reaches the maximum value.
Access Channel
USSD, API
Possible Causes
The number of beneficiaries owned by a customer reaches {0}.
Procedure
Instruct an SP operator to change the value of the system parameter that specifies the
maximum number of beneficiaries owned by a customer.
4.642 IC40434
Description
Adding the beneficiary failed. The beneficiary that is being added for a customer already
exists.
Scenario
The beneficiary that is being added for a customer already exists.
Access Channel
USSD, API
Possible Causes
The beneficiary that is being added for a customer already exists.
Procedure
Reconfigure beneficiary information.

Copyright © Huawei
Mobile Money
4.643 IC40435
Description
Deleting the beneficiary failed. The beneficiary that is being deleted for a customer does not
exist.
Scenario
The beneficiary that is being deleted for a customer does not exist.
Access Channel
USSD, API
Possible Causes
The beneficiary that is being deleted for a customer does not exist.
Procedure
4.644 IC40436
Description
Adding the beneficiary failed. The value length of Reference for the beneficiary that is being
added for a customer exceeds the maximum value {0}.
{0} indicates the maximum length of Reference.
Scenario
The value length of Reference for the beneficiary that is being added for a customer exceeds
the maximum value.
Access Channel
USSD, API
Possible Causes
The value length of Reference for the beneficiary that is being added for a customer exceeds
the maximum value.
Procedure

Copyright © Huawei
Mobile Money
4.645 IC40437
Description
Adding the beneficiary failed. The value of Reference for the beneficiary that is being added
for a customer is in an incorrect format.
Scenario
The value of Reference for the beneficiary that is being added for a customer is in an incorrect
format.
Access Channel
USSD, API
Possible Causes
The value of Reference for the beneficiary that is being added for a customer is in an
incorrect format.
Procedure
4.646 IC40438
Description
Adding the beneficiary failed. The organization corresponding to the short code of the
beneficiary that is being added for a customer does not exist.
Scenario
The organization corresponding to the short code of the beneficiary that is being added for a
customer does not exist.
Access Channel
USSD, API
Possible Causes
customer does not exist.
Procedure

Copyright © Huawei
Mobile Money
4.647 IC40439
Description
Adding the beneficiary failed. The organization corresponding to the short code of the
beneficiary that is being added for a customer is not in the active state.
Scenario
customer is not in the active state.
Access Channel
USSD, API
Possible Causes
customer is not in the active state.
Procedure
4.648 IC40440
Description
The MSISDN field cannot be left blank when the receiver involved in MSISDN recycling is a
till.
Scenario
The MSISDN field is not left blank when the receiver involved in MSISDN recycling is a till.
Access Channel
API
Possible Causes
The MSISDN field is not left blank when the receiver is a till.
Procedure
Leave the MSISDN field blank.

Copyright © Huawei
Mobile Money
4.649 IC40441
Description
The value of the receiver's MSISDN is inconsistent with the entered MSISDN.
Scenario
The value of the receiver's MSISDN is inconsistent with the entered MSISDN during
MSISDN recycling.
Access Channel
API
Possible Causes
The value of the receiver's MSISDN is inconsistent with the entered MSISDN.
Procedure
Change the value of the MSISDN field. Verify that the value is consistent with the receiver
MSISDN.
4.650 IC40442
Description
Adding the beneficiary fails. The value length of Bill Reference for the beneficiary that is
being added for a customer exceeds the maximum value {0}.
Scenario
The value length of Bill Reference for a beneficiary that is being added for a customer
exceeds the maximum value.
Access Channel
USSD, API
Possible Causes
The value length of Bill Reference for the beneficiary that is being added for a customer
exceeds the maximum value.
Procedure
Change the value of Bill Reference.

Copyright © Huawei
Mobile Money
4.651 IC40443
Description
If the initiator is an organization operator when using the API to register the customer, the
RegisterBy parameter must be blank.
Scenario
If the initiator is an organization operator when using the API to register the customer, the
RegisterBy parameter is not blank.
Access Channel
Web
Possible Causes
The initiator is an organization operator, and the RegisterBy parameter is not blank.
Procedure
Delete the value of the RegisterBy parameter.
4.652 IC40444
Description
When you modify products of a till through the API channel, products of the till cannot all be
deleted.
Scenario
Modify products of a till through the API channel.
Access Channel
API
Possible Causes
Products of the till cannot all be deleted.
Procedure
Verify that till's product exists.

Copyright © Huawei
Mobile Money
4.653 IC40445
Description
If the initiator is an organization operator when using the API to query the child organization,
the receiver must be blank.
Scenario
If the initiator is an organization operator when using the API to query the child organization,
the receiver is not blank.
Access Channel
API
Possible Causes
The initiator is an organization operator, and the receiver is not blank.
Procedure
Delete the value of the receiver.
4.654 IC40446
Description
The current organization has a shared account, and the parent short code cannot be changed.
Scenario
This error is reported when you want to change the hierarchical structure of an organization
because the current organization and its parent organization share an account.
Access Channel
Web
Possible Causes
The current organization has a shared account.
Procedure
Retain the current hierarchical structure of the organization.

Copyright © Huawei
Mobile Money
4.655 IC40447
Description
The current organization has an unfinished transaction, and the parent short code cannot be
changed.
Scenario
This error is reported when you want to change the hierarchical structure of an organization
because the organization has an unfinished transaction.
Access Channel
Web
Possible Causes
The current organization has an unfinished transaction.
Procedure
Try again after the transaction finishes.
4.656 IC40451
Description
Failed to delete the O2C link.
Scenario
This error occurred when you attempt to delete an O2C link using the API channel.
Access Channel
API
Possible Causes
The O2C link {0} to be deleted does not exist.
{0} indicates O2C link number.
Procedure
Verify that the O2C link to be deleted exists.

Copyright © Huawei
Mobile Money
4.657 IC40452
Description
Some case-sensitive or case-insensitive answer fields are empty.
Scenario
This error message is reported when some case-sensitive or case-insensitive answer fields are
empty.
Access Channel
Web
Possible Causes
Some case-sensitive or case-insensitive answer fields are empty.
Procedure
Ensure that all of or none of case-sensitive and case-insensitive answer fields are empty.
4.658 IC40453
Description
Failed to delete the O2C link.
Scenario
This error message is reported when the O2C link list has duplicate O2C link numbers.
Access Channel
API
Possible Causes
The O2C link list has duplicate O2C link numbers.
Procedure
Change the duplicate O2C link numbers in the O2C link list.

Copyright © Huawei
Mobile Money
4.659 IC40454
Description
Identity model of the current organization is inconsistent with that of the new upper-level
organization.
Scenario
When the hierarchical structure of the organization is modified, Identity Model of the current
organization is inconsistent with that of the new upper-level organization.
Access Channel
Web
Possible Causes
Inconsistent identity models.
Procedure
Retain the hierarchical structure of the current organization.
4.660 IC40455
Description
The value of the TaxCode parameter must be unique in a request.
Scenario
This error is reported when the ChangeOrgTaxExemption request initiated through the API
channel contains duplicate tax codes.
Access Channel
API
Possible Causes
The value of the TaxCode parameter is not unique in a request.
Procedure
Enter different tax codes.

Copyright © Huawei
Mobile Money
4.661 IC40456
Description
The identity is in suspend state, and the caller does not need to be authenticated.
Scenario
This error is reported when a caller authentication request is initiated through API.
Access Channel
API
Possible Causes
The identity is in suspend state, and the caller does not need to be authenticated.
Procedure
Unlock the identity status.
4.662 IC40457
Description
The question and answer are invalid because the security policy has been changed. Contact
the administrator to reset your password.
Scenario
This message is displayed when the system fails to authenticate the question and answer after
the security policy is change but the question and answer are not changed.
Access Channel
Web
Possible Causes
The security policy has been changed but the question and answer has not been changed.
Procedure
Contact the administrator to reset your password.

Copyright © Huawei
Mobile Money
4.663 IC40458
Description
The till failed to be created because the default operator does not belong to the organization to
which the till belongs.
Scenario
This error is reported when the default operator entered for creating a till does not belong to
the organization to which the till belongs.
Access Channel
Web
Possible Causes
The default operator does not belong to the organization to which the till belongs.
Procedure
Select another default operator.
4.664 IC40459
Description
Failed to create the till. The default operator cannot be in Close state.
Scenario
This error is reported when the default operator entered for creating a till is in Close state.
Access Channel
Web
Possible Causes
The default operator is in Close state.
Procedure
Select another default operator.

Copyright © Huawei
Mobile Money
4.665 IC40469
Description
You do not have the permission to perform the operation.
Scenario
Electronic voucher center (EVC) end users access the system using the USSD, SMS, or STK
method to query their masked number. This error is reported when the system does not
support masked number.
Access Channel
USSD, SMS, STK, Web
Possible Causes
The system does not support masked number.
Procedure
1. Check whether the command is correct.
2. If the command is correct, contact the SP.
4.666 IC40470
Description
The entered masked number is incorrect.
Scenario
This error is reported when an SP operator enters incorrect masked number to query terminal
user numbers.
Access Channel
USSD, SMS, STK, Web
Possible Causes
Masked number is incorrect.
Procedure
Try again after verification.

Copyright © Huawei
Mobile Money
4.667 IC40471
Description
The MSISDN does not support masked number.
Scenario
EVC end users access the system using the USSD, SMS, or STK method to query their
masked number. This error is reported when the user number does not support masked
number.
Access Channel
USSD, SMS, STK, Web
Possible Causes
The MSISDN does not support masked number.
Procedure
Contact the SP for troubleshooting.
4.668 IC40472
Description
The refund destination number cannot be the same as the original customer number.
Scenario
This error occurs when an SP operator performs the refund operation for a customer on the
portal and the entered mobile number is used before the customer account is deregistered.
Access Channel
Web
Possible Causes
The entered refund destination number is the same as the original customer number.
Procedure
Enter another destination number.

Copyright © Huawei
Mobile Money
4.669 IC40473
Description
The start time specified for querying records is later than the end time.
Scenario
The start time specified for querying records is later than the end time.
Access Channel
API
Possible Causes
The specified start time is later than the end time.
Procedure
Change the start time or end time, ensuring that the start time is earlier than the end time.
4.670 IC40475
Description
Operation failed. The default operator ID of the till cannot be empty.
Scenario
This error is reported when the default operator ID of a till is empty during till creation or
default till operator ID modification.
Access Channel
Web
Possible Causes
The default operator ID of the till is empty.
Procedure
Enter a default operator ID for the till.

Copyright © Huawei
Mobile Money
4.671 IC40476
Description
The entered verification question cannot be repeated.
Scenario
This error is reported when Verify Caller authentication is initiated through the API channel
and the entered verification question is repeated.
Access Channel
API
Possible Causes
The entered verification question {0} is repeated.
{0} indicates a verification question.
Procedure
Check the entered verification question information.
4.672 IC40477
Description
Failed to verify reminder {0}.
Scenario
This error is reported when a customer or an organization initiates a transaction according to a
nonexistent reminder.
Access Channel
STK, USSD, WEB
Possible Causes
Reminder {0} does not exist in reminder instances of the system.
Procedure
Check information about reminder {0}.

Copyright © Huawei
Mobile Money
4.673 IC40478
Description
Reminder {0} has expired.
Scenario
This error is reported when a customer or an organization initiates a transaction according to
an expired reminder.
Access Channel
STK, USSD, WEB
Possible Causes
Reminder {0} has expired.
Procedure
Check information about reminder {0}.
4.674 IC40479
Description
Reminder schedule ID {0} does not exist.
{0} indicates a reminder schedule ID.
Scenario
This error is reported when a customer or an organization queries or deletes a reminder
schedule by schedule ID but the entered schedule ID does not exist.
Access Channel
STK, USSD, WEB
Possible Causes
Reminder schedule ID {0} does not exist.
Procedure
Enter a correct schedule ID.

Copyright © Huawei
Mobile Money
4.675 IC40480
Description
Reminder schedule name {0} already exists.
{0} indicates a reminder schedule name.
Scenario
This error is reported when the reminder name entered when a reminder schedule is created
already exists.
Access Channel
STK, USSD, WEB
Possible Causes
Reminder schedule name {0} already exists.
Procedure
Enter another reminder schedule name.
4.676 IC40481
Description
The status of {0} is incorrect.
{0} indicates identity type.
Scenario
This error is reported when the identity status is incorrect when a reminder schedule is
created.
Access Channel
STK, USSD, WEB
Possible Causes
The status of {0} is incorrect.

Copyright © Huawei
Mobile Money
Procedure
Enter a correct {0}.
4.677 IC40482
Description
The customer is a {0} customer and the operation cannot be performed.
{0} indicates customer type.
Scenario
This error is reported when the customer entered when a reminder schedule is created is not a
Access Channel
STK, USSD, WEB
Possible Causes
The customer is a {0} customer.
Procedure
Select a registered customer to perform the operation.
4.678 IC40483
Description
Operation failed. {0} has not subscribed to the service.
Scenario
This error is reported when the identity service does not exist and is not subscribed.
Access Channel
STK, USSD, WEB

Copyright © Huawei
Mobile Money
Possible Causes
{0} has not subscribed to the service.
Procedure
Before operation, ensure that the identity service has been subscribed.
4.679 IC40484
Description
Operation failed. The number of reminder schedules has reached the maximum.
Scenario
This error is reported when the number of reminder schedules has reached the maximum.
Access Channel
STK, USSD, WEB
Possible Causes
The number of reminder schedules has reached the maximum.
Procedure
Change the threshold of the number of reminder schedules to a greater one or delete some
existing reminder schedules.
4.680 IC40485
Description
Failed to query the transaction records. The entered transaction status does not exist in the
system.
Scenario
This error is reported when the entered transaction status for querying transaction records
does not exist in the system.
Access Channel
API

Copyright © Huawei
Mobile Money
Possible Causes
The entered transaction status does not exist in the system.
Procedure
Enter a correct transaction status.
4.681 IC40486
Description
The entered value of Reminder Schedule ID must be a number.
Scenario
This error is reported when a customer queries details on the UMC client but the entered
value of Reminder Schedule ID is not a number.
Access Channel
Web
Possible Causes
The entered value of Reminder Schedule ID is not a number.
Procedure
Enter a correct value of Reminder Schedule ID.
4.682 IC40487
Description
Failed to delete reminder schedule {0}.
{0} indicates a reminder schedule ID.
Scenario
Failed to delete reminder schedule.
Access Channel
STK, USSD, Web

Copyright © Huawei
Mobile Money
Possible Causes
Failed to delete reminder schedule {0}.
Procedure
Verify that the database connection is normal.
4.683 IC40488
Description
The account entered during hot account instance configuration must be an organization
account instead of a customer or an SP account.
Scenario
This error is reported when the account entered during hot account instance configuration is
not an organization account.
Access Channel
Web
Possible Causes
The account entered during hot account instance configuration is not an organization account.
Procedure
Enter an organization account.
4.684 IC40489
Description
The entered account {0} does not exist.
Scenario
This error is reported when the account entered during hot account instance configuration
does not exist.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The entered account {0} does not exist.
Procedure
Enter an existent account.
4.685 IC40490
Description
The entered account {0} does not belong to identity {1}.

{1} indicates an identity ID.
Scenario
This error is reported when the account entered during hot account instance configuration
does not match with the identity.
Access Channel
Web
Possible Causes
The entered account {0} does not belong to identity {1}.
Procedure
Check the entered account and identity information.
4.686 IC40491
Description
Only transactions can be queried. Actions cannot be queried.
Scenario
When a transaction query request is initiated through the API channel, a message indicating
that only transactions can be queried is displayed.
Access Channel
API

Copyright © Huawei
Mobile Money
Possible Causes
Only transactions can be queried.
Procedure
Ensure that transactions are queried.
4.687 IC40492
Description
The Reminder Schedule ID parameter cannot be left empty.
Scenario
This error is reported when a customer performs the query operation on the UMC Client but
no Reminder Schedule ID is entered.
Access Channel
Web
Possible Causes
The Reminder Schedule ID parameter is left empty.
Procedure
4.688 IC40493
Description
The value of Reminder Schedule ID must contain 1 to 18 characters.
Scenario
This error is reported when a customer performs the query operation on the UMC Client but
the value length of the Reminder Schedule ID is incorrect.
Access Channel
Web
Possible Causes
The entered value of Reminder Schedule ID contains more than 18 characters.

Copyright © Huawei
Mobile Money
Procedure
4.689 IC40495
Description
Failed to query the reminder schedule.
Scenario
This error is reported when an SP operator queries the reminder schedule for a customer on a
web page but fails to invoke the query interface.
Access Channel
Web
Possible Causes
During the query, a communication terminal fault (for example, network disconnection)
causes the query interface invoking failure.
Procedure
View the log/debug/bcs_debug.log file of the BCS NE to troubleshoot the fault.
4.690 IC40496
Description
Failed to create the additional account. The account name cannot be empty.
Scenario
This error is reported during the creation of an additional account if the account name is left
empty.
Access Channel
Web
Possible Causes
The account name is left empty.

Copyright © Huawei
Mobile Money
Procedure
Ensure that the account name is not empty.
4.691 IC40497
Description
Failed to create the additional account. The length of the entered account name cannot exceed
the maximum.
Scenario
This error is reported during the creation of an additional account if the length of the entered
account name exceeds the maximum.
Access Channel
Web
Possible Causes
The length of the entered account name exceeds the maximum.
Procedure
Enter an account name whose length does not exceed the maximum.
4.692 IC40498
Description
Failed to create the additional account. The entered account name must be different from the
value of Name of default account instance.
Scenario
This error is reported during the creation of an additional account if the entered account name
is the same as the value of Name of default account instance.
Access Channel
Web
Possible Causes
The entered account name is the same as the value of Name of default account instance.

Copyright © Huawei
Mobile Money
Procedure
Ensure that the entered account name is different from the value of Name of default account
instance.
4.693 IC40499
Description
Failed to create the additional account. The entered account name already exists in the system.
Scenario
already exists in the system.
Access Channel
Web
Possible Causes
The entered account name already exists in the system.
Procedure
Ensure that the entered account name does not exist in the system.
4.694 IC40500
Description
Failed to create the additional account. The account name must consist of letters and digits.
Scenario
does not consist of letters and digits.
Access Channel
Web
Possible Causes
The entered account name does not consist of letters and digits.

Copyright © Huawei
Mobile Money
Procedure
Ensure that the entered account name consists of letters and digits.
4.695 IC40501
Description
Failed to create the additional account. The number of accounts under the same account type
of an identity cannot be greater than the maximum specified by the system control parameter.
Scenario
This error is reported during the creation of an additional account if the number of accounts
under the same account type of an identity is greater than the maximum specified by the
system control parameter.
Access Channel
Web
Possible Causes
The number of accounts under the same account type of an identity is greater than the
maximum specified by the system control parameter.
Procedure
Ensure that the number of accounts under the same account type of an identity is not greater
than the maximum specified by the system control parameter.
4.696 IC40502
Description
Failed to create the additional account. The account type must be supported by the system.
Scenario
This error is reported during the creation of an additional account if the account type is not
supported by the system.
Access Channel
Web
Possible Causes
The account type is not supported by the system.

Copyright © Huawei
Mobile Money
Procedure
Ensure that the account type is supported by the system.
4.697 IC40503
Description
The customer whose MSISDN is {0} does not exist in the system.
{0} indicates a MSISDN.
Scenario
This error is reported when a customer logs in to the system using the mobile App but the
system detects that the customer corresponding to the MSISDN does not exist.
Access Channel
Web
Possible Causes
The customer whose MSISDN is {0} does not exist in the system.
Procedure
Register with the system using the mobile App.
4.698 IC40504
Description
The receiver must be empty when the request is initiated.
Scenario
This error is reported when a BO service request is initiated through the API but the receiver
is not empty.
Access Channel
API
Possible Causes
The receiver is not empty when the request is initiated.

Copyright © Huawei
Mobile Money
Procedure
Leave the receiver empty.
4.699 IC40505
Description
Failed to delete the reminder schedule.
Scenario
This error is reported when an SP operator deletes a reminder schedule for a customer through
the web channel but the reminder has already been deleted through another channel.
Access Channel
Web
Possible Causes
The reminder schedule has already been deleted for the customer through another channel.
Procedure
Check whether the reminder schedule to be deleted exists.
4.700 IC40506
Description
The identity does not have this default account type and accounts of this account type cannot
be created.
Scenario
This error is reported during the creation of an additional account if the identity does not have
this default account type.
Access Channel
Web
Possible Causes
The identity does not have this default account type and accounts of this account type cannot
be created.

Copyright © Huawei
Mobile Money
Procedure
Ensure that the type of the account to be created is supported by the system and the identity
has this default account type.
4.701 IC40507
Description
The reversal amount cannot be greater than the original transaction amount.
Scenario
This error is reported when a specified transaction is reversed through the API but the entered
reversal amount is greater than the original transaction amount.
Access Channel
API
Possible Causes
The reversal amount entered when a specified transaction is reversed is greater than the
original transaction amount.
Procedure
Check the entered reversal amount.
4.702 IC40508
Description
The format of the default operator ID is incorrect.
Scenario
When the API access the Create Till, the entered value of DefaultOperatorID does not meet
the system requirements.
Access Channel
Web, API
Possible Causes
The format of the default operator ID is incorrect.

Copyright © Huawei
Mobile Money
Procedure
Enter a correct default operator ID.
4.703 IC40509
Description
The AuthenticationType parameter is incorrect.
Scenario
This error is reported when an organization operator is created but the AuthenticationType
parameter is incorrect.
Access Channel
API
Possible Causes
The AuthenticationType parameter is incorrect.
Procedure
Check the AuthenticationType parameter.
4.704 IC40510
Description
The entered account name is incorrect.
Scenario
This error is reported when a customer or organization operator closes an account through the
STK channel but the entered account name is incorrect.
Access Channel
STK
Possible Causes
The entered account name is incorrect.
Procedure
Enter a correct account name.

Copyright © Huawei
Mobile Money
4.705 IC40511
Description
AccountTypeId and AcountTypeAlias cannot be both left empty.
Scenario
This error is reported during the creation of an additional account if both AccountTypeId and
AcountTypeAlias are left empty.
Access Channel
STK
Possible Causes
Both AccountTypeId and AcountTypeAlias are left empty.
Procedure
Ensure that AccountTypeId and AcountTypeAlias are not both left empty.
4.706 IC40512
Description
The account type queried by AcountTypeAlias does not exist or has multiple records.
Scenario
This error is reported during the creation of an additional account if the account type queried
by AcountTypeAlias does not exist or has multiple records.
Access Channel
STK
Possible Causes
The account type queried by AcountTypeAlias does not exist or has multiple records.
Procedure
Ensure that the account type to be created is unique.

Copyright © Huawei
Mobile Money
4.707 IC40513
Description
Failed to create the lower-level organization because the operation is not supported for the
identity model.
Scenario
Create organizations, operators, and tills in one step. Products are preset in the system based
on the organization level. When an organization operator initiates a request to create a lower-
level organization, the system checks whether the identity model corresponding to the upper-
level organization matches with that of the product. This error is reported in either of the
following scenarios: The identity models corresponding to the upper-level organization and
product are both mixed. (The identity type of a child organization must be AGGREGATOR or
CENTRALLY_OWNED.) The identity model of the upper-level organization is
AGGREGATOR or CENTRALLY_OWNED but is inconsistent with the identity model of the
product. (For example, the identity type of the upper-level organization is AGGREGATOR
while the identity type of the product is CENTRALLY_OWNED.)
Access Channel
Web
Possible Causes
The identity model does not match with that of the product preset in the system.
Procedure
Contact the SP to solve the problem.
4.708 IC40517
Description
The identifier value does not comply with the matched identifier rule.
Scenario
This error is reported during identity creation when the identifier value does not comply with
the matched identifier rule.
Access Channel
API, Web
Possible Causes
The identifier value does not comply with the matched identifier rule.

Copyright © Huawei
Mobile Money
Procedure
Check the identifier value in the request.
4.709 IC40518
Description
The identifier value is empty and no identifier rule for generating the identifier is matched.
Scenario
This error is reported during identity creation when the identifier value is empty and no
identifier rule for generating the identifier is matched.
Access Channel
API, Web
Possible Causes
The identifier value is empty and no identifier rule for generating the identifier is matched.
Procedure
Check the identifier value in the request.
4.710 IC40519
Description
The customer status is invalid. The customer is not in Active or Pending Active state.
Scenario
This error is reported when a customer logs in to the App but the customer status is invalid.
Access Channel
Web
Possible Causes
The customer is not in Active or Pending Active state.
Procedure
Contact the Customer Care to change the customer status.

Copyright © Huawei
Mobile Money
4.711 IC40520
Description
The request contains duplicate records of the to-be-added product {0}.
{0} indicates a product ID.
Scenario
This error is reported during customer or organization product modification when the request
contains duplicate product records.
Access Channel
API
Possible Causes
The request contains duplicate records of the to-be-added product {0}.
Procedure
Delete duplicate product records from the request.
4.712 IC40521
Description
The reminder fails to be sent. An organization cannot configure to send a reminder to itself.
Scenario
This error is reported when an organization configures to send a reminder to itself.
Access Channel
Web, USSD, STK
Possible Causes
An organization cannot configure to send a reminder to itself.
Procedure
Enter a correct target identity.

Copyright © Huawei
Mobile Money
4.713 IC40522
Description
An error occurs during process creation.
Scenario
This error is reported when the intersection between the organization mapping in Business
Operations Group associated with the current organization and the organization mapping
defined in the system process.
Access Channel
Web, Web(Bulk), STK, USSD, API
Possible Causes
No organization mapping is available.
Procedure
1. Choose My Functions > Operation Support > Workflow > Workflow Configuration
and query the organization mapping defined in the system process.
2. Choose My Functions > Core Configuration > Advanced Configuration > Business
Operations Group and configure the organization mapping in Business Operations
Group to make it has intersection with the organization mapping defined in the system
process.
4.714 IC40523
Description
Failed to perform the FSI operation.
Scenario
This error code is reported when a customer performs the FSI operation to unlock a fixed
saving account or unlock a target saving account using a handset but the entered FI
organization short code is empty.
Access Channel
STK
Possible Causes
The FI organization short code entered by the customer is incorrect.

Copyright © Huawei
Mobile Money
Procedure
Enter the correct FI organization short code and then perform the FSI operation.
4.715 IC40524
Description
Scenario
saving account or unlock a target saving account using a handset but the entered information
is invalid.
Access Channel
STK
Possible Causes
The information entered by the customer is incorrect.
Procedure
Enter the correct request information and then perform the FSI operation.
4.716 IC40525
Description
Scenario
saving account or unlock a target saving account using a handset but no valid associated FSI
product exists.
Access Channel
STK
Possible Causes
The customer has no associated Kenya Commercial Bank (KCB) FSI product or the
associated FSI product is in Closed state.

Copyright © Huawei
Mobile Money
Procedure
Activate the associated KCB FSI product and then perform the FSI operation.
4.717 IC40526
Description
Scenario
This error is reported when the user name and password for the KCB system of the FI
organization to access the Mobile Money are incorrect.
Access Channel
STK
Possible Causes
The user name and password provided by the external system are incorrect.
Procedure
Enter the correct user name and password.
4.718 IC40527
Description
The password of the operator is not in normal status.
Scenario
This error is reported when the password of the operator is not in normal status.
Access Channel
API, Web
Possible Causes
The password of the operator is not in normal status.
Procedure
Perform the operation as another operator.

Copyright © Huawei
Mobile Money
4.719 IC40540
Description
The initiator must be a customer.
Scenario
This error is reported if the operation of obtaining the start PIN is not initiated by a customer.
Access Channel
USSD
Possible Causes
The initiator must be a customer.
Procedure
Ensure that the initiator is a customer.
4.720 IC40544
Description
The Settlement Number KYC parameter is not set.
Scenario
This error is reported during organization settlement number query if the Settlement Number
KYC parameter is not set.
Access Channel
Web
Possible Causes
The Settlement Number KYC parameter is not set.
Procedure
Choose My Functions > Operational Configuration > System Parameter > Identity
Generic Configuration and set the Settlement Number KYC parameter.

Copyright © Huawei
Mobile Money
4.721 IC40545
Description
At least one of the TillMSISDN and ShortCode parameters must be transferred.
Scenario
This error is reported during organization settlement number query if both the TillMSISDN
and ShortCode parameters are not transferred.
Access Channel
Web
Possible Causes
At least one of the TillMSISDN and ShortCode parameters must be transferred.
Procedure
Send the tc_debug.log file to Huawei engineers for troubleshooting.
4.722 IC40548
Description
Operation failed because the FSI link is already in the Suspended state.
Scenario
This error is reported when the FSI link is in Suspended state and another operator clicks
Suspend.
Access Channel
STK
Possible Causes
The FSI link is already in the Suspended state.
Procedure
Verify that the FSI link is not in the Suspended state.

Copyright © Huawei
Mobile Money
4.723 IC40549
Description
Operation failed because the FSI link is already in the Active state.
Scenario
This error is reported when the FSI link is in Active state and another operator clicks
Reactive.
Access Channel
STK
Possible Causes
The FSI link is already in the Active state.
Procedure
Verify that the FSI link is not in the Active state.
4.724 IC40550
Description
The dormant operation cannot be performed for the identity. The identity has incompleted
transactions.
Scenario
This error is reported when the system scheduled task processes the dormant account of an
identity but the identity has incompleted transactions.
Access Channel
System
Possible Causes
The identity has incompleted transactions.
Procedure
Ensure that the identity does not have incompleted transactions.

Copyright © Huawei
Mobile Money
4.725 IC40551
Description
The format of group code {0} is incorrect.
{0} indicates a group code.
Scenario
This error is reported during group creation if the format of group code is incorrect.
Access Channel
Web, USSD, STK
Possible Causes
The format of group code {0} is incorrect.
Procedure
Enter a group code in the correct format. The format of the group code is configured under the
My Functions > Operational Configuration > System Parameter > Group Parameters >
Validation Rule of Group Code menu.
4.726 IC40552
Description
The group code {0} has been used by a group.
Scenario
This error is reported during group creation if the group code has been used by a group.
Access Channel
Web, USSD, STK
Possible Causes
The group code {0} has been used by a group.

Copyright © Huawei
Mobile Money
Procedure
Enter a group code that is not in use.
4.727 IC40553
Description
The group name cannot be empty.
Scenario
This error is reported during group creation if the group name is empty.
Access Channel
Web, USSD, STK
Possible Causes
The group name cannot be empty.
Procedure
Enter a group name.
4.728 IC40554
Description
The format of group name {0} is incorrect.
{0} indicates a group name.
Scenario
This error is reported during group creation if the format of group name is incorrect.
Access Channel
Web, USSD, STK
Possible Causes
The format of group name {0} is incorrect.

Copyright © Huawei
Mobile Money
Procedure
Enter a group name in the correct format.
4.729 IC40555
Description
The number of groups to which the customer belongs exceeds the upper limit {0} configured
at the system level.
{0} indicates the maximum number of groups that a customer belongs to.
Scenario
This error is reported during group creation if the number of groups to which the customer
belongs has exceeded the maximum.
Access Channel
Web, USSD, STK
Possible Causes
The number of groups to which the customer belongs exceeds the upper limit {0} configured
at the system level.
Procedure
Do not add the customer to the group.
4.730 IC40556
Description
Only one product can be subscribed when a group is created.
Scenario
This error is reported during group creation if only one product can be subscribed.
Access Channel
Web, USSD, STK
Possible Causes
Only one product can be subscribed when a group is created.

Copyright © Huawei
Mobile Money
Procedure
Subscribe to a product.
4.731 IC40557
Description
The customer creates the group is not a registered customer.
Scenario
This error is reported during group creation if the customer creates the group is not a
Access Channel
Web, USSD, STK
Possible Causes
The customer creates the group is not a registered customer.
Procedure
Ensure that the customer creates the group is a registered customer.
4.732 IC40561
Description
The to-be-reviewed order ID does not exist.
Scenario
This error is reported during group transaction reviewing if the entered to-be-reviewed order
ID does not exist.
Access Channel
Web
Possible Causes
The to-be-reviewed order ID does not exist.
Procedure
Enter a correct order ID.

Copyright © Huawei
Mobile Money
4.733 IC40562
Description
The customer does not belong to the group reviewer.
Scenario
This error is reported during group transaction reviewing if the entered customer does not
belong to the group reviewer.
Access Channel
Web
Possible Causes
The customer does not belong to the group reviewer.
Procedure
Enter a correct approver MSISDN.
4.734 IC40563
Description
The to-be-reviewed transaction has expired.
Scenario
This error is reported during group transaction reviewing if the to-be-reviewed transaction has
expired.
Access Channel
Web
Possible Causes
The to-be-reviewed transaction has expired.
Procedure
Check the to-be-reviewed transaction.

Copyright © Huawei
Mobile Money
4.735 IC40564
Description
A reviewer can review a transaction once only.
Scenario
This error is reported during group transaction reviewing if the reviewer reviews the
transaction repeatedly.
Access Channel
Web
Possible Causes
A reviewer cannot review a transaction repeatedly.
Procedure
Check the to-be-reviewed transaction.
4.736 IC40565
Description
The entered group code is invalid.
Scenario
This error is reported during group transaction reviewing if the entered group code is invalid.
Access Channel
Web
Possible Causes
Procedure
Enter a correct group code.

Copyright © Huawei
Mobile Money
4.737 IC40566
Description
The entered customer is the initiator of the original transaction or BO.
Scenario
This error is reported during group transaction reviewing if the entered customer is the
initiator of the original transaction or BO.
Access Channel
Web
Possible Causes
The entered customer is the initiator of the original transaction or BO.
Procedure
4.738 IC40567
Description
The customer reviewing the transaction cannot be the credit party of the original group
transaction.
Scenario
This error is reported during group transaction reviewing if the entered customer is the credit
party of the original transaction.
Access Channel
Web
Possible Causes
The customer reviewing the transaction cannot be the credit party of the original group
transaction.
Procedure

Copyright © Huawei
Mobile Money
4.739 IC40568
Description
Both the Transaction Type and Action Type fields are empty, leading to the generation
failure of the group reviewing task.
Scenario
This error is reported if the Transaction Type and Action Type fields are both empty.
Access Channel
WEB, STK, USSD, API
Possible Causes
The Transaction Type and Action Type fields cannot be both empty.
Procedure
Transfer Transaction Type for transactions or action-type services and transfer Action Type
for BO-type services.
4.740 IC40569
Description
The transferred Transaction Type field does not exist, leading to the generation failure of the
group reviewing task.
Scenario
This error is reported when the transferred Transaction Type field does not exist.
Access Channel
WEB, STK, USSD, API
Possible Causes
The transferred Transaction Type field does not exist.
Procedure
Transfer a transaction type that exists in the system and is in the released state.

Copyright © Huawei
Mobile Money
4.741 IC40570
Description
The transferred Action Type field does not exist, leading to the generation failure of the group
reviewing task.
Scenario
This error is reported when the transferred Action Type field does not exist.
Access Channel
WEB, STK, USSD, API
Possible Causes
The transferred Action Type field does not exist.
Procedure
Transfer a action type that exists in the system and is in the released state.
4.742 IC40571
Description
The transferred information about the initiator of the original transaction is incorrect, leading
to the generation failure of the group reviewing task.
Scenario
This error is reported if the initiator of the original transaction does not exist.
Access Channel
WEB, STK, USSD, API
Possible Causes
The transferred information about the initiator of the original transaction is incorrect.
Procedure
Ensure that the transferred information about the initiator of the original transaction is correct.

Copyright © Huawei
Mobile Money
4.743 IC40572
Description
The transferred information about the credit party of the original transaction is incorrect,
leading to the generation failure of the group reviewing task.
Scenario
This error is reported if the credit party of the original transaction does not exist.
Access Channel
WEB, STK, USSD, API
Possible Causes
The transferred information about the credit party of the original transaction is incorrect.
Procedure
Ensure that the transferred information about the credit party of the original transaction is
correct.
4.744 IC40573
Description
The group member role information is empty, leading to the generation failure of the group
reviewing task.
Scenario
This error is reported if the group member role information fails to be obtained.
Access Channel
WEB, STK, USSD, API
Possible Causes
The group member role information is empty.
Procedure
Log in to the SP portal, choose My Functions > Core Configuration > Advanced
Configuration > Product, and configure group member roles.

Copyright © Huawei
Mobile Money
4.745 IC40574
Description
The number of reviewers is less than the minimum, leading to the generation failure of the
group reviewing task.
Scenario
This error is reported if the number of reviewers is less than the minimum.
Access Channel
WEB, STK, USSD, API
Possible Causes
The number of reviewers is less than the minimum. The current service requires at least {0}
reviewers.
{0} indicates the mininum number of reviewers.
Procedure
Log in to the SP portal, choose My Functions > Core Configuration > Advanced
Configuration > Product, and modify the Approve Num Required parameter.
4.746 IC40575
Description
The invited customer is a group member in Invited state and is valid.
Scenario
This error is reported during group member adding if the invited customer has already been
invited and the customer is a group member in Invited state and is valid.
Access Channel
WEB, STK, USSD
Possible Causes
The invited customer is a group member in Invited state and is valid.

Copyright © Huawei
Mobile Money
Procedure
Do not invite a customer who is already in the group, in Invited state, and in the validity
period.
4.747 IC40576
Description
Both the role name and role ID are empty.
Scenario
This error is reported during group member adding if the role name and role ID transferred to
the BCS are both empty.
Access Channel
WEB, STK, USSD
Possible Causes
Both the role name and role ID are empty.
Procedure
Ensure that at least one of the role name and role ID is not empty.
4.748 IC40577
Description
The role does not exist or the group does not support the role.
Scenario
This error is reported during group member adding if no role is found based on the entered
role ID or role name.
Access Channel
WEB, STK, USSD
Possible Causes
No role is found based on the entered role ID or role name.

Copyright © Huawei
Mobile Money
Procedure
Assign proper permission to the invited customer.
4.749 IC40578
Description
The group does not exist or is not in Active state.
Scenario
This error is reported if an invited customer confirms to join a group that does not exist or is
not in Active state.
Access Channel
USSD, STK
Possible Causes
The group does not exist or is not in Active state.
Procedure
Ensure that the group exists and is in Active state.
4.750 IC40580
Description
The invitation has expired.
Scenario
This error is reported if an invited customer confirms to join a group but the invitation has
expired.
Access Channel
USSD, STK
Possible Causes
The invitation has expired.
Procedure
Ensure that the invitation is valid.

Copyright © Huawei
Mobile Money
4.751 IC40581
Description
The number of roles having the role has exceeded the maximum.
Scenario
This error is reported if an invited customer confirms to join a group but the number of group
members having the role has exceeded the maximum.
Access Channel
USSD, STK
Possible Causes
The number of roles having the role has exceeded the maximum.
Procedure
Ensure that the number of roles having the role has not exceeded the maximum.
4.752 IC40582
Description
The operation object remains unchanged before and after the operation.
Scenario
This error is reported if the operation is invalid. For example, the role to be added is the same
as the role to be deleted during group member role modification.
Access Channel
Web, API, STK, USSD
Possible Causes
Invalid operation.
Procedure
Set parameters properly and perform the operation again.

Copyright © Huawei
Mobile Money
4.753 IC40583
Description
The entered role is not a valid role in the system.
Scenario
This error is reported during group member role modification if the entered role is invalid.
Access Channel
Web, API, STK, USSD
Possible Causes
The entered role is invalid.
Procedure
Change the role to be added and the role to be deleted.
4.754 IC40584
Description
The group role does not belong to the current group.
Scenario
This error is reported during group member role modification if the group role does not
belong to the current group.
Access Channel
Web, API, STK, USSD
Possible Causes
The group role does not belong to the current group.
Procedure
Check and modify the entered group code and customer MSISDN.

Copyright © Huawei
Mobile Money
4.755 IC40585
Description
The group member already has the role to be added. Modification failed.
Scenario
This error is reported during group member role modification if the group member already
has the role to be added.
Access Channel
Web, API, STK, USSD
Possible Causes
The group member already has the role to be added.
Procedure
Change the role to be added.
4.756 IC40586
Description
The group member does not have the role to be deleted. Modification failed.
Scenario
This error is reported during group member role modification if the group member does not
have the role to be deleted.
Access Channel
Web, API, STK, USSD
Possible Causes
The group member does not have the role to be deleted.
Procedure

Copyright © Huawei
Mobile Money
4.757 IC40587
Description
The modified group member must have at least one role. Role modification failed.
Scenario
This error is reported during group member role modification if the modified group member
does not have role.
Access Channel
Web, API, STK, USSD
Possible Causes
The modified group member must have at least one role.
Procedure
4.758 IC40588
Description
The customer (initiator, requester, or the recharge party) has not been invited to join the group
or the customer has been invited but has not confirmed the invitation.
Scenario
This error is reported during group member management if the customer has not been invited
to join the group or the customer has been invited but has not confirmed the invitation.
Access Channel
Web, API, STK, USSD
Possible Causes
The current customer is not an official member of the group.
Procedure
Ensure that the customer is an official member of the group.

Copyright © Huawei
Mobile Money
4.759 IC40589
Description
The group member (initiator or requester) does not have the operation permission.
Scenario
This error is reported during group member removal if the group member does not have the
operation permission.
Access Channel
Web, API, STK, USSD
Possible Causes
The group member does not have the operation permission.
Procedure
Assign the operation permission to the group member.
4.760 IC40590
Description
The status of the group member (initiator, requester, or recharge party) does not support the
operation.
Scenario
This error is reported if the status of the group member does not support the operation in the
scenarios of adding the group member, removing the group member, and changing the group
member role..
Access Channel
Web, API, STK, USSD
Possible Causes
The status of the group member does not support the operation.
Procedure
Check the group member status required for the operation and ensure that the group member
is in valid status.

Copyright © Huawei
Mobile Money
4.761 IC40591
Description
The group does not exist.
Scenario
This error is reported during group member removal if the group does not exist.
Access Channel
Web, API, STK, USSD
Possible Causes
The group does not exist.
Procedure
Create the group first.
4.762 IC40592
Description
A group member cannot perform some operations on itself, such as removing itself from the
group or changing its role.
Scenario
This error is reported during group member removal if the group member performs the
operation on itself.
Access Channel
Web, API, STK, USSD
Possible Causes
The group member cannot perform the operation on itself.
Procedure
Perform the operation on the group member as another group member with the permission.

Copyright © Huawei
Mobile Money
4.763 IC40593
Description
The birthday of the group member is incorrect.
Scenario
This error is reported during group member removal if the birthday of the group member is
incorrect.
Access Channel
Web, API, STK, USSD
Possible Causes
The birthday of the group member is incorrect.
Procedure
Enter the correct birthday of the group member.
4.764 IC40596
Description
The group member does not have the permission or does not belong to the specified group.
Scenario
This error is reported when group member does not have the permission to use service in all
BO actions that require group member permission authentication.
Access Channel
Web, API, STK, USSD
Possible Causes
Group member {0} does not have the permission to use service {1}.
{0}: indicates the name of a group member.

{1}: indicates the name of a service.
Procedure
Ensure that the group member has the permission.

Copyright © Huawei
Mobile Money
4.765 IC40597
Description
The MSISDN or order ID is incorrect. The queried review details do not exist.
Scenario
This error is reported if no review details are found based on the MSISDN of the initiator and
order ID.
Access Channel
Web, API, STK, USSD
Possible Causes
The MSISDN or order ID is incorrect.
Procedure
Ensure that the MSISDN and order ID are correct.
4.766 IC40598
Description
The entered operation type is incorrect.
Scenario
This error is reported during group transaction reviewing if the entered operation type is
incorrect.
Access Channel
STK, USSD
Possible Causes
The entered operation type is incorrect.
Procedure
Enter a correct operation type.

Copyright © Huawei
Mobile Money
4.767 IC40599
Description
The invited customer is a group member in Confirmed state.
Scenario
This error is reported during group member adding if the invited customer has already been
invited and the customer is a group member in Confirmed state.
Access Channel
WEB, STK, USSD
Possible Causes
The invited customer is a group member in Confirmed state.
Procedure
Do not invite a customer who is already in the group and in the Confirmed state.
4.768 IC40600
Description
Scenario
This error is reported when a customer reviews a transaction or the BO service but the entered
group code is incorrect.
Access Channel
USSD, STK
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
4.769 IC40601
Description
No member in the group has the role.
Scenario
This error is reported during batch notification sending if no valid data is obtained.
Access Channel
Web, API, STK, USSD
Possible Causes
No valid data is obtained.
Procedure
Select a role that a member in the group has.
4.770 IC40602
Description
When a customer confirms to join a group, the customer must be in the Invited state in the
group.
Scenario
This error is reported when a customer confirms to join a group but the customer is not invited
or the invitation has not been approved.
Access Channel
USSD, STK
Possible Causes
The customer is not invited or the invitation is being reviewed.
Procedure
Ensure that the customer has been invited and the invitation has been approved.

Copyright © Huawei
Mobile Money
4.771 IC40603
Description
The group name fails to be modified.
Scenario
This error is reported during group name modification if the new and old group names are the
same.
Access Channel
Web, USSD, STK
Possible Causes
The new and old group names are the same.
Procedure
Ensure that the new group name is different from the old group name.
4.772 IC40604
Description
The group description fails to be modified.
Scenario
This error is reported during group description modification if the new and old group
descriptions are the same.
Access Channel
Web, USSD, STK
Possible Causes
The new and old group descriptions are the same.
Procedure
Ensure that the new group description is different from the old group description.

Copyright © Huawei
Mobile Money
4.773 IC40608
Description
The Auto Sweep Mode field is not set in the KYC of the bank.
Scenario
This error is reported during organization revenue settlement if Auto Sweep Mode is not set in
the KYC of the bank.
Access Channel
Web, USSD, API, APP, BIO, Third Party Web
Possible Causes
The Auto Sweep Mode field is not set in the KYC of the bank.
Procedure
Choose Search > Bank > Info and set Auto Sweep Mode.
4.774 IC40609
Description
Organization {0} does not have an upper-level organization.
{0} indicates an organization short code.
Scenario
This error is reported during organization revenue settlement if the current organization does
not have an upper-level organization.
Access Channel
Possible Causes
Organization {0} does not have an upper-level organization.
Procedure
Select another child organization to perform the sweep-in and sweep-out operations.

Copyright © Huawei
Mobile Money
4.775 IC40610
Description
Organization {0} cannot be in Closed or Frozen state.
{0} indicates an organization short code.
Scenario
This error is reported during organization revenue settlement if the current organization is in
Closed or Frozen state.
Access Channel
Possible Causes
Organization {0} cannot be in Closed or Frozen state.
Procedure
Select an organization in normal state for organization revenue settlement.
4.776 IC40611
Description
Loyalty points fail to be queried.
Scenario
This error is reported when a customer initiates a request to query loyalty points through the
API channel but the receiver is other identities.
Access Channel
API
Possible Causes
The customer does not have the permission to query loyalty points of other identities.
Procedure
Ensure that the receiver information is correct.

Copyright © Huawei
Mobile Money
4.777 IC40612
Description
The selected service {0} is invalid. The credit party of the transaction type corresponding to
the service must be an organization. The debit party of the transaction type corresponding to
the service must be an organziation or a customer.
{0} indicates a service alias. For example,Buy Airtime_VDF_Demo.
Scenario
This error is reported during bulk task plan creation when Bulk Type is set to Bulk
Transaction Reminder Schedule, the transaction type corresponding to the service is incorrect,
and the task is submitted.
Access Channel
Web(Bulk)
Possible Causes
The selected service {0} is invalid. The credit party of the transaction type corresponding to
the service must be an organization. The debit party of the transaction type corresponding to
the service must be an organziation or a customer.
Procedure
Ensure that the credit and debit parties of the transaction type corresponding to service {0}
are correct.
4.778 IC40613
Description
{0} customer cannot be invited to join the group.
{0} indicates a customer type, such as Unseen, Unregistered, Lite.
Scenario
This error is reported if the type of the customer invited by an operator or another customer to
join the group is not supported.
Access Channel
POS

Copyright © Huawei
Mobile Money
Possible Causes
{0} customer cannot be invited to join the group.
Procedure
Upgrade the customer to ensure that the customer can be invited to join the group.
4.779 IC40619
Description
The certificate number cannot belong to different natural person.
Scenario
This error is reported when an operator creates an identity but the entered certificate number
belongs to different natural person.
Access Channel
POS
Possible Causes
The certificate number cannot belong to different natural person.
Procedure
Ensure that the entered certificate number is correct.
4.780 IC40621
Description
The sweep-in record {0} does not exist or is not in WAITING BANK TRANSFER state.
{0} indicates the sweep-in record ID.
Scenario
This error is reported during organization revenue settlement if the sweep-in record does not
exist or is not in WAITING BANK TRANSFER state.
Access Channel

Copyright © Huawei
Mobile Money
Possible Causes
The sweep-in record {0} does not exist or is not in WAITING BANK TRANSFER state.
Procedure
Select a sweep-in record in WAITING BANK TRANSFER state.
4.781 IC40625
Description
The natural person is in {0} state and the operation is not supported.
{0}: indicates the natural person status. The options include pending approve and approved.
Scenario
This error is reported if the natural person status does not support the operation.
Access Channel
POS
Possible Causes
The natural person is in {0} state and the operation is not supported.
Procedure
Ensure that the natural person status is correct.
4.782 IC40626
Description
KYC fields of a natural person in Approved state cannot be modified.
Scenario
This error is reported when an operator creates an identity and KYC fields of a natural person
in Approved state are modified.
Access Channel
POS

Copyright © Huawei
Mobile Money
Possible Causes
When an identity is created, KYC fields of a natural person in Approved state cannot be
modified.
Procedure
Verify that whether the entered KYC fields of the natural person are the same as existing
KYC fields of the natural person.
4.783 IC40627
Description
When an identity is created, only one ID can be entered for the natural person.
Scenario
This error is reported when an operator creates an identity and the natural person has multiple
IDs.
Access Channel
POS
Possible Causes
When an identity is created, only one ID can be entered for the natural person.
Procedure
Ensure that only one ID is specified in the ID Details parameter.
4.784 IC40628
Description
The third-party FS system response times out and the transaction fails.
Scenario
This error is reported when a timeout occurs during group FSI activation.
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
The third-party FS system response times out.
Procedure
Ensure the connection to the third-party system is correct.
4.785 IC40629
Description
Group Name is left empty and groups fail to be created.
Scenario
This error is reported during bulk group creation if Group Name is empty.
Access Channel
Web, API
Possible Causes
Group Name is left empty.
Procedure
Ensure that Group Name is not empty.
4.786 IC40630
Description
The group identity initiating the FSI activation request is in an invalid state, for example,
FROZEN.
Scenario
This error is reported when the group identity initiating the FSI activation request is in an
invalid state.
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
The group identity initiating the FSI activation request is in an invalid state, for example,
FROZEN.
Procedure
Ensure that the identity is in a valid state.
4.787 IC40631
Description
A deleted ID blacklist record cannot be deleted again.
Scenario
This error is reported in the following scenario: operators 1 and 2 log in to the system, choose
the same menu, find the same record on which they have the delete permission, operator 1
deletes the record, and operator 2 deletes the record again.
Access Channel
Web
Possible Causes
A deleted ID blacklist record cannot be deleted again.
Procedure
Ensure that the record exists in the ID blacklist and is not deleted.
4.788 IC40632
Description
The FSI product fails to be activated by the group. The Core Product has been activated or the
customer already has a link between the Core Product and the organization.
Scenario
This error is reported if the FSI product to be activated by the group has already been
activated.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The Core Product has been activated or the group already has a link between the Core Product
and the organization.
Procedure
Activate another provision product.
4.789 IC40635
Description
The modified ID Type and ID Number conflict with those of other persons. Modification
failed.
Scenario
This error is reported during Person KYC modification if the modified ID Type and ID
Number conflict with those of other persons.
Access Channel
Web, API
Possible Causes
The modified ID Type and ID Number conflict with those of other persons.
Procedure
Enter a correct ID number and initiate the operation again.
4.790 IC40636
Description
The person to be modified does not exist. Modification failed.
Scenario
This error is reported during Person KYC modification if the person to be modified does not
exist.
Access Channel
Web, API

Copyright © Huawei
Mobile Money
Possible Causes
The person to be modified does not exist.
Procedure
Enter correct person information.
4.791 IC40637
Description
Failed to create the bank account associated to the identity.
Scenario
This error is reported when a bank account associated to an identity is created but the bank
account already exists in the identity.
Access Channel
Web, USSD, API
Possible Causes
The bank account already exists in the identity.
Procedure
4.792 IC40638
Description
Scenario
This error is reported when a bank account associated to an identity is created but the bank
account already exists in another identity.
Access Channel
Web, USSD, API
Possible Causes
The bank account already exists in another identity.

Copyright © Huawei
Mobile Money
Procedure
4.793 IC40639
Description
Scenario
This error is reported when a bank account associated to an identity is created but the number
of bank accounts associated to the identity has reached the maximum.
Access Channel
Web, USSD, API
Possible Causes
The number of bank accounts associated to the identity has reached the maximum.
Procedure
Do not associate other bank accounts to the identity.
4.794 IC40640
Description
Failed to configure the default bank account for the identity.
Scenario
This error is reported when the default bank account is configured for an identity but the bank
account is already the default one.
Access Channel
Web, USSD, API
Possible Causes
The bank account is already the default one.
Procedure
Do not configure the default bank account repeatedly.

Copyright © Huawei
Mobile Money
4.795 IC40641
Description
Failed to delete the bank account associated to the identity.
Scenario
This error is reported when a bank account associated to an identity is deleted but the bank
account has to-be-processed transactions.
Access Channel
Web, USSD, API
Possible Causes
The bank account has to-be-processed transactions.
Procedure
Do not delete the bank account.
4.796 IC40642
Description
Transaction {0} has been completely reversed and the dispute cannot be initiated.
{0} indicates a transaction ID.
Scenario
This error is reported when a dispute task is initiated but the transaction has been completely
reversed.
Access Channel
Web, API
Possible Causes
Transaction {0} has been completely reversed and the dispute cannot be initiated.
Procedure
Do not initiate the dispute for the transaction whose ID is {0}.

Copyright © Huawei
Mobile Money
4.797 IC40643
Description
Transaction {0} has not been completed and the dispute cannot be initiated.
Scenario
This error is reported when a dispute task is initiated but the transaction has not been
completed.
Access Channel
Web, API
Possible Causes
Transaction {0} has not been completed and the dispute cannot be initiated.
Procedure
4.798 IC40644
Description
Transaction {0} does not support reversal and the dispute cannot be initiated.
Scenario
This error is reported when a dispute task is initiated but the transaction does not support
reversal.
Access Channel
Web, API
Possible Causes
Transaction {0} does not support reversal and the dispute cannot be initiated.

Copyright © Huawei
Mobile Money
Procedure
4.799 IC40645
Description
The transaction type of transaction {0} does not exist and the dispute cannot be initiated.
Scenario
This error is reported when a dispute task is initiated but the transaction type does not exist.
Access Channel
Web, API
Possible Causes
The transaction type of transaction {0} does not exist and the dispute cannot be initiated.
Procedure
4.800 IC40646
Description
Transaction {0} is already in dispute state and the dispute cannot be initiated.
Scenario
This error is reported when a dispute task is initiated but the transaction is already in dispute
state.
Access Channel
Web, API

Copyright © Huawei
Mobile Money
Possible Causes
Transaction {0} is already in dispute state.
Procedure
4.801 IC40647
Description
Transaction {0} has been reversed (partially or completely) and the dispute cannot be
initiated.
Scenario
This error is reported when a dispute task is initiated but the transaction has been reversed
(partially or completely).
Access Channel
Web, API
Possible Causes
Transaction {0} has been reversed (partially or completely) and the dispute cannot be
initiated.
Procedure
4.802 IC40648
Description
Failed to initiate the dispute. Only SP operators can initiate disputes.
Scenario
This error is reported when a dispute task is initiated but the dispute is not initiated by an SP
operator.

Copyright © Huawei
Mobile Money
Access Channel
Web, API
Possible Causes
The dispute is not initiated by an SP operator.
Procedure
Ask an SP operator to initiate the dispute task.
4.803 IC40649
Description
The identity does not have the subscription permission.
Scenario
This error is reported when an identity without the subscription permission queries
subscribeable bundles.
Access Channel
STK, USSD
Possible Causes
When an identity queries subscribeable bundles, no bundle is assigned to the identity type on
the bundle configuration page or the related bundle is not configured at the trust level of the
identity.
Procedure
Configure the bundle correctly and retry.
4.804 IC40650
Description
The bundle is invalid.
Scenario
This error is reported when an identity subscribes to a bundle, the entered bundle ID does not
exist or has not taken effect.

Copyright © Huawei
Mobile Money
Access Channel
STK, USSD
Possible Causes
When an identity subscribes to a bundle, the entered bundle ID does not exist or has not taken
effect.
Procedure
Ensure that the bundle ID is correct and the bundle is valid.
4.805 IC40651
Description
The subscription is cancelled by the third-party system.
Scenario
This error is reported when an identity sends a request to the third-party system during
external or hybrid bundle subscrption but the third-party system returns a failure or timeout
response.
Access Channel
STK, USSD
Possible Causes
When subscribing to an external or hybrid bundle, the identity fails to send the request to the
third-party system or the third-party system returns a failure or timeout response.
Procedure
Check the external communication link and initiate the subscription again.
4.806 IC40652
Description
The effective date and expiration date of the subscribed bundle must be in the effective date
range and expiration date range configured for the bundle.
Scenario
This error is reported when the validity period entered when an indentity subscribes to a
bundle is not in the range configured for the bundle.

Copyright © Huawei
Mobile Money
Access Channel
STK, USSD
Possible Causes
The validity period entered when an indentity subscribes to a bundle is not in the range
configured for the bundle.
Procedure
Enter a correct validity period.
4.807 IC40653
Description
When an organization is migrated, the new parent organization does not exist.
Scenario
This error is reported when an organization is migrated but the new parent organization does
not exist.
Access Channel
Web
Possible Causes
When an organization is migrated, the new parent organization does not exist.
Procedure
4.808 IC40654
Description
When an organization is migrated, the organization has child organizations and the charge
distribution model cannot be modified.
Scenario
This error is reported when an organization is migrated but the organization has child
organizations and the charge distribution model is modified.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
When an organization is migrated, the organization has child organizations and the charge
distribution model cannot be modified.
Procedure
Do not modify the Charge Distribution Model, or remove the child organizations of the
organization and try again.
4.809 IC40655
Description
When an organization is migrated, the organization has child organizations and the identity
model of the organization cannot be modified.
Scenario
This error is reported when an organization is migrated but the organization has child
organizations and the identity model of the organization is modified.
Access Channel
Web
Possible Causes
When an organization is migrated, the organization has child organizations and the identity
model of the organization cannot be modified.
Procedure
Modify the newly allocated product and do not change the identity model.
4.810 IC40656
Description
When an organization is migrated, the identity model in the newly allocated product conflicts
with the existing one.

Copyright © Huawei
Mobile Money
Scenario
This error is reported when an organization is migrated but the identity model in the newly
allocated product conflicts with the existing one.
Access Channel
Web
Possible Causes
When an organization is migrated, the identity model in the newly allocated product conflicts
with the existing one.
Procedure
Check the identity model defined in the newly allocated product and ensure that it is
compatible with the existing one.
4.811 IC40657
Description
When an organization is migrated, the new identity model of the organization is incompatible
with the identity model of the new parent organization.
Scenario
This error is reported when an organization is migrated but the new identity model of the
organization is incompatible with the identity model of the new parent organization.
Access Channel
Web
Possible Causes
When an organization is migrated, the new identity model of the organization is incompatible
with the identity model of the new parent organization.
Procedure
Check the identity model defined in the newly allocated product and ensure that it is
compatible with the identity model of the new parent organization.

Copyright © Huawei
Mobile Money
4.812 IC40658
Description
When an organization is migrated, the shared account needs to be adjusted (added or closed)
because the accounting model changes. The balance of the to-be-closed shared account {1} of
the to-be-migrated organization {0} is not zero.

{1} indicates an account type alias.
Scenario
This error is reported when an organization is migrated, the shared account needs to be
adjusted (added or closed) because the accounting model changes. The balance of the to-be-
closed shared account of the to-be-migrated organization is not zero.
Access Channel
Web
Possible Causes
When an organization is migrated, the shared account needs to be adjusted (added or closed)
because the accounting model changes. The balance of the to-be-closed shared account {1} of
the to-be-migrated organization {0} is not zero.
Procedure
Ensure that the balance of the to-be-closed shared account {1} of the to-be-migrated
organization {0} is zero.
4.813 IC40659
Description
When an organization is migrated, the commission roll-up reason type fails to be queried.
Scenario
This error is reported when an organization is migrated but the commission roll-up reason
type fails to be queried.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
When an organization is migrated, the commission roll-up reason type fails to be queried.
Procedure
Configure the commission roll-up reason type.
4.814 IC40660
Description
When an organization is migrated, the balance of the commission account {1} of the to-be-
migrated organization {0} is not zero.

{1} indicates an account type alias.
Scenario
This error is reported when an organization is migrated but the balance of the commission
account of the to-be-migrated organization is not zero.
Access Channel
Web
Possible Causes
When an organization is migrated, the balance of the commission account {1} of the to-be-
migrated organization {0} is not zero.
Procedure
Ensure that the balance of the commission account {1} of the to-be-migrated organization {0}
is zero.
4.815 IC40661
Description
When an organization is migrated, the short code of the new parent organization is different
from that of the original parent organization.
Scenario
This error is reported when an organization is migrated but the short code of the new parent
organization is different from that of the original parent organization.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
When an organization is migrated, the short code of the new parent organization is different
from that of the original parent organization.
Procedure
Ensure that the new parent organization information is correct.
4.816 IC40662
Description
When an organization is migrated, the organization and its child organization have
uncompleted commission roll-up tasks.
Scenario
This error is reported when an organization is migrated but the organization and its child
organization have uncompleted commission roll-up tasks.
Access Channel
Web
Possible Causes
When an organization is migrated, the organization and its child organization have
uncompleted commission roll-up tasks.
Procedure
Migrate the organization after the commission roll-up tasks are completed.
4.817 IC40663
Description
When an organization is migrated, the organization and its child organizations have
uncompleted commission claw-back tasks.
Scenario
This error is reported when an organization is migrated but the organization and its child
organizations have uncompleted commission claw-back tasks.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
When an organization is migrated, the organization and its child organizations have
uncompleted commission claw-back tasks.
Procedure
Migrate the organization after the commission claw-back tasks are completed.
4.818 IC40664
Description
The to-be-migrated organization is a top organization, its identity model is MIXED or NON-
HIERLAKEY, and no new identity model is configured through the newly allocated product.
Therefore, the new identity model of the organization cannot be determined and the
organization cannot be migrated.
Scenario
This error is reported when the to-be-migrated organization is a top organization, its identity
model is MIXED or NON-HIERLAKEY, and no new identity model is configured through
the newly allocated product.
Access Channel
Web
Possible Causes
The to-be-migrated organization is a top organization, its identity model is MIXED or NON-
HIERLAKEY, and no new identity model is configured through the newly allocated product.
Therefore, the new identity model of the organization cannot be determined and the
organization cannot be migrated.
Procedure
Allocate a new product to determine the new identity model.
4.819 IC40665
Description
The voucher type {0} must be of the Other voucher type.

Copyright © Huawei
Mobile Money
{0} indicates a voucher type alias.
Scenario
This error is reported when a voucher is canceled but the voucher type is incorrect.
Access Channel
Web, STK, USSD, API
Possible Causes
The voucher type {0} must be of the Other voucher type.
Procedure
Ensure that the voucher type is correctly set.
4.820 IC40666
Description
Failed to change the identity status.
Scenario
This error is reported during identity status change if the identity has uncompleted
transactions.
Access Channel
Web
Possible Causes
The identity has uncompleted transactions.
Procedure
Complete the online or offline e-money withdrawal transaction of the identity and then
change the status of the identity.

Copyright © Huawei
Mobile Money
4.821 IC40667
Description
Failed to execute the fund dispute task. The balance of account {0} of the identity is
insufficient.
{0} indicates a value in account name/account ID format.
Scenario
This error is reported when a fund dispute task is completed but the system detects that the
account balance of the original transaction credit party is less than the amount of the to-be-
reversed transaction.
Access Channel
Web, API
Possible Causes
The balance of account {0} of the identity is insufficient and the disputed fund cannot be
reversed.
Procedure
Verify that the balance is sufficient for the current transaction. If the balance is insufficient,
recharge before performing the transaction.
4.822 IC50001
Description
The value of the MandateStatus parameter is incorrect.
Scenario
This error is reported during direct debit mandate query if the value of the MandateStatus
parameter is incorrect.
Access Channel
STK, USSD, API
Possible Causes
The value of the MandateStatus parameter is incorrect.

Copyright © Huawei
Mobile Money
Procedure
Correct the value of the MandateStatus parameter.
4.823 IC50002
Description
The value {0} of the NeedConfirmation parameter is incorrect.
{0}: Value of the NeedConfirmation parameter.
Scenario
This error is reported during standing order schedule query if the value of the
NeedConfirmation parameter is invalid.
Access Channel
STK, USSD, API
Possible Causes
The value of the NeedConfirmation parameter is incorrect.
Procedure
Correct the value of the NeedConfirmation parameter.
4.824 IC50003
Description
The exchange rate file fails to be processed because the file content or format is incorrect.
Scenario
This error is reported during exchange rate file import if the file fails to be processed because
the file content or format is incorrect.
Access Channel
Web
Possible Causes
The content or format of the imported exchange rate file is incorrect.

Copyright © Huawei
Mobile Money
Procedure
View the file import history and troubleshoot the fault.
4.825 IC50004
Description
The mandate does not exist.
Scenario
This error is reported when the direct debit mandate to be activated, queried, or deleted cannot
be found based on the mandate ID.
Access Channel
Possible Causes
The direct debit mandate to be activated, queried, or deleted cannot be found based on the
mandate ID.
Procedure
Check whether the mandate ID is correct.
4.826 IC50005
Description
The mandate is not in pending active state.
Scenario
This error is reported when the direct debit mandate to be activated is not in pending active
state.
Access Channel
Possible Causes
The direct debit mandate to be activated is not in pending active state.

Copyright © Huawei
Mobile Money
Procedure
Ensure that the mandate is in pending active state.
4.827 IC50006
Description
The mandate is not in pending approve state.
Scenario
This error is reported when the direct debit mandate to be activated is not in pending approve
state.
Access Channel
Possible Causes
The direct debit mandate to be activated is not in pending approve state.
Procedure
Ensure that the mandate is in pending approve state.
4.828 IC50007
Description
The mandate is not in pending active or active state.
Scenario
This error is reported when the direct debit mandate to be canceled is not in pending active or
active state.
Access Channel
Possible Causes
The direct debit mandate to be canceled is not in pending active or active state.
Procedure
Ensure that the mandate is in pending active or active state.

Copyright © Huawei
Mobile Money
4.829 IC50008
Description
The mandate is not in cancelled state.
Scenario
This error is reported when the direct debit mandate to be re-activated is not in cancelled state.
Access Channel
Possible Causes
The mandate to be re-activated is not in cancelled state.
Procedure
Ensure that the mandate is in cancelled state.
4.830 IC50009
Description
The payer does not exist.
Scenario
This error is reported when a direct debit mandate is created but the corresponding payer does
not exist.
Access Channel
Possible Causes
The payer does not exist when a direct debit mandate is created.
Procedure
Ensure that the payer exists and is correct.

Copyright © Huawei
Mobile Money
4.831 IC50010
Description
The payee does not exist.
Scenario
This error is reported when a direct debit mandate is created but the corresponding payee does
not exist.
Access Channel
Possible Causes
The payee does not exist when a direct debit mandate is created.
Procedure
Ensure that the payee exists and is correct.
4.832 IC50011
Description
The exchange rate file fails to be imported because the file path cannot be created.
Scenario
This error is reported during exchange rate file import if the file fails to be processed because
the file path cannot be created.
Access Channel
Web
Possible Causes
The file path cannot be created.
Procedure
Ensure that you have the permission on the file system and that the file system has sufficient
space.

Copyright © Huawei
Mobile Money
4.833 IC50012
Description
The mandate corresponding to the payer reference number already exists and cannot be
created again.
Scenario
This error is reported during direct debit mandate creation if the mandate corresponding to the
entered payer reference number already exists.
Access Channel
Possible Causes
The mandate corresponding to the payer reference number already exists during direct debit
mandate creation.
Procedure
Ensure that the payer reference number is correct.
4.834 IC50013
Description
Failed to create the contact for the identity. The entered bank account of the contact already
exists in the current identity.
Scenario
This error is reported when a contact is created for an identity but the entered bank account
already exists in the identity.
Access Channel
Web, USSD, API
Possible Causes
The entered bank account of the contact already exists in the current identity.
Procedure
Enter a correct bank account.

Copyright © Huawei
Mobile Money
4.835 IC50014
Description
Failed to create the contact for the identity. The number of contacts of the identity has reached
the maximum.
Scenario
This error is reported when a contact is created for an identity but the number of contacts of
the identity has reached the maximum.
Access Channel
Web, USSD, API
Possible Causes
The number of contacts of the identity has reached the maximum.
Procedure
Do not create a contact for the identity again.
4.836 IC50015
Description
Operation failed. The operation must be performed by a registered customer.
Scenario
This error is reported when a service operation must be performed by a registered customer.
Access Channel
Web, USSD, API
Possible Causes
The customer is not registered.
Procedure
Register the customer.

Copyright © Huawei
Mobile Money
4.837 IC50016
Description
Failed to modify the advertising words.
Scenario
This error is reported during organization service advertising word modification if the
following rule is not met: The advertising text supports a maximum of 280 characters
(including space characters between words) and cannot contain special characters. Space
characters at the beginning and end must be automatically deleted.
Access Channel
POS
Possible Causes
The advertising text supports a maximum of 280 characters (including space characters
between words) and cannot contain special characters. Space characters at the beginning and
end must be automatically deleted.
Procedure
Ensure that the advertising word modification meets the rule.
4.838 IC50017
Description
Failed to modify the advertising words. Multiple services are the same.
Scenario
This error is reported during the organization service advertising word modification if
multiple services are the same.
Access Channel
POS
Possible Causes
Multiple services are the same.
Procedure

Copyright © Huawei
Mobile Money
4.839 IC50018
Description
Failed to modify the advertising words. Service {0} does not support advertisements.
{0} indicates a service name.
Scenario
This error is reported during the organization service advertising word modification if the
service does not support advertisements.
Access Channel
POS
Possible Causes
Service {0} does not support advertisements.
Procedure
4.840 IC50019
Description
If the initiator is a customer, the initiator can delete only reminder schedules of the initiator.
Scenario
This error is reported during reminder schedule deletion if the entered receiver is incorrect.
Access Channel
STK, USSD, API
Possible Causes
The initiator does not have the permission to delete data of other users.
Procedure
Ensure that the receiver and initiator are consistent.

Copyright © Huawei
Mobile Money
4.841 IC50020
Description
The identity does not have the account corresponding to the account instance.
Scenario
This error is reported during derect debit creation or activation if the account instance entered
does not exist or is closed.
Access Channel
Possible Causes
The account instance entered when a direct debit mandate is created or activated does not
exist or is closed.
Procedure
Verify that the entered account instance is correct.
4.842 IC50021
Description
The initiator of the direct debit mandate operation must be the payer, payee, or SP operator.
Scenario
This error is reported if the initiator of the direct debit mandate operation is not the payer,
payee, or SP operator.
Access Channel
Possible Causes
The initiator of the direct debit mandate operation is invalid.
Procedure
Ensure that the initiator of the direct debit mandate operation is the payer, payee, or SP
operator.

Copyright © Huawei
Mobile Money
4.843 IC50022
Description
The pre-warning period of the standing order schedule exceeds the maximum or is less than 0.
Scenario
This error is reported if the pre-warning period of the standing order schedule exceeds the
maximum or is less than 0.
Access Channel
Web, STK, USSD, API
Possible Causes
The pre-warning period of the standing order schedule exceeds the maximum or is less than 0.
Procedure
Enter a correct pre-warning period.
4.844 IC50023
Description
Scenario
Access Channel
Possible Causes
Procedure
operator.

Copyright © Huawei
Mobile Money
4.845 IC50024
Description
Scenario
Access Channel
Possible Causes
Procedure
operator.
4.846 IC50025
Description
If the initiator is a customer, the initiator can query only data of the initiator.
Scenario
This error is reported during customer data query if the entered receiver is incorrect.
Access Channel
STK, USSD, API
Possible Causes
The initiator does not have the permission to query data of other users.
Procedure
Modify the receiver to be the same as the initiator.

Copyright © Huawei
Mobile Money
4.847 IC50026
Description
The direct debit mandate has been canceled.
Scenario
This error is reported if the direct debit mandate to be operated has been canceled.
Access Channel
Possible Causes
The direct debit mandate has been canceled.
Procedure
Check input parameters and ensure that the direct debit mandate is correct.
4.848 IC50027
Description
The value of Range of Days of the direct debit mandate is incorrect.
Scenario
This error is reported if the value of Range of Days of the direct debit mandate is incorrect.
Access Channel
Web, STK, USSD, API
Possible Causes
The value of Range of Days of the direct debit mandate is incorrect.
Procedure
Check input parameters and ensure that the value of Range of Days of the direct debit
mandate is correct.

Copyright © Huawei
Mobile Money
4.849 IC50028
Description
The payer of the bulk task of the direct debit mandate must be an organization.
Scenario
This error is reported if the payer of the bulk task of the direct debit mandate is not an
organization.
Access Channel
Web(Bulk)
Possible Causes
The payer of the bulk task of the direct debit mandate must be an organization.
Procedure
Check the input parameter and ensure that the entered payer of the direct debit mandate is
correct.
4.850 IC50029
Description
Card number {2} of the {1} type of identity {0} is not in {3} state.

{1}: indicates the card type.
{2}: indicates the card number.
{3}: indicates the card number status.
Scenario
This error is reported in the financial card association service if the card number
corresponding to the card type of the identity is in an incorrect state.
Access Channel
Web, STK, USSD, API
Possible Causes
Card number {2} of the {1} type of identity {0} is not in {3} state.

Copyright © Huawei
Mobile Money
Procedure
Enter a card number in a correct state.
4.851 IC50030
Description
The initiator's organization {0} is not in the list of organizations that can register or deregister
a card of the {1} card type.
{0}: indicates the short code of the initiator's organization.

Scenario
This error is reported in the financial card association service if the initiator's organization is
not in the list of organizations that can register or deregister a card of the card type.
Access Channel
Web, STK, USSD, API
Possible Causes
The initiator's organization {0} is not in the list of organizations that can register or deregister
a card of the {1} card type.
Procedure
Choose My Functions > Operational Configuration > Card Configuration > Card Type
Management > Card Type, view information about the card type, and check which
organizations can register or deregister a card of the card type.
4.852 IC50031
Description
The entered card number {0} is in incorrect format.
{0} indicates the card number entered by initiator.
Scenario
This error is reported during card registration if the entered card number is in incorrect
format.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
The entered card number {0} is in incorrect format.
Procedure
Enter a correct card number.
4.853 IC50032
Description
Card number {1} of the type {0} to be registered has already been activated.
{0} indicates the card type.

{1} indicates the card number.
Scenario
This error is reported during card activation if the card to be activated has been activated.
Access Channel
Web, STK, USSD, API
Possible Causes
Card number {1} of the type {0} to be registered has already been activated.
Procedure
Enter a correct card number.
4.854 IC50033
Description
The entered card type {0} does not exist.

Copyright © Huawei
Mobile Money
Scenario
This error is reported during card registration or deregistration if the entered card type does
not exist.
Access Channel
Web, STK, USSD, API
Possible Causes
The entered card type {0} does not exist.
Procedure
Enter an existing card type.
4.855 IC50034
Description
Card number {2} of the {1} type of identity {0} already exists.
{0} indicates the receiver party.

{2} indicates the card number.
Scenario
This error is reported during card registration if the entered card number already exists.
Access Channel
Web, STK, USSD, API
Possible Causes
Card number {2} of the {1} type of identity {0} already exists.
Procedure
Enter a card number that does not exist in the system.
4.856 IC50035
Description
The initiator cannot initiate the card operation or the receiver is incorrect.

Copyright © Huawei
Mobile Money
Scenario
This error is reported during card operation if the initiator cannot initiate the operation or the
receiver is incorrect.
Access Channel
Web, STK, USSD, API
Possible Causes
The service initiator or receiver is incorrect.
Procedure
Ensure that the initiator can initiate the operation and the receiver is correct.
4.857 IC50036
Description
The additional card information is configured in the card type but not transferred in the
interface.
Scenario
This error is reported during card registration if additional card information is configured in
the card type but the initiator does not enter the additional card information.
Access Channel
Web, STK, USSD, API
Possible Causes
The additional card information is configured in the card type but not transferred in the
interface.
Procedure
Enter the additional card information as required.
4.858 IC50037
Description
The additional card information is not configured in the card type but transferred in the
interface.

Copyright © Huawei
Mobile Money
Scenario
This error is reported during card registration if additional card information is not configured
in the card type but the initiator enters the additional card information.
Access Channel
Web, STK, USSD, API
Possible Causes
The additional card information is not configured in the card type but transferred in the
interface.
Procedure
Do not enter the additional card information.
4.859 IC50038
Description
The entered additional card information {0} is not in the valid range.
{0} indicates the additional card information code.
Scenario
This error is reported during card registration if the entered additional card information is not
in the valid range.
Access Channel
Web, STK, USSD, API
Possible Causes
The entered additional card information {0} is not in the valid range.
Procedure
4.860 IC50039
Description
The {1} of the additional card information {0} is in incorrect format.

Copyright © Huawei
Mobile Money

{1} indicates the additional card information value.
Scenario
This error is reported during card registration if the additional card information is in incorrect
format.
Access Channel
Web, STK, USSD, API
Possible Causes
The {1} of the additional card information {0} is in incorrect format.
Procedure
Enter the additional card information in correct format.
4.861 IC50040
Description
The additional card information {0} must be transferred in the card registration scenario.
Scenario
This error is reported during card registration if the additional card information is not entered.
Access Channel
Web, STK, USSD, API
Possible Causes
The additional card information {0} must be transferred in the card registration scenario.
Procedure

Copyright © Huawei
Mobile Money
4.862 IC50041
Description
Card number {2} of the {1} type of identity {0} is not in Register or Cancel state.

Scenario
This error is reported during card activation if the card to be activated is not in Register or
Cancel state.
Access Channel
Web, STK, USSD, API
Possible Causes
Card number {2} of the {1} type of identity {0} is not in Register or Cancel state.
Procedure
Ensure that the card to be activated is in a correct state.
4.863 IC50042
Description
Card number {2} of the {1} type of identity {0} does not exist.

Scenario
This error is reported in the financial card association service if the identity does not have the
card number corresponding to the card type.
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
Card number {2} of the {1} type of identity {0} does not exist.
Procedure
Enter an existing card number.
4.864 IC50043
Description
The identity type can only be the registered customer, lite customer, SP operator, or
organization operator.
Scenario
This error is reported during identity linking or unlinking if the entered identity type is not
supported.
Access Channel
API, Web(Bulk)
Possible Causes
The entered identity type is not supported.
Procedure
Enter a correct identity type.
4.865 IC50044
Description
The identity list is repeated.
Scenario
This error is reported during identity linking or unlinking if the identity list is repeated.
Access Channel
API, Web(Bulk)
Possible Causes
The identity list is repeated.

Copyright © Huawei
Mobile Money
Procedure
Delete repeated identities.
4.866 IC50045
Description
The identity list does not meet the linking condition.
Scenario
This error is reported during identity linking or unlinking if the initiator is in the identity list.
Access Channel
API, Web(Bulk)
Possible Causes
Procedure
Contact the customer service personnel for more information.
4.867 IC50046
Description
Scenario
This error is reported during identity linking if the identity list does not meet the linking
condition.
Access Channel
API, Web(Bulk)
Possible Causes
Procedure
Perform the operation on an identity that meets the linking condition.

Copyright © Huawei
Mobile Money
4.868 IC50047
Description
The identity list length does not meet the requirements.
Scenario
This error is reported during identity linking or unlinking if the identity list length does not
meet the requirements.
Access Channel
API, Web(Bulk)
Possible Causes
The identity list length does not meet the requirements.
Procedure
Increase the identity list length. The identity list length must be greater than or equal to 2
during identity linking and greater than or equal to 1 during identity unlinking.
4.869 IC50048
Description
The identity list does not meet the unlinking condition.
Scenario
This error is reported during identity unlinking if the identity list does not meet the unlinking
condition.
Access Channel
API, Web(Bulk)
Possible Causes
The identity list does not meet the unlinking condition.
Procedure
Perform the operation on an identity that meets the unlinking condition. The unlinking
condition is that link IDs of identities to be unlinked are not empty and are the same.

Copyright © Huawei
Mobile Money
4.870 IC50049
Description
The entered identifier type is incorrect.
Scenario
This error is reported during identity unlinking if the entered identity type is incorrect.
Access Channel
API, Web(Bulk)
Possible Causes
The entered identifier type is incorrect.
Procedure
Enter a correct identifier type. The supported identifier types include 1 (MSISDN), 11
(organization operator user name), 12 (organization operator code), and 14 (SP operator user
name).
4.871 IC50050
Description
You are not authorized to perform this operation.
Scenario
This error is reported when an operator initiates the BO operation on identities with the same
link ID.
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
4.872 IC50051
Description
No more customer can be activated due to the license limit. Contact the system administrator.
Scenario
This error is reported in the following scenario: The active user number status is -1 in the
license. New user activation is forbidden after the bypass is enabled for a period of time. A
new activation request is submitted.
Access Channel
USSD
Possible Causes
The activation request is rejected due to the license limit.
Procedure
Ensure that the license permission is correct.
4.873 IC50052
Description
The balance of account {0} is less than the minimum amount configured in the saving plan or
is greater than the maximum amount configured in the saving plan.
Scenario
This error is reported during saving plan subscription if the account balance is less than the
minimum amount configured in the saving plan or is greater than the maximum amount
configured in the saving plan.
Access Channel
Web, STK, USSD, API, System
Possible Causes
The balance of account {0} is less than the minimum amount configured in the saving plan or
is greater than the maximum amount configured in the saving plan.

Copyright © Huawei
Mobile Money
Procedure
Configure the saving plan not to verify the maximum amount or minimum amount, or adjust
the account balance.
4.874 IC50053
Description
The command does not match the receiver type.
Scenario
This error is reported during saving plan subscription if the command does not match the
receiver type.
Access Channel
Possible Causes
The command does not match the receiver type.
Procedure
Ensure that the command matches the receiver type during saving plan subscription.
4.875 IC50054
Description
Identity account {0} is not in Active state.
Scenario
This error is reported during saving plan subscription if the identity account is not in Active
state.
Access Channel
Possible Causes
Identity account {0} is not in Active state.

Copyright © Huawei
Mobile Money
Procedure
Change the identity account status to Active and then subscribe to the saving plan.
4.876 IC50055
Description
The identity account has subscribed to a saving plan of the same type.
Scenario
This error is reported during saving plan subscription if the identity account has subscribed to
a saving plan of the same type.
Access Channel
Possible Causes
The identity account has subscribed to a saving plan of the same type.
Procedure
Subscribe to a saving plan of another type if only one type of saving plan is subscribed. Do
not subscribe to a saving plan if two types of saving plans have been subscribed.
4.877 IC50056
Description
The entered identity account or all accounts of the identity are not in the application scope of
the saving plan.
Scenario
This error is reported during saving plan subscription if the entered identity account or all
accounts of the identity are not in the application scope of the saving plan.
Access Channel
Possible Causes
TThe entered identity account or all accounts of the identity are not in the application scope of
the saving plan.

Copyright © Huawei
Mobile Money
Procedure
Ensure that the account type meets the application scope of the saving plan to be subscribed.
4.878 IC50057
Description
The entered account number or account type does not belong to the identity.
Scenario
This error is reported during saving plan subscription if the entered account number or
account type does not belong to the identity.
Access Channel
Possible Causes
The entered account number or account type does not belong to the identity.
Procedure
Enter a correct account number or account type.
4.879 IC50058
Description
The saving plan does not exist or is not in Active state.
Scenario
This error is reported during saving plan subscription or unsubscription if the saving plan does
not exist or is not in Active state.
Access Channel
Possible Causes
The saving plan does not exist or is not in Active state.
Procedure
Ensure that the saving plan exists and is in Active state.

Copyright © Huawei
Mobile Money
4.880 IC50059
Description
The short code of the provider must be the short code of the organization to which the
operator belongs.
Scenario
This error is reported when an organization operator creates a loyalty account for a consumer
but the entered short code of the provider is not the short code of the organization to which
the operator belongs.
Access Channel
Web, STK, USSD, API
Possible Causes
The short code of the provider is not the short code of the organization to which the operator
belongs.
Procedure
Enter a correct short code of the provider.
4.881 IC50060
Description
The loyalty point account fails to be created. The account type must be the loyalty point
account type.
Scenario
This error is reported during the creation of a loyalty point account if the entered account type
is not the loyalty point account type.
Access Channel
Web, STK, USSD, API
Possible Causes
The entered account type is not a loyalty point account type.
Procedure
Enter a correct loyalty point account type.

Copyright © Huawei
Mobile Money
4.882 IC50061
Description
The loyalty point account fails to be created. The entered account name must be in the loyalty
point plan list of the specified provider.
Scenario
This error is reported during consumer loyalty point account creation if the entered loyalty
point account name is not in the loyalty point plan list of the specified provider.
Access Channel
Web, STK, USSD, API
Possible Causes
The entered loyalty point account name {0} is not in the loyalty point plan list of the specified
provider.
{0} indicates an account name.
Procedure
4.883 IC50062
Description
The loyalty point account fails to be created. The entered account name cannot be the same as
that of an existing loyalty point account.
Scenario
This error is reported during the creation of a loyalty point account if the identity already has
a loyalty point account with the same name.
Access Channel
Web, STK, USSD, API
Possible Causes
The entered account name {0} is the same as that of an existing loyalty point account of the
identity.

Copyright © Huawei
Mobile Money
Procedure
4.884 IC50063
Description
When an organization operator creates a loyalty point account, the provider identity type must
be organization.
Scenario
This error is reported when an organization operator creates a loyalty point account but the
provider identity type is not organization.
Access Channel
Web, STK, USSD, API
Possible Causes
The identity type of the provider is not organization.
Procedure
Enter a correct provider identity type.
4.885 IC50064
Description
The loyalty point account fails to be created. The value of Loyalty Schema Role Type is
incorrect and must be {0}.
{0} indicates schema role type value.
Scenario
This error is reported if the following rule is not met: When an SP operator creates a loyalty
point account, the value of schema role type must be 1 or 2. When an organization operator
creates a loyalty point account, the value of schema role type must be 2.
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
When an SP operator creates a loyalty point account, the value of schema role type must be 1
or 2. When an organization operator creates a loyalty point account, the value of schema role
type must be 2.
Procedure
Set Loyalty Schema Role Type to a correct value.
4.886 IC50065
Description
During the creation of a loyalty point account, if a loyalty point plan is created, the entered
account type must be applicable to the provider. If a loyalty point plan is added, the entered
account type must be applicable to the consumer.
Scenario
This error is reported if the following rule is not met during the creation of a loyalty point
account: If a loyalty point plan is created, the entered account type must be applicable to the
provider. If a loyalty point plan is added, the entered account type must be applicable to the
consumer.
Access Channel
Web, STK, USSD, API
Possible Causes
The account type entered during loyalty point plan creation is not applicable to the provider or
the account type entered during loyalty point plan adding is not applicable to the consumer.
Procedure
Ensure that the setting of Loyalty Account Category of the account type is applicable to the
current scenario.
4.887 IC50066
Description
Card type {0} cannot be registered by identities of the {1} type.
{0} indicates card type.


Copyright © Huawei
Mobile Money
Scenario
This error is reported in the financial card association service if the card type cannot be
registered by identities.
Access Channel
Web, STK, USSD, API
Possible Causes
Card type {0} cannot be registered by identities of the {1} type.
Procedure
Choose My Functions > Operational Configuration > Card Configuration > Card Type
and check the types of identities that can register the card type.
4.888 IC50067
Description
The customer does not belong to the group and cannot query the group.
Scenario
This error is reported when a customer queries a group but the customer does not belong to
the group.
Access Channel
API
Possible Causes
The customer does not belong to the group.
Procedure
Select a customer belonging to the group to query the group.
4.889 IC50068
Description
The initiator does not meet the conditions for querying the current recipient and cannot query
the recipient.

Copyright © Huawei
Mobile Money
Scenario
This error is reported when the initiator does not meet the conditions for querying the current
recipient.
Access Channel
API
Possible Causes
The initiator does not meet the conditions for querying the current recipient.
Procedure
Select an initiator meeting the conditions for querying the current recipient.
4.890 IC50069
Description
The transaction is rejected.
Scenario
This error is reported if a transaction meeting the complex relationship is rejected.
Access Channel
API, Web(Bulk)
Possible Causes
The transaction is rejected.
Procedure
4.891 IC50070
Description
All accounts or the entered accounts have not subscribed to the specified saving plan.
Scenario
This error is reported if all accounts or the entered accounts have not subscribed to the
specified saving plan.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
All accounts or the entered accounts have not subscribed to the specified saving plan.
Procedure
Ensure that the accounts have subscribed to the specified saving plan.
4.892 IC50071
Description
The customer cannot subscribe to or unsubscribe from a saving plan for another customer.
Scenario
This error is reported when a customer subscribes to or unsubscribes from a saving plan for
another customer.
Access Channel
Web, STK, USSD, API
Possible Causes
The customer subscribes to or unsubscribes from a saving plan for another customer.
Procedure
Ensure that the customer subscribe to or unsubscribe from a saving plan for the customer
itself.
4.893 IC50072
Description
The organization operator cannot subscribe to or unsubscribe from a saving plan for another
organization.
Scenario
This error is reported when an organization operator subscribes to or unsubscribes from a
saving plan for another organization.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
The organization operator subscribes to or unsubscribes from a saving plan for another
organization.
Procedure
Ensure that the organization operator subscribe to or unsubscribe from a saving plan for the
organization to which the operator belongs.
4.894 IC50073
Description
The entity or entity account cannot be closed because the entity account has subscribed to the
saving plan and the subscription status is Active.
Scenario
This error is reported when an entity account has subscribed to a saving plan and the
subscription status is Active but the entity or entity account is closed.
Access Channel
Web, STK, USSD, API
Possible Causes
The entity account has subscribed to the saving plan and the subscription status is Active.
Procedure
Unsubscribe from the saving plan and then close the entity or entity account.
4.895 IC50074
Description
The card number must be entered during card registration.
Scenario
This error is reported during card registration if no card number is entered.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
No card number is entered.
Procedure
Enter the card number to be registered.
4.896 IC50075
Description
The card type must be entered during card registration.
Scenario
This error is reported during card registration if no card type is entered.
Access Channel
Web, STK, USSD, API
Possible Causes
No card type is entered.
Procedure
Enter the card type to be registered.
4.897 IC50076
Description
During card registration, if the receiving party is a customer, the customer's MSISDN {0}
must be of the registered customer type.
{0} indicates the MSISDN of the receiving party.
Scenario
This error is reported during card registration if the receiving party is a customer but is not a

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
The receiving party is a customer but is not a registered customer.
Procedure
Ensure that the receiving party is a registered customer.
4.898 IC50077
Description
The value of the Territory Type parameter is incorrect.
Scenario
This error is reported if the entered territory type is invalid when the system checks whether
the real-time location is in the territory of the specified type.
Access Channel
STK, USSD, API
Possible Causes
The value of the Territory Type parameter is incorrect.
Procedure
Enter a correct value for the Territory Type parameter.
4.899 IC50078
Description
The territory type does not exist.
Scenario
This error is reported if the entered territory type does not exist when the system checks
whether the real-time location is in the territory of the specified type.
Access Channel
STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
Territory type {0} does not exist.
{0}: territory type, for example, 10001.
Procedure
Enter an existing territory type.
4.900 IC50079
Description
The verification type can be 1, 2, or 3.
Scenario
This error is reported if the entered verification type is invalid when the system checks
whether the real-time location is in the specified territory.
Access Channel
STK, USSD, API
Possible Causes
Verification type {0} is incorrect.
{0}: verification type, for example, 1.
Procedure
Enter a correct verification type.
4.901 IC50080
Description
No location information is entered.
Scenario
This error is reported if no location information is entered when the system checks whether
the real-time location is in the specified territory.

Copyright © Huawei
Mobile Money
Access Channel
STK, USSD, API
Possible Causes
The location information of {0} cannot be empty.
{0}: role name, for example, Initiator or Receiver.
Procedure
Enter correct location information.
4.902 IC50081
Description
The location information type must be 1 or 2.
Scenario
This error is reported if the entered location information type is incorrect when the system
checks whether the real-time location is in the specified territory.
Access Channel
STK, USSD, API
Possible Causes
The location information type of {0} is incorrect.
Procedure
Enter a correct location information type.
4.903 IC50082
Description
The entered value of the FactorX parameter is incorrect.

Copyright © Huawei
Mobile Money
Scenario
This error is reported if the value of FactorX is incorrect in the entered location information
when the system checks whether the real-time location is in the specified territory.
Access Channel
STK, USSD, API
Possible Causes
The FactorX parameter in location information of {0} is incorrect.
Procedure
Enter a correct value of the FactorX parameter.
4.904 IC50083
Description
The entered value of the FactorY parameter is incorrect.
Scenario
This error is reported if the value of FactorY is incorrect in the entered location information
when the system checks whether the real-time location is in the specified territory.
Access Channel
STK, USSD, API
Possible Causes
The FactorY parameter in location information of {0} is incorrect.
Procedure
Enter a correct value of the FactorY parameter.

Copyright © Huawei
Mobile Money
4.905 IC50084
Description
The territory information has not been configured or the territory information is incorrect.
Scenario
This error is reported if the territory information has not been configured or is incorrect when
the system checks whether the real-time location is in the specified territory.
Access Channel
STK, USSD, API
Possible Causes
The territory information of {0} does not exist.
Procedure
Change the KYC and configure the correct territory information.
4.906 IC50085
Description
No territory information is found based on the territory type.
Scenario
This error is reported if no territory is found based on the territory type when the system
checks whether the real-time location is in the territory of the specified type.
Access Channel
STK, USSD, API
Possible Causes
Territory information corresponding to the territory type {0} does not exist.
{0}: territory type, for example, 10001.

Copyright © Huawei
Mobile Money
Procedure
Enter a correct value for the Territory Type parameter.
4.907 IC50086
Description
The identity is not in the specified region.
Scenario
This error is reported if the identity is not in the specified region when the system checks
whether the real-time location is in the specified territory.
Access Channel
STK, USSD, API
Possible Causes
{0} is not in the specified region.
Procedure
Enter correct location information.
4.908 IC50090
Description
The saving plan to be subscribed is not in the application scope.
Scenario
This error is reported when the saving plan is not in the application scope during the
subscription of the saving plan.
Access Channel
Possible Causes
The saving plan to be subscribed is not in the application scope.

Copyright © Huawei
Mobile Money
Procedure
Subscribe to a saving plan in the application scope or add this saving plan to the application
scope.
4.909 IC50091
Description
The identity is not in the application scope of the saving plan during the subscription of the
saving plan.
Scenario
This error is reported when the identity is not in the application scope of the saving plan
during the subscription of the saving plan.
Access Channel
Possible Causes
The identity is not in the application scope of the saving plan during the subscription of the
saving plan.
Procedure
Ensure that the identity type, subtype (only for identities of the non-group type), trust level,
and segment meet the application scope of the saving plan to be subscribed.
4.910 IC50092
Description
The GPRS location is incorrect.
Scenario
This error is reported when the GPRS location configured is incorrect for checking whether
the real-time location is in the corresponding territory.
Access Channel
STK, USSD, API
Possible Causes
The GPRS location is incorrect.

Copyright © Huawei
Mobile Money
Procedure
Log in to the portal, choose My Functions > Operational Configuration > Territory
Configuration > Territory Hierarchy, and configure the correct GPRS location.
4.911 IC50093
Description
Failed to close the identity. A BO operation is not complete.
Scenario
This error is reported if an identity has an unfinished BO operation when an SP operator or
organization operator attempts to close an identity on the web page.
Access Channel
Web
Possible Causes
A BO operation is not complete so that the identity cannot be closed.
Procedure
End the identity-related BO process first.
4.912 LP10000
Description
The loyalty point account does not exist. loyalty point exchange or adjustment failed.
Scenario
This error is reported during loyalty point exchange or adjustment if the corresponding
account does not exist.
Access Channel
Web, API
Possible Causes
The loyalty point account does not exist.

Copyright © Huawei
Mobile Money
Procedure
Select a correct account for loyalty point exchange or adjustment.
4.913 LP10001
Description
The receiver type {0} is not supported. loyalty point exchange or adjustment failed.
{0} indicates a receiver type, for example, customer.
Scenario
This error is reported during loyalty point exchange or adjustment if the receiver is not
supported.
Access Channel
Web, API
Possible Causes
The receiver in the request is not supported.
Procedure
Select a correct receiver type and initiate the request again.
4.914 LP10002
Description
The loyalty point account balance is insufficient. loyalty point exchange or adjustment failed.
Scenario
This error is reported during loyalty point exchange or adjustment if the loyalty point account
balance is insufficient.
Access Channel
Web, API
Possible Causes
The loyalty point account balance is insufficient.

Copyright © Huawei
Mobile Money
Procedure
Reduce the exchange amount or adjustment amount.
4.915 LP10003
Description
The {0} account already exists.
{0}: indicates identity ID.
Scenario
This error is reported when the identity account to be created already exists.
Access Channel
Web
Possible Causes
The {0} account already exists. Currently, for a customer or agent, only one account can be
created for an account type.
Procedure
Select an account type for which no account is created.
4.916 LP10004
Description
Data of the identity's account is changed too frequently. Try again later.
Scenario
This error is reported during a transaction, the number of account data updates in a certain
period exceeds the maximum number of optimistic lock updates.
Access Channel
Web, STK, USSD, API
Possible Causes
The number of changes to the identity's account data exceeds the upper limit configured for
the optimistic lock.

Copyright © Huawei
Mobile Money
Procedure
If the problem persists, contact a Huawei engineer for help or access http://icare.huawei.com
and submit a fault application report.
4.917 LP10005
Description
Multiple loyalty point accounts are matched. loyalty point exchange or adjustment failed.
Scenario
This error is reported during loyalty point adjustment or exchange if multiple loyalty point
accounts are matched based on then input parameter.
Access Channel
Web, API
Possible Causes
Multiple loyalty point accounts are matched based on the input parameter.
Procedure
Enter more specific loyalty point account information.
4.918 LP10006
Description
The API request fails to be initiated because the loyalty point operation type is incorrect.
Scenario
This error is reported when a loyalty point operation is initiated through the API channel but
the entered loyalty point operation type is incorrect.
Access Channel
API
Possible Causes
The loyalty point operation type is incorrect.

Copyright © Huawei
Mobile Money
Procedure
Enter a correct loyalty point operation type. Currently, only loyalty point adjustment and
exchange are supported. Value 1 indicates loyalty point adjustment and value 2 indicates
loyalty point exchange.
4.919 LP10007
Description
The loyalty point amount is incorrect. loyalty point exchange or adjustment failed.
Scenario
This error is reported when loyalty point exchange or adjustment is initiated through the API
channel but the entered loyalty point amount is incorrect.
Access Channel
API
Possible Causes
The format of the loyalty point amount {0} is incorrect.
{0} indicates an entered loyalty point amount.
Procedure
Enter a correct loyalty point amount. The loyalty point amount must be an integer.
4.920 LP10008
Description
The loyalty point exchange amount is less than 0 and the exchange fails.
Scenario
This error is reported if the loyalty point exchange amount entered during loyalty point
exchange is less than 0.
Access Channel
API

Copyright © Huawei
Mobile Money
Possible Causes
The loyalty point exchange amount is less than 0.
Procedure
Enter a loyalty point exchange amount that is greater than 0.
4.921 LP10009
Description
The entered loyalty point amount is 0. loyalty point exchange or adjustment failed.
Scenario
This error is reported during loyalty point exchange or adjustment if the entered loyalty point
amount is 0.
Access Channel
API
Possible Causes
The entered loyalty point amount is 0.
Procedure
Enter a loyalty point amount that is greater than 0 for loyalty point exchange and enter a
loyalty point amount that is not 0 for loyalty point adjustment. For loyalty point adjustment,
the positive value indicates to increase the loyalty points and the negative value indicates to
decrease the loyalty points.
4.922 LP10010
Description
The length of field {0} is greater than {1}. loyalty point exchange or adjustment failed.
{0} indicates a field name.

{1} indicates the maximum length of the field.
Scenario
This error is reported during loyalty point exchange or adjustment if the field length exceeds
the maximum.

Copyright © Huawei
Mobile Money
Access Channel
API
Possible Causes
The length of field {0} is greater than {1}.
Procedure
Modify the field {0} to ensure that its length does not exceed {1}.
4.923 LP10011
Description
The specified loyalty point account type alias is incorrect.
Scenario
This error is reported if no loyalty point account is found based on the specified loyalty point
account type.
Access Channel
API, Web
Possible Causes
No loyalty point account is found based on the specified loyalty point account type.
Procedure
Ensure that the entered loyalty point account type alias is correct.
4.924 LP10012
Description
The specified loyalty point account type alias is incorrect.
Scenario
This error is reported if no loyalty point account change log is found based on the specified
loyalty point account type.
Access Channel
API, Web

Copyright © Huawei
Mobile Money
Possible Causes
No loyalty point account change log is found based on the specified loyalty point account
type.
Procedure
Ensure that the entered loyalty point account type alias is correct.
4.925 LP10013
Description
The input parameters are incorrect or other system errors occur. Failed to create the loyalty
point account.
Scenario
This error is reported when the loyalty point account fails to be created for an identity due to
incorrect input parameters or other system errors.
Access Channel
API, Web
Possible Causes
The input parameters are incorrect or other system errors occur.
Procedure
Ensure that the input parameters for creating the loyalty point account are correct.
4.926 LP10014
Description
Corresponding LoyaltyPointTypeId is not found.
Scenario
This error is reported during loyalty point account creation if corresponding
LoyaltyPointType is not found in the system based on the input parameter value.
Access Channel
API, Web

Copyright © Huawei
Mobile Money
Possible Causes
{0} indicates a parameter name.
Procedure
Ensure that the value of parameter {0} is correct
4.927 LP10015
Description
The loyalty point account type {0} is not in Released state and is unavailable.
Scenario
This error is reported during loyalty point account creation if corresponding
LoyaltyPointType found in the system based on LoyaltyPointTypeId is not in Released
state.
Access Channel
API, Web
Possible Causes
The loyalty point account type {0} is not in Released state.
Procedure
Choose My Functions > Operational Configuration > Loyalty Point Configuration >
Loyalty Point Type, search for the loyalty point account type whose Loyalty Point Type
Name is {0}, and ensure that the loyalty point account type is in correct state.
4.928 LP10016
Description
Operation failed. The specified LoyaltyPointTypeId is not applicable to the current identity.
Scenario
This error is reported during loyalty point account creation if the loyalty point account type
found in the system based on LoyaltyPointTypeId is not applicable to the current identity.

Copyright © Huawei
Mobile Money
Access Channel
API, Web
Possible Causes
The loyalty point account type found in the system based on LoyaltyPointTypeId is not
applicable to the current identity.
Procedure
Ensure that the value of LoyaltyPointTypeId is correct.
4.929 LP10017
Description
The identity does not have any loyalty point account. Failed to query the loyalty points.
Scenario
This error is reported during loyalty point query if the identity does not have any loyalty point
account.
Access Channel
API
Possible Causes
The identity does not have any loyalty point account.
Procedure
Ensure that the identity has a loyalty point account.
4.930 LP10018
Description
Failed to adjust bonus points. The parameters in the bonus point adjustment request are not set
to the required value.
Scenario
This error is reported if the parameters in the bonus point adjustment request are not set to the
required value.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
When the value of the AdjustmentCategory field is 1 in the request, the initiator is not an SP
operator. When the value of the AdjustmentCategory field is 2 in the request, the initiator is
not an SP operator, a customer, or an organization operator.
Procedure
Modify parameters and initiate the request again.
4.931 LP10019
Description
Failed to adjust bonus points. The recipient is not the same customer as the initiator.
Scenario
This error is reported if the recipient is not the same customer as the initiator for bonus point
adjustment.
Access Channel
Web
Possible Causes
The initiator is a customer, but the recipient is not the customer.
Procedure
4.932 LP10020
Description
Failed to adjust bonus points. Several bonus point types are entered in one request.
Scenario
This error is reported if multiple different bonus point types are found in the same request for
bonus point adjustment.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
Several bonus point types are entered in one request.
Procedure
4.933 LP10021
Description
Failed to adjust bonus points. The entered value of ExpiredDate is earlier than the current
system time.
Scenario
This error is reported if the entered value of ExpiredDate is earlier than the current system
time when the point ID of the bonus point account to be adjusted is entered.
Access Channel
Web
Possible Causes
The entered value of ExpiredDate is earlier than the current system time when the point ID
of the bonus point account to be adjusted is entered.
Procedure
4.934 LP10022
Description
Failed to adjust bonus points. The external service sequence number in the bonus point
adjustment request already exists.
Scenario
This error is reported if the external service sequence number in the bonus point adjustment
request already exists.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The external service sequence number in the bonus point adjustment request already exists.
Procedure
4.935 LP10023
Description
Failed to adjust bonus points. The entered value of ExpiredDate is different from the
expiration date of the bonus point account with the entered point ID.
Scenario
This error is reported if the entered value of ExpiredDate is different from the expiration date
of the bonus point account with the entered point ID.
Access Channel
Web
Possible Causes
The entered value of ExpiredDate is different from the expiration date of the bonus point
account with the entered point ID.
Procedure
4.936 LP10024
Description
Failed to adjust bonus points. The bonus point account to be adjusted is not active.
Scenario
This error is reported if the bonus point account to be adjusted is not active.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The bonus point account to be adjusted is not active.
Procedure
4.937 LP10025
Description
Failed to adjust bonus points. The bonus point account to be adjusted has insufficient balance.
Scenario
This error is reported if the bonus point account to be adjusted has insufficient balance.
Access Channel
Web
Possible Causes
The bonus point account to be adjusted has insufficient balance, and the system does not
allow negative bonus points.
Procedure
4.938 LP10026
Description
Failed to adjust bonus points.
Scenario
This error is reported if the order ID corresponding to the Client Business No. field is in
correct in the bonus point adjustment request.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The order ID corresponding to the Client Business No. field is in correct in the bonus point
adjustment request.
Procedure
4.939 LP10027
Description
Failed to issue bonus points. The quantity of bonus points in the bonus point issuing request
must be less than or equal to zero.
Scenario
This error is reported if the quantity of bonus points in the bonus point issuing request is
greater than zero.
Access Channel
Web
Possible Causes
The quantity of bonus points in the bonus point issuing request is greater than zero.
Procedure
4.940 LP10028
Description
Failed to issue bonus points. The bonus point type does not exist or is invalid.
Scenario
This error is reported if the bonus point type in the bonus point issuing request does not exist
or is invalid.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The bonus point type in the bonus point issuing request does not exist or is invalid.
Procedure
4.941 LP10029
Description
The query fails because the receiver does not have the loyalty point account of this type.
Scenario
This error is reported during loylaty point exchange rate query if the receiver does not have
the loyalty point account of the type specified by PointTypeId.
Access Channel
Web, USSD, API
Possible Causes
The value of the entered PointTypeId is incorrect. The receiver does not have the loyalty
point account of this type.
Procedure
Change the value of PointTypeId to a correct one.
4.942 LP10030
Description
The goods fails to be exchanged because the voucher information is inconsistent with the
receiver information.
Scenario
This error is reported if the voucher information is inconsistent with the receiver information
when an SP exchanges loyalty points for goods for an organization.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The voucher information is inconsistent with the receiver information.
Procedure
Initiate the exchange operation again.
4.943 LP10031
Description
The goods fails to be exchanged because the voucher whose voucher code is {0} does not
exist or is not in Active state.
Scenario
This error is reported if the voucher does not exist or is not in Active state when an SP
exchanges loyalty points for goods for an organization.
Access Channel
Web
Possible Causes
The voucher whose voucher code is {0} does not exist or is not in Active state.
{0} indicates a voucher code.
Procedure
Enter the code of a voucher in Active state.
4.944 LP10032
Description
Loyalty points fail to be reversed due to system exception. The loyalty points are deducted but
the goods fails to be exchanged.
Scenario
This error is reported if loyalty points fail to be reversed due to system exception when an SP
exchanges loyalty points for goods for an organization.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
Loyalty points fail to be reversed due to system exception.
Procedure
Reverse the loyalty points manually.
4.945 LP10033
Description
The loyalty point exchange amount must be greater than 0 and the loyalty point balance ratio
is {0}.
{0} indicates the exchange ratio.
Scenario
This error is reported when the loyalty points are exchanged for balance but the exchanged
balance amount is not greater than 0.
Access Channel
Web, STK, USSD, API
Possible Causes
The loyalty point exchange amount must be greater than 0 and the loyalty point balance ratio
is {0}.
Procedure
Ensure that the loyalty point exchange amount is greater than 0.
4.946 LP10034
Description
The rate for exchanging loyalty points of the {0} type is not configured.
{0} indicates the loyalty point type.

Copyright © Huawei
Mobile Money
Scenario
This error is reported when the loyalty points are exchanged for balance but the exchange rate
is not configured.
Access Channel
Web, STK, USSD, API
Possible Causes
The rate for exchanging loyalty points of the {0} type is not configured.
Procedure
Configure the rate for exchanging loyalty points for balance.
4.947 LP10035
Description
The Goods system fails to return the exchange confirmation message.
Scenario
This error is reported when loyalty points are exchanged for goods but the Goods system fails
to return the exchange confirmation message.
Access Channel
POS
Possible Causes
The Goods system fails to return the exchange confirmation message.
Procedure
Initiate the loyalty point exchange request again.
4.948 LP10036
Description
The Goods system fails to return the exchange confirmation message and fails to reverse the
loyalty points.

Copyright © Huawei
Mobile Money
Scenario
This error is reported when loyalty points are exchanged for goods but the Goods system fails
to return the exchange confirmation message and fails to reverse the loyalty points.
Access Channel
POS
Possible Causes
The Goods system fails to return the exchange confirmation message and fails to reverse the
loyalty points.
Procedure
Manually reverse the loyalty points and initiate the exchange request again.
4.949 LP10037
Description
A timeout occurs when the Goods system returns the exchange result confirmation message.
Scenario
This error is reported when loyalty points are exchanged for goods but a timeout occurs when
the Goods system returns the exchange result confirmation message.
Access Channel
POS
Possible Causes
A timeout occurs when the Goods system returns the exchange result confirmation message.
Procedure
Manually reverse the loyalty points and initiate the exchange request again.
4.950 LP10038
Description
An error is reported when the system changes the loyalty points.

Copyright © Huawei
Mobile Money
Scenario
This error is reported when loyalty points are exchanged for goods but an internal system
error occurs.
Access Channel
POS
Possible Causes
An internal system error occurs when loyalty points are exchanged for goods.
Procedure
4.951 LP10039
Description
The system fails to change the loyalty points and the Goods system fails to cancel the
exchange.
Scenario
error occurs and the Goods system fails to cancel the exchange.
Access Channel
POS
Possible Causes
An internal system error occurs and the Goods system fails to cancel the exchange.
Procedure
4.952 LP10040
Description
The system fails to change the loyalty points and a timeout occurs when the Goods system
cancels the exchange.

Copyright © Huawei
Mobile Money
Scenario
error occurs and a timeout occurs when the Goods system cancels the exchange.
Access Channel
POS
Possible Causes
An internal system error occurs and a timeout occurs when the Goods system cancels the
exchange.
Procedure
4.953 LP10041
Description
The exchange request is rejected and the Goods system fails to cancel the exchange.
Scenario
This error is reported when loyalty points are exchanged for goods but the exchange request is
rejected and the Goods system fails to cancel the exchange.
Access Channel
POS
Possible Causes
The exchange request is rejected and the Goods system fails to cancel the exchange.
Procedure
Contact Huawei engineers.
4.954 LP10042
Description
The exchange request is rejected and a timeout occurs when the Goods system cancels the
exchange.

Copyright © Huawei
Mobile Money
Scenario
This error is reported when loyalty points are exchanged for goods but the exchange request is
rejected and a timeout occurs when the Goods system cancels the exchange.
Access Channel
POS
Possible Causes
The exchange request is rejected and a timeout occurs when the Goods system cancels the
exchange.
Procedure
Contact Huawei engineers.
4.955 LP10043
Description
The receiver must be an organization.
Scenario
This error is reported when an organization operator initiates a request to exchange loyalty
points for goods but the receiver is not an organization.
Access Channel
POS
Possible Causes
When an organization operator initiates a request to exchange loyalty points for goods, the
receiver is not an organization.
Procedure
Change the receiver to an organization.
4.956 LP10044
Description
Loyalty point exchange fails. The loyalty point change amount and the balance do not meet
the configuration requirements.

Copyright © Huawei
Mobile Money
Scenario
The loyalty point exchange service needs to check the limit and check whether the loyalty
point change amount and the balance meet the configuration requirements. This error is
reported if the configuration requirements are not met.
Access Channel
Web
Possible Causes
When the loyalty point exchange service checks the limit, the loyalty point change amount
and the balance do not meet the configuration requirements.
Procedure
Modify the limit parameter and initiate the operation again.
4.957 LP10045
Description
No loyalty point exchange rate corresponding to the loyalty point type is found.
Scenario
This error is reported if no loyalty point exchange rate is configured in the system and the
query result is empty.
Access Channel
API
Possible Causes
No loyalty point exchange rate is configured in the system or the data is incorrect.
Procedure
Choose My Functions > Operational Configuration > Loyalty Point Configuration >
Loyalty Points Type, search for the corresponding loyalty point account type, and verify that
the configuration of Balance Redemption Rate is correct.

Copyright © Huawei
Mobile Money
4.958 LP10046
Description
The loyalty point adjustment or exchange fails. When the identity has accounts of different
loyalty point types, a point type must be specified in the request.
Scenario
This error is reported if the loyalty point adjustment or exchange parameter is incorrect.
Access Channel
Web
Possible Causes
When an identity has different types of loyalty point accounts, the point type is not specified
in the request or multiple point types are specified in the request.
Procedure
Modify request parameters and initiate the request again.
4.959 LP10047
Description
Failed to transfer loyalty points.
Scenario
This error is reported during loyalty point transfer if the transferor and transferee are the
same.
Access Channel
Web
Possible Causes
The transferor and transferee of the loyalty point transfer transaction cannot be the same
customer.
Procedure
Modify the transferee information and initiate the transaction again.

Copyright © Huawei
Mobile Money
4.960 LP10048
Description
Scenario
This error is reported during loyalty point transfer if the system fails to verify the transfer rule.
Access Channel
Web
Possible Causes
The loyalty point transfer rule fails to be verified (because no transfer rule is added for the
loyalty point account, or the transferor or transferee does not meet the transfer rule
requirements.)
Procedure
Modify the transferor information and initiate the transaction again.
4.961 LP10049
Description
Scenario
This error is reported during loyalty point transfer if no loyalty point type is specified and the
transferor identity has multiple loyalty point accounts of different types.
Access Channel
Web
Possible Causes
No loyalty point type is specified during loyalty point transfer and the transferor identity has
multiple loyalty point accounts of different types.
Procedure
Specify a loyalty point type and initiate the transaction again.

Copyright © Huawei
Mobile Money
4.962 LP10050
Description
Loyalty points fail to be transferred.
Scenario
This error is reported when the number of loyalty points for transfer is invalid.
Access Channel
Web
Possible Causes
The number of loyalty points for transfer is invalid.
Procedure
Modify the transferee information and transfer the loyalty points again.
4.963 LP10051
Description
The loyalty points fail to be rolled back.
Scenario
This error is reported when the historical loyalty point operation record cannot be found
during loyalty point rollback.
Access Channel
Web
Possible Causes
During loyalty point rollback, the historical loyalty point operation record where the
transaction ID is {0} cannot be found.
Procedure
Modify related information and initiate the operation again.

Copyright © Huawei
Mobile Money
4.964 LP10052
Description
The operator rejects the loyalty point redeeming operation during review.
Scenario
This error is reported if an operator rejects the loyalty point redeeming operation during
review.
Access Channel
POS
Possible Causes
The operator rejects the loyalty point redeeming operation during review.
Procedure
Contact the system operator.
4.965 LP10053
Description
The voucher does not support the operation.
Scenario
This error is reported when loyalty points are redeemed for goods with a voucher but the
entered voucher is not of the specified type.
Access Channel
Web, API
Possible Causes
Voucher {0} cannot be used to redeem loyalty points for goods.
{0} indicates a voucher code.
Procedure
 Choose My Functions > Operational Configuration > System Parameter > customer
Parameters (customer refund to registered customer).
 Verify that the configured transaction type exists.

Copyright © Huawei
Mobile Money
4.966 LP10054
Description
Only independent loyalty points are supported.
Scenario
This error is reported if the loyalty point adjustment, loyalty point transfer, redeeming loyalty
points for goods, and redeeming loyalty points for balance is not used in the independent
loyalty point solution.
Access Channel
Web, API, USSD
Possible Causes
Only independent loyalty points are supported.
Procedure
The system can only support independent loyalty points.
4.967 TC30000
Description
The order relationship cannot be blank during the rollback of SP withdrawal transactions.
Scenario
The order relationship cannot be blank during the rollback of SP withdrawal transactions.
Access Channel
Web
Possible Causes
The order relationship is blank during the rollback of SP withdrawal transactions.
Procedure

Copyright © Huawei
Mobile Money
4.968 TC30001
Description
The system does not support this type of transactions or operations.
Scenario
The reconciliation operation is abnormal. That is, the system does not have defined
operations.
Access Channel
Web
Possible Causes
The reconciliation function does not support this type of transactions or operations.
Procedure
4.969 TC30002
Description
An error occurs if Reason Type input by the portal is not Bulk Payment during the bulk
payment transaction.
Scenario
An error occurs if Reason Type input by the portal is not Bulk Payment during the bulk
payment transaction.
Access Channel
Web, API
Possible Causes
 The input reason type is incorrect during the transaction.
 The transaction template for bulk payment is incorrectly configured.
Procedure
1. Check whether the selected reason type is correct.
2. Contact Huawei engineers if this is a configuration problem.

Copyright © Huawei
Mobile Money
4.970 TC30003
Description
The account balance direction positive before the transaction, and the account balance must
be equal to or greater than 0 after the transaction.
Scenario
An error occurs if the account balance direction is positive before the Journal Entry
Transaction but the account balance is less than 0 after the transaction.
Access Channel
Web
Possible Causes
The account balance direction is positive before the Journal Entry Transaction but the account
balance is less than 0 after the transaction.
Procedure
Check the account balance of the debit party before and after the transaction.
4.971 TC30004
Description
The account balance direction is negative before transaction, and the account balance must be
equal to or less than 0 after the transaction.
Scenario
An error occurs if the account balance direction is negative before the Journal Entry
Transaction but the account balance is greater than 0 after the transaction.
Access Channel
Web
Possible Causes
The account balance direction is negative before the Journal Entry Transaction but the account
balance is greater than 0 after the transaction.
Procedure
Check the account balance of the debit party before and after the transaction.

Copyright © Huawei
Mobile Money
4.972 TC30005
Description
The voucher type cannot be found based on VoucherTypeIndex ({0}).
{0}: indicates the voucher type index.
Scenario
The verification during voucher redeeming.
Access Channel
API
Possible Causes
The voucher type is incorrectly configured.
Procedure
Check the voucher type and request packets.
4.973 TC30006
Description
The voucher cannot be found based on the voucher code.
Scenario
The verification during voucher redeeming.
Access Channel
API
Possible Causes
The voucher type or the request packets are incorrect.
Procedure
Check the voucher data and request packets.

Copyright © Huawei
Mobile Money
4.974 TC30007
Description
The reversal transaction fails because it is initiated after the reversal period is exceeded. The
reversal period configured in the reason type is {0} minute.
{0}: indicates the reversal period configured in Reason Type.
Scenario
The error message is reported if a reversal transaction is initiated after the reversal period is
exceeded.
Access Channel
Web, USSD, API, STK
Possible Causes
The reversal transaction fails because it is initiated after the reversal period is exceeded.
Procedure
Change the reversal period in the reason type to a larger value.
4.975 TC30008
Description
The voucher to be redeemed contains the short code {0}, but the input short code is {1}.
The {0} variable indicates the short code for voucher to be redeemed.
The {1} variable indicates the input short code.
Scenario
The voucher to be redeemed contains the short code of the organization, but the input short
code during redeeming is different from this short code.
Access Channel
API
Possible Causes
The voucher information or the request packet information is incorrect.

Copyright © Huawei
Mobile Money
Procedure
Apply for a voucher that contains a short cord and check the request packet information.
4.976 TC30009
Description
The order ID cannot be found based on a conversation ID during API transaction
confirmation.
Scenario
The order ID cannot be found based on a conversation ID during API transaction
confirmation.
Access Channel
API
Possible Causes
Searching for an order ID failed during API transaction confirmation.
Procedure
Check the conversation ID input by the AG or directly enter the order.
4.977 TC30010
Description
Multiple bill reference numbers can be found based on the customer ID and organization ID.
Scenario
Multiple bill reference number records are obtained when you query the C20 Link.
Access Channel
Web, USSD, API, STK
Possible Causes
Multiple bill reference number records are obtained when you query the C20 Link.
Procedure
Enter the bill reference number or delete redundant C20 Links from the database.

Copyright © Huawei
Mobile Money
4.978 TC30011
Description
The bill reference number is not found, and the database does not have the bill reference
number.
Scenario
In a pay bill transaction, the initiator does not enter a bill reference number.
Access Channel
Web, USSD, API
Possible Causes
The bill reference number cannot be found.
Procedure
Enter a bill reference number.
4.979 TC30012
Description
The bill number does not meet the third-party authentication rules.
Scenario
The third-party verification on a bill reference number fails in a pay bill transaction.
Access Channel
Web, USSD, API
Possible Causes
The bill number fails to be authenticated in the third-party system.
Procedure
Enter a correct bill number to be authenticated by the third-party system.

Copyright © Huawei
Mobile Money
4.980 TC30013
Description
The third-party system does not return an authentication result in a specified time period.
Scenario
In a pay bill transaction, the third-party verification times out.
Access Channel
Web, USSD, API
Possible Causes
The AG returns a message indicating a third-party authentication timeout.
Procedure
Send the Pay Bill request again.
4.981 TC30065
Description
Identity types of both parties in the transaction should be Organization.
Scenario
Either party of an internal transfer transaction is not an organization.
Access Channel
STK, USSD, API, Web
Possible Causes
Identity types of parties in a transaction are incorrect.
Procedure
Check the organization configuration and whether the packet content is correct.

Copyright © Huawei
Mobile Money
4.982 TC30066
Description
The transaction initiator already has a transaction to be confirmed.
Scenario
When a transaction is initiated, there is already a transaction in the system waiting to be
confirmed by the initiator through the SMS service.
Access Channel
Web, USSD
Possible Causes
The transaction initiator already has a transaction to be confirmed.
Procedure
Confirm the existing transaction first.
4.983 TC30067
Description
Enter Y or Y PIN as the confirmation message configured in the reason type.
Scenario
The SMS content is invalid.
Access Channel
USSD
Possible Causes
The SMS content is invalid.
Procedure
Enter the correct SMS confirmation message.

Copyright © Huawei
Mobile Money
4.984 TC30068
Description
The value or status of the PIN in the SMS confirmation message is incorrect.
Scenario
Access Channel
USSD
Possible Causes
Procedure
Enter the correct PIN. If the problem persists, ask an SP operator to reset the PIN or change
the PIN status.
4.985 TC30070
Description
The SMS confirmation notification receiver configured in the reason type has no MSISDN.
Scenario
The SMS confirmation notification receiver has no MSISDN.
Access Channel
USSD
Possible Causes
The SMS confirmation notification receiver configured in the reason type has no MSISDN.
Procedure
Modify the reason type and set the SMS confirmation notification receiver to an identity that
has an MSISDN.

Copyright © Huawei
Mobile Money
4.986 TC30071
Description
When the account to be queried does not exist, the system displays an error message and
reverses the transaction.
Scenario
When the account to be queried does not exist, the system displays an error message and
reverses the transaction.
Access Channel
Web
Possible Causes
The account to be queried does not exist.
Procedure
Verify that the account to be queried exists.
4.987 TC30072
Description
The customer check rule is empty in the third-party organization.
Scenario
Failed to obtain the check rule of organization for the C2B transaction.
Access Channel
Web, USSD, API
Possible Causes
The customer check rule is empty in the third-party organization.
Procedure
Configure the customer check rule in the product attribute of the third-party organization.

Copyright © Huawei
Mobile Money
4.988 TC30073
Description
The business check rule is empty in the third-party organization.
Scenario
Failed to obtain the check rule of organization for the B2B transaction.
Access Channel
Web, USSD, API, STK
Possible Causes
The business check rule is empty in the third-party organization.
Procedure
Configure the business check rule in the product attribute of the third-party organization.
4.989 TC30074
Description
An SMS confirmation notification receiver must be configured in the reason type.
Scenario
The SMS confirmation notification receiver is not configured.
Access Channel
USSD
Possible Causes
No SMS confirmation notification receiver is configured in the reason type.
Procedure
Modify the reason type and configure the SMS confirmation notification receiver.

Copyright © Huawei
Mobile Money
4.990 TC30075
Description
Failed to configure the KYC field because the entry is not found in the data dictionary.
Scenario
Failed to configure the KYC field because the entry is not found in the data dictionary.
Access Channel
Web, STK, USSD, API
Possible Causes
The entry does not exist in the data dictionary.
Procedure
Verify whether the parameters are correctly set.
4.991 TC30076
Description
The initiator does not have the permission.
Scenario
The initiator does not have the permission to perform Query Balance or Query
Ministatement operations.
Access Channel
STK, USSD, API
Possible Causes
The initiator does not have the permission to perform Query Balance or Query
Ministatement operations.
Procedure
This operation cannot be performed because the initiator does not have the permission.

Copyright © Huawei
Mobile Money
4.992 TC30077
Description
There is no transaction to be confirmed in the system.
Scenario
Access Channel
USSD
Possible Causes
Procedure
Verify whether a transaction needs to be confirmed.
4.993 TC30087
Description
A confirmer sends the short message N to cancel a transaction.
Scenario
A confirmer sends the short message "N" to cancel a transaction.
Access Channel
USSD
Possible Causes
A confirmer sends the short message N to cancel a transaction.
Procedure
This exception message is displayed because a transaction is manually canceled. No further
processing is needed.

Copyright © Huawei
Mobile Money
4.994 TC30088
Description
The Cross-Bank Transfer Transaction Types system parameter is not configured.
Scenario
The transaction type ID for controlling account transfer cannot be obtained.
Access Channel
Web
Possible Causes
The Cross-Bank Transfer Transaction Types system parameter is not configured.
Procedure
1. Choose My Functions > Finance > Reconciliation Management > Finance
Parameter > System Parameter Items > Financial Transactions.
2. Configure the Cross-Bank Transfer Transaction Types parameter.
4.995 TC30090
Description
The {0} organization must subscribe to at least one automatic teller machine (ATM) product.
Scenario
The specified organization has not subscribed to any ATM product.
Access Channel
API
Possible Causes
The {0} organization has not subscribed to any ATM product.
Procedure
Subscribe to an ATM product for the organization.

Copyright © Huawei
Mobile Money
4.996 TC30091
Description
The {0} organization short code must exist in the system.
The {0} variable indicates a short code.
Scenario
The specified organization short code does not exist.
Access Channel
Web
Possible Causes
The {0} organization short code does not exist.
Procedure
Enter a valid organization short code.
4.997 TC30100
Description
Failed to generate summary information.
Scenario
Generating element information lists fails when summary information is obtained.
Access Channel
Web
Possible Causes
Failed to generate summary information.
Procedure
Send transaction center logs in the /log/debug/tc_debug.log to a Huawei engineer for fault
diagnosis.

Copyright © Huawei
Mobile Money
4.998 TC30101
Description
Failed to generate a description for a bulk task.
Scenario
Generating description of batch tasks fails when task description is obtained.
Access Channel
Web
Possible Causes
Failed to generate a description for a bulk task.
Procedure
diagnosis.
4.999 TC30102
Description
Failed to obtain the task execution result.
Scenario
Obtaining task execution results fails during the execution of the withdrawal transaction.
Access Channel
Web
Possible Causes
Failed to obtain the task execution result.
Procedure
diagnosis.

Copyright © Huawei
Mobile Money
4.1000 TC30104
Description
The PIN status is incorrect.
Scenario
Access Channel
USSD
Possible Causes
Procedure
Log in to the SP portal, view the information about an identity, choose Overview > Info, and
check the PIN status on the Security tab.
 If the PIN status is Pending Change, change the PIN by USSD, for example to
12345678.
 If the PIN status is Lock state, ask an SP operator to click the Unlock PIN button on the
identity information page to change the PIN status to Pending Change. Then change the
PIN by USSD.
4.1001 TC30105
Description
Concurrent transactions fail to be processed.
Scenario
Concurrent transactions fail to be processed.
Access Channel
Web, USSD
Possible Causes
A concurrency error occurred in the reentry process.
Procedure
Try again later.

Copyright © Huawei
Mobile Money
4.1002 TC30111
Description
The transaction of order ID {0} failed when reconciliation transactions are approved in bulk.
The {0} variable indicates an order ID.
Scenario
Reconciliation transaction approval is initiated on the portal.
Access Channel
Web
Possible Causes
The transaction of order ID {0} failed when reconciliation transactions are approved in bulk.
Procedure
Send the /log/debug/bcs_debug.log log file in the BCS module to a Huawei engineer for fault
locating.
4.1003 TC30112
Description
Entry {0} fails to be processed when reconciliation entries are processed on the portal in bulk.
The {0} variable indicates an entry ID.
Scenario
Reconciliation entry operations are initiated on the portal.
Access Channel
Web
Possible Causes
Entry {0} fails to be processed when reconciliation entries are processed on the portal in bulk.

Copyright © Huawei
Mobile Money
Procedure
locating.
4.1004 TC30113
Description
Order ID {0} fails to be processed when derivative transactions are manually initiated on the
portal in bulk.
Scenario
Derivative transactions are manually initiated on the portal.
Access Channel
Web
Possible Causes
Order ID {0} fails to be processed when derivative transactions are manually initiated on the
portal in bulk.
Procedure
locating.
4.1005 TC30114
Description
The reconciliation transaction log of order ID {0} does not exist.
Scenario
Reconciliation operations are initiated on the portal, and reconciliation transaction logs are not
found.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The reconciliation transaction log of order ID {0} does not exist.
Procedure
Send the /log/debug/bcs_debug.log file in the BCS to a Huawei engineer for error locating.
4.1006 TC30115
Description
The reconciliation transaction log of order ID {0} indicates that the reconciliation transaction
is in the {1} status and cannot be approved.
The {0} variable indicates an order ID, and the {1} variable indicates the status of the reconciliation
transaction log records.
Scenario
No approval operation can be initiated when the reconciliation transaction logs are not in the
to-be-approved status during manual approval of reconciliation transactions on the portal.
Access Channel
Web
Possible Causes
The reconciliation transaction log of order ID {0} indicates that the reconciliation transaction
is in the {1} status and cannot be approved.
Procedure
Enter an order ID whose reconciliation transaction is in the Pending Authorized status in the
transaction log.
4.1007 TC30116
Description
When a reversal transaction is initiated, the association relationship of the secondary
withdrawal transaction does not exist or is not in the Connected status.

Copyright © Huawei
Mobile Money
Scenario
The association of the phase-2 withdrawal transaction does not exist or the status is not
connected when you manually approve reconciliation transactions and initiate transaction
reverse on the portal.
Access Channel
Web
Possible Causes
When a reversal transaction is initiated, the association relationship of the secondary
withdrawal transaction does not exist or is not in the Connected status.
Procedure
Verify the reconciliation statements or contact a Huawei engineer for help.
4.1008 TC30117
Description
The transaction serial number of order ID {0} does not exist.
The {0} variable indicates the serial number.
Scenario
No information about the source transaction order can be obtained when the reconciliation
operation is initiated on the portal.
Access Channel
Web
Possible Causes
The transaction serial number of order ID {0} does not exist.
Procedure
Verify the reconciliation statements or contact a Huawei engineer for help.

Copyright © Huawei
Mobile Money
4.1009 TC30118
Description
The transaction type parameter is not configured at the system level for reconciliation
transactions.
Scenario
When a reconciliation transaction is initiated on the portal, the system parameter of
transaction type is not configured.
Access Channel
Web
Possible Causes
The transaction type parameter is not configured at the system level for reconciliation
transactions.
Procedure
Parameter > System Parameter Items > Financial Transactions.
2. Verify that all system parameters are correctly configured for reconciliation transactions.
4.1010 TC30119
Description
Transaction type {0} does not exist.
The {0} variable indicates the transaction type name.
Scenario
The transaction type does not exist when a reconciliation transaction is initiated on the portal.
Access Channel
Web
Possible Causes
Transaction type {0} does not exist.
Procedure
1. Choose My Functions > Core Configuration > Transaction Type.

Copyright © Huawei
Mobile Money
2. Add transaction type {0}.
4.1011 TC30120
Description
No bank card information is found based on the {0} control account.
The {0} variable indicates the SP control account.
Scenario
No bank card information is found based on the control account when a reconciliation
transaction is initiated on the portal.
Access Channel
Web
Possible Causes
No bank card information is found based on the {0} control account.
Procedure
1. Choose Search > Service Provider > Bank&Account > Bank Client.
2. Add the bank associated with the {0} control account.
4.1012 TC30121
Description
The secondary withdrawal transaction of the associated ID {0} does not exist.
The {0} variable indicates a link ID.
Scenario
When a derivative reconciliation transaction is initiated on the portal, the secondary
withdrawal transaction of the associated ID does not exist.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The secondary withdrawal transaction of the associated ID {0} does not exist.
Procedure
1. Choose My Functions > Finance > Process Withdrawal.
2. Enter an associated ID that has a secondary withdrawal transaction in the system.
4.1013 TC30122
Description
The secondary withdrawal transaction of the associated ID {0} is in the {1} status and does
not support the transaction.
The {0} variable indicates a link ID, and the {1} variable indicates the association relationship status.
Scenario
When a derivative reconciliation transaction is initiated on the portal, the status of the
secondary withdrawal transaction of the associated ID does not support the transaction.
Access Channel
Web
Possible Causes
The secondary withdrawal transaction of the associated ID {0} is in the {1} status and does
not support the transaction.
Procedure
1. Choose My Functions > Finance > Process Withdrawal.
2. Enter an associated ID that has a secondary withdrawal transaction in a valid status in the
system.
4.1014 TC30123
Description
The {0} reconciliation statement is in the {1} status and does not allow a new transaction to
be initiated.
The {0} variable indicates a reconciliation statement ID. The {1} variable indicates the status of a
reconciliation statement.

Copyright © Huawei
Mobile Money
Scenario
When a reconciliation transaction is initiated on the portal, the status of the reconciliation
statement does not allow a new transaction to be initiated.
Access Channel
Web
Possible Causes
The {0} reconciliation statement is in the {1} status and does not allow a new transaction to
be initiated.
Procedure
Enter the ID of a reconciliation statement in the No Action status.
4.1015 TC30124
Description
Account type instances configured for the bank interaction service {0} and reason type {1} do
not exist or are not associated with banks, and no new transaction can be initiated.
The {0} variable indicates the name of a bank interaction service. The {1} variable indicates the alias of
a reason type.
Scenario
When a new reconciliation transaction is initiated on the portal, the debit and credit account
types configured in the reason type are not associated with banks.
Access Channel
Web
Possible Causes
Account type instances configured for the bank interaction service {0} and reason type {1} do
not exist or are not associated with banks, and no new transaction can be initiated.
Procedure
1. Choose Search > Service Provider > Bank&Account > Bank Client.
2. Click Add to add bank information for the account.

Copyright © Huawei
Mobile Money
4.1016 TC30125
Description
Transaction serial number {0} does not exist, the transaction is not approved, or no electronic
funds transfer (EFT) file is exported for the transaction. No entry-related transaction can be
initiated.
Scenario
When a reconciliation entry transaction is initiated on the portal, the transaction record does
not exist, and entry-related transactions cannot be initiated.
Access Channel
Web
Possible Causes
Transaction serial number {0} does not exist, the transaction is not approved, or no EFT file is
exported for the transaction. No entry-related transaction can be initiated.
Procedure
1. Choose My Functions > Finance > Approve Finance Transactions.
2. Check whether the order is approved, and approve it if it has not been approved.
3. Choose My Functions > Finance > Reconciliation Management > EFT Export.
4. Check whether any EFT file needs to be exported for the bank. If there are EFT files to
be exported, export them.
4.1017 TC30126
Description
Transaction serial number {1} of entry {0} is associated with another entry, and the current
operation is not allowed.
The {0} variable indicates an entry ID. The {1} variable indicates an order ID.
Scenario
When a reconciliation entry transaction is initiated on the portal, the transaction serial number
corresponding to the current entry is associated with other entries.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
Transaction serial number {1} of entry {0} is associated with another entry, and the current
Procedure
Associate with other transactions.
4.1018 TC30127
Description
Transaction serial number {1} of entry {0} is associated with another entry of the same
transaction party, and the current operation is not allowed.
The {0} variable indicates an entry ID. The {1} variable indicates an order ID.
Scenario
When a reconciliation entry transaction is initiated on the portal, multiple reconciliation
details records are the same and cannot automatically match. Manual handling is required.
Access Channel
Web
Possible Causes
Transaction serial number {1} of entry {0} is associated with another entry of the same
transaction party, and the current operation is not allowed.
Procedure
Associate with other transactions.
4.1019 TC30128
Description
Entry {0} is in the {1} status and cannot be associated with other entries.
The {0} variable indicates an entry ID. The {1} variable indicates the identity status.

Copyright © Huawei
Mobile Money
Scenario
When a reconciliation entry transaction is initiated on the portal, the linked entry ID is not in
the Matched status.
Access Channel
Web
Possible Causes
Entry {0} is in the {1} status and cannot be associated with other entries.
Procedure
Associate with other entries.
4.1020 TC30129
Description
The withdrawal and control account transfer services do not support transaction reversal.
Scenario
When a reconciliation entry transaction is initiated on the portal, the withdrawal and control
account transfer services do not support transaction reverse.
Access Channel
Web
Possible Causes
Procedure
4.1021 TC30131
Description
Failed to upgrade the customer because the customer has one or more vouchers being
redeemed or authorized.

Copyright © Huawei
Mobile Money
Scenario
The customer to be upgraded has a voucher that is being processed.
Access Channel
Web
Possible Causes
Failed to upgrade the customer because the customer has one or more vouchers being
redeemed or authorized.
Procedure
Wait until all vouchers are redeemed or authorized and try again.
4.1022 TC30132
Description
The customer is not a registered customer during CCH transaction reversal.
Scenario
Access Channel
USSD
Possible Causes
Procedure
Select a registered customer or register the customer.
4.1023 TC30133
Description
The customer is not identified by the CCH operator during a CCH transaction reversal.
Scenario

Copyright © Huawei
Mobile Money
Access Channel
USSD
Possible Causes
Procedure
Identify the customer first.
4.1024 TC30134
Description
Account {0} has an incomplete transaction or a voucher to be redeemed.
The {0} variable indicates the alias of an account.
Scenario
When a scheduled task moves the balance out of a dormant account, the dormant account has
an incomplete transaction.
Access Channel
Web
Possible Causes
Account {0} has an incomplete transaction or a voucher to be redeemed.
Procedure
Please verify the transaction status of the account.
4.1025 TC30135
Description
No corresponding transaction type {0} is configured in the system parameter.
The {0} variable indicates a system parameter for configuring the transaction type.

Copyright © Huawei
Mobile Money
Scenario
When a scheduled task moves the balance out of a dormant account, no transaction type is
configured.
Access Channel
Web
Possible Causes
No corresponding transaction type {0} is configured in the system parameter.
Procedure
1. Choose My Functions > Operational Configuration > System Parameter > Dormant
Processing Parameters (Customers).
2. Configure the transaction type.
4.1026 TC30136
Description
When the system moves the balance out of a dormant account, the {0} transaction type does
not exist.
The {0} variable indicates the name of a transaction type.
Scenario
When the system moves the balance out of a dormant account, the transaction type does not
exist.
Access Channel
Web
Possible Causes
When the system moves the balance out of a dormant account, the {0} transaction type does
not exist.
Procedure
1. Choose My Functions > Operational Configuration > System Parameter > Dormant
Processing Parameters (Customers).
2. Verify that the transaction type exists.

Copyright © Huawei
Mobile Money
4.1027 TC30137
Description
Scenario
Access Channel
Web
Possible Causes
Procedure
Please configure the default SP operator.
4.1028 TC30138
Description
The account has no dormant record, and cannot be refunded.
Scenario
Access Channel
Web
Possible Causes
The account has no dormant record.
Procedure

Copyright © Huawei
Mobile Money
4.1029 TC30139
Description
Refunded operation failed because the account balance is 0.
Scenario
Access Channel
Web
Possible Causes
Procedure
The account has no balance and does not support refund.
4.1030 TC30140
Description
The account balance has been already moved to the Unclaimed account.
Scenario
The account balance has been moved to the Unclaimed account.
Access Channel
Web
Possible Causes
The account balance has been already moved to the Unclaimed account.
Procedure

Copyright © Huawei
Mobile Money
4.1031 TC30141
Description
The account has an incomplete refund transaction.
Scenario
Access Channel
Web
Possible Causes
Procedure
4.1032 TC30142
Description
Some balances of the account have not been moved to the SP control account.
Scenario
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
4.1033 TC30143
Description
The account balance has been already refunded.
Scenario
The account balance has been refunded.
Access Channel
Web
Possible Causes
The account balance has been already refunded.
Procedure
4.1034 TC30144
Description
The account does not need to be refunded.
Scenario
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
4.1035 TC30145
Description
There is no failed dormant transaction record.
Scenario
There is no failed dormant transaction record, and manual operation is not allowed.
Access Channel
Web
Possible Causes
There is no failed dormant transaction record.
Procedure
There is no failed dormant transaction record, and manual operation is not allowed.
4.1036 TC30146
Description
The balance in the account does not need to be moved to the SP holding account.
Scenario
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
4.1037 TC30147
Description
Bank {1} linked to entry {0} is inconsistent with bank {3} in order {2} to be linked to the
entry.
 The {0} variable indicates the ID of an entry.

 The {1} variable indicates the ID of the bank linked to the current entry.
 The {2} variable indicates the ID of the order to be linked.
 The {3} variable indicates the ID of the bank linked to an order.
Scenario
During the reconciliation process, the bank in an entry to be linked to an order is inconsistent
with the bank linked to the order.
Access Channel
Web
Possible Causes
Bank {1} linked to entry {0} is inconsistent with bank {3} in order {2} to be linked to the
entry.
Procedure
Please verify that the bank information is consistent.
4.1038 TC30148
Description
Process {0} does not support process status {1}, and clearing expired transactions is not
allowed.
The {0} variable indicates a process ID, such as 1.

The {1} variable indicates the status of a process.
Scenario
Clear expired transactions.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
Process {0} does not support process status {1}, and clearing expired transactions is not
allowed.
Procedure
This is a normal prompt. No troubleshooting is required.
4.1039 TC30150
Description
Enter a correct Password during the transaction process.
Scenario
The exception may occur in many transaction scenarios, for example, when the Password of a
transaction initiator fails to be authenticated.
Access Channel
Web
Possible Causes
The Password entered by the identity fails to be authenticated.
Procedure
Enter a correct Password and initiate the transaction again.
4.1040 TC30151
Description
When the system sends an airtime top-up transaction request to a third-party system, the
mobile network operator (MNO) sends back a transaction failure message.
Scenario
During a buy airtime transaction, the MNO sends back a transaction failure message when the
system sends a buy airtime transaction request to a third-party system.
Access Channel
USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
When the system sends an airtime top-up transaction request to a third-party system, the
MNO sends back a transaction failure message.
Procedure
Check information in the log/debug/tc_debug.log file and verify whether an error has
occurred when the system interacts with the third-party system.
4.1041 TC30152
Description
Operation failed. When an operator initiates a refund operation for a dormant account, the
receiver number is set to the number of the operator.
Scenario
When an operator initiates a refund operation for a dormant account, the receiver number is
set to the number of the operator.
Access Channel
Web
Possible Causes
When an operator initiates a refund operation for a dormant account, the receiver number is
set to the number of the operator.
Procedure
Verify that the receiver number is correctly configured.
4.1042 TC30153
Description
If the reason type does not support partial reversal, the specified reversal amount must be
equal to the transaction amount.
Scenario
If the reason type of a transaction to be reversed does not support partial reversal, the
specified reversal amount must be equal to the transaction amount; otherwise, the system
reports this error.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, API
Possible Causes
The specified reversal amount is not equal to the transaction amount.
Procedure
Verify that the specified reversal amount is equal to the transaction amount.
4.1043 TC30154
Description
If the reason type does not support full reversal, the specified reversal amount must be less
than the transaction amount.
Scenario
If the reason type of a transaction to be reversed does not support full reversal, the specified
reversal amount must be less than the transaction amount; otherwise, the system reports this
error.
Access Channel
Web, STK, API
Possible Causes
The specified reversal amount is equal to the transaction amount.
Procedure
Verify that the specified reversal amount is less than the transaction amount.
4.1044 TC30155
Description
The MSISDN of the customer does not exist or is not in the specified number segment.
Scenario
When a customer is created or when the MSISDN of a customer is modified, the specified
MSISDN does not exist or is not in the specified number segment.

Copyright © Huawei
Mobile Money
Access Channel
Web, USSD
Possible Causes
The specified MSISDN does not exist or is not in the specified number segment.
Procedure
1. Verify whether the customer exists.
2. Verify that the MSISDN is in the number segment specified for non-registered
customers.
3. If the MSISDN is not in the specified number segment, change the MSISDN to a number
in the specified number segment.
4.1045 TC30156
Description
The transaction is failed. The Account Type in the Reason Type is inconsistent with that
corresponding to the specific transaction account.
Scenario
When execute SP E-money Withdraw transaction, the Account Type in the Reason Type is
inconsistent with that of specific transaction account.
Access Channel
Web
Possible Causes
The transaction is failed. The Account Type in the Reason Type is inconsistent with that
corresponding to the specific transaction account.
Procedure
Please confirm whether Account Type is correct or check the configuration of Reason Type.
4.1046 TC30158
Description
No receiving channel is configured for the confirmation message in the reason type.

Copyright © Huawei
Mobile Money
Scenario
The system reports this error if a transaction needs to be confirmed by a participant but no
receiving channel is configured for the confirmation message.
Access Channel
USSD, STK
Possible Causes
No receiving channel is configured for the confirmation message in the reason type.
Procedure
Verify that a receiving channel is configured for the confirmation message in the reason type.
4.1047 TC30179
Description
Failed to perform a transfer transaction for the current account.
Scenario
No transfer transaction is required because the amount to be moved during the revenue
settlement is 0.
Access Channel
Web
Possible Causes
The amount to be moved during the revenue settlement is 0.
Procedure
No transfer is needed because the amount to be moved is 0.
4.1048 TC30180
Description
Failed to perform a transfer transaction for the current account.
Scenario
An account used during revenue settlement for an organization cannot be a shared account.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
Account {0} is a shared account.
{0}: indicates account number.
Procedure
Verify revenue settlement configurations for the organization and delete shared accounts from
the configurations.
4.1049 TC30181
Description
Failed to reverse the transaction.
Scenario
Reverse an e-money withdrawal transaction for an SP or organization.
Access Channel
Web
Possible Causes
Transaction reversal failed because the status of a derivative transaction is invalid.
Procedure
If there is a derivative transaction, verify whether the derivative transaction is in the Pending
Authorized status.
4.1050 TC30182
Description
The transaction does not need to be cleared.
Scenario
An expired reconciliation transaction is automatically cleared.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The transaction is not in the Pending Authorized state and does not need to be cleared.
Procedure
N/A
4.1051 TC30183
Description
No data is found.
Scenario
Process a reconciliation report.
Access Channel
Web
Possible Causes
The Variance report contains no data and cannot be exported.
Procedure
Change the query period.
4.1052 TC30189
Description
MSISDN {0} of the customer is incorrect or does not exist.
0: MSISDN
Scenario
When a customer is upgraded and an unredeemed voucher is reversed, no customer is found
based on the MSISDN.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
MSISDN {0} of the customer is incorrect or does not exist.
Procedure
Verify that the MSISDN is correct.
4.1053 TC30190
Description
The PIN entered for the transaction is incorrect.
Scenario
The PIN specified by a CCH operator for a service is incorrect.
Access Channel
USSD, STK
Possible Causes
The PIN is incorrect.
Procedure
Verify that the PIN entered by the CCH operator is correct.
4.1054 TC30191
Description
The entered currency type does not match the supported currency type.
Scenario
The currency type entered during an international money transfer (IMT) transaction does not
match the supported currency type.
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
The entered currency type does not match the supported currency type.
Procedure
Enter a correct currency type.
4.1055 TC30192
Description
The entered transaction amount is invalid.
Scenario
The transaction amount entered during an IMT transaction is invalid.
Access Channel
Web, STK, USSD, API
Possible Causes
The specified amount cannot contain decimal digits after being converted to the basic unit.
Procedure
Check the entered transaction amount.
4.1056 TC30193
Description
The entered customer type is not supported.
Scenario
The customer type entered during an IMT transaction is not supported.
Access Channel
API
Possible Causes

Copyright © Huawei
Mobile Money
Procedure
Check the entered customer type.
4.1057 TC30194
Description
The entered KYC information does not match reason type requirements.
Scenario
The KYC information entered during an IMT transaction does not match reason type
requirements.
Access Channel
API
Possible Causes
The entered KYC information does not match reason type requirements.
Procedure
Check the entered KYC information.
4.1058 TC30195
Description
The commission reason type parameter is not configured at the system level.
Scenario
When a commission transaction is initiated on the portal, the commission reason type is not
configured at the system level.
Access Channel
Web
Possible Causes
The commission transaction type system control parameter is not configured.

Copyright © Huawei
Mobile Money
Procedure
Commission Reason Type.
2. Verify that the commission transaction parameters are configured at the system level.
4.1059 TC30197
Description
The type of the entered input number is invalid.
Scenario
The input number entered during an IMT transaction is not an MSISDN.
Access Channel
API
Possible Causes
The type of the entered input number is invalid.
Procedure
Check the type of the entered input number.
4.1060 TC30198
Description
The entered MSISDN is out of the valid number segment range.
Scenario
The MSISDN entered during an IMT transaction is out of the valid number segment range.
Access Channel
API
Possible Causes
The entered MSISDN is out of the valid number segment range.
Procedure
Check whether the entered MSISDN is within the valid number segment range.

Copyright © Huawei
Mobile Money
4.1061 TC30199
Description
The AG sends a reply indicating transaction cancellation.
Scenario
The AG sends a reply indicating transaction cancellation, and the BCS cancels the transaction.
Access Channel
API
Possible Causes
The AG sends a reply indicating transaction cancellation.
Procedure
The BCS cancels the transaction.
4.1062 TC30200
Description
The IMT transaction has expired.
Scenario
The IMT transaction has expired, and a new IMT transaction needs to be initiated.
Access Channel
API
Possible Causes
The IMT transaction has expired.
Procedure
Initiate a new IMT transaction.

Copyright © Huawei
Mobile Money
4.1063 TC30201
Description
Additional data is incorrectly configured.
Scenario
Additional data is incorrectly configured for an IMT transaction.
Access Channel
API
Possible Causes
Additional data is incorrectly configured.
Procedure
Check additional data configuration.
4.1064 TC30202
Description
The IMT transaction has been cancelled.
Scenario
Access Channel
API
Possible Causes
Procedure
Check transaction information.

Copyright © Huawei
Mobile Money
4.1065 TC30203
Description
The IMT transaction status is incorrect.
Scenario
Access Channel
API
Possible Causes
Procedure
Check transaction status.
4.1066 TC30204
Description
The IMT transaction input parameters are incorrect.
Scenario
Access Channel
API
Possible Causes
Procedure
Check the IMT transaction input parameters.

Copyright © Huawei
Mobile Money
4.1067 TC30205
Description
The IMT validation transaction does not exist.
Scenario
When performing a Credit transaction, the HomeSend finds that the IMT validation
Access Channel
API
Possible Causes
The IMT validation transaction does not exist.
Procedure
Check whether an IMT validation transaction has been performed.
4.1068 TC30206
Description
The IMT transaction request has already been submitted.
Scenario
When a third-party submits an IMT transaction request, the request has already been
submitted.
Access Channel
API
Possible Causes
The IMT transaction request has already been submitted.
Procedure
Submit an IMT transaction request only once.

Copyright © Huawei
Mobile Money
4.1069 TC30207
Description
The transaction ID in the account information in the IMT credit request is inconsistent with
the actual ID.
Scenario
The transaction ID in the account information in the IMT credit request initiated by a third
party is inconsistent with the actual ID.
Access Channel
API
Possible Causes
The transaction ID in the account information in the IMT credit request is inconsistent with
the actual ID.
Procedure
Check whether the transaction ID in the account information in the IMT credit request is
inconsistent with the actual ID.
4.1070 TC30211
Description
Verification on additional data from a third party or input channel fails. Detailed information:
{0}
{0}: indicates an error message to be returned if additional data fails a validation rule. The message is
configured in the addition data validation rule.
Scenario
Verification on additional data from a third party fails during an IMT transaction.
Access Channel
API
Possible Causes
Verification on additional data from a third party or input channel fails. Detailed information:
{0}

Copyright © Huawei
Mobile Money
Procedure
Check additional data configuration.
4.1071 TC30212
Description
The length of the reconciliation file path exceeds the upper limit.
Scenario
A reconciliation report is generated.
Access Channel
Web
Possible Causes
The length of the reconciliation file path {0} is {1} bytes, which exceeds the length upper
limit {2} bytes.
{0}: reconciliation file path.

{1}: reconciliation file path length.
{2}: reconciliation file path length upper limit.
Procedure
Check and modify the Report Root Path parameter as follows:
1. Log in to the SP portal as the SP operator.
2. Choose My Functions > Operational Configuration > System Parameter.
3. Shorten the length of Report Root Path in SFTP Parameters.
4.1072 TC30213
Description
The interaction between the system and the third party is abnormal.
Scenario
In the IMT HomeSend flow of interaction between the IMT and the third party, a third party
initiates a request to cancel the transaction. This error occurs if the credit transaction record is
not generated and cannot be found.

Copyright © Huawei
Mobile Money
Access Channel
API
Possible Causes
The credit transaction record is not generated.
Procedure
Check the logs of interaction between the system and the third party.
4.1073 TC30216
Description
The transaction has been canceled because the number of Receive Money Request sending
attempts has reached the upper limit.
Scenario
In the IMT WU process, the M-Pesa system will proactively send a Receive Money Request
to the WU. If the message returned from the WU indicates an exception, the M-Pesa will send
the request message again. If message returned from the WU indicates an exception again, the
system throws this exception.
Access Channel
API
Possible Causes
An exception has occurred when the system interacts with the WU.
Procedure
Verify the interaction process between the system and the WU.
4.1074 TC30217
Description
The transaction does not comply with limit rule {0}.
{0}: indicates the name of a limit rule, such as Maximum Transaction Count Credit.

Copyright © Huawei
Mobile Money
Scenario
The error reports during the IMT transaction. The IMT transaction does not comply with a
limit rule.
Access Channel
API
Possible Causes
The transaction does not comply with limit rule {0} which indicates the maximum transaction
times.
Procedure
Verify that the transaction complies with limit rule {0} and try again.
4.1075 TC30218
Description
{0}: indicates the name of a limit rule, such as Maximum Total Credit.
Scenario
The error reports during the IMT transaction. The IMT transaction does not comply with a
limit rule.
Access Channel
API
Possible Causes
The transaction does not comply with limit rule {0} which indicates the maximum transaction
amount.
Procedure
Verify that the transaction complies with limit rule {0} and try again.

Copyright © Huawei
Mobile Money
4.1076 TC30219
Description
Identity {0} has not subscribed to a product that contains the {1} service as the {2} party.
{0}: indicates the identifier of an identity, for example, organization short code.
{1}: indicates a service name.
{2}: indicates a transaction role, for example, credit.
Scenario
When a transaction is initiated, the credit party in the transaction has not subscribed to a
product that contains a role of the current service.
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
2. Search the identity according to the identity type (Choose Search > Customer or
Search > Organization, select identity {0}, click Details, and enter the Customer Info
or Organization Info page).
3. Select Product tab page and click Edit icon.
4. Click Add to subscribe to the product that contains {1} service for the identity {0}.
4.1077 TC30220
Description
{0}: indicates the identifier of an identity, for example, organization short code.
{1}: indicates a service name.
{2}: indicates a transaction role, for example, debit.
Scenario
When a transaction is initiated, the debit party in the transaction has not subscribed to a
product that contains a role of the current service.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
Search > Organization, select identity {0}, click Details, and enter the Customer Info
or Organization Info page).
3. Select Product tab page and click Edit icon.
4.1078 TC30221
Description
Scenario
The customer type entered during an IMT validation transaction is not supported.
Access Channel
API
Possible Causes
Procedure
4.1079 TC30222
Description
Scenario
The customer type entered during an IMT credit transaction is not supported.

Copyright © Huawei
Mobile Money
Access Channel
API
Possible Causes
Procedure
4.1080 TC30238
Description
The account is closed and new account is not allowed to be created for the identity.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
New account is not allowed to be created based on the setting of a system parameter.
Procedure
Check the system parameter settings.
4.1081 TC30239
Description
Failed to match a reason type because the Expression factor does not match.
Scenario
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
When a reason type is matched, the Expression factor does not match.
Procedure
2. Choose My Functions > Core Configuration > Advanced Configuration > Reason
Type to enter the Reason Type configuration page.
3. Query by Reason Type Name to verify whether the reason type is correctly configured.
4.1082 TC30240
Description
Failed to match a reason type because the Channel factor does not match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Channel factor does not match.
Procedure
4.1083 TC30241
Description
Failed to match a reason type because the Hierarchy factor does not match.
Scenario

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Hierarchy factor does not match.
Procedure
4.1084 TC30242
Description
Failed to match a reason type because the Initiator Type factor does not match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Initiator Type factor does not match.
Procedure
4.1085 TC30243
Description
Failed to match a reason type because the Identity Type factor of the debit party does not
match.

Copyright © Huawei
Mobile Money
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Identity Type factor of the debit party does not match.
Procedure
4.1086 TC30244
Description
Failed to match a reason type because the Identity Subtype factor of the debit party does not
match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Identity Subtype factor of the debit party does not
match.
Procedure

Copyright © Huawei
Mobile Money
4.1087 TC30245
Description
Failed to match a reason type because the Account Type factor of the debit party does not
match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Account Type factor of the debit party does not match.
Procedure
4.1088 TC30246
Description
Failed to match a reason type because the Identity Status factor of the debit party does not
match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Identity Status factor of the debit party does not match.
Procedure

Copyright © Huawei
Mobile Money
4.1089 TC30247
Description
Failed to match a reason type because the Identity Model factor of the debit party does not
match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Identity Model factor of the debit party does not match.
Procedure
4.1090 TC30248
Description
Failed to match a reason type because the Is Registered by Agent factor of the debit party
does not match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Is Registered by Agent factor of the debit party does not
match.

Copyright © Huawei
Mobile Money
Procedure
4.1091 TC30249
Description
Failed to match a reason type because the Segment factor of the debit party does not match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Segment factor of the debit party does not match.
Procedure
4.1092 TC30250
Description
Failed to match a reason type because the Specific Identity factor of the debit party does not
match.
Scenario
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
When a reason type is matched, the Specific Identity factor of the debit party does not match.
Procedure
4.1093 TC30251
Description
Failed to match a reason type because the Top Organization factor of the debit party does not
match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Top Organization factor of the debit party does not
match.
Procedure
4.1094 TC30252
Description
Failed to match a reason type because the Trust Level factor of the debit party does not
match.
Scenario

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Trust Level factor of the debit party does not match.
Procedure
4.1095 TC30253
Description
Failed to match a reason type because the Identity Type factor of the credit party does not
match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Identity Type factor of the credit party does not match.
Procedure
4.1096 TC30254
Description
Failed to match a reason type because the Identity Subtype factor of the credit party does not
match.

Copyright © Huawei
Mobile Money
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Identity Subtype factor of the credit party does not
match.
Procedure
4.1097 TC30255
Description
Failed to match a reason type because the Account Type factor of the credit party does not
match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Account Type factor of the credit party does not match.
Procedure

Copyright © Huawei
Mobile Money
4.1098 TC30256
Description
Failed to match a reason type because the Identity Status factor of the credit party does not
match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Identity Status factor of the credit party does not match.
Procedure
4.1099 TC30257
Description
Failed to match a reason type because the Identity Model factor of the credit party does not
match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Identity Model factor of the credit party does not match.
Procedure

Copyright © Huawei
Mobile Money
4.1100 TC30258
Description
Failed to match a reason type because the Is Registered by Agent factor of the credit party
does not match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Is Registered by Agent factor of the credit party does not
match.
Procedure
4.1101 TC30259
Description
Failed to match a reason type because the Segment factor of the credit party does not match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Segment factor of the credit party does not match.

Copyright © Huawei
Mobile Money
Procedure
4.1102 TC30260
Description
Failed to match a reason type because the Specific Identity factor of the credit party does not
match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Specific Identity factor of the credit party does not
match.
Procedure
4.1103 TC30261
Description
Failed to match a reason type because the Top Organization factor of the credit party does
not match.
Scenario
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
When a reason type is matched, the Top Organization factor of the credit party does not
match.
Procedure
4.1104 TC30262
Description
Failed to match a reason type because the Trust Level factor of the credit party does not
match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Trust Level factor of the credit party does not match.
Procedure
4.1105 TC30263
Description
Failed to match a reason type because the BO factor does not match.
Scenario

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the BO factor does not match.
Procedure
4.1106 TC30264
Description
Failed to initiate the transaction because the {0} core product subscribed to by the customer
does not have associated link type information.
{0} indicates the core product ID.
Scenario
When a transaction is initiated, the core product subscribed to by the customer does not have
associated link type information.
Access Channel
Web, STK, USSD, API
Possible Causes
The {0} core product subscribed to by the customer does not have associated link type
information.
Procedure
Activate the FSI Provisioning product which contains the FSI Core product for the customer.
4.1107 TC30265
Description
Failed to initiate the transaction because there is no associated link between the customer and
organization.

Copyright © Huawei
Mobile Money
Scenario
When a transaction is initiated, there is no associated link between the customer and
organization.
Access Channel
Web, STK, USSD, API
Possible Causes
There is no associated link between the customer and organization.
Procedure
4.1108 TC30266
Description
Failed to initiate the transaction because the status of the link between the customer and
organization is not Active.
Scenario
When a transaction is initiated, the status of the link between the customer and organization is
not Active.
Access Channel
Web, STK, USSD, API
Possible Causes
The status of the link between the customer and organization is not Active.
Procedure
4.1109 TC30267
Description
An identity has initiated transaction {0} which is in the Pending Authorized or Authorized
state.

Copyright © Huawei
Mobile Money
{0} indicates order ID.
Scenario
An identity has initiated the transaction which is in the Pending Authorized or Authorized
state during a transaction.
Access Channel
Web, STK, USSD, API
Possible Causes
An identity has initiated transaction {0} which is in the Pending Authorized or Authorized
state.
Procedure
Wait until the current transaction is complete before initiating another one.
4.1110 TC30268
Description
Failed to initiate the transaction because the customer has not read the terms and conditions.
Scenario
When a transaction is initiated, the customer has not read the terms and conditions.
Access Channel
Web, STK, USSD, API
Possible Causes
The customer has not read the terms and conditions.
Procedure
Read the terms and conditions before initiating a transaction.
4.1111 TC30269
Description
Reason type {0} associated with the second loan transaction does not exist.

Copyright © Huawei
Mobile Money
{0} indicates reason type ID.
Scenario
Reason type associated with the second loan transaction does not exist during a loan
transaction.
Access Channel
Web, STK, USSD, API
Possible Causes
Reason type {0} associated with the second loan transaction does not exist.
Procedure
Choose My Functions > Core Configuration > Reason Type to configure the existing
associated reason type.
4.1112 TC30270
Description
The {0} FSI transaction is in the success state, the result in the message returned by the FI is
failure.
Scenario
The FSI transaction is in the success state, the result in the message returned by the FI is
failure.
Access Channel
Web, STK, USSD, API
Possible Causes
failure.
Procedure
N/A

Copyright © Huawei
Mobile Money
4.1113 TC30271
Description
The {0} FSI transaction is in the failure state, the result in the message returned by the FI is
success.
Scenario
The FSI transaction is in the failure state, the result in the message returned by the FI is
success.
Access Channel
Web, STK, USSD, API
Possible Causes
success.
Procedure
N/A
4.1114 TC30272
Description
success.
Scenario
The FSI transaction is in the success state, the result in the message returned by the FI is
success.
Access Channel
Web, USSD, STK, API
Possible Causes
success.

Copyright © Huawei
Mobile Money
Procedure
N/A
4.1115 TC30273
Description
failure.
Scenario
The FSI transaction is in the failure state, the result in the message returned by the FI is
failure.
Access Channel
Web, USSD, STK, API
Possible Causes
failure.
Procedure
N/A
4.1116 TC30274
Description
The first loan transaction has succeeded. The second loan transaction does not exist or is not
completed.
Scenario
completed during a loan transaction.
Access Channel
Web, USSD, STK, API

Copyright © Huawei
Mobile Money
Possible Causes
completed.
Procedure
N/A
4.1117 TC30275
Description
Customer {0} has not subscribed to the FSI Core product.
{0} indicates customer's public name.
Scenario
Customer has not subscribed to the FSI Core product during a transaction.
Access Channel
Web, USSD, STK, API
Possible Causes
Customer {0} has not subscribed to the FSI Core product.
Procedure
4.1118 TC30276
Description
The status of the link between the customer and organization can only be Suspended or
Closed.
Scenario
The status of the link between the customer and organization can only be Suspended or
Closed during a FSI payout transaction.
Access Channel
Web, USSD, STK, API

Copyright © Huawei
Mobile Money
Possible Causes
The status of the link between the customer and organization is not Suspended or Closed.
Procedure
Enter the customer details page and change the link status to Closed.
4.1119 TC30277
Description
Confirmation transaction {0} has timed out.
Scenario
Confirmation transaction has timed out.
Access Channel
Web, USSD, STK, API
Possible Causes
Confirmation transaction {0} has timed out.
Procedure
N/A
4.1120 TC30278
Description
Transaction {0} has timed out. The two loan transactions have succeeded, the FI returns a
message indicating that the processing result is a failure.
Scenario
Transaction has timed out. The two loan transactions have succeeded, the FI returns a

Copyright © Huawei
Mobile Money
Access Channel
Web, USSD, STK, API
Possible Causes
Transaction {0} has timed out. The two loan transactions have succeeded, the FI returns a
Procedure
N/A
4.1121 TC30279
Description
The link type of the customer does not have FI account information.
Scenario
The link type of the customer does not have FI account information during a transaction.
Access Channel
Web, USSD, STK, API
Possible Causes
The link type of the customer does not have FI account information.
Procedure
1. Choose My Functions > Core Configuration > FSI > FSI Link Type and configure
link information.
2. When FSI is activated, the FI returns the FI account information.
4.1122 TC30280
Description
FI Account Info attribute {0} does not exist during a transaction.
{0} indicates attribute code.
Scenario
FI Account Info attribute does not exist during a transaction.

Copyright © Huawei
Mobile Money
Access Channel
Web, USSD, STK, API
Possible Causes
FI Account Info attribute {0} does not exist during a transaction.
Procedure
Enter an FI Account Info attribute that exists.
4.1123 TC30281
Description
FI Account Info attribute {0} is invalid during a transaction.
{0} indicates attribute code.
Scenario
FI Account Info attribute is invalid during a transaction.
Access Channel
Web, USSD, STK, API
Possible Causes
FI Account Info attribute {0} is invalid during a transaction.
Procedure
Enter a valid value for the FI Account Info attribute.
4.1124 TC30282
Description
Transaction {0} has timed out. The first loan transaction has succeeded, the second loan
transaction has failed, and the result in the message returned by the FI is failure.

Copyright © Huawei
Mobile Money
Scenario
Transaction has timed out. The first loan transaction has succeeded, the second loan
Access Channel
Web, USSD, STK, API
Possible Causes
Transaction {0} has timed out. The first loan transaction has succeeded, the second loan
Procedure
N/A
4.1125 TC30283
Description
Transaction {0} has timed out and failed. The result in the message returned by the FI is
failure.
Scenario
Transaction has timed out and failed. The result in the message returned by the FI is failure.
Access Channel
Web, USSD, STK, API
Possible Causes
Transaction {0} has timed out and failed. The result in the message returned by the FI is
failure.
Procedure
N/A

Copyright © Huawei
Mobile Money
4.1126 TC30284
Description
Transaction {0} has timed out and succeeded. The result in the message returned by the FI is
failure.
Scenario
Transaction has timed out and succeeded. The result in the message returned by the FI is
failure.
Access Channel
Web, USSD, STK, API
Possible Causes
Transaction {0} has timed out and succeeded. The result in the message returned by the FI is
failure.
Procedure
N/A
4.1127 TC30285
Description
The insurance number is incorrect in a transaction request.
Scenario
Access Channel
Web, USSD, STK, API
Possible Causes
Procedure
Enter a correct insurance number.

Copyright © Huawei
Mobile Money
4.1128 TC30286
Description
The {0} transaction is manually cancelled by an FI.
Scenario
An FSI transaction is manually cancelled by an FI.
Access Channel
Web, USSD, STK, API
Possible Causes
The {0} transaction is manually cancelled by an FI.
Procedure
N/A
4.1129 TC30287
Description
Failed to match a reason type because the Identity Relationship factor does not match.
Scenario
Access Channel
Web, USSD, STK, API
Possible Causes
When a reason type is matched, the Identity Relationship factor does not match.
Procedure

Copyright © Huawei
Mobile Money
4.1130 TC30288
Description
Transaction failed because the follow-up loan transfer has failed.
Scenario
FSI loan service.
Access Channel
USSD, STK
Possible Causes
Transaction failed because the follow-up loan transfer has failed.
Procedure
Verify the cause why the second loan transaction failed. Send the /log/debug/bcs_debug.log
file on the BCS to a Huawei engineer for error location.
4.1131 TC30292
Description
A customer chooses to cancel a transaction after receiving a USSD Push prompt.
Scenario
When performing a Send Money or Pay Bill transaction, the transaction initiator chooses to
cancel the transaction after receiving a USSD Push prompt.
Access Channel
STK
Possible Causes
A customer chooses to cancel a transaction after receiving a USSD Push prompt.
Procedure
N/A

Copyright © Huawei
Mobile Money
4.1132 TC30293
Description
A customer does not enter any information until timeout after receiving a USSD Push prompt.
Scenario
When performing a Send Money or Pay Bill transaction, a customer does not enter any
information until timeout after receiving a USSD Push prompt.
Access Channel
STK
Possible Causes
A customer does not enter any information until timeout after receiving a USSD Push prompt.
Procedure
N/A
4.1133 TC30294
Description
A customer chooses to forcibly cancel a transaction after receiving a USSD Push prompt.
Scenario
When performing a Send Money or Pay Bill transaction, the transaction initiator chooses to
forcibly cancel the transaction after receiving a USSD Push prompt.
Access Channel
STK
Possible Causes
A customer chooses to forcibly cancel a transaction after receiving a USSD Push prompt.
Procedure
N/A

Copyright © Huawei
Mobile Money
4.1134 TC30295
Description
An unknown exception has occurred after a customer receives a USSD Push prompt.
Scenario
When performing a Send Money or Pay Bill transaction, an unknown exception has occurred
after a customer receives a USSD Push prompt.
Access Channel
STK
Possible Causes
An unknown exception has occurred after a customer receives a USSD Push prompt.
Procedure
N/A
4.1135 TC30311
Description
The {0} multi-instance SP account cannot be parsed.
{0}: indicates the type of an account.
Scenario
When an SP operator performs an operation such as Buy Airtime, no multi-instance account is
found.
Access Channel
Web
Possible Causes
 The Charge Receive Account extensive attribute is not configured for the current reason
type.
 The organization is not associated with any SP account.
Procedure
1. Verify whether extensive attributes of the reason type are correctly configured.

Copyright © Huawei
Mobile Money
2. Verify whether an organization is associated with multi-instance SP account.
4.1136 TC30316
Description
Failed to match a reason type because the Account Type factor of the initiator party does not
match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Account Type factor of the initiator does not match.
Procedure
4.1137 TC30317
Description
Failed to match a reason type because the Account Type factor of the receiver does not
match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Account Type factor of the receiver does not match.

Copyright © Huawei
Mobile Money
Procedure
4.1138 TC30318
Description
Failed to match a reason type because the Identity Model factor of the initiator party does not
match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Identity Model factor of the initiator does not match.
Procedure
4.1139 TC30319
Description
Failed to match a reason type because the Identity Model factor of the receiver does not
match.
Scenario
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
When a reason type is matched, the Identity Model factor of the receiver does not match.
Procedure
4.1140 TC30320
Description
Failed to match a reason type because the Identity Status factor of the initiator party does not
match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Identity Status factor of the initiator does not match.
Procedure
4.1141 TC30321
Description
Failed to match a reason type because the Identity Status factor of the receiver does not
match.
Scenario

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Identity Status factor of the receiver does not match.
Procedure
4.1142 TC30322
Description
Failed to match a reason type because the Identity Subtype factor of the initiator party does
not match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Identity Subtype factor of the initiator does not match.
Procedure
4.1143 TC30323
Description
Failed to match a reason type because the Identity Subtype factor of the receiver does not
match.

Copyright © Huawei
Mobile Money
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Identity Subtype factor of the receiver does not match.
Procedure
4.1144 TC30324
Description
Failed to match a reason type because the Identity Type factor of the initiator party does not
match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Identity Type factor of the initiator does not match.
Procedure

Copyright © Huawei
Mobile Money
4.1145 TC30325
Description
Failed to match a reason type because the Identity Type factor of the receiver does not match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Identity Type factor of the receiver does not match.
Procedure
4.1146 TC30326
Description
Failed to match a reason type because the Is Registered by Agent factor of the initiator party
does not match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Is Registered by Agent factor of the initiator does not
match.
Procedure

Copyright © Huawei
Mobile Money
4.1147 TC30327
Description
Failed to match a reason type because the Is Registered by Agent factor of the receiver does
not match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Is Registered by Agent factor of the receiver does not
match.
Procedure
4.1148 TC30328
Description
Failed to match a reason type because the Segment factor of the initiator party does not
match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Segment factor of the initiator does not match.

Copyright © Huawei
Mobile Money
Procedure
4.1149 TC30329
Description
Failed to match a reason type because the Segment factor of the receiver does not match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Segment factor of the receiver does not match.
Procedure
4.1150 TC30330
Description
Failed to match a reason type because the Special Identity factor of the initiator party does
not match.
Scenario
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
When a reason type is matched, the Special Identity factor of the initiator does not match.
Procedure
4.1151 TC30331
Description
Failed to match a reason type because the Special Identity factor of the receiver does not
match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Special Identity factor of the receiver does not match.
Procedure
4.1152 TC30332
Description
Failed to match a reason type because the Top Organization factor of the initiator party does
not match.
Scenario

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Top Organization factor of the initiator does not match.
Procedure
4.1153 TC30333
Description
Failed to match a reason type because the Top Organization factor of the receiver does not
match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Top Organization factor of the receiver does not match.
Procedure
4.1154 TC30334
Description
Failed to match a reason type because the Trust Level factor of the initiator party does not
match.

Copyright © Huawei
Mobile Money
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Trust Level factor of the initiator does not match.
Procedure
4.1155 TC30335
Description
Failed to match a reason type because the Trust Level factor of the receiver does not match.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
When a reason type is matched, the Trust Level factor of the receiver does not match.
Procedure

Copyright © Huawei
Mobile Money
4.1156 TC30340
Description
The {0} account is incorrectly configured.
{0}: indicates the type of an account.
Scenario
When an SP operator executes an operation such as pay MNO, the type of an account is
incorrectly configured as hotspot account.
Access Channel
Web
Possible Causes
Account {0} cannot be configured as a hotspot account.
Procedure
Configure the account type as real-time account.
4.1157 TC30341
Description
The identity's KYC information is incorrectly configured.
Scenario
When an identity uses a service that has integrated the customer name search (CNS) function,
a KYC field is used to indicate whether the CNS function will be used. If this field is not
configured, the system reports an error.
Access Channel
STK
Possible Causes
The identity's KYC information is incorrectly configured.
Procedure
Verify the identity's KYC configurations.

Copyright © Huawei
Mobile Money
4.1158 TC30351
Description
The selected organization does not exist or has been closed.
Scenario
During a claw-back transaction, a selected organization has been closed.
Access Channel
Web
Possible Causes
The selected organization does not exist or has been closed.
Procedure
Verify that the organization exists and is not closed.
4.1159 TC30352
Description
The {1} short code in the confirmation message of the {0} transaction from a third-party
does not belong to the primary, receiver, credit, or debit party.
{0}: indicates the ID of a transaction.

{1}: indicates the short code in a confirmation message.
Scenario
The short code in the transaction confirmation message from a third-party system does not
belong to the primary, receiver, credit, or debit party.
Access Channel
Web, STK, USSD, API
Possible Causes
The {1} short code in the confirmation message of the {0} transaction from a third-party
does not belong to the primary, receiver, credit, or debit party.
Procedure
Verify that organization {1} has the permission to confirm transaction {0}.

Copyright © Huawei
Mobile Money
4.1160 TC30354
Description
Failed to decrypt a file during account reconciliation.
Scenario
Decryption failed due to incorrect configurations or environment errors during account
reconciliation.
Access Channel
Web
Possible Causes
Decryption failed during account reconciliation.
Procedure
Check whether the decryption configuration is correct.
4.1161 TC30355
Description
Failed to encrypt a file during account reconciliation.
Scenario
Encryption failed due to incorrect configurations or environment errors during account
reconciliation.
Access Channel
Web
Possible Causes
Encryption failed during account reconciliation.
Procedure
Check whether the encryption configuration is correct.

Copyright © Huawei
Mobile Money
4.1162 TC30358
Description
When an operator queries the account balance of an organization, the ReceiverParty
parameter must be empty or set to the organization to which the operator belongs if
targetOrgList is specified.
Scenario
When an organization operator queries the organization balance through the API, the
ReceiverParty parameter is set to an incorrect value.
Access Channel
API
Possible Causes
The value of the ReceiverParty parameter is incorrect.
Procedure
Leave the ReceiverParty parameter empty or set it to the organization to which the operator
belongs.
4.1163 TC30359
Description
The value {0} in targetOrgList is invalid. The restriction on the value varies based on the
type of the initiator of the balance query operation:
 SP operator: targetOrgList can contain only short codes of the organizations to be
queried.
 Organization operator: targetOrgList can contain only the short code of the home
organization and child organizations of the organization operator.
{0}: indicates the short code of an organization to be queried.
Scenario
 When an SP operator queries balances about organizations through the API, the
targetOrgList parameter contains a short code that does not belong to the organizations
to be queried.
 When an organization operator queries balances about organizations through the API, the
targetOrgList parameter contains a short code that does not belong to the home
organization of the organization operator and the child organizations of the home
organization.

Copyright © Huawei
Mobile Money
Access Channel
API
Possible Causes
The value {0} in targetOrgList is invalid. The restriction on the value varies based on the
type of the initiator of the balance query operation:
 SP operator: targetOrgList can contain only short codes of the organizations to be
queried.
 Organization operator: targetOrgList can contain only the short code of the home
organization and child organizations of the organization operator.
Procedure
 When an SP operator queries balances about organizations, verify that the targetOrgList
parameter contains only short codes of the organizations to be queried.
 When an organization operator queries balances about organizations, verify that the
targetOrgList parameter contains only the short code of the home organization of the
organization operator and short codes of child organizations of the home organization.
4.1164 TC30360
Description
The number of organizations to be queried has exceeded the upper limit {0}.
{0}: indicates the maximum number of organizations that can be queried.
Scenario
When an organization or SP operator queries the organization balance through the API, the
number of organizations to be queried has exceeded the upper limit.
Access Channel
API
Possible Causes
The number of organizations to be queried has exceeded the upper limit {0}.
Procedure
Verify that the number of organizations to be queried does not exceed the upper limit.

Copyright © Huawei
Mobile Money
4.1165 TC30361
Description
When an SP operator queries the balance of any organization, the targetOrgList parameter
must not be set to ALL, ALLSUBSTORE, or Null.
Scenario
When an SP operator queries the organization balance through the API, the value of the
targetOrgList parameter is incorrect.
Access Channel
API
Possible Causes
The value of the targetOrgList parameter is incorrect.
Procedure
Set the targetOrgList parameter to the short code of an organization.
4.1166 TC30362
Description
When an SP operator queries the account balance, the ReceiverParty parameter must be set
to an SP or organization.
Scenario
When an SP operator queries the organization balance through the API, the ReceiverParty
parameter is set to an incorrect value.
Access Channel
API
Possible Causes
The value of the ReceiverParty parameter is incorrect.
Procedure
Change the ReceiverParty parameter to an SP or organization.

Copyright © Huawei
Mobile Money
4.1167 TC30363
Description
The {0} transaction cannot be cancelled.
{0}: indicates the ID of a transaction, such as 0000000000010007.
Scenario
On the review transaction page, an SP operator cannot cancel a transaction that has been
associated with a bank statement.
Access Channel
Web
Possible Causes
The {0} transaction has already been associated with a bank statement.
Procedure
Process the transaction using the account reconciliation function.
4.1168 TC30364
Description
Organization short code {0} in the TargetOrgList must be unique.
{0}: indicates an organization short code which is not unique.
Scenario
When an SP or organization operator performs a Query Balance operation through the API, a
short code in the TargetOrgList is not unique.
Access Channel
API
Possible Causes
In the TargetOrgList, organization short code {0} is not unique.

Copyright © Huawei
Mobile Money
Procedure
Verify that organization short code {0} in the TargetOrgList is unique.
4.1169 TC30365
Description
The current service cannot be performed because no reconciliation transaction is found.
Scenario
During reconciliation, no transaction type is obtained or the configured transaction type is not
a reconciliation transaction.
Access Channel
Web
Possible Causes
The current service cannot be performed because no reconciliation transaction is found.
Procedure
1. Choose My Functions > Finance > Reconciliation Management > Reconciliation
Configuration, and click Details to enter the Edit Reconciliation Configuration page.
2. Correctly configure the Bank Statement Processing Mode field.
4.1170 TC30366
Description
Operation failed. The associated entry does not exist in the New Entries list.
Scenario
When an SP operator processes a duplicate reconciliation statement, the entry associated with
the statement does not exist in the New Entries list.
Access Channel
Web
Possible Causes
The associated entry does not exist in the New Entries list.

Copyright © Huawei
Mobile Money
Procedure
Check whether the associated entry exists in the New Entries list.
4.1171 TC30374
Description
Operator {1} of {0} is the same as the current operator {2}. Operation failed.
{0}: indicates step x, such as initiating a withdrawal transaction.

{1}: indicates the operator of step x.
{2}: indicates an operator.
Scenario
During a reconciliation transaction, any two operators involved in the financial transaction
and reconciliation process must be different.
Access Channel
Web
Possible Causes
Operator {1} of {0} is the same as the current operator {2}. Operation failed.
Procedure
Change the approver to another operator.
4.1172 TC30375
Description
Operation failed. During control account transfer, order {0} has already been linked to two
entries.
{0}: indicates order ID.
Scenario
During control account transfer, the selected order has already been linked to two entries, and
cannot be linked.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
Operation failed. During control account transfer, the selected order has already been linked
to two entries.
Procedure
1. Choose My Functions > Finance > Bank Reconciliation > Transfer Entries.
2. Cancel existing entry links of the selected order.
4.1173 TC30380
Description
An error occurred during routing information query based on the RecipientMSISDN.
Scenario
The RecipientMSISDN entered when a customer sends a quotation query request to the
HomeSend matches no routing information.
Access Channel
USSD, STK, API
Possible Causes
The RecipientMSISDN matches no routing information.
Procedure
Verify that the RecipientMSISDN and routing information configurations are correct.
4.1174 TC30381
Description
No IMT organization was found based on routing information.
Scenario
No organization information is found when a customer sends a quotation query request to the
HomeSend.

Copyright © Huawei
Mobile Money
Access Channel
USSD, STK, API
Possible Causes
Organization configurations are incorrect in the routing information table.
Procedure
 Verify that organization configurations are incorrect in the routing information table.
 Verify that IMT provider configurations are correct.
4.1175 TC30382
Description
Failed. Your account is being screened as part of registration. Please try again after {0}.
{0}: monitoring expiration date specified by ScreeningEndDate.
Scenario
A customer is within the monitoring period and is not allowed to initiate the transaction.
Access Channel
USSD, STK, API
Possible Causes
The transaction initiator is within the monitoring period {0}.
Procedure
Contact customer service personnel.
4.1176 TC30383
Description
The AG failed to retry, and the failure cause is as follows: Not Processed.
Scenario
The AG failed to retry, and the failure cause is "Not Processed."

Copyright © Huawei
Mobile Money
Access Channel
USSD, STK, API
Possible Causes
The AG failed to retry, and the failure cause is as follows: Not Processed.
Procedure
N/A
4.1177 TC30384
Description
The AG failed to retry, and the failure cause is as follows: Request Inconclusive.
Scenario
The AG failed to retry, and the failure cause is "Request Inconclusive."
Access Channel
USSD, STK, API
Possible Causes
The AG failed to retry, and the failure cause is as follows: Request Inconclusive.
Procedure
N/A
4.1178 TC30385
Description
Failed. The recipient account is unknown. Please review the details about the receivers and try
again.
Scenario
A third party failed to process IMT Request Quote. The corresponding external error code is
ER0010 (Unknown receiver).
Access Channel
USSD, STK, API

Copyright © Huawei
Mobile Money
Possible Causes
The AG receives information about ER0010 (Unknown receiver).
Procedure
N/A
4.1179 TC30386
Description
Failed. {0} is unable to process your request. Please try again.
{0}: system used by the remittance receiver, that is, M-PASE
Scenario
A third party failed to process IMT Request Quote. The corresponding external error code is
not ER0010 (Unknown receiver).
Access Channel
USSD, STK, API
Possible Causes
The AG receives information about an error code except ER0010 (Unknown receiver).
Procedure
N/A
4.1180 TC30387
Description
Failed. The recipient account is unable to accept your transfer. Please contact the receiver.
Scenario
A third party failed to process an IMT Transfer abroad transaction. The corresponding
external error code is ER0013, ER0021, ER0024, or ER0025 (receiver account issue).
Access Channel
USSD, STK, API

Copyright © Huawei
Mobile Money
Possible Causes
The AG receives external error code ER0013, ER0021, ER0024, or ER0025 (receiver account
issue).
Procedure
N/A
4.1181 TC30388
Description
The reason type failed the verification because the extra charge type for dynamically
obtaining a charge is not configured.
Scenario
The extra charge type for dynamically obtaining a charge must be configured in the reason
type for IMT Transfer abroad transactions.
Access Channel
USSD, STK, API
Possible Causes
The extra charge type for dynamically obtaining a charge must be configured in the reason
type for IMT Transfer abroad transactions.
Procedure
Verify that the reason type for IMT Transfer abroad transactions is correctly configured.
4.1182 TC30389
Description
The following message is returned when a third party queries transaction status: rejected.
Scenario
The message "rejected" is returned when a third party queries transaction status during IMT
transfer abroad transactions.
Access Channel
USSD, STK, API

Copyright © Huawei
Mobile Money
Possible Causes
Procedure
4.1183 TC30398
Description
Verifying the KYC information failed.
Scenario
This error code is generated when the KYC information of the request party does not obey
KYC verification rules specified in the related reason type.
Access Channel
Web, STK, USSD, API
Possible Causes
The KYC information of the request party does not obey KYC verification rules specified in
the related reason type.
Procedure
Select a correct identity for the transaction.
4.1184 TC30399
Description
Verifying the entered KYC information failed.
Scenario
This error code is generated when the request party enters incorrect KYC information.
Access Channel
Web, STK, USSD, API
Possible Causes
The request party enters incorrect KYC information.

Copyright © Huawei
Mobile Money
Procedure
Enable the request party to enter correct KYC information.
4.1185 TC30400
Description
Failed to create the unregistered customer because KYC information is not left blank.
Scenario
This error code is generated when an OTC transaction requesting party that is not a system
user and does not leave KYC information blank attempts to create an unregistered customer.
Access Channel
Web, STK, USSD, API
Possible Causes
Failed to create the unregistered customer because KYC information is not left blank.
Procedure
Create a registered or lite customer.
4.1186 TC30401
Description
The input secret code is incorrect.
Scenario
The secret codes input during voucher redeeming and application are different.
Access Channel
USSD, STK Menu
Possible Causes
The secret code is incorrect.
Procedure
Enter the correct secret code, namely, secret code entered during voucher application.

Copyright © Huawei
Mobile Money
4.1187 TC30402
Description
The secret code does not match the regular expression {0}.
{0} indicates the regular expression rule of the secret code.
Scenario
The secret code does not match the regular expression.
Access Channel
USSD, STK Menu
Possible Causes
The secret code failed to match the regular expression.
Procedure
Enter the secret code that match the regular expression.
4.1188 TC30403
Description
The secret code length is less than {0}.
{0} indicates the minimum length of the secret code defined in the system parameter.
Scenario
The secret code length is less than the minimum length defined in the system parameter
Secret Code Rule.
Access Channel
USSD, STK Menu
Possible Causes
The secret code length is less than the lower limit.
Procedure
Enter the secret code whose length is greater than or equal to the lower limit.

Copyright © Huawei
Mobile Money
4.1189 TC30404
Description
The secret code length is greater than {0}.
{0} indicates the maximum length of the secret code defined in the system parameter.
Scenario
The secret code length is greater than the maximum length defined in the system parameter
Secret Code Rule.
Access Channel
USSD, STK Menu
Possible Causes
The secret code length is greater than the upper limit.
Procedure
Enter the secret code whose length is less than or equal to the upper limit.
4.1190 TC30405
Description
The system does not support the entered currency.
Scenario
During transaction initiation, the currency entered in a transaction request is not supported by
the system.
Access Channel
Web, STK, USSD, API
Possible Causes
The currency entered in a transaction request is not supported by the system.
Procedure
Verify that the currency entered in the transaction request is supported by the system.

Copyright © Huawei
Mobile Money
4.1191 TC30406
Description
The corresponding reason type does not support the entered currency.
Scenario
During transaction initiation, the currency entered in a transaction request does not match that
configured in the corresponding reason type.
Access Channel
Web, STK, USSD, API
Possible Causes
The currency entered in a transaction request does not match that configured in the
corresponding reason type.
Procedure
Verify that the entered currency is configured in the corresponding reason type.
4.1192 TC30407
Description
Transaction {0} fails due to risk control.
{0}: order ID.
Scenario
Risk control is required for common transactions.
Access Channel
Web, STK, USSD, API
Possible Causes
Transaction {0} fails due to risk control.
Procedure
The risk control system considers that transaction {0} is risky, and therefore the transaction
cannot be initiated.

Copyright © Huawei
Mobile Money
4.1193 TC30408
Description
The KYC information whose verification is supported is blank.
Scenario
The KYC information whose verification is supported by the bulk payment service is blank.
Access Channel
Web
Possible Causes
The KYC information whose verification is supported is blank.
Procedure
2. Choose My Functions > Operational Configuration > System Parameter > Bulk
Task > Bulk B2C Payment Validation KYC.
4.1194 TC30409
Description
The KYC field whose name is {1} in the KYC group whose name is {0} does not exist in the
KYC information whose verification is supported.
{0} indicates KYC group name.

{1} indicates KYC field name.
Scenario
A KYC field in a KYC group does not exist in the KYC information whose verification is
supported by the bulk payment service.
Access Channel
Web
Possible Causes
The KYC field whose name is {1} in the KYC group whose name is {0} does not exist in the
KYC information whose verification is supported.

Copyright © Huawei
Mobile Money
Procedure
2. Choose My Functions > Operational Configuration > System Parameter > Bulk
Task > Bulk B2C Payment Validation KYC.
4.1195 TC30410
Description
The account whose account type is {1} in identity {0} is not found.
The {0} variable indicates identity type.

The {1} variable indicates account type.
Scenario
The account in identity is not found during a transaction.
Access Channel
Web, STK, USSD, API
Possible Causes
The account whose account type is {1} in identity {0} does not exist.
Procedure
4.1196 TC30414
Description
Voucher generation fails because the number of times vouchers are generated exceeds {0},
which is the specified upper limit.
{0} indicates voucher code generator limit.
Scenario
In the voucher generation service, the number of times vouchers are generated exceeds the
specified upper limit.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
Voucher generation fails because the number of times vouchers are generated exceeds {0},
which is the specified upper limit.
Procedure
1. Log in to the SP portal as an SP operator. Choose My Functions > Operational
Configuration > System Parameter > Voucher > Voucher Code Generator Limit.
Change the specified upper limit.
2. Obtain log/debug/tc_debug.log for fault diagnosis.
4.1197 TC30416
Description
The length of the LanguageCode parameter in the transaction request message exceeds the
upper limit.
Scenario
The length of the LanguageCode parameter in the BCS request message head sent from the
AG NE exceeds the upper limit.
Access Channel
STK, API, USSD
Possible Causes
The length of the LanguageCode parameter in the BCS request message head sent from the
AG NE exceeds the upper limit.
Procedure
Check whether the LanguageCode parameter in the transaction request message is valid.
Change the value and initiate the transaction again.
4.1198 TC30417
Description
When a reason type is matched, the Hierarchy Level factor of the credit party does not
match.

Copyright © Huawei
Mobile Money
Scenario
All transaction operations that need to match reason type.
Access Channel
Web
Possible Causes
When a reason type is matched, the Hierarchy Level factor of the credit party does not
match.
Procedure
4.1199 TC30418
Description
When a reason type is matched, the Hierarchy Level factor of the debit party does not match.
Scenario
All transaction operations that need to match reason type.
Access Channel
Web
Possible Causes
When a reason type is matched, the Hierarchy Level factor of the debit party does not match.
Procedure

Copyright © Huawei
Mobile Money
4.1200 TC30419
Description
The notification channel for sending the SMS confirmation message due to the reason type
{0} must be SMS.
{0} indicates the reason type name.
Scenario
The notification channel for sending the SMS confirmation message due to the reason type is
not SMS during the EVC transactions.
Access Channel
Web
Possible Causes
The notification channel for sending the SMS confirmation message due to the reason type
{0} is not SMS.
Procedure
3. Query by Reason Type Name to verify whether the SMS confirmation message is
correctly configured and the notification channel is SMS.
4.1201 TC30420
Description
The SMS recipient number is not configured for identity {0}.
{0} indicates the identity name.
Scenario
The SMS recipient number is not configured for identity during the electronic voucher center
(EVC) transactions.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The SMS recipient number is not configured for identity {0}.
Procedure
2. Choose Search to enter the corresponding identity page. On the details page, select KYC
information and set Notification Receiving MSISDN.
4.1202 TC30421
Description
The number of requested vouchers is greater than the maximum number of vouchers.
Scenario
Access Channel
Web
Possible Causes
Procedure
Reset the maximum number of vouchers to a value greater than the number of requested
vouchers.
4.1203 TC30422
Description
The voucher signature is incorrect.
Scenario
Parameters are tempered with when voucher information is queried on the PGW payment
page.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
Parameters are tempered with, leading to signature inconsistency.
Procedure
Do not allow parameter changes including location changes during voucher query.
4.1204 TC30423
Description
The entered terminal number is incorrect.
Scenario
When an SP operator initiates a masked number query request, a number segment must be
configured for the specified terminal number and map an MNO. If the mapping is not
configured, this error is reported.
Access Channel
Web
Possible Causes
The terminal number segment is set incorrectly.
Procedure
1. Enter a correct number and try later.
2. If the error persists, log in to the SP portal as an SP operator and configure a number
segment.
4.1205 TC30424
Description
Masked number is invalid.
Scenario
This error is reported when an SP operator enters incorrect masked number to query terminal
numbers.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
Masked number is incorrect.
Procedure
Enter correct masked number and try again.
4.1206 TC30425
Description
The system does not support masked number.
Scenario
This error is reported when the recharge number is masked number during the EVC
transaction.
Access Channel
Web, STK, USSD, API
Possible Causes
The recharge number is a masked number.
Procedure
Ensure that the value transferred by the RechargedMSISDN parameter is a real number, or
choose My Functions > Operational Configuration > System Parameter > Transaction >
Top-up Support Masked Number and change the system control parameter to support
masked number.
4.1207 TC30426
Description
Failed to apply for the OTC voucher.
Scenario
This error is reported when the voucher is applied for the PGW OTC payment.
Access Channel
PGW

Copyright © Huawei
Mobile Money
Possible Causes
The voucher type in the OTC application is incorrect. The possible causes are as follows:
 The validity period of the applied voucher type is shorter than the minimum validity
period specified by PGW OTC Voucher.
 The voucher type is not associated with an mount.
 The maximum number of voucher types is less than 1.
Procedure
Check whether the voucher type is correctly set. Ensure that:
 The validity period of the applied voucher type is longer than the minimum validity
period specified by PGW OTC Voucher.
 The voucher type is associated with an amount.
 The maximum number of voucher types is greater than 0.
4.1208 TC30427
Description
The voucher amount does not match.
Scenario
This error is reported when the voucher is redeemed but the requested voucher amount has
been tempered with.
Access Channel
Web
Possible Causes
The requested voucher amount has been tempered with.
Procedure
Change the voucher amount to the requested amount.
4.1209 TC30430
Description
Accumulator {0} does not exist or is not an entity-level one.
{0} indicates an accumulator name.

Copyright © Huawei
Mobile Money
Scenario
This error occurs when the accumulator does not exist or is not an entity-level one during the
charging of common transactions.
Access Channel
USSD, SMS, STK, Web
Possible Causes
Accumulator {0} does not exist or is not an entity-level one.
Procedure
1. Choose My Functions > Operational Configuration > Detail Ops Configuration >
Charge Profile.
2. Search for the specific charge profile and charge rule and change the accumulator in the
customized function configured in the charge rule to an entity-level accumulator.
4.1210 TC30431
Description
The accumulation entity cannot be obtained based on the accumulation role.
Scenario
This error occurs when the accumulation entity cannot be obtained based on the accumulation
type during the charging of common transaction.
Access Channel
USSD, SMS, STK, Web
Possible Causes
The accumulation entity cannot be obtained based on the accumulation role.
Procedure
Charge Profile.
2. Search for the specific charge profile and charge rule and change the accumulation role
in the customized function configured in the charge rule.

Copyright © Huawei
Mobile Money
4.1211 TC30432
Description
Period SN {0} is incorrect. Currently, only the current period 0 and the previous period -1 is
supported.
{0} indicates a period SN.
Scenario
This error occurs when the period SN is incorrect during the charging of common
transactions.
Access Channel
USSD, SMS, STK, Web
Possible Causes
Period SN {0} is incorrect. Currently, only the current period 0 and the previous period -1 is
supported.
Procedure
Charge Profile.
2. Search for the specific charge profile and charge rule and change the period SN in the
customized function configured in the charge rule to 0 or -1.
4.1212 TC30433
Description
Failed to request the third-party system when an airtime top-up transaction is initiated.
Scenario
This error is reported when the system fails to request the third-party system during an airtime
top-up transaction is initiated.
Access Channel
Web, USSD, STK, API
Possible Causes
Failed to request the third-party system when an airtime top-up transaction is initiated.

Copyright © Huawei
Mobile Money
Procedure
Verify that the requested URL is correct and the network connection is normal.
4.1213 TC30434
Description
The accumulator failed to be locked. The possible cause is that the same identity is using the
same transaction accumulator.
Scenario
This concurrent conflict error is reported when the identity in the EVC transaction is
executing another transaction that references the same accumulator.
Access Channel
Web, STK, USSD, API
Possible Causes
The same identity is executing another transaction that references the same accumulator.
Procedure
Wait till the other transaction is completed.
4.1214 TC30435
Description
The transaction cannot be reversed.
Scenario
This error is reported after an SP operator clicks the button for approving a transaction when
the SP operator reviews the reversal transaction of the Send Money to Unregistered Customer
transaction but the voucher has already been exchanged.
Access Channel
Web
Possible Causes
The voucher has been exchanged or has associated transactions.

Copyright © Huawei
Mobile Money
Procedure
Cancel the reversal operation.
4.1215 TC30436
Description
The currency of account {0} is different from the transaction currency.
Scenario
This error is reported if the account currency is different from the transaction currency during
a common BCS transaction.
Access Channel
Web, STK, USSD, API
Possible Causes
The currency of account {0} is different from the transaction currency.
Procedure
Select an account whose currency is the same as the transaction currency.
4.1216 TC30437
Description
When a transaction is initiated, the specified account does not belong to the identity of {0}.
{0} indicates a service role. For example, initiator, receiver.
Scenario
This error is reported if the specified account does not belong to the service role during a
common BCS transaction.
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
When a transaction is initiated, the specified account does not belong to the identity of {0}.
Procedure
Select an account belonging to the service role to initiate a transaction.
4.1217 TC30438
Description
The credit and debit parties in a multi-instance Intra Account Transfer transaction must belong
to the same identity.
Scenario
This error is reported when the credit and debit parties in a multi-instance Intra Account
Transfer transaction belong to different identites.
Access Channel
Web, USSD, STK, API
Possible Causes
The credit and debit parties in a multi-instance Intra Account Transfer transaction belong to
different identites.
Procedure
Ensure that the multi-instance accounts in the multi-instance Intra Account Transfer
transaction belong to the same identity.
4.1218 TC30439
Description
The Initiator parameter is not carried in the request.
Scenario
This error is reported when transaction details are queried by Receipt No. but the Initiator
parameter is not carried in the request.
Access Channel
STK, USSD, SMS

Copyright © Huawei
Mobile Money
Possible Causes
The Initiator parameter is not carried in the request.
Procedure
Ensure that the request carries the Initiator parameter and the parameter is correctly set.
4.1219 TC30440
Description
The initiator is not an organization operator.
Scenario
This error is reported when transaction details are queried by Receipt No. but the initiator is
not an organization operator.
Access Channel
STK, USSD, SMS
Possible Causes
The initiator is not an organization operator.
Procedure
Ensure that the initiator is an organization operator.
4.1220 TC30441
Description
The Receipt No. parameter is not carried in the request.
Scenario
This error is reported when transaction details are queried by Receipt No. but the Receipt No.
parameter is not carried in the request.
Access Channel
STK, USSD, SMS
Possible Causes
The Receipt No. parameter is not carried in the request.

Copyright © Huawei
Mobile Money
Procedure
Ensure that the request carries the Receipt No. parameter and the parameter is correctly set.
4.1221 TC30442
Description
The transaction whose details are queried by Receipt No. does not exist.
Scenario
This error is reported when transaction details are queried by Receipt No. but the queried
Access Channel
STK, USSD, SMS
Possible Causes
The transaction whose details are queried by Receipt No. does not exist.
Procedure
Ensure that the Receipt No. parameter is correctly set and the transaction corresponding to
Receipt No. exists.
4.1222 TC30443
Description
The query scenario does not meet the system restriction conditions.
Scenario
This error is reported when transaction details are queried by Receipt No. but the query
scenario does not meet the system restriction conditions.
Access Channel
STK, USSD, SMS
Possible Causes
The query scenario does not meet the system restriction conditions.

Copyright © Huawei
Mobile Money
Procedure
The transaction details cannot be queried.
4.1223 TC30444
Description
When the system sends an off-net transaction request to a third-party system, the third-party
system sends back a transaction failure response.
Scenario
This error is reported if the system sends an off-net request to a third-party system but the
third-party system sends back a transaction failure response.
Access Channel
Web, USSD, API
Possible Causes
When the system sends an off-net transaction request to a third-party system, the third-party
system sends back a transaction failure response.
Procedure
Check information in the log/debug/tc_debug.log file and check whether an error has
occurred when the system interacts with the third-party system.
4.1224 TC30445
Description
The organization surplus revenue is less than the expected surplus revenue.
Scenario
This error is reported when an SP or organization operator initiates a partial revenue
calculation request but the calculated organization surplus revenue is less than the expected
surplus revenue.
Access Channel
Web
Possible Causes
The organization surplus revenue is less than the expected surplus revenue.

Copyright © Huawei
Mobile Money
Procedure
Enter a new expected surplus revenue.
4.1225 TC30446
Description
Failed to generate the report. Select a time later than the time {0} when the report is
successfully generated the last time.
{0} indicates the time when the reconciliation report is successfully generated the last time.
Scenario
When an SP operator generates a reconciliation report, the time selected in the End Date of
Summary dialog box that is displayed is earlier than the time when the reconciliation report is
successfully generated the last time.
Access Channel
Web
Possible Causes
The reconciliation report of the selected time has been generated before.
Procedure
Select another end time.
4.1226 TC30447
Description
Failed to generate the report. Select a time earlier than {1}.
{1} indicates a time selected in the last operation.
Scenario
When an SP operator generates a reconciliation report, the data amount queried in the
specified time range exceeds the maximum.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The data amount queried in the specified time range exceeds the maximum {0}.
{0} indicates the maximum data amount can be displayed in a reconciliation report.
Procedure
Select another end time.
4.1227 TC30448
Description
Failed to process the transaction. The transaction configuration is inconsistent.
Scenario
This error is reported when transaction configuration inconsistency occurs because the
configuration is modified during transaction processing.
Access Channel
Web
Possible Causes
The transaction configuration is inconsistent.
Procedure
Re-initiate the transaction.
4.1228 TC30449
Description
The entered receiver account does not exist or has been deregistered.
Scenario
This error is reported during voucher application if the entered receiver account does not exist
or has been deregistered.
Access Channel
Web, USSD

Copyright © Huawei
Mobile Money
Possible Causes
The account does not exist or is deregistered.
Procedure
Enter a correct receiver account.
4.1229 TC30450
Description
The status of the entered account is {0} instead of active.
{0} indicates the entered account status.
Scenario
This error is reported during voucher application if the status of the entered receiver account
is incorrect.
Access Channel
Web, USSD
Possible Causes
The status of the receiver account entered during voucher application is incorrect.
Procedure
Enter a correct account or correct the account status.
4.1230 TC30451
Description
The product has already been subscribed.
Scenario
This error is reported when a service purchase transaction is executed but the specified
product has already been subscribed.
Access Channel
API

Copyright © Huawei
Mobile Money
Possible Causes
The product has already been subscribed.
Procedure
Ensure that the product to be subscribed has not been subscribed.
4.1231 TC30452
Description
The customer's status is invalid.
Scenario
This error is reported when a service purchase transaction is executed but the customer's
status is invalid.
Access Channel
API
Possible Causes
The customer's status is invalid.
Procedure
Change the customer's status to a valid one.
4.1232 TC30453
Description
The MSISDN does not belong to a prepaid subscriber.
Scenario
This error is reported when the MSISDN does not belong to a prepaid subscriber.
Access Channel
API
Possible Causes
The MSISDN does not belong to a prepaid subscriber.

Copyright © Huawei
Mobile Money
Procedure
Enter another MSISDN or register the subscriber first.
4.1233 TC30454
Description
The subscriber does not exist.
Scenario
This error is reported when the subscriber does not exist.
Access Channel
API
Possible Causes
The subscriber does not exist.
Procedure
Enter another subscriber.
4.1234 TC30455
Description
The request has been accepted and processed.
Scenario
This error is reported when the The request has been accepted and processed.
Access Channel
API
Possible Causes
The request has been accepted and processed.
Procedure
Do not send the request again.

Copyright © Huawei
Mobile Money
4.1235 TC30456
Description
The product does not exist or is not applicable to the subscriber.
Scenario
This error is reported when the product does not exist or is not applicable to the subscriber.
Access Channel
API
Possible Causes
The product does not exist or is not applicable to the subscriber.
Procedure
Subscribe to a product that is applicable to the subscriber.
4.1236 TC30457
Description
The account adjustment amount of a non-overdraft account cannot cross 0.
Scenario
This error is reported when an SP operator adjusts a non-overdraft account but the account
adjustment range crosses 0.
Access Channel
Web
Possible Causes
The account adjustment amount of the non-overdraft account crosses 0.
Procedure
Change the account adjustment amount.

Copyright © Huawei
Mobile Money
4.1237 TC30458
Description
The status of the account to be adjusted is invalid.
Scenario
This error is reported when the status of the account to be adjusted is invalid.
Access Channel
Web
Possible Causes
The status of the account to be adjusted is invalid.
Procedure
Select another account.
4.1238 TC30459
Description
The approver cannot be the same as the initiator during balance adjustment.
Scenario
This error is reported when the approver is the same as the initiator during balance
adjustment.
Access Channel
Web
Possible Causes
The approver cannot be the same as the initiator during balance adjustment.
Procedure
Enable another operator to approve the task.

Copyright © Huawei
Mobile Money
4.1239 TC30460
Description
The identity whose type is {0} cannot be the credit party of an inter-network transaction.
{0} indicates an identity type.
Scenario
This error is reported when the identity type of the credit party of an inter-network transaction
does not comply with the requirements.
Access Channel
Web
Possible Causes
The identity whose type is {0} cannot be the credit party of an inter-network transaction.
Procedure
Ensure that the entered transaction credit party is correct.
4.1240 TC30461
Description
The generated EFT file name is invalid.
Scenario
This error is reported during EFT reconciliation file export when the file name fails to be
generated or is invalid.
Access Channel
Web
Possible Causes
The generated EFT file name is invalid.
Procedure
Ensure that the generated EFT file name is valid.

Copyright © Huawei
Mobile Money
4.1241 TC30462
Description
The balance adjustment review has been completed or canceled and cannot be reviewed
again.
Scenario
This error is reported during balance adjustment review if the review task has been reviewed.
Access Channel
Web
Possible Causes
The balance adjustment review task has been reviewed.
Procedure
Select another review task.
4.1242 TC30463
Description
The refund fails because the original transaction does not exist.
Scenario
This error is reported when the original transaction does not exist.
Access Channel
Web, USSD, STK
Possible Causes
The original transaction does not exist.
Procedure
Enter the correct ID of the original transaction.

Copyright © Huawei
Mobile Money
4.1243 TC30464
Description
The refund fails because the accumulated refund amount is greater than the original
transaction amount.
Scenario
This error is reported when the accumulated refund amount is greater than the original
transaction amount.
Access Channel
Web, USSD, STK
Possible Causes
The accumulated refund amount is greater than the original transaction amount.
Procedure
Enter a correct refund amount.
4.1244 TC30465
Description
The signature of the compute table is tampered with.
Scenario
This error is reported when the signature of the compute table is directly modified using the
SQL statement in the background.
Access Channel
Web
Possible Causes
The system data is abnormal and the signature of the compute table in the background is
tampered with.
Procedure
application report.

Copyright © Huawei
Mobile Money
4.1245 TC30466
Description
The signature of the Disburse table is tampered with.
Scenario
This error is reported when the signature of the Disburse table is directly modified using the
SQL statement in the background.
Access Channel
Web
Possible Causes
The system data is abnormal and the signature of the Disburse table in the background is
tampered with.
Procedure
application report.
4.1246 TC30467
Description
The signature of the Identity control table is tampered with.
Scenario
This error is reported when the signature of the Identity control table is directly modified
using the SQL statement in the background.
Access Channel
Web
Possible Causes
The system data is abnormal and the signature of the Identity control table in the background
is tampered with.
Procedure
application report.

Copyright © Huawei
Mobile Money
4.1247 TC30468
Description
Failed to query data in the report database.
Scenario
This error is reported when data fails to be obtained from the report database.
Access Channel
Web
Possible Causes
Data extraction is not finished in the report database or data in the report database is
abnormal.
Procedure
Check the status of the report database and the extraction situation of the report data.
4.1248 TC30469
Description
The daily settlement balance of the user is abnormal.
Scenario
This error is reported when the daily settlement balance fails to be obtained from the report
database.
Access Channel
Web
Possible Causes
The daily settlement balance of a user fails to be extracted from the report database.
Procedure
Check the daily settlement balance of the user in the report.

Copyright © Huawei
Mobile Money
4.1249 TC30470
Description
The interest settlement date is incorrect.
Scenario
This error is reported when the interest settlement date is later than the current date.
Access Channel
Web
Possible Causes
The interest settlement date is later than the current date.
Procedure
Ensure that the interest settlement date is correct.
4.1250 TC30471
Description
Scenario
This error is reported when a customer initiates an FSI KCB Loan Request transaction using a
handset but the system parameter KCB_LOAN_TERM is not set.
Access Channel
STK
Possible Causes
The system parameter KCB_LOAN_TERM is not set.
Procedure
Set the system parameter KCB_LOAN_TERM correctly and then initiate the transaction.

Copyright © Huawei
Mobile Money
4.1251 TC30472
Description
Scenario
This error is reported when a customer initiates an FSI KCB Loan Request transaction using a
handset but the value of the Loan Term parameter is invalid.
Access Channel
STK
Possible Causes
The value of the Loan Term parameter is invalid.
Procedure
Set the Loan Term parameter correctly.
4.1252 TC30475
Description
The interest calculation failure cause is {0}. The interest delivery failure cause is {1}.
{0} indicates the interest calculation failure cause.

{1} indicates the interest delivery failure cause.
Scenario
This error is reported when the interests of a single identity fails to be processed.
Access Channel
Web
Possible Causes
The interest calculation failure cause is {0}. The interest delivery failure cause is {1}.
Procedure
Rectify the fault based on the fault cause.

Copyright © Huawei
Mobile Money
4.1253 TC30484
Description
The tax configuration is incorrect.
Scenario
This error is reported when the tax configuration is obtained but the data is incorrect.
Access Channel
Web
Possible Causes
The tax configuration does not exist in the system.
Procedure
Check the tax configuration under the assistance of Huawei engineers.
4.1254 TC30489
Description
The initiator of the reversal request is different from the debit party of the transaction to be
reversed.
Scenario
This error is reported if the initiator of the reversal request is different from the debit party of
the transaction to be reversed.
Access Channel
Web
Possible Causes
The initiator of the reversal request is different from the debit party of the transaction to be
reversed.
Procedure
Ensure that the initiator of the reversal request is the same as the debit party of the transaction
to be reversed.

Copyright © Huawei
Mobile Money
4.1255 TC30490
Description
The ID of the original transaction can be used to initiate a reversal request only once.
Scenario
This error is reported during reversal request initiation if the ID of the original transaction has
been used to initiate a reversal request.
Access Channel
Web
Possible Causes
The ID of the original transaction can be used to initiate a reversal request only once.
Procedure
Ensure that the ID of the original transaction has not been used to initiate a reversal
transaction.
4.1256 TC30491
Description
The maximum limit time of the reversal request is left empty.
Scenario
This error is reported during reversal request initiation if the maximum limit time of the
reversal request is left empty.
Access Channel
Web
Possible Causes
The maximum limit time of the reversal request is left empty.
Procedure
Ensure that the maximum limit time of the reversal request is normally configured.

Copyright © Huawei
Mobile Money
4.1257 TC30492
Description
The maximum limit time of the reversal request has expired.
Scenario
This error is reported during reversal request initiation if the maximum limit time of the
reversal request has expired.
Access Channel
Web
Possible Causes
The maximum limit time of the reversal request has expired.
Procedure
Ensure that the maximum limit time of the reversal request is normally configured.
4.1258 TC30493
Description
The request ID does not exist and cannot be used to initiate a transaction.
Scenario
This error is reported when a reversal transaction is initiated based on a nonexistent request
ID.
Access Channel
Web
Possible Causes
The request ID does not exist and cannot be used to initiate a transaction.
Procedure
Ensure that the request ID exists.

Copyright © Huawei
Mobile Money
4.1259 TC30494
Description
Only full reversal is supported.
Scenario
This error is reported if a reversal request is initiated to partially reverse a transaction.
Access Channel
Web
Possible Causes
Only full reversal is supported.
Procedure
Ensure that the reversal request is initiated to fully reverse a transaction.
4.1260 TC30497
Description
This operation cannot be performed because the customer is not a group member.
Scenario
This error is reported when a customer who is not a group member initiates a group
transaction or action or when an operator initiates a group transaction or action for a customer
who is not a group member.
Access Channel
POS
Possible Causes
This operation cannot be performed because the customer is not a group member.
Procedure
Add the customer to a group and then perform the operation.

Copyright © Huawei
Mobile Money
4.1261 TC30498
Description
The customer's role in the group does not have the permission to initiate the operation.
Scenario
This error is reported when a customer initiates a group transaction or action or when an
operator initiates a group transaction or action for a customer but the customer's role in the
group does not have the service permission.
Access Channel
POS
Possible Causes
The customer's role in the group does not have the permission to initiate the operation.
Procedure
Assign the related permission to the customer's role in the group.
4.1262 TC30499
Description
No applicant is entered or the applicant fails to be parsed.
Scenario
This error is reported when a customer initiates a group transaction or action or when an
operator initiates a group transaction or action for a customer but no applicant is entered. The
applicant must be entered for some operations.
Access Channel
POS
Possible Causes
No applicant is entered or the applicant fails to be parsed.
Procedure
Enter a correct applicant number.

Copyright © Huawei
Mobile Money
4.1263 TC30500
Description
The voucher fails to be redeemed. The entered amount must be equal to the voucher amount.
Scenario
This error is reported when a customer redeems a voucher but the entered amount is incorrect.
Access Channel
POS
Possible Causes
The amount entered when a voucher is redeemed is incorrect. The amount must be equal to
the voucher amount.
Procedure
Enter the correct redeeming amount.
4.1264 TC30501
Description
The voucher fails to be redeemed. The entered amount must be less than or equal to the
voucher amount.
Scenario
This error is reported when a customer redeems a voucher but the entered amount is incorrect.
Access Channel
POS
Possible Causes
The amount entered when a voucher is redeemed is incorrect. The amount must be less than
or equal to the voucher amount.
Procedure
Enter the correct redeeming amount.

Copyright © Huawei
Mobile Money
4.1265 TC30502
Description
Operation failed. The entered group code must match the holder in the voucher.
Scenario
This error is reported when an operator initiates a group transaction but the entered group
code does not match the holder in the voucher.
Access Channel
USSD, STK
Possible Causes
The entered group code does not match the holder in the voucher.
Procedure
4.1266 TC30503
Description
Scenario
This error is reported when N is entered during transaction confirmation and the initiated
original transaction is canceled.
Access Channel
API
Possible Causes
Procedure
No processing is required.

Copyright © Huawei
Mobile Money
4.1267 TC30504
Description
Operation failed. The entered requester must match the requester in the voucher.
Scenario
This error is reported when an operator initiates a group transaction but the entered requester
does not match the requester in the voucher.
Access Channel
USSD, STK
Possible Causes
The entered requester does not match the requester in the voucher.
Procedure
Enter a correct requester.
4.1268 TC30505
Description
Transaction {0} of group {1} is canceled because it is rejected by at least one approver.

Scenario
This error is reported when a customer or an operator initiates a group transaction but the
transaction is rejected and canceled.
Access Channel
USSD, STK
Possible Causes
The group transaction is rejected.
Procedure
Ensure that the transaction is approved by all approvers in the group.

Copyright © Huawei
Mobile Money
4.1269 TC30506
Description
The voucher amount entered during voucher application is invalid.
Scenario
This error is reported during voucher application if the entered amount is invalid.
Access Channel
Web
Possible Causes
The voucher amount entered during voucher application is empty or exceeds the maximum.
Procedure
Check the entered voucher amount.
4.1270 TC30507
Description
The status of the group member (initiator, requester, or recharge party) does not support the
operation.
Scenario
This error is reported if the status of the group member does not support the operation in the
scenarios of adding the group member, removing the group member, and changing the group
member role.
Access Channel
Web, API, STK, USSD
Possible Causes
The status of the group member does not support the operation.
Procedure
Check the group member status required for the operation and ensure that the group member
is in valid status.

Copyright © Huawei
Mobile Money
4.1271 TC30508
Description
The entered quota is not an integer multiple of {0}.
{0}: multiple of the transaction amount.
Scenario
This error is reported during BCS transaction if the entered quota is not an integer multiple of
the transaction amount.
Access Channel
Web, STK, USSD, API
Possible Causes
The entered quota is not an integer multiple of {0}.
Procedure
Change the transaction amount.
4.1272 TC30509
Description
The confirmation amount in the confirmation request is different from the actual transaction
amount in the transaction request.
Scenario
This error is reported during BCS transaction if the confirmation amount in the confirmation
request is different from the actual transaction amount in the transaction request.
Access Channel
Web, STK, USSD, API
Possible Causes
The confirmation amount in the confirmation request is different from the actual transaction
amount in the transaction request.
Procedure
Enter a correct confirmation amount.

Copyright © Huawei
Mobile Money
4.1273 TC30510
Description
The voucher secret code cannot be obtained.
Scenario
This error is reported if the entered voucher secret code is empty.
Access Channel
Web, USSD, STK
Possible Causes
The entered voucher secret code is empty.
Procedure
 Ensure that the entered voucher secret code is not empty.
 Check the voucher secret code configured in the UMC Menu Template is correct.
4.1274 TC30511
Description
The secret code rule corresponding to the voucher does not exist.
Scenario
This error is reported if the checked secret code rule does not exist.
Access Channel
Web, USSD, STK
Possible Causes
The secret code rule does not exist.
Procedure
Ensure that the secret code rule exists.

Copyright © Huawei
Mobile Money
4.1275 TC30512
Description
The secret code format corresponding to the voucher does not exist.
Scenario
This error is reported if the checked secret code format does not exist.
Access Channel
Web, USSD, STK
Possible Causes
The secret code format does not exist.
Procedure
Ensure that the secret code format exists.
4.1276 TC30513
Description
The KYC entered by the initiator does not match the KYC stored in the system.
Scenario
This error is reported when the KYC entered by initiator does not match the KYC stored in
the system during initiator KYC verification.
Access Channel
API, STK, USSD
Possible Causes
The KYC entered by the initiator does not match the KYC stored in the system.
Procedure
Enter the correct KYC.

Copyright © Huawei
Mobile Money
4.1277 TC30514
Description
The KYC entered by the initiator fails the verification of the KYC verification rule.
Scenario
This error is reported when the KYC entered by the initiator fails the verification during
initiator KYC verification.
Access Channel
API, STK, USSD
Possible Causes
The KYC entered by the initiator fails the verification of the KYC verification rule.
Procedure
Enter the correct KYC.
4.1278 TC30516
Description
The initiator and receiver must belong to the same organization.
Scenario
This error is reported when an organization operator initiates a transaction but the initiator and
receiver do not belong to the same organization.
Access Channel
STK, USSD, API, Web
Possible Causes
The initiator and receiver do not belong to the same organization.
Procedure
Ensure that the initiator and receiver belong to the same organization.

Copyright © Huawei
Mobile Money
4.1279 TC30518
Description
No sweep-in details are found when the auto sweep transaction is initiated.
Scenario
Reconciliation senario. This error is reported if no sweep-in details are found when the auto
sweep transaction is initiated.
Access Channel
Web
Possible Causes
No sweep-in details are found when the auto sweep transaction is initiated.
Procedure
Choose My Functions > Operations > Organization Revenue > Revenue Settlement
History, check whether an auto sweep transaction whose Funding Source is Organization
Bank exists, and initiate the transaction based on the sweep-in information.
4.1280 TC30519
Description
The MNO data configured in the bulk file conflicts with that in the number sgement table.
Scenario
This error is reported during bulk recharging if the MNO data configured in the bulk file
conflicts with that in the number sgement table.
Access Channel
Web, API
Possible Causes
The MNO data configured in the bulk file conflicts with that in the number sgement table.
Procedure
Ensure that the MNO data configured in the bulk file does not conflict with that in the MNO
Subscriber MSISDN Range menu.

Copyright © Huawei
Mobile Money
4.1281 TC30522
Description
Identity {0} has not subscribed to a product that contains service {1} as the {2} party or the
product that identity {0} subscribes to and contains service {1} as the {2} party is not in
Active state.
{0}: indicates the ID of a user.

{1}: indicates a service alias.
{2}: indicates a service initiator.
Scenario
This error is reported if the identity has not subscribed to the product as the initiator or the
product that identity subscribes to is not in Active state.
Access Channel
Web, STK, USSD, API
Possible Causes
Active state.
Procedure
Search > Organization), select identity {0}, click Details, and enter the Customer Info
or Organization Info page.
3. Select Product tab page.
4.1282 TC30523
Description
Operation failed. The CNICs of the transferor and transferee are not entered.
Scenario
This error is reported when the CNICs of the transferor and transferee are not entered.
Access Channel
Web, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
The CNICs of the transferor and transferee are not entered.
Procedure
Enter the CNICs of the transferor and transferee.
4.1283 TC30524
Description
Operation failed. The status of the transfer record is incorrect.
Scenario
This error is reported when the status of the transfer record is incorrect.
Access Channel
Web, USSD, API
Possible Causes
The status of the transfer record is incorrect.
Procedure
Ensure that the transfer record status is correct.
4.1284 TC30525
Description
Operation failed. The transfer record has expired.
Scenario
This error is reported when the transfer record has expired.
Access Channel
Web, USSD, API
Possible Causes
The transfer record has expired.

Copyright © Huawei
Mobile Money
Procedure
The transfer record has expired and money cannot be withdrawn.
4.1285 TC30526
Description
Operation failed. The transfer transaction ID fails to be obtained.
Scenario
This error is reported when the transfer transaction ID fails to be obtained.
Access Channel
Web, USSD, API
Possible Causes
The transfer transaction ID fails to be obtained.
Procedure
Contact the system administrator.
4.1286 TC30527
Description
Operation failed. The transferor and transferee are the same person.
Scenario
This error is reported when the transferor and transferee are the same person.
Access Channel
Web, USSD, API
Possible Causes
The transferor and transferee are the same person.
Procedure
Ensure that the transferor and transferee are different persons.

Copyright © Huawei
Mobile Money
4.1287 TC30528
Description
Operation failed. The CNIC of the transferor does not exist in the system.
Scenario
This error is reported when the CNIC of the transferor does not exist in the system.
Access Channel
Web, USSD, API
Possible Causes
The CNIC of the transferor does not exist in the system.
Procedure
Ensure that the transferor CNIC entered by the customer exists in the system and is correct.
4.1288 TC30529
Description
Operation failed. The transferee is a registered customer but the entered transferee CNIC is
inconsistent with that in the system.
Scenario
This error is reported when the transferee is a registered customer but the entered transferee
CNIC is inconsistent with that in the system.
Access Channel
Web, USSD, API
Possible Causes
The transferee is a registered customer but the entered transferee CNIC is inconsistent with
that in the system.
Procedure
Ensure that the CNIC of the transferee is the same as that in the system.

Copyright © Huawei
Mobile Money
4.1289 TC30530
Description
Operation failed. No transfer record is found.
Scenario
This error is reported when no transfer record is found.
Access Channel
Web, USSD, API
Possible Causes
No transfer record is found.
Procedure
4.1290 TC30531
Description
Operation failed. The transferee CNIC entered during withdrawal is empty.
Scenario
This error is reported when the transferee CNIC entered during withdrawal is empty.
Access Channel
Web, USSD, API
Possible Causes
The transferee CNIC entered during withdrawal is empty.
Procedure
Enter the CNIC of the transferee.

Copyright © Huawei
Mobile Money
4.1291 TC30532
Description
Operation failed. The withdrawal amount entered during withdrawal is incorrect.
Scenario
This error is reported when the withdrawal amount entered during withdrawal is incorrect.
Access Channel
Web, USSD, API
Possible Causes
The withdrawal amount entered during withdrawal is incorrect.
Procedure
Enter a correct withdrawal amount.
4.1292 TC30533
Description
Operation failed. The currency of the voucher table is different from that of the transfer record
table.
Scenario
This error is reported during withdrawal when the currency of the voucher table is different
from that of the transfer record table.
Access Channel
Web, USSD, API
Possible Causes
During withdrawal, the currency of the voucher table is different from that of the transfer
record table.
Procedure

Copyright © Huawei
Mobile Money
4.1293 TC30534
Description
Operation failed. The entered MSISDN of the transferee is different from that recorded in the
system.
Scenario
This error is reported during withdrawal when the entered MSISDN of the transferee is
different from that recorded in the system.
Access Channel
Web, USSD, API
Possible Causes
The entered MSISDN of the transferee is different from that recorded in the system.
Procedure
Enter the correct MSISDN of the transferee.
4.1294 TC30535
Description
Operation failed. The transfer request is invalid.
Scenario
This error is reported when the transfer request is invalid.
Access Channel
Web, USSD, API
Possible Causes
The transfer request is invalid.
Procedure
Ensure that transfer request parameters are correct, for example, the CNICs and MSISDNs of
the transferor and transferee.

Copyright © Huawei
Mobile Money
4.1295 TC30536
Description
Operation failed. The CNIC entered during withdrawal is incorrect.
Scenario
This error is reported when the CNIC entered during withdrawal is incorrect.
Access Channel
Web, USSD, API
Possible Causes
The CNIC entered during withdrawal is incorrect.
Procedure
Enter the correct CNIC of the transferee.
4.1296 TC30537
Description
Operation failed. The CNIC of the transferor is invalid.
Scenario
This error is reported when the CNIC of the transferor is invalid.
Access Channel
Web, USSD, API
Possible Causes
The CNIC of the transferor is invalid.
Procedure
Ensure that the CNIC of the transferor is correct.

Copyright © Huawei
Mobile Money
4.1297 TC30538
Description
Active state.

Scenario
This error is reported if the identity has not subscribed to the product as the receiver or the
Access Channel
Web, STK, USSD, API
Possible Causes
Active state.
Procedure
4.1298 TC30539
Description
Active state.


Copyright © Huawei
Mobile Money
Scenario
This error is reported if the identity has not subscribed to the product as the primary party or
the product that identity subscribes to is not in Active state.
Access Channel
Web, STK, USSD, API
Possible Causes
Active state.
Procedure
4.1299 TC30540
Description
Active state.

Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Active state.

Copyright © Huawei
Mobile Money
Procedure
4.1300 TC30545
Description
In a voucher deposit transaction, the third-party system returns a response successfully but the
response does not contain the redeeming amount.
Scenario
This error is reported when a customer or organization initiates a voucher deposit transaction,
sends the voucher PIN to a third-party system for verification, and the third-party system
returns success but the response does not contain the redeeming amount.
Access Channel
USSD, API
Possible Causes
response does not contain the redeeming amount.
Procedure
Ensure that the success response returned by the third-party system contains the redeeming
amount.
4.1301 TC30546
Description
response does not contain the voucher number.
Scenario
This error is reported when a customer or organization initiates a voucher deposit transaction,
sends the voucher PIN to a third-party system for verification, and the third-party system
returns success but the response does not contain the voucher number.

Copyright © Huawei
Mobile Money
Access Channel
USSD, API
Possible Causes
response does not contain the voucher number.
Procedure
Ensure that the success response returned by the third-party system contains the voucher
number.
4.1302 TC30547
Description
Failed to export EFT. SFTP system parameters are incorrectly set or the database table is
locked.
Scenario
This error is reported when an EFT file is exported.
Access Channel
Web
Possible Causes
SFTP system parameters are incorrectly set or the database table is locked.
Procedure
4.1303 TC30549
Description
The tax amount cannot be greater than the primary transaction amount.
Scenario
This error is reported during basic transaction charging if the tax amount is greater than the
primary transaction amount.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
The tax amount cannot be greater than the primary transaction amount.
Procedure
Change the primary transaction amount. To query the tax amount, choose My Functions >
Core Configuration > Tax Code.
4.1304 TC30550
Description
The voucher type does not support the amount and the amount must be left empty.
Scenario
This error is reported during voucher application if the voucher type does not support the
amount but an amount is entered.
Access Channel
Web, STK, USSD, API
Possible Causes
The voucher type does not support the amount and the amount must be left empty.
Procedure
Ensure that the amount is left empty.
4.1305 TC30551
Description
The group state of the added beneficiary must be Active.
Scenario
This error is reported when a beneficiary is added for a customer but the group status of the
beneficiary is not Active.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
The group state of the added beneficiary must be Active.
Procedure
Reconfigure the beneficiary information.
4.1306 TC30552
Description
The state of organization {0} must be Active.
{0} indicates an organization public name.
Scenario
This error is reported during transaction if the state of the specified organization is not Active.
Access Channel
Web, STK, USSD, API
Possible Causes
The state of organization {0} must be Active.
Procedure
Verify that the organization information is correct.
4.1307 TC30553
Description
When a voucher with an amount is redeemed, the amount cannot be zero.
Scenario
This error is reported when a voucher with an amount is redeemed but the transaction amount
is zero.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
When a voucher with an amount is redeemed, the amount cannot be zero.
Procedure
Verify that the amount is correct.
4.1308 TC30554
Description
The identity corresponding to voucher holder {0} must be in Active state.
{0} indicates MSISDN.
Scenario
This error is reported during voucher release if the identity having the voucher is not in Active
state.
Access Channel
Web, STK, USSD, API
Possible Causes
The identity corresponding to voucher holder {0} must be in Active state.
Procedure
Verify that the identity corresponding to the MSISDN is in Active state.
4.1309 TC30557
Description
The redeeming organization is not in the range allowed by the voucher type.
Scenario
This error is reported during voucher application if the entered redeeming organization is not
in the range allowed by the voucher type.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
The redeeming organization is not in the range allowed by the voucher type.
Procedure
Ensure that the short code is correct.
4.1310 TC30558
Description
The voucher does not exist or is not in Active state.
Scenario
This error is reported when a voucher is canceled but the voucher does not exist or is not in
Active state.
Access Channel
Web, STK, USSD, API
Possible Causes
The voucher does not exist or is not in Active state.
Procedure
Verify that the vocuher information is correctly configured.
4.1311 TC50001
Description
No exchange rate for exchanging the foreign currency to the local currency is found, leading
to limit rule verification failure.
Scenario
This error is reported in the following scenario: During transaction initiation, the limit rule
where Cross Currencies is set to Yes is configured for the transaction parties but no exchange
rate for exchanging the foreign currency to the local currency is configured in the system,
leading to limit rule verification failure.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
The exchange rate for exchanging the foreign currency to the local currency is not configured
in the system.
Procedure
Configure the exchange rate for exchanging the foreign currency to the local currency in the
system.
4.1312 TC50002
Description
The associated transaction fails.
Scenario
This error is reported in the foreign exchange service when the transaction fails because the
associated transaction fails.
Access Channel
Web, STK, USSD, API
Possible Causes
The associated transaction fails.
Procedure
View the record of the associated transaction to troubleshoot the fault.
4.1313 TC50003
Description
Currency {0} when the voucher is redeemed is different from the currency {1} when the
voucher is generated.
{0}: currency when the voucher is redeemed.

{1}: currency when the voucher is generated.

Copyright © Huawei
Mobile Money
Scenario
This error is reported during voucher redeeming if the currency when the voucher is redeemed
is different from the currency when the voucher is generated.
Access Channel
Web, STK, USSD, API
Possible Causes
Currency {0} when the voucher is redeemed is different from the currency {1} when the
voucher is generated.
Procedure
Ensure that the currency when the voucher is redeemed is the same as that when the voucher
is generated.
4.1314 TC50004
Description
Currency unit {1} of currency {0} is not supported in the system.
{0}: name of the currency parameter, for example, SourceCurrency.

{1}: currency, for example, USD.
Scenario
This error is reported in the foreign exchange service if the entered currency unit is not
supported in the system.
Access Channel
Web, STK, USSD, API
Possible Causes
Currency unit {1} of currency {0} is not supported in the system.
Procedure
Enter a currency supported in the system. To query currencies supported in the system, choose
My Functions > Localization > Currency Definition.

Copyright © Huawei
Mobile Money
4.1315 TC50005
Description
The source currency cannot be the same as the destination currency.
Scenario
This error is reported in the foreign exchange service if the source currency is the same as the
destination currency.
Access Channel
Web, STK, USSD, API
Possible Causes
The source currency cannot be the same as the destination currency.
Procedure
Ensure that the source currency is different from the destination currency.
4.1316 TC50006
Description
One of the source currency and destination currency must be the local currency.
Scenario
This error is reported in the foreign exchange service if both the source currency and the
destination currency are not the local currency.
Access Channel
Web, STK, USSD, API
Possible Causes
One of the source currency and destination currency must be the local currency.
Procedure
Ensure that one of the source currency and destination currency must be the local currency.

Copyright © Huawei
Mobile Money
4.1317 TC50007
Description
The base currency must be the source currency or the destination currency.
Scenario
This error is reported in the foreign exchange service if the base currency is neither the source
currency nor the destination currency.
Access Channel
Web, STK, USSD, API
Possible Causes
The base currency must be the source currency or the destination currency.
Procedure
Ensure that the base currency is the source currency or the destination currency.
4.1318 TC50008
Description
No exchange rate is configured for the foreign currency {0} or the exchange rate has expired
or in Disabled state.
{0}: currency, for example, USD.
Scenario
This error is reported in the foreign exchange service if no exchange rate is configured for the
foreign currency or the exchange rate has expired or in Disabled state.
Access Channel
Web, STK, USSD, API
Possible Causes
No exchange rate is configured for the foreign currency {0} or the exchange rate has expired
or in Disabled state.

Copyright © Huawei
Mobile Money
Procedure
Ensure that the exchange rate has been configured for the foreign currency and is in valid
state. To query the exchange rate information, choose My Functions > Localization >
Foreign Exchange Rate.
4.1319 TC50009
Description
Reason type {0} of the associated transaction does not exist.
{0}: reason type ID of the associated transaction.
Scenario
This error is reported in the foreign exchange service if the reason type of the associated
Access Channel
Web, STK, USSD, API
Possible Causes
Reason type {0} of the associated transaction does not exist.
Procedure
Choose My Functions > Core Configuration > Advanced Configuration > Reason Type
and configure a reason type for the associated transaction on the reason type configuration
page.
4.1320 TC50010
Description
In the foreign exchange purchase service, the source currency must be the local currency and
the destination currency must be a foreign currency.
Scenario
This error is reported in the foreign exchange purchase service if the source currency is not
the local currency and the destination currency is not a foreign currency.
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
Procedure
4.1321 TC50011
Description
In the foreign exchange selling service, the source currency must be a foreign currency and
the destination currency must be the local currency.
Scenario
This error is reported in the foreign exchange selling service if the source currency is not a
foreign currency and the destination currency is not the local currency.
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
4.1322 TC50012
Description
The source currency must be the same as the currency {0} of the amount entered for applying
for the voucher.
{0}: currency of the amount when the voucher is applied.

Copyright © Huawei
Mobile Money
Scenario
This error is reported in the foreign exchange service if the source currency is different from
the currency of the amount entered for applying for the voucher.
Access Channel
Web, STK, USSD, API
Possible Causes
The source currency must be the same as the currency {0} of the amount entered for applying
for the voucher.
Procedure
Enter a correct source currency.
4.1323 TC50013
Description
The source currency must be the same as the currency {0} of the account for applying for the
voucher.
{0}: currency of the account when the voucher is applied.
Scenario
This error is reported in the foreign exchange service if the source currency is different from
the currency of the account for applying for the voucher.
Access Channel
Web, STK, USSD, API
Possible Causes
The source currency must be the same as the currency {0} of the account for applying for the
voucher.
Procedure
Enter a correct source currency.

Copyright © Huawei
Mobile Money
4.1324 TC50014
Description
The source account must be the same as the account for applying for the voucher.
Scenario
This error is reported in the foreign exchange service if the source account is different from
the account for applying for the voucher.
Access Channel
Web, STK, USSD, API
Possible Causes
The source account must be the same as the account for applying for the voucher.
Procedure
Enter a correct source account or leave the source account empty.
4.1325 TC50015
Description
The source account name must be the same as that of the account for applying for the
voucher.
Scenario
This error is reported in the foreign exchange service if the source account name is different
from that of the account for applying for the voucher.
Access Channel
Web, STK, USSD, API
Possible Causes
The source account name must be the same as that of the account for applying for the
voucher.
Procedure
Enter a correct source account name or leave the source account name empty.

Copyright © Huawei
Mobile Money
4.1326 TC50016
Description
The settlement period of account {0} is nonconsecutive and cannot be settled.
Scenario
This error is reported when the commission settlement is initiated but the account settlement
period is nonconsecutive.
Access Channel
Web
Possible Causes
The settlement period of account {0} is nonconsecutive.
Procedure
Choose My Functions > Finance > Commission Settlement > Manual Commission
Settlement and manually settle the commission on the manual settlement page.
4.1327 TC50017
Description
The settlement result of account {0} is a negative number and the settlement fails.
Scenario
This error is reported when a dispute task is executed and the account settlement result is a
negative number.
Access Channel
Web
Possible Causes
The settlement result of account {0} is a negative number.

Copyright © Huawei
Mobile Money
Procedure
Choose My Functions > Finance > Commission Settlement > Manual Commission
Settlement, select proper settlement time on the manual settlement page, and manually
initiate commission settlement, ensuring that the settlement result is not a negative number.
4.1328 TC50018
Description
The commission settlement configuration item does not exist.
Scenario
This error is reported if the commission settlement configuration item does not exist.
Access Channel
Web, STK, USSD, API
Possible Causes
The commission settlement configuration item does not exist.
Procedure
Ensure that the commission settlement configuration item exists and is correct.
4.1329 TC50019
Description
Account {1} of organization {0} is a shared account and the invoice cannot be generated for
the account.
{0}: organization policy name.

{1}: organization account number.
Scenario
This error is reported if the account for which the invoice is generated is a shared account.
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
Account {1} of organization {0} is a shared account and the invoice cannot be generated for
the account.
Procedure
Ensure that the account is correct.
4.1330 TC50020
Description
Account {0} is not a commission account or the invoice does not need to be generated for the
account based on the configuration.
{0}: account number.
Scenario
This error is reported if the account for which the invoice is generated is not a commission
account.
Access Channel
Web, STK, USSD, API
Possible Causes
Account {0} is not a commission account or the invoice does not need to be generated for the
account based on the configuration.
Procedure
Ensure that the account is correct.
4.1331 TC50021
Description
The commission payment task status corresponding to the commission payment batch number
is incorrect. The task status cannot be {0}.
{0}: task status.

Copyright © Huawei
Mobile Money
Scenario
This error is reported if the task status corresponding to the current commission payment
batch number is incorrect.
Access Channel
Web, STK, USSD, API
Possible Causes
The commission payment task status corresponding to the commission payment batch number
is incorrect. The task status cannot be {0}.
Procedure
Select a correct commission payment batch number.
4.1332 TC50022
Description
The invoice cannot be repeatedly generated for the same settlement record.
Scenario
This error is reported if the invoice is repeatedly generated for the same settlement record.
Access Channel
Web, STK, USSD, API
Possible Causes
The invoice cannot be repeatedly generated for the same settlement record.
Procedure
Select a correct settlement record or commission payment batch number.
4.1333 TC50023
Description
According to the invoice generation configuration, the invoice does not need to be generated
for an aggregator-type child organization.

Copyright © Huawei
Mobile Money
Scenario
This error is reported if the invoice is generated for an aggregator-type child organization.
Access Channel
Web, STK, USSD, API
Possible Causes
According to the invoice generation configuration, the invoice does not need to be generated
for an aggregator-type child organization.
Procedure
Ensure that parameters for generating the invoice are correctly set.
4.1334 TC50024
Description
The invoice fails to be canceled because it has been canceled.
Scenario
This error is reported if the invoice is repeatedly canceled.
Access Channel
Web, STK, USSD, API
Possible Causes
The invoice has been canceled.
Procedure
Ensure that the invoice is in a correct state.
4.1335 TC50025
Description
The initiator's organization is different from the primary party's organization or the initiator's
organization is not the upper-level organization of the owned organization of the primary
party.

Copyright © Huawei
Mobile Money
Scenario
This error is reported in the foreign exchange service if the initiator's organization is different
from the primary party's organization or the initiator's organization is not the upper-level
organization of the owned organization of the primary party.
Access Channel
Web, STK, USSD, API
Possible Causes
The initiator's organization is different from the primary party's organization or the initiator's
organization is not the upper-level organization of the owned organization of the primary
party.
Procedure
 If the primary party's organization is a owned organization, ensure that the initiator's
organization is the primary party's organization or the upper-level organization of the
primary party's organization.
 If the primary party's organization is an aggretator organization, ensure that the initiator's
organization is the primary party's organization.
4.1336 TC50026
Description
The account name {1} of identity {0} does not exist or cannot be entered.

{1}: indicates the account name to be queried.
Scenario
This error is reported in the foreign exchange service if the account name of identity does not
exist or cannot be entered.
Access Channel
Web, STK, USSD, API
Possible Causes
The account name {1} of identity {0} does not exist or cannot be entered.
Procedure
Ensure the account name of identity exists and can be entered.

Copyright © Huawei
Mobile Money
4.1337 TC50027
Description
The payee of the direct debit transaction is an organization.
Scenario
This error is reported when the payee of the direct debit transaction is an organization.
Access Channel
Possible Causes
The payee of the direct debit transaction is an organization.
Procedure
Ensure that the mandate ID is correct.
4.1338 TC50028
Description
The mandate of the direct debit transaction does not exist.
Scenario
This error is reported when the mandate of the direct debit transaction does not exist.
Access Channel
Possible Causes
The mandate of the direct debit transaction does not exist.
Procedure
Ensure that the mandate ID is correct.

Copyright © Huawei
Mobile Money
4.1339 TC50029
Description
The initiation date of the direct debit transaction is not in the allowed date range.
Scenario
This error is reported when the initiation date of the direct debit transaction is not in the
allowed date range.
Access Channel
Possible Causes
The initiation date of the direct debit transaction is not in the allowed date range.
Procedure
Initiate the direct debit transaction in the allowed date range or modify the date range of the
direct debit mandate.
4.1340 TC50030
Description
Bulk task parameters of the direct debit transaction cannot be parsed.
Scenario
This error is reported when the bulk task parameters of the direct debit transaction cannot be
parsed.
Access Channel
Possible Causes
Bulk task parameters of the direct debit transaction cannot be parsed.
Procedure
Ensure that the task file of the bulk task is correctly configured.

Copyright © Huawei
Mobile Money
4.1341 TC50031
Description
Bulk task parameters of the direct debit transaction are incomplete.
Scenario
This error is reported when the bulk task parameters of the direct debit transaction are
incomplete.
Access Channel
Possible Causes
Bulk task parameters of the direct debit transaction are incomplete.
Procedure
Ensure that the task file of the bulk task is correctly configured.
4.1342 TC50032
Description
The direct debit mandate is not in Active state because it is authorized but not activated.
Scenario
This error is reported when the direct debit mandate is not in Active state.
Access Channel
Possible Causes
The direct debit mandate is not in Active state.
Procedure
Activate or reactivate the mandate.

Copyright © Huawei
Mobile Money
4.1343 TC50033
Description
The task execution result fails to be obtained.
Scenario
This error is reported during bulk transaction execution if the task execution result fails to be
obtained.
Access Channel
Web (Bulk)
Possible Causes
The task execution result fails to be obtained.
Procedure
Collect the /log/debug/bcs_debug.log file in the BCS and sent the file to Huawei engineers
4.1344 TC50034
Description
The bank returns a processing failure response.
Scenario
This error is reported if the response fails to be sent for the transaction request sent by the
bank.
Access Channel
STK, USSD, API, Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
4.1345 TC50035
Description
The bank card owner and the payee are not the same identity.
Scenario
This error is reported when a customer transfers money from a bank account to a Mobile
Money system account but the FI organization of the bank account can transfer to itself only
and the bank card owner and payee are not the same identity.
Access Channel
STK, USSD, API, Web
Possible Causes
The bank card owner and the payee are not the same identity.
Procedure
Ensure that the bank card owner and the payee are the same identity.
4.1346 TC50036
Description
The transaction template fails to be checked because activity {0} is not defined in the
metadata table.
Scenario
This error is reported during transaction template check if the activity is not defined in the
metadata table.
Access Channel
Web, USSD, API
Possible Causes
Activity {0} is not defined in the metadata table.
Procedure
Check the transaction template file.

Copyright © Huawei
Mobile Money
4.1347 TC50037
Description
The transaction template fails to be checked because the migration condition data type in
activity {0} is incorrect.
Scenario
This error is reported during transaction template check if the migration condition data type in
the activity is incorrect.
Access Channel
Web, USSD, API
Possible Causes
The migration condition data type in activity {0} is incorrect.
Procedure
4.1348 TC50038
Description
The transaction template fails to be checked because the enumerated value of the migration
condition in activity {0} is not defined in data field {1}.
Scenario
This error is reported during transaction template check if the enumerated value configured
for migration condition in the activity is not in the defined data field.
Access Channel
Web, USSD, API
Possible Causes
The enumerated value of the migration condition in activity {0} is not defined in data field
{1}.
Procedure

Copyright © Huawei
Mobile Money
4.1349 TC50039
Description
The transaction template fails to be checked. State {1} is not applicable to activity {0}.
Scenario
This error is reported during transaction template check when the status of the current activity
is not defined in the metadata table.
Access Channel
Web, USSD, API
Possible Causes
State {1} is not applicable to activity {0}.
Procedure
4.1350 TC50040
Description
The KYC information entered by the transaction participant does not match the KYC
information stored in the system.
Scenario
This error is reported during the transaction participant (credit or debit party) KYC check if
the KYC information entered by the transaction participant does not match the KYC
Access Channel
Web
Possible Causes
The KYC information entered by the transaction participant does not match the KYC
Procedure

Copyright © Huawei
Mobile Money
4.1351 TC50041
Description
The KYC information entered by the transaction debit party does not match the KYC
Scenario
This error is reported during debit party KYC check if the KYC information entered by the
debit party does not match the KYC information stored in the system.
Access Channel
Web
Possible Causes
The KYC information entered by the transaction debit party does not match the KYC
Procedure
4.1352 TC50042
Description
The KYC information entered by the transaction credit party does not match the KYC
Scenario
This error is reported during credit party KYC check if the KYC information entered by the
credit party does not match the KYC information stored in the system.
Access Channel
Web
Possible Causes
The KYC information entered by the transaction credit party does not match the KYC
Procedure

Copyright © Huawei
Mobile Money
4.1353 TC50043
Description
The identity of the voucher holder is different from the identity activating the card.
Scenario
This error is reported when a card is used to initiate a voucher redeeming transaction if the
identity of the voucher holder is different from the identity activating the card.
Access Channel
Web
Possible Causes
The identity of the voucher holder is different from the identity activating the card.
Procedure
Enter the correct card or voucher information.
4.1354 TC50044
Description
The query fails. The entered account type must be the loyalty point account type.
Scenario
This error is reported during query of loyalty point accounts or loyalty point entries if the
entered account type is not the loyalty point account type.
Access Channel
Web, STK, USSD, API
Possible Causes
The entered account type is not the loyalty point account type.
Procedure
Enter a correct account type.

Copyright © Huawei
Mobile Money
4.1355 TC50045
Description
The query fails. The organization of the initiator does not have any loyalty point account.
Scenario
This error is reported when an organization operator queries the consumer loyalty point
account and loyalty point entries but the organization of the initiator does not have any loyalty
point account.
Access Channel
Web, STK, USSD, API
Possible Causes
The organization of the initiator does not have any loyalty point account.
Procedure
Ensure that the input parameters are correct.
4.1356 TC50046
Description
The query fails. The organization of the initiator does not have the specified loyalty point
account {0}.
Scenario
This error is reported when an organization operator queries the consumer loyalty point
account and loyalty point entries but the initiator does not have the specified loyalty point
account.
Access Channel
Web, STK, USSD, API
Possible Causes
The organization of the initiator does not have the specified loyalty point account {0}.
Procedure
Ensure that the entered account name is correct.

Copyright © Huawei
Mobile Money
4.1357 TC50047
Description
During transaction confirmation, the entered participant is not allowed to confirm the
transaction.
Scenario
This error is reported during the confirmation of a two part payment transaction if the entered
participant does not support transaction confirmation.
Access Channel
Web, STK, USSD, API
Possible Causes
During transaction confirmation, the entered participant is not allowed to confirm the
transaction.
Procedure
Enter a transaction confirmation party that is allowed to confirm the transaction.
4.1358 TC50048
Description
The transaction record cannot be found based on the transaction ID.
Scenario
This error is reported when a two part payment transaction is confirmed but the transaction
record cannot be found based on the transaction ID.
Access Channel
Web, STK, USSD, API
Possible Causes
The transaction record cannot be found based on the transaction ID.
Procedure
Enter a correct transaction ID.

Copyright © Huawei
Mobile Money
4.1359 TC50049
Description
The original transaction is not in Authorized state and cannot be confirmed.
Scenario
This error is reported when a two part payment transaction is confirmed but the original
transaction is not in Authorized state and cannot be confirmed.
Access Channel
Web, STK, USSD, API
Possible Causes
The original transaction is not in Authorized state and cannot be confirmed.
Procedure
Ensure that the original transaction is in Authorized state.
4.1360 TC50050
Description
The voucher record cannot be found based on the voucher code.
Scenario
This error is reported when a two part payment transaction is confirmed but the voucher
record cannot be found based on the voucher code.
Access Channel
Web, STK, USSD, API
Possible Causes
The voucher record cannot be found based on the voucher code.
Procedure
Enter a correct voucher code.

Copyright © Huawei
Mobile Money
4.1361 TC50051
Description
The voucher is invalid and the original transaction cannot be confirmed.
Scenario
transaction cannot be confirmed because the voucher is invalid.
Access Channel
Web, STK, USSD, API
Possible Causes
The voucher is invalid and the original transaction cannot be confirmed.
Procedure
Ensure that the voucher is valid.
4.1362 TC50052
Description
The transaction ID and voucher code association check fails and the original transaction
cannot be confirmed.
Scenario
transaction cannot be confirmed because the transaction ID and voucher code association
check fails.
Access Channel
Web, STK, USSD, API
Possible Causes
The transaction ID and voucher code association check fails and the original transaction
cannot be confirmed.
Procedure
Ensure that the transaction ID and voucher code association check is successful.

Copyright © Huawei
Mobile Money
4.1363 TC50053
Description
Loyalty point accounts of both transaction parties fail to be parsed.
Scenario
This error is reported during a loyalty point transaction if the loyalty point accounts of both
transaction parties are not unique.
Access Channel
Web, STK, USSD, API
Possible Causes
The parsed accounts of both transaction parties are not unique.
Procedure
Ensure that the parsed names of the loyalty point accounts of both transaction parties are
unique.
4.1364 TC50054
Description
Identity {0} does not contain the loyalty point account whose name is {1}.
{0} indicates the public name of the identity.

{1} indicates the account name.
Scenario
This error is reported during a loyalty point transaction if the loyalty point account of one
transaction party cannot be parsed based on the account name of the other transaction party.
Access Channel
Web, STK, USSD, API
Possible Causes
The loyalty point account names of both transaction parties must be consistent.
Procedure
Ensure that the loyalty point accounts of both transaction parties have the same name.

Copyright © Huawei
Mobile Money
4.1365 TC50055
Description
The loyalty point account names of both primary transaction parties must be consistent.
Scenario
This error is reported during a loyalty point transaction if the loyalty point account names of
both primary transaction parties are inconsistent.
Access Channel
Web, STK, USSD, API
Possible Causes
The loyalty point account names of both primary transaction parties must be consistent.
Procedure
Ensure that the loyalty point account names of both primary transaction parties are consistent.
4.1366 TC50056
Description
The transaction template fails to be checked. Template {0} fails to be loaded.
{0} indicates a template ID.
Scenario
This error is reported during transaction template check if the imported template fails to be
loaded.
Access Channel
Web
Possible Causes
Template {0} fails to be loaded.
Procedure

Copyright © Huawei
Mobile Money
4.1367 TC50057
Description
The system task fails to be executed because the trial calculation on the day is not completed.
Scenario
This error is reported when the saving plan system task is executed to query whether the
settlement on the day is completed but the trial calculation is not completed.
Access Channel
System
Possible Causes
The trial calculation on the day is not completed.
Procedure
Execute the system task after the trial calculation is completed.
4.1368 TC50058
Description
There is no daily settlement balance on the day.
Scenario
This error is reported when the daily settlement balance is obtained during interest calculation
but there is no daily settlement balance on the day.
Access Channel
System
Possible Causes
There is no daily settlement balance on the day.
Procedure
Ensure that there is daily settlement balance on the day.

Copyright © Huawei
Mobile Money
4.1369 TC50060
Description
Failed to upload the file because the order whose transaction sequence number is {0} does not
exist or the order is not in Pending state.
{0} indicates transaction sequence number. For example, 0000000000048007.
Scenario
This error is reported if the system fails to verify the transaction ID in the file uploaded by an
SP operator to create a task of the Bulk Complete or Cancel Transaction type on the bulk
page.
Access Channel
Web(Bulk)
Possible Causes
The order whose transaction sequence number is {0} does not exist or the order is not in
Pending state.
Procedure
Enter a correct ID of an order to be approved.
4.1370 TC50061
Description
The system sends a refill request to a third-party system but the third-party system sends back
a transaction failure message.
Scenario
This error is reported if the system sends a refill request for the reload transaction to a third-
party system but receives a transaction failure message from the third-party system.
Access Channel
Web, USSD, API
Possible Causes
The system sends a refill request to a third-party system but the third-party system sends back
a transaction failure message.

Copyright © Huawei
Mobile Money
Procedure
Query the log/debug/tc_debug.log file for interaction errors.
4.1371 TC50062
Description
Failed to subscribe Data/VAS Package due to the lack of the corresponding service package.
Scenario
This error is reported if the corresponding service package is not configured in the system
during Data/VAS Package subscription.
Access Channel
Web
Possible Causes
The corresponding service package is not configured in the system.
Procedure
Initiate the subscription again after the package is configured.
4.1372 TC50063
Description
The value {0} of the purchase_order parameter is found in the order generated by a third-
party system.
Scenario
This error is reported when the inventory allocation order created by an SP operator through
an API interface contains the duplicate purchase_order parameter.
Access Channel
API
Possible Causes
The value {0} of the purchase_order parameter is found in the order generated by a third-
party system.

Copyright © Huawei
Mobile Money
Procedure
Enter only necessary purchase_order parameter.
4.1373 TC50064
Description
Extended denomination attributes are not configured on the service page during the execution
of the reload transaction.
Scenario
This error is reported when extended denomination attributes are not configured on the
service page during the execution of the reload transaction.
Access Channel
Web, USSD, API
Possible Causes
Extended denomination attributes are not configured on the service page during the execution
of the reload transaction.
Procedure
Select extended denomination attributes and set them.
4.1374 TP30000
Description
Transaction succeeded.
Scenario
All transactions and actions
Access Channel
Web, STK, USSD, API
Possible Causes
N/A

Copyright © Huawei
Mobile Money
Procedure
N/A
4.1375 TP30002
Description
The transaction request lacks service configuration information.
Scenario
When a transaction is initiated, the transaction request lacks service configuration
information.
Access Channel
Web, STK, USSD, API
Possible Causes
The transaction request must contain service configuration information.
Procedure
Ask the system to provide service information and perform the transaction again.
4.1376 TP30003
Description
The transaction request lacks the initiator information.
Scenario
When a transaction is initiated, the transaction request lacks the initiator information.
Access Channel
Web, STK, USSD, API
Possible Causes
The transaction request must contain the initiator information.
Procedure
Configure the initiator information and perform the transaction again.

Copyright © Huawei
Mobile Money
4.1377 TP30004
Description
The transaction request lacks the receiver information.
Scenario
When a transaction is initiated, the transaction request lacks the receiver information.
Access Channel
Web, STK, USSD, API
Possible Causes
The transaction request must contain the receiver information.
Procedure
Configure the receiver information and perform the transaction again.
4.1378 TP30005
Description
An operator cannot close the self.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
4.1379 TP30006
Description
The request lacks reason type information.
Scenario
When a transaction is initiated, the transaction request lacks reason type information.
Access Channel
Web, STK, USSD, API
Possible Causes
If the reason type mode is set to manual for a service, you must enter a reason type.
Procedure
Enter reason type information.
4.1380 TP30008
Description
The transaction request lacks an access channel.
Scenario
When a transaction is initiated, the transaction request lacks an access channel.
Access Channel
Web, STK, USSD, API
Possible Causes
The transaction request must contain an access channel.
Procedure
Ask the system administrator to configure an access channel.

Copyright © Huawei
Mobile Money
4.1381 TP30011
Description
The transaction request lacks a transaction amount.
Scenario
When a transaction is initiated, the transaction request lacks transaction amount.
Access Channel
Web, STK, USSD, API
Possible Causes
The transaction request must contain a transaction amount.
Procedure
Enter a transaction amount.
4.1382 TP30012
Description
The transaction request lacks a PIN.
Scenario
When a transaction is initiated, the transaction request lacks a PIN.
Access Channel
Web, STK, USSD, API
Possible Causes
The transaction request must contain a PIN.
Procedure
Enter a PIN.

Copyright © Huawei
Mobile Money
4.1383 TP30013
Description
The PIN is in an invalid status and cannot be used in transactions.
Scenario
The status of the PIN does not support the current transaction.
Access Channel
Web, STK, USSD, API
Possible Causes
The PIN is in the {0} status and cannot be used in transactions.
{0}: indicates the status of a PIN.
Procedure
Change the status of the PIN.
4.1384 TP30014
Description
The transaction amount is invalid.
Scenario
When a transaction is initiated, the amount in the transaction request is less than 0.
Access Channel
Web, STK, USSD, API
Possible Causes
The amount in the transaction request must be equal to or greater than 0.
Procedure
Enter a correct transaction amount.

Copyright © Huawei
Mobile Money
4.1385 TP30015
Description
Scenario
When a transaction is initiated, the PIN is incorrect when initiating the transaction.
Access Channel
STK, USSD, API
Possible Causes
Procedure
4.1386 TP30016
Description
The requested service does not exist.
Scenario
When a transaction is initiated, the requested service does not exist when initiating the
transaction.
Access Channel
Web, USSD, API, STK
Possible Causes
The transaction must belong to an effective service.
Procedure
Enter a correct service.

Copyright © Huawei
Mobile Money
4.1387 TP30017
Description
The requested transaction type does not exist.
Scenario
The requested reason type does not exist when initiating the transaction.
Access Channel
Web, USSD, API, STK
Possible Causes
The transaction request must be valid.
Procedure
Enter a correct transaction type.
4.1388 TP30018
Description
The transaction amount is less than the minimum currency amount.
Scenario
When a transaction is initiated, the transaction amount is less than or equal to 0.
Access Channel
Web, STK, USSD, API
Possible Causes
The transaction amount is not in the valid range.
Procedure
Verify that the transaction amount meets the requirements. If the problem persists, contact a
Huawei engineer for help.

Copyright © Huawei
Mobile Money
4.1389 TP30019
Description
The new PIN and confirmation PIN are different.
Scenario
Access Channel
STK, USSD, API
Possible Causes
Procedure
Set the confirmation PIN the same as the new PIN.
4.1390 TP30020
Description
The debit and credit parties of the primary transaction are using the same account.
Scenario
The debit and credit parties of the primary transaction are using the same account.
Access Channel
Web, STK, USSD, API
Possible Causes
Both parties of the primary transaction are using the same account.
Procedure
Specify different accounts for both parties and initiate the transaction again.

Copyright © Huawei
Mobile Money
4.1391 TP30021
Description
The specified currency unit is incorrect and does not meet the ISO4217 standard.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
Enter a correct currency unit.
4.1392 TP30022
Description
No exchange rate is configured.
Scenario
No exchange rate is configured between the input currency and the system default currency.
Access Channel
API
Possible Causes
No exchange rate is configured between the {0} and {1} currencies.
{0}: indicates the currency used in a transaction.

{1}: indicates the default currency used in the system.
Procedure
2. Choose My Functions > Operational Configuration > Localization > Currency
Exchange Rate.
3. Enter the page for editing currency exchange rate records.

Copyright © Huawei
Mobile Money
4. Configure an exchange rate.
4.1393 TP30023
Description
The {0} service cannot be initiated through the {1} channel.

{1}: indicates a transaction channel.
Scenario
The service in the transaction cannot be initiated through the current channel.
Access Channel
Web, STK, USSD, API
Possible Causes
The {0} service cannot be initiated through the {1} channel.
Procedure
Enter a correct transaction channel.
4.1394 TP30024
Description
Identity {0} has not subscribed to any product or the product subscription has expired.
Scenario
Identity has not subscribed to any product or the product subscription has expired.
Access Channel
Web, STK, USSD, API
Possible Causes
Identity {0} has not subscribed to any product or the product subscription has expired.

Copyright © Huawei
Mobile Money
Procedure
Subscribe to a product for the identity.
4.1395 TP30025
Description
Active state.

Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Active state.
Procedure
4.1396 TP30027
Description
The product subscribed to by the subscriber has expired.

Copyright © Huawei
Mobile Money
Scenario
The product has expired.
Access Channel
Web, STK, USSD, API
Possible Causes
The product subscribed to by the subscriber has expired.
Procedure
Subscribe to the product again.
4.1397 TP30028
Description
The channel is not supported.
Scenario
The channel is not supported when initiating the transaction.
Access Channel
Web, STK, USSD, API
Possible Causes
The channel is not supported.
Procedure
Initiate the transaction through another channel.
4.1398 TP30031
Description
No reason type is found for the current scenario.
Scenario
No reason type is found for the current scenario. For example, the initiator or receiver of a
transaction does not match with the reason type, or the transaction channel does not match
with the reason type.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
No reason type is found for the current scenario.
Procedure
1. Use an SP operator to log in to the SP portal.
4.1399 TP30032
Description
Multiple reason types are found for the current scenario.
Scenario
Multiple reason types are found based on the input parameter when initiating the transaction.
Access Channel
Web, STK, USSD, API
Possible Causes
Multiple reason types are found for the current scenario.
Procedure
1. Use an SP operator to log in to the SP portal.
3. Check whether the reason type is correctly configured.
4.1400 TP30033
Description
The new secret word and confirmation secret word are different.

Copyright © Huawei
Mobile Money
Scenario
The new secret word and confirmation secret word are different during the secret word
modification.
Access Channel
STK, USSD, API
Possible Causes
The new secret word and confirmation secret word are different.
Procedure
Set the confirmation secret word the same as the new secret word.
4.1401 TP30034
Description
The identity who holds the voucher does not support the KYC authentication.
Scenario
The identity that holds the voucher does not support the KYC authentication during voucher
redeeming.
Access Channel
Web, STK, USSD, API
Possible Causes
The voucher type specified by the identity in the reason type during voucher application
cannot be authenticated using the identity's KYC information.
Procedure
3. Query by reason type name to verify whether the voucher type can be authenticated
based on the identity's KYC information.
4. If the voucher type cannot be authenticated using the identity's KYC information, select
a voucher type that can be authenticated.

Copyright © Huawei
Mobile Money
4.1402 TP30035
Description
The KYC information or identity information during voucher exchange is incorrect.
Scenario
The KYC information or identity information set for identity authentication during voucher
exchange is incorrect.
Access Channel
Web, STK, USSD, API
Possible Causes
The KYC information or identity information specified during voucher exchange is incorrect.
Procedure
Verify that the KYC information or identity information is correct.
4.1403 TP30036
Description
The transaction amount exceeds the upper limit.
Scenario
The specified transaction amount exceeds the upper limit when initiating the transaction.
Access Channel
Web, STK, USSD, API
Possible Causes
The specified transaction amount exceeds the upper limit.
Procedure
Enter a transaction amount in the valid range.

Copyright © Huawei
Mobile Money
4.1404 TP30037
Description
Voucher verification value is not input during voucher redeeming.
Scenario
Voucher verification value is not input during voucher redeeming.
Access Channel
Web, STK, USSD, API
Possible Causes
Voucher verification value is mandatory for specified voucher code redeeming.
Procedure
Please input correct voucher verification value corresponding to specified voucher.
4.1405 TP30038
Description
Parties of the same transaction cannot be the same person or organization.
Scenario
The debit and credit parties of a transaction are the same person if the transaction type
configuration indicates that the parties cannot be a same person.
Access Channel
Web, STK, USSD, API
Possible Causes
Parties of the same transaction cannot be the same person or organization.
Procedure
Verify the transaction type settings.

Copyright © Huawei
Mobile Money
4.1406 TP30039
Description
The transaction cannot be performed using an unregistered customer.
Scenario
Access Channel
STK, USSD, API, Web
Possible Causes
Procedure
Use a registered customer to perform the transaction.
4.1407 TP30044
Description
The transaction ID {0} specified for the original transaction does not exist or is in Cancel or
Expired state.
{0}: indicates the original transaction ID.
Scenario
The transaction ID of the original transaction to be reversed or cleared does not exist or is in
incorrect status.
Access Channel
Web
Possible Causes
The transaction ID of the original transaction is incorrect.
Procedure
Verify that the transaction ID specified for the original transaction is correct.

Copyright © Huawei
Mobile Money
4.1408 TP30045
Description
Failed to authenticate the transaction by limit rule {0}.
{0}: indicates the name of a limit rule.
Scenario
The transaction limit rule fails to be verified.
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
Verify that the transaction complies with the limit rule and try again.
4.1409 TP30046
Description
The {0} account of the credit party is in the {1} status and cannot be used to perform
transactions.

Scenario
All transactions
Access Channel
Web, STK, USSD, API
Possible Causes
The account status of the credit party is invalid.

Copyright © Huawei
Mobile Money
Procedure
 Solution 1: Change the account status of the credit party to a valid status and perform the
transaction again.
 Solution 2: Select a credit party whose account is in a valid status and perform the
transaction again.
4.1410 TP30047
Description
The {0} account of the debit party is in the {1} status and cannot be used to perform
transactions.

Scenario
Access Channel
Web, USSD, API, STK
Possible Causes
The account status of the debit party is invalid.
Procedure
 Solution 1: Change the account status of the debit party to a valid status and perform the
transaction again.
 Solution 2: Select a debit party whose account is in a valid status and perform the
transaction again.
4.1411 TP30048
Description
The initiator is in an invalid status.
Scenario
Failed to authentication because the initiator is in an invalid status.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
Initiator {0} is in the {1} status and not allowed to perform transactions.
{0}: indicates identity identifier.

Procedure
 Solution 1: Change the initiator's status to a valid status and perform the transaction
again.
 Solution 2: Select an initiator in a valid status and perform the transaction again.
4.1412 TP30049
Description
The receiver is in an invalid status.
Scenario
Failed to authentication because the receiver is in an invalid status.
Access Channel
Web, STK, USSD, API
Possible Causes
Receiver {0} is in the {1} status and not allowed to perform transactions.

Procedure
 Solution 1: Change the receiver's status to a valid status and perform the transaction
again.
 Solution 2: Select a receiver in a valid status and perform the transaction again.

Copyright © Huawei
Mobile Money
4.1413 TP30051
Description
The credit party is in an invalid status.
Scenario
Failed to authentication because the credit party is in an invalid status.
Access Channel
Web, STK, USSD, API
Possible Causes
Credit party {0} is in the {1} status and not allowed to perform transactions.

Procedure
 Solution 1: Change the credit party's status to a valid status and perform the transaction
again.
 Solution 2: Select a credit party in a valid status and perform the transaction again.
4.1414 TP30052
Description
The debit party is in an invalid status.
Scenario
Failed to authentication because the debit party is in an invalid status.
Access Channel
Web, STK, USSD, API
Possible Causes
Debit party {0} is in the {1} status and not allowed to perform transactions.


Copyright © Huawei
Mobile Money
Procedure
 Solution 1: Change the debit party's status to a valid status and perform the transaction
again.
 Solution 2: Select a debit party in a valid status and perform the transaction again.
4.1415 TP30053
Description
Failed to generate the voucher.
Scenario
Generating a voucher fails (the fault does not occur if the system runs properly).
Access Channel
Web, STK, USSD, API
Possible Causes
Voucher parameter is empty.
Procedure
4.1416 TP30054
Description
Scenario
The Voucher Code parameter for applying for a voucher is blank (the fault does not occurs if
the system runs properly).
Access Channel
Web, STK, USSD, API
Possible Causes
The voucher code parameter is empty.

Copyright © Huawei
Mobile Money
Procedure
4.1417 TP30055
Description
Scenario
The Voucher State parameter for applying for a voucher is blank (the fault does not occurs if
Access Channel
Web, STK, USSD, API
Possible Causes
The voucher state parameter is empty.
Procedure
4.1418 TP30056
Description
Scenario
The Voucher Type parameter for applying for a voucher is blank (the fault does not occurs if
Access Channel
Web, STK, USSD, API
Possible Causes
The voucher type parameter is empty.
Procedure

Copyright © Huawei
Mobile Money
4.1419 TP30057
Description
Scenario
The Effective Data parameter for applying for a voucher is blank.
Access Channel
Web, STK, USSD, API
Possible Causes
The effective date parameter is empty.
Procedure
4.1420 TP30058
Description
Scenario
The Expired Date parameter for applying for a voucher is blank.
Access Channel
Web, STK, USSD, API
Possible Causes
The expired date parameter is empty.
Procedure

Copyright © Huawei
Mobile Money
4.1421 TP30059
Description
Scenario
The Currency parameter for applying for a voucher is blank.
Access Channel
Web, STK, USSD, API
Possible Causes
The currency parameter is empty.
Procedure
4.1422 TP30060
Description
Scenario
The Hold ID parameter for applying a voucher is blank.
Access Channel
Web, STK, USSD, API
Possible Causes
The holder ID parameter is empty.
Procedure

Copyright © Huawei
Mobile Money
4.1423 TP30061
Description
Scenario
The Hold ID Type parameter for applying a voucher is blank.
Access Channel
Web, STK, USSD, API
Possible Causes
The holder ID type parameter is empty.
Procedure
4.1424 TP30062
Description
Scenario
The Issue Time parameter for applying for a voucher is blank.
Access Channel
Web, STK, USSD, API
Possible Causes
The issue time parameter is empty.
Procedure

Copyright © Huawei
Mobile Money
4.1425 TP30063
Description
Scenario
The Issue Pri Type ID parameter for applying for a voucher is blank.
Access Channel
Web, STK, USSD, API
Possible Causes
The ISSUEPRITYPEID parameter is empty.
Procedure
4.1426 TP30064
Description
Scenario
The Issue Reason parameter for applying for a voucher is blank.
Access Channel
Web, STK, USSD, API
Possible Causes
The issue reason parameter is empty.
Procedure

Copyright © Huawei
Mobile Money
4.1427 TP30065
Description
Scenario
The Issue Business Scope parameter for applying for a voucher is blank.
Access Channel
Web, STK, USSD, API
Possible Causes
The issue business scope parameter is empty.
Procedure
4.1428 TP30066
Description
Scenario
The Translog ID parameter for applying for a voucher is blank.
Access Channel
Web, STK, USSD, API
Possible Causes
The TRANSLOGID parameter is empty.
Procedure

Copyright © Huawei
Mobile Money
4.1429 TP30067
Description
The specified voucher does not exist or is in an invalid status.
Scenario
The specified voucher does not exist or is not in the active status during voucher redeeming.
Access Channel
Web, STK, USSD, API
Possible Causes
The specified voucher does not exist or is in an invalid status.
Procedure
4.1430 TP30068
Description
The specified voucher has expired.
Scenario
The entered voucher for voucher exchange has expired.
Access Channel
Web, STK, USSD, API
Possible Causes
The specified voucher has expired.
Procedure

Copyright © Huawei
Mobile Money
4.1431 TP30069
Description
Failed to generate the voucher code.
Scenario
During voucher application, the number of times that vouchers are generated in each
transaction exceeds the threshold.
Access Channel
Web, STK, USSD, API
Possible Causes
The number of valid voucher codes generated exceeds the upper limit.
Procedure
Execute the transaction again.
4.1432 TP30070
Description
The expiration time configured for the voucher type is in an incorrect format.
Scenario
The expiry date configured in Voucher Type is incorrect.
Access Channel
Web, STK, USSD, API
Possible Causes
The format of the expiration time is incorrect.
Procedure
2. Choose Core Configuration > Advanced Configuration > Voucher Type to enter the
Voucher Type configuration page.
3. Query by Voucher Type Name to verify whether the Period field is correctly configured.
4. If the configuration is incorrect, click New Version and modify the Period field.

Copyright © Huawei
Mobile Money
4.1433 TP30071
Description
The voucher code configured for the voucher type is in an incorrect format.
Scenario
The voucher code configured in Voucher Type is in an incorrect format.
Access Channel
Web, STK, USSD, API
Possible Causes
The voucher code is in an incorrect format.
Procedure
2. Choose Core Configuration > Advanced Configuration > Voucher Type to enter the
Voucher Type configuration page.
3. Query by Voucher Type Name to verify whether the voucher code format is correctly
configured.
4. If the voucher code format is incorrect, click New Version and modify the voucher code
format.
4.1434 TP30072
Description
Failed to query the voucher.
Scenario
The ID of a voucher to be queried is blank.
Access Channel
Web, STK, USSD, API
Possible Causes
The voucher ID is empty.
Procedure

Copyright © Huawei
Mobile Money
4.1435 TP30073
Description
Scenario
The voucher holder parameter for cleaning up a voucher is blank.
Access Channel
Web, STK, USSD, API
Possible Causes
The voucher holder parameter is empty.
Procedure
4.1436 TP30075
Description
Scenario
The Voucher Type ID parameter for applying for a voucher is blank.
Access Channel
Web, STK, USSD, API
Possible Causes
The voucher type ID parameter is empty.
Procedure

Copyright © Huawei
Mobile Money
4.1437 TP30076
Description
Scenario
No voucher code is generated based on the voucher format when a voucher is applied.
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
4.1438 TP30077
Description
Scenario
The Voucher State parameter for applying for a voucher is blank (the fault does not occur
when the system runs properly).
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
4.1439 TP30078
Description
Failed to update the voucher.
Scenario
The Voucher State parameter for updating a voucher is blank (the fault does not occur when
the system runs properly). A voucher must be updated when a transaction is cleaned up,
expired vouchers are cleaned up, or a voucher is activated.
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
4.1440 TP30079
Description
Failed to update the voucher.
Scenario
The ID of the voucher to be updated is blank. A voucher must be updated when a transaction
is cleaned up, expired vouchers are cleaned up, and a voucher is activated.
Access Channel
Web, STK, USSD, API
Possible Causes
The voucher ID parameter is empty.
Procedure

Copyright © Huawei
Mobile Money
4.1441 TP30081
Description
The specified voucher is already redeemed.
Scenario
The specified voucher has been exchanged during voucher redeeming.
Access Channel
Web, STK, USSD, API
Possible Causes
The specified voucher is already redeemed.
Procedure
4.1442 TP30083
Description
The currency type does not match the currency type of the transaction account.
Scenario
When the account balance of a transaction is updated, the transaction currency does not match
the account currency.
Access Channel
Web, STK, USSD, API
Possible Causes
The currency type specified for the transaction does not match the currency type of the
transaction account.
Procedure
Verify the currency type settings.

Copyright © Huawei
Mobile Money
4.1443 TP30084
Description
The amount to be unfrozen must not be greater than the frozen amount.
Scenario
During batch transaction execution, the amount requested to be frozen is greater than the
frozen amount.
Access Channel
Web, STK, USSD, API
Possible Causes
The amount to be unfrozen is greater than the frozen amount.
Procedure
Verify the amount to be unfrozen.
4.1444 TP30085
Description
Vouchers of this type cannot be exchanged.
Scenario
During a voucher exchange, the current reason type does not support the specified voucher
type.
Access Channel
Web, STK, USSD, API
Possible Causes
The current reason type does not support the specified voucher type.
Procedure
Select a voucher type supported by the specified reason type.

Copyright © Huawei
Mobile Money
4.1445 TP30086
Description
The receiver must be set to a voucher code.
Scenario
The voucher to be exchanged does not exist.
Access Channel
Web, STK, USSD, API
Possible Causes
The receiver must be set to a voucher code during voucher exchange.
Procedure
Set the receiver to a voucher code.
4.1446 TP30091
Description
The voucher credential is empty.
Scenario
An exception occurred during voucher authentication.
Access Channel
Web, STK, USSD, API
Possible Causes
An exception occurred during voucher authentication.
Procedure

Copyright © Huawei
Mobile Money
4.1447 TP30092
Description
The transaction receiver does not exist.
Scenario
The transaction receiver does not exist (operator and customer creation is not involved in the
transaction).
Access Channel
Web, STK, USSD, API
Possible Causes
The transaction receiver does not exist.
Procedure
Enter a correct receiver.
4.1448 TP30093
Description
The organization status is invalid.
Scenario
During transaction initiation, the organization to which an operator belongs is in the Suspend
status.
Access Channel
Web, STK, USSD, API
Possible Causes
Transaction failed due to invalid organization status.
Procedure
Verify the organization status.

Copyright © Huawei
Mobile Money
4.1449 TP30094
Description
The identity type does not exist or is invalid.
Scenario
During query of latest transaction records, the value of Identity Type is not an organization
operator or customer.
Access Channel
Web, STK, USSD, API
Possible Causes
Only transaction records of operators and customers can be queried.
Procedure
Verify the operator's permission.
4.1450 TP30095
Description
The KYC information does not meet the KYC verification rules of the reason type.
Scenario
The KYC information of the transaction customer does not meet the KYC verification rules of
the reason type.
Access Channel
Web, STK, USSD, API
Possible Causes
The KYC information of the transaction customer does not meet the KYC verification rules of
the reason type.
Procedure
Select a correct customer for the transaction.

Copyright © Huawei
Mobile Money
4.1451 TP30096
Description
The number of voucher code attempts has reached {0}.
{0}: indicates number of failure times.
Scenario
During a voucher exchange, the number of incorrect voucher codes entered by an operator
reaches the threshold, and therefore, the operator enters the Suspended state.
Access Channel
Web, STK, USSD, API
Possible Causes
The identity is suspended after {0} voucher code attempts.
Procedure
Activate the identity and try again.
4.1452 TP30110
Description
The {0} parameter is empty.
{0}: indicates mandatory parameter.
Scenario
The mandatory parameter for initiating a transaction, for example, bulk processing transaction
or reversal transaction, is empty.
Access Channel
Web, STK, USSD, API
Possible Causes

Copyright © Huawei
Mobile Money
Procedure
Verify that mandatory parameters are correctly configured.
4.1453 TP30111
Description
The {0} parameter does not exist or is invalid.
{0}: indicates original parameter value.
Scenario
The parameter specified for initiating a transaction is invalid or does not exist in the system.
Access Channel
Web, STK, USSD, API
Possible Causes
The {0} parameter specified for the transaction is invalid or does not exist in the system.
Procedure
Verify the parameter value and system settings.
4.1454 TP30112
Description
The {0} record is already processed.
{0}: indicates number of a batch task, for example, 1.
Scenario
During batch bulk payment processing, the current bulk payment record has been processed.
Access Channel
Web, API
Possible Causes
The {0} record of the bulk payment transaction is already processed.

Copyright © Huawei
Mobile Money
Procedure
Verify the status of the transaction to be processed.
4.1455 TP30113
Description
The bulk transaction is cancelled.
Scenario
A batch processing task has been cancelled.
Access Channel
Web, API
Possible Causes
The bulk payment transaction is cancelled.
Procedure
Verify the status of the transaction to be processed.
4.1456 TP30114
Description
No matching data is found in the system.
Scenario
The voucher type set for applying for a voucher is invalid.
Access Channel
Web, STK, USSD, API
Possible Causes
No matching data is found in the system or a system data exception has occurred.
Procedure

Copyright © Huawei
Mobile Money
4.1457 TP30115
Description
The specified session ID is invalid.
Scenario
The conversation ID sent back during a transaction does not exist or is invalid.
Access Channel
Web, USSD, API
Possible Causes
The specified session ID does not exist or has expired.
Procedure
Enter a valid session ID.
4.1458 TP30116
Description
The request message cannot be empty when a voucher is resent.
Scenario
The request message is empty when a voucher is resent. Resend Voucher
Access Channel
Web
Possible Causes
The request message is empty when a voucher is resent.
Procedure

Copyright © Huawei
Mobile Money
4.1459 TP30117
Description
The voucher ID in the request cannot be empty when a voucher is resent.
Scenario
The voucher ID in the request is empty when a voucher is resent. Resend Voucher
Access Channel
Web
Possible Causes
The voucher ID in the request is empty when a voucher is resent.
Procedure
4.1460 TP30119
Description
The channel must be set to web for a voucher to be resent.
Scenario
The channel for resending a voucher is not web. Resend Voucher
Access Channel
Web
Possible Causes
The initiation channel is incorrect when a voucher is resent.
Procedure
Send the voucher through the web channel.

Copyright © Huawei
Mobile Money
4.1461 TP30120
Description
The initiator cannot be empty when a voucher is resent.
Scenario
The initiator ID or type for resending a voucher is blank. Resend Voucher
Access Channel
Web
Possible Causes
The initiator is empty when a voucher is resent.
Procedure
4.1462 TP30123
Description
The operator has no permission to query the account of the specified organization.
Scenario
When querying balance, an organization operator does not have the permission to query the
account of a specified organization.
Access Channel
Web, STK, USSD, API
Possible Causes
The operator has no permission to query the account of the specified organization.
Procedure
Execute the transaction as an operator who has the permission to query the organization's
account.

Copyright © Huawei
Mobile Money
4.1463 TP30124
Description
The operator is not associated with the organization to be queried.
Scenario
When querying balance, an organization operator does not have the permission to query
information about a specified organization.
Access Channel
Web, STK, USSD, API
Possible Causes
The operator is not associated with the organization to be queried.
Procedure
Perform the operation as an operator of the organization to be queried.
4.1464 TP30125
Description
Failed to purchase the airtime.
Scenario
The MNO returns a failure during an airtime purchase transaction.
Access Channel
Web, STK, USSD, API
Possible Causes
The MNO returns a failure during an airtime purchase transaction.
Procedure
Contact the MNO based on the error information.

Copyright © Huawei
Mobile Money
4.1465 TP30127
Description
Failed to change the language because the old and new languages are the same.
Scenario
The specified new language is the same as the old language during a language change
operation.
Access Channel
Web, STK, USSD, API
Possible Causes
The specified new language is the same as the old language during a language change
operation.
Procedure
Set the new language to a different language.
4.1466 TP30130
Description
No customer is found for the {0} O2C link.
{0}: indicates O2C Link.
Scenario
During a pay bill transaction, no customer is found based on an O2Clink.
Access Channel
Web, STK, USSD, API
Possible Causes
No customer is found based on the specified O2C link.
Procedure
Enter a valid O2C link.

Copyright © Huawei
Mobile Money
4.1467 TP30131
Description
The current transaction does not support unregistered customers.
Scenario
A non-registered subscriber participates a transaction that does not support non-registered
subscribers. Send Money
Access Channel
Web, STK, USSD, API
Possible Causes
The reason type configuration for the current transaction does not support unregistered
customers.
Procedure
Perform the transaction as a registered customer.
4.1468 TP30136
Description
The voucher type code is empty or incorrect when Reason Type is set to {0}.
Scenario
During voucher application or exchange, the voucher type is blank or is not supported.
Access Channel
Web, STK, USSD, API
Possible Causes
The voucher type code is empty or incorrect when Reason Type is set to {0}.
Procedure
Enter a correct voucher type code in the request message.

Copyright © Huawei
Mobile Money
4.1469 TP30140
Description
The {0} mandatory parameter is not configured for Reason Type {2} in the {1} status.
{0}: indicates value of Reason Type, for example, Notification Type.

{1}: indicates transaction status.
{2}: indicates reason type name.
Scenario
Mandatory activity parameters are not configured in the reason type template.
Access Channel
Web, STK, USSD, API
Possible Causes
Certain mandatory parameters are not configured for the reason type.
Procedure
Ask the SP operator to modify the reason type configurations.
4.1470 TP30141
Description
The {0} parameter is configured for Reason Type {2} in the {1} state.
{0}: indicates value of Reason Type, for example, Notification Type.

{1}: indicates transaction status.
{2}: indicates reason type name.
Scenario
The credit and debit parties for the reason type of an associated airtimeCommission
transaction are not SP, the channel is not System, and initiators do not include sp_operator.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The associated reason type does not meet the roll-up requirements for SP airtime
commissions.
Procedure
Ask the SP operator to modify the reason type configurations.
4.1471 TP30150
Description
The account type does not exist.
Scenario
During balance or ministatement query, the account type is not found.
Access Channel
Web, STK, USSD, API
Possible Causes
The account type specified by the identity does not exist.
Procedure
Enter a correct account type and submit the request again.
4.1472 TP30160
Description
You are not the initiator of the transaction.
Scenario
In a transaction initiated by an API, the initiator in the confirmation request is inconsistent
with the initiator in the transaction request. (The packet sent by the API is inconsistent with
that in a transaction request.)
Access Channel
API

Copyright © Huawei
Mobile Money
Possible Causes
The initiator in the confirmation request is inconsistent with the initiator in the transaction
request.
Procedure
Log in as the initiator of the transaction and confirm the transaction.
4.1473 TP30170
Description
All records fail to be processed, and the scheduled task is terminated abnormally.
Scenario
All records in the current batch fail to be processed, resulting in an abnormal termination of
the scheduled task.
Access Channel
Web, API
Possible Causes
All records in the current batch fail to be processed, resulting in an abnormal termination of
the scheduled task.
Procedure
1. Choose My Functions > Bulk > Bulk Task Plan History.
2. Click Search to query for the abnormal task and clicks Details to view the error
information.
3. Check and modify the bulk processing file based on the error information.
4. Execute the bulk task again.
4.1474 TP30201
Description
The format of the time is incorrect.
Scenario
The date for querying a Cash Up transaction is in an incorrect format.

Copyright © Huawei
Mobile Money
Access Channel
STK, USSD, API
Possible Causes
The format of the start time and end time does not meet the system requirements.
Procedure
Enter a start time and end time in the correct format and query again.
4.1475 TP30202
Description
The time is incorrect.
Scenario
The specified start time is later than the end time during cash up query.
Access Channel
STK, USSD, API
Possible Causes
The specified start time is later than the end time.
Procedure
Verify that the start time is earlier than the end time and query again.
4.1476 TP30203
Description
The current operator has no permission to perform this operation.
Scenario
The current operator has no permission to query cash-up statements when querying a Cash Up
transaction.
Access Channel
STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
The current operator has no permission to query cash-up statements.
Procedure
Ask the system administrator to assign the permission to the operator.
4.1477 TP30204
Description
Operator {0} has no permission to perform the {1} service.
The {0} variable indicates an operator identity, such as operator short code and operator ID.
The {1} variable indicates a service name.
Scenario
The operator does not have the permission to initiate the service during transaction initiation.
Access Channel
Web, STK, USSD, API
Possible Causes
Permission authentication failed.
Procedure
Ask the system administrator to assign the permission to the operator.
4.1478 TP30205
Description
The time is incorrect.
Scenario
The specified start time is later than the current time during cash up transaction.
Access Channel
STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
The specified start time is later than the current time.
Procedure
Verify that the start time is not later than the current time.
4.1479 TP30207
Description
The charge credit party is in an invalid status.
Scenario
The charge credit party of the transaction is in the invalid status and not allowed to perform
the transaction.
Access Channel
Web, STK, USSD, API
Possible Causes
The charge credit party of the transaction is in the {0} status and not allowed to perform
transactions.
The {0} variable indicates the credit user status, for example, Close.
Procedure
Please contact Customer Care.
4.1480 TP30208
Description
The charge debit party is in an invalid status.
Scenario
The charge debit party of the transaction is in the invalid status and not allowed to perform
transactions.
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
The charge debit party of the transaction is in the {0} status and not allowed to perform
transactions.
The {0} variable indicates the debit user status, for example, Close.
Procedure
Please contact Customer Care.
4.1481 TP30209
Description
The account of the charge credit party is in an invalid status.
Scenario
The account of the charge credit party of the transaction is in the invalid status and cannot be
used to perform transactions.
Access Channel
Web, STK, USSD, API
Possible Causes
The account of the charge credit party of the transaction is in the {0} status and cannot be
The {0} variable indicates the credit account status, for example, Close.
Procedure
Ask the system administrator to change the account status of the charge credit party.
4.1482 TP30210
Description
The account of the charge debit party is in an invalid status.
Scenario
The account of the charge debit party of the transaction is in the invalid status and cannot be

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
The account of the charge debit party of the transaction is in the {0} status and cannot be used
to perform transactions.
The {0} variable indicates the debit account status, for example, Close.
Procedure
Ask the system administrator to change the account status of the charge debit party.
4.1483 TP30211
Description
The SP short code does not exist.
Scenario
The short code of the SP is deleted due to a system exception.
Access Channel
Web, STK, USSD, API
Possible Causes
Failed to authenticate the SP short code.
Procedure
Enter a correct SP short code and perform the transaction again.
4.1484 TP30230
Description
Invalid profit allocation information.
Scenario
Profit sharing data is incorrectly configured due to a system exception. As a result,
commission profit sharing performed during transaction execution fails.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
The transaction profit allocation is incorrectly configured.
Procedure
Contact the SP for help or log in as an SP operator and perform the following operations:
1. Log in as an SP operator.
2. Choose My Functions > Core Configuration > Advanced Configuration > Charge
Distribution Model.
3. Configure correct profit allocation information.
4.1485 TP30231
Description
The {0} system parameter cannot be obtained.
The {0} variable indicates the name of a system parameter.

Example: AG_BILL_CONFIRM_MAX_RESEND_DURATION
Scenario
System parameters are incorrectly configured. The parameter of the long type is set to a value
that carries letters.
Access Channel
Web, STK, USSD, API
Possible Causes
The {0} system parameter is incorrectly configured.
Procedure
3. Find the system parameter and click Edit to change the parameter value as prompted.

Copyright © Huawei
Mobile Money
4.1486 TP30300
Description
No rule for verifying the bill reference number is obtained based on short code {0}.
Scenario
The rule for verifying the bill reference number is not configured in a pay bill transaction.
Access Channel
Web, USSD, API
Possible Causes
No verification rule is configured for the organization bill reference number.
Procedure
2. Choose Search > Organization.
3. Enter the organization short code and click Search.
4. Click Operation and configure the Bill Reference Number.
5. Execute the bill payment transaction again.
4.1487 TP30301
Description
Cannot obtain the bill reference number.
Scenario
In a pay bill transaction, the initiator does not enter a bill reference number.
Access Channel
Web, USSD, API
Possible Causes
The bill reference number is not specified and cannot be obtained from historical records.
Procedure
Enter a bill reference number and execute the bill payment transaction again.

Copyright © Huawei
Mobile Money
4.1488 TP30302
Description
The format of the bill reference number does not match the format required for bills.
Scenario
Internal verification of a pay bill transaction fails because the bill reference number entered
by the initiator does not comply with verification rules.
Access Channel
Web, USSD, API
Possible Causes
Failed to authenticate the bill reference number.
Procedure
Enter a correct bill reference number.
4.1489 TP30303
Description
Failed. Business {0} declined your payment of {1} because {2}. Please contact {3} for more
information.
The {0} variable indicates the name of an organization, {1} indicates the amount, {2} indicates the
failure cause returned by a third party, and {3} indicates the name of another organization.
Scenario
The third-party verification on a bill reference number fails in a pay bill transaction.
Access Channel
Web, USSD, API
Possible Causes
Failed to authenticate the bill reference number.
Procedure
Enter a correct bill reference number.

Copyright © Huawei
Mobile Money
4.1490 TP30400
Description
The specified reason type is incorrect.
Scenario
Cached data is not synchronized or is abnormal. As a result, querying the reason type during
transaction execution fails.
Access Channel
Web, STK, USSD, API
Possible Causes
The specified reason type does not exist in the system.
Procedure
Reinitiate the transaction and enter a correct reason type.
4.1491 TP30401
Description
Failed to obtain the reason type of the original transaction.
Scenario
The reason type of the original transaction is deleted during reverse due to a system
exception.
Access Channel
Web, USSD, API, STK
Possible Causes
No reason type is recorded for the original transaction or the reason type does not exist in the
system.
Procedure
The transaction data is invalid. Ask a Huawei engineer to repair the data.

Copyright © Huawei
Mobile Money
4.1492 TP30402
Description
Scenario
Incomplete transactions are reversed.
Access Channel
Web, USSD, API, STK
Possible Causes
The transaction has not been completed and therefore cannot be reversed.
Procedure
Reverse the transaction after it is completed.
4.1493 TP30403
Description
Scenario
Transactions generated during action operations are reversed.
Access Channel
Web, USSD, API, STK
Possible Causes
Action-related transactions cannot be reversed.
Procedure
Select a transaction that can be reversed.

Copyright © Huawei
Mobile Money
4.1494 TP30404
Description
Scenario
The original transaction has been reversed. (The possible scenario is as follows: Two
operators reserve the same transaction at the same time. A transaction is successfully reserved,
and the system displays the error code for B who attempts to reserve the same transaction.)
Access Channel
Web, USSD, API, STK
Possible Causes
The original transaction has been reversed.
Procedure
Refresh the transaction list and view serial numbers of reversed transactions.
4.1495 TP30405
Description
Scenario
The transaction type of the original transaction does not support reverse.
Access Channel
Web, USSD, API, STK
Possible Causes
The type of the original transaction does not support reverse.
Procedure
Verify whether the transaction needs to be reversed and contact a Huawei engineer for help
when necessary.

Copyright © Huawei
Mobile Money
4.1496 TP30406
Description
Scenario
The system determines that a user has no permission to execute a transaction.
Access Channel
Web, USSD, API, STK
Possible Causes
No reverse reason type is configured for the reason type of the original transaction.
Procedure
Type.
3. Click Add to add a reason type, set Transaction Type to Transaction Reversal, and click
Add under Original Reason Type to add a reason type for the original transaction to be
reversed.
4. Configure other information and release the reason type.
5. Reverse the transaction again.
4.1497 TP30407
Description
Permission authentication failed.
Scenario
The system determines that a user has no permission to execute a transaction.
Access Channel
Web, STK, USSD, API
Possible Causes
The current user has no permission to execute the {0} transaction.
The {0} variable indicates a reason type name.

Copyright © Huawei
Mobile Money
Example: create customer
Procedure
Select a user that has the permission to execute the transaction, or ask the system
administrator to assign the permission for executing the transaction to the current user.
4.1498 TP30408
Description
Only the transaction credit party and SP operator can reverse the transaction.
Scenario
The customer or organization operator initiated the reverse operation is not the credit party of
the original transaction.
Access Channel
Web, USSD, API, STK
Possible Causes
The initiator is not the transaction credit party or an SP operator. The authentication fails and
reversing the transaction fails.
Procedure
Contact the transaction credit party or SP operator to reverse the transaction.
4.1499 TP30409
Description
The original transaction is being reversed and cannot be initiated again.
Scenario
This error is reported when the reverse application of the original transaction is submitted and
is waiting for approval or processing but another application is submitted.
Access Channel
Web, USSD, API, STK
Possible Causes
The original transaction is being reversed and is waiting for approval or processing.

Copyright © Huawei
Mobile Money
Procedure
Wait for processing completeness.
4.1500 TP30450
Description
The transaction is in the {0} status and cannot be performed.
The {0} variable indicates the transaction status.
Scenario
A completed transaction is executed again due to a system exception.
Access Channel
Web, STK, USSD, API
Possible Causes
The transaction is in a final status and cannot be executed again.
Procedure
The current transaction is in the final status {0}. Refresh the transaction list to view details.
4.1501 TP30454
Description
The amount format is incorrect and cannot be parsed by the system.
Scenario
The amount is invalid. For example, the amount contains non-digit characters.
Access Channel
STK, USSD, API
Possible Causes
The input amount format is incorrect and cannot contain characters and special characters.

Copyright © Huawei
Mobile Money
Procedure
Enter the amount in the correct format and initiate the transaction again.
4.1502 TP30455
Description
The amount precision is large and the maximum amount precision supported by the system is
{0}.
The {0} variable indicates the maximum amount precision supported by the system.
Scenario
The transaction amount precision exceeds the maximum precision supported by the system.
Access Channel
Web, STK, USSD, API
Possible Causes
The input amount precision exceeds the maximum precision supported by the system.
Procedure
Initiate the transaction again and ensure that the maximum amount precision does not exceed
{0}.
4.1503 TP35002
Description
The source of the refund amount is incorrect and the refund application is rejected.
Scenario
When a customer applies for refund, the dormant records of the customer are not found. The
dormant records of the customer are deleted due to a system exception.
Access Channel
Web
Possible Causes
The refund amount does not come from an identity's dormant account or SP holding account.

Copyright © Huawei
Mobile Money
Procedure
Ask a Huawei engineer to check and repair data.
4.1504 TP35005
Description
Refund is not supported because the account balance of the identity is 0.
Scenario
When a customer applies for refund, the customer's dormant account amount is 0.
Access Channel
Web
Possible Causes
The account balance of the identity is 0.
Procedure
Do not refund using an identity account with no balance.
4.1505 TP35006
Description
The refund request is not supported.
Scenario
A customer applies for refund again after a successful refund.
Access Channel
Web
Possible Causes
The refund request is already processed.
Procedure
Do not submit a refund request repetitively.

Copyright © Huawei
Mobile Money
4.1506 TP35007
Description
Scenario
The balance in the dormant account has been transferred to the unclaimed account of the SP
and applies for the transfer.
Access Channel
Web
Possible Causes
The balance in the dormant account has been transferred to the unclaimed account of the SP.
Procedure
Do not refund an amount that is transferred to the unclaimed account of an SP.
4.1507 TP35008
Description
There is no dormant record.
Scenario
When an identity applies for refund, the dormant records of the identity are not found.
Access Channel
Web
Possible Causes
The identity has no dormant record in the system.
Procedure
1. Choose Search > Customer.
2. Configure customer query conditions.
3. Check whether the customer is in the Dormant status on the customer details page.

Copyright © Huawei
Mobile Money
4.1508 TP35009
Description
The dormant record is in an invalid status.
Scenario
When an SP operator manually transfer account balance of a customer to an SP holding
account after the system fails to transfer the balance to SP holding account, the type of the
failed task is not to holding account.
Access Channel
Web
Possible Causes
The amount needs to be transferred to the SP hold account, but the current task is in the {0}
status.
The {0} variable indicates the type name of the failed task.
Example: to holding account
Procedure
1. Check whether the current task is in the TO_HOLDING_ACCOUNT status.
2. Ask a Huawei engineer to check and repair data.
4.1509 TP35010
Description
The refund application is being processed. Do not submit the refund application again.
Scenario
An identity applies for refund again.
Access Channel
Web
Possible Causes
The refund application is being processed.

Copyright © Huawei
Mobile Money
Procedure
Cancel the existing refund application in the system and reinitiate a refund application, or
approve and complete the existing refund application.
4.1510 TP35011
Description
The refund application is rejected.
Scenario
Executing the transaction for transferring the balance in the dormant account of a customer to
an SP holding account fails due to a system exception. The transaction is not in the Complete
status.
Access Channel
Web
Possible Causes
An account clearing request is being processed.
Procedure
Contact the system administrator for help and complete transactions in progress.
4.1511 TP35013
Description
Refund is not supported.
Scenario
After dormant balance is transferred to an SP holding account, a customer fails to apply for
refund if the account of the customer has balance.
Access Channel
Web
Possible Causes
Refund failed because the balance in an account is not cleared.

Copyright © Huawei
Mobile Money
Procedure
Clear the account first.
4.1512 TP35014
Description
Account clearing is not allowed.
Scenario
If an identity has Uncompleted transactions, that is, the value of Reserved Balance and
Uncleared Balance are not 0, setting the identity to the dormant status fails.
Access Channel
Web
Possible Causes
The account cannot be cleared due to an ongoing transaction.
Procedure
Complete the transaction first.
4.1513 TP36500
Description
The organization whose commission is to be settled does not exist.
Scenario
During commission settlement, querying organization information based on an organization
short code fails due to a system exception.
Access Channel
Web
Possible Causes
No organization information is found based on the {0} organization ID.

Example: 10083

Copyright © Huawei
Mobile Money
Procedure
2. Choose Search > Organization page.
3. Enter organization information for query.
4. Check whether the organization to be queried exists or whether the organization provides
the service. If the organization does not exist, enter the correct organization.
4.1514 TP36501
Description
A system exception has occurred during commission settlement.
Scenario
Debit Party or Credit Party for Transaction Type or Reason Type is blank due to a system
exception.
Access Channel
Web
Possible Causes
System exception {0} has occurred during commission settlement.
The {0} variable indicates the description of a parameter.
Procedure
4.1515 TP36503
Description
The account information does not exist or the account is abnormal.
Scenario
The account of the original transaction is deleted during transaction reverse due to a system
exception.
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
No account information is found based on {0}.
The {0} variable indicates the account number of the original transaction.
Procedure
 If an SP account does not exist, choose Search > Service Provider > Bank&Account >
Internal Account and add account information.
 If an organization account does not exist, ask the SP administrator to subscribe to a
product that contains the account for the organization.
4.1516 TP36504
Description
The commission settlement task does not exist.
Scenario
The commission task data is deleted due to a system exception.
Access Channel
Web
Possible Causes
No commission settlement approval task is found based on {0}.
The {0} variable indicates the task ID.
Procedure
4.1517 TP36506
Description
Failed to create the {0} workflow.
The {0} variable indicates the workflow name. Example: Commission Claw-back

Copyright © Huawei
Mobile Money
Scenario
The commission payment and commission claw-back workflow is closed due to a system
exception.
Access Channel
Web
Possible Causes
The {0} workflow is not available.
Procedure
1. Log in to the Portal as an SP operator.
2. Choose My Functions > Operation Support > Workflow > Workflow Management.
3. Query for and enable the workflow.
4.1518 TP36512
Description
The amount to be clawed back is incorrect.
Scenario
The amount of an applied claw back exceeds the amount of the original transaction.
Access Channel
Web
Possible Causes
The transaction is rejected because the amount to be clawed back is {0} and greater than the
original transaction amount {1}.
The {0} variable indicates the applied reverse amount.

The {1} variable indicates the actual transaction amount.
Procedure
Change the amount to be clawed back and initiate the transaction again.

Copyright © Huawei
Mobile Money
4.1519 TP36513
Description
The specified value does not match the original value during commission roll-up.
Scenario
A system exception occurs, and data is incorrect.
Access Channel
Web
Possible Causes
The approval workflow ID should be {1} instead of {0}.
The {0} variable indicates the input workflow ID.

The {1} variable indicates the correct work flow ID.
Procedure
4.1520 TP36514
Description
No commission claw-back record is found.
Scenario
Transaction data cannot be found based on a task ID during approval due to a system
exception.
Access Channel
Web
Possible Causes
No commission claw-back record is found based on the task ID {0}.
The {0} variable indicates a task ID.

Copyright © Huawei
Mobile Money
Procedure
4.1521 TP36515
Description
The transaction serial number of the commission claw-back task is empty.
Scenario
The transaction ID queried based on a task ID during approval is blank due to a system
exception.
Access Channel
Web
Possible Causes
No transaction serial number is found based on the task ID {0}.
The {0} variable indicates a task ID.
Procedure
4.1522 TP36516
Description
Organization {0} has an unfinished roll-up record in the system and is not allowed to roll-up
or claw-back transaction.
Scenario
This error occurs when an uncompleted commission roll-up task already exists and the task is
initiated again.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
Organization {0} has an unfinished roll-up record in the system.
Procedure
1. Choose My Functions > Finance > Process Commission > Commission Payment
2. Query for the unfinished roll-up transaction of organization {0} and complete the
transaction.
4.1523 TP36521
Description
Failed to reverse the transaction whose ID is {0}.
The {0} variable indicates a transaction ID.
Scenario
Commission reverse fails because the reverse transaction amount is incorrect, the balance is
insufficient, or the database fault occurs.
Access Channel
Web
Possible Causes
{1}
The {1} variable indicates the cause description of the reverse transaction failure.
Procedure
1. Choose My Functions > Operations > Transaction > Review Transaction.
2. Verify that data of the transaction whose ID is {0} is correct.
4.1524 TP36522
Description
Failed to cancel the transaction whose ID is {0}.

Copyright © Huawei
Mobile Money
Scenario
Canceling the reconciliation transaction.
Access Channel
Web
Possible Causes
{1}
The {1} variable indicates that transaction has already exported statements and cannot be cancelled.
Procedure
1. Log in to the SP Portal.
4.1525 TP36523
Description
Failed to resume the transaction whose ID is {0}.
Scenario
A transaction in the Authorized state times out, and the transaction session is released. As a
result, an operator fails to continue executing the transaction on the portal.
Access Channel
Web
Possible Causes
{1}
The {1} variable indicates the transaction failure cause.
Procedure
1. Log in to the SP Portal.

Copyright © Huawei
Mobile Money
4.1526 TP36524
Description
The transaction whose ID is {0} has been submitted and exported to a report, and therefore
cannot be reversed.
Scenario
A reconciliation transaction whose reconciliation reports are generated is reversed.
Access Channel
Web
Possible Causes
The current transaction has been submitted and exported to a report, and therefore cannot be
reversed.
Procedure
Select a transaction that is not submitted and can be reversed.
4.1527 TP39003
Description
The {0} transaction is cancelled.
Scenario
When a transaction in the Authorized status times out, the transaction is automatically or
manually updated to the Cancel status.
Access Channel
Web
Possible Causes
The transaction is manually cancelled because it has expired or another error has occurred.
Procedure
Confirm with the operator.

Copyright © Huawei
Mobile Money
4.1528 TP39004
Description
Conversation IDs in requests must be unique.
Scenario
Multiple API requests are considered as repeated requests because the values of
conversationid in the requests are the same.
Access Channel
API
Possible Causes
The conversation ID in the request already exists in the system.
Procedure
Enter a new conversation ID.
4.1529 TP39040
Description
Failed to obtain the default currency.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
No default currency is configured.
Procedure
Definition.
3. Set the Default Currency field.

Copyright © Huawei
Mobile Money
4.1530 TP39041
Description
Scenario
The default currency is incorrectly set during transaction processing.
Access Channel
Web, STK, USSD, API
Possible Causes
The default currency is incorrectly configured.
Procedure
Definition.
3. Verify whether the configured default currency meets the International Organization for
Standardization (ISO) 4127 standard. If no, manually modify the default currency.
4.1531 TP39042
Description
Failed to find a currency that matches the currency code.
Scenario
The entered transaction currency is not configured.
Access Channel
Web, STK, USSD, API
Possible Causes
The currency code is incorrect.
Procedure

Copyright © Huawei
Mobile Money

Definition.
3. Check whether the specified currency code exists. If not, check whether the specified
currency is correct or add new currency.
4.1532 TP39051
Description
The session does not exist or has timed out.
Scenario
Batch transaction initiation is not approved in a timely manner, which results in transaction
timeout.
Access Channel
Web
Possible Causes
The session does not exist or has been terminated.
Procedure
Check whether the transaction has expired or initiate a new session.
4.1533 TP39998
Description
The request has timed out.
Scenario
The BCS processing duration exceeds the maximum duration because the system is busy.
Access Channel
Web, STK, USSD, API
Possible Causes
The system is busy, and the request has timed out.

Copyright © Huawei
Mobile Money
Procedure
Try again later.
4.1534 TP39999
Description
The system is busy.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
An unknown exception has occurred. Obtain the tracing log for fault diagnosis.
Procedure
http://icare.huawei.com and submit a fault application report.
4.1535 TP40000
Description
Task execution failed.
Scenario
All manual tasks
Access Channel
Web
Possible Causes
The task fails due to a system exception.
Procedure
Resolve the system exception and try the task again.

Copyright © Huawei
Mobile Money
4.1536 TP40001
Description
A message is successfully sent, but callback is not executed.
Scenario
RPC messages for all manual tasks
Access Channel
Web, STK, USSD, API
Possible Causes
Callback is not executed.
Procedure
Execute the callback operation.
4.1537 TP40002
Description
Task failed due to manual redo timeout.
Scenario
Manual intervention task
Access Channel
Web
Possible Causes
Manual redo timed out.
Procedure
Process the manual redo correctly.

Copyright © Huawei
Mobile Money
4.1538 TP40003
Description
Cannot find the KYC information of the identity ID.
Scenario
Manual task for modifying the KYC information of an identity
Access Channel
Web
Possible Causes
Identity {0} has no KYC information.
{0}: indicates the identity name to be modified.
Procedure
4.1539 TP40004
Description
Scenario
All actions and transactions that involve organizations
Access Channel
Web, STK, USSD, API
Possible Causes
The organization to be queried does not exist.
Procedure

Copyright © Huawei
Mobile Money
4.1540 TP40005
Description
The parameter value is incorrect. No till is found.
Scenario
All actions and transactions that involve tills
Access Channel
Web, STK, USSD, API
Possible Causes
The {0} parameter is incorrect.
{0}: indicates a till number.
Procedure
Enter a correct value for the {0} parameter to query for the till information.
4.1541 TP40006
Description
The parameter value is incorrect. No SP is found based on the SP ID.
Scenario
All actions and transactions that involve the SP
Access Channel
Web, STK, USSD, API
Possible Causes
{0}: indicates an SP name.
Procedure
Enter a correct value for the {0} parameter to query for the SP.

Copyright © Huawei
Mobile Money
4.1542 TP40007
Description
The parameter value {0} is incorrect. No organization is found based on the organization ID
or short code.
{0}: Indicates the ID or short code of an organization.
Scenario
All actions and transactions that involve organizations.
Access Channel
Web, STK, USSD, API
Possible Causes
The parameter value {0} is incorrect.
Procedure
Enter a correct value for the parameter to query for the organization.
4.1543 TP40008
Description
Failed to initialize the service context, because {0}.
{0} indicates an error message.
Scenario
All services processed by the IC and TC
Access Channel
Web, STK, USSD, API
Possible Causes
The identity IO object is empty.
Procedure

Copyright © Huawei
Mobile Money
4.1544 TP40009
Description
Failed to parse the information.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
 The identity ID is empty.
 The identity type is empty.
Procedure
The Identity Type and Identity ID fields are mandatory. The identity type must be set to
Customer, SP, SP operator, Organization, Organization Operator, Till, or Bank as enumerated
in the Identity Type field.
4.1545 TP40010
Description
The operator that initiates the transaction does not exist.
Scenario
All transactions initiated by operators
Access Channel
Web, STK, USSD, API
Possible Causes
The initiator does not exist.
Procedure

Copyright © Huawei
Mobile Money
4.1546 TP40011
Description
The parameter value is incorrect. No O2C link object is found based on the specified link
number.
Scenario
O2C transaction
Access Channel
Web, STK, USSD, API
Possible Causes
{0}: indicates the number of an O2C link.
Procedure
Enter a correct value for the {0} parameter to query for the O2C link.
4.1547 TP40012
Description
The parameter value is incorrect. The service that is found based on the {0} command word is
not supported by the system.
{0}: indicates a command word.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes

Copyright © Huawei
Mobile Money
Procedure
Enter a value for the {0} parameter.
4.1548 TP40013
Description
{0}: indicates the name of the parameter that is empty.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
The request parameter is empty.
Procedure
4.1549 TP40014
Description
The parameter value is incorrect. No order is found based on the order ID.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
{0}: indicates an order number.

Copyright © Huawei
Mobile Money
Procedure
4.1550 TP40015
Description
The parameter value is incorrect. No task is found based on the task ID.
Scenario
All services that are processed in a workflow
Access Channel
Web, STK, USSD, API
Possible Causes
{0}: Indicates the ID of a task.
Procedure
Check whether the task whose ID is {0} exists.
4.1551 TP40016
Description
No session is found based on the {0} order ID.
{0}: indicates the ID of an order.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes

Copyright © Huawei
Mobile Money
Procedure
Enter a correct value for the {0} parameter.
4.1552 TP40017
Description
The parameter value is incorrect. The order found based on the {0} order ID has expired.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
4.1553 TP40018
Description
The order session found based on the {0} parameter has expired.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes

Copyright © Huawei
Mobile Money
Procedure
4.1554 TP40019
Description
The order obtained based on the workflow ID {0} is not in the Pending status, and the system
reports an error if the order is changed to the Authorized status.
Scenario
All services that are processed in a workflow.
Access Channel
Web, STK, USSD, API
Possible Causes
The workflow ID {0} is incorrect.
Procedure
Set the workflow ID {0} to a correct value to query for orders in the Pending status.
4.1555 TP40020
Description
The order obtained based on the order ID is not in the Pending state (being processed).
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes

Copyright © Huawei
Mobile Money
Procedure
Set the {0} parameter to a correct value to query for orders in the Pending state.
4.1556 TP40021
Description
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
4.1557 TP40022
Description
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes

Copyright © Huawei
Mobile Money
Procedure
4.1558 TP40023
Description
The value of the {0} parameter (indicating the current network type) is incorrect.
{0}: indicates the type of an NE.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
4.1559 TP40024
Description
System error.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
System error: {0}.

Copyright © Huawei
Mobile Money
{0}: indicates a program exception message.
Procedure
4.1560 TP40025
Description
The number of fields in the {0} parameter is incorrect.
{0}: indicates the name of a parameter.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
4.1561 TP40026
Description
In the {0} parameter, the {1} parameter must be set to a numeral.
{0}: indicates the file content.

{1}: indicates the field name.
Scenario
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
A parameter is incorrect.
Procedure
Enter a correct value for the parameter.
4.1562 TP40027
Description
No file is found based on the {0} parameter (indicating the file name).
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
{0}: indicates the name of a file.
Procedure
4.1563 TP40028
Description
The lengths of the {0} parameter and {1} parameter are different.
{0}: indicates the start number.

{1}: indicates the end number.
Scenario
Configure a number segment.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
Procedure
Verify that lengths of the start and end numbers are the same.
4.1564 TP40029
Description
Failed to create the {0} file directory.
{0}: indicates the name of a file directory.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
The file does not exist and cannot be created.
Procedure
4.1565 TP40030
Description
An exception has occurred when the system obtains the exception code for incorrect stacks
due to a system data configuration error.
Scenario

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
System data is incorrectly configured.
Procedure
4.1566 TP40031
Description
In {0}, the value must be set to {1}.
{0}: indicates the name of a function parameter.

{1}: indicates the value range of a parameter.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
The parameter value is incorrect.
Procedure
Set the {0} parameter to {1}.
4.1567 TP40032
Description
In the {0} parameter, the {1} parameter is mandatory.
{0}: indicates the content of a configuration file.

{1}: indicates the name of a parameter in a configuration file.

Copyright © Huawei
Mobile Money
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
Specify a value for the parameter.
4.1568 TP40033
Description
The date format is incorrect.
Scenario
All operations that involve date changes
Access Channel
Web, STK, USSD, API
Possible Causes
 The date length is incorrect.
 The date entered is not a numeral.
Procedure
Verify that the date is correct. Enter the date in the correct format.
4.1569 TP40034
Description
In the {0}, the value of {1} must be an integer.


Copyright © Huawei
Mobile Money
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
 The value is not empty.
 The value exceeds the value range of an integer.
Procedure
Set the parameter to a correct value.
4.1570 TP40035
Description
In the {0}, the value of {1} must be a long integer.

Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
 The value exceeds the value range of a long integer.
Procedure
4.1571 TP40036
Description
In {0}, the value of {1} must not be less than {2}.

Copyright © Huawei
Mobile Money

{2}: indicates the minimum value of a parameter.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
In the {0} parameter, the value of the {1} parameter is less than the value of {2}.
Procedure
4.1572 TP40037
Description
In {0}, the value of {1} must not be greater than {2}.

{2}: indicates the maximum value of a parameter.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
In the {0} parameter, the value of the {1} parameter is greater than the value of {2}.
Procedure

Copyright © Huawei
Mobile Money
4.1573 TP40038
Description
In {0}, the value of {1} must not be shorter than {2}.

{2}: indicates the minimum length of a parameter.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
The field value is shorter than the minimum length.
Procedure
4.1574 TP40039
Description
In {0}, the value of {1} must not be longer than {2}.

{2}: indicates the maximum length of a parameter.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
The field value is longer than the maximum length.

Copyright © Huawei
Mobile Money
Procedure
4.1575 TP40040
Description
In the {0}, the value of {1} is invalid.

Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
The field value is invalid.
Procedure
4.1576 TP40041
Description
The size of {0} has exceeded {1}.
{0}: indicates the name of a file.

{1}: indicates the maximum size of a file.
Scenario
Bulk file download
Access Channel
Web,

Copyright © Huawei
Mobile Money
Possible Causes
The file size has exceeded the upper limit.
Procedure
Set the parameter to an appropriate value.
4.1577 TP40042
Description
Failed to create a bank.
Scenario
The bank name format is verified when an SP operator creates a bank on the portal.
Access Channel
Web
Possible Causes
Failed to authenticate the bank name.
Procedure
Enter a bank name that meets the authentication rules.
4.1578 TP40043
Description
The parameter value is incorrect. The account type is not control account.
Scenario
The account type is not a control account when an SP operator creates a bank on the portal.
Access Channel
Web
Possible Causes

Copyright © Huawei
Mobile Money
{0} indicates an account type ID, for example, 10021.
Procedure
Enter an account number that indicates an SP control account.
4.1579 TP40045
Description
The account type of {0} is incorrect.
{0} indicates an account type ID, for example, 10021.
Scenario
The account type is not an internal account when an SP operator creates an SP internal
account.
Access Channel
Web
Possible Causes
The account type whose ID is {0} is not an internal account.
Procedure
Set the {0} parameter to an internal account type.
4.1580 TP40046
Description
The {0} initiator is in the {1} status which does not support the current service.

{1}: indicates the status of an initiator.
Scenario
All actions that require permission control

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
4.1581 TP40047
Description
The organization of the {0} initiator is in the {1} status which does not support the current
service.
{0}: indicates the organization to which an initiator belongs.

{1}: indicates the status of the organization to which an initiator belongs.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
Modify the status of the organization.
4.1582 TP40048
Description
The PIN of the {0} initiator is in the {1} status which does not support the current service.

{1}: indicates the PIN status of an initiator.

Copyright © Huawei
Mobile Money
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
Modify the PIN status of the transaction party.
4.1583 TP40049
Description
The password of the {0} initiator is in the {1} status which does not support the current
service.

{1}: indicates the password status of an initiator.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
4.1584 TP40050
Description
The {0} receiver is in the {1} status which does not support the current service.

Copyright © Huawei
Mobile Money
{0}: indicates the name of a recipient.

{1}: indicates the status of a recipient.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
Modify the status of the receiver party.
4.1585 TP40051
Description
The parent organization of the {0} receiver is in the {1} status which does not support the
current service.
{0}: indicates the name of the parent organization to which a recipient belongs.
{1}: indicates the status of the parent organization to which a recipient belongs.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
Modify the status of the organization.

Copyright © Huawei
Mobile Money
4.1586 TP40052
Description
The {0} primary party is in the {1} status which does not support the current service.
{0}: indicates the description for the primary party in a transaction.

{1}: indicates the type of an identity.
Scenario
All transactions that require permission control
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
4.1587 TP40053
Description
The {0} credit party is in the {1} status which does not support the current service.
{0}: indicates the name of the credit identity.

{1}: indicates the status of the credit identity.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes

Copyright © Huawei
Mobile Money
Procedure
4.1588 TP40054
Description
The {0} debit party is in the {1} status which does not support the current service.
{0}: indicates the name of the debit identity.

{1}: indicates the status of the debit identity.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
4.1589 TP40055
Description
The {0} charge credit party is in the {1} status which does not support the current service.
{0}: indicates the name of the charge credit identity.

{1}: indicates the status of the charge credit identity.
Scenario
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
Procedure
4.1590 TP40056
Description
The {0} charge debit party is in the {1} status which does not support the current service.
{0}: indicates the name of the charge debit identity.

{1}: indicates the status of the charge debit identity.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
4.1591 TP40057
Description
The {0} account of the charge credit party is in the {1} status which does not support the
current service.
{0}: indicates the name of the charge credit account.

{1}: indicates the status of the charge credit account.
Scenario

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
4.1592 TP40058
Description
The {0} account of the charge debit party is in the {1} status which does not support the
current service.
{0}: indicates the name of the charge debit account.

{1}: indicates the status of the charge debit account.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
4.1593 TP40059
Description
 The event type does not meet the requirement.
 The transaction identity information or role identity information is empty.
Scenario
The event type is incorrect, or transaction identity information, transaction role is empty.

Copyright © Huawei
Mobile Money
Access Channel
STK, USSD, API, Web
Possible Causes
 The event type is not WORKFLOW_CALLBACK.
 The transaction identity information or role identity information is empty.
Procedure
4.1594 TP40060
Description
The {0} service does not have Reason Type {1}.
{0}: indicates service code.

{1}: indicates reason type id.
Scenario
The service does not have a reason type.
Access Channel
STK, USSD, API, Web
Possible Causes
Procedure
4.1595 TP40061
Description
The {0} subaccount does not exist.

Copyright © Huawei
Mobile Money
Scenario
The account related to the reason type is not configured during the transaction.
Access Channel
STK, USSD, API, Web
Possible Causes
Procedure
4.1596 TP40062
Description
The transaction creation application is rejected.
Scenario
The result code does not meet the condition when a transaction approval task is created.
Access Channel
STK, USSD, API, Web
Possible Causes
The result code does not meet the condition.
Procedure
4.1597 TP40063
Description
The initiator and primary party must belong to the same organization.
Scenario
When an organization operator initiates a transaction, the initiator and the primary party do
not belong to the same organization.

Copyright © Huawei
Mobile Money
Access Channel
STK, USSD, API, Web
Possible Causes
The initiator and primary party belong to different organizations.
Procedure
Select a primary party that belongs to the same organization as the initiator.
4.1598 TP40064
Description
Scenario
The bank name exists when an SP operator creates a bank on the portal.
Access Channel
Web
Possible Causes
The bank name already exists.
Procedure
Change the bank name.
4.1599 TP40065
Description
Scenario
The bank name exists when an SP operator creates a bank on the portal.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
Account number {0} does not exist.
{0} indicates an account number, for example, 100000000100000106.
Procedure
Change the account number.
4.1600 TP40066
Description
Failed to create the bank card.
Scenario
The bank card exists when an SP operator creates a bank on the portal.
Access Channel
Web
Possible Causes
Account bank card {0} already exists.
{0} indicates an account number, for example, 100000000100000106.
Procedure
Change the ID of the bank card to be created.
4.1601 TP40067
Description
Bank type {0} is not found.
{0} indicates a catalog ID, for example, 1.
Scenario
The bank type does not exist in the data dictionary when an SP operator creates a bank on the
portal.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
Bank type {0} does not exist in the data dictionary.
Procedure
Select a bank type that exists in the data dictionary.
4.1602 TP40069
Description
Failed to allocate the task.
Scenario
The task status is incorrect when an SP operator or organization operator distributes tasks on
the portal.
Access Channel
Web
Possible Causes
The task status is incorrect.
Procedure
A system error has occurred. Contact a Huawei engineer for help.
4.1603 TP40070
Description
Failed to modify the state. Original state {0} cannot be changed to new state {1}.
{0} indicates the original status of the identity, for example, Active.
{1} indicates the target status of the identity, for example, New.
Scenario
The original status cannot be changed to the target status when an SP operator or organization
operator changes the identity status on the portal.

Copyright © Huawei
Mobile Money
Access Channel
Web, API, USSD, STK
Possible Causes
Original status {0} cannot be changed to new status {1}.
Procedure
Verify whether original status {0} cannot be changed to new status {1}. If yes, a system error
has occurred. Contact a Huawei engineer for help. If no, change the status to another target
status.
4.1604 TP40071
Description
{0}:{1} does not exist.
{0}: indicates the parameter name.

{1}: indicates the parameter value.
Scenario
All actions that need read configurations
Access Channel
Web, STK, USSD, API
Possible Causes
{0}:{1} does not exist.
Procedure
4.1605 TP40072
Description
Failed to close the account. The account has a balance and cannot be closed.

Copyright © Huawei
Mobile Money
Scenario
When an SP operator or organization operator wants to close the customer or organization on
the portal, the customer or organization cannot be closed because the account has balances.
Access Channel
Web
Possible Causes
The account has a balance and cannot be closed.
Procedure
Clear the account balance and try again.
4.1606 TP40073
Description
Operation failed. The organization name already exists.
Scenario
The organization name exists when an SP operator or organization operator creates an
organization or modifies an organization name on the portal.
Access Channel
Web
Possible Causes
The organization name already exists.
Procedure
Change the name of the organization.
4.1607 TP40074
Description
Failed to close the organization.

Copyright © Huawei
Mobile Money
Scenario
When an SP operator or organization operator closes an organization on the portal, the
organization cannot be closed because it has a child organization that is not closed.
Access Channel
Web
Possible Causes
The organization cannot be closed because it has sub organization(s).
Procedure
Verify that all child organizations are closed before closing the organization.
4.1608 TP40075
Description
Failed to modify the organization relationship.
Scenario
When an SP operator or organization operator changes the organization level relationships on
the portal, this error message is reported.
Access Channel
Web
Possible Causes
The {0} organization relationship already exists.
{0} indicates the task status, for example, Aggregator.
Procedure
Verify the organization relationship to be modified.
4.1609 TP40076
Description
The hierarchy relationship of the current organization cannot be changed.

Copyright © Huawei
Mobile Money
Scenario
Access Channel
Web
Possible Causes
The current organization is not at the second level.
Procedure
Check whether the current organization belongs to the second tier hierarchy. If no, the change
4.1610 TP40077
Description
The hierarchy relationship of the current organization cannot be changed.
Scenario
Access Channel
Web
Possible Causes
The parent organization hierarchy type is not Mixed.
Procedure
View the details page of the parent organization of the current organization, and confirm
whether the hierarchy type is mixed. If not, you cannot modify the hierarchical relationship of
the current organization.
4.1611 TP40078
Description
Failed to close the organization.

Copyright © Huawei
Mobile Money
Scenario
The organization to be closed has an unfinished transaction when an SP operator or
organization operator closes an organization on the portal.
Access Channel
Web
Possible Causes
The organization to be closed has an unfinished transaction.
Procedure
Verify that all transactions of an organization are finished before closing the organization.
4.1612 TP40079
Description
The name specified for the organization is in an incorrect format.
Scenario
1. The organization name format is incorrect when an SP operator or organization operator
creates an organization on the portal.
Access Channel
Web
Possible Causes
The organization name is in an incorrect format.
Procedure
Change the name of the organization.
4.1613 TP40080
Description
Failed to change the device.

Copyright © Huawei
Mobile Money
Scenario
The original device number does not exist when an SP operator or organization operator
changes the customer or till device on the portal.
Access Channel
Web, API
Possible Causes
The old device does not exist.
Procedure
Enter the correct original device number.
4.1614 TP40081
Description
Failed to create the till. The till number is in an incorrect format.
Scenario
The till number format is incorrect when an SP operator or organization operator creates a till.
Access Channel
Web, API
Possible Causes
The till number is in an incorrect format.
Procedure
Change the till number.
4.1615 TP40082
Description
Failed to update the device.
Scenario
The new device number does not exist when an SP operator or organization operator changes
the customer or till device on the portal.

Copyright © Huawei
Mobile Money
Access Channel
Web, API
Possible Causes
The new device does not exist.
Procedure
Change the device to another device.
4.1616 TP40083
Description
Failed to change the device.
Scenario
The new device number is the same as the original device number when an SP operator or
organization operator changes the customer or till device on the portal.
Access Channel
Web, API
Possible Causes
The new device is the same as the old one.
Procedure
Change the new device.
4.1617 TP40085
Description
Failed to add a device to the customer.
Scenario
When a device is added for a customer, the number of devices of the customer has reached the
upper limit.
Access Channel
Web, API

Copyright © Huawei
Mobile Money
Possible Causes
The number of the customer's devices has reached the upper limit.
Procedure
Verify whether the number of the customer's devices has reached the upper limit. If yes, delete
certain devices before adding the current one.
4.1618 TP40087
Description
The security credential of the subscriber is incorrect.
Scenario
All actions that require security certificate verification
Access Channel
Web, STK, USSD, API
Possible Causes
The value of {0} is incorrect.
{0}: indicates the name of a security certificate.
Procedure
4.1619 TP40088
Description
Failed to create the operator. Operator ID field is mandatory.
Scenario
If Handset is selected when an operator is created, the operator ID field is mandatory.
Access Channel
Web, API

Copyright © Huawei
Mobile Money
Possible Causes
If Access Channel is set to Handset when an operator is created, the Operator ID field is
mandatory.
Procedure
Enter a value for the Operator ID field.
4.1620 TP40089
Description
The bank is not found.
Scenario
All actions and transactions that involve banks
Access Channel
Web, STK, USSD, API
Possible Causes
The bank does not exist.
Procedure
Verify the query conditions.
4.1621 TP40090
Description
The {0} mandatory KYC field is empty.
{0}: indicates the name of a KYC field.
Scenario
A mandatory KYC field is empty when the KYC information of an Identity is created or
modified.
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
The {0} mandatory KYC field is empty.
Procedure
1. Choose My Functions > Operational Configuration > KYC Configuration > Assign
KYC to Identity Type.
2. Verify which KYC fields are mandatory for the Identity Type.
3. Return to the previous page and enter values for mandatory KYC fields.
4.1622 TP40091
Description
Failed to match the KYC information to any trust level.
Scenario
The specified KYC information is insufficient even for the lowest trust level when the KYC
information of an Identity is created or modified.
Access Channel
Web, STK, USSD, API
Possible Causes
The specified KYC information is insufficient even for the lowest trust level.
Procedure
1. Choose My Functions > Operational Configuration > SP Configuration > Trust
Level.
2. Verify the minimum KYC information required for the lowest trust level of the Identity
Type and subtype.
3. Return to the previous page and enter KYC information required for the lowest trust
level.
4.1623 TP40092
Description
Failed to update the KYC information.
Scenario
The trust level is degraded after the identity KYC information is updated.

Copyright © Huawei
Mobile Money
Access Channel
Web, API
Possible Causes
1. Certain mandatory KYC information is left empty when the KYC information is
updated.
2. More KYC information is required for the current trust level.
Procedure
1. Check the identity's Trust Level on the current page.
Level.
3. Verify the KYC fields required by the Trust Level.
4. Return to the previous page and enter KYC information required for the trust level.
4.1624 TP40093
Description
The rule profile does not apply to identity.
Scenario
The Trust Level selected when an identity is created is not associated with any rule profile.
Access Channel
Web, API
Possible Causes
The Trust Level of the identity is not associated with the rule profile.
Procedure
Identity Rule Profile.
3. Assign a rule profile for the trust level.
4.1625 TP40094
Description
Failed to create or modify the identity KYC.

Copyright © Huawei
Mobile Money
Scenario
When the KYC information of an identity is modified, no default rule profile is configured for
the current trust level.
Access Channel
Web, API
Possible Causes
The default rule profile of the current trust level is empty.
Procedure
2. Assign a default rule profile for the trust level.
4.1626 TP40095
Description
The charge profile does not apply to identity.
Scenario
When the KYC information of an identity is modified, no charge profile is associated with the
trust level.
Access Channel
Web, API
Possible Causes
The Trust Level of the identity is not associated with the charge profile.
Procedure
Charge Profile.
2. Assign a charge profile for the trust level.
4.1627 TP40096
Description
The value of Trust Level is incorrect.

Copyright © Huawei
Mobile Money
Scenario
An Identity is created or the trust level of the Identity is modified.
Access Channel
Web, STK, USSD, API
Possible Causes
The specified trust level exceeds the maximum level.
Procedure
Enter a new trust level in the valid range.
4.1628 TP40097
Description
Failed to update the identity's segment.
Scenario
The segment of an Identity is modified.
Access Channel
Web, USSD, API
Possible Causes
The current KYC information does not meet the KYC conditions of the selected segment to
be updated for an identity.
Procedure
1. Choose My Functions > Operational Configuration > SP Configuration > Segment.
2. Search for the KYC conditions of the current segment.
3. Return to the identity update page and enter KYC information which meets the KYC
conditions of the segment.
4.1629 TP40098
Description
{0} is locked.

Copyright © Huawei
Mobile Money
Scenario
Security operations are being verified.
Access Channel
Web, USSD, STK, API
Possible Causes
{0} is locked.
Procedure
Unlock the security credential and try again.
4.1630 TP40099
Description
The current security credential of the user has expired.
Scenario
Security operations are being verified.
Access Channel
Web, USSD, STK, API
Possible Causes
{0} has expired.
Procedure
1. Click My Preference at the upper-right corner of the page
2. Choose Basic Info > Change Password to change the password
3. In the navigation tree on the left, click Change PIN and change the PIN
4. In the navigation tree on the left, click Change Secret Word and change the secret
word.

Copyright © Huawei
Mobile Money
4.1631 TP40100
Description
The length of the security credential does not reach the lower limit.
Scenario
Access Channel
Web, USSD, STK, API
Possible Causes
The length of {0} is less than the minimum length {1}.

{1}: indicates minimum length.
Procedure
Enter a security credential with a correct length.
4.1632 TP40101
Description
The length of the security credential exceeds the upper limit.
Scenario
Access Channel
Web, USSD, STK, API
Possible Causes
The length of {0} is greater than the maximum length {1}.

{1}: indicates maximum length.

Copyright © Huawei
Mobile Money
Procedure
Enter a security credential with a correct length.
4.1633 TP40102
Description
The number of numerals in the security credential is incorrect.
Scenario
Access Channel
Web, USSD, STK, API
Possible Causes
{0} does not contain {1} numerals.

{1}: indicates number of digits that the security credential must contain.
Procedure
Enter a correct security credential.
4.1634 TP40103
Description
The number of letters in the security credential is incorrect.
Scenario
Access Channel
Web, USSD, STK, API
Possible Causes
{0} does not contain {1} letters.

Copyright © Huawei
Mobile Money

{1}: indicates number of letters that the security credential must contain.
Procedure
4.1635 TP40104
Description
The number of special characters in the security credential is incorrect.
Scenario
Access Channel
Web, USSD, STK, API
Possible Causes
{0} does not contain {1} special characters.

{1}: indicates number of special characters that the security credential must contain.
Procedure
4.1636 TP40105
Description
The number of uppercase letters in the security credential is incorrect.
Scenario
Access Channel
Web, USSD, STK, API

Copyright © Huawei
Mobile Money
Possible Causes
{0} does not contain {1} uppercase letters.

{1}: indicates number of uppercase and lowercase letters that the security credential must contain.
Procedure
4.1637 TP40106
Description
The credential format does not meet the requirement of the credential policy.
Scenario
Access Channel
Web, USSD, STK, API
Possible Causes
{0} is in an incorrect format.
{0}: indicates security credential content.
Procedure
2. Query for security credential policies.
4.1638 TP40107
Description
The security credential is blacklisted.
Scenario

Copyright © Huawei
Mobile Money
Access Channel
Web, USSD, STK, API
Possible Causes
The security credential is blacklisted.
Procedure
4.1639 TP40108
Description
The security credential is in the Pending status and does not support the current operation.
Scenario
Some operations can be performed only when the security credential is not in the pending
status.
Access Channel
Web, USSD, STK, API
Possible Causes
{0} is in the Pending status.
Procedure
4.1640 TP40109
Description
The credential must not contain two consecutive characters that are the same.
Scenario

Copyright © Huawei
Mobile Money
Access Channel
Web, USSD, STK, API
Possible Causes
The credential contains two consecutive characters that are the same.
Procedure
4.1641 TP40110
Description
A credential that has been used before cannot be used again.
Scenario
Access Channel
Web, USSD, STK, API
Possible Causes
A credential that has been used before cannot be used again.
Procedure
4.1642 TP40111
Description
The {0} credential is changed too frequently. Try again later.
Scenario

Copyright © Huawei
Mobile Money
Access Channel
Web, USSD, STK, API
Possible Causes
The {0} credential is changed too frequently.
Procedure
Try again later.
4.1643 TP40112
Description
The credential is the same as the user name or the inverse order of the user name.
Scenario
Access Channel
Web, USSD, STK, API
Possible Causes
The value of {0} must be different from the user name or the inverse order of the user name.
Procedure
4.1644 TP40113
Description
Your {0} will be locked if another {0} attempt fails.
Scenario
The security credential must be verified before the login to the system or the use of function.

Copyright © Huawei
Mobile Money
Access Channel
Web, USSD, STK, API
Possible Causes
The last {0} attempt is allowed.
Procedure
Enter the correct {0}.
4.1645 TP40114
Description
{0} is already in the Unlocked status.
Scenario
The security credential is unlocked.
Access Channel
Web, USSD
Possible Causes
The credential has been unlocked and does not need to be unlocked again.
Procedure
Verify whether the security credential is in the unlocked status.
4.1646 TP40115
Description
{0} is already in the Locked status.
Scenario
The security credential is locked.

Copyright © Huawei
Mobile Money
Access Channel
Web, USSD, STK, API
Possible Causes
The credential has been locked and cannot be locked again.
Procedure
Verify whether the security credential is in the locked status.
4.1647 TP40116
Description
Failed to generate {0}.
Scenario
The Identity is created or the security credential is reconfigured.
Access Channel
Web, USSD, STK
Possible Causes
No valid {0} is generated after 1000 attempts.
Procedure
3. Verify whether the blacklist contains all digits from 0 to 9, and delete unnecessary digits
from the blacklist. Generate a security credential again.
4.1648 TP40117
Description
No security credential is found. Operation failed.

Copyright © Huawei
Mobile Money
Scenario
Verification of security credential is required.
Access Channel
Web, USSD, STK, API
Possible Causes
Procedure
4.1649 TP40118
Description
Scenario
Verification of security credential is required.
Access Channel
Web, USSD, STK, API
Possible Causes
Procedure
4.1650 TP40147
Description
Failed to update the identity's segment.
Scenario
The segment of an identity is modified.

Copyright © Huawei
Mobile Money
Access Channel
Web, USSD
Possible Causes
The current KYC information does not meet the KYC conditions of the selected segment to
be updated for an identity.
Procedure
1. Choose My Functions > Operational Configuration > SP Configuration > Segment.
2. Search for the KYC conditions of the current segment.
3. Return to the identity update page and enter KYC information which meets the KYC
conditions of the segment.
4.1651 TP40148
Description
Failed to save the bank card information.
Scenario
The entered bank card ID exists when an organization or customer is created.
Access Channel
Web, USSD
Possible Causes
The bank account number already exists in the system.
Procedure
Verify whether the bank card information is correct or change the bank card information. If
you indeed need to use the specified bank card information, contact the customer service for
help.
4.1652 TP40149
Description
The MSISDN is mandatory when the KYC notification channel is set to short message service
(SMS).

Copyright © Huawei
Mobile Money
Scenario
Access Channel
Web, USSD
Possible Causes
The MSISDN is empty when the KYC notification channel is set to SMS.
Procedure
Enter a correct MSISDN.
4.1653 TP40150
Description
The email is mandatory when the KYC notification channel is set to EMAIL.
Scenario
Access Channel
Web, USSD
Possible Causes
The email is empty when the KYC notification channel is set to EMAIL.
Procedure
Enter a correct email.
4.1654 TP40151
Description
If the MSISDN or email is not empty, the Channel field is mandatory.
Scenario

Copyright © Huawei
Mobile Money
Access Channel
Web, USSD
Possible Causes
The MSISDN or email is not empty, but the Channel field is empty.
Procedure
Enter a correct channel.
4.1655 TP40119
Description
A system error has occurred in the encryption process.
Scenario
Create an operator or reset the password of an identity.
Access Channel
Web, API, STK, USSD
Possible Causes
 An error occurred when the new password is encrypted.
 An error occurred when the password to be authenticated is encrypted.
Procedure
4.1656 TP40120
Description
Product is not found or the found product is in an incorrect state.
Scenario
When a product is subscribed or a product subscribed to by an identity is modified, no product
is found based on the product ID or the found product is in an incorrect state.
Access Channel
Web, API

Copyright © Huawei
Mobile Money
Possible Causes
No product is found based on the product ID {0} or the found product is in an incorrect state.
Procedure
Select a correct product.
4.1657 TP40121
Description
The identity is not allowed to subscribe to the {0} product.
Scenario
Modify the products subscribed to for an identity.
Access Channel
Web, API
Possible Causes
The identity is not allowed to subscribe to the {0} product.
Procedure
Please choose the correct product.
4.1658 TP40122
Description
Failed to create the internal account.
Scenario
The identity is already associated with an account when an internal account is created.
Access Channel
Web, API

Copyright © Huawei
Mobile Money
Possible Causes
The identity is already associated with the {0} account.
The {0} variable indicates the account name.
Procedure
Change the account type.
4.1659 TP40123
Description
No account type is found based on the account type ID.
Scenario
When account information is queried, no account type is found based on the account type ID.
Access Channel
Web, API
Possible Causes
Procedure
4.1660 TP40124
Description
The language is not configured in the system.
Scenario
When an identity is created or when the language of an identity is changed, no language is
obtained based on the code.
Access Channel
Web, API, USSD, STK

Copyright © Huawei
Mobile Money
Possible Causes
The system does not support the language.
Procedure
Change the language.
4.1661 TP40125
Description
The short code is in an incorrect format.
Scenario
When an organization is created or when an organization attribute is modified, the short code
format is incorrect.
Access Channel
Web, API
Possible Causes
Short code {0} is in an incorrect format.
The {0} variable indicates the short code.
Procedure
Enter a short code in the correct format.
4.1662 TP40126
Description
Failed to change the status of the identity.
Scenario
When the status of an identity is modified, the identity has a voucher waiting to be redeemed.
Access Channel
Web, API, STK, USSD

Copyright © Huawei
Mobile Money
Possible Causes
There is a voucher that is not exchanged.
Procedure
1. Choose Search > Organization to query for the organization.
2. On the details page, choose Organization Transaction > Initiate Transaction.
3. Exchange the voucher as necessary.
4.1663 TP40127
Description
The account type does not apply to the identity type.
Scenario
When a product or account of an identity is modified, the account type does not apply to the
identity type.
Access Channel
Web, API
Possible Causes
The account type does not apply to the identity type.
Procedure
Change the account type or the identity types to which the account type applies.
4.1664 TP40128
Description
Failed to subscribe to the products.
Scenario
When products subscribed to an identity are modified, the products contain duplicate services.
Access Channel
Web, API

Copyright © Huawei
Mobile Money
Possible Causes
Products {0} and {1} to be subscribed to contain duplicate services.
{0}: indicates the first product that contains a duplicate service.

{1}: indicates the second product that contains a duplicate service.
Procedure
Change the products to be subscribed to and verify that they do not contain duplicate services.
4.1665 TP40129
Description
Failed to query for the till.
Scenario
All operations performed on a till
Access Channel
Web, API, USSD
Possible Causes
No till is found based on the specified device number or till number.
Procedure
1. Verify whether the device number is correct.
2. Verify whether the till number is correct.
4.1666 TP40130
Description
Failed to obtain the process ID.
Scenario
All operations that need to invoke functions of the BCS.
Access Channel
Web, API, USSD, STK

Copyright © Huawei
Mobile Money
Possible Causes
No process ID is found based on action type {0}.
{0}: indicates an action type.
Procedure
4.1667 TP40131
Description
Failed to create the customer.
Scenario
The value of Customer Type specified for the customer to be created is incorrect.
Access Channel
Web, API, USSD, STK
Possible Causes
Customer type {0} is incorrect.
{0}: indicates a customer type.
Procedure
Enter a correct value for customer type.
4.1668 TP40132
Description
Failed to upgrade the customer.
Scenario
Upgrade or update attributes of a customer.
Access Channel
Web, API, USSD, STK

Copyright © Huawei
Mobile Money
Possible Causes
The customer type is not unregistered.
Procedure
Verify whether the customer is upgraded.
4.1669 TP40133
Description
Failed to obtain the trust level.
Scenario
When the KYC information of an identity is modified, no trust level is obtained based on the
KYC information.
Access Channel
Web, API, USSD
Possible Causes
No trust level is obtained based on the identity KYC information.
Procedure
Level.
2. Verify the minimum KYC information required for the lowest trust level of the Identity
Type and subtype.
3. Return to the previous page and enter KYC information required for the lowest trust
level.
4.1670 TP40134
Description
No default charge profile is configured for the current Trust Level. Failed to create or modify
the identity.
Scenario
When the KYC information of an identity is modified, no default charge profile is configured
for the current trust level.

Copyright © Huawei
Mobile Money
Access Channel
Web, API, USSD, STK
Possible Causes
The default charge profile of the current {0} trust level is empty.
{0}: indicates the current trust level.
Procedure
Charge Profile.
2. Assign a default charge profile for the {0} trust level.
4.1671 TP40135
Description
Scenario
When products subscribed to by an identity are modified, the expiration time specified for a
product exceeds the validity period of the product.
Access Channel
Web, API
Possible Causes
The expiration time of the {0} product to be subscribed to exceeds the product validity period.
Procedure
Change the product or its validity period.
4.1672 TP40136
Description

Copyright © Huawei
Mobile Money
Scenario
When products subscribed to by an identity are modified, the effective time of a product to be
subscribed to is later than the expiration time of the product.
Access Channel
Web, API
Possible Causes
The effective time of the {0} product to be subscribed to is later than its expiration time.
Procedure
Change the product effective time to a time earlier than the expiration time or replace the
product.
4.1673 TP40137
Description
Scenario
When products subscribed to by an identity are modified, the expiration time of a product to
be subscribed to is earlier than the current time.
Access Channel
Web, API
Possible Causes
The expiration time of the {0} product to be subscribed to is earlier than the current time.
Procedure
Change the product expiration time to a time later than the current time or replace the product.

Copyright © Huawei
Mobile Money
4.1674 TP40138
Description
The product subscribed to by the identity does not contain the account required for the
transaction. Failed to create the account, the account type name is {0}.
{0} indicates account type name.
Scenario
An identity account is created.
Access Channel
Web, API, STK, USSD
Possible Causes
The product subscribed to by the identity does not contain the account required for the
transaction.
Procedure
Contact the operator to check product account configurations and ensure that the accounts
required for the transaction are configured.
4.1675 TP40139
Description
The rule profile of the {0} account is not the rule profile assigned to the trust level.
Scenario
The rule profile of an account is not the rule profile assigned to the trust level when the rule
profile of an account is modified.
Access Channel
Web, API
Possible Causes
The rule profile of the {0} account is not the rule profile assigned to the trust level.

Copyright © Huawei
Mobile Money
Procedure
4.1676 TP40140
Description
Failed to create or update the identity.
Scenario
When an identity is created or updated, the identity does not support the specified channel.
Access Channel
Web, API
Possible Causes
The identity does not support the {0} channel.
{0}: indicates the name of a channel.
Procedure
Change the specified channel or channels supported by the identity.
4.1677 TP40141
Description
Failed to create the till. The specified till number is already used by a till.
Scenario
When a till is created, the specified till number is already used by a till.
Access Channel
Web, API
Possible Causes
The specified till number is already used by a till.

Copyright © Huawei
Mobile Money
Procedure
4.1678 TP40142
Description
Failed to create the till. The specified till number is already used by a bank.
Scenario
When a till is created, the specified till number is already used by a bank.
Access Channel
Web, API
Possible Causes
The specified till number is already used by a bank.
Procedure
4.1679 TP40143
Description
Failed to create the till. The specified till number is already used by an organization.
Scenario
When a till is created, the specified till number is already used by an organization.
Access Channel
Web, API
Possible Causes
The specified till number is already used by an organization.
Procedure

Copyright © Huawei
Mobile Money
4.1680 TP40144
Description
Failed to create the identity. The specified short code is already used by a till.
Scenario
When an organization is created, the specified short code is already used by a till.
Access Channel
Web, API
Possible Causes
The specified short code is already used by a till.
Procedure
Change the short code.
4.1681 TP40145
Description
Failed to create the identity. The specified short code is already used by a bank.
Scenario
When an organization is created, the specified short code is already used by a bank.
Access Channel
Web, API
Possible Causes
The specified short code is already used by a bank.
Procedure

Copyright © Huawei
Mobile Money
4.1682 TP40146
Description
Failed to create the identity. The specified short code is already used by an organization.
Scenario
When an organization is created, the specified short code is already used by another
organization.
Access Channel
Web, API
Possible Causes
The specified short code is already used by an organization.
Procedure
4.1683 TP40152
Description
Failed to add an account to the account type.
Scenario
When the account of an identity is modified, an account is defined for the account type.
Access Channel
Web, API
Possible Causes
An account has already been defined for the account type.
Procedure
Verify whether an account has already been configured for the account type.

Copyright © Huawei
Mobile Money
4.1684 TP40153
Description
The operator has no permission to perform this operation or does not belong to the specified
organization.
Scenario
All BO actions that require permission authentication.
Access Channel
Web
Possible Causes
Operator {0} is not allowed to use the {1} service.
{0}: indicates the name of an operator.

{1}: indicates an action to be performed.
Procedure
Verify the permission of the operator.
4.1685 TP40154
Description
Failed to create the password.
Scenario
When an SP operator is created or when a password is modified, the two passwords entered
are not the same.
Access Channel
Web
Possible Causes
The two passwords are different.
Procedure
Enter the same passwords.

Copyright © Huawei
Mobile Money
4.1686 TP40155
Description
Failed to assign a role to the identity.
Scenario
When the role of an identity is modified, the new role cannot be assigned to the identity.
Access Channel
Web
Possible Causes
The {0} role does not match with the current identity.
{0}: indicates the name of a role.
Procedure
Change the role.
4.1687 TP40156
Description
The operator has no permission to assign the {0} role to other operators. Failed to assign a
role to the identity.
{0}: indicates the name of a role.
Scenario
When modifying the role of an operator, the current operator is not allowed to assign the new
role to other operators.
Access Channel
Web
Possible Causes
The operator has no permission to assign the {0} role to other operators.

Copyright © Huawei
Mobile Money
Procedure
Change the role.
4.1688 TP40157
Description
Failed to create the operator. The user name does not meet the authentication rules.
Scenario
When an operator is created, the operator name does not meet the verification rules.
Access Channel
Web, USSD
Possible Causes
The operator name does not meet the authentication rules.
Procedure
Enter an operator name that meets the authentication rules.
4.1689 TP40159
Description
Failed to create the operator because the operator ID does not meet the authentication rules.
Scenario
When an operator is created, the operator ID does not meet the verification rules.
Access Channel
Web, USSD, STK, API
Possible Causes
The operator ID does not meet the authentication rules.
Procedure
Enter an operator ID that meets the authentication rules.

Copyright © Huawei
Mobile Money
4.1690 TP40162
Description
Failed to create the organization operator.
Scenario
When an operator is created, the operator type is incorrect.
Access Channel
Web, USSD
Possible Causes
The operator type is incorrect.
Procedure
Change the operator type.
4.1691 TP40163
Description
Scenario
When an operator is created, no rule profile is found based on the rule profile ID.
Access Channel
Web, USSD, STK
Possible Causes
Rule profile {0} does not exist.
Procedure

Copyright © Huawei
Mobile Money
4.1692 TP40164
Description
Failed to create the operator because the rule profile ID does not belong to the organization
operator.
Scenario
When an operator is created, the rule profile does not belong to the organization operator.
Access Channel
Web, USSD, STK
Possible Causes
Rule profile {0} does not belong to an organization operator.
Procedure
4.1693 TP40165
Description
Failed to add the channel.
Scenario
When a channel is added for an operator, the specified channel ID is incorrect.
Access Channel
Web, USSD, STK
Possible Causes
The channel value {0} is incorrect.
{0}: indicates the name of a channel.
Procedure
Enter a correct channel value.

Copyright © Huawei
Mobile Money
4.1694 TP40166
Description
Failed to add the web channel.
Scenario
If the channel of an identity is changed to web, the User Name field is mandatory.
Access Channel
Web, USSD
Possible Causes
If the identity channel is set to Web, the User Name field is mandatory.
Procedure
Enter a correct user name.
4.1695 TP40167
Description
Failed to change the operator role.
Scenario
There must be at least two system administrators. Currently, there are only two system
administrators, and either of them cannot be closed.
Access Channel
Web
Possible Causes
If there are only two administrators in the system, you cannot change the role of one
administrator to a common operator.
Procedure
Enter a correct operator role.

Copyright © Huawei
Mobile Money
4.1696 TP40168
Description
Failed to change the operator role. The operator's KYC information does not match with the
role.
Scenario
When the role of an operator is changed, the operator's KYC information does not match with
the new role.
Access Channel
Web
Possible Causes
The operator's KYC information does not match with the {0} role.
{0}: indicates a role ID.
Procedure
Query for the KYC information required for the {0} role and match the information with the
operator's KYC.
4.1697 TP40169
Description
No operator question is found for the {0} operator. Failed to reset the password.
{0}: indicates an operator ID.
Scenario
An operator retrieves the password.
Access Channel
Web, USSD, STK
Possible Causes
No operator question is found for the {0} operator.

Copyright © Huawei
Mobile Money
Procedure
4.1698 TP40170
Description
Failed to query for the Admin Type.
Scenario
When an operator queries the Admin Type, the value of Admin Type is invalid.
Access Channel
Web, USSD, STK
Possible Causes
The value of Admin Type is invalid.
Procedure
Enter a correct value for Admin Type.
4.1699 TP40171
Description
Login failed.
Scenario
When an operator logs in, the user name does not exist or the password is incorrect.
Access Channel
Web
Possible Causes
Procedure
Enter a correct user name and password.

Copyright © Huawei
Mobile Money
4.1700 TP40172
Description
Login failed.
Scenario
When an operator logs in, the account has already been closed.
Access Channel
Web
Possible Causes
The account number has been inactive for a long time and closed.
Procedure
4.1701 TP40173
Description
Incorrect answer. {0} chances left.
{0}: indicates the number of remaining opportunities for answering a security question.
Scenario
When an operator retrieves the password by answering security questions, the answer is
incorrect, and the operator has {0} more opportunities.
Access Channel
Web
Possible Causes
Incorrect answer. {0} chances left.
Procedure
Enter the correct password.

Copyright © Huawei
Mobile Money
4.1702 TP40174
Description
Failed to reset the password.
Scenario
When an operator retrieves the password by answering security questions, no question and
answer policy is found.
Access Channel
Web
Possible Causes
No answer policy is found.
Procedure
4.1703 TP40175
Description
The number of incorrect answers has reached the upper limit, and the security question is
locked. Failed to reset the password.
Scenario
When an operator retrieves the password by answering security questions, a security question
is locked because the number of incorrect answers has reached the upper limit.
Access Channel
Web
Possible Causes
The number of incorrect answers has reached the upper limit, and the security question is
locked.
Procedure

Copyright © Huawei
Mobile Money
4.1704 TP40176
Description
Failed to configure the organization hierarchy.
Scenario
When organization levels are configured, the number of levels exceeds the upper limit.
Access Channel
Web
Possible Causes
The specified organization hierarchy exceeds the upper limit.
Procedure
Enter a correct organization hierarchy.
4.1705 TP40177
Description
Scenario
When a top organization is created, the accounting model of the top organization is
mandatory.
Access Channel
Web
Possible Causes
The Accounting Model is mandatory for the top organization.
Procedure
Enter a correct accounting model.

Copyright © Huawei
Mobile Money
4.1706 TP40178
Description
Scenario
When a top organization is created, the accounting model of the top organization does not
exist.
Access Channel
Web
Possible Causes
No accounting model is configured for the top organization.
Procedure
Enter a correct accounting model.
4.1707 TP40179
Description
Scenario
When a child organization is created or when relationships between child organizations are
modified, the child organization relationship type is mandatory.
Access Channel
Web
Possible Causes
The relationship type is mandatory for the child organization.
Procedure
Enter a relationship type for the child organization.

Copyright © Huawei
Mobile Money
4.1708 TP40180
Description
Tax {0} does not exist.
{0}: indicates a tax code.
Scenario
When a tax code is queried by tax code ID, no tax code is found.
Access Channel
Web
Possible Causes
Tax {0} does not exist.
Procedure
4.1709 TP40181
Description
The input region is incorrect.
Scenario
When the region of an identity is modified, no region is found based on the region ID.
Access Channel
Web
Possible Causes
The region does not exist.
Procedure
Please input the correct region.

Copyright © Huawei
Mobile Money
4.1710 TP40182
Description
The charge distribution model does not exist.
Scenario
When a child organization is created or when the profit sharing model is modified, no profit
sharing is found based on the profit sharing ID.
Access Channel
Web
Possible Causes
The charge distribution model does not exist.
Procedure
4.1711 TP40184
Description
The associated customer {0} does not exist. Failed to modify the organization's O2C link.
{0}: indicates a mobile phone number.
Scenario
When O2C links are created or modified, the associated customer does not exist.
Access Channel
Web, USSD
Possible Causes
The associated customer {0} does not exist.
Procedure
Verify whether the associated customer exists.

Copyright © Huawei
Mobile Money
4.1712 TP40185
Description
The associated old O2C {0} does not exist. Failed to modify the organization's O2C link.
Scenario
When O2C links are created or modified, the associated old O2C link does not exist.
Access Channel
Web, USSD
Possible Causes
The associated old O2C {0} does not exist.
Procedure
Verify whether the associated old O2C link exists.
4.1713 TP40186
Description
The associated O2C {0} already exist. Failed to modify the organization's O2C link.
Scenario
When O2C links are created or modified, the associated target O2C link does not exist.
Access Channel
Web, USSD
Possible Causes
The associated O2C {0} already exist.
Procedure
Verify whether the associated new O2C link exists.

Copyright © Huawei
Mobile Money
4.1714 TP40187
Description
If the verification mode is 1/3, the verification expression cannot be empty.
Scenario
Modify the rules for verifying organization PayBill transactions.
Access Channel
Web, USSD, STK
Possible Causes
If the verification mode is 1/3, the verification expression cannot be empty.
Procedure
Verify the verification expression.
4.1715 TP40188
Description
Failed to create the till.
Scenario
When a till is created, the value of till type is incorrect.
Access Channel
Web
Possible Causes
The value of till type {0} is incorrect.
{0}: indicates the type of a till.
Procedure
Verify the till type.

Copyright © Huawei
Mobile Money
4.1716 TP40189
Description
The organization has not subscribed to the {0} product. Failed to modify or create the
organization's till.
Scenario
When a product subscribed to for an organization till is modified, the organization has not
subscribed to the product.
Access Channel
Web
Possible Causes
The organization has not subscribed to the {0} product.
Procedure
Verify the products subscribed to by the organization.
4.1717 TP40190
Description
The {0} organization product has been suspended. Failed to modify or create the
Scenario
When a product subscribed to for an organization till is modified, the product has been
suspended.
Access Channel
Web
Possible Causes
The {0} organization product has been suspended.

Copyright © Huawei
Mobile Money
Procedure
4.1718 TP40191
Description
The {0} organization product has not taken effect. Failed to modify or create the
Scenario
When a product subscribed to for an organization till is modified, the product has not taken
effect.
Access Channel
Web
Possible Causes
The {0} organization product has not taken effect.
Procedure
4.1719 TP40192
Description
Failed to create the transaction approval task.
Scenario
All BCS transactions that require workflow approval
Access Channel
Web, USSD, API, STK
Possible Causes
Failed to call back the BCS.

Copyright © Huawei
Mobile Money
Procedure
4.1720 TP40193
Description
Failed to modify the identity status.
Scenario
A parameter is invalid when the status of an identity is modified.
Access Channel
Web
Possible Causes
A parameter value is invalid.
Procedure
Verify the parameter values.
4.1721 TP40194
Description
Account Type {0} does not apply to identity {1}.
{0}: indicates an account type.
Scenario
When an account is added for an identity, the account type does not apply to the identity.
Access Channel
Web
Possible Causes
Account Type {0} does not apply to identity {1}.

Copyright © Huawei
Mobile Money
Procedure
Select a correct account type.
4.1722 TP40199
Description
Enter a correct PIN during the transaction process.
Scenario
The exception may occur in many transaction scenarios, for example, when the PIN of a
transaction initiator fails to be authenticated.
Access Channel
STK, USSD, API, Web
Possible Causes
The PIN entered by the identity fails to be authenticated.
Procedure
Enter a correct PIN and initiate the transaction again.
4.1723 TP40200
Description
The {0} parameter in the revenue settlement approval request is incorrect or empty.
Scenario
A parameter in the revenue settlement approval request is incorrect or empty.
Access Channel
System
Possible Causes
A parameter in the revenue settlement approval request is incorrect or empty.

Copyright © Huawei
Mobile Money
Procedure
4.1724 TP40201
Description
The {0} parameter in the revenue settlement request is incorrect or empty.
Scenario
A parameter in the revenue settlement request is incorrect or empty.
Access Channel
System
Possible Causes
A parameter in the revenue settlement request is incorrect or empty.
Procedure
4.1725 TP40202
Description
Failed to initiate the revenue settlement workflow.
Scenario
Access Channel
System
Possible Causes

Copyright © Huawei
Mobile Money
Procedure
4.1726 TP40203
Description
Both parties of the transaction are the same identity.
Scenario
Parties of a transaction cannot be the same identity based on the transaction type
configuration.
Access Channel
STK, USSD, API, Web
Possible Causes
Information about the parties of the transaction is incorrect.
Procedure
Verify that parties of the transaction are not the same identity.
4.1727 TP40204
Description
Child organization {0} does not belong to top organization {1}.
{0}: indicates the short code of child organization.

{1}: indicates the short code of top organization.
Scenario
This exception occurs during commission roll-up, the child organization does not belong to
top organization.
Access Channel
Web, System
Possible Causes
Child organization {0} does not belong to top organization {1}.

Copyright © Huawei
Mobile Money
Procedure
Enter a child organization that belongs to the top organization.
4.1728 TP40205
Description
Failed to reverse the commission transaction. The value of {0} is {1} after reversal.

{1}: indicates the parameter value.
Scenario
This exception occurs during commission transaction reversal.
Access Channel
Web, System
Possible Causes
Failed to reverse the commission transaction. The value of {0} is {1} after reversal.
Procedure
4.1729 TP40206
Description
The commission task does not exist. CommTaskId is {0}.
{0}: indicates the ID of a commission.
Scenario
The commission approval task does not exist.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The commission task does not exist. CommTaskId is {0}.
Procedure
Enter a correct CommTaskId.
4.1730 TP40207
Description
The commission payment record does not exist. CommTaskId is {0}.
{0}: indicates the ID of a commission.
Scenario
When a commission task is being approved, the commission payment data does not exist.
Access Channel
Web
Possible Causes
The commission payment record does not exist. CommTaskId is {0}.
Procedure
4.1731 TP40208
Description
The status of the BPM task associated with the {0} task is incorrect, and the current operation
is not allowed.
{0}: indicates the ID of a task.
Scenario
When a workflow task is processed, the status of the BPM task associated with the current
task is incorrect.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The status of the BPM task associated with the {0} task is incorrect.
Procedure
Set {0} to a correct value and verify that the associated BMP task is in a valid state.
4.1732 TP40209
Description
No BPM task is associated with the {0} task.
Scenario
When a workflow task is processed, the BPM task associated with the current task does not
exist.
Access Channel
Web
Possible Causes
Incorrect parameter.
Procedure
Set the {0} parameter to a correct value.
4.1733 TP40210
Description
The current operator has no permission to execute the {0} task. Assign the permission to the
operator.

Copyright © Huawei
Mobile Money
Scenario
When a workflow task is processed, the current operator has no permission to process this
task.
Access Channel
Web
Possible Causes
The current operator has no permission to execute the {0} task.
Procedure
Assign the permission to the operator.
4.1734 TP40211
Description
The {0} task has been suspended and does not support the current operation.
Scenario
When a workflow task is processed, the task obtained based on the {0} parameter has been
suspended.
Access Channel
Web
Possible Causes
Procedure
Set {0} to a correct value and verify that the current task is not suspended.
4.1735 TP40212
Description
The new PIN is mandatory when an organization operator in the Pending Active state is
activated.

Copyright © Huawei
Mobile Money
Scenario
The new PIN is empty when the organization operator is activated.
Access Channel
Web, USSD, API, STK
Possible Causes
The new PIN is empty.
Procedure
Enter the new PIN.
4.1736 TP40213
Description
The API Initiator Key to be added already exists.
Scenario
When a new API initiator key is added, the API initiator key already exists.
Access Channel
Web
Possible Causes
The API Initiator Key already exists.
Procedure
Verify that the API Initiator Key to be added does not exist.
4.1737 TP40214
Description
The operation type entered for managing an API initiator key does not exist.
Scenario
When an API initiator key is modified, the specified operation type does not exist.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The operation type does not exist.
Procedure
Enter a correct operation type.
4.1738 TP40215
Description
The API initiator key to be added or modified must not be empty.
Scenario
When an API initiator key is added or modified, the API initiator key is empty.
Access Channel
Web
Possible Causes
The API Initiator Key is empty.
Procedure
Enter a correct API initiator key.
4.1739 TP40216
Description
The STK key to be managed must not be empty.
Scenario
When an STK key is managed, the STK key is empty.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The STK key is empty.
Procedure
Enter a correct STK key.
4.1740 TP40217
Description
{0} product subscription failed.
Scenario
When the product subscribed to by an identity is modified, the current time is not in the
validity period of the product.
Access Channel
Web, USSD, API, STK
Possible Causes
The current time is not in the validity period of the product {0}.
Procedure
Modify the validity period of the product or replace the product.
4.1741 TP40218
Description
Failed to change the operator certificate.
Scenario
When the certificate of an operator is modified, the target certificate already exists.
Access Channel
Web, USSD

Copyright © Huawei
Mobile Money
Possible Causes
The {0} certificate already exists.
{0}: indicates the certificate identifier.
Procedure
Replace the new certificate.
4.1742 TP40219
Description
Failed to change the operator certificate.
Scenario
When an operator is modified, the status of the specified certificate is incorrect.
Access Channel
Web, USSD
Possible Causes
The {0} certificate status is incorrect.
{0}: indicates the certificate status.
Procedure
Enter a correct certificate status.
4.1743 TP40220
Description
Operator login failed.
Scenario
Activate an operator.
Access Channel
Web, USSD, STK

Copyright © Huawei
Mobile Money
Possible Causes
The operator is not logging for the first time.
Procedure
4.1744 TP40222
Description
The new and old PINs are the same.
Scenario
The new and old PINs are the same during a changing PIN operation.
Access Channel
Web, STK, USSD, API
Possible Causes
The new and old PINs are the same.
Procedure
Verify that the new PIN is different from the old PIN.
4.1745 TP40223
Description
No permission data is configured for the workflow to provide the current service.
Scenario
When an operation that requires workflow approval is performed, no permission is configured
for the process.
Access Channel
Web, USSD, API
Possible Causes
Incorrect configuration.

Copyright © Huawei
Mobile Money
Procedure
Configure permission data for the workflow.
4.1746 TP40224
Description
Failed to change the security credential.
Scenario
When a security certificate is modified, the old and new security certificates are the same.
Access Channel
Web, USSD
Possible Causes
The new and old security credentials are the same.
Procedure
Verify that the new password is different from the old one.
4.1747 TP40225
Description
Product subscription failed.
Scenario
When the product subscribed to by an identity is modified, the effective time specified for the
product to be subscribed to is earlier than the product effective time.
Access Channel
Web, USSD
Possible Causes
The product subscription effective time cannot be earlier than the product effective time.
Procedure
Modify the subscription effective time.

Copyright © Huawei
Mobile Money
4.1748 TP40228
Description
Failed to change certificate.
Scenario
When a certificate is modified, the cert status is specified, but no certificate serial number is
specified.
Access Channel
Web, USSD
Possible Causes
If cert status is configured, the certificate serial number is mandatory.
Procedure
Enter a correct certificate serial number.
4.1749 TP40229
Description
The rule profile does not exist, or does not belong to the current identity.
Scenario
The rule profile is incorrect when modifying rule profile.
Access Channel
Web, USSD, STK
Possible Causes
The rule profile does not exist, or does not belong to the current identity.
Procedure
Enter a correct rule profile.

Copyright © Huawei
Mobile Money
4.1750 TP40230
Description
Account Number does not meet the naming rules.
Scenario
Account Number does not meet the naming rules when creating Bank Account.
Access Channel
Web, USSD
Possible Causes
Account Number does not meet the naming rules.
Procedure
Enter a correct account number.
4.1751 TP40231
Description
Account Name does not meet the naming rules.
Scenario
Account Name does not meet the naming rules when creating Bank Account.
Access Channel
Web, USSD
Possible Causes
Account Name does not meet the naming rules.
Procedure

Copyright © Huawei
Mobile Money
4.1752 TP40232
Description
The {0} account is not in the Active status, and cannot be set as the default control account.
The {0} variable indicates an account ID.
Scenario
The account status is not Active when the default control account of the bank is changed.
Access Channel
Web
Possible Causes
The {0} account is not in the Active status, and cannot be set as the default control account.
Procedure
Select a correct account.
4.1753 TP40233
Description
The verification session must not be empty.
Scenario
No verification session is found when the Session interface is created for the Take a Call
menu.
Access Channel
Web
Possible Causes
No verification session is found.
Procedure
Verify the specified session ID.

Copyright © Huawei
Mobile Money
4.1754 TP40234
Description
The verification policy must not be empty.
Scenario
No verification policy is found when the Session interface is created for the Take a Call menu.
Access Channel
Web
Possible Causes
No verification policy is found based on the identity type and subtype.
Procedure
Query the cps_verify_policy table based on identity type {0} and sub type {1}. If no record is
found, add preconfigured data in the table.
{0} indicates an identity type, {1} indicates a subtype.
4.1755 TP40235
Description
Failed to obtain the value of a verification policy attribute.
Scenario
Values of certain verification policy attributes cannot be obtained when the Session interface
is created for the Take a Call menu.
Access Channel
Web
Possible Causes
Failed to obtain the value of the {2} verification policy attribute.
Procedure
Query the cps_verify_policy table for the {2} attribute based on identity type {0} and sub
type {1}. If no record is found, add preconfigured data in the table.

Copyright © Huawei
Mobile Money
{0} indicates an identity type, {1} indicates a subtype, and {2} indicates a required score.
4.1756 TP40236
Description
The receiving information does not match the identity information found based on the flag ID.
Scenario
The receiving information does not match the identity information found based on the flag ID
when a Take a Call interface is verified.
Access Channel
Web
Possible Causes
The receiving information does not match the identity information found based on the flag ID.
Procedure
Verify the identity information.
4.1757 TP40237
Description
The receiving information does not match the identity information found based on the session
ID.
Scenario
ID when a Take a Call interface is verified.
Access Channel
Web
Possible Causes
ID.

Copyright © Huawei
Mobile Money
Procedure
Verify the identity information.
4.1758 TP40238
Description
Entries to be verified are empty.
Scenario
No verification entry is found when a Take a Call interface is verified.
Access Channel
Web
Possible Causes
No verification entry is found.
Procedure
Verify the verification information.
4.1759 TP40239
Description
More than one verification entry needs to be verified at a time.
Scenario
More than one verification entry needs to be verified when a Take a Call interface is verified.
Access Channel
Web
Possible Causes
More than one verification entry needs to be verified at a time.
Procedure
Verify the verification information.

Copyright © Huawei
Mobile Money
4.1760 TP40240
Description
The key of the verification entry does not exist.
Scenario
The key of a verification entry does not exist when a Take a Call interface is verified.
Access Channel
Web
Possible Causes
The value of the item name {0} parameter is incorrect.
{0}: indicates an item name.
Procedure
Verify data in the cps_verify_item table and set itemname to a correct value.
4.1761 TP40241
Description
A verification entry is unavailable.
Scenario
A verification entry is unavailable when a Take a Call interface is verified.
Access Channel
Web
Possible Causes
The {0} verification entry is unavailable.
{0}: indicates an entry needs to be verified.
Procedure
Verify data in the cps_verify_item table.

Copyright © Huawei
Mobile Money
4.1762 TP40242
Description
The registration time formatting parameter is incorrect.
Scenario
The registration time formatting parameter is incorrect when a Take a Call interface is
verified.
Access Channel
Web
Possible Causes
The {0} registration time formatting parameter is incorrect.
{0}: indicates registration time formatting parameter.
Procedure
Verify the {0} registration time formatting parameter.
4.1763 TP40243
Description
No verifier is found for the item name.
Scenario
No verifier is found for an item name when a Take a Call interface is verified.
Access Channel
Web
Possible Causes
The value of item name {0} is incorrect.
{0}: indicates an item name.
Procedure
Verify whether the item name is valid.

Copyright © Huawei
Mobile Money
4.1764 TP40244
Description
The value of the verification result parameter is invalid.
Scenario
The value of a verification result parameter value is invalid when a Take a Call interface is
verified.
Access Channel
Web
Possible Causes
The value of the {0} verification result parameter is invalid. The value can only be 1 or 0.
{0}: indicates verification result parameter name.
Procedure
The value of the verification result parameter must be 1 or 0.
4.1765 TP40245
Description
The value of the verification mode parameter is invalid.
Scenario
The value of a verification mode parameter value is invalid when a Take a Call interface is
verified.
Access Channel
Web
Possible Causes
The value of the {0} verification mode parameter is invalid. The value can only be 1 or 2.
{0}: indicates verification mode.

Copyright © Huawei
Mobile Money
Procedure
The value of the verification mode parameter must be 1 or 2.
4.1766 TP40246
Description
The verification mode does not match the manual mode configuration item.
Scenario
The verification mode does not match the manual mode in the configuration item when a Take
a Call interface is verified.
Access Channel
Web
Possible Causes
The verification mode is 1, and does not support the manual verification mode.
Procedure
Set the verification mode to 2.
4.1767 TP40247
Description
No verification object is found.
Scenario
The verification object cannot be parsed when a Take a Call interface is verified.
Access Channel
Web
Possible Causes
The verification object cannot be parsed.
Procedure
Verify whether the item name is correct.

Copyright © Huawei
Mobile Money
4.1768 TP40248
Description
The transaction amount is invalid.
Scenario
The specified transaction amount is invalid when a Take a Call interface is verified.
Access Channel
Web
Possible Causes
The {0} transaction amount is invalid.
{0}: indicates the specified transaction amount.
Procedure
Check the transaction amount.
4.1769 TP40249
Description
The account type is invalid.
Scenario
The specified account type is invalid when a Take a Call interface is verified.
Access Channel
Web
Possible Causes
The {0} account type is invalid.
{0}: indicates the specified account type.
Procedure
Verify the account type.

Copyright © Huawei
Mobile Money
4.1770 TP40250
Description
The identifier type is invalid.
Scenario
The specified identifier type is invalid when a Take a Call interface is verified.
Access Channel
Web
Possible Causes
The identifier type is invalid.
Procedure
Verify the identifier type.
4.1771 TP40251
Description
The identity does not need to be unlocked.
Scenario
The identity is not suspended in Take a Call and does not need to be unlocked.
Access Channel
Web
Possible Causes
The identity is not suspended in Take a Call.
Procedure
The identity does not need to be unlocked.

Copyright © Huawei
Mobile Money
4.1772 TP40252
Description
The task cannot be assigned to the task creator.
Scenario
The creator of a manual task attempts to assign the task to the self.
Access Channel
Web
Possible Causes
The creator of a manual task cannot assign the task to the self.
Procedure
Assign the task to another operator.
4.1773 TP40253
Description
The value IsContactTask parameter is invalid.
Scenario
The value of the IsContactTask parameter is invalid when a manual task is created.
Access Channel
Web
Possible Causes
The IsContactTask parameter can be set only to 0 or 1.
Procedure
Verify that the IsContactTask parameter is set only to 0 or 1. Please set the valid value.

Copyright © Huawei
Mobile Money
4.1774 TP40254
Description
The {1} effective date of the {0} operator role must not be earlier than the current date {2}.
{0}: indicates an operator role.

{1}: indicates the effective date of the operator role.
{2}: indicates the current date.
Scenario
The specified effective date is invalid when the role of an operator is changed.
Access Channel
Web
Possible Causes
The {1} effective date of the {0} operator role is earlier than the current date {2}.
Procedure
Verify that the effective date of the operator role is not earlier than the current date.
4.1775 TP40255
Description
The {1} expiration date of the {0} operator role must not be earlier than the {2} effective
date.

{1}: indicate the expiration date.
{2}: indicates the effective date.
Scenario
The effective date is later than the expiration date when the role of an operator is changed.
Access Channel
Web
Possible Causes
The {1} expiration date of the {0} operator role is earlier than the {2} effective date.

Copyright © Huawei
Mobile Money
Procedure
Verify that the expiration date of the operator role is not earlier than the effective date.
4.1776 TP40256
Description
The {1} expiration date of the {0} operator role must not be earlier than the current date {2}.

{1}: indicate the expiration date.
{2}: indicates the current date.
Scenario
The specified expiration date is invalid when the role of an operator is changed.
Access Channel
Web
Possible Causes
The {1} expiration date of the {0} operator role is earlier than the current date {2}.
Procedure
Verify that the expiration date of the operator role is not earlier than the current date.
4.1777 TP40261
Description
The commission roll-down record does not exist.
Scenario
The commission roll-down record to be approved does not exist.
Access Channel
Web
Possible Causes
The commission roll-down record whose CommTaskId is {0} does not exist.

Copyright © Huawei
Mobile Money
{0}: indicates commission task ID.
Procedure
4.1778 TP40262
Description
The commission claw-back record does not exist.
Scenario
The commission claw-back record to be approved does not exist.
Access Channel
Web
Possible Causes
The commission claw-back record whose ClawBackId is {0} does not exist.
{0}: indicates commission claw-back ID.
Procedure
Enter a correct ClawBackId.
4.1779 TP40263
Description
The commission amount to be clawed back must be greater than 0.
Scenario
The commission amount to be clawed back is less than or equal to 0.
Access Channel
Web
Possible Causes
The commission amount to be clawed back is less than or equal to 0.

Copyright © Huawei
Mobile Money
Procedure
The commission amount to be clawed back must be greater than 0.
4.1780 TP40267
Description
Failed to change the account status. The account status cannot be changed from {0} to {1}.
Scenario
The status of the identity account cannot be changed from the old status to the new status.
Access Channel
Web
Possible Causes
The account status cannot be changed from {0} to {1}.
{0}, {1}: indicate the status of the identity account.
Procedure
Verify that the old account status can be changed to the new status. For example, Active can
be changed to Suspended, Frozen, or Closed; Suspended can be changed to Active, Frozen,
or Closed; Frozen can be changed to Active or Closed; and Dormant can be changed to
Active or Closed.
4.1781 TP40268
Description
Failed to change the account rule profile.
Scenario
The target rule profile of the identity account does not exist during the rule profile changing
process.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The rule profile does not exist.
Procedure
Enter a valid rule profile.
4.1782 TP40269
Description
Failed to change the account status.
Scenario
The status entered is incorrect when the status of an identity account is changed.
Access Channel
Web
Possible Causes
The specified account status does not exist.
Procedure
Enter a valid state.
4.1783 TP40270
Description
Failed to change the identity account.
Scenario
The account entered does not exist when the rule profile or status of an identity account is
changed.
Access Channel
Web
Possible Causes
The specified account does not exist.

Copyright © Huawei
Mobile Money
Procedure
Enter a valid account number.
4.1784 TP40271
Description
Failed to change the identity account.
Scenario
The account entered is not an independent account when the rule profile or status of an
identity account is changed.
Access Channel
Web
Possible Causes
The account is not an independent account and cannot be changed.
Procedure
The account is not an independent account and cannot be changed.
4.1785 TP40272
Description
Failed to query the identity service.
Scenario
The identity type does not support the specified query mode when the information about an
identity is queried.
Access Channel
Web
Possible Causes
The identity type does not support the specified query mode.

Copyright © Huawei
Mobile Money
Procedure
Select a correct query mode from the following modes: 1: Query identity information. This
option applies to all identity types. 2: Query the service list. This option applies to customers
and tills. 3: Query the identity information and service list. This option applies to customers
and tills. 4: Query account information. This option applies to customers, organizations, and
SP.
4.1786 TP40273
Description
Scenario
The identity information cannot be queried.
Access Channel
Web
Possible Causes
The information about identities in the New or Close state cannot be queried.
Procedure
1. Log in to the portal as an SP operator.
2. Choose the Search menu to query the detailed identity information.
3. Change the identity status to Active.
4.1787 TP40274
Description
Scenario
The access channel used to query the identity service does not exist.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The access channel does not exist.
Procedure
Entered a valid access channel.
4.1788 TP40275
Description
Scenario
The upper-level organization of the identity does not support service query.
Access Channel
Web
Possible Causes
The upper-level organization is not in the Active, Frozen, or Suspend status and does not
support service query.
Procedure
2. Choose the Search menu to query the detailed information of the identity's upper-level
organization.
3. Change the upper-level organization status to Active.
4.1789 TP40276
Description
The MSISDN parameter does not exist in the request.
Scenario
The MSISDN to be recharge is empty when a non-customer identity initiates an airtime
purchase transaction.
Access Channel
Web, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
The recharge request lacks the MSISDN parameter.
Procedure
When a customer purchases airtime, the MSISDN can be empty, and the system recharges the
customer by default. When identities of other types purchase airtime, the MSISDN is
mandatory. Verify the MSISDN parameter in the request.
4.1790 TP40277
Description
The new and old secret words are the same.
Scenario
The new and old secret words are the same during the secret word changing process.
Access Channel
Web, USSD, API, STK
Possible Causes
The new and old secret words are the same.
Procedure
Set the new and old secret words to different values.
4.1791 TP40278
Description
The MSISDN specified during the till activation process does not belong to a till.
Scenario
Access Channel
USSD, API, STK
Possible Causes

Copyright © Huawei
Mobile Money
Procedure
4.1792 TP40279
Description
An operator queries statements or balances of an organization that is neither the operator's
home organization nor a child organization of the operator's home organization.
Scenario
An operator queries statements or balances of an organization that is neither the operator's
home organization nor a child organization of the operator's home organization.
Access Channel
STK, USSD, API
Possible Causes
The queried organization is neither the operator's home organization nor a child organization
of the operator's home organization.
Procedure
The queried organization must be the operator's home organization or a child organization of
the operator's home organization.
4.1793 TP40289
Description
The {0} identity type does not support the identifier.
{0} indicates an identity identifier type.
Scenario
The {0} identity type does not support the identifier when the identity is created.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The {0} identity type does not support the identifier.
Procedure
Select an identity type that supports the identifier.
4.1794 TP40290
Description
The {0} identity type does not support the {1} identifier.
{0} indicates an identity identifier type, and {1} indicates the value of the identity identifier.
Scenario
The {0} identity type does not support the {1} identifier when the identity is created.
Access Channel
Web
Possible Causes
The {0} identity type does not support the {1} identifier.
Procedure
Enter a value for the {1} identifier that is supported by the {0} identity type.
4.1795 TP40291
Description
The {0} identifier is mandatory.
{0} indicates an identity identifier value.
Scenario
The identifier is empty when an identity is created.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The {0} identifier is empty.
Procedure
Enter a value for the {0} identifier.
4.1796 TP40292
Description
The count of device access numbers must not be greater than the count of numbers in the flag.
Scenario
The count of device access numbers is greater than the count of numbers in the flag when an
identity is created.
Access Channel
Web
Possible Causes
The count of device access numbers is greater than the count of numbers in the flag.
Procedure
The count of device access numbers must be less than or equal to the count of numbers in the
flag.
4.1797 TP40293
Description
The {0} device access number does not exist in the flag list.
{0} indicates the access device number.
Scenario
The device access number does not exist in the flag list when an identity is created.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The {0} device access number does not exist in the flag list.
Procedure
The {0} device access number must exist in the flag list.
4.1798 TP40294
Description
Only one identifier of the {0} type can be entered.
{0} indicates an identity identifier type.
Scenario
The number of identifier types entered is not 1 when an identity is created.
Access Channel
Web
Possible Causes
The number of identifier types entered is not 1.
Procedure
Only one identifier of the {0} type can be entered.
4.1799 TP40295
Description
The {1} identifier of the {0} identifier type is not unique.
{0} indicates an identity identifier type, and {1} indicates the value of the identity identifier.
Scenario
The {1} identifier of the {0} identifier type is not unique when an identity is created.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The {1} identifier of the {0} identifier type is not unique.
Procedure
identifiers of the {0} type must be unique. Set the {1} identifier to another value.
4.1800 TP40296
Description
The {0} access device is not unique.
{0} indicates the access device number.
Scenario
The access device is not unique when an identity is created.
Access Channel
Web
Possible Causes
The {0} access device is not unique.
Procedure
The {0} access device must be unique. Enter a different value for the {0} access device.
4.1801 TP40297
Description
The {0} identifier already exists.
{0} indicates the identifier value of the corresponding identifier type.
Scenario
The identity ID already exists when an identity is created.
Access Channel
Web, USSD, API, STK

Copyright © Huawei
Mobile Money
Possible Causes
The {0} identifier already exists.
Procedure
Enter a different value for the {0} identifier.
4.1802 TP40260
Description
The MSISDN entered does not belong to a till.
Scenario
The MSISDN specified for the access device does not belong to the till for which settlement
is to be performed.
Access Channel
Web, STK, USSD
Possible Causes
The MSISDN specified for the access device does not belong to the till.
Procedure
Enter the MSISDN of a till.
4.1803 TP40264
Description
The claw back Id {0} of the commission claw-back transaction to be cancelled is not in the
Pending Claw-back state.
{0}: indicates the claw back Id.
Scenario
The commission claw-back transaction cannot be cancelled when the ClawBackId is not in
the Pending Claw-back state.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The claw back Id {0} of the commission claw-back transaction to be cancelled is not in the
Pending Claw-back state.
Procedure
Enter the claw back Id of a claw-back transaction in the Pending Claw-back state.
4.1804 TP40265
Description
The SP account is not found.
Scenario
The SP account used in a transaction does not exist.
Access Channel
Web, STK, USSD, API
Possible Causes
The SP account does not exist.
Procedure
4.1805 TP40298
Description
Scenario
During a reverse transaction, no reverse Reason Type is configured for the reason type of the
original transaction.
Access Channel
Web, USSD, API
Possible Causes
No reverse reason type is configured for the reason type of the original transaction.

Copyright © Huawei
Mobile Money
Procedure
Type.
3. Click Add to add a reason type.
4. Click Add in the Original Reason Type area to add a reason type for the transaction to
be reversed.
5. Configure other information and release the reason type.
6. Reverse the transaction again.
4.1806 TP40299
Description
The reason type is incorrect.
Scenario
The specified reason type alias does not exist during a reverse transaction.
Access Channel
Web, USSD, API
Possible Causes
The {0} reason type does not exist in the system. Here, {0} indicates the alias of a reason
type.
Procedure
4.1807 TP40300
Description
Scenario
During a reverse transaction, the specified reason type is not associated with the reason type
of the original transaction.
Access Channel
Web, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
The specified reason type is not associated with the reason type of the original transaction.
Procedure
4.1808 TP40301
Description
Reverse failed because the transaction serial number does not exist.
Scenario
During a reverse transaction, the transaction serial number specified for the original
Access Channel
Web, USSD, API
Possible Causes
The order whose transaction serial number is {0} does not exist in the system.
{0}: indicates the transaction serial number.
Procedure
Reinitiate the transaction and enter a correct order number for the transaction to be rolled
back.
4.1809 TP40302
Description
Scenario
During a reverse transaction, the transaction to be rolled back is not in the Completed state
and cannot be reversed.
Access Channel
Web, USSD, API, STK

Copyright © Huawei
Mobile Money
Possible Causes
The transaction has not been completed and therefore cannot be reversed.
Procedure
Reverse the transaction after it is completed.
4.1810 TP40303
Description
The transaction cannot be reversed because the original transaction has been reversed.
Scenario
The original transaction has been reversed. The possible scenario is as follows: Two operators
reverse the same transaction at the same time. After A successfully reverses the transaction,
the system displays the error code for B who attempts to reverse the same transaction.
Access Channel
Web, USSD, API
Possible Causes
The original transaction has been reversed.
Procedure
Refresh the transaction list and view serial numbers of reversed transactions.
4.1811 TP40304
Description
The original transaction is being reversed and cannot be initiated again.
Scenario
The original transaction is reversed. (Two operators reverse the same transaction at the same
time. A successfully reverses the transaction, and the system displays the error code for B who
attempts to reverse the same transaction.)
Access Channel
Web, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
The original transaction is reversed and is waiting for approval or processing.
Procedure
Wait for the reverse transaction to be completed.
4.1812 TP40305
Description
Reverse failed because the reason type of the original transaction does not exist.
Scenario
This error occurs when the reason type of the original transaction cannot be found during the
reverse transaction.
Access Channel
Web, USSD, API
Possible Causes
Reverse failed because the reason type of the original transaction does not exist.
Procedure
Contact the carrier for more information.
4.1813 TP40306
Description
Scenario
The transaction type of the original transaction does not support reverse.
Access Channel
Web, USSD, API
Possible Causes
The type of the original transaction does not support reverse.

Copyright © Huawei
Mobile Money
Procedure
Contact the carrier for more information.
4.1814 TP40307
Description
Reverse failed because the initiator has no permission to reverse the transaction.
Scenario
The initiator has no permission to reverse the transaction.
Access Channel
Web, USSD, API
Possible Causes
The initiator has no permission to reverse the transaction whose order number is {0}.
{0}: indicates the order number.
Procedure
Verify that the initiator has permission to reverse the transaction.
4.1815 TP40308
Description
Reverse failed because action-related transactions cannot be reversed.
Scenario
Action-related transactions cannot be reversed. For example, if a password is changed, the fee
generated by the action cannot be refunded.
Access Channel
Web, USSD, API
Possible Causes
Action-related transactions cannot be reversed.

Copyright © Huawei
Mobile Money
Procedure
Select a transaction that can be reversed.
4.1816 TP40221
Description
Access {0} device is not a till.
{0}: indicates till number (MSISDN).
Scenario
Operations performed used by a till.
Access Channel
Web, USSD
Possible Causes
Procedure
Set the {0} parameter to a till.
4.1817 TP40226
Description
The value {1} of the {0} parameter is incorrect, failed to authenticate the parameter.
{0}: indicates parameter name.

{1}: indicates parameter value.
Scenario
The parameters in remote procedure call protocol (RPC) packets received by the BCS
network element (NE) are incorrect.
Access Channel
Web, USSD, STK

Copyright © Huawei
Mobile Money
Possible Causes
The value {1} of the {0} parameter is incorrect.
Procedure
Modify the incorrect parameter.
4.1818 TP40227
Description
The service initiator cannot be empty.
Scenario
RPC packets received by the BCS NE do not contain initiator information or the initiator
information is incorrect.
Access Channel
Web, USSD, STK
Possible Causes
The service initiator is empty.
Procedure
Verify that the service initiator is not empty.
4.1819 TP40257
Description
Scenario
Access Channel
Web, USSD, STK
Possible Causes
The operator cannot be parsed.

Copyright © Huawei
Mobile Money
Procedure
Verify the operator information.
4.1820 TP40258
Description
The device does not belong to a till.
Scenario
RPC packets received by the BCS NE specifies that the connection device is till, but the
corresponding till cannot be found.
Access Channel
Web, USSD, STK
Possible Causes
The device does not belong to a till.
Procedure
Enter a till device.
4.1821 TP40259
Description
The initiator must not be empty.
Scenario
Access Channel
Web, USSD, STK
Possible Causes
The initiator is empty.
Procedure
Enter an initiator.

Copyright © Huawei
Mobile Money
4.1822 TP40266
Description
There is an ongoing task when the task is initiated.
Scenario
The same Identity contains incomplete services. Therefore, the same new services cannot be
initiated.
Access Channel
Web, USSD
Possible Causes
Another task is being processed when the task is initiated.
Procedure
Verify that there is no ongoing task being processed before initiating another task.
4.1823 TP40280
Description
Authentication failed because the ID number or the ID type is not unique.
Scenario
Access Channel
Web, USSD, STK
Possible Causes
 The ID number is already used by another identity.
 The ID number of the same type already exists.
Procedure
1. Verify that the ID number is correct and unique.
2. Verify that no duplicate ID numbers are entered for the same ID type.
3. Enter the correct ID number again.

Copyright © Huawei
Mobile Money
4.1824 TP40281
Description
Scenario
Access Channel
Web, USSD
Possible Causes
{0}: indicates KYC field name.
Procedure
Field.
4.1825 TP40282
Description
Failed to create or modify the identity KYC fields.
Scenario
Access Channel
Web, USSD
Possible Causes
The bank-related KYC fields are incomplete in the identity's KYC information.
Procedure
Enter complete bank-related KYC fields, including bank branch id, bank account name, bank
account number, and currency.

Copyright © Huawei
Mobile Money
4.1826 TP40283
Description
The number of bank-related KYC fields is incorrect.
Scenario
Access Channel
Web, USSD
Possible Causes
The number of bank-related KYC fields is not 4.
Procedure
2. Select the specified identity type, and assign four bank-related KYC fields to the identity
type.
4.1827 TP40284
Description
Failed to save the KYC information {0}.
{0} indicates the KYC field name.
Scenario
Access Channel
Web, USSD, STK
Possible Causes
 The {0} KYC field does not apply to the identity type.
 The {0} KYC field is a multi-value field but is placed in the list of single-value KYC
fields.
 The {0} KYC field is a single-value field but is placed in the list of multi-value KYC
fields.

Copyright © Huawei
Mobile Money
{0}: indicates the KYC field name.
Procedure
2. Check whether the {0} KYC field is assigned to the current identity type.
− If yes but the KYC field is not selected, select it and save the changes.
− If no, contact a Huawei engineer for help.
3. If the {0} KYC field is a single-value field, place it in the list of single-value KYC
fields. If the {0} KYC field is a multi-value field, place it in the list of multi-value KYC
fields.
4.1828 TP40285
Description
Failed to verify the KYC.
Scenario
Access Channel
Web, USSD
Possible Causes
KYC field or group does not exist.
Procedure
Please check the KYC information.
4.1829 TP40286
Description
Failed to save the KYC information.
Scenario

Copyright © Huawei
Mobile Money
Access Channel
Web, USSD
Possible Causes
The value of a date or time KYC field is in an incorrect format.
Procedure
Enter the date and time in the correct format.
4.1830 TP40287
Description
Failed to save the identity's KYC information.
Scenario
Access Channel
Web, USSD
Possible Causes
Authentication failed because certain associated KYC fields are not configured at the same
time. For example, the ID type is selected but the ID number is not entered.
Procedure
Verify that associated KYC fields are correctly configured.
4.1831 TP40288
Description
The {0} identifier does not exist.
{0}: indicates identity identifier content.
Scenario
The Identity ID in RPC packets received by the BCS NE is incorrect.

Copyright © Huawei
Mobile Money
Access Channel
Web, USSD, STK, API
Possible Causes
The {0} identifier does not exist.
Procedure
Enter an existing identifier.
4.1832 TS20001
Description
Limit rule authentication failed.
Scenario
During transaction execution, the transaction amount threshold of an identity does not comply
with limit rules.
Access Channel
Web, STK, USSD, API
Possible Causes
The transaction does not meet the limit rule.
Procedure
2. Search for the identity rule profile and account rule profile of the identity in the Search
menu.
3. Choose My Functions > Operational Configuration > Detail Ops Configuration to
enter the Limit Rule configuration page.
4. View the limit rules in the identity's rule profile.
5. Verify whether the current transaction complies with the rules and modify the transaction
request based on the rules.

Copyright © Huawei
Mobile Money
4.1833 TS20002
Description
Failed to obtain the account during limit rule authentication.
Scenario
The limit rule engine fails to obtain the balance of an identity from the transaction engine
context due to a system exception.
Access Channel
Web, STK, USSD, API
Possible Causes
The identity's account data is invalid.
Procedure
2. Search for the identity's basic information in the Search menu and verify whether the
account data is correct.
3. If the data is incorrect, obtain the BCS debug logs and contact a Huawei engineer for
help, or access http://icare.huawei.com and submit a fault application report.
4.1834 TS20003
Description
Failed to authenticate a cumulative threshold.
Scenario
During transaction execution, querying accumulated count of an identity fails because a
database fault occurs.
Access Channel
Web, STK, USSD, API
Possible Causes
Failed to update the database during limit rule authentication.
Procedure
Contact a Huawei engineer for help or access http://icare.huawei.com and submit a fault
application report.

Copyright © Huawei
Mobile Money
4.1835 TS20004
Description
Failed to authenticate an amount limit.
Scenario
Filtering amount upper limit authentication based on transaction scenarios.
Access Channel
Web, STK, USSD, API
Possible Causes
A Class Cast Exception has occurred due to a configuration or code error.
Procedure
menu.
3. Choose My Functions > Operational Configuration > Detail Ops Configuration to
enter the Limit Rule configuration page.
4. Verify the limit rules in the identity's rule profile.
If the problem persists, obtain the BCS debug logs and contact a Huawei engineer for help, or
access http://icare.huawei.com and submit a fault application report.
4.1836 TS20005
Description
Failed to obtain the transaction amount during amount limit authentication.
Scenario
The limit rule engine fails to obtain a transaction amount from the transaction engine context
due to a system exception.
Access Channel
Web, STK, USSD, API
Possible Causes
Failed to obtain the transaction amount from the transaction session.

Copyright © Huawei
Mobile Money
Procedure
4.1837 TS20006
Description
A cumulative threshold record already exists.
Scenario
Access Channel
Web, STK, USSD, API
Possible Causes
A cumulative threshold record already exists. Adding another one results in a primary key
conflict.
Procedure
No processing is needed.
4.1838 TS20008
Description
No cumulative threshold is configured.
Scenario
Accumulating limit rules fails because system resources are insufficient.
Access Channel
Web, STK, USSD, API
Possible Causes
No cumulative threshold is entered.
Procedure
No processing is needed.

Copyright © Huawei
Mobile Money
4.1839 TS20009
Description
The amount limit authentication type is not supported.
Scenario
The number of accumulators exceeds the threshold because limit rule data is incorrect.
Currently, only the total transaction amount, transaction quantity, and action quantity are
supported.
Access Channel
Web, STK, USSD, API
Possible Causes
The amount limit authentication type configured in the Limit Type field is not supported.
Procedure
menu.
3. Choose My Functions > Operational Configuration > Detail Ops Configuration.
4. Choose the Rule Profile submenu, enter the Rule Profile configuration page, and find
and verify the limit rules in the identity's rule profile.
5. Choose the Limit Rule submenu, enter the Limit Rule configuration page, and verify
the limit type of the limit rule.
6. Choose the Limit Type submenu, enter the Limit Type configuration page, modify the
check rule, and verify that all limit types are correctly configured.
4.1840 TS20010
Description
The amount limit authentication rule is not supported.
Scenario
The judge rule for preconfiguring limit types is faulty due to a system exception. The judge
rule must be Max, MIN, or IN.
Access Channel
Web, STK, USSD, API

Copyright © Huawei
Mobile Money
Possible Causes
The amount limit authentication rule configured in the Limit Type field is not supported.
Procedure
menu.
3. Choose My Functions > Operational Configuration > Detail Ops Configuration.
4. Choose the Rule Profile submenu, enter the Rule Profile configuration page, and find
and verify the limit rules in the identity's rule profile.
5. Choose the Limit Rule submenu, enter the Limit Rule configuration page, and verify the
limit type of the limit rule.
6. Choose the Limit Type submenu, enter the Limit Type configuration page, modify the
judge rule, and verify that all limit types are correctly configured.
4.1841 TS24003
Description
The amount cannot be matched with any amount range in the charge profile.
Scenario
No charging range is found based on the transaction amount due to a system exception.
Access Channel
Web, STK, USSD, API
Possible Causes
The amount in the transaction request cannot be matched with any amount range in the charge
profile when ranked charging is configured in the charge profile of the charge type in the
reason type. The configuration is incorrect.
Procedure
2. Search for the charge profile of the identity in the Search menu.
Charge Profile to enter the charge profile configuration page. Verify charge
configurations in the reason type for the identity.

Copyright © Huawei
Mobile Money
4.1842 TS24004
Description
No amount range is configured for the reason type in the charge profile.
Scenario
During transaction execution, obtaining a charging value fails because the amount configured
for Reason Type in Charge Profile is blank.
Access Channel
Web, STK, USSD, API
Possible Causes
The charge rule is not configured or incorrectly configured for the reason type in the charge
profile.
Procedure
Charge Profile to enter the charge profile configuration page.
4. Add or complete the charge rule for the reason type.
4.1843 TS24005
Description
No charge rule is configured for the reason type in the charge profile.
Scenario
During transaction execution, querying charging rules based on a reason type fails.
Access Channel
Web, STK, USSD, API
Possible Causes
No charge rule is configured for the reason type in the charge profile.
Procedure

Copyright © Huawei
Mobile Money
Charge Profile to enter the charge profile configuration page.
4. Add a charge rule for the reason type.
4.1844 TS24100
Description
An empty field is found during charge calculation.
Scenario
Updating charging configuration data in the charge profile on the background fails due to
system exception.
Access Channel
Web, STK, USSD, API
Possible Causes
The cached data is incorrect. No charge profile is obtained from the cache.
Procedure
application report.
4.1845 TS28007
Description
The status of the {0} account type cannot be changed to {1}.
Scenario
When the account status is automatically updated or updated by an SP operator, whether the
account can be updated to the target status is checked.
Access Channel
Web
Possible Causes
The {0} status cannot be specified for the {0} account type, or the original status cannot be
changed to the specified status.

Copyright © Huawei
Mobile Money
Procedure
1. Choose My Functions > Core Configuration > Advanced Configuration > Account
Type.
2. Check whether an evolution relationship is configured for the old and new states in the
system.
Default status evolution relationships are configured in the
CPS_ACCOUNT_STATUS_RELATION table. To change the table data, contact a Huawei
engineer for help or access http://icare.huawei.com and submit a change application.
4.1846 TS28008
Description
The debiting operation is illegal.
Scenario
A system exception occurs, the interface package is inconsistent.
Access Channel
Web, STK, USSD, API
Possible Causes
An exception occurred during program running.
Procedure
4.1847 TS28009
Description
The balance in account {2} of account type {1} of identity {0} is insufficient for the
transaction.
{0}: indicates identity name.

{2}: indicates account.
Scenario
The account balance of a subscriber is insufficient during transaction execution.

Copyright © Huawei
Mobile Money
Access Channel
Web, STK, USSD, API
Possible Causes
Procedure
4.1848 TS28010
Description
The account signature is tampered.
Scenario
Account signature information is modified by using structured query language (SQL)
statements on the background.
Access Channel
Web, STK, USSD, API
Possible Causes
The background account signature is tampered.
Procedure
application report.
4.1849 TS28011
Description
The {0} account already exists.
{0}: indicates identity ID.
Scenario
The identity account to be created already exists.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The {0} account already exists. Currently, for a customer or agent, only one account can be
created for an account type.
Procedure
Select an account type for which no account is created.
4.1850 TS28012
Description
Data of the identity's account is changed too frequently. Try again later.
Scenario
During a transaction, the number of account data updates in a certain period exceeds the
maximum number of optimistic lock updates.
Access Channel
Web, STK, USSD, API
Possible Causes
The number of changes to the identity's account data exceeds the upper limit configured for
the optimistic lock.
Procedure
4.1851 TS28013
Description
The {0} identity type cannot have an account.
{0}: indicates identity type, for example, customer.

Copyright © Huawei
Mobile Money
Scenario
The account type definition does not support the identity that is not SP, customer, or
organization during an account creation.
Access Channel
Web
Possible Causes
The account type definition does not support the {0} identity type.
Procedure
1. On the SP Portal, choose My Functions > Core Configuration > Advanced
Configuration > Account Type.
2. Query for the account type definitions and configure a supported identity type.
If the identity type is not in the configurable list, the identity cannot have accounts. Select
another identity and create an account.
4.1852 TS28300
Description
The balance in the account to be closed is not 0.
Scenario
If the balance of an account whose status is to be updated to close is not 0, the account cannot
be closed.
Access Channel
Web(System)
Possible Causes
The account cannot be closed because the balance is not 0.
Procedure
Clear the account balance by transfer or cashing and perform the operation again.

Copyright © Huawei
Mobile Money
4.1853 TS39600
Description
make_checker does not exist.
Scenario
The revenue settlement system parameter make_checker is not set due to a system exception.
Access Channel
Web
Possible Causes
The make_checker system control parameter is not configured for revenue settlement.
Procedure
2. Choose My Functions > Finance > Revenue Settlement > Settlement Configuration.
3. Verify that Maker-Checker is correctly configured for revenue settlement.
4.1854 TS39601
Description
The revenue settlement plan must be in the {1} or {2} state.
{1}: Planned
{2}: Settlement Finished
Scenario
During balance freezing, the settlement task is no in the Planned state due to a system
exception.
Access Channel
System
Possible Causes
The revenue settlement plan is in the {0} state, which is invalid.
{0}: indicates status of the current task, for example, New.

Copyright © Huawei
Mobile Money
Procedure
4.1855 TS39602
Description
A revenue settlement plan is being processed, and no new revenue settlement plan can be
created.
Scenario
A new task is created when the previous revenue settlement plan is not executed.
Access Channel
System
Possible Causes
A revenue settlement plan is being processed.
Procedure
2. Choose My Functions > Finance > Revenue Settlement > Settlement Process.
3. Complete all revenue settlement plans that are being processed and verify that they end
up in the Failed, Terminate, Completed, or Cancelled state.
4.1856 TS39603
Description
Hot account debiting failed.
Scenario
If the settlement account is a hot account, debiting fails due to insufficient database or system
resource.
Access Channel
System
Possible Causes
Database or system resource is insufficient.

Copyright © Huawei
Mobile Money
Procedure
4.1857 TS39604
Description
Failed to create the revenue settlement plan.
Scenario
Recording task plan data fails due to a database exception.
Access Channel
System
Possible Causes
Failed to create the revenue settlement plan.
Procedure
4.1858 TS39605
Description
Failed to create the revenue settlement details.
Scenario
Access Channel
System
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
4.1859 TS39606
Description
Failed to query the account by reason type.
Scenario
No SP settlement account is found based on Reason Type because the account is not created.
Access Channel
System
Possible Causes
Failed to query the account.
Procedure
3. Verify that debit and credit accounts are configured for the revenue settlement reason
type.
4.1860 TS39607
Description
No SP account is found by reason type.
Scenario
Querying an SP settlement account fails because the reason type for settlement is incorrect or
a database exception occurs.
Access Channel
System
Possible Causes
Failed to query the SP account by reason type.
Procedure

Copyright © Huawei
Mobile Money
3. Verify that debit and credit accounts are configured for the revenue settlement reason
type.
4.1861 TS39608
Description
No reason type is found in the revenue settlement configurations.
Scenario
The settlement reason type in the cache is null or not configured due to a system exception.
Access Channel
System
Possible Causes
Failed to query the reason type in the revenue settlement configurations.
Procedure
2. Choose My Functions > Core Configuration > Advanced > Configuration > Reason
3. Verify that the revenue settlement reason type is configured.
4.1862 TS39609
Description
The balance in the receiver's account must be greater than 0.
Scenario
The balance of the revenue account is found to be less than zero during revenue settlement.
Access Channel
System
Possible Causes
The balance in the receiver's account {0} is less than 0.
{0}: indicates revenue account number.

Copyright © Huawei
Mobile Money
Procedure
2. Choose My Functions > Core Configuration > Advanced Configuration > Account
Type to enter the Account Type configuration page.
3. Verify configurations for the receiver's account.
4.1863 TS39611
Description
Failed to query the revenue settlement account.
Scenario
The Settlement Account system parameter is not set.
Access Channel
System
Possible Causes
The revenue settlement account is not configured or incorrectly configured.
Procedure
2. Choose My Functions > Operational Configuration > System Parameter > Revenue
Settlement.
3. Verify that the Settlement Account Type field is displayed on the GUI and set to
Revenue Settlement Account.
4.1864 RN36000
Description
No reconciliation file record is found.
Scenario
No reconciliation file record is found.
Access Channel
Web, STK, USSD

Copyright © Huawei
Mobile Money
Possible Causes
A data exception has occurred.
Procedure
4.1865 RN36001
Description
No reconciliation detail is obtained.
Scenario
No reconciliation record detail is obtained based on the detail ID.
Access Channel
Web
Possible Causes
Procedure
4.1866 RN36014
Description
Failed to generate a reconciliation report.
Scenario
No reconciliation report data is generated.
Access Channel
Web
Possible Causes
No report needs to be generated.

Copyright © Huawei
Mobile Money
Procedure
This operation is unnecessary.
4.1867 RN36015
Description
The reconciliation report fails to be approved.
Scenario
A statement reconciliation task is approved by another operator.
Access Channel
Web
Possible Causes
The reconciliation task does not exist.
Procedure
4.1868 RN36018
Description
The parameter is invalid.
Scenario
During a reconciliation transaction performed after statements are parsed, parameters in
statements are found invalid.
Access Channel
Web
Possible Causes
{0}
{0} indicates invalid parameter description, for example, bankId is not exist.

Copyright © Huawei
Mobile Money
Procedure
4.1869 RN36025
Description
Failed to find the default operator.
Scenario
No default operator is configured, or configured default operator does not exists.
Access Channel
Web, STK, USSD, API
Possible Causes
The default operator is not configured or incorrectly configured.
Procedure
Transaction to enter the system parameter configuration page.
2. Correctly configure the SP Operator Initiating Transaction.
4.1870 RN36027
Description
No control account is obtained for the {0} parameter.
{0} indicates accountNo or BankId.
Scenario
When an EFT file is exported, or a statement is imported, no control account is found based
on the control account number or bank ID.
Access Channel
Web
Possible Causes
The control account does not exist.

Copyright © Huawei
Mobile Money
Procedure
4.1871 RN36029
Description
Failed to export EFT.
Scenario
An error occurs when an EFT file is exported.
Access Channel
Web
Possible Causes
{0}
Procedure
{1}
{1} indicates please check the tc logs.
4.1872 RN36030
Description
Failed to import reconciliation statements. Cause: {0}
{0}: indicates the cause of a failure.
Scenario
An error occurs when a statement is imported.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
Failed to import reconciliation statements. Cause: {0}
Procedure
locating.
4.1873 RN36031
Description
Failed to match reconciliation records for control account transfer transactions.
Scenario
Reconciliation records of a credit party are not found during automatic or manual
reconciliation performed after statements are imported.
Access Channel
Web
Possible Causes
Failed to find the credit reconciliation record by the {0} transLogId.
Procedure
4.1874 RN36032
Description
Scenario
Multiple reconciliation records of a credit party are found during automatic or manual
reconciliation performed after statements are imported.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
Multiple credit reconciliation records are found by the {0} transLogId.
Procedure
4.1875 RN36034
Description
SFTP connection failed.
Scenario
SFTP connections fail when bills are imported or EFT files are exported.
Access Channel
Web
Possible Causes
{0}
{0} indicates a connection error.
Procedure
1. Choose My Functions > Operational Configuration > System Parameter > SFTP
Parameters.
2. Verify whether the SFTP configurations are correct.
4.1876 RN36035
Description
Failed to obtain the {0} system parameter.
{0} indicates a system parameter, for example, EFT_ROOT_PATH or STATEMENT_HISTORY_PATH.

Copyright © Huawei
Mobile Money
Scenario
System parameters are not obtained in the following scenarios: 1. Bank reconciliation
directory creation 2. Statement download 3. Access to SFTP configurations including user
names and passwords 4. EFT file and log download
Access Channel
Web
Possible Causes
The {0} system parameter is not configured.
Procedure
Parameters.
2. Configure SFTP system parameters as required.
4.1877 RN36036
Description
Failed to access the {0} directory.
{0} indicates a directory that does not exist.
Scenario
An access directory does not exist or no access permission is assigned when statements are
imported, EFT files are exported, and logs are downloaded.
Access Channel
Web
Possible Causes
The directory does not exist, or the operator has no permission to access the directory.
Procedure
Check whether the directory exists. If no, manually create the directory. If yes, assign the
permission for accessing the directory to the operator.

Copyright © Huawei
Mobile Money
4.1878 RN36037
Description
Failed to obtain information about the bank whose bank ID is {0}.
{0} indicates bank ID.
Scenario
No bank information is found based on a bank ID during EFT file export.
Access Channel
Web
Possible Causes
Procedure
4.1879 RN36038
Description
Failed to submit the reconciliation report approval task.
Scenario
Submitting a reconciliation report fails because the reconciliation report is not created.
Access Channel
Web
Possible Causes
No reconciliation report is created.
Procedure
Click Generate Summary to generate a reconciliation report.

Copyright © Huawei
Mobile Money
4.1880 RN36039
Description
Scenario
Submitting a reconciliation report fails because the reconciliation report has expired.
Access Channel
Web
Possible Causes
The reconciliation report has expired.
Procedure
Click Generate Summary to generate a reconciliation report again.
4.1881 RN36040
Description
Failed to generate a reconciliation report.
Scenario
Generating a reconciliation report fails after the reconciliation report is uploaded to an SFTP
server.
Access Channel
Web
Possible Causes
{0}
Procedure
Parameters.

Copyright © Huawei
Mobile Money
4.1882 RN36041
Description
Scenario
Submitting a reconciliation report for approval fails because a reconciliation report to be
approved already exists.
Access Channel
Web
Possible Causes
The task for approving the reconciliation report already exists.
Procedure
Wait until the reconciliation report is approved.
4.1883 RN36042
Description
Failed to create the {0} directory.
{0} indicates a directory to be created.
Scenario
Creating a directory fails in the following scenarios: 1. Control account creation 2.Statement
log import 3. EFT file export
Access Channel
Web
Possible Causes
{1}

Copyright © Huawei
Mobile Money
Procedure
Parameters.
2. Verify whether the directories configured for the SFTP are correct.
3. Ask for the administrator to create the necessary folder manually.
4.1884 RN36043
Description
Failed to obtain the {0} EFT exporter.
Scenario
No EFT exporter is configured for importing statements.
Access Channel
Web
Possible Causes
No EFT exporter is configured.
Procedure
Parameter > System Parameter Items > Financial Generic Parameters.
2. Configure an exporter.
4.1885 RN36044
Description
The {0} EFT exporter is not found.
{0}: indicates Flag String in File Name configured in the parser.
Scenario
No parser is found during reconciliation statement import.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The EFT exporter is incorrectly configured.
Procedure
2. Verify that an exporter is correctly configured.
4.1886 RN36045
Description
Failed to obtain the {0} bill parser.
Scenario
No parser is found during reconciliation statement import.
Access Channel
Web
Possible Causes
No bill parser is configured.
Procedure
2. Configure a bill parser.
4.1887 RN36046
Description
The {0} bill parser is not found.
Scenario
The parser is incorrectly configured during reconciliation statement import.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The bill parse is incorrectly configured.
Procedure
2. Verify that a bill parser is correctly configured.
4.1888 RN36047
Description
Scenario
A system exception has occurred.
Access Channel
Web
Possible Causes
{0}
{0}: indicates description about a parameter that does not exist, for example, Bank ID is not exist.
Procedure
4.1889 RN36049
Description
Failed to obtain the {0} SFTP parameter.
{0}: indicates the name of a parameter that is not configured.

Copyright © Huawei
Mobile Money
Scenario
An SFTP system parameter is not configured for the following scenarios: 1. Reconciliation
statement import 2. EFT file export 3. Log file download
Access Channel
Web
Possible Causes
The {0} SFTP parameter is not configured.
Procedure
Parameters.
2. Configure the {0} parameter.
4.1890 RN36052
Description
The account does not exist.
Scenario
When a reconciliation statement is imported, the system creates a deposit transaction based on
the statement content. If the second transaction is Bank Charge or Bank Interest, the system
checks whether the bank has an account of this type.
Access Channel
Web
Possible Causes
Failed to obtain the account whose account type is {1} for the {0} bank.
{0}: indicates a bank name.

{1}: indicates an account type.
Procedure
1. Choose Search > Service Provider > Bank and Account > Bank Client.
2. Create a {1} account for the {0} bank.

Copyright © Huawei
Mobile Money
4.1891 RN36055
Description
Failed to obtain the bank card whose ID is {0}.
{0}: indicates the ID of a bank card.
Scenario
Failed to obtain the bank card based on the bank card ID.
Access Channel
Web
Possible Causes
Procedure
4.1892 RN36056
Description
Failed to obtain the bank card associated with the organization whose short code is {0}.
{0}: indicates an identity ID.
Scenario
The identity ID of an organization is not associated with a bank card.
Access Channel
Web
Possible Causes
The organization whose short code is {0} is not associated with a bank card.
Procedure
2. Select the organization whose short code is {0}.

Copyright © Huawei
Mobile Money
3. Select Overview > Organization Info > KYC Info > Bank Account Details and
associate it with a bank card.
4.1893 RN36058
Description
Failed to find the SP whose SP short code is {0}.
{0}: indicates an SP short code.
Scenario
Failed to find the SP base on SP short code.
Access Channel
Web
Possible Causes
The SP Short Code parameter is incorrect.
Procedure
Enter a correct SP short code.
4.1894 RN36060
Description
Scenario
The transaction to be reversed is not an e-money withdrawal transaction.
Access Channel
Web
Possible Causes
The original transaction is not an E-money cashing transaction.
Procedure
Select a correct reverse transaction template.

Copyright © Huawei
Mobile Money
4.1895 RN36061
Description
Scenario
The transaction cannot be reversed because a derivative transaction (second traction) has been
approved.
Access Channel
Web
Possible Causes
The transaction cannot be reversed because a derivative transaction is approved.
Procedure
Select another transaction to be reversed.
4.1896 RN36062
Description
The current operation is not supported.
Scenario
The status of the reconciliation statement does not support the current association operation.
Access Channel
Web
Possible Causes
The entry is already processed.
Procedure
Select another entry to be processed.

Copyright © Huawei
Mobile Money
4.1897 RN36070
Description
A request parameter is incorrect.
Scenario
A request parameter is incorrect.
Access Channel
Web
Possible Causes
The request parameter is empty.
Procedure
Set the request parameter to a correct value.
4.1898 RN36071
Description
The account number of the control account is incorrect.
Scenario
The account number of the control account is incorrect.
Access Channel
Web
Possible Causes
The bank card obtained based on ctrlAccountNo is empty.
Procedure
Enter a correct value for ctrlAccountNo.

Copyright © Huawei
Mobile Money
4.1899 RN36072
Description
The workflow fails to be initiated.
Scenario
Failed to generate a reconciliation workflow.
Access Channel
Web
Possible Causes
Failed to invoke the BCS to create a workflow.
Procedure
Set request parameters to correct values.
4.1900 WF55006
Description
The time format cannot be parsed.
Scenario
Modify KYC on the portal.
Access Channel
Web
Possible Causes
Procedure
Enter a time in the required format.

Copyright © Huawei
Mobile Money
Error Codes Reference 4 BTS Error Codes
5 BTS Error Codes
About This Chapter

5.1 BC50000
5.2 BC50001
5.3 BC50003
5.4 BC50004
5.5 BC51108
5.6 BC51125
5.7 BC51128
5.8 BC51131
5.9 BC51136
5.10 BC51137
5.11 BC51138
5.12 BC52002
5.13 BC52003
5.14 BC52004
5.15 BC52005
5.16 BC52014
5.17 BC52015
5.18 BC52017
5.19 BC52018
5.20 BC52019

Copyright © Huawei
Mobile Money
5.21 BC52020
5.22 BC52021
5.23 BC52022
5.24 BC52023
5.25 BC52027
5.26 BC52029
5.27 BC52032
5.28 BC52037
5.29 BC52038
5.30 BC52043
5.31 BC52046
5.32 BC52048
5.33 BC52052
5.34 BC52053
5.35 BC52054
5.36 BC52055
5.37 BC52056
5.38 BC52057
5.39 BC52060
5.40 BC52061
5.41 BC52062
5.42 BC52063
5.43 BC52064
5.44 BC52065
5.45 BC52067
5.46 BC52068
5.47 BC52069
5.48 BC52070
5.49 BC52071
5.50 BC52072
5.51 BC52073
5.52 BC52074
5.53 BC52075

Copyright © Huawei
Mobile Money
5.54 BC52076
5.55 BC52077
5.56 BC52078
5.57 BC52079
5.58 BC52080
5.59 BC52081
5.60 BC52082
5.61 BC52083
5.62 BC52084
5.63 BC52085
5.64 BC52086
5.65 BC52087
5.66 BC52088
5.67 BC52089
5.68 BC52090
5.69 BC52091
5.70 BC52092
5.71 BC52093
5.72 BC52094
5.73 BC52095
5.74 BC52096
5.75 BC52097
5.76 BC60001
5.77 BC60003
5.78 BC60004
5.79 BC60005
5.80 BC60006
5.81 BC60007
5.82 BC60008
5.83 BC60009
5.84 BC60010
5.85 BC60011
5.86 BC60012

Copyright © Huawei
Mobile Money
5.87 BC60013
5.88 BC60014
5.89 BC60015
5.90 BC60016
5.91 BC60017
5.92 BC60018
5.93 BC61000
5.94 CS50000
5.95 CS50001
5.96 CS50002
5.97 CS50004
5.98 CS50005
5.99 CS50006
5.100 CS50007
5.101 CS50008
5.102 CS50009
5.103 CS50010
5.104 CS50011
5.105 CS50012
5.106 BTS00002
5.107 BTS00003
5.108 BTS00004
5.109 BTS00005
5.110 BTS00006
5.111 BTS00007
5.112 BTS00008
5.113 BTS00009
5.114 BTS00010
5.115 BTS00011
5.116 BTS00012
5.117 BTS00013
5.118 BTS00014
5.119 BTS00015

Copyright © Huawei
Mobile Money
5.120 BTS00016
5.121 BTS00017
5.122 BTS00018
5.123 BTS00019
5.124 BTS00020
5.125 BTS00021
5.126 BTS00022
5.127 BTS00023
5.128 BTS00024
BC50000
Description
The operation failed.
Scenario
A system error has occurred when the NE is running. For example, a database exception has
occurred.
Access Channel
Web, API
Possible Causes
An unknown system exception has occurred.
Procedure
Collect /log/debug/*.log on {0} NE and send the log to a Huawei engineer for fault locating.
The {0} variable indicates the name of the NE.
5.1 BC50001
Description
A logic execution error has occurred in the {0} NE.
The {0} variable indicates an NE type, for example, BCS.

Copyright © Huawei
Mobile Money
Scenario
A system error has occurred. For example, the BTS invokes the BCS to execute a bulk
operation but the BCS fails to be started.
Access Channel
Web
Possible Causes
A logic execution error has occurred in the {0} NE.
Procedure
Check whether the {0} NE is normally started.
5.2 BC50003
Description
The secure file transfer protocol (SFTP) operation failed.
Scenario
An SFTP parameter (for example, password to the SFTP server) cannot be obtained when an
SP or organization operator uploads or downloads files on a web page.
Access Channel
Web
Possible Causes
Failed to obtain the SFTP parameter.
Procedure
3. Check SFTP parameter settings are correct.
4. Change incorrect parameter values as required.
5.3 BC50004
Description
The secure file transfer protocol (SFTP) operation failed.

Copyright © Huawei
Mobile Money
Scenario
A system exception has occurred because of network connection or permission errors when an
service provider (SP) or organization operator uploads or downloads files on a web page. For
example, the configure SFTP user has no permission to perform operations on the specified
directory.
Access Channel
Web
Possible Causes
Failed to connect to the SFTP server or there is no permission.
Procedure
3. Check SFTP parameter settings are correct.
4. Change incorrect parameter values as required.
5.4 BC51108
Description
The {0} field is empty.
The {0} variable indicates the name of a mandatory field in the bulk file, for example, mobile station
international ISDN number (MSISDN).
Scenario
When an SP or organization operator creates a bulk task on a web page or through an API, the
system verifies the bulk file data after the plan is submitted.
Access Channel
Web, API
Possible Causes
The {0} field in the bulk file is empty.
Procedure

Copyright © Huawei
Mobile Money
5.5 BC51125
Description
Fields are missing in the {0} line.
The {0} variable indicates the line number of a record in the bulk file, for example, 1.
Scenario
When an SP or organization operator creates a bulk task on a web page by uploading a bulk
file, the BTS module parses and verifies the bulk file.
Access Channel
Web
Possible Causes
Fields are missing in the {0} line of the bulk file.
Procedure
Verify the {0} line in the file that is uploaded.
5.6 BC51128
Description
The task is cancelled by an operator and will not be executed.
Scenario
This message is displayed when an operator cancels a batch task or system task that is being
executed through web.
Access Channel
Web
Possible Causes
The task is cancelled by an operator.
Procedure
Initiate another task.

Copyright © Huawei
Mobile Money
5.7 BC51131
Description
The amount in the {0} line is incorrect.
The {0} variable indicates the line number of a record in the bulk file, for example, 1.
Scenario
Access Channel
Web
Possible Causes
The amount in the {0} line in the bulk file is incorrect.
Procedure
Verify the {0} line in the file that is uploaded.
5.8 BC51136
Description
Execution timed out.
Scenario
Access Channel
Web
Possible Causes
The BCS does not respond, resulting in bulk task timeout.
Procedure
Create a bulk task plan again.

Copyright © Huawei
Mobile Money
5.9 BC51137
Description
The system supports only bulk files in the TXT, CSV, or XML formats.
Scenario
When a bulk task is created, the bulk file to be uploaded on a web page is in an incorrect
format.
Access Channel
Web, API
Possible Causes
The system does not support the current bulk file format.
Procedure
Upload a bulk file in a correct format.
5.10 BC51138
Description
The {1} field in the bulk file must be unique.
Scenario
When a bulk task is created, the system verifies the bulk file data.
Access Channel
Web
Possible Causes
The {1} field in the current record is the same as the field in record {0}.
{0}: indicates the sequence of bulk data in a bulk file, for example, 1 indicates the first data record.
{1}: indicates a field or combination of fields that must be unique in different records in a bulk file.
Procedure
Verify that the field is unique in the bulk file.

Copyright © Huawei
Mobile Money
5.11 BC52002
Description
The format of the XML file is incorrect.
Scenario
Access Channel
Web
Possible Causes
Failed to load the bulk file.
Procedure
Verify that the bulk file complies with xml rules.
5.12 BC52003
Description
Failed to load the bulk file.
Scenario
file, the BC module parses and verifies the bulk file.
Access Channel
Web
Possible Causes
The number of records in a bulk file cannot exceed {0}.
The {0} variable indicates the maximum number of records in a bulk file. The default value is 30000.
Procedure
Split and reload the file.

Copyright © Huawei
Mobile Money
5.13 BC52004
Description
The bulk task is in the Failed status and cannot be cancelled.
Scenario
An SP or organization operator cancels a bulk task plan on a web page.
Access Channel
Web
Possible Causes
The task is in the Failed status and cannot be cancelled.
Procedure
Refresh the page and verify the status of the bulk task. A task in the failed status cannot be
cancelled.
5.14 BC52005
Description
All valid records have been sent to the BCS module for processing. The bulk task cannot be
cancelled or suspended.
Scenario
A user cancels or suspends a bulk task on a web page.
Access Channel
Web
Possible Causes
There is no valid record in the Pending status.
Procedure
The bulk task cannot be cancelled or suspended.

Copyright © Huawei
Mobile Money
5.15 BC52014
Description
The number of tasks in the execution time slot selected for the bulk task has reached the upper
limit.
Scenario
An SP or organization operator selects the execution time slot for a bulk task plan on a web
page.
Access Channel
Web
Possible Causes
The number of tasks in the time slot has reached the upper limit.
Procedure
Select another time slot for executing the task.
5.16 BC52015
Description
The task is interrupted by an exception.
Scenario
The BTS NE restarts.
Access Channel
Web
Possible Causes
The BTS is restarted before a system task is completed.
Procedure
Manually trigger the task or wait for the system to trigger the task again next time. The
procedure for manually triggering the task is as follows:
2. Choose My Functions > Operation Support > System Task Plan > System Task
Plan.

Copyright © Huawei
Mobile Money
3. Select the task plan to be triggered, click View and enter View System Task Plan page.
4. Click Manual Execution.
5.17 BC52017
Description
Scenario
An SP or organization operator modifies the traffic control parameter TPS of the BTS on a
web page.
Access Channel
Web
Possible Causes
The TPS must be greater than 0.
Procedure
Set the TPS to a value greater than 0.
5.18 BC52018
Description
Scenario
An SP or organization operator modifies the traffic control parameter Package size of the BTS
on a web page.
Access Channel
Web
Possible Causes
The package size ranges from 10 to 100.
Procedure
Set the package size to a value ranging from 10 to 100.

Copyright © Huawei
Mobile Money
5.19 BC52019
Description
The task is not in the running status.
Scenario
An SP or organization operator modifies the execution status of a bulk task on a web page.
Access Channel
Web
Possible Causes
The bulk task plan is suspended by an operator.
Procedure
Refresh the page and verify the status of the bulk task. Only a task in the running status can be
suspended.
5.20 BC52020
Description
The task cannot be resumed again.
Scenario
An SP or organization operator resumes a bulk task on a web page.
Access Channel
Web
Possible Causes
The task is already resumed and cannot be resumed again.
Procedure
Refresh the page and verify the status of the bulk task.

Copyright © Huawei
Mobile Money
5.21 BC52021
Description
The number of valid records must be greater than 0.
Scenario
file, the bulk file contains no valid record.
Access Channel
Web
Possible Causes
The uploaded bulk file contains no valid record.
Procedure
Click Error Items and view the detailed error cause.
5.22 BC52022
Description
The length of the plan name exceeds the upper limit.
Scenario
When an SP or organization operator creates a bulk task on a web page, the length of the plan
name exceeds 64 characters.
Access Channel
Web
Possible Causes
The length of the plan name exceeds the upper limit.
Procedure
Set the plan name to a string with 1 to 64 characters.

Copyright © Huawei
Mobile Money
5.23 BC52023
Description
The length of the plan description exceeds the upper limit.
Scenario
When an SP or organization operator creates a bulk task on a web page, the length of the
Description field exceeds 256 characters.
Access Channel
Web
Possible Causes
The length of the plan description exceeds the upper limit.
Procedure
Set the plan description to a string with 1 to 256 characters.
5.24 BC52027
Description
Failed to create the bulk task plan.
Scenario
A workflow fails to be invoked when an SP or organization operator creates a bulk task plan
on a web page. For example, when the system invokes a workflow to verify whether a task
needs to be approved, the workflow fails to be invoked.
Access Channel
Web
Possible Causes
Failed to invoke the workflow.
Procedure
Locate the error cause and perform troubleshooting based on information in the
/log/debug/*_debug.log file on the BCS under the help of a Huawei engineer.

Copyright © Huawei
Mobile Money
5.25 BC52029
Description
Scenario
When an SP or organization operator creates a task plan on a web page, the task status change
is not supported.
Access Channel
Web
Possible Causes
The current status is {0} and cannot be changed to {1}.
The {0} and {1} variables indicates task status, which can be Initial, Checking, Waitactive, Failed,
Active, Disactive, Expire, Final, or cancelled.
Procedure
Query bulk plans again and verify the status.
5.26 BC52032
Description
The task is being executed, but the execution time has exceeded the configured validity
period. Task execution times out.
Scenario
The execution time has exceeded the configured validity period during a system task is
executed.
Access Channel
Web
Possible Causes
The task is being executed, but the execution time has exceeded the configured validity
period.

Copyright © Huawei
Mobile Money
Procedure
A task execution timeout or a system exception occurs. Try again later.
5.27 BC52037
Description
Payment operation failed.
Scenario
An SP or organization operator initiates a bulk payment task on a web page or through an
API.
Access Channel
Web, API
Possible Causes
Payment operation failed.
Procedure
Check BCS logs in the /log/debug/bcs_debug.log.
5.28 BC52038
Description
The bulk plan has expired before being approved, and the bulk data in the bulk plan has been
deleted from the system.
Scenario
A task that is initiated by an SP or organization operator on a web page or through an API
requires approval, but is not approved before the expiration time.
Access Channel
Web
Possible Causes
The bulk plan has expired before being approved.

Copyright © Huawei
Mobile Money
Procedure
Create another bulk plan.
5.29 BC52043
Description
The organization has not subscribed to the service.
Scenario
When an SP or organization operator initiates a bulk payment task on a web page or through
an API, the specified organization has not subscribed to the bulk payment service.
Access Channel
Web, API
Possible Causes
The organization has not subscribed to the service.
Procedure
Verify that the organization has subscribed to the bulk payment service. If not, subscribe to
the service for the organization.
5.30 BC52046
Description
The operator has no permission to use the service.
Scenario
An SP or organization operator who does not have the permission to initiate bulk tasks
attempts to initiate a bulk task on a web page or through an API.
Access Channel
Web
Possible Causes
The operator has no permission to use the service.

Copyright © Huawei
Mobile Money
Procedure
Verify that the operator has the permission to use the service. If not, assign the permission for
the operator.
5.31 BC52048
Description
Select an available execution time.
Scenario
An SP or organization operator creates a bulk task plan on a web page, and sets the task
execution time to a time earlier than the current time.
Access Channel
Web
Possible Causes
The specified execution time has expired.
Procedure
Select another execution time.
5.32 BC52052
Description
A bulk task plan cannot be created for the {0} organization.
{0}: indicates the short code of the organization to which an operator who creates a bulk payment task
belongs.
Scenario
An organization operator attempts to create a bulk payment task on a web page for an
organization which is not the home organization of the operator.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
A bulk task plan cannot be created for the {0} organization.
Procedure
Check the organization of the operator.
5.33 BC52053
Description
Failed to cancel the bulk task plan.
Scenario
An SP or organization operator cancels a bulk task that is being executed on a web page.
Access Channel
Web
Possible Causes
All items are executed.
Procedure
Query the bulk task plan again.
5.34 BC52054
Description
The {0} parameter is invalid.
The {0} variable indicates an invalid third-party parameter from an API, for example, IdentifierType is
not set to 4 which indicates an organization.
Scenario
An SP or organization operator initiates a bulk task through an API.
Access Channel
API

Copyright © Huawei
Mobile Money
Possible Causes
A parameter from a third-party system is invalid.
Procedure
Collect bulk center logs in /log/debug/bc_debug.log and send the logs to a Huawei engineer
for fault locating.
5.35 BC52055
Description
Failed to obtain the execution time.
Scenario
An SP or organization operator creates a bulk task plan through an API.
Access Channel
API
Possible Causes
The execution time specified for the bulk task plan created through an API is in an incorrect
format.
Procedure
Verify whether the date and time settings are valid.
5.36 BC52056
Description
The operator is not found.
Scenario
An SP or organization operator initiates a bulk task through an API.
Access Channel
API
Possible Causes
No operator is found for the bulk task plan created through an API.

Copyright © Huawei
Mobile Money
Procedure
Set the identifier type and identifier to correct values.
5.37 BC52057
Description
The operator has no permission to perform the current operation.
Scenario
The operator has no permission to perform the bulk operation (view, create, modify, or
cancel).
Access Channel
Web
Possible Causes
The operator has no permission to perform the current operation.
Procedure
Verify whether the role of the operator has the permission to perform the current task. If no,
apply for the permission for the role from the home organization.
5.38 BC52060
Description
The bank is not associated with a control account.
Scenario
An SP or organization operator creates a reconciliation task plan on a web page.
Access Channel
Web
Possible Causes
The bank selected during bank reconciliation configuration has not associated with a control
account.

Copyright © Huawei
Mobile Money
Procedure
Select another bank.
5.39 BC52061
Description
The task will never be executed.
Scenario
An SP or organization operator creates or modifies a scheduled task on the web page, the
execution time specified for the scheduled task is invalid.
Access Channel
Web
Possible Causes
The specified task execution time is invalid.
Procedure
Verify that the execution time is later than the current time.
5.40 BC52062
Description
All records are invalid.
Scenario
The bulk file uploaded by an SP or organization operator to create a bulk task plan on a web
page or through an API contains no valid data record.
Access Channel
Web, API
Possible Causes
After a bulk task plan is created, the system checks whether the records are valid in
asynchronous mode. None of the data records is valid based on the check result.

Copyright © Huawei
Mobile Money
Procedure
Click Failed Initial Validation Items to view the detailed error description.
5.41 BC52063
Description
No scheduled task is found.
Scenario
An SP or organization operator attempts to modify an AML scheduled task on a web page or
through an API, but the task has not been created.
Access Channel
Web
Possible Causes
No scheduled task is found during AML task maintenance.
Procedure
Modify the AML task and provide information about the associated scheduled task.
5.42 BC52064
Description
The task status has changed.
Scenario
An SP or organization operator suspends, cancels, or resumes an anti money laundering
(AML) scheduled task on a web page or through an API.
Access Channel
Web
Possible Causes
The task status has changed.
Procedure
Refresh the current page.

Copyright © Huawei
Mobile Money
5.43 BC52065
Description
No schedule configuration is found for the bank account.
Scenario
An SP or organization operator initiates an import or export operation for reconciliation on a
web page, but the import or export task has not been configured.
Access Channel
Web
Possible Causes
No schedule configuration is found for the bank account.
Procedure
Configure a schedule for the bank account in the My Functions > Finance > Reconciliation
Management > Reconciliation Configuration menu path.
5.44 BC52067
Description
The short code and reference number must be different.
Scenario
An SP or organization operator creates an organization to customer (O2C) link bulk task plan
on a web page.
Access Channel
Web
Possible Causes
The short code and reference number are the same, and the O2C link instance cannot be
created.
Procedure
Verify that the short code and reference number are different in the uploaded O2C link file.

Copyright © Huawei
Mobile Money
5.45 BC52068
Description
The short code scenario in the xml file is incorrect.
Scenario
Access Channel
Web
Possible Causes
The short code scenario in the xml file is incorrect.
Procedure
Verify the short code field in the O2C link file. The short code field is mandatory for an SP
operator but must be left empty for an organization operator.
5.46 BC52069
Description
Operation failed.
Scenario
The bulk file uploaded by an SP or organization operator to create a bulk task plan on a web
page fails to be saved into the database.
Access Channel
Web
Possible Causes
A database exception has occurred.
Procedure
Send bulk center logs in the /log/debug/bc_debug.log to a Huawei engineer for fault
diagnosis.

Copyright © Huawei
Mobile Money
5.47 BC52070
Description
The name of the uploaded file is too long.
Scenario
An SP or organization operator uploads a bulk file to create a bulk task plan on a web page.
Access Channel
Web
Possible Causes
The file name length must not exceed 64 bytes.
Procedure
Modify the file name and verify that it does not exceed 64 bytes.
5.48 BC52071
Description
Failed to connect to the specified URL.
Scenario
An SP or organization operator initiates a CRL system task on a web page or using a
scheduled task.
Access Channel
Web
Possible Causes
Network connection failed or the specified URL must be accessed through a proxy.
Procedure
1. Access another website to verify whether the network connection is available. If yes, go
to step 2.
2. Ask a system maintenance engineer to verify whether URLs configured in the
bc.config.properties file is reachable. If yes, go to step 3.
3. In the menu bar of the Internet explorer, Choose Tools > Internet Options >
Connection > LAN Settings to verify whether the proxy function is enabled. If yes, add
the address and port of the proxy to the bc.config.properties file.

Copyright © Huawei
Mobile Money
5.49 BC52072
Description
Failed to download the bulk template file from the BCS for the {0} task type.
{0}: indicates the type name of a bulk file.
Scenario
Click to download a bulk file template from the web portal.
Access Channel
Web
Possible Causes
The BCS returns an error message indicating that the template file for the {0} task type is
empty.
Procedure
Verify the /log/debug/*_debug.log file of the BCS with the help of a Huawei engineer to
obtain the failure cause and correct the problem.
5.50 BC52073
Description
Failed to check the cyclic redundancy code (CRC) of the bulk file.
Scenario
Verify the integrity of the bulk file when a bulk task is created.
Access Channel
Web
Possible Causes
The bulk file was broken.
Procedure
Upload the file again please.

Copyright © Huawei
Mobile Money
5.51 BC52074
Description
Failed to create the {0} bulk task.
{0}: indicates the type name of a bulk task.
Scenario
Failed to schedule and execute a bulk task.
Access Channel
Web, API
Possible Causes
Failed to create the {0} bulk task.
Procedure
/log/debug/*_debug.log file on the BTS NE under the help of a Huawei engineer.
5.52 BC52075
Description
The bulk task to be approved is rejected by the approver. The bulk task is failed.
Scenario
A bulk task to be approved is rejected by the approver after the workflow approval feature is
enabled.
Access Channel
Web, API
Possible Causes
The bulk task to be approved is rejected by the approver.
Procedure
If necessary, create another bulk task plan.

Copyright © Huawei
Mobile Money
5.53 BC52076
Description
The file name cannot contain the slash character (/).
Scenario
When a bulk task is initiated through an API, the name of the bulk file is invalid.
Access Channel
API
Possible Causes
The name of the API request file is invalid.
Procedure
Modify the name of the API request file and verify that the name does not contain any slash
character (/).
5.54 BC52077
Description
The {0} file does not exist and cannot be downloaded.
The {0} variable indicates the file name.
Scenario
When the file is downloaded from the remote SFTP server, the file does not exist.
Access Channel
Web
Possible Causes
The file to be downloaded does not exist in the remote server.
Procedure
Verify that the file path is correct.

Copyright © Huawei
Mobile Money
5.55 BC52078
Description
The path length generated for the bulk file exceeds {0}.
The {0} variable indicates the length of the database field used to store the file path.
Scenario
When a bulk task is created, the length of the file path that is generated after a bulk file is
uploaded exceeds the upper length limit.
Access Channel
Web
Possible Causes
The length of the file path generated for the bulk file exceeds length limit of {0}.
Procedure
Configure the path of SFTP bulk files:
1. Log in to the SP portal as the SP operator.
3. Shorten the length of Bulk Root Path in SFTP Parameters.
5.56 BC52079
Description
TPS is set to 0, and there is no available time slot to be assigned.
Scenario
An SP or organization operator initiates a bulk task on the portal.
Access Channel
Web
Possible Causes
All TPS fields are set to 0.

Copyright © Huawei
Mobile Money
Procedure
Configure at least one time slot whose TPS is greater than 0.
5.57 BC52080
Description
Trial calculation failed for the transaction amount of a bulk task, resulting in a bulk task
failure.
Scenario
When an SP or organization operator initiates a bulk task on a web page, the trial calculation
failed for the transaction amount of a bulk task, resulting in a bulk task failure.
Access Channel
Web
Possible Causes
Trial calculation failed for the transaction amount of a bulk task.
Procedure
Verify that identity's data involved in the bulk task meet the bulk operation requirements. For
example, verify whether their balances are sufficient.
5.58 BC52081
Description
Bulk data fails to be processed.
Scenario
Bulk data is sent more than once when a bulk task is executed.
Access Channel
Web
Possible Causes
Bulk data sent by the BTS to service NE {0} has already been sent and is being processed.
{0}: indicates the name of an NE.

Copyright © Huawei
Mobile Money
Procedure
The system cannot determine whether the thread that is processing the bulk data is in a normal
state, and updates the data status to failure. Whether data is successfully processed needs to be
manually viewed.
5.59 BC52082
Description
The {2} field in line {0} and line {1} are set to the same value.
The {0} and {1} variables indicate the line number.

The {2} variable indicates a data field, such as MSISDN.
Scenario
An uploaded bulk file contains duplicate records when a bulk task is created.
Access Channel
Web
Possible Causes
In the bulk file, multiple records have the same field value that must be unique.
Procedure
Delete duplicate records and upload the bulk file again.
5.60 BC52083
Description
The system cannot find a task type for the uploaded bulk file.
Scenario
Upload a bulk file to create a bulk task.
Access Channel
Web
Possible Causes
No task type is selected when a non-XML bulk file is uploaded.

Copyright © Huawei
Mobile Money
Procedure
Initiate a bulk task using a non-XML bulk file on the non-XML bulk file page.
5.61 BC52084
Description
The system cannot find the task type specified in the uploaded bulk file.
Scenario
Upload a bulk file to create a bulk task.
Access Channel
Web
Possible Causes
The bulk task type specified by the root element of the uploaded XML bulk file does not exist
in the system.
Procedure
Upload a bulk file supported by the system. Verify that the format of the uploaded bulk file is
consistent with the template in the system.
5.62 BC52085
Description
Failed to authenticate the initiator information and failed to initiate a bulk task through the
API.
Scenario
When a bulk task is initiated through the API, information of the initiator fails to be
authenticated.
Access Channel
API
Possible Causes
Failed to authenticate the initiator information.

Copyright © Huawei
Mobile Money
Procedure
Verify that the initiator information is correct.
5.63 BC52086
Description
The length of the record in line {0} has exceeded the upper limit {1} configured for the
database field.
{0}: indicates the line number of a record.

{1}: indicates the maximum length of a database field used to store a record in a bulk task file.
Scenario
When a bulk task is initiated, the length of a record exceeds the upper limit.
Access Channel
Web, API
Possible Causes
The length of the record in line {0} has exceeded the upper limit {1} configured for the
database field.
Procedure
Modify the content of the record and ensure that the length does not exceed the upper limit
{1}.
5.64 BC52087
Description
Failed to query bulk tasks because the system database or the BCS is abnormal.
Scenario
When bulk tasks are queried, the system database or the BCS is abnormal.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The system database or the BCS is abnormal.
Procedure
Verify whether the BCS is started. If no, start the BCS. If yes, locate the error cause and
perform troubleshooting by referring to the /log/debug/*_debug.log file of the SWA under the
help of a Huawei engineer.
5.65 BC52088
Description
When a bulk task is initiated through the API, the system fails to decrypt a bulk file from a
third-party system or encrypt a bulk task execution result file.
Scenario
When a bulk task is initiated through the API, the system fails to decrypt a bulk file from a
third-party system or encrypt a bulk task execution result file.
Access Channel
API
Possible Causes
Failed to decrypt a bulk file from a third-party system or encrypt a bulk task execution result
file.
Procedure
1. Choose My functions > Operational Configuration > File Encryption Configuration
and verify that the file encryption configurations are correct.
2. If the configurations are correct, collect the /log/debug/bts_debug.log file in the BTS
and send it to a Huawei engineer for fault locating.
5.66 BC52089
Description
The approval task has expired. The bulk task is failed.
Scenario
An approval task has expired after the workflow approval feature is enabled and the bulk task
is initiated.

Copyright © Huawei
Mobile Money
Access Channel
Web, API
Possible Causes
The approval task has expired.
Procedure
Create another bulk task plan.
5.67 BC52090
Description
Data verification fails during bulk-task creation.
Scenario
Data verification fails during bulk-task creation.
Access Channel
API, Web
Possible Causes
The number of pieces of bulk data contained in a single file or the number of bulk tasks of the
current type that can be created by the organization on the current day exceeds the specified
upper limit.
Procedure
The maximum number of pieces of bulk data contained in a single file is {0}. The maximum
number of bulk tasks of the current type that can be created by an organization on the current
day is {1}. If the number of pieces of bulk data is greater than {0}, reduce the number and re-
create the bulk task. If the number of bulk tasks of the current type is greater than {1}, create
the bulk task on the next day.
{0} indicates the maximum number of pieces of bulk data contained in a single file.
{1} indicates the maximum number of bulk tasks of the current type that can be created by an
organization on the current day.

Copyright © Huawei
Mobile Money
5.68 BC52091
Description
An execution record already exists in the current data. The task cannot be executed again.
Scenario
When a bulk task is executed, an execution record already exists in the current data.
Access Channel
Web, API
Possible Causes
An execution record already exists in the current data.
Procedure
An execution record already exists in the current data. The task cannot be executed again. The
current execution record must be manually checked to see whether the execution is
successful.
5.69 BC52092
Description
An initiator in {0} state cannot initiate a bulk task. Only initiators in active state can initiate a
bulk task.
{0} indicates initiator state.
Scenario
This error is reported when an operator in suspended state initiates a bulk task.
Access Channel
API
Possible Causes
The initiator is not in active state.
Procedure
Use an initiator in active state to initiate a bulk task.

Copyright © Huawei
Mobile Money
5.70 BC52093
Description
The currency parameter is incorrect in the batch request.
Scenario
This error is reported when a bulk task is initiated through an API, the request parameter is
incorrect.
Access Channel
API
Possible Causes
The currency parameter is incorrect in the batch request.
Procedure
Ensure that the currency parameter is correct in the batch request.
5.71 BC52094
Description
The bulk file size exceeds the maximum.
Scenario
This error is reported when a bulk operation is initiated but the bulk file size exceeds the
maximum.
Access Channel
API, Web(Bulk)
Possible Causes
Procedure
Verify that the bulk file size does not exceed the maximum.

Copyright © Huawei
Mobile Money
5.72 BC52095
Description
The number of records in the bulk file exceeds the maximum.
Scenario
This error is reported when a bulk operation is initiated but the number of records in the bulk
file exceeds the maximum.
Access Channel
API, Web(Bulk)
Possible Causes
The number of records in the bulk file exceeds the maximum.
Procedure
Verify that the number of records in the bulk file does not exceed the maximum.
5.73 BC52096
Description
The bulk file validator of the task type {0} cannot be found. Verification cannot be initiated.
{0} indicates a task type.
Scenario
This error is reported if the bulk file validator of the task type cannot be found during bulk
files verification.
Access Channel
Web(Bulk)
Possible Causes
The bulk file validator of the task type {0} cannot be found.
Procedure
Contact Huawei engineers to configure a correct validator for the task type.

Copyright © Huawei
Mobile Money
5.74 BC52097
Description
The request convertor of the task type {0} cannot be found. The bulk task fails to be executed.
{0} indicates a task type.
Scenario
This error is reported if the request convertor of the specified task type cannot be found
during bulk task execution.
Access Channel
Web(Bulk)
Possible Causes
The request convertor of the task type {0} cannot be found.
Procedure
Contact Huawei engineers to configure a correct convertor for the task type.
5.75 BC60001
Description
Scenario
This error is reported if the content of the bulk file is in an incorrect format.
Access Channel
Web(Bulk)
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
5.76 BC60003
Description
In {0}, the value of {1} must not be shorter than {2}.

{2}: indicates the minimum length of a parameter.
Scenario
This error is reported if the field value is shorter than the minimum length during bulk files
verification.
Access Channel
Web(Bulk)
Possible Causes
The field value is shorter than the minimum length.
Procedure
5.77 BC60004
Description
In {0}, the value of {1} must not be longer than {2}.

{2}: indicates the maximum length of a parameter.
Scenario
This error is reported if the field value is longer than the maximum length during bulk files
verification.
Access Channel
Web(Bulk)

Copyright © Huawei
Mobile Money
Possible Causes
The field value is longer than the maximum length.
Procedure
5.78 BC60005
Description
{0} variable indicates the field name in bulk files.
Scenario
This error is reported if the field is empty during bulk files verification.
Access Channel
Web(Bulk)
Possible Causes
Procedure
5.79 BC60006
Description
The {0} field indicates the name of a bulk field in the bulk file.
Scenario
This error is reported if the parameter is not a numeral during bulk files verification.
Access Channel
Web(Bulk)

Copyright © Huawei
Mobile Money
Possible Causes
Procedure
5.80 BC60007
Description
In the {0}, the value of {1} must be a long integer.

Scenario
This error is reported if the value is not a long integer during bulk files verification.
Access Channel
Web(Bulk)
Possible Causes
 The value exceeds the value range of a long integer.
Procedure
5.81 BC60008
Description
In {0}, the value of {1} must not be less than {2}.

{2}: indicates the minimum value of a parameter.

Copyright © Huawei
Mobile Money
Scenario
This error is reported if the value of the parameter is less than the minimum value during bulk
files verification.
Access Channel
Web(Bulk)
Possible Causes
In the {0} parameter, the value of the {1} parameter is less than the value of {2}.
Procedure
5.82 BC60009
Description
In {0}, the value of {1} must not be greater than {2}.

{2}: indicates the maximum value of a parameter.
Scenario
This error is reported if the value of the parameter is greater than the maximum value during
bulk files verification.
Access Channel
Web(Bulk)
Possible Causes
In the {0} parameter, the value of the {1} parameter is greater than the value of {2}.
Procedure

Copyright © Huawei
Mobile Money
5.83 BC60010
Description
The date format is incorrect.
Scenario
This error is reported if the date format is incorrect during bulk files verification.
Access Channel
Web(Bulk)
Possible Causes
 The date length is incorrect.
 The date entered is not a numeral.
Procedure
Verify that the date is correct. Enter the date in the correct format.
5.84 BC60011
Description
In {0}, the value must be set to {1}.
{0}: indicates the name of a function parameter.

{1}: indicates the value range of a parameter.
Scenario
This error is reported if the parameter value is incorrect during bulk files verification.
Access Channel
Web(Bulk)
Possible Causes
Procedure
Set the {0} parameter to {1}.

Copyright © Huawei
Mobile Money
5.85 BC60012
Description
{0}: indicates root note.
Scenario
This error is reported if the file content lacks root node during bulk files verification.
Access Channel
Web(Bulk)
Possible Causes
Procedure
5.86 BC60013
Description
{0}: node ID in an XML file.
Scenario
This error is reported if the content under the node is empty during bulk files verification.
Access Channel
Web(Bulk)
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
5.87 BC60014
Description
Scenario
This error is reported if the number of fields in the record is incorrect during bulk files
verification.
Access Channel
Web(Bulk)
Possible Causes
Procedure
Upload an effective bulk file.
5.88 BC60015
Description
Scenario
This error is reported if there are duplicate fields during bulk files verification.
Access Channel
Web(Bulk)
Possible Causes
There are more than one {0} fields.
{0}: indicates field name in bulk files.
Procedure
Delete the duplicate fields.

Copyright © Huawei
Mobile Money
5.89 BC60016
Description
System error.
Scenario
This error is reported if system error occurs during bulk files verification.
Access Channel
Web(Bulk)
Possible Causes
System error: {0}.
{0}: indicates a program exception message.
Procedure
5.90 BC60017
Description
Scenario
This error is reported if the content of the bulk file is incorrect during bulk files verification.
Access Channel
Web(Bulk)
Possible Causes
Procedure
Verify that the content meets the format requirement of the template.

Copyright © Huawei
Mobile Money
5.91 BC60018
Description
Scenario
This error is reported if the content of the bulk file is in an incorrect format during bulk files
verification.
Access Channel
Web(Bulk)
Possible Causes
Procedure
5.92 BC61000
Description
The denomination of the current product ID {0} is incorrectly configured and fails to be
verified.
{0} indicates a product ID.
Scenario
This error is reported if the denomination of the current product ID is incorrectly configured
during bulk files verification.
Access Channel
Web(Bulk)
Possible Causes
The denomination of the current product ID {0} is incorrectly configured.

Copyright © Huawei
Mobile Money
Procedure
Enter a correct product ID.
5.93 CS50000
Description
One uncompleted configuration deployment task already exists in the Mobile Money system.
The new configuration deployment task is rejected.
Scenario
One uncompleted configuration deployment task already exists in the Mobile Money system
when the repository portal initiates a configuration deployment task.
Access Channel
Web
Possible Causes
One uncompleted configuration deployment task already exists in the Mobile Money system.
Procedure
Reinitiate the new configuration deployment task when the uncompleted configuration
deployment task is complete.
5.94 CS50001
Description
Deployment files do not exist.
Scenario
Deployment files in a configuration deployment task initiated by the repository portal do not
exist.
Access Channel
Web
Possible Causes
Deployment files do not exist.

Copyright © Huawei
Mobile Money
Procedure
Upload deployment files.
5.95 CS50002
Description
The sequence number information of the configuration deployment task does not exist.
Scenario
The sequence number information of a configuration deployment task executed by the Mobile
Money system does not exist.
Access Channel
Web
Possible Causes
The sequence number information of the configuration deployment task does not exist.
Procedure
Initiate a new configuration deployment task.
5.96 CS50004
Description
Data files in the configuration deployment task are damaged. Executing the configuration
deployment task fails.
Scenario
Data files in a configuration deployment task executed by the Mobile Money system are
damaged.
Access Channel
Web
Possible Causes
Data files in the configuration deployment task are damaged.

Copyright © Huawei
Mobile Money
Procedure
5.97 CS50005
Description
The number of data tables in the deployment files is inconsistent with that of tables deployed
in the database. Executing the configuration deployment task fails.
Scenario
The number of data tables in the deployment files of a configuration deployment task
executed by the Mobile Money system is inconsistent with that of tables deployed in the
database.
Access Channel
Web
Possible Causes
The number of data tables in the deployment files is inconsistent with that of tables deployed
in the database.
Procedure
Modify the deployment files and initiate a new configuration deployment task.
5.98 CS50006
Description
The current data set has been deployed in the Mobile Money system. Deploying the current
data set fails.
Scenario
The data set in a configuration deployment task executed by the Mobile Money system has
been deployed in the Mobile Money system.
Access Channel
Web
Possible Causes
The current data set has been deployed in the Mobile Money system.

Copyright © Huawei
Mobile Money
Procedure
5.99 CS50007
Description
The structure of the {0} data table in the configuration deployment task is inconsistent with
that of tables in the database. Executing the configuration deployment task fails.
{0} indicates a data table name.
Scenario
The structure of a data table in a configuration deployment task executed by the Mobile
Money system is inconsistent with that of tables in the database.
Access Channel
Web
Possible Causes
The structure of the {0} data table in the configuration deployment task is inconsistent with
that of tables in the database.
Procedure
5.100 CS50008
Description
The number of pieces of updated deployment data exceeds {0}. Executing the configuration
{0} indicates the maximum number of pieces of data that can be deployed in the Mobile Money system.
Scenario
The number of pieces of updated deployment data in a configuration deployment task
executed by the Mobile Money system exceeds the maximum number of pieces of data that
can be deployed in the Mobile Money system.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The number of pieces of updated deployment data exceeds {0}.
Procedure
5.101 CS50009
Description
The deployment file size exceeds {0} megabyte (MB). Executing the configuration
{0} indicates the maximum file size allowed in the Mobile Money system.
Scenario
The size of a deployment file in a configuration deployment task executed by the Mobile
Money system exceeds the maximum file size allowed in the Mobile Money system.
Access Channel
Web
Possible Causes
The deployment file size exceeds {0} MB.
Procedure
5.102 CS50010
Description
Verifying the parameters of the Secure Hypertext Transfer Protocol (HTTPS) request initiated
by the repository portal fails. The Mobile Money system rejects the HTTPS request.

Copyright © Huawei
Mobile Money
Scenario
The Mobile Money system fails to verify the parameters of an HTTPS request initiated by the
repository portal.
Access Channel
Web
Possible Causes
Verifying the parameters of the HTTPS request initiated by the repository portal fails.
Procedure
Verify that the request parameters are correct.
5.103 CS50011
Description
Authenticating the HTTPS request initiated by the repository portal fails. The Mobile Money
system rejects the HTTPS request.
Scenario
The Mobile Money system fails to authenticate an HTTPS request initiated by the repository
portal.
Access Channel
Web
Possible Causes
Authenticating the HTTPS request initiated by the repository portal fails.
Procedure
Verify that the authentication information is correct.
5.104 CS50012
Description
The repository portal frequently sends HTTPS requests to the Mobile Money system, and the
Mobile Money system rejects the requests.

Copyright © Huawei
Mobile Money
Scenario
The repository portal frequently sends HTTPS requests to the Mobile Money system.
Access Channel
Web
Possible Causes
The repository portal frequently sends HTTPS requests to the Mobile Money system, and the
Mobile Money system rejects the requests.
Procedure
Enable the repository portal to send requests later.
5.105 BTS00002
Description
The UID format fails to be verified. The UID must be an 8-bit string of digits and letters.
Scenario
This error is reported if the uploaded file fails to be verified during batch import of NFC tag
resources.
Access Channel
Web
Possible Causes
The UID format is incorrect.
Procedure
Modify the UID and ensure that the UID is in correct format.
5.106 BTS00003
Description
The customer does not exist, is not registered, or is not in Active state.

Copyright © Huawei
Mobile Money
Scenario
This error is reported when coupons are issued in batches but the customer in the uploaded
template is incorrect.
Access Channel
POS
Possible Causes
The entered customer is not registered or is not in Active state.
Procedure
Enter a registered customer in Active state.
5.107 BTS00004
Description
The entered number of coupons is incorrect.
Scenario
This error is reported when coupons are issued in batches but the number of coupons in the
uploaded template is incorrect.
Access Channel
POS
Possible Causes
The entered number of coupons is incorrect.
Procedure
Enter an integer number of coupons.
5.108 BTS00005
Description
The entered validity period type in the bulk template is incorrect.

Copyright © Huawei
Mobile Money
Scenario
This error is reported when coupons are issued in batches but the validity period type in the
Access Channel
POS
Possible Causes
The entered validity period is incorrect.
Procedure
Ensure that the entered validity period is 0 (absolute validity period) or 1 (relative validity
period).
5.109 BTS00006
Description
The entered validity period in the bulk template is incorrect.
Scenario
This error is reported when coupons are issued in batches but the validity period in the
Access Channel
POS
Possible Causes
The entered validity period is incorrect.
Procedure
Ensure that the entered date is correct. If the validity period type is absolute validity period,
the entered date must be later than the current day and the end date must be later than the start
date. If the validity period type is relative validity period, the value must be greater than 0.
5.110 BTS00007
Description
The Excel file fails to be converted because the XML structure or mapping relationship is not
configured.

Copyright © Huawei
Mobile Money
Scenario
The bulk task supports the Excel format and an error is reported when a file is uploaded on
the My Functions > Bulk > Create Bulk Task Plan page.
Access Channel
Web, API
Possible Causes
When an Excel bulk file is used to initiate the bulk task, the XML template is not configured
or the template mapping to the Excel file is not configured.
Procedure
Configure the XML structure and Excel mapping relationship and then initiate the bulk task.
5.111 BTS00008
Description
The Excel file fails to be converted.
Scenario
Access Channel
Web, API
Possible Causes
The basic name of the Excel bulk file is not on the SFTP server.
Procedure
Upload the bulk file again.
5.112 BTS00009
Description
The Excel template or uploaded Excel bulk file does not contain the column name and fails to
be converted.

Copyright © Huawei
Mobile Money
Scenario
Access Channel
Web, API
Possible Causes
The Excel bulk file (template or uploaded bulk file) does not contain the column name.
Procedure
Upload the bulk file again.
5.113 BTS00010
Description
The file fails to be converted because the column name in the Excel template is inconsistent
with that in the uploaded Excel bulk file.
Scenario
Access Channel
Web, API
Possible Causes
The column name in the Excel bulk file is inconsistent with that in the provided Excel
template.
Procedure
5.114 BTS00011
Description

Copyright © Huawei
Mobile Money
Scenario
Access Channel
Web, API
Possible Causes
The path to the Excel template file is not configured.
Procedure
Choose My Functions > Operational Configuration > System Parameter > SFTP
Parameters and configure the bulk template path.
5.115 BTS00012
Description
The duration and durationUnit parameters are empty when a customer or organization adds a
status tag.
Scenario
This error is reported when a customer or organization fails to add a status tag because
autoRemove is set to 1 and duration and durationUnit are empty.
Access Channel
Web
Possible Causes
The duration and durationUnit parameters cannot be empty.
Procedure
Set duration and durationUnit.
5.116 BTS00013
Description
The stateTag field is empty or is in incorrect format.

Copyright © Huawei
Mobile Money
Scenario
This error is reported when a customer or organization adds a status tag but the status tag
name is empty or does not exist.
Access Channel
Web
Possible Causes
The stateTag field is empty or is in incorrect format.
Procedure
Ensure that stateTag is not empty and is in correct format.
5.117 BTS00014
Description
The status tag does not exist.
Scenario
This error is reported when a customer or organization removes a status tag but the status tag
does not exist.
Access Channel
Web
Possible Causes
The status tag does not exist.
Procedure
Ensure that the status tag to be deleted exists.
5.118 BTS00015
Description
The tag exists. However, the matching MSISDN or organization short code is incorrect and
the data uniqueness cannot be determined.

Copyright © Huawei
Mobile Money
Scenario
This error is reported when a customer or organization removes a status tag but the status tag
does not have the matching organization or customer.
Access Channel
Web
Possible Causes
The tag exists. However, the matching MSISDN or organization short code is incorrect and
the data uniqueness cannot be determined.
Procedure
Ensure that the status tag exist and check the MSISDN and organization short code.
5.119 BTS00016
Description
The TerritoryId, LACId, and CellId fields must be set to a non-negative integer.
Scenario
This error is reported if the TerritoryId, LACId, or CellId field is not set to a non-negative
integer in the LACCI batch upload task.
Access Channel
POS
Possible Causes
The TerritoryId, LACId, or CellId field is not set to a non-negative integer.
Procedure
Modify related parameters and submit the task again.
5.120 BTS00017
Description
The GIS information in each island must contain at least 3 geographical locations.

Copyright © Huawei
Mobile Money
Scenario
This error is reported if the number of region points entered for island in the GIS batch upload
task is less than 3.
Access Channel
POS
Possible Causes
The number of locations in the GIS information about the island is less than 3.
Procedure
Modify the GIS information and submit the task again.
5.121 BTS00018
Description
The entered longitude and latitude should contain no more than 6 decimal places.
Scenario
This error is reported if the longitude and latitude entered in the Bulk GIS contain more than 6
decimal places.
Access Channel
POS
Possible Causes
The entered longitude and latitude contain more than 6 decimal places.
Procedure
Change the accuracy of the longitude and latitude.
5.122 BTS00019
Description
The entered longitude and latitude are not in the valid range.

Copyright © Huawei
Mobile Money
Scenario
This error is reported if the longitude and latitude entered in the Bulk GIS are not in the valid
range.
Access Channel
POS
Possible Causes
The entered longitude and latitude are not in the valid range.
Procedure
Ensure that the longitude is in the range from -180 degree to +180 degree and the latitude is in
the range from -90 degree to +90 degree.
5.123 BTS00020
Description
The entered TerritoryID can be composed of only digits.
Scenario
This error is reported if the TerritoryID entered during bulk lacci, boundary, or gis task
execution is not composed of digits.
Access Channel
POS
Possible Causes
The entered TerritoryID can be composed of only digits.
Procedure
Set the value to a string containing only digits.
5.124 BTS00021
Description
The value of the Amount field is not a valid amount or is a negative number.

Copyright © Huawei
Mobile Money
Scenario
This error is reported when the bulk file fails to be uploaded during Bulk Transaction Reversal
execution because the amount format is incorrect.
Access Channel
POS
Possible Causes
The value of the Amount field is incorrect.
Procedure
Set Amount to a non-negative number.
5.125 BTS00022
Description
When the identity bank account {0} is operated, the {1} attribute cannot be empty.
 {0}: indicates the add, update, or delete operation.

 {1}: indicates the specific parameter.
Scenario
This error is reported when the IdentityBankAccount Bulk file is uploaded but the parameters
fail to be parsed.
Access Channel
POS
Possible Causes
Procedure
Ensure that the {1} attribute is not empty when the identity bank account {0} is operated.
5.126 BTS00023
Description

Copyright © Huawei
Mobile Money
 {0}: indicates the add, update, or delete operation.

 {1}: indicates the specific parameter.
Scenario
This error is reported when the IdentityBankAccount Bulk file is uploaded but the parameters
are parsed incompletely.
Access Channel
POS
Possible Causes
Procedure
Ensure that the {1} attribute is not empty when the identity bank account {0} is operated.
5.127 BTS00024
Description
Operations other than add, delete, update are invalid operations.
Scenario
This error is reported when the IdentityBankAccount Bulk file is uploaded but the operation
parameters fail to be parsed.
Access Channel
POS
Possible Causes
The operation is invalid.
Procedure
Ensure that the operation is valid.

Copyright © Huawei
Mobile Money
Error Codes Reference 5 DIP Error Codes
6 DIP Error Codes
About This Chapter

6.1 DE10001
6.2 DE10002
6.3 DE10003
6.4 DE10004
6.5 DE10005
6.6 DE10006
6.7 DE10007
6.8 DE10008
6.9 DE10009
6.10 DE10010
6.11 DE10011
6.12 DE10012
6.13 DE10013
6.14 DE10014
6.15 DE10015
6.16 DE10016
6.17 DE10017
6.18 DE10018
6.19 DE10019
6.20 DE10021

Copyright © Huawei
Mobile Money
6.21 DE10022
DE10001
Description
The same manual data extraction task is in progress.
Scenario
When an SP operator or organization operator executes a MNO payment Air Time or SMS
data extraction task on the portal web page, the task is already initiated for the same
organization. As a result, executing the task fails.
Access Channel
Web
Possible Causes
The manual data extraction task is already initiated for the same organization.
Procedure
Execute the task after the ongoing task is completed.
6.1 DE10002
Description
The operation is illegal.
Scenario
When an SP operator or organization operator executes an AML data extraction task on the
portal web page, the page has timed out.
Access Channel
Web
Possible Causes
The operation does not apply to the current task status because the page has timeout.
Procedure
Refresh the page and perform the operation again.

Copyright © Huawei
Mobile Money
6.2 DE10003
Description
The BDI platform failed to execute a task. {0}
Scenario
When an SP operator or organization operator executes a MNO payment, bill payment, or
EVO data extraction task on the portal web page, the BDI platform fails to execute the task.
Access Channel
Web
Possible Causes
N/A
Procedure
N/A
6.3 DE10004
Description
Only one EVO data extraction task can be executed at a time.
Scenario
When an SP operator or organization operator executes an EVO data extraction task on the
portal web page, an EVO data extraction task has been started at the background.
Access Channel
Web
Possible Causes
The current task cannot be processed because an EVO data extraction task is being processed
at the background.
Procedure
Execute the task after the ongoing task is completed.

Copyright © Huawei
Mobile Money
6.4 DE10005
Description
No version of the GL mapping is found.
Scenario
When an SP operator or organization operator executes a daily preprocessing task on the
portal web page, no released GL mapping version is found.
Access Channel
Web
Possible Causes
The GL mapping has no released version.
Procedure
1. Log in to the SP portal.
2. Choose My Functions > Finance > EVO Extraction > GL Mapping.
3. Verify that the GL mapping has at least one effective version (in the Released state).
If there is no released version, add a version and change its status to Released in the Operation
menu.
6.5 DE10006
Description
The data is already aggregated.
Scenario
portal web page, all data in the given duration is already aggregated.
Access Channel
Web
Possible Causes
All data in the given duration is already aggregated.
Procedure
Do not aggregate data repetitively.

Copyright © Huawei
Mobile Money
6.6 DE10007
Description
Failed to extract the transaction data on certain dates because the data records are not ready in
the report database.
Scenario
portal web page, data in the report database is not ready.
Access Channel
Web
Possible Causes
The transaction data is not ready in the report database.
Procedure
Check whether the data in the report database is ready. If the data is not recorded, re-extract
the data on the report client. If the problem persists, ask the system administrator for help.
6.7 DE10008
Description
No unique ID is found.
Scenario
portal web page, the GL mapping has no released version, or no unique ID is obtained for the
specified date.
Access Channel
Web
Possible Causes
The GL mapping has no released version, or no unique ID is obtained for the specified date.
Procedure
2. Choose My Functions > Finance > EVO Extraction > GL Mapping.

Copyright © Huawei
Mobile Money
3. Verify that the GL mapping has at least one effective version on the specified date (in the
Released state). If there is no effective version, add a version and release it.
6.8 DE10009
Description
The GL mapping configuration is incorrect, or the service data is incorrect, resulting in
unbalances between debit and credit amounts in the line entry.
Scenario
portal web page, the sum of all credit amounts does not match with the sum of all debit
amounts in the line entry.
Access Channel
Web
Possible Causes
Sum of all credit amounts does not match with the sum of all debit amounts in the line entry.
Procedure
1. Log in to the SP portal and check whether the GL mapping configuration is correct.
− If no, modify the configurations.
− If yes, the cause may be invalid service data or periodical credit-debit unbalances,
and you need to ask the system administrator for help.
2. If the data is valid, execute the daily preprocessing task again.
6.9 DE10010
Description
Failed to obtain the task instance ID.
Scenario
portal web page, the task instance ID cannot be successfully obtained.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
No task instance ID is obtained because an error has occurred in the BDI platform or the DIP
is not started.
Procedure
Ask the system administrator to check whether the BDI platform is working properly and
whether the DIP is started.
6.10 DE10011
Description
Scenario
Scenario 1: During EVO data extraction on the SP portal, no Company Code is configured on
My Functions > Operational Configuration > System Parameter > EVO Extraction, or
no Extract Path is configured on My Functions > Operational Configuration > System
Parameter > SFTP Parameters. Scenario 2: During EVO data extraction on the SP portal,
the BTS does not deliver the Extract Type, End Date, or Extract Mode parameter to the DE, or
the Extract Type, End Date, or Extract Mode parameter delivered by the BTS to the DIP is
invalid.
Access Channel
Web
Possible Causes
Some of the system parameter include CompanyCode, ExtractPath, ExtractType, EndDate
and ExtractMode is not configured.
Procedure
3. Configure parameters in the EVO Extraction and SFTP Parameters submenus.
6.11 DE10012
Description
Daily preprocessing failed.

Copyright © Huawei
Mobile Money
Scenario
On the SP portal, after an EVO daily preprocessing task is created on My Functions >
Operation Support > System Task Plan, data of at least one day in the given duration is not
ready in the T_O_CPS_EVO_ETL_LOG table on the report.
Access Channel
Web
Possible Causes
EVO data extraction failed for certain dates because the daily preprocessing for these dates is
not completed.
Procedure
2. Choose My Functions > Operation Support > System Task Plan > System Task
Plan.
3. Find the daily preprocessing task, manually execute the task, or configure a scheduled
task to execute preprocessing again. EVO data extraction can be performed only after the
preprocessing is complete.
6.12 DE10013
Description
Do not extract data repetitively.
Scenario
During incremental EVO data extraction on the SP portal, all data in the given duration is
already extracted.
Access Channel
Web
Possible Causes
All data in the given duration is already extracted.
Procedure
EVO data in the given duration is already extracted.

Copyright © Huawei
Mobile Money
6.13 DE10014
Description
The SFTP directory does not exist, or the operator does not have the permission to access the
directory.
Scenario
During EVO data extraction on the SP portal, on My Functions > Operational Configuration >
System Parameter > SFTP Parameters > EVO Extraction File Path, no directory is configured,
the operator has no permission to create the directory, or files cannot be uploaded from the
directory.
Access Channel
Web
Possible Causes
No SFTP directory is created, or the SFTP directory is incorrectly configured.
Procedure
1. Log in to the Portal.
Parameters.
3. Check whether the Path of EVO Extract files directory exists, and whether the operator
has the necessary permissions to access the directory. If the directory does not exist,
create it and assign access permissions to the operator.
6.14 DE10015
Description
The EVO daily preprocessing failed.
Scenario
After an EVO daily preprocessing task is created on the SP portal, the BDI platform fails to
execute the task.
Access Channel
Web
Possible Causes
For the detailed cause, see the error message for the preprocessing task instance.

Copyright © Huawei
Mobile Money
Procedure
2. Choose My Functions > Finance > EVO Extraction > EVO Extraction History.
3. Find Daily Preprocess, click Details to view the error message for each preprocessing
task instance, and handle the error based on the error prompt.
6.15 DE10016
Description
EVO data extraction failed.
Scenario
The BDI platform fails to execute an EVO data extraction task on the SP portal.
Access Channel
Web
Possible Causes
For the detailed cause, see the error message for the extraction task instance.
Procedure
2. Choose My Functions > Finance > EVO Extraction > EVO Extraction History.
3. Find EVO Extraction, click Details to view the error message for each preprocessing
task instance, and handle the error based on the error prompt.
6.16 DE10017
Description
The number of bill payment data extractions has reached the daily upper limit.
Scenario
The number of times for which a bill payment data extraction task created on the SP or
organization portal is performed one day exceeds 100.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
Each organization can extract bill payment data for a maximum of 100 times per day.
Procedure
Try again the next day.
6.17 DE10018
Description
The daily preprocessing failed because no or multiple currencies are found in the transaction
record.
Scenario
After an EVO daily preprocessing task is created on the SP portal, the daily preprocessing
fails because no or multiple currencies are found in the transaction record.
Access Channel
Web
Possible Causes
The daily preprocessing failed because no or multiple currencies are found in the transaction
record.
Procedure
Verify whether the currency is correct in the transaction record.
6.18 DE10019
Description
No currency information is found.
Scenario
During execution of an EVO daily preprocessing task, no information about the currency
specified in the transaction record is found on My Functions > Operational Configuration >
Localization > Currency Definition on the SP portal.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
There is no currency definition for certain currencies in Operational Configuration.
Procedure
Definition..
3. Define currency information based on the currency.
6.19 DE10021
Description
Data extraction failed because the organization is not in the Active state.
Scenario
Extract data of an organization not in the Active state on the SP portal.
Access Channel
Web
Possible Causes
The organization is not in the Active state.
Procedure
Activate the organization first.
6.20 DE10022
Description
The task is currently in the {0} state, and cannot be changed to the {1} state.
{0}: indicates the current status of a task.

{1}: indicates an operation that cannot be performed on a task instance. For example, a task instance in
the success state cannot be terminated.
Scenario
When canceling, terminating, or resuming an AML or FSI extraction task instance, the system
reports an error because the task status is not the latest.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The task cannot be changed to the target status.
Procedure
Refresh the page to query for the task status.

Copyright © Huawei
Mobile Money
Error Codes Reference 6 Foundation Error Codes
7 Foundation Error Codes
About This Chapter

7.1 FDN15204
7.2 FDN15205
7.3 FDN15301
7.4 FDN15311
7.5 FDN30000
7.6 FDN30231
7.7 FDN39040
7.8 FDN39041
7.9 FDN39042
7.10 FDN50000
7.11 FDN52061
7.12 FDN60001
7.13 FDN61110
7.14 FDN70000
7.15 FDN70001
7.16 FDN70002
7.17 FDN70003
7.18 FDN70004
7.19 FDN70005
7.20 FDN70006

Copyright © Huawei
Mobile Money
7.21 FDN70007
7.22 FDN70008
7.23 FDN90000
7.24 FDN90001
7.25 FDN90002
7.26 FDN90003
7.27 FDN90004
7.28 FDN90005
7.29 FDN90006
7.30 FDN90007
7.31 FDN90009
7.32 FND90011
7.33 FND90012
7.34 FND90030
7.35 FND90031
7.36 FND90032
7.37 FND90033
7.38 FND90042
7.39 FND90043
7.40 FND90044
7.41 FND90045
7.42 FND90046
7.43 FND89974
7.44 SYS00000
7.45 SYS90006
FDN15204
Description
The KYC field information does not meet the data type requirement.
Scenario
The KYC field information does not meet the data type requirement.

Copyright © Huawei
Mobile Money
Access Channel
System
Possible Causes
N/A
Procedure
N/A
7.1 FDN15205
Description
Scenario
The KYC field information does not meet the data type requirement. The value must be a
positive or negative integer of 1 to 18 digits or 0.
Access Channel
System
Possible Causes
The value of the {0} KYC field is not an integer with 1 - 18 digits.
Procedure
Enter a correct value for the {0} KYC field.
7.2 FDN15301
Description
Failed to find the cache.
Scenario
Cache error. For example, no product ID is obtained from the cache.
Access Channel
System

Copyright © Huawei
Mobile Money
Possible Causes
Failed to load the cache or a cache exception has occurred.
Procedure
N/A
7.3 FDN15311
Description
The format of the date or time is incorrect.
Scenario
Data format conversion error.
Access Channel
System
Possible Causes
The format of the date or time is incorrect.
Procedure
N/A
7.4 FDN30000
Description
Transaction succeeded.
Scenario
Transaction execute successful.
Access Channel
System
Possible Causes
N/A

Copyright © Huawei
Mobile Money
Procedure
N/A
7.5 FDN30231
Description
Scenario
A system parameter is incorrectly configured. A parameter of the Long type is set to a value
containing letters.
Access Channel
System
Possible Causes
Procedure
7.6 FDN39040
Description
Scenario
The default currency is not configured and fails to be obtained during the transaction.
Access Channel
System
Possible Causes

Copyright © Huawei
Mobile Money
Procedure
Definition.
3. Set the Default Currency field.
7.7 FDN39041
Description
Scenario
The default currency is incorrectly configured and fails to be obtained during the transaction.
Access Channel
System
Possible Causes
Procedure
Definition.
3. Verify whether the configured default currency meets the ISO 4127 standard. If no,
manually modify the default currency.
7.8 FDN39042
Description
Scenario
The specified default currency is not configured in the system.
Access Channel
System

Copyright © Huawei
Mobile Money
Possible Causes
Procedure
1. Log in to the SP portal as an administrator.
Definition.
3. Check whether the specified currency code exists.
If not, check whether the specified currency is correct or add new currency.
7.9 FDN50000
Description
Scenario
A system error has occurred when the BTS is running, for example, the database fails to be
accessed.
Access Channel
System
Possible Causes
An unknown system exception has occurred.
Procedure
Collect BTS logs in /log/debug/bts_debug.log and send the logs to a Huawei engineer for
fault locating.
7.10 FDN52061
Description
The task will never be executed.
Scenario
An SP operator or organization operator creates an AML scheduled task on the web.

Copyright © Huawei
Mobile Money
Access Channel
System
Possible Causes
The specified task execution time is invalid.
Procedure
Verify that the execution time is later than the current time.
7.11 FDN60001
Description
No cache is named {0}.
Scenario
The UCC cache is cleared, or cache configurations of other NEs are not synchronized with the
UCC cache configurations.
Access Channel
System
Possible Causes
The cache name specified by the request does not exist.
Procedure
Verify that the cache name {0} specified by the request is correct.
7.12 FDN61110
Description
The current currency is incorrect.
Scenario
No currency is found based on the currency code.
Access Channel
System

Copyright © Huawei
Mobile Money
Possible Causes
The current currency is empty.
Procedure
N/A
7.13 FDN70000
Description
Foundation system error.
Scenario
Foundation system error. Example: object exception.
Access Channel
System
Possible Causes
Foundation system error. Example: object exception
Procedure
Locate and resolve the problem by checking information in /log/debug/*_debug.log under the
7.14 FDN70001
Description
Scenario
The parameter is incorrect, for example, when the system verifies whether a file is correct or
whether a mandatory SQL parameter is empty.
Access Channel
System
Possible Causes

Copyright © Huawei
Mobile Money
Procedure
Locate and resolve the problem by checking information in /log/debug/*_debug.log under the
7.15 FDN70002
Description
DAS error.
Scenario
DAS operation failed, for example, a SQL statement fails to be executed or SQL statements
fail to be executed in bulk.
Access Channel
System
Possible Causes
N/A
Procedure
N/A
7.16 FDN70003
Description
Unknown Foundation error.
Scenario
Unknown foundation error. This is a unified handling scenario for exceptions.
Access Channel
System
Possible Causes
N/A
Procedure
N/A

Copyright © Huawei
Mobile Money
7.17 FDN70004
Description
The Foundation parameter is invalid.
Scenario
The foundation parameter is invalid. When an xml string is converted into an
org.w3c.dom.Document object, a string parameter does not meet the xml specifications.
Access Channel
System
Possible Causes
The parameter value is empty or invalid.
Procedure
Enter a valid parameter value as required and try again.
7.18 FDN70005
Description
Foundation request operation succeeded.
Scenario
A foundation request succeeded. A result object is successfully returned for a general service
execution success.
Access Channel
System
Possible Causes
N/A
Procedure
N/A

Copyright © Huawei
Mobile Money
7.19 FDN70006
Description
The cache loading method is incorrect.
Scenario
Cache load error, for example, the cache loading configuration is incorrect.
Access Channel
System
Possible Causes
The cache loading method is incorrectly configured.
Procedure
N/A
7.20 FDN70007
Description
The cache does not exist.
Scenario
The cache does not exist, for example, no data is obtained from the cache.
Access Channel
System
Possible Causes
Failed to load the cache.
Procedure
N/A

Copyright © Huawei
Mobile Money
7.21 FDN70008
Description
The requested processor is empty.
Scenario
No request handler is obtained for a remote invocation request.
Access Channel
System
Possible Causes
No data source is found.
Procedure
Check the DAS log or startup log to determine the error cause and rectify the fault.
7.22 FDN90000
Description
Failed to execute the database operation.
Scenario
Database exception: The database is disconnected, or a database table does not exist.
Access Channel
System
Possible Causes
A database exception has occurred, for example, the database is stopped, or the system is
disconnected from the database.
Procedure

Copyright © Huawei
Mobile Money
7.23 FDN90001
Description
{0}.
Scenario
RPC communication exception: The invoked NE is not started, an exception occurred in the
startup process and the service is not registered in the registration center, or a network
connection failure has occurred.
Access Channel
System
Possible Causes
RPC communication exception.
Procedure
Change parameters based on the error cause description. If the problem persists, locate the
error cause and perform troubleshooting based on information in the /log/debug/*_debug.log
file under the help of a Huawei engineer.
7.24 FDN90002
Description
Invalid configuration data.
Scenario
A parameter is not configured or incorrectly configured. For example, an input parameter is
set to a value containing more than 2 decimal digits to delete a released data record, but the
required precision is 2 decimal digits.
Access Channel
System
Possible Causes
The initial configuration data is incomplete or invalid.
Procedure

Copyright © Huawei
Mobile Money
7.25 FDN90003
Description
An assertion exception has occurred.
Scenario
A parameter is missing or invalid. For example, a mandatory parameter is set to an empty
value.
Access Channel
System
Possible Causes
Data is missing or invalid.
Procedure
7.26 FDN90004
Description
An encryption or decryption exception has occurred: Exception information: {0}.
Scenario
Access Channel
System
Possible Causes
Procedure
Change the key based on the exception description and try again. If the problem persists,
locate the error cause and perform troubleshooting based on information in the

Copyright © Huawei
Mobile Money
7.27 FDN90005
Description
A parameter value is invalid. Cause: {0}
Scenario
A mandatory parameter is empty. For example, a mandatory parameter of a notification object
is empty.
Access Channel
System
Possible Causes
A parameter value is empty or invalid.
Procedure
Enter a valid parameter value based on the prompt information.
7.28 FDN90006
Description
Operation failed.
Scenario
An exception which is not defined and cannot be processed by the system has occurred.
Access Channel
System
Possible Causes
An unknown error has occurred. The cause may be system resource exhaustion.
Procedure

Copyright © Huawei
Mobile Money
7.29 FDN90007
Description
MOM service error. Cause: {0}
Scenario
An exception occurred when the AG sends a message to the MQ, resulting in a message
sending failure.
Access Channel
System
Possible Causes
MOM service error.
Procedure
N/A
7.30 FDN90009
Description
Service access error.
Scenario
A service access exception may occur due to an MQ exception or when a bulk task or
transaction is executed.
Access Channel
Web, STK, USSD, API
Possible Causes
N/A
Procedure
N/A

Copyright © Huawei
Mobile Money
7.31 FND90011
Description
License verification failed.
Scenario
Various service requests.
Access Channel
Web, STK, USSD, API
Possible Causes
The number of service requests exceeds the maximum specified in the license. The service
request fails.
Procedure
Apply for a higher license.
7.32 FND90012
Description
Failed to encrypt or decrypt a reconciliation statement using PGP.
Scenario
When an SP operator uploads a reconciliation statement to the SFTP server or downloads a
reconciliation statement, the reconciliation statement cannot be encrypted for decrypted using
PGP.
Access Channel
Web
Possible Causes
 The parameter value is incorrect.
 The reconciliation statement is incorrect.
 Failed to decrypt the PGP password.
Procedure
1. Verify that the parameter value is correct.
2. Check whether the file to be encrypted or decrypted is correct.

Copyright © Huawei
Mobile Money
3. Check whether the ciphertext of the PGP encryption password is correct.
7.33 FND90030
Description
The {0} service is unavailable.
{0}: indicates the name of a service, for example, ICService.
Scenario
All services.
Access Channel
Web, STK, USSD, API
Possible Causes
The NE that provides the {0} service is not running properly.
Procedure
Check whether the NE that provides the service is running properly.
7.34 FND90031
Description
The {0} service has timed out.
{0}: indicates the name of a service, for example, ICService.
Scenario
All services.
Access Channel
Web, STK, USSD, API
Possible Causes
The NE that executes the {0} service is busy.

Copyright © Huawei
Mobile Money
Procedure
Check whether the NE that executes the service is running properly.
7.35 FND90032
Description
The passcode file cannot be downloaded because no PIN Mailer key is uploaded.
Scenario
Download a passcode file on the Passcode Download for PIN Mailer page.
Access Channel
Web
Possible Causes
No PIN Mailer key is uploaded.
Procedure
Upload a PIN Mailer key in the My Functions > Operational Configuration > Key
Management > Key Upload Management menu before downloading the passcode file.
7.36 FND90033
Description
An error has occurred when the public key for encryption is imported.
Scenario
Download a passcode file on the Passcode Download for PIN Mailer page.
Access Channel
Web
Possible Causes
The content or format of the uploaded public key is incorrect.
Procedure
1. Verify that the file of the public key is correct.

Copyright © Huawei
Mobile Money
2. Choose My Functions > Operational Configuration > Key Management > Key
Upload Management to upload a correct public key.
7.37 FND90042
Description
An error occurred when modifying or reading configuration parameters.
Scenario
This error is generated when modifying or reading configuration parameters.
Access Channel
Web
Possible Causes
An error occurred when modifying or reading configuration parameters.
Procedure
7.38 FND90043
Description
The input parameter is invalid.
Scenario
This error is reported when the input parameter of the rule ID generation interface is invalid.
Access Channel
Web
Possible Causes
The input parameter is invalid.
Procedure
Ensure that the input parameter is correct.

Copyright © Huawei
Mobile Money
7.39 FND90044
Description
The rule ID definition is abnormal.
Scenario
This error is reported when the rule ID definition is abnormal.
Access Channel
Web
Possible Causes
The rule ID definition is abnormal.
Procedure
Ensure that the rule ID definition is correct.
7.40 FND90045
Description
An error occurs during rule ID generation.
Scenario
This error is reported when an error occurs during rule ID generation.
Access Channel
Web
Possible Causes
An error occurs during rule ID generation.
Procedure
Check the rule ID logs and contact Huawei technical support.

Copyright © Huawei
Mobile Money
7.41 FND90046
Description
The rule IDs have been used up.
Scenario
This error is reported when the rule IDs have been used up.
Access Channel
Web
Possible Causes
The number of generated rule IDs has reached the maximum.
Procedure
Redefine the rule ID or increase the rule ID generation range.
7.42 FND89974
Description
The PIN of the customer has expired.
Scenario
After being created, a customer uses a random PIN. This error is reported when the PIN is
modified but the PIN has expired.
Access Channel
Web,STK,USSD,API,Web(Bulk),Socket,ATM,POS,System,APP,BIO,Third Party Web
Possible Causes
The PIN of the customer has expired.
Procedure
Generate a new PIN for the customer.

Copyright © Huawei
Mobile Money
7.43 SYS00000
Description
Response is successfully returned.
Scenario
The MQ returns a success.
Access Channel
System
Possible Causes
Response is successfully returned.
Procedure
N/A
7.44 SYS90006
Description
Unknown system error.
Scenario
An unknown system error has occurred when a log is generated.
Access Channel
Web
Possible Causes
Unknown system error.
Procedure
Check the /log/debug/*_debug.log file of the SP portal under the help of a Huawei engineer.

Copyright © Huawei
Mobile Money
Error Codes Reference 7 SWA/OWA Error Codes
8 SWA/OWA Error Codes
About This Chapter

8.1 PORTAL90001
8.2 PORTAL90002
8.3 PORTAL90003
8.4 PORTAL90004
8.5 PORTAL90005
8.6 PORTAL90006
8.7 PORTAL90007
8.8 PORTAL90008
8.9 PORTAL90009
8.10 PORTAL90010
8.11 PORTAL90011
8.12 PORTAL90012
8.13 PORTAL90013
8.14 PORTAL90015
8.15 PORTAL90016
8.16 PORTAL90017
8.17 PORTAL90018
8.18 PORTAL90019
8.19 PORTAL90020
8.20 PORTAL90021

Copyright © Huawei
Mobile Money
8.21 PORTAL90022
8.22 PORTAL90023
8.23 PORTAL90024
8.24 PORTAL90025
8.25 PORTAL90026
8.26 PORTAL90027
8.27 PORTAL90028
8.28 PORTAL90029
8.29 PORTAL90030
8.30 PORTAL90031
8.31 PORTAL90032
8.32 PORTAL90033
8.33 PORTAL90034
8.34 PORTAL90035
8.35 PORTAL90036
8.36 PORTAL90037
8.37 PORTAL90038
8.38 PORTAL90039
8.39 PORTAL90040
8.40 PORTAL90041
8.41 PORTAL90042
8.42 PORTAL90043
8.43 PORTAL90044
8.44 PORTAL90045
8.45 PORTAL90046
8.46 PORTAL90047
8.47 PORTAL90048
8.48 PORTAL90049
8.49 PORTAL90050
8.50 PORTAL90051
8.51 PORTAL90052
8.52 PORTAL90053
8.53 PORTAL90054

Copyright © Huawei
Mobile Money
8.54 PORTAL90055
8.55 PORTAL90056
8.56 PORTAL90057
8.57 PORTAL90058
8.58 PORTAL90059
8.59 PORTAL90060
8.60 PORTAL90061
8.61 PORTAL90062
8.62 PORTAL90063
8.63 PORTAL90064
8.64 PORTAL90065
8.65 PORTAL90066
8.66 PORTAL90067
8.67 PORTAL90068
8.68 PORTAL90069
8.69 PORTAL90070
8.70 PORTAL90071
8.71 PORTAL90072
8.72 PORTAL90073
8.73 PORTAL90074
8.74 PORTAL90075
8.75 PORTAL90076
8.76 PORTAL90077
8.77 PORTAL90078
8.78 PORTAL90079
8.79 PORTAL90080
8.80 PORTAL90081
8.81 PORTAL90082
8.82 PORTAL90083
8.83 PORTAL90084
8.84 PORTAL90085
8.85 PORTAL90086
8.86 PORTAL90087

Copyright © Huawei
Mobile Money
8.87 PORTAL90088
8.88 PORTAL90089
8.89 PORTAL90090
8.90 PORTAL90091
8.91 PORTAL90092
8.92 PORTAL90093
8.93 PORTAL90094
8.94 PORTAL90095
8.95 PORTAL90096
8.96 PORTAL90097
8.97 PORTAL90098
8.98 PORTAL90099
8.99 PORTAL90100
8.100 PORTAL90101
8.101 PORTAL90102
8.102 PORTAL90103
8.103 PORTAL90104
8.104 PORTAL90105
8.105 PORTAL90106
8.106 PORTAL90107
8.107 PORTAL90108
8.108 PORTAL90109
8.109 PORTAL90110
8.110 PORTAL90111
8.111 PORTAL90112
8.112 PORTAL90113
8.113 PORTAL90114
8.114 PORTAL90115
8.115 PORTAL90116
8.116 PORTAL90117
8.117 PORTAL90118
8.118 PORTAL90119
8.119 PORTAL90120

Copyright © Huawei
Mobile Money
8.120 PORTAL90121
8.121 PORTAL90122
8.122 PORTAL90123
8.123 PORTAL90124
8.124 PORTAL90125
8.125 PORTAL90126
8.126 PORTAL90127
8.127 PORTAL90128
8.128 PORTAL90129
8.129 PORTAL90130
8.130 PORTAL90131
8.131 PORTAL90132
8.132 PORTAL90133
8.133 PORTAL90134
8.134 PORTAL90135
8.135 PORTAL90136
8.136 PORTAL90137
8.137 PORTAL90138
8.138 PORTAL90139
8.139 PORTAL90140
8.140 PORTAL90141
8.141 PORTAL90142
8.142 PORTAL90143
8.143 PORTAL90144
8.144 PORTAL90145
8.145 PORTAL90146
8.146 PORTAL90147
8.147 PORTAL90148
8.148 PORTAL90149
8.149 PORTAL90150
8.150 PORTAL90151
8.151 PORTAL90152
8.152 PORTAL90153

Copyright © Huawei
Mobile Money
8.153 PORTAL90154
8.154 PORTAL90155
8.155 PORTAL90156
8.156 PORTAL90157
8.157 PORTAL90158
8.158 PORTAL90159
8.159 PORTAL90160
8.160 PORTAL90161
8.161 PORTAL90162
8.162 PORTAL90163
8.163 PORTAL90164
8.164 PORTAL90165
8.165 PORTAL90166
8.166 PORTAL90167
8.167 PORTAL90168
8.168 PORTAL90169
8.169 PORTAL90170
8.170 PORTAL90171
8.171 PORTAL90172
8.172 PORTAL90173
8.173 PORTAL90174
8.174 PORTAL90175
8.175 PORTAL90176
8.176 PORTAL90177
8.177 PORTAL90178
8.178 PORTAL90179
8.179 PORTAL90180
8.180 PORTAL90181
8.181 PORTAL90182
8.182 PORTAL90183
8.183 PORTAL90184
8.184 PORTAL90185
8.185 PORTAL90186

Copyright © Huawei
Mobile Money
8.186 PORTAL90187
8.187 PORTAL90188
8.188 PORTAL90189
8.189 PORTAL90190
8.190 PORTAL90191
8.191 PORTAL90192
8.192 PORTAL90193
8.193 PORTAL90194
8.194 PORTAL90195
8.195 PORTAL90196
8.196 PORTAL90197
8.197 PORTAL90198
8.198 PORTAL90199
8.199 PORTAL90200
8.200 PORTAL90201
8.201 PORTAL90202
8.202 PORTAL90203
8.203 PORTAL90204
8.204 PORTAL90205
8.205 PORTAL90206
8.206 PORTAL90207
8.207 PORTAL90208
8.208 PORTAL90209
8.209 PORTAL90210
8.210 PORTAL90211
8.211 PORTAL90212
8.212 PORTAL90213
8.213 PORTAL90214
8.214 PORTAL90215
8.215 PORTAL90216
8.216 PORTAL90217
8.217 PORTAL90218
8.218 PORTAL90219

Copyright © Huawei
Mobile Money
8.219 PORTAL90220
8.220 PORTAL90221
8.221 PORTAL90222
8.222 PORTAL90223
8.223 PORTAL90224
8.224 PORTAL90225
8.225 PORTAL90226
8.226 PORTAL90227
8.227 PORTAL90228
8.228 PORTAL90229
8.229 PORTAL90230
8.230 PORTAL90231
8.231 PORTAL90232
8.232 PORTAL90233
8.233 PORTAL90234
8.234 PORTAL90235
8.235 PORTAL90236
8.236 PORTAL90237
8.237 PORTAL90238
8.238 PORTAL90239
8.239 PORTAL90240
8.240 PORTAL90241
8.241 PORTAL90242
8.242 PORTAL90243
8.243 PORTAL90244
8.244 PORTAL90245
8.245 PORTAL90246
8.246 PORTAL90247
8.247 PORTAL90248
8.248 PORTAL90249
8.249 PORTAL90250
8.250 PORTAL90251
8.251 PORTAL90252

Copyright © Huawei
Mobile Money
8.252 PORTAL90253
8.253 PORTAL90254
8.254 PORTAL90255
8.255 PORTAL90256
8.256 PORTAL90257
8.257 PORTAL90258
8.258 PORTAL90259
8.259 PORTAL90260
8.260 PORTAL90261
8.261 PORTAL90262
8.262 PORTAL90263
8.263 PORTAL90264
8.264 PORTAL90266
8.265 PORTAL90267
8.266 PORTAL90269
8.267 PORTAL90271
8.268 PORTAL90272
8.269 PORTAL90273
8.270 PORTAL90274
8.271 PORTAL90275
8.272 PORTAL90276
8.273 PORTAL90277
8.274 PORTAL90278
8.275 PORTAL90279
8.276 PORTAL90280
8.277 PORTAL90281
8.278 PORTAL90282
8.279 PORTAL90283
8.280 PORTAL90284
8.281 PORTAL90285
8.282 PORTAL90286
8.283 PORTAL90287
8.284 PORTAL90288

Copyright © Huawei
Mobile Money
8.285 PORTAL90289
8.286 PORTAL90290
8.287 PORTAL90291
8.288 PORTAL90292
8.289 PORTAL90299
8.290 PORTAL90300
8.291 PORTAL90301
8.292 PORTAL90302
8.293 PORTAL90303
8.294 PORTAL90304
8.295 PORTAL90305
8.296 PORTAL90308
8.297 PORTAL90311
8.298 PORTAL90312
8.299 PORTAL90313
8.300 PORTAL90319
8.301 PORTAL90320
8.302 PORTAL90321
8.303 PORTAL90328
8.304 PORTAL90329
8.305 PORTAL90330
8.306 PORTAL90331
8.307 PORTAL90332
8.308 PORTAL90333
8.309 PORTAL90334
8.310 PORTAL90335
8.311 PORTAL90336
8.312 PORTAL90337
8.313 PORTAL90338
8.314 PORTAL90339
8.315 PORTAL90340
8.316 PORTAL90341
8.317 PORTAL90342

Copyright © Huawei
Mobile Money
8.318 PORTAL90343
8.319 PORTAL90344
8.320 PORTAL90345
8.321 PORTAL90346
8.322 PORTAL90347
8.323 PORTAL90348
8.324 PORTAL90349
8.325 PORTAL90350
8.326 PORTAL90351
8.327 PORTAL90352
8.328 PORTAL90353
8.329 PORTAL90354
8.330 PORTAL90355
8.331 PORTAL90356
8.332 PORTAL90357
8.333 PORTAL90358
8.334 PORTAL90359
8.335 PORTAL90360
8.336 PORTAL90361
8.337 PORTAL90362
8.338 PORTAL90363
8.339 PORTAL90364
8.340 PORTAL90365
8.341 PORTAL90367
8.342 PORTAL90368
8.343 PORTAL90369
8.344 PORTAL90370
8.345 PORTAL90371
8.346 PORTAL90382
8.347 PORTAL90383
8.348 PORTAL90384
8.349 PORTAL90386
8.350 PORTAL90387

Copyright © Huawei
Mobile Money
8.351 PORTAL90388
8.352 PORTAL90389
8.353 PORTAL90390
8.354 PORTAL90391
8.355 PORTAL90394
8.356 PORTAL90395
8.357 PORTAL90396
8.358 PORTAL90397
8.359 PORTAL90398
8.360 PORTAL90399
8.361 PORTAL90400
8.362 PORTAL90404
8.363 PORTAL90405
8.364 PORTAL90406
8.365 PORTAL90407
8.366 PORTAL90408
8.367 PORTAL90410
8.368 PORTAL90411
8.369 PORTAL90412
8.370 PORTAL90413
8.371 PORTAL90414
8.372 PORTAL90415
8.373 PORTAL90416
8.374 PORTAL90417
8.375 PORTAL90418
8.376 PORTAL90419
8.377 PORTAL90420
8.378 PORTAL90421
8.379 PORTAL90422
8.380 PORTAL90423
8.381 PORTAL90424
8.382 PORTAL90425
8.383 PORTAL90426

Copyright © Huawei
Mobile Money
8.384 PORTAL90427
8.385 PORTAL90428
8.386 PORTAL90429
8.387 PORTAL90430
8.388 PORTAL90431
8.389 PORTAL90432
8.390 PORTAL90433
8.391 PORTAL90434
8.392 PORTAL90435
8.393 PORTAL90436
8.394 PORTAL90437
8.395 PORTAL90438
8.396 PORTAL90439
8.397 PORTAL90440
8.398 PORTAL90441
8.399 PORTAL90442
8.400 PORTAL90443
8.401 PORTAL90444
8.402 PORTAL90445
8.403 PORTAL90446
8.404 PORTAL90447
8.405 PORTAL90449
8.406 PORTAL90450
8.407 PORTAL90452
8.408 PORTAL90453
8.409 PORTAL90454
8.410 PORTAL90455
8.411 PORTAL90456
8.412 PORTAL90457
8.413 PORTAL90458
8.414 PORTAL90459
8.415 PORTAL90461
8.416 PORTAL90462

Copyright © Huawei
Mobile Money
8.417 PORTAL90463
8.418 PORTAL90464
8.419 PORTAL90465
8.420 PORTAL90466
8.421 PORTAL90467
8.422 PORTAL90468
8.423 PORTAL90469
8.424 PORTAL90470
8.425 PORTAL90471
8.426 PORTAL90472
8.427 PORTAL90473
8.428 PORTAL90474
8.429 PORTAL90475
8.430 PORTAL90476
8.431 PORTAL90477
8.432 PORTAL90478
8.433 PORTAL90479
8.434 PORTAL90480
8.435 PORTAL90481
8.436 PORTAL90482
8.437 PORTAL90483
8.438 PORTAL90484
8.439 PORTAL90485
8.440 PORTAL90487
8.441 PORTAL90488
8.442 PORTAL90489
8.443 PORTAL90490
8.444 PORTAL90491
8.445 PORTAL90492
8.446 PORTAL90493
8.447 PORTAL90494
8.448 PORTAL90495
8.449 PORTAL90500

Copyright © Huawei
Mobile Money
8.450 PORTAL90501
8.451 PORTAL90502
8.452 PORTAL90504
8.453 PORTAL90505
8.454 PORTAL90506
8.455 PORTAL90507
8.456 PORTAL90508
8.457 PORTAL90509
8.458 PORTAL90510
8.459 PORTAL90511
8.460 PORTAL90512
8.461 PORTAL90515
8.462 PORTAL90516
8.463 PORTAL90517
8.464 PORTAL90518
8.465 PORTAL90520
8.466 PORTAL90521
8.467 PORTAL90522
8.468 PORTAL90523
8.469 PORTAL95000
8.470 PORTAL95001
8.471 PORTAL95002
8.472 PORTAL95003
8.473 PORTAL95004
8.474 PORTAL95005
8.475 PORTAL95006
8.476 PORTAL95007
8.477 PORTAL95008
8.478 PORTAL95009
8.479 PORTAL95010
8.480 PORTAL95011
8.481 PORTAL95012
8.482 PORTAL95013

Copyright © Huawei
Mobile Money
8.483 PORTAL95014
8.484 PORTAL95015
8.485 PORTAL95016
8.486 PORTAL95017
8.487 PORTAL95018
8.488 PORTAL95019
8.489 PORTAL95020
8.490 PORTAL95021
8.491 PORTAL95022
8.492 PORTAL95023
8.493 PORTAL95024
8.494 PORTAL95025
8.495 PORTAL95026
8.496 PORTAL95027
8.497 PORTAL95028
8.498 PORTAL95029
8.499 PORTAL95030
8.500 PORTAL95031
8.501 PORTAL95032
8.502 PORTAL95033
8.503 PORTAL95034
8.504 PORTAL95035
8.505 PORTAL95036
8.506 PORTAL95037
8.507 PORTAL95038
8.508 PORTAL95039
8.509 PORTAL95040
8.510 PORTAL95041
8.511 PORTAL95043
8.512 PORTAL95044
8.513 PORTAL95045
8.514 PORTAL95046
8.515 PORTAL95047

Copyright © Huawei
Mobile Money
8.516 PORTAL95048
8.517 PORTAL95049
8.518 PORTAL95050
8.519 PORTAL95051
8.520 PORTAL95052
8.521 PORTAL95053
8.522 PORTAL95054
8.523 PORTAL95055
8.524 PORTAL95056
8.525 PORTAL95057
8.526 PORTAL95058
8.527 PORTAL95059
8.528 PORTAL95060
8.529 PORTAL95061
8.530 PORTAL95064
8.531 PORTAL95065
8.532 PORTAL95066
8.533 PORTAL95067
8.534 PORTAL95068
8.535 PORTAL95069
8.536 PORTAL95070
8.537 PORTAL95071
8.538 PORTAL95072
8.539 PORTAL95073
8.540 PORTAL95074
8.541 PORTAL95075
8.542 PORTAL95076
8.543 PORTAL95077
8.544 PORTAL95078
8.545 PORTAL95079
8.546 PORTAL95080
8.547 PORTAL95081
8.548 PORTAL95082

Copyright © Huawei
Mobile Money
8.549 PORTAL95083
8.550 PORTAL95084
8.551 PORTAL95085
8.552 PORTAL95086
8.553 PORTAL95087
8.554 PORTAL95088
8.555 PORTAL95089
8.556 PORTAL95090
8.557 PORTAL95091
8.558 PORTAL95092
8.559 PORTAL95093
8.560 PORTAL95095
8.561 PORTAL95097
8.562 PORTAL95099
8.563 PORTAL95101
8.564 PORTAL95103
8.565 PORTAL95104
8.566 PORTAL95105
8.567 PORTAL95106
8.568 PORTAL95107
8.569 PORTAL95108
8.570 PORTAL95109
8.571 PORTAL95110
8.572 PORTAL95111
8.573 PORTAL95112
8.574 PORTAL95113
8.575 PORTAL95114
8.576 PORTAL95115
8.577 PORTAL95116
8.578 PORTAL95117
8.579 PORTAL95118
8.580 PORTAL95119
8.581 PORTAL95120

Copyright © Huawei
Mobile Money
8.582 PORTAL95121
8.583 PORTAL95122
8.584 PORTAL95123
8.585 PORTAL95124
8.586 PORTAL95125
PORTAL90001
Description
Session timed out.
Scenario
Long time did not operate portal.
Access Channel
Web
Possible Causes
You have been away for a long time.
Procedure
Log in again.
8.1 PORTAL90002
Description
The system is busy or the network connection is terminated.
Scenario
Abnormal network connection.
Access Channel
Web
Possible Causes
The system is busy. Please try again later.

Copyright © Huawei
Mobile Money
Procedure
Check whether the network connection is normal.
8.2 PORTAL90003
Description
No certificate is found.
Scenario
Upload file does not contain the certificate.
Access Channel
Web
Possible Causes
No certificate is found.
Procedure
Check whether a certificate exists.
8.3 PORTAL90004
Description
The certificate has expired.
Scenario
Upload expired certificate file.
Access Channel
Web
Possible Causes
The certificate has expired.
Procedure
Verify that the certificate is in the validity period before performing this operation.

Copyright © Huawei
Mobile Money
8.4 PORTAL90005
Description
The certificate file is corrupted or in an incorrect format.
Scenario
Access Channel
Web
Possible Causes
Procedure
1. Check whether the certificate file is in a correct format.
2. Check whether the certificate file is corrupted.
8.5 PORTAL90006
Description
The key file is corrupted or in an incorrect format.
Scenario
The key file format error or file is damaged.
Access Channel
Web
Possible Causes
Failed to read the key file.
Procedure
1. Check whether the key file is in a correct format.
2. Check whether the key file is corrupted.

Copyright © Huawei
Mobile Money
8.6 PORTAL90007
Description
The file is corrupted or in an incorrect format.
Scenario
The file format error or is damaged.
Access Channel
Web
Possible Causes
Failed to read the file.
Procedure
1. Check whether the file is in a correct format.
2. Check whether the file is corrupted.
8.7 PORTAL90008
Description
The current user has no permission to perform this operation.
Scenario
The current user has no permission to perform this operation.
Access Channel
Web
Possible Causes
No permission is assigned to the user for the operation.
Procedure
1. Choose My Functions > Operational Configuration > Create&View and enter the
operator role management page.
2. Add permission to the role of the operator.
If you do not have the permission to change the permissions of a role, ask an authorized
operator to perform the operation.

Copyright © Huawei
Mobile Money
8.8 PORTAL90009
Description
An operator cannot modify information about the self, and a common SP operator cannot
modify information about an SP system administrator.
Scenario
An operator attempts to change the information about the self, or a common SP operator
attempts to change the information about an SP system administrator.
Access Channel
Web
Possible Causes
No permission is assigned to the user for the operation.
Procedure
Perform this operation as an authorized operator or administrator.
8.9 PORTAL90010
Description
The GL mapping does not exist.
Scenario
GL Mapping record is deleted.
Access Channel
Web
Possible Causes
The GL mapping is deleted.
Procedure
Cancel this operation.

Copyright © Huawei
Mobile Money
8.10 PORTAL90011
Description
The tasks to be processed in bulk are not of the same type.
Scenario
Operator batch approval task, need to detect the examination and approval of the tasks to be
for the same type.
Access Channel
Web
Possible Causes
An error has occurred when tasks are processed in bulk.
Procedure
Select the same type of tasks.
8.11 PORTAL90012
Description
Failed to view information about the customer or the organization operator info failed.
Scenario
In the environment of customer care, he (or she) is not allowed to query the information
about a customer or organization operator by entering the URL way directly, only if passed
the verification.
Access Channel
Web
Possible Causes
The customer or organization operator is not authenticated or fails to be authenticated.
Procedure
Please verify the customer or the organization operator first.

Copyright © Huawei
Mobile Money
8.12 PORTAL90013
Description
The item value or item name already exists.
Scenario
New data dictionary, values and name of the Item the Item cannot be repeated and existing
data.
Access Channel
Web
Possible Causes
The item value or item name already exists.
Procedure
Change the item value or item name.
8.13 PORTAL90015
Description
No data permission is assigned to the user for the reason type used by the transaction.
Scenario
The current user has no permission to view the data.
Access Channel
Web
Possible Causes
No data permission is assigned to the user for the reason type used by the transaction.
Procedure
2. Add the data permission to the role of the operator.

Copyright © Huawei
Mobile Money
8.14 PORTAL90016
Description
Template content of language {0} is invalid.
Scenario
A state template of USSD process exists syntax error when configuring it on the portal.
Access Channel
Web
Possible Causes
Template content is invalid.
Procedure
Check jexl syntax correctness of template content.
8.15 PORTAL90017
Description
Script content is invalid. Please check content.
Scenario
A state script of USSD process exists syntax error when configuring it on portal.
Access Channel
Web
Possible Causes
Script content is invalid.
Procedure
Check jexl syntax correctness of script content.

Copyright © Huawei
Mobile Money
8.16 PORTAL90018
Description
Cannot delete first state named {0}.
Scenario
Try to delete the begin state of USSD process on portal.
Access Channel
Web
Possible Causes
Cannot delete the first state of any process.
Procedure
Do not delete the first state named {0}.
8.17 PORTAL90019
Description
Template or script content is invalid, please check it.
Scenario
Template or script content is invalid.
Access Channel
Web
Possible Causes
Template or script content has some syntax error.
Procedure
please check whether template and script meet Jexl synx rules.

Copyright © Huawei
Mobile Money
8.18 PORTAL90020
Description
The parameter name is not unique.
Scenario
Some parameter names are duplicated in process template.
Access Channel
Web
Possible Causes
Some parameter names are duplicated in process template.
Procedure
Verify that parameter names are unique.
8.19 PORTAL90021
Description
A selected task initiator is incorrect.
Scenario
The Tasks you chose ,their initiators do not belong to the same organization.
Access Channel
Web
Possible Causes
A task initiator selected during bulk task assignment belongs to another organization.
Procedure
Select task initiators that belong to the same organization.

Copyright © Huawei
Mobile Money
8.20 PORTAL90022
Description
The following task types do not support bulk processing: Transaction and Action, Manual
Task.
Scenario
Trying to examination and approval is not allowed to batch processing tasks.
Access Channel
Web
Possible Causes
The selected task does not support bulk processing.
Procedure
Select a task that support bulk processing or process the tasks one by one.
8.21 PORTAL90023
Description
Only approval tasks can be processed in bulk.
Scenario
Trying to examination and approval is not allowed to batch processing tasks.
Access Channel
Web
Possible Causes
The selected task does not support bulk processing.
Procedure
Select a task that support bulk processing or process the tasks one by one.

Copyright © Huawei
Mobile Money
8.22 PORTAL90024
Description
The time format cannot be parsed.
Scenario
The format of the time entered on the portal is incorrect.
Access Channel
Web
Possible Causes
Procedure
Enter a time in the required format.
8.23 PORTAL90025
Description
The key is in an incorrect format.
Scenario
The added key or new key is in an incorrect format.
Access Channel
Web
Possible Causes
The added key or new key is in an incorrect format.
Procedure
Verify that the key is in a correct format.

Copyright © Huawei
Mobile Money
8.24 PORTAL90026
Description
Currency code {0} is in use.
Scenario
The currency is in use and cannot be deleted.
Access Channel
Web
Possible Causes
The currency is in use and cannot be deleted.
Procedure
Do not delete a currency in use.
8.25 PORTAL90027
Description
The {0} record already exists.
Scenario
The data record to be inserted already exists.
Access Channel
Web
Possible Causes
The data record to be inserted already exists.
Procedure
Do not insert data record that already exists.

Copyright © Huawei
Mobile Money
8.26 PORTAL90028
Description
There can be only one released version which takes effect in the future.
Scenario
There is already a released version which takes effect in the future.
Access Channel
Web
Possible Causes
There is already a released version which takes effect in the future.
Procedure
Perform the operation again after the released version has taken effect.
8.27 PORTAL90029
Description
The version effective time must be later than the release time.
Scenario
The version effective time must not be earlier than the release time.
Access Channel
Web
Possible Causes
The version effective time must not be earlier than the release time.
Procedure
Change the effective time and release the version again.

Copyright © Huawei
Mobile Money
8.28 PORTAL90030
Description
Current entity already exists.
Scenario
The configuration data has been added by another operator.
Access Channel
Web
Possible Causes
Current entity already exists.
Procedure
Duplicate data.
8.29 PORTAL90031
Description
Data of the current {0} is already referenced.
Scenario
Current entity has been used.
Access Channel
Web
Possible Causes
The current {0} has already been referenced.
Procedure
Do not modify or delete a referenced entity.

Copyright © Huawei
Mobile Money
8.30 PORTAL90032
Description
The line entry already has 499 pairs of GL mapping. No more GL mapping can be added.
Scenario
The maximum GL mapping pairs for the same line entry cannot exceed 499.
Access Channel
Web
Possible Causes
The maximum GL mapping pairs for the same line entry cannot exceed 499.
Procedure
Delete unnecessary GL mapping rules and try again.
8.31 PORTAL90033
Description
A GL account is used for the debit and credit parties in one pair of GL mapping rules.
Scenario
A GL account cannot be used for the debit and credit parties in one pair of GL mapping rules.
Access Channel
Web
Possible Causes
A GL account cannot be used for the debit and credit parties in one pair of GL mapping rules.
Procedure
Verify that the GL account is used only for either the debit or credit party in one pair of GL
mapping rules.

Copyright © Huawei
Mobile Money
8.32 PORTAL90034
Description
The GL mapping rules for the debit and credit parties in the same line entry are the same.
Scenario
The GL mapping rules for the debit and credit parties in the same line entry must be different.
Access Channel
Web
Possible Causes
The GL mapping rules for the debit and credit parties in the same line entry must be different.
Procedure
Chang GL mapping rules and verify that GL mapping rules for the debit and credit parties in
the same line entry are different.
8.33 PORTAL90035
Description
The current action role exists.
Scenario
Choose My Function > Operational Configuration > Notification Configuration > Business
Operation Notification Rule (Action) on an SP portal and perform the add operation.
Access Channel
Web
Possible Causes
The current action role exists.
Procedure
The action role cannot be inserted repeatedly.

Copyright © Huawei
Mobile Money
8.34 PORTAL90036
Description
The variable is referenced and therefore cannot be deleted.
Scenario
The variable is referenced and therefore cannot be deleted.
Access Channel
Web
Possible Causes
The variable is referenced.
Procedure
1. Verify whether the DEFAULT_CONTENT field in the CPS_NC_TYPE table in the
CPSSYS database has referenced the variable.
2. Verify whether the CONTENT field in the CPS_NC_ENTITY table in the CPSSYS
database has referenced the variable.
8.35 PORTAL90037
Description
Operation failed. No permission for current operator to do this operation.
Scenario
Access Channel
Web
Possible Causes
Procedure
Make sure current operator has permission.

Copyright © Huawei
Mobile Money
8.36 PORTAL90038
Description
Authentication failed because the failure rule is not unique.
Scenario
The failure rule is not unique.
Access Channel
Web
Possible Causes
The failure rule already exists.
Procedure
Verify that the failure rule is correct and unique.
8.37 PORTAL90039
Description
Scenario
The system parameter is incorrectly configured.
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
8.38 PORTAL90040
Description
The transaction initiator does not exist.
Scenario
Access Channel
Web
Possible Causes
Procedure
8.39 PORTAL90041
Description
The identity type does not exist or is invalid.
Scenario
Access Channel
Web
Possible Causes
Procedure
Verify the operator's permission.

Copyright © Huawei
Mobile Money
8.40 PORTAL90042
Description
No record is found based on the amount freezing serial number.
Scenario
The amount freezing serial number does not exist.
Access Channel
Web
Possible Causes
The amount freezing serial number does not exist.
Procedure
8.41 PORTAL90043
Description
The balance in the {1} account {2} of {0} is insufficient for the transaction.
Scenario
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
8.42 PORTAL90044
Description
Scenario
The obtained default currency is incorrectly configured during transaction.
Access Channel
Web
Possible Causes
Procedure
Definition.
3. Set the default currency.
8.43 PORTAL90045
Description
Scenario
The obtained default currency is incorrectly configured during transaction.
Access Channel
Web
Possible Causes
Procedure
Definition.

Copyright © Huawei
Mobile Money
3. Verify whether the configured default currency meets the ISO 4127 standard. If no,
manually modify the default currency.
8.44 PORTAL90046
Description
Scenario
The obtained specified currency is incorrectly configured during transaction.
Access Channel
Web
Possible Causes
Procedure
Definition.
3. Check whether the specified currency code exists. If not, check whether the specified
currency is correct or add new currency.
8.45 PORTAL90047
Description
Scenario
Access Channel
Web
Possible Causes
The revenue settlement account is not configured or incorrectly configured.

Copyright © Huawei
Mobile Money
Procedure
1. Log in to the Portal as the system administrator.
2. Choose My Functions > Operational Configuration > System Parameter > Revenue
Settlement.
3. Verify that the Settlement Account Type field is displayed on the GUI and set to
Revenue Settlement Account.
8.46 PORTAL90048
Description
The system is busy.
Scenario
The fail due to the system busy or other unknown exception.
Access Channel
Web
Possible Causes
An unknown exception has occurred. Obtain the tracing log for fault diagnosis.
Procedure
Obtain the Portal debug logs and contact a Huawei engineer for help, or access
8.47 PORTAL90049
Description
Failed to obtain the {0} system parameter.
Scenario
Can not get system config value
Access Channel
Web
Possible Causes
The {0} system parameter is not configured.

Copyright © Huawei
Mobile Money
Procedure
Parameters.
2. Configure SFTP system parameters as required.
8.48 PORTAL90050
Description
Refund is not supported because the account balance of the identity is 0.
Scenario
Access Channel
Web
Possible Causes
Procedure
Do not refund using an identity account with no balance.
8.49 PORTAL90051
Description
Scenario
Access Channel
Web
Possible Causes
Procedure
Do not submit a refund request repetitively.

Copyright © Huawei
Mobile Money
8.50 PORTAL90052
Description
Scenario
Access Channel
Web
Possible Causes
Procedure
Do not refund an amount that is transferred to the unclaimed account of an SP.
8.51 PORTAL90053
Description
There is no dormant record, or money has been refunded to the identity.
Scenario
The identity has no dormant record in the system, or money has been refunded to the identity.
Access Channel
Web
Possible Causes
The identity has no dormant record in the system, or money has been refunded to the identity.
Procedure
1. Choose Search > Customer.
2. Configure customer query conditions.
3. Check whether the customer is in the Dormant state on the customer details page.

Copyright © Huawei
Mobile Money
8.52 PORTAL90054
Description
The refund application is being processed. Do not submit the refund application again.
Scenario
A customer submits another refund request when the last refund transaction is in progress.
Access Channel
Web
Possible Causes
The refund application is being processed.
Procedure
Cancel the existing refund application in the system and reinitiate a refund application, or
approve and complete the existing refund application.
8.53 PORTAL90055
Description
The refund application is rejected.
Scenario
An account clearing request is being processed in the system.
Access Channel
Web
Possible Causes
An account clearing request is being processed.
Procedure
Contact the system administrator for help and complete transactions in progress.

Copyright © Huawei
Mobile Money
8.54 PORTAL90056
Description
Refund is not supported.
Scenario
Access Channel
Web
Possible Causes
Procedure
Clear the account first.
8.55 PORTAL90057
Description
Account clearing is not allowed.
Scenario
Access Channel
Web
Possible Causes
Procedure
Complete the transaction first.

Copyright © Huawei
Mobile Money
8.56 PORTAL90058
Description
No reconciliation detail is obtained.
Scenario
Can not find any bank statement detail
Access Channel
Web
Possible Causes
Procedure
8.57 PORTAL90059
Description
Scenario
Parameter invalid
Access Channel
Web
Possible Causes
{0}
Procedure

Copyright © Huawei
Mobile Money
8.58 PORTAL90060
Description
Failed to find the default operator.
Scenario
Access Channel
Web
Possible Causes
Procedure
Transaction to enter the system parameter configuration page.
2. Correctly configure the SP Operator Initiating Transaction.
8.59 PORTAL90061
Description
No control account is obtained for the {0} parameter.
Scenario
Can not find sp control account.
Access Channel
Web
Possible Causes
The control account does not exist.
Procedure

Copyright © Huawei
Mobile Money
8.60 PORTAL90062
Description
Scenario
There is no detail with transLogId={0} mathed the credit entry when query entries.
Access Channel
Web
Possible Causes
Failed to find the credit reconciliation record by the {0} transLogId.
Procedure
8.61 PORTAL90063
Description
Scenario
More than one detail mathed the credit entry when query entries.
Access Channel
Web
Possible Causes
Multiple credit reconciliation records are found by the {0} transLogId.
Procedure

Copyright © Huawei
Mobile Money
8.62 PORTAL90064
Description
Scenario
Connect SFTP failed, for {0},please check system config.
Access Channel
Web
Possible Causes
{0}
Procedure
Parameters.
8.63 PORTAL90065
Description
Failed to access the {0} directory.
Scenario
The directory is not existed or the user has no permission.
Access Channel
Web
Possible Causes
The directory does not exist, or the operator has no permission to access the directory.
Procedure
Check whether the directory exists. If no, manually create the directory. If yes, assign the
permission for accessing the directory to the operator.

Copyright © Huawei
Mobile Money
8.64 PORTAL90066
Description
Failed to obtain information about the bank whose bank ID is {0}.
Scenario
Cank not get Mobile Money bank with bankId={0}.
Access Channel
Web
Possible Causes
Procedure
8.65 PORTAL90067
Description
Failed to create the {0} directory.
Scenario
Create the SFTP file directory {0} failed.
Access Channel
Web
Possible Causes
{1}
Procedure
Parameters.
2. Verify whether the directories and permissions configured for the SFTP are correct.

Copyright © Huawei
Mobile Money
8.66 PORTAL90068
Description
Failed to obtain the {0} EFT exporter.
Scenario
EFT exporter is not configured.
Access Channel
Web
Possible Causes
No EFT exporter is configured.
Procedure
2. Configure an exporter.
8.67 PORTAL90069
Description
The {0} EFT parser is not found.
Scenario
EFT exporter is not found.
Access Channel
Web
Possible Causes
The EFT exporter is incorrectly configured.
Procedure
2. Verify that an exporter is correctly configured.

Copyright © Huawei
Mobile Money
8.68 PORTAL90070
Description
Failed to obtain the {0} bill parser.
Scenario
Bank statement parser is not configured.
Access Channel
Web
Possible Causes
No bill parser is configured.
Procedure
2. Configure a bill parser.
8.69 PORTAL90071
Description
The {0} bill parser is not found.
Scenario
Bank statement parser with classname {0} is not found.
Access Channel
Web
Possible Causes
The bill parse is incorrectly configured.
Procedure
2. Verify that a bill parser is correctly configured.

Copyright © Huawei
Mobile Money
8.70 PORTAL90072
Description
Failed to obtain the {0} SFTP parameter.
Scenario
Parameter is not configured.
Access Channel
Web
Possible Causes
The {0} SFTP parameter is not configured.
Procedure
Parameters.
2. Configure the {0} parameter.
8.71 PORTAL90073
Description
Failed to obtain the control account of the {0} bank.
Scenario
Failed to obtain the default control account of the bank.
Access Channel
Web
Possible Causes
No default control account is configured for the {0} bank.
Procedure
1. Choose Search > Bank.
2. Select the {0} bank and configure a default control account for it.

Copyright © Huawei
Mobile Money
8.72 PORTAL90074
Description
Failed to obtain the bank card whose ID is {0}.
Scenario
Failed to obtain the account information.
Access Channel
Web
Possible Causes
Procedure
8.73 PORTAL90075
Description
Failed to obtain the bank card associated with the organization whose identity ID is {1}.
Scenario
Failed to obtain the bank card.
Access Channel
Web
Possible Causes
The organization whose identity ID is {1} is not associated with a bank card.
Procedure
2. Select the {1} organization and associate it with a bank card.

Copyright © Huawei
Mobile Money
8.74 PORTAL90076
Description
Failed to find the SP whose SP short code is {0}.
Scenario
Failed to find the SP base on SP short code.
Access Channel
Web
Possible Causes
The SP Short Code parameter is incorrect.
Procedure
Enter a correct SP short code.
8.75 PORTAL90077
Description
The current operation is not supported.
Scenario
The entry is already processed, and the current operation is not supported.
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
8.76 PORTAL90078
Description
The organization that executes revenue settlement does not exist.
Scenario
No organization information is found during commission settlement.
Access Channel
Web
Possible Causes
No organization information is found based on the {0} organization ID.
Procedure
2. Choose Search > Organization page.
3. Enter organization information for query.
4. Check whether the organization to be queried exists or whether the organization provides
the service. If the organization does not exist, enter the correct organization.
8.77 PORTAL90079
Description
A system exception has occurred during commission settlement.
Scenario
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
8.78 PORTAL90080
Description
The account information does not exist or the account is abnormal.
Scenario
Access Channel
Web
Possible Causes
Procedure
 If an SP account does not exist, choose Search > Service Provider > Bank&Account >
> Internal Account and add account information.
 If an organization account does not exist, ask the SP administrator to subscribe to a
product that contains the account for the organization.
8.79 PORTAL90081
Description
The commission settlement task does not exist.
Scenario
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
8.80 PORTAL90082
Description
Scenario
The voucher ID is empty when querying voucher.
Access Channel
Web
Possible Causes
The voucher ID is empty.
Procedure
8.81 PORTAL90083
Description
Scenario
The voucher holder parameter is empty when querying voucher.
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
8.82 PORTAL90084
Description
Scenario
The voucher holder parameter is empty when querying voucher.
Access Channel
Web
Possible Causes
Procedure
8.83 PORTAL90085
Description
Scenario
The voucher type ID parameter is empty when querying voucher.
Access Channel
Web
Possible Causes
The voucher type ID parameter is empty.
Procedure

Copyright © Huawei
Mobile Money
8.84 PORTAL90086
Description
Scenario
The voucher code parameter is empty when querying voucher.
Access Channel
Web
Possible Causes
Procedure
8.85 PORTAL90087
Description
Scenario
The voucher state parameter is empty when querying voucher.
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
8.86 PORTAL90088
Description
Duplicate data records.
Scenario
Records in the database are not unique.
Access Channel
Web
Possible Causes
Records in the database are not unique.
Procedure
Send the error information to a Huawei engineer for fault diagnosis.
8.87 PORTAL90089
Description
An input parameter of the method is invalid. {0}
Scenario
Access Channel
Web
Possible Causes
The length, type, or format of an input parameter of the method is incorrect. {0}
Procedure
Enter a correct value.

Copyright © Huawei
Mobile Money
8.88 PORTAL90090
Description
An input parameter is invalid.
Scenario
An input parameter does not indicate an identity.
Access Channel
Web
Possible Causes
An input parameter does not indicate an identity. The Identity field can be set only to
customer, SP, SP operator, organization, organization operator, till, and bank.
Procedure
Set parameter types as required.
8.89 PORTAL90091
Description
No valid identity type is found.
Scenario
No valid identity type is defined in the Spring configuration file.
Access Channel
Web
Possible Causes
The {0} type is not defined in the Spring configuration file.
Procedure
Add the {0} type to the map whose bean is identityRuleProfileDaoProvider or
identityDaoProvider in the payment.dao.service.xml file.

Copyright © Huawei
Mobile Money
8.90 PORTAL90092
Description
No valid identity type is found.
Scenario
Access Channel
Web
Possible Causes
Procedure
Add the {0} type to the map whose bean is identityManagerProvider in the
payment.manager.service.xml file.
8.91 PORTAL90093
Description
The {0} does not exist.
Scenario
The Identity field is mandatory.
Access Channel
Web
Possible Causes
The {0} does not exist.
Procedure
Set the Identity field to a correct value.

Copyright © Huawei
Mobile Money
8.92 PORTAL90094
Description
The Identity type field is mandatory.
Scenario
The Identity type field is mandatory.
Access Channel
Web
Possible Causes
The Identity type field can be set only to customer, SP, SP operator, organization, organization
operator, till, or bank.
Procedure
8.93 PORTAL90095
Description
The Identity ID field is empty.
Scenario
The Identity ID field is mandatory.
Access Channel
Web
Possible Causes
The Identity ID field is mandatory.
Procedure

Copyright © Huawei
Mobile Money
8.94 PORTAL90096
Description
You are forcibly offline.
Scenario
The system is busy.
Access Channel
Web
Possible Causes
The system is busy.
Procedure
Log in again.
8.95 PORTAL90097
Description
Your account has logged in at another location. Check whether your account is stolen.
Scenario
Your account has logged in at another location.
Access Channel
Web
Possible Causes
Your account has logged in at another location.
Procedure
Log in again.

Copyright © Huawei
Mobile Money
8.96 PORTAL90098
Description
The RPC fails to invoke the remote service.
Scenario
The RPC fails to invoke the remote service.
Access Channel
Web
Possible Causes
Server exception.
Procedure
8.97 PORTAL90099
Description
The {0} parameter is set to an incorrect value or not configured.
Scenario
The {0} parameter related to BO is set to an incorrect value or not configured.
Access Channel
Web
Possible Causes
The {0} parameter is set to an incorrect value or not configured.
Procedure
Set the {0} parameter to a correct value.

Copyright © Huawei
Mobile Money
8.98 PORTAL90100
Description
The business operation does not exist.
Scenario
Access Channel
Web
Possible Causes
Procedure
8.99 PORTAL90101
Description
The item {1} does not exist in the Mobile Money system configuration or failed to read data
from the cache.
Scenario
1 The item does not exist in the Mobile Money system configuration. 2.No cache is found.
Access Channel
Web
Possible Causes
 The item {1} does not exist in the Mobile Money system configuration.
 No cache is found based on the cache name {0} and key {1}.
Procedure
1. Check whether the configurable item exists in the corresponding configurable category.
Go to next step if it exists.
2. Contact a Huawei engineer for help.

Copyright © Huawei
Mobile Money
8.100 PORTAL90102
Description
The system parameter is incorrect.
Scenario
The system parameter is incorrect.
Access Channel
Web
Possible Causes
The parameter type {0} is incorrect.
Procedure
Check whether the system parameter type {0} is correct.
8.101 PORTAL90103
Description
SP {0} is not found.
Scenario
The SP {0} does not exist.
Access Channel
Web
Possible Causes
SP {0} does not exist.
Procedure

Copyright © Huawei
Mobile Money
8.102 PORTAL90104
Description
SP {0} exists.
Scenario
The SP {0} exists.
Access Channel
Web
Possible Causes
SP {0} exists.
Procedure
Change the SP name.
8.103 PORTAL90105
Description
No SP is found.
Scenario
No SP exists in the system.
Access Channel
Web
Possible Causes
No SP exists in the system.
Procedure

Copyright © Huawei
Mobile Money
8.104 PORTAL90106
Description
The organization is not found.
Scenario
The organization is not found based on the short code.
Access Channel
Web
Possible Causes
Procedure
Change the short code and search for the organization again.
8.105 PORTAL90107
Description
Organization information is blank.
Scenario
Organization information cannot be blank.
Access Channel
Web
Possible Causes
Cause 1: Organization information cannot be blank. Cause 2: An operator has changed
information about the organization, resulting in a query error.
Procedure
Solution 1: Contact a Huawei engineer for help. Solution 2: Choose Search > Organization,
enter the search criteria, and query for details about the organization again.

Copyright © Huawei
Mobile Money
8.106 PORTAL90108
Description
The organization already exists.
Scenario
Access Channel
Web
Possible Causes
Procedure
Change the organization name or short code.
8.107 PORTAL90109
Description
The Parameter:{0} is null.
Scenario
Failed to validate the parameter because the parameter:{0} is null.
Access Channel
Web
Possible Causes
Parameter validation failed because it is null.
Procedure
Send the error information to a Huawei engineer for fault diagnosis.

Copyright © Huawei
Mobile Money
8.108 PORTAL90110
Description
Failed to query the customer.
Scenario
Information about this customer does not exist based on the primary ID.
Access Channel
Web
Possible Causes
Information about this customer does not exist in the database.
Procedure
Data exception. Contact Huawei engineers.
8.109 PORTAL90111
Description
Failed to add devices.
Scenario
Only one device can be allocated to each till.
Access Channel
Web
Possible Causes
Only one device can be allocated to each till.
Procedure
View the till details page. Determine whether the till contains a device. If yes, the device
cannot be added.

Copyright © Huawei
Mobile Money
8.110 PORTAL90112
Description
Failed to query the till.
Scenario
Till information cannot be found based on the input device number or till number.
Access Channel
Web
Possible Causes
Till information cannot be found based on the input device number or till number.
Procedure
1. Check whether the input device number is correct.
2. Check whether the input till number is correct.
8.111 PORTAL90113
Description
Failed to add the device.
Scenario
The device number exists when adding the device for the identity.
Access Channel
Web
Possible Causes
The device number exists.
Procedure
Use another device number, or contact customer service representatives to delete the existing
number if the original is not used anymore and add it again.

Copyright © Huawei
Mobile Money
8.112 PORTAL90114
Description
The device does not exist.
Scenario
The till device is closed or not registered.
Access Channel
Web
Possible Causes
The till device is closed or not registered.
Procedure
Query by another till device number.
8.113 PORTAL90115
Description
The customer's device number is incorrect.
Scenario
The device number does not belong to the customer.
Access Channel
Web
Possible Causes
The device number belongs to {0}, but does not belong to the customer.
Procedure
Change the device number.

Copyright © Huawei
Mobile Money
8.114 PORTAL90116
Description
The length of the MSISDN specified for {0} is {1} and exceeds the valid length range.
Scenario
The length of an MSISDN must be in the range from {2} to {3}. The length of the MSISDN
specified when {0} is created is outside of the valid length range.
Access Channel
Web
Possible Causes
The length of an MSISDN must be in the range from {2} to {3}.
Procedure
Enter an MSISDN whose length is in the range from {2} to {3}.
8.115 PORTAL90117
Description
The operator does not exist or the password is incorrect.
Scenario
The operator does not exist or the password is incorrect when the operator logs in.
Access Channel
Web
Possible Causes
The operator does not exist or the password is incorrect.
Procedure
Enter a correct operator name and password.

Copyright © Huawei
Mobile Money
8.116 PORTAL90118
Description
Scenario
The operator name or the operator ID already exists when creating an operator.
Access Channel
Web
Possible Causes
 The operator name already exists.
 The operator ID already exists.
Procedure
Verify whether the operator name and ID already exist. If yes, change the operator name and
operation ID.
8.117 PORTAL90119
Description
Scenario
The operator to be queried does not exist.
Access Channel
Web
Possible Causes
 The operator is not registered.
Procedure
1. Verify that the operator is registered.

Copyright © Huawei
Mobile Money
8.118 PORTAL90120
Description
Failed to create the organization operator.
Scenario
The operator ID is empty when creating the operator by API/BULK/USSD .
Access Channel
Web
Possible Causes
The operator ID is empty.
Procedure
Enter a correct operator ID.
8.119 PORTAL90121
Description
The operator has no permission to perform this operation.
Scenario
The operator has no permission to operate other organization.
Access Channel
Web
Possible Causes
 The operator does not belong to the organization.
 The operator belongs to a lower-level organization.
 The ordinary SP operator can not modify the sysadmin operator.
Procedure
1. Verify that the operator has the permission to perform the operation.
2. Perform the operation as another operator.

Copyright © Huawei
Mobile Money
8.120 PORTAL90122
Description
Failed to save the KYC field.
Scenario
A KYC field with the same name already exists.
Access Channel
Web
Possible Causes
A KYC field with the same name already exists.
Procedure
Verify the KYC configurations or enter a KYC field with another name.
8.121 PORTAL90123
Description
Operation failed because the KYC field does not exist.
Scenario
Operation failed because the KYC field does not exist.
Access Channel
Web
Possible Causes
The KYC field is deleted.
Procedure

Copyright © Huawei
Mobile Money
8.122 PORTAL90124
Description
Failed to delete the KYC field.
Scenario
The KYC field is not in the draft state and cannot be deleted.
Access Channel
Web
Possible Causes
The KYC field is not in the draft state and cannot be deleted.
Procedure
Refresh the current page and check the status of the KYC field.
8.123 PORTAL90125
Description
Failed to deactivate the KYC field.
Scenario
The KYC field is referenced by the other KYC group.
Access Channel
Web
Possible Causes
The KYC field is referenced by the {0} KYC group.
Procedure
Remove the reference to the KYC field from the {0} KYC group.

Copyright © Huawei
Mobile Money
8.124 PORTAL90126
Description
Operation failed because the ID format does not exist.
Scenario
The ID format to be operated does not exist.
Access Channel
Web
Possible Causes
The ID format is deleted.
Procedure
8.125 PORTAL90127
Description
Failed to save the KYC group.
Scenario
A KYC group to be created or updated already exists.
Access Channel
Web
Possible Causes
A KYC group with the same name already exists.
Procedure
Check the KYC Group configuration and enter a new KYC group name.

Copyright © Huawei
Mobile Money
8.126 PORTAL90128
Description
The KYC group does not exist.
Scenario
Operation failed because the KYC group does not exist.
Access Channel
Web
Possible Causes
System data configuration is incorrect. The {0} KYC group does not exist.
Procedure
The database contains dirty data. Contact a Huawei engineer for help.
8.127 PORTAL90129
Description
Failed to save the KYC group.
Scenario
No KYC field is assigned to the KYC group when saving the KYC group.
Access Channel
Web
Possible Causes
No KYC field is assigned to the KYC group.
Procedure
Assign at least one KYC field to the KYC group.

Copyright © Huawei
Mobile Money
8.128 PORTAL90130
Description
Failed to add KYC fields to the current KYC group.
Scenario
The KYC field in the KYC group is not in the Active state.
Access Channel
Web
Possible Causes
The {0} KYC field in the KYC group is not in the Active state.
Procedure
Activate or delete KYC fields not in the Active state.
8.129 PORTAL90131
Description
Failed to delete the KYC field.
Scenario
The KYC field is referenced by an identity type and therefore cannot be deleted.
Access Channel
Web
Possible Causes
{0}
Procedure
The KYC field is referenced by an identity type and therefore cannot be deleted. To delete it,
perform the following operations:
2. Remove the reference for the KYC field for the corresponding identity.

Copyright © Huawei
Mobile Money
8.130 PORTAL90132
Description
N/A
Scenario
N/A
Access Channel
Web
Possible Causes
N/A
Procedure
N/A
8.131 PORTAL90133
Description
The trust level configured for the identity does not exist.
Scenario
The trust level does not exist during the customer or organization query process.
Access Channel
Web
Possible Causes
 The {0} trust level does not exist after system configuration changes.
 The trust level configuration is incorrect for the identity.
Procedure

Copyright © Huawei
Mobile Money
8.132 PORTAL90134
Description
Failed to save the trust level.
Scenario
The trust level does not exist during the customer or organization query process.
Access Channel
Web
Possible Causes
The {0} trust level does not contain all KYC fields of the {1} trust level which is lower.
Procedure
Level.
2. Add missing KYC fields to the {0} trust level or delete them from the {1} trust level.
8.133 PORTAL90135
Description
Failed to save the trust level.
Scenario
KYC fields assigned to the current trust level must all be contained in the higher trust level.
Access Channel
Web
Possible Causes
KYC fields assigned to the {0} trust level must all be contained in the {1} trust level which is
higher.
Procedure
Level.
2. Delete extra KYC fields from the {0} trust level or add them to the {1} trust level.

Copyright © Huawei
Mobile Money
8.134 PORTAL90136
Description
Failed to save the segment.
Scenario
A segment name specified for the segment to be created or updated already exists.
Access Channel
Web
Possible Causes
A segment with the same name already exists.
Procedure
Check the segment configuration and enter a new segment name.
8.135 PORTAL90137
Description
The segment configured for the identity does not exist.
Scenario
The segment does not exist during the customer or organization query process.
Access Channel
Web
Possible Causes
 The {0} segment does not exist after system configuration changes.
 The segment configuration is incorrect for the identity.
Procedure

Copyright © Huawei
Mobile Money
8.136 PORTAL90138
Description
N/A
Scenario
N/A
Access Channel
Web
Possible Causes
N/A
Procedure
N/A
8.137 PORTAL90139
Description
N/A
Scenario
N/A
Access Channel
Web
Possible Causes
N/A
Procedure
N/A

Copyright © Huawei
Mobile Money
8.138 PORTAL90140
Description
N/A
Scenario
N/A
Access Channel
Web
Possible Causes
N/A
Procedure
N/A
8.139 PORTAL90141
Description
Failed to save the customer subtype.
Scenario
A customer subtype with the same name already exists when updating the customer subtype.
Access Channel
Web
Possible Causes
A customer subtype with the same name already exists.
Procedure
Check the customer subtype configuration and enter a new customer subtype name.

Copyright © Huawei
Mobile Money
8.140 PORTAL90142
Description
Failed to submit the KYC assignment.
Scenario
The KYC field is not selected but is referenced.
Access Channel
Web
Possible Causes
The {0} KYC field is not selected but is referenced.
Procedure
Select the {0} KYC field.
8.141 PORTAL90143
Description
Failed to submit the identity type KYC assignment.
Scenario
The number of KYC mappings for the current identity type exceeds the upper limit.
Access Channel
Web
Possible Causes
The number of KYC mappings for the current identity type exceeds the upper limit.
Procedure
Deselect certain KYC fields with lower priorities. If the problem persists, contact a Huawei
engineer for help.

Copyright © Huawei
Mobile Money
8.142 PORTAL90144
Description
Failed to submit the identity type KYC assignment.
Scenario
Select associated KYC fields together. For example, ID type and ID number must be selected
together.
Access Channel
Web
Possible Causes
The special KYC assignment does not meet the specifications requirement.
Procedure
Select associated KYC fields together. For example, ID type and ID number must be selected
together.
8.143 PORTAL90145
Description
The KYC field is set in an incorrect format on a non-portal interface.
Scenario
The KYC field is set in an incorrect format on a non-portal interface.
Access Channel
Web
Possible Causes
The {0} KYC field is in an incorrect format.
Procedure
Verify that the content in the configuration file is in the [GroupName][FieldName] format.

Copyright © Huawei
Mobile Money
8.144 PORTAL90146
Description
N/A
Scenario
N/A
Access Channel
Web
Possible Causes
N/A
Procedure
N/A
8.145 PORTAL90147
Description
N/A
Scenario
N/A
Access Channel
Web
Possible Causes
N/A
Procedure
N/A

Copyright © Huawei
Mobile Money
8.146 PORTAL90148
Description
Scenario
The value of the KYC field is not an integer with 1 - 18 digits.
Access Channel
Web
Possible Causes
The value of the {0} KYC field is not an integer with 1 - 18 digits.
Procedure
Enter a correct value for the {0} KYC field.
8.147 PORTAL90149
Description
Scenario
Access Channel
Web
Possible Causes
Procedure
Enter the date and time in the correct format.

Copyright © Huawei
Mobile Money
8.148 PORTAL90150
Description
Scenario
Access Channel
Web
Possible Causes
Procedure
Enter complete bank-related KYC fields, including bank, bank name, bank account name, and
bank account number.
8.149 PORTAL90151
Description
The number of bank-related KYC fields is incorrect.
Scenario
Access Channel
Web
Possible Causes
Procedure
2. Select the specified identity type, and assign four bank-related KYC fields to the identity
type.

Copyright © Huawei
Mobile Money
8.150 PORTAL90152
Description
Scenario
Access Channel
Web
Possible Causes
The bank whose ID is {0} does not exist in the system or is not in the Active state.
Procedure
Choose Search > Bank and check whether the bank exists.
 If yes, return to the previous page and select a bank in the Active state.
 If no, ask the system administrator to create a bank.
8.151 PORTAL90153
Description
Scenario
The bank account number already exists when editing the identity KYC information.
Access Channel
Web
Possible Causes
The bank account number already exists.
Procedure
Enter another bank account number.

Copyright © Huawei
Mobile Money
8.152 PORTAL90154
Description
Scenario
The MSISDN is empty when the operator notification channel is set to SMS.
Access Channel
Web
Possible Causes
The MSISDN is empty when the operator notification channel is set to SMS.
Procedure
Enter the MSISDN.
8.153 PORTAL90155
Description
Scenario
The email is empty when the operator notification channel is set to email.
Access Channel
Web
Possible Causes
The email is empty when the operator notification channel is set to email.
Procedure
Enter the email address.

Copyright © Huawei
Mobile Money
8.154 PORTAL90156
Description
Scenario
No notification channel is selected when setting the operator notification channel.
Access Channel
Web
Possible Causes
No notification channel is selected.
Procedure
Select a notification channel.
8.155 PORTAL90157
Description
Scenario
The KYC field is in an incorrect format when an identity KYC information is created or
modified.
Access Channel
Web
Possible Causes
Procedure
Field.

Copyright © Huawei
Mobile Money
8.156 PORTAL90158
Description
The mandatory KYC field is empty.
Scenario
The mandatory KYC field is empty when an identity KYC information is created or
modified.
Access Channel
Web
Possible Causes
The mandatory {0} KYC field is empty.
Procedure
2. View mandatory KYC fields for the identity type.
3. Return to the previous page and configure mandatory KYC fields.
8.157 PORTAL90159
Description
The KYC fields do not exist or are not assigned to the identity type.
Scenario
The mandatory KYC field is empty when an identity KYC information is created or
modified.
Access Channel
Web
Possible Causes
The {0} KYC field is not assigned or does not exist.
Procedure
2. Verify whether the KYC fields are assigned to the identity type.

Copyright © Huawei
Mobile Money
3. If the KYC fields exist but are not assigned to the identity type, assign them to the
identity type. If the KYC fields do not exist, check whether the packet is correct or
contact a Huawei engineer for help.
8.158 PORTAL90160
Description
Failed to create the identity.
Scenario
No trust level is created for the identity.
Access Channel
Web
Possible Causes
No trust level is created for the {0} identity.
Procedure
Level.
2. Create a trust level for the identity type.
8.159 PORTAL90161
Description
Failed to match any trust level.
Scenario
The KYC information is insufficient for even the lowest trust level.
Access Channel
Web
Possible Causes
The KYC information is insufficient for even the lowest trust level.

Copyright © Huawei
Mobile Money
Procedure
Level.
2. Check the KYC fields required by the lowest trust level of the identity type or subtype.
3. Return to the previous page and configure KYC fields required for the three lowest trust
levels.
8.160 PORTAL90162
Description
Scenario
The default product of the current trust level is empty.
Access Channel
Web
Possible Causes
The default product of the trust level {0} is empty.
Procedure
Product.
2. Edit the identity's product.
3. Assign a default product for the {0} trust level.
8.161 PORTAL90163
Description
Scenario
The default rule profile of the current trust level is empty.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The default rule profile of the trust level {0} is empty.
Procedure
2. Assign a default rule profile for the {0} trust level.
8.162 PORTAL90164
Description
Scenario
The default charge profile of the current trust level is empty.
Access Channel
Web
Possible Causes
The default charge profile of the trust level {0} is empty.
Procedure
Charge Profile.
2. Assign a default charge profile for the {0} trust level.
8.163 PORTAL90165
Description
Scenario
The input rule profile is not included in the trust level when creating identity in bulk..
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The {1} rule profile is not included in the {0} trust level.
Procedure
3. Assign the {1} rule profile to the {0} trust level, or select a rule profile already assigned
to the current trust level.
8.164 PORTAL90166
Description
Scenario
The charge profile is not included in the trust level when creating identity in bulk.
Access Channel
Web
Possible Causes
The {1} charge profile is not included in the {0} trust level.
Procedure
Charge Profile.
2. Edit the identity's charge profile.
3. Assign the {1} charge profile to the {0} trust level, or select a charge profile already
assigned to the current trust level.
8.165 PORTAL90167
Description
Failed to match the identity with any trust level.
Scenario
Failed to match the identity with any trust level.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
 {0} has no matching trust level: {1}.
 Failed to read the cache.
Procedure
Add KYC information for the identity so that it can be matched with a trust level.
8.166 PORTAL90168
Description
Failed to create or modify the identity.
Scenario
When creating or modifying the identity, the assignment of trust level is not configured or the
cache is failed to read.
Access Channel
Web
Possible Causes
 The assignment of trust level {0} is not configured.
 Failed to read the cache.
Procedure
1. Choose My Functions > Operational Configuration > Assignment Management.
2. Assign rule profile, charge profile and product for the trust level.
8.167 PORTAL90169
Description
Failed to verify the identity.
Scenario
The operator does not exist, or the answer to the security question is incorrect.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The operator does not exist, or the answer to the security question is incorrect.
Procedure
1. Verify that the operator exists.
2. Verify that the answer to the security question is correct.
8.168 PORTAL90170
Description
The answer to the security question is incorrect.
Scenario
A customer answers one or more identity verification questions incorrectly.
Access Channel
Web
Possible Causes
The answer to the security question is incorrect.
Procedure
Enter the correct answer. You have {0} attempts before being locked out.
8.169 PORTAL90171
Description
The password is locked because the number of identity verification attempts has reached the
upper limit.
Scenario
The number of answers to identity verification problems exceeds the upper limit.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The password is locked because the number of identity verification attempts has reached the
upper limit.
Procedure
Ask the system administrator to unlock the password.
8.170 PORTAL90172
Description
The security credential, such as password, PIN, or secret word, is incorrect.
Scenario
The security credential, such as password, PIN, or secret word, is incorrect.
Access Channel
Web
Possible Causes
The input {1} is incorrect.
Procedure
Enter the correct security credential.
8.171 PORTAL90173
Description
The old security credential is incorrect.
Scenario
The old security credential is incorrect.
Access Channel
Web
Possible Causes
The old {0} is incorrect.

Copyright © Huawei
Mobile Money
Procedure
8.172 PORTAL90174
Description
The current security credential expires.
Scenario
The current security credential expires.
Access Channel
Web
Possible Causes
The {0} is expired.
Procedure
8.173 PORTAL90175
Description
The security credential length is short.
Scenario
The input security credential length is less than the limit length in the credential policies.
Access Channel
Web
Possible Causes
The {0} length must be greater than or equal to {1}.

Copyright © Huawei
Mobile Money
Procedure
Enter the correct security credential length.
8.174 PORTAL90176
Description
The security credential is long.
Scenario
The input security credential length is greater than the limit length in the credential policies.
Access Channel
Web
Possible Causes
The {0} length must be less than or equal to {1}.
Procedure
Enter the correct security credential length.
8.175 PORTAL90177
Description
The number of digits in the security credential is incorrect.
Scenario
The number of digits in the security credential is incorrect.
Access Channel
Web
Possible Causes
The {0} must contain {1} digital number.
Procedure

Copyright © Huawei
Mobile Money
8.176 PORTAL90178
Description
The number of letters in the credential does not meet the requirement.
Scenario
The number of letters in the credential does not meet the requirement.
Access Channel
Web
Possible Causes
{0} must contain at least {1} letters.
Procedure
8.177 PORTAL90179
Description
The number of special characters in the credential does not meet the requirement.
Scenario
The number of special characters in the credential does not meet the requirement.
Access Channel
Web
Possible Causes
{0} must contain at least {1} special characters.
Procedure

Copyright © Huawei
Mobile Money
8.178 PORTAL90180
Description
The number of uppercase letters in the credential does not meet the requirement.
Scenario
The number of uppercase letters in the credential does not meet the requirement.
Access Channel
Web
Possible Causes
{0} must contain at least {1} uppercase letters.
Procedure
8.179 PORTAL90181
Description
The configuration file is incorrect.
Scenario
The spring configuration file is incorrect.
Access Channel
Web
Possible Causes
The security credential management interface cannot be found.
Procedure

Copyright © Huawei
Mobile Money
8.180 PORTAL90182
Description
Scenario
Access Channel
Web
Possible Causes
The format of {0} is incorrect.
Procedure
8.181 PORTAL90183
Description
The credential value contains forbidden characters in the prohibited list.
Scenario
The credential value contains forbidden characters in the prohibited list.
Access Channel
Web
Possible Causes
{0} contains forbidden characters in the credential policies.
Procedure

Copyright © Huawei
Mobile Money
8.182 PORTAL90184
Description
The number of incorrect credential attempts exceeds the upper limit.
Scenario
The number of incorrect credential attempts exceeds the upper limit and the credential has
been locked.
Access Channel
Web
Possible Causes
{0} has been locked.
Procedure
Wait for 30 minutes and try again.
8.183 PORTAL90185
Description
The credential is in the pending state and cannot perform any operations.
Scenario
The credential is in the pending state and cannot perform any operations.
Access Channel
Web
Possible Causes
{0} is in the pending state.
Procedure

Copyright © Huawei
Mobile Money
8.184 PORTAL90186
Description
The credential cannot contain two duplicate characters.
Scenario
The credential cannot contain two duplicate characters.
Access Channel
Web
Possible Causes
The {0} cannot contain two duplicate characters.
Procedure
8.185 PORTAL90187
Description
Scenario
Access Channel
Web
Possible Causes
The {0} must be different from historical ones.
Procedure

Copyright © Huawei
Mobile Money
8.186 PORTAL90188
Description
The {0} is being changed too frequently. Please try again later.
Scenario
The credential is being changed too frequently.
Access Channel
Web
Possible Causes
The {0} is being changed too frequently.
Procedure
Please try again later.
8.187 PORTAL90189
Description
The credential value is the same as the user name or the inverted user name.
Scenario
The credential value is the same as the user name or the inverted user name.
Access Channel
Web
Possible Causes
The {0} must be different from the user name or the inverted user name.
Procedure

Copyright © Huawei
Mobile Money
8.188 PORTAL90190
Description
The number of credential lines to be imported to the blacklist exceeds the upper limit.
Scenario
The number of credential lines to be imported to the blacklist exceeds the upper limit.
Access Channel
Web
Possible Causes
The number of lines in the {0} credential blacklist cannot exceed {1}.
Procedure
Verify that the number of lines does not exceed the upper limit.
8.189 PORTAL90191
Description
Your password will be locked if another password attempt fails.
Scenario
The last password attempt is allowed.
Access Channel
Web
Possible Causes
The last password attempt is allowed.
Procedure
Enter the correct password.

Copyright © Huawei
Mobile Money
8.190 PORTAL90192
Description
Your password is locked.
Scenario
The number of password attempts has reached the upper limit and the password is locked.
Access Channel
Web
Possible Causes
The number of password attempts has reached the upper limit.
Procedure
Ask the system administrator to unlock the password.
8.191 PORTAL90193
Description
{1} of {0} is not found.
Scenario
No credential is found.
Access Channel
Web
Possible Causes
Operation failed because no credential is found.
Procedure

Copyright © Huawei
Mobile Money
8.192 PORTAL90194
Description
Operation failed because no credential is found.
Scenario
Access Channel
Web
Possible Causes
Procedure
8.193 PORTAL90195
Description
The {0} is already unlocked.
Scenario
The system prompts that the credential is already unlocked, and does not need to be unlocked
again.
Access Channel
Web
Possible Causes
The credential is already unlocked, and does not need to be unlocked again.
Procedure
Verify whether the security credential is in the unlocked state.

Copyright © Huawei
Mobile Money
8.194 PORTAL90196
Description
The {0} is already locked.
Scenario
The system prompts that the credential is already locked, and does not need to be locked
again.
Access Channel
Web
Possible Causes
The credential is already locked, and does not need to be locked again.
Procedure
Verify whether the security credential is in the locked state.
8.195 PORTAL90197
Description
Failed to generate security credentials.
Scenario
The number of times for generating security credentials exceeds 1000, but no valid security
credential is generated.
Access Channel
Web
Possible Causes
The number of times for generating security credentials exceeds 1000, but no valid security
credential is generated.
Procedure
1. Log in to the SP portal as the system admin user.
3. Check whether the blacklist contains all digits ranging from 0 to 9, and delete
unnecessary digits. Regenerate security credentials.

Copyright © Huawei
Mobile Money
8.196 PORTAL90198
Description
Login failed. The account is not in the Active state.
Scenario
The identity login failed because the status of the account is not pending active or active.
Access Channel
Web
Possible Causes
The status of your account {0} is {1}. Only the activated accounts or the accounts waiting to
be activated can log in.
Procedure
Contact customer service representatives to update account status.
8.197 PORTAL90199
Description
The verification of the digital certificate fails.
Scenario
The digital certificate is suspended and the verification fails.
Access Channel
Web
Possible Causes
The digital certificate is suspended and the verification fails.
Procedure
Contact customer service representatives to update certificate status.

Copyright © Huawei
Mobile Money
8.198 PORTAL90200
Description
Scenario
Access Channel
Web
Possible Causes
Procedure
Contact customer service representatives to obtain the correct digital certificate.
8.199 PORTAL90201
Description
Scenario
Failed to obtain the digital certificate from the browser.
Access Channel
Web
Possible Causes
Failed to obtain the digital certificate from the browser.
Procedure
Use Internet Explorer 8.0, Chrome 2X, or later.

Copyright © Huawei
Mobile Money
8.200 PORTAL90202
Description
Your PIN will be locked if another PIN attempt fails.
Scenario
The last PIN attempt is allowed.
Access Channel
Web
Possible Causes
The number of consecutive PIN attempts is {0}.
Procedure
8.201 PORTAL90203
Description
Your digital certificate has been revoked.
Scenario
The digital certificate to be queried has been revoked.
Access Channel
Web
Possible Causes
Your digital certificate expires.
Procedure
Contact customer service representatives to obtain a new digital certificate.

Copyright © Huawei
Mobile Money
8.202 PORTAL90204
Description
Failed to delete the key.
Scenario
Failed to delete the API Initiator Key.
Access Channel
Web
Possible Causes
The system database is abnormal.
Procedure
8.203 PORTAL90205
Description
An error occurs in the query.
Scenario
No API Initiator Key is found.
Access Channel
Web
Possible Causes
The system database is abnormal.
Procedure

Copyright © Huawei
Mobile Money
8.204 PORTAL90206
Description
Failed to verify the identity.
Scenario
The identity credential cannot be found.
Access Channel
Web
Possible Causes
The identity credential cannot be found.
Procedure
Ensure that your identity credential is valid. Any doubts, contact customer service
representatives.
8.205 PORTAL90207
Description
Failed to add the identity credential.
Scenario
The organization already has the identity credential. One organization has only one identity
credential.
Access Channel
Web
Possible Causes
The organization has the identity credential. One organization has only one identity credential.
Procedure
Delete the original identity credential of the organization and add a new credential.

Copyright © Huawei
Mobile Money
8.206 PORTAL90208
Description
The login fails.
Scenario
Only activated organizations can log in.
Access Channel
Web
Possible Causes
The status of your organization {0} is {1}. Only activated organizations can log in.
Procedure
Contact customer service representatives to change organization status.
8.207 PORTAL90209
Description
The {1} {0} is in the incorrect state and not allowed to perform this operation.
Scenario
The state is incorrect when executing the operation.
Access Channel
Web
Possible Causes
The {1} {0} is in the {2} state and cannot perform this operation.
Procedure
Check the status of {1} {0} and change the status as necessary.

Copyright © Huawei
Mobile Money
8.208 PORTAL90210
Description
Failed to add the secret word.
Scenario
The secret word already exists.
Access Channel
Web
Possible Causes
The secret word already exists.
Procedure
Change the secret word to be added.
8.209 PORTAL90211
Description
The {0} is in an invalid state and not allowed to change the account or account rule profile.
Scenario
1. The account is in New or Closed state when changing the account of the customer or
organization. 2. The account is in New or Closed state when changing the account rule profile
of the customer or organization.
Access Channel
Web
Possible Causes
The {0} is in the {1} state and not allowed to change the account or account rule profile.
Procedure
Check the status of {0} and change the status as necessary.

Copyright © Huawei
Mobile Money
8.210 PORTAL90212
Description
The {0} is in an invalid state and not allowed to perform this operation.
Scenario
The security credential is in an invalid state and not allowed to perform this operation.
Access Channel
Web
Possible Causes
The {0} is in the {1} state and cannot perform this operation.
Procedure
Check the status of {0} and change the status as necessary.
8.211 PORTAL90213
Description
The security policy is incorrect.
Scenario
Access Channel
Web
Possible Causes
Min.Length must be set to a value greater than 1 during security policy configuration.
Procedure
Set Min.Length again.

Copyright © Huawei
Mobile Money
8.212 PORTAL90214
Description
Scenario
Access Channel
Web
Possible Causes
Min.Length must not be greater than Max.Length during security policy configuration.
Procedure
Set Min.Length and Max.Length for the security policy again.
8.213 PORTAL90215
Description
Scenario
Access Channel
Web
Possible Causes
The sum of Min.Numeric, Min.Alphabetic, and Min.Special must not be greater than
Min.Length during security policy configuration.
Procedure
Set Min.Numeric, Min.Alphabetic, Min.Special, and Min.Length for the security policy again.

Copyright © Huawei
Mobile Money
8.214 PORTAL90216
Description
Scenario
Access Channel
Web
Possible Causes
Min.Uppercase must not be greater than Min.Alphabetic during security policy configuration.
Procedure
Set Min.Uppercase and Min.Alphabetic again.
8.215 PORTAL90217
Description
An encryption error has occurred.
Scenario
Access Channel
Web
Possible Causes
 An encryption error occurred when a new password is generated.
 An encryption exception occurred during password verification.
Procedure

Copyright © Huawei
Mobile Money
8.216 PORTAL90218
Description
Scenario
Access Channel
Web
Possible Causes
Min.Uppercase must not be greater than Min.Length during security policy configuration.
Procedure
Set Min.Uppercase and Min.Length again.
8.217 PORTAL90219
Description
The {0} product is not found.
Scenario
No product is found based on the product ID during product subscription.
Access Channel
Web
Possible Causes
No product is found based on the {0} product ID during product subscription.
Procedure

Copyright © Huawei
Mobile Money
8.218 PORTAL90220
Description
The {0} identity is not allowed to subscribe to the product.
Scenario
1. The product to be subscribed for the till does not belong to the organization product
subscription range. 2. The identity is not allowed to subscribe to this product.
Access Channel
Web
Possible Causes
 The product to be subscribed for the till does not belong to the organization product
subscription range.
 The identity is not allowed to subscribe to this product.
Procedure
8.219 PORTAL90221
Description
The MSISDN is ported out.
Scenario
The MSISDN specified for the till or customer to be created has been ported out.
Access Channel
Web
Possible Causes
 The MSISDN specified for the customer to be created has been ported out.
 The MSISDN specified for the till to be created has been ported out.
Procedure
Enter another MSISDN.

Copyright © Huawei
Mobile Money
8.220 PORTAL90222
Description
Scenario
The input MSISDN is blank or does not exist when verifying the MSISDN.
Access Channel
Web
Possible Causes
Procedure
Check whether the MSISDN is correct.
8.221 PORTAL90223
Description
The new MSISDN of the customer or till is not in the range.
Scenario
The new MSISDN of the customer or till is not in the range.
Access Channel
Web
Possible Causes
Procedure
1. View MSISDN range of the customer or till. Check whether the MSISDN is in the range.
2. If the MSISDN is not in the range, select the MSISDN in the range.elp.

Copyright © Huawei
Mobile Money
8.222 PORTAL90224
Description
The MSISDN does not exist.
Scenario
No device is not found based on the MSISDN which does not exist.
Access Channel
Web
Possible Causes
Procedure
8.223 PORTAL90225
Description
The device whose MSISDN is {0} does not exist.
Scenario
No device is not found based on the MSISDN.
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
8.224 PORTAL90226
Description
Failed to query the identity.
Scenario
The identity does not exist.
Access Channel
Web
Possible Causes
The identity does not exist.
Procedure
1. When activating the identity, check whether the input is correct.
2. The data is incorrect. Contact Huawei engineers.
8.225 PORTAL90227
Description
Scenario
1. When activating the till, the status of the organization to which the till belongs is not
Active. 2. When bulk processing registerby information, the status of the organization is not
Active. 3. When registering customer, the status of the organization is not Active.
Access Channel
Web
Possible Causes
The status of the organization to which the identity belongs must be Active.
Procedure
1. Use an SP operator to access the SP Portal.
2. Choose Search > Till or Search > Customer to access the till or customer search page,
view the identity organization.
3. Choose Search > Organization and check organization status. If the status is not active,
you cannot perform related operations.

Copyright © Huawei
Mobile Money
4. Select an active organization when creating a customer.
8.226 PORTAL90228
Description
Operation failed. The account type cannot be found.
Scenario
Failed to obtain the BANK_LINKED_ACCOUNT_TYPE parameter from the cache.
Access Channel
Web
Possible Causes
Failed to obtain the BANK_LINKED_ACCOUNT_TYPE parameter from the cache.
Procedure
8.227 PORTAL90229
Description
The account is not found.
Scenario
The identity account does not exist.
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
8.228 PORTAL90230
Description
The account whose account type is {1} in identity {0} is not found.
Scenario
The account whose account type is accountTypeName in identity is not found.
Access Channel
Web
Possible Causes
The account whose account type is {1} in identity {0} does not exist.
Procedure
8.229 PORTAL90231
Description
The bank account is not found.
Scenario
The SP control account is not found based on SPID and SP bank card number.
Access Channel
Web
Possible Causes
No account is associated with the SP bank card number.
Procedure

Copyright © Huawei
Mobile Money
8.230 PORTAL90232
Description
The account type is not found.
Scenario
The account type is not found during the account querying.
Access Channel
Web
Possible Causes
Procedure
8.231 PORTAL90233
Description
The bank ID is not found.
Scenario
The bank ID is not found during the bank information querying.
Access Channel
Web
Possible Causes
The bank ID does not exist.
Procedure

Copyright © Huawei
Mobile Money
8.232 PORTAL90234
Description
The account is not found.
Scenario
Access Channel
Web
Possible Causes
Procedure
8.233 PORTAL90235
Description
The identifier for querying the identity is empty.
Scenario
The identifier for querying the identity is empty.
Access Channel
Web
Possible Causes
The identifier to be used as a condition for querying an identity is empty.
Procedure
Enter a valid identifier.

Copyright © Huawei
Mobile Money
8.234 PORTAL90236
Description
Failed to add the language {0}.
Scenario
The language already exists in the system when adding the language.
Access Channel
Web
Possible Causes
The {0} language exists.
Procedure
Choose My functions > Core Configuration > Language to check whether the {0} language
exists. If the language exists, change the language name.
8.235 PORTAL90237
Description
Failed to change the language.
Scenario
The system does not support the language specified for changing language by API or bulk
task.
Access Channel
Web
Possible Causes
The system does not support the {0} language.
Procedure
2. Choose My functions > Core Configuration > Language to query the language
supported by the system, and change the language to the language supported by the
system.
3. Click Add to change the language to the language supported by the system.

Copyright © Huawei
Mobile Money
8.236 PORTAL90238
Description
Failed to create the account.
Scenario
The account type does not apply to the identity when creating the account for identity.
Access Channel
Web
Possible Causes
The account type does not apply to the identity.
Procedure
8.237 PORTAL90239
Description
The SP short code is incorrect.
Scenario
The SP short code is incorrect.
Access Channel
Web
Possible Causes
There is only one SP in the system, and the short code is 1.
Procedure
Set the short code to 1.

Copyright © Huawei
Mobile Money
8.238 PORTAL90240
Description
The short code is empty.
Scenario
1. The short code of the business organization to be created is empty. 2. The short code of the
business operator to be queried is empty. 3. The short code of the identity to be queried is
empty.
Access Channel
Web
Possible Causes
 The short code of the business organization to be created is empty.
 The short code of the business operator to be queried is empty.
 The short code of the identity to be queried is empty.
Procedure
8.239 PORTAL90241
Description
Scenario
Access Channel
Web
Possible Causes
Procedure
3. Verify whether the organization exists.

Copyright © Huawei
Mobile Money
If the organization does not exist, you cannot query the status of the organization.
8.240 PORTAL90242
Description
Scenario
The system prompts the parameter is empty during parameter authentication.
Access Channel
Web
Possible Causes
The {0} parameter is mandatory for bulk operations.
Procedure
Enter a valid parameter value. If the problem persists, contact a Huawei engineer for help.
8.241 PORTAL90243
Description
Failed to authenticate the parameter.
Scenario
The input KYC value is invalid.
Access Channel
Web
Possible Causes
The {0} value is invalid.
Procedure
Change the parameter value as required.

Copyright © Huawei
Mobile Money
8.242 PORTAL90244
Description
Failed to delete files in bulk.
Scenario
Failed to delete files in bulk.
Access Channel
Web
Possible Causes
An error occurred during file deletion in bulk.
Procedure
8.243 PORTAL90245
Description
The identity has a voucher not exchanged and therefore cannot be closed.
Scenario
The identity has a voucher not exchanged and therefore cannot be closed.
Access Channel
Web
Possible Causes
The identity has a voucher not exchanged.
Procedure
1. Choose Search > Organization to query for the organization.
2. On the details page, choose Organization Transaction > Initiate Transaction.
3. Exchange the voucher as necessary.

Copyright © Huawei
Mobile Money
8.244 PORTAL90246
Description
The workflow is abnormal.
Scenario
Failed to find a bean.
Access Channel
Web
Possible Causes
Failed to find a bean that matches with {0}.
Procedure
8.245 PORTAL90247
Description
Number recycle or number porting failed.
Scenario
Number recycle or number porting failed.
Access Channel
Web
Possible Causes
The old record is not found during the number recycle or number porting process.
Procedure

Copyright © Huawei
Mobile Money
8.246 PORTAL90248
Description
Number recycle or number porting succeeded.
Scenario
Access Channel
Web
Possible Causes
Procedure
This is not an exception. Number recycle or number porting succeeded.
8.247 PORTAL90249
Description
Failed to create a data extractor.
Scenario
The organization is a data client during creating a data extractor.
Access Channel
Web
Possible Causes
The organization is a data client and cannot function as a data extractor.
Procedure
 Method 1: Select another organization as the data extractor.
 Method 2: Remove the relationship between the organization and the data extractor so
that the organization does not function as a data client.

Copyright © Huawei
Mobile Money
8.248 PORTAL90250
Description
Failed to create a data client.
Scenario
The organization is a data client during creating a data client.
Access Channel
Web
Possible Causes
The organization is a data client and has created the relationships with the data extractor {0}.
Procedure
Remove the relationships between the organization and the data extractor {0} and create the
organization as a data client.
8.249 PORTAL90251
Description
Failed to create a data client.
Scenario
The organization is a data extractor during creating a data client.
Access Channel
Web
Possible Causes
The organization is a data extractor and cannot function as a data client.
Procedure
Select another organization as a data client.

Copyright © Huawei
Mobile Money
8.250 PORTAL90252
Description
The number is already recycled and cannot be recycled again.
Scenario
Access Channel
Web
Possible Causes
Procedure
The number is already recycled. Do not recycle it again.
8.251 PORTAL90253
Description
Scenario
The organization is a data extractor during creating a data extractor.
Access Channel
Web
Possible Causes
The organization is a data extractor and cannot function as a data extractor.
Procedure
Select another organization to function as a data extractor.

Copyright © Huawei
Mobile Money
8.252 PORTAL90254
Description
The task fails to be initiated.
Scenario
The system initiates the task, no default initiator is found when recording audit logs.
Access Channel
Web
Possible Causes
No default initiator is found when recording audit logs.
Procedure
Transaction.
2. Verify whether an initiator is correctly configured for the SP Operator Initiating
Transaction. If no, configure information as required.
8.253 PORTAL90255
Description
Failed to update data client status.
Scenario
The new status of the data client is the same as the original status when updating data client
status.
Access Channel
Web
Possible Causes
The new status of the data client is the same as the original status.
Procedure
Select another state.

Copyright © Huawei
Mobile Money
8.254 PORTAL90256
Description
The Name, Short Code, Operator ID, or Till Number specified for a new operator or till does
not comply with the regular expression rule.
Scenario
The Name or Operator ID, specified for a new operator or till does not comply with the
regular expression rule.
Access Channel
Web
Possible Causes
{0} does not comply with regular expression rule {1}.
Procedure
1. Choose My Functions > Operational Configuration > System Parameter and enter
the Operator Parameters or Till Parameters configuration page.
2. Check the regular expression rules configured in Validation Rule of Operator ID,
Validation Rule of User Name, and Validation Rule of Till Number.
3. Modify the Name, Short Code, Operator ID, or Till Number fields based on the regular
expression rule.
8.255 PORTAL90257
Description
Scenario
The data client specified for a new data extractor is duplicate.
Access Channel
Web
Possible Causes
The data extractor has duplicate data clients.
Procedure
Remove a duplicate data client.

Copyright © Huawei
Mobile Money
8.256 PORTAL90258
Description
The region name already exists.
Scenario
The region name already exists when creating region infomation.
Access Channel
Web
Possible Causes
The region name already exists.
Procedure
Change the region name to a name that does not exist.
8.257 PORTAL90259
Description
Failed to create the region because the number of region levels exceeds the upper limit.
Scenario
The number of region levels exceeds the upper limit.
Access Channel
Web
Possible Causes
The number of region levels exceeds the upper limit.
Procedure
Change the level of the region to ensure that the maximum number of levels do not exceed 5.

Copyright © Huawei
Mobile Money
8.258 PORTAL90260
Description
Failed to create or query the bank.
Scenario
The details of the bank that is created or to be queried are empty.
Access Channel
Web
Possible Causes
The details of the bank that is created or to be queried are empty.
Procedure
8.259 PORTAL90261
Description
Failed to query the bank card or control account.
Scenario
The bank card ID of the bank card or control account to be queried is empty.
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
8.260 PORTAL90262
Description
Failed to query the bank card information by account number.
Scenario
Access Channel
Web
Possible Causes
The account number of the bank card to be queried is empty.
Procedure
8.261 PORTAL90263
Description
Failed to add the number segment.
Scenario
The number segment to be added overlaps with an existing number segment.
Access Channel
Web
Possible Causes
 A number segment to be added for registered customers overlaps with an existing
number segment for registered customers.
 A number segment to be added for unregistered or Lite customers overlaps with an
existing number segment for unregistered or Lite customers.
Procedure
 Modify the number segment to be added for registered customers so that it does not
overlap with any existing number segments for registered customers.
 Modify the number segment to be added for unregistered or Lite customers so that it
does not overlap with any existing number segments for unregistered or Lite customers.

Copyright © Huawei
Mobile Money
8.262 PORTAL90264
Description
The organization fails to subscribe to the product.
Scenario
The shared account does not exist in the parent organization.
Access Channel
Web
Possible Causes
The shared account {0} is generated from {1} but does not exist in the parent organization.
Procedure
Select another product for subscription.
8.263 PORTAL90266
Description
An error occurs when the role is deleted.
Scenario
The role status is incorrect.
Access Channel
Web
Possible Causes
The role status is incorrect. Only the role in the draft state can be deleted.
Procedure
Discard this operation.

Copyright © Huawei
Mobile Money
8.264 PORTAL90267
Description
The security verification fails.
Scenario
You have not permission to access Web or Handset.
Access Channel
Web
Possible Causes
You have not permission to access {0}.
Procedure
Use the correct access channel to use the system.
8.265 PORTAL90269
Description
System is busy.
Scenario
System is busy, please try again later.
Access Channel
Web
Possible Causes
System is busy.
Procedure
Please try again later.

Copyright © Huawei
Mobile Money
8.266 PORTAL90271
Description
The transaction type is used by another voucher type.
Scenario
The transaction type selected when a voucher type is added or modified is used by another
voucher type.
Access Channel
Web
Possible Causes
The transaction type is in use.
Procedure
Select a transaction type that is not in use.
8.267 PORTAL90272
Description
The expiration time of the workflow must be later than the expiration time of all its tasks.
Scenario
Access Channel
Web
Possible Causes
Procedure
 Modify the expiration time of the workflow.
 Modify the expiration time of the task.

Copyright © Huawei
Mobile Money
8.268 PORTAL90273
Description
Scenario
Connect SFTP failed,please check system config.
Access Channel
Web
Possible Causes
SFTP configuration information is incorrect.
Procedure
Parameters.
8.269 PORTAL90274
Description
Failed to download the SFTP file.
Scenario
Failed to download the SFTP file.
Access Channel
Web
Possible Causes
SFTP file downloading path is incorrect.
Procedure
Please check whether the SFTP file downloading path is correct.

Copyright © Huawei
Mobile Money
8.270 PORTAL90275
Description
Failed to query log repository.
Scenario
Failed to query log repository.
Access Channel
Web
Possible Causes
Log warehouse path exception.
Procedure
Please check whether the log repository is normal.
8.271 PORTAL90276
Description
Failed to upload bulk task file. The bulk file size exceeds the maximum.
Scenario
Bulk task file upload fail.
Access Channel
Web
Possible Causes
Procedure
Verify that the bulk file size does not exceed the maximum configured in the Max. File Size
system parameter.

Copyright © Huawei
Mobile Money
8.272 PORTAL90277
Description
The status returned by the third-party RPC is {0}.
Scenario
The status returned by the third-party RPC is incorrect.
Access Channel
Web
Possible Causes
The status returned by the third-party RPC is incorrect.
Procedure
8.273 PORTAL90278
Description
All system parameters must be correctly configured.
Scenario
A system parameter is not configured during the commission roll-up process.
Access Channel
Web
Possible Causes
A system parameter related to commission roll-up is not configured.
Procedure
Commission Reason Type to enter the system parameter configuration page.
2. Set Commission Reason Type to a correct value.

Copyright © Huawei
Mobile Money
8.274 PORTAL90279
Description
Get preview results failed.
Scenario
Channel configuration information is missing.
Access Channel
Web
Possible Causes
Channel configuration information is missing.
Procedure
Please complete the priority channel configuration information.
8.275 PORTAL90280
Description
An unknown exception has occurred.
Scenario
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
8.276 PORTAL90281
Description
The identity cannot be registered because the age is lower than the minimum age required by
local laws.
Scenario
When a customer, organization, or operator is created, the existing CNIC information in the
system is directly used, and if the age of the identity is lower than the minimum age required
by local laws, the system prompts this error.
Access Channel
Web
Possible Causes
The registered age is lower than the minimum age required by local laws.
Procedure
Enter a valid date of birth.
8.277 PORTAL90282
Description
Operation failed because a parameter is invalid.
Scenario
The data has been tampered in the transmission process.
Access Channel
Web
Possible Causes
Parameter {0} is invalid.
The {0} variable indicates the name of an invalid parameter.
Procedure
 Check whether the network is properly connected.
 Try to submit the data in another operation environment.

Copyright © Huawei
Mobile Money
8.278 PORTAL90283
Description
The current configuration references an inactive configuration item {0} whose name is {1}.
{0}: indicates a configuration item, such as transaction type.

{1}: indicates the name of a configuration item, such as send money.
Scenario
A configuration item to be released references another configuration item in the Inactive state.
Access Channel
Web
Possible Causes
The current configuration references a configuration item in the Inactive state.
Procedure
Update the status of the configuration item that is referenced.
8.279 PORTAL90284
Description
Dates in the conditions must be unique.
Scenario
When conditions for updating the DOB are configured, dates conditions must be unique.
Access Channel
Web
Possible Causes
Dates in the conditions must be unique.
Procedure
Modify dates in conditions for updating the DOB.

Copyright © Huawei
Mobile Money
8.280 PORTAL90285
Description
Duplicate routes are added.
Scenario
The routes to be added contain duplicate routes.
Access Channel
Web
Possible Causes
Duplicate routes are added.
Procedure
Verify that routes to be added are unique.
8.281 PORTAL90286
Description
There are duplicate message queue names.
Scenario
There are duplicate message queue names when message queues are added or updated.
Access Channel
Web
Possible Causes
There are duplicate message queue names.
Procedure
Verify that message queue names are unique.

Copyright © Huawei
Mobile Money
8.282 PORTAL90287
Description
Failed to activate the license file.
Scenario
The license file to be activated does not exist or does not meet the activation conditions.
Access Channel
Web
Possible Causes
The license file does not exist or does not meet the activation conditions.
Procedure
Verify that the license file exists and meets the activation conditions.
8.283 PORTAL90288
Description
Failed to deactivate the license file.
Scenario
The license file to be deactivated does not exist or does not meet the deactivation conditions.
Access Channel
Web
Possible Causes
The license file does not exist or does not meet the deactivation conditions.
Procedure
Verify that the license file exists and meets the deactivation conditions.

Copyright © Huawei
Mobile Money
8.284 PORTAL90289
Description
Failed to obtain the invalid code of the license file.
Scenario
The license file for which an invalid code is to be obtained does not exist or is not in the
deactivated state.
Access Channel
Web
Possible Causes
The license file does not exist or is not in the deactivated state.
Procedure
Verify that the license file exists and is in the deactivated state.
8.285 PORTAL90290
Description
Failed to download a log file for statement import and export operations.
Scenario
Failed to download a log file for statement import and export operations because the file does
not exist in the specified directory.
Access Channel
Web
Possible Causes
The log file does not exist in the specified directory.
Procedure
Verify that the log file exists in the specified directory.

Copyright © Huawei
Mobile Money
8.286 PORTAL90291
Description
The selected original reason type can be associated with only one reversal reason type of a
specific channel and reversal mode.
Scenario
When a reversal reason type is added or modified, the specified original reason type has been
associated with another reversal reason type with the same channel and reversal mode.
Access Channel
Web
Possible Causes
The selected original reason type has been associated with another reversal reason type of the
same channel and reversal mode.
Procedure
Select another original reason type, channel, or reversal mode.
8.287 PORTAL90292
Description
The content of the uploaded file does not match with the content download template.
Scenario
The file content of the PIN blacklist to be uploaded does not meet the format required in the
template, and cannot be recognized by the system.
Access Channel
Web
Possible Causes
The content of the uploaded file does not meet the format requirement.
Procedure
2. Click Download Template to download the template and verify that the content of the
uploaded file meets the format required in the template.

Copyright © Huawei
Mobile Money
8.288 PORTAL90299
Description
An export or import task is being executed on the background, and the task of the same type
cannot be created.
Scenario
When an operator chooses My Functions > Operation Support > Business Configuration Data
Management and then selects Configuration Data Import or Business Configuration Data
Export to import or export tasks, the system reports this error if there is a task being processed
at the background.
Access Channel
Web
Possible Causes
An export or import task is being executed on the background, and the task of the same type
cannot be created.
Procedure
Initiate the task request after the export or import task that is being executed ends.
8.289 PORTAL90300
Description
The {0} table structure of the import data is different from that of the local database.
{0} indicates the table name.
Scenario
Management > Business Configuration Data Import to import configuration data, the system
reports this error if the table to be imported and the current system table have different
structures.
Access Channel
Web
Possible Causes
The {0} table structure of the import data is different from that of the local database.

Copyright © Huawei
Mobile Money
Procedure
Verify that the table structure of the import data is the same as that of the local database.
8.290 PORTAL90301
Description
Scenario
Management > Business Configuration Data Import to import configuration data, the system
reports this error if the portal fails to invoke a workflow to generate an approval task.
Access Channel
Web
Possible Causes
Procedure
Check whether the workflow NE is normally started.
8.291 PORTAL90302
Description
Failed to import the configuration data task.
Scenario
Management > Business Configuration Data Import to import configuration data, the task
fails.
Access Channel
Web
Possible Causes
Failed to import the configuration data task.

Copyright © Huawei
Mobile Money
Procedure
 Check whether the name of the compression package of the latest import success task is
the same as that of the compression package to be uploaded.
 Check whether the name of the compression package is the same as the name of the
excel file in the compression package.
 Check whether the number of sheets in the excel table in the compression package is the
same as the number of sheets to be imported to the database.
8.292 PORTAL90303
Description
Scenario
Management > Business Configuration Data Import to import configuration data, the approval
task is rejected because the workflow has been enabled.
Access Channel
Web
Possible Causes
Procedure
1. Log in to the portal as an SP operator and choose My Tasks > Group Task.
2. Check and approve the task.
8.293 PORTAL90304
Description
Failed to export the configuration data task.
Scenario
Management > Business Configuration Data Export to export configuration data, the task
fails.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
Failed to export the configuration data task.
Procedure
1. Check whether the SFTP upload path is correct.
2. Check whether the primary key of the database table to be exported exists.
8.294 PORTAL90305
Description
The global TPS is less than the TPS of one or multiple time slots.
Scenario
Choose My Functions > Operation Support > Bulk Configuration to modify the configuration
data. The system reports this error if the global TPS is less than the TPS of one or multiple
time slots.
Access Channel
Web
Possible Causes
The global TPS is less than the TPS of one or multiple time slots.
Procedure
The global TPS must be greater than TPS configurations for each time slot. Choose My
Functions > Operation Support > Bulk Configuration to modify the configuration data.
8.295 PORTAL90308
Description
The current data record does not exist.
Scenario
When an SP or organization operator views or modifies a data record on the web portal, the
data record has been deleted by another operator.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The current data record has been deleted.
Procedure
Verify whether the data record has been deleted.
8.296 PORTAL90311
Description
The uploaded template file does not meet the verification rules.
Scenario
An xml file uploaded failed the xsd verification.
Access Channel
Web
Possible Causes
The uploaded template file does not meet the verification rules.
Procedure
Upload a template file that meets the verification rules.
8.297 PORTAL90312
Description
The notification type to be imported already has a draft version and cannot be imported.
Scenario
The GUI displays an error when an operator chooses My Functions > Operational
Configuration > Notification Configuration > Notification Type to import a notification that
already exists in the system.
Access Channel
Web
Possible Causes
The notification type to be imported already has a draft version and cannot be imported.

Copyright © Huawei
Mobile Money
Procedure
Check whether the same record already exists in the system.
8.298 PORTAL90313
Description
The entrusted operator cannot be the self only.
Scenario
When entrusting a task in the My To-Do menu, an operator entrusts a task to only the self.
Access Channel
Web
Possible Causes
The entrusted operator cannot be the self only.
Procedure
Select another entrusted operator.
8.299 PORTAL90319
Description
A task that is rejected for modification can be processed only by the task initiator, and cannot
be delegated to others.
Scenario
An operator entrusts a task rejected for modification in the My To-Do menu to an operator
other than the task initiator.
Access Channel
Web
Possible Causes
A task that is rejected for modification cannot be delegated.

Copyright © Huawei
Mobile Money
Procedure
A task that is rejected for modification cannot be delegated. Select another task that can be
delegated.
8.300 PORTAL90320
Description
The entity is already in the draft state.
Scenario
The new version operation has been performed by another operator.
Access Channel
Web
Possible Causes
The entity is already in the draft state.
Procedure
Operation error, do not add the same draft entity.
8.301 PORTAL90321
Description
The system parameter Claw-back Reason Type is not configured.
Scenario
The system parameter Claw-back Reason Type is not configured on the My Functions >
Finance > Commission Claw-back > Claw-back from Transaction page.
Access Channel
Web
Possible Causes
The system parameter Claw-back Reason Type is not configured.

Copyright © Huawei
Mobile Money
Procedure
Choose My Functions > Operational Configuration > System Parameter > Commission
Reason Type and configure the correct system parameter.
8.302 PORTAL90328
Description
The resending rule to be processed does not exist.
Scenario
Before an SP operator submits a request for modifying or deleting a resending rule, another
operator has modified or deleted the rule.
Access Channel
Web
Possible Causes
The resending rule does not exist.
Procedure
Query for resending rules again.
8.303 PORTAL90329
Description
The configuration item has two effective versions both in the Released state. No new version
can be added.
Scenario
An operator creates a new version for a configuration item that has two effective versions
both in the Released state.
Access Channel
Web
Possible Causes
The configuration item has two effective versions both in the Released state.

Copyright © Huawei
Mobile Money
Procedure
Click the Inactive icon in the Operation column of the released version that last takes effect to
modify the version status, and create a new version again.
8.304 PORTAL90330
Description
The version that first takes effect cannot be deactivated.
Scenario
An operator deactivates the released version with a smaller version number for a
configuration item that has two versions in the Released state.
Access Channel
Web
Possible Causes
The version to be deactivated for the configuration item is the version that first takes effect.
Procedure
Deactivate the version that last takes effect.
8.305 PORTAL90331
Description
Failed to modify the role information.
Scenario
Before an SP operator submits a request for modifying a role, another operator has submitted
a request for modifying the role.
Access Channel
Web
Possible Causes
The role is modified by another operator.

Copyright © Huawei
Mobile Money
Procedure
Query the role information again before modifying and saving the role information.
8.306 PORTAL90332
Description
Scenario
Before an SP operator submits a request for modifying a role, another operator has deleted the
role.
Access Channel
Web
Possible Causes
The role is deleted by another operator.
Procedure
The role is deleted and cannot be modified.
8.307 PORTAL90333
Description
Scenario
Before an SP operator submits a request for modifying a role, another operator has released
the role.
Access Channel
Web
Possible Causes
The role status is modified by another operator.
Procedure

Copyright © Huawei
Mobile Money
8.308 PORTAL90334
Description
Failed to create the task. You must select at least one product to be assigned or removed.
Scenario
When an operator chooses My Functions > Operations > Time Triggered Product Allocation >
Task Plan to create a task for modifying or adding products to be assigned or removed, the
buttons on the right side of Product to be Assigned and Product to be Removed are set to OFF.
Access Channel
Web
Possible Causes
No product is selected when products are assigned or removed.
Procedure
Select at least one product to be assigned or removed.
1. Click the button on the right side of Product to be Assigned or Product to be Removed
to change it to ON.
2. Click the Confirm button and select products to be assigned or removed from the
Available area box.
8.309 PORTAL90335
Description
There is no valid identity information.
Scenario
Choose My Functions > Operations > Time Triggered Product Allocation > Task Plan to
create or modify a task and click Obtain to obtain identity information.
Access Channel
Web
Possible Causes
There is no valid identity information.

Copyright © Huawei
Mobile Money
Procedure
Reset the query conditions to query for identity information.
8.310 PORTAL90336
Description
Only tasks in the Running state can be suspended.
Scenario
Choose My Functions > Operations > Time Triggered Product Allocation > Task Plan to enter
the Task Plan page, select a task in the Suspended state, and click the Suspend button.
Access Channel
Web
Possible Causes
The selected tasks include a task which is in the Suspended state and cannot be suspended
again.
Procedure
Select tasks in the Running state.
8.311 PORTAL90337
Description
Only tasks in the Suspended state can be resumed.
Scenario
Choose My Functions > Operations > Time Triggered Product Allocation > Task Plan to enter
the Task Plan page, select a task in the Running state, and click the Resume button.
Access Channel
Web
Possible Causes
The selected tasks include a task which is in the Running state and cannot be resumed again.

Copyright © Huawei
Mobile Money
Procedure
Select tasks in the Suspended state.
8.312 PORTAL90338
Description
Failed to download the file because the file does not exist on the SFTP server.
Scenario
When a file is manually deleted from the SFTP server, the file fails to be downloaded on the
Business Configuration Data Export page in the My Functions > Operation Support >
Business Configuration Data Management > Business Configuration Data Export menu.
Access Channel
Web
Possible Causes
The file does not exist on the SFTP server.
Procedure
Verify whether the file exists on the SFTP server.
8.313 PORTAL90339
Description
Failed to download the file because it does not exist on the SFTP server or the SFTP
configurations are incorrect.
Scenario
Choose My Functions > Operation Support > Business Configuration Data Management >
Business Configuration Data Export. The system reports this error when a file is downloaded
on the Business Configuration Data Export page because the file does not exist on the SFTP
server or the SFTP configurations are incorrect.
Access Channel
Web
Possible Causes
The file does not exist on the SFTP server or the SFTP configurations are incorrect.

Copyright © Huawei
Mobile Money
Procedure
1. Verify whether the specified file exists on the SFTP server.
Parameters.
8.314 PORTAL90340
Description
Downloaded failed because the directory does not contain a Bank Reconciliation Variance
History file.
Scenario
The Bank Reconciliation Variance History file to be downloaded does not exist in the
specified directory.
Access Channel
Web
Possible Causes
The directory does not contain a Bank Reconciliation Variance History file.
Procedure
Verify that the specified directory contains a Bank Reconciliation Variance History file.
8.315 PORTAL90341
Description
Scenario
When two operators modify or delete the same resending rule at the same time, one of the
operator cannot find the resending rule, and this error is reported.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
Procedure
Query and modify the resending rule again.
8.316 PORTAL90342
Description
The current time is later than the effective time.
Scenario
When an operator releases a configuration version, the effective time expires, and this error is
reported.
Access Channel
Web
Possible Causes
The current time is later than the effective time.
Procedure
Change the effective time and release the version again.
8.317 PORTAL90343
Description
The quoted KYC field {0} is not assigned to the specified identity type {1}.
{0}: KYC field name in the [kyc field name] format.

{1}: name of an identity type.
Scenario
A configuration item quotes a KYC field assigned to an identity type. If the system detects
that a KYC field is not assigned to the specified identity type during verification performed
when the configuration item is released or modified, this error is reported.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The quoted KYC field is not assigned to the specified identity type.
Procedure
2. Select the specified identity type to assign the KYC field to it.
8.318 PORTAL90344
Description
An error is reported when product details are queried.
Scenario
A product in the draft state is to be released, and the approval work flow for releasing the
product expires. After the product is deleted, an error is reported when an operator checks
details about the work flow.
Access Channel
Web
Possible Causes
The product does not exist or is deleted.
Procedure
Choose My Functions > Core Configuration > Advanced Configuration > Product and
check whether the product exists.
8.319 PORTAL90345
Description
Failed to upload the file.
Scenario
This error occurs if the content length of the file to be uploaded exceeds the length required
by the database.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The file content exceeds the length upper limit.
Procedure
Check whether the file size meets the system requirements.
8.320 PORTAL90346
Description
Failed to import an excel file.
Scenario
The content in an imported file contains a blank value. If the verification fails, this error code
occurs on this page.
Access Channel
Web
Possible Causes
No value is contained in row {2} column {3} in sheet {0} of the excel file.
Procedure
Modify file content and upload the file again.
8.321 PORTAL90347
Description
Scenario
The content in an imported file contains invalid special characters. If the verification fails, this
error code occurs on this page.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
In sheet {0} of the excel file, invalid characters exist in row {2} column {3}. This cell cannot
contain {4}.
Procedure
Delete invalid characters and upload the file again.
8.322 PORTAL90348
Description
Scenario
The field length in the imported Excel file is greater than the maximum length. If the
verification fails, this error code occurs on this page.
Access Channel
Web
Possible Causes
The field value length in row {2} column {3} in sheet {0} of the excel file exceeds the upper
limit {4}.
Procedure
8.323 PORTAL90349
Description
Scenario
The names of columns in the imported Excel file are incorrect. If the verification fails, this
error code occurs on this page.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
Names of columns in sheet {0} of the excel file are incorrect.
Procedure
Change the names of columns in a file and upload the file again.
8.324 PORTAL90350
Description
Scenario
The imported Excel file is blank. If the verification fails, this error code occurs on this page.
Access Channel
Web
Possible Causes
The imported Excel file is blank.
Procedure
8.325 PORTAL90351
Description
Scenario
The table head in the imported Excel file is blank. If the verification fails, this error code
Access Channel
Web
Possible Causes
Certain headings in sheet {0} of the excel file are left blank.

Copyright © Huawei
Mobile Money
Procedure
8.326 PORTAL90352
Description
Scenario
Access Channel
Web
Possible Causes
In sheet {0} of the excel file, invalid characters exist in row {2} column {3}. This cell can
only contain {4}.
Procedure
8.327 PORTAL90353
Description
Scenario
Access Channel
Web
Possible Causes
In sheet {0} of the excel file, restricted invalid characters exist in row {2} column {3}.

Copyright © Huawei
Mobile Money
Procedure
8.328 PORTAL90354
Description
Only letters, digits, and underscores (_) can be contained in the excel file.
Scenario
Access Channel
Web
Possible Causes
Invalid special characters exsit in the excel file.
Procedure
8.329 PORTAL90355
Description
The Statement Notification Type and EFT Notification Type system parameters are not
configured.
Scenario
This error reports when the Statement Notification Type and EFT Notification Type system
parameters are not configured.
Access Channel
Web
Possible Causes
The Statement Notification Type and EFT Notification Type system parameters are not
configured.

Copyright © Huawei
Mobile Money
Procedure
System Parameter Items > Financial Generic Parameters and configure system
parameters correctly.
8.330 PORTAL90356
Description
The {0} {1} configuration item is deactivated.
{0}: indicates the name of a configuration item.

{1}: indicates the value of a configuration item.
Scenario
This error reports when an inactive configuration item is selected.
Access Channel
Web
Possible Causes
An inactive configuration item is selected.
Procedure
Select a valid {0}.
8.331 PORTAL90357
Description
The name of the file to be uploaded must be different from the file that is successfully
uploaded the last time.
Scenario
Import and export service configuration data.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The name of the file to be uploaded must be different from the file that is successfully
Procedure
Verify that the name of the file to be uploaded is different from the file that is successfully
8.332 PORTAL90358
Description
A table does not have an Excel file, or the zip package to be imported contains redundant
table files.
Scenario
Access Channel
Web
Possible Causes
The versions of the import and export environments are inconsistent.
Procedure
Verify that the versions of the import and export environments are consistent.
8.333 PORTAL90359
Description
The compressed package file does not exist.
Scenario
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The compressed package file does not exist.
Procedure
Verify the source of the import file.
8.334 PORTAL90360
Description
The compressed package file cannot be read.
Scenario
Access Channel
Web
Possible Causes
The compressed package file cannot be read.
Procedure
8.335 PORTAL90361
Description
The name of the compressed package is invalid.
Scenario
Access Channel
Web
Possible Causes
The name of the compressed package is invalid.

Copyright © Huawei
Mobile Money
Procedure
Verify that the compressed package is named in the
CPSSysData_{YYYYMMDDhhmmss}.zip format.
8.336 PORTAL90362
Description
Failed to verify the summary.
Scenario
Access Channel
Web
Possible Causes
The summary is invalid.
Procedure
8.337 PORTAL90363
Description
The selected data whose name is {0} has been referenced by {1} and cannot be deleted.
{0}: indicates the name of manipulated data.

{1}: indicates the name of an outgoing message field.
Scenario
An operator attempts to delete output manipulated data referenced by an outgoing message
field.
Access Channel
Web
Possible Causes
The selected data whose name is {0} has been referenced by {1} and cannot be deleted.

Copyright © Huawei
Mobile Money
Procedure
Select another data to delete or delete the reference relationship of {0}.
8.338 PORTAL90364
Description
The content of the email has exceeded {0} characters and cannot be sent.
Scenario
When creating a manual task for sending an email on the web, an SP operator enters email
content which is longer than the upper limit.
Access Channel
Web
Possible Causes
The content of the email has exceeded {0} characters.
Procedure
Verify that the content of the email does not exceed the upper length limit.
8.339 PORTAL90365
Description
The top organization does not exist or is rejected during approval after being created.
Scenario
An operator creates a child organization immediately after creating a top organization.
Access Channel
Web
Possible Causes
The top organization does not exist.
Procedure
Select an existing top organization.

Copyright © Huawei
Mobile Money
8.340 PORTAL90367
Description
The order is not in the pending authorized state. If you click Approve or Reject, the system
will report an error.
Scenario
Open two browser windows to approve the same transaction on the Review Transaction page.
The system reports this error when the approval operation is performed on the second page.
Access Channel
Web
Possible Causes
The order has been approved by an operator.
Procedure
Refresh the page to check whether the order state has been updated.
8.341 PORTAL90368
Description
Import failed because the system memory is less than {0} MB.
{0} indicates value of the system memory.
Scenario
Management > Business Configuration Data Import to import business configuration data,
import failed because the system memory is insufficient.
Access Channel
Web
Possible Causes
Import failed because the system memory is less than {0} MB.
Procedure
Check whether the system memory is sufficient.

Copyright © Huawei
Mobile Money
8.342 PORTAL90369
Description
The interface code and outbound command of the added record already exists.
Scenario
An outbound URL record to be added already exists.
Access Channel
Web
Possible Causes
The interface code and outbound command of the added record already exists.
Procedure
Verify the interface code and outbound command and add the record again.
8.343 PORTAL90370
Description
The system is in the maintenance state.
Scenario
Management > Business Configuration Data Export to export business configuration data, the
portal NE is interrupted.
Access Channel
Web
Possible Causes
Unexpected interruption occurred during runtime.
Procedure

Copyright © Huawei
Mobile Money
8.344 PORTAL90371
Description
The file fails to be uploaded.
Scenario
The content length of the file to be uploaded is less than the length required by a system
parameter.
Access Channel
Web
Possible Causes
The file content length is outside of the valid range.
Procedure
Verify that the file length meets the system requirement.
8.345 PORTAL90382
Description
The notification receiver fails to be added.
Scenario
A notification receiver to be added by an SP operator already exists.
Access Channel
Web
Possible Causes
Two notification receivers cannot have the same Receiver Type, Receiver Name, and
Notification Type.
Procedure
Verify that the notification receiver to be added is unique.

Copyright © Huawei
Mobile Money
8.346 PORTAL90383
Description
No data permission is assigned to the user for the bulk type.
Scenario
The current user has no permission to view the data.
Access Channel
Web
Possible Causes
No data permission is assigned to the user for the bulk type.
Procedure
2. Add the data permission to the role of the operator.
8.347 PORTAL90384
Description
Operation failed.
Scenario
When certain unavailable controls on the portal are made changeable by modifying browser
elements, the system reports this error when the operation is submitted.
Access Channel
Web
Possible Causes
Illegal operation.
Procedure
Verify that the operation is legal.

Copyright © Huawei
Mobile Money
8.348 PORTAL90386
Description
The Sysadmin role cannot be modified.
Scenario
The Sysadmin role cannot be modified. An operator intercepts an http request using a third-
party tool and attempts to modify a parameter in the request to change the Sysadmin role.
Access Channel
Web
Possible Causes
The Sysadmin Role cannot be modified.
Procedure
Do not modify the Sysadmin role.
8.349 PORTAL90387
Description
Failed to search for customers.
Scenario
When an operator chooses Search > Customer to search for customers, the number of records
in the search result has exceeded the upper limit.
Access Channel
Web
Possible Causes
 The number of records in the search result is {0} and has exceeded the upper limit {1}.
{0}: indicates the number of records in the search result.

{1}: indicates the upper limit on the number of records.
 The system is busy.
Procedure
Use more precise search conditions or please try again later.

Copyright © Huawei
Mobile Money
8.350 PORTAL90388
Description
The value of a parameter is not in the valid value range.
Scenario
When an operator changes a parameter in a request by intercepting an HTTP request, the
parameter value is not in the specified value range.
Access Channel
Web
Possible Causes
The value of a parameter is invalid.
Procedure
Enter a correct parameter value.
8.351 PORTAL90389
Description
Data decryption failed.
Scenario
When a file or data that needs to be decrypted is downloaded, the decryption fails.
Access Channel
Web
Possible Causes
Data decryption failed.
Procedure
Verify the encryption configurations.

Copyright © Huawei
Mobile Money
8.352 PORTAL90390
Description
The {0} transaction type cannot be matched with the transaction type configured in the
system parameter.
Scenario
During account reconciliation, a reconciliation statement cannot be matched with the
transaction type configured in the system parameter.
Access Channel
Web
Possible Causes
An account reconciliation parameter is incorrectly configured.
Procedure
Financial Transactions and verify the reconciliation parameter configurations.
8.353 PORTAL90391
Description
The credential value is the same as the operator ID or the inverted operator ID.
Scenario
Access Channel
Web
Possible Causes
The value of {0} must be different from the operator ID or the inverted operator ID.
The {0} variable indicates the type of a security credential.
Procedure

Copyright © Huawei
Mobile Money
8.354 PORTAL90394
Description
Failed to add the number segment.
Scenario
A number segment to be added does not meet the length requirement.
Access Channel
Web
Possible Causes
The number segment to be added does not meet the length requirement.
Procedure
Verify that the length of the number segment meets the length requirement.
8.355 PORTAL90395
Description
The start number is greater than the end number.
Scenario
When a number segment record is added, the start number is greater than the end number.
Access Channel
Web
Possible Causes
The start number is greater than the end number.
Procedure
Verify that the start number is smaller than the end number.

Copyright © Huawei
Mobile Money
8.356 PORTAL90396
Description
Locking failure. The entry has been locked. Refresh the page and try again.
Scenario
When an operator chooses My Functions > Finance > Bank Reconciliation > New Entries and
then locks the entry, the system reports this error if the entry has been locked by another
operator.
Access Channel
Web
Possible Causes
Procedure
8.357 PORTAL90397
Description
Operation failed.
Scenario
Choose My Functions > Core Configuration > Transaction Type. A transaction type is
referenced by a reason type, and the Allow Reversal to Applied field cannot be modified.
Access Channel
Web
Possible Causes
Illegal operation.
Procedure
The transaction type is referenced by a reason type, and the Allow Reversal to Applied field
cannot be modified.

Copyright © Huawei
Mobile Money
8.358 PORTAL90398
Description
Failed to add the period criterion.
Scenario
When a period criterion is added, the criterion already exists.
Access Channel
Web
Possible Causes
The period criterion to be added already exists.
Procedure
Set the Identity Type or Category field to a different value.
8.359 PORTAL90399
Description
The difference between the start time and the end time cannot be greater than {0} days.
{0} indicates the difference between the start time and the end time, in days.
Scenario
This error is reported when the difference between the start time and the end time selected
during the audit log query exceeds the specified upper limit.
Access Channel
Web
Possible Causes
The difference between the start time and the end time is greater than {0} days.
Procedure
Reselect the start time and end time.

Copyright © Huawei
Mobile Money
8.360 PORTAL90400
Description
Operation failed. The operator does not have the Search permission.
Scenario
An error is reported when an SP operator that has the Take Call permission but does not have
the Search permission attempts to access the customer or organization operator detail page
through the URL under the Search menu.
Access Channel
Web
Possible Causes
The operator does not have the Search permission.
Procedure
Grant the Search permission to the operator.
8.361 PORTAL90404
Description
Download failed due to decryption failure.
Scenario
This error code is generated during the download of files or data that must be decrypted.
Access Channel
Web
Possible Causes
Decrypting files or data failed.
Procedure
Verify that the files or data is correctly configured.

Copyright © Huawei
Mobile Money
8.362 PORTAL90405
Description
Failed to add the MQ node.
Scenario
This error code is generated when the IP address or port specified during the addition of an
MQ node already exists.
Access Channel
Web
Possible Causes
The MQ node already exists.
Procedure
Change the IP address or port.
8.363 PORTAL90406
Description
You do not have the permission to access the web portal.
Scenario
An operator using a non-web channel attempts to log in to the portal.
Access Channel
Web
Possible Causes
An operator using a non-web channel attempts to log in to the portal.
Procedure
Enable the operator to abandon the operation.

Copyright © Huawei
Mobile Money
8.364 PORTAL90407
Description
A duplicate SOAP fault template is added for a same error code.
Scenario
This error code is generated when a duplicate SOAP fault template is added for a same error
code in a SOAP request command.
Access Channel
Web
Possible Causes
A duplicate SOAP fault template is added for a same error code.
Procedure
Select another error code to add a SOAP fault template.
8.365 PORTAL90408
Description
The default SOAP fault template is not added.
Scenario
This error code is generated when the default SOAP fault template is not added for a SOAP
request command.
Access Channel
Web
Possible Causes
The default SOAP fault template is not added.
Procedure
Add a SOAP fault template for the "ALL" error code.

Copyright © Huawei
Mobile Money
8.366 PORTAL90410
Description
Saving customized menu data failed.
Scenario
This error code is generated when an operator saves customized menu data where a menu
node with a blank action is used as a leaf node.
Access Channel
Web
Possible Causes
{0} cannot be saved as a leaf node in customized menu data.
{0} indicates a menu name, for example, Group Task, My To-Do, and Active Task Management.
Procedure
Reconfirm and recustomize menus.
8.367 PORTAL90411
Description
Scenario
This error code is generated when an operator saves customized menu data with a menu level
higher than the allowed maximum menu level (4).
Access Channel
Web
Possible Causes
The level specified for {0} in customized menu data is higher than the allowed maximum
menu level (4).

Copyright © Huawei
Mobile Money
Procedure
8.368 PORTAL90412
Description
Scenario
This error code is generated when an operator saves customized menu data where a menu
node with a blank action is used as a level-2 menu node.
Access Channel
Web
Possible Causes
{0} cannot be saved as a level-2 menu node in customized menu data.
Procedure
8.369 PORTAL90413
Description
Failed to search for customers.
Scenario
When an operator chooses Search > Customer to search for customers, the amount of
customers in the system is too large.
Access Channel
Web
Possible Causes
Overmany customers in the system.

Copyright © Huawei
Mobile Money
Procedure
Use more precise search conditions.
8.370 PORTAL90414
Description
The BTS returns a failure message when the BTS is invoked to execute an import or export
task.
Scenario
The BTS returns a failure message when My Functions > Operation Support > Business
Configuration Data Management > Business Configuration Data Export or My
Functions > Operation Support > Business Configuration Data Management > Business
Configuration Data Import is chosen to invoke the BTS to export or import configuration
data.
Access Channel
Web
Possible Causes
The BTS returns a failure message.
Procedure
1. Verify that the BTS is properly connected.
2. Verify that the database is properly functioning.
3. View BTS logs to analyse failure reasons.
8.371 PORTAL90415
Description
Scenario
This error code is generated if an operator adds a node under a menu node that functions as a
leaf node when the operator saves customized menu data.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
No menu node can be added under {0} in customized menu data to be saved.
Procedure
8.372 PORTAL90416
Description
File uploading fails because an error occurs in the system or the system is busy.
Scenario
Uploading a KYC image file of the picture type fails because the NCSS file server reports an
error.
Access Channel
Web
Possible Causes
The NCSS server is overloaded or incorrectly configured.
Procedure
Verify that NCSS server configurations are correct.
8.373 PORTAL90417
Description
The transaction cannot be {0}.
{0} indicates the canceled or completed state.
Scenario
This error code is generated when you click Cancel or Complete for the canceled or
completed transaction.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The corresponding original tansaction is {1}.
{1} indicates the canceled or completed state.
Procedure
Refresh the transaction list and check the transaction status.
8.374 PORTAL90418
Description
An operator fails to upload an image because the number of times the operator uploads
images exceeds the specified upper limit.
Scenario
An operator fails to upload an image because the number of times the operator uploads
images is large.
Access Channel
Web
Possible Causes
The number of times an operator uploads images is large.
Procedure
Enable the operator to re-log in.
8.375 PORTAL90419
Description
Failed to modify the record information.
Scenario
Before an SP operator submits a request for modifying a record, another operator has
submitted a request for modifying the record.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The record is modified by another operator.
Procedure
Query the record information again before modifying and saving the record information.
8.376 PORTAL90420
Description
Scenario
Before an SP operator submits a request for modifying a record, another operator has deleted
the record.
Access Channel
Web
Possible Causes
The record is deleted by another operator.
Procedure
The record is deleted and cannot be modified.
8.377 PORTAL90421
Description
Scenario
Before an SP operator submits a request for modifying a record, another operator has released
the record.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The record status is modified by another operator.
Procedure
Query the record information again before modifying and saving the record information.
8.378 PORTAL90422
Description
The following organizations' revenue settlement fails: {0}. Check Revenue Settlement
History for more information.
{0} indicates a list of organizations whose revenue settlement fails.
Scenario
An SP operator initiates an organization revenue settlement request on the portal.
Access Channel
Web
Possible Causes
The following organizations' revenue settlement fails: {0}
Procedure
Send portal logs in /log/debug/portal_debug.log to Huawei engineers for fault diagnosis.
8.379 PORTAL90423
Description
The associated product has expired or is in the inactive state.
Scenario
This error code is generated when the product associated with a charge profile has expired or
been deactivated.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The associated product has expired.
Procedure
Configure a product that has not expired and is in the released state.
8.380 PORTAL90424
Description
The SOAP fault template to be deleted has been referenced.
Scenario
This error code is generated when the SOAP fault template to be deleted has been referenced.
Access Channel
Web
Possible Causes
The SOAP fault template to be deleted has been referenced.
Procedure
Do not delete a SOAP fault template that has been referenced.
8.381 PORTAL90425
Description
The value of First Name or Last Name is incorrect.
Scenario
An operator who forgets the password clicks Forgot password? on the login page and resets a
password by answering specified questions.
Access Channel
Web
Possible Causes
The value of First Name or Last Name is incorrect.

Copyright © Huawei
Mobile Money
Procedure
Enable the operator to click Cancel and reset First Name and Last Name.
8.382 PORTAL90426
Description
An error occurs when modifying TEP policy information.
Scenario
When modifying TEP policy information in a reason type transaction template, an SP operator
selects an existing policy or the policy selected by the SP operator contains duplicate receiver
information.
Access Channel
Web
Possible Causes
The SP operator selects an existing policy, or the policy selected by the SP operator contains
duplicate information.
Procedure
Instruct the SP operator not to select an existing policy, or instruct the SP operator to select a
policy that contains no duplicate information.
8.383 PORTAL90427
Description
Failed to delete the rule profile.
Scenario
Before an SP operator submits a request for deleting a rule profile, another operator has
already deleted the rule profile.
Access Channel
Web
Possible Causes
The rule profile is deleted by another operator.

Copyright © Huawei
Mobile Money
Procedure
Query the rule profile again.
8.384 PORTAL90428
Description
Failed to add the TEP receiver.
Scenario
Duplicate TEP receivers added to the TEP sending policy.
Access Channel
Web
Possible Causes
The TEP receiver has been referenced by current TEP sending policy.
Procedure
Select another receiver.
8.385 PORTAL90429
Description
The configuration item version expires, and the new version cannot be added.
Scenario
The configuration item record expires, and the New Version operation is not allowed.
Access Channel
Web
Possible Causes
The configuration item version expires, and the new version cannot be added.
Procedure
Before adding a new version, ensure that the configured version must be in the validity
period.

Copyright © Huawei
Mobile Money
8.386 PORTAL90430
Description
The configuration item version {0} expires, and cannot be released.
{0} and {1} indicate configuration item version ID.
Scenario
The configuration item record expires, and the Release operation is not allowed.
Access Channel
Web
Possible Causes
The configuration item version {0} expires, and the configuration item version {1} cannot be
released.
Procedure
Before releasing the configuration item version {1}, ensure that the configured version {0}
must be in the validity period.
8.387 PORTAL90431
Description
The effective time of the new version must be later than or the same as the current time and
must be greater than the effective time of the old version. If the new version will take effect in
a future time, effective time of the new version must be earlier than or the same as the
expiration time of the old version plus one. If the new version takes effect on the current day,
the effective time of the new version must be earlier than or equal to the current time.
Scenario
Verify the effective date of the new version during a New Version operation on the
Accumulator Configuration page.
Access Channel
Web
Possible Causes

Copyright © Huawei
Mobile Money
Procedure
8.388 PORTAL90432
Description
Failed to add the TEP sending policy.
Scenario
No receiver information is added during the addition of a TEP sending policy.
Access Channel
Web
Possible Causes
No receiver information is added (receiver information is blank) during the addition of a TEP
sending policy.
Procedure
Add receiver information.
8.389 PORTAL90433
Description
Scenario
No parameter information is added during the addition of a TEP sending policy.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
No parameter information is added (parameter information is blank) during the addition of a
TEP sending policy.
Procedure
Add parameter information.
8.390 PORTAL90434
Description
The command ID fails to be deleted.
Scenario
The command ID fails to be deleted because routing information of the command ID already
exists.
Access Channel
Web
Possible Causes
The command ID fails to be deleted because routing information of the command ID already
exists.
Procedure
Delete routing information of the command ID, and then delete the command ID.
8.391 PORTAL90435
Description
The command ID fails to be deleted or modified.
Scenario
The command ID is referenced by TEP or out band, and therefore cannot be deleted or
modified.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The command ID is referenced by TEP or out band, and therefore cannot be deleted or
modified.
Procedure
Delete information of the command ID to be referenced, and then delete the command ID.
8.392 PORTAL90436
Description
Failed to modify the data dictionary.
Scenario
Existing dictionary items do not meet the new verification expression when modifying the
Validation Expression.
Access Channel
Web
Possible Causes
Existing dictionary items do not meet the new verification expression.
Procedure
Verify that the verification expression of Validation Expression after modifying meet the
existing dictionary items.
8.393 PORTAL90437
Description
The template has been referenced and failed to be deleted.
Scenario
This error message is reported when you attempt to delete a bank statement template
referenced by a control account.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The template has been referenced.
Procedure
Ensure that the template is not referenced.
8.394 PORTAL90438
Description
The number segments to be added for the MNO organization overlap with each other or
overlap with an existing number segment.
Scenario
When an operator adds the number segments for the MNO organization, the number segments
to be added overlap with each other or overlap with an existing number segment.
Access Channel
Web
Possible Causes
The number segments to be added for the MNO organization overlap with each other or
overlap with an existing number segment.
Procedure
Add another number segment.
8.395 PORTAL90439
Description
Failed to add a routing rule.
Scenario
The values of Starting Routing and End Routing overlap for the new routing rule of the TEP
sending policy.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The values of Starting Routing and End Routing overlap for the new routing rule of the TEP
sending policy.
Procedure
Check whether the routing rule settings overlap.
8.396 PORTAL90440
Description
Compilation failed.
Scenario
This error is reported when compilation failed due to incorrect content of the rule engine
script.
Access Channel
Web
Possible Causes
The script is incorrect.
Procedure
Modify the script.
8.397 PORTAL90441
Description
The new version operation cannot be performed on an accumulator in inactive state.
Scenario
The new version operation cannot be performed on inactive accumulators regardless of
whether they have multiple versions and whether they have taken effect.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The new version operation cannot be performed on an accumulator in inactive state.
Procedure
Create an accumulator in release state and then perform the new version operation on it.
8.398 PORTAL90442
Description
Failed to add the outbound information.
Scenario
This message is displayed after a record whose Interface Code is empty is inserted when
outbound information is being added.
Access Channel
Web
Possible Causes
A record whose Interface Code is empty cannot be inserted.
Procedure
Set Interface Code and then add the outbound information.
8.399 PORTAL90443
Description
An approval error or rejection error occurs.
Scenario
This error is reported when an organization operator approves or rejects a transaction on the
Review Transaction page because the operator has no permission or the order is not in
Pending Authorized state.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The organization operator has no permission or the order is not in Pending Authorized state.
Procedure
Check the operator permission or order status.
8.400 PORTAL90444
Description
The Excel file fails to be imported.
Scenario
This error is reported when an SP operator imports a multi-language template in which the
sheet name is a name that does not exist.
Access Channel
Web
Possible Causes
The sheet name is incorrect in the Excel file to be imported.
Procedure
Check the sheet name and then upload the file again.
8.401 PORTAL90445
Description
More than 100 configuration items are selected, or the total length of configuration items
exceeds 3500.
Scenario
This error is reported when more than 100 configuration items are selected for creating AML
tasks or the total length of configuration items exceeds 3500.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
More than 100 configuration items are selected, or the total length of configuration items
exceeds 3500.
Procedure
Select less configuration items.
8.402 PORTAL90446
Description
Refund has been executed for the subscriber and cannot be executed again.
Scenario
Access Channel
Web
Possible Causes
Procedure
Contact Huawei technical support.
8.403 PORTAL90447
Description
Query failed because the number of records which you are trying to query may very huge.
Scenario
This error is reported when an operator queries transaction information on the Review
Transaction page and the number of transaction records is excessively large.
Access Channel
Web
Possible Causes
The number of records which you are trying to query may very huge.

Copyright © Huawei
Mobile Money
Procedure
The number of records which you are trying to query may very huge, modify your query time
range, and try later again.
8.404 PORTAL90449
Description
Parameter {0} already exists in the parent parameter {1}.
{0} indicates a sub parameter name.

{1} indicates parent parameter name.
Scenario
This error occurs when a sub parameter is set for a parameter in the GOA template but the sub
parameter already exists in the parent parameter.
Access Channel
Web
Possible Causes
The parameter already exists.
Procedure
Enter a correct parameter name.
8.405 PORTAL90450
Description
Parameter Name is not set.
Scenario
This error occurs in the following scenario: an operator chooses My Functions > Operational
Configuration > API > AG Template Configuration > AG Template > API > GOA, clicks Add
Sub Node next to a level-1 node of the GOA, sets parameters on the Add Parameter page, and
clicks Submit without setting Parameter Name.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
Parameter Name is not set.
Procedure
Set Parameter Name first.
8.406 PORTAL90452
Description
Parameter {0} cannot be left empty when a statement template is added.
Scenario
This error is reported when a parameter is left empty during the addition of a statement
template.
Access Channel
Web
Possible Causes
Parameter {0} is left empty.
Procedure
Enter a valid parameter value. If the fault persists, contact Huawei technical support.
8.407 PORTAL90453
Description
The statement template does not exist.
Scenario
This error is reported when a nonexistent statement template is deleted or modified.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The statement template does not exist.
Procedure
Ensure that the statement template to be deleted or modified exists.
8.408 PORTAL90454
Description
This context must be used in complex mode, and cannot be used in simple mode.
Scenario
An SP operator configures the rule for TC outband messages and selects Simple Mode. The
field drop-down list box under Rule > Transaction > Context has no option. This error is
reported when a subscriber selects the field.
Access Channel
Web
Possible Causes
This context must be used in complex mode, and cannot be used in simple mode.
Procedure
Select other functions.
8.409 PORTAL90455
Description
Scenario
This error is reported when the Max Retry Number or Retry Interval parameter is left empty
during a TEP sending policy addition.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The Max Retry Number or Retry Interval parameter is left empty when a TEP sending
policy is added.
Procedure
Check the Max Retry Number or Retry Interval parameter.
8.410 PORTAL90456
Description
Failed to unsubscribe from the saving plan.
Scenario
This error is reported when no charging rule is configured during saving plan unsubscription.
Access Channel
Web
Possible Causes
No charging rule is configured for saving plan unsubscription.
Procedure
Configure a charging rule.
8.411 PORTAL90457
Description
The length of the imported file content exceeds the maximum.
Scenario
This error is reported when the length of the file content imported during TEP receiver adding
or modification exceeds the database field length.
Access Channel
Web
Possible Causes
The length of the imported file content exceeds the database field length.

Copyright © Huawei
Mobile Money
Procedure
Select another file.
8.412 PORTAL90458
Description
Failed to add the parameter.
Scenario
This error is reported if the parameter added during TEP sending policy modification or
creation is not in the defined data dictionary scope.
Access Channel
Web
Possible Causes
The added parameter {0} is not in the defined data dictionary scope.
Procedure
Ensure that the added parameter is in the defined data dictionary scope.
8.413 PORTAL90459
Description
The Parameters and TEP Receivers for adding a TEP sending policy cannot be left empty.
Scenario
This error is reported if only mandatory fields are setted when an application to add a TEP
sending policy is submitted.
Access Channel
Web
Possible Causes
The Parameters and TEP Receivers for adding a TEP sending policy cannot be left empty.

Copyright © Huawei
Mobile Money
Procedure
Ensure that Parameters and TEP Receivers are not left empty.
8.414 PORTAL90461
Description
The rule configuration record does not exist.
Scenario
This error is reported if an SP performs operation on a non-existent rule configuration record.
Access Channel
Web
Possible Causes
The rule configuration record has been deleted by another operator.
Procedure
Perform the operation on another rule configuration record.
8.415 PORTAL90462
Description
The rule data to be created already exists.
Scenario
This error is reported when an SP operator creates a rule but the corresponding hierarchy level
rule data already exists.
Access Channel
Web
Possible Causes
The corresponding hierarchy level rule has been configured.

Copyright © Huawei
Mobile Money
Procedure
Check whether the selected hierarchy level is correct. If the selected hierarchy level is correct,
access the menu again and check whether the rule data corresponding to the current hierarchy
level is correct.
8.416 PORTAL90463
Description
The Username, Password, Send Username, Send Password, and Key fields must be set.
Scenario
This error is reported when an Outbound Receiver containing GOA messages is added but one
of the Username, Password, Send Username, Send Password, and Key fields is not set.
Access Channel
Web
Possible Causes
One of the Username, Password, Send Username, Send Password, and Key fields is not
set.
Procedure
Verify that the Username, Password, Send Username, Send Password, and Key fields are
all set.
8.417 PORTAL90464
Description
Failed to add or modify the tax code of the new version.
Scenario
This error is reported when the tax code of a new version is added or modified but the tax
dynamic rate information is left empty when Rate Mode is set to Dynamic.
Access Channel
Web
Possible Causes
The tax dynamic rate information is left empty during dynamic taxing.

Copyright © Huawei
Mobile Money
Procedure
Enter the tax dynamic rate information.
8.418 PORTAL90465
Description
The {0} role and the {1} role are mutually exclusive and cannot be assigned to the same
operator.
The {0} and {1} indicate organization operator role names.
Scenario
This error is reported during organization creation in one step when the organization roles
conflict with each other.
Access Channel
Web
Possible Causes
The {0} role and the {1} role are mutually exclusive.
Procedure
Verify that the roles are not mutually exclusive.
8.419 PORTAL90466
Description
A blacklist rule has already been configured for the identity type or the entered identity type is
incorrect.
Scenario
This error is reported when a blacklist rule has already been configured for the identity type or
the entered identity type is incorrect.
Access Channel
Web, USSD

Copyright © Huawei
Mobile Money
Possible Causes
incorrect.
Procedure
8.420 PORTAL90467
Description
The length of the blacklist rule definition is incorrect. The length must ranges from 1 to 2048.
Scenario
This error is reported when the length of the blacklist rule definition is incorrect.
Access Channel
Web, USSD
Possible Causes
The length of the blacklist rule definition is incorrect.
Procedure
Enter the correct rule definition.
8.421 PORTAL90468
Description
Failed to add the receiver routing rule. The routing rule number segment of the receiver
overlaps.
Scenario
This error is reported if the routing rule number segment of the receiver added in the TEP
sending policy overlaps.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The routing rule number segment of the receiver overlaps.
Procedure
Enter a correct receiver routing rule.
8.422 PORTAL90469
Description
Failed to delete the identifier generation rule. The identifier generation rule does not exist.
Scenario
This error is reported when the identifier generation rule to be deleted does not exist.
Access Channel
Web
Possible Causes
The identifier generation rule does not exist.
Procedure
Refresh the page and ensure that the identifier generation rule exists.
8.423 PORTAL90470
Description
Failed to delete the identifier generation rule blacklist. The identifier generation rule blacklist
does not exist.
Scenario
This error is reported when the identifier generation rule blacklist to be deleted does not exist.
Access Channel
Web
Possible Causes
The identifier generation rule blacklist does not exist.

Copyright © Huawei
Mobile Money
Procedure
Refresh the page and ensure that the identifier generation rule blacklist exists.
8.424 PORTAL90471
Description
The identity of the {0} type does not have a corresponding account.
{0} indicates an identity type.
Scenario
This error is reported in the following scenario: An operator initiates a P2P transaction using
the Initiate Transaction menu on the customer details page. When the identity type of the
receiver identity is set to MSISDN, set the MSISDN field to the MSISDN of the till in the
customer number segment and click Verify.
Access Channel
Web
Possible Causes
The identity of the {0} type does not have a corresponding account.
Procedure
Ensure that this type of identity has a corresponding account.
8.425 PORTAL90472
Description
Template {0} has been referenced by another template and cannot be deleted.
{0} indicates a template name.
Scenario
This error is reported during TC message template modification when a template or parameter
referenced by an AG template is deleted.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
Template {0} has been referenced by another template and cannot be deleted.
Procedure
Select another template or delete the reference relationship of the selected template.
8.426 PORTAL90473
Description
Failed to delete the charge profile. Charge profiles not in draft state cannot be deleted.
Scenario
This error is reported when the charge profile to be deleted is not in draft state.
Access Channel
Web
Possible Causes
Charge profiles not in draft state cannot be deleted.
Procedure
Ensure that the charge profile to be deleted is in draft state.
8.427 PORTAL90474
Description
Failed to release the record. Records not in draft state cannot be released.
Scenario
This error is reported when the record to be released is not in draft state.
Access Channel
Web
Possible Causes
Records not in draft state cannot be released.

Copyright © Huawei
Mobile Money
Procedure
Ensure that the record to be released is in draft state.
8.428 PORTAL90475
Description
Failed to query, release, or edit the record. The record to be operated has been deleted or
expired.
Scenario
This error is reported when the record to be operated does not exist.
Access Channel
Web
Possible Causes
The record to be operated has been deleted or expired.
Procedure
Ensure that the record to be operated exists.
8.429 PORTAL90476
Description
The New Version operation is not allowed when there are valid records in draft state.
Scenario
This error is reported when there are valid records in draft state during New Version
operation.
Access Channel
Web
Possible Causes
There are valid records in draft state.

Copyright © Huawei
Mobile Money
Procedure
Change records in draft state to records in released state and then perform the New Version
operation.
8.430 PORTAL90477
Description
The version number next to New Version is incorrect.
Scenario
This error is reported when the version number is incorrect.
Access Channel
Web
Possible Causes
The version number next to New Version has been occupied or is less than the existing
maximum version number.
Procedure
Refresh the page and then perform the New Version operation.
8.431 PORTAL90478
Description
The release cancelation operation cannot be performed on records not in released state.
Scenario
This error is reported when the record whose release is to be canceled is not in released state.
Access Channel
Web
Possible Causes
The record is not in released state.
Procedure
Refresh the page and then perform the release cancelation operation.

Copyright © Huawei
Mobile Money
8.432 PORTAL90479
Description
Failed to delete the record. Records not in draft state cannot be deleted.
Scenario
This error is reported when the record to be deleted is not in draft state.
Access Channel
Web
Possible Causes
Records not in draft state cannot be deleted.
Procedure
Ensure that the record to be deleted is in draft state.
8.433 PORTAL90480
Description
The selected records include records that cannot be reviewed.
Scenario
When an SP operator reviews a refund task, the selected records include records that cannot
be reviewed.
Access Channel
Web
Possible Causes
The selected records include records that cannot be reviewed.
Procedure
Select records again and then review the task.

Copyright © Huawei
Mobile Money
8.434 PORTAL90481
Description
During the adding of a TC message template, the selected Interface Code already exists.
Scenario
This error is reported when the selected Interface Code already exists in the TC template.
Access Channel
Web
Possible Causes
The selected Interface Code already exists in the TC template.
Procedure
Select another Interface Code.
8.435 PORTAL90482
Description
During the adding of an AG template, the selected Interface Code does not match the TC
Message Command.
Scenario
This error is reported when the selected Interface Code does not match TC Message
Command.
Access Channel
Web
Possible Causes
The selected Interface Code does not match TC Message Command.
Procedure
Select another Interface Code.

Copyright © Huawei
Mobile Money
8.436 PORTAL90483
Description
incorrect.
Scenario
This error is reported when a blacklist rule has already been configured for the identity type or
the entered identity type is incorrect.
Access Channel
Web, USSD
Possible Causes
incorrect.
Procedure
8.437 PORTAL90484
Description
The accumulator fails to be reviewed. The accumulator of the earlier version has expired.
Scenario
This error is reported when the accumulator of the earlier version has expired.
Access Channel
Web
Possible Causes
The accumulator of the earlier version has expired and cannot be reviewed.
Procedure
Reject the review and create a new valid accumulator.

Copyright © Huawei
Mobile Money
8.438 PORTAL90485
Description
The length of the identifier rule definition is incorrect. The length must ranges from 1 to 2048.
Scenario
This error is reported when the length of the identifier rule definition is incorrect.
Access Channel
Web, USSD
Possible Causes
The length of the identifier rule definition is incorrect.
Procedure
Enter the correct rule definition.
8.439 PORTAL90487
Description
The entered value of Send User Name already exists.
Scenario
This error is reported when the outbound receiver is modified but the entered value of Send
User Name already exists.
Access Channel
Web
Possible Causes
The entered value of Send User Name has been used by another outbound receiver.
Procedure
Enter another value of Send User Name.

Copyright © Huawei
Mobile Money
8.440 PORTAL90488
Description
The entered value of User Name already exists.
Scenario
This error is reported when the outbound receiver is modified but the entered value of User
Name already exists.
Access Channel
Web
Possible Causes
The entered value of User Name has been used by another outbound receiver.
Procedure
Enter another value of User Name.
8.441 PORTAL90489
Description
This role does not exist or has been deleted.
Scenario
This error is reported when an operator deletes a Business Operations Group and another
operator deletes the same Business Operations Group without refreshing the Business
Operations Group page.
Access Channel
Web
Possible Causes
This role does not exist or has been deleted.
Procedure
Refresh the Business Operations Group page and then delete the group.

Copyright © Huawei
Mobile Money
8.442 PORTAL90490
Description
The role is in Inactive state.
Scenario
This error is reported when an operator disables a Business Operations Group and another
operator disables or edits the same Business Operations Group without refreshing the
Business Operations Group page.
Access Channel
Web
Possible Causes
The role status is incorrect. A role in Inactive state can only be queried.
Procedure
Refresh the Business Operations Group page and then perform the operation.
8.443 PORTAL90491
Description
The key file is incorrect.
Scenario
This error is reported when the key file uploaded during the Add API Caller Management
operation is incorrect.
Access Channel
Web
Possible Causes
The key file is incorrect.
Procedure
Upload a correct key file.

Copyright © Huawei
Mobile Money
8.444 PORTAL90492
Description
Command ID {0} has been deleted.
{0} indicates a name of the current edited command ID.
Scenario
This error is reported when a deleted command ID is modified and submitted on the TC
Outband page.
Access Channel
Web
Possible Causes
Command ID {0} has been deleted.
Procedure
Refresh the TC Outband page and perform the operation again.
8.445 PORTAL90493
Description
The SFTP operation failed.
Scenario
This error is reported when an operator clicks the download button in the export or import list
on the Configuration Items Export or Configuration Items Import page and the system is
abnormal due to network connection and permission reasons.
Access Channel
Web
Possible Causes
Failed to connect to the SFTP server or there is no permission.
Procedure
1. Check whether the network connection is normal.
2. Contact Huawei engineers to change the operation permission.

Copyright © Huawei
Mobile Money
8.446 PORTAL90494
Description
Only one import task can be initiated.
Scenario
This error is reported when an import task on the Business Configuration Data Import page is
not complete and the operator submits another import task.
Access Channel
Web
Possible Causes
Only one import task can be initiated.
Procedure
Refresh the Business Configuration Data Import page to ensure that the import task has been
completed and then initiate another import task.
8.447 PORTAL90495
Description
The version of the exported target object has changes.
Scenario
This error is reported when the version of the exported target object has changes during export
configuration.
Access Channel
Web
Possible Causes
The version of the exported target object has changes.
Procedure
Export the target object again.

Copyright © Huawei
Mobile Money
8.448 PORTAL90500
Description
The Reason Type TEP Policy failed to be added or modified.
Scenario
This error is reported when the added or modified Reason Type TEP Policy record is the same
as an existing record in the database.
Access Channel
Web
Possible Causes
The added or modified record is the same as an existing record in the database.
Procedure
Modify the entered information to ensure that the record is not the same as an existing record
in the database.
8.449 PORTAL90501
Description
The new version operation cannot be performed on an accumulator whose versions are all in
Inactive or Release state.
Scenario
All accumulator versions are in Inactive or Release state. The new version operation cannot
be performed regardless whether the accumulator has multiple versions or is in the validity
period.
Access Channel
Web
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
8.450 PORTAL90502
Description
The passcode failed to be deleted from the blacklist. The passcode is empty.
Scenario
This error is reported when a passcode is deleted from the blacklist but the passcode is empty.
Access Channel
Web
Possible Causes
The passcode is empty.
Procedure
Enter a correct passcode.
8.451 PORTAL90504
Description
Two roles of the operator cannot be mutually exclusive.
Scenario
This error is reported when operator roles are configured on the lower-level organization
configuration page but two roles are mutually exclusive.
Access Channel
Web
Possible Causes
Two roles of the operator are mutually exclusive.
Procedure
Ensure that the two roles of the operator are not mutually exclusive.

Copyright © Huawei
Mobile Money
8.452 PORTAL90505
Description
Review rules have been configured for all channels of the reason type.
Scenario
This error is reported when a review rule is added for a reason type but review rules have
been configured for all channels of the reason type.
Access Channel
Web
Possible Causes
Review rules have been configured for all channels of the reason type.
Procedure
Modify the review rules of the reason type or delete the original review rules and then add the
rules again.
8.453 PORTAL90506
Description
In the current settlement profile, the settlement whose Funding Source is Organization
Bank has been configured.
Scenario
This error is reported when the settlement whose Funding Source is Organization Bank has
been configured in the current settlement profile.
Access Channel
Web
Possible Causes
The settlement of the organization bank type already exists and cannot be configured again.
Procedure
Add the settlement of other types.

Copyright © Huawei
Mobile Money
8.454 PORTAL90507
Description
In the current settlement profile, the settlement whose Funding Source is Parent or Child
has been configured.
Scenario
This error is reported when the settlement whose Funding Source is Parent or Child has been
configured in the current settlement profile.
Access Channel
Web
Possible Causes
The settlement of the Parent or Child type already exists and cannot be configured again.
Procedure
Add the settlement of other types.
8.455 PORTAL90508
Description
The KYC field {0} has been assigned to {1} and cannot be assigned to Person again.
Scenario
This error is reported when a KYC field is assigned to a person but the KYC field has been
assigned to an identity (customer, SP operator, organization operator, or organization)
supporting natural persons.
Access Channel
Web
Possible Causes
The KYC field {0} has been assigned to {1}.
{0} indicates the KYC field name.

{1} indicates the identity type name.

Copyright © Huawei
Mobile Money
Procedure
Cancel the KYC field assigned to the identity supporting natural persons.
8.456 PORTAL90509
Description
Failed to save the KYC field configuration of Display in Search Result of Person.
Scenario
This error is reported if more than eight KYC fields of Display in Search Result of Person are
selected.
Access Channel
Web
Possible Causes
More than eight KYC fields of Display in Search Result of Person are selected.
Procedure
Ensure that the number of selected KYC fields of Display in Search Result of Person does
not exceed eight.
8.457 PORTAL90510
Description
The FSICore attribute cannot be removed from the current version because the previous
version contains the FSICore attribute.
Scenario
This error is reported when an SP operator modifying a product, the previous version contains
the FSICore attribute, and the current new version does not contain the FSICore attribute.
Access Channel
Web
Possible Causes
The current version does not contain the FSICore attribute.

Copyright © Huawei
Mobile Money
Procedure
Add the FSICore attribute to the current version and save the modification.
8.458 PORTAL90511
Description
The configured dependency relationship of the FSI Link Type has been deleted by an
operator.
Scenario
This error is reported in the following scenario: Two operators perform operations on FSI
Link Dependence on different portals. One operator has deleted the dependency relationship
of an FSI Link Type. The other operator edits the deleted dependency relationship of the FSI
Link Type.
Access Channel
Web
Possible Causes
The dependency relationship of the FSI Link Type has been deleted.
Procedure
Ensure that the configured dependency relationship of the FSI Link Type exists.
8.459 PORTAL90512
Description
Operation failed. The limit rule whose Limit Type is Max.Balance cannot be selected in the
Identity Rule Profile of the organization operator.
Scenario
This error is reported when the limit rule whose Limit Type is Max.Balance is selected in the
Identity Rule Profile of the organization operator.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The limit rule whose Limit Type is Max.Balance cannot be selected in the Identity Rule
Profile of the organization operator.
Procedure
Perform the operation again and then modify and save the limit rule.
8.460 PORTAL90515
Description
The identity's account is in Unclaimed state and the refund operation cannot be performed.
Scenario
This error is reported if the refund operation is performed when the identity's account is in
Unclaimed state.
Access Channel
Web
Possible Causes
The identity's account is in Unclaimed state and the refund operation cannot be performed.
Procedure
Ensure that the identity's account is not in Unclaimed state.
8.461 PORTAL90516
Description
The added segment information is incorrect.
Scenario
This error is reported when an SP operator configures segment-based tax exemption for
registered customers and adds the same segment.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
When an SP operator configures segment-based tax exemption for registered customers, the
same segment is added.
Procedure
Select another segment.
8.462 PORTAL90517
Description
The reason type or service of the same unit is added in the internal bundle.
Scenario
This error is reported if the reason type or service of the same unit is added in the internal
bundle.
Access Channel
Web
Possible Causes
Unit {2} is repeatedly configured for {0} {1} in the internal bundle.
{0} indicates a service or reason type.

{1} indicates the name of the service or reason type.
{2} indicates the currency or quantity unit.
Procedure
Select another internal bundle or delete the duplicate records.
8.463 PORTAL90518
Description
The external bundle element to be deleted is referenced by a bundle.
Scenario
This error is reported if the external bundle element to be deleted is referenced by a bundle.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The external bundle element to be deleted is referenced by a bundle.
Procedure
Ensure that the external bundle element to be deleted is not referenced by a bundle.
8.464 PORTAL90520
Description
The internal bundle list in the internal bundle and combine bundle cannot be empty.
Scenario
This error is reported if the internal bundle list in an internal bundle or combine bundle is
empty.
Access Channel
Web
Possible Causes
The internal bundle list is empty.
Procedure
Add internal bundle records and submit again.
8.465 PORTAL90521
Description
The external bundle list in the external bundle and combine bundle cannot be empty.
Scenario
This error is reported if the external bundle list in an external bundle or combine bundle is
empty.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The external bundle list is empty.
Procedure
Add external bundle records and submit again.
8.466 PORTAL90522
Description
The segment of the provider does not match or the provider is not in Active state.
Scenario
This error is reported when the segment of the provider does not match or the provider is not
in Active state.
Access Channel
Web
Possible Causes
The segment of the provider does not match or the provider is not in Active state.
Procedure
Select another provider.
8.467 PORTAL90523
Description
The KYC value of the external bundle provider is incorrect in the system parameter
configuration.
Scenario
This error is reported when the KYC value of the external bundle provider is incorrect in the
system parameter configuration.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The KYC value of the external bundle provider is incorrect in the system parameter
configuration.
Procedure
Choose My Functions > Operational Configuration > System Parameter > Bundle >
KYC External Bundle Provider, and correctly configure the system parameter.
8.468 PORTAL95000
Description
The bank card attributes corresponding to the FI fail to be added. A maximum of five
attributes can be added for an identity type.
Scenario
This error is reported when bank card attributes corresponding to the FI are added but more
than five attributes are added for an identity type.
Access Channel
Web
Possible Causes
A maximum of five attributes can be added for an identity type.
Procedure
Add no more than five attributes for an identity type.
8.469 PORTAL95001
Description
Add at least one reason type.
Scenario
This error is reported when an SP operator modifies the commission settlement configuration
and adds a record without adding a reason type.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
No reason type is added.
Procedure
Add at least one reason type.
8.470 PORTAL95002
Description
The foreign currency exchange rate is incorrectly configured for the currency.
Scenario
This error is reported in the foreign exchange service when the foreign currency exchange rate
is incorrectly configured for the currency.
Access Channel
Web
Possible Causes
The foreign currency exchange rate is incorrectly configured for the currency.
Procedure
Configure the foreign currency exchange rate correctly on the foreign currency exchange rate
configuration page and try again.
8.471 PORTAL95003
Description
The reason type of the foreign exchange transaction is incorrect.
Scenario
This error is reported when the reason type of the foreign exchange transaction is incorrect.
Access Channel
Web
Possible Causes
The reason type of the foreign exchange transaction is incorrect.

Copyright © Huawei
Mobile Money
Procedure
Configure the reason type correctly and initiate the transaction again.
8.472 PORTAL95004
Description
Select at least one settlement record.
Scenario
This error is reported when an SP operator manually rolls up commission without selecting
settlement records.
Access Channel
Web
Possible Causes
No settlement record is selected.
Procedure
Select at least one settlement record.
8.473 PORTAL95005
Description
Select at most one settlement record for an account.
Scenario
This error is reported when an SP operator manually rolls up commission and selects multiple
settlement records for one account.
Access Channel
Web
Possible Causes
Multiple settlement records are selected for an account.
Procedure
Select at most one settlement record for an account.

Copyright © Huawei
Mobile Money
8.474 PORTAL95006
Description
No configuration information about the commission invoice exists.
Scenario
This error is reported when an SP or organization operator goes to the manual commission
invoice generation page but the system does not contain any invoice configuration
information.
Access Channel
Web
Possible Causes
No configuration information about the commission invoice exists.
Procedure
Ensure that configuration related to the commission invoice has been configured.
8.475 PORTAL95007
Description
The number of selected qualified organizations has reached the maximum of 20.
Scenario
This error is reported if the number of selected qualified organizations has reached the
maximum of 20.
Access Channel
Web
Possible Causes
The number of selected qualified organizations has reached the maximum of 20.
Procedure
Delete some selected qualified organizations and then add new qualified organizations.

Copyright © Huawei
Mobile Money
8.476 PORTAL95008
Description
The additional field to be deleted has been referenced in the card type.
Scenario
This error is reported if the additional field to be deleted has been referenced in the card type.
Access Channel
Web
Possible Causes
The additional field to be deleted has been referenced in the card type.
Procedure
Delete the reference relationship from the card type and then delete the additional field.
8.477 PORTAL95009
Description
A maximum of 10 target parameters can be selected in a rule.
Scenario
This error is reported during target parameter adding if the number of selected target
parameters exceeds the maximum.
Access Channel
Web
Possible Causes
The number of selected target parameters exceed 10.
Procedure
Check the selected target parameters.

Copyright © Huawei
Mobile Money
8.478 PORTAL95010
Description
The Target Parameters list cannot be empty.
Scenario
This error is reported during lookup saving if the Target Parameters list is empty.
Access Channel
Web
Possible Causes
The Target Parameters list is empty.
Procedure
Ensure that the Target Parameters list is not empty.
8.479 PORTAL95011
Description
The Lookup Rule list cannot be empty.
Scenario
This error is reported during lookup saving if the Lookup Rule list is empty.
Access Channel
Web
Possible Causes
The Lookup Rule list is empty.
Procedure
Ensure that the Lookup Rule list is not empty.

Copyright © Huawei
Mobile Money
8.480 PORTAL95012
Description
No service is configured for the confirm part.
Scenario
This error is reported during the confirmation of the two part payment if no service is
configured.
Access Channel
Web
Possible Causes
No service is configured for the confirm part.
Procedure
Configure a service for the confirm part.
8.481 PORTAL95013
Description
The selected service and channel already exist.
Scenario
This error is reported during process adding if the selected service and channel already exist.
Access Channel
Web
Possible Causes
The selected service and channel already exist.
Procedure
Select other services or channels.

Copyright © Huawei
Mobile Money
8.482 PORTAL95014
Description
Scenario
This error is reported if details of the linked identity cannot be viewed on the SP/Organization
Portal.
Access Channel
Web
Possible Causes
Procedure
8.483 PORTAL95015
Description
The saving plan has been subscribed.
Scenario
This error is reported when an operator clicks the deactivation button next to a referenced
saving plan.
Access Channel
Web
Possible Causes
The saving plan has been subscribed.
Procedure
Unsubscribe from the saving plan before deactivation.

Copyright © Huawei
Mobile Money
8.484 PORTAL95016
Description
The transaction template fails to be imported because the transaction template file format is
incorrect.
Scenario
This error is reported during transaction template import on the transaction template
configuration page if the transaction template file format is incorrect.
Access Channel
Web
Possible Causes
The transaction template file format is incorrect.
Procedure
8.485 PORTAL95017
Description
The transaction template fails to be imported because the transaction template ID is empty.
Scenario
configuration page if the transaction template ID is empty.
Access Channel
Web
Possible Causes
The transaction template ID is empty.
Procedure

Copyright © Huawei
Mobile Money
8.486 PORTAL95018
Description
The transaction template fails to be imported because the transaction template version is
empty.
Scenario
configuration page if the transaction template version is empty.
Access Channel
Web
Possible Causes
The transaction template version is empty.
Procedure
8.487 PORTAL95019
Description
The transaction template fails to be imported because the transaction template version is
incorrect. The version of the new template must be greater than that of the old template.
Scenario
configuration page if the transaction template version is incorrect.
Access Channel
Web
Possible Causes
The transaction template version is incorrect.
Procedure

Copyright © Huawei
Mobile Money
8.488 PORTAL95020
Description
Files of the non-image type cannot be viewed.
Scenario
This error is reported if the operator queries a file of the non-image type.
Access Channel
Web
Possible Causes
Files of this type cannot be viewed.
Procedure
Download the file and view it.
8.489 PORTAL95021
Description
The transaction template fails to be imported because it already exists in the draft list.
Scenario
configuration page if the transaction template already exists in the draft list.
Access Channel
Web
Possible Causes
The transaction template fails to be imported because it already exists in the draft list.
Procedure

Copyright © Huawei
Mobile Money
8.490 PORTAL95022
Description
The transaction template fails to be imported because the transaction template ID format is
incorrect.
Scenario
configuration page if the transaction template ID format is incorrect.
Access Channel
Web
Possible Causes
The transaction template ID format is incorrect.
Procedure
8.491 PORTAL95023
Description
The currencies of the selected original reason types is not unique.
Scenario
This error is reported in the following scenario: The non-independent loyalty point function is
enabled. In a single-currency system, an SP operator selects multiple original reasons when
configuring the reason type of the reversal transaction type but the currencies of the original
reason types are inconsistent.
Access Channel
Web
Possible Causes
The currencies of the selected original reason types is not unique.
Procedure
Select only original reason types of the same currency.

Copyright © Huawei
Mobile Money
8.492 PORTAL95024
Description
Operation failed. The parameter already exists.
Scenario
This error is reported when a Transaction Initiation Configuration parameter is added or
modified but the added or modified parameter already exists.
Access Channel
Web
Possible Causes
The parameter already exists.
Procedure
Ensure that the parameter does not exist and retry.
8.493 PORTAL95025
Description
Failed to import territory hierarchies in batches.
Scenario
This error is reported when the system fails to parse territory hierarchy files that are being
imported in batches.
Access Channel
Web
Possible Causes
An error occurred when parsing the imported file.
Procedure
Check the imported file.

Copyright © Huawei
Mobile Money
8.494 PORTAL95026
Description
Scenario
This error is reported when the territory hierarchy files that are being imported in batches are
in an incorrect format.
Access Channel
Web
Possible Causes
The imported file format is incorrect.
Procedure
8.495 PORTAL95027
Description
Scenario
This error is reported when values in the Territory Type column is incorrect in the territory
hierarchy files that are imported in batches.
Access Channel
Web
Possible Causes
The Territory Type in line {0} is incorrect in the imported file.
{0} indicates a line number.
Procedure

Copyright © Huawei
Mobile Money
8.496 PORTAL95028
Description
Scenario
This error is reported when values in the Parent column is incorrect in the territory hierarchy
files that are imported in batches.
Access Channel
Web
Possible Causes
The Parent in line {0} is incorrect in the imported file.
Procedure
8.497 PORTAL95029
Description
Scenario
This error is reported when values in the Region Code column is incorrect in the territory
Access Channel
Web
Possible Causes
The Region Code in line {0} is incorrect in the imported file.

Copyright © Huawei
Mobile Money
Procedure
8.498 PORTAL95030
Description
Scenario
This error is reported when values in the Region Name column is incorrect in the territory
Access Channel
Web
Possible Causes
The Region Name in line {0} is incorrect in the imported file.
Procedure
8.499 PORTAL95031
Description
Scenario
This error is reported when values in the Description column is incorrect in the territory
Access Channel
Web
Possible Causes
The Description in line {0} is incorrect in the imported file.

Copyright © Huawei
Mobile Money
Procedure
8.500 PORTAL95032
Description
Scenario
This error is reported when values in the LACCI column is incorrect in the territory hierarchy
Access Channel
Web
Possible Causes
The LACCI in line {0} is incorrect in the imported file.
Procedure
8.501 PORTAL95033
Description
Scenario
This error is reported when values in the GIS column is incorrect in the territory hierarchy
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The GIS in line {0} is incorrect in the imported file.
Procedure
8.502 PORTAL95034
Description
Scenario
This error is reported when values in the Boundary column is incorrect in the territory
Access Channel
Web
Possible Causes
The Boundary in line {0} is incorrect in the imported file.
Procedure
8.503 PORTAL95035
Description
Failed to move the territory node because this node is not a leaf node.
Scenario
This error is reported when a non-leaf node is being moved.

Copyright © Huawei
Mobile Money
Access Channel
Web
Possible Causes
The node to be moved is not a leaf node.
Procedure
Do not move the node.
8.504 PORTAL95036
Description
Failed to change the territory node state because some subnodes are in active state.
Scenario
This error is reported if some subnodes are in active state during the change of the territory
node state.
Access Channel
Web
Possible Causes
Some subnodes are in active state.
Procedure
Do not change the state.
8.505 PORTAL95037
Description
Failed to delete the territory node because this node is not in draft state
Scenario
This error is reported when a node not in draft state is being deleted.
Access Channel
Web

Copyright © Huawei
Mobile Money
Possible Causes
The node to be deleted is not in draft state.
Procedure
Do not delete this node.
8.506 PORTAL95038
Description
Failed to delete the territory node because this node is not a leaf node.
Scenario
This error is reported when a non-leaf node is being deleted.
Access Channel
Web
Possible Causes
The node to be deleted is not a leaf node.
Procedure
8.507 PORTAL95039
Description
Failed to change the state.
Scenario
This error is reported if the upper-level territory is not in active state during the change of the
territory node state.
Access Channel
Web
Possible Causes
The upper-level territory is not in active state.

Copyright © Huawei
Mobile Money
Procedure
Activate the upper-level territory and try again.
8.508 PORTAL95040
Description
Failed to delete the territory type because it has been referenced.
Scenario
This error is reported if the territory type has been referenced during the deletion of the
territory type.
Access Channel
Web
Possible Causes
The territory type has been referenced.
Procedure
8.509 PORTAL95041
Description
Failed to add a territory type because the depth has reached the limit.
Scenario
This error is reported if the depth has reached the limit during the adding of a territory type.
Access Channel
Web
Possible Causes
The depth has reached the limit.
Procedure
Do not add a territory type.

Copyright © Huawei
Mobile Money
8.510 PORTAL95043
Description
Failed to save the LACCI information.
Scenario
This error is reported when the LACCI information that is being saved already exists.
Access Channel
Web
Possible Causes
The LACCI {0}, {1} to be saved already exists.
{0} indicates LACID.

{1} indicates CELLID.
Procedure
Check the saved LACCI information.
8.511 PORTAL95044
Description
Failed to move the territory node because this node is not in draft state.
Scenario
This error is reported when a territory node not in draft state is being moved.
Access Channel
Web
Possible Causes
The node to be moved is not in draft state.
Procedure
Do not move the node.

Copyright © Huawei
Mobile Money
8.512 PORTAL95045
Description
Failed to save the GIS information. Each closed region in GIS information must contain at
least three locations.
Scenario
This error is reported when there are less than three locations in the closed region in the GIS
information that is being saved.
Access Channel
Web
Possible Causes
There are less than three locations in the closed region in the saved GIS information.
Procedure
Check the saved GIS information.
8.513 PORTAL95046
Description
Failed to import LACCIs in batches.
Scenario
This error is reported when values of the LACCIs are incorrect in the LACCI files that are
imported in batches.
Access Channel
Web
Possible Causes
The LACCI {1}, {2} in line {0} is incorrect in the imported file.
{0} indicates line number.

{1} indicates LACID.
{2} indicates CELLID.

Copyright © Huawei
Mobile Money
Procedure
8.514 PORTAL95047
Description
Failed to import GISs in batches.
Scenario
This error is reported when values of the GISs are incorrect in the GIS files that are imported
in batches.
Access Channel
Web
Possible Causes
The GIS {1}, {2} in line {0} is incorrect in the imported file.
{0} indicates line number.

{1} indicates longitude.
{2} indicates latitude.
Procedure
8.515 PORTAL95048
Description
Operation failed. The identity that receives the verification code has changed.
Scenario
This error is reported when the identity that receives the verification code has changed.
Access Channel
Web
Possible Causes
The identity that receives the verification code has changed.

Copyright © Huawei
Mobile Money
Procedure
Obtain the new verification code under the current identity.
8.516 PORTAL95049
Description
The login fails. The verification code for login is invalid.
Scenario
This error is reported when the verification code for login is invalid.
Access Channel
Web
Possible Causes
The verification code for login is invalid.
Procedure
Obtain the new verification code.
8.517 PORTAL95050
Description
The current TEP receiver has been referenced by the TEP sending policy and cannot be set to
Inactive state.
Scenario
This error is reported when setting the status of the TEP receiver that has been referenced by
the TEP sending policy from Released to Inactive.
Access Channel
Web
Possible Causes
The current TEP receiver has been referenced by the TEP sending policy.
Procedure
Delete the reference relationship between the TEP receiver and TEP sending policy.

Copyright © Huawei
Mobile Money
8.518 PORTAL95051
Description
The current TEP sending policy has been referenced by the Reason Type TEP Policy and
cannot be set to Inactive state.
Scenario
This error is reported when setting the status of the TEP sending policy that has been
referenced by the Reason Type TEP Policy from Released to Inactive.
Access Channel
Web
Possible Causes
The current TEP sending policy has been referenced by the Reason Type TEP Policy.
Procedure
Delete the reference relationship between the TEP sending policy and Reason Type TEP
Policy.
8.519 PORTAL95052
Description
Failed to save the external bundle. Only one external bundle is allowed when Bundle Type is
set to SP Bundle.
Scenario
This error is reported if multiple external bundles are found when Bundle Type is set to SP
Bundle.
Access Channel
Web
Possible Causes
When Bundle Type is set to SP Bundle, only one external bundle is allowed.
Procedure
Check the external bundle.

Copyright © Huawei
Mobile Money
8.520 PORTAL95053
Description
Failed to save the external bundle. The current external bundle is referenced by other bundles.
Scenario
This error is reported if the saved external bundle is referenced by other bundles when Bundle
Type is set to SP Bundle.
Access Channel
Web
Possible Causes
The current external bundle is referenced by other bundles.
Procedure
Check the external bundle.
8.521 PORTAL95054
Description
The page redirection configuration is missing.
Scenario
This error is reported when the page redirection configuration is missing.
Access Channel
Web
Possible Causes
The page redirection configuration is missing.
Procedure
Ensure that the configuration has been configured.

Copyright © Huawei
Mobile Money
8.522 PORTAL95055
Description
The loyalty point balance is insufficient.
Scenario
This error is reported when loyalty points are exchanged for goods but the loyalty point
balance is smaller than or equal to 0.
Access Channel
Web
Possible Causes
The loyalty point balance is insufficient.
Procedure
The loyalty point balance is insufficient and goods cannot be exchanged.
8.523 PORTAL95056
Description
No rank is configured for the rank or rank by accumulator function.
Scenario
This error is reported when there is no rank is configured for the rank or rank by accumulator
function.
Access Channel
Web
Possible Causes
No rank is configured for the rank or rank by accumulator function.
Procedure
Add ranks.

Copyright © Huawei
Mobile Money
8.524 PORTAL95057
Description
No specific reward rule is configured.
Scenario
This error is reported when there is no specific reward rule is configured.
Access Channel
Web
Possible Causes
No specific reward rule is configured.
Procedure
Add at least one reward rule and then submit the request again.
8.525 PORTAL95058
Description
The configured loyalty point reward rule is repeated.
Scenario
This error is reported when the configured loyalty point reward rule is repeated.
Access Channel
Web
Possible Causes
The configured loyalty point reward rule is repeated.
Procedure
Delete or modify the repeated loyalty point reward rule.

Copyright © Huawei
Mobile Money
8.526 PORTAL95059
Description
The bill amount fails to be queried through the interface provided by the Dompetku.
Scenario
This error is reported if the Dompetku bill amount fails to be queried.
Access Channel
Web
Possible Causes
The bill amount fails to be queried through the interface provided by the Dompetku.
Procedure
Check the interface status.
8.527 PORTAL95060
Description
The KYC field {1} of the bill issuer organization whose short code is {0} is empty.

Scenario
This error is reported when the corresponding KYC is not configured for the current bill
issuer organization.
Access Channel
Web
Possible Causes
The corresponding KYC is not configured for the current bill issuer organization.
Procedure
Check the KYC configuration of the current organization.

Copyright © Huawei
Mobile Money
8.528 PORTAL95061
Description
A loyalty point type must be selected.
Scenario
This error is reported when independent loyalty points are enabled and loyalty points are
exchanged for balance but no loyalty point type is specified when multiple loyalty point types
exist.
Access Channel
Web
Possible Causes
A loyalty point type must be selected.
Procedure
Select a loyalty point type.
8.529 PORTAL95064
Description
The method in the request is not supported.
Scenario
This error is reported when the method in the request is not supported.
Access Channel
Web
Possible Causes
The method in the request is not supported.
Procedure
Check the connection method in the request and perform the operation again.

Copyright © Huawei
Mobile Money
8.530 PORTAL95065
Description
The territory node fails to be deleted. The current territory node is to be reviewed.
Scenario
This error is reported during territory node deletion when the node to be deleted contains
review tasks.
Access Channel
Web
Possible Causes
The current territory node is to be reviewed.
Procedure
Do not delete the territory node.
8.531 PORTAL95066
Description
The territory node status fails to be modified. The current territory node is to be reviewed.
Scenario
This error is reported during territory node status modification when the node to be modified
contains review tasks.
Access Channel
Web
Possible Causes
Procedure
Do not modify the territory node status.

Copyright © Huawei
Mobile Money
8.532 PORTAL95067
Description
The territory node fails to be moved. The current territory node is to be reviewed.
Scenario
This error is reported during territory node moving when the node to be moved contains
review tasks.
Access Channel
Web
Possible Causes
Procedure
Do not move the territory node.
8.533 PORTAL95068
Description
The configuration item fails to be modified.
Scenario
This error is reported during configuration item modification if the workflow task to be
reviewed already exists.
Access Channel
Web
Possible Causes
The workflow task to be reviewed exists.
Procedure
Wait for the operator to review the workflow task.

Copyright © Huawei
Mobile Money
8.534 PORTAL95069
Description
The file fails to be parsed.
Scenario
This error is reported if the file fails to be parsed.
Access Channel
Web
Possible Causes
The file fails to be parsed.
Procedure
Verify the file format and content and perform the operation again.
8.535 PORTAL95070
Description
The exchange rate has been configured for the currency and cannot be configured again.
Scenario
This error is reported during loyalty point exchange rate configuration if more than one
exchange rates are configured for a currency.
Access Channel
Web
Possible Causes
The exchange rate has been configured for the currency and cannot be configured again.
Procedure
Choose My Functions > Operational Configuration > Loyalty Points Configuration >
Loyalty Points Type and check whether the configured loyalty point exchange rate already
exists.

Copyright © Huawei
Mobile Money
8.536 PORTAL95071
Description
The submitted action type and status already exist.
Scenario
This error is reported when an action type is added in the action type TEP policy but the
submitted action type and status already exist.
Access Channel
POS
Possible Causes
The submitted action type and status already exist.
Procedure
Modify the action type or status to ensure that one of them does not exist.
8.537 PORTAL95072
Description
The start routing is greater than the end routing.
Scenario
This error is reported when a short code-type routing is added in the TEP send policy but the
start routing is greater than the end routing.
Access Channel
POS
Possible Causes
The start routing is greater than the end routing.
Procedure
Modify the end routing to ensure that the ending routing is greater than the start routing.

Copyright © Huawei
Mobile Money
8.538 PORTAL95073
Description
The interface code of the BO type already exists.
Scenario
This error is reported when a new interface code is added in the BCS Outbound but the added
interface code is of the BO type and already exists in the list.
Access Channel
POS
Possible Causes
The added interface code is of the BO type and already exists in the list.
Procedure
Select an interface code of other types or perform operations on the existing interface code of
the BO type.
8.539 PORTAL95074
Description
The third-party system fails to send a response.
Scenario
This error is reported when an SP operator queries the status of the third-party system on the
transaction details page and the third-party system times out.
Access Channel
Web
Possible Causes
The third-party system is abnormal.
Procedure
Try again later.

Copyright © Huawei
Mobile Money
8.540 PORTAL95075
Description
When an organization operator initiates an AgentOwnerTransfer transaction, the agent must
have the corresponding owner MSISDN.
Scenario
This error is reported when an organization operator fails to initiate an AgentTransfer
transaction on the organization portal because the organization does not have the owner
MSISDN or the corresponding customer cannot be found based on the MSISDN.
Access Channel
Web
Possible Causes
When an organization operator initiates an AgentOwnerTransfer transaction, the agent must
have the corresponding owner MSISDN.
Procedure
Ensure that the agent has the corresponding owner MSISDN.
8.541 PORTAL95076
Description
The system is error or busy and the file fails to be uploaded.
Scenario
When a picture-type KYC picture is uploaded, the NCSS file server reports an error and the
file fails to be uploaded.
Access Channel
WEB, API, USSD, APP
Possible Causes
The NCSS server is overloaded or incorrectly configured.
Procedure
Verify that NCSS server is correctly configured.

Copyright © Huawei
Mobile Money
8.542 PORTAL95077
Description
The uploaded template file is incorrect.
Scenario
This error is reported when the uploaded template file is incorrect.
Access Channel
Web
Possible Causes
The uploaded template file is incorrect.
Procedure
Upload the correct template file.
8.543 PORTAL95078
Description
The deregistration request fails to be sent.
Scenario
When an SP operator sends a deregistration request to the customer, a response indicating that
the request fails to be sent is returned.
Access Channel
Web
Possible Causes
The deregistration request fails to be sent.
Procedure
Ensure that the deregistration request can be correctly sent to the third-party system.

Copyright © Huawei
Mobile Money
8.544 PORTAL95079
Description
The customer does not exist, is not registered, or is not in Active state.
Scenario
This error is reported when a coupon is rewarded to a registered customer in Active state on
the Operations > Reward Coupon page.
Access Channel
POS
Possible Causes
The customer is not registered or is not in Active state.
Procedure
Enter a registered customer in Active state.
8.545 PORTAL95080
Description
File {0} does not exist.
{0} indicates the file name.
Scenario
This error is reported when a reconciliation file is deleted on the portal but the file has been
deleted on the FTP server.
Access Channel
Web
Possible Causes
File {0} does not exist.
Procedure
Refresh the portal.

Copyright © Huawei
Mobile Money
8.546 PORTAL95081
Description
The printing template fails to be uploaded.
Scenario
This error is reported when a printing template is uploaded but no path is specified or the
specified path does not have the permission.
Access Channel
POS
Possible Causes
No path is specified or the specified path does not have the permission.
Procedure
Check the SFTP configuration, path, and permission.
8.547 PORTAL95082
Description
The postpayment bill fails to be queried in the third-party system.
Scenario
This error is reported when the postpayment service is initiated through the web channel but
the postpayment bill fails to be queried in the third-party system.
Access Channel
Web
Possible Causes
The postpayment bill fails to be queried in the third-party system.
Procedure
Contact engineers of the third-party system.

Copyright © Huawei
Mobile Money
8.548 PORTAL95083
Description
The MSISDN and product name cannot be empty.
Scenario
This error is reported when the postpayment service is initiated through the web channel but
no information is entered on the initiation page or empty data is submitted.
Access Channel
Web
Possible Causes
The MSISDN or product name is empty.
Procedure
Enter the corresponding MSISDN and product name.
8.549 PORTAL95084
Description
The list data has expired and needs to be queried again.
Scenario
This error is reported in the following scenario: When the bank statement file is imported on
the portal and the file deletion button is clicked, a message is displayed, indicating that the
data has expired and needs to be queried again.
Access Channel
Web
Possible Causes
The list data has expired and needs to be queried again.
Procedure
Query the list data again.

Copyright © Huawei
Mobile Money
8.550 PORTAL95085
Description
The corresponding certificate issuer information is not transferred on the client.
Scenario
HTTPS is empty.
Access Channel
All
Possible Causes
Procedure
8.551 PORTAL95086
Description
Scenario
HTTPS is empty.
Access Channel
All
Possible Causes
Procedure

Copyright © Huawei
Mobile Money
8.552 PORTAL95087
Description
Audit logs fail to be exported.
Scenario
This error is reported during audit log export of the number of exported records exceed the
maximum.
Access Channel
API
Possible Causes
The number of audit logs exported at a time cannot exceed {0}.
{0} indicates the maximum number of audit logs that can be exported at a time.
Procedure
Modify the condition and export the audit logs again.
8.553 PORTAL95088
Description
Deletion failed.
Scenario
This error is reported when an XML template fails to be deleted because the mapping between
the XML template and an Excel template is configured.
Access Channel
Web
Possible Causes
Deletion failed.
Procedure
Delete the mapping configured in the Excel template and then delete the XML template.

Copyright © Huawei
Mobile Money
8.554 PORTAL95089
Description
The incentive rule configuration data fails to be saved.
Scenario
This error is reported during incentive rule configuration if the added limitation references to
accumulators with the same accumulation type and accumulation period.
Access Channel
Web
Possible Causes
The configured incentive limitation includes accumulators with the same accumulation type
and accumulator.
Procedure
Ensure that the configured incentive limitation does not include accumulators with the same
accumulation type and accumulator.
8.555 PORTAL95090
Description
The client IP address in the HTTP/HTTPS request does not exist.
Scenario
This error is reported when the IP address in the HTTP/HTTPS request does not exist.
Access Channel
Web
Possible Causes
The client IP address in the HTTP/HTTPS request does not exist.
Procedure
Construct a request containing the client IP address.

Copyright © Huawei
Mobile Money
8.556 PORTAL95091
Description
The FSI organization fails to be queried.
Scenario
This error is reported during FSI organization query of the number of found organizations
exceeds 1000.
Access Channel
API
Possible Causes
The number of FSI organizations in the system exceeds 1000.
Procedure
Verify that the system configuration is correct.
8.557 PORTAL95092
Description
The names of the files uploaded at two times are the same.
Scenario
This error is reported when the uploaded printing template file name is the same as that of the
resource template file.
Access Channel
Web
Possible Causes
Procedure
Ensure that the name of the uploaded file is consistent.

Copyright © Huawei
Mobile Money
8.558 PORTAL95093
Description
The printing template format is incorrect.
Scenario
This error is reported when the customer printing information is created but the printing
template is incorrect.
Access Channel
Web
Possible Causes
The printing template format is incorrect.
Procedure
Ensure that the printing template format is correct.
8.559 PORTAL95095
Description
The status of the bank statement entry whose ID is {0} cannot be changed from {1} to {2}.
 {0}: BSE detail ID.

 {1}: BSE original status.
 {2}: BSE new status.
Scenario
This error is reported when the bank statement entry status is changed from {1} to {2}.
Access Channel
POS
Possible Causes
The status of the bank statement entry whose ID is {0} cannot be changed from {1} to {2}.
Procedure
Refresh the page and select the correct bank statement entry.

Copyright © Huawei
Mobile Money
8.560 PORTAL95097
Description
The key cannot be activated.
Scenario
This error is reported when the key in draft state fails to be activated because there are keys in
Active state with the same type and zone.
Access Channel
POS
Possible Causes
There are keys in Active state with the same type and zone.
Procedure
Ensure that no key with the same type and zone is in Active state.
8.561 PORTAL95099
Description
The key fails to be exported.
Scenario
This error is reported when the key fails to be exported.
Access Channel
POS
Possible Causes
There are no keys that are of the ZMK type and in Active state.
Procedure
Ensure that there are keys that are of the ZMK type and in Active state. If the fault persists,
contact Huawei technical support.

Copyright © Huawei
Mobile Money
8.562 PORTAL95101
Description
The uploaded XML file does not match the selected bulk type.
Scenario
This error is reported when an operator selects the XML-type bulk type during bulk task
creation but the uploaded XML file does not match the bulk type.
Access Channel
Web(Bulk)
Possible Causes
The uploaded XML file does not match the selected bulk type.
Procedure
Ensure that the bulk type corresponds to the uploaded XML template.
8.563 PORTAL95103
Description
The role information fails to be modified.
Scenario
This error is reported when an SP operator submits a request for modifying a role but the role
has been released by another operator.
Access Channel
POS
Possible Causes
The role status has been modified by another operator.
Procedure

Copyright © Huawei
Mobile Money
8.564 PORTAL95104
Description
The check rule fails to be added.
Scenario
This error is reported when an SP or organization operator configures Verification Rule Where
Credit Party Is Organization on the product details tab page on the organization details page
but the check rule type has already been configured for the product to be added.
Access Channel
POS
Possible Causes
The current product already contains the same check rule type.
Procedure
Select a correct check rule type.
8.565 PORTAL95105
Description
The KYC field already exists in the list and cannot be added again.
Scenario
This error is reported when a KYC field fails to be added because the KYC field already
exists in the list.
Access Channel
Web
Possible Causes
Procedure
Add a KYC field that does not exist in the list.

Copyright © Huawei
Mobile Money
8.566 PORTAL95106
Description
The addtionnalInfo field is not set when operations are performed on entries.
Scenario
This error is reported when operations are performed on entries but the addtionnalInfo field is
not set.
Access Channel
POS
Possible Causes
The addtionnalInfo field is not set when operations are performed on entries.
Procedure
Set the addtionnalInfo field.
8.567 PORTAL95107
Description
Sequence update fails.
Scenario
This error is reported if the Sequence fails to be updated.
Access Channel
API
Possible Causes
Sequence update fails.
Procedure
Check Sequence configuration.

Copyright © Huawei
Mobile Money
8.568 PORTAL95108
Description
The cache fails to be refreshed.
Scenario
This error is reported if the cache fails to be refreshed.
Access Channel
API
Possible Causes
The cache fails to be refreshed.
Procedure
Check cache configuration.
8.569 PORTAL95109
Description
Deletion failed.
Scenario
This error is reported when the XML template to be deleted is mapped to an Excel template.
Access Channel
Web
Possible Causes
Deletion failed.
Procedure
Delete the mapping in the Excel template and then try again.

Copyright © Huawei
Mobile Money
8.570 PORTAL95110
Description
The export fails.
Scenario
This error is reported during reconciliation record export if the number of exported records
exceeds the threshold.
Access Channel
Web
Possible Causes
The number of records exported at a time cannot exceed the threshold specified in the system.
Procedure
1. Choose My FunctionsFinanceReconciliation Management Finance ParameterSystem
Parameter ItemsFinancial Generic Parameters. 2. Modify the conditions and export the
records again.
8.571 PORTAL95111
Description
The Dompetku customer fails to be queried.
Scenario
This error is reported when the Dompetku customer fails to be queried.
Access Channel
POS
Possible Causes
The Dompetku customer fails to be queried.
Procedure
Verify that the interface is normal.

Copyright © Huawei
Mobile Money
8.572 PORTAL95112
Description
Permission assignment fails.
Scenario
This error is reported when permission assignment fails. During permission adding or
modification, a role cannot have multiple menu permissions of the Promotion.
Access Channel
Web
Possible Causes
A role can be assigned with only one Promotion menu permission.
Procedure
Ensure that a role is assigned with only one of the following Promotion menu permissions:
Promotion Release, Promotion Template Approve, Promotion Template, Promotion Rule, and
Promotion Rule.
8.573 PORTAL95113
Description
The key import file does not exist or is in incorrect format. The file can contain only two
rows: one row is the key and the other row is the check value.
Scenario
This error is reported if the key import file does not exist or is in incorrect format.
Access Channel
POS
Possible Causes
The key import file does not exist or is in incorrect format. The file can contain only two
rows: one row is the key and the other row is the check value.
Procedure
Ensure that the key import file exists and is in correct format.

Copyright © Huawei
Mobile Money
8.574 PORTAL95114
Description
The key fails to be imported because the check value fails to be verified.
Scenario
This error is reported if the key fails to be imported because the check value fails to be
verified.
Access Channel
POS
Possible Causes
The key fails to be imported because the check value fails to be verified.
Procedure
Ensure that the key to import matches with the check value.
8.575 PORTAL95115
Description
The Dompetku MSISDN corresponding to the organization short code {0} cannot be empty.
{0} indicates the organization short code.
Scenario
This error is reported when the Dompetku MSISDN corresponding to the organization short
code is empty.
Access Channel
POS
Possible Causes
The Dompetku MSISDN corresponding to the organization short code {0} is empty.
Procedure
Ensure that the Dompetku MSISDN is not empty.

Copyright © Huawei
Mobile Money
8.576 PORTAL95116
Description
The URL entered is incorrect. Please enter a correct URL.
Scenario
The error is reported when an operator enters a URL containing invalid keywords to access
the system.
Access Channel
Web
Possible Causes
When accessing the system, the URL entered by the operator contains invalid keywords.
Procedure
Confirm and enter a correct URL.
8.577 PORTAL95117
Description
The Dompetku system returns the error information {0}.
Scenario
This error is reported when querying a customer with wrong PIN or user name in the
Dompetku system.
Access Channel
Web
Possible Causes
PIN or user name is wrong.
Procedure
Contact the owner of the Dompetku system.

Copyright © Huawei
Mobile Money
8.578 PORTAL95118
Description
The URL is invalid.
Scenario
This error is reported when the entered URL contains invalid characters.
Access Channel
Web
Possible Causes
The entered URL contains invalid characters.
Procedure
Verify that the entered URL does not contain invalid characters.
8.579 PORTAL95119
Description
The CreditLimit setting fails to be submitted.
Scenario
This error is reported when CreditLimit configured and submitted in AccountType but the
configured three attributes are incorrect.
Access Channel
Web
Possible Causes
The configured attributes are incorrect.
Procedure
Set Balance Direction to Positive, Allow Overdraft to Yes, and Real-time to Yes.

Copyright © Huawei
Mobile Money
8.580 PORTAL95120
Description
The credit limit is less than 0, greater than the limitation, or empty.
Scenario
This error is reported when the credit limit is less than 0, greater than the limitation, or empty.
Access Channel
Web
Possible Causes
The credit limit is less than 0, greater than the limitation, or empty.
Procedure
Ensure that the credit limit is not empty and is greater than or euqal to 0 and less than or equal
to the limitation.
8.581 PORTAL95121
Description
The added configuration already exists.
Scenario
This error is reported when an SP operator configures to verify the case-sensitiveness of KYC
fields but the added configuration already exists.
Access Channel
Web
Possible Causes
The added configuration already exists.
Procedure
Enter configuration that does not exist in the system.

Copyright © Huawei
Mobile Money
8.582 PORTAL95122
Description
The TPS reserved for the system task is less than the real-time TPS.
Scenario
This error is reported when the TPS reserved for the system task on the Bulk TPS
configuration page is less than the real-time TPS.
Access Channel
Web
Possible Causes
The TPS reserved for the system task is less than the real-time TPS.
Procedure
Ensure that the TPS reserved for the system task is greater than or equal to the real-time TPS.
8.583 PORTAL95123
Description
Search criteria and search results cannot be set to No for all items.
Scenario
This error is reported when all the search criteria or search results are set to No during search
identity configuration.
Access Channel
Web
Possible Causes
Search criteria and search results cannot be set to No for all items.
Procedure
Ensure that the display is set to Yes for at least one item of the search criteria or search results.

Copyright © Huawei
Mobile Money
8.584 PORTAL95124
Description
When an IMT provider is added, at least one of receiveName and SendName must be set.
Scenario
This error is reported when an IMT provider is added but both receiveName and SendName
are empty.
Access Channel
POS
Possible Causes
When an IMT provider is added, at least one of receiveName and SendName must be set.
Procedure
Ensure that at least one of receiveName or SendName is set.
8.585 PORTAL95125
Description
When a routing table is added, MSISDN Prefix or Factor already exists in the system.
Scenario
This error is reported when a routing table is added but MSISDN Prefix or Factor already
exists in the system.
Access Channel
POS
Possible Causes
When a routing table is added, MSISDN Prefix or Factor already exists in the system.
Procedure
Ensure that the data is correct.

Copyright © Huawei
Mobile Money
Error Codes Reference A Acronyms and Abbreviations
A Acronyms and Abbreviations
A
AG access gateway
The access gateway provides various
channels or interfaces for third parties to
access the Mobile Money System. It
accepts business operation and transaction
requests from third parties and dispatches
the requests to the corresponding back-end
servers.
AML anti money laundering
Actions taken to in accordance with laws
to prevent the crime of disguising or
concealing sources of income.
API application programming interface
An application programming interface is a
particular set of rules and specifications
that are used for communication between
software programs.
ATM automatic teller machine
An automatic teller machine or automated
teller machine is an electronic device
which allows a bank's customers to make
cash withdrawals and check their account
balances at any time without the need for a
human teller. Many ATMs also allow
people to deposit cash or checks, transfer
money between their bank accounts or
even buy postage stamps.
B
BC bulk center

Copyright © Huawei
Mobile Money
The bulk center is used to improve the

service processing and management
efficiency. Bulk operations and bulk
payment are required in the Mobile Money
system. The Bulk Center provides the
capabilities of managing bulk task
schedules and controlling bulk task
execution traffic.
BCR business configuration repository
BCS backend core service
BTS bulk task scheduler
BDI big data integration
The big data integration is part of the data
warehouse and a specialized data
integration tool that can be used to process
massive data.
BO business operation
Business operations are required to support
service provider or organizations in the
day-to-day operations and product
management.
C
C2O customer to organization
CCH customer care handset
CNS customer name search
When the customer initiates either the send
money request or the pay bill request via
STK, the recipient name can be prompted
on the customer's phone via USSD push.
The customer can then confirm whether
the recipient prompted is the intended one.
CRC cyclic redundancy code
A class of linear error detecting codes
which generate parity check bits by
finding the remainder of a polynomial
division.
CRL certification revoke list
D
DB database
A database stores a combination of data.
Serving various applications, the data is
configurable and has no harmful or

Copyright © Huawei
Mobile Money
unnecessary redundancy. The data is

stored separately from the relevant
programs. You can use a common and
controllable method to insert new data into
the database in addition to modifying and
searching the data in the database. If
several databases totally separated in
structure exist in a system, the system
contains a database combination.
DE data extractor.
An organization or system which is
authorized to extract customer and
organization data from the mobile money
system.
DIP data integration platform
E
EFT electronic funds transfer
EVC electronic voucher center
A service center that provides recharge
and payment functions for subscribers
based on virtual recharge cards. Carriers
can issue virtual recharge cards by setting
up distributor channel in the tree mode.
Compared with traditional recharge based
on real recharge cards, recharge based on
virtual recharge cards saves card costs and
enables carriers to understand precise
transaction and inventory information in
time.
EVO evolution Vodafone
F
FI financial institution
Finance institution is a third party which
cooperates with the Mobile Money system
to provide savings, loans, and insurance
services to customer. It is typically a bank.
FSI financial service integration
Financial service provided by the Mobile
Money system on behalf of finance
institution (FI) to customer, such as
deposit money to account within FI or
withdraw money from account within FI to
Mobile Money system.

Copyright © Huawei
Mobile Money
G
GL general ledger
The general ledger is a collection of the
group of accounts that supports the value
items shown in the major financial
statements. The general ledger can be
supported by one or more subsidiary
ledgers that provide details for accounts in
the general ledger.
GUI graphical user interface
A visual computer environment that
represents programs, files, and options
with graphical images, such as icons,
menus, and dialog boxes, on the screen.
H
HTTPS secure hypertext transfer protocol
An HTTP protocol that runs on top of
transport layer security (TLS) and Secure
Sockets Layer (SSL). It is used to establish
a reliable channel for encrypted
communication and secure identification
of a network web server. For details, see
RFC2818.
I
IC identity center
The IC is responsible for managing all
identities in the Mobile Money System.
The Identity Center provides identity
management related functions, including
identity lifecycle management, security
credential lifecycle management, device
lifecycle management, product life cycle
management, and permission management.
In addition, the Identity Center also
provides services for identities, such as
authentication, authorization, validation.
The Identity Center is also the entry for
account management, such as account
lifecycle management.
ICCID integrated circuit card identifier
Each SIM is internationally identified by
its integrated circuit card identifier
(ICCID). ICCIDs are stored in the SIM
cards and are also engraved or printed on
the SIM card body during a process called
personalization.

Copyright © Huawei
Mobile Money
IMT International Money Transfer

IP Internet Protocol
ISO International Organization for
Standardization
An international association that works to
establish global standards for
communications and information
exchange. Primary among its
accomplishments is the widely accepted
ISO/OSI reference model, which defines
standards for the interaction of computers
connected by communications networks.
J
JDBC Java database connectivity
A Java language that specifies how a piece
of client software accesses the application
programming interface (API) of the
database and offers methods for querying
and updating data in the database. JDBC is
also a trademark of SUN Microsystems
registered for relational databases.
K
KYC know your customer
KYC information indicates detailed
identity information that can be used as a
basis for profiling.
M
MB megabyte
MNP mobile number portability
A service with which a subscriber can
switch from the network of a carrier to the
network of another carrier with the
original mobile number.
MNO mobile network operator
A company that has a network
infrastructure, sells network capacities in
bulk, and provides transparent network
channels.
MOM Message-oriented Middleware
The MOM is used to send and distribute
messages.

Copyright © Huawei
Mobile Money
MSISDN mobile station international ISDN number

MQ message queue
N
NC notification center
The NC is used for generating and sending
notifications to identities. When a
notification needs to be issued, the
business module sends a notification
issuing request to NC. NC composes the
notification message and sends it to the
recipient through the appointed channel.
NC can also receive a message and send it
to the recipient.
NE network element
An entity that contains hardware and
software. An NE has at least one main
control board that manages and monitors
the entire network element. The NE
software runs on the main control board.
O
O2C organization to customer
OWA organization web application
P
PIN personal identification number
A code used by a mobile user in
conjunction with a SIM card to complete a
call.
PG payment gateway
The payment gateway provides interfaces
for merchants to access the Mobile Money
system. It receives transaction requests
from merchants, distributes them to the
Mobile Money system for processing, and
then sends the transaction result to
merchants.
R
RPC remote procedure call protocol
The RPC is used as the service registration
center in the Mobile Money system

Copyright © Huawei
Mobile Money
S
SFTP secure file transfer protocol
A network protocol designed to provide
secure file transfer over SSH.
SMS short message service
Short message service is a service that
enables mobile phones to send and receive
and enables service providers to send text
messages with up to 140 bytes.
SMSC short message service center
A node on the network, which implements
the functions of receiving the text
messages submitted by an MS,
determining the current status of a
message receiver, and delivering messages
to the proper destination users or storing
messages for subsequent delivery.
SMPP short message peer to peer
An open message-transfer protocol that
enables short message entities (SMEs)
outside the mobile network to interface
with an SMSC. Nonmobile entities that
submit messages to, or receive messages
from an SMSC are known as External
Short Message Entities (ESMEs).
SOAP simple object access protocol
A type of protocol that is lightweight,
simple, and XML-based. It is designed to
exchange structured information at web.
SP service provider
An entity that offers service subscriptions
to individual subscribers and contracts
with carriers to implement services. A
service provider may contract with more
than one carrier.
SQL structured query language
A database query and programming
language widely used for accessing,
querying, updating, and managing data in
relational database systems.
STK SIM application toolkit
SIM application toolkit is commonly
referred to as STK, which is a standard of
the GSM system and enables the
Subscriber Identity Module (SIM) to
initiate actions for various value-added

Copyright © Huawei
Mobile Money
services.
SWA SP web application
T
TC transaction center
The transaction center is used to process
external business and transaction requests
in business operations. It is also used to
manage accounts in the mobile money
platform. It provides the accounting
capability for the Transaction Engine and
provides account type customization and
account life cycle maintenance capabilities
for SPs.
TPS transaction per second
A performance indicator which indicates
the number of transactions that can be
processed by the system per second.
U
UCC unified configuration center
UDH user data header
UMC unified menu center
The unified menu center provides menu
information for handset customers and
collects service parameters for customer
transactions.
URI uniform resource identifier
A uniform resource identifier is a member
of this universal set of names in registered
namespaces and addresses referring to
registered protocols or namespaces. URI is
used to locate available resources on the
Web, including HTML documents,
images, video clips, and programs.
URL uniform resource locator
An address that uniquely identifies a
location on the Internet. A URL is usually
preceded by http://, as in
http://www.microsoft.com. A URL can
contain more details, such as the name of a
hypertext page, often with the file name
extension .html or .htm.
USSD unstructured supplementary service data
Unstructured supplementary service data is

Copyright © Huawei
Mobile Money
a new interactive data business in the GSM

network, using which a customer can enter
certain predefined numbers or symbols,
such as *#, and then presses the send key
to send a command to the system. The
system will then provide the corresponding
service for the customer.
W
WF workflow
The automation of a business process, in
whole or part, during which documents,
information or tasks are passed from one
participant to another for action, according
to a set of procedural rule.

Copyright © Huawei

Mobile Money V100R003 Error Codes Reference 01

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Mobile Money V100R003 Error Codes Reference 01

Caricato da

Copyright:

Formati disponibili

Mobile Money

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2017-07-28) Huawei Proprietary and Confidential i

About This Document

Indicates an imminently hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Issue 01 (2017-07-28) Huawei Proprietary and Confidential ii

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Issue 01 (2017-07-28) Huawei Proprietary and Confidential iii

Issue 01 (2017-07-28) Huawei Proprietary and Confidential iv

Issue 01 (2017-07-28) Huawei Proprietary and Confidential v

1 Error Code Description

About This Chapter

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 1

1.2 View Method

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 2

About This Chapter

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 3

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 4

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 5

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 6

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 7

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 8

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 9

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 10

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 11

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 12

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 13

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 14

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 15

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 16

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 17

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 18

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 19

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 20

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 21

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 22

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 23

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 24

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 25

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 26

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 27

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 28

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 29

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 30

{0}: indicates the name of an network element (NE).

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 31

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 32

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 33

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 34

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 35

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 36

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 37

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 38

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 39

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 40

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 41

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 42

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 43

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 44

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 45