2012

Sandbox User Guide April 2012 51
Testing Error Conditions
Testing Using AVS Codes
7
NOTE: The specified AVS code is set, regardless of whether a PP API error code is set. If no
AVS code is specified or the AVS risk control is not specified, AVS code X is returned.
Testing an AVS Code Using Virtual Terminal
Consider an example of testing for AVS code A using Virtual Terminal. You enter AVS_A in
the Address Line 1 field:
Y AVS_Y Exact match (no error). The complete address and 5-digit zip code matches.
Z AVS_Z The 5-digit zip code matches but no address is specified; results in an error if the “Partial
Address Match” risk control is set.
N AVS_N No address information; results in an error if the “No Address Match” risk control is set.
C AVS_C No address information for an international address; results in an error if the “No
Address Match” risk control is set.
E AVS_E Not allowed for MOTO (internet/phone) transactions.
I AVS_I Service unavailable internationally; results in an error if the “Service
Unavailable/Unsupported” risk control is set.
G AVS_G Service globally unavailable; results in an error if the “Service
Unavailable/Unsupported” risk control is set.
R AVS_R Retry; results in an error if the “Service Unavailable/Unsupported” risk control is set.
S AVS_S Service not supported; results in an error if the “Service Unavailable/Unsupported” risk
control is set.
U AVS_U Service unavailable; results in an error if the “Service Unavailable/Unsupported” risk
control is set.
AVS Code Trigger Description of Error