This page serves as the central reference for understanding error and decline codes returned by the ECR. These codes enable developers and support staff to diagnose and resolve issues that arise during setup, communication, and payment processing.

🚦 Why Error Codes Matter

During ECR operation, different types of issues may arise, from faulty integration to transaction rejections due to invalid card data. Maya One communicates these problems using structured error codes or response statuses, which are critical for:

• Debugging integration issues
• Informing merchants of user actions
• Handling transaction fallbacks or retries

🧩 Types of Error Codes

📂 Error Code Guides

❗ ECR App Error Codes

These errors occur before or during ECR communication setup. They typically indicate missing components, misconfigurations, or connection issues that prevent successful integration.

Location: These errors will be visible in the Maya terminal

Examples:

• E:0001 – ECR not yet paired
• E:0002 – Maya One app not installed
• E:0003 – USB/L920 not connected

Each entry includes:

• A description
• Cause and impact
• Recommended resolution

⚠️ ECR Transaction Response Codes

These are real-time responses from the terminal during transaction processing. They reflect the real-time state or outcome of a transaction, such as rejection, cancellation, or in-progress status. Understanding these codes helps in diagnosing transaction issues and implementing appropriate handling logic on the ECR side.

Location: These errors will be visible in the command line

Common statuses:

• R – Rejected (e.g., invalid card, insufficient funds)
• C – Cancelled (e.g., timeout, back button pressed)
• V – Voided
• P – Processing

Includes:

• Sample JSON response data
• Code explanation and troubleshooting guidance

📘 Need Full Context?

Refer to the ECR Interface Specification Manual (contact your designated Maya Relationship Manager for a copy) for full protocol specifications, supported commands, and system flows.

✅ Best Practices

• Always log and monitor status and responseText fields in transaction responses.
• Use app error codes to validate the setup before processing transactions.
• Map each error or decline to actionable UI feedback when possible.

Do you need further assistance?

Unable to find your concern? Feel free to reach out to us. We're always happy to talk to you.

Maya Terminal hardware, transaction, and settlement concerns

Be ready with the following information, and contact us in any of the channels.

• Merchant Name
• MID (Merchant ID)
• Maya Terminal Model and Serial Number
• Details/background of the problem
• Screenshot, photo, or recorded video of the issue (optional)

Keep in Mind

For Maya Terminal Concerns, reach us via:

• Maya Business Support Hotline: (+63)2 8845 7700 or 1-800-18-886-57
• Maya Business Email: [email protected]
• Log on and file a ticket via your Maya Business Manager

Sandbox Technical Integrations (ECR, Merchant terminal app)

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 an ASKMAYADEV ticket in Maya Developer Hub Service Desk
3. On the ticket fields, make sure to provide the following information:
   1. Maya Terminal Model and Serial Number
   2. Maya ONE and Maya ECR application versions
   3. Details/background of the problem
   4. Screen display if the "DEBUG only" watermark appears (if using a test terminal device): Yes / No
   5. Raw request and response (e.g., -debug option in ECR Tool)
   6. Procedure to replicate the issue
   7. Screenshot, photo, or recorded video of the issue