• Unzip the extension package file into the root folder of your Magento 2 installation.
• Connect to SSH console of your server:
  • Navigate to the root folder of your Magento 2 setup

  • Run command as per below sequence,

    php -f bin/magento setup:upgrade

    php -f bin/magento module:enable Magedelight_Megamenu

    php -f bin/magento setup:static-content:deploy

• Flush store cache
• log out from the backend and log in again

Hourly Velocity Filter

You can specify velocity of the transactions per hour. It allows you to specify a threshold for the number of transactions allowed per hour. All transactions exceeding the threshold in that hour will be flagged and processed according to the selected filter actions. You can see available filter action options in below image.

Suspicious Transaction Filter

The Suspicious Transaction Filter is a proprietary tool developed by Authorize.Net Risk Management team to identify suspicious transactions. Based on a vast knowledge base of transaction behaviors and fraud detection analysis, the Suspicious Transaction Filter provides enhanced fraud detection for your account.

Transaction IP Velocity Filter

You can specify the number of maximum transactions allowed per IP address per hour. It allows you to specify the maximum number of transactions allowed from the same Internet protocol (IP) address per hour. If your account receives more transactions from the same IP address in an hour than the threshold you set, all exceeding transactions received that hour will be flagged and processed according to the selected filter action. You can see available filter action options in below image.

Enhanced AVS Handling Filter

The payment gateway provides comprehensive Address Verification Service (AVS). It is a tool designed to assist in identifying potentially fraudulent credit card transactions. For every credit card authorization, AVS compares the billing address and ZIP code provided by the customer at the time of purchase, to the address and ZIP code on file at the card issuing bank. AVS then returns a response code indicating the results of the comparison.

Enhanced CCV Handling Filter

The payment gateway provides comprehensive code verification services. Card Code Verification (CCV) compares the three- or four-digit card code submitted in a transaction with the card code on file at the card issuing bank. Based on the results of that comparison, the bank returns a CCV response code. 

Amount Filter

The Amount Filter allows you to specify a lower limit and/or upper limit for your transactions. Transactions that are submitted with an amount less than your lower limit or greater than your upper limit will be flagged and processed according to the selected filter action. You can see available filter action options in below image.

Shipping Address Verification Filter

The Shipping Address Verification (SAV) Filter verifies that the shipping address received with an order is a valid postal address or not. 

IP-Shipping Address Mismatch Filter

The IP-Shipping Address Mismatch Filter compares the order’s originating IP Address with the shipping address provided. This helps to determine whether or not the order is shipping to the country in which it originated. You can see available filter action options in below image.

Regional IP Address Filter

The Regional IP Address Filter allows you to designate regions or countries from which you do not want to accept transactions. You can choose to process normally and report; hold for review; or decline orders based on an entire geographic area, or on a country-by-country basis.

To configure the filter actions based on an entire region, click Edit Regional Settings and then select the radio button that corresponds to the action you want to select.

To configure filter actions for each country in a region, click Edit Regional Settings, then click Expand Geographic Region. A list of all countries in the region will display. Select the radio button that corresponds to the action you want to select for each country, then click Save when finished.

Shipping-Billing Mismatch Filter

This filter permits you to compare the shipping and billing addresses provided by the client. If the two addresses do not match, the transaction is flagged and processed according to the selected filter action. 

Authorized API IP Addresses

The payment gateway allows IP address validation to access APIs. API can not be accessed from other IP address. You can configure a list of authorized server IP addresses from which API transactions will be accepted by the payment gateway. Any API transaction submitted from an IP address not included on this list will be rejected. 

IP Address Blocking

An advanced IP blocking functionality is available with Payment Gateway. IP Address Blocking allows you to block transactions submitted from IP addresses known to be the source of suspicious or fraudulent transactions. No one can access from blocked IP address.

• Enabled: This can enable/disable the Authorize.net CIM Payment method.
• Title: Here you can define the label for Authorize.net CIM Payment method that will display in
  • Payment section of one page checkout.
  • Payment information of order, invoice, credit memo and shipment section.
• API Login ID: Merchant can define API Login Id that is associated with current Authorize.net merchant account.
• Transaction Key : Merchant can define Transaction Key that is associated with current Authorize.net merchant account.

• Enable Accept.js: Admin can enable the Accept.js if he wants to transfer the payment data directly from client to authorize.net server. (If it is enabled the sensitive data of client would bypass the merchant server)

  Make sure that the URL of your website is SSL certified. To use this feature it is mandatory to get the SSL certificate for your website.

• Client Key: Copy the key from merchant account of authorize.net and enter here.
• Test Mode:Admin can define the mode of Authorize.net CIM Payment method of web shop. Merchant can set either “Yes”/ “No” for this option depends on the environment of web shop (Production or Development).
• Payment Action: Admin can define the payment action that would take on successful order placed by user. Admin can choose,
  • Authorize and Capture: This payment action will directly capture the requested amount from the customer credit card on placing an order from frontend or backend. Invoice will automatically create when user successfully place an order.
  • Authorize Only: This payment action will only authorize the requested amount on the credit card of customer on placing an order from frontend or backend. In this payment action invoice will not be created after order creation successfully. Admin will have to manually create invoice from backend from order management section.
