Nuvanté Technologies logo
Sandbox APIhttps://sandbox-api.nuvante.io

Settlement modes

Mode 1: delegated signing

The issuer gives Nuvanté narrowly scoped signing authority. The issuer commits at the moment the operation is observed on-chain.

Order of steps

  1. The member's source asset is locked.
  2. Nuvanté asks for an RTGS earmark.
  3. The delegated issuer operation burns the source asset.
  4. Nuvanté verifies the on-chain burn proof.
  5. The engine settles the earmarked RTGS leg.
  6. For a swap, the target asset is minted to the member.

Control and custody

Delegated signing leaves beneficial ownership of member assets and fiat exactly where it was. Nuvanté can only perform the specific issuer operation you've configured, and anyone can see the resulting ledger transaction.

Delegation verification

Before Mode 1 goes live, call POST /api/v1/issuers/{issuerId}/custody/verify-delegation. Nuvanté inspects your on-chain account itself to confirm the operator key has been added, so you don't need to vouch for it. This works the same way for self-custody, MPC and CaaS, because only the resulting account state matters.

Code sample
POST https://sandbox-api.nuvante.io/api/v1/issuers/{issuerId}/custody/verify-delegation

{
  "chain": "stellar",
  "accountId": "GABC...ISSUERACCOUNT"
}

If the response says meetsPolicyRequirement: false, it also includes a reason field, such as operator_key_not_found or threshold_too_low. You can fix your configuration and verify again without raising a support ticket.

Sandbox availability

Mode 1 is the default sandbox path for issuers that don't have an instruction-based profile. Use the standard transaction endpoint. There's no mode parameter to set.