Authorize.net problem solved (invalid referrer URL)

I called miva and they figured out the problem. I want to share this with
everyone so you can stop banging your head against the wall... I am just
running test transactions but i hope it works when i select go live...

On the option to post valid URLs in the settings option in Authorize.net 3.0

LISTEN CLOSELY....


DONT PUT ANYTHING... delete all refrences to url's domains or anything...

I dont understand it but it works now and thats a load off my shoulders....

Mike

Authorize.net problem solved (invalid referrer URL)



>> I want to share this with everyone so you
>> can stop banging your head against the wall

Actually, YOU are the one that has been banging
your head.

>> LISTEN CLOSELY....

Ok.

>> On the option to post valid URLs in the settings
>> option in Authorize.net 3.0
>> DONT PUT ANYTHING

No such option!

It doesn't exist in Miva Merchant and it doesn't exist
on Authorize.net. At least no option such as this that I
can find. Is this something you did in Miva Merchant Admin
or on Authorize.net?

Don't you think you owe the poor gal at Authorize.net an
apology for being so belligerent?

Kenny

Authorize.net problem solved (invalid referrer URL)



Mike,

I never had any URL's configured in Authorize.net
and didn't feel they were necessary because if somebody
want's to put money into my account from a different URL,
then let um do it (grin)! BUT, they can also take money out!

You should be able to keep the URL's, as long as they are
valid URL's. How much did you have to pay Miva for the
Information that was already given to you?

When you setup Referring URL's, Authorize.net simply checks
the URL's that you have configured to make sure the URL that
is sending the payment information is "authorized". That is
probably one of their defenses to make sure nobody has access
to your account other than you. Anyone who knows your
User ID and Password (ex employee for instance) can debit your
account if they know your login information, so the Referring
URL's is just a secondary defense to prevent this type of fraud.

Example: If I used to process your orders as an Employee, I
would know your login information and could create a script to
automatically issue refunds to myself and use my own computer
to do so. The referring URL's (my understanding of how they
work) would help prevent this.

The gal at Authorize.net probably didn't fully understand your
problem. Not defending Authorize.net support as I've heard they
are pretty bad. But then again, is Miva's support any better?

Kenny

---
Kenny Gardner
[email protected]

GAP Development Company (CLACom For Windows)
<A HREF ="http://www.gapdev.com">http://www.gapdev.com</A>

Authorize.net problem solved (invalid referrer URL)



> >> On the option to post valid URLs in the settings
> >> option in Authorize.net 3.0
> >> DONT PUT ANYTHING
>
> No such option!

To get to the Referrer URL option go to:

https://secure.authorize.net/login.dll?merchant

LOG IN

SELECT: Settings

SELECT: Manage URLs

Add a New URL or Edit an existing one.
-CHECK BOX: Add To List Of Valid Referrers

UPDATE

Mike Mashburn
Mgr of IT
Wall St Whispers / Interwebworld

PS: I normally cut tech support folks a lot of slack, having been in that
end of the business for many years, and knowing how difficult it is to deal
with clients when the folks you work for are stonewalling you -- it's tough
to be caught in the middle. However in the case of the other MIKE here he
has my full sympathy -- since I'm dealing with the same problem and have
been getting the same non-responsive non-answers for a week now. If they
don't know the answer or just don't care to help their users they should
just say so -- the finger-pointing back at Miva and my IHP is really wearing
thin.