Skip to main content
POST
/
api
/
v1
/
sub-accounts
/
{sub_auth_id}
/
kyc
/
verify-pan
Verify PAN
curl --request POST \
  --url https://api.vobiz.ai/api/v1/sub-accounts/{sub_auth_id}/kyc/verify-pan \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "pan": "ABCDE1234F"
}
'
{
  "verification_type": "pan",
  "status": "verified",
  "pan": "ABCDE1234F",
  "registered_name": "ACME PRIVATE LIMITED",
  "name_match": true,
  "kyc_calls_blocked": true
}

Documentation Index

Fetch the complete documentation index at: https://docs.vobiz.ai/llms.txt

Use this file to discover all available pages before exploring further.

Runs a real PAN verification for the sub-account. pan must be exactly 10 characters. The result is persisted and the sub-account’s aggregated KYC status is recomputed.
Authenticate as the parent main account with Authorization: Bearer {parent_jwt}.
Testing? Use the mock endpoint with magic inputs like TESTSUCCESS0001 instead of a real PAN.

Authorizations

​
Authorization
string
header
required

Parent main-account JWT. Sub-account KYC endpoints authenticate as the parent account that owns the sub-account (or an admin), not with the X-Auth-ID / X-Auth-Token header pair.

Path Parameters

​
sub_auth_id
string
required

The sub-account's Auth ID.

Example:

"SA_XXXXXX"

Body

application/json
​
pan
string
required
Required string length: 10
Example:

"ABCDE1234F"

Response

Verification result

Outcome of a single KYC verification step.

​
verification_type
enum<string>
required
Available options:
pan,
gst,
cin,
aadhaar
​
status
enum<string>
required
Available options:
verified,
failed,
pending
​
kyc_calls_blocked
boolean

Recomputed sub-account call-blocking state after this verification.

​
mock
boolean

Present and true on responses from the test-mode endpoints.