Indonesia licensed operator control plane
Run an Indonesia operator-control plane across operator admission, segregated Rupiah funding, listed-asset execution, custody segregation, reporting registers, and reconciled close without public quote display.
Overview
Indonesia operator controls keep admission, segregated Rupiah funding, listed-asset execution, and reporting close aligned.
Indonesia licensed operator control plane. StableNexus coordinates operator admission, segregated Rupiah funding, listed-asset execution, custody segregation, and reporting close while bank, clearing, and custody roles stay explicit.
Route coverage
- 4-stage Indonesia operator control plane
- Admission, safeguarded funds, approved-asset controls, and licensed execution
- Segregated client-money, clearing placement, and custody booking
- Reporting-register release with segregation booking and matched bank, clearing, and custody records
Infrastructure
- OJK and BI boundaries stay explicit across bank, clearing, custody, and reporting surfaces
- Segregated client-money and funding-status controls
- Listed-asset execution with clearing continuity and custody settlement
- Reporting registers, notice logs, and archive-ready close records
Lifecycle stages
| Stage | Flow steps |
|---|---|
| Operator Perimeter | Confirm the licensed entity, official-channel perimeter, participant cohort, and approved-asset scope; Bind investment-only, payment-use prohibition, Travel Rule, and retention controls before any cash movement; Record the operator run against the named legal entity, licence state, and perimeter decision; Unlock bank and clearing steps only after the perimeter review is complete |
| Banked Customer Funds | Confirm the segregated client-money account, approved IDR bank surface, and available Rupiah prefund; Match bank status, statement evidence, and clearing placement before release; Keep safeguarded-funds and bank-bind controls visible to operations and finance; Arm the execution route only after bank and operator balances agree |
| Licensed Execution And Custody | Select the listed-asset route and keep quote visibility internal to the operator desk; Link clearing, settlement, and custody booking to one operator reference; Confirm the licensed custody-place-manager segregation outcome before the position is treated as booked; Preserve the bank and custody ledger snapshot for reporting |
| Reporting And Close | Match bank, trade, clearing, and custody records on the reporting cycle; Resolve open exceptions before the reporting register is published; Release the archive manifest, notice log, and reporting exports on the same run; Close the operator cycle on published records rather than narrative follow-up |
Setup reference
| Field | Explanation | Related terms |
|---|---|---|
| Operator funding amount | Sets the amount carried from funding lock through execution, custody allocation, and beneficiary close. | |
| Execution channel | Determines which licensed execution path the operator uses before custody and bank exit. | Licensed digital-asset operator |
| Traded product | Fixed for this case. Scoped to one licensed digital-asset product so policy, execution, and custody stay aligned. | |
| Trade direction | Fixed for this case. Sets whether the operator is buying or selling into the controlled execution and custody flow. | |
| Custody posture | Fixed for this case. Keeps custody allocation and segregation rules explicit after execution. | |
| Settlement method | Fixed for this case. Keeps bank funding, trade settlement, and close on the same operator evidence path. | |
| Counterparty class | Fixed for this case. Keeps the workflow inside the licensed-operator perimeter rather than a retail or consumer-facing route. |