• Gateway WSDL: This options defines the WSDL URL of Authorize.net CIM Payment method API. Depending on the API Type option selected by admin, this option will have different value,
  • API Type Selected “Xml” will have this value https://api.authorize.net/xml/v1/schema/AnetApiSchema.xsd
  • API Type Selected “Soap” will have this value https://api.authorize.net/soap/v1/Service.asmx?WSDL
• Gateway URL: This option defines the Gateway URL for live mode of Authorize.net CIM payment method API. Depending on the API Type option selected by admin, this option will have different value
  • API Type Selected “Xml” will have this value
    https://api.authorize.net/xml/v1/request.api
  • API Type Selected “Soap” will have this value
    https://api.authorize.net/soap/v1/Service.asmx
• Test Gateway URL: This option defines the Gateway URL for Test mode of Authorize.net CIM payment method API. Depending on the API Type option selected by admin, this option will have different value
  • API Type Selected “Xml” will have this value “https://apitest.authorize.net/xml/v1/request.api”.
  • API Type Selected “Soap” will have this value “https://apitest.authorize.net/soap/v1/Service.asmx”.
• Accepted Currency: This option defines the currency that merchant want to accept with Authorize.net CIM payment method.
• Debug: This option defines the debugging mode of Authorize.net CIM payment method. Admin can choose “Yes / No” depending on the Production / Development environment if web site. Normally this option should only enabled for development environment.
• Email Customer: This option will define the email notification generated from authorize.net payment gateway when transaction will successfully completed from web site.
• Option value “Yes” of this field will send gateway generated transaction email to customer email address.
• Sort Order: This option defined the sort order of payment method on the payment step on checkout one page of frontend.
• Credit Card Types: This option defines the list of Credit Cards that customer can choose from card selection field on payment section of one page checkout page.
• Credit Card Verification: This field will allow admin to select whether Card Code Verification option should be display or not on payment section.
• Payment from Applicable Countries: This option allow admin to configure Authorize.net CIM Payment gateway for specific countries,
  • By selecting “All Allowed Countries” from this option will make Authorize.net CIM Payment for customers from all the countries.
  • By selecting “Specific Countries” from this option will make Authorize.net CIM Payment method for customers from specific countries.
• Payment from Specific Countries:
  This option will only enabled if “Payment from Applicable Countries” option will set to “Specific Countries”.
  This option will be multi select option so admin can choose one or more countries from this fields for which this payment method will be display on payment section.
• Minimum Order Total: This option defines the minimum order total for which this payment method display on payment section of one-page checkout on frontend.
• Maximum Order Total: This option defines the maximum order total for which this payment method will display on payment section of one-page checkout page of frontend.
• Allow Partial Authorization: This option defines whether merchant would allow customers to place an order who have not balance on credit card for order processing.

• Send Line Items: By configuring this field to “Yes” will display the order items to display in gateway generated emails and also in transaction details page in merchant panel.

• Delete Cards: Admin can edit the merchant details (though it is not a good practice to change). On edit, it is required to delete the saved credit cards manually from Stores->configuration->Sales->Payment Methods ->Authorize.net CIM

  • All saved credit cards details are associated with merchant details. Hence, if merchant edits the details it is required to delete the saved cards because for the authorization merchant details should be matched with saved credit cards. 

    
    

Admin can manage customer cards from customer management section of backend interface. In customer edit section admin can go to the “Saved Cards” tab. Here, admin can able to view all stored cards for each customer, also can add new card as well as edit or delete particular card.

Manage fraud/suspected fraud transactions

Authorize.net merchant account settings: Set up conditions in Authorize.net merchant account for credit card verification and address verification services.

Credit card code verification settings: Login to your merchant account on Authorize.net site and click on Account tab. Under settings go to security settings -> card code verification to manage fraud transactions related to credit card code value.

Admin can accept payment or deny or review the transaction if suspected fraud as per the conditions set in Authorize.net merchant account.

Address verification settings: Login to your merchant account on Authorize.net site and click on Account tab. Under settings go to security settings -> address verification service to manage fraud transactions related address and zipcode.

Admin can accept payment or deny or review the transaction if suspected fraud as per the conditions set in Authorize.net merchant account.

Admin can accept payment or deny or review the transaction if suspected fraud as per the conditions set in Authorize.net merchant account.

• Accept Payment: would approve the process and capture the payment.
• Deny Payment: If the transaction has been denied then, it would void the process.
• Get Payment Update: would update the transaction status in Magento admin as per the action taken on suspected fraud transaction from Authorize.net merchant account.

Manage truthful orders

Admin can see the payment information for specific order like “Credit Card Type”, Credit card number with masked format, total processed amount on the card, card issuer approval code, CAVV Result code, Authorize.net gateway generated transaction id and the currency format in which order was placed.

Authorize.net CIM payment gateway extension by magedelight.com would allow admin to place order on behalf of customer using saved order. It simply means the admin would not need to contact customer for payment information.

As you can see with above screenshot logged in customer have already stored three cards listed. Customer can able to edit each cards information if required, they can also have option to delete particular card.

Customer will also have button to add new card, which will head to add new card form, which needs to filed with customer billing address and card details.

If customer have already saved card with authorize.net CIM, they can use to pay for order at the time of checkout. For checkout on payment step there would be a list of stored card from where customer can select the one from list and pay for order to selected saved card. There is also an option to use other card if customer don’t want to use save card or if customer don’t have any sore card. If card save option is set optional, customer will have choose to save card or not.