> For the complete documentation index, see [llms.txt](https://ninjapay.gitbook.io/webupi-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ninjapay.gitbook.io/webupi-protocol/namaste/welcome-to-webupi.md).

# Welcome to WebUPI!

## WebUPI Guide

## NINX & Ninjapay

Protocol spec — [Nalanda Naidu](mailto:undefined) CTO Ninja Labs & Medinin Labs(IN)  — 

[Contact us](https://t.me/+zxixB1S99rIzYWY1)

***

## 🧭 Intro

> WebUPI is a proposed interface that brings the power of Unified Payments Interface (UPI) to the web. Just as UPI revolutionized payments by providing a simple and standardized protocol for transactions across different banks in India, WebUPI seeks to extend this simplicity and standardization to the internet, enabling seamless integration of UPI payments on the web.
>
> ### **What is WebUPI?**
>
> WebUPI is a protocol that allows websites to request payments from users via UPI. With WebUPI, a website can send a payment request to a user's UPI application, and the user can approve the payment right from their app(eg. Chrome Extension), making the payment process swift and seamless.
>
> The WebUPI protocol is designed to facilitate direct peer-to-peer transactions on the web. It leverages the existing UPI infrastructure, which supports instant round-the-clock money transfer through mobile devices and a single mobile application for accessing different bank accounts\*\*[1](https://www.npci.org.in/what-we-do/upi/product-overview)\*\*.
>
> WebUPI builds on the idea of [Web3.js](https://www.npmjs.com/package/web3) and [WebLN](https://github.com/getAlby/webln-guide/blob/main/README.md), a collection of libraries that allow interaction with local or remote blockchain nodes using HTTP, IPC, or WebSocket. The WebUPI specifications are proposed in 2023 and since then, have been continuously refined. In the meantime, the hope is to see several applications and client providers be built using this standard, taking advantage of the widespread adoption of UPI in various markets. However, the implementation and growth of WebUPI will depend on the adoption and support by browser vendors, UPI apps, and the broader financial technology community.

<figure><img src="/files/AE1nwFAEJgywQYN9c0X9" alt=""><figcaption><p>webUPI Arch</p></figcaption></figure>


---

# 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://ninjapay.gitbook.io/webupi-protocol/namaste/welcome-to-webupi.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.