Internal Billing
Departments, please use account number and object code 1704703-0616, and expense object code 5490, when creating internal billing for services from the CatCard office.
CatCard Reader Purchases and Data Access
Purchasing Card Readers
To ensure compatibility and proper programming, we strongly recommend purchasing all card reader devices through the CatCard Office. At a minimum, all devices intended for use with CatCards must be reviewed and approved by the CatCard Office prior to purchase. Using unapproved devices may lead to compatibility issues, rendering CatCards unreadable.
For assistance with hardware validation, contact fnsv-catcardqa@arizona.edu.
Obtaining CatCard Numbers or University IDs
CatCard numbers can be accessed in several ways, depending on your specific needs.
University of Arizona Enterprise Directory Service (EDS) CatCard Attribute
The EDS provides a secure repository of identity data, including biographic, demographic, role, and membership-related attributes for students, faculty, staff, departmental sponsored visitors, and others. With the introduction of mobile credentials, we recommend using the CatCard Attribute instead of the ISO attribute. The ISO attribute only includes the physical card number, while the CatCard Attribute includes all active card numbers.
With EDS access and a properly developed application, you can:
- Retrieve a list of CatCard numbers for employees in your department for use with systems like Amer-X for keyless access.
- Verify an individual’s university status using a CatCard number or EmplID.
- Convert a list of collected CatCard numbers to their corresponding University ID numbers.
- Confirm whether a swiped CatCard is the current one for the cardholder and retrieve their University ID.
Requesting EDS Access
To access EDS, you must first complete FERPA training. After completing the training, visit the EDS website to request access.
University of Arizona CardSync Integration
If a downstream system requires real-time credential updates, CardSync is configured to push changes to Boomi, which can be extended to new destination systems as needed. CardSync also provides API endpoints that accept a card number and return data previously encoded on a magstripe. To explore the use of these features, please submit a ServiceNow ticket.