In order to enable your customer to pay via Authorize.net, you need to create an Authorize.net merchant account and attach it to your store via the editor.
Set Up an Authorize.Net Account
In order to use Authorize.net as your payment provider, you first need to obtain a merchant account with Authorize.Net.
- Log in to your Authorize.net merchant account.
- Go to the Receipt/Response URLs page.
- Click Add URL.
- Enter https://app.multiscreenstore.com/authorizenet/11111111
(where STORE_ID is the ID of your store) to the URL field. You can find your store ID at the bottom of the Dashboard field.
- Click Submit.
Connect Authorize.Net to the Store
To connect Authorize.Net to Store:
- In the left panel, click Sell Online and then click Manage Store.
- Click Payment, scroll to the bottom of the page and click Choose Payment Processor.
- Select Credit Card: Authorize.Net SIM from the drop-down.
- Type your API Login ID, Transaction Key and MD5 Hash value.
- Pick the transaction type you want to enable:
- Authorize only. This transaction type will not be sent for settlement until you capture the funds manually in your Authorize.Net merchant account.
- Authorize and Capture. This is the most common type of credit card transaction, when the amount is sent for authorization, and if approved, is automatically submitted for settlement.
- Click Save.
Supported Currencies
The following currencies are supported.
Business Location | Supported Currencies |
---|---|
United States, Canada | USD, CAD |
United Kingdom, Europe | CHF, DKK, EUR, GBP, NOK, PLN, SEK, USD |
Australia | AUD, NZD, USD |
Troubleshooting
Some common errors you may come across when setting up your account:
Authorize.net FDC Merchant ID or Terminal ID is incorrect
This error indicates there is an issue with your Authorize.net setup. Please report this error to the Authorize.net customer support.
(99) This transaction cannot be accepted
(13) The merchant login ID or password is invalid or the account is inactive
Regarding Authorize.net: API Login Id, Transaction Key, and MD5 Hash Value must be completely the same in your customer's Authorize.Net account and his Authorize.Net settings in the store control panel. Even one unnecessary space at the end of one value can cause the 99 error.