Authorize.Net is a well-respected, international Payment Gateway with a many features and benefits. Authorize.Net allows you to accept donations directly on your website easily and seamlessly.
After your Authorize.Net Add-on is activated, go to “Donations > Settings” and click on the Payment Gateways tab. There you will see the default Payment Gateways (PayPal Standard, Test Payment, and Offline Donations). You should also see Authorize.Net as an option as well. Click on that to enable Authorize.Net as your credit card Gateway for your website.
If you would like to accept credit cards directly on your website with Authorize.Net you will need an SSL certificate.
Obtaining your Authorize.Net API Keys
Once you have activated the Add-on it’s time get your API Keys and configure Give to integrate with your Authorize.Net account to accept donations.
NOTE: When you first sign-up for Authorize.net, they provide you with two items which cannot be recovered easily later. Make sure that after you sign-up that you take note of both your Secret Question, and your Transaction Key. These items can be used immediately, but if you forget them or misplace them you will not be able to recover them easily and will instead have to delete them and generate new keys.
After logging into your Authorize.Net account, you’ll be presented with your Authorize.Net Dashboard like the image above. From here, look in the left-hand sidebar and scroll down to the Account section and click on the Settings item. In the Settings page, look in the Security Settings and click on the link titled API Login ID and Transaction Key.
To integrate with Give, you need just two pieces of information:
- API Login ID
- Transaction Key
Both of these are available on this screen. The API Login ID is clearly labeled at the top of the page. But the Transaction Key is hidden. This is why it’s important to save that after you first sign-up for Authorize.Net. If you didn’t save it, hopefully you saved the answer to your Secret Question. Because that’s the only way you’ll be able to recover that Transaction Key again. Input the Secret Answer in the field and you’ll be redirected to a page that provides you with your Transaction ID. Alternatively, you can select the Disable Old Transaction Key(s) checkbox and you’ll force the old key to be invalid and a new key to be generated.
Copy each key and go to your WordPress site. Go to “Donations > Settings” and click on the Payment Gateways tab. There you’ll see a section called Authorize.Net Gateway Settings. Paste each key into it’s respective field, then hit save.
That’s all there is to it. Now when your donors come to your site, they’ll be able to use credit cards to donate to you directly in the currency of your country and not have to be redirected to another site.
Give Authorize.Net Frequently Asked Questions
Authorize.Net is a powerful payment gateway with many payment processing options and configurations. We want to help you get setup with Give and Authorize.Net as easily as possible. The following are a few common issues and their resolutions:
Yes. Give can be used with the Recurring Donations and Authorize.net to accept subscription donations within your live merchant account.
To configure the integration, See the configuring Authorize.Net and Recurring Donations article.
The Payment Form module in Authorize.Net has a field that is checked as “required” but it isn’t being passed to the gateway, therefore it’s rejected.
To resolve this, login to your Authorize.Net account and click on the “Account” tab. Next, click on the “Payment Form” link within the Transaction Submission Settings section. On the Payment Form page click on “Form Fields”. Ensure no fields are checked as “required”. Give handles required fields on the donation form side. It is not necessary for any of the fields to be required within Authorize.Net.
No. We migrated the Give Authorize.Net add-on away from the MD5 approach quite a while ago because it was never a very secure or reliable method to capture events from the gateway.
That’s the simple answer. For full details, here is the response from our Head of Product:
MD5 Hash Deprecated Explanation
We no longer use any functionality of the MD5 Hash feature from Authorize.Net since we moved to using the Webhooks API. The MD5 Hash feature was used alongside with Silent Post to authenticate that results indeed were coming from Authnet’s API.
If you received an email from Authorize.Net mentioning they deprecated the MD5 Feature. Please upgrade to the latest version of the Authorize.Net gateway to ensure you’re using the Webhooks API rather than the Silent Post API.