For UK merchants, “one-click payment” usually means making checkout quicker for a returning customer by showing a saved payment method or prefilled details. It does not guarantee that one click completes the payment: the customer may still need to confirm the purchase or authenticate it. A compliant setup also needs clear consent for saving payment details and a way to handle required security checks.
What “one-click payment” means in a merchant checkout
“One-click” is a description of a checkout experience, not a formal promise that payment always takes one action. The customer may be offered an eligible saved card or have some details filled in, but the checkout can still require confirmation, additional information, or authentication. The Financial Conduct Authority (FCA) describes when strong customer authentication can apply, while Stripe documents one provider’s saved-card Checkout behavior: FCA guidance on Strong Customer Authentication and Stripe’s existing-customer Checkout documentation.
How a saved-payment checkout works
- Collect the payment details. The customer enters payment details through the merchant’s checkout and payment provider.
- Explain and obtain agreement to save. If the customer chooses to save a method for a future use, explain that use clearly and retain evidence of the agreement. Saving a card is not blanket permission to charge it whenever the merchant chooses.
- Associate the method with the customer. The provider’s system links the eligible payment method to that customer according to its configuration and rules.
- Offer it on a later visit. The returning customer may see the saved method or have eligible details prefilled. What appears depends on the provider, its configuration, and the available customer and payment-method data.
- Complete the purchase and any required checks. The customer confirms the transaction; the provider processes it and may request authentication or another action.
Stripe’s documentation describes saving details during an in-app payment and pre-filling eligible details in Checkout for existing customers. These are provider-specific behaviors, not a guarantee that every saved card or checkout integration will work identically: Stripe’s guide to saving payment details during an in-app payment and Stripe’s existing-customer Checkout documentation.
On-session and off-session payments are different
Payment providers may distinguish future payments by whether the customer is present in the checkout when the payment is attempted. An on-session transaction takes place while the customer is actively using the checkout. An off-session transaction is attempted when the customer is not actively there. Neither term means “one click”: an on-session checkout can still require authentication, while an off-session attempt is not the same as a customer confirming a purchase in a live checkout. The intended future use, customer agreement, payment method, and provider configuration all matter. Stripe explains these distinctions in its saved-payment documentation and notes that merchants remain responsible for applicable laws, regulations, and card-network rules.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems#1 Best Overall
Consent, security checks, and UK SCA
Saving details requires a clear purpose
Tell customers what will be saved and how it will be used in future, make the choice clear, and keep a record of the agreement. A customer’s agreement to store a method for future checkout should not be treated as unrestricted permission for later charges. Stripe’s merchant-facing guidance discusses consent and future use in its guide to saving payment details during an in-app payment.
Authentication may still be required
The FCA says strong customer authentication (SCA) can apply when a payer initiates an electronic payment, accesses a payment account online, or performs a remote action that may imply fraud risk, unless an exemption applies. The exact outcome depends on the transaction and applicable rules; a saved card does not by itself remove authentication requirements. The FCA also says firms should make authentication usable for different customer groups, including considering methods that do not rely on mobile phones. See the FCA’s Strong Customer Authentication guidance.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
The FCA’s May 2026 Payment Services and Electronic Money – Our Approach is identified as a draft in the FCA’s key publications index. It describes SCA as using at least two independent elements from knowledge, possession, and inherence, and explains that authenticating to access account information does not necessarily satisfy authentication when a payment is initiated. Treat that document as draft explanatory material, not final guidance; check current FCA rules and final publications before implementing a flow.
When is the merchant a payment service provider?
A retailer that accepts a debit or credit card for its own goods or services generally is not itself providing the card payment service. The FCA Handbook says: “In our view, the simple act of accepting payment by way of debit card or credit card for supply of your own goods or services does not generally amount to the provision of the service of execution of payment transactions through a payment card.” The FCA’s discussion of the merchant’s role is in PERG 15.3, Q18.
In that common arrangement, the acquirer that enables card payment processing provides the payment service. The FCA also says that technical processing or storage of data, payment terminals, and online gateways alone do not amount to acquiring. Calling a business a “gateway” does not settle its regulatory status. Marketplaces and other businesses that handle or pass customer funds, provide acquiring, or initiate bank payments may raise different questions; their actual fund flows and contracts need to be assessed. See the FCA Handbook’s PERG 15.3 guidance and the FCA’s overview of the Payment Services Regulations 2017 and Electronic Money Regulations 2011.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to compare saved-payment checkout options
- Consent and customer control: Can the checkout explain what is stored and the intended future use, give the customer an informed choice, and preserve evidence of agreement?
- Authentication and recovery: Can the provider request required SCA and guide customers through a payment that needs authentication instead of promising a frictionless completion? Are there usable authentication options for people who do not rely on a mobile phone?
- Saved-method display and prefill: Which eligible methods can be offered to returning customers, and what account data or configuration is required? Can customers manage their saved methods?
- Integration fit: Does the flow fit the merchant’s platform and customer-account model, support the payment methods the business accepts, and match whether future payments are intended to happen with the customer present or absent?
- Regulatory roles: Confirm who is acting as the merchant, acquirer, and payment service provider in the actual arrangement. A product’s label alone does not establish its role.
These are practical comparison criteria, not a ranking of providers. The cited sources do not establish an independent UK conversion-lift study, neutral vendor ranking, or current provider price comparison for one-click payments.
Quick Recap
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
