You can accept credit card payments on your phone through a mobile payment processor that connects to a card reader or uses your phone's built-in technology

The most common setup is a small card reader that plugs into your phone's charging port or headphone jack, paired with an app from a payment processor like Square, PayPal, or Stripe. When a customer swipes, inserts, or taps their card, the reader captures the information, the app processes the payment, and the money lands in your bank account — usually within one to two business days. You do not need a traditional merchant account or a physical store to do this.

The second option is contactless-only: some processors let customers pay by tapping their phone or card near your phone, using technology called NFC (near-field communication). This requires no separate hardware but works only if your phone has NFC built in, which most modern phones do.

A third option, less common but growing, is QR code payments. You display a code, the customer scans it with their phone camera, and they pay through a link — no card reader needed, but the customer must have their phone and internet access.

Key Takeaways

  • A card reader that attaches to your phone plus a free or low-cost app is the most reliable way to accept cards in person, and works even if the customer's phone is dead or they do not have one.
  • Payment processors charge a fee per transaction (usually 2.6% to 3.5% plus $0.10 to $0.30) and sometimes a monthly fee, so compare rates before choosing one.
  • Your phone must have a working internet connection — cellular data or Wi-Fi — for the payment to go through, and the processor will hold the transaction if the connection drops.
  • You are responsible for keeping customer card data secure; most processors handle this for you, but you still need to follow their rules about storing receipts and protecting the reader itself.
  • Contactless and QR code payments work without a card reader but require the customer to have their phone, making them less reliable as a sole payment method.

How card readers and apps work together

The card reader is a small device, usually about the size of a matchbox, that reads the magnetic stripe, chip, or contactless signal from a card. It connects to your phone through the charging port (Lightning on iPhones, USB-C on newer Android phones) or the headphone jack (older models). The reader sends the card data to an app on your phone, which encrypts it and sends it to the processor's servers.

The processor verifies the card is real and has enough money or credit, then either approves or declines the payment in seconds. If approved, the money is held by the processor and transferred to your bank account on a set schedule — often the next business day, sometimes longer depending on the processor and your bank. You get a receipt on your phone, and the customer gets one too, either printed from a small printer you connect to your phone or sent to their email or phone number.

Popular processors include Square (which offers the Square Reader for contactless and chip cards), PayPal (PayPal Here), Stripe (Stripe Reader), and Block (formerly Square Cash). Each has slightly different fees, features, and hardware options, so the choice depends on your volume, the types of cards you expect, and whether you need features like invoicing or inventory tracking.

Understanding the fees you will pay

Every payment processor charges a fee, and there is no such thing as truly free payment processing. The most common structure is a percentage of each transaction plus a flat per-transaction fee. For example, Square charges 2.6% plus $0.10 for card-present transactions (when the customer is in front of you), while PayPal Here charges 2.7% plus $0.30. These rates vary by processor and change over time, so check the current rates on their websites before you decide.

Some processors also charge a monthly fee if you process a certain volume or want access to premium features like advanced reporting or payroll tools. Others charge nothing monthly but take a higher percentage per transaction. A few charge a flat monthly fee regardless of volume — useful if you process a very high volume and want predictable costs.

There are also fees for things like chargebacks (when a customer disputes a charge and the processor sides with them), refunds, and failed transactions. These are less common but can add up if you have a high dispute rate. Before you start, read the processor's fee schedule carefully and calculate what you will actually pay on your expected monthly volume.

What you need to get your free guide

You need a smartphone (iPhone or Android), the processor's app (free to download), and a card reader if you want to accept physical cards in person. Most processors sell their readers for $20 to $50 as a one-time purchase, or sometimes include one free with your first order. You also need a bank account in your name to receive the payments — the processor will ask for your routing and account number during setup.

You will need to provide some personal information during signup: your name, address, phone number, email, and usually your Social Security number or tax ID. The processor uses this to verify your identity and comply with banking regulations. If you are a business, you may need to provide your business license or EIN (Employer Identification Number), though many processors let sole proprietors use their personal SSN.

Finally, you need a reliable internet connection — either cellular data or Wi-Fi — to process payments. If your connection drops mid-transaction, the processor will queue the payment and try again when you reconnect. This usually happens automatically, but you should check your app to make sure the payment went through before you hand over the goods or service.

Contactless and QR code payments as alternatives

If your phone has NFC (near-field communication), you can accept contactless payments without a card reader. The customer taps their card or phone near your phone, and the payment goes through using the same app and processor. This is faster than inserting a chip card and works with most modern credit cards and digital wallets like Apple Pay and Google Pay. However, not all processors support this, and not all phones have NFC, so check before you rely on it.

