Creating an Authorize.Net Clearing Model

Authorize.Net has two types of accounts that can be used as a clearing method in uStore: a merchant account (real and/or live) and a sandbox account (developer/testing).

It is recommended that you use a sandbox account for testing until you are ready to switch to the merchant account to process live transactions.

Your merchant account will need to include the payment gateway option to connect to the Authorize.Net platform. For more information, see http://authorize.net

Notes:

·     Authorize.net does not support any top-level domain name with more than 6 characters. The top-level domain names are the characters that follow the last period in the domain name.

For example: https://training.xmpie.sandbox will not work because "sandbox" is more than 6 characters. However, https://training.xmpie.store will work as "store" is less than 6 characters.

This is also true for shorter domain names, that do not contain a subdomain name – https://xmpie.sandbox will not be allowed but https://xmpie.store will.

·     The "Authorize and Hold for Review" option is not supported by uStore.

·     Authorize.Net does not work correctly if the store does not have a Friendly URL.

·     An Authroize.Net account can be used for a single uStore system only. If you have more than one system, you should obtain separate Authorize.Net accounts, one per system.

Set up a Sandbox account on Authorize.Net

Notes:

·     These instructions were written in July 2020. We will do our best to keep them up-to-date. Should you have questions, please contact XMPie Support for help.

·     Authorize.net does not support any domains with more than 6 characters after the "."
For example, https//:xmpie.training will not work.

The sandbox functions like Authorize.Net's production environment. However, no actual card processing is performed. The sandbox only simulates connections to the card networks, but no actual card payments are processed.

Sign up for a sandbox account to test the service and the processing of test orders through uStore.

To create a sandbox account:

1.       Go to https://developer.authorize.net/hello_world/sandbox.html

2.       Fill out the initial form with your details.
The following screen will then be displayed:

Note that "Simon" is not a signature key. You will need to generate one at a later stage.

You will also receive an email. Use the link in the email to log into the sandbox interface, if you have not done so already.

3.       Click the Account tab, and then select Response/Receipt URLs.

4.       In the Response/ Receipt URLs page, click Edit to define the URL value for the Default Receipt URL.

5.       In the following screen, fill in the general URL used for your stores, and change the method to Post.
You can use different text for the link text, if desired. Be sure to use HTTPS:// if you are using an SSL with your store(s).

6.       Click the Account tab and navigate again to the Response/Receipt URLs page to define the Relay Response URL.

If you have more than one domain name (i.e. multiple stores with different domain/subdomain names), navigate again to the Response/Receipt URLs page, and click the Add URL link.
If you are using HTTPS:// you should add those as the primary (first two) addresses.

You do not need to add the folder names for friendly URLs, only the domain names.

This image shows https:// as an added URL. It has been added so later when SSL is added, it will be ready for testing.

7.       Click the Account tab, and then select API Credentials & Keys.

8.       In the API Credentials & Keys screen, select New Signature Key.
You may disable the old key.

9.       You will now be prompted to verify your identity. A PIN will be sent to your email. While the pin email is immediate, you only have 30 minutes to complete this step.

10.  You have now been given a new key to use. Copy it to the clipboard.

Your sandbox account is now in live mode.  You can see this if you go to the Account tab > Security Settings > Test Mode.

Configure Authorize.Net payment in uStore

1.       On the menu bar, click Presets view and then select Clearing Model Setup.
The Clearing Model list opens.

2.       Click New to create a new clearing method (or edit an existing one).
The Edit Clearing Model Settings page is displayed. The fields displayed in this page vary according to the selected clearing method.

3.       Fill in all fields, as described in the table below.

4.       Click Test Connection and then save this new clearing method to add it to your store(s).

5.       To apply a clearing method to a store, go to the store's setup page and add this new payment method in the Clearing tab.
Note that if you do not see the payment method you've just created in the list, it is most likely that the store has Order Approval enabled and will not be able to use credit cards as a payment method.

If you are using Rest API, enter the URL of the external domain by which Authorize.Net communicates with uStore.

1.       Go to Presets > System Setup > Global Configurations.

2.       Locate the UstoreDomainWebhookURL key, and enter the domain name.
The URL should contain an http or https protocol and IP address or domain name. Examples: http://MyDomain.com, https://192.168.0.1

Troubleshooting

If payment in Authorize.Net fails, this may be because you don't have the following webhook in your Authorize.Net account: https://<yourDomain>/uStore.CommonControls/Clearing/AuthorizeNETPaymentWebHook.aspx

You can add it manually in the following location: in the authorize.net site go to Account > Settings > Business settings > Notification settings > Webhooks.
Make sure the webhook is active, and select all events.

More topics

Clearing Plugin Pair Table