> 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-iii-casp-obligations/article-17-transfers-with-missing-or-incomplete-information.md).

# Article 17 — Transfers of crypto-assets with missing or incomplete information

1. The [crypto-asset service provider](https://www.mica.wtf/definitions/definitions/tofr/crypto-asset-service-provider) of the [beneficiary](https://www.mica.wtf/definitions/definitions/tofr/beneficiary) shall implement effective risk-based procedures, including procedures based on the risk-sensitive basis referred to in Article 13 of Directive (EU) 2015/849, for determining whether to execute, reject, return or suspend a [transfer of crypto-assets](https://www.mica.wtf/definitions/definitions/tofr/transfer-of-crypto-assets) lacking the required complete information on the [originator](https://www.mica.wtf/definitions/definitions/tofr/originator) and the beneficiary and for taking the appropriate follow-up action.\
   \
   Where the [crypto-asset](https://www.mica.wtf/definitions/definitions/tofr/crypto-asset) service provider of the [beneficiary](https://www.mica.wtf/definitions/definitions/tofr/beneficiary) becomes aware that the information referred to in Article 14(1) or (2), or in Article 15, is missing or incomplete, that [crypto-asset service provider](https://www.mica.wtf/definitions/definitions/tofr/crypto-asset-service-provider) shall, on a risk-sensitive basis and without undue delay:
   1. reject the transfer or return the transferred [crypto-assets](https://www.mica.wtf/definitions/definitions/tofr/crypto-asset) to the [originator](https://www.mica.wtf/definitions/definitions/tofr/originator)'s [crypto-asset account](https://www.mica.wtf/definitions/definitions/tofr/crypto-asset-account); or
   2. request the required information on the originator and the beneficiary before making the crypto-assets available to the beneficiary.
2. Where a crypto-asset service provider repeatedly fails to provide the required information on the originator or the beneficiary, the crypto-asset service provider of the beneficiary shall:

   1. take steps, which may initially include the issuing of warnings and setting of deadlines, before proceeding to a rejection, restriction or termination in accordance with point (b) if the required information is still not provided; or
   2. directly reject any future transfers of crypto-assets to or from, or restrict or terminate its business relationship with, that crypto-asset service provider.

   The crypto-asset service provider of the beneficiary shall report that failure, and the steps taken, to the competent authority responsible for monitoring compliance with anti-money laundering and counter-terrorist financing provisions.


---

# 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-iii-casp-obligations/article-17-transfers-with-missing-or-incomplete-information.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.