Announcement

Collapse
No announcement yet.

New Update for PayFlow Pro in MM5

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    New Update for PayFlow Pro in MM5

    Anyone had experience with this payment update yet?

    I updated MM5 and noticed that the error messages are less informative now. All messages now just say:

    "Unable to authorize payment."

    Before it would say "Invalid account number, CVV2 does not match, Declined, etc."

    Are there people experiencing problems with this new update from Miva? Is this version suppose to be better than the original?

    #2
    That message usually indicates a problem with the security, password, or SSL handshake.

    Make sure your host has the latest commerce library also installed for your payment module.

    Actaully, if I recall correctly, the latest PayFlow module no longer requires the PNTransact library.

    Comment


      #3
      When I tested it, it was working.

      It is when I purposely put in an invalid CC number or CVV2 do I get the message, "Unable to authorize payment."

      Usually, when I test the cart with an invalid CC number or CVV2 number, it will tell the customer what was wrong, for example "Invalid credit card number."

      I think those messages are important for when legitamate customers enter it in wrong.

      Comment


        #4
        When you test in test mode, the payment gateway is not actually contacted. The connection is simulated.

        Comment


          #5
          Hmmm... isn't test-payflow.verisign.com contacted in test mode? It will respond differently depending on which test card numbers you submit, too - some test card numbers are set up to 'always approve', some to 'always decline', and so on. The connection is not simulated - only the response you get, depending on the card number used and set of Verisign Fraud Protection package(s) enabled on your account.

          Comment


            #6
            My account is not in TEST mode.

            I am not getting errors when the valid orders are placed.

            It is when invalid CC numbers, CVV2 numbers, etc are entered is when I get the "unable to Authorize." message. Which I should be getting.

            However, the messages used to be more detailed, such as "Invalid account number" and "CVV2 mismatch"

            My question is when an invalid order is plaed, is there a way to give the customer some more detail like before?

            Also, (especially dotcomhost, since they use PayFlow Pro) is the new update perfect, buggy? Have anyone had experience with this update yet to confirm its functionality?

            TIA
            Mike

            Comment


              #7
              That is correct with PayFlow Pro, it does have its own testing gateway that is different from the production gateway.

              Comment


                #8
                Mike,

                I have not personally tested this update just yet. We are not using the latest MM5 updates in our own store so this didn't affect us and we can't see anything different, so until we do some hands-on testing - I couldn't give you a definitive answer. If you are hosting your site through us, feel free to open a support ticket and we'll test a few scenarios on your site, if you'd like.

                Comment

                Working...
                X