> For the complete documentation index, see [llms.txt](https://qualitax.gitbook.io/interop/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://qualitax.gitbook.io/interop/solutions-providers/universal-digital-payments-network-alliance.md).

# Universal Digital Payments Network Alliance

## 1.  Problems/Challenges it aims to solve

## 2. Solutions

* The UDPN is a messaging network connecting all government-regulated digital currency systems, including regulated stablecoins and future CBDCs.
* The UDPN also serves as a distribution network to bring digital currencies to all enterprise IT systems , no matter how small or large, enabling the transfer and swap of different currencies. The UDPN is a permissioned, decentralised network managed via a decentralised governance model consisting of 8 to 24 alliance members, preventing any single entity from controlling the network.

## 3. Target Customers

## 4. Key points

## 5. People

## 6. Industry Initiatives Participation

## 7. Resources

| **Initiative Name**     |   |
| ----------------------- | - |
| **Organization**        |   |
| **Type**                |   |
| **Description**         |   |
| **Ecosystem**           |   |
| **Public Participants** |   |
| **Link**                |   |


---

# 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://qualitax.gitbook.io/interop/solutions-providers/universal-digital-payments-network-alliance.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.