General Errors
2553 - Missing/invalid parameters
2553 - Missing/invalid parametersProduct/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS CHECKOUT-QRPHDYNAMIC QRPH
| Error Code and Message | 2553- Missing/invalid parameters. |
| HTTP Code | 400 |
| Problem | The API call was made with missing or invalid parameters. In most cases, the problem is how API Consumers call the API endpoint. It can be a missing parameter in a required field or cannot be done with your current configuration. |
| What you should do | The API Consumer must review the API specifications and send the API request with complete specs and correct values. |
PY0001 - Generic system error
PY0001 - Generic system errorProduct/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS
| Error Code and Message | PY0001 - A problem is encountered. Please contact your system administrator. |
| HTTP Code | 400 |
| Problem | A problem was encountered in Maya. |
| What you should do | If the error appears, the API Consumer can retry the operation. If the issue persists, they can reach out to Maya through these channels: 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
|
PY0064 - Invalid JSON Format
PY0064 - Invalid JSON FormatHTTP 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
PY0015 PY0016 PY0040 PY0041 PY0060 PY0066 PY0067 PY0069 PY0122 PY0143 PY9999 - System has encountered a systematic error or is unreachable / timed out.
PY0015 PY0016 PY0040 PY0041 PY0060 PY0066 PY0067 PY0069 PY0122 PY0143 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.
If the error persists even after multiple retries, please escalate the issue to Support by providing any of the following:
-customerIdorlinkId
-paymentId
PY0013 - Card vault server unreachable / timed out.
PY0013 - Card vault server unreachable / timed out.Product/s: VAULT
| Error Code and Message | PY0013 - Card vault server unreachable / timed out |
| HTTP Code | 400 |
| Problem | A problem was encountered between your server and Maya. |
| What you should do | If the error appears, the API Consumer can retry the operation. If the issue persists, they can reach out to Maya through these channels: 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
|
PY0059 - Customer Vault server unreachable / timed out
PY0059 - Customer Vault server unreachable / timed outProduct/s: VAULT
| Error Code and Message | PY0059 - Customer Vault server unreachable / timed out |
| HTTP Code | 400 |
| Problem | A problem was encountered between your server and Maya. |
| What you should do | If the error appears, the API Consumer can retry the operation. If the issue persists, they can reach out to Maya through these channels: 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
|
PY0014 - Card Vault service error
PY0014 - Card Vault service errorProduct/s: VAULT
| Error Code and Message | PY0014 - Card Vault service error |
| HTTP Code | 400 |
| Problem | A problem was encountered between your server and Maya. |
| What you should do | If the error appears, the API Consumer can retry the operation. If the issue persists, they can reach out to Maya through these channels: 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
|
PY0060 - Customer Vault service error
PY0060 - Customer Vault service errorProduct/s: VAULT
| Error Code and Message | PY0060 - Customer Vault service error |
| HTTP Code | 400 |
| Problem | A problem was encountered between your server and Maya. |
| What you should do | If the error appears, the API Consumer can retry the operation. If the issue persists, they can reach out to Maya through these channels: 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
|
Third Party Errors
PY0114 - WeChat Service unreachable / timed out
PY0114 - WeChat Service unreachable / timed outHTTP Status: 400
Product/s: INVOICE CHECKOUTVAULTPLUGINS
WeChat service is unreachable or taking too long to respond. Kindly retry transaction.
If the error persists even after multiple retries, please escalate the issue to Support.
PY0115 - WeChat Service error
PY0115 - WeChat Service errorHTTP Status: 400
Product/s: INVOICE CHECKOUTVAULTPLUGINS
This is a systematic error on WeChat Service. Kindly retry transaction.
If the error persists even after multiple retries, please escalate the issue to Support.
PY0129 - GCash Service unreachable / timed out
PY0129 - GCash Service unreachable / timed outHTTP Status: 400
Product/s: INVOICE CHECKOUTVAULTPLUGINS
GCash Service is unreachable or taking too long to respond. Kindly retry transaction.
If the error persists even after multiple retries, please escalate the issue to Support.
PY0130 - GCash Service error
PY0130 - GCash Service errorHTTP Status: 400
Product/s: INVOICE CHECKOUTVAULTPLUGINS
This is a systematic error on GCash Service. Kindly retry transaction.
If the error persists even after multiple retries, please escalate the issue to Support.
PY0140 - ShopeePay Service unreachable / timed out
PY0140 - ShopeePay Service unreachable / timed outHTTP Status: 400
Product/s: INVOICE CHECKOUTVAULTPLUGINS
ShopeePay Service is unreachable or taking too long to respond. Kindly retry transaction.
If the error persists even after multiple retries, please escalate the issue to Support.
PY0141 - ShopeePay Service error
PY0141 - ShopeePay Service errorHTTP Status: 400
Product/s: INVOICE CHECKOUTVAULTPLUGINS
This is a systematic error in the ShopeePay Service. Kindly retry transaction.
If the error persists even after multiple retries, please escalate the issue to Support.
Webhook Errors
PY0038 - Webhook does not exist
PY0038 - Webhook does not existHTTP 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 exists via Maya Manager or by calling the Get Webhooks endpoint.
PY0039 - Webhook already exists
PY0039 - Webhook already existsHTTP Status: 400
Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS
This error happens if a webhook has already been created.
You may want to check if the registered webhook exists 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
PY0091 - Payment state is invalid for sending webhooksHTTP Status: 400
Product/s: INVOICE CHECKOUTPAY WITH MAYAVAULTPLUGINS
Review and expand your understanding of Maya’s webhooks by following this guide: Webhooks for Payment Solutions.
PY0092 - Merchant's registered webhook is unreachable
PY0092 - Merchant's registered webhook is unreachableHTTP Status: 408
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
PY0049 - Subscription does not existHTTP Status: 404
Will be encountered when a subscription does not exist.
Make sure you have supplied a correct subscription and retry again.
PY0051 - Failed to update subscription details
PY0051 - Failed to update subscription detailsHTTP Status: 400
This is a systematic error in updating subscription details. Kindly retry transaction.
If the error persists even after multiple retries, please escalate the issue to Support by providing the
subscriptionId.
PY0052 - Failed to cancel subscription
PY0052 - Failed to cancel subscriptionHTTP Status: 400
This error will arise when there are errors in canceling the subscription. Kindly retry transaction.
If the error persists even after multiple retries, please escalate the issue to Support by providing the
subscriptionId.
PY0054 - Subscription already charged
PY0054 - Subscription already chargedHTTP Status: 400
You will encounter this error when the subscription you are trying to process has already been charged.
To validate the status of the subscription, get the status via the retrieve endpoint.