• I’ve got an ecommerce site and using payflow.

    We have tested with the billing address zip being different than the credit card zip and it is still processing through even though it is getting an ‘N’ for the match. Shouldn’t it be rejecting the order because of that?

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor angelleyesupport

    (@angelleyesupport)

    Hi, We have received your request and are looking into that, will get back to you soon after discussion with our lead developer.
    Thanks!

    Plugin Contributor angelleye

    (@angelleye)

    @zerozendesign, This depends on your PayPal account configuration. You need to check for Fraud Management Filters, or Risk Controls, or Block Payments, or something like that in your profile. Unfortunately, it’s different depending on the version of account you’re using so I can’t tell you exactly which one to expect you’ll find.

    Within that you can specify rules for how to treat transactions where AVS or CVV2 match fails. Yours must be set to accept them, so you could adjust that accordingly.

    Also, keep in mind that if you’re working in the sandbox it will always accept those unless you are doing negative testing to force errors.

    Thread Starter Frog Eat Fly

    (@zerozendesign)

    Hi guys,

    Thanks for the response. We’ve checked everything. PayPal is returning that it doesn’t match. It is also being recorded on the transaction.

    On the checkout end (visitor side) it seems to go through as normal BUT then on the backend the order is put on hold.

    Seems it should be showing an error, not appearing that it is going through as normal.

    What do we need to do to get it to show an error vs seem to process as normal?

    Plugin Contributor angelleye

    (@angelleye)

    You need to find those fraud filters. Yes, PayPal returns the mis-match, but without fraud filters enabled to block those it’s going to let them through, and it would be up to you to make sure you’re comfortable shipping the order (or not). If you configure the fraud filters to block transactions where AVS or CVV2 mis-match, then the error would occur and be returned to the buyer during checkout.

    As it is now, the system expects that it should allow it to go through as normal since you are not specifically blocking those transactions with fraud filters. As such, it shows the customer a successful order and doesn’t give them any reason to believe anything was wrong. In that setup, nothing was wrong. It worked exactly as configured.

    Now, we do have an option in the PayFlow settings for Fraud Management Filters, and it sounds like you must have this set to “Place order On Hold for further review.” This would allow the payment to be processed through PayPal since the fraud filters are allowing it, and the money would fall into your account, but then in WooCommerce it would set it to On Hold so that you can clearly see it happened and make sure to review the order before shipping or deciding to refund it. Of course, if this option was set to “Ignore warnings and proceed as usual” then you the order would go to Processing in WooCommerce like any other order.

    So if you want these transactions to simply be declined when AVS and/or CVV2 codes do not match you will need to get Fraud Filters configured on your account that way. If you aren’t finding anything like that then you’ll need to contact PayPal and get them to enable them for you. Once enabled you’ll be able to configure settings for AVS and CVV2 as I’ve said.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Billing Zip Code match N but still processing’ is closed to new replies.