For the complete documentation index, see llms.txt. This page is also available as Markdown.

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

1. Portal wallet creation

User signs up in the app — Portal generates an MPC-based non-custodial wallet. No seed phrase required on the user side.

2. Pay(ID) attachment

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.

3. Omnichain receive

Anyone can send funds to the user's Pay(ID) from any supported network. Reveel routes the payment to the Portal wallet automatically.

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

Last updated

Was this helpful?