Other Payment Errors

General Errors

2553 - Missing/invalid parameters

HTTP Status: 400

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

This message will appear if any of the mandatory request payload properties are absent or do not conform to the given specifications.

We suggest that you validate your request and ensure that you furnish all the required payload properties with accurate values.

---

PY0001 - Generic system error

HTTP Status: 400

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS

If an unspecified error occurs, this generic error code will be returned, and it is advisable to attempt the operation again.

---

PY0064 - Invalid JSON Format

HTTP Status: 400

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS

This error will arise if the payload request is not a valid JSON format. Please check your payload and ensure that you are sending the correct JSON format.

---

Server Related Errors

PY0013 PY0014 PY0015 PY0016 PY0040 PY0041 PY0059 PY0060 PY0066 PY0067 PY0069 PY0122 PY0143 PY0144 PY9999 - System has encountered a systematic error or is unreachable / timed out.

HTTP Status: 400

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

If you run into this error, take a moment to confirm the transaction. Use the GET https://pg-sandbox.paymaya.com/payments/v1/payment-rrns/{rrn} endpoint, inputting the requestReferenceNumber you've created to distinctly identify your payment transaction. If there's no response, go ahead and make another attempt to generate the payment transaction.

---

Third Party Errors

PY0114 - WeChat Service unreachable / timed out

HTTP Status: 400

Product/s: INVOICE CHECKOUTVAULTPLUGINS

WeChat service is unreachable or taking too long to respond. Kindly retry transaction.

---

PY0115 - WeChat Service error

HTTP Status: 400

Product/s: INVOICE CHECKOUTVAULTPLUGINS

This is a systematic error on WeChat Service. Kindly retry transaction.

---

PY0129 - GCash Service unreachable / timed out

HTTP Status: 400

Product/s: INVOICE CHECKOUTVAULTPLUGINS

GCash Service is unreachable or taking too long to respond. Kindly retry transaction.

---

PY0130 - GCash Service error

HTTP Status: 400

Product/s: INVOICE CHECKOUTVAULTPLUGINS

This is a systematic error on GCash Service. Kindly retry transaction.

---

PY0134 - ShopeePay Service unreachable / timed out

HTTP Status: 400

Product/s: INVOICE CHECKOUTVAULTPLUGINS

ShopeePay Service is unreachable or taking too long to respond. Kindly retry transaction.

---

PY0135 - ShopeePay Service error

HTTP Status: 400

Product/s: INVOICE CHECKOUTVAULTPLUGINS

This is a systematic error on ShopeePay Service. Kindly retry transaction.

---

Webhook Errors

PY0038 - Webhook does not exist

HTTP Status: 404

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS

If you encounter this error, it means that the registration of the webhook was unsuccessful.

Additionally, this error may also occur if the webhook endpoint is incorrect for a particular environment. Please note that the webhook endpoint differs between the sandbox environment and the production environment.

You may want to check if the registered webhook exist via Maya Manager or by calling the Get Webhooks endpoint.

---

PY0039 - Webhook already exists

HTTP Status: 400

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS

This error happens if webhook has already been created.

You may want to check if the registered webhook exist via Maya Manager or by calling the Get Webhooks endpoint.

To retry the request, you may delete the existing webhook and define a new one.

---

PY0091 - Payment state is invalid for sending webhooks

HTTP Status: 400

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS

Review and expand your understanding on Maya’s webhooks by following this guide: Webhooks for Payment Solutions.

---

PY0092 - Merchant's registered webhook is unreachable

HTTP Status: 400

Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS

Make sure you have registered the correct webhook URL that is up and running. For more details, see Webhooks for Payment Solutions.

---

Subscription Related Errors

PY0049 - Subscription does not exist

HTTP Status: 404

Will be encountered when subscription does not exist.

Make sure you have supplied a correct subscription and retry again.

---

PY0051 - Failed to update subscription details

HTTP Status: 400

This is a systematic error in updating subscription details. Kindly retry transaction.

---

PY0052 - Failed to cancel subscription

HTTP Status: 400

This error will arise when there are errors in cancelling the subscription. Kindly retry transaction.

---

PY0054 - Subscription already charged

HTTP Status: 400

You will encounter this error when subscription your are trying to process has already been charged.

To validate the status of the subscription, get the status via retrieve endpoint.