Skip to content
Amani logo

Address & residency proof

Verify where your customers actually live.

Proof of address arrives as blurry photos and unreadable PDFs in a hundred formats. Amani classifies the document, extracts name and address, matches them to the verified identity, and enforces your recency rules - automatically.

The challenge

Manual proof-of-address review is slow, inconsistent and easy to fool with edited PDFs. Yet regulators and residency schemes require documented, defensible evidence for every customer.

With Amani

  • Utility bills, statements and tenancy contracts handled automatically
  • Name and address matched against the verified identity
  • Document-age limits enforced from the document date
  • Edited and composited files flagged before acceptance
  • Normalised address data ready for your CRM

The stack

Modules powering this flow.

Switch these on in Amani Studio - or call them directly from one API.

For developers

Build this flow.

Three API calls start the session; the modules above run inside it. Compose the journey in Amani Studio without code, or let your AI coding agent wire up the SDK from a single prompt.

  • JWT auth with refresh tokens
  • Regional base URLs (EU · TR · UAE)
  • HMAC-signed webhooks with retries
  • 27 languages in the SDKs

verify.sh

# 1 · Authenticate (server-side only)
curl -X POST 'https://ae.amani.ai/api/v2/user/login/' \
  --form 'username="you@company.com"' \
  --form 'password="••••••••"'

# 2 · Create the customer profile
curl -X POST 'https://ae.amani.ai/api/v2/profile' \
  -H 'Authorization: Bearer $ACCESS_TOKEN' \
  --form 'id_card_number="784199012345678"' \
  --form 'name="Layla Haddad"'

# 3 · Generate the verification URL
curl -X POST 'https://ae.amani.ai/api/v2/profile/url' \
  -H 'Authorization: Bearer $ACCESS_TOKEN' \
  -H 'Content-Type: application/json' \
  --data '{
    "profile": PROFILE_ID,
    "web_sdk_url": "https://verify.amani.ai",
    "language": "en",
    "return_url": "https://yourapp.com/verified"
  }'

# This session runs: Address Verification, KYC, Database Validation.

Address & residency proof - common questions

Which documents are accepted?

You configure the accepted list per journey - typically utility bills, bank statements and government correspondence within your recency window.

How are non-English documents handled?

OCR and matching support Arabic, Turkish and other major scripts, with transliteration-aware name comparison.

Can we skip documents entirely?

In supported markets, Database Validation can confirm address data from authoritative sources without a document.

Related use cases

Build this flow with Amani

Compose it in Studio without code, or integrate the API in an afternoon.