Wio enables Click to Pay: what checkout teams should test

On 6 October 2026, Wio and Mastercard announced automatic Click to Pay enablement for the bank's cards in the UAE. Shoppers will not need to manually enter card details each time at supported checkouts. The experience combines tokenization with Mastercard Payment Passkey and device biometrics.

The issuer changes the starting point

The interesting feature is who initiates enablement. When storing a payment instrument depends entirely on a particular store, every merchant must take the customer through its own path. Bank-side enablement moves part of that preparation earlier, before the shopper reaches the store. This is an interpretation of the announcement's significance, not a claim that every storefront is compatible.

The merchant benefit depends on several conditions meeting: the card participates, checkout supports the relevant flow, and the customer can complete verification on their device. One issuer's announcement does not mean manual card entry has disappeared from the country's entire ecommerce market.

A new phone is a revealing example. The main journey may be fast, but the customer still needs a clear route when their usual verification method is unavailable. Checkout quality includes that branch: can the order continue without an ambiguous error or unnecessary repetition of information already supplied?

Operationally, authentication completion and final payment approval should remain distinct. A successful biometric check is not, by itself, evidence of a paid order. Support and reconciliation need a reliable connection between those events.

The announcement shows issuers participating in a simpler online purchase before the customer presses the store's payment button. The meaningful merchant test is whether issuer-prepared credentials lead to more completed orders on its own storefront.

What this means for merchants and PSPs

For a merchant in the UAE, the announcement is a reason to check whether its checkout is ready for a shopper who already holds an issuer-prepared payment credential. If the storefront relies on a PSP or a hosted payment page, support usually depends on whether the provider has enabled the relevant flow and whether the contract covers it. With a custom integration the question is broader: interface, token handling and status logic may all need work.

For PSPs, it is a product question: which merchants can use the flow without changes, how it appears in reporting and how such payments are identified during disputes and refunds.

What to check internally

• Whether the current provider or hosted page supports the flow and whether it must be enabled separately.
• How tokenised payments are flagged in reports, and whether their conversion can be compared with manual entry.
• What the shopper sees if device verification fails: is there a clear fallback that keeps the basket intact?
• Whether authentication, authorisation and final order status are linked in the event log.
• Whether support is ready for questions about stored cards and device changes.
• Which metrics to track after enablement: completed orders, time to pay, drop-off at the verification step.

Risks and limitations

The conversion effect depends on the share of shoppers with eligible cards and on the quality of each storefront's implementation. Expectations from an announcement should not go into a budget without internal measurement; comparing segments before and after enablement on real traffic is the safer approach.

Sources: Mastercard and Wio announcement