Maya ONE App Decline Codes: Transaction Value or State Conflicts

Overview

Occurs when transaction references, RRN, or amount values don’t match expected states in the system.

Note: The error or decline code is only prompted in the Maya Terminal, where the Maya ONE App is installed.

For ECR-integrated setup, Maya Terminal sends a decline response, with a command status R for Rejected, to the connected Electronic Cash Register (ECR).


Declines Requiring Values Check

TRN Does Not Exist

Cause and Impact:

The Transaction Reference Number (TRN) is invalid or not found in the system. The transaction cannot be located or processed.

Possible Maya ONE App Error:

Error CodeMessage
2545TRN does not exist
PY0116Transaction could not be completed.

Recommended handling:

Confirm that the TRN is correct before retrying the transaction.


Transaction Already Voided

Cause and Impact:

The transaction has already been voided and cannot be voided again.

Possible Maya ONE App Error:

Error CodeMessage
2547Transaction already voided
PY0116Transaction could not be completed.

Recommended handling:

Do not attempt to void a transaction that has already been voided.


Invalid RRN

Cause and Impact:

The Retrieval Reference Number (RRN) is missing or invalid. The system cannot match the transaction for processing.

Possible Maya ONE App Error:

Error CodeMessage
2552Invalid RRN
PY0116Transaction could not be completed.

Recommended handling:

Ensure a valid RRN is provided in the request.


Transaction No Longer Valid for Void

Cause and Impact:

The transaction has already been finalized and can no longer be voided.

Possible Maya ONE App Error:

Error CodeMessage
2569Transaction is no longer valid for void
PY0116Transaction could not be completed.

Recommended handling:

Verify the transaction state before attempting a void.


Transaction Not Yet Valid for Refund

Cause and Impact:

The transaction has not yet been settled; refunds can only be processed after settlement.

Possible Maya ONE App Error:

Error CodeMessage
2570Transaction is not yet valid for refund
PY0116Transaction could not be completed.

Recommended handling:

Wait until the transaction is settled before retrying the refund.


Payment RRN, Merchant ID, and Amount Combination Invalid

Cause and Impact:

The provided combination of RRN, Merchant ID (MID), and amount is invalid or not found.

Possible Maya ONE App Error:

Error CodeMessage
2571Payment RRN, Merchant ID, and Amount does not exist
PY0116Transaction could not be completed.

Recommended handling:

Verify the combination of RRN, MID, and amount before retrying.


Excessive Capture

Cause and Impact:

The capture amount exceeds the original authorized transaction amount.

Possible Maya ONE App Error:

Error CodeMessage
ACQ012Excessive capture
PY0116Transaction could not be completed.

Recommended handling:

Ensure the capture amount does not exceed the authorized total.


Captured Authorization Transaction Cannot Be Voided

Cause and Impact:

Once captured, a transaction cannot be voided; it must be refunded.

Possible Maya ONE App Error:

Error CodeMessage
ACQ013Captured authorization transaction cannot be voided
PY0116Transaction could not be completed.

Recommended handling:

Process a refund instead of a void after a capture.


Concurrent Operations Not Allowed

Cause and Impact:

Multiple requests (e.g., void, refund, capture) are being sent simultaneously for the same transaction, which causes conflict.

Possible Maya ONE App Error:

Error CodeMessage
ACQ024Concurrent operations on a transaction is not allowed
PY0116Transaction could not be completed.

Recommended handling:

Avoid sending multiple operations at the same time for the same transaction.


Transaction Not Valid for Capture

Cause and Impact:

The transaction is not in an authorized state and cannot be captured.

Possible Maya ONE App Error:

Error CodeMessage
ACQ011Transaction is not valid for capture
PY0094Payment is not available for capture.

Recommended handling:

Ensure the transaction is authorized before performing a capture.


FAQs

Q: When do these value and state conflicts usually occur?

A: They typically occur during refund, void, or capture operations, especially when the same transaction is already completed, voided, refunded, or settled.

Q: Are the value and state conflicts caused by network or issuer issues?

A: No. These are usually logic or process errors at the ECR or application level, not due to the issuer or network. They indicate that the transaction is no longer valid for the requested operation.

Q: Can I retry the same transaction request when there are value or state conflicts?

A: Retrying is not recommended unless the transaction state is confirmed as valid for the operation. Repeated retries may result in duplicate errors or invalid transaction states.

Q: How can I confirm the correct transaction state?

A: You can cross-check the transaction’s RRN (Retrieval Reference Number), Transaction ID, and status in your ECR logs or the Maya Business Manager dashboard to verify whether it was successfully processed, refunded, or voided.


Next Steps

When encountering Transaction Value or State Conflict declines:

  1. Review the Transaction Status
    • Check your ECR logs for the transaction’s last known state (Approved, Voided, Refunded, etc.).
    • Cross-reference this with the Maya Business Manager dashboard to confirm the same state.
  2. Verify the Transaction Details
    • Ensure the RRN (Retrieval Reference Number), Merchant ID (MID), and Amount match exactly with the original transaction.
    • If any parameter mismatches, correct it before retrying.
  3. Check for Concurrent Operations
    • Avoid sending multiple requests (e.g., two refunds or captures) simultaneously for the same transaction.
    • Wait for confirmation responses from the Maya terminal before issuing follow-up actions.
  4. Reconcile Before Retrying
    • Do not retry refund, void, or capture requests until reconciliation is done.
    • If a mismatch occurs (e.g., transaction stuck as “Processing”), perform backend reconciliation before proceeding.
  5. Document and Escalate
    • Record relevant details, including:
      • Terminal Type (Sunmi / PAX / PAX Lite)
      • Merchant and Terminal IDs
      • Transaction ID or RRN
      • Error code and message displayed
      • Screenshot or log snippet from the ECR or Maya terminal
    • Send these details to [email protected] for investigation.