> For the complete documentation index, see [llms.txt](https://team-race.gitbook.io/race-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://team-race.gitbook.io/race-protocol/race-research/security-audit-report/findings/payment-handling.md).

# Payment Handling

This section assesses the security and transparency of the recipient account mechanism in Race Protocol for managing complex payments. Additionally, the audit reviews the process of claiming assets from recipient accounts, focusing on its security and fairness.

**Findings:**

{% hint style="warning" %}
This section of report is currently only accessible to the core team for security reasons. \
Once the identified issues are resolved they will be publicly revealed.
{% endhint %}

**Transparency Assessment:**

* The recipient account mechanism is designed to be transparent, with all transactions and share distributions recorded on the blockchain. This allows anyone to verify the flow of funds and ensures that the distribution of assets is done fairly and according to the predefined rules.

**Claiming Process Review:**

* The process of claiming assets from recipient accounts appears to be secure, requiring authorization from the capability account or the payer account.
* However, the documentation could be improved by providing more details about the claiming process and the security measures in place to prevent unauthorized access to funds.


---

# 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://team-race.gitbook.io/race-protocol/race-research/security-audit-report/findings/payment-handling.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.