| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Set Merchant Underwriting Status to Pending Review
Transitions a merchant's underwriting status to PendingReview, signaling to the UW team that the ISO or merchant has corrected the items previously flagged and the application is ready to be re-examined. An optional comment can be included to explain what was updated. This is the standard handoff call after uploading new documents or making corrections in response to underwriter feedback.
Endpoint
POST /api/v1/underwriting/pending-review
Authentication
Basic HTTP Authentication required.
Encode username:password in Base64 and pass in the Authorization header:
Authorization: Basic {base64(username:password)}
When to use
Use this endpoint as the final step after an ISO has addressed all items requested by the underwriting team — for example, after uploading required documents via POST /api/v1/merchant/attachment or correcting application information. This call moves the merchant out of a stalled state (such as UnderwritingPending or RequestChanges) and back into the UW team's active review queue. Without this call, the UW team may not be aware that corrections have been made.
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
| id | integer (int32) | Yes | Merchant profile ID to transition to Pending Review status |
| comment | string | No | Optional note explaining what corrections or documents were submitted |
{
"id": 48201,
"comment": "Uploaded the requested driver's license and 3 months of business bank statements as requested in the UW notes."
}Response
200 OK
The response returns the same MerchantPendingReviewRequest object that was sent in the request body, serving as a confirmation echo.
| Field | Type | Description |
|---|---|---|
| id | integer | Merchant profile ID from the request |
| comment | string | Comment from the request |
{
"id": 48201,
"comment": "Uploaded the requested driver's license and 3 months of business bank statements as requested in the UW notes."
}Error Codes
| Code | When it happens |
|---|---|
| 400 | id is missing or not a valid integer, or the merchant is not in a status that allows transitioning to PendingReview |
| 401 | Invalid or missing Basic Auth credentials |
| 403 | User does not have permission for this operation |
| 404 | Merchant not found |
| 500 | Internal server error |
Common Mistakes
- Calling this endpoint before actually uploading the required documents — the UW team will find the same missing documents and flag the application again.
- Omitting the
commentfield when it could provide valuable context to the underwriter about what was changed and why. - Confusing this endpoint with
POST /api/v1/uwTasks/setStatusInReview— this endpoint changes the overall merchant underwriting status, whilesetStatusInReviewchanges the status of a specific UW task ticket.
Related Endpoints
GET /api/v1/merchant/underwritingNotes— check what documents or corrections the UW team has requestedPOST /api/v1/merchant/attachment— upload documents to the merchant recordGET /api/v1/underwriting/status-history— verify the status transition was recorded
Example
curl -X POST https://hq.staging.netevia.dev/api/v1/underwriting/pending-review \
-H "Authorization: Basic $(echo -n 'username:password' | base64)" \
-H "Content-Type: application/json" \
-d '{
"id": 48201,
"comment": "Uploaded the requested driver'\''s license and 3 months of business bank statements."
}'