eNACH - Simulation Data
This page gives the overview of ENACH simulation data for testing purpose.
Overview
The ENACH(Electronic National Automated Clearing House) product allows for electronic mandate registration and processing of recurring payments. This document outlines the simulation data used for testing various scenarios in the ENACH system.
Please use staging credentials to test our ENACH simulation.
Refer to this ENACH API Reference Page.
Live Simulation APIs
| Sl. No. | API Name | Description |
|---|---|---|
| 1 | Check Supported Banks & Authentication Modes | Provides a list of supported banks and the authentication modes they support. |
| 2 | Mandate Registration API | Handles the registration of new mandates in the system. |
| 3 | Mandate Registration Status | User can check the registration status using the Mandate Registration Status API. |
| 4 | Mandate Execution API | Executes the registered mandates for processing payments. |
| 5 | Mandate Execution Status | User can check the execution status using the Mandate Execution Status API. |
| 6 | Mandate Registration Callback | A callback service that provides updates on the status of mandate registrations. (Your custom endpoint) |
| 7 | Mandate Execution Callback | A callback service that provides updates on the status of mandate executions. (Your custom endpoint) |
Simulation Data - Testing Scenarios
Mandate Registration API
This API lets you test the mandate registration API. You can use the amount given below to test the different scenarios.
OTP Validation
- Enter any 6-digit random number to validate the OTP.
- "111-111" use this 6-digit number to verify the wrong OTP scenario.
Debit Card Validation
- Enter a random 12-digit debit card number.
- Enter a random 3-digit CVV.
- Enter a random debit card expiry date.
Authentication Mode - Debit Card
| Amount | Scenario | Message | Error Code |
|---|---|---|---|
| 100 | Wrong account details. | Account doesn't exist or invalid account details. | AP05 |
| 200 | Registration Successful. | Success/ Active | - |
| 500 | Registration Successful. | Success/ Active | - |
| 300 | Wrong debit card details. | Customer entered the wrong debit card details. | AP35 |
| 400 | The Bank account belongs to a minor. | Mandates were not registered. The Bank account is of minor. | AP16 |
| Random amount | Other than the specified amount. | Transaction rejected or cancelled by the customer | AP23 |
| Cancel button | User clicked on the cancel button. | Transaction rejected or cancelled by the customer. | AP23 |
Authentication Mode - Net Banking
| Scenario | Message | Error Code |
|---|---|---|
| User clicked on the cancel button. | Customer cancelled or rejected the mandate registration. | AP23 |
| User accepted | Active/ Success | - |
Mandate Execution API
This API lets you test the mandate execution API. You can use the amount given below to test the different scenarios.
Ensure to use UMRN generated from Mandate Registration API.
| Amount | Scenario | Description |
|---|---|---|
| 200 | Failure | The mandate execution failed. This could be due to multiple reasons. |
| 500 | Success | The mandate was executed successfully, and the amount was debited. |
Execution callbacks will be sent within 20 mins of the execution API call.
Conclusion
This documentation provides the necessary guidelines for using simulation data to test ENACH transactions. Ensure to follow the specified conditions and amounts to accurately simulate and validate different transaction scenarios.
Updated about 2 months ago