### Create eKYC request

Source: https://docs.setu.co/data/ekyc/quickstart

Call this API to create a unique request to get your customer started on the eKYC journey.

```APIDOC
## POST /api/ekyc/

### Description
Initiates an eKYC request and generates a verification URL.

### Method
POST

### Endpoint
/api/ekyc/

### Parameters
#### Query Parameters
- **webhook_url** (string) - Optional - The URL to receive webhook notifications.
- **redirection_url** (string) - Optional - The URL to redirect the user after the eKYC process.

### Request Example
```json
{
  "webhook_url": "<client_webhook_url>",
  "redirection_url": "<client_redirection_url>"
}
```

### Response
#### Success Response (200)
- **id** (string) - The unique identifier for the eKYC request.
- **status** (string) - The current status of the eKYC request (e.g., CREATED).
- **kycURL** (string) - The URL for the customer to complete the eKYC process.

#### Response Example
```json
{
  "id": "0c624d3e-9cb0-4323-b468-d89092d7d305",
  "status": "CREATED",
  "kycURL": "https://{base_url}/public/ekyc-web/0c624d3e-9cb0-4323-b468-d89092d7d305"
}
```
```

--------------------------------

### Webhook Response

Source: https://docs.setu.co/data/ekyc/quickstart

Example of a webhook notification received upon completion of the eKYC process.

```APIDOC
## Webhook Response

### Description
This is an example of the payload received via webhook when the eKYC process is completed.

### Response Example
```json
{
    "event": "EKYC_DATA",
    "data": {
        "id": "...",
        "status": "SUCCESS",
        "aadhaar": {
            "name": "Ritesh Ujjwal",
            "dateOfBirth": "1989",
            "gender": "M",
            "address": {
                "careOf": "",
                "country": "India",
                "district": "ABC",
                "house": "",
                "landmark": "XYZ",
                "locality": "AAAAAA",
                "pin": "560001",
                "postOffice": "Bangalore",
                "state": "Karnataka",
                "street": "ABC Road",
                "subDistrict": "",
                "vtc": "my location"
            },
            "photo": "...base64...",
            "aadhaarNumber": "XXXXXXXX8888",
            "generatedAt": "2024-03-22T15:18:35.269+05:30"
        },
        "xml": {
            "xmlBase64": "...base64..."
        }
    }
}
```
```

--------------------------------

### eKYC Request Response Example (API)

Source: https://docs.setu.co/data/ekyc

Illustrates the response structure for an eKYC request. It includes the unique request ID, the current status (e.g., CREATED), and a URL for the customer to complete the KYC process.

```json
{
  "id": "0c624d3e-9cb0-4323-b468-d89092d7d305", // UUID4
  "status": "CREATED", // enum 'eKYC Request Status'
  "kycURL": "https://{base_url}/public/ekyc-web/0c624d3e-9cb0-4323-b468-d89092d7d305"
}
```

--------------------------------

### POST /api/ekyc/

Source: https://docs.setu.co/data/ekyc

Initiates a new eKYC request and generates a unique verification URL for the customer.

```APIDOC
## POST /api/ekyc/

### Description
Call this API to create a unique request to get your customer started on the eKYC journey.

### Method
POST

### Endpoint
/api/ekyc/

### Parameters
#### Request Body
- **webhook_url** (string) - Optional - The URL to receive asynchronous status updates.
- **redirection_url** (string) - Required - The URL to redirect the user to after the eKYC process.

### Request Example
{
  "webhook_url": "<client_webhook_url>",
  "redirection_url": "<client_redirection_url>"
}

### Response
#### Success Response (200)
- **id** (string) - The unique identifier for the eKYC request.
- **status** (string) - The current status of the request (e.g., CREATED).
- **kycURL** (string) - The URL where the user completes the Aadhaar verification.

#### Response Example
{
  "id": "0c624d3e-9cb0-4323-b468-d89092d7d305",
  "status": "CREATED",
  "kycURL": "https://{base_url}/public/ekyc-web/0c624d3e-9cb0-4323-b468-d89092d7d305"
}
```

--------------------------------

### Get eKYC request

Source: https://docs.setu.co/data/ekyc/quickstart

Call this API to get the status and data (if the status is SUCCESS) of your eKYC request.

