Build an app that runs inside Shainee
Your users are already signed in. This guide shows how to receive them in your own web app, with no login screen, and what to prepare before you go live.
Try itPlaygroundTest your server in the browser against the sandbox: automatic checks, an API console, no setup.
ConceptHow sign-in worksThe handshake between your page, Shainee and your server, in eight steps.
CodeComplete server examplesWorking Node.js and Python servers with no packages to install. Copy and adapt.
PaymentsTaking paymentsCustomers pay on Shainee's own sheet; the money is held until you release it to your sellers.
ReferenceAPI referenceThe verify route, public keys and payment routes, with every request, response and error. Also as an OpenAPI file.
LaunchGoing live on a public URLEnvironments, headers, hosting and the go-live checklist.
TestThe sandboxFake users and ready-made credentials, with every failure you need to handle.
QualityTesting your appWhat to test, from the handshake to a real phone.
All pages
| # | Page | What it covers |
|---|---|---|
| 1 | Overview | A partner app is an ordinary web app on your own server that Shainee opens inside a full-screen container, already knowing who the user is. You build the app and keep your own data; Shainee gives you |
| 2 | How sign-in works | Your page asks first, Shainee answers with a one-time token, and your server confirms it with the identity provider. A token can only be used by the page load that asked for it. |
| 3 | Browser-side contract | Your page and Shainee exchange three messages to sign in, and two more to take a payment. Everything is JSON. Shainee only answers while the page shown is served from your registered origin, so a mess |
| 4 | Server-side contract | Your server exposes four small routes and calls one route on ours. There is no library to install: this page is the full contract, followed by an outline of the logic. Complete, tested servers in Node |
| 5 | API reference | The routes a partner server calls on the identity provider. The same information is available as an OpenAPI 3.1 file , which you can load into Postman, Insomnia or any code generator. |
| 6 | Request and response examples | Every sample below was captured from the running system and shortened only where marked. In the commands, $IDP is the identity provider's base URL, $PARTNER is your own public base URL, and $CLIENT_ID |
| 7 | Generating the nonce | The nonce is a one-time random string that your server creates for every page load. It is what stops a token from being used by anyone except the page that asked for it. A good one looks like this: 8n |
| 8 | Complete server examples | These are complete, working servers. Neither uses a library or SDK: copy the one for your language and adapt it. Save each one as the file named above its code. Both pass every check in the Playground |
| 9 | Taking payments | Customers pay you inside Shainee with Pay with Shainee . You never handle wallet details, card numbers or passwords: your server asks for a payment, Shainee shows its own payment sheet, the customer p |
| 10 | The sandbox | The sandbox is a hosted copy of the identity provider that holds only fake people. You use it to build and test your server before your app is registered: there is nothing to sign up for and nothing t |
| 11 | Registering your app | Today the Shainee team registers your app for you; a self-serve console is planned. Send us the fields below and you get back a client_id and a client_secret . The secret is shown once and stored only |
| 12 | Security requirements | Every partner must meet these before being set to Active. The demo apps follow all of them and are the best examples to copy. |
| 13 | Going live on a public URL | Your app must be reachable on the public internet, over HTTPS, at the address you registered. This page is what to prepare, and the checklist the Shainee team goes through before setting your app to A |
| 14 | Testing your app | Test in three layers, from fastest to most realistic. |
| 15 | Troubleshooting and open items | Also check: if your page looks blank inside the phone app, make sure it sets its own background and text colour. The app shows white behind your page, but a page that relies on browser defaults in dar |
| 16 | Glossary |
Addresses
These documents are served by the Shainee identity provider itself, at /docs/ on its public address, https://superapp.ideapreneurnepal.com. Credentials for your app are issued when it is registered.