> ## Documentation Index
> Fetch the complete documentation index at: https://razorpay-881012b3.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Set Or Reset UPI PIN
> Set or reset UPI PIN using the Razorpay TPAP Pro API.
Available in
🇮🇳 India
Customer’s card details and OTP are required to set or reset UPI PIN. These details are validated at the payment source provider’s (bank) end before allowing to set the PIN. Use this endpoint to generate the OTP via the remitter bank while setting the UPI PIN.
```bash Curl theme={null}
curl -X POST 'api.rzp..com/v1/upi/tpap/fundsources/:id/upi_pin?expand[]=vpas' \
-u [YOUR_KEY_ID]:[YOUR_SECRET] \
-H "Content-type: application/json" \
-H "x-device-fingerprint: " \
-H "x-device-fingerprint-timestamp: 1496918882000" \
-H "x-customer-reference: customer-id-from-customer" \
-d '{
"action":"set",
"upi_credentials":{
// credentials received from CL
},
"upi_transaction_id":"123qwert12",
"vpa":"abc@upiexample",
"card":{
"last6":"123456",
"expiry_month":"02",
"expiry_year":"26"
},
"device":{
"geocode":"1234.1213",
"ip":"198.1.1.1"
}
}'
```
```json Response theme={null}
{
"entity":"upi.fundsource",
"id":"fs_1234",
"type":"savings",
"customer_name":"name",
"masked_account_number":"xx9987",
"ifsc":"IFSC001",
"upi_pin_set":true,
"upi_pin_length":4,
"otp_length":4,
"atm_pin_length":4,
"fundsource_provider":{
"name":"HDFC Bank",
"upi_iin":"600007",
"upi_enabled":false,
"mobile_registration_format":"FORMAT1",
"logo_url":""
},
"vpas":{
"entity":"collection",
"count":1,
"items":[
{
"mobile":"9999999999",
"address":"anc@handle",
"status":"active",
"primary":true
}
]
}
}
```
## Query Parameters
The payment source identifier.
## Request Parameters
Indicates whether the action is a set or reset. Both set and reset happen from the same API, so we should specify the action to distinguish between them. Possible values:
* `set`
* `reset`
The encrypted UPI PIN. NPCI credentials is the output from the WebCL page.
The unique identifier of the transaction across all entities, created by the originator.
Card details.
Last 6 digits of the card which the fundsource provider will verify before setting the PIN.
Expiry month of the card in `MM` format.
Expiry year of the card in `YY` format.
VPA of the customer for which the PIN is set.
Device details.
The IP address of the device.
The location coordinates of the device. For example, `12.9667,77.5667`.
## Response Parameters
Name of the entity. Here, it is `fundsource`.
Unique identifier of the entity.
Type of account.
Name of the account holder.
Masked account number.
IFSC of the bank.
UPI Issuer Identification Numbers (iin) of the payment source provider issued by NPCI.
Indicates whether the UPI PIN is set. Possible values:
* `true`: UPI PIN is set.
* `false`: UPI PIN is not set.
Length of the UPI PIN.
Length of the OTP.
Length of the ATM PIN.
Payment source provider details. Here, if the payment source is a bank, payment source providers will be bank information.
Name of the payment source.
UPI Issuer Identification Numbers (upi\_iin) of the payment source provider issued by NPCI.
Indicates whether the provider has UPI enabled. Possible values:
* `true`: UPI is enabled.
* `false`: UPI is not enabled.
Indicates the format as defined by NPCI - `format1`, `format2` and so on.
The URL of the bank logo.
Details of the VPAs linked to the payment source.
The entity type name. Here, it is `collection`.
Indicates the number of items in the entity type.
VPA details.
The mobile number of the VPA linked to the payment source.
The address of the VPA linked to the payment source.
The status of the VPA linked to the payment source.
Indicates if the VPA linked to the payment source marked as primary.
* `true`: VPA is linked to the payment source.
* `false`: VPA is not linked to the payment source.