Upload a bank statement PDF or image to detect fake-statement signals, validate visible IBANs, review inconsistencies, and get a structured KYC risk report. Login is required for file upload.
The file is saved server-side for a statement-only review job, retained for 24 hours after upload, and then pruned with its review artifacts. You can delete a completed review sooner through the review controls or API. A separate copy of each uploaded file is kept for fraud prevention for 12 months and is disclosed to law enforcement or other competent authorities only on a lawful request.
IBANs and supported domestic routing identifiers are checked independently from the AI review.
The agent returns parseable JSON for score, evidence, inconsistencies, and next steps.
Every completed review can be downloaded as structured JSON for case files, QA evidence, or API integration. Teams get predictable monthly capacity without turning a risk score into an automatic approval decision.
View multipart API and polling contractUse the validator when a customer uploads a statement during onboarding and your team needs a fast first-pass risk report before manual review or direct bank-source verification.
It reviews uploaded bank statement PDFs or images, extracts visible banking fields, validates detected IBANs or supported domestic routing identifiers, checks statement-like terminology, dates and amounts, and returns a structured risk score for KYC review.
Yes. IBANgen provides an authenticated multipart API endpoint for one bank statement file per request, with polling for the final structured risk report.
No. The result is a review aid for KYC and onboarding teams. High-risk or high-value workflows should still use manual review or direct bank-source verification.
Upload a statement to generate the report.
This is a preview without an account. Create a free account to see every finding, the extracted fields and the account checks: your first full check is free.