Authorize.net (SIM) is a credit card processing merchant that allows for online card payments through Eventsforce. Eventsforce has an existing integration with Authorize.net, therefore all that is required is an account with Authorize.net. A different Authorize.net account can be used for each event in Eventsforce.

In order to accept online credit card payments via the Authorize.net payment gateway, the “Authorize.net (SIM)” gateway must be included as part of your Eventsforce license. For more information, please contact your account manager or support@eventsforce.com.

You will first need to contact Authorize.net directly and obtain a merchant account. This can be done through the Authorize.net website. 

Authorize.net will provide a username and password for logging into their Merchant Interface. You can log into Authorize.net by visiting the Merchant Interface and entering your Authorize.net Username and Password.

Effective August 15, 2019, Authorize.net requires that a relay response URL be added to your Authorize.net account.  If no relay response URL is added, the transactions will fail. Each client will have a unique URL, as the URL uses the domain and account names. 

The format of the relay response URL is:

https://<domainName>/<accountName>/frontend/xt/xtProcessAuthorizeSIM3.csp 

The “domainName” is the customer's custom account domain OR "www.eventsforce.net" without the quotes and “accountName” is customer's account name. 

Note: If using a custom account domain, use your custom domain instead of “www.eventsforce.net” for the ‘domainName’. 

Add the relay response URL by taking the following steps:

In order to link your Authorize.net account with your Eventsforce event, you will need these two pieces of information:

These credentials can be found in Authorize.net using the steps below:

Your ‘API Login ID’ will be displayed on the page. For security reasons, you cannot view your ‘Transaction Key’. Instead, you must generate a new one. To do this you will need the ‘Secret Answer’ to the system-generated ‘Secret Question’. An API Login ID will be a 12 digit string of characters and number, for example “u8YNx36lpS21”.

Once you have obtained your 'API Login ID' and 'Transaction Key' from the merchant interface, you can then enter those credentials into Eventsforce. These credentials must be entered for each event that should be linked to this specific Authorize.net account. Authorize.net credentials do not copy when cloning an event. The following steps need to be taken in your event:

Note: You may choose to set your Authorize.net account to “Test mode” for testing. While in “Test” mode, submitted transactions are not actually processed. To switch to “Test” mode, log into the Authorize.net merchant account, navigate to “Account”, then select “Test Mode” in the ‘Security Settings’ area. 

The Authorize.net (SIM) gateway is now linked to Eventsforce. Additional testing is strongly recommended to ensure a successful integration.

When testing through Eventsforce, you will need to go through a live registration on the event website:

If an error message is encountered during this process, you can search for the error message for more information in the Authorize.net knowledge base.

Note: If you are not directed to the Authorize.net page after clicking “Pay Now”, your Authorize.net credentials may be incorrect. If the credit card payment failed, you can learn more about why in our “Why did the credit card payment fail?” article.

For your reference, you can use the following test credit card numbers when testing your Authorize.net payment gateway. The expiration date must be set to the present date or later: