Send Remittance Errors

This document is in active development. As a pioneer merchant, you will be informed of new changes. Visit our Release Notes for more details.

This page provides a comprehensive list of potential error codes that may arise when calling Maya's Remittance API.


General Errors

REMGTW0001

HTTP Status: 400

One or more fields have invalid values (headers or body). Please review the list of invalid fields provided in the response.


REMGTW0002

HTTP Status: 422

You are not allowed to use the service because you are not yet onboarded in Maya’s Remittance system. Please contact your Maya Relationship Manager to check your onboarding status.


REMGTW0003

HTTP Status: 422

You are not allowed to transact or use the service because your status is inactive. Please contact your Maya Relationship Manager to check and update your status.


REMGTW0004

HTTP Status: 422

You’re trying to transact a remittance that is invalid (e.g. specified claim agent is from the unaffiliated remittance company). Kindly use a valid remittance offering.


REMGTW0005

HTTP Status: 422

You’re trying to transact a remittance that is inactive (e.g. specified claim agent is from the unaffiliated remittance company). Kindly use a valid remittance offering.


REMGTW0006

HTTP Status: 422

You are not allowed to use the remittance offering. Kindly reach out to your Maya Relationship Manager for the list of remittance offerings that you may use.


REMGTW0007

HTTP Status: 422

You’re using a remittance offering that is inactive. Kindly reach out to your Maya Relationship Manager for the list of remittance offerings that you may use.


Server Related Errors

REMGTW0000

HTTP Status: 500

An unexpected error occurred while processing the transaction. Kindly contact your Maya Relationship Manager to assist you in checking and getting more information.


REMDDR0000 REMDDR0001

HTTP Status: 500

An unexpected error occurred while validating the accounts. Kindly contact your Maya Relationship Manager to assist you in checking and getting more information.


REMDDR0502 REMDDR0503

HTTP Status: 503

The account cannot be validated due to intermittence within the service. Kindly retry the transaction later using a new x-idempotency-key.


REMDDR0504

HTTP Status: 504

The account cannot be validated due to timeouts encountered within the service. Kindly retry the transaction later using a new x-idempotency-key.


REMUNS0000 REMUNS0001

HTTP Status: 500

An unexpected error occurred while validating Maya Center network. Kindly contact your Maya Relationship Manager to assist you in checking and getting more information.


REMUNS0502 REMUNS0503

HTTP Status: 503

The Maya Center network cannot be validated due to intermittence within the service. Kindly retry the transaction later using a new x-idempotency-key.


REMUNS0504

HTTP Status: 504

The Maya Center network cannot be validated due to timeouts encountered within the service. Kindly retry the transaction later using a new x-idempotency-key.


REMCPM0000 REMCPM0001

HTTP Status: 500

An unexpected error occurred while validating your account. Kindly contact your Maya Relationship Manager to assist you in checking and getting more information.


REMCPM0002 REMCPM0503

HTTP Status: 503

Your account cannot be validated due to intermittence within the service. Kindly retry the transaction later using a new x-idempotency-key.


REMCPM0004

HTTP Status: 504

Your account cannot be validated due to timeouts encountered within the service. Kindly retry the transaction later using a new x-idempotency-key.


REMRMS0000 REMRMS0001

HTTP Status: 500

An unexpected error occurred while screening the participants. Kindly contact your Maya Relationship Manager to assist you in checking and getting more information.


REMRMS0502 REMRMS0503

HTTP Status: 503

The participant's screening cannot be processed due to intermittence within the service. Kindly retry the transaction later using a new x-idempotency-key.


REMRMS0504

HTTP Status: 504

The participant's screening cannot be processed due to timeouts encountered within the service. Kindly retry the transaction later using a new x-idempotency-key.


REMCRG0000

HTTP Status: 500

An error occurred while processing the balance transfer. Kindly contact your Maya Relationship Manager to assist you in checking and getting more information.


REMCRG0001

HTTP Status: 500

The balance transfer cannot proceed due to internal restrictions. Kindly contact your Maya Relationship Manager to assist you in checking and getting more information.


REMCRG0502 REMCRG0503

HTTP Status: 503

