SG-MY Regulated Off-Ramp
Named MYR beneficiaries receive funds through screened intake, cutoff-safe route lock, regulated conversion, bank submission, credit advice, and reconciled close.
Operating thesis
Four-stage corridor control plane that routes 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.
Actor-lane operating map
Six actors on one governed corridor lane.
Phase map
How the four chapters sequence.
Canonical chapters
| Chapter | Outcome | Lifecycle states |
|---|---|---|
| Corridor intake and beneficiary pre-clearance | Source admissibility cleared, supporting-document basis attached, beneficiary identity validated, beneficiary-bank match cleared, release conditions known. | Intake open · Intake held · Pre-clear cleared |
| Booked-rate lock, cutoff, and route admissibility | Route admissibility positive, quote lock live, expiry explicit, cutoff posture explicit, fallback route basis explicit, execution release basis explicit. | Route lock open · Route locked · Route lock expired |
| Regulated venue execution and MYR availability | Execution commit confirmed, status path known, MYR availability confirmed, bank release not yet assumed complete, beneficiary credit not yet implied. | Execution handoff pending · Execution committed · MYR available |
| Bank submission, credit confirmation, and close | Release conditions rechecked, submission receipt exists, beneficiary credit confirmed, close register reconciled, close pack published. | Bank release armed · Bank submitted · Credit confirmed · Close reconciled · Closed · Replay recovery |
Control overlay matrix
| Overlay | Active in chapters | Scope |
|---|---|---|
| Beneficiary verification | Corridor intake and beneficiary pre-clearance; Bank submission, credit confirmation, and close | Control overlay across active chapters |
| Route admissibility | Corridor intake and beneficiary pre-clearance; Booked-rate lock, cutoff, and route admissibility | Control overlay across active chapters |
| Quote lock / expiry | Booked-rate lock, cutoff, and route admissibility | Control overlay across active chapters |
| Cutoff / operating window | Booked-rate lock, cutoff, and route admissibility; Bank submission, credit confirmation, and close | Control overlay across active chapters |
| Execution callback / status confirmation | Regulated venue execution and MYR availability | Control overlay across active chapters |
| Idempotent release / replay-safe recovery | Regulated venue execution and MYR availability; Bank submission, credit confirmation, and close | Control overlay across active chapters |
Lifecycle states
Intake hold, route lock expiry, replay recovery, and cancellation are distinct branches. Operational completion requires credit confirmed, close reconciled, and close pack published.
Technical closeout sequence
From MYR availability through bank submission, credit advice, and reconciled close.
Evidence and status matrix
| Chapter | Runtime artifacts | Docs-derived surfaces and evidence |
|---|---|---|
| Corridor intake and beneficiary pre-clearance | Source funding confirmation · Beneficiary packet · Corridor packet | Corridor intake packet · Beneficiary pre-clear state | Signals: Source screening passed · Supporting docs attached · Beneficiary-bank match passed · Release conditions bound |
| Booked-rate lock, cutoff, and route admissibility | Quote sheet · Route decision · Execution approval | Route lock state | Signals: Route admissible · Cutoff window confirmed · Quote lock live · Fallback route defined |
| Regulated venue execution and MYR availability | Source handoff receipt · MY venue credit confirmation · MY conversion report | Execution commit state · MYR availability state | Signals: Execution commit received · Settlement callback received · MYR available confirmed · Release gate passed |
| Bank submission, credit confirmation, and close | Payout release approval · Payout reference · Reconciliation snapshot | Bank credit confirmation state · Close register state | Signals: Bank submission receipted · Beneficiary credit confirmed · Close register reconciled · Close pack published |
Support docs
- Treasury conversion and off-ramp family: Parent family overview with all cases in this family.
- Partner control plane: Shared control-plane context for partner connectivity.
- Callback automation: Signed delivery, replay, and poll fallback for callback and status semantics.
- Evidence and replay: Replay-safe recovery and close proof.
- Reference preview and routing: Route-admissibility and pricing-context distinction.
- Geo availability: Market and service posture context.
- Interactive case: Run this case interactively on the public proof surface.
- Case projector: View the full-screen projector for this case.
Required corridor inputs
- Corridor amount
- Value carried across funding, route lock, execution, and payout.
- Source funds
- Source treasury position and funding basis.
- Beneficiary
- Named recipient identity used in pre-clearance and payout records.
- Payout destination
- Destination-bank route used in pre-clearance and release.
- Conversion route
- Route selection input for admissibility and lock.
- Source asset
- Fixed to USDC in the current public case framing.
Glossary
- Regulated exit
- The conversion and bank-payout leg that completes under regulated local rails.
- Route admissibility
- The approval-grade decision that a named corridor, beneficiary, bank route, cutoff window, and fallback posture are valid before execution release.
- MYR availability
- The confirmed state in which converted MYR is available for bank release. Not the same as beneficiary credit.
- Close register
- The final reconciled operational record for a corridor run: submission, credit confirmation, reconciliation snapshot, and close-pack publication together.
- Receiving-institution confirmation
- Proof that the destination institution accepted and credited the movement.