> 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/jan-2025/cregis-update-notification-version-v2.15.0.md).
# Cregis Update Notification - Version \[V2.15.0]
We are excited to announce the launch of Cregis's latest version, V2.15.0, scheduled for 8 Jan 2025, at 20:30:00 (UTC+8). This update is mandatory and will take approximately one hour to complete. The details are as follows:
1. Payment engine API optimization and added callback retry mechanism (PC only)
2. Optimized callback retry mechanism for deposit and withdrawal API interfaces (PC only)
3. Auto-collection and auto-signature feature optimization (PC only)
4. Optimized batch payment and collection transaction record display (PC only)
5. Support multi-language bill export (PC only)
6. Cregis card activation process optimization and new PIN code setup
7. Cregis card interface upgrade and data display optimization
8. Launched transaction acceleration for the BTC network
9. MPC network setting interaction optimization
10. Support Ripple (XRP) and Filecoin (FIL) chains
Cregis Team \
2025-01-07
---
# 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/jan-2025/cregis-update-notification-version-v2.15.0.md?ask=&goal=
```
`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.