Open the embed on the buy sheet

1. Give your button a destination

   Decide what the button in your app should open. For “Buy ₹500 of gold” that is the buy screen with amount 500. Keep it on your server: the destination travels with the link you mint, never in a URL your app builds.

2. Mint a link with launch, on your server

   POST/partner/users/initembed

   Nodecurl

   Copy

   app.post("/gold/buy-500", async (req, res) => {
     const r = await fetch("https://api.oropocket.com/partner/users/init", {
       method: "POST",
       headers: {
         Authorization: `Bearer ${process.env.OROPOCKET_KEY}`,
         "Content-Type": "application/json",
       },
       body: JSON.stringify({
         flow: "embed",
         mobile: req.user.mobile,
         launch: { screen: "buy", metal: "gold", amount: 500 },
       }),
     });
     const body = await r.json();
     if (!body.success) return res.status(400).json(body.error); // e.g. INVALID_LAUNCH
     res.json({ url: body.data.embed_url });
   });

   The response is the usual one, plus the launch we accepted. Mint the link when the user taps — it is single-use and lasts 10 minutes.

3. Open embed_url in your WebView

   Exactly as without a launch: load embed_url in the WebView you already set up. If you haven't, follow WebView & UPI setup first — the buy sheet hands off to UPI apps, which a WebView blocks unless you forward those links.

4. What your user sees

   A returning user lands on the buy sheet with ₹500 entered and gold selected. A new user verifies their mobile and fills in their profile first, then lands on the same sheet. They can change the amount, and nothing is charged until they choose how to pay and approve it.

Other buttons, same pattern

Check it

• The sheet opens once. Refresh the embed and you are on the dashboard — that is by design.
• A request without launch still opens on the dashboard.
• A 403 LAUNCH_NOT_ENABLED means the switch isn't on yet; every other error is listed in Open the embed on a screen.