Information security is critical to our business. We work to protect the security of your information during transmission by using Secure Sockets Layer (SSL) software, which encrypts information you input. We store information gathered on secure computers located in a locked data center. The number of employees involved in the management of the data center that have physical access to these computers is limited. We use firewalls and other security technology to prevent our computers from being accessed by unauthorized persons.
We also require that any personally identifiable consumer information sent to us by you be encrypted using SSL encryption.
Short for Secure Sockets Layer, a protocol developed by Netscape for transmitting private documents via the Internet. SSL works by using a public key to encrypt data that's transferred over the SSL connection. Both Netscape Navigator and Internet Explorer support SSL, and many Web sites use the protocol to obtain confidential user information, such as credit card numbers. By convention, URLs that require an SSL connection start with https: instead of http:
Authorize.Net Merchants and Transaction Security
Authorize.Net is committed to helping merchants minimize their risk of fraudulent transactions. As part of our ongoing effort, Authorize.Net continually works to inform and educate merchants on our available fraud detection tools and provide recommendations on the features that are available to better protect themselves from fraud and security compromise.
At a system level, Authorize.Net has several anti-fraud features available:
Address Verification System - AVS is a verification system that compares the billing address information (Street Address and Zip Code) provided by the customer online with the billing address on file at the credit card issuing bank.
CVV2 - is a three-digit security code appearing in reverse italic at the top of the signature panel on the back of the card. Implementation of this feature requires the user to enter the
CVV2 code when making a purchase, helping to confirm that the user is the authorized cardholder.
Referrer URL - This feature allows a Merchant to designate the URL(s) from which
Authorize.Net allows a transaction to take place. The URL must be listed as a "Valid
Referrer URL" in the "Manage URLs" portion under "Settings" in the Merchant Interface. Through regular communications such as email, Web site and Merchant Interface changes, Authorize.Net has also advised
Merchants on additional actions they can take to detect, prevent and manage fraud:
Actively use the Address Verification System (AVS) and the CVV2 features listed above
Change password regularly and use alphanumeric characters
Monitor transaction batches daily prior to settlement and look for suspicious transaction activity