Administration Guide for Oracle Self-Service E-Billing > Payment Transactions > About Credit Card Payment Transactions >

About the Address Verification Service


Address Verification Service (AVS) reduces the risk of fraudulent transactions by verifying that the credit card holder's billing address matches the one on file at the card issuer. The address is optional and does not affect whether the payment is accepted or rejected. However, using an address might get a lower rate from card issuer.

A merchant (also known as the biller) submits the AVS request through the payment process directly to the specific credit card association (for example, PayPal Payflow Pro) for address comparison. If AVS is turned on by an Oracle Self-Service E-Billing administrator, address information passes into PayPal Payflow Pro as part of the PayPal Payflow Pro request. PayPal Payflow Pro then contacts the credit card issuing bank and passes along the address information.

The credit card issuing bank verifies the credit card address information on record matches the address information passed in by PayPal Payflow Pro. The credit card issuing bank then replies back to PayPal Payflow Pro whether information matched (address and zip code are checked during AVS). The value Y means yes, N means no, and X means a match cannot be determined. PayPal Payflow Pro then accepts or rejects (voids) the transaction based on the filter set through the Payment module (for both street address and zip code). There is also a filter option to set the international AVS code to determine if the AVS response was international, US or could not be determined. Some credit card issuing banks require city and state verification as well.

The Payment module does not handle these by default, but the pmtCreditCardSubmit job has a plug-in to allow custom code pass in the AVS values. For more information about AVS functionality, go to

https://www.paypal.com/payflow-support

If the Payment module does not send the address information to PayPal Payflow Pro, or if the Oracle Self-Service E-Billing administrator did not turn on AVS and the AVS check level is set to Full, the transaction fails. If the card issuer address is sent to the payment gateway, but the address does not match the information on the gateway, then the gateway can send an AVS code. If an AVS code is received, the Payment module logs the AVS code in the audit tables.

The Payment module supports PayPal Payflow Pro, but PayPal Payflow Pro does not support turning AVS on or off for each transaction. However, the lower capability PayPal Payflow Link can. You also must set up the AVS level with PayPal Payflow Pro as part of your PayPal Payflow Pro agreement. When setting up the account with PayPal Payflow Pro, the merchant must specify the level of AVS check: full, medium or light. When the Payment module passes the address information, PayPal Payflow Pro accepts or rejects the transaction based on the AVS check level. Note that the AVS check level is specified one time during merchant account setup and applies to all transactions for that merchant. The customer (merchant) also must specify to PayPal Payflow Pro during setup and that they will be using PayPal Payflow Pro (through the Payment module) for transactions.

Administration Guide for Oracle Self-Service E-Billing Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.