http://washingtonexaminer.com/credit-card-firm-cuts-off-nations-no.-1-gun-store-for-selling-guns/article/2536417Please
explain the reasoning behind this. If this is Cybersource policy now, I
may have to start looking into alternatives and discontinue...
I got a call today from someone who has a bunch of encrypted swipers and
wants to be able to integrate them using Authorize.net. I realize that
there's no interface for entering the decryption keys in Authorize.net -
that's something that has to be n...
Since we will likely be getting at least some orders from foreign
countries, Authorize.net's fields are insufficient. Specifically, not
all address formats fall neatly into address, city, state, zip, and for
that reason we prefer to have address2 as ...
I assume there's no problem with this, but I just want to make sure. My
parents' business has an Authorize.net account set up (including
Cybersource merchant account, I believe) as of some months ago. We never
got around to actually integrating it. N...
My code was working just fine with my developer account. I switched over
to the production account in test mode, still worked. Now I'm testing on
the production account in live mode, and every time I fill out the CIM
popup (and I tried with both my c...
If you update the subscription, it will reactivate. If the payment it
failed on was the first one, it will restart with that payment;
otherwise it will start with the payment after the one that failed. In
the latter case, you need to do an AIM transa...
https://developer.authorize.net/tools/responsecode99/Your fingerprint
isn't calculating correctly. Reverify that you have the correct login ID
and transaction key set. If that doesn't fix anything, post your code
(with the ID and key masked) here, pr...
Or also have Authorize.net post everything twice, with a certain amount
of time between posts. If your failure rate is say 2%, this would bring
it down to 4/100 of one percent, or 4 failures every 10,000
transactions, which is an acceptable loss rate...
This is a great idea. Ideally, you could specify a date/time range, and
Authorize.net would then silent post everything again - spaced out
enough so it doesn't overwhelm your hosting. With maybe a flag so you
know if something is a post or a repost.