Skip to main content
Each decision component produces outcomes that fall into two categories:

​
Automated results

Results from automated verification checks, represented by DecisionComponentOutcome:
ScenarioBen’s application includes himself as owner and a business partner as a stakeholder. The identity verification component runs on both. Ben’s result is “VERIFIED” (status outcome). For the business partner, the component detects a name mismatch and produces a “REVIEW_REQUIRED” status, flagging it for manual review.

​
Manual review items

Items that require human review, represented by DecisionComponentReview:
  • Review description – Explains what needs manual evaluation
  • Review status – Whether the review is pending, in progress, or complete
  • Review fields – Specific data points that need human verification
When a decision component produces review items, the application typically transitions to the Pending status for manual underwriting.

​
Example: Identity verification outcomes

This example shows decision component outcomes for an identity verification check that passed for one stakeholder but requires review for another.
Response
{
  "decisionComponents": [
    {
      "id": "a7b8c9d0-e1f2-4a3b-4c5d-6e7f80910213",
      "status": "ACCEPTED",
      "items": [
        {
          "id": "b8c9d0e1-f2a3-4b4c-5d6e-7f8091021324",
          "label": "Owner - John Doe",
          "stakeholderId": "d4e5f6a7-b8c9-4d0e-1f2a-3b4c5d6e7f80",
          "status": "ACCEPTED",
          "outcomes": {
            "results": [
              {
                "status": "VERIFIED",
                "statusMessage": "Identity successfully verified",
                "label": "Identity Verification"
              }
            ],
            "reviews": []
          }
        },
        {
          "id": "c9d0e1f2-a3b4-4c5d-6e7f-809102132435",
          "label": "Owner - Jane Smith",
          "stakeholderId": "e5f6a7b8-c9d0-4e1f-2a3b-4c5d6e7f8091",
          "status": "REVIEW_REQUIRED",
          "outcomes": {
            "results": [
              {
                "status": "REVIEW_REQUIRED",
                "statusMessage": "Name mismatch detected",
                "label": "Identity Verification"
              }
            ],
            "reviews": [
              {
                "label": "Verify stakeholder name matches government ID",
                "fields": [
                  {
                    "name": "firstName",
                    "value": "Jane",
                    "status": "MISMATCH"
                  }
                ]
              }
            ]
          }
        }
      ]
    }
  ]
}

​
Interpreting decision component results

When reviewing decision component outcomes:
  1. Check overall status – Determine if the component completed successfully
  2. Review automated results – Examine status and assessment outcomes
  3. Identify manual reviews – Look for items flagged for human review
  4. Understand blockers – Identify which components are preventing automatic approval
If any decision component produces review items, the application typically requires manual underwriting before a final decision can be reached.
Applications with decision components that require manual review will transition to Pending status. Monitor these applications using webhooks to receive notifications when review is complete.

​
Decision components and application status

The relationship between decision components and application status:
  • Created/Submitted → Decision components are pending
  • Processing → Decision components are running
  • Pending → One or more components require manual review
  • Decisioned → All components are complete, decision made
Understanding this relationship helps you communicate application status to merchants and anticipate when applications will require additional attention.