QR code payments work differently: you display a unique QR code (generated by your processor's app) on your phone or print it out, the customer scans it with their phone camera, and they complete the payment on their phone. This requires no card reader and no NFC, but it does require the customer to have their phone, a camera that works, and internet access. It is slower than a card reader because the customer has to open a link and enter payment details. QR codes are useful as a backup or for remote payments, but most in-person businesses still prefer card readers because they are faster and do not depend on the customer's phone.

Security and compliance responsibilities

Payment processors handle most of the heavy lifting for security. They encrypt card data, store it on secure servers, and comply with PCI DSS (Payment Card Industry Data Security Standard), a set of rules that protect card information. Your app and card reader are designed to work within this system, so you do not have to worry about storing card numbers yourself.

However, you still have responsibilities. You should keep your phone and card reader physically secure — do not leave them unattended or let customers handle the reader. You should also keep receipts organized and secure, especially if they contain partial card numbers. If a customer disputes a charge, the processor will ask you for proof that the transaction happened, so keep records for at least a few months. Finally, use a strong password on your processor account and enable two-factor authentication if the processor offers it.

If you suspect fraud — for example, if someone uses a stolen card to pay you — report it to your processor immediately. They will investigate and may reverse the charge, which means the money comes back out of your account. This is rare, but it is why keeping good records matters: if you can prove the customer was in front of you and authorized the payment, you have a better chance of keeping the money.

Choosing between processors

The main differences between processors are fees, hardware options, and extra features. Square is popular because it has low fees for in-person payments and a simple app, but it charges more for online payments and invoicing. PayPal Here has similar fees but integrates with PayPal's ecosystem if you already use PayPal for online sales. Stripe is geared toward businesses that also sell online and want one processor for everything. Block (formerly Square Cash) is newer and targets small businesses and freelancers.

To choose, start by listing what you need: Do you only accept payments in person, or do you also need online invoicing? Do you need a receipt printer? Do you want to track inventory or employee sales? Then compare the fees and features of two or three processors on those specific needs. Most offer free trials or let you process a few test transactions before you commit, so try them out with your phone and see which interface feels easiest to use.

What happens after the payment goes through

Once a payment is approved, the processor holds the money temporarily and deposits it into your bank account on a schedule you set during signup. Most processors deposit daily or weekly, but some deposit every few days or on a fixed day of the week. You can usually change this in your app settings. The deposit appears as a single lump sum from the processor, not as individual transactions, so your bank statement will show one line item per deposit rather than one per customer payment.

You can see a detailed breakdown of all transactions in your processor's app or dashboard. This shows each payment, the fee charged, the customer's name (if they provided it), the time and date, and the deposit date. You can download this data as a CSV file or connect it to accounting software like QuickBooks, which is useful if you need to track income for taxes or business purposes.

If a customer wants a refund, you can issue one through the app in seconds. The processor reverses the charge, and the money goes back to the customer's card. The fee you paid is usually not refunded, so if you charged $100 and paid $2.70 in fees, you will refund $100 but keep the $2.70 cost. Some processors refund the fee if you refund the full transaction within a certain time window, so check your processor's refund policy.

Frequently Asked Questions

Do I need a business license or tax ID to accept card payments on my phone?

No, most processors let you sign up as a sole proprietor using your personal Social Security number. However, you are still responsible for reporting the income to the IRS on your tax return. If you operate as a business entity (LLC, S-corp, etc.), you will need your EIN, but many processors do not require this upfront.

What if a customer's card is declined?

The processor will tell you immediately that the payment failed. You can ask the customer to try a different card, or they can pay you another way (cash, check, bank transfer). The declined transaction does not charge you a fee and does not appear on your account history.

Can I accept payments offline if I do not have internet?

Most processors queue transactions when your connection drops and send them once you reconnect. However, some require an active connection to process the payment in the first place. Check your processor's offline policy before you rely on it in an area with spotty service.

What is the difference between a card reader and contactless payments?

A card reader lets you accept physical cards (swiped, inserted, or tapped) and works even if the customer does not have their phone. Contactless payments require the customer to tap their card or phone near your phone and work only if your phone has NFC. Card readers are more reliable because they do not depend on the customer's device.

How long does it take to get paid after a customer swipes their card?

The payment is approved in seconds, but the money does not land in your bank account until the processor's deposit schedule — usually one to three business days later. Some processors offer next-day deposits for an extra fee, but most standard deposits take longer.