Skip to main content
POST
/
ppi
/
otp
/
submit
Submit OTP
curl --request POST \
  --url https://api.cashfree.com/ppi/otp/submit \
  --header 'Content-Type: application/json' \
  --header 'x-api-version: <x-api-version>' \
  --header 'x-client-id: <api-key>' \
  --header 'x-client-secret: <api-key>' \
  --data '
{
  "otp_verification_id": "Test123",
  "otp": "222113"
}
'
{ "otp_verification_id": "Test123", "cf_otp_verification_id": "8901234567890123456", "status": "VERIFIED", "user_id": "USER827364" }

Authorizations

ā€‹
x-client-id
string
header
required

Your unique client identifier issued by Cashfree. You can find this in your Merchant Dashboard.

ā€‹
x-client-secret
string
header
required

The secret key associated with your client ID. Use this to authenticate your API requests. You can find this in your Merchant Dashboard.

Headers

ā€‹
x-api-version
string
default:2025-11-01
required

API version to be used. Format is in YYYY-MM-DD.

Example:

"2025-11-01"

Body

application/json

Request parameters to submit and verify an OTP.

ā€‹
otp_verification_id
string
required

Unique identifier for the OTP verification request.

Example:

"Test123"

ā€‹
otp
string
required

The OTP provided by the user for verification.

Example:

"123456"

Response

Success response for verifying an OTP.

ā€‹
otp_verification_id
string

Unique identifier for the OTP verification request.

Example:

"Test123"

ā€‹
cf_otp_verification_id
string

Unique identifier for the OTP verification request, generated by Cashfree.

Example:

"8901234567890123456"

ā€‹
status
enum<string>

Status of the OTP verification process.

Available options:
VERIFIED,
FAILED
Example:

"VERIFIED"

ā€‹
user_id
string

Unique identifier for the user, as provided by you during PPI user creation.

Example:

"USER827364"