Premium version settings

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

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 testing it first on a sandbox environment select Sandbox, so you can try the configuration and if the plugin is working correctly.

To work in Sandbox mode it is necessary to create an account on developer.authorize.net. Production and Sandbox accounts are two different accounts, and it won’t be enough only to 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.

In order to test the plugin configuration, enable Sandbox mode as explained above then go on 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.

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

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 univocal key used to authenticate requests to Authorize.net. Access your registered account on Authorize.net and recover this information in the section API Login ID and Transaction Key:

You will have to enter these details in YITH > Authorize.net > Credit Card Payment:

Request mode

If the admin selects the “Redirect” value, users will be redirected to the Authorize.net page to complete their orders. In the opposite case, that is using API keys, their purchase can be completed on the same page without having to redirect.

This option allows storing of credit card data used by users so that they are not bound to enter them manually during the next checkout.

If this option is enabled, a section in the user’s “My Account” page will be automatically created. Here users can check which credit cards they have associated with their account and, if they want to, delete the ones they no longer need to use.

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

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

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

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

In the credit card settings, you can choose how the transactions have to be handled. Go to YITH > Authorize.net > Credit Card Settings > Transaction type. You will be able to choose from two available methods:

• Authorize & Capture: this will let you authorize and capture the payment immediately.
• Authorize only: this will let you 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 time expires after 30 days, so, all authorized transactions that are not captured within that time, will change to Expired and the funds will not be transferred.

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

You can customize the style of the credit card section. Just 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. In order to enable eChecks, you can go to YITH > Authorize.net > eCheck and enable the related option.

You will have to enter the Login ID and Transaction key as well (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 can also enable the Debug log if you need to.

To see if it is working well, check if, 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 have the same behavior as standard Authorize payment mode.

Authorize.net enables also an option for automatic refunds from WooCommerce. In order to do it, you have to go to the “Order details” page of the order you want to refund and click on “Refund”. Now you can specify the amount you intend to refund and click on Refund via Authorize.net.

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

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