Authorize.net allows you to process credit cards in RepairShopr. Please make sure you have done or are aware of the following before continuing further:
- Know what Authorize payment options are supported.
- Find what hardware is supported with the integration.
- Note that we do not support ACH or EMV through Authorize.net at this time.
Table of Contents
- Set up an Account
- Go to Authorize.net's website (or call them) and sign up for an eCommerce account. When the account is created it is set up as a blended account. This allows you to process both Card Not Present (CNP) and Card Present (CP) transactions from one account.
- While it is possible to order a strictly Card Present account, you would only do this if you will only take credit cards in person and won't take payments over the phone nor allow customers to make payments online. We strongly recommend going with a blended account for more flexibility in the future.
- Be sure to ask them about Customer Information Manager (CIM) if you want to store cards. This is included at no extra charge.
- When Authorize.net says your account is "Live" this means your gateway is ready. But it doesn't necessarily mean that you can process transactions. You must be connected to your merchant account as well. Contact your merchant account provider and tell them you will be connecting to Authorize.net. They will say something like, "Great, we'll build you an Authorize.net profile" and they will give you a "Terminal ID" and related information.
- Contact Authorize.net with the terminal ID and related information to complete your gateway configuration.
- Sign in to your Authorize.net account.
- Click the Account tab.
- Under Security Settings, click the API Credentials & Keys link.
- Note the API Login ID (A)—you will need it later to enter in the integration settings.
- Click the New Transaction Key radio button (B).
- Check the Disable Old Transaction Key Immediately box (C).
- Click Submit (D).
- Click REQUEST PIN.
- Check your email for the PIN, then enter it into the next dialog and click VERIFY PIN.
- Assuming you entered it correctly, a dialog will say, "Identity Verified." Click CONTINUE.
- You will now see the Generated Key. Click Copy to Clipboard.
- Click Continue to return to the API Credentials & Keys screen.
- In a different browser tab, on your RepairShopr site, navigate to Admin > App Center.
- Click the Authorize.net app card. If the Authorize.net app card is not showing in the App Center, please email firstname.lastname@example.org and we will get it enabled for you.
- Make sure Authorize.net Enabled is checked (E).
- Change the Currency if needed (F).
- Click the Please select your Authorize.net account type dropdown > Card Not Present / Blended (G).
- If you set up a Card Present only account with Authorize.net, select Card Present in the dropdown instead.
- Paste the Generated Key you copied in step 11 above into the Authorize.net API Transaction Key field (H).
- Go back to the Authorize.net browser tab and copy the API Login ID (noted in step 4 of prior steps above).
- Back on the RepairShopr tab, paste the ID into the Authorize.net API Login ID field (I).
- Click Save.
You are all set! If you run into any issues or errors please refer to the troubleshooting steps below.
If you plan to accept credit cards in person, you can find links to order a generic USB swiper in the supported hardware section.
If after completing the setup you aren't able to process a transaction,
- Go to Admin > Reports > Payments > Payments Report.
- Once here, click View on your recently failed transaction.
- If you see this error, "This transaction cannot be accepted - Authorize.net Reason Code: 103, Response Code: 3," you will need to get a new Transaction Key from Authorize.net (see steps above).
- After doing so, go to Admin > App Center > Authorize.net app card.
- Paste this new key into the Authorize.net API Transaction Key field and click Save.
If you receive a "A duplicate transaction has been submitted" error when intentionally trying to process the same card for the same $ amount, wait two minutes and try again.
"The request field(s) are either invalid or missing" error — This indicates you have custom fields enabled in your Authorize.net account. You will need to disable that requirement and try the transaction again.