> ## 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.

# Bank Card Verification

> Configure bank card ownership verification as an additional step in your iDenfy KYC workflow, confirming the card used during onboarding belongs to the verified user.

Bank Card Verification confirms that a bank card used during onboarding actually belongs to the person completing identity verification. It's added as an additional step inside the standard IDV flow.

<Note>
  Bank Card Verification is currently only available as an additional step within the IDV flow. Standalone Bank Card Verification (independent of an IDV session) is not yet supported.
</Note>

<Warning>
  **Heads up:** Bank Card Verification requires settings to be enabled on your account before it becomes available. Under [Settings → Know Your Customer → Configuration](/guides/dashboard/settings/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](https://idenfy-ivs.atlassian.net/servicedesk/customer/portal/1) to request access.
</Warning>

## 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.*

5. Optionally, provide the expected **last 4 digits** of the card number in the field that appears — this field is not required.

***

## How It Works

Once enabled, the user is asked to photograph the front (and, if needed, back) of their bank card, or upload a supporting document, after completing the main IDV steps.

* **Cardholder name matching** — the name read from the card is compared against the user's verified identity name.
* **Card number matching** — if the partner provided expected last 4 digits, they're compared against the card's actual last 4 digits.

| Name extracted?          | Expected last 4 provided?  | Verdict                              |
| ------------------------ | -------------------------- | ------------------------------------ |
| Yes, name matches        | No                         | Match                                |
| Yes, name matches        | Yes, last 4 matches        | Match                                |
| Yes, name matches        | Yes, last 4 does not match | No Match (card number mismatch)      |
| Yes, name does not match | Either                     | No Match (name mismatch)             |
| No (name not detected)   | Either                     | No Match (cardholder name not found) |

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](/guides/dashboard/kyc/verification-details), and a follow-up Bank Card Verification request can be triggered from the review screen using [Request Update](/guides/dashboard/general/request-update).


## Related topics

- [Verification Details](/guides/dashboard/kyc/verification-details.md)
- [Android SDK Additional Features](/sdks/android/additional-features.md)
- [iOS SDK Additional Features](/sdks/ios/additional-features.md)
- [Configuration](/guides/dashboard/settings/configuration.md)
- [Request Update in the Dashboard](/guides/dashboard/general/request-update.md)