Overview

The Authorize.net 2.0 Mobile Point of Sale (mPOS) application is a next-generation mobile payment solution that enables merchants to accept and manage payments from virtually anywhere. By transforming an Apple or Android mobile device into a fully functional point of sale system, the mPOS app provides flexibility, convenience, and broad payment method support for merchants on the go.

This article provides a comprehensive guide to downloading, setting up, and using the Authorize.net 2.0 mPOS app. It covers supported devices and operating systems, accepted payment methods, processor compatibility, transaction types, card reader setup, Tap to Pay (TTP) configuration, troubleshooting steps, and frequently asked questions (FAQs).

This guide is intended for merchants who are new to the Authorize.net 2.0 mPOS app or who are transitioning from the legacy Authorize.net mPOS application.

What Is the Mobile Point of Sale (mPOS)?

The Authorize.net Mobile Point of Sale (mPOS) is a mobile application that allows merchants to accept and manage payments on the go, turning an Apple or Android/Google mobile device into a point-of-sale system.

Downloading the Authorize.net 2.0 App

The mPOS application can be found on the iOS and Android app stores by searching for Authorize.net.

• Authorize.net (Legacy Version): This version is in maintenance mode and will only receive security and maintenance updates.
• Google Play Store: Authorize.net 2.0
• Apple App Store: Authorize.net 2.0

Supported Operating Systems

• iOS: Requires iOS 18 or higher. Only available in the US iTunes/App Store and can only process transactions in USD at this time.
• Android: Requires Android OS 15 or higher. Only available in the US Google Play Store and can only process transactions in USD at this time.

Supported Devices

Various Apple and Android phones and tablets running supported versions of iOS and Android are compatible with the Authorize.net 2.0 mPOS app.

Using the App

For detailed instructions on how to use the Authorize.net 2.0 mPOS app, refer to the Mobile User Guide for iOS and Android.

Supported Payment Methods

The Authorize.net 2.0 mPOS app supports the following payment methods:

• Credit/Debit — Tap to Pay (TTP): Use your smartphone to accept payments from cards that support Tap to Pay or Near Field Communications (NFC)-enabled devices with digital wallets such as Apple Pay or Google Pay. Android devices must have a companion app installed to accept Tap to Pay. For more information, see the section Setting Up and Processing Tap to Pay Transactions below and see: What is and how to process Tap to Pay transactions?
• Credit/Debit — Tap to Terminal (TTT): Use a reader along with your smartphone to accept payments from cards that support Tap to Terminal/Device for Near Field Communications (NFC).
• Credit/Debit — Card Reader (Swipe, EMV Dip): Use a card reader connected via Bluetooth. This option is the default when a card reader is connected to the app.
• Credit/Debit — Manual Entry: Enter the card number, expiration date, and ZIP code for the cardholder manually. This option is the default when no card reader is connected.
• Cash: Enter the amount of cash received; a balance due will appear. Cash transactions are recorded in the app only and are not passed to the Merchant Interface.

Processor Compatibility

The following table outlines processor support for each payment method available in the Authorize.net 2.0 MPOS app:

Customer Data Entry and Payment Form Fields

The mPOS app has limitations on what customer data can be entered. The following information can be entered manually:

Billing Information

• Card Number
• Expiration Date
• ZIP Code (only the ZIP code may be collected for billing information)

Shipping Information

• Name (First and Last)
• Address (Street, City, State, ZIP)

Important: If the Merchant Interface Payment Form fields are set to required but cannot be entered through the mPOS app, the transaction will fail with Error 33. You will need to modify the required fields in the Payment Form Settings to ensure no fields are set to required that cannot be entered through the mPOS app.

Supported Transaction Types

The Authorize.net 2.0 mPOS app supports the following transaction types:

• Authorize and Capture
• Prior Authorization and Capture (full amount only — partial captures are not supported)
• Credit (full amount only — partial refunds are not supported)
• Void

Understanding Processing Rates

Transactions processed through the Authorize.net 2.0 mPOS app are treated the same as any other transaction processed through your Authorize.net account. A Transaction Fee will be charged for each transaction. Your Merchant Service Provider (MSP) will also charge the applicable fee or discount rate.

Compatible Card Readers and EMV Support

Compatible swipe readers and EMV (Europay, Mastercard, and Visa) chip-enabled card readers can be found and purchased through Authorize.net's partner, POS Portal.

• You must be on a supported processor (TSYS or FDC) to accept EMV chip transactions using the mPOS app.
• If you are currently using Wells Fargo or PaySafe as your Merchant Service Provider (MSP), contact their support team for further information on obtaining a card reader.

For additional information, refer to the support article: How do I use a compatible card reader with the Authorize.net mPOS, Virtual Point of Sale (VPOS) App for Windows?

Using a Receipt Printer with the App

The mPOS application supports printing of receipts. For details on compatible receipt printers, refer to the support article: Which receipt printers work with Virtual Point of Sale (VPOS) App for Windows and Mobile Point of Sale (mPOS)?

For help enabling a printer within the app, refer to the Mobile User Guide.

Setting Up and Processing Tap to Pay Transactions

Tap to Pay Availability

