Authorize.Net

Authorize.Net Tap to Pay on mPOS What Omni-Channel High-Risk Sellers Gain

E-commerce 4 Internet Marketers Editorial

Shop clerk accepting a contactless phone payment on a handheld mPOS terminal at a retail counter
Illustration of a merchant taking tap-to-pay on an mPOS device in a small shop.

By E-commerce 4 Internet Marketers Editorial

Authorize.net added Tap to Pay support for its New Experience (2.0) Mobile Point of Sale (mPOS) apps in the release notes for the week starting March 2, 2026. Eligible merchants on the TSYS processor connection can accept contactless card and mobile-wallet payments directly on supported Android and iOS devices through the Authorize.net

According to the Authorize.net release notes (KA-05319), Tap to Pay for mPOS became available for merchants processing on the TSYS processor connection using the latest Authorize.net 2.0 mPOS app on Android and iOS. Authorize.net states that merchants can accept contactless payments via card or mobile wallet directly on the phone, with no external card reader required. Distribution is through the Google Play Store listing for Authorize.net 2.0 and the Apple App Store listing for Authorize.net 2.0.

The companion Eligibility is narrower than a generic "Authorize.net merchant" claim. The March 2, 2026 release notes name TSYS as the processor connection for the Tap to Pay mPOS launch. KA-08236's Tap to Pay availability section likewise states that Tap to Pay via the mobile device is currently supported for iOS and Android only on the TSYS processor, with additional processor connections described as future work. The same article's processor table lists First Data Nashville (FDC) as Yes for Tap to Pay via phone, while its glossary still describes FDC Tap to Pay support as coming soon. Apple's App Store listing for Authorize.net 2.0 currently states that Tap to Pay on iPhone is supported on TSYS and First Data Nashville. Merchants should confirm their live processor connection and current app version with Authorize.net or their Merchant Service Provider (MSP) rather than assume FDC phone Tap t

Payment-method and product limits still apply. KA-08236 states that the mPOS app does not support eCheck, Automated Recurring Billing (ARB), or Customer Information Manager (CIM). Supported card transaction types include Authorize and Capture, Prior Authorization and Capture (full amount only), Credit (full amount only), and Void. Partial captures and partial refunds are not supported in the app. Manual entry can collect card number, expiration date, and ZIP code for billing, plus limited shipping fields. If Merchant Interface Payment Form settings require fields the app cannot collect, transactions fail with Error 33 until those required designations are removed.

Fees are not a special Tap to Pay rate in the documentation. KA-08236 says transactions through the 2.0 mPOS app are treated like other Authorize.net account transactions, with a Transaction Fee charged per transaction and applicable MSP fees or discount rates still applying.

Why omni-channel high-risk sellers care

High-risk and regulated sellers often need more than a single online checkout. A CBD, supplement, telehealth, nicotine, or tactical merchant may take card-not-present orders on the site while also collecting deposits or walk-up sales at trade shows, clinics, or local pickup. Hardware readers, Bluetooth pairing, and spare batteries add failure points in those environments. Phone-based Tap to Pay, when the account is on a supported processor and device, gives staff a contactless path without carrying a separate terminal for every tap.

o Pay from any single table cell.

Device and market limits are explicit in KA-08236. The 2.0 mPOS app requires iOS 18 or higher, or Android OS 15 or higher. It is available only in the U.S. App Store and Google Play Store and processes U.S. dollar (USD) transactions only at this time. Android Tap to Pay requires installation of the Tap to Pay Ready companion ap

The gain is operational, not a change in underwriting. Authorize.net's cited materials do not claim that Tap to Pay expands merchant-category eligibility, softens reserves, or replaces online gateway, ARB, or CIM workflows. Subscription, vault, and eCheck flows still belong in the Merchant Interface and API surfaces that support them. For developers integrating or supporting these stacks, the practical checklist is processor connection (TSYS for the announced phone Tap to Pay launch), 2.0 app install versus legacy, OS version, Android companion app if applicable, Payment Form required-field settings to avoid Error 33, and a clear split between in-person mPOS payments and online recurring or stored-credential flows.

Authorize.net has not, in the cited release notes, published a dated public roadmap for phone Tap to Pay on every remaining processor connection listed as No in KA-08236 (including EPX, First Data Omaha, Chase Paymentech, Global, Elavon, and others). Merchants on those connections should not treat the March 2026 TSYS launch as universal coverage. KA-08236 also does not enumerate a complete device model matrix beyond OS version floors and U.S./USD limits.

This report does not invent fee deltas, underwriting changes, or eligibility for any specific high-risk vertical. Operators should verify processor, MSP, and app eligibility against their live account before retiring external readers.

Sources

Tap to Terminal and EMV via reader remain available for merchants who still need a physical reader. KA-08236 states that Tap to Terminal via an accepted card reader is currently supported on iOS and Android for TSYS and FDC, and that EMV chip acceptance through mPOS also requires TSYS or FDC. Compatible readers are sold through Authorize.net's partner POS Portal, with Wells Fargo or PaySafe MSP merchants directed to their MSP for reader guidance.

What remains unknown

plication. An internet or cellular connection is required. The legacy Authorize.net mPOS app is in maintenance mode and receives only security and maintenance updates.

ze.net/knowledgebase/article/KA-08236/en-us” target=”_blank” rel=”noreferrer noopener”>mPOS New Experience (2.0) guide (KA-08236) defines Tap to Pay (TTP) as smartphone-based Near Field Communications (NFC) acceptance for contactless cards and digital wallets such as Apple Pay or Google Pay. It distinguishes TTP from Tap to Terminal (TTT), which still uses an accepted card reader for contactless taps, and from Bluetooth swipe or EMV (Europay, Mastercard, and Visa) chip readers.

Who qualifies and what limits remain

2.0 apps, without an external card reader.

The change matters for website owners and developers who already run Authorize.net for online checkout and also collect in-person payments at pop-ups, events, delivery, or consultation desks. Omni-channel operators selling regulated or higher-risk catalogs often keep a gateway account for ecommerce while still needing a portable card-present path. Tap to Pay on the phone reduces hardware dependency for those field and counter moments, but only when the merchant's processor, device, and app version qualify.

What Authorize.net announced