Payment Related Errors

This page provides a comprehensive list of potential error codes that may arise during the actual payment transaction, determined by either the acquirer or the issuer.

`PY0009` - Payment does not exist

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS


Error Code and Message	`PY0009` - Payment does not exist
HTTP Code	`404`
Problem	The API call was made with a `paymentId` or `rrn` that does not exist or has no corresponding payment intent.
What you should do	The API Consumer should verify the existence of the `paymentId` or `rrn` via the Maya Manager and use the correct values to retry the intended operation.

`PY0017` - Merchant not found

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS CHECKOUT-QRPHDYNAMIC QRPH


Error Code and Message	`PY0017` - Merchant not found
HTTP Code	`404`
Problem	There is a problem with the configuration of your merchant account.
What you should do	If the error was encountered in PRODUCTION, contact [email protected]. If the error was encountered during sandbox integration, create a ticket via Maya Developer Hub Service Desk and provide the following: payment ID and/or request reference number the error code you encountered and its corresponding Maya Developer Hub link (this is to make sure that you have exhausted all your efforts and resources in Maya Developer Hub to solve the error) the log of the API request where you experienced the error

`PY0019` - Forbidden

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS


Error Code and Message	`PY0019`- Forbidden
HTTP Code	`401`
Problem	The API call was made with an API key that does not have the necessary permissions to do the operation.
What you should do	The API Consumer should review the Welcome Letter (sent by Maya to your nominated email address) to confirm that the feature intended to be used (e.g. Authorize and Capture) has been activated.

`PY0037` - Currency is not supported

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS


Error Code and Message	`PY0037` - Currency is not supported
HTTP Code	`400`
Problem	The API call was made with the wrong currency.
What you should do	API Consumers are restricted to utilizing only the specified currency within their integration. Ensure to pass the currency value that has been configured.

`PY0044` - Payment is invalid

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS CHECKOUT-QRPH


Error Code and Message	`PY0044` - Payment is invalid
HTTP Code	`400`
Problem	A problem was encountered while processing the payment.
What you should do	The API Consumer can validate the error message to determine the actual error. If the error pertains to missing parameters or invalid values, the API consumer should review and ensure that the correct parameters and values are correct before retrying. Otherwise, report the error to Maya: If the error was encountered in PRODUCTION, contact [email protected] . If the error was encountered during sandbox integration, create a ticket via the Maya Developer Hub Service Desk and provide the following: payment ID and/or request reference number the error code you encountered and its corresponding Maya Developer Hub link (this is to make sure that you have exhausted all your efforts and resources in Maya Developer Hub to solve the error) the log of the API request where you experienced the error a screenshot of your transaction in Maya Manager

`PY0045` - Payment is not available for void

HTTP Status: 400

Product/s: INVOICE CHECKOUTVAULTPLUGINS

You will encounter this error if the payment is not eligible for void. Similarly, attempting to void the transaction beyond 12am GMT+8 of the transaction date will result in this error.

Validate the payment by getting the payment status via Retrieve Payment via ID endpoint.

Kindly also refer to the Manual Capture document for the transition rules.

You may execute and validate voids using the Maya Business Manager.

`PY0046` - Refund does not exist

HTTP Status: 404

Product/s: INVOICE CHECKOUTVAULTPLUGINS

You will encounter this error if refundId does not exist.

Validate if you are using a correct refundId and it is not currently deleted, then retry the request.

You may execute and validate refunds using the Maya Business Manager.

`PY0047` - Payment is ineligible for refund

HTTP Status: 401

Product/s: INVOICE CHECKOUTVAULTPLUGINS

This error can be caused by either of these reasons:

The transaction being refunded is not yet eligible according to cut-off rules. Refunds can only be initiated after 12am GMT+8 of the transaction date, which means you may have to wait until the start of the next day.
The transaction being refunded is older than 180 days.

You may execute and validate refunds using the Maya Business Manager.

`PY0048` - Requested refund amount is greater than the original amount

HTTP Status: 400

Product/s: INVOICE CHECKOUTVAULTPLUGINS

This error will occur when the requested amount to refund is greater than the original amount.

Validate your request and make sure the requested refund amount is the same as the original.

You may execute and validate refunds using the Maya Business Manager.

`PY0057` - The payment has expired and cannot be processed

HTTP Status: 422

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS

You will encounter this error when a transaction exceeds the given time limit.

Once a payment has expired, it cannot be processed any further. If the user still wishes to proceed with the payment, a new payment transaction must be created.

You can also get and validate the payment status by calling the Retrieve Payment Status.

`PY0058` - The merchant indicated does not have P2M services enabled

HTTP Status: 403

You will encounter this error when P2M service is not activated in your merchant profile.

ℹ️ Please escalate the issue to your Relationship Manager.

`PY0063` - Void does not exist

HTTP Status: 404

Product/s: INVOICE CHECKOUTVAULTPLUGINS

Will be encountered when there are no void requests for the paymentId provided.

Make sure you have supplied the correct paymentId and try again.

You may execute and validate voids using the Maya Business Manager.

`PY0065` - This merchant has no customizations present

HTTP Status: 404

This error may happen from Get or Delete Customizations API. When encountered, it means that the merchant’s request to Get or Delete is invalid because there are no page customizations to begin with. No further action required.

