Callback Update: Image Delivery via S3 URLs

Last updated: February 9, 2026

What’s changing?

User verification completion callbacks will now include S3 URLs for images instead of embedding large base64-encoded payloads. This change reduces callback size, improves processing speed, and makes downstream integrations more reliable.

What’s the transition plan?

  • Now through ~2 months from release:
    Callbacks will include both S3 URL fields and base64 image fields (as a fallback).

  • Effective April 1:
    Base64 image attributes will be fully removed. Consumers must use the S3 URLs exclusively.

Which images are impacted?

The following images will be delivered via S3 URLs:

Previous Field (Base64)

New Field (S3 URL)

user_photo

user_photo_s3_url

user_signature

user_signature_s3_url

signature

signature_s3_url

document

document_s3_url

issue_signature

issue_signature_s3_url

probationary_document

probationary_document_s3_url

What do the S3 URLs contain?

Each S3 URL points to the corresponding image asset (for example, user photo or ID document image) stored securely and ready for retrieval by your system.

What action is required?

Please ensure your systems:

  • Read and process the new *_s3_url fields

  • Do not rely on base64 fields beyond April 1

  • Handle S3 URL access as part of your verification ingestion flow

If you have questions or want help validating your integration, tag AiPrise support on slack or reach out to us at support@aiprise.com