```APIDOC
## GET /api/ekyc/:request_id

### Description
Retrieves the status and data of a specific eKYC request.

### Method
GET

### Endpoint
/api/ekyc/:request_id

### Parameters
#### Path Parameters
- **request_id** (string) - Required - The unique identifier of the eKYC request.

### Response
#### Success Response (200)
- **id** (string) - The unique identifier for the eKYC request.
- **status** (string) - The current status of the eKYC request (e.g., CREATED, SUCCESS).
- **kycURL** (string) - The URL for the customer to complete the eKYC process.
- **data** (object) - Contains the eKYC data if the status is SUCCESS. This includes:
  - **aadhaar** (object) - Aadhaar details.
  - **xml** (object) - XML representation of the Aadhaar data.

#### Response Example (In Progress)
```json
{
    "id": "2ac3191e-d5ef-4e99-9aef-4ad93e1b720d",
    "status": "CREATED",
    "kycUrl": "http://localhost:3100/v1/public/ekyc-web/2ac3191e-d5ef-4e99-9aef-4ad93e1b720d",
    "data": null
}
```

#### Response Example (Success)
```json
{
  "id": "0c624d3e-9cb0-4323-b468-d89092d7d305",
  "status": "SUCCESS",
  "kycURL": "http://dg-ekyc.setu.co/public/ekyc-web/0c624d3e-9cb0-4323-b468-d89092d7d305",
  "data": {
      "aadhaar": {
          "name": "Ritesh Ujjwal",
          "dateOfBirth": "1989",
          "gender": "M",
          "address": {
              "careOf": "",
              "country": "India",
              "district": "ABC",
              "house": "",
              "landmark": "XYZ",
              "locality": "AAAAAA",
              "pin": "560001",
              "postOffice": "Bangalore",
              "state": "Karnataka",
              "street": "ABC Road",
              "subDistrict": "",
              "vtc": "my location"
          },
          "photo": "...base64...",
          "aadhaarNumber": "XXXXXXXX8888",
          "generatedAt": "2024-03-22T15:18:35.269+05:30"
      },
      "xml": {
        "xmlBase64": "...base64..."
      }
  }
}
```
```

--------------------------------

### Create eKYC Request (API)

Source: https://docs.setu.co/data/ekyc

Initiates an eKYC request to start the customer's verification journey. Requires a redirection URL and optionally accepts a webhook URL. Returns a unique request ID, status, and a KYC URL.

```json
{
  "webhook_url": "<client_webhook_url>", // Optional
  "redirection_url": "<client_redirection_url>"
}
```

--------------------------------

### Web Redirection Flow

Source: https://docs.setu.co/data/ekyc/quickstart

Information on how status and ID are passed as query parameters during the web redirection flow.

```APIDOC
## Web Redirection Flow

### Description
Details on how the eKYC status and ID are appended as query parameters to the redirection URL.

### Redirection URL Format
```
https://{your_redirection_url}?status={status}&id={ekyc_id}&errorCode={code}
```
```

--------------------------------

### GET /payment-links/<platformBillId>

Source: https://docs.setu.co/payments/upi-deeplinks/quickstart

Retrieve the current status of a specific payment link.

```APIDOC
## GET /payment-links/<platformBillId>

### Description
Checks the status of an existing payment link using the platform bill ID.

### Method
GET

### Endpoint
/payment-links/<platformBillId>

### Parameters
#### Path Parameters
- **platformBillId** (string) - Required - The unique ID of the bill/payment link.

### Response
#### Success Response (200)
- **status** (string) - Current status of the payment link (e.g., PAID, PENDING, EXPIRED).

#### Response Example
{
  "status": "PAID"
}
```

--------------------------------

### GET /payment-links/{platformBillId}

Source: https://docs.setu.co/payments/upi-deeplinks/quickstart

Checks the payment status for a given payment link. This is intended for specific use cases and not for polling.

```APIDOC
## GET /payment-links/{platformBillId}

### Description
Checks the payment status for a given payment link. This is intended for specific use cases and not for polling. It can be used, for example, if a callback is not received within a certain timeframe.

### Method
GET

### Endpoint
/payment-links/{platformBillId}

### Path Parameters
- **platformBillId** (string) - Required - The unique identifier for the payment link.

### Headers
- **X-Setu-Product-Instance-ID** (string) - Required - Your unique product instance ID.
- **Authorization** (string) - Required - Bearer <insert_token_here>. Generate this token using OAuth or JWT.

### Response
#### Success Response (200)
(Details of the response body for success are not provided in the source text. Typically, this would include the payment status.)

#### Error Response
(Details of error responses are not provided in the source text.)
```

