ShopSite uses ADC Direct Response (and always has), not WebLink or Relay
Response. If you read the PDF file their email refers to
(
http://www.authorizenet.com/files/referrerURL.pdf) click on the link on the
first page called "What if I Don't Connect to Authorize.Net Using WebLink or
ADC Relay Response" and you will see that it says:
"Referrer URLs apply only to the WebLink and ADC Relay Response
connection methods."
Also interesting, if you click on the link in that PDF file to take you to
another PDF file
(
http://www.authorizenet.com/files/secur ... ctices.pdf) regarding
security "best practices" you will see that they recommend using ADC Direct
Response... the method ShopSite uses.
For emphasis, on
http://www.authorizenet.com/files/secur ... ctices.pdfpage 3, in the section titled "Referrer URLs (soon-to-be REQUIRED)" it
specifically states:
"DO NOT use this feature if you connect to Authorize.Net via ADC Direct
Response."
If you continue to get emails like the one below from Authorize.net, and you
have no software using your Authorize.net account except ShopSite, then I
would recommend that you contact Authorize.net tech support, tell them that
your shopping cart does NOT use the methods their emails say you are using,
and ask them if they can verify what their emails are claiming.
-Loren
"Gerald Good" <Jerry@importfood.com> wrote in message
news:3CEF216C.5015AC47@importfood.com...
Thanks for your comment. Actually I had read the Solution S05446 and
understood that Shopsite uses ADC Direct Response, and I was quite sure
that
the delimiter issue was not the cause of my problems, but you have a much
higher understanding of it than I do. I'm just glad the upgrade to 6.0
solved
my problem.
By the way, I am getting the following message via email from
Authorize.net.
Is it correct that I should do nothing and ignore it? Or must I make any
changes to my settings. Please let me know. Thanks!!
************
Subject: SECOND NOTICE: New Authorize.Net Security Requirement
Date: 24 May 2002 15:20:04 -0600
Status:
Dear Authorize.Net Merchant,
This email serves as a reminder to a previous email that was sent to you
on May
17, 2002. Your action is requested.
During a recent analysis of the Authorize.Net system, it was determined
that
your website connects to the Authorize.Net payment gateway via the WebLink
or
ADC Relay Response linking method. Authorize.Net will begin requiring
Merchants
who connect to the Authorize.Net payment gateway via WebLink or ADC Relay
Response to implement a Referrer URL on their account, effective May 28,
2002.
If you only use Virtual Terminal as your method of processing
transactions, the
Referrer URL requirement does not apply. However, you are strongly advised
to
set the Password Required Mode to True. This will offer increased
security on
on your payment gateway account.
A Referrer URL is any Webpage address from which your site processes its
Authorize.Net transactions. Authorize.Net uses Referrer URLs to verify
that
each transaction submitted to your payment gateway account originated from
your
Website. Hereís how it works: First, you supply Authorize.Net with the Web
address (otherwise known as a URL) from which your Website submits
transactions
(e.g., ìhttps://www.mywebsite.com/paymentform.htmlî). Then, each time a
transaction is submitted to your payment gateway account, Authorize.Net
checks
the address the transaction is coming from against the addresses that you
have
supplied in your Merchant Interface. Finally, if the addresses donít
match,
Authorize.Net rejects the transaction
This security feature is available to all Merchants at no additional cost.
Itís
convenient, easy to install and serves as an additional security measure
for
you. In order to continue processing transactions through your
Authorize.Net
payment gateway account, you will need to become compliant with this new
requirement by May 28, 2002. ANY MERCHANT WHO FAILS TO MEET THIS
REQUIREMENT
WILL BE UNABLE TO PROCESS TRANSACTIONS AFTER MAY 28, 2002, UNTIL THEY ARE
IN
COMPLIANCE WITH THIS NEW SECURITY MEASURE.
To help you implement a Referrer URL on your account, weíve created a
short
document designed to assist your Websiteís technical specialist, Web
developer,
or shopping cart provider:
http://www.authorizenet.com/files/referrerURL.pdf.
Should you have more questions about protecting your account, see our
Security
ìBest Practicesî White Paper located at
http://www.authorizenet.com/files/secur ... ctices.pdf or contact our
Customer Support department at
support@authorize.net.
Thank you for your cooperation,
Authorize.Net Corp.
915 South 500 East, Suite 200
American Fork, UT 84003
*** Please do not reply to this email.
You received this email because you chose to be an Administrator Notices
or
Developer Announcement recipient. You may change your email options by
logging
in to your Merchant Interface. Click on Settings, select Manage Contact
Information, and click Go. To Edit a contact, click Select next to the
contact
that you would like to edit. Click Edit Contact, change or add information
as
desired, and click Submit to save the changes.
If you wish to unsubscribe completely from receiving future Authorize.Net
mailings, please delete your email address from the Manage Contacts area
of
your Merchant Interface. You may also send an email to
support@authorize.netfrom the email address you wish to remove.
Loren wrote:
Actually, I believe the problem was caused by the misconfiguration of
his
Authorize.net account's ADC response delimiters as described in Solution
S05447 in the ShopSite Knowledgebase
(
http://support.shopsite.com/kbase).
If it had been the Referrer URL (see Solution S05446 for an article
about
THAT) then the problem could not have been resolved by upgrading to
ShopSite
v6.
-Loren
"Norman" <shop1ob@aol.com> wrote in message
news:3CEE68D1.CED6446@aol.com...
At least one cause of this has been discovered. We use a payment page
that
links to AuthorizeNet using WebLink in addition to ShopSite for our
store.
I added the referrer URL as requested by AuthorizeNet for the payment
page. Doing this knocked ShopSite processing offline with the exact
error
message you received. I deleted the URL and the store has started
functioning again.
Norman
1 Ocean Boulevard
Beautiful, Quality Swimwear
http://www.web8.com/oceanGerald Good wrote:
Hi. I am an old Shopsite user but have a new Authorize.net account.
Authorize.net will just not work for some reason.
I have a very competent web host, the venerable Lexiconn, and they
confirmed to me that everything is setup correctly with regard to my
Shopsite.
I spoke to a rep at Authorize.net and she seemed knowledgeable, as
she
has worked there for 2 years. She also checked with her boss after
not
finding any solutions. Well, here is what she advised:
1. She checked all of my authorize.net settings and they looked
fine.
2. After trying to place some sample orders, she was getting the
same
error message I initially reported (pasted below).
3. She is sure that this is "definitely a cart problem". Reasons
are
*the transactions are not "hitting the Authorize.net servers". no
evidence of this at all.
*she mentioned that the cart is doing a front line check and
rejecting
the transaction without sending the info to Authorize.net
4. Zip code and credit card info, those things are reported as
errors
and she doesn't know why.
Last night I actually did complete an order with Authorize.net via
Shopsite, it was when Authorize.net was in test mode. After that
one
order, I could never get another one to go through.
Would anyone be able to guess what the problem is?
Thanks!!
**************
Credit Card Processing Error
Your order was not processed
There was a problem processing your
credit card information.
Please verify that the following
were
entered correctly:
Zip Code
Card Number
Expiration Date
If you repeatedly see this message,
complete your order by
contacting the merchant directly.
Detailed error message:
(-)