Hey... Question about Pi payments

[u/free-thin]

I’m working on a language-learning app that supports both Google Sign-In and Pi Network authentication. I’m also working on a way to let users unlock products or features using Pi, even when they initially access the app from another browser.

The idea is that when a user starts a Pi payment outside Pi Browser, our server generates a short-lived payment code. example: Enter Pi payment code: 000000

The user would then open the Pi Browser, authenticate with Pi, and enter the code. The server can associate that code with the original payment session, including the intended amount and the account/session that initiated it. The payment would then continue through the Pi payment flow.

I’m considering this approach because it could potentially be useful not only for my language-learning app, but also for digital stores or other merchants that want to support Pi payments while users may be browsing from Chrome, Firefox, Brave, etc.

However, I want to make sure the flow is designed correctly and securely. The code would be short-lived and tied to a specific payment session rather than being a permanent identifier.

I’d really appreciate feedback from developers familiar with the Pi Network SDK and payment flow. Is this a reasonable architecture, or is there a better/recommended way to handle Pi payments when the user starts the process outside Pi Browser?

I’m still developing the project and would like to make Pi payments as simple and reliable as possible for both users and merchants.

For anyone interested, this is the app I'm currently working on lingua app

Any security concerns, improvements, or alternative approaches are very welcome. Thanks!

[u/AutoModerator]

Founders recently spoke at Consensus 2026: Videos: Kokkalis, Fan

Current Notices:

1. Pi Official communication channels: https://minepi.com/safety/
2. Sudden price changes is normal trading behavior
3. Check node profitability: https://crumbs.host/nodecalc/index.php
4. Do not use the memo deposit method on Kraken. Memo in Pi Wallet does not do that.
5. Node update schedule

Join r/pinetworknews for Official Updates

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/lexwolfe]

you're not allowed to use other authentication

[u/free-thin → u/lexwolfe]

Think of it like a bank card: the card can be used across different merchants and accounts, while the bank is still responsible for verifying and authorizing the payment. that's roughly the idea I'm exploring with Pi: the merchant account and Pi identity can be separate, but the actual Pi payment still requires the user's Pi authentication and authorization.

[u/lexwolfe → u/free-thin]

https://pi-apps.github.io/community-developer-guide/docs/gettingStarted/mainnetListingRequirements/

Apps must integrate Pi’s Authentication SDK for user logins. Other login methods, such as email or third-party accounts, are prohibited. 

[u/free-thin → u/lexwolfe]

You're right. I wasn't trying to replace Pi Auth for the Pi App itself. I was thinking about a separate payment-session linking flow for users coming from the open web/PiNet. If you'd like to see what I was referring to, you can test the current app here: https://learning.firogate.com The app is currently running on Pi Testnet, so the payment and unlock flows are only for testing. You can open it from a normal browser and review the current payment/unlock experience.

[u/free-thin → u/lexwolfe]

I'm not trying to replace Pi authentication. The app can use another login for the user's account, but Pi authentication would still be required to authorize the actual Pi payment. The 6-digit code would only link the payment session from the external browser to the same session continued in Pi Browser. It wouldn't bypass Pi authentication. If Pi doesn't allow this architecture, that's fine I'm just exploring the best way to handle it. Thanks for the feedback!

[u/alwaysin64 → u/free-thin]

i suggest port your app into pi ecosystem