Authorize.Net is arguably the most popular payment gateway to use to process credit cards in North America. As such, you'll of course find this as an out-of-the-box payment gateway. This article will show you the steps required to get Authorize.Net setup in your store.
The following prerequisites will be necessary to accomplish the goals of this article:
- Have access to your Hotcakes store administration
- Be familiar with payment gateways in Hotcakes
- Have a developer or production account with Authorize.Net
Before you proceed with this article, you should first learn about and be familiar with how to use payment gateways in Hotcakes. This article will only go into detail on how to enable and configure the gateway itself, and not the rest of the payment gateway configuration.
Authorize.Net Payment Gateway
Before you can do anything else, you'll need to create an account with Authorize.Net. This will give you information that you'll need before you can configure the payment gateway to work.
Once you have your account, you'll want to sign in so that you can gather a few pieces of information.
From the Authorize.Net accouunt home page, choose Account.
Next, find and click on the API link shown below. This is where you'll find the connection information we're looking for.
You'll immediately see your Login ID displayed, but you may need to generate your transaction key. Copy both values to a safe location temporarily, or copy and paste them to the Hotcakes configuration view discussed below immediately.
The settings in Hotcakes will require the values we just located above. You'll see the Hotcakes configuration below. If you're not sure how to get there, please review the payment gateway documentation.
|Merchant Login ID||This is the merchant ID you copied from the Authorize.Net control panel discussed in the steps above.|
|Transaction Key||This is the transaction key you generated and copied from the Authorize.Net control panel discussed in the steps above.|
|Send Authorize.Net E-Mail to Customer||Hotcakes will already send your customers a receipt via e-mail. However, if you'd like for a receipt to also be send from Authorize.Net, you'd check this setting.|
|Developer Mode||When checked, the payments will go to the Authorize.Net sandbox URL. These payments will not transfer any actual money. In production, this setting should be unchecked.|
|Test Mode||When checked, this setting will add the "x_test_request" parameter to the requests sent to Authorize.Net. This indicates that the transaction is a test, regardless of the gateway being in developer mode or not.|
|Debug Mode||This setting will add a larger level of detail when checked. This is helpful for when you need to troubleshoot payment issues in your store. You should only keep this setting enabled for short periods of time and disable it as soon as you have what you need.|
Authorize.Net Account: Test Mode
Whenever you're ready to accept payments in production, don't forget to turn off "Test Mode" in the Authorize.Net control panel. You can see where to do this from most pages. It's highlighted in the orange bar below.
Testing: Captures and Voids
When you're testing this gateway using "test" or "developer" modes, you won't be able to test voids or captures. These are disabled by Authorize.Net. Please see the links below for more information.
- Authorize.Net: How do I test voiding an authorization?
- StackOverflow.com: Test mode won't process an authorization capture