The balance transfer cannot be processed due to intermittence within the service. Kindly retry the transaction later using a new x-idempotency-key.


REMCRG0504

HTTP Status: 504

The balance transfer cannot be processed due to timeouts encountered within the service. Kindly retry the transaction later using a new x-idempotency-key.


Transaction Related Errors

REMGTW0010

HTTP Status: 422

The transaction you are confirming does not exist. Kindly initiate a transaction first.


REMGTW0011

HTTP Status: 422

The request you are trying to initiate has an existing transaction with the same request information. You can inspect the status of the existing transaction using the included ID. Otherwise, you can initiate the same request with a different x-idempotency-key.


REMGTW0012

HTTP Status: 422

The transaction you are confirming already reached its confirmation deadline. Kindly initiate a transaction again using a different x-idempotency-key.


REMGTW0013

HTTP Status: 422

The transaction you are confirming does not exist. Kindly initiate a transaction first.


REMGTW0014

HTTP Status: 422

You’re trying to initiate a request with the same x-idempotency-key but with a different request body. If this is a new transaction, please use a different x-idempotency-key.


Account Validation Errors

REMGTW0008

HTTP Status: 422

The combination of source and receiver accounts for remittance is not supported for this client. Kindly reach out to your Maya Relationship Manager for further information.


REMGTW0009

HTTP Status: 422

The combination of source and receiver accounts for remittance is inactive for this client. Kindly reach out to your Maya Relationship Manager for further information.


REMGTW0015

HTTP Status: 422

The receiver name does not match the receiver account name on the record. Please check with the customer and ask them to provide the correct details.


REMDDRS001

HTTP Status: 422

The source account in Maya does not exist. Try another account and make sure you use the valid one.


REMDDRS002

HTTP Status: 422

The source account is not allowed to participate in a remittance. Try another account and make sure you use the valid one.


REMDDRT001

HTTP Status: 422

The target account in Maya does not exist. You may ask the sender to provide a valid receiver account.


REMDDRT002

HTTP Status: 422

The target account is not allowed to participate in a remittance. You may ask the sender to provide a valid receiver account.


REMUNSS001

HTTP Status: 422

The source account is not in the Maya Center network. Kindly check the source account in your request if it is a valid Maya Center account.


REMUNST001

HTTP Status: 422

The target account is not in the Maya Center network. Kindly check the target account in your request if it is a valid Maya Center account.


REMCPMS001

HTTP Status: 500

The source account in Maya does not have an organization ID. Kindly contact your Maya Relationship Manager to assist you in checking and getting more information.


REMCPMS002

HTTP Status: 500

The organization ID of the source account in Maya does not exist. Kindly contact your Maya Relationship Manager to assist you in checking and getting more information.


REMCPMS003

HTTP Status: 422

You’re using a source account that is not associated with you. Kindly use a source account that you own.


REMRMSS001

HTTP Status: 422

The sender failed our sanction screening. Your system should handle this according to your business process.


REMRMSR001

HTTP Status: 422

The receiver failed our sanction screening. Your system should handle this according to your business process.


REMCRGS001

HTTP Status: 422

The source account does not exist in the specified financial institution. Try another account and make sure you use the valid one.


REMCRGS002

HTTP Status: 422

The source account is not allowed to participate in a remittance. Try another account and make sure you use the valid one.


REMCRGS003

HTTP Status: 422

The source account has an insufficient balance. Please request to replenish your source account and make sure it has sufficient balance before processing a remittance send.


REMCRGT001

HTTP Status: 422

The target account does not exist in the specified financial institution. You may ask the sender to provide a valid receiver account.


REMCRGT002

HTTP Status: 422

The target account is not allowed to participate in a remittance. You may ask the sender to provide a valid receiver account.


REMCRG0002

HTTP Status: 422

One of the accounts does not exist in the specified financial institution. Try another account and make sure you use the valid one.


REMCRG0003

HTTP Status: 422

One of the accounts is not allowed to participate in a remittance. Try another account and make sure you use the valid one.


REMCRG0004

HTTP Status: 422

The transaction count limit was exceeded for one of the accounts.


REMCRG0005

HTTP Status: 422

The transaction amount limit was exceeded for one of the accounts.