User - Proof of Address (POA)

Overview

The Address Document Module enables structured and reliable Proof of Address (POA) verification as part of KYC. It replaces the legacy User Document Module – POA and provides stronger validation, configurable document rules, and support for multiple file types.

This module is recommended for all new integrations.

Module Availability & Defaults

New customers: Address Document Module is enabled by default
Existing customers: Enabled if using the Address Verification Template.

Supported Documents

AiPrise classifies each submitted POA document into one of the following categories:

Category	Description
`FINANCIAL_STATEMENT`	Bank statement, credit card statement, investment or brokerage statement
`UTILITY_BILL`	Electricity, gas, water, internet, phone, or other utility bill
`GOVERNMENT_LETTER`	Letter from a government authority, tax notice, benefit or council letter
`INSURANCE_DOCUMENT`	Insurance policy schedule, renewal notice, or coverage certificate
`TENANCY_AGREEMENT`	Rental or lease contract between landlord and tenant
`EMPLOYMENT_DOCUMENT`	Payslip, employer letter, or any employment-related document
`COMMERCIAL_INVOICE`	Supplier invoice for goods or services to a business
`NATIONAL_ID`	National identity card, passport, driving licence, or government-issued ID
`UNKNOWN`	Cannot be determined or does not fit any other category

Customers can configure which of these document types are allowed via the dashboard within Templates.

File Upload Rules

Rule	Value
Maximum documents per check	Up to 2
File formats	PDF and/or Images
Image formats	JPG, JPEG, PNG
File size limit	10 MB per file

SDK Behaviour (Onboarding Flow)

When using the onboarding SDK:

Users must select a document type before upload
Upload rules are dynamically applied based on the selected document
On-device quality checks detect:
- Blurry or unreadable documents
- Unsupported file formats
If the uploaded document does not match the selected document type, an error is shown
Users see clear guidance on allowed file types and remaining upload count

📘
Note: On-device checks and document-type mismatch validation apply only to SDK-based integrations, not API-only flows.

Response

When a POA document is processed, the response includes a poa_document_category field indicating the classified document type.

{
  "poa_document_category": "UTILITY_BILL"
}

The value is one of the categories listed in Supported Documents.

API Integration

Endpoint

POST /api/v1/verify/run_user_verification

Address Document Payload

When submitting POA via API, include the file_sub_type parameter to specify the document type.

{
  "additional_info": [
    {
      "additional_info_type": "ADDRESS_PROOF_DOCUMENT",
      "additional_info_data": [
        {
          "file": "base64_payload_string",
          "file_sub_type": "NATIONAL_ID_FRONT"
        }
      ] 
		}
  ]
}

Only the payload portion of the base64 string should be sent.

Validation & Enforcement

Validation rules are enforced at both:

SDK level (on-device checks)
Backend level (API validation)

This includes:

File type and size limits
Document count limits
Customer-configured document rules
Module exclusivity checks

📘
Recommendation
We strongly recommend switching to the Address Document Module in place of the legacy User Document Module to benefit from: Better document classification, Stronger validation, Improved user experience & Future enhancements
The module has already been enabled on your template. Please reach out if you need assistance with migration or configuration.