---
page_source: https://juspay.io/in/docs/upi-merchant-stack/docs/transactions/verify-vpa-360
page_title: Verify VPA 360
---

## API Version: Default


## **Verify VPA 360** 



This API will be used to resolve the name of the entity to whom a vpa belongs. In case of a valid vpa, it will provide the name and other details of the entity.

**name, ifsc**  and **iin**  will be sent in response only when **gatewayResponseCode**  is **"00"** .

**isMerchantVerified** , **mcc**  and **merchantType**  will be sent in response only when **isMerchant**  is **"true"** .

UPI Numbers can also be resolved using this API by passing the request parameter **vpa**  in the format **upiNumber@mapper.npci**  (Example: **9876543210@mapper.npci** ). The actual VPA mapped to the **upiNumber**  shall be sent in the response parameter **vpa** .## Endpoints:
- Production: {{host}}/api/{{uri}}/merchants/vpas/validity360

## Request Type: 
POST

## Content-Type: 
application/json

## Headers:

#### jpupi-routing-id:
Header value should be same as of **upiRequestId**  sent in request body
- Tags: String, Mandatory
## Sample Code Snippets:
### Code Snippets:

#### Shell Code Snippet:

```shell
{"success":false,"message":"No Data found for the given path"}
```

### Sample Request and Response:

#### Request:
```json
{"success":false,"message":"No Data found for the given path"}
```

#### Response:
```json
{"success":false,"message":"No Data found for the given path"}
```

## Body Parameters:
### Parameters:

#### vpa:
- Description: VPA to be verified.

Example:**** something@handle. 

**Constraint:**  VPA should only contain a-z, 0-9, . (dot), - (hyphen).
- Tags: String, Mandatory

#### iat:
- Description: Current Epoch Unix timestamp string. Has to be of 13 digit in Milliseconds. 

Example: 1496918882000.
- Tags: String, Mandatory

#### upiRequestId:
- Description: Unique id sent for the request.**Constraints:** Must be 35 character alphanumeric. Should always start with PSP Prefix.
- Tags: String, Mandatory

#### udfParameters:
- Description: Merchant Defined Parameters

