Simulation Data
This section explains how to simulate various scenarios as part of the payouts module of Decentro.
Initiate Payout API and Get Transaction Status API
Decentro provides certain static values for platforms to simulate the various scenarios.
Please utilize the input parameters, shared in the table below, for initiating the Initiate Payout API. The initiate payout API will share a decentroTxnId in the response payload. The decentroTxnId must be passed
in the Get Transaction Status API to receive the expected output.
Note - Simulation Data
To test Simulation Staging data for Initiate Transfer and Status Handling, please use the following API Endpoint - https://in.staging.decentro.tech/core_banking/money_transfer/initiate
https://in.staging.decentro.tech/core_banking/money_transfer/get_status/
| To Account | IFSC Code | Test Cases | Transaction Status |
|---|---|---|---|
| 123456789011 | SBIN0001077 | Initiate Payout API status as 'Pending' Get Transaction Status API status as 'Success' | Success |
| 123456789012 | UTIB0001506 | Initiate Payout API status as 'Pending' Get Transaction Status API status as 'Pending' | Pending |
| 123456789013 | HDFC0001234 | Initiate Payout API status as 'Pending' Get Transaction Status API status as 'Failure' | Failure |
Validate Bank Account (Penny Drop)
Decentro provides certain static values for platforms to simulate the various scenarios of validating a bank account.
Please utilize the input parameters, shared in the table below, for initiating the Validate Bank Account.
Note - Simulation Data
To test Simulation Staging data for Validate Bank Account (Penny Drop), please use the following API Endpoint - https://in.staging.decentro.tech/core_banking/money_transfer/validate_account
| To Account | IFSC Code | Test Cases | Transaction Status |
|---|---|---|---|
| 123456789011 | SBIN0001077 | Validate Bank Account API Status as 'Success' | Success |
| 123456789013 | HDFC0001234 | Validate Bank Account API Status as 'Failure' | Failure |
Validate VPA - Simulation Data
Below is the test data that can be used by platforms to test out standard scenarios for Validate UPI Handle (VPA).
The platform is expected to pass the parameters as-is to get the intended scenario.
Note - Simulation Data
To test Simulation Staging data for Validate VPA, please use the following API Endpoint - https://in.staging.decentro.tech/v2/payments/vpa/validate
Steps to use this data:
- Take the UPI ID from the values shared below depending on the scenario to be tested.
- Trigger the validate VPA API with that UPI ID with the required type.
- API response will state the validation of the VPA (valid or invalid)
- The information about the UPI ID depends on the the type param passed in the request payload.
| UPI ID | Validation status | Test case |
|---|---|---|
| charles.babbage@okhdfc | VALID | When VPA is valid |
| alan.turing@oksbi | INVALID | When VPA is invalid |
Generate payment link & Get transaction status API - Simulation Data
Below is the test data that can be used by platforms to test out standard scenarios for Generate payment link.
The platform is expected to pass the parameters as-is 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
Steps to use this data:
- Generate a payment link with amount parameter as either 10, 20, 30 depending on the test case being observed.
- Obtain the generated link in the response.
- Use decentro_txn_id from the response and pass in Get transaction status API to fetch the terminal status of the transaction.
- Depending on the Amount passed in step 1, you'll receive the terminal status.
- Please refer to the table below for Amount v/s transaction status test cases in staging simulation.
- In the live flow, step 4 will take some time till the end user enters the UPI pin and makes the payment. Till then the status of the transaction by GTS 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 Pending |
Collection request - Simulation Data
Coming soon
Refund - Simulation Data
coming soon
ENACH
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.
Note - Simulation Data (eNACH Mandate Registration)
To test simulation staging data for eNACH Mandate Registration API - <https://staging.api.decentro.tech/v3/payments/enach/mandate>
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.
Aadhar Validation
- Enter random 12 digit Aadhar card number.
- Enter random 6 digit OTP
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/Aadhar
| 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
Note : Simulation Data (eNACH Presentation)
To test simulation staging data for eNACH Mandate Execution API - <https://staging.api.decentro.tech/v3/payments/enach/mandate/execute>
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.
AUTOPAY
Simulation Data
Decentro's simulation data helps developers simulate all the real-world scenarios when using the Create mandate API.
This requires the platform to use standard request payloads to handle scenarios for each API and scenario, as mentioned below.
The platform will need to whitelist their IP and configure callback endpoints with Decentro if they wish to handle the flow. Please reach out to us at [email protected] for the same.
How to test?
Below is the flow to test the Simulation data
- Generate a mandate link by using Create Mandate API with the 'amount' parameter in the required range as mentioned in the test bed section.
- Note: To test the instant presentation within a 5-minute scenario when the amount rule is set to MAX, ensure that you pass the simulation amount value in the default_amount parameter.
- Click the generated link once before proceeding. This is a mandatory step to receive the simulation responses.
- Next Decentro will propagate the updated status of the mandate as per the amount (range) passed in step-1.
- Alternatively, client can use Get Mandate Status to fetch the latest status of the mandate.
- Next proceed to trigger the Pre Debit Notification API to test various scenario basis the amount range values mentioned in the respective test bed section.
- Next, proceed to trigger the Mandate Presentation API to test various scenarios basis the amount range values as mentioned in the respective test bed section.
- Note: The simulation environment is an exact replica of production environment including all the checks of production systems for registration, notification and, presentation .
Test Bed
Mandate Creation
Note : Simulation Data (Autopay Mandate Registration)
To test simulation data for Autopay Mandate Registration - https://staging.api.decentro.tech/v3/payments/upi/autopay/mandate/link
| Amount | Scenario |
|---|---|
| 1 - 1000 | Mandate registration is successful. Mandate status is Active |
| 1001 - 1500 | Mandate is paused |
| 1501 - 2000 | Mandate registration is rejected by user |
| 2001 3000 | Mandate registration is failed |
Pre Debit Notification
Note : Simulation Data (Autopay Pre-Debit Notification)
To test simulation data for Autopay Pre-Debit Notification - https://staging.api.decentro.tech/v3/payments/upi/autopay/mandate/notify
| Amount | Scenario |
|---|---|
| 1 - 500 | Pre debit notification is successful. |
| 501 - 1000 | Pre debit notification failed |
Presentation
Note : Simulation Data (Autopay Presentation)
To test simulation data for Autopay Presentation - https://staging.api.decentro.tech/v3/payments/upi/autopay/mandate/presentation
| Amount | Scenario |
|---|---|
| 1 - 300 | Mandate Presentation is successful. |
| 301 - 500 | Mandate Presentation failed |
Mandate Presentation Callback
| Amount | Scenario |
|---|---|
| 1 - 150 | Mandate Presentation is successful. |
| 151 - 300 | Mandate Presentation failed |
Mandate Registration Callback
| Amount | Scenario |
|---|---|
| 0 - 500 | Active |
| 501 - 1000 | Active, Pause, Unpause (Active) |
| 1001 - 1500 | Paused |
| 1501 - 2000 | Rejected |
Updated about 9 hours ago
