> For the complete documentation index, see [llms.txt](https://doc.api.tieto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.api.tieto.com/api-references/obl-standard/payment-initiation-api.md). # Payment Initiation API The UK equivalent of regulated payment initiation: a licensed third party starts a payment from a bank customer's account, with that customer's authorization. In the UK this is a mature payment method rather than an emerging one — pay-by-bank at checkout, bill payments, payouts — and publishing the interface puts every tenant bank in the flow of it. It covers immediate domestic payments, scheduled payments, standing orders and international transfers, so it serves consumer apps and corporate payment providers alike, and a payment provider integrates with your platform once rather than with each bank in turn. Every payment carries the customer's authorization on record, duplicate submissions are guarded against, and mandates that need more than one approver are tracked by the standard rather than by anything you or your tenants have to build. {% hint style="info" %} In scope: domestic payments, domestic scheduled payments, domestic standing orders, international payments and international scheduled payments. File payments, international standing orders and Variable Recurring Payments are part of the standard but not in the current platform scope. {% endhint %} ## Domestic payments {% openapi src="" path="/domestic-payment-consents" method="post" %} {% endopenapi %} {% openapi src="" path="/domestic-payment-consents/{ConsentId}" method="get" %} {% endopenapi %} {% openapi src="" path="/domestic-payment-consents/{ConsentId}/funds-confirmation" method="get" %} {% endopenapi %} {% openapi src="" path="/domestic-payments" method="post" %} {% endopenapi %} {% openapi src="" path="/domestic-payments/{DomesticPaymentId}" method="get" %} {% endopenapi %} ## Domestic scheduled payments {% openapi src="" path="/domestic-scheduled-payment-consents" method="post" %} {% endopenapi %} {% openapi src="" path="/domestic-scheduled-payments" method="post" %} {% endopenapi %} {% openapi src="" path="/domestic-scheduled-payments/{DomesticScheduledPaymentId}" method="get" %} {% endopenapi %} ## Domestic standing orders {% openapi src="" path="/domestic-standing-order-consents" method="post" %} {% endopenapi %} {% openapi src="" path="/domestic-standing-orders" method="post" %} {% endopenapi %} ## International payments {% openapi src="" path="/international-payment-consents" method="post" %} {% endopenapi %} {% openapi src="" path="/international-payment-consents/{ConsentId}/funds-confirmation" method="get" %} {% endopenapi %} {% openapi src="" path="/international-payments" method="post" %} {% endopenapi %} {% openapi src="" path="/international-payments/{InternationalPaymentId}" method="get" %} {% endopenapi %} ## International scheduled payments {% openapi src="" path="/international-scheduled-payment-consents" method="post" %} {% endopenapi %} {% openapi src="" path="/international-scheduled-payments" method="post" %} {% endopenapi %} --- # 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://doc.api.tieto.com/api-references/obl-standard/payment-initiation-api.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.