Simulation Data

This page gives the simulation data for Penny Pull provided by Decentro as part of the user verification stack.

Penny Pull - 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 -

  1. Intent API: https://in.staging.decentro.tech/v2/payments/penny_pull
  2. Get Transaction Status API: https://in.staging.decentro.tech/v2/payments/penny_pull/fetch/{decentroTxnId}/status

1. Intent API

Steps to use this data:

  1. In the request body, pass request values as shared below in the table, depending on the scenario to be tested.
  2. Trigger the Create Intent API with the choice(s) chosen in Step 1.
  3. 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.
  4. 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 bodyRequest valueTest case
generate_qr0 or 10/1 depending on the choice to generate QR. 1 for generating QR and 0 for not generating QR
generate_uri0 or 10/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_logo0 or 10/1 depending on whether you want to get a customised QR code with logo

2. Get Transaction Status API

Steps to use this data:

  1. In the Get Transaction Status API endpoint, pass the decentroTxnId as a path parameter.
  2. Trigger the Get Transaction Status API.
  3. 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.