Getting Started

This page will help you get started with Asset Verification via the Snappt Enterprise API

Asset Verification

Enabling Asset Verification

To start using the Asset Verification flow with your Snappt properties, you must activate the following:

Create an Asset Verification Session

In order to create an Asset Verification session, you follow the same steps in the Getting Started for Fraud Detection. Once a property has Asset Verification active, then any Document Types that meet the criteria for Bank Statements with a Personal Checking or Personal Savings account will be processed after application submission.

This classification criteria will be determined by Snappt's AI-powered Document Classification agent.

Checking for the Report Ready Status

The steps for obtaining a REPORT_READY webhook are the same as they are for Fraud Detection. Once your documents have been reviewed for both Fraud, Income and Assets, then your report will be ready and the webhook will be delivered.

Obtaining a Report

In order to obtain your PDF report for Asset Verification, you will use the same GET /applicants/{applicantId}/report endpoint as you would for a Fraud Detection report.

If Asset Verification is active for a property or an asset calculation has been made for an applicant in the past, you will be able to view the Applicant's Asset Verification report if the documents have met the above criteria.

How To Fetch Available Asset Calculations

Once an Asset Verification report has been created, an applicant's assets can be viewed using the GET /applicants/{applicantId} endpoint. If an Asset calculation for an applicant is available, an assetVerificationDetails object will be added at the root level of the response body.

{
  "id": "7d54e8a7-ade7-41bb-afef-0ea0254586b7",
  "fullName": "Test User",
  "firstName": "Test",
  "middleInitial": null,
  "lastName": "User",
  "email": "[email protected]",
  "phone": null,
  "notification": false,
  "entryId": "2a1956f5-b319-4f95-a56f-c7af31f5bb40",
  "insertedAt": "2024-06-13T02:56:50.000Z",
  "updatedAt": "2024-06-13T02:56:50.000Z",
  "status": "READY",
  "result": "CLEAN",
  "applicantDetailId": "ae99c8a2-6ecf-4339-8872-fb9ff68ab9e7",
  "documents": [
    {
      "id": "3d22f8df-676f-4245-bc1c-075acd591f9f",
      "insertedAt": "2024-06-13T02:56:50.000Z",
      "type": "PAYSTUB",
      "result": "CLEAN",
      "incomeVerificationDetails": {
        "calculationStartDate": "2024-06-12T00:00:00.000Z",
        "calculationEndDate": "2024-07-19T00:00:00.000Z",
        "grossIncome": 1000,
        "incomeSource": "Snappt",
        "applicantName": "Test User"
      },
      "assetVerificationDetails": null
    },
    {
      "id": "3d22f8df-676f-4245-bc1c-075acd591f9f",
      "insertedAt": "2024-06-13T02:56:50.000Z",
      "type": "BANK_STATEMENT",
      "result": "CLEAN",

      "incomeVerificationDetails": null
    }
  ],
  "incomeVerificationDetails": {
    "calculationDate": "2024-06-13T03: 01: 44.972Z",
    "grossDailyIncome": 26.32,
    "grossMonthlyIncome": 789.47,
    "grossYearlyIncome": 9605.26,
    "consecutiveDays": 38,
    "status": "ok",
    "statusDetails": []
  },
  "assetVerificationDetails": {
    "calculationDate": "2025-02-13T03:01:44.972Z",
    "totalVerifiedAssets": 14500.75,
    "accounts": [
      {
        "accountId": "4322f8df-676f-4245-bc1c-975acd591f93",
        "accountType": "PERSONAL_CHECKING",
        "accountHolderName": "John Smith",
        "verifiedAssets": 1500.25,
        "institutionName": "Wells Fargo",
        "statements": [
          {
            "documentId": "3d22f8df-676f-4245-bc1c-075acd591f9f",
            "startDate": "2024-05-01T00:00:00Z",
            "endDate": "2024-05-31T00:00:00Z",
            "endBalance": 1000.00
          },
          {
            "documentId": "3d22f8df-676f-4245-bc1c-075acd591f9e",
            "startDate": "2024-04-01T00:00:00Z",
            "endDate": "2024-04-30T00:00:00Z",
            "endBalance": 2000.50
          }
        ]
      },
      {
        "accountId": "5332f8df-676f-4245-bc1c-975acd591f93",
        "accountType": "PERSONAL_SAVINGS",
        "accountHolderName": "John Smith",
        "verifiedAssets": 12000.50,
        "institutionName": "Wells Fargo",
        "statements": [
          {
            "documentId": "3d22f8df-676f-4245-bc1c-075acd591f9f",
            "startDate": "2024-05-01T00:00:00Z",
            "endDate": "2024-05-31T00:00:00Z",
            "endBalance": 12000.50
          }
        ]
      },
      {
        "accountId": "6332f8df-676f-4245-bc1c-975acd591f32",
        "accountType": "PERSONAL_CHECKING",
        "accountHolderName": "John Smith",
        "verifiedAssets": 1000.00,
        "institutionName": "Bank of America",
        "statements": [
          {
            "documentId": "3d22f8df-676f-4245-bc1c-075acd59145f",
            "startDate": "2024-05-01T00:00:00Z",
            "endDate": "2024-05-31T00:00:00Z",
            "endBalance": 1000.00
          }
        ]
      }
    ],
    "status": "ok",
    "statusDetails": []
  }
}

