Too Many Address Verification Service (AVS) Issues – GDP Now Turned Off

  • Resolved esd3104

    (@esd3104)


    7 months, 1 week ago

    Just to say that the AVS mismatching seems to have ratcheted up again and I’ve just turned off GDP for 95% of my payment processing as a result. Saving 15c per transaction is simply not worth it for the hassle your AVS implementation causes. About 17 failures from 75 transactions.

    This is not an outside USA problem either – 95% of these are USA and a few Canada.

    I’ve given lots of feedback on this before. See this prior support thread.

    It seems to have gotten worse again. Although it’s not the plugin itself, its in the back end processing, it really makes your payments system unusable. There’s a lot to like about GDP, but this AVS nonsense is a killer and creates too many customer issues, so it is just no longer worth bothering with.

    I worked in the Card/Payment industry for 30 years. 25+ of those with a major payment brand. If you want to understand how to make your systems usable, please get in touch and/or actually implement merchant level controls on the strictness of AVS as I previously described.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Kari-SkyVerge

    (@kariskyverge)

    Hey there,

    Kari here, from the SkyVerge Support Team. Thank you for reaching out again about the AVS mismatching concerns. We have also seen an uptick in support requests for this issue in the last two weeks or so and our engineers have been working with the GoDaddy Payments teams to identify if there were any additional recent changes to the system that were the cause for more of these mismatches to happen.

    As you stated, the plugin itself is merely the tool for sending the data to GoDaddy Payments, so the resolution to this particular issue sits with the GoDaddy Payments teams, however, we have once again submitted feedback directly to those teams internally about this recent uptick in incidences and have met with some of the team members to clearly state the impact it is having on our customers.

    Your feedback here is appreciated, as without hearing from merchants like you, we would be unaware of the issues that you are facing when using GoDaddy Payments. Please know that the GoDaddy Payments engineers and product teams have been looped in on this issue and they are actively investigating what can be done while still maintaining the level of security they need to protect our merchants from fraudulent chargebacks. I don’t have any information at this time about resolution or changes that can/will be made to the system, as it is an ongoing investigation into the issue currently.

    While submitting this feedback, I have also mentioned the functionality of allowing merchants to toggle various AVS levels per site as a feature request, and sent them the link to this conversation and your previous conversations with us related to these AVS issues.

    Do you have any questions for me about this information at this time?

    Kind Regards,
    Kari

    Thread Starter esd3104

    (@esd3104)

    Thanks for responding – no additional questions at this time. It seems your core systems are setup to decline anything that is not an AVS response code of Y which is frankly insane to apply to every single merchant. I get what the fraud concern is, but trust me, what is implemented isn’t the solution.

    I posted here because you actually respond. ?? In another post it was mentioned about getting support vie the GDP Portal. I tried chat and got no response so I sent an email via that option and also got zero response (a different unrelated to AVS issue). ??

    I’d actually love to help and provide input if anyone wants to connect. As a payments systems person, its distressing to see what could be a great merchant processing/gateway service be ruined by bad decisions in the core processing logic.

    Plugin Support Kari-SkyVerge

    (@kariskyverge)

    Hey there,

    I want to once again thank you so much for your feedback and candor on this issue. As of yesterday, May 6, you should start to see improvements in the checkout process for your customers! Your feedback was heard and the engineering team made some adjustments to the AVS system that should work out better for all of your customers.

    When you have the chance, would you please let us know if you can test the gateway again and see how it now performs for you and your customers?

    All the Best,
    Kari | SkyVerge Support

    Thread Starter esd3104

    (@esd3104)

    Thanks, I also got a note from Ed that the bug had been fixed. I have flipped GDP back on but until I get some renewals for club membership I won’t know if it’s working. That should happen around May 15 when the next reminders hit. Tks

    Thread Starter esd3104

    (@esd3104)

    @kariskyverge so after 50+ transactions I am not seeing any issues. Just 1 customer had an issue but they live in an apartment for which addressing can always be error prone. They apparently correctly changed the address to match so seems the bug fix implemented is working as expected. ??

    Plugin Support Kari-SkyVerge

    (@kariskyverge)

    Hey @esd3104,

    We are so thrilled to hear this update! I will share this feedback with the plugin team so that they are aware that the changes made have indeed been very helpful. Thank you so much for updating us here and for letting us know the outcome is a positive one!

    Moving forward, if you find any additional issues with the GoDaddy Payments plugin, please feel free to start a new conversation thread, since this one was previously marked “done,” so we don’t miss your reach out. : )

    Wishing you all the best,

    Kari | SkyVerge Support Team

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Too Many Address Verification Service (AVS) Issues – GDP Now Turned Off’ is closed to new replies.