How To Configure Authorize.Net Emulation

Authorize.NET Emulation is one of the payment gateways that accept credit card payments through Method’s Payments App. You can use Authorize.Net Emulation if you’re using any credit card processor that uses the same API as Authorize.NET. In this article we will cover the installation and configuration of Authorize.Net Emulation step by step.

Main Features of Authorize.Net Emulation

Real-Time Transactions

This payment gateway allows you to accept credit card payments without needing to be inside QuickBooks.

Eliminate Manual Processes That Lead to Error

Reduce the time of your Sales department. Your sales department doesn’t require to make phone call to get the credit card numbers, writing them down, passing them to a different department and getting them entered into your QuickBooks account.

Streamline Your Workflows

Send invoice to customer with a link to make an online payment through their customer portal. Your customers will be able to pay easily and securely through the Authorize.NET Emulation payment gateway.

Please note that Authorize.Net Emulation support only Payment Process. It does not support advanced features such as refunds, voids and capturing charges from WooCommerce.

You can find the Authorize.Net Emulation to WooCommerce > Settings > Checkout. To use this gateway you must have to enable this and enter the Gateway URL and API credentials provided to you by your payment processor.

WooCommerce Authorize.Net AIM Emulator Settings

Extension Settings

  • Enable / Disable – Put tick mark on the check box to Enable the gateway to use this by customers to checkout.
  • Title – Enter a title here that will determine what users see during checkout.
  • Description – Enter a description here that will determine what users see during checkout. You have to use only HTML. If you enable Test mode during USA ePay API settings this section will also display a notice along with test credit card numbers.
  • Card Verification (CSC) – If you enable this your customers require to enter their CVV / CV2 (Card Security Code) when checking out.
  • Transaction Type – From the drop down menu you have to choose either “Charge” or “Authorization”. By default you will see “Charge”.
  • Accepted Cards Types – In this field you can display the card logos during checkout.
  • Debug Mode – If you enable this, it will mean that you are having issues correctly processing transactions. You can save either log API requests / responses directly to the checkout / thank you page or both to the WooCommerce Error Log. You can find the WooCommerce Error Log WooCommerce > System Status > Logs.
  • Environment – From the drop down menu you can select either “Production” or “Test”. If you select “Test” it will send transactions to your Authorize.Net Sandbox Account. Note: This is not the “test mode” that is listed under your Authorize.Net account.  You requires a separate login. For test account you have to create a developer account. When your account creation will complete you can enter a separate API key and PIN for your test account.
  • Payment Gateway URL – This is the Gateway URL of the Authorize.Net gateway processor. You can change this URL to a different processor that allows Authorize.Net emulation.
  • API Login – The API Login for your Authorize.Net account (Test or Production). Follow the steps to get this. If you’re using Authorize.Net Emulation gateway, then this will be the API Login provided to you by your payment processor.
  • Transaction Key – The API Transaction Key for your Authorize.Net Emulation account (Test or Production).

Read More here.

Leave a Reply