SG-MY regulated off-ramp
Route screened Singapore treasury stablecoin balances into named MYR beneficiaries through corridor pre-clearance, cutoff-safe route lock, regulated venue conversion, bank submission, and reconciled close.
Overview
Screened SG treasury conversion into named MYR beneficiaries with booked-rate lock, regulated venue execution, and bank-close proof.
Treasury corridor control plane. StableNexus keeps intake screening, route admissibility, regulated conversion, and bank-close evidence aligned while execution and payout delivery remain partner-led.
Route coverage
- 4-stage SG to MY regulated treasury corridor
- Intake screening, beneficiary bank match, and route admissibility
- Cutoff-safe route lock with regulated conversion and MYR availability
- Bank submission, credit advice, and reconciled close-pack evidence
Infrastructure
- Corridor intake and admissibility desk
- Beneficiary-bank match and release-condition controls
- Regulated venue plus settlement-account boundary visibility
- Bank submission, credit advice, and close-register continuity
Lifecycle stages
| Stage | Flow steps | Notes |
|---|---|---|
| Funding Verification | Capture source funding, payment purpose, and document basis before pricing opens; Match beneficiary identity, receiving bank, and release constraints on one intake packet; Clear SG source screening and beneficiary-bank admissibility before route lock opens; Publish a screened corridor packet instead of stopping at a ready queue item | Step 1 must end in a cleared corridor packet with both sides pre-cleared, not just a captured request. |
| Quote Route Lock | Compare regulated routes on booked rate, cutoff, and delivery posture; Keep expiry, fallback, and approval basis visible on the same route desk; Lock the approved route file before any source handoff occurs; Treat route admissibility as execution control rather than later close evidence | The route desk should read like approval-grade treasury software, not a lightweight quote card. |
| Execution Regulated Exit | Keep source handoff, venue fill, MYR availability, and bank-release readiness as separate facts; Show the regulated venue boundary without implying StableNexus is the executing principal; Do not arm bank release until MYR credit availability is confirmed; Preserve order, fill, and release-readiness records on the same run | This is the main realism boundary and cannot collapse into a generic execution blotter. |
| Beneficiary Payout Reconciliation | Match release conditions before the bank submission is sent; Track submission receipt, credit advice, and reconciliation as separate close records; Publish the close pack only after beneficiary credit is confirmed; Finish on reconciled evidence rather than a generic released status | Final state must show bank-confirmed delivery and close-pack evidence, not in-flight payout language. |
Setup reference
| Field | Explanation |
|---|---|
| Corridor amount | Sets the value carried through funding, quoting, conversion, and payout. Determines the amounts shown across the workflow records. |
| Source funds | Links the workflow to a specific funding record. Determines which source position the route starts from. |
| Beneficiary | Identifies who receives the payout. Determines who is checked and named in the payout records. |
| Payout destination | Identifies where MYR is paid out. Determines the bank route used at release and close. |
| Conversion route | Supports more than one execution path. Controls how the conversion leg is sourced before payout. |
| Source asset | Fixed for this case. Scoped to a USDC-funded corridor. |