Update Merchant Application Status

Manually sets a merchant application's status to a specified value. This endpoint is used by ISO administrators and operations staff to manage the application workflow — for example, marking an application as conditionally approved, returning it to pending review, or flagging it for underwriting. An optional comment can be added to document the reason for the status change.

Endpoint

POST /api/v1/merchant/updateStatus

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 when a workflow event needs to be applied to a merchant application outside of the standard sequential status transitions. For example, an underwriter may set an application to ConditionallyApproved after reviewing all documents and confirming the merchant meets approval criteria pending minor outstanding items. This endpoint provides direct status control for operations users with appropriate permissions.

Request Body

{
  "id": 10482,
  "status": "ConditionallyApproved",
  "comment": "All documents verified and risk assessment passed. Pending final ID verification."
}

Response

200 OK

{
  "data": {
    "success": true
  },
  "status": "OK",
  "error": null,
  "warning": null,
  "validationResults": [],
  "requestId": 79340
}

Error Codes

Common Mistakes

• Sending a status value not in the allowed enum (ConditionallyApproved, PendingReview, Underwriting) causes a 400 error.
• Not all users have permission to set all status values — operations-only statuses may require elevated privileges.
• Omitting the comment when making an auditable status change makes it harder to trace the decision in the application history.
• This endpoint does not validate whether all required documents are uploaded — status can be set even if the application is incomplete, so verify completeness separately.

Related Endpoints

• POST /api/v1/merchant/underwritingPending — Dedicated endpoint for setting "UW Level 1: Pending" status.
• POST /api/v1/merchant/underwritingReview — Dedicated endpoint for advancing to "UW Level 1: Pending Review".
• GET /api/v1/merchant/status — Retrieve the current application status.

Example

curl -X POST https://hq.staging.netevia.dev/api/v1/merchant/updateStatus \
  -H "Authorization: Basic $(echo -n 'username:password' | base64)" \
  -H "Content-Type: application/json" \
  -d '{
    "id": 10482,
    "status": "ConditionallyApproved",
    "comment": "All documents verified and risk assessment passed. Pending final ID verification."
  }'