There is no documented ‘Null’ error code in Maya’s Pay With Maya solution. Based on your logs, the actual errors are:
Error Code: PY0014 - “Card Vault service error”
This indicates a temporary failure in Maya’s card vault system when processing a tokenized card payment.
Resolution: Retry the transaction. If the error persists, escalate to Maya Developer Support with the paymentId (34d6350a-d759-4b96-a7d9-42d3866d6404) and request logs.
Error: Read timed out (I/O error)
This is a network timeout, not a Maya-specific error code. It suggests the server did not respond within the expected time.
Resolution: Retry the request after a short delay. If timeouts are frequent, check your network connectivity, server response times, or verify the sandbox/production endpoint configuration.
The error codes ‘13’ and ‘901’ you mentioned are not recognized Maya error codes. The documented errors in your logs are PY0014 and network timeout. Ensure your integration handles these correctly using retry logic and proper error logging.
For Sandbox concerns and other technical implementation inquiries, please get in touch with us via:
Sandbox Health Page: Check real-time service status updates.
Maya Developer Hub Service Desk: File
a ticket in Sandbox.
To Know More:
We value your input and would love to hear your insights. Please submit you feedback here.
On the response, Maya responded PY0014. Based on the error and troubleshooting guides, your merchant endpoint can retry the transaction. But if this is still persistent, you may reach out to Maya through these channels, so they can investigate further.
If the error was encountered during sandbox integration , create a ticket via the [Maya Developer Hub Service Desk (Maya Developer Hub Service Desk Guide) 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