Skip to main content

​
Improvements

​
Session Timer Appears Only When the Session Is Nearly Over

The countdown timer now stays hidden until the session is genuinely at risk of expiring, instead of ticking down from the moment the user starts. Until now the timer began counting immediately after the session started — before document selection — so users watched a countdown for many minutes while there was no real time pressure. That added avoidable stress at the very point where people are most likely to abandon a verification. When the timer appears depends on the total session length, whether that comes from your dashboard settings or from sessionLength at token generation: If the threshold would fall in the first half of a very short session, the timer appears at the halfway point instead. In the last 30 seconds it switches to a distinct critical state, so the warning is unmistakable rather than just a smaller number. Where the timer appears has not changed, and neither has the setting that controls it: turning Show session timer off still hides it everywhere. This is rolling out as an A/B test across the web flow, so only a share of your users see the later timer — the rest keep the timer that counts down from the start. See Session Timer.

​
Landscape Orientation Support on Mobile

The verification flow now renders correctly in landscape, so it works whichever way the user is holding their phone. Document capture in particular benefits: a card or licence held in landscape fills far more of the frame, which means better source images and fewer retakes. Rotating the device mid-flow no longer disrupts the session — entered data and progress are preserved across the rotation, and there is no button to press, since the flow simply follows the device. The change applies across the end-user flows, including Proof of Address and Bank Card Verification. Nothing needs configuring. If your onboarding guidance still tells users to turn their phone a particular way for document capture, that advice can go — see Best Practices.

​
Back Navigation at Every Step

The Back button now stays available throughout the verification flow, including after a document photo has been taken. Previously it disappeared once the first photo was captured. A user who selected the wrong document type at the start — an ID card instead of a driving licence, say — then had no way back to the selection screen, and was left with a choice between completing a verification they knew was wrong and abandoning it entirely. Both outcomes cost you a conversion and, in the first case, a review. Returning to document selection and choosing a different type overwrites the photos captured earlier in that session, so there is no risk of mixing images from two document types. Steps where going back is deliberately not allowed behave exactly as before. See Document Selection and Back Navigation.

​
Deny Reason on the KYB Report PDF

A denied company’s PDF report now prints the deny reason directly, so there is no need to read the whole report to find out why the company was declined. The reason shown is one of the custom deny reasons configured for your account, or iDenfy’s default reason when you have not set any of your own. It appears on denied reports regardless of which sections you select when generating the file. Configure your own reasons under Settings → Business Verifications (KYB) → Operational settings, and see KYB PDF Generation for the report side.

​
Bank Card Verification Settings Moved

The Bank card verification and Bank card PDF upload settings have moved out of KYC → Configuration into their own block on the AML and fraud prevention page. Configuration had become the place these two ended up rather than the place they belonged, which made them hard to find. They now sit together under a Bank card verification heading alongside the other fraud prevention controls. Your existing values carried over with the move — nothing needs reconfiguring, and the settings are still requested through iDenfy rather than toggled directly. Find them at Settings → Know Your Customer → AML & Fraud Prevention.

​
API Key Terminology Matches the Documentation

In the dashboard under Settings → API Keys, Access key and Secret access key are now labelled API key and API secret. The documentation, integration guides and support conversations have always called them API key and API secret, so the old dashboard labels left developers matching up two sets of names for the same pair of credentials — with two similar-looking labels inviting a mix-up between them. This is a labelling change only. Your existing keys keep working, and API request and response field names are untouched. See API Keys and Authentication.