Credit Application Statuses

Statuses a credit application can return while it is being validated and decisioned, and the responses your integration should expect for each. For statuses on a signed contract rather than an application, see Contract Statuses.

The two checks

An application passes through two checks, in order, and the status tells you which one it is sitting in.

Can a credit report be retrieved, and does it match the application? CREDIT_FREEZE and NO_HIT are failures of this step. Identity has not been assessed yet.
Does the identification match the applicant? PENDING with a pendingReason is a failure of this step.

Only the consumer can clear most of these. Your integration should surface the status to the consumer and let them resolve it in the application flow — not queue it for merchant action. See Resolving Pending Applications.

Status reference

Status	`pendingReason`	What it means	Who resolves it
`CREDIT_FREEZE`	—	A freeze at the bureau blocked the credit pull	Consumer only
`NO_HIT`	—	No credit report matched the application data	Consumer, by correcting the application
`NO_HIT` (second occurrence)	—	Still no match after the application was corrected	UAS, with the consumer
`PENDING`	`FRAUD`	A fraud indicator on the credit report	Consumer or UAS
`PENDING`	`IDENTITY_VERIFICATION`	The identification check returned a warning	Consumer or UAS
`PENDING`	`UNRESOLVED_DATA_MISMATCH`	Self-service resolution failed, or documentary ID is required	UAS only
`APPROVED`	—	Both checks cleared	—
`DECLINED`	—	A credit decision was made	—

Terminal statuses

Status	Reached when
`APPLICATION_EXPIRED`	30 days from the time of application without a valid credit report
`APPLICATION_VOID`	The application was voided before a credit report was retrieved
`PENDING_EXPIRED`	30 days from the time of application with the pend unresolved
`PENDING_VOID`	The pend was closed as unresolvable or incomplete

The 30-day clock runs from the time of application, not from when the status changed. An application that pends on day 25 has five days left, not thirty. Do not compute the deadline from the status transition.

An expired application may receive a Statement of Credit Denial, Termination, or Change (SCDTC). Expiry is not a decline — no credit decision was reached.

Example responses

Base URL shown is the test environment. See Testing for credentials and the sandbox.

Credit freeze

{
    "data": {
        "id": "76697079907c4f3dae32",
        "accountNumber": "2BBC85F",
        "status": "CREDIT_FREEZE",
        "edit": {
            "href": "https://test-api.uportal360.com/applications/76697079907c4f3dae32",
            "method": "PATCH"
        },
        "self": {
            "href": "https://test-api.uportal360.com/applications/76697079907c4f3dae32",
            "method": "GET"
        }
    }
}

No hit

{
    "data": {
        "id": "d56761e04407407caf21",
        "accountNumber": "WFB22A8",
        "status": "NO_HIT",
        "edit": {
            "href": "https://test-api.uportal360.com/applications/d56761e04407407caf21",
            "method": "PATCH"
        },
        "self": {
            "href": "https://test-api.uportal360.com/applications/d56761e04407407caf21",
            "method": "GET"
        }
    }
}

A PATCH with corrected applicant data re-runs the lookup. Supplying a full SSN, a previous last name or a previous address is what usually resolves it.

Identity verification

Returned on PATCH when identity verification is the pending reason.

{
    "data": {
        "id": "35d7c30ef9d548fea349",
        "accountNumber": "D4ACC4X",
        "status": "PENDING",
        "pendingReason": "IDENTITY_VERIFICATION",
        "edit": {
            "href": "https://test-api.uportal360.com/applications/35d7c30ef9d548fea349",
            "method": "PATCH"
        },
        "self": {
            "href": "https://test-api.uportal360.com/applications/35d7c30ef9d548fea349",
            "method": "GET"
        }
    }
}

Unresolved data mismatch

{
    "data": {
        "id": "45d7c30ef9d848fge389",
        "accountNumber": "D4ACC4Y",
        "status": "PENDING",
        "pendingReason": "UNRESOLVED_DATA_MISMATCH",
        "edit": {
            "href": "https://test-api.uportal360.com/applications/45d7c30ef9d848fge389",
            "method": "PATCH"
        },
        "self": {
            "href": "https://test-api.uportal360.com/applications/45d7c30ef9d848fge389",
            "method": "GET"
        }
    }
}

This one cannot be cleared through the API. The consumer must speak to UAS and supply documentary identification.

Handling these in your integration

Do not poll aggressively while an application is pending. The consumer is working through a resolution flow that can take minutes or days.
Do not treat a pend as a decline. Applications only pend if they otherwise meet the finance program’s criteria for approval.
Do not re-submit a new application to clear a pend. A duplicate creates its own problems and the original stays open for its full 30 days.
Surface the reason to the consumer, and link them to the resolution steps on the consumer FAQ.

Overview

Support

uPortal Guide

Support Tickets & Contract Changes

Finance Programs (PUR and SRV)

Frequently Asked Questions

Help & Contacts

Getting Started with UGA Finance

Account & User Setup

Credit Application Process

Managing Contracts

Servicing & Consumer Payments

Purchasing Program Approval

Support Tickets & Cases

Reports & Invoices

Integrations & API

The two checks

Status reference

Terminal statuses

Example responses

Credit freeze

No hit

Identity verification

Unresolved data mismatch

Handling these in your integration

​The two checks

​Status reference

​Terminal statuses

​Example responses

​Credit freeze

​No hit

​Identity verification

​Unresolved data mismatch

​Handling these in your integration

The two checks

Status reference

Terminal statuses

Example responses

Credit freeze

No hit

Identity verification

Unresolved data mismatch

Handling these in your integration