Simulation Data - User verification
This page gives the simulation data for Penny Pull provided by Decentro as part of the user verification stack.
1. Penny Pull v2 - Simulation Data
Below is the test data that can be used by platforms to fetch the status of a transaction undertaken through the Penny Pull Create Intent API.
The platform is expected to pass the parameters as-is to get the intended scenario.
Note - Simulation Data
To test Simulation Staging data for Penny Pull Intent Flow, please use the following API Endpoints -
- Intent API: https://in.staging.decentro.tech/v2/payments/penny_pull
- Get Transaction Status API: https://in.staging.decentro.tech/v2/payments/penny_pull/fetch/{decentroTxnId}/status
1. Intent API
Steps to use this data:
- In the request body, pass request values as shared below in the table, depending on the scenario to be tested.
- Trigger the Create Intent API with the choice(s) chosen in Step 1.
- Based on the values provided in Step 1 for each request parameter, the API response will confirm the creation of a short link, QR code (with or without a logo), and PSP-specific deep links.
- In the API response, locate the field labeled decentroTxnId and make a note of it. This decentroTxnId will be utilized to retrieve the transaction status using the Get Transaction Status API, indicating whether the payer has completed the payment or not.
| Request body | Request value | Test case |
|---|---|---|
| generate_qr | 0 or 1 | 0/1 depending on the choice to generate QR. 1 for generating QR and 0 for not generating QR |
| generate_uri | 0 or 1 | 0/1 depending on the choice to generate UPI data URI to implement customized flow based on URI data for GPay, PhonePe, PayTm UPI apps. |
| customized_qr_with_logo | 0 or 1 | 0/1 depending on whether you want to get a customised QR code with logo |
2. Get Transaction Status API
Steps to use this data:
- In the Get Transaction Status API endpoint, pass the decentroTxnId as a path parameter.
- Trigger the Get Transaction Status API.
- The API response will indicate the success of the API request, the terminal status of the transaction, and provide essential details of the payer such as payerName, payerVpa, payerAccountNumber, and payerIfsc.
2. Validate VPA v3 - 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 |
3. Validate Bank Account v2
Decentro provides certain static values for platforms to simulate the various scenarios of validating a bank account as part of its staging (sandbox) environment to mirror the key scenarios encountered on live environment.
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
| Validation Type | To Account | IFSC Code | Test Cases | Transaction Status |
|---|---|---|---|---|
| pennydrop | 123456789011 | SBIN0001077 | Validate Bank Account API Status as 'Success' | Success |
| pennydrop | 123456789012 | UTIB0001506 | Validate Bank Account API Status as 'Pending' | Pending |
| pennydrop | 123456789013 | HDFC0001234 | Validate Bank Account API Status as 'Failure' | Failure |
| penniless | 123456789021 | SBIN0001077 | Validate Bank Account API Status as 'Success' | Success |
| penniless | 123456789023 | HDFC0001234 | Validate Bank Account API Status as 'Failure' | Failure |
| hybrid | 123456789031 | SBIN0001077 | Validate Bank Account API Status as 'Success' where the validation is "pennydrop" | Success |
| hybrid | 123456789033 | HDFC0001234 | Validate Bank Account API Status as 'Failure' where the validation is "pennydrop" | Failure |
| hybrid | 123456789041 | SBIN0001077 | Validate Bank Account API Status as 'Success' where the validation is "penniless" | Success |
| hybrid | 123456789043 | HDFC0001234 | Validate Bank Account API Status as 'Failure' where the validation is "penniless" | Failure |
4. Mobile to Account API v2
Steps to use this data:
- In the request body, pass request values as shared below in the table, depending on the scenario to be tested.
- Trigger the API with the scenario chosen in Step 1.
- Based on the values provided in Step 1 for each request parameter, the API response will contain the relevant output.
| Mobile Number | Validation Status | Test Scenario |
|---|---|---|
| 8266657824 | SUCCESS | Account details retrieved successfully |
| 8266617854 | SUCCESS | The account associated with this mobile number is frozen. |
| 8266457854 | SUCCESS | The account associated with this mobile number is a NRE account and cannot be validated. |
| 8266457814 | SUCCESS | The account associated with this mobile number is closed. |
| 8263657854 | FAILURE | There is no account associated with this mobile number. |
| 8266607854 | FAILURE | The account associated with this mobile number is inactive and cannot be validated. |
| 8176157814 | FAILURE | Internal Server Error. Kindly retry the transaction after sometime. |
| 8306457714 | FAILURE | Unexpected response received from provider. |
Updated 6 months ago