> 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/2024-codapay-changelog/2024-07-16-channel-closed-announcement-philippines-globe.md).

# \[2024-07-16] Channel Closed Announcement: Philippines Globe

Dear Partners,&#x20;

We're writing to inform you that Globe, one of our payment channel partners in the Philippines, has had to decommission its Direct Carrier Billing (DCB) charging platform.&#x20;

As a result, Globe's DCB service will no longer be available as a payment option on Codapay in the Philippines from **16 July 2024**.&#x20;

Nevertheless, GCash, the Globe Group's mobile wallet service, will continue to be available as a payment method on Codapay in the Philippines.&#x20;

Thank you for your understanding and for your continuous trust.


---

# 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/2024-codapay-changelog/2024-07-16-channel-closed-announcement-philippines-globe.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.
