To answer your question: Nothing. It's already verifying it for you.
The HMAC is included with the AES ciphertext and hidden from the developer. When you call crypter.decrypt(ciphertext), it will automatically check the HMAC automatically. You don't need to do a second verification operation nor need to instantiate a separate Verifier object.
Verifier objects are strictly for verifying stand-alone HMACs or public-key signatures. That's why it's throwing an exception -- it expects keys with purpose SIGN_AND_VERIFY or VERIFY.