> For the complete documentation index, see [llms.txt](https://docs.powens.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powens.com/documentation/integration-guides/pay-by-bank/getting-started-with-pay-by-bank.md). # Getting started with Pay by Bank Discover what the Pay by Bank product is about, and enable Pay on your domain! The Pay by Bank product allows you to initiate and follow up on payments with banks complying with the revised Payment Service Directive (PSD2). It does not require bank account aggregation made beforehand: you may request payments from an emitter bank *without* creating a connection in our API. If you do not have a domain yet, you can preview connectors supporting the Pay by Bank product by going on [Powens Institutions](https://institutions.powens.com/), and selecting "Pay" on the left hand side. ## Enable Pay by Bank on your domain Pay by Bank features can be activated by your commercial contact only. ## Enable Pay by Bank connectors Going on the [console](https://console.budget-insight.com/), selecting your domain then selecting "Pay" on the left. From there, you can enable connectors you want to use on your domain. ## Configure the Payment State Updated Webhook It is highly recommended to configure the `PAYMENT_STATE_UPDATED` webhook; see [Webhooks](/documentation/integration-guides/webhooks.md) for more information on how webhooks work. --- # 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.powens.com/documentation/integration-guides/pay-by-bank/getting-started-with-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.