Tap to Pay on iPhone UI: Accept Cards, No Hardware

Tap to Pay on iPhone turns a merchant’s iPhone into a contactless card reader, no dongle, no terminal. The short answer: you design the accept-payment flow (enter amount, the hold-card-near prompt, success and failure), but you do not build the secure NFC read itself, that requires a supported payment platform and Apple’s entitlement, and the platform plus Apple handle the card data. Contactless is now the norm: in many markets over 80% of in-person card transactions are contactless, per Visa, so accepting taps is essential for sellers.

You design the flow, the platform takes the card

The clean mental model: Tap to Pay is a capability you unlock through a payment platform (such as Stripe, Adyen, or another certified provider) plus an Apple entitlement, and the actual contactless read and card handling happen securely through Apple and that platform. You never see raw card numbers. So your job is the merchant-facing flow: a clear amount entry, an unmistakable hold-card-near prompt during the read, and clean confirmation or failure afterward. Make it calm and obvious, the person tapping is often a customer watching over the counter, so Apple’s Human Interface Guidelines on clear feedback matter here. Apple’s Tap to Pay on iPhone program defines the requirements.

Build it from a free design

VP0 is a free iOS design library for AI builders. Pick amount-entry, payment, and confirmation designs, copy their links, and have Cursor or Claude Code rebuild them in SwiftUI. Integrate a certified payment platform’s SDK to enable Tap to Pay and process the transaction, and request the entitlement Apple requires. Design the states clearly: amount entry, the read prompt (“Hold card or phone near the top of iPhone”), processing, success (with a receipt option), and failure (with a plain reason and retry). Never build your own card capture, the platform and Apple own that. For the broader checkout pattern, see eCommerce checkout screen UI mobile, and for secure money-screen patterns, see SwiftUI banking app template.

Tap to Pay flow building blocks

Each state keeps a counter transaction clear.

State	What the merchant sees	Note
Amount	Enter the charge	Clear, easy to correct
Read prompt	Hold card near the top	Unmistakable instruction
Processing	Reassure during the read	Do not double-charge
Success	Confirmed, receipt option	Clear and fast
Failure	Plain reason, retry	Decline, timeout, etc.

Common mistakes

The first and most important mistake is trying to handle card data yourself, you cannot and must not; use the certified platform and Apple’s secure read. The second is an unclear read prompt, leaving the customer unsure where to tap. The third is a confusing amount-entry that invites wrong charges. The fourth is no clear failure handling for declines and timeouts. The fifth is forgetting the entitlement and platform requirements and assuming you can build it raw. Design the flow; let Apple and the platform take the card.

A worked example

Say you build a point-of-sale app. Using a certified payment platform’s SDK and Apple’s entitlement, your VP0-built flow lets the merchant enter an amount, then shows a clear “Hold their card or phone near the top of iPhone” prompt during the secure read. On success, a confirmation with an optional receipt; on a decline, a plain message and a retry. The customer taps their card or Apple Pay, and the money moves, with your app never touching card data. For the digital-key access cousin, see Apple Wallet pass UI template free, and for EU app-distribution rules next, see Digital Markets Act DMA alternative app store UI Figma.

Key takeaways

• Tap to Pay on iPhone accepts contactless cards and wallets with no extra hardware.
• You design the accept-payment flow; a certified platform plus Apple handle the read.
• Build the amount, read prompt, processing, success, and failure states from a free VP0 design.
• Never handle raw card data; it requires a payment platform SDK and Apple’s entitlement.
• Make the hold-card-near prompt unmistakable for the customer at the counter.

Frequently asked questions

How do I build a Tap to Pay on iPhone UI? Build the amount, read prompt, processing, and result states from a free VP0 design, and enable Tap to Pay through a certified payment platform’s SDK plus Apple’s entitlement, which handle the secure read.

Do I handle the card data myself? No. The secure contactless read and card handling happen through Apple and your certified payment platform. Your app never sees raw card data, and you must not try to capture it.

What do I need to use Tap to Pay on iPhone? A supported payment platform (such as Stripe or Adyen) that offers Tap to Pay, plus the Apple entitlement. You build the UI on top of that platform’s SDK.

What should the read prompt say? Something unmistakable like “Hold their card or phone near the top of iPhone,” so the customer knows exactly where to present their card or Apple Pay during the secure read.