Example: "{\"udf1\":\"value1\",\"udf2\":\"value2\",…}"**Note** : Few special characters are not allowed. Regex for the characters which are not allowed : **^[^/#-()*!%~`]+$** 
- Tags: Stringified JSON, Optional
## API Responses:
### 200:

#### status:
- Description: PSP status of the API.

**Values:** SUCCESS, FAILURE.
- Tags: String, Mandatory

#### responseCode:
- Description: PSP response code for the API.

**Values:** Refer Codes Guide in Resource Section.
- Tags: String, Mandatory

#### responseMessage:
- Description: PSP response message for the API.

**Values:** Refer Codes Guide in Resource Section.
- Tags: String, Mandatory

#### payload:
- Value:
  - **MerchantId**:
    - Description: Unique id for the merchant as passed in request headers.
    - Tags: String, Mandatory
  - **MerchantChannelId**:
    - Description: Unique id for the merchant channel as passed in request headers.
    - Tags: String, Mandatory
  - **GatewayTransactionId**:
    - Description: Transaction id returned by gateway.
    - Tags: String, Mandatory
  - **GatewayResponseStatus**:
    - Description: Response status returned by gateway.
      
      `SUCCESS`, `FAILURE`
    - Tags: String, Mandatory
  - **GatewayResponseCode**:
    - Description: Response code returned by gateway.
    - Tags: String, Mandatory
  - **GatewayResponseMessage**:
    - Description: Response message for code returned by gateway.
    - Tags: String, Mandatory
  - **Vpa**:
    - Description: This is a vpa for which name should be resolved.
      
      **Values:** As passed in request.
    - Tags: String, Mandatory
  - **Name**:
    - Description: Name of the customer.
    - Tags: String, Optional
  - **Ifsc**:
    - Description: IFSC code of the account linked to this VPA.
    - Tags: String, Optional
  - **Iin**:
    - Description: IIN code of the account linked to this VPA.
    - Tags: String, Optional
  - **IsMerchant**:
    - Description: Flag indicating whether the VPA is of merchant or not.
    - Tags: String, Mandatory
  - **IsMerchantVerified**:
    - Description: Flag indicating whether merchant is verified or not.
    - Tags: String, Optional
  - **Mcc**:
    - Description: Merchant Category Code for the merchant whose VPA is passed.
    - Tags: String, Optional
  - **MerchantType**:
    - Description: Merchant Type for the merchant whose VPA is passed.
    - Tags: String, Optional
  - **UpiNumber**:
    - Description: Number mapped to a customer's VPA that is unique to the customer across the UPI ecosystem.
      
      **Values:** 8 to 10 digit numeric string. 10 digit number must be the mobile number. Last 3 digits must not be same. Must not start with a 0.
    - Tags: String, optional
  - **AccType**:
    - Description: Account Type.
    - Tags: String, optional
- Tags: Json String, Mandatory

#### udfParameters:
- Description: Merchant Defined ParametersExample: "{\"udf1\":\"value1\",\"udf2\":\"value2\",…}"
- Tags: Stringified JSON, optional


---

## API Version: v1


## **Verify VPA 360** 



This API will be used to resolve the name of the entity to whom a vpa belongs. In case of a valid vpa, it will provide the name and other details of the entity.

**name, ifsc**  and **iin**  will be sent in response only when **gatewayResponseCode**  is **"00"** .

**isMerchantVerified** , **mcc**  and **merchantType**  will be sent in response only when **isMerchant**  is **"true"** .

UPI Numbers can also be resolved using this API by passing the request parameter **vpa**  in the format **upiNumber@mapper.npci**  (Example: **9876543210@mapper.npci** ). The actual VPA mapped to the **upiNumber**  shall be sent in the response parameter **vpa** .

In this version, the features supported by that vpa are also shared along with the response. The features supported against the different feature tags are listed below.## Endpoints:
- Production: {{host}}/api/n2/merchants/vpas/validity360

## Request Type: 
POST

## Content-Type: 
application/json

## Headers:

#### jpupi-routing-id:
Header value should be same as of upiRequestId sent in request body
- Tags: String, Mandatory
## Sample Code Snippets:
### Code Snippets:

#### Shell Code Snippet:

```shell
{"success":false,"message":"No Data found for the given path"}
```

### Sample Request and Response:

#### Request:
```json
{"success":false,"message":"No Data found for the given path"}
```

#### Response:
```json
{"success":false,"message":"No Data found for the given path"}
```

## Body Parameters:
### Parameters:

#### vpa:
- Description: VPA to be verified.

Example:**** something@handle. 

**Constraint:**  VPA should only contain a-z, 0-9, . (dot), - (hyphen).
- Tags: String, Mandatory

#### iat:
- Description: Current Epoch Unix timestamp string. Has to be of 13 digit in Milliseconds. 

Example: 1496918882000.
- Tags: String, Mandatory

#### upiRequestId:
- Description: Unique id sent for the request.**Constraints:** Must be 35 character alphanumeric. Should always start with PSP Prefix.
- Tags: String, Mandatory

#### udfParameters:
- Description: Merchant Defined Parameters

Example: "{\"udf1\":\"value1\",\"udf2\":\"value2\",…}"
- Tags: Stringified JSON, Optional
## API Responses:
### 200:

#### status:
- Description: PSP status of the API.

**Values:** SUCCESS, FAILURE.
- Tags: String, Mandatory

#### responseCode:
- Description: PSP response code for the API.

**Values:** Refer Codes Guide in Resource Section.
- Tags: String, Mandatory

#### responseMessage:
- Description: PSP response message for the API.

**Values:** Refer Codes Guide in Resource Section.
- Tags: String, Mandatory

#### payload:
- Value:
  - **MerchantId**:
    - Description: Unique id for the merchant as passed in request headers.
    - Tags: String, Mandatory
  - **MerchantChannelId**:
    - Description: Unique id for the merchant channel as passed in request headers.
    - Tags: String, Mandatory
  - **GatewayTransactionId**:
    - Description: Transaction id returned by gateway.
    - Tags: String, Mandatory
  - **GatewayResponseStatus**:
    - Description: Response status returned by gateway.
      
      `SUCCESS`, `FAILURE`
    - Tags: String, Mandatory
  - **GatewayResponseCode**:
    - Description: Response code returned by gateway.
    - Tags: String, Mandatory
  - **GatewayResponseMessage**:
    - Description: Response message for code returned by gateway.
    - Tags: String, Mandatory
  - **Vpa**:
    - Description: This is a vpa for which name should be resolved.
      
      **Values:** As passed in request.
    - Tags: String, Mandatory
  - **Name**:
    - Description: Name of the customer.
    - Tags: String, Optional
  - **Ifsc**:
    - Description: IFSC code of the account linked to this VPA.
    - Tags: String, Optional
  - **Iin**:
    - Description: IIN code of the account linked to this VPA.
    - Tags: String, Optional
  - **IsMerchant**:
    - Description: Flag indicating whether the VPA is of merchant or not.
    - Tags: String, Mandatory
  - **IsMerchantVerified**:
    - Description: Flag indicating whether merchant is verified or not.
    - Tags: String, Optional
  - **Mcc**:
    - Description: Merchant Category Code for the merchant whose VPA is passed.
    - Tags: String, Optional
  - **MerchantType**:
    - Description: Merchant Type for the merchant whose VPA is passed.
    - Tags: String, Optional
  - **UpiNumber**:
    - Description: Number mapped to a customer's VPA that is unique to the customer across the UPI ecosystem.
      
      **Values:** 8 to 10 digit numeric string. 10 digit number must be the mobile number. Last 3 digits must not be same. Must not start with a 0.
    - Tags: String, optional
  - **AccType**:
    - Description: Account Type.
    - Tags: String, optional
  - **FeatureTags**:
    - Description: This will be an array of feature values, each having it's own significance as decided by NPCI. 
      
      **Feature Tag Values :** 01 (MANDATE), 05 (CREDIT), 06 (PPIWALLET), 09 (UOD), 10 (VOUCHER), 11 (Special commercials 1 for RuPay Credit Card on UPI), 12 (Special commercials 2 for PPI on UPI), 13 (Special commercials 3 for Credit Line on UPI), 14 to 30 (Reserved for future use-cases), 31 (Credit Line Products)**Note :** Empty Feature Tags List indicate that all the features are supported.
    - Value:
    - Tags: Array, Optional
- Tags: Json String, Mandatory

#### udfParameters:
- Description: Merchant Defined ParametersExample: "{\"udf1\":\"value1\",\"udf2\":\"value2\",…}"
- Tags: Stringified JSON, optional