Rejection Reasons

Use this reference to interpret a rejection label Rain returns on a webhook, whether it’s temporary (fixable) or final (permanent), and to decide what to do about it. For every rejection reason grouped the way the Dashboard groups them, including the Reason and Reason ID behind each label, see the rejection catalog.

Webhook rejection label reference

The user.updated and company.updated webhooks include an applicationReason field containing one or more rejection labels that describe why an application was rejected. Parsing the field: applicationReason may contain multiple comma-separated labels (for example, "DUPLICATE, REGULATIONS_VIOLATIONS"). Split the string by comma, trim whitespace from each token (for example, token.trim() or equivalent), and discard any empty strings before looking up each label. The following table lists the labels Rain has seen in production that carry a recommended action, sorted alphabetically. Each one includes its category, whether the rejection is temporary (fixable) or final (permanent), and what to do about it. For labels not listed here, look up the reason group in the rejection catalog:

Label	Category	Severity	Description	Recommended action
`ADDITIONAL_DOCUMENT_REQUIRED`	Documentation	Temporary	Additional documents are required to complete verification.	Prompt the user to upload the requested documents.
`ADVERSE_MEDIA`	Compliance / AML	Final	The applicant is mentioned in adverse media.	No action. The application is permanently denied.
`BAD_FACE_MATCHING`	Selfie	Temporary	The selfie cannot be matched against the photo in the identity document.	Prompt the user to retake their selfie with better lighting and positioning.
`BAD_PROOF_OF_IDENTITY`	Identity document	Temporary	The identity document is unacceptable (for example, uploaded a copy, missing data, or unsupported type).	Prompt the user to re-upload a clear photo of a valid, original identity document.
`BAD_SELFIE`	Selfie	Temporary	The selfie failed quality or liveness checks.	Prompt the user to retake their selfie.
`COMPROMISED_PERSONS`	Compliance / AML	Final	The applicant was found on watchlists (for example, Interpol, FBI, EU most wanted).	No action. The application is permanently denied.
`DB_DATA_NOT_FOUND`	Database check	Temporary	The applicant’s data was not found in the government database.	Prompt the user to verify their personal details and resubmit.
`DOCUMENT_DAMAGED`	Identity document	Temporary	The identity document is damaged or unreadable.	Prompt the user to upload a photo of an undamaged document.
`DOCUMENT_PAGE_MISSING`	Identity document	Temporary	The uploaded document is missing required pages (for example, back side, address page).	Prompt the user to upload the missing pages.
`DUPLICATE`	Regulation	Final	The applicant already has an active account. Only one active account is allowed.	No action. The application is permanently denied.
`EXPIRATION_DATE`	Identity document	Temporary	The identity document has expired or expires within one month.	Prompt the user to upload a document with a valid expiration date.
`FRAUDULENT_PATTERNS`	Fraud	Final	Suspected fraud network activity or high-risk anomalies detected (for example, VPN usage, IP issues).	No action. The application is permanently denied.
`GRAPHIC_EDITOR`	Fraud	Temporary	Image editing software was detected on the submitted document.	Prompt the user to upload an unedited photo of the original document.
`PEP`	Compliance / AML	Final	The applicant is a politically exposed person.	No action. The application is permanently denied.
`PROBLEMATIC_APPLICANT_DATA`	Data mismatch	Temporary	The data on the applicant’s profile does not match the data on the submitted document (for example, name, date of birth, gender).	Prompt the user to correct their profile data or upload a matching document.
`REGULATIONS_VIOLATIONS`	Regulation	Final	The applicant violated regulatory requirements (for example, age, region, duplicate account).	No action. The application is permanently denied.
`SANCTIONS`	Compliance / AML	Final	The applicant was found on sanctions lists.	No action. The application is permanently denied.
`SELFIE_MISMATCH`	Fraud	Final	The selfie does not match the document photo.	No action. The application is permanently denied.
`SPAM`	Abuse	Final	The applicant uploaded an excessive number of files.	No action. The application is permanently denied.
`UNSATISFACTORY_PHOTOS`	Photo quality	Temporary	The document photos are unreadable or too low quality for verification.	Prompt the user to retake and re-upload clear, well-lit photos.
`WRONG_ADDRESS`	Data mismatch	Temporary	The address on the applicant’s profile does not match the document data.	Prompt the user to correct their address or upload a document with the correct address.
`WRONG_USER_REGION`	Regulation	Final	The applicant is from a region not supported by the program.	No action. The application is permanently denied.

The label ESIGN_FAILED has been observed in production but is not yet formally documented. If you encounter this label, contact Rain support for guidance. This section will be updated once the label definition is confirmed with the compliance team.

Understanding multi-label responses

Some rejections produce multiple labels because a single verification failure maps to more than one concern. When applicationReason contains multiple labels, treat the full set as the reason. Do not pick one and ignore the rest. The following table lists the most common multi-label combinations observed in production.

Labels	Meaning
`DUPLICATE, REGULATIONS_VIOLATIONS`	The applicant already has an active account, which is a regulatory violation.
`WRONG_USER_REGION, REGULATIONS_VIOLATIONS`	The applicant is from an unsupported region.
`COMPROMISED_PERSONS, PEP`	The applicant is both on watchlists and a politically exposed person.
`COMPROMISED_PERSONS, SANCTIONS`	The applicant is on both watchlists and sanctions lists.
`GRAPHIC_EDITOR, UNSATISFACTORY_PHOTOS`	Image editing software was detected in the submitted photos.
`BAD_PROOF_OF_IDENTITY, BAD_FACE_MATCHING, BAD_SELFIE`	Multiple identity verification failures across documents and selfie.

One severity per response: multi-label responses always share the same severity. You will not receive a mix of temporary and final labels in a single applicationReason string.

Temporary vs. final rejections

Rejection labels fall into two categories:

Temporary: the issue is fixable. A label with this severity moves the applicationStatus to needsInformation, and the user can correct the problem and resubmit. Redirect them to the applicationCompletionLink, or resubmit the corrected information through the update endpoints. See Application states for both approaches.
Final: the rejection is permanent. The user cannot reapply. The applicationStatus will be denied. See the rejection catalog for the full breakdown by group.

needsVerification is not a rejection outcome. It means the applicant has not submitted any documents yet, so no applicationReason label applies. See Application states for what triggers it and why the API resubmission approach for needsInformation does not apply there.

Do not prompt the user to resubmit documents when you receive a final rejection label. Final rejections are permanent and cannot be overturned through resubmission.

What’s next

Application states

How rejections map to application states.

Rejection catalog

Every rejection reason by group, temporary and final.

Troubleshoot verification

Fix common verification issues.

Introduction

Understand Compliance

Collect & Submit

Track a Decision

Reference

Payments

Rejection Reasons

Webhook rejection label reference

Understanding multi-label responses

Temporary vs. final rejections

What’s next

Application states

Rejection catalog

Troubleshoot verification

​Webhook rejection label reference

​Understanding multi-label responses

​Temporary vs. final rejections

​What’s next

Application states

Rejection catalog

Troubleshoot verification

Webhook rejection label reference

Understanding multi-label responses

Temporary vs. final rejections

What’s next