Nov
07
Authorize.Net….wtf?
Posted by Sara
The past few days I’ve been finishing up an ecommerce application and the last pieces of the puzzle were to enable a customer to update his recurring billing info and also be able to cancel their recurring billing.
When developing for the Authorize.net payment gateway, each developer is assigned their own unique login credentials but we all share the same development account. So, in the past, you could login and see all of the developers transactions as well. I say in the past because we can’t get in anymore. On Monday, I made some updates to my code base and went to test it out and all of the sudden I am receiving a receipt from Authorize.net about my purchase (which as a developer you typically don’t receive) and the from email address isn’t even Authorize.net’s. It is some other developer who went in and made changes to the single developer account that everyone shares! So anyone testing authorize.net right now are all getting emails from deepak.jain@somedomain.com. And my new friend Deepak is also getting emails from authorize.net every time I update a subscription; he is CC’d on them.
So, I tried to login and change whatever Deepak messed with, but now I cannot login. WTF?! Let me put a call out to Deepak now.
HEY DEEPAK!! FIX THE ACCOUNT SETTINGS PLEASE!
While it is annoying that Deepak went in and made those changes that affects every single authorize.net developer, I can’t put the blame on Deepak. Seriously Authorize.net, why can this even be possible? Each developer should ideally be able to manage their own settings. We are pushing YOUR product and writing reusable code that we freely distribute to integrate YOUR gateway into people’s website. We like you… really, we do. Make it a little bit easier for us so next time Deepak, who refers to himself as the elusive “test test”, wants to change his settings, it isn’t global.
Deron over at 
