Why did I get result code 112?

The following outlines the causes and solutions to this issue:

Processor AVS settings causing declined transactions

Payflow Pro allows merchants to request AVS authorization at the processor level. Once a transaction is returned to Payflow Pro an edit check occurs. The Payflow Gateway either accepts or rejects it based on the AVS results. If it is rejected, we return result code 112.

Although this isn't the preferred way to validate AVS (see the Payflow Gateway Developer Guide and Reference and the Payflow Fraud Protection Services User’s Guide for other ways to handle AVS), some merchants require this functionality. To remove or modify the AVS settings on your account, contact Payflow Support to have AVS turned on or off at the processor level.

Declined transactions on test servers

The card-issuing bank doesn't validate the street address and ZIP code on the test servers, but you can use the following method to verify these values.

• The Payflow Pro testing server simulates AVS by returning a value for AVSADDR, based on the first three characters of the submitted value for BILLTOSTREET.
• The testing server returns a value for AVSZIP, based on the submitted BILLTOZIP value as shown in the following table.
• If BILLTOSTREET starts with 667 or higher, or begins with a non-numeric character, then the simulator returns AVSADDR=X, AVSZIP=X.

The following table tests AVSADDR.

The following table tests AVSZIP.

American Express not set up with FISERV

Contact your merchant bank and ask to have American Express added to your account with FISERV.

Customer billed

Global Payments Central (MAPP), Moneris, Litle, and Planet Payment are host-based processors. AVS restrictions shouldn't be used with a host-based account, because if a Sale transaction is successfully authorized but fails the AVS check, the processor will settle the transaction even though we returned result code 112. This happens because AVS is a secondary function that occurs after the authorization process. Contact Payflow Support to have AVS restrictions turned off on your account.

Note: Even if you're not using a host-based processor, the cardholder may see a pending authorization on their account because the AVS check occurs after the authorization process. The pending authorization will be released within 3 to 29 days, depending on the card-issuing bank.

See also:
RESULT Values and RESPMSG Text