Mobile Payments

What mobile payments are

A mobile payment is a transaction made with a smartphone or tablet. A customer might tap a phone at your counter, pay through your app, or enter payment details on a mobile website. Mobile commerce, also called m-commerce, is the broader activity of buying and selling on a mobile device. Mobile payments are the payment part of that activity.

The term covers different methods, not one specific payment rail. A customer might use a digital wallet such as Apple Pay or Google Pay, scan a QR code, pay through a bank app, or enter card details in a mobile checkout. A mobile device can also help you take an in-person payment away from a fixed counter.

A mobile payment describes the device, not a guaranteed discount on your processing rate.

How mobile payments work

For an in-person sale, the customer taps a contactless card or phone on a compatible terminal. Near-field communication (NFC) sends payment information between the devices. With a mobile point of sale (mPOS), you enter the sale on a phone or tablet connected to a card reader. SoftPOS, also called tap-to-phone, uses a compatible phone as the terminal without a separate reader.

For an online or in-app sale, your checkout sends payment information for authorization. A digital wallet can provide a token in place of the card number, while authentication can use a fingerprint, face scan, or one-time code. A QR code usually directs the customer to a payment app or webpage to complete the transaction.

What mobile payments mean for your costs

Using a phone does not automatically make a transaction cheaper. The processing cost depends on how the customer pays, how the transaction is entered, the card and its interchange category, and your pricing plan. An in-person tap and an online wallet payment use a mobile device, but they are not the same transaction type.

Budget for the full setup, not just the card rate. A mobile reader or terminal, POS app, connectivity, and setup can add costs alongside processing fees. Compare the card-present rate for in-person taps with the rate for manually keyed or online sales, and check for separate monthly software or equipment charges.

There is no standard card-statement line called “mobile payment.” Reconcile sales using the transaction type, card brand, and processing category shown on your statement. Look separately for recurring app, terminal, or connectivity charges so they do not get mistaken for card-processing fees.

Security and access

Mobile acceptance still brings data-security and fraud responsibilities. PCI DSS version 4.0.1 is current as of 2026. Your compliance obligations depend on how your checkout handles card data; tokenization reduces exposure of the card number, but it does not by itself remove your responsibilities.

A phone-based checkout also depends on a working device and network connection. Plan for a backup way to take payment if the device loses power or connectivity, and keep another payment option for customers who do not use a smartphone.

What you can actually change

1. 01
   Compare transaction types. Separate in-person taps from keyed and online sales on your statement. Compare the rates and transaction fees for each group.
2. 02
   Add up the setup. List reader or terminal costs, software, connectivity, and processing fees. Check whether recurring charges appear separately from your card fees.
3. 03
   Plan for outages. Decide how you will accept payment if your phone, reader, battery, or network is unavailable. Keep an option for customers without mobile wallets.
4. 04
   Review data handling. Confirm how your checkout captures and protects card data, and keep your PCI DSS validation current for your setup.

Frequently asked questions