Premium version settings

After installing and activating the plugin, go to YITH > Authorize.net > Credit card payment settings, enable this payment gateway on your site and choose between a live or test environment.

If you’re ready to start with the gateway live, select Live and refer to this page for the settings.

If, on the other hand, you prefer to test it first in a sandbox environment, select Sandbox so that you can try out the configuration and see if the plugin works correctly.

To work in Sandbox mode, you must create an account on developer.authorize.net. The production and sandbox accounts are two different accounts, and it won’t be enough to simply enable this option to switch to sandbox mode.

The admin will also need to create a sandbox account here: https://developer.authorize.net/hello_world/sandbox/ and set Login ID and Transaction key for this account in the plugin settings.

To test the plugin configuration, enable Sandbox mode as explained above, then proceed with your test purchase and select Authorize.net payment mode during checkout.

To test the credit card method, you can use some randomly generated card numbers available on this page.

If the test was performed locally, the system will generate an error, otherwise, you will be redirected to the My Account page if it was successful or to the Checkout page if there was an error (incompatibilities between currency and payment method are common).

NB: Check the order status during and after payment in WooCommerce panel. During payment, the order status is labeled as pending payment; once the order has been completed, its status will change to processing or completed.

Once you install and activate the plugin, you can go to YITH > Authorize.net > Credit Card Payment to and enable this payment gateway on your site. You will be able to choose between Live or Test environment at first.

To read more about Sandbox environment please, refer to this page.

If you’re ready to start with the gateway live, then, select Live and configure the following options.

The transaction key is the unique key used to authenticate requests to Authorize.net. Access your registered account on Authorize.net and retrieve this information in the API Login ID and Transaction Key section:

Now add these details in YITH > Authorize.net > Credit Card Payment:

Request mode

By selecting the Redirect option, users will be redirected to the Authorize.net page to complete their order. In the opposite case, that is by using API keys, their purchase can be completed on the same page without any redirect.

This option allows users’ credit card details to be saved so that they do not have to re-enter them the next time they check out.

When this option is enabled, a section is automatically created on the user’s ‘My Account’ page. Here, users can check which credit cards they have associated with their account and, if they wish, delete those they no longer need.

Please note: Enabling CIM is only available when using API mode.

The option “Enable itemized transaction” enables product registration during order transactions so that in invoices, users will see not only the total of their order but also a list of the products in it and their individual prices.

Purchase details are also shown to users during the checkout process. To check if the plugin is functioning, you should verify if the list of purchased products shows in order details during the transaction (when “Redirect” mode is set) or in the “Reports” section on your Authorize.net account.

This allows the registration of the items in the cart during the transaction, with a maximum of 30 items.

The credit card settings allow you to choose how transactions are handled. Go to YITH > Authorize.net > Credit card settings > Transaction type and choose from two available methods:

• Authorize only: this allows you to authorize the transaction but not charge your users. You can review the order or any other details and then capture the payment from your Authorize.net account.
  
  Please note: the authorization period expires after 30 days, so, all authorized transactions that are not captured within this time will change to Expired and the funds will not be transferred.
• Authorize and capture: this allows you to immediately authorize and capture the payment.
  

For more information about the Authorization Only transaction, please, refer to the official documentation.

To customize the style of the credit card section go to YITH > Authorize.net > Credit card settings and scroll down to the Customization section:

You will be able to change the following details of the credit card box and show all or just some of the supported credit card logos:

• Title
• Description
• Order button label
• Show credit card icons

eCheck is a payment method that allows users to make payments by entering the identification code of their bank or merchant bank and their bank account number. To enable eChecks, you can go to YITH > Authorize.net > eCheck and enable the related option.

You will also have to enter the Login ID and Transaction key (please check this page for more info), and choose whether to enable itemized transactions for eChecks too (please refer to this page for more info about this option).

You also have the option to enable the Debug log if needed.

To see if it is working well, check that once the payment request has been sent, the order goes to “Processing” or “Completed”, depending on whether the shipping is included or not.

Once this new payment model has been enabled, it will be available to users during checkout. All options in eCheck mode behave in the same way as the standard Authorise payment mode.

Authorize.net also provides an option for automatic refunds from WooCommerce. To do it, go to the “Order details” page of the order you want to refund and click on “Refund”. You can then enter the amount you want to refund and click on Refund via Authorize.net.

It might happen that refunds are not processed and an error is returned. This usually happens because the transaction must be set as “settled” by Authorize.net before a refund can be issued. In case of errors, by refreshing the “Order details” page, you should see a note with the reason for the failed refund; in any case, a note will be added to the log files.

If you partially refund an order, Authorize.net will create a refund; if you fully refund an order, Authorize.net will void the order, which looks like this: