> 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/compliance/open-banking.md). # Open Banking Direct account-to-account payments and account information services enabled through regulated APIs. Open Banking allows licensed third-party providers to access payment-account information or initiate payments through secure APIs, with the customer’s consent. In Europe, this model is closely linked to PSD2 and the regulated services it created for account access and payment initiation. ### What Open Banking enables Depending on the service and the customer’s bank, Open Banking can allow customers to: * Pay directly from a bank account without using a payment card. * Authorize the payment using the authentication methods provided by their own bank. * Share account information, with explicit consent, with regulated providers for services such as account aggregation and financial-management tools. For merchants, account-to-account payments can provide a card-free payment option that is integrated into the checkout journey while the customer remains in control of authorization through their bank. ### The role of PSD2 PSD2 established the European framework for regulated third-party access to payment accounts. Two key service types are: * Account Information Service (AIS) - allows an authorized provider to retrieve payment-account information with the customer’s consent. * Payment Initiation Service (PIS) - allows an authorized provider to initiate a payment from the customer’s payment account on the customer’s behalf. ### Security and consent * [Strong Customer Authentication (SCA)](/compliance/strong-customer-authentication-sca.md) is performed where required, usually by the customer’s bank. * Access to account data or payment initiation requires the customer’s explicit consent. * Customer authentication and consent are handled by the customer’s Account Servicing Payment Service Provider (ASPSP), typically the customer’s bank, in accordance with applicable requirements. ### Why it matters Open Banking gives customers more control over how their payment-account data is used and enables new ways to pay without a card. For merchants, it can add a direct bank-payment option alongside card and wallet methods and can simplify payment acceptance through a single gateway integration. --- # 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/compliance/open-banking.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.