--------------------------------

### Loan EMI Payment Options Example (JSON)

Source: https://docs.setu.co/payments/billpay/api-integration/paying-bills/bill-payment-options

Provides an example of payment options for a loan EMI, demonstrating how users can choose to pay a single month's EMI, multiple months, or the full outstanding amount (foreclosure).

```json
{
  "bills": [{
    "amount": 1200000,  // ₹12000 full outstanding
    "billDate": "2024-12-01",
    "dueDate": "2024-12-31",
    "paymentOptions": [
      { "name": "1 Month EMI", "amount": 300000 },     // ₹3000
      { "name": "3 Month EMI", "amount": 900000 },     // ₹9000
      { "name": "Foreclosure", "amount": 1150000 }     // ₹11500 (with discount)
    ]
  }]
}
```

--------------------------------

### POST /refund/batch

Source: https://docs.setu.co/payments/upi-deeplinks/quickstart

Initiate a batch refund process.

```APIDOC
## POST /refund/batch

### Description
Processes a batch of refunds for multiple transactions.

### Method
POST

### Endpoint
/refund/batch

### Request Example
{
  "refunds": [
    { "transactionId": "tx_1", "amount": 500 },
    { "transactionId": "tx_2", "amount": 200 }
  ]
}

### Response
#### Success Response (200)
- **batchID** (string) - Unique identifier for the refund batch.

#### Response Example
{
  "batchID": "ref_batch_98765"
}
```

--------------------------------

### POST /triggers/funds/addCredit

Source: https://docs.setu.co/payments/upi-deeplinks/quickstart

Mocks a successful payment against a payment link. This is useful for testing and automation purposes in sandbox environments.

```APIDOC
## POST /triggers/funds/addCredit

### Description
Mocks a successful payment against a payment link. This is useful for testing and automation purposes in sandbox environments.

### Method
POST

### Endpoint
/triggers/funds/addCredit

### Headers
- **X-Setu-Product-Instance-ID** (string) - Required - Your unique product instance ID.
- **Authorization** (string) - Required - Bearer <insert_token_here>. Generate this token using OAuth or JWT.
- **Content-Type** (string) - Required - application/json

### Request Body
- **amount** (float or double) - Required - The amount in rupees.
- **type** (string) - Required - The payment type (e.g., "UPI").
- **destinationAccount** (object) - Required - Details of the destination account.
  - **accountID** (string) - Required - The UPI ID generated for the link.
- **sourceAccount** (object) - Required - Details of the source account.
  - **accountID** (string) - Required - A dummy VPA in a valid format.
- **transactionReference** (string) - Required - The platformBillID from the Create Link response.

### Request Example
```json
{
  "amount": 100,
  "type": "UPI",
  "destinationAccount": {
    "accountID": "test464618891939677612@kaypay"
  },
  "sourceAccount": {
    "accountID": "dummy_customer@vpa"
  },
  "transactionReference": "464618891939677612"
}
```

### Response
#### Success Response (200)
- **Status** (string) - OK
```

--------------------------------

### GET /api/ekyc/:request_id

Source: https://docs.setu.co/data/ekyc

Retrieves the current status and associated KYC data for a specific eKYC request.

```APIDOC
## GET /api/ekyc/:request_id

### Description
Call this API to get the status and data (if the status is SUCCESS) of your eKYC request.

### Method
GET

### Endpoint
/api/ekyc/:request_id

### Parameters
#### Path Parameters
- **request_id** (string) - Required - The unique ID returned during the creation of the eKYC request.

### Response
#### Success Response (200)
- **id** (string) - The request ID.
- **status** (string) - The current status (CREATED, KYC_REQUESTED, SUCCESS, ERROR).
- **data** (object) - Contains Aadhaar details and XML data if status is SUCCESS.

#### Response Example
{
  "id": "0c624d3e-9cb0-4323-b468-d89092d7d305",
  "status": "SUCCESS",
  "kycURL": "http://dg-ekyc.setu.co/public/ekyc-web/0c624d3e-9cb0-4323-b468-d89092d7d305",
  "data": {
    "aadhaar": { "name": "Ritesh Ujjwal", "aadhaarNumber": "XXXXXXXX8888" },
    "xml": { "xmlBase64": "...base64..." }
  }
}
```

