> For the complete documentation index, see [llms.txt](https://www.mica.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mica.wtf/tofr/transfer-of-funds-regulation/chapter-ii-psp-obligations/article-4-information-accompanying-transfers-of-funds.md).

# Article 4 — Information accompanying transfers of funds

1. The [payment service provider](https://www.mica.wtf/definitions/definitions/tofr/payment-service-provider) of the [payer](https://www.mica.wtf/definitions/definitions/tofr/payer) shall ensure that transfers of [funds](https://www.mica.wtf/definitions/definitions/tofr/funds) are accompanied by the following information on the payer:
   1. the name of the [payer](https://www.mica.wtf/definitions/definitions/tofr/payer);
   2. the payer's [payment account](https://www.mica.wtf/definitions/definitions/tofr/payment-account) number;
   3. the payer's address including the name of the country, official personal document number and customer identification number, or, alternatively, the payer's date and place of birth; and
   4. subject to the existence of the necessary field in the relevant payments message format, and where provided by the payer to its [payment service provider](https://www.mica.wtf/definitions/definitions/tofr/payment-service-provider), the current [LEI](https://www.mica.wtf/definitions/definitions/tofr/legal-entity-identifier) of the payer or, in its absence, any available equivalent official identifier.
2. The payment service provider of the payer shall ensure that transfers of [funds](https://www.mica.wtf/definitions/definitions/tofr/funds) are accompanied by the following information on the [payee](https://www.mica.wtf/definitions/definitions/tofr/payee):
   1. the name of the [payee](https://www.mica.wtf/definitions/definitions/tofr/payee);
   2. the payee's [payment account](https://www.mica.wtf/definitions/definitions/tofr/payment-account) number; and
   3. subject to the existence of the necessary field in the relevant payments message format, and where provided by the payer to its payment service provider, the current [LEI](https://www.mica.wtf/definitions/definitions/tofr/legal-entity-identifier) of the payee or, in its absence, any available equivalent official identifier.
3. By way of derogation from paragraph 1, point (b), and paragraph 2, point (b), in the case of a transfer not made to or from a payment account, the payment service provider of the payer shall ensure that the [transfer of funds](https://www.mica.wtf/definitions/definitions/tofr/transfer-of-funds) is accompanied by a [unique transaction identifier](https://www.mica.wtf/definitions/definitions/tofr/unique-transaction-identifier) rather than the payment account number.
4. Before transferring funds, the payment service provider of the payer shall verify the accuracy of the information referred to in paragraph 1 and, where applicable, in paragraph 3, on the basis of documents, data or information obtained from a reliable and independent source.
5. Verification as referred to in paragraph 4 of this Article shall be deemed to have taken place where one of the following applies:
   1. the identity of the payer has been verified in accordance with Article 13 of Directive (EU) 2015/849 and the information obtained pursuant to that verification has been retained in accordance with Article 40 of that Directive;
   2. Article 14(5) of Directive (EU) 2015/849 applies to the payer.
6. Without prejudice to the derogations provided for in Articles 5 and 6, the payment service provider of the payer shall not execute any [transfer of funds](https://www.mica.wtf/definitions/definitions/tofr/transfer-of-funds) before ensuring full compliance with this Article.


---

# 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://www.mica.wtf/tofr/transfer-of-funds-regulation/chapter-ii-psp-obligations/article-4-information-accompanying-transfers-of-funds.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.