To set up Authorize.net credit card payment integration, the following steps must be followed:

1. Go to Configurations > Payment Methods > + New Payment Method

2. Select "AuthorizeNet" and name the payment method - in this case we have named it "Credit Card" then click "Save"

3. Get the API Login ID and the Transaction Key from the API Credentials & Keys section which can be accessed in Settings (Transaction Key can be obtained by answering the secret question)

4. Enter the API Login ID and the Transaction Key in the respective fields. Name the Server "live" and uncheck "Test Mode", then click "Update" - There is the option to manually capture the payment or Auto Capture the payment depending on whether the "Auto Capture" button is switched on or off.  

Auto Capture button: this button allows you to capture payment automatically, when it is on. If this button is off, you have to go to the orders and manually capture payments.

Active button: this button allows you to activate or deactivate a payment method.

Use to Mark Orders Paid button: when this button is on, payment information will not be asked when you mark orders as paid. 

Payment can now be taken for an "Approved" transaction by taking the following steps:

1. Go to the order and click on +New Payment

2. Enter credit card information and click on "Apply Payment" and the payment will be taken from the customer and applied to the invoice

Note: Credit card numbers will be saved on Authorize.NET’s Customer Information Manager (CIM) which is  Payment Card Industry Data Security Standard (PCI DSS) compliant.

Authorize.Net and Authorize.Net CIM defined

Authorize.Net is one of the most popular payment processors around for a reason: they offer easy, safe, and affordable credit card and eCheck processing. This Authorize.Net CIM payment gateway integration lets you take advantage of several features offered by Authorize.Net, such as customer profiles, card tokenization, and eCheck processing.

The CIM version of the Authorize.Net Payment Gateway extension allows you to keep the customer on your site for the checkout process, allowing you maximum control over checkout so that you can test and implement the most effective experience for your store. An SSL is required for PCI compliance due to the direct checkout to ensure that your customers’ credit card information is secure.

Did this answer your question?