Bills Payment Troubleshooting Guide

• This may occur in Validate and Post transaction legs.
• May be caused by a possible mismatch in the configured Sandbox environment secret key.

Troubleshooting:

• Check the currently configured secret key used by the merchant’s Validate and Post services and see if it matches the secret key provided by Maya.
• Review and make sure that the correct computation of paymaya-signature header value was followed.

• The error message "Bill Payment ID is invalid / required" may occur in the Validate and Post transaction legs.
• This may be caused if there were any changes made to the request body and/or the Postman pre-request script.

Troubleshooting:

• Check the request body’s id field. The value should be the Postman variable placeholder: {{BILLSPAY_ID}}.
• If there were any changes made in the Pre-request script, revert the changes made.

• May occur in Validate, Post, and Callback.
• This error should naturally occur when running the test case Declined Validate Biller API - Invalid Account Number

Troubleshooting:

• Check the value inputted under the VALID_ACCOUNT_NUMBER variable. This should be a valid value accepted by your Validate service.
• Check the biller.accountNumber value in your request body. The value should be the Postman variable placeholder: {{VALID_ACCOUNT_NUMBER}}
• For Callback, make sure that the Bill Payment ID in the callback request matches the previously generated Bill Payment ID from the Successful Post Request.

For the Biller API Sandbox environment, this is a catch-all error and may have varying causes.

Troubleshooting:

• Biller Slug:
  • Check the value inputted under the BILLER_SLUG variable. This should match the provided biller slug onboarded by Maya.
  • Check the biller.slug value in your request body. The value should be the Postman variable placeholder: {{BILLER_SLUG}}
• Custom Fields:
  • Check the value inputted under the CUSTOM_FIELDS variable. This should be a valid JSON format.
  • Check the biller.fields value in your request body. The value should be the Postman variable placeholder: {{CUSTOM_FIELDS}}
• Transaction Date:
  • The transaction date for the request body is generated via Postman’s pre-request script. If there were any changes made in the Pre-request script, revert the changes made.
  • Check the transaction.date value in your request body. The value should be the Postman variable placeholder: {{BILLSPAY_TRANSACTION_DATE}}
• Check if there were any general changes made on the request body. Request body should be a valid JSON format.

• May occur in Validate and Post legs.
• This may occur if the value of any currency field in the request body is changed to any value other than PHP

Troubleshooting:

• Make sure all the currency fields/ in the request body are only PHP

• This may occur in the Validate, Post, and Callback transaction legs.
• This may occur if any required header is missing from the request made.

Troubleshooting:

• Check request headers and see if any of the following headers have been unticked:
  • Request-Reference-No
  • Authorization (For Callback only)

• May only occur on the Callback leg.
• This occurs if the Bill Payment ID being updated via Callback has already been processed.

Troubleshooting:

• Ensure that the bill payment transaction being updated has not been used during callback previously.
• Make sure that there was a previous execution of a Successful Post Biller API before executing the callback step.
• Revert any changes, if any, made in the Tests section of the previous Successful Post Biller API step.

• May only occur on the Callback leg.
• This may occur if there’s a mismatch between the Bill Payment ID in the request body and the URL.
• This may also occur if the Bill Payment ID used was not generated from the previous Post step.

Troubleshooting:

• Make sure that there was a previous execution of a Successful Post Biller API before executing the callback step.
• Ensure that the bill_payment_id Postman variable was not tampered with before running the Callback step.

• May only occur on the Callback transaction leg.
• Occurs if the Receipt Number set in the callback request body is missing or the value is blank.

Troubleshooting:

• Check if the transaction.request field is present in the callback request body.
• Check if the value of the transaction.request field in the callback request body is valid and not set to a blank String.

1. Make sure you are enrolled in the Maya Developer Hub Service Desk . Otherwise, request for access to ASKMAYADEV.
2. Once you are provided access, create ASKMAYADEV ticket in Maya Developer Hub Service Desk portal.