Tap to Pay on iPhone is coming to Saudi Arabia. What it changes at the counter

On 17 September the Saudi Central Bank (SAMA) said that Tap to Pay on iPhone will soon be available in the Kingdom. Once it goes live, a merchant will be able to accept mada cards, other contactless cards and digital wallets on an ordinary NFC-capable iPhone, with no separate card terminal. SAMA has not given a launch date. That leaves operators a few weeks or months to decide where a phone-based payment actually helps them, and to make sure the money it takes ends up in the same reports as everything else.

What SAMA announced

The announcement came out of Money20/20 Middle East, held in Riyadh from 14 to 16 September 2026. According to SAMA's release:

• Merchants will accept payments directly on compatible iPhones over NFC.
• Customers pay by tapping a mada card, another contactless card, or a phone or watch wallet against the merchant's iPhone.
• The service builds on the national mada network and on the SoftPOS service SAMA introduced in 2021 for accepting card payments on software rather than dedicated terminals.
• SAMA says the service follows international standards and local technical requirements for payment acceptance.

At the same event SAMA also confirmed Alipay+ acceptance for international visitors, which matters to anyone selling to tourists.

One detail is easy to miss. Apple does not sell Tap to Pay to merchants directly. Apple's developer documentation says a merchant uses a supported payment app from a payment service provider, and the provider processes the payments and handles certification. So in practice, Tap to Pay will reach you through your bank, your acquirer or a payment company that adds it to their app. Which providers in Saudi Arabia will support it, and at what fees, has not been announced.

Why it matters for operators

Card terminals are a small cost on paper and a constant nuisance in practice. They run out of battery, lose their SIM signal at the back of the venue, get borrowed by the next section and go missing at closing. For a café with one counter that is fine. For a padel club taking payment courtside, a family entertainment centre selling extra time at the play area, a caterer collecting a balance on site, or a retail team running a pop-up at a mall weekend, a phone that staff already carry is simply easier.

But the terminal was never the hard part. The hard part is what happens to the transaction after the tap. In most of the businesses we work with, card payments already arrive from two or three places: the main POS terminal, a delivery platform, and a payment link sent on WhatsApp. Each lands in a different settlement report, on a different day, with a different reference. Add a fourth channel that staff can open on their own phones, and the daily cash-up gets harder unless the phone payment is tied to an order in your POS from the start.

Where it helps

• Line busting and table-side payment. A server can close a bill at the table, and a busy counter can take a second queue without a second terminal.
• Mobile and event sales. Courtside, poolside, at a delivery door, at a site visit or a weekend stand, where a fixed terminal does not reach.
• Small branches and new openings. A new kiosk can start trading before the terminal arrives, provided the payment app is linked to the same merchant account and reporting.
• Field collections. Technicians and delivery drivers who collect payment on completion can do it on the company phone instead of sending a link and waiting.

Where to be careful

• Orphan payments. If staff open a standalone payment app, type an amount and tap, you get money with no order, no items and no VAT breakdown behind it. Choose a setup where the payment is started from the order in your POS or booking system, so the receipt, the invoice and the payment share one reference.
• ZATCA invoices still apply. Taking the payment on a phone does not remove the need for a compliant e-invoice. The invoice has to come from your invoicing system, not from the payment app's receipt screen.
• Device control. A phone that takes payments needs a passcode, its own staff login in the payment app, and a clear owner. Personal phones are a poor idea. Decide who is allowed to issue refunds from a phone, because refunds are where small losses hide.
• Fees and settlement. Ask your provider for the fee per transaction, the settlement schedule, and whether phone payments show up in the same settlement file as terminal payments or in a separate one.
• Timing. Nothing is live yet. Do not cancel terminal contracts or design a new venue around phone payments until your provider confirms availability.

Cicada Solutions view

Tap to Pay on iPhone is a welcome change, mostly for venues where staff move around: recreation, hospitality, events and field service. We would treat it as a new payment channel to be integrated, not a gadget to hand out. Before it launches, list every place your business takes card payments today and check that each one carries an order reference into your reports. Then pick the one or two situations where a phone would remove a real queue or a real delay, and ask your payment provider when they will support it and how it connects to your POS.

If your POS or booking system cannot start a payment from an order and match the settlement back to it, that is the gap to close first. Our guide to POS software requirements for Saudi retail and restaurants covers what to ask for, and our restaurant POS work shows how we connect payments, orders and ZATCA invoicing in one flow.

Sources

• Saudi Central Bank (SAMA): Tap to Pay on iPhone to be available soon in the Kingdom (Arabic) - published 2026-09-17, accessed 2026-10-09.
• Fintech News UAE: SAMA to enable Tap to Pay on iPhone for merchants - published 2026-09-18, accessed 2026-10-09.
• FinTech Global: Saudi Arabia expands payment options with Alipay+ - published 2026-09-17, accessed 2026-10-09.
• Apple Developer: Tap to Pay on iPhone - accessed 2026-10-09.