https://sandbox-api.nuvante.ioGuides
Settlement modes
Issuers work in different ways, and they all sit behind one public API. The engine works out the mode from each issuer's profile, so you never have to deal with it directly.
You never send a mode
Leave the mode out of your transaction request. Nuvanté works out the order of steps from the source issuer's declared capability profile and takes a snapshot of it when the transaction starts.
Compare the modes
Delegated signing
Nuvanté coordinates issuer operations using delegated signing and observes the resulting ledger transaction.
Two-phase instruction
The issuer authorises and executes an instruction asynchronously. Nuvanté waits for verified burn or mint proof.
Single-phase instruction
The member asset must move or be atomically transferred before the issuer can execute the burn.
Settlement waits for proof
An issuer authorising an operation doesn't make it final on the ledger. Nuvanté never starts RTGS settlement because an issuer says it has authorised or is executing something. Settlement only moves forward after a verified Burned event that carries on-chain proof.
Swaps have two issuer legs
A swap burns the source asset and mints the target asset. Each issuer can have its own mode, approval SLA, adapter and registered wallet handle. Sandbox captures each leg's settings separately, so you can try any configured mix of Mode 1 and Mode 2. The target mint path is never guessed from the source issuer.