> For the complete documentation index, see [llms.txt](https://bify.gitbook.io/rwa-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bify.gitbook.io/rwa-docs/bify-rwa/architecture.md).

# RWA Architecture

![BIFY RWA architecture](/files/1EFvbiKWxrNLqq6Oeaki)

## Issuer flow

1. The issuer submits a business and asset application.
2. BIFY approves the issuer and links the issuer identity to the approved wallet and portal account.
3. The issuer creates an offering with its legal documents, terms, supply, unit price, jurisdiction, and transfer restrictions.
4. BIFY reviews and activates the offering.

## Investor flow

1. The investor connects a wallet and signs in to the investor portal.
2. The investor completes the required identity and geolocation checks.
3. The investor selects an approved offering and quantity.
4. The investor pays the exact USDC amount on the configured network.
5. The sale contract verifies eligibility, price, supply, and payment.
6. The asset token is issued to the eligible investor.
7. BIFY creates the purchase certificate and the investor mints it to the investor wallet.
8. After the issuer-defined holding period, the investor may request the configured redemption process. There is no resale marketplace.

## Boundary

An RWA token represents the rights defined by the offering documents and legal structure. The token, contracts, issuer, and legal documents must be treated as one issuance system. RWA certificates and asset tokens are not Commerce purchase certificates.


---

# 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://bify.gitbook.io/rwa-docs/bify-rwa/architecture.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.