# Multi-Technology Credentials Overview

Multi-Technology credentials let you use a single card with both Verkada’s secure MIFARE DESFire EV3 chip and a legacy 125 kHz proximity (Prox) antenna. This allows users to access Verkada readers with secure EV3 authentication while maintaining compatibility with on-site systems that still rely on Prox.

{% hint style="danger" %}
You need at least **Access Credential Manager** permissions to manage credentials.
{% endhint %}

### Before you begin

* A Verkada Access Control deployment with EV3-capable readers
* Familiarity with the legacy onsite systems at your site that read 125 kHz Prox

{% hint style="warning" %}
Multi-Technology credentials use the same encryption as standard Verkada EV3 cards. No firmware updates or custom reader configuration are required to start issuing them.
{% endhint %}

***

## Multi-Technology credentials

Multi-Technology credentials help bridge secure and legacy systems using a single badge. Common use cases include:

### Migrating from a legacy access control system

Organizations transitioning from a legacy access control system that uses 125 kHz Prox cards can issue a single Multi-Technology credential during the migration period. Cardholders can use the same badge at upgraded Verkada doors, which authenticate the secure EV3 credential, and at doors that still use legacy Prox readers until the migration is complete.

### Integrating with non-access ancillary systems

Many organizations operate ancillary systems such as parking gates, secure print release systems, vending machines, cafeteria point-of-sale systems, and time clocks that still rely on 125 kHz Prox. Multi-Technology credentials allow organizations to adopt Verkada’s EV3 standard for door access without replacing these existing systems.

For maximum security at the door, you can disable the 125 kHz Prox antenna on 4th-generation Verkada readers (AD34, AD64, AL54, and AF64) and Verkada Intercoms with built-in readers so they only accept the secure EV3 credential.

{% hint style="info" %}
To prevent duplicate reads from a single tap, disable the Prox Unlock setting on Verkada readers when deploying Multi-Technology credentials. This ensures the reader authenticates only against the secure EV3 credential.
{% endhint %}

***

## Credential structure

Each card contains two independent technologies in a single ISO-standard card body.

| **Attribute** | **Secure side (HF)**                                                              | **Legacy side (LF)**                                                                        |
| ------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| Frequency     | 13.56 MHz                                                                         | 125 kHz                                                                                     |
| Chip / format | MIFARE DESFire EV3, Verkada DESFire 40x                                           | Standard 26-bit (H10301)                                                                    |
| Encryption    | AES-128                                                                           | None (open format)                                                                          |
| Memory        | 8K                                                                                | N/A                                                                                         |
| Use with      | Verkada readers (AD34, AD64, AL54, AF64) and Verkada Intercoms (TD33, TD53, TD63) | Legacy Prox readers including door readers, parking, print, POS, vending, time clocks, etc. |

The programmed Prox card number and EV3 card number match, so the credential represents a single identity across both technologies. Verkada also ensures that the Facility Code and Card Number ranges assigned to Multi-Technology credentials do not overlap with those assigned to standard EV3-only credentials.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.verkada.com/access-control/users-and-credentials/commission-access-control-cards/multi-technology-credentials-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.