> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/announcement/jun-2025/cregis-update-notification-version-v3.2.0.md).

# Cregis Update Notification - Version \[V3.2.0]

Dear Cregis User,

We are pleased to announce that the latest version of Cregis, <mark style="color:green;">**V3.2.0**</mark>, will be released on <mark style="color:green;">**June 12, 2025, 07:00 – 08:00 (UTC+8)**</mark><mark style="color:green;">.</mark> This is a <mark style="color:green;">**non-mandatory update**</mark>. During the system maintenance period, services including login, transfers, API access, payment acceptance, and others will be temporarily unavailable. Deposits may experience delays, and settlement processing will resume after maintenance concludes. We apologize for any inconvenience and kindly advise you to adjust your operations in advance and upgrade to the new version and adjust relevant permissions promptly after maintenance.<br>

Update Details:

1. Bug fixes and system enhancements

\
Thank you for your continued support. Please feel free to contact us if you have any questions.

Cregis Team \
2025-06-10


---

# 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://support.cregis.com/announcement/jun-2025/cregis-update-notification-version-v3.2.0.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.