Documentation Home »User Guide: Commerce »Payment »Payment Methods and Providers »Authorize.Net Payments Services
3.0 version
You are currently viewing documentation for version 3.0 which is not a long-term support release. The latest long-term support release is version 1.6

Authorize.Net Payments Services

Authorize.Net is one of the world’s most popular payment gateways. It provides services for businesses based in the United States, Canada, United Kingdom, Europe, and Australia. It ensures secure and reliable money transactions and offers a wide range of additional services.

Integration of OroCommerce with Authorize.Net enables you to accept credit and debit cards on your OroCommerce website.

While your business must be based in one of the aforementioned countries, you can accept payments from the buyers worldwide.


Note that to accept card payments, business must have a merchant account. This is a special bank account to which payments are transferred as soon as they are received from buyers. In next step, money is transferred from the merchant account to your regular bank account, from which you can withdraw it.

You may acquire a merchant account on your own or obtain it from Authorize.Net.


See Prerequisites for Authorize.Net Integration topic for pre-integration steps. See Authorize.Net Integration topic for detailed integration steps.


OroCommerce server never stores buyer’s sensitive payment information (complete card number, expiration date, and cvv code), this information is directly sent to Authorize.Net.

As Authorize.Net servers are PCI DSS complaint, this ensures that you provide to your buyers the security of payments that meets requirements of the controlling organizations.

OroCommerce uses Authorize.Net Accept.js library to process buyer’s sensitive information in their web browser.

Transaction response from the payment gateway also does not contain sensitive information about a buyer’s card. It serves as an identifier of the initial authorization that is solely handled by the payment gateway.


Note that the Authorize.Net payment method runs only via HTTPS for security reasons. The JS library uses HTTPS to ensure that the connection is secure, and all passed data is encrypted. In case of non-https connection used, the payment method gets disabled.

Browse maintained versions:

You will be redirected to [title]. Would you like to continue?

Yes No