> 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/payment-methods/pay-by-bank.md). # Pay by Bank Let customers pay directly from their bank account – authenticated by their own bank, with no payment card involved. **Pay by Bank** enables customers to make secure online payments directly from their bank account, without using a payment card. Powered by **PSD2 Open Banking**, the payment is initiated through the gateway and authorized by the customer at their own bank, using the authentication methods they already know – their mobile banking app, Smart-ID, or Mobile-ID. The SEB Ecommerce Payment Gateway provides a single integration with access to participating banks across the Baltic region. The gateway manages connectivity to all supported banks: you integrate once, and your customers pay from the bank of their choice. Pay by Bank is ideal for merchants looking to offer a secure and convenient alternative to card payments – particularly in the Baltics, where paying through one’s own bank is a familiar and trusted way to pay online. *** ### Key Benefits #### For Merchants * Single integration with access to all participating banks – new banks are added without changes on your side. * Strong Customer Authentication (SCA) is performed by the customer’s bank – no 3DS handling on your side. * Real-time payment status updates via [callback notifications](/integration/merchant-api/webhooks.md). * No payment card data handling – Pay by Bank does not add card-related PCI DSS scope. * Automated [refunds](/payment-methods/pay-by-bank/refunds.md) – full, partial, and multiple partial – for eligible transactions. * [One-click payments](/features/one-click-payments.md) for returning customers, where enabled – see One-Click Payments below. #### For Customers * Payments directly from their bank account – no card required and no card details to type. * Authentication with familiar methods: mobile banking app, Smart-ID, Mobile-ID, biometrics. * A fast, trusted checkout experience in their own bank’s environment. *** ### Capability Summary
CapabilitySupport
Payment TypeAccount-to-account (A2A) payment via PSD2 Open Banking
CoverageParticipating banks in Latvia, Lithuania, and Estonia – single integration
Customer AuthenticationPerformed by the customer’s bank (SCA)
Payment ConfirmationReal-time status updates; final status via callback notifications
“Paid” StatusSettled – funds transferred (A2A payments do not use Authorized/Captured)
One-Click PaymentsSupported where enabled. A stored bank and account reference can shorten the payment flow for returning customers, but additional customer confirmation or SCA may still be required.
Recurring and subsequent paymentsSupported through the Merchant API where enabled and supported by the relevant bank or ASPSP. The Merchant manages the schedule and recurring payment logic.
RefundsFull, partial, and multiple partial – via Merchant Portal or Merchant API, for eligible transactions
Integration OptionsHosted Checkout, Merchant API
Sandbox TestingAvailable
{% hint style="info" %} Availability of individual capabilities depends on your merchant agreement, enabled services, and the participating banks. {% endhint %} ### What You Need to Accept Pay by Bank * Pay by Bank is enabled as a payment method in your e-shop agreement. Contact your SEB representative to have Pay by Bank activated for your shop. * Your integration – Hosted Checkout or Merchant API – processes callback notifications and updates orders based on the confirmed payment status. * For automated refunds, your payments are settled to your SEB settlement account (see Refunds). {% hint style="info" %} No separate registration with individual banks is required – bank connectivity is provided by the gateway. {% endhint %} --- # 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/payment-methods/pay-by-bank.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.