AAMVA Verification configurations

What these configurations cover

AAMVA Verification runs a suite of Verification checks against what an end user submits. The configurations decide which of those checks a template requires, and how the checks that carry their own options behave.

AAMVA Verification offers required or un-required Verification checks, Identity Comparison checks, and Verification check sub-configurations.

Where to find it in the Dashboard

Two places matter, and they do different jobs.

Documentation > Verification Checks is the reference. Find the section for AAMVA checks to see every check you can choose from.
Inquiries > Templates is where the change is made. Select a template that uses AAMVA Verification, use the left panel of the Flow Editor to head to Verifications, select the AAMVA Verification template, then open Checks.

What the settings control

Each check is either required or not required. A required check must pass for the Inquiry as a whole to be marked completed, so requiring more checks makes a template stricter and requiring fewer makes it more forgiving. See What is a Required Verification Check? for what that status means in practice.

There is no one set of checks that suits every organization. The choice turns on whether you would rather avoid passing someone who should have failed, or avoid failing someone who should have passed, and on which checks are more fraud oriented than conversion oriented.

When to reach for it

Reach for these settings when your pass rates or your fraud exposure suggest the current required checks are wrong for the template. Expect to iterate: you can start from the defaults, change one check, and watch what it does.

For the full walkthrough, including how to read the check reference and how to edit required checks, see Configuring AAMVA Verification checks. To read what the checks report once they have run, see Understanding AAMVA Verification results.

Plans Explained