This method is called after the merchant's comments have been corrected. Set merchant underwriting status to Pending Review

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

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

FieldTypeRequiredDescription
idinteger (int32)YesMerchant profile ID to transition to Pending Review status
commentstringNoOptional 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.

FieldTypeDescription
idintegerMerchant profile ID from the request
commentstringComment 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

CodeWhen it happens
400id is missing or not a valid integer, or the merchant is not in a status that allows transitioning to PendingReview
401Invalid or missing Basic Auth credentials
403User does not have permission for this operation
404Merchant not found
500Internal 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 comment field 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, while setStatusInReview changes the status of a specific UW task ticket.

Related Endpoints

  • GET /api/v1/merchant/underwritingNotes — check what documents or corrections the UW team has requested
  • POST /api/v1/merchant/attachment — upload documents to the merchant record
  • GET /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."
  }'
Body Params
int32
string
Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
string
enum
Defaults to application/json

Generated from available request content types

Allowed:
Response

Language
Credentials
Basic
base64
:
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
text/json