Skip to main content

Keycard Encoders Overview

Quick Setup

Choose your encoder type, connect it, then run a test card. Plan about 15 minutes.

This guide explains keycard encoding in AVA and links to setup steps. It also covers room mapping and vendor sync when your encoder supports it. Saflok supports read-keycard requests when you use the dynamic Universal Encoder Agent session path. PMS-integrated readers use the PMS transport and do not need a Universal Encoder Agent session. Be-Tech Windows Agent installations can recover a stopped client or service automatically.

Quick reference​

TaskWhat it doesWhere you go
Select encoder typePicks your lock systemSettings → Room Access → Keycard Encoding
Set up ACSHotelConfigures the ACSHotel hotel ID, shared Windows Agent routing, encoder records, and kiosk routing on the Kiosk pageACSHotel Setup
Configure GreatLocks encodersKeeps each physical encoder and Windows Agent PC separateSet Up Keycard Encoders
Choose connection methodDirect vs. Windows AgentSet Up Keycard Encoders
Configure encoderAdds server, PMS, or device detailsSet Up Keycard Encoders
Enable PMS card readingAllows Entitlements to scan physical PMS cardsSet Up Keycard Encoders
Map room names (optional)Align PMS rooms to encoder names and building and floor dataKeycard Room Mapping
Customize instructionsUpdates guest-facing messagesKeycard Guest Instructions
Fix issuesResolves encoder errorsKeycard Encoder Troubleshooting

Where to find it​

Settings → Room Access → Keycard Encoding

How keycard encoding works​

  1. AVA confirms the guest’s room assignment.
  2. The kiosk or desk encoder writes the room key.
  3. The guest receives a physical keycard.

Supported encoder types​

  • Saflok (Assa Abloy) for keycard writes, plus read-keycard support on the dynamic Universal Encoder Agent session path
  • Be-Tech encoder workstations with direct or Windows Agent support
  • LockSDK bridge-based encoders
  • GreatLocks servers
  • ACSHotel Windows Agent packages
  • PMS-integrated encoders (requires active PMS integration)
PMS card reading

PMS card reading needs an active PMS encoder, the reading setting, and PMS-advertised support. It does not require a local Universal Encoder Agent session.

Before you start​

  • Encoder hardware is installed and powered
  • Encoder software or drivers are set up
  • Network access is available from kiosk or desk
  • PMS integration is active (if using PMS encoders)
  • ACSHotel Windows Agent package is installed on the connected Windows PC.
Be-Tech Windows Agent setup

Each Be-Tech Windows Agent registration supports one encoder. For multiple encoders, register one agent per encoder and route kiosks to the matching agent. After a Windows restart or manual stop, the agent can recover the Be-Tech client and refresh readiness automatically.

GreatLocks multi-encoder setup

Add one GreatLocks row for each physical encoder. Give each row a unique Encoder ID. With Windows Agent mode, install the matching agent on each encoder PC.

Next steps​

  1. Set Up Keycard Encoders
  2. ACSHotel Setup
  3. Keycard Room Mapping
  4. Keycard Guest Instructions
  5. Keycard Encoder Troubleshooting

Still Stuck?​

Contact success@vouch-technologies.com if:

  • ❌ You are unsure which encoder type to select
  • ❌ Encoders are offline after setup
  • ❌ Keys cannot be encoded for any room

Helpful to include:

  • Encoder type (Saflok, Be-Tech, LockSDK, GreatLocks, ACSHotel, or PMS)
  • Screenshot of the Keycard Encoder Settings section
  • Time the issue started