--------------------------------

### Retrieve Insights API Request Example

Source: https://docs.setu.co/data/insights/quickstart/api-integration

This example demonstrates how to make a GET request to the Retrieve Insights API. It requires the 'reportId' obtained from the previous step and specific headers for authentication and content negotiation. The 'Accept' header should be 'application/json'.

```http
GET /v3/insight?reportId={reportId}
--header 'Accept: application/json'
--header 'x-client-id: <client_id>'
--header 'x-client-secret: <client_secret>'
--header 'x-product-instance-id: <product_instance_id>'
```

--------------------------------

### Create Payment Link

Source: https://docs.setu.co/payments/upi-deeplinks/quickstart

This endpoint allows merchants to create a payment link for a specified amount and currency. It supports various options for amount exactness, transaction notes, and additional information.

```APIDOC
## POST /create/payment/link

### Description
Creates a payment link for a specified amount and currency. Supports flexible options for amount exactness and additional transaction details.

### Method
POST

### Endpoint
/create/payment/link

### Parameters
#### Request Body
- **billerBillID** (string) - Required - An identifier for this link in the merchant's system.
- **amount** (object) - Required - The amount to be collected.
  - **value** (integer) - Required - The amount in paise (e.g., 10000 for INR 100).
  - **currencyCode** (string) - Required - The currency code, typically 'INR'.
- **amountExactness** (enum) - Optional - Specifies the flexibility of the payment amount. Allowed values: EXACT, EXACT_DOWN, ANY. Defaults to EXACT.
- **name** (string) - Optional - The payee's name.
- **transactionNote** (string) - Optional - A message for the UPI payment.
- **additionalInfo** (object) - Optional - Additional key-value pairs to be sent back in payment notifications.
  - **UUID** (string) - Optional - A unique identifier.
  - **tags** (string) - Optional - Tags for categorization.

### Request Example
```json
{
    "billerBillID": "EB-1123-345324",
    "amount": {
        "value": 10000,
        "currencyCode": "INR"
    },
    "amountExactness": "EXACT",
    "name": "Merchant name",
    "transactionNote": "Payment for ABC bill",
    "additionalInfo": {
        "UUID": "b6b6f173-8649-4b2e-9c22-f78e9195a23e",
        "tags": "electricity"
    }
}
```

### Response
#### Success Response (200)
- **status** (integer) - The HTTP status code.
- **success** (boolean) - Indicates if the request was successful.
- **data** (object) - Contains the payment link details.
  - **name** (string) - The name associated with the payment link.
  - **paymentLink** (object) - Details of the generated payment link.
    - **shortURL** (string) - A short URL that can be shared with customers.
    - **upiID** (string) - The UPI ID for the payment.
    - **upiLink** (string) - A deep link for UPI payments.
  - **platformBillID** (string) - A unique ID for tracking the payment link.

#### Response Example
```json
{
    "status": 200,
    "success": true,
    "data": {
        "name": "Test Link generator",
        "paymentLink": {
            "shortURL": "https://bills.pe/yH9c9",
            "upiID": "test464618891939677612@kaypay",
            "upiLink": "upi://pay?pa=test464618891939677612@kaypay&pn=Test+Link+generator&am=100.00&tr=EB-1123-345324&tn=Payment+for+EB-1123-345324&cu=INR"
        },
        "platformBillID": "464618891939677612"
    }
}
```
```

--------------------------------

### FIP List API Request Example

Source: https://docs.setu.co/data/account-aggregator/api-integration/fip-apis

This snippet demonstrates how to make a GET request to the FIP List API. No specific parameters are shown for this basic request, but it serves as a starting point for interacting with the API.

```http
GET /v2/fips
```

--------------------------------

### Mock Payment Trigger via POST

Source: https://docs.setu.co/payments/upi-deeplinks/quickstart

Triggers a mock payment in the sandbox environment to simulate a successful customer transaction. Requires a Bearer token for authorization and specific account details in the JSON body.

