# Risk & Compliance

Risks and Compliance for Rupya Token on akad.finance Following Sharia Manner

1. Introduction

The Rupya token, a Shariah-compliant stablecoin on the AkadDao product within the akad.finance platform, offers users a stable digital currency pegged to the Indonesian Rupiah (IDR). Although the Rupya token aims to provide a secure and stable means of transacting and investing, users should be aware of the risks and compliance considerations associated with the token. This document outlines the primary risks and compliance aspects related to the Rupya token, with a focus on Shariah compliance.

2. Risks Associated with Rupya Token

a. Collateral Price Fluctuations: Rupya tokens are backed by AKAD tokens, which are pegged to the value of gold. A significant decrease in gold prices may lead to reduced collateralization ratios, potentially triggering the liquidation process for users who have minted Rupya tokens.

b. Counterparty Risks: As a stablecoin, the Rupya token may be subject to counterparty risks, such as the potential failure of the underlying collateral (AKAD tokens) to maintain their value or the risk of default by borrowers in the lending pool.

c. Regulatory Risks: The regulatory environment for DeFi platforms and stablecoins is still evolving. Changes in regulations, compliance requirements, and legal frameworks may impact the operation and accessibility of the Rupya token, exposing users to potential risks.

d. Peg Maintenance: The Rupya token is designed to maintain a stable peg to the Indonesian Rupiah (IDR). However, market fluctuations, liquidity issues, or other unforeseen factors may cause the token's value to deviate from its intended peg, introducing price instability.

3. Compliance Considerations Following Sharia Manner

a. Shariah Compliance: To ensure ongoing compliance with Islamic finance principles, the Rupya token and its associated products and services should be regularly reviewed and audited by a qualified Shariah advisory board.

b. Ethical Investing and Financing: The platform should promote ethical investing and financing by offering Shariah-compliant investment opportunities and prohibiting investments in industries or activities that are not in line with Islamic principles, such as alcohol, gambling, and interest-based lending.

c. Transparency and Accountability: The platform should maintain a high level of transparency and accountability by providing users with clear information on the Rupya token's mechanisms, the underlying collateral, and the associated risks. Users should also have access to relevant financial data and performance metrics.

d. Community Oversight and Governance: In line with Shariah principles, the platform should foster community involvement in decision-making processes related to the Rupya token and its associated products and services. This can be achieved through community-driven governance mechanisms that promote collective decision-making and consensus.

4. Conclusion

While the Rupya token offers users a Shariah-compliant stablecoin for transactions and investments within the AkadDao product on the akad.finance platform, it is essential to consider the risks and compliance aspects associated with the token, with a focus on Shariah compliance. By understanding and mitigating these risks, as well as adhering to relevant compliance requirements, users can make more informed decisions and better protect their investments in accordance with Shariah principles.

<br>


---

# 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://akad-finance.gitbook.io/akad.finance/english/tokenomics/rupya-token/risk-and-compliance.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.