Collections - Simulation Data
This page gives an overview of using testbed data to simulate multiple scenarios from a collections stack perspective.
Overview
Decentro provides platform simulation data (dummy data) from an integration support perspective so that the platform can simulate all possible scenarios without undertaking real money transactions.
This requires the platform to use standard request payloads to handle scenarios for each API and scenario, as mentioned below.
Generate payment link v3 API & Check Payment status API
Below is the test data that platforms can use to test out standard scenarios for Generate payment link. The platform is expected to pass as-is parameters to get the intended scenario.
Note - Simulation Data
To test Simulation Staging data for Generate payment link API & Get transaction status API, please use the following API Endpoint - https://in.staging.decentro.tech/v2/payments/upi/link https://in.staging.decentro.tech/v2/payments/transaction/status
Flow
- Generate a payment link with the 'amount' parameter as either 10, 20, or 30, depending on the test case being observed.
- Obtain the generated link in the response.
- Use the decentro_txn_id from the response and pass in Check Payment Statusto fetch the transaction's terminal status.
- You'll receive the terminal status depending on the Amount passed in Step 1.
- To test the scenario where the payment link expires, include the necessary time value in the expiry_time field when generating the link. Once the expiry time window has passed, repeat step 3 to receive the terminal status as EXPIRED.
- Please refer to the table below for Amount v/s transaction status test cases in staging simulation.
- Step 4 will take some time in the production environment until the end user enters the UPI pin and makes the payment. Until then, the transaction's status will be PENDING.
| Amount | Transaction Status | Test case |
|---|---|---|
| 10 | Success | Payment link is created & Transaction status is Success |
| 20 | Failure | Payment link is created & Transaction status is Failed |
| 30 | Pending | Payment link is created & Transaction status is Pendin |
E-NACH v3
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