# Transfer Errors

<table><thead><tr><th width="57.095703125">ID</th><th width="306.94140625">Code</th><th width="357.5625">Description</th></tr></thead><tbody><tr><td>0</td><td>REJECTED</td><td>Default rejection reason. </td></tr><tr><td>1</td><td>UNKNOWN_WALLET_ADDRESS</td><td>VASP doesn't control the beneficiary wallet address.</td></tr><tr><td>2</td><td>UNKNOWN_ORIGINATOR</td><td>The originator account can't be identified.</td></tr><tr><td>3</td><td>UNKNOWN_BENEFICIARY</td><td>The beneficiary account can't be identified.</td></tr><tr><td>4</td><td>UNSUPPORTED_CURRENCY</td><td>VASP doesn't support the specified cryptocurrency. </td></tr><tr><td>5</td><td>EXCEEDED_TRADING_VOLUME</td><td>VASP can't receive more transaction inflows.</td></tr><tr><td>6</td><td>COMPLIANCE_CHECK_FAIL</td><td>VASP internal compliance check has failed.</td></tr><tr><td>7</td><td>NO_COMPLIANCE</td><td>VASP not able to implement travel rule compliance.</td></tr><tr><td>8</td><td>HIGH_RISK</td><td>VASP unwilling to proceed with the transaction after risk assessment.</td></tr><tr><td>9</td><td>OUT_OF_NETWORK</td><td>Wallet address or transaction is not available on the specified blockchain network.</td></tr><tr><td>10</td><td>BAD_REQUEST</td><td></td></tr><tr><td>11</td><td>UNPARSEABLE_IDENTITY</td><td>Unable to parse identity record.</td></tr><tr><td>12</td><td>PRIVATE_INFO_WRONG_FORMAT</td><td></td></tr><tr><td>13</td><td>UNPARSEABLE_TRANSACTION</td><td>Unable to parse transaction data record.</td></tr><tr><td>14</td><td>MISSING_FIELDS</td><td>There are missing required fields in the transaction data.</td></tr><tr><td>15</td><td>INCOMPLETE_IDENTITY</td><td>The identity record is not complete enough for compliance purposes.</td></tr><tr><td>16</td><td>VALIDATION_ERROR</td><td>There was an error validating a field in the transaction data.</td></tr><tr><td>17</td><td>COMPLIANCE_PERIOD_EXCEEDED</td><td>The review period has exceeded the required compliance timeline.</td></tr><tr><td>18</td><td>CANCELED</td><td>The transfer request was canceled.</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.ospree.io/ospree-api/travel-rule/transfer-errors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.