MY regulated DAX treasury
Malaysia treasury converts admitted digital-asset balances into banked MYR through venue funding, regulated DAX execution, withdrawal control, and finance-close evidence.
Overview
Admitted digital-asset treasury balances convert into bank-usable MYR through funded regulated execution and controlled withdrawal.
Local treasury withdrawal workflow. StableNexus keeps mandate approval, venue funding, trade proof, and bank-close evidence aligned while regulated execution and bank release remain partner-led.
Route coverage
- 4-stage MY treasury-to-bank workflow
- Mandate, beneficiary, and withdrawal-authority controls
- Venue funding, booked balance, and regulated DAX trade confirmation
- Bank credit callback and finance-close publication
Infrastructure
- Treasury mandate and beneficiary-control packet
- Venue funding and booked-balance checkpoint
- Regulated DAX trade confirmation and MYR proceeds visibility
- Withdrawal release, bank credit, and finance-close evidence
Lifecycle stages
| Stage | Flow steps | Notes |
|---|---|---|
| Local Treasury Scope | Capture admitted asset inventory, named beneficiary account, and withdrawal authority on one mandate packet; Keep source-wallet authority and venue-admission basis visible before any deposit is released; Do not imply execution can start before the beneficiary bank mandate is accepted; End this stage on an approved funding mandate, not a generic ready queue | Step 1 should read like mandate approval and beneficiary control software, not a generic treasury intake card. |
| Venue Funding | Separate venue funding proof from trade execution; Show deposit credit, booked balance, and tradeable release as distinct facts; Treat the booked balance as the control point for opening the sell order; Finish on funded venue capacity, not hypothetical inventory | Step 2 must show credited venue balance before execution opens. |
| Regulated Execution | Read like institutional DAX execution software, not a payout queue; Keep order acknowledgement, fill confirmation, and MYR proceeds posting separate from bank withdrawal; Avoid bank-withdrawal labels until the close stage opens; Preserve trade confirmation as finance-grade evidence, not generic execution copy | Step 3 cannot inherit bank-withdrawal grammar before trade confirmation is complete. |
| Withdrawal Close | Show withdrawal release, bank credit, and finance close as separate records; Keep the named beneficiary bank destination visible through the close stage; Do not publish cash availability until the bank-credit callback is confirmed; End on banked-MYR proof and close-pack publication | Final state must show bank-confirmed MYR plus finance-close publication, not just a released withdrawal. |
Setup reference
| Field | Explanation |
|---|---|
| Treasury amount | Sets the value carried through conversion, withdrawal, and close. Determines the amounts shown across the workflow records. |
| Source position | Links the workflow to a specific funding record. Determines which source position the route starts from. |
| MYR recipient | Identifies who receives the payout. Determines who is checked and named in the payout records. |
| Bank destination | Identifies where MYR is paid out. Determines the bank route used at release and close. |
| Venue path | Supports more than one execution style. Controls how the conversion leg is sourced before withdrawal. |
| Source asset | Fixed for this case. Scoped to one source asset. |