Hello Community, We would love to hear your feedback on AFDS as it is
today, what you would like to see in an updated Risk/Fraud management
feature and what you like/don't like about other fraud solutions out
there. As this is a developer community w...
Back in December of 2014, I wrote about the release of our 1.8.3 SDKs (A
Holiday Gift for Developers: Version 1.8.3 SDKs Released). I mentioned
in that article that we’ve been getting lots of feedback on our new
controller model. In this post, I want...
It’s been nine months since we first published our SDKs on GitHub, and
we couldn’t be more delighted with the level of developer interaction
and community involvement. From the very first formatting pull request
to the latest feedback on our new cont...
The Authorize.Net SDKs are now on GitHub! We have also published our
SDKs to all of the major package repositories, making it simpler to
include Authorize.Net in your project. For those who don’t know me, my
name is Brian McManus, and I’m Authorize.N...
I would strongly recommend using Cybersource if you need 3DS.
Authorize.Net will not be supporting the latest version (called EMV 3DS)
and 1.0 (which Authorize.Net does support) is currently being sunset by
the networks and banks:
It must be some data in your three Customer Profile fields that are
causing an issue. Can you change them one field at a fime from the test
First Last XXXX@EXAMPLE.COM
It looks like there may just have been an issue with sandbox processing,
does this happen consistently? If you try our API Reference you can see
this method working :
Not sure I understand the question, what do you mean by AIM ARB? AIM is
only for single transaction processing. For recurring you will need the
Authorize.Net XML/JSON API