Skip to main content

​
What’s New

​
Standalone Bank Card Verification

Bank Card Verification can now run as its own flow, independently of an identity verification. This is useful when the user has already been verified, or when only card ownership needs confirming. A standalone session is initialized from its own bank card token and applies your branding, language, privacy policy display, and help channels from the bank card configuration. The flow covers a Verify your bank card consent screen, desktop-to-mobile handoff by QR code or SMS link, a choice between camera capture and document upload, a Which card are you verifying? screen when multiple cards are detected and no expected last 4 digits were supplied, and success, retry, and denial result screens. Enable it by contacting iDenfy; the existing Bank Card PDF Upload setting under Settings → Know Your Customer → Configuration controls whether the standalone flow offers document upload. See Standalone Bank Card Verification for the full flow.

​
Bank Card Verification Runs in a PCI-DSS Compliant Environment

Card capture and card image processing have been fully separated into a dedicated environment certified to PCI-DSS v4.0.1, and no card imagery is retained once processing completes. The end-user experience is unchanged — this is an infrastructure and compliance change. PCI-DSS v4.0.1 is now listed alongside our other certifications in the Compliance Overview.

​
Persian (Farsi) Language Support

End users can now complete the full identity verification process in Persian (Farsi), with correct right-to-left layout, characters, and numerals at every step. This opens the flow to Persian-speaking users in Iran, Afghanistan, and Tajikistan. Persian uses the same RTL behavior already in place for Arabic, so no configuration changes are needed. To use it, pass "locale": "FA" in your token generation request, or let the user pick Farsi / فارسی from the language switcher. See Supported Languages for the full locale code reference.

​
Improvements

​
Ownership Chains Can End at a Company with No Further Shareholders

Clients can now declare that a company shareholder has no shareholders of its own, and submit the ownership structure without tracing that branch further down to individuals. Previously, Full ownership list required every company in the chain to have at least one individual behind it. That left no correct way to finish a structure where a company genuinely has no further owners — a state-owned institution being the common case, but not the only one. A declared company now terminates the chain in the same way a natural person does. The option is off by default. Turn on Companies without further shareholders in the workflow’s Ownership Structure step — it appears only when Full ownership list is selected. Clients must confirm the declaration before continuing. See Stakeholder Roles for how this affects submission validation.

​
Fewer False Name Mismatches on AAMVA Checks

Name suffixes are now normalized before an AAMVA check runs, so verifications are no longer flagged as Suspected — and sent to manual review — over a suffix that never represented a real mismatch. JR, SR, II, III, and IV are removed from the first and last name in any capitalization or format (JR, Jr, Jr.) before the request is sent, because DMV records often normalize or omit them. A suffix is only removed when it stands alone as the final element of a name, so names that merely contain those letter sequences are untouched. Mismatches for any other reason behave exactly as before. See USA Driver’s License Check (AAMVA).

​
Separate Color Setting for Primary Buttons

Primary action buttons can now be given their own color, independently of the primary color used for other clickable elements. Until now, changing the button color meant changing Primary brand color, which also recolored links, selections, and step indicators throughout the flow. The new optional Primary button color field sits under Other UI colors and applies only to primary buttons such as Continue and Save. Left unset, primary buttons keep using the primary color, so existing themes are unaffected. It’s available for both KYC and KYB — see Branding (KYC) and Branding (KYB).

​
Automatic Photo Capture on the Selfie Step

The selfie step can now take the photo automatically once the face is correctly positioned and held steady, removing a manual tap and reducing motion blur. When the face is framed correctly the outline turns green and the user is asked to hold still; keeping the position steady for a moment captures the photo and moves straight into analysis. Moving away resets the progress until the framing is right again. This is rolling out as an A/B test across the web flow, so only a share of your users see it — the rest keep the existing capture button. Sessions where users can upload an image at the capture step are excluded, as are mobile SDK sessions. See Face Capture Guidance.

​
Audit Trail for Unchanged Information Requests

When a client opens a KYB request-update link and submits the form without changing anything, that submission is now recorded in the audit log as Form re-submitted without changes. Previously an unchanged submission left no trace, so there was no way to tell a review-and-resubmit apart from a client who never opened the link. Submissions that do change at least one field continue to be logged as before. The entry appears in the case’s audit log — see Compliance Monitoring Tab and Request Update (KYB).

​
Age Estimation: Minimal Data When a Document Step-Up Runs

When Save selfie photo is off and an age estimation session escalates to a document check, the document is now used only to establish the age. No selfie, document image, or personal data is stored. The session detail shows an ID verification block with the check method, its result, and when it ran, so you can still prove the check happened — but it doesn’t link through to a verification review, and the session stays out of the identity verification review list and is never sent to manual review. Where the age came from the document rather than the AI estimate, the Estimated age row is no longer shown. Sessions with photo saving enabled are unaffected. See Age Estimation Dashboard.

​
Hardened Session Security

All active sessions are now fully terminated on sign-out and after a password reset, alongside stricter validation of partner data access. Both access and refresh tokens are revoked, so signing out or changing a password requires signing in again on every device and browser tab. See Personal Details.

​
Daily Usage Overview Report No Longer Assumes EUR

The Daily usage overview report no longer prints a fixed EUR label next to the Total balance and Used balance values. The label was shown to every partner regardless of their settlement currency, which was misleading for those who don’t settle in euros. All other fields in the report are unchanged.