> For the complete documentation index, see [llms.txt](https://docs.abapays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abapays.com/product/channels.md).

# Channels

> Telegram & WhatsApp — conversational

Before it was reachable by MCP, A2A, or x402, AbaPay was already an agent — a natural-language identity, not a protocol endpoint. Every payment it makes on these channels runs through the exact same allowance-bounded execution engine as every other rail in this handbook.

|          |                                                  |
| -------- | ------------------------------------------------ |
| Telegram | [@AbaPays](https://t.me/AbaPays)                 |
| WhatsApp | [+234 707 541 8792](https://wa.me/2347075418792) |

## What this is — and isn't

This is **AbaPay's own agent identity** — the same one registered on-chain under ERC-8004 — reachable in plain language. A human types "pay 1000 naira MTN airtime to 08012345678" and it understands intent, not menu numbers. Nothing here is a separate system: it's the identical execution pipeline behind MCP and A2A, just with a chat interface in front of it.

The PIN here works the same way as everywhere else in this handbook — set inside the conversation itself ("Reply with your PIN to set it up"), never through a web form.

What this **isn't**: a structured, machine-typed protocol. A program that wants to drive these channels has to speak natural language the way a human would, rather than calling a typed function — which is exactly why x402, A2A and MCP exist as separate, structured rails for agent-to-agent integration. Use this chapter to understand AbaPay as an agent in its own right; use those three to integrate one.


---

# 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://docs.abapays.com/product/channels.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.