```json
{
  "amount": 100,
  "type": "UPI",
  "destinationAccount": {
    "accountID": "test464618891939677612@kaypay"
  },
  "sourceAccount": {
    "accountID": "dummy_customer@vpa"
  },
  "transactionReference": "464618891939677612"
}
```

--------------------------------

### Webhook Response Example (Event)

Source: https://docs.setu.co/data/ekyc

Represents the data structure received via webhook when an eKYC event occurs, typically upon successful verification. It contains event details and the verified Aadhaar data, including personal information and the XML payload.

```json
{
    "event": "EKYC_DATA",
    "data": {
        "id": "...",
        "status": "SUCCESS",
        "aadhaar": {
            "name": "Ritesh Ujjwal",
            "dateOfBirth": "1989",
            "gender": "M",
            "address": {
                "careOf": "",
                "country": "India",
                "district": "ABC",
                "house": "",
                "landmark": "XYZ",
                "locality": "AAAAAA",
                "pin": "560001",
                "postOffice": "Bangalore",
                "state": "Karnataka",
                "street": "ABC Road",
                "subDistrict": "",
                "vtc": "my location"
            },
            "photo": "...base64...",
            "aadhaarNumber": "XXXXXXXX8888", // masked aadhaar number
            "generatedAt": "2024-03-22T15:18:35.269+05:30"
        },
        "xml": {
            "xmlBase64": "...base64..."
        }
    }
}
```

--------------------------------

### Setu API Request Headers

Source: https://docs.setu.co/payments/upi-deeplinks/quickstart

Standard HTTP headers required for all Setu API requests. Includes the product instance ID, bearer token authentication, and content type specification.

```http
X-Setu-Product-Instance-ID: <your-merchant-id>
Authorization: Bearer <insert_token_here>
Content-Type: application/json
```

--------------------------------

### Get eKYC Request Status and Data (API)

Source: https://docs.setu.co/data/ekyc

Retrieves the status and, if available, the eKYC data for a given request ID. This API is used to check the progress or completion of the verification process. The response includes the request ID, status, and potentially Aadhaar details and XML data.

```json
GET /api/ekyc/:request_id
```

--------------------------------

### POST /payment-links

Source: https://docs.setu.co/payments/upi-deeplinks/quickstart

Create a new UPI payment link to initiate a transaction.

```APIDOC
## POST /payment-links

### Description
Creates a new UPI payment link for a transaction.

### Method
POST

### Endpoint
/payment-links

### Parameters
#### Request Body
- **X-Setu-Product-Instance-ID** (string) - Required - Unique identifier for your merchant configuration.
- **Authorization** (string) - Required - Bearer <token> (OAuth or JWT).
- **Content-Type** (string) - Required - application/json

### Request Example
{
  "amount": 1000,
  "currency": "INR",
  "description": "Payment for order #123"
}

### Response
#### Success Response (200)
- **paymentLink** (string) - The generated UPI payment URL.

#### Response Example
{
  "paymentLink": "https://upi.setu.co/pay/12345"
}
```

--------------------------------

### Update GET /disputes Query Parameters (API)

Source: https://docs.setu.co/payments/billpay/api-integration/v2-migration

Illustrates the modification of query parameters for the GET /disputes API. `partnerRefIds` has been renamed to `paymentRefIds`, and `customerMobileNumber` to `mobile`.

```HTTP
- GET /disputes?partnerRefIds=N2001121212344&customerMobileNumber=9505987798
+ GET /disputes?paymentRefIds=N2001121212344&mobile=9505987798
```

--------------------------------

### Create UPI Payment Link API

Source: https://docs.setu.co/payments/upi-deeplinks/quickstart

Endpoint for generating a new UPI payment link. Requires a POST request with specific authentication and product instance headers.

```http
POST /payment-links HTTP/1.1
Host: uat.setu.co/api
X-Setu-Product-Instance-ID: <your-merchant-id>
Authorization: Bearer <insert_token_here>
Content-Type: application/json
```

--------------------------------

### Create Name Match Request via HTTP

Source: https://docs.setu.co/data/match-apis/name-match/quickstart

This snippet demonstrates the POST request structure for the Name Match API. It requires two name strings as input, which must be under 100 characters and exclude special characters except for periods, apostrophes, and hyphens.