`PY0068` - Payment not executed due to authorization failure

HTTP Status: 400

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS

This is a systematic error on Authentication. Kindly retry the transaction.

ℹ️ If the error persists even after multiple retries, please escalate the issue to Support.

`PY0070` - Scheme is unsupported by merchant


Error Code and Message	`PY0070` - Scheme is unsupported by the merchant
HTTP Code	`400`
Problem	The card used for the transaction is from a card scheme not configured to the merchant’s account.
What you should do	As a merchant, confirm with your Relationship Manager that your expected card scheme has been configured. The card schemes supported by Maya are: Visa MasterCard AMEX JCB

`PY0072` - Transaction cannot be processed. Cannot refund a transaction before cut off time

HTTP Status: 400

Product/s: INVOICE CHECKOUTVAULTPLUGINS

Refunds can only be initiated AFTER 12AM GMT+8 of the transaction date.

`PY0073` - Transaction cannot be processed. Cannot void a transaction after cut off time

HTTP Status: 400

Product/s: INVOICE CHECKOUTVAULTPLUGINS

Authorized payments can only be voided BEFORE the 12AM cut-off time.

`PY0082` - Refund already exists

HTTP Status: 400

Product/s: INVOICE CHECKOUTVAULTPLUGINS

Will be encountered when paymentId already has a refund request.

You may execute and validate refunds using the Maya Business Manager.

`PY0093` - Payment has already been updated

HTTP Status: 409

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS

In rare cases, the error is encountered when concurrent calls to refund the transactions have been issued and the transaction reached a non-refundable state.

`PY0094` - Payment is not available for capture

HTTP Status: 400

Product/s: INVOICE CHECKOUTVAULTPLUGINS

Will be encountered when the payment state is not allowed to be captured.

Validate the payment by getting the payment status via
Retrieve Payment via ID endpoint.

Kindly also refer to the Manual Capture document for the transition rules.

`PY0095` - Amount must be less than or equal to amount authorized

HTTP Status: 400

Product/s: INVOICE CHECKOUTVAULTPLUGINS

This error will occur when the requested amount to capture is greater that the authorization amount.

Refer to Manual Capture and follow the recommended steps.

`PY0096` - Amount must be equal to amount authorized

HTTP Status: 400

Product/s: INVOICE CHECKOUTVAULTPLUGINS

This error will occur when the requested amount to capture is not equal to the authorization amount.

Refer to Manual Capture and follow the recommended steps.

`PY0100` - Authentication failed

HTTP Status: 400

Product/s: INVOICE CHECKOUTVAULTPLUGINS

⚠️ Applicable for Card payments only.

You will encounter this error when the user fails to authenticate the request in 3DS.

`PY0101` - Acquirer decline due to high risk

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS CHECKOUT-QRPH


Error Code and Message	`PY0101` - Acquirer decline due to high risk
HTTP Code	`400`
Problem	The acquirer has declined the payment transaction because of suspected fraud. This error happens when the merchant’s customer uses a payment method, like a card, that is high risk or suspected fraud.
What you should do	The API Consumer or the merchant should advise the customer to create a new transaction using a different payment method or card.

`PY0103` - Payment is already expired

HTTP Status: 400

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS

You will encounter this error when a transaction exceeds the given time limit.

Once a payment has expired, it cannot be processed any further. If the user still wishes to proceed with the payment, a new payment transaction must be created.

You can also get and validate the payment status by calling the Retrieve Payment Status.

`PY0104` - Reference number is linked to multiple payments

HTTP Status: 400

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS

You will encounter this error when the payment you are trying to process using the Reference number is linked to multiple payment records.

If you intend to process specific payments, you can try calling the endpoints that will use paymentId.

`PY0113` - Partial refund is not allowed for this transaction

HTTP Status: 200

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS

You will encounter this error if the payment is not eligible for partial refunds.

Validate the payment by calling Retrieve Payment via ID endpoint.

Kindly also refer to the Manual Capture document for the transition of status and refund rules.

You may execute and validate refunds using the Maya Business Manager.

`PY0116` - Transaction could not be completed

HTTP Status: 400

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS CHECKOUT-QRPH

The operation you are trying to do with the transaction has encountered error.

ℹ️ If the error persists even after multiple retries, please escalate the issue to Support by providing any of the following:
-paymentId
-transactionId

`PY0124` - Transaction could not be verified

HTTP Status: 400

Product/s: INVOICE CHECKOUTVAULTPLUGINS

⚠️ Applicable for Card payments only.

Reason for this error may vary depends on the 3DS verification.

`PY0137` - Decline due to high risk

HTTP Status: 400

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS

You will encounter this error when the transaction was suspected to be fraud.

ℹ️ Please escalate the issue to Support by providing any of the following:
-paymentId

`PY0138` - Acquirer decline

HTTP Status: 400

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS

You will encounter this error when the transaction was suspected to be fraud.

ℹ️ Please escalate the issue to Support by providing any of the following:
-paymentId

`PY0146` - Login cancelled by user

HTTP Status: 200

Product/s: PAY WITH MAYA

You will encounter this error when the customer decides to cancel the request during user login.