> 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/nextgenpsd2-xs2a/payment-initiation-service.md). # Payment Initiation Service Payment initiation lets a licensed third party start a payment from a bank customer's account, with that customer's authorization. It is what stands behind pay-by-bank at online checkout, bill-payment apps, and the payment features built into accounting and treasury software — money moving directly from an account, with no card in the middle. Publishing it discharges the payment half of the PSD2 obligation for each tenant bank, and it is the service that makes a platform commercially interesting: payment providers want reach, and one connection to you puts them in front of every bank you serve. The service covers single payments, bulk submissions and standing instructions, so it serves consumer apps and corporate payment providers alike. Every payment carries the customer's authorization on record, and mandates that need more than one approver are handled by the standard rather than by anything you or your tenants have to build. The reference below is generated from the Berlin Group **openFinance API Framework XS2A — Payment Initiation Service, version 2.4.1**. ## Initiating a payment {% openapi src="" path="/payments/{payment-product}" method="post" %} {% endopenapi %} {% openapi src="" path="/bulk-payments/{payment-product}" method="post" %} {% endopenapi %} {% openapi src="" path="/periodic-payments/{payment-product}" method="post" %} {% endopenapi %} ## Tracking and cancelling {% openapi src="" path="/{payment-service}/{payment-product}/{paymentId}/status" method="get" %} {% endopenapi %} {% openapi src="" path="/{payment-service}/{payment-product}/{paymentId}" method="get" %} {% endopenapi %} {% openapi src="" path="/bulk-payments/{payment-product}/{paymentId}/extended-status" method="get" %} {% endopenapi %} {% openapi src="" path="/{payment-service}/{payment-product}/{paymentId}" method="delete" %} {% endopenapi %} ## Authorization sub-resources These are the endpoints behind multi-approver mandates — each approval is tracked as its own sub-resource, and the payment stays pending until the required set is complete. {% openapi src="" path="/{resource-path}/{resourceId}/{authorisation-category}" method="post" %} {% endopenapi %} {% openapi src="" path="/{resource-path}/{resourceId}/{authorisation-category}" method="get" %} {% endopenapi %} {% openapi src="" path="/{resource-path}/{resourceId}/{authorisation-category}" method="put" %} {% endopenapi %} {% openapi src="" path="/{resource-path}/{resourceId}" method="put" %} {% 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/nextgenpsd2-xs2a/payment-initiation-service.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.