I am currently testing sandbox transactions for Maya Vault.
I tested a scenario wherein the requested cardToken is not linked to the customerId.
After submitting the curl request with a requestReferenceNumber, i received a JSON response with an error code and error message, but it does not show my submitted requestReferenceNumber.
It seems you may be referring to the requestReferenceNumber not being displayed in the JSON response for failed transactions in Maya Vault. The requestReferenceNumber is typically included in the response payload for successful transactions. However, for failed transactions, the response may not include this field. You may refer to the documentation for the specific API endpoint you are using to see if it includes the requestReferenceNumber in the response payload for failed transactions. If not, you may need to handle this case in your application logic.
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.
We value your input and would love to hear your insights. Please submit you feedback here.
Hi @jsjarabejo, in the current implementation of the Maya Vault API, whenever a request fails, the service returns only the standard error response payload (this includes the error code, description, and message), but it does not echo back the requestReferenceNumber you submitted.
If you need to reconcile failed transactions, the best source of truth is the webhook payload. The webhook event includes the final and complete context and identifiers, which you can rely on for matching and tracing failed attempts.
Hi @genson.cerezo.
The error we are testing is PY0027 - Card does not exist. Is this the reason why both the standard response and the webhook payload do not contain the RRN, because it did not reach issuer-level validation?