Authorize.net Payment Gateway

Are you ready for your own online merchant account? If you are selling a relatively large number of tickets, HoldMyTicket can help you integrate an Authorize.net merchant account with our online sales framework.

Who is eligible for setting up their own merchant account? We can offer this service for any client willing to sign up for a long-term contract. If operating from your own merchant account is something you're seriously thinking about, contact us at any time, and we'd be happy to talk about it. Once you're ready, setting up your Auth.net merchant account to receive sales from holdmyticket.com is a simple process. In fact, you don't have to do very much at all; most of the work is taken care of by the HMT team. Let us know when you're ready to make this transition, and we'll get it set up in no time.

We'll just need the following from you:

Make sure your Address Verification Services settings are the same as ours.

Go to: Account -> Settings -> Security Settings -> Basic Fraud Settings -> Address Verification Service (See #1 in the second image below).
You will see a variety of different options, listed by a code letter.
The only option you want clicked is B, which will reject transactions submitted without a billing address.
If any other options are selected, deselect them now, then click Submit to save the changes.

You can obtain these in your account by going to: Account -> Settings -> Security Settings -> General Security Settings -> API Login ID and Transaction Key (See #2 in the image below).
You will have to enter some security information.
Once you have access to the info, please send it to us at: team@holdmyticket.com. We will set it up with your online sales right away.

Testing

Once you have been notified by HoldMyTicket that your merchant account has been linked and your ticketing fees have been recalculated, you can test to see if transactions are going through.

Enter Authorize.net's Test Mode. Go to Account -> Settings -> Security Settings -> General Security Settings -> Test Mode (See #3 in the image above) and click Turn Test Mode OFF.
Open up HMT and order a ticket for one of your events. Enter the transaction and submit it for payment.
Go back into the Auth.net account, and find the Unsettled Transactions by going to Search/Unsettled Transactions. You should see your test transaction listed there.
Make sure the transaction goes according to the ticket price you have chosen and the agreed-upon fee schedule. If the amount does not seem correct, let the HMT team know ASAP.
When you are finished, click on the transaction ID on the left of the Unsettled Transactions list to bring up the Transaction Details, then click the Void button to eliminate the test transaction.
Of course, let us know if you receive any errors.
IMPORTANT NOTE:
If a transaction is flagged in your Authorize.net account when a sale is processed in our system, our system is set to let the Authorize.net account holder review the transactions manually, which HoldMyTicket will not have access to, only you will. This will not allow the ticket transaction to go through in HoldMyTicket's system even if flagged in your Authorize.net account. As part of their Advanced Fraud Detection Suite, there is an option under your filter settings you will need to have selected, "Authorize and hold for review" or you should turn off flag for review altogether on your account through these settings, as well. Here is a link on Authorize.net's website to help you learn how to further review suspicious transactions that may come through your account.

You're done! Your ticket sales on holdmyticket.com are now going directly into your Authorize.net Merchant Account.

Daily Velocity Settings

The Daily Velocity Filter in Authorize.net is a part of the Fraud Detection Suite that allows you to limit the total number of transactions received per day. All transactions received in excess of your established threshold will be processed according to the filter action you select. Sometimes this can prevent your tickets from selling if there's a cap in place and cause issues with the traffic on your site.

Note: This filter differs from the Transaction IP Velocity Filter in that it tracks only the total number of transactions received per day, not the originating IP address.

The filter status, Filter Enabled, Filter Disabled or Not Configured appears at the top of the page.

Multiple transactions that are part of the same order do not trigger this filter.

To Enable the Daily Velocity Filter:

Step 1: Click the Enable Filter check box at the top of the page. Or, to disable the Daily Velocity Filter, make sure that the Enable Filter check box is deselected. This filter is available to all merchants regardless of whether you are subscribed to AFDS (Advanced Fraud Detection Suite).

Step 2: Enter the maximum number of transactions that should be processed per day in the Transaction Velocity Threshold text field.

Note: To determine an appropriate Transaction Velocity Threshold you might want to evaluate your weekly or monthly transaction processing volume history and calculate the average number of transactions you are likely to process in a day.

Step 3: Click the radio button next to the appropriate Filter Action for this filter.

Process as normal and report filter(s) triggered: "Process as normal and report filter(s) triggered” is one of the four filter action options for handling transactions that trigger one or more Advanced Fraud Detection Suite (AFDS) filters. Transactions that trigger an AFDS filter with this filter action are processed as normal, but are also reported in the Merchant Interface as triggering the filter. This action is useful when testing your AFDS filter settings.
Authorize and hold for review: “Authorize and hold for review” is one of the four filter actions for handling transactions that trigger one or more Advanced Fraud Detection Suite (AFDS) filters. Transactions that trigger an AFDS filter with this filter action are placed in the Authorized/Pending Review state after being successfully authorized by the processor. Once the transactions are in Authorized/Pending Review, you have 30 days to manually review and either approve or void them. We recommend you process these transactions within 72 hours. Any transactions you approve are sent for settlement. If no action is taken in the 30-day period, the transactions will expire. This action is useful if you want to review authorized transactions prior to submitting for settlement.
Do not authorize, but hold for review: “Do not authorize, but hold for review” is one of the four filter action options for handling transactions that trigger one or more Advanced Fraud Detection Suite (AFDS) filters. Transactions that trigger an AFDS filter with this filter action are placed in the Pending Review state. Once in Pending Review, you will have 5 days to manually review and either approve or decline the transaction. Once you approve the transaction, it is sent for authorization. If no action is taken in the 5-day period, the transaction will expire. This action is useful if you want to review transactions prior to authorization to avoid incurring any associated authorization fees.
Decline the transaction: “Do not authorize, but hold for review” is one of the four filter action options for handling transactions that trigger one or more Advanced Fraud Detection Suite (AFDS) filters. Transactions that trigger an AFDS filter with this filter action are placed in the Pending Review state. Once in Pending Review, you will have 5 days to manually review and either approve or decline the transaction. Once you approve the transaction, it is sent for authorization. If no action is taken in the 5-day period, the transaction will expire. This action is useful if you want to review transactions prior to authorization to avoid incurring any associated authorization fees.

Note: In the event that a transaction triggers more than one filter, and each filter is configured with a different action, the most severe filter action will be applied to the transaction. For example, you might configure filter A to decline all triggered transactions, and filter B to authorize but hold all triggered transactions. If a transaction triggers both filters A and B, it will be declined rather than authorized and held for review.

Step 4: Click Save to save your settings or click Cancel to cancel the action.

Your saved settings are applied immediately to all transactions screened by the Advanced Fraud Detection Suite.