Check KYC Verification
Endpoints
Check KYC Verification
Check KYC verification status for a user account
GET
Check KYC Verification
Overview
Check the KYC (Know Your Customer) verification status for a user account. This endpoint returns whether the user is verified, their money transfer limit, and a verification URL if needed.KYC Provider
CashQ uses Veriff as our Attested KYC provider for identity verification.Custom Veriff IntegrationIf you are using your own Veriff account, we can integrate with your Veriff API key to maintain a unified verification experience.
Alternative KYC ProvidersIf you need to use another KYC provider, please contact support@mycashq.com to discuss integration options.
Endpoint
Path Parameters
User account ID (phone number in E.164 format without the
+ sign)Format: [country code][subscriber number including area code]Example: 16175551212 for a US numberAuthentication
Your CashQ API Key for authentication
Request Example
Response
KYC verification status
true: User is verifiedfalse: User is not verified or has limited verification
Maximum amount the user can receive in a single transfer (in dollars)
- If
"0": User cannot receive money transfers - Otherwise: Maximum transfer amount allowed
URL to redirect user for KYC verification
- Empty string (
"") if user is fully verified - Contains verification URL if user needs to complete KYC
Response Examples
Understanding KYC Status
Verified Users (kyc_verify: true)
- User has completed full KYC verification
- Can receive transfers up to their
money_limit - No additional verification needed
kyc_urlwill be empty
Unverified Users (kyc_verify: false)
- User has limited or no verification
- Can only receive transfers up to their
money_limit - Should be directed to
kyc_urlto complete verification - After verification, their
money_limitwill increase
Money Limit Interpretation
| money_limit | Meaning |
|---|---|
"0" | Cannot receive any transfers |
"600" | Can receive up to $600 per transfer |
"8990" | Can receive up to $8,990 per transfer |
Phone Number Formatting
Converting to E.164 Format
Error Responses
| Error Code | Description | Solution |
|---|---|---|
authentication_error | Invalid or missing API key | Verify your API key |
invalid_phone_number | Phone number format is incorrect | Use E.164 format without + |
account_not_found | Account doesn’t exist | Verify the phone number is correct |
internal_server_error | Server error occurred | Retry the request |
Best Practices
Always check before transfers
Always check before transfers
Check KYC status before initiating any transfer to avoid failures due to verification limits.
Cache KYC status appropriately
Cache KYC status appropriately
Cache KYC status for a reasonable time (e.g., 1 hour) but refresh before large transfers.
Provide clear user guidance
Provide clear user guidance
If a user needs verification, clearly explain why and provide the verification URL.
Validate phone numbers
Validate phone numbers
Validate and format phone numbers on your end before sending to the API.
Handle all limit scenarios
Handle all limit scenarios
Account for all cases: fully verified, partially verified, and unverified users.
Related Endpoints
Check Transfer
Validate transfer details including KYC requirements
Money Transfer
Execute a money transfer after KYC verification
