Mode 2: two-phase instruction

The issuer authorises an instruction and then carries it out on its own. The member doesn't have to transfer any tokens before the burn.

Order of steps

The member's source asset is locked and the RTGS leg is earmarked.
Nuvanté sends a burn instruction to the issuer adapter.
The issuer may accept and authorise the instruction asynchronously.
Nuvanté keeps polling while the issuer carries it out.
A verified on-chain burn proof moves RTGS settlement forward.
If the issuer rejects the instruction, the transaction unwinds automatically as long as that's still safe. If it fails or goes silent, the transaction parks for review.

Authorisation comes before settlement

InstructionAuthorised tells us the issuer has accepted the operation. The tokens may not have been destroyed yet. An issuer's equivalent of EXECUTING stays inside its adapter. Neither of these statuses can trigger RTGS settlement.

Approval budget

Polling runs for the issuer's declared approvalSlaSeconds. If that time runs out without a final result, the instruction becomes ParkedOnSilence and an operator needs to investigate.

Sandbox availability

Mode 2 is available to participants who have an issuer configured with an ON_INSTRUCTION profile. Both redemptions and swaps can use simulated Mode 2 issuer legs, and each issuer in a swap is configured and captured separately. Your transaction payload stays exactly the same, because the mode comes from the issuer's capability profile. To set up a profile, see Issuer capability declaration and onboarding.