Conversation
This commit starts sending an address to AAMVA to validate. The verification still succeeds even if the address fails to match. This is because MVAs do not reliably perform address verification. The address results are included in the hash returned from `Proofing::Aamva::Responses::VerificationResponse#verification_results`. These can be used downstream to allow the address to be used for validation when other proofers are unable to verify an address. [skip changelog]
| last_name: applicant[:last_name], | ||
| dob: format_dob(applicant[:dob]), | ||
| state_id_data: format_state_id_data(applicant), | ||
| address1: applicant[:address1], |
There was a problem hiding this comment.
is there an address2?
There was a problem hiding this comment.
There is an address2 though I am just throwing the first line in for now since getting the 2nd in is a little complicated.
There was a problem hiding this comment.
To elaborate on this, the way the docs say to add the address to the request is to include an additional AddressDeliveryPointText field for address line 2, but only if there is an address line 2 present.
This means adding a little bit of extra logic to this class to handle that. We probably should do that but I'm keeping it simple for now to verify everything is working then we can come back around and handle the second address line.
There was a problem hiding this comment.
Just pushed 0386575 which is a little messy but does get address line 2 in there
|
Okay, I think I have everything here. Should be ready for review |
3 participants
This commit starts sending an address to AAMVA to validate. The verification still succeeds even if the address fails to match. This is because MVAs do not reliably perform address verification.
The address results are included in the hash returned from
Proofing::Aamva::Responses::VerificationResponse#verification_results. These can be used downstream to allow the address to be used for validation when other proofers are unable to verify an address.