Connecting your Authorize.net Payment Gateway to your Eventsquid account
To connect your Authorize.net Payment Gateway to your Eventsquid account, you will need:
- The API Login and Transaction Key from your Authorize.net account
- Access to the Payment Form Fields set in your Authorize.net account
Check with your organization’s Authorize.net administrator to see if you already have a Transaction Key generated and in use for your API Login. If you do, you do not have to generate a new one.
Locating Information Within Authorize.net
API Login and Transaction Key
1. Sign into your Authorize.net account and click the ACCOUNT tab. Under the ACCOUNT tab, click on “API Credentials & Keys” in the Security Settings section.
2. In the API Credentials & Keys section, you will see your API Login ID. Make note of it. You then need to generate a Transaction Key. Enter your secret answer and click the radio button to the left of “New Transaction Key” next to obtain then click “Submit”.
Make sure you record the Transaction Key in a safe place – you will not be able to look up that Transaction Key again in Authorize.net (you would have to generate a new one).
Payment Form Fields
You will need to align your Payment Form Field settings in Authorize.net with the settings within Eventsquid.
1. Sign into your Authorize.net account and click the ACCOUNT tab.
2. In the Settings area, click Payment Form under Transaction Format Settings
3. Click Form Fields under Payment Form
Configuring your Eventsquid Account for Authorize.net
In Eventsquid, from your main dashboard click on the MANAGE ORGANIZATION tab. Then click Payment Processing. Click ADD and choose Authorize.net.
Give the account a nickname (e.g., Authnet Corporate, etc) and click Add.
Enter the API Login and Transaction Key from steps above.
This will reveal additional settings.
VERY IMPORTANT - Your settings in the Authorize.net FORM FIELDS section must match your settings within Eventsquid otherwise your transactions may FAIL.
Go to your Form Fields settings in Authorize.net (see Payment Form Fields above).
- The FORM FIELD settings in Authorize.net are a bit tricky. VIEW means show to the person checking out and EDIT allows the person to enter data into the field being presented. If you want to ASK FOR a particular field, ensure both VIEW and EDIT are selected.
- If you require a set of fields, ensure REQUIRED, VIEW and EDIT are all checked
- Through Authorize.net's API which is used for integrations like the one with Eventsquid, the form fields can only be specified in sets meaning there isn't granular control. For example, you cannot require "Billing Address" and leave out "Country".
|Card Code||Card Code||Authorize.net always asks for the card code. You just set whether this is required (recommended) or not|
|Customer Billing Information||Billing Address||For Billing, Authorize.net does NOT recognize COMPANY, FAX or CUSTOMER ID in the integration so do not require those fields.|
|Shipping Information||Shipping Address||For Shipping, Authorize.net does NOT recognize COMPANY so do not require that field.|
|Email (under Customer Billing Information)||Email Address|
|Security Code||Enable Captcha|
Here is a mapping of Authorize.net fields to the settings within Eventsquid. The checkboxes in Authorize.net of "View" and "Edit" correlate to the Eventsquid setting "Ask For". The checkboxes in Authorize.net of "Required" correlate to the Eventsquid setting "Make Required".
Each section is further explained below.
Please be sure not to set the unsupported form fields to Required otherwise transactions will fail.
The credit card code (cvc) will always be asked for by Authorize.net so View and Edit should be checked in Authorize.net. If you require the card code (recommended), check Required in Authorize.net and "Required" next to Card Code in Eventsquid.
The registrant will see this on the payment form.
For Billing Information, Authorize.net allows through their API the following fields to be presented as a set:
Therefore, in Eventsquid if you select "Ask For" next to Billing Address, all of the fields above will show on the form. If you select "Make Required", all of the fields above will be required.
For Shipping Information, Authorize.net allows through their API the following fields to be presented as a set:
Therefore, in Eventsquid if you select "Ask For" next to Shipping Address, all of the fields above will show on the form. If you select "Make Required", all of the fields above will be required. If you also ask for Billing Address, the "Shipping Address different than Billing Address will appear.
Email Address will be presented within Billing Address above. If Email Address is asked for/required and Billing Address is not, email address will be asked for below the credit card number.
The option under "Security Code" within Authorize.net correlates to "Enable Captcha" within Eventsquid. When enabled, this will be presented on the payment form.
Pay by eCheck/Bank Account
You may offer eCheck payment (Bank Account, ACH) through Eventsquid provided you have that feature available though your Authorize.net account.
First, check your Merchant Profile within your Authorize.net account
Once confirmed you can set "Enable pay by Bank Account" within Eventsquid. Then customers will have the following option upon checkout.
Test Mode / Sandbox
If your Authorize.net account is brand new to you, you can test the connection. You will need to put your Authorize.net account in “test” mode* AND set your configuration in Eventsquid to test mode. Run through a registration and use the test credit card number displayed on the Eventsquid Payment Processing screen (pictured above). You will only have to run this test once. Set both back to live mode and you are ready to roll!
* If your Authorize.net account is established and in use for payment processing outside of Eventsquid, you should not put your Authorize.net account in test mode. You can talk to your Authorize.net administrator or Authorize.net by establishing alternate account profiles if you need to segment your business.