Authorize.Net is a payment gateway service, which makes accepting credit card payments simple. We're here to answer questions you may have about it so you can get set up and start accepting in-person credit card payments using a card reader and an Android mobile device.
How do I sign up with Authorize.Net?
Sign up for an Authorize.Net account by following this link here and selecting the All-in-One option (unless of course you already have an account).
What card reader should I use, and where can I get it?
Our Android app is currently compatible with the BBPOS Chipper 2x Bluetooth card reader, which can be purchased here.
How do I link my Authorize.Net account with the Omega EDI app?
You are going to need three things from your Authorize.Net account: Your API Login ID, your Transaction Key, and your Public Client Key.
1a) Login to your Authorize.Net account as an administrator here and click Account, which is in the top right of the screen.
1b) Click API Credentials & Keys from the Security Settings section.
1c) On this page, you will be able to find your API Login ID. You will also see a section called Create New Key(s). Select New Transaction Key and click Submit.
1d) It will ask you to verify your identity by sending you a PIN. Kindly oblige.
1e) Go back to the previous page (the Account tab). Your Public Client Key can be found by clicking Manage Public Client Key.
1f) Once you have your API Login ID, your Transaction Key, and your Public Client Key from Authorize.Net, login to Omega EDI as an administrator.
2a) From the navigation bar on the left, open the Admin dropdown and select Payment Methods.
2b) Click the
to create a new Payment Method.
2c) From the Type dropdown, select Payment Gateway (Authorize.Net).
2d) Enter your Authorize.Net API Login ID, Transaction Key, and Public Client Key into their respective fields and click Save.
How do I connect to the card reader?
Note: You do not need to open your Android bluetooth settings to pair the reader to your Android device, and doing so may confuse the app when it tries to scan for available card readers
Method 1: From the payment page (easiest way)
1) From the Technician Mobile App, select the Job you are working on.
2) When you are ready to accept payment from the customer, tap the $ icon, then tap CREATE PAYMENT.
3) From the Payment Method dropdown, select a Payment Method that is of the Payment Gateways (Authorize.Net) type, make sure the card reader is on, and then tap CONNECT READER .
4) If this is the first time you have tried to connect to this card reader since installing the Technician Mobile app, it will scan for nearby compatible card readers. Otherwise, skip to step 5.
Give it a moment to finish scanning for nearby card readers, then select your card reader from the dropdown and tap CONNECT.
The name of your card reader is often the serial number found on the back of the card reader. It might be something along the lines of CHB209227007514.
5) You are connected and ready to capture payment!
Method 2: From the settings menu
1) Open the menu in the top left corner and select Settings
2) Turn on your bluetooth card reader device
3) Select Connect New Card Reader, then BBPOS
You should see a message that says "Scanning for Bluetooth devices", then after a few seconds, a message that says "Got devices!"
4) Select your card reader from the dropdown and tap CONNECT.
The name of your card reader is often the serial number found on the back of the card reader, and should resemble the example above
Tapping CONNECT is important because the app remembers the last card reader that connected to it and won't have to scan for card reader devices when you are creating a payment
Are there any fees?
Authorize.Net has no setup fee, but it does have a monthly subscription cost, as well as a fairly standard per-transaction fee. These prices can be found here.
What does it mean if a payment says "held for review"?
If you make a payment on Omega with an Authorize.net payment method (credit_authnet), and you see a reference that looks something like
2148061808-Held for review
That means Authorize.net suspects it may be fraudulent. You will want to find that payment in your Authorize.net account and review it. It will not be submitted for settlement until it is approved either by you or Authorize.net.
On the Omega side of things, the payment is treated like a successful payment.