Sign in or reset your password to view additional content, start a chat or submit a support case.
Can't sign in? View other options to receive support.
Your welcome email includes a link that begins the account activation process. After activating your account, you will be logged in to the Merchant Interface. This interface provides administrative access for managing and protecting your Authorize.net payment gateway account. Through the Merchant Interface (https://login.authorize.net), you can:
The person with primary responsibility for the payment gateway account should complete the account activation process. This process establishes the account owner. The Account Owner role is one of several user roles that can be established for your account. After activation, you can add more users and assign them the Account Owner role or other roles as needed.
Account owners can access all of the Merchant Interface features and functionality. They are responsible for managing the users of the account and for properly configuring the payment gateway account's processing and security settings.
By default, your account is in Test Mode, which allows you to submit test transactions to validate that your Authorize.net compatible payment solution can connect to the account, without submitting an actual charge. Work with your payment solution developer to test your connection to Authorize.net. After your connection is validated, you can disable Test Mode to begin processing live transactions. To disable Test Mode, click the orange banner at the top of the Merchant Interface.
You can also enable Test Mode to temporarily stop payment processing, if you notice suspicious activity on your account.
To turn Test Mode on or off:
Remember to turn off Test Mode when you are ready to process live transactions.
To connect your payment solution to Authorize.net, generate an API Login ID, a Transaction Key, and a Signature Key (optional), and add these API credentials to your payment solution. The API credentials are unique to your Authorize.Net account and are used to identify and validate the payment solution for transaction processing.
It is crucial to store your API Login ID, Transaction Key, and Signature Key securely. Do not send these credentials through email. As a best practice, create an Account Administrator user for your web developer. This user can generate the API credentials and should be removed once the web developer has finished configuring the payment solution.
Do not configure your payment solution to use your Merchant Interface login ID and password. These credentials are only for signing in to the Merchant Interface and should not be shared with anyone.
After you have created your API Login ID, you may not change it in the Merchant Interface. To reset your API Login ID, contact Customer Support.
Important: Check Disable Old Transaction Key or Disable Old Signature Key if you suspect that your current keys are being used fraudulently, and you need to disable the keys immediately. Otherwise, the previous Transaction Key or Signature Key remain valid for 24 hours to provide time to change the keys in your payment solution.
The following features of Authorize.net help prevent fraudulent transactions:
The Address Verification Service (AVS) is a system provided by issuing banks and card associations to help identify suspicious payment card activity for e-commerce transactions. AVS matches portions of the customer's billing address, as provided by the merchant, to the billing address on file with the issuing bank. Authorize.net then accepts or rejects the transactions according to the settings that you specify.
The default AVS settings are set to reject transactions when the billing street address or ZIP code do not match the issuing bank's records. International cards typically do not support AVS, and they are typically rejected by default.
Review and configure your AVS settings to suit your business model. Contact your Merchant Service Provider to discuss AVS best practices for your business.
To review and edit your AVS settings:
Click Help in the top right corner if you have questions about the response codes.
Card Code Verification (CCV) compares the card code submitted by the customer with the card code on file with the issuing bank. The card code appears at the end of the signature panel on the back of the card, or for American Express cards, on the front of the card just above the end of the credit card number.
Card codes provide extra security against unauthorized credit card transactions. Because card codes cannot be stored in payment solutions, checking the card code helps to ensure that the customer authorized the transaction. You can use CCV to better decide whether to accept or reject credit card transactions.
Contact your Merchant Service Provider to discuss CCV best practices for your business.
To review and edit your CCV settings:
Click Help in the top right corner if you have questions about the response codes.
The Daily Velocity Filter is a tool that allows you to specify a threshold for the number of transactions allowed per day. All transactions exceeding the threshold in that day are flagged and processed according to the actions that you specify. It is a useful tool for preventing high-volume attacks that are common with fraudulent transactions.
To configure the Daily Velocity Filter:
Click Help in the top right corner if you have questions about the filter actions.
Authorize.net offers the Advanced Fraud Detection Suite, a set of customizable, rules-based filters and tools that identify, manage, and prevent suspicious transactions.
For more information on Advance Fraud Detection Suite, click Tools on the main toolbar, then click Fraud Detection Suite.
Use the following settings to customize your Authorize.net account for your business.
Set your Authorize.net account to use the time zone in which your business is located. This setting enables transactions, statements, and reports to display timestamps in your local time zone, and ensures that your transaction cut-off time is accurate.
To update the time zone:
The Transaction Cut-Off Time setting specifies the daily cut-off time for batched transactions to be submitted to your processor for settlement. Transactions submitted after the cut-off time are sent to the processor after the cut-off time the following day. The default transaction cut-off time is 3:00 p.m. Pacific time.
To update the transaction cut-off Time:
Important: Allow up to 24 hours for the transaction cut-off time to update.
The User Administration feature enables an account owner to create unique user accounts with distinct login IDs and passwords for employees who need access to the Merchant Interface. You can also customize permissions for each user account to match each employee’s job responsibilities—helping you to keep transaction and account management activities in the Merchant Interface separate and streamlining your transaction management processes. By default, the person who activates your payment gateway account is the account owner. This account will be the only user account until you create additional accounts.
To create additional user accounts:
The Virtual Terminal enables you to submit payment transactions manually through the Merchant Interface. Use the Virtual Terminal if you accept payments for mail order/telephone order (MOTO) sales. To submit a payment card transaction for automatic settlement using the Virtual Terminal:
Important: You can also add/delete specific fields on the Virtual Terminal payment page for the information you wish to collect at the time you process the transaction. Simply click the checkbox under View/Edit for the field you wish to have present. You can also click the check box under Required for information you want collected before a Virtual Transaction can be processed.
If you use CCV to verify the customer’s card code, click Virtual Terminal Settings at the bottom of the Virtual Terminal, check Card Code in the Required column, and click Submit.