> ## Documentation Index > Fetch the complete documentation index at: https://documentation.idenfy.com/llms.txt > Use this file to discover all available pages before exploring further. # Sprint 131 > Sprint 131 release notes: Bank Card Verification, KYB shared identity verification across companies, a new Blocklist API endpoint, and PNG logo uploads. ## What's New ### IDV: Bank Card Verification Partners can now verify that the bank card used during onboarding actually belongs to the person completing identity verification. Enable it as an additional IDV step under [New Verification → Advanced Settings → Additional Verification Steps](/guides/dashboard/features/bank-card-verification), optionally with the expected last 4 digits of the card for an extra match check. Reviewers get a new Bank Card Verification panel directly in [Verification Details](/guides/dashboard/kyc/verification-details), showing the match status, card data, and a link to the full check. The card's extracted cardholder name is compared against the verified identity, and — if provided — the card's last 4 digits are compared against the expected value. A mismatch marks the verification as suspected for review rather than an automatic denial. *** ### KYB: Shared Identity Verification Across Companies The same verified identity can now be linked to a person's role — Director, Representative, or Beneficial Owner — across multiple companies, so someone who sits on several company structures no longer needs to repeat identity verification each time. An existing `scanRef` can be supplied when [creating a company](/guides/dashboard/kyb/create-new-company), when [creating a KYB token](/kyb/generate-token), or added later to an existing Director, Beneficiary, or Representative from the [Company Details](/guides/dashboard/kyb/company-details-tab) page. There's no limit on how many companies can reuse the same `scanRef`, and the behavior is identical via the dashboard and the API — see [KYC Integration](/kyb/kyc-integration#reusing-an-identity-verification-across-companies) for details. *** ### Blocklist API Endpoint Partners can now block a user directly through the API, covering all three blocklist types — Face, Document Face, and Document Data. A block applied in your own CRM or internal system is reflected in iDenfy automatically, with no manual dashboard step required. See [Blocklist Setup](/guides/dashboard/risk/blocklist-setup) for how blocklisting works via the dashboard, and the [API Reference](/api-reference) tab for the new endpoint. *** ## Improvements ### KYB: Remembered Session Settings KYB session creation now supports **Remember session settings for next time** under [Session Validity](/guides/dashboard/kyb/creating-session), matching the behavior already available in the KYC IDV flow. Enable the checkbox once, and your chosen session validity is automatically applied to the next KYB session you create. *** ### KYB: Clearer Verification Prompts The identity verification step in the KYB flow now uses more generic wording for both the "Verify now" and "Verify later" prompts, no longer tied to a specific onboarding or application process. This makes the messaging fit any client's workflow, regardless of how their KYB process is structured. *** ### PNG Logo Uploads Partners can now upload PNG logos for branding, in addition to SVG. PNG uploads require a minimum of 200 × 200 px; SVG remains recommended for the sharpest results at any size. See [Branding (KYC)](/guides/dashboard/settings/kyc-branding) and [Branding (KYB)](/guides/dashboard/settings/kyb-branding) to update your logo. *** ### Clearer Camera Permission Prompts During identity verification, users now see a clear "Camera access required" message while the browser's camera permission decision is pending, instead of an indefinite loading spinner. If permission is blocked or denied, the existing "Camera required" guidance is still shown. ## Related topics - [Compliance](/guides/compliance/overview.md)