```HTTP
POST /api/match/v1/name

payload= {
    "name1": "Rakesh Kumar Singh",
    "name2": "Rakesh Kumar Singh"
}
```

--------------------------------

### GET /bbps/bills/mandate/response

Source: https://docs.setu.co/payments/billpay/api-integration/apis

Polls the status of a previously initiated FX mandate booking.

```APIDOC
## GET /bbps/bills/mandate/response

### Description
Polls the status of an FX mandate booking request using the reference ID generated during the request phase.

### Method
GET

### Endpoint
/bbps/bills/mandate/response

### Query Parameters
- **refId** (string) - Required - The reference ID received from the booking request

### Response
#### Success Response (200)
- **status** (string) - Success
- **refId** (string) - The reference ID
- **data** (object) - Contains the biller response details
```

--------------------------------

### GET /api/v2/bbps/billers

Source: https://docs.setu.co/payments/billpay/api-integration/fx-retail

Fetch all FX Retail billers to identify available forex services.

```APIDOC
## GET /api/v2/bbps/billers

### Description
Retrieves a list of all billers under the Forex category. Use this to identify Relationship banks or CCIL pseudo-billers.

### Method
GET

### Endpoint
/api/v2/bbps/billers?categoryName=Forex

### Parameters
#### Query Parameters
- **categoryName** (string) - Required - Must be 'Forex'
- **pseudoBiller** (boolean) - Optional - Filter by pseudo-biller status

### Response
#### Success Response (200)
- **billerId** (string) - Unique identifier for the biller
- **valAddFlag** (boolean) - Indicates if value-added services are enabled
- **pseudoBiller** (boolean) - Indicates if the biller is a CCIL pseudo-biller
```

--------------------------------

### GET /disputes

Source: https://docs.setu.co/payments/billpay/api-integration/v2-migration

Retrieves a list of disputes. Parameters have been renamed from partnerRefIds to paymentRefIds and customerMobileNumber to mobile.

```APIDOC
## GET /disputes

### Description
Lists disputes associated with the account. Note the parameter renaming: partnerRefIds is now paymentRefIds and customerMobileNumber is now mobile.

### Method
GET

### Endpoint
/disputes

### Parameters
#### Query Parameters
- **paymentRefIds** (string) - Optional - The payment reference ID.
- **mobile** (string) - Optional - The customer mobile number.

### Request Example
GET /disputes?paymentRefIds=N2001121212344&mobile=9505987798

### Response
#### Success Response (200)
- **data** (object) - Contains the list of disputes.

#### Response Example
{
  "data": {
    "disputes": [
      {
        "complaintId": "AS013201095300ZKXR6T",
        "mobile": "9505987798",
        "paymentRefId": "N2001121212344"
      }
    ]
  }
}
```

--------------------------------

### Create Payment Link Request

Source: https://docs.setu.co/payments/upi-deeplinks/quickstart

JSON payload structure for initiating a payment link request. It includes biller identifiers, amount details in paise, and optional metadata for reconciliation.

```json
{
    "billerBillID"    : "EB-1123-345324",
    "amount": {
        "value"        : 10000,
        "currencyCode" : "INR"
    },
    "amountExactness" : "EXACT",
    "name" : "Merchant name",
    "transactionNote": "Payment for ABC bill",
    "additionalInfo" : {
        "UUID": "b6b6f173-8649-4b2e-9c22-f78e9195a23e",
        "tags": "electricity"
    }
}
```

--------------------------------

### GET /v3/insight

Source: https://docs.setu.co/data/insights/quickstart/api-integration

Retrieves the generated insight report for a specific report ID.

