> For the complete documentation index, see [llms.txt](https://docs.ecommerce.seb.ee/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecommerce.seb.ee/features/one-click-payments.md). # One-Click Payments Returning customers pay in seconds – with a saved card, their saved bank account, or their wallet. One feature, three ways the platform delivers it. One-click payments remove the single biggest source of checkout friction: re-entering payment details. A returning customer confirms the purchase with what they already saved – and is done. Fewer fields means fewer abandoned checkouts, especially on mobile. The SEB Ecommerce Payment Gateway supports one-click experiences across its payment methods – not just for cards. This page gives you the map; the linked pages contain the implementation detail. *** ### Three Ways to Offer One-Click
Saved CardsPay by Bank One-ClickDigital Wallets
What the customer savesA card, stored as a secure token with their consent during a first purchaseTheir bank and account selection, stored as a secure reference with their consentCards in their wallet – Apple Pay, Google Pay, or a Click to Pay profile
Where it is storedThe gateway’s token vault; you keep only the token IDThe gateway’s secure environment; valid for a limited period (e.g., up to 180 days)With the wallet provider or card scheme – not in your systems at all
Returning checkoutCustomer picks the saved card and confirms; authentication where requiredCustomer skips bank and account selection; confirms with their bank as requiredCustomer confirms in the wallet – Face ID, biometrics, or wallet login
Your integration effortStore token IDs against customer profiles; offer saved cards at checkoutInitiate payments with the stored account reference via a dedicated API endpointNone beyond enabling the wallet – the fast checkout is the wallet’s own
Read the detailsCards › One-Click PaymentsPay by Bank › One-Click PaymentsApple Pay · Google Pay · Click to Pay
The three approaches complement each other: saved cards serve your account-holding regulars, wallets serve customers who live in the Apple or Google ecosystem, and Pay by Bank one-click serves customers who prefer paying from their account. Most merchants offer more than one. *** ### What All Three Have in Common * Consent comes first. Credentials are stored only after the customer explicitly agrees – during a regular first purchase. Silent storage is never acceptable. * The customer clicks. One-click means the customer actively confirms each payment. Charging without the customer’s participation is a [Merchant-Initiated Transaction](/payment-methods/cards/stored-credentials/merchant-initiated-transactions-mit.md) and follows different rules – see [Stored Credentials](/payment-methods/cards/stored-credentials.md). * Authentication is built in. Where SCA or the issuer/bank requires authentication, it happens as part of the flow – handled by the gateway, the customer’s bank, or the wallet. You implement no authentication logic. * Your systems stay out of scope. No card numbers or bank credentials touch your systems – you work with tokens and references only. *** ### Where to Start * For the quickest win: enable [Apple Pay](/payment-methods/wallets/apple-pay.md), [Google Pay](/payment-methods/wallets/google-pay.md), or [Click to Pay](/payment-methods/wallets/click-to-pay.md) – fast checkout with no storage logic on your side. * For customers with accounts at your shop: implement saved cards – see [Stored Credentials](/payment-methods/cards/stored-credentials.md) for the framework and [Cards › One-Click Payments](/payment-methods/cards/stored-credentials/one-click-payments.md) for the checkout experience. * For account-to-account regulars: add Pay by Bank one-click – see [Pay by Bank › One-Click Payments](/payment-methods/pay-by-bank/payment-processing.md). {% hint style="info" %} Availability of each option depends on your merchant agreement and enabled services – contact your SEB representative. {% endhint %} ### Related Documentation * [One-Click Payments](/payment-methods/cards/stored-credentials/one-click-payments.md) * [Pay by Bank › One-Click Payments](/payment-methods/pay-by-bank/payment-processing.md) * [Stored Credentials](/payment-methods/cards/stored-credentials.md) * [Tokenization](/payment-methods/cards/tokenization.md) * [Apple Pay](/payment-methods/wallets/apple-pay.md) · [Google Pay](/payment-methods/wallets/google-pay.md) · [Click to Pay](/payment-methods/wallets/click-to-pay.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ecommerce.seb.ee/features/one-click-payments.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.