Announcement

Collapse
No announcement yet.

authorize.net relay response error

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

  • authorize.net relay response error

    phpinfo: http://www.offshoreonly.com/phpinfo.php

    after recently upgrading from 2.2.9 to 3.0.1 we're testing the new vb in parallel before cutting all 20k users over.

    our 2.2.9 forums still exist at: http://www.offshoreonly.com/forums

    our new 3.0.1 forums are at: http://www.offshoreonly.com/forums-new

    We are testing the paid subscriptions to our authorize.net acct and get the following message when trying to purchase a subscription from the UserCP.

    -------------------------
    The following errors have occurred.

    (14) The referrer, relay response or receipt link URL is invalid.

    ----------------------

    1. we setup the Relay Response URL per the vb documentationd using this link.

    http://www.offshoreonly.com/forums-n.../authorize.php

    2. we also edited the functions_subscriptions.php file to add our transaction key

    3. setup our authorize.net userid in the AdminCP

    4. setup a usergroup for paid subscriptions in the AdminCP

    Is this a known error? Did we miss a step?

  • #2
    Per Authorize.net documentation:

    The second cause of this error is submitting a Relay URL with your transaction information that isn't listed as a Valid Response URL within your Settings. By designating a Valid Response/Receipt URL, you are telling our system to only return results to one of the listed URL's. We will only post results to scripts designated as Valid Response/Receipt URLs.

    To add a Valid Relay URL, do the following:

    - Log into your merchant menu at https://secure.authorize.net
    - Click on "Settings" in your Merchant Menu
    - Select "Response/Receipt URL's"
    - Click "Add URL"
    - Enter your Response URL
    - Press "Submit"

    The final cause of this error is a compatibility issue- your customers web browser does not support the ability to pass the Referrer URL to us. In this case, the customer can use a different browser to place the order. The long-term solution for this is to upgrade your connection method to SIM or AIM, as these methods do not rely on customer browser compatibility for authentication.

    Comment


    • #3
      I had the same problem, there is a bug report here but if you want a fix right now go to vbulletin.org and do a search for authorize.net - you'll find the code you need to change to fix this problem.
      Sebastián J. Bianchi

      Comment


      • #4
        I found this thread and added the modifications, but i'm still getting the same error message.

        http://www.vbulletin.org/forum/showt...=authorize.net

        Where's the bug report, i did a search here and found nothing related.

        Comment


        • #5
          Originally posted by memdy
          I found this thread and added the modifications, but i'm still getting the same error message.

          http://www.vbulletin.org/forum/showt...=authorize.net

          Where's the bug report, i did a search here and found nothing related.
          Here's the bug report,

          http://www.vbulletin.com/forum/bugs....iew&bugid=2537

          That thread seemed to fix the error for me... at least I stopped getting the e-mails
          Sebastián J. Bianchi

          Comment


          • #6
            Thanks Basa, this was good information. But the thread/bug was closed and I did a quick scan looking for a new bug regarding this issue but didn't find one.

            Does anyone have any news on this issue, should it be fixed in v3.0.1 or not?

            Comment


            • #7
              We've been testing the new vB in parallel under a different directory structure, meaning that instead of www.domain.com/forums we were using www.domain.com/forums-new on a hunch i took down our live forums and renamed our vb3.0.1 forums to be www.domain.com/forums and now the paid subscriptions work.

              Don't know if this could be worked around in the code or not. But it's good enough for me to move forward with our testing and migration.

              problem resolved.

              Comment

              Related Topics

              Collapse

              Working...
              X