Issuer capability profiles

Every issuer declares a versioned capability profile during onboarding. When a transaction starts, the engine takes a snapshot of that profile and uses it to decide the order of settlement steps. Callers never send a mode themselves.

Start with the profile

The profile is the agreement between you and Nuvanté. Fields like commitPoint, preBurnTransferRequired, custody, feedback channel and approvalSlaSeconds describe how you actually operate as an issuer. Mode 1, 2 or 3 is simply the label the engine gives to that combination of fields. Get comfortable with the fields first, then read Settlement modes. You don't need either before your first API call.

When you update your profile, the change applies to transactions started after the update. Transactions already in flight keep the snapshot they started with.

Declared fields

commitPointON_OBSERVATION or ON_INSTRUCTIONWhen the issuer commits to the operation.

preBurnTransferRequiredbooleanFor instruction-based issuers, chooses between Mode 2 and Mode 3.

custodyModelPER_MEMBER_ISSUER_WALLET or POOLED_ISSUER_WALLETHow the issuer's wallets are structured (one per member, or pooled). See the note below.

mintDeliveryTargetenumWhere minted tokens go: a raw address, a registered handle, or an omnibus account that forwards them.

feedbackChannelenum[]How you report status: signed webhook, polling, on-chain observation, or a mix.

fiatLegenumWhich party submits or owns the fiat settlement leg.

ledgerstringThe ledger family the issuer adapter uses.

finalityClassDETERMINISTIC or PROBABILISTICWhich proof-verification policy applies.

amountPrecisionintegerThe maximum number of decimal places accepted at the API.

approvalSlaSecondsinteger or nullYour time budget for approving instructions asynchronously.

Example simulated profile

Code sample

{
  "commitPoint": "ON_INSTRUCTION",
  "preBurnTransferRequired": false,
  "custodyModel": "PER_MEMBER_ISSUER_WALLET",
  "mintDeliveryTarget": "REGISTERED_HANDLE",
  "feedbackChannel": ["POLLABLE_RESOURCE"],
  "fiatLeg": "NUVANTE_SETTLES_RTGS",
  "ledger": "solana",
  "finalityClass": "PROBABILISTIC",
  "amountPrecision": 2,
  "approvalSlaSeconds": 45
}

This profile results in Mode 2. You set it up during issuer onboarding, and it can't be sent as part of a public transaction request.

Testnet policy

Sandbox chain integrations use Stellar Testnet, Polygon Amoy (chain ID 80002) or Solana Devnet. Issuer credentials can't be used to connect to mainnet.

Registered handles

Some issuer APIs identify wallets with an ID assigned at onboarding, such as walletId, in place of a raw chain address. Your integration has to resolve that handle explicitly. Please don't make up an address field the API doesn't support.