OroPocket
Hosted embed

See your users and their transactions

Two pages in the Operate section answer almost every support question you will get: who is this customer, and what did they do. Both are scoped to your own users and mask identity by default.

4 min read · 3 screenshots

Users

Users lists everyone you have registered in the mode you are currently in. You address people by user_code — the internal account id is never exposed to a partner, and mobile numbers and emails are masked.

The Users page of the OroPocket developer dashboard, showing a searchable table of registered users with columns for user code, name, masked mobile, KYC status, gold and silver holdings and registration date.
Fifty per page. The search box filters the page you are on, not the whole set.

  1. Find the customer

    Search accepts a user_code, a name, a mobile or a KYC status. If you are hunting a specific person, the code is the reliable key — names are whatever was supplied at registration.

  2. Open the detail drawer

    Clicking a row slides in a panel with the full picture: the copyable user_code, masked contact details, KYC state, whether they already had an OroPocket account before you registered them, and their holdings.

    The user detail drawer in the OroPocket dashboard, showing a copyable user code, masked mobile and email, KYC status, registration date and a holdings breakdown for gold, silver and INR.
    Holdings shown here are the balances held under your integration, not the person's entire OroPocket portfolio.
    Pre-existing matters more than it looks. Someone who already had an OroPocket account before you registered them keeps their own relationship with us — you see what they hold through you, not everything they own.

Transactions

Transactions is the unified feed: every buy, sell, SIP debit and gift across all your users, however it was made. The Type column carries a channel label, which is the part worth reading.

The Transactions page of the OroPocket developer dashboard, showing a table of trades with columns for when, type, user, asset, amount, grams, rate per gram and reference, and channel labels beside each type.
Buys, sells, SIP debits and gifts in one feed, with the channel each came through.
ChannelMeans
APIA server-to-server call your backend made — a quote you confirmed.
HostedMade inside our interface: either the hosted embed or your white-label site. The two cannot be told apart, because the underlying order records no session.
AppMade by the user in the OroPocket consumer app, attributed to you.
SIPAn installment of a recurring plan, or the creation of one.
If you are building against the API rather than reading the dashboard, use GET /partner/transactions/all for this feed. GET /partner/trades reads consumed quote rows only, so it is always empty for hosted and white-label activity — that difference has caught out more than one integration.

Test mode shows test data

Both pages follow the Test/Live toggle. In Test mode rows carry a Test badge and the users are sandbox users — created by your own calls, holding simulated balances. Switching to Live shows real customers and real trades, and nothing crosses between the two.

Empty in Test mode? Nothing has happened yet. Run a test buy and both pages fill in within seconds.
← Test a hosted embedMake your first API call →