> For the complete documentation index, see [llms.txt](https://docs.reveel.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reveel.id/use-cases/embedded-wallets/portal-poc.md).

# Portal POC

A proof-of-concept integration combining Portal's embedded wallet infrastructure with Reveel Pay(ID), enabling applications to give their users a single omnichain payment identity.

#### What it demonstrates

* Spin up a non-custodial Portal wallet for any user inside your app
* Attach a Pay(ID) to that wallet as a universal payment identity
* Accept any stablecoin from any supported chain — routed automatically to the user's preferred token and network
* No bridging or manual swaps required from the user's perspective

#### Who it's for

* Consumer app developers already using or evaluating Portal for wallet infrastructure
* Products that want to add stablecoin payment flows without exposing chain complexity to users
* Teams building wallet-gated features who need a simple payment identity layer

#### How it works

<table data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td><p><strong>1. Portal wallet creation</strong></p><p></p><p>User signs up in the app — Portal generates an MPC-based non-custodial wallet. No seed phrase required on the user side.</p></td></tr><tr><td><p><strong>2. Pay(ID) attachment</strong></p><p></p><p>The Reveel API links a Pay(ID) to the Portal wallet address. Route rules define which token and chain the user wants to receive on.</p></td></tr><tr><td><p><strong>3. Omnichain receive</strong></p><p></p><p>Anyone can send funds to the user's Pay(ID) from any supported network. Reveel routes the payment to the Portal wallet automatically.</p></td></tr></tbody></table>

#### Outcome / benefits

* Embedded, non-custodial wallets with no UX complexity
* Single Pay(ID) identifier works across all supported chains
* Users hold only their preferred stablecoin — routing is fully abstracted
* Easy integration path for teams already using Portal SDK


---

# 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.reveel.id/use-cases/embedded-wallets/portal-poc.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.