Credit-registry, AML and registry checks
Vincu Verify
Every check a case needs — credit registry, AML list, company registers — run with consent, attached to the file and logged.
Verify runs the checks a bank must make before it decides: the national credit registry, the bank's own AML acceptability list, company registers and account-status data. Consent is captured and verified before a registry is queried, results land on the case as structured data that feeds the decision rules, and every query is logged for the auditor.
- Every
- party on a case screened — applicant, co-debtors, related companies, authorised persons
- Four-eyes
- on every credit-registry query — consent checked, then approved by a second person
- Local
- consent verification — identifier and signature checked in-house, no AI, nothing leaves the bank
- Logged
- who asked, on which consent, what came back — per query
The problem it removes
The checks are scattered across portals, smart cards and spreadsheets.
The credit registry lives behind a smart card on one laptop. The AML list is a spreadsheet someone maintains. Company registers are a browser tab. Each check is done by hand, pasted into a file, and impossible to prove later.
Every check, run once, with consent — and provable later.
Vincu Verify
How it works
One place to run every check — and to prove it was run
Credit registry: queries run through a bridge inside the bank's network, so certificates and smart cards never leave it. The signed consent is uploaded first and checked automatically — identifier match, signature present — before a second person approves the query.
AML: every party on a case — applicant, co-debtors, related companies, authorised representatives — is screened against the bank's own acceptability list, automatically at intake and on demand. A listed party carrying a 'stop' instruction halts the case; a name-only match is flagged for review, never auto-declined.
Registers and account status: company identity, activity and authorised persons come from the official register; account blockades are checked at the central bank; public data enriches the picture.
Results become structured data on the case — exposures, arrears, classifications, blockades — and feed the decision rules directly, with the report's age enforced.
A standalone query desk for the registry team, with its own roles, audit log, reports and export in the registry's native format.
What the bank sees
- One place to run and prove every check
- Eliminatory findings surfaced before analysis starts
- An audit log per query — who asked, on what consent, what came back
- Compliance sees every screened party and every instruction, not a yes/no box
What the customer sees
- One consent, signed once, used for exactly what it says
- Fewer requests to 'send that again'
- A decision that isn't delayed by a check nobody ran