Money Movement Errors

Gateway Errors

HTTP Status	Description	What to do?
502	Gateway error	In cases that you have acquired and processing the `transferId` (like executing a transfer), it is recommended to validate the status of the transfer by calling the Retrieve a Transfer endpoint with the `transferId`. Otherwise, you may retry the request. ℹ️ When the error still persist after a number of retries, kindly raise it to [email protected].
503	Gateway error	In cases that you have acquired and processing the `transferId` (like executing a transfer), it is recommended to validate the status of the transfer by calling the Retrieve a Transfer endpoint with the `transferId`. Otherwise, you may retry the request. ℹ️ When the error still persist after a number of retries, kindly raise it to [email protected].
504	Gateway error	In cases that you have acquired and processing the `transferId` (like executing a transfer), it is recommended to validate the status of the transfer by calling the Retrieve a Transfer endpoint with the `transferId`. Otherwise, you may retry the request. ℹ️ When the error still persist after a number of retries, kindly raise it to [email protected].
No Code	Any timeout error	In cases that you have acquired and processing the `transferId` (like executing a transfer), it is recommended to validate the status of the transfer by calling the Retrieve a Transfer endpoint with the `transferId`. Otherwise, you may retry the request. ℹ️ When the error still persist after a number of retries, kindly raise it to [email protected].

General Errors

Code	HTTP Status	Description	What to do?
7011	400	Temporary failure encountered	In cases that you have acquired and processing the `transferId` (like executing a transfer), it is recommended to validate the status of the transfer by calling the Retrieve a Transfer endpoint with the `transferId`. Otherwise, you may retry the request. ℹ️ When the error still persist after a number of retries, kindly raise it to [email protected].
7012	400	The transaction is still processing or connection failure is encountered. The client is advised to retrieve the transfer to verify the actual status.	In cases that you have acquired and processing the `transferId` (like executing a transfer), it is recommended to validate the status of the transfer by calling the Retrieve a Transfer endpoint with the `transferId`. Otherwise, you may retry the request. ℹ️ When the error still persist after a number of retries, kindly raise it to [email protected].

During Create Transfer

Code	HTTP Status	Description	What to do?
1096	400	Transfer to the same account is not allowed. Usually applicable to funded partners if they try to add money to their Maya Corporate Account.	Align your use case and note that Money Movement prohibits using the same Maya account as the source and the receiver.
1301	400	Invalid Client-Id header.	Validate if you’re providing the correct Client ID values. ℹ️ When the error still persist after providing the correct values, kindly raise it to the following: Maya Developer Hub Service Desk for non production environment [email protected] for production environment or contact your Maya Relationship Manager.
1630	400	Invalid Product Type. Recipient type must always be PAYMAYA.	Validate if you’re providing correct values on the transfer request’s Recipient Type, it should be either of the following: TOKEN for Transfer Funds to Maya Wallet or Maya Mini Apps CODE for Add Money via Cash In Code ℹ️ When the error still persist after providing the correct values, kindly raise it to the following: Maya Developer Hub Service Desk for non production environment [email protected] for production environment or contact your Maya Relationship Manager.
2841	400	Recipient value is invalid.	Validate if you’re providing the correct values for the Recipient Value of the transfer request. Revisit the following references for the correct values: Transfer Funds to Maya Wallet or Maya Mini Apps Add Money via Cash In Code ℹ️ When the error still persist after providing the correct values, kindly raise it to the following: Maya Developer Hub Service Desk for non production environment [email protected] for production environment or contact your Maya Relationship Manager.
1646	400	The recipient type is not allowed to receive money from this partner. Must be PAYMAYA.
2856	400	The recipient is not a recognized PayMaya account.	Validate if you’re providing the correct values for the Recipient Value of the transfer request. Revisit the following references for the correct values: Transfer Funds to Maya Wallet or Maya Mini Apps Add Money via Cash In Code ℹ️ When the error still persist after providing the correct values, kindly raise it to the following: Maya Developer Hub Service Desk for non production environment [email protected] for production environment or contact your Maya Relationship Manager.
M001	400	No mother account defined for the partner. Usually appears if there are errors in onboarding a funded partner.	ℹ️ When the error still persist after providing the correct values, kindly raise it to the following: Maya Developer Hub Service Desk for non production environment [email protected] for production environment or contact your Maya Relationship Manager.
M003	400	Invalid Mother Account Product Type. Usually appears if there are errors in onboarding a funded partner.	ℹ️ When the error still persist after providing the correct values, kindly raise it to the following: Maya Developer Hub Service Desk for non production environment [email protected] for production environment or contact your Maya Relationship Manager.
M122	400	Recipient is inactive and cannot receive funds.	You will encounter this error when recipient’s account was not active - either closed per request of the user or not yet active. You may ask the user to coordinate with Maya Customer Care to check their account. ℹ️ Discuss with your Maya Relationship Manager to know more on handling and spiels.
M036	400	Add Money code is invalid. The recipient value isn’t found in the Add Money code records.	This usually happens when user provides an incorrect Add Money code or a code that is not generated from the Maya app. Make sure that the user generates the Add Money Code from their Maya App and provided it to your system.
M055	400	Amount does not match	Happens when the amount inputted by the customer is different from the amount currency and value provided by your system. Make sure that customer provided the correct details to proceed with the funding.
M056	400	Amount value does not match	Happens when the amount inputted by the customer is different from the amount value provided by your system. Make sure that customer provided the correct details to proceed with the funding.
M057	400	Amount currency does not match	Happens when the amount inputted by the customer is different from the amount currency provided by your system. Make sure that customer provided the correct details to proceed with the funding.
M132	422	Recipient funding is closed and cannot receive funds.	You will encounter this error when recipient’s account was closed - either closed per request of the user or got blocked due to suspicious activity. You may ask the user to coordinate with Maya Customer Care to check their account. ℹ️ Discuss with your Maya Relationship Manager to know more on handling and spiels.
M133	422	The recipient profile is not allowed to receive money from this partner. Consult with onboarding team what profiles are allowed	You will encounter this error when recipient’s account is not yet upgraded (KYC1). You may ask the user to upgrade their account prior to do funding. ℹ️ Discuss with your Maya Relationship Manager to know more on handling and spiels.

