> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/changelog/legacy-changelog/2023-06-14-channel-closed-announcement-thailand-dolfin-wallet.md).

# \[2023-06-14] Channel Closed Announcement: Thailand Dolfin Wallet

Dear Merchant / Publisher,

We would like to inform you about the unfortunate decision to close the **Thailand Dolfin Wallet** Payment Channel service. We have concluded that it is no longer feasible to continue operating the **Thailand Dolfin Wallet** service in Coda.

Effective immediately on **14th June 2023**, the Dolfin Wallet service will be discontinued in Coda. We understand that this news may come as a disappointment to our valued users, and we sincerely apologise for any inconvenience caused.

Our team will be available to provide support and address any concerns you may have. If you require assistance or have any questions, please do not hesitate to contact our Business Development Team.

Thank you for your understanding and cooperation during this process.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coda.co/changelog/legacy-changelog/2023-06-14-channel-closed-announcement-thailand-dolfin-wallet.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
