When to use
| Scenario | Example |
|---|---|
| Income verification | Borrower confirms retrieved income matches their actual earnings |
| Employment confirmation | Borrower validates employer name, start date, and pay rate |
| Asset verification | Borrower reviews account balances and ownership details |
| Dispute handling | Borrower flags incorrect or outdated data with a reason |
Retrieve certification results [Server-side]
Send aGET request to the order’s /certifications/ endpoint after the user completes their review.
Response structure
Each result contains adecision and either an employment or account object.
Decision values
| Decision | Meaning |
|---|---|
representative | Borrower confirmed the data is accurate |
not_representative | Borrower flagged the data as inaccurate |
Rejection reasons
When the decision isnot_representative, the result includes a rejection_reason:
| Reason | Description |
|---|---|
employment_no_longer_active | Borrower is no longer employed at this company |
incorrect_amount | Income or balance amount is wrong |
duplicate_entry | Employer or account appears more than once |
outdated_information | Data is stale or no longer current |
other | Borrower provided a custom explanation in rejection_comment |
Next steps
Follow-up
Re-engage users who didn’t finish verification
Embedded Orders
Full embedded orders implementation guide