> For the complete documentation index, see [llms.txt](https://developers.gurupay.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.gurupay.eu/getting-started/guides/transactions.md).

# Transactions

Transactions have several required fields, along with optional fields that can be added depending on your needs. All transactions that are submitted to Guru Pay are subject to regulatory and sanctions scanning prior to release.

As transactions progress through workflow, status changes are automatically communicated through webhooks if configured, or through a manual [Get Transaction ](https://developers.gurupay.eu/api-reference/transactions)request.

**Transaction type**

All transaction flow is being sent as SEPA INSTANT, in case the beneficiary bank does not accept INSTANT payments, the transaction will be routed via SEPA CT. You will always see the type of transaction via endpoint `/api/v1/transactions/{uuid}` as `"payment_type"`

**Cancel transaction**

To cancel transaction, please promptly contact your account manager and Client Care team at <clientcare@gurupay.eu>.&#x20;


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developers.gurupay.eu/getting-started/guides/transactions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.