Gold in your app by the end of the sprint
Ship gold in a sprint, not a quarter.
Issue a user_code, load the URL it returns in a WebView, and OroPocket renders buying, selling and KYC inside your app. The users who onboard through it are yours.
No card. No approval queue. No sales call.
One call to start
Mint a user_code with the user's mobile and you get back the embed URL to load. It is single-use and expires in ten minutes.
Nothing to design
Buy, sell, portfolio and the full PAN + Aadhaar KYC flow are all rendered for you, in both metals.
The user becomes yours
A new account created through your embed is attributed to you, and its buys pay your commission from then on.
Two steps are yours. The rest is ours.
The same sequence the guide walks through, so you can see the shape before you read a line of reference.
- Your server:
Issue a user_code
One call with the user's mobile returns a single-use code and the embed URL to load.
POST/partner /users /init Expires in 10 minutes — issue it when they tap in, not ahead of time.
- Your server:
Load it in a WebView
Point a WebView at the returned embed_url. JavaScript and DOM storage must both be on.
Mandate popups need multi-window support; UPI needs deep links forwarded to the OS.
- The user:
They verify by OTP
The embedded app handles the code. A brand-new OroPocket account created here is attributed to you.
This is the only moment attribution is set.
- OroPocket:
We render the rest
Buying, selling and KYC all happen inside the embed. There is no UI for you to build.
- OroPocket:
We call your webhook
A signed buy.completed or sell.completed lands on your endpoint. You never poll.
Two calls, or one.
# issue a single-use user_code + embed_url
curl -X POST https://api.oropocket.com/partner/users/init \
-H "Authorization: Bearer oro_live_xxx" \
-d '{"flow":"embed","mobile":"9876543210","name":"Anya"}'What you are not building.
The parts of this that are hard are the parts you would otherwise have to write, test and operate yourself.
The KYC you would rather not build
PAN and Aadhaar verification, the document capture, the retry paths and the rejected state are all inside the embed. You never see the documents and never store them.
Prices that hold
Every quote inside the embed locks its rate for ten minutes against a frozen price block. What the user is shown is what settles.
You never hold the PII
You address the user by an opaque user_code. Mobile numbers and emails come back masked, and internal identifiers never leave our side.
Preview it before you ship
The Playground's Embed tab runs the whole journey in a phone simulator in your browser, against the stateful sandbox. Sandbox OTP is always 1234.
This is the path that earns the most.
Attribution is set at exactly one moment — when a brand-new OroPocket account is created through your embed. From then on every buy that user makes pays your commission, whether or not it happened inside your app. Users who already had an OroPocket account are never attributed, so the number is honest.
Frequently asked.
- What is hosted gold investing?
- A WebView you drop into your app that renders the entire buy, sell and KYC experience for digital gold and silver. You issue a single-use user_code, load the embed URL it returns, and OroPocket renders everything the user sees from there.
- How much code do I write?
- One server call to mint a user_code, and the WebView that loads the returned URL. There is no UI for you to build, no price feed to poll and no KYC flow to design.
- What does my app have to support?
- JavaScript and DOM storage must both be on, since the session lives in localStorage. You also need multi-window support — recurring-plan mandates open a payment popup — and you must forward upi:// and intent:// URLs to the OS so UPI apps can open. Miss those and mandate or payment flows fail silently.
- Do I earn from it?
- Yes. A brand-new OroPocket account created through your embed is attributed to you, so that user's buys earn your commission — 1%, or 2% on Pro. A user who already had an OroPocket account is never attributed.
- Can I try it before writing any app code?
- Yes. The Playground has an Embed tab that runs the whole flow in a phone simulator in your browser. The sandbox OTP is always 1234.
Start with a key, not a meeting.
Verify a mobile number, pick what you are building, and your sandbox key is on the screen.