Skip to main content
Bank Card Verification confirms that a bank card used during onboarding actually belongs to the person completing identity verification. It can be added as an additional step inside the standard IDV flow, or run on its own as a standalone check.
Bank Card Verification also runs as a standalone check, on its own session token with no identity verification behind it and its own redirect handling. See Create a Bank Card Session for the API integration.This page covers the version that runs as an additional step inside the IDV flow.
Bank Card Verification runs in a dedicated environment certified to PCI-DSS v4.0.1. Card capture and card image processing are fully separated from the rest of the platform, and no card imagery is retained once processing completes. The end-user experience is unchanged.
Heads up: Bank Card Verification requires settings to be enabled on your account before it becomes available. Under Settings → Know Your Customer → Configuration, enable Bank Card Verification to turn the feature on, and Bank Card PDF Upload if you also want to allow users to submit a PDF instead of a live capture. Neither setting is self-service — contact iDenfy to request access.

Enabling As an Additional Verification Step

Through Dashboard

  1. Select ID Verifications section
  2. Select New Verification
  3. Select tab Advanced settings
  4. In the section Additional verification steps, find the option Bank Card Verification and enable it
  • Title: Bank Card Verification
  • Subtitle: Enable card ownership check as part of the verification flow. You can optionally enter the last 4 digits of the card to confirm a match.
  1. Optionally, provide the expected last 4 digits of the card number in the field that appears — this field is not required.

Standalone Bank Card Verification

Bank Card Verification can also run as its own flow, independently of an identity verification — 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 session token and applies your branding, language, privacy policy display and help channels from the bank card configuration. See Standalone Bank Card Verification for the consent and capture screens, the attempt and timer rules, and the results the end user sees.

How It Works

In both flows, the user is asked to photograph the front (and, if needed, back) of their bank card, or upload a supporting document. As an additional IDV step this happens after the main IDV steps; in the standalone flow it is the whole session.
  • Cardholder name matching — the name read from the card is compared against the user’s verified identity name. In a standalone session there is no IDV identity to compare against, so the check rests on the name and card number you supply.
  • Card number matching — if the partner provided expected last 4 digits, they’re compared against the card’s actual last 4 digits.
If Bank Card Verification runs as part of an active IDV session and returns No Match, the verification is marked Suspected for further review rather than automatically denied. If it runs after the IDV has already been Approved, the IDV status is updated to Suspected. A Bank Card No Match result never automatically denies a verification. Results appear alongside the identity verification in Verification Details, and a follow-up Bank Card Verification request can be triggered from the review screen using Request Update.