Get Auto UW Results

Returns the results of automated underwriting (autoUW) verification checks that the system has run against a merchant. Each result identifies a verification type and its outcome. Optionally, results can be filtered to return only checks that failed, making it easy to identify which areas require attention before manual review.

Endpoint

GET /api/v1/merchant/getAutoUwResults

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 after a merchant has been submitted to TSYS and the system has performed its automated pre-screening. The autoUW checks run automatically and cover areas such as MATCH list verification, OFAC screening, GIACT bank validation, Google search, WHOIS, and Clear background checks. Call this endpoint to review automated findings before escalating to a human underwriter, or to display compliance check results in an ISO dashboard.

Query Parameters

Response

200 OK

{
  "data": [
    {
      "verificationType": "AutomatedMATCH",
      "verificationResult": "Pass"
    },
    {
      "verificationType": "AutomatedOfac",
      "verificationResult": "Pass"
    },
    {
      "verificationType": "AutomatedGiact",
      "verificationResult": "Fail"
    },
    {
      "verificationType": "AutomatedGoogleSearch",
      "verificationResult": "Review"
    },
    {
      "verificationType": "AutomatedWhois",
      "verificationResult": "Pass"
    },
    {
      "verificationType": "AutomatedClear",
      "verificationResult": "Pass"
    }
  ],
  "requestId": 88621,
  "success": true,
  "error": null,
  "validationErrors": []
}

Error Codes

Common Mistakes

• Calling this endpoint before the merchant has been submitted — autoUW checks only run after submission, so results may be empty or unavailable for draft merchants.
• Misinterpreting a "Review" result as a failure — a "Review" result means the check flagged something that requires human inspection, not that the merchant is rejected.
• Forgetting the failedChecks=true filter when you only want to surface actionable problems in a UI.

Related Endpoints

• GET /api/v1/underwriting/statuses — get the current underwriting status for all merchants
• GET /api/v1/underwriting/status-history — get the full underwriting status history for a merchant
• POST /api/v1/underwriting/pending-review — notify the UW team after corrections have been made

Example

curl -X GET "https://hq.staging.netevia.dev/api/v1/merchant/getAutoUwResults?id=48201&failedChecks=true" \
  -H "Authorization: Basic $(echo -n 'username:password' | base64)"