Skip to main content

Managing Student RFID Card Identifiers

Before students can use RFID cards for checkpoints or attendance, Orah must be able to match each card to a student record. This guide explains how RFID card identifiers work and how to manage them in Orah.

Overview

RFID check-ins rely on a unique identifier stored on the student’s RFID card.

When a student taps their card, the RFID reader sends that identifier to Orah. Orah then matches the identifier to a student profile and completes the configured workflow.

Orah supports three identifier options for matching:

  • Card UID – a unique value you capture per student (using the card’s factory serial number)

  • Orah Reference ID – the student’s internal Orah identifier

  • Blackbaud SIS ID – the student’s Blackbaud SIS identifier

📌 The identifier stored in Orah must match the value being sent by the RFID reader. If they do not match, the student will not be recognised.

For a full explanation of how each identifier option works and how it affects your hardware requirements, see the RFID Hardware & Setup Guide — How Student Matching Works section.


What is a Card UID?

A Card UID (Unique Identifier) is a unique value assigned to an RFID card.

Each RFID card should have its own Card UID.

Examples:

  • 04A7C21B9F

  • 138274651

  • 0012459876

The format varies depending on the card type and reader being used.


How Orah Uses Card UIDs

When a student taps their card:

  1. The RFID reader reads the Card UID.

  2. The reader sends the Card UID to Orah.

  3. Orah searches for a matching student profile.

  4. If a match is found, the RFID workflow continues.

If no matching Card UID is found, the student cannot be identified.


Adding Card UIDs to Student Records

Schools can manage Card UIDs in several ways.

Option 1: Add Card UIDs Manually

If only a small number of students require RFID access, Card UIDs can be added individually to student records.

Option 2: Import Card UIDs in Bulk

For larger deployments, schools may choose to import Card UIDs using a CSV file.

This allows multiple student records to be updated at once.

Here is an article walks you through the bulk import steps.


Replacing Lost or Reissued Cards

If a student receives a replacement card, the new card may have a different Card UID.

When this happens:

  1. Obtain the new Card UID.

  2. Update the student’s Card UID in Orah.

  3. Test the new card at a checkpoint.

The old Card UID should no longer be used.


Best Practices

Use Consistent Student Records

Ensure each student has only one active Card UID.


Test Before Rollout

Before deploying RFID across campus, test a sample group of student cards.


Keep Card Data Current

Update student records whenever cards are replaced or reissued.


FAQs

Can two students share the same Card UID?

No. Each Card UID should be unique to a single student.


What happens if a Card UID is incorrect?

Orah will not be able to identify the student when the card is scanned.


Can Card UIDs be imported in bulk?

Yes. Schools can manage Card UIDs through bulk import processes where appropriate.


Can RFID use identifiers other than Card UID?

Yes. Orah supports three identifier options for RFID matching:

  • Card UID – the card's factory serial number (recommended for most schools)

  • Orah Reference ID – the student's internal Orah identifier

  • Blackbaud SIS ID – the student's Blackbaud SIS identifier

The identifier you choose affects which RFID reader hardware is required and the overall setup involved. See the RFID Hardware & Setup Guide for details.


Can other scanners like barcode / Magnetic Strip be used to identify students?

Yes, Any Plug and Play external scanner can be used to work with the checkpoint app.

Did this answer your question?