```APIDOC
## GET /v3/insight

### Description
Use the `reportId` obtained from the insight generation process to poll this endpoint and retrieve the generated financial insight report.

### Method
GET

### Endpoint
/v3/insight?reportId={reportId}

### Parameters
#### Query Parameters
- **reportId** (string) - Required - The unique identifier for the insight generation job.

### Request Example
GET /v3/insight?reportId=05a5a389-b922-4197-be03-b309cdcc575a
--header 'Accept: application/json'
--header 'x-client-id: <client_id>'
--header 'x-client-secret: <client_secret>'
--header 'x-product-instance-id: <product_instance_id>'

### Response
#### Success Response (200)
- **status** (string) - The status of the request.
- **body** (object) - Contains the list of accounts and their respective insights.

#### Response Example
{
    "status": "Success",
    "version": "0.73.1",
    "body": {
        "accounts": [
            {
                "accountIdentifierKey": "8a467ff9-51a5-4c8e-9cec-396d56acda13",
                "insights": [
                    {
                        "indicatorName": "fraud_flags",
                        "value": [
                            {
                                "title": "Mostly Cash Mode",
                                "description": "Maximum transactions (80%) involving cash deposit or withdrawals",
                                "value": "100% of transactions were cash based"
                            }
                        ]
                    }
                ],
                "status": "success"
            }
        ]
    }
}
```

--------------------------------

### Verify GSTIN with Additional Address

Source: https://docs.setu.co/data/gst/quickstart

This request demonstrates verifying a GSTIN that is valid and has additional address information associated with it. The API call structure is the same as a standard GSTIN verification, with the response detailing the additional address components.

```json
{
    "gstin": "27AAICB3919J1CT"
}
```

--------------------------------

### Setu Get Payment Link API Response Body

Source: https://docs.setu.co/payments/billpay/custom-payment/website

Example JSON response body for the Get Payment Link API. Indicates the success status and provides a one-time payment link.

```json
{
  "code": "success",
  "data": {
    "link": "https://example.com/onetimepayment-link"
  }
}
```

--------------------------------

### Verify PAN API Request and Response

Source: https://docs.setu.co/data/pan

Demonstrates the HTTP POST request structure to verify a PAN number and the corresponding JSON response returned by the Setu API. The request requires the PAN value, consent flag, and a reason string, while the response provides verification status and user details.

```http
POST /api/verify/pan

{
  "pan": "ABCDE1234A",
  "consent": "Y",
  "reason": "Reason for verifying PAN set by the developer"
}
```

```json
{
  "data": {
    "aadhaar_seeding_status": "LINKED",
    "category": "Individual",
    "full_name": "John Doe",
    "first_name": "John Hartwell",
    "middle_name": "Walter",
    "last_name": "Doe"
  },
  "message": "PAN is valid",
  "verification": "success",
  "traceId": "1-6346a91a-620cf6cc4f68d2e30316881e"
}
```

--------------------------------

### GET /transactions

Source: https://docs.setu.co/payments/billpay/api-integration/v2-migration

Retrieves transaction history. Fields customerMobileNumber and partnerRefId have been updated to mobile and paymentRefId respectively.

```APIDOC
## GET /transactions

### Description
Fetches transaction records. The response fields have been updated to use 'mobile' and 'paymentRefId'.

### Method
GET

### Endpoint
/transactions

### Response
#### Success Response (200)
- **data** (object) - Contains the list of transactions.

#### Response Example
{
  "data": {
    "transactions": [
      {
        "transactionId": "AS01320109451110R5LL",
        "mobile": "9505987798",
        "paymentRefId": "N2001121212344"
      }
    ]
  }
}
```

--------------------------------

### Verify GSTIN using Setu API

Source: https://docs.setu.co/data/gst/quickstart

This API endpoint is used to verify a provided GSTIN. It requires 'x-client-id', 'x-client-secret', and 'x-product-instance-id' headers for authentication. The request body contains the 'gstin' to be verified. The response indicates the verification status and provides detailed GST information if successful.

```json
{
    "gstin": "27AAICB3918J1CT"
}
```

--------------------------------

### GET /fips/active

Source: https://docs.setu.co/data/account-aggregator/embed-setu-aa

Retrieves the list of currently active Financial Information Providers (FIPs) to be used for guided auto-discovery in consent requests.

```APIDOC
## GET /fips/active

### Description
Fetches a list of active FIPs. FIUs must verify FIP status in real-time before creating a consent request to ensure only active providers are included in the guided auto-discovery flow.

### Method
GET

### Endpoint
/fips/active

### Parameters
None

### Request Example
GET /fips/active

### Response
#### Success Response (200)
- **fips** (array) - List of active FIP objects containing ID and status.

#### Response Example
{
  "fips": [
    { "id": "setu-fip-1", "status": "active" },
    { "id": "setu-fip-2", "status": "active" }
  ]
}
```