During Execute Transfer

⚠️ Most errors during execution are due to customer account problems (except for 6051 which would apply to your wallet account). These errors usually start with 60xx. You may safely prompt consumers about these errors.

Code	HTTP Status	Description	What to do?
6014	400	Invalid account Details.	You may ask the user to coordinate with Maya Customer Care to check their account.
6041	400	Recipient’s primary account marked as Lost	You will encounter this error when recipient’s account was not active - either closed per request of the user or not yet active. You may ask the user to coordinate with Maya Customer Care to check their account.
6043	400	Recipient’s primary account marked as Card Stolen	You will encounter this error when recipient’s account was not active - either closed per request of the user or not yet active. You may ask the user to coordinate with Maya Customer Care to check their account.
6051	400	Your funds are not enough to give to the customer.	You need to replenish the balance of your Maya Corporate Account. You may contact your Maya Relationship Manager for further assistance.
6054	400	Recipient’s primary account has expired.	You may ask the user to coordinate with Maya Customer Care to check their account.
6058	400	Recipient’s profile is not permitted to transact with this partner in our ledgers.	You may ask the user to coordinate with Maya Customer Care to check their account.
6061	400	Recipient has reached their Add Money limit (amount).	You may inform the user that they have already reached the wallet limit.
6065	400	Recipient has reached their Add Money limit (count).	You may inform the user that they have already reached the wallet limit.
6072	400	Partner’s account has reached its limit.	You reached your account limit. You may contact your Maya Relationship Manager for further assistance.
6076	400	Recipient’s primary account is Invalid.	You may ask the user to coordinate with Maya Customer Care to check their account.
6091	504	Internal ledger error.	In cases that you have acquired and processing the transferId (like executing a transfer), it is recommended to validate the status of the transfer by calling the Retrieve a Transfer endpoint with the transferId. Otherwise, you may retry the request. ℹ️ When the error still persist after a number of retries, kindly raise it to [email protected].
6096	400	Internal ledger error.	In cases that you have acquired and processing the transferId (like executing a transfer), it is recommended to validate the status of the transfer by calling the Retrieve a Transfer endpoint with the transferId. Otherwise, you may retry the request. ℹ️ When the error still persist after a number of retries, kindly raise it to [email protected].
6097	400	Internal ledger error.	In cases that you have acquired and processing the transferId (like executing a transfer), it is recommended to validate the status of the transfer by calling the Retrieve a Transfer endpoint with the transferId. Otherwise, you may retry the request. ℹ️ When the error still persist after a number of retries, kindly raise it to [email protected].
6098	504	Internal ledger timeout.	In cases that you have acquired and processing the transferId (like executing a transfer), it is recommended to validate the status of the transfer by calling the Retrieve a Transfer endpoint with the transferId. Otherwise, you may retry the request. ℹ️ When the error still persist after a number of retries, kindly raise it to [email protected].
6005	400	Internal ledger error.	In cases that you have acquired and processing the transferId (like executing a transfer), it is recommended to validate the status of the transfer by calling the Retrieve a Transfer endpoint with the transferId. Otherwise, you may retry the request. ℹ️ When the error still persist after a number of retries, kindly raise it to [email protected].
2896	504	Internal service timeout.	In cases that you have acquired and processing the transferId (like executing a transfer), it is recommended to validate the status of the transfer by calling the Retrieve a Transfer endpoint with the transferId. Otherwise, you may retry the request. ℹ️ When the error still persist after a number of retries, kindly raise it to [email protected].

Money Movement Errors

Error Codes

Payment APIs

Developer resources

More