The following street address and ZIP codes combinations will trigger specified AVS results in the BridgePay Network Solutions Test (UAT) Environment - Not for Production NOTE: Account verification restriction to the 4111111111111111 card should be removed. All valid card numbers will be supported for the above mentioned transaction types.
Street Address
ZIP Code
Results in AVS Response Code
AVS Response Message
Provided or Not
11111
00
AVS Error – Retry, System unavailable or Timed out
Not Provided or does not begin with 8320
22222
46
Street address doesn’t match, 5-digit ZIP matches
Must begin with 8320
22222
4E
Street address and 5-digit ZIP match
Provided or Not
33333
43
Street address not available (not verified), ZIP matches
Provided or Not
44444 or Not Provided
40
Address not available (Address not verified)
Must begin with 8320
55555
4F
Street address and ZIP matches
Must begin with 8320
Any Zip not listed above
4D
Street address matches, zip does not
CVV Verification
CVV numbers: AMEX 1234 or 1111, All Others 999 or 111
Card Type
CVV Number
CVResult
CVMessage
Amex
1234 or 1111
M
Matches
All others
999 or 111
M
Matches
Amex
Provided but none of those listed above
N
No Match
All others
Provided but none of those listed above
N
No Match
All Card Types
Not Provided
null
no value returned in message
Account Verification Gateway Results
NOTE: If using TSYS set TransIndustryType to "DM"
As part of testing account verification, the combination of the above Street, Zip, and CVV values will trigger results as follows.
AVS Result
CVV Result
BridgePay Response Code
BridgePay Message
4E, 4F, 40, 7F
M
A01
Approved (EXACT MATCH)
00, 46, 43, 4D, null
M
A01
Approved (CARD OK)
4E, 4F, 43
N
A01
Approved (CARD OK)
46, 4E, 43, 4F, 4D, null
null
A01
Approved (CARD OK)
00, 40, 46, 4D
N
D01
Denied by customer's bank (DECLINE)
00, 40
null
D01
Denied by customer's bank (DECLINE)
Any account-verification request sent with exp-date of 12/99 will result in a decline.
TPI Gateway
On the TPI gateway the match or not matches response is sent back from the processor. There is an interface within TPI’s UI that allows the gateway to decline or approve the transaction based upon the CVV response from the processor. This is processor dependent since some processors want to fully control whether they approve a transaction based on CVV match. In general, this only works with terminal processors.