Vietnam licensed operator control plane
Run a Vietnam licensed-operator control plane across participant eligibility, authorized-bank VND settlement readiness, licensed execution, segregated custody booking, regulatory reporting, and reconciled close.
Overview
Vietnam market-operator controls keep licensed perimeter, special-account funding, OTC execution, and reporting aligned.
Pilot-only operator control plane. StableNexus keeps perimeter, authorized-bank VND settlement, licensed execution, custody booking, and reporting visible on one Vietnam route.
Route coverage
- 4-stage Vietnam operator control plane
- Perimeter admission, participant eligibility, and asset-scope controls
- Authorized-bank VND bind, licensed execution, and segregated booking
- Reporting-register release, archive manifest, and reconciled close
Infrastructure
- Authorized-bank VND account and settlement-control surfaces
- Perimeter, participant-class, and asset-scope controls
- Licensed execution with linked cash-leg and custody booking
- Reporting registers, archive manifests, and reconciled close records
Lifecycle stages
| Stage | Flow steps |
|---|---|
| Operator Perimeter | Confirm the licensed entity, participant classes, and admitted asset scope; Block excluded-asset and payment-use interpretations before the route opens; Record the operator run against the licence and filing references; Release the bank-bind step only after perimeter controls are complete |
| Banked Customer Funds | Confirm the special VND account and the authorized-bank settlement profile; Clear bank document, AML, and segregation checks before execution is armed; Keep custody bind, settlement cut-off, and reporting hooks visible on the route; Treat the bank bind as execution readiness, not generic bank status |
| Licensed Execution And Custody | Lock the licensed execution route, quote basis, and trade reference on the operator desk; Link the VND cash leg and custody settlement under one governed execution record; Publish the segregated booking only after both legs confirm; Preserve the synchronized bank, settlement, and custody ledgers for reporting |
| Reporting And Close | Match bank, execution, settlement, and custody ledgers on the reporting cycle; Generate the reporting register, disclosure decision, and archive manifest together; Resolve exceptions before the close pack is published; Close the route on named regulatory records rather than a generic export bundle |
Setup reference
| Field | Explanation | Related terms |
|---|---|---|
| Operator VND notional | Sets the amount carried from perimeter intake through execution, custody settlement, and reconciled close. | |
| Approved asset | Sets which approved asset the operator is handling in the Vietnam market-ops flow. | |
| Operator intent | Sets whether the operator is buying or selling into the controlled VND settlement flow. | Licensed digital-asset operator |
| Operator entity | Fixed for this case. Keeps the workflow tied to one operator perimeter and one evidence boundary. | |
| Participant class | Fixed for this case. Keeps the workflow inside the licensed-operator market perimeter rather than a retail or merchant route. | |
| Linked bank account | Fixed for this case. Provides the linked Techcombank-facing bank account used for bank-status and settlement-control checks. | |
| Custody account | Fixed for this case. Provides the custody scope used after execution and through reconciled close. |