Announcement

Collapse
No announcement yet.

Unable to authorize transaction using PayflowPro and test transactions

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

    Unable to authorize transaction using PayflowPro and test transactions

    I've read all the relevant posts in this forum on this topic but can't find a solution. First let me assure you that I have all of the MIVA upgrades, including the Payflow one, and I'm using "pilot-payflowpro.verisign.com" as the host.

    Port is set to 443 - I didn't do this, MIVA did.

    My user id, password, vendor number and partner are entered correctly in the MIVA Payment Configuration for Payflow Pro.

    In Paypal Manager, I can see that my PayFlow Pro account is authorized for both live and test transactions.

    I entered a test transaction in MIVA using a test credit card number as specified by PayPal. They don't really say what to use for exp date and CVV2, so I picked a valid date and entered "1234" for the CVV2 (I'm using a test AMEX number). I get an "unable to authorize payment" error .. no other info.

    Tried again with a test Mastercard number and a 3-digit CVV@ - same error.

    I look in Paypal Manager and there are no transactions recorded .. at least none that I can find. (Do they record test transactions?) I ran a report for today and there were no transactions.

    When I login to PayFlow Pro, I use "partner", "merchant login" and "password" fields. No "user" field.

    MIVA Payment configuration asks for "User ID" so I put my "Merchant Login" there. I assume that's correct.

    HELP!

    #2
    Re: Unable to authorize transaction using PayflowPro and test transactions

    When you run a report you have to specify that you want test transactions instead of live. A generic unable to authorize payment can occur when the user info is wrong, make sure you are using your payflow username in both the login and the vendor boxes, partner should be the partner code given by whomever you signed up with, then the password you use for logging into the payflow management interface. Also make sure the amount you're testing with is below $100 as I think test transactions decline above that.
    David Hubbard
    CIO
    Miva
    [email protected]
    http://www.miva.com

    Comment


      #3
      Re: Unable to authorize transaction using PayflowPro and test transactions

      Actually, "vendor" is vendor ID, right? That's a totally different thing from my username. My vendor ID starts with V and is followed by numbers. My username is something that I made up.

      I thought the $100 thing might be the key. I was testing with an item that costs $119. So I changed the price of the item to $25 and tried again. Still get the same error. :-(

      I ran the PayFlow Pro report again, this time specifying "test" transactions instead of "live" (thanks for that). Still ... no transactions. So it appears it's never even getting to PayPal.

      Any other ideas? ;-(

      Comment


        #4
        Re: Unable to authorize transaction using PayflowPro and test transactions

        No, the 'vendor' it wants you to fill in is identical to your login name, the V number you're thinking of is related to your merchant account and how payflow talks to it but not related to the payflow setup in the store. Set the login and vendor boxes to be the same thing.
        David Hubbard
        CIO
        Miva
        [email protected]
        http://www.miva.com

        Comment


          #5
          Re: Unable to authorize transaction using PayflowPro and test transactions

          You are absolutely correct! I had just figured it out on my own and then found your post, so at least you are verifying the solution for me. Thank you so much!
          Also, for the record, I was able to do a test transaction for over $100.
          Last edited by alicia1234; 01-15-08, 06:58 AM.

          Comment


            #6
            Re: Unable to authorize transaction using PayflowPro and test transactions

            Now I am having problems with PayflowPro

            We are switching from Miva 4 to Miva 5, and I have input all the fields as they are from Miva 4 to the Miva 5 Payflow Pro section. But getting unable to authorize payment error. Tried multiple times, still the same problem.

            On Miva 4 it works without any issues, but on Miva 5 problems.
            One thing i found out, on Miva 4 host is payflow.verisign.com
            Miva 5 host is: pilot-payflowpro.verisign.com
            I tried changing it to Miva 4 settings, but still the same unable to authorize payment error.

            What can be the problem?

            Comment


              #7
              Re: Unable to authorize transaction using PayflowPro and test transactions

              Originally posted by zscg
              Miva 5 host is: pilot-payflowpro.verisign.com
              I tried changing it to Miva 4 settings, but still the same unable to authorize payment error.

              What can be the problem?
              pilot-payflowpro.verisign.com is only for testing, and will only accept test credit card numbers, such as 4111111111111111, and there may be dollar limit restrictions too. Remove "pilot-" from the front if you want the live server for live cards.
              David Hubbard
              CIO
              Miva
              [email protected]
              http://www.miva.com

              Comment


                #8
                Re: Unable to authorize transaction using PayflowPro and test transactions

                When I was having my problems back in January, somewhere along the line someone told me that in late February the server name was going to change from pilot-payflowpro.verisign.com to pilot-payflowpro.paypal.com. Maybe you're running into that? Here's the thread about that:
                http://extranet.mivamerchant.com/for...3957#post63957

                Comment


                  #9
                  Re: Unable to authorize transaction using PayflowPro and test transactions

                  The link in my 2/19/08 post is incorrect. It should have been:

                  http://www.paypaldeveloper.com/pdn/b...2799&jump=true

                  Comment

                  Working...
                  X