Asset Verification Status Codes

Asset Verification codes appear in the statusDetails array on assetVerificationDetails, and are grouped by their leading digit:

  • 2xxx - Warnings. A verified asset figure is still shown on the report.
  • 3xxx - Errors. No asset figure can be provided.
  • 4xxx - Override / audit markers. A reviewer adjusted the verification.

Asset Verification Warning Codes with Report Verbiage

  • 2003 - Account holder name may not match across documents.
    • The account holder name may not match across all uploaded documents.
  • 2020 - Ending balance is missing from one or more documents.
    • The Ending Balance is missing from one or more uploaded documents.
  • 2021 - Statement start and/or end date is missing from one or more documents.
    • The statement start and/or end date are missing from one or more uploaded documents.
  • 2022 - Banking institution is missing from one or more documents.
    • The Banking Institution is missing from one or more uploaded documents.
  • 2023 - One or more statements are older than 90 days; other statements are still reviewable.
    • One or more of the uploaded statements are older than 90 days; other statements are still viewable.
  • 2024 - Duplicate statement was submitted.
    • A duplicate document was submitted.
  • 2025 - One or more statements are not from a personal account.
    • One or more of the uploaded statements do not represent a personal account.

Asset Verification Error Codes with Report Verbiage

  • 3020 - Ending balance is missing from all documents.
    • The Ending Balance is missing from all uploaded documents.
  • 3021 - Account holder name is missing from one or more documents.
    • The account Holder Name is missing from one or more uploaded documents.
  • 3022 - Account holder name does not match across all documents.
    • The account Holder Name does not match across all uploaded documents.
  • 3024 - All statements are older than 90 days.
    • The uploaded statements do not represent the past 90 days.
  • 3025 - Statement start and/or end date is missing from all documents.
    • The statement start and/or end date are missing from all uploaded documents.
  • 3026 - All statements are from non-personal accounts.
    • The statements uploaded do not represent personal accounts.
  • 3027 - All statements are from account types not eligible for asset evaluation.
    • The statements uploaded are from account types that are not eligible for asset evaluation.

How Warnings Become Errors

A warning is reported when some statements are still usable for the asset calculation. When no usable statements remain, the same condition is reported as its matching error code instead, because no asset figure can be produced.

WarningReported as this error when no statements remain
2020 Ending balance missing3020 Ending balance missing from all documents
2021 Start date missing3025 Start date missing from all documents
2023 Older than 90 days3024 All statements older than 90 days
2025 Non-personal account3026 All statements from non-personal accounts

Account holder name codes work differently. A missing or mismatched name is reported as either the warning (2003) or the corresponding error (3021 for a missing name, 3022 for a mismatch), depending on how name matching is configured for the property.

Override / Audit Codes (4xxx)

The 4000-series codes are override / audit markers. They appear in statusDetails when an asset verification has been manually adjusted by a reviewer.

Unlike the 2xxx and 3xxx ranges, 4xxx codes are never treated as errors. They accompany a status of "ok" or "warning", and totalVerifiedAssets is populated and usable. Treat them as informational context about why a verification was adjusted, not as a reason to withhold the figure.

Override / Audit Codes with Report Verbiage

  • 4001 - Additional asset sources were provided during review.
  • 4002 - Non-recurring income was included in the calculation.
  • 4003 - An offer letter was provided and accepted.
  • 4004 - The calculated figure was manually corrected.
    • Codes 4001-4004 share a single message on the report:
      "The asset calculation was updated using data from the applicant's uploaded documents or connected accounts."
    • The report presents this as an update notice rather than a warning.

Additional Report Messages

These messages reflect the state of the submission rather than a specific status code, so they appear on the report without an accompanying code.

  • One or more documents did not pass fraud detection.
    • We cannot verify the applicant's assets, because one or more documents failed during the fraud detection review.
  • Asset verification review is still in progress.
    • We're unable to verify the applicant's assets at this time because the submitted documents are still pending final asset verification review.
  • No asset figure is available.
    • We are unable to provide an asset figure based on the documents provided.

Which Message Appears on the Report

A submission can carry more than one status code, but the report summary displays only one message: the highest-priority error, or the highest-priority warning if no error is present.

  • Error priority: 3027 → 3026 → 3022 → 3021 → 3024 → 3025 → 3020
  • Warning priority: 2025 → 2024 → 2020 → 2021 → 2022 → 2023 → 4001 → 4002 → 4003 → 4004 → 2003

All codes for the submission are still returned in statusDetails, so integrations can read the complete set rather than only the displayed message.

Document-Level Labels

When a code applies to a single statement, the PDF report shows a short label on that document's row instead of a full sentence.

Code(s)Label
3022Name Mismatch
3021Missing Name
2022Missing Bank Name
2021, 3025Missing Dates
2023, 302490+ Days Old
2020, 3020Missing Balance
2025, 3026Non-personal Account

Codes not listed above (2003, 2024, 3027, and 4001-4004) do not display a document-level label.

📘

These per-statement labels appear only on the PDF report. The statements objects returned by GET /applicants/{applicantId} do not include status codes — use the statusDetails array on assetVerificationDetails to read codes programmatically.


Did this page help you?