For gold and silver institutions
Organize gold and silver operations
An institution working with gold and silver faces the same questions every day: whose gold is this, at what price was this trade approved, which customer’s leasing contract is running. HOLD OS is built to answer exactly these questions.
- Gold Its own identity, unit and reference price
- Silver Its own identity, unit and reference price
- Custom When the institution needs one
Shared financial core One logic for both metals
Familiar operational challenges
These challenges come from the nature of handling precious metals for many customers, not from a statistic or a special claim.
- Two metals, similar units
- Gold and silver are both weighed in grams, and mixing them up in records is a costly error.
- The price that actually governs a trade
- The day’s reference price and each trade’s agreed price need to be recorded separately.
- Approvals you can trace
- It must be clear who approved each trade and under what authority.
- Each customer’s holdings
- Each customer’s assets must stay apart from other customers’ assets and from cash.
Gold and silver, each with its own identity
In HOLD OS gold and silver are two separate assets with stable identities, even when their unit is the same.
| What to evaluate | How HOLD OS approaches it |
|---|---|
| Same unit | Separate identity; a gram of Gold is never added to or swapped with a gram of Silver. |
| Reference price | Recorded manually and separately for each metal. |
| Wallet | Each metal has its own wallet, and every account one shared cash wallet in whole toman. |
| Default asset changes | Earlier records of each metal stay that metal. |
From customer to trade
A typical gold and silver workflow in HOLD OS runs like this.
-
Customer account
The institution creates the customer account through a private process.
-
Metal wallet
A Gold or Silver wallet in the customer’s account.
-
Trade request
A purchase or sale is recorded with explicit quantity and price.
-
Approval
Someone with authority for that account and that metal approves it.
-
Record
The result is recorded under that metal’s identity in the customer’s account.
Leasing gold and silver, when you need it
If your institution places metals with others under a leasing contract, HOLD OS keeps the metal principal and the rent as two separate obligations. The principal must return in the same metal, unit and standard, and rent is settled separately under the approved policy.
Each metal needs an approved leasing profile covering its standard, custody and delivery method, calculation policy and calendar.
Leasing contract Metal, quantity and approved terms
- Metal principal Returned in full, same metal and standard
- Rent A separate obligation in the same metal or whole toman
A clear view for management
For an institution’s management, the main value of this structure is accountability: every balance belongs to a specific account and metal, every trade has a specific price and approver, and every contract has separate, traceable obligations.
Choosing the active and default metals rests with the general administrator; ordinary administrative access does not grant that authority.
Fit questions
Your answers show which parts of HOLD OS matter most for your institution.
Do you work with gold only, or gold and silver?
In single-asset mode HOLD OS hides the unnecessary selector; in multi-asset mode it offers a shared selector with a separate price for each metal.
How are trade prices set?
HOLD OS does not pull automatic market prices; reference prices and each trade’s price are recorded manually and explicitly.
Do you run metal leasing contracts?
If so, the walkthrough covers the approved leasing profile for each metal and how principal and rent are kept apart.
See your gold and silver operations in HOLD OS
Describe your gold and silver operations in your email so the walkthrough focuses on this workflow.