Passkeys at Checkout: What They Mean for Your Payment Gateway (and Why Mid-Market Merchants Should Care)
Passkeys at Checkout: What They Mean for Your Payment Gateway (and Why Mid-Market Merchants Should Care)

Short answer: passkeys don’t require you to change your checkout today. They’re in pilot or limited rollouts, and access depends on your payment provider, integration and transaction. For a merchant processing €1 million to €5 million or more in card payments each year, the useful question is whether passkeys could improve repeat-payment checkout, and how they fit into authentication, routing and fraud-liability reporting.
A passkey is an authentication method, not a new way to accept cards. It may replace a bank’s 3D Secure challenge for an eligible returning shopper. It won’t be offered on every payment, and it doesn’t guarantee a completed sale or prevent a dispute.
What changes, and what doesn’t
Scheme passkeys are a form of Strong Customer Authentication (SCA). When the method is available and selected, a returning shopper can confirm an online card payment on their device using a fingerprint, face scan or device PIN, rather than being redirected to their bank for another 3D Secure challenge. The issuer still makes the payment authorisation decision.
The documented flow starts with a standard SCA challenge. After the shopper completes it successfully, the processor may offer them the option to create a passkey on that device for the saved card. On a later purchase with the same card and device, the processor assesses whether a challenge is needed and which authentication method to use. If a passkey is eligible and selected, the device prompt replaces another issuer challenge. Otherwise, another method, such as a bank challenge, may be used. Adyen’s scheme passkey documentation sets out this flow and its limits.

For a mid-market merchant, the point is less about a new device feature and more about the repeat-payment journey. A saved card avoids re-entering card details; a passkey may remove an additional verification interruption. That’s potentially relevant for online retail, travel, B2B ordering and other businesses with returning customers, but the impact needs to be measured in your own checkout.
What the processor decides, and what you control
You generally can’t tell an authentication engine to use a passkey for a specific transaction. In Adyen’s documented pilot, its engine selects the authentication method automatically when it considers the passkey the most suitable option. A passkey may not be available for that shopper or transaction, or another method may be chosen.
Your influence is mainly in the payment setup around that decision. You can work with your provider and technical team to understand how your integration handles authentication, what information is passed between authentication and authorisation, what happens when a passkey can’t be used, and what your reporting makes visible.
The market is moving, but access remains selective. As reported by PYMNTS on 5 November 2026, Adyen is introducing Visa Payment Passkey through its Authenticate product, starting in the UK. Checkout.com is offering Visa Payment Passkey to eligible merchants, initially in the UK and Europe, through its existing authentication integration. Existing verification methods remain available when a passkey can’t be used.
Those announcements do not mean the feature is live for every merchant on those platforms, or for merchants using other providers. Treat availability as something to confirm for your specific account and payment flow.
Check the limits before you plan around passkeys
Eligibility rules can exclude a meaningful share of transactions. Adyen’s current documentation identifies these constraints for its scheme passkey pilot:
- Limited availability: the feature is in pilot and enabled for a specific group of merchants.
- Region and device: the documented service is available in the UK and EEA on WebAuthn-capable devices and supported browser versions: Chrome 67+, Firefox 60+, Safari 13+ and Edge 18+.
- Recurring payments: recurring Merchant Initiated Transactions (MIT), including subscriptions and unscheduled card-on-file payments, aren’t supported in the documented flow. A customer-initiated repeat purchase is different from an automatic subscription charge.
- Integration setup: the documented Adyen integration must use Adyen for both authentication and authorisation and support the relevant 3D Secure 2 redirect flow. A redirect URL that opens in an iFrame isn’t supported.
- Some Mastercard payments: eligibility requires an integration that supports network tokenisation.
These are provider-specific criteria, not a universal checklist for every passkey product. Ask your own gateway which rules apply to your account. If your checkout uses an older or customised integration, check it directly rather than assuming it qualifies.

Understand the liability shift, and its limits
A successful scheme passkey authentication can shift transaction liability from the merchant to the issuer. But the final liability outcome is determined after authorisation, and a card scheme can downgrade the shift. A liability shift also doesn’t stop a shopper from raising a dispute or chargeback. These qualifications are set out in Adyen’s documentation.
Ask your provider how you’ll see the final outcome in transaction reporting, and what authentication data is available for reconciliation and dispute handling. Don’t treat a successful passkey prompt as a guarantee that every later fraud or chargeback issue is covered.
For businesses routing payments through more than one provider, also check what happens when a transaction moves to a backup route. As PYMNTS notes, if the verification result can’t carry across and the backup route requires fresh verification, the shopper may face another prompt. Whether this applies depends on how your providers and integration handle the handoff.
Track three numbers before and after
Don’t assume a conversion improvement. Establish a baseline, then compare like-for-like transactions if passkeys become available to your business.
- How often shoppers see a verification prompt at all. Measure the share of relevant checkout attempts that trigger a challenge, not just the total number of payments.
- How often shoppers are offered a passkey. Compare passkey offers with the transactions that could plausibly qualify, and ask your provider how it defines eligibility.
- How often shoppers complete the purchase after the prompt. Compare completion after a passkey prompt with completion after the usual bank prompt, while accounting for differences in shopper, device, region and transaction mix.

Use a consistent reporting window and denominator. If your provider can’t separate passkey offers, successful authentications and final authorisation outcomes, ask what data it can supply before treating the feature’s impact as measurable.
Questions to put to your gateway provider
Ask for specific answers about your account and integration:
- Is scheme passkey authentication available to our merchant account now, or is it still in pilot or phased rollout?
- Which card schemes, markets, devices and payment flows qualify?
- Are our current 3D Secure integration and checkout design supported? Do any iFrame, redirect or custom-flow elements affect eligibility?
- Which transaction types are excluded, including subscriptions and other merchant-initiated payments?
- How does the authentication engine decide when to use a passkey, and what fallback does the shopper see?
- Can our reports distinguish a passkey offer, completed authentication, authorisation result and final liability outcome?
- If we route to a backup provider, can the verification result carry across, or could the shopper be prompted again?
- What testing, technical work and commercial changes would be needed for our business?
What to make of the regulatory direction
Strong Customer Authentication remains central to the proposed EU payments framework. The incoming Payment Services Regulation (PSR) is expected to provide more flexibility in acceptable authentication factors, but the framework is subject to formal adoption and further detail. See Adyen’s PSD3 and PSR overview for its current summary. Don’t treat the proposed direction as a settled rule or as a reason to rebuild your checkout before you’ve confirmed what applies to your provider and business.
How CFS Ireland can help you assess the wider setup
At CFS Ireland, we take an independent, consultative approach: we compare payment options rather than pushing a single provider. Our NMI-powered online payment gateway has integration capability across 213 acquirers. That capability doesn’t mean every authentication result can be carried across every route, so we’d help you ask the provider-specific questions that matter for your setup.
We offer a free rate analysis, transparent pricing with no hidden fees, and direct personal support, including access to our founder, Aaron Kelly. A 48-hour go-live may be possible when your setup is ready, but timing depends on the integration, provider and banking requirements, and completion of any necessary checks. It isn’t a guaranteed timeline for every merchant.
If you’re reviewing your gateway, authentication flow or payment routing, we can talk through your requirements without assuming you need to switch. Visit our online payment gateway page or contact CFS Ireland.
Detailed discussions involving confidential payment flows can be handled under NDA.