Skip to main content
POST
/
v2
/
partner
/
card
/
users
/
{serviceId}
/
retry-kyc
curl -X POST https://services-staging.getplu.com/api/v2/partner/card/users/acme-user-abc123/retry-kyc \
  -H "Authorization: Bearer sk_staging_your_api_key" \
  -H "Content-Type: application/json"

{
  "status": "success",
  "message": "KYC retry initiated successfully",
  "data": {
    "serviceId": "acme-user-abc123",
    "applicationStatus": "pending",
    "retryCount": 1
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.getplu.com/llms.txt

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

Retries KYC for a user in a denied state. The system automatically detects the correct retry path:
  • Persona KYC failed — Creates a new Persona inquiry and returns a new verificationUrl
  • Persona passed, KYC denied — Re-submits stored identity documents without requiring the user to redo Persona verification
Each user can be retried up to 3 times. After that, contact support.
​
Authorization
string
required
Bearer token. Example: Bearer sk_staging_your_api_key
​
serviceId
string
required
The serviceId of the user to retry KYC for.
curl -X POST https://services-staging.getplu.com/api/v2/partner/card/users/acme-user-abc123/retry-kyc \
  -H "Authorization: Bearer sk_staging_your_api_key" \
  -H "Content-Type: application/json"

{
  "status": "success",
  "message": "KYC retry initiated successfully",
  "data": {
    "serviceId": "acme-user-abc123",
    "applicationStatus": "pending",
    "retryCount": 1
  }
}

​
Response Fields

The response varies based on the retry path:
FieldTypeDescription
serviceIdstringThe user’s service ID
applicationStatusstringKYC application status (automated retries)
verificationUrlstringPersona verification URL (returned when Persona KYC needs to be redone)
retryCountnumberTotal number of retries attempted for this user

​
After Retry

  • If verificationUrl is returned: Redirect the user to complete Persona KYC again
  • If applicationStatus is returned: The retry is fully automated — listen for KYC webhook events for the outcome
  • In both cases, you’ll receive the same webhook events as the original user creation flow