> For the complete documentation index, see [llms.txt](https://docs.lhv.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lhv.com/home/connect/services/indirect-scheme-access/payment-collection-services.md). # Payment Collection Services Different Payment Collection Services **Payment Collection Services involve the automated collection of payments** from customers' bank accounts, typically through direct debit schemes such as SEPA Direct Debit (SDD) in Europe or Bacs Direct Debit in the UK. These services allow businesses to collect recurring payments like subscriptions or utility bills directly from customers' accounts with prior authorization. In contrast, Payment Initiation Services (PIS) facilitate the initiation of payments on behalf of the customer, typically for one-off transactions, by connecting to the customer's bank and instructing it to make a payment. While Payment Collection Services focus on recurring, pre-authorized debits, PIS are used for single, user-initiated transactions. {% hint style="danger" %} Payment Collection Services are currently under development! This part of the documentation is still subject to change and improve. {% endhint %} ## Services ### Bacs Direct Debit [Bacs Direct Debit](/home/connect/services/indirect-scheme-access/payment-collection-services/bacs-direct-debit.md) (Bacs DD) is a UK-based payment method that allows businesses to collect payments directly from customers' bank accounts. ### Sepa Direct Debit SEPA Direct Debit (SDD) is a pan-European payment method that allows businesses to collect euro-denominated payments directly from customers' bank accounts across the Single Euro Payments Area (SEPA) for both recurring and one-off transactions, based on prior authorization. **SEPA DD services are currently provided only by LHV EE.** --- # 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.lhv.com/home/connect/services/indirect-scheme-access/payment-collection-services.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.