• Tap to Terminal (via an accepted card reader): Currently supported for iOS and Android on TSYS only. Additional processor connections will be supported in the future.
• Tap to Pay (via mobile device): Currently supported for Android only on TSYS. iOS and additional processor connections will be supported at a later date.
• For Tap to Pay on Android devices, installation of the Tap to Pay Ready companion application is required.

For additional information on Tap to Pay, refer to the support article: What is and how to process Tap to Pay (TTP) transactions?

Troubleshooting the App and Card Reader

If the App Is Not Working

1. Verify you have downloaded the most recent version of the app.
2. Uninstall and then reinstall the app.
3. Restart your device.
4. Confirm that you have a stable Internet or cellular connection.

If the Card Reader Is Not Working

1. Verify that you are using a supported device and card reader.
2. Ensure the reader is fully plugged in.
3. Confirm that mute is not enabled and that the volume is turned all the way up after the reader is plugged in.

If the EMV Reader Is Not Working

1. Verify that you are using a supported device and EMV reader.
2. Ensure the reader has been fully charged.
3. Confirm the reader has been set to Chip mode by completing the following steps:
   1. Navigate to Settings.
   2. Select Card Readers.
   3. Select Connect.
   4. Select BT Connection or Audio Jack depending on your reader type.
   5. Select the radial button next to your reader and confirm it is set to Chip.
4. If the issue persists after completing these steps, contact Client Services for further assistance.

mPOS FAQs

• Can the app process cash transactions?
  • Yes. However, cash transactions have limitations. They are not passed to the Merchant Interface, are only viewable within the app, and are stored for 7 days. Split tender transactions with cash are not supported — your customer must pay entirely in cash or entirely by credit card. Cash transactions cannot be downloaded.
• Can I process transactions without an Internet connection?
  • No. An Internet connection is required to process transactions. This can be through Wi-Fi or a 3G/4G/LTE cellular connection.
• Can I process eCheck transactions through the mPOS app?
  • No. The mPOS app is for processing credit card transactions only. eCheck processing is not supported.
• Can I use Automated Recurring Billing (ARB) or Customer Information Manager (CIM) with the mPOS app?
  • No. ARB and CIM cannot be used with the mPOS app.
• Can I use the mPOS app on multiple devices?
  • Yes. The mPOS app can be used on multiple devices, including phones and tablets.
• What should I do if I cannot sign in to the app?
  • The mPOS app uses the same login credentials (login ID and password) as the Merchant Interface, along with the same username and password recovery options. If you are unable to sign in, contact an Account Owner or Account Administrator for your account.
• Why is my transaction failing with Error 33?
  • Error 33 occurs when the Merchant Interface Payment Form has required fields that cannot be entered through the mPOS app. Navigate to your Payment Form Settings and remove the required designation from any fields that are not supported by the mPOS app.
• What processors support EMV chip transactions through the mPOS app?
  • You must be on TSYS or First Data Nashville (FDC) to accept EMV chip transactions using the mPOS app.
• Is Tap to Pay available on iOS?
  • Tap to Pay and Tap to Terminal via mobile device is currently supported on Android and iOS on TSYS. Support or additional processor connections will be available at a later date.

Additional Resources

• Mobile User Guide for iOS and Android
• What is and how to process Tap to Pay transactions?
• Merchant EMV Chip FAQs
• How do I use a compatible card reader with the Authorize.net mPOS, Virtual Point of Sale (VPOS) App for Windows?
• Which receipt printers work with Virtual Point of Sale (VPOS) App for Windows and Mobile Point of Sale (mPOS)?

Glossary

• ARB — Automated Recurring Billing: An Authorize.net feature that automates recurring payment schedules. Not supported in the mPOS app.
• CIM — Customer Information Manager: An Authorize.net feature for storing customer payment data. Not supported in the mPOS app.
• EMV — Europay, Mastercard, and Visa: A global standard for chip-based payment card transactions that provides enhanced security over magnetic stripe cards.
• FDC — First Data Nashville: A payment processing platform supported by the Authorize.net mPOS app for EMV and swipe transactions, with Tap to Pay support coming soon.
• FDCO — First Data Omaha: A payment processing platform supported by the Authorize.net mPOS app for swipe transactions only.
• mPOS — Mobile Point of Sale: A mobile application that enables merchants to accept and manage payments using a smartphone or tablet.
• MSP — Merchant Service Provider: The financial institution or payment processor that provides merchant accounts and payment processing services.
• NFC — Near Field Communications: A short-range wireless technology that enables contactless payment transactions between a payment card or digital wallet and a compatible device.
• TTP — Tap to Pay: A contactless payment method that uses NFC technology to accept payments directly via a smartphone without a card reader.
• TTT — Tap to Terminal/Device: A contactless payment method that uses NFC technology to accept payments directly via a card reader.
• TSYS: A payment processing platform that supports the full range of mPOS payment methods, including Tap to Pay and EMV transactions.
• USD — United States Dollar: The only supported currency for transactions processed through the Authorize.net 2.0 mPOS app at this time.
• VPOS — Virtual Point of Sale: A Windows-based point-of-sale application offered by Authorize.net, related to but distinct from the mPOS mobile application.