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

# FAQ

### General

**What is Synthesys?** \
Synthesys builds blockchain-native infrastructure for tokenized real-world assets. The platform enables fund managers, distributors, and investors to issue, distribute, and access tokenized funds across supported blockchain networks.

**What products does Synthesys offer?** \
Synthesys has three core products: **Mint** (tokenization and fund administration), **Network** (distribution API for sub-distributors), and **Zodiac** (DeFi wrapper for permissioned fund tokens).

***

### Mint

**Can an investor hold fund tokens without completing KYC?** \
No. The Fund Token Contract enforces an on-chain whitelist. An investor's wallet must be explicitly added to the whitelist by the Transfer Agent following successful KYC verification before it can receive or hold tokens. This is enforced at the smart contract level and cannot be bypassed.

**What happens if an investor's wallet is compromised?** \
The Transfer Agent can revoke the investor's wallet from the whitelist immediately via the Mint UI. This action is executed on-chain and immediately blocks the compromised wallet from receiving any further tokens. The investor can be re-onboarded with a new wallet address following the standard KYC/whitelisting process.

**On which blockchain are fund tokens deployed?** \
Mint will launch on Ethereum Mainnet — the most widely adopted and institutionally recognised public blockchain, and the primary network supported by Chainlink's DTA infrastructure. Cross-chain interoperability is available through Chainlink's CCIP, enabling tokens issued on Ethereum to be accessible on additional networks without requiring separate fund structures.

**How is the NAV provided to the smart contract?** \
The Fund Administrator publishes the NAV via the Mint UI. The Mint API delivers this data to the Chainlink Smart NAV Oracle, which secures and records the NAV on-chain. The Chainlink DTA smart contract reads this on-chain NAV when calculating token quantities for subscriptions and redemptions.

**Is fiat settlement on-chain?** \
No. Fiat settlement (e.g., SWIFT payments) occurs off-chain through existing banking infrastructure. The Transfer Agent confirms receipt or dispatch of fiat payment in the Mint UI, which triggers the corresponding on-chain action (minting or burning).

**Does Mint charge fees?** \
The Mint platform does not charge investors or distributors any platform-level transaction or subscription fees. The only fees applicable are management fees set by the individual fund manager, disclosed in each fund's offering documents.

**How does Mint integrate with existing transfer agency systems?** \
Mint provides a comprehensive API layer that can connect with existing fund administrator and transfer agency systems for data exchange and reconciliation. Integration is assessed on a per-fund basis during onboarding.

***

### Network

**How do I get access to the Network API?** \
Reach out to the Synthesys team at <developer@synthesys.co> to get your distributor record, share-class access, and environment hostname provisioned.

**How long does subscription processing take?**\
Pinetree processes subscription and redemption orders within one business day of the daily cut-off time. Orders received after cut-off are processed the following business day.

**Can I track order status programmatically?** \
Yes. You can poll the order status endpoint (`GET /api/v1/orders/:id`) or register webhooks to receive real-time notifications for events like `order.accepted` and `token.transfer_completed`.

***

### Contact

For questions not covered here, contact:

* **Developer support:** <developer@synthesys.co>
* **General inquiries:** <operations@synthesys.co>


---

# 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://synthesys-2.gitbook.io/synthesys-docs/support/faq.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.
